Job Management Partner 1 Version 10 Job Management Partner 1/Base Messages

3021-3-302-20(E)

Notices

Relevant program products

For details about the supported operating systems and the service packs or patches that are required by Job Management Partner 1/Base, see the Release Notes.

For Windows:

P-2W2C-6LAL Job Management Partner 1/Base 10-50

The above product includes the following:

P-CC242C-6LAL Job Management Partner 1/Base 10-50 (for Windows XP Professional, Windows Server 2003)

P-CC2A2C-6LAL Job Management Partner 1/Base 10-50 (for Windows Vista, Windows Server 2008, Windows 7, Windows Server 2012, Windows 8, Windows 8.1)

For UNIX:

P-1J2C-6LAL Job Management Partner 1/Base 10-50 (for HP-UX (IPF))

P-9D2C-6LAL Job Management Partner 1/Base 10-50 (for Solaris (SPARC))

P-1M2C-6LAL Job Management Partner 1/Base 10-50 (for AIX)

P-812C-6LAL Job Management Partner 1/Base 10-50 (for Linux 5 (x86), Linux 5 (AMD/Intel 64), Linux 6 (x86), Linux 6 (AMD/Intel 64))

These products have been developed under a quality management system which has been certified to comply with ISO 9001.

Trademarks

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

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

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

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

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

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

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

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

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

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

POSIX stands for Portable Operating System Interface for Computer Environment, which is a set of standard specifications published by the Institute of Electrical and Electronics Engineers, Inc.

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

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

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

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

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

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

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

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

XPG4 stands for X/Open Portability Guide Issue 4, which is a set of specifications published by X/Open Company Limited.

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

The following program product contains some parts whose copyrights are reserved by Oracle Corporation, its subsidiaries, or affiliates: P-9D2C-6LAL

The following program product contains some parts whose copyrights are reserved by UNIX System Laboratories, Inc.: P-9D2C-6LAL

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

Microsoft product name abbreviations

This manual uses the following abbreviations for Microsoft product names.

Abbreviation

Full name or meaning

Hyper-V

Microsoft(R) Hyper-V(R)

Microsoft Cluster Server

Microsoft(R) Cluster Server

Microsoft Internet Explorer

Microsoft(R) Internet Explorer

Windows(R) Internet Explorer(R)

Visual C++

Microsoft(R) Visual C++(R)

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

Windows(R) 8 Pro

Windows(R) 8 Enterprise

Windows 8.1

Windows(R) 8.1

Windows(R) 8.1 Pro

Windows(R) 8.1 Enterprise

Windows NT

Microsoft(R) Windows NT(R) Server Enterprise Edition Version 4.0

Microsoft(R) Windows NT(R) Server Network Operating System Version 4.0

Microsoft(R) Windows NT(R) Workstation Operating System Version 4.0

Windows Server 2003

Windows Server 2003

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

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

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

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

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

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

Windows Server 2003 (x64)

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

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

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

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

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

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

Windows Server 2008

Windows Server 2008

Microsoft(R) Windows Server(R) 2008 Datacenter

Microsoft(R) Windows Server(R) 2008 Enterprise

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

Microsoft(R) Windows Server(R) 2008 Standard

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

Windows Server 2008 R2

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

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

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

Windows Server 2012

Windows Server 2012

Microsoft(R) Windows Server(R) 2012 Datacenter

Microsoft(R) Windows Server(R) 2012 Standard

Windows Server 2012 R2

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

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

Windows Vista

Microsoft(R) Windows Vista(R) Business

Microsoft(R) Windows Vista(R) Enterprise

Microsoft(R) Windows Vista(R) Ultimate

Windows XP

Windows XP Professional

Microsoft(R) Windows(R) XP Professional Operating System

Windows is sometimes used generically, referring to Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2012, Windows 8, and Windows 8.1.

Windows Vista and later is sometimes used generically, referring to Windows Vista, Windows Server 2008, Windows 7, Windows Server 2012, Windows 8, and Windows 8.1.

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.

Edition history

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

Copyright

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

Summary of amendments

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

Changes

Location

The following OSs were added to the supported OSs:

Windows 8.1

Windows Server 2012 R2

--

The following functions were added to suppress forwarding of large numbers of events:

Event-forwarding suppression using an event-forwarding suppression command (jevagtfw command)

Event-forwarding suppression using a threshold

User's Guide: 2.5, 3.1, 3.2.3(6), 3.3.4(6), 4.1, 4.8, 10.1.1, 10.1.2, 10.1.8, 10.1.9, 15. Commands, 15. jevagtfw, 15. jevfwstat, 15. jevreload, 16. Event server settings file, 16. Forwarding settings file, 16. Action definition file for log file trapping, 18.5.1(1), A.1, A.2, C.1, Appendix P

Messages: --

Function Reference: --

Descriptions about the JP1 events to which local action execution conditions are applied were added.

User's Guide: 2.8.1, 16. Local action execution definition file

Messages: --

Function Reference: --

HNP_Admin was added to the permissions that are granted to JP1 users at initial settings for user management.

User's Guide: 3.2.1, 3.3.1

Messages: --

Function Reference: --

Descriptions about the language type in the LANG environment variable for an automated startup script were added.

User's Guide: 3.4.1, 3.4.1(1), 5.8.3, 7.2.1, 15. jbs_start (UNIX only), 15. jbs_start.cluster (UNIX only)

Messages: --

Function Reference: --

Japanese UTF-8 is now supported as a language type in JP1/Base in HP-UX, Solaris, and AIX.

User's Guide: 3.4.1

Messages: --

Function Reference: --

The jbsgetcnf command can now be used to collect definition information by specifying a component.

User's Guide: 3.5.2(1)(b), 3.5.3(1)(b), 15. jbsgetcnf

Messages: --

Function Reference: --

Exclusive control can now be enabled or disabled when outputting to an integrated trace log.

User's Guide: 4.6, 15. hntr2conf, 15. hntr2getconf, 16. Action definition file for log file trapping

Messages: --

Function Reference: --

The jbshostsimport command can now be used to forcibly register the jp1hosts information in an environment where jp1hosts2 information is specified.

Descriptions about the behavior when both jp1hosts information and jp1hosts2 information is specified were also added.

User's Guide: 5.6.1(4), 6.4.3, 6.4.4(2), 6.4.6, 6.6.1, 6.6.2, 15. jbshostsimport

Messages: --

Function Reference: --

Notes on event service communication settings were added.

User's Guide: 6.5.1(4), 6.6.3

Messages: --

Function Reference: --

Notes on using log file trapping to monitor a Unicode file in Windows were added.

User's Guide: 11.1.3(3)

Messages: --

Function Reference: --

The JP1/Base setup information can now be collected by one operation.

User's Guide: 15. Commands, 15. jbsparamdump, 16. Definition Files, 16. Collection information file, A.1, A.2

Messages: --

Function Reference: --

Notes on using the jbsmkumap and jbssetumap commands to register user mapping information in the common definition information were added.

User's Guide: 15. jbsmkumap, 15. jbssetumap

Messages: --

Function Reference: --

Notes on using the jbssetcnf command to change the JP1/AJS common definition information were added.

User's Guide: 15. jbssetcnf

Messages: --

Function Reference: --

In Windows, Unicode (UTF-8)-formatted log files are now supported for monitoring by log file trapping.

User's Guide: 15. jevlogstart, 16. Action definition file for log file trapping

Messages: --

Function Reference: --

The following JP1 events were added:

00003D05, 00003D06, 00003D07, 00003D08, 00003D09, 00003D0B, 00003D0C, 00003D0D, 00003D0E

User's Guide: 17.2, 17.3.1

Messages: --

Function Reference: --

The extended attributes that are set to a JP1 event issued by the log file trapping function now include a monitor ID and monitor name.

User's Guide: 17.3.1(28)

Messages: --

Function Reference: --

The following items were added to the information that can be collected by the data collection tool:

Assigning user rights

Group policy

Range of dynamic ports (IPV4)

Range of dynamic ports (IPV6)

Exclusive control of the integrated trace log

Output destination of the integrated trace log

User's Guide: 18.3.1(1), 18.3.1(2), 18.3.2(2)

Messages: --

Function Reference: --

The number and size of the configuration management log files were changed.

User's Guide: A.1(2), A.2(2)

Messages: --

Function Reference: --

Descriptions about the parameters defined in the communication protocol settings file were added.

User's Guide: H.10

Messages: --

Function Reference: --

Descriptions about the differences between the communication protocols of JP1/Base version 06-51 or earlier and JP1/Base version 06-71 or later were added.

User's Guide: H.11

Messages: --

Function Reference: --

Descriptions about the communication protocols specified during cluster setup were added.

User's Guide: H.12

Messages: --

Function Reference: --

Descriptions about the messages that are output when a request is denied by connection restriction were added.

User's Guide: M.5

Messages: --

Function Reference: --

The following messages were added:

KAJP1083-W, KAJP1084-I, KAJP1085-I, KAJP1086-W, KAJP1087-W, KAJP1350-I, KAJP1351-I, KAJP1352-E, KAJP1401-I, KAJP1402-E, KAJP1403-E, KAJP1404-I, KAJP1405-I, KAJP1406-E, KAJP1407-E, KAJP1408-I, KAJP1410-I, KAJP1411-E, KAJP1413-I, KAJP1414-I, KAJP1415-E, KAJP1416-I, KAJP1417-I, KAJP1418-I, KAJP1419-I, KAJP1420-I, KAJP1421-I, KAJP1422-I, KAJP1423-E, KAJP1424-I, KAJP1425-E, KAJP1426-I, KAJP1427-I, KAJP1428-I, KAJP1429-I, KAJP1430-I, KAJP1431-I, KAJP1432-E, KAJP1433-I, KAJP1434-E, KAJP1435-E, KNAM9001-I, KNAM9002-I, KNAM9003-E, KNAM9004-E, KNAM9005-E, KNAM9006-E, KNAM9007-E, KNAM9008-E, KNAM9009-E, KNAM9010-E, KNAM9011-W, KNAM9012-I, KNAM9013-E, KNAM9014-E, KNAM9015-W, KNAM9016-W, KNAM9020-I, KNAM9021-E, KNAM9022-I, KNAM9023-E, KNAM9024-I, KNAM9025-E, KNAM9026-I, KNAM9027-E, KNAM9028-W

User's Guide: --

Messages: 1.2.1, 1.2.17, 1.4.1, 2.1, 2.17

Function Reference: --

The following messages were modified:

KAJP1033-E, KAVA0443-E, KAVA0590-E, KAVA0592-E, KAVA0678-E, KAVA0901-E, KAVA0906-E, KAVA3650-I, KAVA6726-E, KAVB2027-E, KAVB3098-E, KAVB3107-E, KNAM3130-E, KNAM3170-E

User's Guide: --

Messages: 2.1, 2.2, 2.4, 2.7, 2.9, 2.10, 2.15

Function Reference: --

Visual C++(R) 2012 was added to the supported compilers.

User's Guide: --

Messages: --

Function Reference: 2.1.1(2)

Legend:

User's Guide: Job Management Partner 1/Base User's Guide

Messages: Job Management Partner 1/Base Messages

Function Reference: Job Management Partner 1/Base Function Reference

--: N/A

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

Preface

This manual explains the messages output with a message ID by Job Management Partner 1/Base. In this manual, Job Management Partner 1 is abbreviated to JP1. This manual is for all supported operating systems. Any differences between operating systems in regard to the operation of this program are mentioned at the appropriate place in the manual.

Intended readers

This manual is intended for:

System administrators who are responsible for introducing and operating JP1/Base.

System administrators and system operators who are responsible for introducing, configuring, and operating a system that incorporates JP1 products (such as JP1/IM, JP1/AJS, and JP1/Power Monitor) for which JP1/Base is a prerequisite.

Organization of this manual

This manual is organized as follows:

1. Overview of Messages

Chapter 1 provides an overview of JP1/Base messages, including the output destinations and the message format.

2. List of Messages

Chapter 2 explains the contents of JP1/Base messages.

JP1/Base manual organization

The JP1/Base documentation is divided into three manuals. Read the manual appropriate to your purpose, referring to the content of each manual shown in the following table.

Manual

Content

Job Management Partner 1/Base User's Guide

Overview and functionality of JP1/Base

Setup of each function

Commands, definition files, and JP1 events

Troubleshooting

Processes, port numbers, and operation logs

Job Management Partner 1/Base Messages

Messages

Job Management Partner 1/Base Function Reference

Procedures for issuing and acquiring JP1 events by using a JP1 program or user application

Functions

Conventions: "Administrator permissions" as used in this manual

In this manual, Administrator permissions refers to Administrator permissions for the local PC. The local user, domain user, or user of the Active Directory environment can perform tasks requiring Administrator permissions if granted Administrator permissions for the local PC.

Conventions: Directory names

HP-UX directory names are used in this manual as a general rule. The directory names have symbolic links, so that users of UNIX OSs other than HP-UX can use the same directory names.

When HP-UX uses a different directory name from another flavor of UNIX, both directory names are given.

Conventions: Fonts and symbols

Font and symbol conventions are classified as:

General font conventions

Conventions in syntax explanations

These conventions are described below.

General font conventions

The following table lists the general font conventions:

Font

Convention

Bold

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

From the File menu, choose Open.

Click the Cancel button.

In the Enter name entry box, type your name.

Italics

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

Write the command as follows:

copy source-file target-file

Do not delete the configuration file.

Code font

A code font indicates text that the user enters without change, or text (such as messages) output by the system. For example:

At the prompt, enter dir.

Use the send command to send mail.

The following message is displayed:

The password is incorrect.

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

MakeDatabase
...
StoreDatabase temp DB32

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

Conventions in syntax explanations

Syntax definitions appear as follows:

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

The following table lists the conventions used in syntax explanations:

Example font or symbol

Convention

|

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.

perm

Underlined characters indicate a default value.

This symbol is used to explicitly indicate a space.

₀: Enter one or more spaces, or none (a space is optional).

₁: Enter one or more spaces (a space is mandatory).

StoreDatabase

Code-font characters must be entered exactly as shown.

database-name

This font style marks a placeholder that indicates where appropriate characters are to be entered in an actual command.

SD

Bold code-font characters indicate an abbreviation for a command.

Conventions: Installation folder for JP1/Base

This manual uses the following to indicate the installation folder for JP1/Base:

Product

Indication of an installation folder

Installation folder#

JP1/Base

installation-folder

In an x86 environment:

system-drive:\Program Files\HITACHI\JP1Base

In an x64 environment:

system-drive:\Program Files (x86)\HITACHI\JP1Base

#: The installation folders in this column are the default installation folders.

For Windows Vista or later, the manual uses the expression system-drive:\ProgramData. The actual value is determined by the OS environment variable when the program is installed. The installation destination may differ depending on the 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.

Other reference information

For other reference information, see Reference Material for this Manual in the Job Management Partner 1/Base User's Guide.

1 Overview of Messages

This chapter provides an overview of JP1/Base messages, including the output destinations and the message format.

1.1 Types of messages

When you introduce, create, and operate a system using JP1/IM and JP1/AJS, which require JP1/Base as a prerequisite program, the system outputs the messages of JP1/IM and JP1/AJS as well as the messages of JP1/Base.

The following table lists the messages that are output by JP1/Base, JP1/IM and JP1/AJS, and the manuals that contain the information about the corresponding messages.

Table 1‒1: Message IDs and manuals containing the corresponding messages

Message ID

Manual containing the corresponding message

Messages beginning with KAJP

Job Management Partner 1/Base Messages

Messages beginning with KAVA

Messages beginning with KAIU

Messages beginning with KNAM

KAVB0001 to KAVB2000

Job Management Partner 1/Integrated Management - Manager Messages

KAVB2002 to KAVB3914

Job Management Partner 1/Integrated Management - Manager Messages and Job Management Partner 1/Base Messages

KAVB4001 to KAVB9999

Job Management Partner 1/Integrated Management - Manager Messages

Messages beginning with KAVS

Job Management Partner 1/Automatic Job Management System 2 Messages, Job Management Partner 1/Automatic Job Management System 3 Messages 1, and Job Management Partner 1/Automatic Job Management System 3 Messages 2

Messages beginning with KAVT

Messages beginning with KAVU

KAVV001 to KAVV899

1.2 List of output destinations for messages

1.2.1 Output destinations of event service messages (KAJP1001 to KAJP1871)

In the table, the output destinations are shown as follows:

Abbreviations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

JP1 event: JP1 event

fwderr: Event service forwarding error log

Y: Output

--: Not output

Table 1‒2: Output destinations of event service messages

Message ID

Output destination

syslog

Event

log#1

HNTRLib2

stdout

stderr

JP1 event

fwderr

KAJP1001 to KAJP1003

Y

Y

Y

--

Y

--

--

KAJP1004

Y

Y

Y

--

Y

--

--

KAJP1005

Y

Y

Y

--

Y

--

--

KAJP1006

--

--

--

--

--

Y

--

KAJP1010

Y

Y

Y

--

--

--

--

KAJP1011

Y

Y

Y

--

--

--

--

KAJP1012

--

Y

Y

--

--

--

--

KAJP1013

Y

Y

Y

--

Y

--

--

KAJP1015

--

Y

Y

--

--

--

--

KAJP1017 to KAJP1018

Y

Y

Y

--

--

--

--

KAJP1019 to KAJP1020

Y

--

--

--

Y

--

--

KAJP1021 to KAJP1025

Y

Y

Y

--

--

--

--

KAJP1027 to KAJP1028

Y

Y

Y

--

Y

--

--

KAJP1029

Y

--

Y

--

Y

--

--

KAJP1030 to KAJP1032

Y

Y

Y

--

--

--

--

KAJP1033

Y

Y

Y

--

Y

--

--

KAJP1034 to KAJP1036

Y

Y

Y

--

--

--

--

KAJP1037

Y#2

Y#2

Y#3

--

--

--

Y

KAJP1038

--

Y

Y

--

--

--

--

KAJP1039

--

Y

Y

--

Y

--

--

KAJP1040

--

Y

Y

--

--

--

--

KAJP1043 to KAJP1044

Y

Y

Y

--

--

--

--

KAJP1045 to KAJP1046

Y

--

Y

--

Y

--

--

KAJP1048

Y

--

Y

--

Y

--

--

KAJP1049

Y

Y

Y

--

--

--

--

KAJP1051

Y

--

Y

--

Y

--

--

KAJP1052

Y

--

Y

--

Y

--

--

KAJP1053

Y

Y

Y

--

--

--

--

KAJP1056 to KAJP1064

Y

Y

Y

--

--

--

--

KAJP1065 to KAJP1067

Y

--

Y

--

--

--

--

KAJP1068

Y

Y

Y

--

--

--

--

KAJP1070 to KAJP1071

Y

--

Y

--

--

--

--

KAJP1072

Y

--

Y

--

--

Y

--

KAJP1073

Y

--

Y

--

--

--

--

KAJP1074

Y

Y

Y

--

--

--

--

KAJP1075 to KAJP1076

Y

Y

Y

--

--

--

--

KAJP1081 to KAJP1082

Y

Y

Y

--

--

--

--

KAJP1083 to KAJP1087

Y

Y

Y

--

--

Y

--

KAJP1101 to KAJP1111

--

--

--

--

Y

--

--

KAJP1113 to KAJP1126

--

--

--

--

Y

--

--

KAJP1128

--

--

--

--

Y

--

--

KAJP1130 to KAJP1137

--

--

--

--

Y

--

--

KAJP1141 to KAJP1157

--

--

--

--

Y

--

--

KAJP1201 to KAJP1213

--

--

Y

--

--

--

--

KAJP1302 to KAJP1308

--

--

Y

Y

--

--

--

KAJP1350 to KAJP1352

--

--

--

Y

--

--

--

KAJP1401 to KAJP1408

--

--

--

Y

--

--

--

KAJP1410

--

--

--

Y

--

Y

--

KAJP1411

--

--

--

Y

--

--

--

KAJP1413 to KAJP1420

--

--

--

Y

--

--

--

KAJP1421

--

--

--

Y

--

Y

--

KAJP1422 to KAJP1423

--

--

--

Y

--

--

--

KAJP1424

--

--

--

Y

--

Y

--

KAJP1425 to KAJP1429

--

--

--

Y

--

--

--

KAJP1430

--

--

--

Y

--

Y

--

KAJP1431 to KAJP1435

--

--

--

Y

--

--

--

KAJP1701 to KAJP1712#4

--

--

Y

Y

Y

--

--

KAJP1731 to KAJP1735

--

--

--

--

Y

--

--

KAJP1736

--

--

--

Y

Y

--

--

KAJP1737 to KAJP1740

--

--

--

--

Y

--

--

KAJP1741 to KAJP1742

Y

Y

--

--

--

--

--

KAJP1743

Y

Y

Y

--

Y

--

--

KAJP1744

--

--

--

--

Y

--

--

KAJP1745

Y

Y

Y

--

Y

--

--

KAJP1751 to KAJP1765

--

--

--

Y

--

--

--

KAJP1771 to KAJP1774

--

--

--

Y

--

--

--

KAJP1775 to KAJP1777

--

--

Y

--

--

--

--

KAJP1780

--

--

--

--

Y

--

--

KAJP1781 to KAJP1784

--

--

Y

Y

--

--

--

KAJP1786 to KAJP1800

--

--

Y

Y

--

--

--

KAJP1801 to KAJP1803

Y

Y

Y

--

--

--

--

KAJP1804

Y

--

Y

--

--

--

--

KAJP1805

--

Y

Y

--

--

--

--

KAJP1806

Y

--

Y

--

--

--

--

KAJP1807

Y

Y

Y

--

--

--

--

KAJP1808

--

Y

Y

--

--

--

--

KAJP1810

Y

Y

Y

--

--

--

--

KAJP1811 to KAJP1819

--

Y

Y

--

--

--

--

KAJP1820

Y

--

Y

--

--

--

--

KAJP1826

Y

--

Y

--

--

--

--

KAJP1830 to KAJP1864

Y

--

Y

--

--

--

--

KAJP1869 to KAJP1871

Y

--

Y

--

--

--

--

#1 For messages from KAJP1001 through KAJP1076, message IDs are not output to the Windows event log.

#2 This message is not output if KAJP1037-syslogoff is specified for the options parameter in the event server settings file (conf).

#3 This message is not output if KAJP1037-hntroff is specified for the options parameter in the event server settings file (conf).

#4 Messages from KAJP1701 to KAJP1712 are output to the integrated trace log only when the jevdbinit, jevdbmkrep, or jevdbswitch command is executed.

1.2.2 Output destinations of user management functionality messages (KAVA0200 to KAVA1694)

In the table, the output destinations are shown as follows:

Abbreviations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

JP1 event: JP1 event

Y: Output

--: Not output

Table 1‒3: Output destinations of user management functionality messages

Message ID

Output destination

syslog

Event log

HNTRLib2

stdout

stderr

JP1 event

KAVA0200 to KAVA0408

--

--

--

--

Y

--

KAVA0410 to KAVA0440

--

--

Y

--

Y

--

KAVA0441

--

--

Y

--

--

--

KAVA0442

--

--

Y

--

Y

--

KAVA0443 to KAVA0454

--

--

Y

--

Y

--

KAVA0455 to KAVA0458

--

--

--

--

Y

--

KAVA0460 to KAVA0461

--

--

Y

--

Y

--

KAVA0462

--

--

--

--

Y

--

KAVA0463 to KAVA0466

--

--

Y

--

Y

--

KAVA0467 to KAVA0468

--

--

Y

--

--

--

KAVA0469

--

--

Y

--

Y

--

KAVA0470

--

--

--

--

Y

--

KAVA0569 to KAVA0594

--

--

--

--

Y

--

KAVA0601 to KAVA0666

--

--

--

Y

--

--

KAVA0667 to KAVA0683

--

--

--

--

Y

--

KAVA0684

--

--

--

Y

--

--

KAVA0686

--

--

--

Y

--

--

KAVA0687 to KAVA0699

--

--

--

--

Y

--

KAVA0701 to KAVA0761

--

--

--

Y

--

--

KAVA0762 to KAVA0769

--

--

--

--

Y

--

KAVA0784 to KAVA0794

--

--

--

Y

--

--

KAVA0801 to KAVA0839

--

--

--

Y

--

--

KAVA0850 to KAVA0854

--

--

--

--

Y

--

KAVA0856

--

--

--

Y

--

--

KAVA0863 to KAVA0866

--

--

--

--

Y

--

KAVA0867

--

--

--

Y

--

--

KAVA0869 to KAVA0895

--

--

--

--

Y

--

KAVA0896 to KAVA0907

--

--

--

Y

--

--

KAVA0927

--

--

--

Y

--

--

KAVA0930

--

--

--

--

Y

--

KAVA0931 to KAVA0932

--

--

--

Y

--

--

KAVA0936

--

--

--

--

Y

--

KAVA0938

--

--

--

Y

--

--

KAVA0939 to KAVA0947

--

--

--

--

Y

--

KAVA0948

--

--

--

Y

--

--

KAVA0951 to KAVA0979

--

--

--

Y

--

--

KAVA1395

--

--

Y

--

--

--

KAVA1396

--

--

Y

--

--

--

KAVA1400 to KAVA1508

--

--

Y

--

--

--

KAVA1509

--

--

--

--

Y

--

KAVA1510 to KAVA1515

--

--

Y

--

--

--

KAVA1516 to KAVA1519

--

--

--

--

Y

--

KAVA1520 to KAVA1528

--

--

Y

--

--

--

KAVA1529

--

--

--

--

Y

--

KAVA1530 to KAVA1531

--

--

Y

--

Y

--

KAVA1532

--

--

Y

--

--

--

KAVA1533 to KAVA1537

--

--

Y

--

Y

--

KAVA1538

--

--

--

--

Y

--

KAVA1539

--

--

Y

--

Y

--

KAVA1549

Y

Y

Y

--

--

--

KAVA1554

--

--

Y

--

--

--

KAVA1555 to KAVA1558

--

--

Y

--

Y

--

KAVA1559

--

--

Y

--

--

--

KAVA1565 to KAVA1566

--

--

Y

--

Y

--

KAVA1578 to KAVA1579

--

--

Y

--

Y

--

KAVA1584 to KAVA1585

--

--

Y

--

Y

--

KAVA1586

Y

Y

Y

--

Y

--

KAVA1587 to KAVA1588

--

--

Y

--

Y

--

KAVA1589 to KAVA1595

--

--

Y

--

--

--

KAVA1597 to KAVA1599

--

--

--

Y

--

--

KAVA1603 to KAVA1604

--

--

Y

--

Y

--

KAVA1615

--

--

Y

--

--

--

KAVA1617 to KAVA1619

--

--

Y

--

--

--

KAVA1623 to KAVA1624

--

--

Y

--

--

--

KAVA1625

--

--

Y

--

Y

--

KAVA1634 to KAVA1639

--

--

--

--

Y

--

KAVA1642

--

--

--

--

Y

--

KAVA1643 to KAVA1644

--

--

--

Y

--

--

KAVA1645 to KAVA1646

--

--

--

--

Y

--

KAVA1647 to KAVA1649

--

--

--

Y

--

--

KAVA1652 to KAVA1653

--

--

--

Y

--

--

KAVA1654 to KAVA1656

--

--

Y

--

Y

--

KAVA1657

--

--

--

Y

--

--

KAVA1658

Y

Y

Y

--

--

--

KAVA1661

--

--

Y

--

Y

--

KAVA1662

--

--

--

--

Y

--

KAVA1665

--

--

--

--

Y

--

KAVA1674

--

--

--

--

Y

--

KAVA1675 to KAVA1679

--

--

Y

--

--

--

KAVA1687 to KAVA1692

--

--

Y

--

--

--

KAVA1693

--

--

--

--

Y

--

KAVA1694

--

--

Y

--

--

--

1.2.3 Output destinations of setup messages (KAVA1700 to KAVA1946)

In the table, the output destinations are shown as follows:

Abbreviations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

Dialog: Message dialog box

Y: Output

--: Not output

Table 1‒4: Output destinations of setup messages

Message ID

Output destination

syslog

Event log

HNTRLib2

stdout

stderr

Dialog

KAVA1700 to KAVA1715

--

--

--

Y

--

--

KAVA1716 to KAVA1717

--

--

Y

--

Y

--

KAVA1718 to KAVA1723

--

--

--

--

Y

--

KAVA1724 to KAVA1726

--

--

Y

Y

--

--

KAVA1727 to KAVA1731

--

--

--

--

Y

--

KAVA1732

--

--

Y

--

--

--

KAVA1733 to KAVA1736

--

--

--

--

Y

--

KAVA1737

--

--

Y

Y

--

--

KAVA1738 to KAVA1743

--

--

Y

--

Y

--

KAVA1791 to KAVA1792

--

--

--

--

--

Y

KAVA1820

--

--

--

--

Y

--

KAVA1821

--

--

Y

Y

--

--

KAVA1822

--

--

Y

--

--

--

KAVA1823 to KAVA1824

--

--

--

Y

--

--

KAVA1825

--

--

--

--

Y

--

KAVA1826 to KAVA1827

--

--

--

Y

--

--

KAVA1828 to KAVA1829

--

--

Y

--

Y

--

KAVA1830

--

--

--

--

Y

--

KAVA1832 to KAVA1835

--

--

--

--

Y

--

KAVA1837

--

--

--

--

Y

--

KAVA1850 to KAVA1899

--

--

--

Y

--

Y

KAVA1902

--

--

--

Y

--

--

KAVA1940

--

--

--

Y

--

--

KAVA1943 to KAVA1944

--

--

--

Y

--

--

KAVA1946

--

--

--

Y

--

--

1.2.4 Output destinations of event service messages (KAVA2000 to KAVA3918)

In the table, the output destinations are shown as follows:

Abbreviations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

JP1 event: JP1 event

Result log: Log-file trap startup execution results log

Y: Output

--: Not output

Table 1‒5: Output destinations of event service messages

Message ID

Output destination

syslog

Event log

HNTRLib2

stdout

stderr

JP1 event

Result log

KAVA2000

--

--

Y

--

--

--

--

KAVA2001 to KAVA2004

--

--

--

--

Y

--

--

KAVA2006 to KAVA2018

--

--

--

--

Y

--

--

KAVA2101 to KAVA2111

--

--

Y

--

--

--

--

KAVA3000 to KAVA3006

--

Y

Y

--

--

--

--

KAVA3008

--

Y

Y

Y

--

--

--

KAVA3009

--

Y

Y

--

--

--

--

KAVA3010 to KAVA3011

--

--

--

--

Y

--

--

KAVA3013 to KAVA3014

--

--

--

--

Y

--

--

KAVA3015 to KAVA3020

--

Y

Y

--

--

--

--

KAVA3023 to KAVA3024

--

Y

Y

--

--

--

--

KAVA3025 to KAVA3026

--

Y

Y

--

Y

--

--

KAVA3027

--

Y

Y

--

--

--

--

KAVA3028

--

Y

Y

--

Y

--

--

KAVA3029

--

--

--

--

Y

--

--

KAVA3030 to KAVA3031

--

--

Y

--

--

Y#1

--

KAVA3032

--

--

Y

--

--

--

--

KAVA3033 to KAVA3034

--

Y

Y

--

--

--

--

KAVA3400 to KAVA3401

Y

--

Y

--

Y

--

--

KAVA3403 to KAVA3408

--

--

--

--

Y

--

--

KAVA3409 to KAVA3410

Y

--

Y

--

--

--

--

KAVA3411 to KAVA3412

--

--

--

--

--

--

Y

KAVA3413

Y

--

Y

--

--

--

--

KAVA3414 to KAVA3416

--

--

--

Y

--

--

--

KAVA3417 to KAVA3418

--

--

--

--

Y

--

--

KAVA3500 to KAVA3502

--

Y

Y

--

--

--

--

KAVA3503 to KAVA3507

--

--

--

--

Y

--

--

KAVA3508

--

--

--

--

Y

--

--

KAVA3509 to KAVA3510

--

Y

Y

--

--

--

--

KAVA3511 to KAVA3512

--

--

--

--

--

--

Y

KAVA3513

--

Y

Y

--

--

--

--

KAVA3600

Y

Y

Y

--

--

--

--

KAVA3601

Y

Y

Y

Y

--

--

--

KAVA3602

Y

Y

Y

--

Y

--

--

KAVA3604

--

Y

--

--

Y

--

--

KAVA3606

--

--

--

--

Y

--

--

KAVA3608

Y

Y

Y

--

Y

--

--

KAVA3609

--

Y

--

--

Y

--

--

KAVA3610

--

--

--

--

Y

--

--

KAVA3611

--

Y

--

--

Y

--

--

KAVA3613

Y

Y

Y

--

Y

--

--

KAVA3614

--

Y

--

--

Y

--

--

KAVA3615

Y

Y

Y

--

--

--

--

KAVA3616

Y

Y

Y

--

Y

--

--

KAVA3617

Y

Y

Y

--

--

--

--

KAVA3618

--

--

--

--

Y

--

--

KAVA3619

--

--

--

Y

--

--

--

KAVA3620

--

--

--

Y

--

--

--

KAVA3621

Y

Y

Y

--

Y

--

--

KAVA3622

--

--

Y

Y

--

--

--

KAVA3623

Y

Y

Y

--

Y

--

--

KAVA3624

Y

Y

Y

--

--

--

--

KAVA3625

Y

--

Y

--

Y

--

--

KAVA3628

--

--

--

Y

--

--

--

KAVA3629

Y

Y

Y

Y

--

--

--

KAVA3630 to KAVA3631

--

--

--

--

Y

--

--

KAVA3632 to KAVA3634

Y

Y

Y

--

Y

--

--

KAVA3635 to KAVA3639

Y

Y

Y

--

--

--

--

KAVA3640

Y

Y

Y

--

--

Y

--

KAVA3641 to KAVA3642

Y

Y

Y

--

--

--

--

KAVA3643 to KAVA3645

Y

Y

Y

--

--

Y

--

KAVA3646

Y

Y

Y

--

Y

--

--

KAVA3647

Y

Y

Y

--

Y

--

--

KAVA3648

--

--

--

--

Y

--

--

KAVA3650 to KAVA3651

Y

Y

Y

--

--

--

--

KAVA3652

Y

Y

Y

Y

--

--

--

KAVA3653

Y

Y

Y

--

Y

--

--

KAVA3654 to KAVA3655

--

--

--

--

--

--

Y

KAVA3656

Y

Y

Y

--

Y

--

--

KAVA3657

Y

Y

Y

Y

--

--

--

KAVA3658 to KAVA3659

Y

Y

Y

--

Y

--

--

KAVA3660

Y

Y

Y

--

--

--

--

KAVA3661 to KAVA3662

--

--

--

--

--

--

Y

KAVA3663

Y

Y

Y

--

--

--

--

KAVA3664

--

--

--

--

Y

--

--

KAVA3665 to KAVA3667

Y

Y

Y

--

Y

--

--

KAVA3668 to KAVA3669

Y

Y

Y

--

--

Y#2

--

KAVA3670 to KAVA3673

Y

Y

Y

--

--

Y

--

KAVA3674

--

Y

Y

--

Y

--

--

KAVA3903 to KAVA3908

--

--

Y

--

--

--

--

KAVA3909 to KAVA3910

--

--

Y

--

--

Y

--

KAVA3911 to KAVA3914

--

--

Y

--

--

--

--

KAVA3915

--

--

Y

--

--

Y

--

KAVA3916 to KAVA3918

--

--

Y

--

--

--

--

#1 This message is output if 1 is specified for the jp1event-send parameter in the event log trap action definition file (ntevent.conf), which is for Windows only.

#2 This message is output if 1 is specified for the upd-output-event parameter in the log file trap definition file.

1.2.5 Output destinations of startup control functionality messages (KAVA4001 to KAVA4614)

In the table, the output destinations are shown as follows:

Abbreviations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

Dialog: Dialog box

Y: Output

--: Not output

Table 1‒6: Output destinations of startup control functionality messages

Message ID

Output destination

syslog

Event log

HNTRLib2

Dialog

KAVA4001 to KAVA4049

--

--

Y

--

KAVA4101 to KAVA4111

--

Y

Y

--

KAVA4501 to KAVA4523

--

Y

--

--

KAVA4602 to KAVA4614

--

--

--

Y

1.2.6 Output destinations of user management messages for the authentication server (KAVA5001 to KAVA5902)

In the table, the output destinations are shown as follows:

Abbreviations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

Y: Output

--: Not output

Table 1‒7: Output destinations of user management messages for the authentication server

Message ID

Output destination

syslog

Event log

HNTRLib2

stdout

stderr

KAVA5001 to KAVA5003

--

--

Y

--

--

KAVA5004 to KAVA5008

--

--

Y

Y

--

KAVA5011

--

--

Y

Y

--

KAVA5014

--

--

Y

Y

--

KAVA5016 to KAVA5017

--

--

Y

Y

--

KAVA5018

--

--

--

Y

--

KAVA5019

--

--

Y

Y

--

KAVA5022 to KAVA5024

--

--

Y

Y

--

KAVA5026

--

--

Y

Y

--

KAVA5027

--

--

Y

--

--

KAVA5028

--

--

Y

Y

--

KAVA5031

--

--

--

Y

--

KAVA5032

--

--

Y

--

--

KAVA5033

--

--

Y

Y

--

KAVA5034

--

--

Y

--

--

KAVA5038

--

--

Y

Y

--

KAVA5041

--

--

Y

Y

--

KAVA5042 to KAVA5043

--

--

Y

--

--

KAVA5044 to KAVA5046

--

--

Y

Y

--

KAVA5047

--

--

--

--

--

KAVA5049

--

--

Y

--

--

KAVA5051

--

--

Y

--

--

KAVA5055 to KAVA5060

--

--

Y

Y

--

KAVA5062

--

--

Y

Y

--

KAVA5063 to KAVA5064

--

--

Y

--

--

KAVA5065

--

--

--

Y

--

KAVA5069 to KAVA5071

--

--

Y

Y

--

KAVA5072 to KAVA5073

--

--

Y

--

--

KAVA5074 to KAVA5075

--

--

Y

Y

--

KAVA5076 to KAVA5079

--

--

--

Y

--

KAVA5080 to KAVA5082

--

--

Y

--

--

KAVA5083

--

--

Y

Y

--

KAVA5084

--

--

Y

--

--

KAVA5085

--

--

Y

Y

--

KAVA5089

--

--

Y

Y

--

KAVA5092

--

--

Y

--

--

KAVA5094

--

--

Y

Y

--

KAVA5095 to KAVA5099

--

--

--

Y

--

KAVA5101 to KAVA5103

--

--

Y

--

--

KAVA5104 to KAVA5107

--

--

Y

Y

--

KAVA5109

--

--

Y

Y

--

KAVA5116 to KAVA5117

--

--

Y

Y

--

KAVA5118

--

--

--

Y

--

KAVA5119

--

--

Y

Y

--

KAVA5122 to KAVA5126

--

--

Y

Y

--

KAVA5127

--

--

Y

--

--

KAVA5128

--

--

Y

Y

--

KAVA5131

--

--

--

Y

--

KAVA5132

--

--

Y

--

--

KAVA5133

--

--

--

Y

--

KAVA5134

--

--

Y

--

--

KAVA5141

--

--

Y

Y

--

KAVA5142 to KAVA5143

--

--

Y

--

--

KAVA5144 to KAVA5146

--

--

Y

Y

--

KAVA5149

--

--

Y

--

--

KAVA5151

--

--

Y

--

--

KAVA5155 to KAVA5158

--

--

Y

Y

--

KAVA5162

--

--

Y

Y

--

KAVA5163 to KAVA5164

--

--

Y

--

--

KAVA5165

--

--

--

Y

--

KAVA5169 to KAVA5171

--

--

Y

Y

--

KAVA5172 to KAVA5173

--

--

Y

--

--

KAVA5174 to KAVA5175

--

--

Y

Y

--

KAVA5176 to KAVA5179

--

--

--

Y

--

KAVA5180 to KAVA5182

--

--

Y

--

--

KAVA5183

--

--

Y

Y

--

KAVA5185

--

--

Y

Y

--

KAVA5192

--

--

Y

--

--

KAVA5194

--

--

Y

Y

--

KAVA5195 to KAVA5196

--

--

--

Y

--

KAVA5201 to KAVA5203

--

--

Y

--

--

KAVA5204 to KAVA5207

--

--

Y

Y

--

KAVA5209 to KAVA5217

--

--

Y

Y

--

KAVA5218

--

--

--

Y

--

KAVA5219

--

--

Y

Y

--

KAVA5220

--

--

Y

--

--

KAVA5222 to KAVA5226

--

--

Y

Y

--

KAVA5227

--

--

Y

--

--

KAVA5228

--

--

Y

Y

--

KAVA5231

--

--

--

Y

--

KAVA5232

--

--

Y

--

--

KAVA5233

--

--

--

Y

--

KAVA5234

--

--

Y

--

--

KAVA5238

--

--

Y

Y

--

KAVA5241

--

--

Y

Y

--

KAVA5242 to KAVA5243

--

--

Y

--

--

KAVA5244 to KAVA5246

--

--

Y

Y

--

KAVA5249

--

--

Y

--

--

KAVA5251

--

--

Y

--

--

KAVA5255 to KAVA5260

--

--

Y

Y

--

KAVA5262

--

--

Y

Y

--

KAVA5263 to KAVA5264

--

--

Y

--

--

KAVA5265

--

--

--

Y

--

KAVA5269 to KAVA5271

--

--

Y

Y

--

KAVA5272 to KAVA5273

--

--

Y

--

--

KAVA5274 to KAVA5275

--

--

Y

Y

--

KAVA5276 to KAVA5279

--

--

--

Y

--

KAVA5280 to KAVA5282

--

--

Y

--

--

KAVA5283

--

--

Y

Y

--

KAVA5284

--

--

Y

--

--

KAVA5285

--

--

Y

Y

--

KAVA5289

--

--

Y

Y

--

KAVA5292

--

--

Y

--

--

KAVA5294

--

--

Y

Y

--

KAVA5295 to KAVA5299

--

--

--

Y

--

KAVA5301 to KAVA5303

--

--

Y

--

--

KAVA5304

--

--

Y

Y

--

KAVA5317

--

--

Y

Y

--

KAVA5318

--

--

--

Y

--

KAVA5319

--

--

Y

Y

--

KAVA5322

--

--

Y

Y

--

KAVA5324

--

--

Y

Y

--

KAVA5326

--

--

Y

Y

--

KAVA5327

--

--

Y

--

--

KAVA5328

--

--

Y

Y

--

KAVA5331

--

--

--

Y

--

KAVA5332

--

--

Y

--

--

KAVA5333

--

--

--

Y

--

KAVA5334

--

--

Y

--

--

KAVA5341

--

--

Y

Y

--

KAVA5342 to KAVA5343

--

--

Y

--

--

KAVA5344 to KAVA5346

--

--

Y

Y

--

KAVA5351

--

--

Y

--

--

KAVA5355 to KAVA5358

--

--

Y

Y

--

KAVA5362

--

--

Y

Y

--

KAVA5363 to KAVA5364

--

--

Y

--

--

KAVA5365

--

--

--

Y

--

KAVA5369 to KAVA5371

--

--

Y

Y

--

KAVA5372 to KAVA5373

--

--

Y

--

--

KAVA5374 to KAVA5375

--

--

Y

Y

--

KAVA5376 to KAVA5379

--

--

--

Y

--

KAVA5380 to KAVA5382

--

--

Y

--

--

KAVA5383

--

--

Y

Y

--

KAVA5385

--

--

Y

Y

--

KAVA5392

--

--

Y

--

--

KAVA5394

--

--

Y

Y

--

KAVA5395 to KAVA5396

--

--

--

Y

--

KAVA5401 to KAVA5403

--

--

Y

--

--

KAVA5404

--

--

Y

Y

--

KAVA5417

--

--

Y

Y

--

KAVA5418

--

--

--

Y

--

KAVA5419

--

--

Y

Y

--

KAVA5422 to KAVA5426

--

--

Y

Y

--

KAVA5427

--

--

Y

--

--

KAVA5428

--

--

Y

Y

--

KAVA5431

--

--

--

Y

--

KAVA5432

--

--

Y

--

--

KAVA5433

--

--

--

Y

--

KAVA5434

--

--

Y

--

--

KAVA5441

--

--

Y

Y

--

KAVA5442 to KAVA5443

--

--

Y

--

--

KAVA5444 to KAVA5446

--

--

Y

Y

--

KAVA5449

--

--

Y

--

--

KAVA5451

--

--

Y

--

--

KAVA5455 to KAVA5458

--

--

Y

Y

--

KAVA5462

--

--

Y

Y

--

KAVA5463 to KAVA5464

--

--

Y

--

--

KAVA5465

--

--

--

Y

--

KAVA5469 to KAVA5471

--

--

Y

Y

--

KAVA5472 to KAVA5473

--

--

Y

--

--

KAVA5474 to KAVA5475

--

--

Y

Y

--

KAVA5476 to KAVA5479

--

--

--

Y

--

KAVA5480 to KAVA5482

--

--

Y

--

--

KAVA5483

--

--

Y

Y

--

KAVA5485

--

--

Y

Y

--

KAVA5492

--

--

Y

--

--

KAVA5494

--

--

Y

Y

--

KAVA5495 to KAVA5496

--

--

--

Y

--

KAVA5501 to KAVA5503

--

--

Y

--

--

KAVA5505

--

--

Y

Y

--

KAVA5517

--

--

Y

Y

--

KAVA5518

--

--

--

Y

--

KAVA5519

--

--

Y

Y

--

KAVA5521

--

--

--

--

--

KAVA5524

--

--

Y

Y

--

KAVA5528 to KAVA5541

--

--

Y

Y

--

KAVA5562

--

--

Y

Y

--

KAVA5565

--

--

--

Y

--

KAVA5566

--

--

Y

--

--

KAVA5567

--

--

--

Y

--

KAVA5570

--

--

Y

Y

--

KAVA5572 to KAVA5573

--

--

Y

--

--

KAVA5574 to KAVA5575

--

--

Y

Y

--

KAVA5576 to KAVA5579

--

--

--

Y

--

KAVA5580

--

--

Y

--

--

KAVA5590

--

--

Y

Y

--

KAVA5592

--

--

Y

--

--

KAVA5594

--

--

Y

Y

--

KAVA5595 to KAVA5596

--

--

--

Y

--

KAVA5597 to KAVA5598

--

--

Y

Y

--

KAVA5700

--

--

--

--

Y

KAVA5702 to KAVA5703

--

--

Y

--

--

KAVA5705

--

--

Y

Y

--

KAVA5706 to KAVA5707

--

--

Y

--

--

KAVA5708 to KAVA5710

--

--

Y

Y

--

KAVA5718

--

--

--

Y

--

KAVA5724

--

--

Y

Y

--

KAVA5762

--

--

Y

Y

--

KAVA5765

--

--

--

Y

--

KAVA5770

--

--

Y

Y

--

KAVA5778

--

--

--

Y

--

KAVA5802 to KAVA5803

--

--

Y

--

--

KAVA5805 to KAVA5807

--

--

Y

Y

--

KAVA5808 to KAVA5809

--

--

Y

--

--

KAVA5810 to KAVA5811

--

--

Y

Y

--

KAVA5812

--

--

Y

--

--

KAVA5813 to KAVA5816

--

--

Y

Y

--

KAVA5818

--

--

--

Y

--

KAVA5822 to KAVA5823

--

--

--

Y

--

KAVA5824 to KAVA5862

--

--

Y

Y

--

KAVA5865

--

--

--

Y

--

KAVA5870

--

--

Y

Y

--

KAVA5878

--

--

--

Y

--

KAVA5889 to KAVA5901

--

--

Y

Y

--

KAVA5902

--

--

--

--

Y

1.2.7 Output destinations of plug-in service messages (KAVA6002 to KAVA6855)

In the table, the output destinations are shown as follows:

Abbreviations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

Dialog: Message dialog box

Y: Output

--: Is not output

Table 1‒8: Output destinations of plug-in service messages

Message ID

Output destination

syslog

Event log

HNTRLib2

stdout

stderr

Dialog

KAVA6002 to

KAVA6603

--

--

Y

--

--

--

KAVA6005

--

--

Y

--

--

--

KAVA6007 to

KAVA6008

--

--

Y

--

--

--

KAVA6017

--

--

Y

--

--

--

KAVA6030

--

--

Y

--

--

--

KAVA6037 to

KAVA6050

--

--

Y

--

--

--

KAVA6101

--

--

Y

--

--

--

KAVA6117 to

KAVA6119

--

--

Y

--

--

--

KAVA6129

--

--

Y

--

--

--

KAVA6641 to

KAVA6643

--

--

Y

--

--

--

KAVA6651

--

--

Y

--

--

--

KAVA6653

--

--

Y

--

--

--

KAVA6671

--

--

Y

--

--

--

KAVA6676 to

KAVA6680

--

--

Y

--

--

--

KAVA6682

--

--

Y

--

--

--

KAVA6684

--

--

Y

--

--

--

KAVA6693

--

--

Y

--

--

--

KAVA6701

--

--

Y

--

--

--

KAVA6703

--

--

Y

--

--

--

KAVA6705

--

--

Y

--

--

--

KAVA6706

--

--

Y

--

--

--

KAVA6707

--

--

Y

--

--

--

KAVA6709

--

--

Y

--

--

--

KAVA6711

--

--

Y

--

--

--

KAVA6713

--

--

Y

--

--

--

KAVA6715

--

--

Y

--

--

--

KAVA6717

Y

Y

--

--

Y

--

KAVA6719

--

--

Y

--

--

--

KAVA6721

--

--

Y

--

--

--

KAVA6722

--

--

Y

--

--

--

KAVA6723

--

--

Y

--

--

--

KAVA6724

--

--

Y

--

--

--

KAVA6725

--

--

Y

--

--

--

KAVA6726

--

--

Y

--

--

--

KAVA6727

--

--

Y

--

--

--

KAVA6728

--

--

Y

--

--

--

KAVA6730

--

--

Y

--

--

--

KAVA6731

--

--

Y

--

--

--

KAVA6732

--

--

Y

--

--

--

KAVA6733

--

--

Y

--

Y

--

KAVA6735

--

--

Y

--

Y

--

KAVA6737

--

--

Y

--

--

--

KAVA6739

--

--

Y

--

--

--

KAVA6741

--

--

Y

--

--

--

KAVA6743

--

--

Y

--

--

--

KAVA6745

--

--

Y

--

--

--

KAVA6747

--

--

Y

--

--

--

KAVA6748

--

--

--

--

Y

--

KAVA6801

--

--

--

Y

--

--

KAVA6803

--

--

--

--

Y

--

KAVA6805

--

--

--

--

Y

--

KAVA6807

--

--

--

--

Y

--

KAVA6809

--

--

--

--

Y

--

KAVA6811

--

--

--

--

Y

--

KAVA6813

--

--

--

Y

--

--

KAVA6815

--

--

--

--

Y

--

KAVA6817

--

--

--

--

Y

--

KAVA6851

--

--

--

--

Y

--

KAVA6853

--

--

--

--

Y

--

KAVA6855

--

--

--

--

Y

--

1.2.8 Output destinations of health check messages (KAVA7001 to KAVA7560)

In the table, the output destinations are shown as follows:

Abbreviations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

JP1 event: JP1 event

Y: Output

--: Is not output

Table 1‒9: Output destinations of health check messages

Message ID

Output destination

syslog

Event log

HNTRLib2

stdout

stderr

JP1 event

KAVA7001 to KAVA7002

--

--

Y

--

--

--

KAVA7003

Y

Y

Y

--

--

Y

KAVA7013 to KAVA7017

Y

Y

Y

--

--

Y

KAVA7020 to KAVA7023

--

--

Y

--

--

--

KAVA7026 to KAVA7028

Y

Y

--

--

--

--

KAVA7030

Y

Y

Y

--

--

Y

KAVA7031

--

--

Y

--

--

--

KAVA7032 to KAVA7034

Y

Y

Y

--

--

Y

KAVA7050 to KAVA7052

Y

Y

Y

--

--

--

KAVA7053 to KAVA7209

--

--

Y

--

--

--

KAVA7210

Y

Y

Y

--

--

Y

KAVA7211 to KAVA7221

--

--

Y

--

--

--

KAVA7222 to KAVA7224

Y

Y

Y

--

--

Y

KAVA7225

--

--

Y

--

--

--

KAVA7226

Y

Y

--

--

--

--

KAVA7227

--

--

Y

--

--

--

KAVA7228 to KAVA7229

Y

Y

Y

--

--

Y

KAVA7230 to KAVA7231

--

--

Y

--

--

--

KAVA7560

--

--

--

--

Y

--

1.2.9 Output destinations of command execution messages (KAVB2002 to KAVB2638)

In the table, the output destinations are shown as follows:

Abbreviations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

Window: Execute Command window or Action Log Details window in JP1/IM - View

Command: Command execution log directory (You can use the jcocmdlog command to check the output messages. For details on the command, see the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.)

JP1 event: JP1 event

Y: Output

--: Not output

Table 1‒10: Output destinations of command execution messages for JP1/IM

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

--

--

--

--

--

Y

--

--

KAVB2013

--

--

--

--

--

Y

Y

--

KAVB2022 to KAVB2024

--

--

Y

--

--

Y

Y

--

KAVB2027

--

--

--

--

--

Y

Y

--

KAVB2029 to 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

--

Y

--

--

--

KAVB2213

--

--

Y

--

--

--

--

--

KAVB2214 to 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

--

--

--

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

--

--

--

--

Y

--

--

--

KAVB2566

--

--

--

--

Y

--

--

--

KAVB2567

--

--

--

--

Y

--

--

--

KAVB2600

--

--

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 KAVB2638

--

--

Y

--

--

--

--

--

1.2.10 Output destinations of configuration management messages (KAVB3001 to KAVB3172)

In the table, the output destinations are shown as follows:

Abbreviations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

Y: Output

--: Not output

Table 1‒11: Output destinations of configuration management messages for JP1/IM

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

--

--

Y

--

--

KAVB3159

--

--

--

Y

--

KAVB3160 to KAVB3161

--

--

Y

--

--

KAVB3162

--

--

Y

Y

--

KAVB3163

--

--

--

--

Y

KAVB3164 to KAVB3172

--

--

Y

--

--

1.2.11 Output destinations of process management messages (KAVB3501 to KAVB3914)

In the table, the output destinations are shown as follows:

Abbreviations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

JP1 event: JP1 event

Y: Output

--: Not output

Note

In addition to the messages in the following list, the system may output messages with message IDs, such as internal error messages.

When using JP1/AJS2, see the manuals Job Management Partner 1/Automatic Job Management System 2 Messages, Job Management Partner 1/Automatic Job Management System 3 Messages 1, and Job Management Partner 1/Automatic Job Management System 3 Messages 2 for details on process management messages.

Table 1‒12: Output destinations of process management messages

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 KAVB3612

--

--

Y

--

--

--

KAVB3613

Y

Y

Y

--

--

Y

KAVB3614

Y

Y

Y

--

--

--

KAVB3616

--

--

--

--

--

Y

KAVB3617

--

--

Y

--

--

--

KAVB3619

--

--

Y

--

--

--

KAVB3620

Y

Y

Y

Y

--

--

KAVB3621

Y

--

Y

--

--

--

KAVB3623

Y

--

Y

--

--

--

KAVB3624

Y

Y

Y

--

--

--

KAVB3625 to KAVB3626

Y

Y

Y

Y

--

--

KAVB3627

--

--

Y

--

--

--

KAVB3631

--

--

Y

--

--

--

KAVB3642 to KAVB3644

Y

Y

Y

--

--

--

KAVB3645 to KAVB3647

--

--

Y

--

--

--

KAVB3649

Y

Y

Y

Y

--

--

KAVB3651 to KAVB3662

--

--

Y

Y

--

--

KAVB3663

--

--

--

--

Y

--

KAVB3664 to KAVB3665

Y

Y

Y

--

--

Y

KAVB3666

Y

Y

Y

--

--

--

KAVB3672 to KAVB3684

--

--

Y

Y

--

--

KAVB3685

--

--

--

Y

--

--

KAVB3686 to KAVB3687

--

--

Y

--

--

--

KAVB3688 to KAVB3694

--

--

--

Y

--

--

KAVB3705 to KAVB3736

--

--

Y

--

--

--

KAVB3737

Y

Y

Y

--

--

Y

KAVB3743 to KAVB3751

--

--

Y

--

--

--

KAVB3752

Y

Y

Y

--

--

--

KAVB3760 to KAVB3769

--

--

Y

--

--

--

KAVB3777 to KAVB3786

--

--

Y

--

--

--

KAVB3788

Y

Y

Y

--

--

--

KAVB3792

--

Y

--

--

--

--

KAVB3802

--

--

Y

--

--

--

KAVB3840 to KAVB3841

--

--

Y

--

--

--

KAVB3846 to 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

Y

--

Y

--

--

KAVB3905 to KAVB3910

--

--

Y

--

--

--

KAVB3911 to KAVB3914

--

--

Y

Y

--

--

1.2.12 Output destinations of ISAM file messages (KAIU001 to KAIU999)

In the table, output destinations are shown as follows:

Abbreviations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

Y: Output

--: Not output

Table 1‒13: Output destinations of ISAM file messages

Message ID

Output destination

syslog

Event log

HNTRLib2

stdout

stderr

KAIU001-E to KAIU999-E

--

--

--

--

Y

1.2.13 Output destinations of interprocess communication messages (KNAM1001 to KNAM1514)

In the table, output destinations are shown as follows:

Abbreviations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

JP1 event: JP1 event

Y: Output

--: Not output

Table 1‒14: Output destinations of interprocess communication messages

Message ID

Output destination

syslog

Event log

HNTRLib2

stdout

stderr

JP1 event

KNAM1001 to KNAM1010

--

--

Y

--

--

--

KNAM1012

--

--

Y

--

--

--

KNAM1014 to KNAM1016

--

--

Y

--

--

--

KNAM1020

--

--

Y

--

--

--

KNAM1023 to KNAM1029

--

--

Y

--

--

--

KNAM1038

--

--

Y

--

--

--

KNAM1040

--

--

Y

--

--

--

KNAM1049 to KNAM1051

--

--

Y

--

--

--

KNAM1054 to KNAM1055

--

--

Y

--

--

--

KNAM1060 to KNAM1064

--

--

Y

--

--

--

KNAM1067 to KNAM1071

--

--

Y

--

--

--

KNAM1084

--

--

Y

--

--

--

KNAM1088

--

--

Y

--

--

--

KNAM1093

--

--

Y

--

--

--

KNAM1500 to KNAM1501

--

--

Y

--

Y

--

KNAM1505

--

--

Y

--

Y

--

KNAM1509

--

--

--

--

Y

--

KNAM1511

--

--

Y

--

Y

--

KNAM1513

--

--

Y

--

Y

--

KNAM1514

--

--

--

--

Y

--

1.2.14 Output destinations of operating-information acquisition messages (KNAM2000 to KNAM2012)

In the table, output destinations are shown as follows:

Abbreviations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

JP1 event: JP1 event

Y: Output

--: Not output

Table 1‒15: Output destinations of operating-information acquisition messages for JP1/IM

Message ID

Output destination

syslog

Event log

HNTRLib2

stdout

stderr

JP1 event

KNAM2000 to

KNAM2002

--

--

--

--

Y

--

KNAM2003 to

KNAM2010

--

--

Y

--

Y

--

KNAM2011

--

--

--

--

Y

--

KNAM2012

--

--

Y

--

Y

--

1.2.15 Output destinations of local action messages (KNAM3000 to KNAM3369)

In the table, output destinations are shown as follows:

Abbreviations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

JP1 event: JP1 event

Execution log: Local action execution log

Y: Output

--: Not output

Table 1‒16: Output destinations of local action messages

Message ID

Output destination

syslog

Event

log

HNTRLib2

stdout

stderr

JP1 event

Execution log

KNAM3000

--

--

Y

--

--

--

--

KNAM3010

--

--

Y

--

--

--

--

KNAM3016 to KNAM3017

--

--

Y

--

--

--

--

KNAM3020

--

--

Y

--

--

--

--

KNAM3021

Y

Y

Y

--

--

--

--

KNAM3024 to KNAM3025

--

--

Y

--

--

--

--

KNAM3030

--

--

Y

--

--

--

--

KNAM3031

Y

Y

Y

--

--

--

--

KNAM3040

--

--

Y

--

--

--

--

KNAM3099 to KNAM3100

--

--

Y

--

--

--

--

KNAM3101 to KNAM3106

Y

Y

Y

--

--

--

--

KNAM3120

Y

Y

Y

--

--

--

--

KNAM3122

Y

Y

Y

--

--

--

--

KNAM3130 to KNAM3134

Y

Y

Y

--

--

--

--

KNAM3135

--

--

Y

--

--

--

--

KNAM3137

Y

Y

Y

--

--

--

--

KNAM3140

Y

Y

Y

--

--

--

--

KNAM3142

Y

Y

Y

--

--

--

--

KNAM3150

Y

Y

Y

--

--

--

--

KNAM3160

--

--

Y

--

--

--

--

KNAM3170

--

--

Y

--

--

--

--

KNAM3201

--

--

--

--

--

--

Y

KNAM3202

--

--

--

--

--

--

Y

KNAM3203

--

--

--

--

--

Y

Y

KNAM3204

--

--

--

--

--

--

Y

KNAM3205 to KNAM3209

--

--

--

--

--

--

Y

KNAM3210

--

--

--

--

--

Y

Y

KNAM3211 to KNAM3212

--

--

--

--

--

Y

Y

KNAM3310 to KNAM3311

--

--

Y

Y

--

--

--

KNAM3312 to KNAM3313

--

--

Y

--

Y

--

--

KNAM3314

--

--

Y

Y

--

--

--

KNAM3315 to KNAM3320

--

--

--

--

Y

--

--

KNAM3321 to KNAM3323

--

--

Y

--

Y

--

--

KNAM3329

--

--

Y

--

Y

--

--

KNAM3350 to KNAM3351

--

--

Y

Y

--

--

--

KNAM3352 to KNAM3354

--

--

Y

--

Y

--

--

KNAM3355 to KNAM3360

--

--

--

--

Y

--

--

KNAM3361 to KNAM3364

--

--

Y

--

Y

--

--

KNAM3369

--

--

Y

--

Y

--

--

1.2.16 Output destinations of service management control messages (KNAM4000 to KNAM4412)

In the table, output destinations are shown as follows:

Abbreviations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

JP1 event: JP1 event

Y: Output

--: Not output

Table 1‒17: Output destinations of service management control messages

Message ID

Output destination

syslog

Event

log

HNTRLib2

stdout

stderr

JP1 event

KNAM4000 to KNAM4003

--

--

Y

--

--

--

KNAM4006 to KNAM4008

--

--

Y

--

--

--

KNAM4011 to KNAM4012

--

--

Y

--

--

--

KNAM4200 to KNAM4202

--

--

Y

--

--

--

KNAM4204

--

--

Y

--

--

--

KNAM4206

--

--

Y

--

--

--

KNAM4208

--

--

Y

--

--

--

KNAM4210

--

--

Y

--

--

--

KNAM4212

--

--

Y

--

--

--

KNAM4214

--

--

Y

--

--

--

KNAM4216

--

--

Y

--

--

--

KNAM4218

--

--

Y

--

--

--

KNAM4220

--

--

Y

--

--

--

KNAM4222

--

--

Y

--

--

--

KNAM4224

--

--

Y

--

--

--

KNAM4226

--

--

Y

--

--

--

KNAM4228

--

--

Y

--

--

--

KNAM4230

--

--

Y

--

--

--

KNAM4232

--

--

Y

--

--

--

KNAM4234

--

--

Y

--

--

--

KNAM4236

--

--

Y

--

--

--

KNAM4238

--

--

Y

--

--

--

KNAM4240

--

--

Y

--

--

--

KNAM4402

--

--

Y

--

--

--

KNAM4404

--

--

Y

--

--

--

KNAM4406

--

--

Y

--

--

--

KNAM4408

--

--

Y

--

--

--

KNAM4410

--

--

Y

--

--

--

KNAM4412

--

--

Y

--

--

--

1.2.17 Output destinations of setup information collection messages (KNAM9001 to KNAM9028)

In the table, output destinations are shown as follows:

Abbreviations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

Individual log: Individual log for the setup information collection command

Y: Output

--: Not output

Table 1‒18: Output destinations of setup information collection messages

Message ID

Output destination

syslog

Event log

HNTRLib2

stdout

stderr

Individual log

KNAM9001 and

KNAM9002

--

--

--

Y

--

Y

KNAM9003 and

KNAM9004

--

--

--

--

Y

Y

KNAM9005 and

KNAM9006

--

--

--

--

Y

--

KNAM9007 to

KNAM9010

--

--

--

--

Y

Y

KNAM9011 and

KNAM9012

--

--

--

Y

--

Y

KNAM9013 to

KNAM9016

--

--

--

--

Y

Y

KNAM9020

--

--

--

Y

--

Y

KNAM9021

--

--

--

--

Y

Y

KNAM9022

--

--

--

Y

--

Y

KNAM9023

--

--

--

--

Y

Y

KNAM9024

--

--

--

Y

--

Y

KNAM9025

--

--

--

--

Y

Y

KNAM9026

--

--

--

Y

--

Y

KNAM9027

--

--

--

--

Y

Y

KNAM9028

--

--

--

Y

--

Y

1.3 Message format

This section explains JP1/Base messages and ISAM utility messages that have message IDs. For other messages, see the chapter about troubleshooting in the Job Management Partner 1/Base User's Guide.

Note

In addition to the messages that have been newly added, some messages used in a previous version of JP1/Base have been changed. If you are using log file trapping to convert the JP1/Base messages into JP1 events, check the converted messages for any changes.

1.3.1 Format of output messages

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

Messages are output in any of the following formats:

KAJPnnnn-Z message text

KAVAnnnn-Z message text

KAVBnnnn-Z message text

KAIUnnn-Z message text

KNAMnnnn-Z message text

(1) Message ID

The message ID consists of the following components:

K

System identifier

AJP, AVA, AVB, or NAM

Indicates the message output by JP1/Base.

AIU

Indicates a message output by ISAM.

nnnn

Message serial number

Z

Message type, as one of the following:

E: Error message. Processing is canceled.

W: Warning message. Processing continues after message output.

I: Information message. Notifies the user of information.

Q: Question message. Prompts the user to choose an execution option.

1.3.2 Format of message explanations

Messages are explained in the following format in this manual:

Message ID

Message text

Explanation of the output message text.

(S)

System action

(O)

Operator action at message output

1.3.3 Note to the system administrator

If any problem occurs during operation, see the chapter about troubleshooting in the Job Management Partner 1/Base User's Guide, collect log information, and perform the initial investigation.

To perform the initial investigation for identifying the cause of the problem, see the OS log information (Windows event log in Windows, and syslog in UNIX) and the log information output by JP1/Base. Use these two sets of log information to check the time when the problem occurred and avoid the same problem or take an appropriate action.

In addition, record the operations performed up to the problem. If possible, check whether the problem can be repeated.

1.4 Contents of syslog and the Windows event log

This section provides lists of syslog and Windows event log entries output by JP1/Base.

1.4.1 List of syslog and the Windows event log entries (related to the event service)

Abbreviation:

--: Not output

Table 1‒19: List of syslog and the Windows event log entries (related to the event service)

Message ID

UNIX

(syslog)

Windows

(application log)

Facility

Level

Event ID

Type

Source

KAJP1001-I

LOG_DAEMON

LOG_INFO

1001

Information

JP1/Base Event

KAJP1002-I

LOG_DAEMON

LOG_INFO

1002

Information

JP1/Base Event

KAJP1003-I

LOG_DAEMON

LOG_INFO

1003

Information

JP1/Base Event

KAJP1004-E

--

--

1004

Error

JP1/Base Event

KAJP1005-E

LOG_DAEMON

LOG_ERR

1005

Error

JP1/Base Event

KAJP1010-E

LOG_DAEMON

LOG_ERR

1010

Error

JP1/Base Event

KAJP1011-E

--

--

1011

Error

JP1/Base Event

KAJP1012-E

--

--

1012

Error

JP1/Base Event

KAJP1013-E

LOG_DAEMON

LOG_ERR

1013

Error

JP1/Base Event

KAJP1015-E

--

--

1015

Error

JP1/Base Event

KAJP1017-E

LOG_DAEMON

LOG_ERR

1017

Error

JP1/Base Event

KAJP1018-I

LOG_DAEMON

LOG_INFO

1018

Information

JP1/Base Event

KAJP1019-W

LOG_DAEMON

LOG_WARNING

--

--

--

KAJP1020-W

LOG_DAEMON

LOG_WARNING

--

--

--

KAJP1021-E

LOG_DAEMON

LOG_ERR

1021

Error

JP1/Base Event

KAJP1022-E

LOG_DAEMON

LOG_ERR

1022

Error

JP1/Base Event

KAJP1023-E

LOG_DAEMON

LOG_ERR

1023

Error

JP1/Base Event

KAJP1024-E

LOG_DAEMON

LOG_ERR

1024

Error

JP1/Base Event

KAJP1025-E

LOG_DAEMON

LOG_ERR

1025

Error

JP1/Base Event

KAJP1027-E

LOG_DAEMON

LOG_ERR

1027

Error

JP1/Base Event

KAJP1028-E

LOG_DAEMON

LOG_ERR

1028

Error

JP1/Base Event

KAJP1029-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1030-W

LOG_DAEMON

LOG_WARNING

1030

Warning

JP1/Base Event

KAJP1031-W

LOG_DAEMON

LOG_WARNING

1031

Warning

JP1/Base Event

KAJP1032-E

LOG_DAEMON

LOG_ERR

1032

Error

JP1/Base Event

KAJP1033-E

LOG_DAEMON

LOG_ERR

1033

Error

JP1/Base Event

KAJP1034-E

LOG_DAEMON

LOG_ERR

1034

Error

JP1/Base Event

KAJP1035-E

LOG_DAEMON

LOG_ERR

1035

Error

JP1/Base Event

KAJP1036-E

LOG_DAEMON

LOG_ERR

1036

Error

JP1/Base Event

KAJP1037-E

LOG_DAEMON

LOG_ERR

1037

Error

JP1/Base Event

KAJP1038-E

--

--

1038

Error

JP1/Base Event

KAJP1039-E

--

--

1039

Error

JP1/Base Event

KAJP1040-E

--

--

1040

Error

JP1/Base Event

KAJP1043-E

LOG_DAEMON

LOG_ERR

1043

Error

JP1/Base Event

KAJP1044-E

LOG_DAEMON

LOG_ERR

1044

Error

JP1/Base Event

KAJP1045-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1046-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1048-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1049-E

LOG_DAEMON

LOG_ERR

1049

Error

JP1/Base Event

KAJP1051-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1052-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1053-E

LOG_DAEMON

LOG_ERR

1053

Error

JP1/Base Event

KAJP1056-E

LOG_DAEMON

LOG_ERR

1056

Error

JP1/Base Event

KAJP1057-W

LOG_DAEMON

LOG_WARNING

1057

Warning

JP1/Base Event

KAJP1058-W

LOG_DAEMON

LOG_WARNING

1058

Warning

JP1/Base Event

KAJP1059-E

LOG_DAEMON

LOG_ERR

1059

Error

JP1/Base Event

KAJP1060-E

LOG_DAEMON

LOG_ERR

1060

Error

JP1/Base Event

KAJP1061-I

LOG_DAEMON

LOG_INFO

1061

Information

JP1/Base Event

KAJP1062-E

LOG_DAEMON

LOG_ERR

1062

Error

JP1/Base Event

KAJP1063-E

LOG_DAEMON

LOG_ERR

1063

Error

JP1/Base Event

KAJP1064-W

LOG_DAEMON

LOG_WARNING

1064

Warning

JP1/Base Event

KAJP1065-I

LOG_DAEMON

LOG_INFO

--

--

--

KAJP1066-W

LOG_DAEMON

LOG_WARNING

--

--

--

KAJP1067-W

LOG_DAEMON

LOG_WARNING

--

--

--

KAJP1068-I

LOG_DAEMON

LOG_INFO

1068

Information

JP1/Base Event

KAJP1070-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1071-I

LOG_DAEMON

LOG_INFO

--

--

--

KAJP1072-I

LOG_DAEMON

LOG_INFO

--

--

--

KAJP1073-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1074-I

LOG_DAEMON

LOG_INFO

1074

Information

JP1/Base Event

KAJP1075-W

LOG_DAEMON

LOG_WARNING

1075

Warning

JP1/Base Event

KAJP1076-E

LOG_DAEMON

LOG_ERR

1076

Error

JP1/Base Event

KAJP1081-W

LOG_DAEMON

LOG_WARNING

1081

Warning

JP1/Base Event

KAJP1082-W

LOG_DAEMON

LOG_WARNING

1082

Warning

JP1/Base Event

KAJP1083-W

LOG_DAEMON

LOG_WARNING

1083

Warning

JP1/Base Event

KAJP1084-I

LOG_DAEMON

LOG_INFO

1084

Information

JP1/Base Event

KAJP1085-I

LOG_DAEMON

LOG_INFO

1085

Information

JP1/Base Event

KAJP1086-W

LOG_DAEMON

LOG_WARNING

1086

Warning

JP1/Base Event

KAJP1087-W

LOG_DAEMON

LOG_WARNING

1087

Warning

JP1/Base Event

KAJP1741-W

LOG_DAEMON

LOG_WARNING

1741

Warning

JP1/Base Event

KAJP1742-I

LOG_DAEMON

LOG_INFO

1742

Information

JP1/Base Event

KAJP1743-E

LOG_DAEMON

LOG_ERR

1743

Error

JP1/Base Event

KAJP1745-E

LOG_DAEMON

LOG_ERR

1745

Error

JP1/Base Event

KAJP1801-I

LOG_DAEMON

LOG_INFO

1801

Information

JP1/Base Event

KAJP1802-I

LOG_DAEMON

LOG_INFO

1802

Information

JP1/Base Event

KAJP1803-E

LOG_DAEMON

LOG_ERR

1803

Error

JP1/Base Event

KAJP1804-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1805-E

--

--

1805

Error

JP1/Base Event

KAJP1806-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1807-E

LOG_DAEMON

LOG_ERR

1807

Error

JP1/Base Event

KAJP1808-W

--

--

1808

Warning

JP1/Base Event

KAJP1810-E

LOG_DAEMON

LOG_ERR

1810

Error

JP1/Base Event

KAJP1811-E

--

--

1811

Error

JP1/Base Event

KAJP1812-W

--

--

1812

Warning

JP1/Base Event

KAJP1813-E

--

--

1813

Error

JP1/Base Event

KAJP1814-E

--

--

1814

Error

JP1/Base Event

KAJP1815-E

--

--

1815

Error

JP1/Base Event

KAJP1816-W

--

--

1816

Warning

JP1/Base Event

KAJP1817-E

--

--

1817

Error

JP1/Base Event

KAJP1819-E

--

--

1819

Error

JP1/Base Event

KAJP1820-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1826-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1830-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1840-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1841-W

LOG_DAEMON

LOG_WARNING

--

--

--

KAJP1852-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1860-I

LOG_DAEMON

LOG_INFO

--

--

--

KAJP1861-I

LOG_DAEMON

LOG_INFO

--

--

--

KAJP1863-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1864-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1869-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1870-E

LOG_DAEMON

LOG_ERR

--

--

--

KAJP1871-I

LOG_DAEMON

LOG_INFO

--

--

--

KAVA3000-I

--

--

3000

Information

JP1/Base EventlogTrap

KAVA3001-I

--

--

3001

Information

JP1/Base EventlogTrap

KAVA3002-E

--

--

3002

Error

JP1/Base EventlogTrap

KAVA3003-E

--

--

3003

Error

JP1/Base EventlogTrap

KAVA3004-E

--

--

3004

Error

JP1/Base EventlogTrap

KAVA3005-E

--

--

3005

Error

JP1/Base EventlogTrap

KAVA3006-E

--

--

3006

Error

JP1/Base EventlogTrap

KAVA3008-I

--

--

3008

Information

JP1/Base EventlogTrap

KAVA3009-E

--

--

3009

Error

JP1/Base EventlogTrap

KAVA3015-E

--

--

3015

Error

JP1/Base EventlogTrap

KAVA3016-E

--

--

3016

Error

JP1/Base EventlogTrap

KAVA3017-I

--

--

3017

Information

JP1/Base EventlogTrap

KAVA3018-I

--

--

3018

Information

JP1/Base EventlogTrap

KAVA3019-I

--

--

3019

Information

JP1/Base EventlogTrap

KAVA3020-E

--

--

3020

Error

JP1/Base EventlogTrap

KAVA3023-W

--

--

3023

Warning

JP1/Base EventlogTrap

KAVA3024-I

--

--

3024

Information

JP1/Base EventlogTrap

KAVA3025-W

--

--

3025

Warning

JP1/Base EventlogTrap

KAVA3026-W

--

--

3026

Warning

JP1/Base EventlogTrap

KAVA3027-E

--

--

3027

Error

JP1/Base EventlogTrap

KAVA3028-E

--

--

3028

Error

JP1/Base EventlogTrap

KAVA3033-E

--

--

3033

Error

JP1/Base EventlogTrap

KAVA3034-E

--

--

3034

Error

JP1/Base EventlogTrap

KAVA3400-I

LOG_DAEMON

LOG_INFO

--

--

--

KAVA3401-I

LOG_DAEMON

LOG_INFO

--

--

--

KAVA3409-I

LOG_DAEMON

LOG_INFO

--

--

--

KAVA3410-W

LOG_DAEMON

LOG_WARNING

--

--

--

KAVA3413-W

LOG_DAEMON

LOG_WARNING

--

--

--

KAVA3500-I

--

--

3500

Information

JP1/Base LogTrap

KAVA3501-I

--

--

3501

Information

JP1/Base LogTrap

KAVA3502-E

--

--

3502

Error

JP1/Base LogTrap

KAVA3509-I

--

--

3509

Information

JP1/Base LogTrap

KAVA3510-W

--

--

3510

Warning

JP1/Base LogTrap

KAVA3513-W

--

--

3513

Warning

JP1/Base LogTrap

KAVA3600-I

LOG_DAEMON

LOG_INFO

3600

Information

JP1/Base LogTrap

KAVA3601-I

LOG_DAEMON

LOG_INFO

3601

Information

JP1/Base LogTrap

KAVA3602-E

LOG_DAEMON

LOG_ERR

3602

Error

JP1/Base LogTrap

KAVA3604-E

--

--

3604

Error

JP1/Base LogTrap

KAVA3608-E

LOG_DAEMON

LOG_ERR

3608

Error

JP1/Base LogTrap

KAVA3609-E

--

--

3609

Error

JP1/Base LogTrap

KAVA3611-E

--

--

3611

Error

JP1/Base LogTrap

KAVA3613-E

LOG_DAEMON

LOG_ERR

3613

Error

JP1/Base LogTrap

KAVA3614-E

--

--

3614

Error

JP1/Base LogTrap

KAVA3615-E

LOG_DAEMON

LOG_ERR

3615

Error

JP1/Base LogTrap

KAVA3616-E

LOG_DAEMON

LOG_ERR

3616

Error

JP1/Base LogTrap

KAVA3617-E

LOG_DAEMON

LOG_ERR

3617

Error

JP1/Base LogTrap

KAVA3621-W

LOG_DAEMON

LOG_WARNING

3621

Warning

JP1/Base LogTrap

KAVA3623-E

LOG_DAEMON

LOG_ERR

3623

Error

JP1/Base LogTrap

KAVA3624-E

LOG_DAEMON

LOG_ERR

3624

Error

JP1/Base LogTrap

KAVA3625-E

LOG_DAEMON

LOG_ERR

--

--

--

KAVA3629-I

LOG_DAEMON

LOG_INFO

3629

Information

JP1/Base LogTrap

KAVA3632-E

LOG_DAEMON

LOG_ERR

3632

Error

JP1/Base LogTrap

KAVA3633-E

LOG_DAEMON

LOG_ERR

3633

Error

JP1/Base LogTrap

KAVA3634-E

LOG_DAEMON

LOG_ERR

3634

Error

JP1/Base LogTrap

KAVA3635-W

LOG_DAEMON

LOG_WARNING

3635

Warning

JP1/Base LogTrap

KAVA3636-W

LOG_DAEMON

LOG_WARNING

3636

Warning

JP1/Base LogTrap

KAVA3637-I

LOG_DAEMON

LOG_INFO

3637

Information

JP1/Base LogTrap

KAVA3638-E

LOG_DAEMON

LOG_ERR

3638

Error

JP1/Base LogTrap

KAVA3639-E

LOG_DAEMON

LOG_ERR

3639

Error

JP1/Base LogTrap

KAVA3640-W

LOG_DAEMON

LOG_WARNING

3640

Warning

JP1/Base LogTrap

KAVA3641-W

LOG_DAEMON

LOG_WARNING

3641

Warning

JP1/Base LogTrap

KAVA3642-E

LOG_DAEMON

LOG_ERR

3642

Error

JP1/Base LogTrap

KAVA3643-E

LOG_DAEMON

LOG_ERR

3643

Error

JP1/Base LogTrap

KAVA3644-E

LOG_DAEMON

LOG_ERR

3644

Error

JP1/Base LogTrap

KAVA3645-E

LOG_DAEMON

LOG_ERR

3645

Error

JP1/Base LogTrap

KAVA3646-E

LOG_DAEMON

LOG_ERR

3646

Error

JP1/Base LogTrap

KAVA3647-E

LOG_DAEMON

LOG_ERR

3647

Error

JP1/Base LogTrap

KAVA3650-E

LOG_DAEMON

LOG_INFO

3650

Information

JP1/Base LogTrap

KAVA3651-E

LOG_DAEMON

LOG_INFO

3651

Information

JP1/Base LogTrap

KAVA3652-I

LOG_DAEMON

LOG_INFO

3652

Information

JP1/Base LogTrap

KAVA3653-W

LOG_DAEMON

LOG_WARNING

3653

Warning

JP1/Base LogTrap

KAVA3656-E

LOG_DAEMON

LOG_ERR

3656

Error

JP1/Base LogTrap

KAVA3657-I

LOG_DAEMON

LOG_INFO

3657

Information

JP1/Base LogTrap

KAVA3658-W

LOG_DAEMON

LOG_WARNING

3658

Warning

JP1/Base LogTrap

KAVA3659-E

LOG_DAEMON

LOG_ERR

3659

Error

JP1/Base LogTrap

KAVA3660-W

LOG_DAEMON

LOG_WARNING

3660

Warning

JP1/Base LogTrap

KAVA3663-E

LOG_DAEMON

LOG_ERR

3663

Error

JP1/Base LogTrap

KAVA3665-E

LOG_DAEMON

LOG_ERR

3665

Error

JP1/Base LogTrap

KAVA3666-E

LOG_DAEMON

LOG_ERR

3666

Error

JP1/Base LogTrap

KAVA3667-E

LOG_DAEMON

LOG_ERR

3667

Error

JP1/Base LogTrap

KAVA3668-I

LOG_DAEMON

LOG_INFO

3668

Information

JP1/Base LogTrap

KAVA3669-I

LOG_DAEMON

LOG_INFO

3669

Information

JP1/Base LogTrap

KAVA3670-E

LOG_DAEMON

LOG_ERR

3670

Error

JP1/Base LogTrap

KAVA3671-E

LOG_DAEMON

LOG_ERR

3671

Error

JP1/Base LogTrap

KAVA3672-E

LOG_DAEMON

LOG_ERR

3672

Error

JP1/Base LogTrap

KAVA3673-W

LOG_DAEMON

LOG_WARNING

3673

Warning

JP1/Base LogTrap

KAVA3674-E

--

--

3674

Error

JP1/Base LogTrap

1.4.2 List of syslog and the Windows event log entries (related to user management)

Table 1‒20: List of syslog and the Windows event log entries (related to user management)

Message ID

UNIX

(syslog)

Windows

(application log)

Facility

Level

Event ID

Source

KAVA1549-E

LOG_USER

LOG_ERR

1549

JP1/Base

KAVA1586-E

LOG_USER

LOG_ERR

1586

JP1/Base

KAVA1658-E

LOG_USER

LOG_ERR

1658

JP1/Base

1.4.3 List of syslog and the Windows event log entries (related to startup control)

Abbreviation:

--: Not output

Table 1‒21: List of syslog and the Windows event log entries (related to startup control)

Message ID

UNIX

(syslog)

Windows

(application log)

Facility

Level

Event ID

Type

Source

KAVA4101-I

--

--

3

Information

JP1/Base

KAVA4102-I

--

--

3

Information

JP1/Base

KAVA4103-I

--

--

3

Information

JP1/Base

KAVA4104-I

--

--

3

Information

JP1/Base

KAVA4105-I

--

--

3

Information

JP1/Base

KAVA4106-I

--

--

3

Information

JP1/Base

KAVA4107-W

--

--

2

Warning

JP1/Base

KAVA4108-E

--

--

1

Error

JP1/Base

KAVA4109-I

--

--

3

Information

JP1/Base

KAVA4110-I

--

--

3

Information

JP1/Base

KAVA4111-E

--

--

1

Error

JP1/Base

KAVA4501-I

--

--

3

Information

JP1/Base

KAVA4502-I

--

--

3

Information

JP1/Base

KAVA4503-I

--

--

3

Information

JP1/Base

KAVA4504-E

--

--

1

Error

JP1/Base

KAVA4505-E

--

--

1

Error

JP1/Base

KAVA4506-W

--

--

2

Warning

JP1/Base

KAVA4507-E

--

--

1

Error

JP1/Base

KAVA4508-E

--

--

1

Error

JP1/Base

KAVA4509-E

--

--

1

Error

JP1/Base

KAVA4510-W

--

--

2

Warning

JP1/Base

KAVA4511-E

--

--

1

Error

JP1/Base

KAVA4512-E

--

--

1

Error

JP1/Base

KAVA4513-E

--

--

1

Error

JP1/Base

KAVA4514-E

--

--

1

Error

JP1/Base

KAVA4515-E

--

--

1

Error

JP1/Base

KAVA4516-E

--

--

1

Error

JP1/Base

KAVA4517-E

--

--

1

Error

JP1/Base

KAVA4518-E

--

--

1

Error

JP1/Base

KAVA4519-E

--

--

1

Error

JP1/Base

KAVA4520-E

--

--

1

Error

JP1/Base

KAVA4521-E

--

--

1

Error

JP1/Base

KAVA4522-I

--

--

3

Information

JP1/Base

KAVA4523-W

--

--

2

Warning

JP1/Base

1.4.4 List of syslog and the Windows event log entries (related to plug-in services)

Table 1‒22: List of syslog and the Windows event log entries (related to plug-in services)

Message ID

UNIX (syslog)

Windows (application log)

Facility

Level

Event ID

Type

Source

KAVA6717-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

1.4.5 List of syslog and the Windows event log entries (related to health checks)

Table 1‒23: List of syslog and the Windows event log entries (related to a health check)

Message ID

UNIX

(syslog)

Windows

(application log)

Facility

Level

Event ID

Type

Source

KAVA7003-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVA7013-W

LOG_USER

LOG_WARNING

2

Warning

JP1/Base

KAVA7014-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVA7016-I

LOG_USER

LOG_INFO

3

Information

JP1/Base

KAVA7017-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVA7026-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVA7027-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVA7028-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVA7030-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVA7050-W

LOG_USER

LOG_WARNING

2

Warning

JP1/Base

KAVA7051-W

LOG_USER

LOG_WARNING

2

Warning

JP1/Base

KAVA7052-W

LOG_USER

LOG_WARNING

2

Warning

JP1/Base

KAVA7210-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVA7222-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVA7223-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVA7224-I

LOG_USER

LOG_INFO

3

Information

JP1/Base

KAVA7226-E

LOG_USER

LOG_ERR

2

Error

JP1/Base

KAVA7228-I

LOG_USER

LOG_INFO

3

Information

JP1/Base

KAVA7229-W

LOG_USER

LOG_WARNING

2

Warning

JP1/Base

1.4.6 List of syslog and the Windows event log entries (related to command execution)

Abbreviation:

--: Not output

Table 1‒24: List of syslog and the Windows event log entries (related to command execution)

Message ID

UNIX (syslog)

Windows (application log)

Facility

Level

Event ID

Type

Source

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

--

--

--

1.4.7 List of syslog and the Windows event log entries (related to configuration management)

Table 1‒25: List of syslog and the Windows event log entries (related to configuration management)

Message ID

UNIX (syslog)

Windows (application log)

Facility

Level

Event ID

Type

Source

KAVB3001-E to KAVB3004-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVB3007-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

1.4.8 List of syslog and the Windows event log entries (related to process management)

Abbreviation:

--: Not output

Table 1‒26: List of syslog and the Windows event log entries (related to process management)

Message ID

UNIX (syslog)

Windows (application log)

Facility

Level

Event ID

Type

Source

KAVB3501-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVB3516-E

LOG_USER

LOG_ERR

--

--

JP1/Base

KAVB3613-W

LOG_USER

LOG_WARNING

2

Warning

JP1/Base

KAVB3614-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVB3620-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVB3621-E

LOG_USER

LOG_ERR

--

--

JP1/Base

KAVB3623-E

LOG_USER

LOG_ERR

--

--

JP1/Base

KAVB3624-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVB3625-E to KAVB3626-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVB3642-E to KAVB3644-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVB3649-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVB3664-I

LOG_USER

LOG_INFO

3

Information

JP1/Base

KAVB3665-I

LOG_USER

LOG_INFO

3

Information

JP1/Base

KAVB3666-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVB3737-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVB3752-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVB3788-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVB3792-E

--

--

1

Error

JP1/Base

KAVB3862-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVB3870-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVB3872-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVB3874-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVB3875-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

KAVB3899-E

LOG_USER

LOG_ERR

1

Error

JP1/Base

1.4.9 List of syslog and the Windows event log entries (related to local actions)

Table 1‒27: List of syslog and the Windows event log entries (related to local actions)

Message ID

UNIX (syslog)

Windows (application log)

Facility

Level

Event ID

Type

Source

KNAM3021-W

LOG_DAEMON

LOG_WARNING

2

Warning

JP1/Base

KNAM3031-W

LOG_DAEMON

LOG_WARNING

2

Warning

JP1/Base

KNAM3101-E to

KNAM3132-E

LOG_DAEMON

LOG_ERR

1

Error

JP1/Base

KNAM3133-W

LOG_DAEMON

LOG_WARNING

2

Warning

JP1/Base

KNAM3134-I

LOG_DAEMON

LOG_INFO

3

Information

JP1/Base

KNAM3137-I

LOG_DAEMON

LOG_INFO

3

Information

JP1/Base

KNAM3140-E to KNAM3150-E

LOG_DAEMON

LOG_ERR

1

Error

JP1/Base

2 List of Messages

This section describes JP1/Base messages that have message IDs. For other messages, see the chapter about troubleshooting in the Job Management Partner 1/Base User's Guide.

2.1 Event service messages (KAJP1001 to KAJP1871)

Note

Messages from KAJP1001-I through KAJP1076-E are output to the Windows event log without message IDs.

KAJP1001-I

The event server will now start.

The event service will now start.

KAJP1002-I

The event server is ready.

The event server is ready for use.

KAJP1003-I

The event server will now stop.

The event server will now stop.

KAJP1004-E

The event server cannot start because another one is already running.

The event server cannot start because another event service is already running.

(S)

Cancels event server startup processing.

(O)

Stop the active event service, and then restart the event server you want. In a UNIX system, if the event service is running on the physical host, even if you attempt to stop the jevservice by using the kill command, processes of the JP1/SES compatibility function may not stop. In such a case, the event server cannot start and outputs this message.

Use the ps -el command to check whether the jesdmain and jesrd processes are active. If these processes are active, use the kill command to stop them, and then start the event service.

KAJP1005-E

The event server stopped due to an error that prevents processing.

An unrecoverable error occurred at the event server.

An attempt to start the event servers simultaneously caused the error (when the KAJP1056-E message has been output).

(S)

Stops the event server.

(O)

Check the event log (in Windows) or syslog (in UNIX) to see whether there is any other error message regarding the event service.

If there is another error message, this message is caused by that error message. Take action according to the other error message. If the KAJP1056-E message has been output, see the corrective action shown in this message.

If there is no other error message, contact the system administrator.

KAJP1006-I

The event DB was switched from old-database-number to new-database-number.

The event database file was switched from the previous database number to a new database number.

KAJP1010-E

A system error occurred. (detail-code)

A system error occurred at the event server.

(S)

Stops the event server.

(O)

To resolve the local host name by using DNS, make sure that DNS is running.

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

KAJP1011-E

A software exception occurred. (detail-code)

A software exception occurred at the event server.

(S)

Stops the event server.

(O)

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

KAJP1012-E

An unexpected exception occurred. (detail-code)

An unexpected exception occurred at the event server.

(S)

Stops the event server.

(O)

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

KAJP1013-E

Memory is insufficient. (detail-code)

There is not enough memory at the event server.

(S)

Continues processing.

(O)

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

KAJP1015-E

An attempt to obtain a system resource has failed. (detail-code)

An attempt to obtain an OS system resource used by the event server has failed.

(S)

Stops the event server.

(O)

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

KAJP1017-E

An error occurred during the forwarding of an event to event-server-name.

An error occurred while an event was being forwarded to the indicated remote event server.

(S)

Continues processing.

(O)

Check the status of the destination event server where the error occurred. When using a machine that uses more than two network information cards (NIC), check whether the client-blind parameter in the event server settings (conf) file is defined.

KAJP1018-I

The event server is ready to forward events to event-server-name.

Events can now be forwarded to the indicated remote event server.

KAJP1019-W

The event server is already running.

The event server is already running.

(O)

Stop the already running event service, and then restart the event server. This message also appears when an attempt was made to start the event service during initialization of an event database by using the jevdbinit or jevdbmkrep command. In such a case, make sure that the jevdbinit or jevdbmkrep command has finished, and then start the event service.

KAJP1020-W

The event server has already stopped.

The event server has already stopped.

KAJP1021-E

The DB manager ended abnormally. (detail-code)

The database process (thread) ended abnormally.

(S)

Stops the event server.

(O)

Check the timing at which logs are output. If cluster resources have stopped or the OS has been shut down, the cluster software or OS might have forcibly stopped the system. In this case, no special action is required.

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

KAJP1022-E

The event forwarding manager ended abnormally. (detail-code)

The event forwarding management process (thread) ended abnormally.

(S)

Stops the event server.

(O)

Make sure that:

Timing at which logs are output

If cluster resources have stopped or the OS has been shut down, the cluster software or OS might have forcibly stopped the system. In this case, no special action is required.

The local event server name has not been specified as the destination event server name in the forwarding settings file (forward).

If the local event server name is specified as the destination event server name, more resources are consumed. For the destination event server name, always specify the name of an event server other than the local event server.

A network error has not occurred.

If a network error has occurred, remove the cause of the error, and then restart the event service.

The IP address to be used by the event service is assigned.

If you are using a cluster system, the IP address must be online before the event service starts.

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

KAJP1023-E

The SES emulator ended abnormally. (detail-code)

The SES emulator process (thread) ended abnormally.

(S)

Stops the event server.

(O)

Make sure that:

Timing at which logs are output

If the OS has been shut down, the OS might have forcibly stopped the system. In this case, no particular action is required.

The files under /usr/tmp/jp1_ses have not been deleted.

If the settings are specified so that the files under /tmp are automatically deleted by tools, make sure that the files under /usr/tmp/jp1_ses have not been deleted mistakenly. If the files were deleted, change the settings so that the files under /usr/tmp/jp1_ses are not deleted.

The number of messages queued in the message queue has not reached the system limit.

If the number of queued messages has reached the system limit, check and, if necessary, revise the kernel parameters so that the number of messages used by JP1/Base can be allocated.

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

KAJP1024-E

The log manager ended abnormally. (detail-code)

The log output management process (thread) ended abnormally.

(S)

Stops the event server.

(O)

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

KAJP1025-E

An I/O error occurred. (detail-code)

An I/O error occurred.

(S)

Stops the event server.

(O)

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

KAJP1027-E

The event server name is not defined.

The event server name is not defined in the event server index file.

(S)

Cancels event server startup processing.

(O)

Define the event server name in the event server index file, and then restart the event server.

KAJP1028-E

The event server cannot start.

The event server cannot start because of an error in the event server index file or event server settings file.

(S)

Cancels event server startup processing.

(O)

Make sure that:

The directory specified in the event server index file (index) exists.

If the specified directory does not exist, create a directory and then copy the definition files (conf and forward) to the directory, or change the specified directory to an existing directory.

If you are using a cluster system, the settings are specified so that the event service starts after the shared disk is mounted.

If the settings are specified so that the event service starts before the shared disk is mounted, change the settings.

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

KAJP1029-E

The event server cannot be stopped.

The event server cannot be stopped because of an error in the event server index file or event server settings file.

(S)

Terminates event server shutdown.

(O)

Make sure that the event server index file (index) has not been changed. If it has been changed, restore the file to the previous status and then stop the event service.

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

KAJP1030-W

number-of-deleted-records invalid record(s) were deleted from the end of the event DB (applicable-file-number.type).

Invalid data was found at the end of the event database file. The system may not have terminated normally at the previous termination. The issued event may be lost.

(S)

Deletes the invalid data and continues processing.

(O)

Use the jevexport command to make sure that the event required for the task is not lost.

KAJP1031-W

Missing record(s) were detected in the event DB (applicable-file-number.type).

Required records are missing in the event database. The system may not have terminated normally at the previous termination.

(S)

Corrects only the consistency of the event database and continues processing.

(O)

Use the jevexport command to make sure that the event required for the task is not lost.

KAJP1032-E

An event cannot be registered. (system-error-message)

The event could not be registered because of the reason between the parentheses (for example: insufficient disk space).

(S)

Returns the error to the registration source program and continues processing the event server.

(O)

Eliminate the cause indicated by the system error message.

KAJP1033-E

There is an error in the forwarding setting file. (line-number, error-line)

The JP1 event cannot be forwarded since the forwarding settings file (forward) contains an error.

(S)

Continues processing.

(O)

There is an error in the definitions of the forwarding settings file (forward). Make sure that:

There are no spelling errors in the attribute names or comparison keywords that are set in the forwarding settings file (forward).

There are no extra spaces or tab characters after OR.

There are no comments written after the filter.

Double-byte spaces are not used as the delimiter.

The number of bytes specified for the line is fewer than 1,023.

The size of the event filter specified in the forwarding setting block or forwarding-suppression setting block does not exceed 64 kilobytes.

Correct the error in the definitions of the forwarding settings file (forward), and then execute the jevreload command.

KAJP1034-E

The socket cannot be initialized. (service-name: port-number) (maintenance-code)

An incorrect service name or port number was specified in the port parameter in the event server settings file (conf).

(S)

Terminates the startup of the event server.

(O)

Make sure that the service name specified in the port parameter in the event server settings file (conf) is defined in the services file of the system, and that the correct port number is specified. Then, correct the error.

KAJP1035-E

An error occurred during processing of the event database. (maintenance-information)

An error occurred during processing of the event database.

(S)

The event server continues processing.

(O)

Make sure that the network connection is correct. Also, make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAJP1036-E

An error occurred during processing of an event. (maintenance-information)

An error occurred during processing of an event.

(S)

The event server stops processing.

(O)

Make sure that the network connection is correct. Also, make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAJP1037-E

An event could not be forwarded. (seqno = serial-number-in-event-database eventid = event-ID server = destination-event-server-name time = registration-time)

An event could not be forwarded.

(S)

The event server continues processing.

(O)

Make sure that:

The network connection is correct.

There has been no severe deterioration in OS resources, available memory, or the communication environment.

Both the send-source and send-destination event servers use the same IP address version (IPv4 or IPv6).

For details about how to check the IP address version (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the Job Management Partner 1/Base User's Guide.

KAJP1038-E

The registry cannot be read. (maintenance-information)

The registry cannot be read.

(S)

The event service stops processing.

(O)

Check the status (security) of the registry.

KAJP1039-E

A message cannot be read. (maintenance-information)

A message string for display or logging cannot be read.

(S)

Terminates command processing.

(O)

Make sure that the following file exists and that you have read permission for it:

In Windows: Message DLL file (jevmessage.dll)

In UNIX: Message catalog file (msg.cat)

KAJP1040-E

An error occurred during internal log output processing. (maintenance-information)

An error occurred during internal log output processing.

(S)

The event service stops processing.

(O)

Make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAJP1043-E

An unexpected command was received. (maintenance-information)

An unexpected command was received.

(S)

Continues processing.

(O)

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

KAJP1044-E

An error occurred during command processing. (maintenance-information)

An error occurred during command processing.

(S)

Continues processing.

(O)

Make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAJP1045-E

An error occurred during processing to obtain the event server name. (maintenance-information)

An error occurred during processing to obtain the event server name.

(S)

Terminates command processing.

(O)

Make sure that the network connection is correct.

KAJP1046-E

A process cannot be created. (maintenance-information)

A process for starting the event service cannot be created.

(S)

Terminates command processing.

(O)

Make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAJP1048-E

A process group cannot be set. (maintenance-information)

A process group cannot be set.

(S)

Terminates command processing.

(O)

Make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAJP1049-E

The event server cannot be initialized. (maintenance-information)

The event server cannot be initialized.

(S)

Stops the startup of the event server.

(O)

Make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment. Also, check that the name of the event server of the physical host set in index matches with the host name output by the hostname command. Note that the event server name specified in index is case sensitive.

KAJP1051-E

The event server cannot start. (maintenance-information)

The event server cannot start.

(S)

Terminates command processing.

(O)

Make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAJP1052-E

The event server cannot be stopped. (maintenance-information)

The event server cannot be stopped.

(S)

Terminates command processing.

(O)

Make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAJP1053-E

There is an error in the settings file (file-name).

The environment settings file contains an error.

(S)

Assumes or ignores the value for the parameter, and continues processing.

(O)

Correct the settings in the environment settings files, and then restart the event server. When this message is output even if there is no problem in the environment settings files, collect data by using the data collection tool, and then contact the system administrator.

KAJP1056-E

Since the event server has already started, it cannot start simultaneously.

An attempt was made to start an event server while another event server has already started.

(S)

Terminates command processing.

(O)

Make sure that there is a running event server. Also check and, if necessary, revise the environment settings of the event service so that the event service does not reference the files on the same shared directory as the running event server.

KAJP1057-W

An invalid record was detected in the event database (file-number.type). (record number = record-number)

An invalid record was detected in the event database during acquisition of events. Some events could not be searched for. Registration and acquisition of new events will not be affected.

(S)

Continues the event service.

(O)

Check whether the event database was backed up or restored using an OS command or backup software while the event service was running. Also check whether the event database was referenced or edited using an editor.

An invalid record in the event database may cause deterioration in performance. Switch or initialize the event database.

KAJP1058-W

An invalid record was detected in the event database (file-number.type). The event (seqno = serial-number-in-event-database) cannot be obtained.

An invalid record was detected in the event database during acquisition of events. Some events could not be searched for. Registration and acquisition of new events will not be affected.

(S)

Continues the event service.

(O)

Check whether the event database was backed up or restored using an OS command or backup software while the event service was running. Also check whether the event database was referenced or edited using an editor.

An invalid record in the event database may cause deterioration in performance. Switch or initialize the event database.

KAJP1059-E

The event service cannot start because restoration of the event database (file-number.type) failed.

The header record in the event database is corrupted. The event service cannot start because an attempt to correct the event database has failed.

(S)

Stops the event service.

(O)

Initialize the event database, and then start the event service.

KAJP1060-E

The event service cannot start because the event database (file-number.type) cannot be opened.

(cause = cause)

The event service cannot start because the system retried opening the event database for a predefined period of time, but could not open it.

(S)

Stops the event service.

(O)

Another program may have opened the event database.

Stop the program that has opened the event database, and then start the event service.

KAJP1061-I

The event database was switched from old-database-number to new-database-number.

The event database was switched according to the setting of the event service or by using the jevdbswitch command.

(S)

Continues the event service.

KAJP1062-E

The event database could not switch from old-database-number to new-database-number. (cause = cause)

An attempt to switch the event database according to the setting of the event service or by using the jevdbswitch command has failed.

(S)

Continues the event service.

(O)

Correct the cause of the error indicated in cause in the message.

KAJP1063-E

An attempt to acquire the port number has failed. (service name = service-name, cause = cause)

An attempt to acquire the port number used for starting the service has failed.

(S)

Continues the event service.

(O)

Check whether the port number for the service name has been registered in the services file. Also check whether read permission has been set for the services file.

KAJP1064-W

The event service will now start, and the default port number will be assumed. (service name = service-name)

The service has started using the default port number because an attempt to acquire the port number failed.

(S)

Assumes the default port number and continues the event service.

(O)

Check whether the port number for the service name has been registered in the services file. Also check whether read permission has been set for the services file.

KAJP1065-I

The event server will now operate in interchangeable character encoding mode. (jevsend)

Interchangeable character encoding mode was enabled when the event service started.

(S)

Continues the event service.

KAJP1066-W

The value specified for the interchangeable character encoding mode is invalid. (jevsend)

The mode setting value is not 0 or 1.

(S)

Disables interchangeable character encoding mode, and continues processing.

(O)

Correct the value of the setting for interchangeable character encoding mode, and then re-execute the command.

For details about how to check the value that is set, see 3.4.1 Setting the language (UNIX only) in the Job Management Partner 1/Base User's Guide.

KAJP1067-W

The event server cannot operate in interchangeable character encoding mode because the value specified for this mode could not be acquired. (jevsend)

The value of the setting for interchangeable character encoding mode could not be acquired.

(S)

Disables interchangeable character encoding mode, and continues processing.

(O)

If the event server needs to operate in interchangeable character encoding mode, re-execute the command.

If the event server does not need to operate in interchangeable character encoding mode, ignore the message.

KAJP1068-I

The compatibility functions of version 5 cannot be used.

The functions for compatibility with the pre-Version 6 programs, JP1/AJS and JP1/SES, are unavailable.

(S)

Continues the event service.

KAJP1070-E

An internal function ended abnormally. (function name = internal-function-name, signal = signal-number)

The system detected that an internal function of the event service terminated abnormally.

(S)

If the restart parameter is defined in the event server settings file (conf), the event server continues processing by restarting the internal function. If the restart parameter is not defined or the number of restarts exceeds the upper limit, the event server stops processing.

(O)

A message that indicates the cause of abnormal termination of the internal function is output immediately before this message. Remove the cause of the error according to the action described in the message. If you cannot identify the cause, use the data collection tool to collect data, and then contact the system administrator.

KAJP1071-I

An internal function will now restart. (function name = internal-function-name, count = number-of-restarts / maximum-number-of-restarts)

The internal function of the event service that terminated abnormally will now restart.

KAJP1072-I

The event service was recovered by restarting an internal function. (abnormal end time = YYYY:MM:DD hh:mm:ss)

The event service was recovered by restarting an internal function.

KAJP1073-E

An attempt to restart an internal function has failed. (function name = internal-function-name, errno = error-number)

An attempt to restart an internal function of the event service has failed.

(S)

If the number of times the internal function terminated abnormally is less than the maximum number of times defined in the restart parameter, the system attempts to restart the internal function. If it exceeds the maximum number of times, the system stops the event service.

(O)

If the event service stops, use the data collection tool to collect data, and then contact the system administrator.

KAJP1074-I

The forwarding settings file was read successfully. (file = file-name, last updated = YYYY/MM/DD hh:mm:ss)

The forwarding settings file (forward) was read successfully.

KAJP1075-W

The repetition prevention table is in an invalid state. (message-that-indicates-the-cause)

The repetition prevention table is in an invalid state.

(S)

Continues processing with the retention of the files in the repetition prevention table disabled.

(O)

Stop the event service and then execute the jevdbmkrep command.

KAJP1076-E

Input to or output from the repetition prevention table file has failed. (cause = message-that-indicates-the-cause)

Input to or output from the repetition prevention table file has failed.

(S)

During startup: Stops the event server.

During operation: Continues processing with the retention of the files in the repetition prevention table disabled.

(O)

Stop the event service and then execute the jevdbmkrep command.

If the error cannot be recovered, use the data collection tool to collect data, and then contact the system administrator.

KAJP1081-W

The event server received (from the event server event-server-name) an event acquisition request that used an unsupported encoding. (encoding = encoding)

An event acquisition (search) request that used unsupported encoding (indicated by encoding) was received from the event server (indicated by event-server-name).

(S)

The event acquisition request is assumed to be issued in English, and processing of the request continues. If the event filter of the request contains multi-byte characters when the request is processed, the intended JP1 event might not be obtained.

(O)

Perform one of the following workarounds:

Upgrade to a version of JP1/Base that supports the encoding used in the messages.

If the operating system of the host that is acquiring the information is UNIX, change the language setting of the environment variable LANG for JP1/Base to a language supported by the version of JP1/Base that the host that the information is being acquired from is running.

KAJP1082-W

A JP1 event message lost data when it was converted to UTF-8 encoding. (bytes of data lost =bytes-of-data-lost, original encoding = original-encoding, seqno = serial-number-in-event-database)

Part of the message is lost when the JP1 event is converted to UTF-8 encoding.

(S)

The JP1 event is registered to the event database without a message, and processing continues.

(O)

Check whether the information in the omitted message has any effect on operations (monitoring conditions for JP1/AJS event monitoring jobs, and the execution conditions for JP1/IM automatic actions).

KAJP1083-W

host-name will start the threshold-based suppression of event-forwarding. (suppression ID = identifier)

The event server indicated by host-name will start suppression of event-forwarding because events that meet the conditions (indicated by identifier) for the suppression of event-forwarding occurred frequently and the number of events reached the threshold.

(S)

Continues processing.

(O)

Investigate the cause of events that occurred frequently, and take the necessary action.

KAJP1084-I

host-name stopped the threshold-based suppression of event-forwarding. (suppression ID = identifier)

The event server indicated by host-name stopped suppression of event-forwarding because the number of events per a given time that meet the condition (indicated by identifier) for the suppression of event-forwarding was reduced below the threshold.

KAJP1085-I

host-name stopped all threshold-based suppressions of event-forwarding.

All event-forwarding suppression statuses were stopped because the event server indicated by host-name stopped or because the forwarding settings file (forward) was reloaded by the jevreload command.

KAJP1086-W

Suppression of event-forwarding by host-name has continued for total-suppression-time seconds. (suppression ID = identifier)

Suppression of event-forwarding on the host indicated by host-name has continued for a predefined time.

(S)

Continues processing.

(O)

Investigate the cause of events that occurred frequently and any suppression that continues for an extended period of time, and then take the necessary action.

KAJP1087-W

Suppression of event-forwarding by the jevagtfw command has continued for total-suppression-time seconds. (server = host-name)

Suppression of event-forwarding from the host indicated by host-name has continued for a predefined time.

(S)

Continues processing.

(O)

If the suppression is not intentionally continued (for example, the user omitted to stop the suppression), execute the jevagtfw command with the -r option specified to stop the suppression of event-forwarding.

KAJP1101-E

An attempt to distribute setting/definition information has failed.

An attempt at distribution processing in the distribution-destination host has failed.

(S)

Continues command processing.

(O)

Check the cause of the error from the previous output message, and then re-execute the command.

KAJP1102-E

An attempt to obtain setting/definition information has failed. (host = host-name)

An attempt to obtain information at a managed host has failed.

(S)

Continues command processing.

(O)

Check the cause of the error from the previous output message, and then re-execute the command.

KAJP1103-E

Invalid protocol data was received. (host = host-name)

Invalid protocol data was received.

(S)

Terminates command processing.

(O)

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

KAJP1104-E

A required option is not specified.

A required option is not specified.

(S)

Terminates command processing.

(O)

One of the -f, -e, or -l options must be specified for this command.

KAJP1105-E

A temporary file cannot be created.

A temporary file cannot be created.

(S)

Terminates command processing.

(O)

Make sure that the system can open the number of files to be opened for the command execution environment, and make sure that there is enough disk space, and then re-execute the command.

KAJP1106-E

A log file cannot be created.

A log file cannot be created.

(S)

Terminates command processing.

(O)

Make sure that the system can open the number of files to be opened for the command execution environment, and make sure that there is enough disk space, and then re-execute the command.

KAJP1107-E

A connection to the plug-in service cannot be established. (host = host-name)

A command has been executed but the plug-in service is not active yet.

(S)

Terminates command processing.

(O)

Re-execute the command after you have made sure that:

The plug-in service on the connected host is active.

The connected host has a name that can be resolved by both the manager host and the managed host.

The environment settings of JP1/Base for the connected host are correct.

The JP1/Base versions between the connected host and the manager host are compatible.

The network settings and the communication environment are correct.

Both the connected host and the manager host use the same IP address version (IPv4 or IPv6).

For details about how to check the IP address version (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the Job Management Partner 1/Base User's Guide.

KAJP1108-E

The conf path could not be obtained from the common definition information.

The conf path could not be obtained from the common definition information.

(S)

Terminates command processing.

(O)

Make sure that the path of the conf directory for JP1/Base has been defined in the common definition information.

KAJP1109-E

The log path could not be obtained from the common definition information.

The log path could not be obtained from the common definition information.

(S)

Terminates command processing.

(O)

Make sure that the path of the log directory for JP1/Base is defined in the common definition information.

KAJP1110-E

A message cannot be read. (maintenance-information)

A message cannot be read.

(S)

No message is output.

Continues command processing.

(O)

Make sure that the following file exists and that you have read permission for it:

In Windows: Message DLL file (jevmessage.dll)

In UNIX: Message catalog file (msg.cat)

KAJP1111-E

Distribution of setting/definition information was successful, but reloading failed.

Setting or definition information was successfully distributed, but an attempt to reload the information has failed.

(S)

Terminates command processing.

(O)

Check the cause of the error from the previous output message, and then re-execute the command.

KAJP1113-E

There is no definition of the conf directory path for JP1/IM - Console.

The definition of the conf directory for JP1/IM - Manager could not be obtained.

(S)

Terminates command processing.

(O)

Install and set up JP1/IM - Manager correctly.

KAJP1114-E

There is no JP1/IM - Console product information.

The product type of JP1/IM - Manager could not be obtained. This message is output on a machine where only JP1/Base is installed.

(S)

Terminates command processing.

(O)

Install and set up JP1/IM - Manager correctly.

KAJP1115-E

An attempt to open the distribution definition file has failed. (file = file-name)

An attempt to open the distribution definition file has failed.

(S)

Terminates the jevdef_distrib command.

(O)

Make sure that the distribution definition file is located in the specified directory, and that the user has read permission for the distribution definition file.

KAJP1117-E

The name of the distribution host is duplicated in the distribution definition file. (line = line-number, duplicated host = host-name)

The name of the host is duplicated within a distribution definition file.

(S)

Terminates command processing.

(O)

Make sure that no host name is duplicated within a distribution definition file.

KAJP1118-E

The specified distribution host is not defined.

The host name is not defined in the distribution definition file.

(S)

Terminates command processing.

(O)

Check the distribution definition file.

KAJP1119-E

The length of the host name exceeds 256 characters. (line = line-number, host = host-name)

The host name defined in the distribution definition file has 256 or more characters.

(S)

Terminates command processing.

(O)

Check and correct the distribution definition file so that the host name has no more than 255 characters.

KAJP1121-E

The specified host is not a managed host. (line = line-number, host = host-name)

A non-managed host is defined.

(S)

Terminates command processing.

(O)

Check and correct the configuration file so that there all hosts specified for destination hosts are managed hosts.

KAJP1123-E

An attempt to obtain configuration definition data has failed.

An input/output error occurred during an attempt to read the configuration definition file.

(S)

Cannot execute the command.

(O)

Make sure that you have write permission for the conf/route/ directory.

KAJP1124-W

The server is processing. (server = host-name)

A command for integrated management has been executed during processing of the integrated management server.

(S)

Continues command processing.

(O)

Wait a while, and then re-execute the command.

KAJP1126-I

The jevdef_distrib command ended successfully.

The jevdef_distrib command ended successfully.

(S)

The jevdef_distrib command terminated normally.

KAJP1128-E

The common definition information could not be accessed.

An attempt to read common definition information has failed.

(S)

Terminates command processing.

(O)

Make sure that the /opt/jp1/hcclibcnf directory exists, and that you have access permissions for it.

KAJP1130-E

The connection with the plug-in service timed out. (host = host-name)

The command timed out.

(S)

Continues command processing.

(O)

Check the following:

Make sure that no error occurred in the distribution-destination host.

If acquisition or distribution of settings or definitions takes too much time, the command times out. Check and, if necessary, revise the system configuration.

KAJP1131-E

The specified logical host name is not defined. (host = host-name)

An attempt to initialize the communication base has failed. The jp1hosts data was invalid and could not be read.

(S)

Terminates command processing.

(O)

Information about the specified logical host does not exist. Make sure that the specified logical host name is correct, and that setup was performed correctly.

KAJP1132-I

Obtaining the event-log trap definition from a UNIX host is not possible.

Obtaining the event-log trap definition from a UNIX host is not possible.

(S)

Continues command processing.

KAJP1134-E

The length of a line exceeds 1,024 characters. (line num. = line-number)

A line that exceeds 1,024 characters is defined in the distribution definition file.

(S)

Terminates command processing.

(O)

Check the contents of the distribution definition file, and then re-execute the command.

KAJP1135-E

There is an error in the specified distribution host. (line num. = line-number)

There is an error in the specified distribution host in the distribution definition file.

(S)

Terminates command processing.

(O)

In the distribution definition file, check whether there is an error in the specification of a distribution host, and then re-execute the command.

KAJP1136-E

An invalid name for an action definition file was specified. (line = line-number)

An invalid name for an action definition file was specified in the distribution definition file.

(S)

Terminates command processing.

(O)

Do not include \, /, :, ., ;, *, ?, ", <, >, |, tabs and spaces in the name of a distribution definition file. Check the contents of the definition file, and then re-execute the command.

KAJP1137-E

An action definition file cannot be specified. (line = line-number)

An action definition file name is specified in a distribution definition file.

(S)

Terminates command processing.

(O)

You cannot specify an action definition file name using this command. Check the contents of the distribution definition file, and then re-execute the command.

KAJP1141-E

The logical host name is too long.

A logical host name with 197 or more characters (in Windows), or 256 or more characters (in UNIX), has been specified.

(S)

Terminates command processing.

(O)

In Windows, specify a logical host name that has no more than 196 characters.

In UNIX, specify a logical host name that has no more than 255 characters.

KAJP1142-E

An attempt to obtain information at one or more managed hosts has failed.

An attempt to obtain information at a host has failed.

(S)

Terminates command processing.

(O)

Check the cause of the error from the output message, and then re-execute the command.

KAJP1143-E

At attempt to distribute to one or more managed hosts has failed.

Distribution processing for a host has failed.

(S)

Terminates command processing.

(O)

Check the cause of the error from the output message, and then re-execute the command.

KAJP1144-I

Setting/definition information was successfully obtained.

Processing to obtain setting or definition information finished successfully.

(S)

Terminates command processing.

KAJP1145-I

Setting/definition information was successfully distributed.

Distribution of the setting or definition information finished successfully.

(S)

Terminates command processing.

KAJP1146-E

The name of the acquisition host is duplicated. (host=host-name)

The name of the host acquisition was requested for is duplicated.

(S)

Terminates command processing.

(O)

Correct the option, and re-execute the command.

KAJP1147-E

The specified host is not a managed host. (host=host-name)

The specified host is not a managed host.

(S)

Terminates command processing.

(O)

Correct the host name, and re-execute the command.

KAJP1150-E

There is a syntax error in the distribution definition file. (line = line-number)

There is a syntax error in the distribution definition file.

(S)

Terminates command processing.

(O)

Check the contents of the distribution definition file, and then re-execute the command.

KAJP1152-E

There is a syntax error in the action definition in the distribution definition file. (distribution host = host-name)

The distribution processing was not performed due to a syntax error in the action definition line in the distribution definition file.

(S)

Terminates command processing.

(O)

Check the contents of the distribution definition file, and then re-execute the command.

KAJP1154-E

An invalid name for the action definition file was specified.

An invalid file name was specified for acquiring the action definition file.

(S)

Terminates command processing.

(O)

Do not include \, /, :, ;, *, ?, ", <, >, |, tabs and spaces in the name of an action definition file.

KAJP1155-E

An invalid name was specified for the distribution definition file.

An invalid name was specified for the distribution definition file.

(S)

Terminates command processing.

(O)

Do not include \, /, :, ;, *, ?, ", <, >, |, tabs and spaces in the name of a distribution definition file.

KAJP1156-W

JP1/Base on the host does not support distribution of the log-file trap startup definition file. (host = host-name)

The host that distribution was requested for does not support distribution of the log-file trap startup definition file.

(S)

Continues command processing.

(O)

Update the version of JP1/Base on the host to 10-00 or later.

KAJP1157-W

JP1/Base on the host does not support acquisition of the log-file trap startup definition file. (host = host-name)

The host acquisition was requested for does not support acquisition of the log-file trap startup definition file.

(S)

Continues command processing.

(O)

Update the version of JP1/Base on the host to 10-00 or later.

KAJP1201-I

The processing to obtain information via the plug-in service will now start.

The processing to obtain information via the plug-in service will now start.

KAJP1202-I

Distribution processing via the plug-in service will now start.

Distribution processing via the plug-in service will now start.

KAJP1203-I

The processing to obtain or distribute information via the plug-in service will now end. (exit code = exit-code)

The processing to obtain or distribute information via the plug-in service will now end.

KAJP1204-I

The reload command will now execute. (command = command-name)

The reload command will now execute.

KAJP1205-E

An attempt to execute a reload command has failed. (exit code = exit-code)

An attempt to execute the jevreload, jeveltreload, or jevlogreload command has failed.

(S)

Does not execute the reload command.

(O)

Check the contents of the configuration definition and the distribution definition file, and then re-execute the command.

KAJP1206-W

The setting/definition file does not exist. (file = file-name)

The setting or definition file does not exist.

(S)

Does not obtain the setting or definition file.

(O)

Make sure that the file exists.

KAJP1207-E

The setting/definition file cannot be accessed. (file = file-name)

You do not have access privileges for the setting or definition files.

(S)

Terminates the acquisition or the distribution processing.

(O)

Check the access privileges for the files, and then re-execute the command.

KAJP1208-I

The setting/definition files were distributed. (file = file-name)

The setting or definition files were distributed.

KAJP1209-E

Memory is insufficient.

Insufficient memory.

(S)

Terminates the acquisition or distribution processing.

(O)

Terminate other programs that may be using memory, and then re-execute the command.

KAJP1210-E

A message cannot be read. (maintenance-information)

A message cannot be read.

(S)

Does not output any message. Terminates the acquisition or distribution processing.

(O)

Make sure that the following file exists, and that you have appropriate permissions for it:

In Windows: Message DLL file (jevmessage.dll)

In UNIX: Message catalog file (msg.cat)

KAJP1211-I

The command will now operate in interchangeable character encoding mode. (jevdef)

Interchangeable character encoding mode was enabled when the command was executed.

(S)

Continues command processing.

KAJP1212-W

The value specified for the interchangeable character encoding mode is invalid. (jevdef)

The mode setting value is not 0 or 1.

(S)

Disables interchangeable character encoding mode, and continues processing.

(O)

Correct the value of the setting for interchangeable character encoding mode, and then re-execute the command.

For details about how to check the value that is set, see 3.4.1 Setting the language (UNIX only) in the Job Management Partner 1/Base User's Guide.

KAJP1213-W

The command could not be executed in interchangeable character encoding mode because the value specified for this mode in the host collecting or distributing the definition information could not be acquired. (jevdef)

The value of the setting for interchangeable character encoding mode could not be acquired.

(S)

Disables interchangeable character encoding mode, and continues processing.

(O)

If the host needs to operate in interchangeable character encoding mode, re-execute the command. If the host does not need to operate in interchangeable character encoding mode, ignore the message.

KAJP1302-E

[event-server-name] The event database could not be switched.

The event database could not be switched.

(S)

Terminates the jevdbswitch command.

(O)

Check the message and that was output immediately before this message and the return value of the command.

KAJP1304-I

[event-server-name] The event database has completed switching.

The event database was switched successfully.

(S)

Terminates the jevdbswitch command.

KAJP1305-I

[event-server-name] The event database will now be switched.

This message appears when the jevdbswitch command is executed.

(S)

Continues command processing.

KAJP1306-I

[event-server-name] The event database is being switched...

The event database is being switched.

(S)

Continues command processing.

KAJP1307-W

[event-server-name] The event database was switched successfully, though an error occurred during the switch.

The event database was switched successfully even though an error occurred during switching.

(S)

Terminates the jevdbswitch command.

(O)

Investigate the contents of the error. If recovery is required, check the error message that was output immediately before this message, and then correct the cause of the error.

KAJP1308-E

[event-server-name] The system cannot determine whether the event database has been switched.

The system cannot determine whether the event database has been switched.

(S)

Terminates the jevdbswitch command.

(O)

If this message appears, check whether one of the following messages was output to the integrated trace log or to the event log (in Windows) or syslog (in UNIX) to confirm whether the event database was switched.

When the event database was switched:

The KAJP1061-I message is output.

When the event database was not switched:

The KAJP1062-E message is output.

KAJP1350-I

The status of the threshold-based suppression of event-forwarding for host-name will be checked.

The status of the threshold-based suppression of event-forwarding will be checked.

KAJP1351-I

The conditions for the suppression of event-forwarding are not defined.

Conditions for the suppression of event-forwarding (suppress blocks) are not defined in the forwarding settings file (forward).

KAJP1352-E

Another user is already running this command.

Another user is executing the command.

(S)

Terminates processing of the jevfwstat command.

(O)

Wait a while, and then re-execute the jevfwstat command.

KAJP1401-I

The forward file of host-name is being backed up.

The forwarding settings file (forward) of the host indicated by host-name is being backed up.

KAJP1402-E

A communication error occurred when acquiring the definition from host-name.

Communication failed while definition information was being acquired from the host indicated by host-name.

(S)

Terminates processing of the jevagtfw command.

(O)

Make sure that:

The version of JP1/Base on the host indicated by host-name is 08-00 or later.

JP1/Base on the host indicated by host-name is running.

There is no problem in the network with the host indicated by host-name.

KAJP1403-E

An error occurred when acquiring the definition from host-name.

An attempt to acquire definition information from the host indicated by host-name failed.

(S)

Terminates processing of the jevagtfw command.

(O)

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

KAJP1404-I

The forward file of host-name was backed up. (file = file-name)

Backup of the forwarding settings file (forward) of the host indicated by host-name is completed.

KAJP1405-I

The forward file for suppressing event-forwarding will be sent to host-name.

The forwarding settings file for suppressing event-forwarding (forward_suppress) will be sent to the host indicated by host-name.

KAJP1406-E

A communication error occurred when sending the definition to host-name.

Communication failed while the definition was being sent to the host indicated by host-name.

(S)

Terminates processing of the jevagtfw command.

(O)

Make sure that:

The version of JP1/Base on the host indicated by host-name is 08-00 or later.

JP1/Base on the host indicated by host-name is running.

There is no problem in the network with the host indicated by host-name.

KAJP1407-E

An error occurred when sending the definition to host-name.

An attempt to send the definition to the host indicated by host-name failed.

(S)

Terminates processing of the jevagtfw command.

If an attempt to apply the forwarding settings file for suppressing event-forwarding (forward_suppress) failed, the system restores the forwarding settings file (forward_backup) that was backed up during suppression.

(O)

To check the distribution definition file for errors, make sure that:

There are no spelling errors in the attribute names or comparison keywords that are set in the forwarding settings file (forward).

There are no extra spaces or tab characters after OR.

There are no comments written after the filter.

Double-byte spaces are not used as the delimiter.

If the problem is not solved, use the data collection tool to collect the required data, and then contact the system administrator.

KAJP1408-I

The forward file for suppressing event-forwarding was applied to host-name.

The forwarding settings file for suppressing event-forwarding (forward_suppress) was applied normally to the host indicated by host-name.

KAJP1410-I

Event-forwarding from host-name is now being suppressed.

Event-forwarding from the host indicated by host-name is suppressed.

KAJP1411-E

An attempt to suppress event-forwarding from host-name failed.

An attempt to suppress event-forwarding for the host indicated by host-name failed.

(S)

Terminates processing of the jevagtfw command.

(O)

Perform the operator's action provided in the message that was output immediately before this message.

KAJP1413-I

host-name is now suppressing event-forwarding from the following hosts:

A list of hosts that are suppressed from forwarding events will be displayed.

KAJP1414-I

The contents of the forward file of host-name will be checked.

The forwarding settings file (forward) for the host indicated by host-name will be checked. The contents of the file must match those of the forwarding settings file (forward_suppress) that was sent when event-forwarding was suppressed (by executing the jevagtfw command with the -s specified).

KAJP1415-E

The contents of the forward file for suppressing event-forwarding of host-name are different from those set at the time of suppression.

The contents of the forwarding settings file (forward) for the host (host-name) are different from the forwarding settings file (forward_suppress) that was sent when event-forwarding was suppressed (by executing the jevagtfw command with the -s option specified).

(S)

Terminates processing of the jevagtfw command.

(O)

Check why the system administrator of the agent host changed the forwarding settings file (forward). Then, use either of the following methods to stop the suppression of event-forwarding:

Forcibly stop the suppression of event-forwarding (execute the jevagtfw command with the -r and -f options specified).

If no problem occurs when the settings of the forwarding settings file (forward) are returned to the settings that existed before the suppression of event-forwarding, forcibly stop the suppression.

Stop the suppression of event-forwarding only for the manager (execute the jevagtfw command with the -r and -m options specified).

If you want to continuously use the forwarding settings file (forward) that was changed during suppression of event-forwarding, stop the suppression of event-forwarding only for the manager. The settings of the forwarding settings file (forward) for the agent are not returned to the settings that existed before the suppression of event-forwarding. In this case, compare the forward file with the forwarding settings file (forward_backup) that was backed up during suppression on the manager, and make sure that required definitions are not omitted.

KAJP1416-I

An applicable forward file for suppressing event-forwarding is specified for host-name.

The contents of the forwarding settings file (forward) for the host (host-name) are the same as the forwarding settings file (forward_suppress) that was sent when event-forwarding was suppressed (by executing the jevagtfw command with the -s option specified).

KAJP1417-I

The backed-up forward file will be sent to host-name.

The forwarding settings file (forward_backup) that was backed up during suppression of event-forwarding will be sent to the host indicated by host-name.

KAJP1418-I

The backed-up forward file was applied to host-name.

The forwarding settings file (forward_backup) that was backed up during suppression of event-forwarding was normally sent (applied) to the host indicated by host-name.

KAJP1419-I

Event-forwarding from host-name will be suppressed.

Event-forwarding from the host indicated by host-name will be suppressed.

KAJP1420-I

The suppression of event-forwarding from host-name will be stopped.

The suppression of event-forwarding from the host indicated by host-name will be stopped.

KAJP1421-I

The suppression of event-forwarding from host-name was stopped.

The suppression of event-forwarding from the host indicated by host-name was stopped.

KAJP1422-I

The events received from host-name will be discarded.

The events received from the host indicated by host-name will be discarded.

KAJP1423-E

An attempt to discard the events received from host-name failed.

An attempt to discard the events received from the host indicated by host-name failed.

(S)

Terminates processing of the jevagtfw command.

(O)

Perform the operator's action provided in the message that was output immediately before this message.

KAJP1424-I

Discarding of events received from host-name was stopped.

Discarding of events received from the host indicated by host-name was stopped.

KAJP1425-E

An attempt to stop the discarding of events received from host-name failed.

An attempt to stop the discarding of events received from the host indicated by host-name failed.

(S)

Terminates processing of the jevagtfw command.

(O)

Perform the operator's action provided in the message that was output immediately before this message.

KAJP1426-I

Event-forwarding from host-name is not being suppressed.

Stopping of the suppression of event-forwarding is skipped for the host (indicated by host-name) for which event-forwarding is not suppressed.

KAJP1427-I

Discarding of events received from host-name will be stopped.

Discarding of events received from the host indicated by host-name will be stopped.

KAJP1428-I

The events received from host-name are not being discarded.

Stopping of the discarding of received events is skipped for the host (indicated by host-name) for which no events are discarded.

KAJP1429-I

The events received from host-name are already being discarded.

Discarding of received events is skipped for the host (indicated by host-name) for which received events are already discarded.

KAJP1430-I

The events received from host-name are now being discarded.

The events received from the host indicated by host-name are now being discarded.

KAJP1431-I

Event-forwarding from host-name is already being suppressed.

Suppression of event-forwarding is skipped for the host (indicated by host-name) for which event-forwarding has already been suppressed.

KAJP1432-E

An attempt to stop the suppression of event-forwarding from host-name failed.

An attempt to stop the suppression of event-forwarding failed for the host indicated by host-name.

(S)

Terminates processing of the jevagtfw command.

(O)

Perform the operator's action provided in the message that was output immediately before this message.

KAJP1433-I

Event-forwarding is not being suppressed.

Suppression of event-forwarding is not set up for this host.

KAJP1434-E

Failed to restore the file forward to host-name. (file = file-name)

An attempt to apply (restore) the backed up forwarding settings file (forward_backup) to the host indicated by host-name failed.

(S)

Terminates processing of the jevagtfw command.

(O)

Manually set the contents of the file indicated by file-name in the forwarding settings file (forward) for the host indicated by host-name.

KAJP1435-E

The local host (host-name) cannot be set up to suppress event-forwarding.

Suppression of event-forwarding cannot be set up for the local host.

(S)

Terminates processing of the jevagtfw command.

(O)

Make sure that the specified host name is not the local host, and then re-execute the jevagtfw command. To set up suppression of event-forwarding for the local host, re-execute the jevagtfw command with the -n option specified.

KAJP1701-E

The specified option contains an error.

An option specified at command execution contains an error.

(S)

Terminates command processing.

(O)

Make sure that the name of an event server that is running on another host is not specified for the -s option of the jevsend or jevsendd command. If it is specified, change it to the name of an event server running on the local host.

KAJP1702-E

At least one extra option exists.

Too many options are specified.

(S)

Terminates command processing.

(O)

Re-execute the command with the correct number of options.

KAJP1703-E

The same option is specified more than once.

An option that can be specified only once was specified repeatedly.

(S)

Terminates command processing.

(O)

Re-execute the command with the correct number of options.

KAJP1704-E

Memory is insufficient.

There is not enough memory to execute the command.

(S)

Terminates command processing.

(O)

Terminate other processes that may be using memory, and then re-execute the command.

KAJP1705-E

A system error occurred. (code = detail-code)

Command execution was halted due to a system error.

(S)

Terminates command processing.

(O)

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

KAJP1706-E

A connection to the event server cannot be established.

The command was executed while the event server was inactive.

(S)

Terminates command processing.

(O)

Re-execute the command after you have made sure that:

The event service is running. (You can check this by using the jevstat command.)

The service name specified for the ports parameter as an application port in the event server settings file (conf) is set in the services file.

Communication is possible between the address specified for the ports parameter in the event server settings file (conf) and the addresses specified for the server and client parameters in the API settings file.

When JP1/Base is operating with the ANY binding method on a host that uses IPv6 addresses, the IPv6 address of the local host is set in the jp1hosts2 information.

KAJP1707-E

The user lacks permission to execute this command.

Execution of this command requires operator privileges. In Windows, the user who executes this command must be a member of the Administrators group. In UNIX, the user who executes this command must have root privileges or JP1/Base administrator privileges.

(S)

Terminates command processing.

(O)

Re-execute the command as a user who has operator privileges.

KAJP1708-E

A message cannot be read.

The message string to be displayed or output to a log cannot be read.

(S)

Terminates command processing.

(O)

Make sure that the following file exists and that you have read permission for it:

Windows: Message DLL file

installation-folder\jp1base\bin\jevmessage.dll

UNIX: Message catalog file

/opt/jp1base/lib/nls/C/msg.cat

If the fie does not exist or if you do not have the appropriate read permission, re-install JP1/Base.

KAJP1709-E

The specified event server name is not defined. (server = server-name)

An event server name that does not exist was specified in the command option or in the JP1_HOSTNAME environment variable.

(S)

Terminates command processing.

(O)

Check whether the event server name specified in the command option or in the JP1_HOSTNAME environment variable is correct.

KAJP1710-E

A file I/O error occurred.

An error occurred during reading or writing to a file.

(S)

Terminates command processing.

(O)

The causes of the error are:

The disk has insufficient free space.

System resources required for using the file are insufficient.

Check and, if necessary, revise the disk size and kernel parameters.

KAJP1711-E

A required option is not specified.

A required option is not specified.

(S)

Terminates command processing.

(O)

Correct the error and then re-execute the command.

KAJP1712-E

Execute the command from the administrator console.

This command must be executed on the administrator console.

(S)

Terminates command processing.

(O)

Re-execute the command on the administrator console.

KAJP1731-E

The event ID is specified incorrectly.

The event ID is specified incorrectly.

(S)

Terminates command processing.

(O)

Correct the event ID, and then re-execute the command.

KAJP1732-E

The name of the extended attribute is specified incorrectly.

The name of the extended attribute is specified incorrectly.

(S)

Terminates command processing.

(O)

Correct the extended attribute name, and then re-execute the command.

KAJP1733-E

The total length of the extended attributes exceeds the maximum.

The total length of the specified extended attributes exceeds 10,000 bytes.

(S)

Terminates command processing.

(O)

Specify no more than 10,000 bytes in extended attribute values, and then re-execute the command.

KAJP1734-E

The number of specified extended attributes exceeds the maximum.

The number of specified extended attributes exceeds 100.

(S)

Terminates command processing.

(O)

Specify no more than 100 extended attributes, and then re-execute the command.

KAJP1735-E

The message is specified incorrectly.

The message is specified incorrectly.

(S)

Terminates command processing.

(O)

Correct the message, and then re-execute the command.

KAJP1736-E

The event service is installed incorrectly.

The event service is installed incorrectly.

(S)

Terminates command processing.

(O)

Re-install JP1/Base, and then re-execute the command.

KAJP1737-E

A connection to the event service cannot be established.

A command was executed before the event service started.

(S)

Terminates command processing.

(O)

Re-execute the command after you have made sure that:

The event service is active. (This can be checked by using the jevstat command.)

The service name specified for the ports parameter as an application port in the event server settings file (conf) is set in the services file.

Communication is possible between the address specified for the ports parameter in the event server settings file (conf) and the addresses specified for the server and client parameters in the API settings file.

When JP1/Base is operating with the ANY binding method on a host that uses IPv6 addresses, the IPv6 address of the local host is set in the jp1hosts2 information.

KAJP1738-E

The specified name of the send-source event server is incorrect.

The specified name of the send-source event server is incorrect.

(S)

Terminates command processing.

(O)

Correct the error, and then re-execute the command.

KAJP1739-E

The specified name of the send-destination event server is incorrect.

The specified name of the send-destination event server is incorrect.

(S)

Terminates command processing.

(O)

Correct the error, and then re-execute the command.

KAJP1740-E

An I/O error occurred.

An unrecoverable I/O error occurred during command processing.

(S)

Terminates command processing.

(O)

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

KAJP1741-W

The event did not reach the send-destination event server.

The event did not reach the event server at the send destination.

(S)

Continues command processing.

KAJP1742-I

The event reached the send-destination event server.

The event reached the event server at the send destination.

(S)

Terminates command processing.

KAJP1743-E

Arrival of an event at the send-destination event server could not be confirmed.

Arrival of an event at the event server at the send destination could not be confirmed.

(S)

Terminates command processing.

(O)

Check the status of the event server at the send destination, and then retry transmission.

KAJP1744-E

A message cannot be read. (maintenance-information)

A message string for display or logging cannot be read.

(S)

Terminates command processing.

(O)

Make sure that the following file exists, and that you have appropriate permissions for it:

In Windows: Message DLL file (jevmessage.dll)

In UNIX: Message catalog file (msg.cat)

KAJP1745-E

An error occurred when an event was sent. (maintenance-information)

An error occurred when an event was sent.

(S)

Terminates command processing.

(O)

Check the status of the event server, and then retry transmission. Also contact the system administrator.

KAJP1751-E

The event database file is not specified.

An event database file, which should be specified in a mandatory parameter, was not specified.

(S)

Terminates command processing.

(O)

Specify the event database file, and then re-execute the command.

KAJP1752-E

An I/O error occurred. (file = file-name)

An I/O error occurred in file-name.

(S)

Terminates command processing.

(O)

If the output file name is specified for the option, make sure that:

The file name specified for the -i or -f option exists and the path is correct.

If the specified file does not exist, specify an existing file and then re-execute the jevexport command.

The path specified for the -o option exists and the path is not read-only.

If the specified path does not exist, specify an existing path and then re-execute the jevexport command. If the specified path is read-only, permit writing to the path or change the path to a writable path, and then execute the jevexport command.

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

KAJP1753-E

A file could not be opened. (file = file-name)

The file cannot be opened since the user does not have the required access permission for the specified file, or for some other reason.

(S)

Terminates command processing.

(O)

Correct the error, and then re-execute the jevexport command.

KAJP1754-E

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

The specified file was not found.

(S)

Terminates command processing.

(O)

Specify the correct file name, and then re-execute the jevexport command.

KAJP1755-E

The specified file is not an event database.

The specified file is not an event database, or is invalid as an event database.

(S)

Terminates command processing.

(O)

Specify the correct event database, and then execute the jevexport command.

KAJP1756-E

The event database file is corrupted.

The event database file is corrupted.

(S)

Terminates command processing.

(O)

Restart the event service, and then re-execute the jevexport command.

KAJP1757-E

The same file is specified more than once.

The same file is specified in different arguments.

(S)

Terminates command processing.

(O)

The same file name cannot be specified more than once. Change the file name, and then re-execute the jevexport command.

KAJP1758-E

A filter statement contains a syntax error. (line = line-number)

The filter syntax in the filter file is incorrect.

(S)

Terminates command processing.

(O)

There is an error in the filter on the output line number. Make sure that:

There are no spelling errors in the specified attribute names or comparison keywords.

There are no comments written after the filter.

Double-byte spaces are not used as the delimiter.

Filter files created in Windows are not transferred using FTP in binary mode.

Correct the error in the filter on the output line number, and then re-execute the jevexport command.

Correct the error in the definitions of the forwarding settings file (forward), and then execute the jevreload command.

KAJP1759-E

There is an error in the specified index file. (line num. = line-number)

The contents of the index file are incorrect.

(S)

Terminates command processing.

(O)

There is an error in the item name on the output line number. Make sure that:

Only single-byte alphanumeric characters (alphabetic characters must be upper case) are used for the item name.

Filter files created in Windows are not transferred using FTP in binary mode.

Correct the error in the item on the output line number, and then re-execute the jevexport command.

KAJP1760-W

The event database file is empty. (file = file-name)

The event database file is empty.

(S)

Terminates command processing.

KAJP1761-E

The specified event server name is not defined. (server = event-server-name)

The specified event server name is not defined.

(S)

Terminates command processing.

(O)

Specify the defined event server name, and then re-execute the jevexport command.

KAJP1762-E

A message cannot be read. (maintenance-information)

A message string for display or logging cannot be read.

(S)

Terminates command processing.

(O)

Make sure that the following file exists and that you have read permission for it:

In Windows: Message DLL file (jevmessage.dll)

In UNIX: Message catalog file (msg.cat)

KAJP1763-E

Event data cannot be exported. (maintenance-information)

Event data cannot be exported.

(S)

Terminates command processing.

(O)

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

KAJP1764-E

Output to the CSV file was interrupted during export processing.

Processing has been suspended because the event database file was switched during export processing.

(S)

Terminates command processing.

(O)

Re-execute the jevexport command.

KAJP1765-W

number-of-bytes corrupted bytes were detected.

Corrupted data was detected in the event database while the jevexport command was outputting data to a CSV file.

(S)

Continues command processing.

(O)

The performance of JP1 event searches may deteriorate. Switch or initialize the event database.

If you specified a backed up event database for the -i option, no action is required.

KAJP1771-I

Processing to report the status of the event service event-service-name will now start.

Processing to report the status of the event service will now start.

(S)

Continues command processing.

KAJP1772-I

All the processes are running.

All the event service processes are running.

(S)

Terminates command processing.

KAJP1773-I

Some of the processes are running.

Some of the event service processes are running.

(S)

Terminates command processing.

KAJP1774-I

None of the processes are running.

None of the event service processes are running.

(S)

Terminates command processing.

KAJP1775-E

An attempt to send or receive communication data has failed. (maintenance-information)

An attempt to send communication data to, or receive communication data from, the event service has failed.

(S)

Terminates command processing.

(O)

Make sure that the event service is not starting or stopping now, and then re-execute the command.

KAJP1776-E

An attempt to process communication data has failed. (maintenance-information)

An attempt to process communication data has failed.

(S)

Terminates command processing.

(O)

Make sure that the event service is not starting or stopping now, and then re-execute the command.

KAJP1777-E

An attempt to obtain the event service status has failed. (maintenance-information)

An attempt to obtain the event service status has failed.

(S)

Terminates command processing.

(O)

Make sure that the event service is not starting or stopping now, and then re-execute the command.

KAJP1780-E

A message cannot be read. (maintenance-information)

A message string for display or logging cannot be read.

(S)

Terminates command processing.

(O)

Make sure that the following file exists and that you have read permission for it:

In Windows: Message DLL file (jevmessage.dll)

In UNIX: Message catalog file (msg.cat)

KAJP1781-E

The repetition prevention table file cannot be created because an event service is running.

The repetition prevention table file cannot be created because an event service is running.

(S)

Terminates command processing.

(O)

Stop the event service and then re-execute the command. If this message is output even though the event service has stopped, make sure that another user are not executing the jevdbmkrep or jevdbinit command.

KAJP1782-I

The repetition prevention table file will now be created.

The repetition prevention table file will now be created.

KAJP1783-I

The repetition prevention table file is now being created...

The repetition prevention table file is now being created.

KAJP1784-E

The repetition prevention table file cannot be created because the event database is in an invalid state.

The repetition prevention table file cannot be created because the event database is in an invaild state.

(S)

Terminates command processing.

(O)

Execute the jevdbinit command to initialize the event database.

KAJP1786-I

[event-server-name]The event database will now be initialized.

Initialization of the event database will now start.

KAJP1787-I

[event-server-name]Initialization of the event database completed.

Initialization of the event database terminated.

KAJP1788-I

[event-server-name]The initial sequence number in the event database is serial-number.

An event database beginning with the indicated serial number will now be created.

(S)

Continues processing.

KAJP1789-E

[event-server-name]Initialization of the event database failed because the serial number for the event database cannot be taken over.

An attempt to initialize the event database has failed because the serial number in the event database could not be taken over.

(S)

Terminates command processing.

(O)

If this event server has forwarded JP1 events, use JP1/IM - View or a CSV file output by the jevexport command to check the JP1 events that arrived at the destination event service. Then, acquire the most recent serial number of these JP1 events in the event database.

Then, specify this most recent serial number plus 1 for the -s option, and re-execute the jevdbinit command.

If this event server has not forwarded a JP1 event, specify 0 for the -s option and then re-execute the jevdbinit command.

KAJP1790-E

[event-server-name]The event database cannot be initialized because the event service is active.

The event database cannot be initialized because the event service is active.

(S)

Terminates command processing.

(O)

If the event service is active, stop it and then re-execute the jevdbinit command.

If this message appears when the event service is inactive, the jevdbinit command is probably being executed. Check whether the jevdbinit command is being executed.

To initialize the event database when the event service is active, execute the jevdbswitch command twice to switch the event database twice.

KAJP1791-I

[event-server-name]The event database is being initialized...

The event database is being initialized.

KAJP1792-I

[event-server-name]The event database prior to initialization will be backed up.

The event database prior to initialization will be backed up.

KAJP1793-I

[event-server-name]The event database prior to initialization will not be backed up.

The event database prior to initialization will not be backed up.

KAJP1794-E

[event-server-name]The event database cannot be initialized because another process has opened it.

An attempt to initialize the event database has failed because another process was accessing the event database.

(S)

Terminates command processing.

(O)

In the environment where the error occurred, the command may have been executed while you were:

Executing the jevexport command.

Opening the event database by using a text editor.

Backing up the event database by using the backup software.

Checking the files in the event database by using the virus check software.

Wait until the event database is not being accessed from anywhere, and then re-execute the command.

KAJP1795-E

[event-server-name]The event database will be restored to the state before command execution.

The event database will be restored to the state in effect before the command was executed because an error occurred during initialization of the event database.

(S)

Terminates command processing.

(O)

Initialization of the event database was interrupted due to a file I/O error. Restore the event database to the state in effect before the command was executed because the command processing cannot be completed.

KAJP1796-E

[event-server-name]The restore processing failed to rename the event database file. (target = database-name-to-be-renamed, after rename = database-name-after-rename)

An attempt to rename the event database has failed.

(S)

Continues command processing.

(O)

The event database to be renamed still remains under the directory that contains the event database to be initialized.

Wait until the command terminates, and then rename the event database manually. If an event database with the name indicated in database-name-after-rename already exists, delete that database, and then rename the event database.

KAJP1797-E

[event-server-name]An attempt to delete the event database file has failed. (target = database-name-to-be-deleted)

An attempt to delete the event database has failed.

(S)

Continues command processing.

(O)

The event database to be deleted still remains under the directory that contains the event database to be initialized.

Wait until the command terminates, and then delete the event database manually.

KAJP1798-E

[event-server-name]An attempt to restore the event database to the state before command execution has failed.

An attempt to restore the event database to the state in effect before the command was executed has failed.

(S)

Continues command processing.

(O)

Restoration of the event database was interrupted due to a file I/O error.

Restore the event database to the state in effect before the initialization command was executed, according to the operator's action provided in the KAJP1796-E or KAJP1797-E message that was output to standard output or to the integrated trace log.

If more than one KAJP1796-E or KAJP1797-E messages were output, take action for each message. After you take action for all the messages, re-execute the command.

KAJP1799-E

[event-server-name]Initialization of the event database ended with an incomplete status.

Initialization of the event database terminated with an incomplete status.

(S)

Continues command processing.

(O)

Initialization of the event database was interrupted due to a file I/O error.

Bring the event database to the status it should be in when the initialization command finishes, according to the operator's action provided in the KAJP1796-E or KAJP1797-E message that was output to standard output or to the integrated trace log. If more than one KAJP1796-E or KAJP1797-E messages were output, take action for each message. This completes initialization of the event database.

KAJP1800-I

[event-server-name]The event database was restored to the state before command execution.

The event database was restored to the state in effect before the command was executed.

KAJP1801-I (Windows)

The SES emulator will now start.

The JP1/AJS compatibility function (the part pertaining to the event service) will now start.

KAJP1801-I (UNIX)

The event management server will now start.

The JP1/SES compatibility function will now start.

KAJP1802-I (Windows)

The SES emulator will now stop.

The JP1/AJS compatibility function (the part pertaining to the event service) will now stop.

KAJP1802-I (UNIX)

The event management server will now stop.

The JP1/SES compatibility function will now stop.

KAJP1803-E (Windows)

The SES emulator cannot start because an event stack area could not be allocated.

The JP1/AJS compatibility function (the part pertaining to the event service) cannot start because an event stack area could not be allocated.

(S)

Stops the event server.

(O)

Take either of the following actions as required, and then restart the event server:

Reduce the buffnum value in the event server settings file.

If you specified include ajs-conf to include the JP1/AJS environment definitions, reduce the maximum event count in the JP1/AJS system environment settings.

KAJP1803-E (UNIX)

The event management server is already running.

The JP1/SES compatibility function is already running.

(S)

Terminates command processing.

KAJP1804-E

An error occurred during the opening of the environment definition file.

An error occurred during the opening of the environment definition file for the JP1/SES compatibility function.

(S)

Terminates command processing.

(O)

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

KAJP1805-E (Windows)

Memory is insufficient for the SES emulator.

There is not enough memory for the JP1/AJS compatibility function (the part pertaining to the event service).

(S)

Stops the event server.

(O)

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

KAJP1805-E (UNIX)

The event management server cannot start because an event stack area could not be allocated

The event server cannot start because an event stack area could not be allocated for the JP1/SES compatibility function.

(S)

Terminates command processing.

(O)

Take either of the following actions as required, and then restart the event server:

Reduce the buffnum value in the event server settings file.

If you specified include ses-conf to include the JP1/SES environment definitions, reduce the value of the BUFFNUM parameter in the JP1/SES environment definition file.

KAJP1806-E (Windows)

An I/O error occurred in the SES emulator.

An I/O error occurred at the JP1/AJS compatibility function (the part pertaining to the event service).

(S)

Stops the event server.

(O)

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

KAJP1806-E (UNIX)

Event management server has already stopped.

The JP1/SES compatibility function has already stopped.

(S)

Terminates command processing.

KAJP1807-E

The SES emulator stopped due to an error that prevents processing.

An unrecoverable error occurred during processing by the JP1/AJS compatibility function (the part pertaining to the event service).

(S)

Stops the event server.

(O)

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

KAJP1808-W

An event that could not be reported occurred at the SES emulator.

Event information could not be reported to the pseudo operator because the event stack area for the JP1/AJS compatibility function (the part pertaining to the event service) is full.

(S)

Continues processing.

(O)

Take either of the following actions as required, and then restart the event server:

Increase the buffnum value in the event server settings file.

If you specified include ajs-conf to include the JP1/AJS environment definitions, increase the maximum event count in the JP1/AJS system environment settings.

KAJP1810-E

The port ID for the SES emulator is not defined in \systemroot\SYSTEM32\DRIVERS\ETC\SERVICES.

No port number is specified for event transfer with a remote host using the JP1/AJS compatibility function (the part pertaining to the event service).

(S)

Cannot send or receive events under a JP1/SES-compatible protocol.

(O)

Add the JP1AutoJob service to \systemroot\SYSTEM32\DRIVERS\ETC\SERVICES, and then restart the event server.

KAJP1811-E

The number of pseudo operators that can exist at one time exceeds the maximum number at the SES emulator.

A pseudo operator cannot start because the number of pseudo operators exceeds the maximum that can exist at one time for the JP1/AJS compatibility function (the part pertaining to the event service).

(S)

Cancels pseudo operator startup.

(O)

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

KAJP1812-W

The user (user-name) lacks start permission for a pseudo operator of SES emulator.

A request to start a pseudo operator was received from a user (user-name) who is not authorized to start a pseudo operator for the JP1/AJS compatibility function (the part pertaining to the event service).

(S)

Cancels pseudo operator startup.

(O)

Re-execute the command from the account of an authorized user. A user authorized to start a pseudo operator means a user who is set in the users parameter in the event server settings file (conf).

KAJP1813-E

The SES emulator cannot start due to a corrupted environment definition file.

The JP1/AJS compatibility function (the part pertaining to the event service) cannot start because the environment definition file used by the function is corrupted.

(S)

Stops the event server.

(O)

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

KAJP1814-E

The user (user-name) who started the SES emulator lacks start permission for the pseudo operator.

The user who started the event server is not authorized to start a pseudo operator at the JP1/AJS compatibility function (the part pertaining to the event service).

(S)

Stops the event server.

(O)

Restart the event server under the system account.

KAJP1815-E

An error occurred during access to the event log file of SES Emulator.

An access error occurred at the event log file for the JP1/AJS compatibility function (the part pertaining to the event service).

(S)

Cancels event log-file access.

(O)

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

KAJP1816-W

SES emulator will reuse the port ID.

A port number used for event transfer with a remote host is already being used, but the JP1/AJS compatibility function (the part pertaining to the event service) reused the port number.

KAJP1817-E

An attempt to perform a bind for the SES emulator has failed. (detail-code)

An error occurred during bind() processing for an event transfer with a remote host being carried out by the JP1/AJS compatibility function (the part pertaining to the event service).

(S)

Stops processing.

(O)

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

KAJP1819-E

A error occurred during communication processing at the SES emulator. (maintenance-information)

An error occurred during communication processing for an event transfer with a remote host being carried out by the JP1/AJS compatibility function (the part pertaining to the event service).

(S)

Stops processing.

(O)

Make sure that the network connection is correct.

KAJP1820-E

Memory is insufficient.

There is not enough memory.

(S)

Stops the event server.

(O)

Terminate other processes that are using memory, and then re-execute the command.

KAJP1826-E

An I/O error occurred.

An error occurred in file I/O or in some other processing by the JP1/SES compatibility function.

(S)

Terminates the process in which the error occurred.

(O)

Make sure that the number of messages queued in the message queue has not reached the system limit. If the number of queued messages has reached the system limit, check and, if necessary, revise the kernel parameters so that the number of messages used by JP1/Base can be allocated.

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

KAJP1830-E

The environment definition file contains an invalid specification.

The environment definition file for the JP1/SES compatibility function contains an invalid specification.

(S)

Terminates command processing.

(O)

If there is an error in the event server settings file, or in the JP1/SES environment definitions included by specifying include ses-conf, correct the setting error, and then re-execute the command.

KAJP1840-E

The event management server stopped due to an error that prevents processing.

The event server stopped due to an unrecoverable error at the JP1/SES compatibility function.

(S)

Stops the event server.

(O)

Check the timing at which logs are output. If the OS has been shut down, the OS might have forcibly stopped the system. In this case, no special action is required.

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

KAJP1841-W

An event could not be reported. (process ID = process-ID)

Event information could not be reported to the pseudo operator because the event stack area for the JP1/SES compatibility function is full.

(S)

Continues processing.

(O)

Check the process indicated by process-ID, and then take either of the following actions as required, and restart the event server:

Increase the buffnum value in the event server settings file.

If you specified include ses-conf to include the JP1/SES environment definitions, increase the value of the BUFFNUM parameter in the JP1/SES environment definition file.

KAJP1852-E

A system error occurred. (maintenance information)

A system error occurred during processing by the JP1/SES compatibility function.

(S)

Stops the event server.

(O)

Make sure that:

Timing at which logs are output

If the OS has been shut down, the OS might have forcibly stopped the system. In this case, no particular action is required.

The files under /usr/tmp/jp1_ses have not been deleted.

If the settings are specified so that the files under /tmp are automatically deleted by tools, make sure that the files under /usr/tmp/jp1_ses have not been deleted mistakenly. If the files were deleted, change the settings so that the files under /usr/tmp/jp1_ses are not deleted.

The number of messages queued in the message queue has not reached the system limit.

If the number of queued messages has reached the system limit, check and, if necessary, revise the kernel parameters so that the number of messages used by JP1/Base can be allocated.

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

KAJP1860-I

The JP1/SES remote management server will now start.

JP1/SES remote management server will now start.

(S)

Continues processing.

KAJP1861-I

The JP1/SES remote management server will now stop.

The JP1/SES remote management server will now stop.

(S)

Continues processing.

KAJP1863-E

JP1/SES remote management server has already stopped.

The remote manager for the JP1/SES compatibility function has already stopped.

(S)

Terminates command processing.

KAJP1864-E

The JP1/SES remote management server stopped due to error that prevents processing.

The JP1/SES compatibility function (the part pertaining to the event service) stopped due to a system error.

(S)

Cannot forward events to a remote host under a JP1/SES-compatible protocol.

(O)

Check the timing at which logs are output. If the OS has been shut down, the OS might have forcibly stopped the system. In this case, no special action is required.

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

KAJP1869-E

The JP1/SES remote management server will stop because the event management server stopped.

The JP1/SES compatibility function stopped.

(S)

Stops the event server.

(O)

Check the timing at which logs are output. If the OS has been shut down, the OS might have forcibly stopped the system. In this case, no special action is required.

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

KAJP1870-E

An error occurred while an event was being sent to another host. (host = host-name)

Event transfer under a JP1/SES-compatible protocol failed because of a line error or some other cause.

The event server to which events have been sent using a JP1/SES-compatible protocol went down.

The line was released due to a line failure.

(S)

Stops forwarding events to the host where the error occurred until event transfer under a JP1/SES-compatible protocol is again enabled (that is, until message KAJP1871-I is output).

(O)

Check the status of the host at which the error occurred.

KAJP1871-I

Events can now be sent to another host. (host = host-name)

Events can now be forwarded to the indicated host under a JP1/SES-compatible protocol.

2.2 User management messages (KAVA0200 to KAVA1694)

KAVA0200-E (Windows)

Administrator privileges are required to execute the command.

To execute the command, you must be logged on as a user who has Administrators permissions.

(S)

Terminates processing of the jbsgetcnf command.

(O)

Only a user who logged on as a user who has Administrators permissions can execute the jbsgetcnf command. Execute the command as a user who has Administrators permissions.

KAVA0200-E (UNIX)

Root privileges are required to execute the command.

Execute the command as a user who has root privileges.

(S)

Terminates processing of the jbsgetcnf command.

(O)

Only a user who has root privileges can execute the jbsgetcnf command. Execute the command as a user who has root privileges.

KAVA0201-E

The argument is invalid. You must specify a component name.

The argument is invalid. You must specify a component name.

(S)

Terminates processing of the jbsgetcnf command.

(O)

The jbsgetcnf command was started with a subkey (-n) specified by an argument without specifying a component name (-c). Check that the component name key is specified.

KAVA0202-E

The argument is invalid. The specified information name (key-name) does not exist.

The argument is invalid. The specified information name key-name does not exist.

(S)

Terminates processing of the jbsgetcnf command.

(O)

The specified information name does not exist in the common definition information. Make sure that the specified name is correct.

KAVA0203-E

/opt/jp1/hcclibcnf cannot be accessed. Check whether /opt/jp1/hcclibcnf is available.

The files under the /opt/jp1/hcclibcnf/ directory cannot be read.

(S)

Terminates processing of the jbsgetcnf command.

(O)

The files under the /opt/jp1/hcclibcnf/ directory, used to reference the common definition information, cannot be read. Make sure that the directories and files exist, and the access permissions are correct.

KAVA0204-E

A jbsgetcnf option is invalid.

A command option is incorrect.

(S)

Terminates command processing.

(O)

Specify the correct option, and then re-execute the command.

KAVA0206-E

Memory is insufficient.

An attempt to perform a new OutStream has failed.

There is not enough memory.

(S)

Terminates processing of the jbsgetcnf command.

(O)

Stop unnecessary processes, and then re-execute the command. The first line of this message is output to the standard error, and the second line is output to the trace log.

KAVA0207-E

Memory is insufficient.

An attempt to perform a new LineMergeOutStream has failed.

There is not enough memory.

(S)

Terminates processing of the jbsgetcnf command.

(O)

Stop unnecessary processes, and then re-execute the command. The first line of this message is output to the standard error, and the second line is output to the trace log.

KAVA0208-E

An unexpected error occurred.

character-string

An unexpected error occurred.

(S)

Terminates processing of the jbsgetcnf command.

(O)

Use the data collection tool to collect data, record the arguments specified in the command, and then contact the system administrator. The first line of this message is output to the standard error output and the second line is output to the trace log.

KAVA0212-E

An unexpected error occurred.

character-string

An unexpected error occurred.

(S)

Terminates processing of the jbsgetcnf command.

(O)

Use the data collection tool to collect data, record the arguments specified in the command, and then contact the system administrator. The first line of this message is output to the standard error output and the second line is output to the trace log.

KAVA0215-E

Memory is insufficient.

malloc(256+1) has failed.

There is not enough memory.

(S)

Terminates processing of the jbsgetcnf command.

(O)

Stop unnecessary processes, and then re-execute the command. The first line of this message is output to the standard error, and the second line is output to the trace log.

KAVA0216-E

Memory is insufficient.

malloc (value) has failed.

There is not enough memory.

(S)

Terminates processing of the jbsgetcnf command.

(O)

Stop unnecessary processes, and then re-execute the command. The first line of this message is output to the standard error, and the second line is output to the trace log.

KAVA0217-E

An unexpected error occurred.

character-string

An unexpected error occurred.

(S)

Terminates processing of the jbsgetcnf command.

(O)

Use the data collection tool to collect data, record the arguments specified in the command, and then contact the system administrator. The first line of this message is output to the standard error output and the second line is output to the trace log.

KAVA0218-E

An unexpected error occurred.

character-string

An unexpected error occurred.

(S)

Terminates processing of the jbsgetcnf command.

(O)

Use the data collection tool to collect data, record the arguments specified in the command, and then contact the system administrator. The first line of this message is output to the standard error output and the second line is output to the trace log.

KAVA0219-E

The value (character-string) is not REG_SZ nor REG_DWORD. The value is skipped.

(S)

Processing of the jbsgetcnf command continues.

(O)

The common definition information contains a type of information that cannot be referenced. Use the data collection tool to collect data, record the arguments specified in the command, and then contact the system administrator.

KAVA0220-E

maintenance-information

character-string indicates the contents of the exception that occurred.

(S)

Terminates processing of the jbsgetcnf command.

(O)

Re-execute the jbsgetcnf command. If the same error still occurs, use the data collection tool to collect data, record the arguments specified in the command, and then contact the system administrator.

KAVA0300-E

There are too many arguments

There are too many arguments.

(S)

Terminates processing of the jbssetcnf command.

(O)

There are too many arguments. Check the content of the specified arguments.

KAVA0301-E

Memory is insufficient.

There is not enough memory.

(S)

Terminates processing of the jbssetcnf command.

(O)

Stop unnecessary processes, and then re-execute the command.

KAVA0302-E

The file (file-name) does not exist.

The specified file does not exist.

(S)

Terminates processing of the jbssetcnf command.

(O)

The file specified by the argument cannot be accessed. Make sure that all files and directories included in the path to the file exist, and that you have appropriate access privileges.

KAVA0303-E

The path does not specify a file. (file-name)

The path specified by an argument is not a file.

(S)

Terminates processing of the jbssetcnf command.

(O)

The path specified by an argument is not a file. Check the content of the argument specification.

KAVA0306-E

Memory is insufficient.

An attempt to perform a new IoInStrm has failed.

There is not enough memory.

(S)

Terminates processing of the jbssetcnf command.

(O)

Stop unnecessary processes, and then re-execute the command. The first line of this message is output to the standard error, and the second line is output to the trace log.

KAVA0307-E

Memory is insufficient.

An attempt to perform a new IoLineBreakInBtStrStream has failed.

There is not enough memory.

(S)

Terminates processing of the jbssetcnf command.

(O)

Stop unnecessary processes, and then re-execute the command. The first line of this message is output to the standard error, and the second line is output to the trace log.

KAVA0308-E

File format error. Line No. = value

(error-occurrence-line)

No key is selected before the value.

FORMAT ERR - A value record appears before a key record.

A syntax error was found in a value line of the definition information file.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The definition information file must begin with the key setting. Check the contents of the definition information file to make sure that the key information is set. The third line of this message is output to the standard error, and the fourth line is output to the integrated trace log.

KAVA0312-E

The file has a syntax error. (line num. = value)

error-occurrence-line

A key record did not end with ']'.

A syntax error was found in a value line of the definition information file.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The key information must be enclosed by square brackets ([]), but a right square bracket (]) is missing. Check the content of the definition information file.

KAVA0313-E

The file has a syntax error. (line num. = value)

error-occurrence-line

A key record did not end with ']'.

A syntax error was found in a value line of the definition information file.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The key information must be enclosed by square brackets ([]), but a right square bracket (]) is missing. Check the content of the definition information file.

KAVA0314-E

The file has a syntax error. (line num. = value)

error-occurrence-line

A key record has a syntax error. The key is too long. (max. = 230)

A syntax error was found in a value line of the definition information file.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The key length is too long. Check the content of the definition information file.

KAVA0315-E

The file has a syntax error. (line num. = value)

error-occurrence-line

There is no logical hostname key.

A syntax error was found in a value line of the definition information file.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The logical host name key cannot be fetched from the key information.

KAVA0316-E

The file has a syntax error. (line num. = value)

error-occurrence-line

A component key was not found.

A syntax error was found in a value line of the definition information file.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The component name key cannot be fetched from the key information. Check the content of the definition information file.

KAVA0317-E

The file has a syntax error. (line num. = value)

error-occurrence-line

A subkey was not found.

A syntax error was found in a value line of the definition information file.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The sub-key cannot be fetched from the key information. Check the content of the definition information file.

KAVA0318-E

The file has a syntax error. (line num. = value)

error-occurrence-line

An error occurred during creation of a registry key. Permission was denied.

character-string

A syntax error was found in a value line of the definition information file.

character-string is the return value of jp1BsCnfGetErrMsg().

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. Creating the specified key information was attempted, but access was rejected. Check the registry status (security).

KAVA0319-E

The file has a syntax error. (line num. = value)

error-occurrence-line

An error occurred during creation of a registry key. An unexpected error occurred.

character-string

A syntax error was found in a value line of the definition information file.

character-string is the return value of jp1BsCnfGetErrMsg().

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in line value in the definition information file. The specified key information cannot be created. Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0323-E

The file has a syntax error. (line num. = value)

error-occurrence-line

A value label string must start with '"'.

A syntax error was found in a value line of the definition information file.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The value label must be enclosed by double quotation marks (""). Check the content of the definition information file.

KAVA0324-E

The file has a syntax error. (line num. = value)

error-occurrence-line

The value syntax is incorrect.

A syntax error was found in a value line of the definition information file.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The value must be defined using the syntax "label" = value. Check the content of the definition information file.

KAVA0325-E

The file has a syntax error. (line num. = value)

error-occurrence-line

The value syntax is incorrect.

A syntax error was found in a value line of the definition information file.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The value label must be enclosed by double quotation marks (""). Check the content of the definition information file.

KAVA0326-E

The file has a syntax error. (line num. = value)

error-occurrence-line

The value syntax is incorrect.

A syntax error was found in a value line of the definition information file.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The value must be defined using the syntax "label" = value. Check the content of the definition information file.

KAVA0327-E

The file has a syntax error. (line num. = value)

error-occurrence-line

The value syntax is incorrect. The label is too long. (max. = 260)

A syntax error was found in a value line of the definition information file.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The value is too long. Check the content of the definition information file.

KAVA0328-E

The file has a syntax error. (line num. = value)

error-occurrence-line

The value syntax is incorrect.

A syntax error was found in a value line of the definition information file.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The value must be defined using the syntax "label" = value. Check the content of the definition information file.

KAVA0329-E

The file has a syntax error. (line num. = value)

error-occurrence-line

The value syntax is incorrect.

A syntax error was found in a value line of the definition information file.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The value must be defined using the syntax "label" = value. Check the content of the definition information file.

KAVA0330-E

The file has a syntax error. (line num. = value)

error-occurrence-line

The value syntax is incorrect.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The value must be defined using the syntax "label" = value. Check the content of the definition information file.

KAVA0331-E

The file has a syntax error. (line num. = value)

error-occurrence-line

The value syntax is incorrect.

A syntax error was found in a value line of the definition information file.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The character string value is defined using the syntax "label" = "character-string" The character-string, however, was not enclosed by double quotation marks (""). Check the content of the definition information file.

KAVA0332-E

The file has a syntax error. (line num. = value)

error-occurrence-line

An error occurred during setting of a string value. Permission was denied.

character-string

A syntax error was found in a value line of the definition information file.

character-string is the return value of jp1BsCnfGetErrMsg().

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. Creating the specified key information was attempted, but access was rejected. Check the registry status (security).

KAVA0333-E

The file has a syntax error. (line num. = value)

error-occurrence-line

An error occurred during setting of a string value. An unexpected error occurred.

character-string

A syntax error was found in a value line of the definition information file.

character-string is the return value of jp1BsCnfGetErrMsg().

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in line value in the definition information file. The specified value cannot be set. Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0334-E

The file has a syntax error. (line num. = value)

error-occurrence-line

The value syntax is incorrect.

A syntax error was found in a value line of the definition information file.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The value must be defined using the syntax "label" = dword: numeral. The syntax dword: numeral is invalid. Check the content of the definition information file.

KAVA0335-E

The file has a syntax error. (line num. = value)

error-occurrence-line

An error occurred during setting of a ulong value. Permission was denied.

character-string

A syntax error was found in a value line of the definition information file.

character-string is the return value of jp1BsCnfGetErrMsg().

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. Creating the specified key information was attempted, but access was rejected. Check the registry status (security).

KAVA0336-E

The file has a syntax error. (line num. = value)

error-occurrence-line

An error occurred during setting of a ulong value. An unexpected error occurred.

character-string

A syntax error was found in a value line of the definition information file.

character-string is the return value of jp1BsCnfGetErrMsg().

(S)

Terminates processing of the jbssetcnf command.

(O)

An error occurred during registration of the contents of the value line of the definition information file. The specified value cannot be set. Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0337-E

The file has a syntax error. (line num. = value)

error-occurrence-line

The value syntax is incorrect.

character-string

A syntax error was found in a value line of the definition information file.

character-string indicates the contents of the exception that occurred.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The specified content of the value is invalid. Check the content of the definition information file.

KAVA0338-E

The file has a syntax error. (line num. = value)

error-occurrence-line

The value syntax is incorrect.

A syntax error was found in a value line of the definition information file.

(S)

Terminates processing of the jbssetcnf command.

(O)

A syntax error was found in a value line of the definition information file. The content of the specified value is not a character string or a value. Check the content of the definition information file.

KAVA0340-E

/opt/jp1/hcclibcnf cannot be accessed. Check whether /opt/jp1/hcclibcnf is available.

The files in the /opt/jp1/hcclibcnf/ directory cannot be read.

(S)

Terminates processing of the jbssetcnf command.

(O)

The files under the /opt/jp1/hcclibcnf/ directory, used to reference the common definition information, cannot be read. Make sure that the directories and files exist and that access permissions are correct.

KAVA0341-E (Windows)

Administrator privileges are required to execute the command.

To execute the command, you must be logged on as a user who has Administrators permissions.

(S)

Terminates processing of the jbssetcnf command.

(O)

Log on as a user who has Administrators permissions, and then re-execute the jbssetcnf command.

KAVA0341-E (UNIX)

Root privileges are required to execute the command.

To execute the command, you must be logged on as a user who has root privileges.

(S)

Terminates processing of the jbssetcnf command.

(O)

Only a user who has root privileges can execute the jbssetcnf command. Execute the command as a user who has root privileges.

KAVA0400-E (Windows)

Administrator privileges are required to execute the command.

To execute the command, you must be logged on as a user who has Administrators permissions.

(S)

Terminates command processing.

(O)

Log on as a user who has Administrators permissions, and then re-execute the command.

KAVA0400-E (UNIX)

Root privileges are required to execute the command.

To execute the command, you must be logged on as a user who has root privileges.

(S)

Terminates command processing.

(O)

Log on as a user who has root privileges, and then re-execute the command.

KAVA0401-E

A jbsunsetcnf option is invalid.

The command option is incorrect.

(S)

Terminates command processing.

(O)

Specify the correct option, and then re-execute the command.

KAVA0402-E

jbsunsetcnf needs a logical hostname.

You need to specify a logical host name in the jbsunsetcnf command.

(S)

Terminates command processing.

(O)

Specify a logical host, and then re-execute the command.

KAVA0403-E

/opt/jp1/hcclibcnf cannot be accessed. Check whether /opt/jp1/hcclibcnf is available.

The /opt/jp1/hcclibcnf directory cannot be accessed.

(S)

Terminates command processing.

(O)

Check that the /opt/jp1/hcclibcnf directory is valid.

KAVA0404-I

The specified character-string information was deleted. (logical-host-information)

The information about the specified logical host was deleted. This messages reports that processing was successful. The display of character-string and logical-host-information differs depending on the options specified in the jbsunsetcnf command.

When only the -h option is specified, character-string shows logical-host and logical-host-information shows the logical host name.

When the -h and -c options are specified, character-string shows component-key and logical-host-information shows logical-host-name\component-name.

When the -h, -c, and -n options are specified, character-string shows sub-key and logical-host-information shows logical-host-name\component-name\subkey.

(S)

Terminates command processing.

KAVA0405-I

The specified character-string does not exist (logical-host-information). Processing stops.

The information about the specified logical host does not exist. This message reports that the specified logical host does not exist. The display of character-string and logical-host-information differs depending on the options specified in the jbsunsetcnf command.

When only the -h option is specified, character-string shows logical-host and logical-host-information shows the logical host name.

When the -h and -c options are specified, character-string shows component-key and logical-host-information shows logical-host-name\component-name.

When the -h, -c, and -n options are specified, character-string shows sub-key and logical-host-information shows logical-host-name\component-name\subkey.

(S)

Terminates command processing.

KAVA0406-E

The specified character-string information could not be deleted. (logical-host-information)

The information about the specified logical host could not be deleted.

The display of character-string and logical-host-information differs depending on the options specified in the jbsunsetcnf command.

When only the -h option is specified, character-string shows logical-host and logical-host-information shows the logical host name.

When the -h and -c options are specified, character-string shows component-key and logical-host-information shows logical-host-name\component-name.

When the -h, -c, and -n options are specified, character-string shows sub-key and logical-host-information shows logical-host-name\component-name\subkey.

(S)

Terminates command processing.

(O)

Make sure that the root user has write permission for the /opt/jp1/hcclibcnf/regdir/HKEY_LOCAL_MACHINE.dat file, and then re-execute the command.

If the error still occurs, use the data collection tool to collect data, and then contact the system administrator.

KAVA0407-I

The user stopped the deletion. (logical-host-information)

The user has canceled the deletion. This message reports that deletion processing is canceled. The display of logical-host-information differs depending on the options specified in the jbsunsetcnf command.

When only the -h option is specified, logical-host-information shows the logical host name.

When the -h and -c options are specified, logical-host-information shows logical-host-name\component-name.

When the -h, -c, and -n options are specified, logical-host-information shows logical-host-name\component-name\subkey.

(S)

Terminates command processing.

KAVA0408-E

An argument is invalid. You must set a component name.

(S)

Terminates processing of the jbsunsetcnf command.

(O)

The jbsunsetcnf command was started with a subkey (-n) specified by an argument without specifying a component name (-c). Make sure that a component name is specified.

KAVA0410-E

A resource could not be obtained.

A resource could not be obtained.

(S)

Terminates command processing.

(O)

OS resources may be insufficient. Re-execute the command.

KAVA0411-E

A resource could not be obtained.

A resource could not be obtained.

(S)

Terminates command processing.

(O)

OS resources may be insufficient. Re-execute the command.

KAVA0412-E

A resource could not be obtained.

A resource could not be obtained.

(S)

Terminates command processing.

(O)

OS resources may be insufficient. Re-execute the command.

KAVA0413-E

A resource could not be obtained.

A resource could not be obtained.

(S)

Terminates command processing.

(O)

OS resources may be insufficient. Re-execute the command.

KAVA0414-E

A resource could not be obtained.

A resource could not be obtained.

(S)

Terminates command processing.

(O)

OS resources may be insufficient. Re-execute the command.

KAVA0415-E

A command argument is invalid.

A command argument is invalid.

(S)

Terminates command processing.

(O)

An unrecognizable option is specified, or no argument is specified in an option that requires an argument. Make sure that the argument specification is correct.

KAVA0416-E

You have no permission for execution. Re-execute with Administrator or root privileges.

You have no permission for execution. Retry with the manager permission.

(S)

Terminates command processing.

(O)

The user must be a member of the Administrators group or must have root privileges. Retry as a user who has the required permissions.

KAVA0417-E

An error occurred during access to the common definition, so the attempt to output jp1hosts failed.

An attempt to output jp1hosts failed because an error occurred during access to a common definition.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified for the -h option or the JP1_HOSTNAME environment variable is correct, and then re-execute the command.

If this message is output when the logical host name is correct, use the data collection tool to collect data, record the arguments specified in the command, and then contact the system administrator.

KAVA0418-E

The logical host logical-host-name has not been set up.

The logical host has not been set up.

(S)

Terminates command processing.

(O)

The information about the specified logical host does not exist. Make sure that the specified logical host name is correct, and that setup was performed correctly.

KAVA0419-E

jp1hosts has not been set up.

jp1hosts has not been set up.

(S)

Terminates command processing.

(O)

jp1hosts does not exist on the specified logical host. Make sure that the specified logical host name is correct, and that jp1hosts is correctly specified on the specified logical host.

KAVA0420-E

An attempt to obtain jp1hosts failed.

An attempt to obtain jp1hosts has failed.

(S)

Terminates command processing.

(O)

OS resources may be insufficient. Re-execute the command.

KAVA0421-E

An attempt to read the jp1hosts definition file (jp1hosts-definition-file-name) has failed.

An attempt to read the jp1hosts definition file has failed.

(S)

Terminates command processing.

KAVA0422-E

An IP address character string is specified for the host name. (line num. = error-occurrence-line)

An IP address character string is specified for the host name.

(S)

Terminates command processing.

(O)

The jp1hosts definition file or the jp1hosts2 definition file has a format error on the line indicated in the message. An IP address is specified for the host name. Correct the jp1hosts definition file or the jp1hosts2 definition file.

KAVA0423-E

The specified number of IP addresses exceeds the maximum. (line num. = error-occurrence-line)

The specified number of IP addresses exceeds the maximum.

(S)

Terminates command processing.

(O)

The jp1hosts definition file or the jp1hosts2 definition file has a format error on the line indicated in the message. No more than four IPv4 or IPv6 addresses can be specified for one host. Correct the jp1hosts definition file or the jp1hosts2 definition file.

KAVA0424-E

character-string is not an IP address character string. (line num. = error-occurrence-line)

character-string cannot be used as an IP address.

(S)

Terminates command processing.

(O)

The jp1hosts definition file or the jp1hosts2 definition file has a format error on the line indicated in the message. An incorrect IP address is specified. Correct the jp1hosts definition file or the jp1hosts2 definition file.

KAVA0425-E

The definition of the host name (host-name) is duplicated. (line num. = error-occurrence-line)

The definition of host-name is duplicated.

(S)

Terminates command processing.

(O)

The jp1hosts definition file or the jp1hosts2 definition file has a format error on the line indicated in the message. The same host name (host-name) is specified more than once in the jp1hosts definition file or the jp1hosts2 definition file. Correct the jp1hosts definition file or the jp1hosts2 definition file.

KAVA0426-E

A host name (host-name) includes a character that cannot be used. (line num. = error-occurrence-line)

host-name includes a character that cannot be used.

(S)

Terminates command processing.

(O)

The jp1hosts definition file or the jp1hosts2 definition file has a format error on the line indicated in the message. A character that cannot be used in a host name is specified. Correct the jp1hosts definition file or the jp1hosts2 definition file.

The following characters cannot be used in the jp1hosts definition file and the jp1hosts2 definition file: / \ [ ] ; : | = , + ? < >

KAVA0427-E

No definition exists in the jp1hosts definition file, so processing cannot continue.

Processing cannot continue because the jp1hosts configuration file contains no definition.

(S)

Terminates command processing.

(O)

The jp1hosts configuration file contains no definition. Check the jp1hosts configuration file.

KAVA0428-E

Processing cannot continue because the jp1hosts configuration file contains an error.

Processing cannot continue because the jp1hosts configuration file contains an error.

(S)

Terminates command processing.

(O)

A syntax error was found in the specified jp1hosts configuration file. Check the contents of the file.

KAVA0429-E

Processing cannot continue because a memory shortage occurred during analysis of the jp1hosts configuration file.

Processing cannot continue because a memory shortage occurred during analysis of the jp1hosts configuration file.

(S)

Terminates command processing.

(O)

OS resources may be insufficient. Re-execute the command.

KAVA0430-E

The specified jp1hosts definition file (jp1hosts-definition-file-name) does not exist, so the attempt to read the definition file failed.

The specified jp1hosts configuration file could not be read because it was not found.

(S)

Terminates command processing.

(O)

The specified jp1hosts configuration file was not found. Make sure that the specified jp1hosts configuration file name is correct.

KAVA0431-E

You do not have permission to access the specified jp1hosts definition file (jp1hosts-definition-file-name), so the attempt to read the definition file failed.

The specified jp1hosts configuration file could not be read because you were not permitted to access it.

(S)

Terminates command processing.

(O)

Retry as a user who is a member of the Administrators group or a root user.

KAVA0432-E

A memory shortage occurred during the reading of the jp1hosts definition file, so processing cannot continue.

Processing cannot continue because a memory shortage occurred while the jp1hosts configuration file was being read.

(S)

Terminates command processing.

(O)

OS resources may be insufficient. Re-execute the command.

KAVA0433-E

An error occurred in an OS system call during the reading of the jp1hosts definition file, so processing cannot continue. (system error code = system-error-code)

Processing cannot continue because an error occurred in an OS system call while the jp1hosts configuration file was being read.

(S)

Terminates command processing.

(O)

OS resources may be insufficient. Re-execute the command.

KAVA0434-E

An error occurred during access to the common definition, so processing cannot continue.

Processing cannot continue because an error occurred during access to the common definition.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified for the -h option or the JP1_HOSTNAME environment variable is correct, and then re-execute the command.

If this message is output when the logical host name is correct, use the data collection tool to collect data, record the arguments specified in the command, and then contact the system administrator.

KAVA0435-E

The processing failed.

Processing failed.

(S)

Terminates command processing.

(O)

Check the error message that was output immediately before this message, correct the cause of the error, and then re-execute the command.

KAVA0436-I

The processing was successful.

Processing succeeded.

(S)

Terminates command processing.

KAVA0437-E

An IP address is not coded. (line num. = error-occurrence-line)

An IP address is not coded.

(S)

Terminates command processing.

(O)

The jp1hosts definition file or the jp1hosts2 definition file has a format error on the line indicated in the message. No IP address is specified for the host. Correct the jp1hosts definition file or the jp1hosts2 definition file.

KAVA0438-E

The jp1hosts definition is incorrect.

The jp1hosts definition is incorrect.

(S)

Terminates command processing.

(O)

The jp1hosts definition is incorrect. Execute the jbshostsimport command with the -r option specified, and reconfigure jp1hosts.

KAVA0439-E

Use from 1 to 255 characters to specify a host name. (line num. = error-occurrence-line)

Use from 1 to 255 characters to specify a host name.

(S)

Terminates command processing.

(O)

The jp1hosts definition file or the jp1hosts2 definition file has a format error on the line indicated in the message. A host name can be from 1 to 255 characters long. Correct the jp1hosts definition file or the jp1hosts2 definition file.

KAVA0440-E (integrated trace log)

The operation failed because an error occurred in the write-lock procedure. The return code is return-code.

An attempt to set a write-lock on the common definition has failed.

(S)

Cancels the command.

(O)

The system environment is invalid. Reinstall and set up the system.

KAVA0440-E (standard error output)

The operation failed because an error occurred in the write-lock procedure.

An attempt to set a write-lock on the common definition has failed.

(S)

Cancels the command.

(O)

The system environment is invalid. Reinstall and set up the system.

KAVA0441-W

The function jp1BsUnlock() failed. Operation will continue. The return code is return-code.

An attempt to release the lock on the common definition has failed.

(S)

Continues command execution.

KAVA0442-E (integrated trace log)

The operation failed because an error occurred in the read-lock procedure. The return code is return-code.

An attempt to set a read-lock on the common definition has failed.

(S)

Cancels the command.

(O)

The system environment is invalid. Reinstall and set up the system.

KAVA0442-E (standard error output)

The operation failed because an error occurred in the read-lock procedure.

An attempt to set a read-lock on the common definition has failed.

(S)

Cancels the command.

(O)

The system environment is invalid. Reinstall and set up the system.

KAVA0443-E

The command cannot be executed because jp1hosts2 was already imported.

The command cannot be executed because the jp1hosts2 information is enabled currently.

(S)

Terminates command processing.

(O)

To use the jp1hosts information, disable the jp1hosts2 information.

To set the jp1hosts information in an environment where the jp1hosts2 information is applied, execute the jbshostsimport command with the -f option specified.

To update the jp1hosts2 information, execute the jbshosts2import command.

KAVA0444-E

An error occurred during access to the common definition, so the attempt to output jp1hosts2 failed.

The jp1hosts2 information could not be output because an error occurred during access to the common definition.

(S)

Terminates command processing.

(O)

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

KAVA0445-E

jp1hosts2 has not been set up.

The jbshosts2import -d command was executed on a host on which the jp1hosts2 information has not been set.

(S)

Terminates command processing.

(O)

Do not execute the jbshosts2import -d command in an environment in which the jp1hosts2 information has not been set.

KAVA0446-E

An attempt to obtain jp1hosts2 failed.

Acquisition of the jp1hosts2 information failed.

(S)

Terminates command processing.

(O)

OS resources might be insufficient. Re-execute the command.

KAVA0447-E

An attempt to read the jp1hosts2 definition file (jp1hosts2-definition-file-name) has failed.

The jp1hosts2 definition file could not be loaded.

(S)

Terminates command processing.

(O)

Make sure that the indicated file exists, and then re-execute the command.

KAVA0448-E

Processing cannot continue because the jp1hosts2 configuration file contains an error.

Processing cannot continue because the jp1hosts2 definition file is incorrect.

(S)

Terminates command processing.

(O)

Check and correct the contents of the jp1hosts2 definition file.

KAVA0449-E

Processing cannot continue because a memory shortage occurred during analysis of the jp1hosts2 configuration file.

Analysis of the jp1hosts2 definition file could not continue because memory became insufficient.

(S)

Terminates command processing.

(O)

OS resources might be insufficient. Re-execute the command.

KAVA0450-E

The specified jp1hosts2 definition file (jp1hosts2-definition-file-name) does not exist, so the attempt to read the definition file failed.

The specified jp1hosts2 definition file could not be loaded because it was not found.

(S)

Terminates command processing.

(O)

Check whether the specified jp1hosts2 definition file name was correct.

KAVA0451-E

You do not have permission to access the specified jp1hosts2 definition file (jp1hosts2-definition-file-name), so the attempt to read the definition file failed.

The specified jp1hosts2 definition file could not be loaded because the user did not have permission to access it.

(S)

Terminates command processing.

(O)

The user must be a member of the Administrators group or must have root privileges. Retry as a user who has the required permissions.

KAVA0452-E

A memory shortage occurred during the reading of the jp1hosts2 definition file, so processing cannot continue.

Processing cannot continue because memory became insufficient while the jp1hosts2 definition file was being loaded.

(S)

Terminates command processing.

(O)

OS resources might be insufficient. Re-execute the command.

KAVA0453-E

An error occurred in an OS system call during the reading of the jp1hosts2 definition file, so processing cannot continue. (system error code = system-error-code)

Processing cannot continue because an OS system call error occurred while the jp1hosts2 definition file was being loaded.

(S)

Terminates command processing.

(O)

OS resources might be insufficient. Re-execute the command.

KAVA0454-E

The jp1hosts2 definition is incorrect.

The jp1hosts2 information has been corrupted.

(S)

Terminates command processing.

(O)

Delete the jp1hosts2 information by executing the jbshosts2import command with the -d option specified. Then, re-import the jp1hosts2 information by executing the jbshosts2import command with the -r or -o option specified.

KAVA0455-I

Importing jp1hosts2 will cause jp1hosts to be disabled.

If the jp1hosts2 definition file is imported, the existing jp1hosts information will be deleted.

KAVA0456-I

There are no changes from the imported jp1hosts2 settings.

The specified jp1hosts2 definition file was not imported because importing of the file will not change the existing jp1hosts2 information.

KAVA0457-I

The addresses of the following hosts were changed or deleted:

Host IP addresses that had been defined were changed or deleted when the specified jp1hosts2 definition file was imported. This message shows the IP addresses that were changed or deleted.

KAVA0458-I

Restart JP1/Base to apply the changes.

The changes have not been applied yet. To apply the changes, JP1/Base must be restarted.

(O)

Restart JP1/Base and all products that require JP1/Base.

If this message is output when the file is imported to JP1/Base on a physical host, you must also restart JP1/Base on the logical host on which either +PhysicalMerge is enabled or the jp1hosts2 definition file has not been imported. In this case, you must also restart all products that require that JP1/Base.

KAVA0460-E

The value specified for the parameter-name parameter is invalid. (line num. = error-occurrence-line)

The value specified for the indicated parameter is invalid.

(S)

Terminates command processing.

(O)

The jp1hosts2 definition file has a format error on the line indicated by error-occurrence-line. Correct the jp1hosts2 definition file.

KAVA0461-E

Over 10,000 hosts are defined.

The number of defined hosts exceeds 10,000.

(S)

Terminates command processing.

(O)

Make sure that the number of defined hosts does not exceed 10,000.

KAVA0462-I

The parameter-name parameter was changed.

The setting of the indicated parameter was changed when the specified jp1hosts2 definition file was imported.

KAVA0463-E

A system error occurred. (detail-code)

The command processing was stopped because a system error occurred.

(S)

Terminates command processing.

(O)

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

KAVA0464-E

Another jbshosts2import command is already running.

The jbshosts2import command is being executed.

(S)

Terminates command processing.

(O)

Check whether the jbshosts2import command was executed from another console or by another user.

Note that this message is also output if an attempt is made to execute the jbshosts2import command on multiple logical hosts at the same time. In this case, execute the jbshosts2import command on one logical host after another, making sure that you do not execute a jbshosts2import command while another jbshosts2import command is still running.

KAVA0465-E

A parameter value is not coded. (line num. = error-occurrence-line)

No value is specified for a parameter.

(S)

Terminates command processing.

(O)

The jp1hosts2 definition file has a format error on the line indicated by error-occurrence-line. Correct the jp1hosts2 definition file.

KAVA0466-E

An unknown parameter value is coded. (line num. = error-occurrence-line)

An unknown parameter value is specified.

(S)

Terminates command processing.

(O)

The jp1hosts2 definition file has a format error on the line indicated by error-occurrence-line. Correct the jp1hosts2 definition file.

KAVA0467-I

jp1hosts2 has imported. (hostname = host-name, filename = path-and-name-of-the-jp1hosts2-definition-file, file-date = update-date-of-the-jp1hosts2-definition-file, import-type = {r|o})

The indicated jp1hosts2 information was imported.

KAVA0468-I

jp1hosts2 has deleted. (hostname = host-name)

The jp1hosts2 information was deleted.

KAVA0469-E

The definition of the parameter-name parameter is duplicated. (line num. = error-occurrence-line)

The indicated parameter is defined more than once.

(S)

Terminates command processing.

(O)

The jp1hosts2 definition file has a format error on the line indicated by error-occurrence-line. A parameter is duplicated in the file. Correct the jp1hosts2 definition file.

KAVA0470-I

jp1hosts2 has not been set up.

The jbshosts2export command was executed on a host on which the jp1hosts2 information has not been set.

KAVA0569-E

The user mapping file name can be from 1 to numeric-value characters.

The name of the user mapping definition file is too long.

(S)

Cancels the command.

(O)

Change the file name, and then re-execute the command.

KAVA0570-E

The logical host name logical-host-name can be from 1 to numeric-value characters.

The logical host name is too long.

(S)

Cancels the command.

(O)

Recheck the logical host name specified in the -h option.

KAVA0571-E

A line exceeds numeric-value characters. (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0572-E

A line does not contain three fields separated by colons (:). (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0573-E

The name of the server-side user is not specified. (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0574-E

The host name of the server-side host is not specified. (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0575-E

The OS user list is invalid. No OS user name is specified. (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping file according to the information in the message.

KAVA0576-E

The name (user-name) of the server-side user contains invalid characters: string (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0577-E

The host name (host-name) of the server-side host contains invalid characters: string (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0578-E

The name of the server-side user exceeds numeric-value characters. (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0579-E

The host name of the server-side host exceeds numeric-value characters. (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0580-E

The name (user-name) of the server-side user contains invalid characters (a space or tab). (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0581-E

The host name (host-name) of the server-side host contains invalid characters (a space or tab). (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0582-E

The name (user-name) of the server-side user is invalid. (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0583-E

The OS user list is invalid. The OS user list (OS-user-list) ends with a comma (,). (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0584-E

The OS user list is invalid. An OS user name exceeds numeric-value characters. (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0585-E

The OS user list is invalid. An OS user name (OS-user-name) contains more than one backslash (\). (line num. = line-number)

The OS user list is invalid.

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0586-E

The OS user list is invalid. An OS user name (OS-user-name) does not have a domain name. (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0587-E

The OS user list is invalid. An OS user name (OS-user-name) has only the domain name. (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0588-E

The password management information is not registered.

(S)

Cancels the command.

(O)

Make sure that the password management information is specified.

KAVA0589-E

The user (user-name) is not registered in the password management information. (line num. = line-number)

(S)

Cancels the command.

(O)

Make sure that information about the displayed user is contained in the password management information.

KAVA0590-E

The execution user does not have the user rights policy "Act as part of the operating system".

(S)

Cancels the command.

(O)

Give the execution user the user rights policy "Act as part of the operating system", or turn off the logon check.

For details about how to set the user rights, see 8.1.5(2) Assigning a user right to an OS user in the Job Management Partner 1/Base User's Guide.

KAVA0591-E

The OS user list is invalid. An OS user name (OS-user-name) does not exist or a password is incorrect. (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0592-E

The OS user list is invalid. An OS user name (OS-user-name) does not have the user rights policy "Act as part of the operating system". (line num. = line-number)

The OS user does not have the user rights policy "Log on locally".

(S)

Cancels the command.

(O)

Use the OS functionality to add the user rights policy "Log on locally" to the the OS user. For details about how to set the user rights, see 8.1.5(2) Assigning a user right to an OS user in the Job Management Partner 1/Base User's Guide.

KAVA0593-E

An error occurred while the validity of the OS user (OS-user-name) was being checked. (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0594-E

jbssetumap was interrupted. (line num. = line-number)

The error disables processing, so the jbssetumap command was canceled.

(S)

Cancels the command.

(O)

Take action according to the information in the message output with this message.

KAVA0601-E (Windows)

Administrator privileges are required to execute the command.

To execute the command, you must be logged on as a user who has Administrators permissions.

(S)

Terminates command processing.

(O)

Log on as a user who has Administrators permissions, and then re-execute the command.

KAVA0601-E (UNIX)

Root privileges are required to execute the command.

To execute the command, you must be logged on as a user who has root privileges.

(S)

Terminates command processing.

(O)

Log on as a user who has root privileges, and then re-execute the command.

KAVA0602-E

A system error occurred during deletion of the key for user mapping information.

A system error occurred during deletion of the key for user mapping information.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0603-E

A system error occurred during creation of the key for user mapping information.

A system error occurred during creation of the key for user mapping information.

(S)

Terminates command processing.

(O)

Re-execute the command. If the error still occurs, use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0604-E

The file file-name cannot be opened.

The specified file-name cannot be opened.

(S)

Terminates command processing.

(O)

Make sure that the file-name specified by the -f option is correct, and that a directory (folder) is specified. Specify a correct file-name, and then re-execute the command.

KAVA0605-E

The length of a line exceeds 4,096 characters.

The command cannot be executed since the number of characters in a line exceeds 4,096.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0606-E

A colon (:) can only be specified twice.

You can specify only two colons (:) in the definition file.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0607-E

An attempt to obtain the user name at the server has failed.

An attempt to obtain the JP1 user name has failed.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0608-E

Use from 1 to 31 characters to specify the name of a server-side user.

The JP1 user name must be specified using 1 to 31 characters.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0609-E

An exception error occurred during an attempt to obtain the name of the server-side user. (code = error-number)

An exception error occurred during an attempt to acquire the JP1 user name.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0610-E

Do not use these symbols in the name of a server-side user: "'/\[]{}():;|=,+?<>

You cannot use the following symbols for JP1 user names: "'/\[]{}():;|=,+?<>

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0611-E

An attempt to obtain the host name of the server-side host has failed.

An attempt to acquire the host name of the server-side host has failed.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0612-E

Use from 1 to 255 characters long to specify the host name of a server-side host.

The host name on the server must be specified using 1 to 255 characters.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0613-E

An exception error occurred during an attempt to obtain the host name of the server-side host. (code = error-number)

An exception error occurred during an attempt to obtain the host name of the server-side host.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0614-E

Do not use these symbols in the host name of a server-side host: "/\[]:;|=,+?<>

The server host name cannot use these symbols: "/\[]:;|=,+?<>.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0615-E

A system error occurred during creation of an ID key of a server-side user.

A system error occurred during creation of an ID key of a server-side user.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0616-E

A system error occurred during creation of an ID key of a server-side host.

A system error occurred during creation of an ID key of a server-side host.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0617-E

No mapping information is registered.

The mapping information was not registered.

(S)

Terminates command processing.

(O)

The mapping information file may be damaged. Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0618-E

The name of the server-side user JP1-user-name is not registered.

JP1-user-name is not registered.

(S)

Terminates command processing.

(O)

The mapping information file may be damaged. Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0619-E

A system error occurred during an attempt to obtain the user ID of the server-side user.

A system error occurred during an attempt to obtain the user ID of the server-side user

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0620-E

An exception error occurred during an attempt to obtain the user ID of the server-side user. (code = error-number)

An exception error occurred during an attempt to obtain the user ID of the server-side user.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0621-E

No mapping information is registered.

The mapping information is not registered.

(S)

Terminates command processing.

(O)

The mapping information file may be damaged. Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0622-E

The server-side host server-host is not registered.

The server-host is not registered.

(S)

Terminates command processing.

(O)

The mapping information file may be damaged. Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0623-E

A system error occurred during an attempt to obtain the host ID of the server-side host.

A system error occurred during an attempt to obtain the host ID of the server-side host.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0624-E

An exception error occurred during an attempt to obtain the host ID of the server-side host. (code = error-number)

An exception error occurred during an attempt to obtain the host ID of the server-side host.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0625-W

The name of a server-side user (JP1-user-name) and server-side host (server-side-host-name) are defined more than once. This line is ignored.

The setting in the line is ignored since JP1-user-name and server-host-name are defined more than once.

(S)

Ignores the specified line and continues processing.

(O)

This is a warning message. A combination of the JP1 user name and the server host name is defined twice in a definition file. The last specified line is ignored.

KAVA0626-E

A system error occurred during creation of a server-side registry key.

A system error occurred during creation of a server-side registry key.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0627-E

An attempt to obtain a list of agent-side users has failed.

An attempt to obtain a list of users has failed.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0629-E

An exception error occurred during an attempt to obtain a list of agent-side users. (code = error-number)

An exception error occurred during an attempt to obtain a list of users.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0630-E

An attempt to obtain the agent-side user has failed.

An attempt to obtain the OS user has failed.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0631-E

Use from 1 to 64 characters to specify an agent-side user.

The OS user name must be specified using from 1 to 64 characters.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0632-E

An exception error occurred during an attempt to obtain the agent-side user. (code = error-number)

An exception error occurred during an attempt to obtain the OS user.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0633-W

The agent-side user (OS-user-name) is defined more than once.

The OS-user-name is defined twice.

(S)

Ignores the specified OS user and continues processing.

(O)

This is a warning message. The OS user name is defined twice in the same line of a definition file. The last specified OS user is ignored.

KAVA0634-E

A system error occurred during registration of an agent-side user.

A system error occurred during registration of the OS user.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0635-E

A system error occurred during registration of the primary user.

A system error occurred during registration of the primary user.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0636-E

Only one \ can be specified in a user name.

Only one backslash (\) can be specified for a user name.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0637-E

An attempt to obtain the domain name has failed.

An attempt to obtain the domain name has failed.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0638-E

Use from 1 to 64 characters to specify a domain name.

The domain name must be specified using 1 to 64 characters.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0639-E

An exception error occurred during an attempt to obtain the domain name. (code = error-number)

An exception error occurred during an attempt to obtain the domain name.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0640-E

An attempt to obtain the user name has failed.

An attempt to obtain the OS user name has failed.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0641-E

Use from 1 to 64 characters to specify a user name.

A user name must be specified using 1 to 64 characters.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0642-E

An exception error occurred during an attempt to obtain the user name. (code = error-number)

An exception error occurred during an attempt to obtain the user name.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0643-E

No password management information is registered.

The password management information is not registered.

(S)

Terminates command processing.

(O)

Execute the jbsmkpass command and the jbspassmgr command to register the password management information, and then re-execute the command.

KAVA0644-E

The user (OS-user-name) is not registered in the password management information.

OS-user-name is not registered in the password management information.

(S)

Terminates command processing.

(O)

The logical host specified in the password management information and the logical host specified in the mapping management information are different. Alternatively, the OS user may not be registered in the password management information.

Check that the logical host specified in the password management information and the logical host specified in the mapping management information have the same host name. If the host names are different, specify the same host name, and then re-execute the command. If a user is not registered in the password management information, use the jbsmkpass command to register the OS user in the password management information. Then re-execute the command.

KAVA0645-E

A system error occurred during an attempt to obtain the password.

A system error occurred during an attempt to obtain the password.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0646-E

A system error occurred while the password was being scrambled.

A system error occurred while the password was being scrambled.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0647-E

The name of the agent-side user (OS-user-name) is incorrect.

OS-user-name is incorrect.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0648-E

The number of arguments is incorrect.

The number of arguments is incorrect.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0649-E

The -f option is defined more than once.

The -f option is defined twice.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0650-E

The -h option is defined more than once.

The -h option is defined twice.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0651-E

The option name option-name cannot be recognized.

The option-name option cannot be recognized.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0653-E

An attempt to allocate memory failed due to insufficient memory.

Memory allocation failed because of insufficient memory.

(S)

Terminates command processing.

(O)

Make sure that sufficient memory is available, and then re-execute the command.

KAVA0654-I

Mapping information was successfully registered.

Registering user mapping information was successful.

(S)

Terminated command processing normally.

(O)

This messages indicates that mapping information was registered successfully.

KAVA0655-E (Windows)

Use a maximum of 196 characters to specify the logical host name.

The logical host name must be specified using no more than 196 characters.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command. no more than 63 characters can be specified for actual operation. Specify the logical host name using no more than 63 characters.

KAVA0655-E (UNIX)

Use a maximum of 255 characters to specify the logical host name.

The logical host name must be specified using no more than 255 characters.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command. no more than 63 characters can be specified for actual operation. Specify the logical host name using no more than 63 characters.

KAVA0656-I

jbsmkumap has started. (definition file name = definition-file-name, logical host name = logical-host-name)

The jbsmkumap command has started.

(S)

Started the jbsmkumap command.

(O)

This messages indicates that processing has started.

KAVA0657-E

You cannot use spaces or tabs in the name of a server-side user.

You cannot specify a space or tab in a JP1 user name.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0658-E

You cannot use spaces or tabs in the host name of a server-side host.

You cannot specify a space or tab in a server host name.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0659-E

An illegal comma (,) is coded at the end of the list of agent-side users.

A comma (,) is specified at the end of a user list.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0660-E

No common definition information (JP1BASE_CONFDIR) is defined.

No common definition information (JP1BASE_CONFDIR) is defined.

(S)

Terminates command processing.

(O)

An environment setting was not done normally. Re-execute the environment setting command, and then re-execute this command.

KAVA0661-E

A system error occurred during an attempt to obtain the default file name.

A system error occurred during an attempt to obtain the default file name.

(S)

Terminates command processing.

(O)

The environment was not set up normally. Re-execute the environment setting command (jp1base_setup), and then re-execute the command.

KAVA0662-W

You can register up to 9,999 server-side users. No more user registration is allowed.

You can register no more than 9,999 JP1 users. 10,000 or more users cannot be registered.

(S)

Terminates command processing.

(O)

10,000 or more users are specified in a definition file. The system cancels registration when 9,999 users are registered.

KAVA0663-W

You can register up to 9,999 server-side hosts. No more host registration is allowed.

You can register no more than 9,999 hosts on the server host. 10,000 or more hosts cannot be registered.

(S)

Terminates command processing.

(O)

10,000 or more hosts are specified in a definition file. The system cancels registration when 9,999 hosts are registered.

KAVA0664-E

The name of the server-side user contains invalid characters.

An invalid character (multi-byte) is found in the name of the server-side user.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0665-W

jbsmkumap was interrupted.

The jbsmkumap command processing was interrupted by a user's instruction.

(S)

Terminates command processing.

(O)

This warning message reports that the jbsmkumap command processing was interrupted by a user's instruction. To re-register, re-execute the jbsmkumap command.

KAVA0666-E

The common definition information key [logical-host\JP1BASE] is not defined.

The common definition information key is not defined.

(S)

Terminates command processing.

(O)

Check that the setup processing is performed normally. Check also that the logical host name specified in the -h option is correct.

KAVA0667-I

jbssetumap has started. (logical host name = logical-host-name)

KAVA0668-E

The name of a server-side user can be from 1 to 31 characters.

The specified user name is too long.

(S)

Cancels the command.

(O)

Check the options, and then re-execute the command.

KAVA0669-E

The name of a server-side host can be from 1 to numeric-value characters.

The specified host name is too long.

(S)

Cancels the command.

(O)

Check the options, and then re-execute the command.

KAVA0670-E

The OS user list can be from 1 to numeric-value characters.

The specified OS user list is too long.

(S)

Cancels the command.

(O)

Check the options, and then re-execute the command.

KAVA0671-E

The option-name option is not specified.

The option-name option is missing.

(S)

Cancels the command.

(O)

Check the option, and then re-execute the command.

KAVA0672-E

The OS user list is invalid. An OS user name (OS-user-name) does not have a domain name.

The OS user list is invalid.

(S)

Cancels the command.

(O)

Check the options according to the information in the message.

KAVA0673-E

The OS user list is invalid. An OS user name (OS-user-name) has only a domain name.

The OS user list is invalid.

(S)

Cancels the command.

(O)

Check the options according to the information in the message.

KAVA0674-E

The OS user list is invalid. An OS user name (OS-user-name) has more than one backslash (\).

The OS user list is invalid.

(S)

Cancels the command.

(O)

Check the options according to the information in the message.

KAVA0675-E

The OS user (OS-user-name) is not registered in the password management information.

(S)

Cancels the command.

(O)

Make sure that the password management information contains the displayed user information.

KAVA0676-E

An error occurred during a consistency check of the OS user name OS-user-name.

(S)

Cancels the command.

(O)

Check the options according to the information in the message.

KAVA0677-E

The OS user list is invalid. An OS user name (OS-user-name) does not exist or a password is incorrect.

The OS user list is invalid.

(S)

Cancels the command.

(O)

Check the options according to the information in the message.

KAVA0678-E

The OS user list is invalid. An OS user (OS-user-name) does not have the user rights policy "Log on locally".

The OS user list is invalid.

(S)

Cancels the command.

(O)

Use the OS functionality to add the user rights policy "Log on locally" to the OS user. For details about how to set the user rights, see 8.1.5(2) Assigning a user right to an OS user in the Job Management Partner 1/Base User's Guide.

KAVA0679-E

The OS user list is invalid. An OS user (OS-user-name) is invalid.

The OS user list is invalid.

(S)

Cancels the command.

(O)

Check the options according to the information in the message.

KAVA0682-E

The number of server-side users reached the maximum (9,999), so registration will not be executed.

(S)

Terminates processing.

(O)

Delete unnecessary settings.

KAVA0683-E

The number of server-side hosts reached the maximum (9,999), so registration will not be executed.

(S)

Terminates processing.

(O)

Delete unnecessary settings.

KAVA0684-W

The mapping information for the user (user-name) and host (host-name) was not updated because the information already exists.

KAVA0686-W

A user name is duplicated in the OS user list.

The same OS user is specified more than once.

(S)

Continues processing.

KAVA0687-E

The name (user-name) of the server-side user is invalid.

(S)

Cancels the command.

(O)

Check the options according to the information in the message.

KAVA0688-E

The name (user-name) of the server-side user contains an invalid character: string.

(S)

Cancels the command.

(O)

Check the options according to the information in the message.

KAVA0689-E

The name (user-name) of the server-side user contains an invalid character (a space or tab).

(S)

Cancels the command.

(O)

Check the options according to the information in the message.

KAVA0690-E

The host name (host-name) of the server-side host contains an invalid character: string.

(S)

Cancels the command.

(O)

Check the options according to the information in the message.

KAVA0691-E

The host name (host-name) of the server-side host contains an invalid character (a space or tab).

(S)

Cancels the command.

(O)

Check the options according to the information in the message.

KAVA0692-E

The OS user list is invalid. The OS user list (OS-user-name) ends with a comma (,).

(S)

Cancels the command.

(O)

Check the options according to the information in the message.

KAVA0693-E

The OS user list is invalid. An OS user name is not specified.

(S)

Cancels the command.

(O)

Check the options according to the information in the message.

KAVA0694-E

The OS user list is invalid. An OS user name exceeds numeric-value characters.

(S)

Cancels the command.

(O)

Check the options according to the information in the message.

KAVA0695-E

The -f option cannot be specified together with the -u, -ua, -sh, -sha, or -o options.

(S)

Cancels the command.

(O)

Check the options according to the information in the message.

KAVA0696-E

The option-name or option-name option is defined more than once.

(S)

Cancels the command.

(O)

Check the options according to the information in the message.

KAVA0697-E

The option-name or option-name option is not specified.

(S)

Cancels the command.

(O)

Check the options according to the information in the message.

KAVA0699-E

Root privileges are required to set mapping information for the root user.

To add the specified user mapping settings, you must have root privileges.

(S)

Cancels the command.

(O)

Re-execute the command as a user who has root privileges.

KAVA0701-E

Administrator privileges are required to execute the command.

To execute the command, you must be logged on as a user who has Administrators permissions.

(S)

Terminates command processing.

(O)

Log on as a user who has Administrators permissions, and then re-execute the command.

KAVA0702-E

A system error occurred during deletion of a for key for password management information.

A system error occurred during deletion of a key for password management information.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0703-E

A system error occurred during creation of a key for password management information.

A system error occurred during creation of a key for password management information.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0704-E

The file file-name cannot be opened.

file-name cannot be opened.

(S)

Terminates command processing.

(O)

Make sure that the file-name specified by the -f option is correct, and that the path is specified correctly. Specify the correct file-name, and then re-execute the command.

KAVA0705-E

The length of a line exceeds 4,096 characters.

The number of characters in a line exceeds 4,096.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0706-E

An attempt to obtain the user name has failed.

An attempt to obtain the OS user name or the information-search user name has failed.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0707-E

Use from 1 to 64 characters to specify the user name.

The OS user name or the information-search user name must be specified using 1 to 64 characters.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0708-E

An unexpected error occurred during an attempt to obtain the user name. (code = error-number)

An unexpected error occurred during an attempt to obtain the OS user name or the information-search user name.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0709-E

Only one \ can be specified in a user name.

Only one backslash (\) character can be specified in an OS user name.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0710-E

An attempt to obtain the domain name has failed.

An attempt to obtain the domain name has failed.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0711-E

Use from 1 to 64 characters for a domain name.

The domain name must be specified using 1 to 64 characters.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0712-E

An unexpected error occurred during an attempt to obtain the domain name. (code = error-number)

An unexpected error occurred during an attempt to obtain the domain name.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0713-E

An attempt to obtain the user name has failed.

An attempt to obtain the OS user name or the information-search user name has failed.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0714-E

Use from 1 to 64 characters to specify a user name.

The OS user name or the information-search user name must be specified using 1 to 64 characters.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0715-E

An unexpected error occurred during an attempt to obtain the user name. (code = error-number)

An unexpected error occurred during an attempt to obtain the OS user name or the information-search user name.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0716-E

An attempt to obtain the password has failed.

An attempt to acquire the password has failed.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0717-E

Use from 1 to 64 characters for a password.

A password must be specified using 1 to 64 characters.

(S)

Terminates command processing.

(O)

The definition file contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0718-E

An unexpected error occurred during an attempt to obtain the password. (code = error-number)

An unexpected error occurred during an attempt to obtain the password.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0719-W

The user (OS-user-name-or-information-search-user-name) is defined more than once. This line is ignored.

This line is ignored because OS-user-name-or-information-search-user-name has been defined more than once.

(S)

Ignores the specified line and continues processing.

(O)

This is a warning message. The OS user name is defined twice in the same line of a definition file. The last specified line is ignored.

KAVA0720-E

A system error occurred while the password was being scrambled.

A system error occurred while the password was being scrambled.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0721-E

A system error occurred during registration of the user.

A system error occurred during registration of the OS user or information-search user.

(S)

Terminates command processing.

(O)

Re-execute the command. If the error still occurs, use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0722-E

The number of arguments is incorrect.

The number of arguments is incorrect.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0723-E

The -f option is defined more than once.

The -f option is defined twice.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0724-E

The -h option is defined more than once.

The -h option is defined twice.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0725-E

The option name option-name cannot be recognized.

The option-name option cannot be recognized.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0726-E

No -f option is specified.

The -f option is not specified.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA0727-E

Memory allocation failed due to insufficient memory.

An attempt to allocate memory failed because of insufficient memory.

(S)

Terminates command processing.

(O)

Allocate sufficient memory, and then re-execute the command.

KAVA0728-I

The password was successfully registered.

The password information was successfully registered.

(S)

Terminated command processing normally.

(O)

This message notifies you that processing was successful in registering mapping information.

KAVA0729-E (Windows)

Use a maximum of 196 characters to specify the logical host name.

The logical host name must be specified using no more than 196 characters.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command. no more than 63 characters can be specified for actual operation. Specify the logical host name using no more than 63 characters.

KAVA0729-E (UNIX)

Use a maximum of 255 characters to specify the logical host name.

The logical host name must be specified using no more than 255 characters.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command. no more than 63 characters can be specified for actual operation. Specify the logical host name using no more than 63 characters.

KAVA0730-I

jbsmkpass has started. (definition file name = definition-file-name, logical host name = logical-host-name)

The jbsmkpass command has started.

(S)

Started the jbsmkpass command.

(O)

This message notifies you that processing has started.

KAVA0731-E

The -p option is defined more than once.

The -p option is defined more than once.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command.

KAVA0732-E

The -u option is defined more than once.

The -u option is defined more than once.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command.

KAVA0733-E

No -u option is specified.

The -u option is not specified.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command.

KAVA0735-I

jbsumappass has started. (user name = OS-user-name-or-information-search-user-name)

jbsumappass has started.

(S)

Started jbsumappass.

(O)

This message reports that processing has started.

KAVA0736-E

An attempt to open a resource file has failed.

An attempt to open a resource file has failed.

(S)

Terminates processing.

(O)

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

KAVA0737-I

jbsrmumappass has started. (user name = OS-user-name-or-information-search-user-name)

jbsrmumappass has started.

(S)

Started jbsrmumappass.

(O)

This message reports that processing has started.

KAVA0739-E

The specified logical host 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.

KAVA0740-E

A system error occurred during an attempt to obtain the status of registered authentication servers.

The registered authentication server has a logical inconsistency.

(S)

Terminates processing.

(O)

Use the JP1/Base Environment Settings dialog box (in Windows) or the jbssetusrsrv command (in UNIX) to register the authentication server again. If the problem is not solved, use the data collection tool to collect data, and then contact the system administrator.

KAVA0741-E

No authentication server is specified.

No authentication server is set.

(S)

Terminates processing.

(O)

Use the JP1/Base Environment Settings dialog box (in Windows) or the jbssetusrsrv command (in UNIX) to register the authentication server again. Then re-execute the command.

KAVA0742-E

A system error occurred during an attempt to obtain the blocking status of the authentication server.

A system error occurred during an attempt to obtain the blocking status of the authentication server.

(S)

Terminates processing.

(O)

In Windows, check whether the user has the appropriate access permission for the blockade file in the installation-folder\jp1base\conf\user_acl\blockade folder.

In UNIX, check whether the user has the appropriate access permission for the blockade file in the /etc/opt/jp1base/conf/user_acl/blockade directory.

If the problem is not solved, delete the file, and then re-execute the command.

KAVA0744-W

The authentication server (authentication-server-name) is already unblocked.

The authentication server (authentication-server-name) is already unblocked.

(S)

Terminates processing.

(O)

This warning message indicates that no processing was performed because the authentication server was already unblocked.

KAVA0745-E

A system error occurred during an attempt to unblock an authentication server.

A system error occurred during an attempt to release the blocked status of an authentication server.

(S)

Terminates processing.

(O)

In Windows, check whether the user has the appropriate access permission for the blockade file in the installation-folder\jp1base\conf\user_acl\blockade folder.

In UNIX, check whether the user has the appropriate access permission for the blockade file in the /etc/opt/jp1base/conf/user_acl/blockade directory.

If the problem is not solved, delete the file, and then re-execute the command.

KAVA0746-E

Use a maximum of 255 characters for the authentication server name.

The authentication server name must be specified using no more than 255 characters.

(S)

Terminates processing.

(O)

The command specification contains a syntax error. Correct the argument error, and then re-execute the command.

KAVA0748-W

The authentication server (authentication-server-name) is already blocked.

The authentication server (authentication-server-name) is already blocked.

(S)

Terminates processing.

(O)

This warning message indicates that no processing was performed because the authentication server was already blocked.

KAVA0749-E

The -s option is defined more than once.

The -s option is defined more than once.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command.

KAVA0750-E

The -s option is not specified.

The -s option is not specified.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command.

KAVA0751-E

A system error occurred during an attempt to block an authentication server.

A system error occurred during blocking of the authentication server.

(S)

Terminates processing.

(O)

In Windows, check whether the user has the appropriate access permission for the blockade file in the installation-folder\jp1base\conf\user_acl\blockade folder.

In UNIX, check whether the user has the appropriate access permission for the blockade file in the /etc/opt/jp1base/conf/user_acl/blockade directory.

If the problem is not solved, delete the file, and then re-execute the command.

KAVA0755-E

An attempt to access the file storing the blocking status has failed.

An attempt to access the blocked status file has failed.

(S)

Terminates processing.

(O)

Display the initial blocked status.

KAVA0756-E

The directory containing the file storing the blocking status does not exist.

No directory contains the blocked status file.

(S)

Terminates processing.

(O)

Display the initial blocked status.

KAVA0757-W

The specified authentication server cannot be blocked.

The specified authentication server cannot be blocked.

(S)

Terminates processing.

(O)

If there is only one authentication server (primary), you cannot block it.

KAVA0758-E

The specified authentication server is not registered in the common definition information.

The specified authentication server is not registered in the common definition information.

(S)

Terminates processing.

(O)

Check the registered authentication server, and then re-execute the command.

KAVA0759-E

The common definition information cannot be accessed.

The common definition information cannot be accessed.

(S)

Terminates processing because the attempt to access the common definition information failed.

(O)

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

KAVA0760-W

An attempt to initialize the blocking status has failed.

An attempt to initialize the blocked status file has failed.

(S)

Continues processing.

(O)

This is a warning message indicating that the system failed to initialize the blocked status of the authentication server containing the error.

KAVA0761-E

An attempt to create a storage directory for the file keeping the authentication server's blocking status has failed.

An attempt to create the directory containing the blocked status file has failed.

(S)

Continues processing.

(O)

In Windows, check whether the user has the appropriate access permission for the installation-folder\jp1base\conf\user_acl folder.

In UNIX, check whether the user has the appropriate access permission for the /etc/opt/jp1base/conf/user_acl directory.

If this message appears on the secondary node in a cluster environment, use the primary node to perform the check.

KAVA0762-E

System resources are insufficient.

System resources necessary for command execution are insufficient.

(S)

Cancels the command.

(O)

Terminate other processes that are currently being executed and can be stopped, and then re-execute the command.

KAVA0763-E

Administrator privileges are required to execute the command.

The user who tries to execute the command does not have Administrators permissions.

(S)

Cancels the command.

(O)

Execute the command as a user who has Administrators permissions.

KAVA0764-E

The string option does not exist.

(S)

Cancels the command.

(O)

Recheck the specified option, and then re-execute the command.

KAVA0765-E

The option-name option is specified more than once.

(S)

Cancels the command.

(O)

Recheck the specified option, and then re-execute the command.

KAVA0766-E

The option-name, option-name or option-name option is mandatory.

(S)

Cancels the command.

(O)

Recheck the specified option, and then re-execute the command.

KAVA0767-E

The value of the option-name option is not specified.

(S)

Cancels the command.

(O)

Recheck the specified option, and then re-execute the command.

KAVA0768-E

The specified logical host does not exist. (logical host name = logical-host-name)

(S)

Cancels the command.

(O)

Recheck the logical host name specified in the -h option.

KAVA0769-E

An attempt to read the user mapping definition file (file-name) failed.

(S)

Cancels the command.

(O)

Make sure that the user mapping definition file can be read.

KAVA0784-W

The file (file-name) does not contain user mapping information.

(S)

Cancels the command.

(O)

Check the contents of the file.

KAVA0785-I

jbssetumap has started. (user mapping file = file-name, logical host name = logical-host-name)

KAVA0786-W

More than one user (user-name) and host (host-name) are defined. This line will be ignored. (line = line-number)

(S)

Continues processing.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0788-E

The number of server-side users reached the maximum (9,999). No more registration is allowed. (line num. = line-number)

(S)

Terminates processing.

(O)

Delete unnecessary settings.

KAVA0789-E

The number of server-side hosts reached the maximum (9,999). No more registration is allowed. (line num. = line-number)

(S)

Terminates processing.

(O)

Delete unnecessary settings.

KAVA0790-W

The mapping information for the user (user-name) and host (host-name) was not updated because the mapping information already exists. (line num. = line-number)

KAVA0791-I

jbssetumap executed successfully.

KAVA0792-W

An error occurred while the log directory information was being read from the common definition. The processing will now continue without log output.

Information about the log output destination could not be obtained.

(S)

Continues command processing without outputting log data.

(O)

Operation is performed normally, but the environment is invalid. Reinstall and set up the system.

KAVA0793-W

An error occurred while the log settings information was being read from the common definition. The processing will now continue without log output.

Information about the log output destination could not be obtained.

(S)

Continues command processing without outputting log data.

(O)

Operation is performed normally, but the environment is invalid. Reinstall and set up the system.

KAVA0794-W

An error occurred while HNTR Library was being initialized. (return code = return-code) The processing will now continue without log output.

The integrated trace log is unavailable.

(S)

Continues command processing without outputting log data.

KAVA0801-E

Enter a user name.

An OS user name or an information-search user name must be entered.

(S)

Terminates command processing.

(O)

The entered data contains an error. Correct the data error, and then re-execute the command.

KAVA0802-E

Only one \ can be specified in a user name.

Only one backslash (\) can be specified for a user name.

(S)

Terminates command processing.

(O)

The entered data contains an error. Correct the data error, and then re-execute the command.

KAVA0803-E

An attempt to obtain the domain name has failed.

An attempt to obtain the domain name has failed.

(S)

Terminates command processing.

(O)

The entered data contains an error. Correct the data error, and then re-execute the command.

KAVA0804-E

Use from 1 to 64 characters for a domain name.

The domain name must be specified using 1 to 64 characters.

(S)

Terminates command processing.

(O)

The entered data contains an error. Correct the data error, and then re-execute the command.

KAVA0805-E

An unexpected error occurred during an attempt to obtain the domain name. (code = error-number)

An unexpected error occurred during an attempt to acquire the domain name.

(S)

Terminates command processing.

(O)

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

KAVA0806-E

An attempt to obtain the user name has failed.

An attempt to obtain the OS user name or the information-search user name has failed.

(S)

Terminates command processing.

(O)

The entered data contains an error. Correct the data error, and then re-execute the command.

KAVA0807-E

Use from 1 to 64 characters for a user name.

The OS user name or the information-search user name must be specified using 1 to 64 characters.

(S)

Terminates command processing.

(O)

The entered data contains an error. Correct the data error, and then re-execute the command.

KAVA0808-E

An unexpected error occurred during an attempt to obtain the user name. (code = error-number)

An unexpected error occurred during an attempt to obtain the OS user name or the information-search user name.

(S)

Terminates command processing.

(O)

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

KAVA0809-E

The password and password confirmation do not match.

The password and the result of password confirmation do not match.

(S)

Terminates command processing.

(O)

The entered data contains an error. Correct the data error, and then re-execute the command.

KAVA0810-W

OS-user-name is already registered.

OS-user-name-or-information-search-user-name has already been registered.

(S)

Ignores the specified OS user and continues processing.

(O)

This is a warning message. The specified OS user has already been registered.

KAVA0811-E

A system error occurred while the password was being scrambled.

A system error occurred while the password was being scrambled.

(S)

Terminates command processing.

(O)

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

KAVA0812-E

A system error occurred during registration of a new user.

A system error occurred during registration of a new user.

(S)

Terminates command processing.

(O)

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

KAVA0813-I

OS-user-name-or-information-search-user-name was successfully registered.

OS-user-name-or-information-search-user-name was successfully registered.

(S)

Terminated command processing normally.

(O)

This message reports that processing was successful. The OS user is registered.

KAVA0814-E

Enter a user name.

An OS user name or an information-search user name must be entered.

(S)

Terminates command processing.

(O)

The entered data contains an error. Correct the data error, and then re-execute the command.

KAVA0815-E

Only one \ can be specified in a user name.

Only one backslash (\) can be specified for a user name.

(S)

Terminates command processing.

(O)

The entered data contains an error. Correct the data error, and then re-execute the command.

KAVA0816-E

An attempt to obtain the domain name has failed.

An attempt to acquire the domain name has failed.

(S)

Terminates command processing.

(O)

The entered data contains an error. Correct the data error, and then re-execute the command.

KAVA0817-E

Use from 1 to 64 characters for a domain name.

The domain name must be specified using 1 to 64 characters.

(S)

Terminates command processing.

(O)

The entered data contains an error. Correct the data error, and then re-execute the command.

KAVA0818-E

An unexpected error occurred during an attempt to obtain the domain name. (code = error-number)

An unexpected error occurred during an attempt to acquire the domain name.

(S)

Terminates command processing.

(O)

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

KAVA0819-E

An attempt to obtain the user name has failed.

An attempt to obtain the OS user name or the information-search user name has failed.

(S)

Terminates command processing.

(O)

The entered data contains an error. Correct the data error, and then re-execute the command.

KAVA0820-E

Use from 1 to 64 characters for a user name.

The OS user name or the information-search user name must be specified using 1 to 64 characters.

(S)

Terminates command processing.

(O)

The entered data contains an error. Correct the data error, and then re-execute the command.

KAVA0821-E

An unexpected error occurred during an attempt to obtain the user name. (code = error-number)

An unexpected error occurred during an attempt to acquire the OS user name or the information-search user name.

(S)

Terminates command processing.

(O)

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

KAVA0822-E

The password and password confirmation do not match.

The password and the result of password confirmation do not match.

(S)

Terminates command processing.

(O)

The entered data contains an error. Correct the data error, and then re-execute the command.

KAVA0823-E

A system error occurred while the password was being scrambled.

A system error occurred while the password was being scrambled.

(S)

Terminates command processing.

(O)

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

KAVA0824-E

A system error occurred during registration of the password.

A system error occurred during registration of a password.

(S)

Terminates command processing.

(O)

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

KAVA0825-I

The password for OS-user-name-or-information-search-user-name was changed.

The password for OS-user-name-or-information-search user name was changed.

(S)

Terminated command processing normally.

(O)

This message reports that processing was successful. The password of the OS user or information-search user was changed.

KAVA0826-E

Administrator privileges are required to execute the command.

To execute the command, you must be logged on as a user who has Administrators permissions.

(S)

Terminates command processing.

(O)

Log on as a user who has Administrators permissions, and then re-execute the command.

KAVA0827-E

A system error occurred during creation of a key for password management information.

A system error occurred during creation of a key for password management information.

(S)

Terminates command processing.

(O)

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

KAVA0828-W

OS-user-name-or-information-search-user-name was already deleted.

OS-user-name-or-information-search-user-name has already been deleted.

(S)

Terminated command processing normally.

(O)

This is a warning message. The OS user or the information-search user has already been deleted from the password management information.

KAVA0829-I

Are you sure you want to delete the selected user?

The selected OS user or information-search user is about to be deleted.

(S)

Waits for the operator's instruction.

(O)

This is a confirmation message. Make sure that you really want to delete the OS user or the information-search user.

KAVA0830-W

OS-user-name-or-information-search-user-name was already deleted.

OS-user-name-or-information-search-user-name has already been deleted.

(S)

Terminated command processing normally.

(O)

This is a warning message. The specified OS user or information-search user has already been deleted from the password management information.

KAVA0831-E

A system error occurred during deletion of the user.

A system error occurred during deletion of the OS user or the information-search user.

(S)

Terminates command processing.

(O)

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

KAVA0832-E

A system error occurred during an attempt to obtain the registered users.

A system error occurred during an attempt to obtain the registered OS users or information-search users.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information that you want to register, and then contact the system administrator.

KAVA0833-E

A system error occurred in Windows.

An error occurred in the Windows API.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information that you want to register, and then contact the system administrator.

KAVA0834-E

The password management facility is already running.

The password management functionality is already running.

(S)

Terminates command processing.

(O)

Terminate the password management functionality that is already running, and then re-execute the command.

KAVA0835-I

The password management has been invoked. (logical host name = logical-host-name)

The password management has started.

(S)

Started the password management.

(O)

This message reports that processing has started.

KAVA0836-I

Password management has ended.

The password management has terminated.

(S)

Terminated the password management.

(O)

This message reports that processing has terminated.

KAVA0837-I

OS-user-name-or-information-search-user-name was deleted.

OS-user-name-or-information-search-user-name was deleted.

(S)

Terminated command processing normally.

(O)

This message reports that processing has terminated successfully. The OS user or the information-search user was deleted.

KAVA0838-E

Enter a logical host name.

Enter a logical host name.

(S)

Terminates command processing.

(O)

The entered data contains an error. Correct the data error, and then re-execute the command.

KAVA0839-E

Memory allocation failed due to insufficient memory.

An attempt to allocate memory has failed because of insufficient memory.

(S)

Terminates command processing.

(O)

Make sure that sufficient memory is available, and then re-execute the command.

KAVA0850-E

Root privileges are required to set mapping information for the root user.(line num. =line-number)

To add the specified user mapping settings, you must have root privileges.

(S)

Cancels the command.

(O)

Re-execute the command as a user who has root privileges.

KAVA0851-E

The operation failed because an error occurred in the write-lock procedure.

An attempt to set a write-lock on the common definition has failed.

(S)

Cancels the command.

(O)

The system environment is invalid. Reinstall and set up the system.

KAVA0852-E

An error occurred while the common definition was being accessed.

An error occurred while the common definition was being referenced.

(S)

Cancels the command.

(O)

The system environment is invalid. Reinstall and set up the system.

KAVA0853-E

The user mapping file is corrupted.

The user mapping definition file could not be read.

(S)

Cancels the command.

(O)

Make sure that the user mapping definition file can be read.

KAVA0854-E

The common definition is corrupted.

The common definition information is corrupted.

(S)

Cancels the command.

(O)

The environment is invalid. Reinstall and set up the system.

KAVA0856-W

A user name is duplicated in the OS user list. (line num. = line-number)

The same OS user is specified more than once.

(S)

Continues processing.

KAVA0863-E

An internal error occurred.

(S)

Cancels the command.

(O)

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

KAVA0864-E

An attempt to lock the common definition information has failed. Contact the system administrator.

(S)

Cancels the command.

(O)

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

KAVA0865-E

The OS user list is invalid. An OS user (OS-user-name) is invalid. (line num. = line-number)

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file according to the information in the message.

KAVA0866-E

The user mapping file (file-name) is invalid.

(S)

Cancels the command.

(O)

Check the contents of the user mapping definition file.

KAVA0867-W

An attempt to open the catalog file has failed.

English messages will be used because the catalog file could not be opened.

(S)

Continues processing.

(O)

Make sure that the catalog file exists under the /opt/jp1base/lib/nls directory. The file name is jbsrmumap.cat for the jbsrmumap command, and jbssetumap.cat for the jbssetumap command.

KAVA0869-E

The contents of the common definition are corrupted. The key\\JP1BASE key does not exist.

The common definition is invalid.

(S)

Cancels the command.

(O)

The environment is invalid. Reinstall and set up the system.

KAVA0870-E

The common definition is corrupted. The key\\JP1BASE key does not exist.

The common definition is invalid.

(S)

Cancels the command.

(O)

The environment is invalid. Reinstall and set up the system.

KAVA0871-E

OS resources are insufficient.

System resources necessary for command execution are insufficient.

(S)

Cancels the command.

(O)

Terminate other processes that are currently being executed and can be stopped, and then re-execute the command.

KAVA0873-E

Administrator privileges are required to execute the command.

The user who tried to execute the command does not have Administrators permissions.

(S)

Cancels the command.

(O)

Execute the command as a user who has Administrators permissions.

KAVA0874-E

The string option does not exist.

(S)

Cancels the command.

(O)

Recheck the specified option, and then re-execute the command.

KAVA0875-E

The option-name option is defined more than once.

(S)

Cancels the command.

(O)

Recheck the specified option, and then re-execute the command.

KAVA0876-E

The option-character option is mandatory.

(S)

Cancels the command.

(O)

Recheck the specified option, and then re-execute the command.

KAVA0877-E

The value for the option-character option is not specified.

(S)

Cancels the command.

(O)

Recheck the specified option, and then re-execute the command.

KAVA0878-E

The specified logical host does not exist. (logical host name = logical-host-name)

(S)

Cancels the command.

(O)

Recheck the logical host name specified in the -h option.

KAVA0879-E

The name of the server-side user can be from 1 to numeric-value characters.

The specified user name is too long.

(S)

Cancels the command.

(O)

Check and, if necessary, revise the specified option, and then re-execute the command.

KAVA0880-E

The logical host name logical-host-name can be from 1 to numeric-value characters.

The logical host name is too long.

(S)

Cancels the command.

(O)

Recheck the logical host name specified in the -h option.

KAVA0881-E

The host name of the server-side host can be from 1 to numeric-value characters.

The specified host name is too long.

(S)

Cancels the command.

(O)

Check and, if necessary, revise the specified option, and then re-execute the command.

KAVA0894-E

The user mapping information for the specified user (user-name) does not exist.

(S)

Terminates the command.

(O)

Check and, if necessary, revise the specified option, and then re-execute the command.

KAVA0895-E

The user mapping information for the specified user (user-name) and host (host-name) does not exist.

(S)

Terminates the command.

(O)

Check and, if necessary, revise the specified option, and then re-execute the command.

KAVA0896-I

jbsrmumap has started. (logical host name = logical-host-name)

KAVA0897-I

jbsrmumap has successfully deleted the user mapping information.

KAVA0898-I

Deletion of the user mapping data was canceled.

KAVA0899-W

An error occurred while the log directory information was being read from the common definition. The processing will now continue without log output.

Information about the log output destination could not be obtained.

(S)

Continues command processing without outputting log data.

(O)

Operation is performed normally, but the environment is invalid. Reinstall and set up the system.

KAVA0900-W

An error occurred while the log settings information was being read from the common definition. The processing will now continue without log output.

Information about the log output destination could not be obtained.

(S)

Continues command processing without outputting log data.

(O)

Operation is performed normally, but the environment is invalid. Reinstall and set up the system.

KAVA0901-E

The execution user does not have the user rights policy "Act as part of the operating system".

The execution user does not have the user rights policy "Act as part of the operating system".

(S)

Terminates command processing.

(O)

Use the OS functionality to add the user rights policy "Act as part of the operating system" to the execution user. Then, log off once, and then re-execute the command. For details about how to set the user rights, see 8.1.5(2) Assigning a user right to an OS user in the Job Management Partner 1/Base User's Guide.

KAVA0902-E

The user (OS-user-name) does not exist or the password is incorrect.

The user (OS-user-name) does not exist or the password is incorrect.

(S)

Terminates command processing.

(O)

Register OS-user-name for the OS or specify a correct password, and then re-execute the command.

KAVA0903-E

The user name (OS-user-name-or-information-search-user-name) message

User name (OS-user-name-or-information-search-user-name) message

(S)

Terminates command processing.

(O)

Check the content of the displayed message.

KAVA0906-E

The user (OS-user-name) does not have the user rights policy "Log on locally".

OS-user-name does not have the user rights policy "Log on locally".

(S)

Terminates command processing.

(O)

Use the OS functionality to give the user rights policy "Log on locally" to the OS user. For details about how to set the user rights, see 8.1.5(2) Assigning a user right to an OS user in the Job Management Partner 1/Base User's Guide.

KAVA0907-E

Root privileges are required to set mapping information for the root user.

To add the specified user mapping settings, you must have root privileges.

(S)

Terminates command processing.

(O)

Re-execute the command as a user who has root privileges.

KAVA0927-Q

Do you want to delete the user mapping?

(S)

Waits for the operator's instruction.

(O)

This is a confirmation message. Make sure that the user mapping information is to be deleted.

KAVA0930-E

An error occurred while the common definition was being accessed.

An error occurred while the common definition was being referenced.

(S)

Cancels the command.

(O)

The environment is invalid. Reinstall and set up the system.

KAVA0931-E

The operation failed because an error occurred in the read-lock procedure.

An attempt to set a read-lock on the common definition has failed.

(S)

Cancels the command.

(O)

The environment is invalid. Reinstall and set up the system.

KAVA0932-W

An error occurred while the HNTR Library was being initialized. (return code = return-code) The processing will now continue without log output.

The integrated trace log is unavailable.

(S)

Continues command processing without outputting log data.

KAVA0936-E

The common definition is corrupted.

The common definition information is corrupted.

(S)

Cancels the command.

(O)

The environment is invalid. Reinstall and set up the system.

KAVA0938-I

No user mapping information exists in the common definition.

KAVA0939-E

An error occurred while the input was being read.

An error occurred during the input processing.

(S)

Cancels the command.

(O)

Re-execute the command.

KAVA0940-E

An attempt to lock the common definition has failed. Contact the system administrator.

(S)

Cancels the command.

(O)

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

KAVA0947-E

An internal error occurred.

(S)

Cancels the command.

(O)

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

KAVA0948-W

An attempt to open the catalog file has failed.

English messages will be used because the catalog file could not be opened.

(S)

Continues processing.

(O)

Make sure that the catalog file (jbsrmumap.cat) exists under the /opt/jp1base/lib/nls directory.

KAVA0951-E (Windows)

Administrator privileges are required to execute the command.

The command must be executed by a user who has Administrators permissions.

(S)

Terminates command processing.

(O)

Log on as a user who has Administrators permissions, and then re-execute the command.

KAVA0951-E (UNIX)

Root privileges are required to execute the command.

The command must be executed by a user who has root privileges.

(S)

Terminates command processing.

(O)

Log on as a user who has root privileges, and then re-execute the command.

KAVA0952-E

No mapping information is registered.

No user mapping information is registered.

(S)

Terminates command processing.

(O)

The user mapping information is not registered or the mapping information file may be damaged. Re-execute the command for setting user mapping.

KAVA0953-E

A system error occurred during an attempt to obtain a list of server-side users.

A system error occurred during an attempt to obtain a list of JP1 users.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information that you want to register, and then contact the system administrator.

KAVA0954-E

No server-side user is registered.

No JP1 user key exists.

(S)

Terminates command processing.

(O)

The user mapping information is not registered or the mapping information file may be damaged. Re-execute the command for setting user mapping.

KAVA0955-E

A system error occurred during an attempt to obtain a list of server-side hosts.

A system error occurred during an attempt to obtain a list of server-side hosts.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information that you want to register, and then contact the system administrator.

KAVA0956-E

No server-side host key is registered.

No server host key exists.

(S)

Terminates command processing.

(O)

The user mapping information is not registered or the mapping information file may be damaged. Re-execute the command for setting user mapping.

KAVA0957-E

The primary user label does not exist.

No primary user label exists.

(S)

Terminates command processing.

(O)

The user mapping information is not registered or the mapping information file may be damaged. Re-execute the command for setting user mapping.

KAVA0958-E

A system error occurred during an attempt to obtain the primary user.

A system error occurred during an attempt to obtain the primary user.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information that you want to register, and then contact the system administrator.

KAVA0959-E

A system error occurred during an attempt to obtain a list of agent-side users.

A system error occurred during an attempt to obtain a list of OS users.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information that you want to register, and then contact the system administrator.

KAVA0960-E

No agent-side user label exists.

No OS user label exists.

(S)

Terminates command processing.

(O)

The user mapping information is not registered or the mapping information file may be damaged. Re-execute the command for setting user mapping.

KAVA0961-E

The number of arguments is incorrect.

The number of arguments is incorrect.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command.

KAVA0962-E

The -h option is defined more than once.

The -h option is defined twice.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command.

KAVA0963-E

The option name option-name cannot be recognized.

The option-name option cannot be recognized.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command.

KAVA0964-E

Memory allocation failed due to insufficient memory.

An attempt to allocate memory failed because of insufficient memory.

(S)

Terminates command processing.

(O)

Allocate sufficient memory, and then re-execute the command.

KAVA0965-I

Mapping information was successfully obtained.

The mapping information was successfully obtained.

(S)

Terminates command processing.

(O)

This message reports that processing was successful. The mapping information was successfully obtained.

KAVA0966-E (Windows)

Use a maximum of 196 characters for the logical host name.

The logical host name must be specified using no more than 196 characters.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command. no more than 63 characters can be specified for actual operation. Specify the logical host name using no more than 63 characters.

KAVA0966-E (UNIX)

Use a maximum of 255 characters for the logical host name.

The logical host name must be specified using no more than 255 characters.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command. no more than 63 characters can be specified for actual operation. Specify the logical host name using no more than 63 characters.

KAVA0967-I

jbsgetumap has started. (logical host name = logical-host-name)

jbsgetumap is started.

(S)

Started jbsgetumap.

(O)

This message reports that processing has started.

KAVA0968-E

A system error occurred during an attempt to obtain a list of server-side users.

A system error occurred during an attempt to obtain a list of JP1 users.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information that you want to register, and then contact the system administrator.

KAVA0969-E

A system error occurred during an attempt to obtain a list of server-side hosts.

A system error occurred during an attempt to obtain a list of server-side hosts.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information that you want to register, and then contact the system administrator.

KAVA0970-E

No server-side user label exists.

No JP1 user label exists.

(S)

Terminates command processing.

(O)

The user mapping information is not registered or the mapping information file may be damaged. Re-execute the command for setting user mapping.

KAVA0971-E

No server-side host label exists.

No server host label exists.

(S)

Terminates command processing.

(O)

The user mapping information is not registered or the mapping information file may be damaged. Re-execute the command for setting user mapping.

KAVA0972-E

A system error occurred during an attempt to obtain the user ID of the server-side user.

A system error occurred during an attempt to obtain the user ID of the JP1 user.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0973-E

A system error occurred during an attempt to obtain the host ID of the server-side host.

A system error occurred during an attempt to obtain the host ID of the server-side host.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information file that you want to register, and then contact the system administrator.

KAVA0974-E

The primary user label does not exist.

No primary user label exists.

(S)

Terminates command processing.

(O)

The user mapping information is not registered or the mapping information file may be damaged. Re-execute the command for setting user mapping.

KAVA0975-E

A system error occurred during an attempt to obtain the primary user.

A system error occurred during an attempt to obtain the primary user.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information that you want to register, and then contact the system administrator.

KAVA0976-E

A system error occurred during an attempt to obtain a list of agent-side users.

A system error occurred during an attempt to obtain a list of OS users.

(S)

Terminates command processing.

(O)

Use the data collection tool to collect data, collect the definition information that you want to register, and then contact the system administrator.

KAVA0977-E

No agent-side user labels exist.

No OS user labels exist.

(S)

Terminates command processing.

(O)

The user mapping information is not registered or the mapping information file may be damaged. Re-execute the command for setting user mapping.

KAVA0978-E

No mapping information is registered.

No user mapping information is registered.

(S)

Terminates command processing.

(O)

The user mapping information is not registered or the mapping information file may be damaged. Re-execute the command for setting user mapping.

KAVA0979-E

No mapping information is registered.

No user mapping information is registered.

(S)

Terminates command processing.

(O)

The user mapping information is not registered or the mapping information file may be damaged. Re-execute the command for setting user mapping.

KAVA1395-E

The blocked status of the authentication server changed, but the JP1 event could not be issued.

The status of the authentication server was changed, but the JP1 event could not be issued.

(S)

Continues processing.

(O)

Make sure that the event service is running.

KAVA1396-E

All authentication servers were blocked.

Connections to all authentication servers were blocked.

(S)

Authentication servers cannot be used from the host that issues events.

(O)

Check the cause of the authentication servers being blocked from the log output to the integrated trace log. Then make the authentication servers available.

KAVA1400-I

The authentication server (user authentication and access control) started.

The authentication server (user authentication and access control) has started.

KAVA1401-I

The authentication server (user authentication and access control) terminated normally.

The authentication server (user authentication and access control) terminated normally.

KAVA1402-E

The authentication server (user authentication and access control) terminated abnormally. (internal error code = value)

The authentication server (user authentication and access control) terminated abnormally.

(S)

Terminates registration processing on the authentication server.

(O)

Make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAVA1420-E

Memory is insufficient, so the file cannot be opened. (file name = file-name)

The file cannot be opened due to insufficient memory.

(S)

During startup: Terminates registration processing on the authentication server.

Other than during startup: Fails to perform the processing (SPMD reloading, ACL reloading, user addition, user deletion, or user password change) that requires file operations, and terminates the processing.

(O)

Increase the physical memory or the amount of memory that processes can use.

KAVA1421-E

An attempt to open a file failed because there was no access permission. (file name = file-name)

The file cannot be opened because there is no access permission.

(S)

During startup: Terminates registration processing on the authentication server.

Other than during startup: Fails to perform the processing (SPMD reloading, ACL reloading, user addition, user deletion, or user password change) that requires file operations, and terminates the processing.

(O)

Check the access permission of the file-name file and change it to the appropriate permission.

KAVA1422-E

An attempt to open a file failed because an error occurred in an OS system call. (file name = file-name, system error code = value)

The file cannot be opened because an error occurred in an OS system call.

(S)

During startup: Terminates registration processing on the authentication server.

Other than during startup: Fails to perform the processing (SPMD reloading, ACL reloading, user addition, user deletion, or user password change) that requires file operations, and terminates the processing.

(O)

Make sure that the I/O status of the OS file is stable.

KAVA1423-E

An attempt to open a file failed because the file does not exist. (file name = file-name)

The file-name file, which is needed for starting the authentication server, does not exist.

(S)

During startup: Terminates registration processing on the authentication server.

Other than during startup: Fails to perform the processing (SPMD reloading or ACL reloading) that requires file read operations, and terminates the processing.

(O)

The file-name file, which is needed for authentication server operations, does not exist. Re-install JP1/Base, or restore the definition file with file-name.model renamed file-name.

KAVA1424-E

An attempt to open a file failed. (file name = file-name)

The file-name file cannot be opened.

(S)

During startup: Terminates registration processing on the authentication server.

Other than during startup: Fails to perform the processing (SPMD reloading, ACL reloading, user addition, user deletion, or user password change) that requires file operations, and terminates the processing.

(O)

Make sure that the I/O status of the OS file is stable.

KAVA1425-E

An attempt to read a file failed because an error occurred in an OS system call. (file name = file-name, system error code = value)

The file cannot be read because an error occurred in an OS system call.

(S)

During startup: Terminates registration processing on the authentication server.

Other than during startup: Fails to perform the processing (SPMD reloading or ACL reloading) that requires file read operations, and terminates the processing.

(O)

Make sure that the I/O status of the OS file is stable.

KAVA1426-E

An attempt to read a file has failed. (file name = file-name)

The file cannot be read.

(S)

During startup: Terminates registration processing on the authentication server.

Other than during startup: Fails to perform the processing (SPMD reloading or ACL reloading) that requires file read operations, and terminates the processing.

(O)

Make sure that the I/O status of the OS file is stable.

KAVA1428-E

An attempt to write to a file has failed because an error occurred in an OS system call. (file name = file-name, system error code = value)

A write to the file is impossible because an error occurred in an OS system call.

(S)

During startup: Terminates registration processing on the authentication server.

Other than during startup: Fails to perform the authentication server processing (user addition, user deletion, or user password change) that requires file write operations, and terminates the processing.

(O)

Make sure that the I/O status of the OS file is stable.

KAVA1429-E

An attempt to write to a file has failed because disk space is insufficient. (file name = file-name)

A write to the file is impossible because there is insufficient disk space.

(S)

During startup: Terminates registration processing on the authentication server.

Other than during startup: Fails to perform the authentication server processing (user addition, user deletion, or user password change) that requires file write operations, and terminates the processing.

(O)

Check for insufficient disk space.

KAVA1430-E

An attempt to write to a file has failed. (file name = file-name)

A write to the file is impossible.

(S)

During startup: Terminates registration processing on the authentication server.

Other than during startup: Fails to perform the authentication server processing (user addition, user deletion, or user password change) that requires file write operations, and terminates the processing.

(O)

Make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAVA1431-E

An attempt to obtain the path of the definition file has failed. The authentication server will now stop.

An attempt to obtain a definition file's path from the common definition information has failed. The authentication server will now stop.

(S)

Terminates registration processing on the authentication server.

(O)

Make sure that the common definition information includes the path to the definition file.

KAVA1432-W

The definition of jp1hosts is incorrect, so the content of jp1hosts will have no effect.

The contents of jp1hosts do not take effect because the definition of jp1hosts is incorrect.

(S)

Starts the authentication server, with the definition of jp1hosts ineffective.

(O)

Make sure that the definition of jp1hosts is correct.

KAVA1433-I

The initialization of the communication base of JP1/Base was completed.

The communications base of JP1/Base was initialized successfully.

KAVA1434-W

The port number cannot be obtained, so the authentication server will be started using the default port number (20240).

The default port number (20240) will be used to start the authentication server because an attempt to obtain the port number for TCP/IP communication has failed.

(S)

Uses port number 20240 to start the authentication server.

(O)

Make sure that the definition of the services file is correct.

KAVA1435-W

The acquired port number is a number (up to 1023) that the OS has reserved, so the authentication server will be started using the default port number (20240).

The acquired port number for TCP/IP communication is a number (up to 1023) that the OS has reserved. Therefore, the default port number (20240) will be used to start the authentication server.

(S)

Uses port number 20240 to start the authentication server.

(O)

Make sure that the definition of the services file is correct.

KAVA1436-W

An invalid entry in the access permission definition file (JP1_AccessLevel) will be ignored. (entry = character-string, line num. = line-number-in-file)

The JP1_AccessLevel file contains a coding error. The definition on the line with the error will be ignored.

(S)

Ignores the incorrect definition in the JP1_AccessLevel file and starts the authentication server.

(O)

Make sure that the definition on line line-number-in-file in the JP1_AccessLevel file is correct.

KAVA1437-W

An invalid entry in the user permission definition file (JP1_UserLevel) will be ignored. (entry = character-string, line num. = line-number-in-file)

The JP1_UserLevel file contains a coding error. The definition on the line with the error will be ignored.

(S)

Ignores the incorrect definition in the JP1_UserLevel file and starts the authentication server.

(O)

Make sure that the definition on line line-number-in-file in the JP1_UserLevel file is correct.

KAVA1438-E

An attempt to initialize the communication base of JP1/Base has failed. (internal error code = value)

The authentication server will now stop because an attempt to initialize the communications base has failed.

(S)

Terminates registration processing on the authentication server.

(O)

Make sure that the common definition information is correct. Also, make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAVA1440-W

An attempt to create a message resource file name has failed. Processing will continue using the default message.

The default message will be output to the integrated trace log because the resource file name cannot be created.

(S)

After this message output, the system will output the default message to the integrated trace log.

(O)

Make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAVA1441-W

An attempt to create a message catalog file name has failed. Processing will continue using the default message.

The default message will be output to the integrated trace log because the catalog file name cannot be created.

(S)

After this message output, the system will output the default message to the integrated trace log.

(O)

Make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAVA1442-W

An attempt to load a message resource file has failed. Processing will continue using the default message.

The default message will be output to the integrated trace log because the resource file cannot be loaded.

(S)

After this message output, the system will output the default message to the integrated trace log.

(O)

Make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAVA1443-W

The message catalog file cannot be opened. Processing will continue using the default message.

The default message will be output to the integrated trace log because the catalog file cannot be opened.

(S)

After this message output, the system will output the default message to the integrated trace log.

(O)

Make sure that the catalog file (jbssessionmgr.cat) exists in the /opt/jp1base/lib/nls directory.

KAVA1460-W

An attempt to reread the user definition and the definition of the access control failed. Processing will continue using the data from before the rereading.

Reloading failed because an error occurred during reloading.

(S)

Continues processing using the data that was before reloading.

(O)

Check the access permission for the definition file on the authentication server, or whether the file exists. Also, make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAVA1461-W

An attempt to reread the definition of the access control failed. Processing will continue using the data from before the rereading.

Reloading failed because an error occurred during reloading.

(S)

Continues processing using the data from before reloading.

(O)

Check the access permission for the definition file on the authentication server, or whether the file exists. Also, make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAVA1462-E

An exception was generated in the TCP/IP communication wait processing, so the authentication server will now stop.

An exception occurred during the TCP/IP communication wait processing.

(S)

Terminates registration processing on the authentication server.

(O)

Make sure that the system resources of the OS are stable.

KAVA1464-W

The protocol analysis failed, so the request from the client will be discarded.

An attempt to analyze the communication failed.

(S)

Continues the next processing.

(O)

Check whether the communication environment has severely deteriorated. Alternatively, an error may have occurred in an internal command.

KAVA1468-I

The TCP/IP waiting-for-communications thread ended normally.

The TCP/IP waiting-for-communications thread ended normally.

KAVA1469-I

The TCP/IP waiting-for-communications thread started.

The TCP/IP waiting-for-communications thread started.

KAVA1470-I

The authentication server will be stopped by a stop request from the process management.

The authentication server started the stop processing in response to a stop request from the process management.

KAVA1471-I

Data in the authentication server will be updated by a reload request from the process management.

The authentication server started reloading.

KAVA1474-E

The authentication server will be stopped because there was an invalid request from the process management. (process management request code = value)

The authentication server will stop because there was an invalid request from the process management.

(S)

Terminates registration processing on the authentication server.

(O)

Check for invalid termination of the process management. Also, make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAVA1475-E

The start notification for the process management failed, so the authentication server will be stopped.

The authentication server will now stop because an attempt to notify the process management of startup has failed.

(S)

Terminates registration processing on the authentication server.

(O)

Check for invalid termination of the process management. Also, make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAVA1497-I

The JP1-user-name user logged in.

The user (JP1-user-name) logged in successfully.

KAVA1498-W

The JP1-user-name user password is incorrect.

Login failed because the password was incorrect.

(S)

Rejects the login attempt and waits for the next login.

(O)

Use the correct password that is registered for login.

If the password storage format on the authentication server has been changed, make sure that the JP1 user was reregistered after the format was changed.

KAVA1499-W

The user definition of the JP1-user-name user does not exist.

Login failed because the user name was not registered.

(S)

Rejects the login attempt and waits for the next login.

(O)

Use the correct user name that is registered for login.

KAVA1500-W

The user cannot be registered because the user-name (JP1-user-name) is a duplicate.

A new user attempted to register an already existing user name.

(S)

Rejects the new user's registration attempt and waits for the next registration.

(O)

Register a new user name that has not been registered.

KAVA1501-I

The JP1-user-name user was deleted from the user definition.

The specified user was deleted from the user definition.

KAVA1502-W

An attempt to delete the user JP1-user-name has failed.

The user name could not be deleted because a problem occurred with internal processing.

(S)

Rejects the deletion request and waits for the next deletion request.

(O)

Make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

KAVA1506-W

The JP1-user-name user does not exist in the user definition, so the user cannot be deleted.

The user could not be deleted because an undefined user name was specified.

(S)

Rejects the deletion request and waits for the next deletion request.

(O)

Specify a defined user name.

KAVA1507-W

The user cannot be registered because the registered number of users is the maximum number (65,535).

The user could not be registered because the number of registered users reached the upper limit (65,535).

(S)

Rejects the user registration request and waits for the next registration request.

(O)

You cannot register any more users. If you want to register new users, delete existing users.

KAVA1508-I

The JP1-user-name user was successfully registered.

The user (JP1-user-name) was successfully registered.

KAVA1509-E

The option-name option is invalid.

An invalid option is specified.

(S)

Cancels the command.

(O)

Specify the correct option, and then re-execute the command.

KAVA1510-E

An attempt to create the TCP/IP waiting-for-communications thread has failed because memory was insufficient.

An attempt to create the TCP/IP waiting-for-communications thread has failed because memory was insufficient.

(S)

Cancels creation of the TCP/IP waiting-for-communications thread.

(O)

There is not enough system memory. Terminate other applications, and then restart the service.

KAVA1511-E

An attempt to create the TCP/IP waiting-for-communications thread has failed because IP address binding failed during communication initialization processing.

An attempt to create the TCP/IP waiting-for-communications thread has failed because IP address binding failed during communication initialization processing.

(S)

Cancels creation of the TCP/IP waiting-for-communications thread.

(O)

bind processing failed during creation of a TCP/IP waiting-for-communications thread. Check for any local-host IP address that cannot be used for communication.

KAVA1512-E

An attempt to create the TCP/IP waiting-for-communications thread has failed because an error occurred in communication initialization processing.

An attempt to create the TCP/IP waiting-for-communications thread has failed because an error occurred in communication initialization processing.

(S)

Cancels creation of the TCP/IP waiting-for-communications thread.

(O)

A socket operation failed during creation of a TCP/IP waiting-for-communications thread. Restart the service.

KAVA1513-E

An attempt to create a TCP/IP waiting-for-communications thread has failed because a local host name could not be obtained.

An attempt to create a TCP/IP waiting-for-communications thread has failed because a local host name could not be obtained.

(S)

Cancels creation of the TCP/IP waiting-for-communications thread.

(O)

A local host name could not be acquired during creation of a TCP/IP waiting-for-communications thread. Check the setting of the local host name, and then restart the service.

KAVA1514-E

An attempt to create a TCP/IP waiting-for-communications thread has failed because of an error in an OS system call. (system error code = detail-code)

An attempt to create a TCP/IP waiting-for-communications thread has failed because of an error in an OS system call.

(S)

Cancels creation of the TCP/IP waiting-for-communications thread.

(O)

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

KAVA1515-E

User JP1-user-name does not exist.

JP1-user-name does not exist.

(S)

Terminates command processing.

(O)

Register the JP1 user.

KAVA1516-E

The option-name option is defined more than once.

The same option is specified more than once.

(S)

Cancels the command.

(O)

Recheck the specified option, and then re-execute the command.

KAVA1517-E

The value for the option-name option is not specified.

No value is specified for an option that requires a value.

(S)

Cancels the command.

(O)

Recheck the specified option, and then re-execute the command.

KAVA1518-E

The option-name option is mandatory.

A required option is missing.

(S)

Cancels the command.

(O)

Recheck the specified option, and then re-execute the command.

KAVA1519-E

Specify between 1 and numeric-value characters for the option-name.

The length of the specified string exceeds the limit.

(S)

Cancels the command.

(O)

Recheck the specified option, and then re-execute the command.

KAVA1520-I

A TCP/IP waiting-for-communications thread for the IP address IP-address was created.

A TCP/IP waiting-for-communications thread for IP-address was created.

(S)

Continues processing.

KAVA1521-E

An attempt to create the TCP/IP waiting-for-communications thread for the IP address IP-address has failed.

An attempt to create the TCP/IP waiting-for-communications thread for the IP address IP-address has failed.

(S)

Continues processing.

(O)

If the KAVA1527-E message was output after this message, see the corrective action shown in the KAVA1527-E message. If the KAVA1527-E message was not output, JP1/Base runs in the fallback mode. Restart the service.

KAVA1524-W

connection-sequence: authentication-server-name was successfully blocked.

authentication-server-name is blocked.

(S)

Blocks authentication-server-name and terminates processing.

(O)

The authentication server was blocked by the authentication API. Check that the blocked authentication server is operating, eliminate the problems (such as a communication error with the authentication server), and then release the authentication server from the blocked status.

KAVA1525-I

connection-sequence: authentication-server-name was successfully unblocked.

authentication-server-name is released from the blocked status.

The blocked status of authentication-server-name was released by the authentication API.

KAVA1526-W

Some attempts to create TCP/IP waiting-for-communications threads have failed. Processing will continue.

Some attempts to create TCP/IP waiting-for-communications threads have failed. Processing will continue.

(S)

Continues processing with only the created TCP/IP waiting-for-communications threads.

(O)

Some of the TCP/IP waiting-for-communications threads could not be created. Eliminate the cause of the failure, and then restart the service.

KAVA1527-E

All attempts to create TCP/IP waiting-for-communications threads have failed. The authentication server will terminate.

All attempts to create TCP/IP waiting-for-communications threads have failed. The authentication server will terminate.

(S)

Cancels the service.

(O)

No TCP/IP waiting-for-communications threads were created. Eliminate the cause of failure, and then restart the service.

KAVA1528-I

All the TCP/IP waiting-for-communications threads were created successfully.

All the TCP/IP waiting-for-communications threads were created successfully.

(S)

Continues processing.

KAVA1529-E

The number of arguments is incorrect.

An option is incorrect.

(S)

Cancels the command.

(O)

Recheck the specified options, and then re-execute the command.

KAVA1530-E

The command-name command was interrupted.

(S)

Cancels the command.

(O)

Re-execute the command as required.

KAVA1531-E

An error occurred on the authentication server.

An error occurred on the authentication server at the connection destination.

(S)

Cancels the command.

(O)

See the message output to the integrated trace log in the host where the authentication server exists, and then correct the error.

KAVA1532-E

An exception occurred in the command-name command.

This message provides internal information for checking.

(S)

Cancels the command.

(O)

Take action according to the information in the message output with this message.

KAVA1533-E

An attempt to acquire a lock on the server failed. Wait a while, and then re-execute the command.

Another command was being executed, so processing was canceled.

(S)

Cancels the command.

(O)

Wait a while, and then re-execute the command.

KAVA1534-E

Administrator privileges are required to execute the command.

The user who tries to execute the command does not have Administrators permissions.

(S)

Cancels the command.

(O)

Execute the command as a user who has Administrators permissions.

KAVA1535-E

An attempt to open the catalog file string failed.

A string resource could not be read.

(S)

Cancels the command.

(O)

The environment is invalid. Reinstall JP1/Base.

KAVA1536-E

An attempt to load the message dll string failed.

A string resource could not be read.

(S)

Cancels the command.

(O)

The environment is invalid. Reinstall JP1/Base.

KAVA1537-E

An invalid argument exists. (function = function, value = value)

This message provides internal information for checking.

(S)

Cancels the command.

(O)

Take action according to the information in the message output with this message.

KAVA1538-E

The contents of the common definition are corrupted. The key\jp1base key does not exist.

Common definition information necessary for command execution could not be obtained.

(S)

Cancels the command.

(O)

The environment is invalid. Reinstall and set up JP1/Base.

KAVA1539-E

System resources are insufficient.

System resources necessary for command execution are insufficient.

(S)

Cancels the command.

(O)

Terminate other processes that are currently being executed and can be stopped, and then re-execute the command.

KAVA1549-E

The API function API-name failed. (error number = value)

This message provides internal information for checking.

(S)

Cancels the command.

(O)

Take action according to the information in the message output with this message.

KAVA1554-E

An attempt to initialize the communications base functionality failed.

Initialization necessary for communication could not be performed.

(S)

Cancels the command.

(O)

Recheck the settings necessary for communication.

KAVA1555-E

An attempt to get the JP1_HOSTNAME label value from the common definition information failed.

The specified logical host has not been set up.

(S)

Cancels the command.

(O)

Recheck the logical host name specified in the -h option.

KAVA1556-E

An attempt to retrieve the host information for the specified logical host logical-host-name failed.

The specified logical host has not been set up.

(S)

Cancels the command.

(O)

Recheck the logical host name specified in the -h option.

KAVA1557-E

The authentication server authentication-server-name is unknown.

The specified authentication server is undefined.

(S)

Cancels the command.

(O)

Recheck the authentication server name specified in the -s option.

KAVA1558-E

The authentication server authentication-server-name is not running or not responding.

Communication with the specified authentication server could not be established.

(S)

Cancels the command.

(O)

Make sure that:

The JP1/Base service is running.

The specified authentication server exists.

The network connection is correct.

Both the host on which the command was executed and the authentication server use the same IP address version (IPv4 or IPv6).

For details about how to check the IP address version (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the Job Management Partner 1/Base User's Guide.

KAVA1559-E

The specified address family cannot be used on a TCP network.

Communication could not be initialized.

(S)

Cancels the command.

(O)

Recheck the network settings.

KAVA1565-E

The socket creation failed.

Communication could not be initialized.

(S)

Cancels the command.

(O)

Recheck the network settings.

KAVA1566-E

An attempt to bind the socket failed.

Communication could not be initialized.

(S)

Cancels the command.

(O)

Recheck the network settings.

KAVA1578-E

An attempt to change the socket to non-blocking mode failed.

The communication process could not be performed.

(S)

Cancels the command.

(O)

Recheck the network settings.

KAVA1579-E

An attempt to change the socket to blocking mode failed.

The communication process could not be performed.

(S)

Cancels the command.

(O)

Recheck the network settings.

KAVA1584-E

An attempt to send data to the authentication server failed.

The communication process could not be performed.

(S)

Cancels the command.

(O)

Recheck the network settings.

KAVA1585-E

The authentication server authentication-server-name could not be connected.

The communication process could not be performed.

(S)

Cancels the command.

(O)

Recheck the network settings.

KAVA1586-E

An attempt to receive data from the authentication server failed.

The communication process could not be performed.

(S)

Cancels the command.

(O)

Recheck the network settings.

KAVA1587-E

The logical host logical-host-name does not exist.

The specified logical host has not been set up.

(S)

Cancels the command.

(O)

Recheck the logical host name specified in the -h option.

KAVA1588-E

The user lacks permission to reference the common definition information.

An attempt to access the common definition information failed because the access permission is inadequate.

(S)

Cancels the command.

(O)

The environment is invalid. Reinstall and set up the system.

KAVA1589-E

An internal error occurred in the JP1/Base common definition library.

An error occurred during an attempt to reference the common definition library.

(S)

Cancels the command.

(O)

The environment is invalid. Reinstall and set up the system.

KAVA1594-W

A buffer area shortage occurred while a JP1/Base common definition API function jp1BsCnfGetStringValue() was executing.

Memory became insufficient.

(S)

Cancels the command.

(O)

Terminate other processes that are currently being executed and can be stopped, and then re-execute the command.

KAVA1595-E

An attempt to execute the common definition API function (jp1BsCnfGetStringValue() or jp1BsCnfGetULongValue()) has failed. (error number = value)

This message provides internal information for checking.

(S)

Cancels the command.

(O)

Take action according to the information in the message output with this message.

KAVA1597-W

The log directory information of the logical host logical-host-name was not found in the common definition. The processing will now continue without log output.

Information about the log output destination could not be obtained.

(S)

Continues command processing without outputting log data.

(O)

Operation is performed normally, but the environment is invalid. Reinstall and set up the system.

KAVA1598-W

The log settings information of the logical host logical-host-name was not found in the common definition. The processing will now continue without log output.

Information about the log output destination could not be obtained.

(S)

Continues command processing without outputting log data.

(O)

Operation is performed normally, but the environment is invalid. Reinstall and set up the system.

KAVA1599-W

An attempt to initialize the HNTR library failed. The processing will now continue without log output.

The integrated trace log is unavailable.

(S)

Continues command processing without log output.

KAVA1603-W

A message could not be acquired from the message DLL.

A message could not be acquired from the message DLL. The message DLL may be corrupted.

(S)

Continues processing without outputting the message.

(O)

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

KAVA1604-W

A message could not be acquired from the catalog file.

A message could not be acquired from the catalog file. The catalog file may be corrupted.

(S)

Continues processing without outputting the message.

(O)

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

KAVA1615-W

An invalid value is specified for JP1_BIND_ADDR. ANY is assumed and the processing will now start.

(S)

Assumes ANY binding and continues operation.

(O)

Settings must be changed when a logical host is used. Make settings for the logical host again.

KAVA1617-W

Socket creation will now be retried.

(S)

Continues processing.

KAVA1618-W

An attempt to perform communication-process failed because of a timeout.

The communication process could not be performed because of a timeout.

(S)

Cancels the command.

(O)

Check the network for errors.

KAVA1619-W

Connection to the authentication server authentication-server-name will now be retried.

(S)

Continues processing.

KAVA1623-W

An attempt to send data to the authentication server failed because of a temporary error. Sending will now be retried.

(S)

Continues processing.

KAVA1624-W

An attempt to receive data from the authentication server failed because of a temporary error. Receiving will now be retried.

(S)

Continues processing.

KAVA1625-W

The entry-name does not exist in the common definition information.

An attempt to obtain information the common definition information has failed.

(O)

Take action according to the information in the message output with this message.

KAVA1634-E

An attempt to open the user permission level file failed.

(S)

Cancels the command.

(O)

Check whether the file specified in the option is corrupted.

KAVA1635-E

An attempt to read the user permission level file failed.

(S)

Cancels the command.

(O)

Check whether the file specified in the option is corrupted.

KAVA1636-E

string is not specified in the user permission level file. (line num. = line-number)

The entries in the user permission level file are incorrect.

(S)

Cancels the command.

(O)

Correct the contents of the user permission level file according to the information in the message.

KAVA1637-E

string specified in the user permission level file has an invalid character (string, tab or space). (line num. = line-number)

The entries in the user permission level file are incorrect.

(S)

Cancels the command.

(O)

Correct the contents of the user permission level file according to the information in the message.

KAVA1638-E

string specified in the user permission level file exceeds numeric-value characters. (line num. = line-number)

The entries in the user permission level file are incorrect.

(S)

Cancels the command.

(O)

Correct the contents of the user permission level file according to the information in the message.

KAVA1639-E

The user permission level file file-name contains a syntax error. (line num. = line-number)

The entries in the user permission level file are incorrect.

(S)

Cancels the command.

(O)

Correct the contents of the user permission level file according to the information in the message.

KAVA1642-E

The line exceeds numeric-value characters. (line num. = number-of-lines)

An entry in the user permission level file is incorrect.

(S)

Cancels the command.

(O)

Correct the contents of the user permission level file according to the information in the message.

KAVA1643-W

The operating permissions settings for the following users were not registered.

The names of the JP1 users who were not registered are displayed.

KAVA1644-W

The user permission level file does not contain any operating permissions information.

(S)

Continues processing.

KAVA1645-E

The specified user name contains invalid characters (string, tab or space).

(S)

Cancels the command.

(O)

Check the specified JP1 user name.

KAVA1646-E

No operating permissions information for the user JP1-user-name exists on the authentication server.

The authentication server does not contain the permissions information about the JP1 user specified in the option.

KAVA1647-I

Setting of the operating permissions for the users on the authentication server was successful.

The command successfully set the operating permissions.

KAVA1648-I

The deletion of the operating permissions information for the user was cancelled.

The deletion of the operating permissions information for the JP1 user was cancelled.

KAVA1649-I

The deletion of the operating permissions information for the user JP1-user-name on the authentication server was successful.

The JP1 user was successfully deleted.

KAVA1652-Q

Do you want to delete the operating permissions information for the user?

(S)

Waits for the operator's instruction.

(O)

This is a confirmation message. You are requested to confirm the deletion of operating permissions information for the JP1 user.

KAVA1653-I

Acquiring and displaying of the user's operating permissions information from the authentication server was successful.

KAVA1654-E

The common definition is corrupted. The key\JP1BASE key does not exist.

The common definition is invalid.

(S)

Cancels the command.

(O)

The environment is invalid. Reinstall and set up the system.

KAVA1655-E

The SVNAME entry does not exist in the common definition information.

The common definition information is invalid.

(S)

Cancels the command.

(O)

The environment is invalid. Reinstall and set up the system.

KAVA1656-E

Invalid information was passed to the authentication server.

(S)

Cancels the command.

(O)

Check the options, and then re-execute the command.

KAVA1657-I

No registered JP1 user operating permissions information exists on the authentication server.

KAVA1658-E

The API function API-name failed.

This message provides internal information for checking.

(S)

Cancels the command.

(O)

Take action according to the information in the message output with this message.

KAVA1661-E

The command-name command is not supported on the authentication server.

The authentication server could not manipulate the request.

(S)

Cancels the command.

(O)

Check that the version of the authentication server at the connection destination is JP1/Base 07-00 or later.

KAVA1662-I

string specified in the user permission level file is invalid. (line num. = line-number)

The entries in the user permission level file are incorrect.

(S)

Cancels the command.

(O)

Correct the contents of the user permission level file according to the information in the message.

KAVA1665-E

The user permission level file file-name is invalid.

The entries in the user permission level file are incorrect.

(S)

Cancels the command.

(O)

Take action according to the information in the message output with this message.

KAVA1674-E

Execute the command from the administrator console.

This command must be executed on the administrator console.

(S)

Terminates command processing.

(O)

Re-execute the command on the administrator console.

KAVA1675-W

An error occurred during initialization of the operation log. (function-name, code = error-number) Processing will now continue without the log output.

The operation log is not output because an error occurred during initialization of the operation log.

(S)

Continues processing.

KAVA1676-W

An attempt to output the operation log has failed. (code = error-number) Processing will now continue without the log output.

Operation logs will not be output after this message because an error occurred when the operation log was output.

(S)

Continues processing without outputting log data.

KAVA1677-W

A connection to the directory server could not be established. (ds = directory-server-name, port = port-number, func = function-name, code = LDAP-error-number)

A connection to the directory server could not be established.

(S)

Rejects linkage to the directory server, and waits for the next linkage request.

(O)

Check the items below.

Note that you can use the connection check command jbschkds to check the current directory server linkage settings and the results of connection to the directory server.

Make sure that the directory server name and port number specified in the common definition are correct.

Make sure that the directory server is running.

If SSL is enabled, make sure that the environment is such that SSL can be used.

Make sure that the directory server connection settings are correct.

Make sure that the firewall settings are correct.

In the following cases, check the status of the directory server:

If the LDAP error number is 85: A timeout occurred during connection with the directory server.

If the LDAP error number is 51: The directory server is in a busy state.

KAVA1678-W

Directory server login authentication has failed. (dn = identification-name, func = function-name, code = LDAP-error-number)

Directory server login authentication has failed.

(S)

Rejects linkage to the directory server, and waits for the next linkage request.

(O)

Make sure that:

The specified user name and password are correct.

The identification name specified in the common definition is correct.

The status of the user account on the directory server is correct.

Make sure that the account is valid.

Make sure that the account has not expired.

Make sure that the account is not locked out.

Make sure that the password has not expired.

Make sure that the User must change password at next login setting is not specified for the user.

KAVA1679-W

An error occurred during directory server login authentication. (dn = identification-name, func = function-name, code = LDAP-error-number)

An error occurred during directory server login authentication.

(S)

Rejects linkage to the directory server, and waits for the next linkage request.

(O)

If the LDAP error number is 90:

Memory is insufficient. Make sure that there are enough resources on the directory server.

If the LDAP error number is not 90:

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

KAVA1687-W

An attempt to acquire the directory server linkage information has failed. (label = label-name, code = error-number)

An attempt to acquire the directory server linkage information in the common definition has failed.

(S)

Rejects linkage to the directory server, and waits for the next linkage request.

(O)

The common definition information might contain incorrect settings. Set the correct directory server linkage information in the common definition.

KAVA1688-W

A value in the directory server linkage information is invalid. (label = label-name, value = value)

The directory server linkage information in the common definition contains an invalid value.

(S)

Rejects linkage to the directory server, and waits for the next linkage request.

(O)

The label name in the common definition contains an error. Correct the error.

KAVA1690-W

Login authentication cannot be performed on the directory server because directory server linkage is disabled.

Login authentication cannot be performed on the directory server because directory server linkage is disabled.

(S)

Rejects linkage to the directory server, and waits for the next linkage request.

(O)

Check the directory server linkage settings and the specified user name, and then re-execute the command.

KAVA1691-W

An attempt to authenticate the linkage user JP1-user-name has failed.

An attempt to authenticate linkage user has failed.

(S)

Rejects linkage to the directory server, and waits for the next linkage request.

(O)

Take action according to the information in the message output with this message.

KAVA1692-I

The hash level is numeric-value.

The hash level of the authentication server is numeric-value.

KAVA1693-E

Root privileges or JP1/Base administrator privileges are required to execute the command.

(S)

Terminates command processing.

(O)

Re-execute the command as a user who has root privileges or JP1/Base administrator privileges.

KAVA1694-W

Authentication of the information-search user failed. (dn = identification-name, func = function-name, code = LDAP-error-number)

An attempt to authenticate the information-search user failed.

(S)

Rejects linkage to the directory server, and waits for the next linkage request.

(O)

Make sure that:

The identification name specified in the common definition is correct.

The password of the information-search user registered in the password management system is correct.

The status of the user account on the directory server is correct.

- Make sure that the account is valid.

- Make sure that the account has not expired.

- Make sure that the account is not locked out.

- Make sure that the password has not expired.

- Make sure that the password contains at least one character.

- Make sure that the User must change password at next login setting is not specified for the user.

2.3 Setup messages (KAVA1700 to KAVA1946)

KAVA1700-E

Enter a logical host name.

The -h option has not specified a logical host name.

(S)

Terminates processing without setting the authentication server.

(O)

Check whether the -h command option specifies a logical host name.

KAVA1701-E

option-character is an invalid switch.

There is an invalid option character.

(S)

Terminates processing without setting the authentication server.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command.

KAVA1702-E

Enter an authentication server.

An authentication server is not specified.

(S)

Terminates processing without setting the authentication server.

(O)

Check whether an authentication server host name is specified.

KAVA1703-I

Setup of the authentication server (authentication-server-name) finished.

The setting of an authentication server has finished.

(S)

The authentication server was set successfully. Terminates processing.

(O)

This message reports that the authentication server was set successfully.

KAVA1704-E

Setup of the authentication server (authentication-server-name) failed.

An attempt to setup an authentication server has failed.

(S)

Fails to set up the authentication server. Terminates processing.

(O)

The setup of the authentication server has failed. Make sure that data can be written to the /var/tmp directory and that JP1/Base has been installed correctly. Then, set up the authentication server again.

KAVA1705-I

Setup of the primary authentication server (authentication-server-name) and secondary authentication server (authentication-server-name) finished.

Setting the primary authentication server and the secondary authentication server has finished.

(S)

The primary authentication server and the secondary authentication server were set successfully. Terminates processing.

(O)

This message reports that the primary authentication server and the secondary authentication server were set successfully.

KAVA1706-E

Setup of a primary authentication server (authentication-server-name) and a secondary authentication server (authentication-server-name) failed.

An attempt to set up the primary authentication server and the secondary authentication server has failed.

(S)

Fails to set up the primary authentication server and the secondary authentication server. Terminates processing.

(O)

This message reports that the primary authentication server and the secondary authentication server could not be set. Make sure that data can be written to the /var/tmp directory and that JP1/Base has been installed correctly. Then, set up the authentication server again.

KAVA1707-E

The number of arguments is incorrect.

The number of arguments is invalid.

(S)

Terminates processing without setting the authentication server.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command.

KAVA1708-E

The -h option is specified more than once.

The -h option is specified more than once.

(S)

Terminates processing without setting the authentication server.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command.

KAVA1709-E

The logical host name can be up to 255 characters long.

The logical host name must be specified using no more than 255 characters.

(S)

Terminates processing without setting the authentication server.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command. no more than 63 characters can be specified for actual operation. Specify the logical host name using no more than 63 characters.

KAVA1710-E

An authentication server name can be up to 255 characters long.

The host name of the authentication server must be specified using no more than 255 characters.

(S)

Terminates processing without setting the authentication server.

(O)

The command specification contains a syntax error. Correct the option error, and then re-execute the command.

KAVA1711-E

Specify the -h option as the first argument.

The -h option must be specified in the first argument.

(S)

Terminates processing without setting the authentication server.

(O)

The command specification contains a syntax error. Correct the error in the definition file, and then re-execute the command.

KAVA1712-E

Deletion of a secondary authentication server failed.

The system failed to delete the secondary authentication server.

(S)

The secondary authentication server could not be deleted. Terminates processing.

(O)

Although the primary authentication server was set successfully, the setting for the secondary authentication server is old. Check that the host name of the authentication server is correct and that JP1/Base is correctly installed, and then set the authentication server.

KAVA1713-W

Initialization of the blocking status storage file failed.

The system failed to initialize the blocked status file.

(S)

The blocked status file could not be initialized. Terminates processing.

(O)

Although the primary authentication server and the secondary authentication server were set successfully, the settings in the blocked status file are old. Use the jbslistsrv command to check the blocked status, and then use the jbsunblockadesrv command to release the blocked status.

KAVA1714-E

An authentication server name is invalid.

An invalid character is set in the authentication server name.

(S)

Terminates processing without setting the authentication server.

(O)

The command specification contains a syntax error. Check whether the authentication server name contains an invalid character (space or tab), and then re-execute the command.

KAVA1715-E

The same name of an authentication server is specified more than once.

The same authentication server name is set more than once.

(S)

Terminates processing without setting the authentication server.

(O)

The command specification contains a syntax error. Check whether the same authentication server name is set for the primary authentication server and the secondary authentication server, and then re-execute the command.

KAVA1716-E

Administrator privileges are required to execute the command.

To execute the command, you must be logged on as a user who has Administrators permissions.

(S)

Terminates command processing.

(O)

Only a user who logged on as a user who has Administrators permissions can execute the command. Execute the command as a user who has Administrators permissions.

KAVA1717-E

Execute the command from the administrator console.

This command must be executed on the administrator console.

(S)

Terminates command processing.

(O)

Re-execute the command on the administrator console.

KAVA1718-E

A command argument is invalid.

A command argument is invalid.

(S)

Terminates command processing.

(O)

An unrecognizable option is specified, the same option is specified twice, or no argument is specified in an option that requires an argument. Make sure that the argument specification is correct.

KAVA1719-E

The logical host name can be up to 196 characters long.

The logical host name must be specified by using no more than 196 characters.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Correct the error in the definition file, and then re-execute the command. We recommend that you specify the logical host name by using no more than 63 characters for actual operation.

KAVA1720-E

An authentication server name can be up to 255 characters long.

The host name of the authentication server must be specified by using no more than 255 characters.

(S)

Terminates command processing.

(O)

The command specification contains a syntax error. Make sure that the specified authentication server name does not exceed 255 characters.

KAVA1721-E

The logical host logical-host-name does not exist.

The specified logical host does not exist.

(S)

Terminates command processing.

(O)

Make sure that the specified logical host name is correct and that the value in the JP1_HOSTNAME environment variable is correct, and then re-execute the command.

KAVA1722-E

Failed to create the shared directory.

An attempt to create a shared directory failed.

(S)

Terminates command processing.

(O)

Make sure that you can access the specified shared directory.

KAVA1723-E

Failed to set up logical host logical-host-name.

An attempt to set up the logical host failed.

(S)

Terminates command processing.

(O)

Make sure that JP1/Base is installed correctly, and then set up the logical host again.

KAVA1724-I

Setup of the logical host logical-host-name finished.

The setup of the logical host finished.

KAVA1725-I

Setup of the authentication server (authentication-server-name) finished.

The setup of the authentication server finished.

KAVA1726-I

Setup of the primary authentication server (authentication-server-name) and secondary authentication server (authentication-server-name) finished.

The setup of the primary authentication server and secondary authentication server finished.

KAVA1727-E

Setup of the authentication server (authentication-server-name) failed.

The setup of the authentication server failed.

(S)

Terminates command processing.

(O)

Make sure that JP1/Base is installed correctly, and then set up the authentication server again.

KAVA1728-E

Setup of a primary authentication server (authentication-server-name) and a secondary authentication server (authentication-server-name) failed.

An attempt to set up the primary authentication server and secondary authentication server failed.

(S)

Terminates command processing.

(O)

Make sure that JP1/Base is installed correctly, and then set up the authentication servers.

KAVA1729-E

Deletion of a secondary authentication server failed.

An attempt to delete the secondary authentication server failed.

(S)

Terminates command processing.

(O)

Although the primary authentication server was set successfully, the setting for the secondary authentication server is old. Check that the host name of the authentication server is correct and that JP1/Base is correctly installed, and then delete the authentication server.

KAVA1730-W

Initialization of the blocking status storage file failed.

An attempt to initialize the blocked status storage file has failed.

(S)

Terminates command processing.

(O)

Although the primary authentication server and the secondary authentication server were set successfully, the settings in the blocked status storage file are old. Use the jbslistsrv command to check the blocked status, and then use the jbsunblockadesrv command to release the blocked status.

KAVA1731-E

An already-used authentication server name was specified.

The specified authentication server name is already used.

(S)

Terminates command processing.

(O)

Make sure that the specified authentication server name is not used, and then re-execute the command.

KAVA1732-I

The command-name command has started.

The command-name command has started.

KAVA1733-E

Deletion of the authentication server failed.

An attempt to delete the authentication server failed.

(S)

Terminates command processing.

(O)

Make sure that the host name of the authentication server is correct and that JP1/Base is correctly installed, and then delete the authentication server.

KAVA1734-E

Memory is insufficient.

Memory is insufficient.

(S)

Terminates command processing.

(O)

Stop unnecessary processes, and then re-execute the command.

KAVA1735-E

An error occurred during access to the common definition, so processing cannot continue.

Processing cannot continue because an error occurred during access to the common definition.

(S)

Terminates command processing.

(O)

Make sure that JP1/Base has stopped, and then re-execute the command.

KAVA1736-E

An internal error has occurred. Acquire the relevant data, and then contact the system administrator.

An internal error has occurred.

(S)

Terminates command processing.

(O)

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

KAVA1737-I

The authentication server was successfully deleted.

The authentication server was successfully deleted.

KAVA1738-E

This command is not execute command-name at the same time.

An attempt was made to start commands that cannot be started at the same time.

(S)

Terminates command processing.

(O)

Wait until the indicated command finishes, and then re-execute the command.

KAVA1739-E

The authentication server setup stopped because JP1/Base activate now.

The command processing was canceled because an attempt was made to change the authentication server setting from the local host to a remote host or vise versa while JP1/Base is being activated.

(S)

Terminates command processing.

(O)

Stop JP1/Base, or re-execute the command with the -f option specified.

KAVA1740-E

Do not execute by secondary server.

An attempt was made to execute a command that cannot be executed on the secondary node on that node.

(S)

Terminates command processing.

(O)

Execute the command on the primary node.

KAVA1741-E

Deletion of logical host logical-host-name failed.

An attempt to delete the logical host failed.

(S)

Terminates command processing.

(O)

Make sure that the specified host name is correct and that JP1/Base is installed correctly, and then re-execute the command.

KAVA1742-I

The logical host logical-host-name was successfully deleted.

The logical host was successfully deleted.

KAVA1743-E

The specified authentication server authentication-server-name does not exist.

The specified authentication server does not exist.

(S)

Terminates command processing.

(O)

Make sure that the specified authentication server name is correct, and then re-execute the command.

KAVA1791-E

An attempt to start the administrator console has failed. (function = function-name, error code = error-code)

An attempt to start the administrator console has failed.

(S)

Stops the administrator console.

(O)

This problem might have occurred because there are not sufficient system resources such as virtual memory and desktop heap. Allocate sufficient system resources by stopping unnecessary applications or reducing the system resource requirements for the applications that use too many system resources, and then restart the administrator console.

If the problem is not solved, record the function name and error code, use the data collection tool to collect data, and then contact the system administrator.

KAVA1792-E

The user who doesn't belong to the Administrators group cannot start.

The user who does not belong to the Administrators group cannot start the administrator console.

(S)

Stops the administrator console.

(O)

Start the administrator console as a user that belongs to the Administrators group.

KAVA1792-E

The user who doesn't belong to the Administrators group cannot start.

Users who are not members of the Administrators group cannot start the administrator console.

(S)

Stops the administrator console.

(O)

Start the administrator console as a member of the Administrators group.

KAVA1820-E

Root privileges are required to execute the command.

Execute the command as root.

(S)

Cancels the command.

(O)

Re-execute the command as a user who has root privileges.

KAVA1821-I

The setting that allows JP1/Base administrators to perform operations has been enabled.

(JP1-administrators-group, gid=group-ID, logical host name=logical-host-name).

The setting that allows JP1/Base administrators to perform operations was enabled on the indicated host.

KAVA1822-E

An internal error occurred during JP1/Base setup.

An error occurred during setup automatically performed by JP1/Base when an overwrite installation was performed or a patch was applied.

(S)

Stops performing the overwrite installation or applying the patch.

(O)

Review the OS resources, and then re-execute the overwrite installation or re-apply the patch.

KAVA1823-I

JP1/Base can now be used by the JP1 administrators group.

(JP1-administrators-group, gid=group-ID, logical host name=logical-host-name).

JP1/Base can now be used by the indicated JP1 administrators group.

KAVA1824-I

The JP1 administrators group has not been set up.

No JP1 administrators group has been set.

KAVA1825-E

The logical host (logical-host-name) is not set up to allow JP1/Base administrators to perform operations.

JP1/Base administrators are allowed to perform operations on physical hosts, but are not allowed on a logical host.

(S)

Terminates command processing.

(O)

Mount the shared directory, and then execute the jbssetadmingrp command with the -s option specified. JP1/Base administrators will be able to perform operations on the logical host.

KAVA1826-Q

Do you want to set up the JP1 administrators group? (JP1-administrators-group, gid=group-ID)? (Y/N)

(S)

Waits for the operator's instruction.

(O)

This is a confirmation message. The setting that allows JP1/Base administrators to perform operations will be enabled. Note that if you respond with Y, you can no longer undo the operation.

KAVA1827-I

Processing was canceled.

The response to the KAVA1826-Q message was not Y. Execution of the jbssetadmingrp command will be terminated.

KAVA1828-E

The OS group (OS-group-name) specified for the JP1 administrators group is not registered in the OS.

The OS group specified for the JP1 administrators group has not been registered in the OS.

(S)

Terminates command processing.

(O)

Specify a correct OS group, and re-execute the command.

KAVA1829-W

An attempt to allow JP1/Base administrators to perform operations on the logical host (logical-host-name) failed because the shared directory is not mounted.

The logical host settings for the primary node were not specified because the shared directory was not mounted.

(S)

Continues command processing.

(O)

If the command was executed with the -s option on the primary node, make sure that the shared directory for the logical host is mounted, and then re-execute the command. If the command was executed on the secondary node, you can ignore this message.

KAVA1830-W

The system could not determine whether the setting that allows JP1/Base administrators to perform operations is enabled for the logical host (logical-host-name) because the shared directory is not mounted.

Because the shared directory has not been mounted, whether the setting that allows JP1/Base administrators to perform operations is allowed on the logical host cannot be determined.

(S)

Continues command processing.

(O)

If the command was executed with the -v option on the primary node, make sure that the shared directory for the logical host is mounted, and then re-execute the command. If the command was executed on the secondary node, you can ignore this message.

KAVA1832-E

An attempt to enable the setting that allows JP1/Base administrators to perform operations failed.

An attempt to enable the setting that allows JP1/Base administrators to perform operations failed.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA1833-E

Memory is insufficient.

(S)

Terminates command processing.

(O)

Stop unnecessary processes, and then re-execute the command.

KAVA1834-E

The command cannot be used while JP1/Base is running.

You cannot specify options other than the -v option when executing the jbssetadmingrp command while JP1/Base is running.

(S)

Terminates command processing.

(O)

Stop JP1/Base, and then re-execute the command.

KAVA1835-E

An unexpected error occurred. (maintenance-information)

An unexpected error occurred.

(S)

Terminates command processing.

(O)

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

KAVA1837-E

The specified option contains an error.

The command contains an option error.

(S)

Terminates command processing.

(O)

Specify correct options, and re-execute the command.

KAVA1850-W

This platform is not supported. Do you want to stop installation?

You cannot install JP1/Base on this OS.

(S)

Yes: Cancels processing.

No: Continues processing.

(O)

Install JP1/Base in a supported OS.

KAVA1851-E

This platform is not supported. Installation will be stopped.

You cannot install JP1/Base on this OS.

(S)

Cancels processing.

(O)

Install JP1/Base in a supported OS.

KAVA1852-E

The user does not have administrator permissions. The user must have administrator permissions to install this product.

To perform installation, you must be logged on as a user who has Administrators permissions.

(S)

Cancels processing.

(O)

Install JP1/Base from an account with Administrators permissions.

KAVA1853-E

An attempt to register the common definition information has failed. Reboot the machine, and then try installation again.

The common definition information could not be registered.

(S)

Cancels processing.

(O)

Restart the computer, and then try installation again.

KAVA1854-E

An attempt to copy the files has failed. Reboot the machine, and then try installation again.

The files could not be copied.

(S)

Cancels processing.

(O)

Stop unnecessary services, and then try installation again.

KAVA1855-W

An attempt to delete the files has failed. After the installation has completed, delete the following files. Undeleted files : file-names

The files could not be deleted.

(S)

Continues processing.

(O)

Delete the files after installation is complete.

KAVA1856-E

An attempt to open the files has failed. Reboot the machine, and then try installation again. Undeleted files : file-names

The files could not be opened.

(S)

Cancels processing.

(O)

Stop unnecessary services, and then try installation again.

KAVA1857-E

The files could not be accessed. Reboot the machine, and then try installation again. Unaccessed files : file-names

The files could not be accessed.

(S)

Cancels processing.

(O)

Stop unnecessary services, and then try installation again.

KAVA1858-E

The installation will be stopped because the information necessary for installation is insufficient. Reboot the machine, and then try installation again.

Information required for installation could not be obtained.

(S)

Cancels processing.

(O)

Stop unnecessary services, and then try installation again.

KAVA1859-E

The information could not be set in the registry. Reboot the machine, and then try installation again.

The information could not be set in the registry.

(S)

Cancels processing.

(O)

Stop unnecessary services, and then try installation again.

KAVA1860-W

An attempt to register the services into the SERVICES file has failed. Unregistered services : service-name port-number protocol

The service could not be registered in the services file.

(S)

Continues processing.

(O)

After installation is complete, register the service indicated in the dialog box in the services file.

KAVA1861-W

An attempt to set the Path environment variable has failed. Unset value : path-name

The environment variable PATH could not be set.

(S)

Continues processing.

(O)

After installation is complete, register the value indicated in the dialog box in the environment variable PATH.

KAVA1862-E

Files necessary for installation cannot be found. Aquire the relevant data, and then contact the system administrator.

A file or files required for installation could not be found.

(S)

Cancels processing.

(O)

Collect data, and then contact the system administrator.

KAVA1863-E

An attempt to register the service has failed. Reboot the machine, and then try installation again.

The service could not be registered.

(S)

Cancels processing.

(O)

Restart the computer, and then try installation again.

KAVA1864-E

An attempt to create the file has failed. Reboot the machine, and then try installation again.

The file could not be created.

(S)

Cancels processing.

(O)

Stop unnecessary services, and then try installation again.

KAVA1865-W

An attempt to delete the services from the SERVICES file has failed. Undeleted services : service-name

The service could not be deleted from the services file.

(S)

Continues processing.

(O)

After installation is complete, delete the service indicated in the dialog box from the services file.

KAVA1866-W

An attempt to delete the Path environment variable has failed. Undeleted value : path-name

The environment variable PATH could not be deleted.

(S)

Continues processing.

(O)

After installation is complete, delete the value indicated in the dialog box from the environment variable PATH.

KAVA1867-W

An attempt to delete the program Folder has failed. After the installation has completed, delete the following program folder. Undeleted folder : folder-name

The program folder could not be deleted.

(S)

Continues processing.

(O)

Wait until installation is complete, and then delete the folder.

KAVA1890-E

Memory is insufficient. Stop all unnecessary applications, and then try installation again.

There is not enough memory.

(S)

Cancels processing.

(O)

Stop unnecessary applications, and then try installation again.

KAVA1891-E

An internal error has occurred. Acquire the relevant data, and then contact the system administrator.

An internal error occurred.

(S)

Cancels processing.

(O)

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

KAVA1892-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 because there were not enough resources.

(S)

Cancels processing.

(O)

Confirm that there are enough system resources.

Reacquire product information after the insufficient-resources issue has been resolved. If the problem cannot be resolved, use the data collection tool to collect data, and then contact the system administrator.

KAVA1893-E

The product information could not be acquired because the environment is invalid. (Detailed information: function-name, return-value)

Acquisition of product information failed because the environment is invalid

(S)

Cancels processing.

(O)

Confirm that there are no failures in the system.

Uninstall, reinstall, and then re-acquire the program information.

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

KAVA1898-E

The user might have performed an incorrect operation. Perform setup by executing HCD_INST.EXE.

An incorrect operation may have been performed.

(S)

Cancels processing.

(O)

Perform installation by executing HCD_INST.EXE.

KAVA1899-E

The disk might be corrupt. Contact your technical support representative.

The disk may be corrupt.

(S)

Cancels processing.

(O)

Contact the supplier.

KAVA1902-E

Found "library-name".

Installation error: JP1/Base

Error code: 0B30 0005

Reason: C++ Runtime Libraries are already installed.

The runtime library of Optimizing C++ is already installed in the system.

(S)

Continues processing without installing the library.

(O)

Although the runtime library of Optimizing C++ is already installed in the system where you attempted to install JP1/Base, the runtime library may not be compatible with the one used for JP1/Base.

Delete the library, and then install JP1/Base.

KAVA1940-I

JP1/Base setup has started.

The JP1/Base setup started.

(S)

Starts JP1/Base setup.

(O)

This message reports that JP1/Base setup has started.

KAVA1943-E

An attempt to register data of file-name has failed.

An attempt to register the definition information defined by file-name has failed.

(S)

Stops setup.

(O)

Make sure that JP1/Base is installed correctly. Then perform setup again.

KAVA1944-I

All data was successfully registered.

The definition information was registered successfully.

(S)

Continues setup.

(O)

This message reports that all the definition information was registered successfully.

KAVA1946-I

JP1/Base setup has finished.

Setup of JP1/Base has finished.

(S)

Setup has terminated normally.

(O)

This message reports that setup finished successfully.

2.4 Event service messages (KAVA2000 to KAVA3918)

KAVA2000-E

IMEvtgw cannot receive SNMPTrap.

The SNMP trap converter cannot receive SNMP traps.

(S)

Reconnects NNM and restarts the SNMP trap converter.

(O)

Check that the SNMP trap converter is operating.

KAVA2001-I

An environment compatible with Job Management Partner 1/Integrated Manager events was created.

An environment compatible with JP1/IM events has been created.

KAVA2002-I

An environment compatible with Job Management Partner 1/Integrated Manager events was deleted.

An environment compatible with JP1/IM events has been deleted.

KAVA2003-W

An environment compatible with Job Management Partner 1/Integrated Manager events does not exist.

An environment compatible with JP1/IM events has not been created.

(S)

Cancels deletion of the environment compatible with JP1/IM events.

KAVA2004-E

There is an error in the specified option.

The command option is specified incorrectly.

(S)

Terminates command processing.

(O)

Correct the error, and then re-execute the command.

KAVA2006-I

The specified event server was registered. (service = service-display-name)

The specified event server has been registered.

KAVA2007-I

The specified event server has been deleted. (service = service-display-name)

The specified event server has been deleted.

KAVA2008-E

The specified event server name is too long.

The specified event server name is too long.

(S)

Terminates command processing.

(O)

Correct the event server name, and then re-execute the command.

KAVA2009-E

An attempt to obtain the name of the local host has failed. (line = maintenance-code, code = maintenance-code)

An attempt to obtain the name of the local host has failed. The host name may not be set.

(S)

Terminates command processing.

(O)

Check that the host name is set. If the host name is not set, set it.

KAVA2010-E

A file cannot be found. (file = file-name)

The file cannot be found.

(S)

Terminates command processing.

(O)

Re-install JP1/Base.

KAVA2011-W

The specified event server already exists.

The specified event server already exists.

KAVA2012-E

The specified event server name is invalid.

The specified event server name is invalid.

(S)

Terminates command processing.

(O)

Correct the event server name, and then re-execute the command.

KAVA2013-E

The specified event server cannot be registered. (line = maintenance-code, code = maintenance-code)

The event server cannot be registered.

(S)

Terminates command processing.

(O)

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

KAVA2014-E

An attempt to register the message DLL has failed. (line = maintenance-code, code = maintenance-code)

An attempt to register the message DLL has failed.

(S)

Terminates command processing.

(O)

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

KAVA2015-E

The specified event server cannot be deleted. (line = maintenance-code, code = maintenance-code)

The event server cannot be deleted.

(S)

Terminates command processing.

(O)

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

KAVA2016-W

The specified event server has already been marked for deletion.

The specified event server is already marked for deletion. The event server will be deleted when the system is restarted.

(S)

Terminates command processing.

(O)

Restart the system.

KAVA2017-E

The specified event server does not exist.

The specified event server does not exist.

(S)

Terminates command processing.

(O)

Correct the event server name, and then re-execute the command.

KAVA2018-E

An error occurred during the building or deletion of a compatible environment. (maintenance-information)

An error occurred during compatible environment construction processing or deletion processing.

(S)

Terminates command processing.

(O)

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

KAVA2101-E

Event registration failed. (function = function, code = detail-code).

An error occurred during event registration for the SNMP trap converter.

(S)

Aborts the JP1 event data that caused the error, and continues processing.

(O)

If detail-code is not 40, contact the system administrator.

If detail-code is 40 (cannot connect to the event service), make sure that:

The event service is running. (You can check this by using the jevstat command.)

The service name specified for the ports parameter as an application port in the event server settings file (conf) is set in the services file.

Communication is possible between the address specified for the ports parameter in the event server settings file (conf) and the addresses specified for the server and client parameters in the API settings file.

When JP1/Base is operating with the ANY binding method on a host that uses IPv6 addresses, the IPv6 address of the local host is set in the jp1hosts2 information.

KAVA2102-I

Event registration is now possible.

Event registration is now possible for the SNMP trap converter.

KAVA2103-I

number event(s) were deleted during an event registration error.

Some JP1 events were aborted when an event registration occurred in the SNMP trap converter.

KAVA2104-I

IMEvtgw can now receive SNMP traps.

It is now possible to receive SNMP traps because the SNMP trap converter is reconnected to NNM.

KAVA2105-W

The filter specification is invalid. (file = file-name, line = line-number)

A filter defined for the SNMP trap converter is invalid.

(S)

Continues processing.

(O)

Correct the filter specification, and then execute the reload command (xnmevents -event).

KAVA2106-E

OVsnmpOpen has Failed. (error-message)

A session could not be established with NNM.

(S)

Stops the SNMP trap converter.

(O)

Eliminate the cause of the error, and then execute the command to start the SNMP trap converter (ovstart IMEvtgw).

KAVA2107-E

IMEvtgw cannot start because there is an error in the action definition file. (file = file-name, line = line-number, token = invalid-string)

The SNMP trap converter cannot start because there is an error in the action definition file.

(S)

Stops the SNMP trap converter.

(O)

Correct the action definition file, and then execute the command to start the SNMP trap converter (ovstart IMEvtgw).

KAVA2108-E

Message editing failed because acquisition of $variable information failed. (function = function, code = detail-code, message = message)

The message could not be edited because information could not be acquired from the $ variable.

(S)

Registers the converted JP1 event message without expanding the $ variable.

(O)

Eliminate the cause of the error that prevented the acquisition of $ variable information.

KAVA2109-E

Acquisition of action definition file information has failed. (function = function, code = detail-code)

Action definition file information could not be acquired.

(S)

Stops the SNMP trap converter.

(O)

Eliminate the cause of the failure to acquire action definition file information.

KAVA2110-E

Acquisition of filter file information has failed. (function = function, code = detail-code)

Filter file information could not be acquired.

(S)

Stops the SNMP trap converter.

(O)

Eliminate the cause of the failure to acquire filter file information.

KAVA2111-W

Part of the specified source name became invalid. (file = file-name, line = line-number)

Part of the specified source name was invalid.

(S)

Continues processing.

(O)

Make sure that the length of a source-attribute conditional statement contained in the snmp-filter statement in the action definition file does not exceed 1,023 bytes.

KAVA3000-I

The Event Log Trap service will now start.

The event log trap service is starting.

KAVA3001-I

The Event Log Trap service will now stop.

The event log trap service is stopping.

KAVA3002-E

The Event Log Trap service stopped due to error that prevents processing. (function = function, code = detail-code)

An unrecoverable error occurred during event log trapping.

(S)

Stops the event log trap service.

(O)

Make sure that sufficient system resources and available memory are allocated.

If the system resources and memory are insufficient, remove the cause of the error, and then restart the event log trap service.

If the problem is not solved, use the data collection tool to collect data, and then contact the system administrator.

KAVA3003-E

The Event Log Trap Service cannot start because there is an error in the action definition file. (line = line-number, token = invalid-string)

The event log trap service cannot start because of an invalid setting in the action definition file.

(S)

Stops the event log trap service.

(O)

Correct the invalid setting, and then re-execute the event log trap service.

If the action definition file was created using Unicode, this message might appear. Re-create the action definition file by using the language specified in the Language for non-Unicode programs section on the Advanced page in the dialog box that is opened by double-clicking Regional and Language Options in the Windows Control Panel. Then, restart the event log trapping service.

KAVA3004-E

A connection to the event server cannot be established.

The event log trap service cannot start because the event service is not running.

(S)

Stops the event log trap service.

(O)

Re-execute the JP1/Base Eventlog Trap service after you have made sure that:

The event service is running. (You can check this by using the jevstat command.)

The service name specified for the ports parameter as an application port in the event server settings file (conf) is set in the services file.

Communication is possible between the address specified for the ports parameter in the event server settings file (conf) and the addresses specified for the server and client parameters in the API settings file.

When JP1/Base is operating with the ANY binding method on a host that uses IPv6 addresses, the IPv6 address of the local host is set in the jp1hosts2 information.

KAVA3005-E

The action definition file cannot be opened.

An attempt to open the action definition file failed.

(S)

Stops the event log trap service.

(O)

The action definition file does not exist or may be corrupted. Create the action definition file, and then restart the event log trap service.

KAVA3006-E

Memory is insufficient.

Memory is insufficient for the event log trap service.

(S)

Stops the event log trap service.

(O)

Terminate other programs that are using memory, and then restart the event log trap service.

KAVA3008-I

Reloading of the Event Log Trap has finished.

Reloading the Event Log Trap has finished.

KAVA3009-E

The Event Log Trap cannot be reloaded because there is an error in the action definition file. (line num. = line-number, token = invalid-string)

The action definition file for the Event Log Trap contains incorrect specifications, so the Event Log Trap could not be reloaded.

(S)

Terminates command processing.

(O)

Correct the errors in the action definition file, and then re-execute the command.

If the action definition file was created using Unicode, this message might appear. Re-create the action definition file by using the language specified in the Language for non-Unicode programs section on the Advanced page in the dialog box that is opened by double-clicking Regional and Language Options in the Windows Control Panel. Then, re-execute the command.

KAVA3010-E

The Event Log Trap service is not running.

Command processing was terminated because the Event Log Trap service was inactive.

(S)

Terminates command processing.

(O)

Start the Event Log Trap service.

KAVA3011-E

An error occurred in the connection with the Event Log Trap management service.

Command processing was terminated because an error occurred at connection to the Event Log Trap service.

(S)

Terminates command processing.

(O)

Make sure that the Event Log Trap service is active.

KAVA3013-E

The user lacks operator permissions to execute this command.

Only a user with operator privileges (Administrators group permissions) can execute this command.

(S)

Terminates command processing.

(O)

Re-execute the command as a user who has operator privileges.

KAVA3014-E

An attempt to reload the Event Log Trap has failed.

The Event Log Trap could not be reloaded.

(S)

Terminates command processing.

(O)

Determine the cause of the error from the event log or the integrated trace log.

KAVA3015-E

An I/O error occurred. (function = function, code = maintenance-code)

The command terminated due to an I/O error.

(S)

Terminates command processing.

(O)

Make sure that:

Sufficient system resources and available memory are allocated.

The event log is not damaged. (Make sure it can be viewed from the event viewer.)

If system resources and memory are insufficient or the event log is damaged, remove the cause of the error, and then restart the event log trap service.

If the problem is not solved, use the data collection tool to collect data, and then contact the system administrator.

KAVA3016-E

An attempt to reload the Event Log Trap failed due to an error that prevents processing.

The Event Log Trap could not be reloaded because an unrecoverable error occurred.

(S)

Terminates command processing.

(O)

Determine the cause of the error from the event log or the integrated trace log.

KAVA3017-I

Event registration will now be retried.

Event registration will be retried.

KAVA3018-I

The Event service can now be connected.

The Event service can be connected.

KAVA3019-I

The Event Log Trap will now continue according to the settings.

If the Event service cannot be connected at the start of the Event Log Trap service, this message is output and the service continues if retrying is specified in the action definition file.

KAVA3020-E

The Event service cannot be connected even after the specified number of retries, so the processing will now stop.

Retrying was performed the specified number of times, and processing stopped because the Event service could not be connected.

(S)

Stops the Event Log Trap service.

(O)

Re-execute the JP1/Base Eventlog Trap service after you have made sure that:

The event service is running. (You can check this by using the jevstat command.)

The service name specified for the ports parameter as an application port in the event server settings file (conf) is set in the services file.

Communication is possible between the address specified for the ports parameter in the event server settings file (conf) and the addresses specified for the server and client parameters in the API settings file.

When JP1/Base is operating with the ANY binding method on a host that uses IPv6 addresses, the IPv6 address of the local host is set in the jp1hosts2 information.

KAVA3023-W

There is an event log that cannot be monitored because a large amount of event log data has been generated.

The event log was overwritten before it was monitored because a large amount of Windows event log data was generated in a short time. Event log data specified as subject to trapping, if any, will not be trapped.

(S)

Continues processing, beginning with event log data that can be trapped. This message appears when the event log was overwritten and cannot be monitored. However, this message will not appear even if the same problem occurs again, unless the event log trapping service is restarted.

(O)

Check the contents of the event log, and then correct the problem that caused too much event log data to be generated. If you are aware that a large amount of event log data may be generated, increase the size of the event log.

KAVA3024-I

The management ID of the Windows event log has been initialized.(eventlog-kind = event-log-type)

The management ID of the event log has been initialized.

(S)

Continues processing.

KAVA3025-W

The filter is invalid because the specified log type is not correct.(line = line-number, token = invalid-string)

The filter is invalid because the event log file for the log type specified for the filter does not exist in the system. In the message, line-number indicates the line number of the action definition file where the problem occurred, and invalid-string indicates the string specified as the log type.

(S)

Continues processing.

(O)

Check and correct the contents of the invalid filter, and then execute the jeveltreload command.

KAVA3026-W

The filter is invalid because the specified regular expression is incorrect.(line = line-number, token = invalid-string)

This filter is invalid because an invalid regular expression is specified for the filter. In the message, line-number indicates the line number of the action definition file where the problem occurred, and invalid-string indicates the string specified as the regular expression.

(S)

Continues processing.

(O)

Check and correct the contents of the invalid filter, and then execute the jeveltreload command.

KAVA3027-E

The Event Log Trap Service cannot start because there is no valid filter in the action definition file.

The event log trapping service cannot start because the action definition file does not contain a valid filter.

(S)

Stops the event log trapping service.

(O)

Check that a filter is specified in the action definition file, and then restart the event log trapping service.

KAVA3028-E

An attempt to reload the Event Log Trap failed because there is no valid filter in the action definition file.

An attempt to reload the event log trapping failed because the action definition file did not contain a valid filter.

(S)

Terminates command processing. Using the condition that was specified before the action definition file was changed, the system continues monitoring of the event log without stopping the event log trapping service.

(O)

Check that a filter is specified in the action definition file, and then re-execute the jeveltreload command.

KAVA3029-E

Execute the command from the administrator console.

This command must be executed on the administrator console.

(S)

Terminates command processing.

(O)

Re-execute the command on the administrator console.

KAVA3030-W

Acquisition of event log data failed. (function = function, code = reason-code, log = log-type)

An error of the indicated reason code occurred in the Windows API function while event log data of the indicated log type was being monitored. After this message is output, log data of the indicated log type might not be monitored correctly. If the reason code is 1500, event log data might have been damaged.

This message is not output again until the recovery message (KAVA3031-I) is output.

(S)

Continues processing.

(O)

Contact the system administrator.

KAVA3031-I

An event log can now be monitored. (log = log-type)

The system recovered from the error that occurred while event log data of the indicated log type was being monitored and can now be ready for monitoring event log data. This message is output if the system recovers from the error output by the KAVA3030-W message.

(S)

Continues the monitoring of event log data.

KAVA3032-W

Registration of the JP1 event failed. (Event ID = JP1-event-ID)

An attempt to register the JP1 event failed.

(S)

Continues processing.

(O)

Use the jevstat command to make sure that the event service is running correctly.

KAVA3033-E

The Event Log Trap service could not be started because the action definition file was created using Unicode.

The event log trapping service cannot start because the action definition file was created using Unicode.

(S)

Stops the event log trapping service.

(O)

Re-create the action definition file by using the language specified in the Language for non-Unicode programs section on the Advanced page in the dialog box that is opened by double-clicking Regional and Language Options in the Windows Control Panel. Then, restart the event log trapping service.

KAVA3034-E

Reloading of the Event Log Trap failed because an action definition file was created using Unicode.

An attempt to reload the event log trap failed because the action definition file was created using Unicode.

(S)

Terminates command processing.

(O)

Re-create the action definition file by using the language specified in the Language for non-Unicode programs section on the Advanced page in the dialog box that is opened by double-clicking Regional and Language Options in the Windows Control Panel. Then, re-execute the jeveltreload command.

KAVA3400-I

The log-file trap management daemon will now start.

The log-file trap management daemon will now start.

KAVA3401-I

The log-file trap management daemon will now stop.

The log-file trap management daemon will now stop.

KAVA3403-E

The process ID is not specified.

No process ID is specified.

(S)

Terminates command processing.

(O)

Specify the process ID, and then re-execute the command.

KAVA3404-E

The log-file trap management daemon is not running.

Command processing was terminated because the log-file trap management daemon is not running.

(S)

Terminates command processing.

(O)

Execute the jevlogdstart command to start the log-file trap management daemon, and then re-execute the failed command.

KAVA3405-E

An error occurred in the connection with the log-file trap management daemon.

Command processing was terminated because an error occurred in the connection with the log-file trap management daemon.

(S)

Terminates command processing.

(O)

Make sure that the log-file trap management daemon is active, and then re-execute the command.

KAVA3406-E

There is an error in the specified process ID.

Command processing was terminated because the specified process ID is invalid.

(S)

Terminates command processing.

(O)

Make sure the process ID is specified correctly, and then re-execute the command.

KAVA3407-W

The log-file trap management daemon has already started.

The log-file trap management daemon has already started. This message is also output when you use jbs_start.model or jbs_start.cluster to start JP1/Base in multiple logical hosts or use jbs_stop.model to terminate JP1/Base. The message is not reporting an abnormality. Ignore the message.

KAVA3408-E

The log-file trap management daemon has already stopped.

The log-file trap management daemon has already stopped.

KAVA3409-I

The log-file trap targeted for startup has started.

A log file trap specified in the log-file trap startup definition file was started.

KAVA3410-W

The syntax of a parameter specified in the startup definition file is incorrect, so the parameter will be ignored. (line=line-number, keyword=keyword)

Because the format of a parameter specified in the log-file trap startup definition file is incorrect, the parameter will be ignored. line-number is the location of the parameter in the file, and keyword is the name of the parameter.

(S)

Continues processing.

(O)

Correct the parameter error, and then restart the log-file trap management daemon.

KAVA3411-W

Because the number of parameters that can be specified in a startup definition file was exceeded, the excess parameters will be ignored. (line=line-number, keyword=keyword)

The number of parameters specified in the log-file trap startup definition file has reached the maximum. All subsequent parameters will be ignored. line-number is the location of the parameter in the file, and keyword is the name of the parameter.

(S)

Continues processing.

(O)

Make sure that the number of log file traps that will be started with the log-file trap startup definition file does not exceed the maximum, and then restart the log-file trap management daemon.

KAVA3412-W

An attempt to start the log-file trap targeted for startup has failed.

An error occurred when a log file trap specified in the log-file trap startup definition file was started.

(S)

Continues processing.

(O)

Make sure that sufficient system resources and available memory are allocated.

If the system resources and memory are insufficient, remove the cause of the error, and then restart the log-file trap management daemon.

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

KAVA3413-W

One or more parameters in the startup definition file are invalid. Those parameters have been disabled.

There are disabled parameters in the log-file trap startup definition file.

(S)

Continues processing.

(O)

Correct the log-file trap startup definition file, and then restart the log-file trap management daemon. For details about disabled parameters, see the log-file trap startup execution results log.

KAVA3414-I (Windows)

The log-file trap management service is already running.

The log file trap management service is running.

KAVA3414-I (UNIX)

The log-file trap management daemon is already running.

The log-file trap management daemon is running.

KAVA3415-I (Windows)

The log-file trap management service has already stopped.

The log file trap management service has stopped.

KAVA3415-I (UNIX)

The log-file trap management daemon has already stopped.

The log-file trap management daemon has stopped.

KAVA3416-I (Windows)

The log-file trap management service is starting.

The log file trap management service is being started.

(O)

Wait a while, and then try again.

KAVA3416-I (UNIX)

The log-file trap management daemon is starting.

The log-file trap management daemon is being started.

(O)

Wait a while, and then try again.

KAVA3417-E (Windows)

Communication with the log-file trap management service has failed.

An error occurred during communication with the log file trap management service.

(S)

Terminates command processing.

(O)

Re-execute the command. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KAVA3417-E (UNIX)

Communication with the log-file trap management daemon has failed.

An error occurred during communication with the log-file trap management daemon.

(S)

Terminates command processing.

(O)

Re-execute the command. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KAVA3418-E

An error occurred that prevents processing.

An error that prevents the command processing from continuing occurred.

(S)

Terminates command processing.

(O)

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

KAVA3500-I

The log-file trap management service will now start.

The log-file trap management service will now start.

KAVA3501-I

The log-file trap management service will now stop.

The log-file trap management service will now stop.

KAVA3502-E

The log-file trap management service has stopped due to error that prevents processing. (function = function, code = detail-code)

An error that prevents processing occurred at the log-file trap management service.

(S)

Stops the log-file trap management service.

(O)

Make sure that sufficient system resources and available memory are allocated.

If system resources and memory are insufficient, remove the cause of the error, and then restart the log-file trap service.

If the problem is not solved, use the data collection tool to collect data, and then contact the system administrator.

KAVA3503-E

The thread ID is not specified.

The thread ID is not specified.

(S)

Terminates command processing.

(O)

Specify the thread ID, and then re-execute the command.

KAVA3504-E

The log-file trap management service is not running.

Command processing was terminated because the log-file trap management service is not running or the service cannot be executed because of a request from another log file trap.

(S)

Terminates command processing.

(O)

Start the log-file trap management service or make sure that there is no request from another log file trap, and then re-execute the command.

KAVA3505-E

An error occurred in the connection with the log-file trap management service.

Command processing was terminated because an error occurred in the connection with the log-file trap management service.

(S)

Terminates command processing.

(O)

Make sure that the log-file trap management service is active, and then re-execute the command.

KAVA3506-E

The user lacks operator permissions to execute this command.

Execution of this command requires operator privileges. In Windows, the user who executes this command must be a member of the Administrators group. In UNIX, the user who executes this command must have root privileges or JP1/Base administrator privileges.

(S)

Terminates command processing.

(O)

Re-execute the command from the account of an authorized user.

KAVA3507-E

There is an error in the specified thread ID.

Command processing was terminated because there is an error in the specified thread ID.

(S)

Terminates command processing.

(O)

Make sure that the thread ID is specified correctly, and then re-execute the command.

KAVA3508-E

Execute the command from the administrator console.

This command must be executed on the administrator console.

(S)

Terminates command processing.

(O)

Re-execute the command on the administrator console.

KAVA3509-I

The log-file trap targeted for startup has started.

A log file trap specified in the log-file trap startup definition file was started.

KAVA3510-W

The syntax of a parameter specified in the startup definition file is incorrect, so the parameter will be ignored. (line=line-number, keyword=keyword)

Because the format of a parameter specified in the log-file trap startup definition file is incorrect, the parameter will be ignored. line-number is the location of the parameter in the file, and keyword is the name of the parameter.

(S)

Continues processing.

(O)

Correct the parameter error, and then restart the log file trap management service.

KAVA3511-W

Because the number of parameters that can be specified in a startup definition file was exceeded, the excess parameters will be ignored. (line=line-number, keyword=keyword)

The number of parameters specified in the log-file trap startup definition file has reached the maximum. All subsequent parameters will be ignored. line-number is the location of the parameter in the file, and keyword is the name of the parameter.

(S)

Continues processing.

(O)

Make sure that the number of log file traps that will be started with the log-file trap startup definition file does not exceed the maximum, and then restart the log file trap management service.

KAVA3512-W

An attempt to start the log-file trap targeted for startup has failed.

An error occurred when a log file trap specified in the log-file trap startup definition file was started.

(S)

Continues processing.

(O)

Make sure that sufficient system resources and available memory are allocated.

If the system resources and memory are insufficient, remove the cause of the error, and then restart the log file trap managemet service.

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

KAVA3513-W

One or more parameters in the startup definition file are invalid. Those parameters have been disabled.

There are disabled parameters in the log-file trap startup definition file.

(S)

Continues processing.

(O)

Correct the log-file trap startup definition file, and then restart the log file trap management service. For details about disabled parameters, see the log-file trap startup execution results log.

KAVA3600-I

The log file trap will now start. (ID = process-ID/thread-ID[monitored-name])

The log file trap will now start.

KAVA3601-I

The log file trap has stopped. (ID = process-ID/thread-ID[monitored-name])

The log file trap has stopped.

KAVA3602-E

The log file trap will now stop due to error that prevents processing.

An error that prevents processing occurred in the log file trap.

(S)

Stops log file trapping.

(O)

Check the following:

Make sure that sufficient system resources and available memory are allocated.

Make sure that the size of the monitoring file is 2MB or less.

Make sure that the following directory or folder is enabled:

Windows: Base_Path\sys\tmp\event\logtrap

UNIX: /var/opt/jp1base/sys/tmp/event/logtrap

If system resources and memory are insufficient, the size of the monitoring file is 2MB or more, or the above directory or folder is not enabled, remove the cause of the error, and then restart the log file trap.

If the problem is not solved, use the data collection tool to collect data, and then contact the system administrator.

KAVA3604-E

An error occurred during the opening of the action definition file.

An error occurred during an attempt to open the action definition file for the log file trap.

(S)

Terminates command processing.

(O)

Make sure that there are no errors in the action definition file, and then re-execute the jevlogstart command.

In Windows, check the following and take corrective actions:

If the maximum number of log files that can be monitored is exceeded, this message might appear. In this case, stop monitoring unnecessary log files, and then re-execute the jevlogstart command. For details about the number of log files that can be monitored, see 2.4.6 Number of log files that can be monitored in the Job Management Partner 1/Base User's Guide.

If the action definition file includes environment dependent characters, this message appears. Change the action definition file name so that no environment dependent characters are included, and then re-execute the jevlogstart command.

KAVA3606-E

There is an error in the specified option.

The option is specified incorrectly.

(S)

Terminates command processing.

(O)

Re-execute the command with the correct number of options.

KAVA3608-E

Memory is insufficient.

There is not enough memory for the process.

(S)

Terminates command processing.

(O)

Terminate other processes that may be using memory, and then re-execute the command.

KAVA3609-E

An error occurred during opening of the log file. (file = file-name)

An error occurred while the log file was being opened.

(S)

Terminates command processing.

(O)

Make sure that the log file name is specified correctly, and then re-execute the command.

In Windows, check the following and take corrective actions:

If the action definition file includes environment dependent characters, this message appears. Change the action definition file name so that no environment dependent characters are included, and then re-execute the jevlogstart command.

KAVA3610-E

Log files are not specified.

No log file is specified.

(S)

Terminates command processing.

(O)

Specify a log file name, and then re-execute the command.

KAVA3611-E

There is an error in the action definition file. (keyword = keyword)

There is an error in the action definition file for the log file trap.

(S)

Terminates command processing.

(O)

Correct the invalid setting, and then re-execute the command.

In Windows, check the following and take corrective actions:

If the action definition file was created using Unicode, this message might appear. Re-create the action definition file by using the language specified in the Language for non-Unicode programs section on the Advanced page in the dialog box that is opened by double-clicking Regional and Language Options in the Windows Control Panel. Then, re-execute the jevlogstart command.

KAVA3613-E

A connection to the event server cannot be established. (function = function, code = detail-code)

An attempt to connect to the event server has failed.

(S)

Stops log file trapping.

(O)

Re-execute the jevlogstart command after you have made sure that:

The event service is running. (You can check this by using the jevstat command.)

The service name specified for the ports parameter as an application port in the event server settings file (conf) is set in the services file.

Communication is possible between the address specified for the ports parameter in the event server settings file (conf) and the addresses specified for the server and client parameters in the API settings file.

When JP1/Base is operating with the ANY binding method on a host that uses IPv6 addresses, the IPv6 address of the local host is set in the jp1hosts2 information.

KAVA3614-E

An event server is not running. (name = event-server-name, total = number-of-event-servers)

The event server is inactive.

(S)

Terminates command processing.

(O)

Re-execute the jevlogstart command after you have made sure that:

The event service is running. (You can check this by using the jevstat command.)

The service name specified for the ports parameter as an application port in the event server settings file (conf) is set in the services file.

Communication is possible between the address specified for the ports parameter in the event server settings file (conf) and the addresses specified for the server and client parameters in the API settings file.

When JP1/Base is operating with the ANY binding method on a host that uses IPv6 addresses, the IPv6 address of the local host is set in the jp1hosts2 information.

KAVA3615-E

An error occurred during event registration. (function = function, code = detail-code)

An error occurred during event registration.

(S)

Stops log file trapping.

(O)

Make sure that sufficient system resources and available memory are allocated.

If the system resources and memory are insufficient, remove the cause of the error, and then restart the event log trap service.

If the problem is not solved, use the data collection tool to collect data, and then contact the system administrator.

KAVA3616-E

The log file trap will now stop due to an error that prevents processing. (function = function, code = detail-code)

An error that prevents processing occurred during log file trap processing.

(S)

Stops log file trapping.

(O)

Check the following:

Make sure that sufficient system resources and available memory are allocated.

If you use DNS to resolve the local host name, make sure that DNS is running.

If the system resources and memory are insufficient or DNS is not running, remove the cause of the error, and then restart the log file trap.

If the problem is not solved, use the data collection tool to collect data, and then contact the system administrator.

KAVA3617-E

Event registration failed. (function = function, code = detail-code)

An error occurred during event registration.

(S)

Stops log file trapping.

(O)

For code = 40 (the event service cannot be connected), correct the problem, such as a communication error, that prevented the connection with the event service.

For other codes, contact the system administrator.

KAVA3618-E

The specified log file trap cannot be stopped. (ID = process-ID/thread-ID[monitored-name], code = detail-code)

The specified log file trap cannot be stopped.

(S)

Terminates command processing.

(O)

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

KAVA3619-I

The specified log file trap is already running. (ID = process-ID/thread-ID[monitored-name])

The specified log file trap has already started.

KAVA3620-W

The specified log file trap does not exist. (ID = process-ID/thread-ID)

The specified log file trap does not exist.

KAVA3621-W

There is no response from the specified log file trap. (ID = process-ID/thread-ID[monitored-name])

There is no response from the specified log file trap.

(S)

Terminates command processing.

(O)

If there is no response even after the jevlogstop command is executed, wait a while and then execute the jevlogstat command. If you can confirm that the target log file trap has stopped by using the jevlogstop command, you do not need to take further action.

If the target log file trap has not stopped even if you execute the jevlogstat command, or if there is no response even if another command is executed, use the data collection tool to collect data, and then contact the system administrator.

KAVA3622-I

All log file traps were stopped.

All log file traps were stopped.

KAVA3623- E

A system error occurred. (function = function, code = detail-code)

The command terminated due to a system error.

(S)

Terminates command processing.

(O)

Make sure that sufficient system resources and available memory are allocated.

If system resources and memory are insufficient, remove the cause of the error, and then re-execute the command.

If the problem is not solved, use the data collection tool to collect data, and then contact the system administrator.

KAVA3624-E

An I/O error occurred. (function = detail-code, code = detail-code)

The command terminated due to an I/O error.

(S)

Terminates command processing.

(O)

Make sure that sufficient system resources and available memory are allocated.

If system resources and memory are insufficient, remove the cause of the error, and then re-execute the command.

If the problem is not solved, use the data collection tool to collect data, and then contact the system administrator.

KAVA3625-E

The locale could not be set. (maintenance-information)

The system failed to set the language environment at a log file trap. The LANG environment variable or an environment variable beginning with LC_ may have an invalid value when the jevlogstart command is executed.

(S)

Terminates processing the log file trap.

(O)

Check the values of environment variables and correct invalid settings. Then re-execute the jevlogstart command.

KAVA3628-I

Reloading of the log file trap has finished.

Reloading of the log file trap has finished.

KAVA3629-I

Reloading of the log file trap has finished. (ID = process-ID/thread-ID[monitored-name])

Reloading the process with the process ID returned at activation has finished.

KAVA3630-E

Reloading of the log file trap was interrupted due to an error that prevents processing.

An unrecoverable error occurred in the log-file trap management daemon.

(S)

Cancels the reloading of the log file trap.

(O)

Determine the cause of the error from syslog, the event log, and the integrated trace log, and then re-execute the command.

KAVA3631-E

An attempt to reload the log file trap has failed.

An attempt to reload the log file trap has failed.

(S)

Terminates command processing.

(O)

Determine the cause of the error from syslog, the event log, and the integrated trace log.

KAVA3632-E

An error occurred during opening of the action definition file. (ID = process-ID/thread-ID[monitored-name])

An error occurred when the action definition file specified at activation was opened.

The process with the process ID returned at activation could not be reloaded.

(S)

Terminates the reloading of the log file trap.

(O)

Make sure that the action definition file exists and that the file is specified correctly, and then re-execute the command.

KAVA3633-E

There is an error in the action definition file. (keyword = keyword, ID = process-ID/thread-ID[monitored-name])

The action definition file contains incorrect specifications. The process with the process ID returned at activation could not be reloaded.

(S)

Terminates reloading.

(O)

Correct the keyword error in the action definition file, and then re-execute the command.

KAVA3634-E

A parameter in the action definition file cannot be reloaded. (keyword = keyword, ID = process-ID/thread-ID[monitored-name])

The action definition file cannot be reloaded with changes in a parameter in the file.

(S)

Terminates reloading.

(O)

Make sure that you have not changed the parameters other than MARKSTR or ACTDEF.

If you have changed such parameters, perform either of the following operations:

Restart the log file trap.

Re-execute the command without changing the settings for the parameters other than MARKSTR or ACTDEF in the action definition file.

KAVA3635-W

The last surveillance file create failed.(ID = process-ID/thread-ID[monitored-name])

An attempt to create the last surveillance file failed when the -w option was specified for the jevlogstop command.

(S)

Continues command processing, without monitoring the last log of the process (thread).

KAVA3636-W

An attempt to connect to the event service has failed. The attempt will be retried.(ID=process-ID/thread-ID[monitored-name])

Issuing of the JP1 event was retried because an attempt to connect to the event service by using log file trapping has failed.

(S)

Performs retry processing.

(O)

Make sure that the event service is running.

KAVA3637-I

A connection to the event service has been re-established. (ID=process-ID/thread-ID[monitored-name])

The JP1 events can now be issued after the retry of log file trapping.

(S)

Issues the suspended JP1 events.

KAVA3638-E

An old event was deleted because the events to be suspended exceed the valid number of suspensions. (ID=process-ID/thread-ID[monitored-name])

JP1 events that can no longer be suspended will be deleted during retry processing of the connection with the event service.

(S)

Sequentially deletes the JP1 events that can no longer be suspended.

(O)

Correct the problem that prevented the connection to the event service.

KAVA3639-E

A new event was deleted because the events to be suspended exceed the valid number of suspensions. (ID=process-ID/thread-ID[monitored-name])

JP1 events that can no longer be suspended during retry processing of the connection with the event service will be deleted.

(S)

Sequentially deletes the JP1 events that can no longer be suspended.

(O)

Correct the problem that prevented the connection to the event service.

KAVA3640-W

Event issuance was delayed because the system retried the log file trap. (ID=process-ID/thread-ID[monitored-name])

The event service has now been successfully connected by the connection retry processing, and the issuing of the suspended JP1 events has started.

(S)

Sequentially issues the suspended JP1 events.

(O)

Make sure that the delay in issuing the JP1 events does not cause a problem.

KAVA3641-W

numeric-value event(s) were deleted during retry processing. (ID=process-ID/thread-ID[monitored-name])

Some JP1 events were deleted during retry processing of log file trapping.

(S)

Continues processing.

(O)

Make sure that the deletion of the JP1 events does not cause a problem.

KAVA3642-E

The Event service cannot be connected even after the specified number of retries, so the processing will now stop. (ID=process-ID/thread-ID[monitored-name])

Log file trapping was stopped because the service could not be connected even after the log file trapping function performed the specified number of retries or even after 24 hours elapsed from the time the retries started.

(S)

Stops log file trapping.

(O)

Make sure that the deletion of the JP1 events does not cause a problem.

Then, re-execute the jevlogstart command after you have made sure that:

The event service is running. (You can check this by using the jevstat command.)

The service name specified for the ports parameter as an application port in the event server settings file (conf) is set in the services file.

Communication is possible between the address specified for the ports parameter in the event server settings file (conf) and the addresses specified for the server and client parameters in the API settings file.

When JP1/Base is operating with the ANY binding method on a host that uses IPv6 addresses, the IPv6 address of the local host is set in the jp1hosts2 information.

KAVA3643-E

Monitoring of the relevant log file cannot start. (code = error-number, file name = log-file-name)

An attempt to open the log file has failed during execution of the jevlogstart command. Monitoring of the log file will not start because the system could not open this file after the specified number of retries.

(S)

Does not monitor the log file.

(O)

Correct the cause of the open error, and then separately start the log file trapping that monitors the log file.

KAVA3644-E

Monitoring will now stop because the specified number of retries was performed, but the relevant log file cannot be read. (code = error-number, file name = log-file-name)

An attempt to read the log file has failed during monitoring of the log file. Monitoring of the log file will stop because the system could not read this file after the specified number of retries.

(S)

Stops monitoring of the log file. The log file trapping continues monitoring of other log files, if any.

However, if the log file trapping started from a JP1/AJS log file monitoring job, the log file trapping stops.

(O)

Correct the cause of the read error, and then separately start the log file trapping that monitors the log file.

KAVA3645-E

Monitoring of the relevant log file cannot continue. (code = error-number, file name = log-file-name)

The log file cannot be monitored correctly because the status of this file is abnormal. This error message is output if the format of the log file is different from the log file format specified in the action definition file.

For details about the status of the log file, see the following error numbers.

code = 01: The log file being monitored was deleted.

code = 02: The log file being monitored was re-created.

code = 03: The size of the log file being monitored was reduced.

(S)

Continues processing.

(O)

If the format of the output log file is different from the log file format specified in the action definition file, one of the error numbers shown in the table below might be output. Revise the specification of the FILETYPE parameter to the correct format, and then restart the log file trapping.

FILETYPE value

Format of the output log file

SEQ

SEQ2

SEQ3

WRAP1

WRAP2

HTRACE

SEQ

Y#1

code = 01

code = 02

--

--

code = 03

--#2

SEQ2

--

Y#1

--

--

code = 03

--#2

SEQ3

--

--

Y#1

--

code = 03

--#2

WRAP1

--

code = 01

code = 02

--

Y#1

code = 03

--#2

WRAP2

--

code = 01

code = 02

--

--

Y#1

--#2

HTRACE

--#2

--#2

--#2

--#2

--#2

Y#1

Legend:

Y: The format of the log file matches the log file format specified in the action definition file.

--: The KAVA3645-E message is not output.

#1: If the log file formats match but this message is output, the probable causes are as follows:

The size of the monitored file exceeds 2 GB.

In this case, code = 01 or code = 03 might be output. Make sure that the size of the monitored file does not exceed 2 GB.

When a file on the shared disk was being monitored, the shared disk was moved (unmounted) while the log file trapping was running.

In this case, code = 01 might be output. Make sure that the log file trapping is stopped before you attempt to move the shared disk.

#2: A KAVA3646-E error message is output when the log file trapping starts monitoring.

KAVA3646-E

There is an error in the specified FILETYPE parameter in the action definition file. (FILETYPE = file-format)

The FILETYPE parameter is specified incorrectly in the action definition file.

(S)

Terminates command processing.

If the -r option is specified in the jevlogstart command, the system stops log file trapping.

(O)

To monitor multi-process traces, specify HTRACE for the FILETYPE parameter in the action definition file. Then, re-execute the jevlogstart command.

KAVA3647-E

The log file trap of the monitor name cannot be started because it is already running. (monitored-name)

A log file trap that has the same monitored name is already running.

(S)

Terminates command processing.

(O)

Use the jevlogstat command to make sure that a log file trap that has the same monitored name is not running.

KAVA3648-W

The log file trap of the specified monitor name does not exist. (monitored-name)

The log file trap of the specified monitored name has not started.

(S)

Terminates command processing.

(O)

Make sure that the monitored name is correct.

KAVA3650-I

Information about startup of the log file trap (ID = process-ID/thread-ID): conf-file = action-definition-file-name, last updated = YYYY/MM/DD hh:mm:ss, options = option-information, watch-file = name-of-the-monitored-file1 name-of-the-monitored-file2...

This message outputs startup information of the log file trap.

Table 2‒1: Startup information

Startup information

Description

process-ID/thread-ID

If the monitored name is specified during startup, this item is output in the following format:

id = process-ID[monitored-name]/thread-ID[monitored-name]

action-definition-file-name

The absolute path to the target action definition file is output.

YYYY/MM/DD hh:mm:ss

The time when the target action definition file was last saved is output.

option-information

This item is output in the following format:

options = file-monitoring-interval-in-seconds|maximum-length-of-the-data-to-be-changed-to-an-event-in-bytes|whether-to-read-data-from-the-beginning-of-the-log-file-by-yes-or-no|displayed-command-name (in UNIX only)|name-of-the-program-that-outputs-log-data|whether-to-wait-until-the-log-file-is-opened-by-yes-or-no|registration-destination-event-server-name|whether-to-monitor-UNICODE-files-by-yes(UTF-8)-or-yes(UTF-16)-or-no (in Windows only)|UNICODE-file-byte-order-specification (in Windows only)

file-monitoring-interval-in-seconds

If no value is specified, the default value (10) is output.

maximum-length-of-the-data-to-be-changed-to-an-event-in-bytes

If no value is specified, the default value (512) is output.

whether-to-read-data-from-the-beginning-of-the-log-file-by-yes-or-no

If no value is specified, no is output.

displayed-command-name (in UNIX only)

This item is output for UNIX only. If no value is specified, the name of the monitored target file that you specified first is output.

name-of-the-program-that-outputs-log-data

If no value is specified, /HITACHI/JP1/NT_LOGTRAP# is output. If a value is specified, /HITACHI/JP1/NT_LOGTRAP/name-of-the-specified-program is output.

whether-to-wait-until-the-log-file-is-opened-by-yes-or-no

If no value is specified, no is output.

registration-destination-event-server-name

If no value is specified, nothing is output.

whether-to-monitor-UNICODE-files-by-yes(UTF-8)-or-yes(UTF-16)-or-no (in Windows only)

If no value is specified, no is output.

UNICODE-file-byte-order-specification-by-LE-or-BE (in Windows only)

If no value is specified, nothing is output.

name-of-the-monitored-file

The absolute path to the monitored target file specified during startup is output. If you specified multiple monitored target files, they are output, separated by spaces.

If all of the monitored target file names cannot be output because of the message length limitations, the file names are output up to the maximum allowable length, and the forward slash (/) is output at the end of the message.

#: For UNIX, this portion is UX_LOGTRAP.

KAVA3651-I

Information about reloading of the log file trap (id = process-ID/thread-ID): conf-file = action-definition-file-name, last updated = YYYY/MM/DD hh:mm:ss

This message outputs reload information of the log file trap.

Table 2‒2: Reload information

Reload information

Description

process-ID/thread-ID

If the log file trap to be reloaded has the monitored name, this item is output in the following format:

id = process-ID[monitored-name]/thread-ID[monitored-name]

action-definition-file-name

The absolute path to the target action definition file is output.

YYYY/MM/DD hh:mm:ss

The time when the target action definition file was last saved is output.

KAVA3652-I

The log-file trap targeted for startup has started. (CID=cluster-ID)

The log file trap for the indicated cluster ID specified in the log-file trap startup definition file was started.

KAVA3653-W

The log-file trap targeted for startup does not exist. (CID=cluster-ID)

The log file trap for the indicated cluster ID is not specified in the log-file trap startup definition file.

KAVA3654-W

The syntax of a parameter specified in the startup definition file is incorrect, so the parameter will be ignored. (line=line-number, keyword=keyword, CID=cluster-ID)

Because the format of a parameter specified in the log-file trap startup definition file is incorrect, the parameter will be ignored. line-number is the location of the parameter in the file, and keyword is the name of the parameter.

(S)

Continues processing.

(O)

Correct the parameter error, and then re-execute the command.

KAVA3655-W

Because the number of parameters that can be specified in a startup definition file was exceeded, the excess parameters will be ignored. (line=line-number, keyword=keyword, CID=cluster-ID)

The number of parameters specified in the log-file trap startup definition file has reached the maximum. All subsequent parameters will be ignored. line-number is the location of the parameter in the file, and keyword is the name of the parameter.

(S)

Continues processing.

(O)

Make sure that the number of log file traps that will be started with the log-file trap startup definition file does not exceed the maximum, and then re-execute the command.

KAVA3656-E

An attempt to start the log-file trap targeted for startup has failed. (CID=cluster-ID)

An error occurred when the log file trap for the indicated cluster ID specified in the log-file trap startup definition file was started.

(S)

Terminates command processing.

(O)

Make sure that sufficient system resources and available memory are allocated.

If the system resources and memory are insufficient, remove the cause of the error, and then re-execute the command.

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

KAVA3657-I

The log-file trap targeted for termination has stopped. (CID=cluster-ID)

A log-file trap to be stopped has been stopped.

KAVA3658-W

The log-file trap targeted for termination does not exist. (CID=cluster-ID)

The log file trap to be stopped does not exist.

KAVA3659-E

An attempt to stop the log-file trap targeted for termination failed. (CID=cluster-ID)

An error occurred when an attempt was made to stop a log file trap.

(S)

Terminates command processing.

(O)

Make sure that sufficient system resources and available memory are allocated.

If the system resources and memory are insufficient, remove the cause of the error, and then re-execute the command.

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

KAVA3660-W

One or more parameters in the startup definition file are invalid. Those parameters have been disabled. (CID=cluster-ID)

There are disabled parameters in the log-file trap startup definition file.

(S)

Continues processing.

(O)

Correct the log-file trap startup definition file, and then re-execute the command. For details about disabled parameters, see the log-file trap startup execution results log.

KAVA3661-I

Log-file trap startup details: [CID=cluster-ID,] LANG=LANG-value, WatchName=monitored-name, CommandLine=jevlogstart-command-line

This message outputs log-file trap startup details.

Table 2‒3: Log-file trap startup details

Input information

Description

cluster-ID

Outputs the cluster ID for which the jevlogstart command was executed with the -cluster option specified.

This item is not output when the management service or daemon is started.

LANG-value

Outputs the value of the LANG environment variable used when the jevlogstart command was executed.

monitored-name

Outputs the monitored name specified when the jevlogstart command was executed.

jevlogstart-command-line

Outputs the command line of the jevlogstart command that was executed.

KAVA3662-I

Log-file trap startup-result details: WatchName=monitored-name, ReturnCode=jevlogstart-command's-return-value, Message=jevlogstart-command's-response-message

This message outputs log-file trap startup-result details.

Table 2‒4: Log-file trap startup-result details

Output information

Description

monitored-name

Outputs the monitored name specified when the jevlogstart command was executed.

jevlogstart-command's-return-value

Outputs the return value of the jevlogstart command.

jevlogstart-command's-response-message

Outputs the jevlogstart command's response message.

In the normal status, the command outputs the process (thread) ID.

KAVA3663-E

Attempt to forced stop the running remote monitor(s).

Remote monitoring will be stopped forcibly.

(S)

Stops the currently running remote log monitoring, remote event log monitoring, and log file trap management service (or log-file trap management daemon in UNIX).

(O)

If remote monitoring is running, stop JP1/IM, and then stop the log file trap management service (or the log-file trap management daemon in UNIX).

KAVA3664-E

The specified log file is invalid. (FILETYPE=file-type)

The specified log file is invalid.

(S)

Terminates command processing.

(O)

If the file type was UPD, make sure that the file name is specified using a wildcard character, and then re-execute the command.

In UNIX, make sure that the wildcard specification is escaped, and then re-execute the command.

KAVA3665-E

No log files correspond to the specified monitoring file name. (FILETYPE=file-type, file=name-of-the-monitored-file)

Log files that correspond to the specified file name are not found.

(S)

Terminates command processing.

(O)

Make sure that the specified file name is correct, and then re-execute the command.

If you re-execute the command with the -r option specified, the command will wait until a log file that corresponds to the specified file name is created.

KAVA3666-E

The number of files corresponding to the specified monitoring file name exceeds the maximum. (FILETYPE=file-type, file=name-of-the-monitored-file)

The number of files that correspond to the specified file name exceeds the maximum.

(S)

Terminates command processing.

(O)

Delete or move some of the files that correspond to the specified file, and then re-execute the command.

KAVA3667-E

No log files can be identified for monitoring. (FILETYPE=file-type, file=name-of-the-monitored-file)

The log files to be monitored cannot be identified.

(S)

Terminates command processing.

(O)

Two or more files that correspond to the specified file name (that uses wildcard specifications) might have the latest timestamp. To avoid this, change the wildcard specification of the file name so that only one log file matches, and then re-execute the command.

KAVA3668-I

The log file (file-type) will now be monitored. (id=process-ID[monitored-name]/thread-ID[monitored-name], file name=log-file-name)

Monitoring of the log file started.

KAVA3669-I

A different log file (file-type) is now being monitored. (id=process-ID[monitored-name]/thread-ID[monitored-name], file name=log-file-name)

The monitoring-target log file changed.

KAVA3670-E

The log file (file-type) can no longer be properly monitored. (id=process-ID[monitored-name]/thread-ID[monitored-name], code=error-number, file name=log-file-name)

The monitored log file cannot be monitored correctly because the file status became abnormal.

The cause of the error is indicated by error-number:

code=01: The log file has been deleted.

code=02: After the log file was deleted, it was re-created with the same name.

code=03: The log file became smaller.

(S)

Continues processing.

(O)

Common to codes 01, 02, and 03

Check whether the log file can be monitored as a UPD-type file. If the log file cannot be monitored as a UPD-type file, specify another log file type, and then restart the log file trap.

If code is 03

The size of the monitored file might exceed 2 GB. Make sure that the size of the monitored file does not exceed 2 GB during operation.

KAVA3671-E

Monitoring will now stop because the number of files corresponding to the monitoring file name exceeds the maximum. (id=process-ID[monitored-name]/thread-ID[monitored-name], FILETYPE=file-type)

Monitoring will stop because the number of files corresponding to the monitored file name exceeds the maximum.

(S)

Stops log file traps.

(O)

Delete or move some of the files that correspond to the file name (that uses wildcard specifications), and then restart the log file traps that were stopped.

KAVA3672-E

Monitoring will now stop because no log files can be identified for monitoring. (id=process-ID[monitored-name]/thread-ID[monitored-name], code=error-number, FILETYPE=file-type)

Monitoring will stop because the log files to be monitored cannot be identified.

The cause of the error is indicated by error-number:

code=01: Two or more log files that have the latest time stamp were detected.

(S)

Stops log file traps.

(O)

If code is 01:

Two or more files that correspond to the monitored file name (that uses wildcard specifications) might be created with the same time stamp. To avoid this, change the wildcard specification of the monitored file name so that only one file becomes the monitoring target, and then restart the log file traps that were stopped.

KAVA3673-W

number-of-files files correspond to the monitoring file name. (id=process-ID[monitored-name]/thread-ID[monitored-name], FILETYPE=file-type)

The number of files that correspond to the monitored file name (that uses wildcard specifications) is near the maximum (1,000).

This message is output when the number of files that correspond to the monitored file name (that uses wildcard specifications) reaches 900 or 950.

(S)

Continues processing.

(O)

Delete or move some of the files that correspond to the file name (that uses wildcard specifications) to prevent the number of corresponding files from exceeding the maximum.

KAVA3674-E

An action definition file was created using Unicode. (file name = action-definition-file-name)

An action definition file was created using Unicode.

(S)

Terminates command processing.

(O)

Re-create the action definition file by using the language specified in the Language for non-Unicode programs section on the Advanced page in the dialog box that is opened by double-clicking Regional and Language Options in the Windows Control Panel. Then, re-execute the jevlogstart command.

KAVA3903-E

Input to or output from the status retention file has failed. (path = file-path, function = function-name, error number = error-number)

An error has occurred.

(S)

Terminates remote monitoring abnormally.

(O)

Use the data collection tool to collect data about JP1/IM and JP1/Base, and then contact the system administrator.

KAVA3904-E

The connection standby has timed out. (pipe-name)

An error has occurred.

(S)

Terminates remote monitoring abnormally.

(O)

Use the data collection tool to collect data about JP1/IM and JP1/Base, and then contact the system administrator.

KAVA3905-E

An invalid log number was received. (number)

An error has occurred.

(S)

Terminates remote monitoring abnormally.

(O)

Use the data collection tool to collect data about JP1/IM and JP1/Base, and then contact the system administrator.

KAVA3906-E

Invalid data was received. (invalid-message)

An error has occurred.

(S)

Terminates remote monitoring abnormally.

(O)

Use the data collection tool to collect data about JP1/IM and JP1/Base, and then contact the system administrator.

KAVA3907-E

JP1/IM terminated abnormally.

An error has occurred.

(S)

Terminates remote monitoring abnormally.

(O)

Use the data collection tool to collect data about JP1/IM and JP1/Base, and then contact the system administrator.

KAVA3908-I

An unsupported parameter in the configuration files was ignored. (parameter)

An unsupported parameter in the action definition file was ignored.

KAVA3909-W

Log data from the termination previous to this startup might not be registered as JP1 events. (event server = event-server-name, target host = monitored-host, monitor name = monitored-name)

No JP1 events might be logged during the period from the previous termination to this startup.

(S)

Continues remote monitoring.

(O)

Make sure that:

Monitored messages had not been output to the monitored log since the system terminated previously until this message was output.

If this message is output in a cluster environment, the wait for termination might time out too early. Set a longer timeout value.

To investigate why this message was output, use the data collection tool to collect data about JP1/IM and JP1/Base, and then contact the system administrator.

KAVA3910-E

The remote monitor stopped due to an error that prevents processing. (event server = event-server-name, target host = monitored-host, monitor name = monitored-name)

Remote monitoring will be stopped because an error that prevents processing from continuing occurred.

(S)

Terminates remote monitoring abnormally.

(O)

Use the data collection tool to collect data about JP1/IM and JP1/Base, and then contact the system administrator.

KAVA3911-W

An attempt to connect to the event service has failed. The attempt will be retried. (event server = event-server-name, target host = monitored-host, monitor name = monitored-name)

An attempt to connect to the event service has failed. The attempt will be retried.

(S)

Performs retry processing.

(O)

Make sure that the event service is running or the communication settings of the event service are correct. If the problem cannot be corrected, use the data collection tool to collect data about JP1/IM and JP1/Base, and then contact the system administrator.

KAVA3912-I

A connection to the event service has been re-established. (event server = event-server-name, target host = monitored-host, monitor name = monitored-name)

A connection to the event service was re-established by retry processing.

(S)

Issues JP1 events that have been suspended.

KAVA3913-E

An old event was deleted because the events to be suspended exceed the valid number of suspensions. (event server = event-server-name, target host = monitored-host, monitor name = monitored-name)

The oldest of suspended events was deleted because the number of events that can be suspended exceeded the maximum.

(S)

Deletes a suspended JP1 event every time a new JP1 event is suspended.

(O)

Correct the problem that prevents connection to the event service.

KAVA3914-E

A new event was deleted because the events to be suspended exceed the valid number of suspensions. (event server = event-server-name, target host = monitored-host, monitor name = monitored-name)

The newest of suspended events was deleted because the number of events that can be suspended exceeded the maximum.

(S)

Deletes a suspended JP1 event every time a new JP1 event is suspended.

(O)

Correct the problem that prevents connection to the event service.

KAVA3915-W

Event issuance was delayed because the system retried the remote monitor. (event server = event-server-name, target host = monitored-host, monitor name = monitored-name)

Event issuance was delayed because the system retried remote monitoring.

(S)

Issues suspended JP1 events.

(O)

Check for any problems that are due to the delay of JP1 event issuance.

KAVA3916-W

number event(s) were deleted during retry processing. (event server = event-server-name, target host = monitored-host, monitor name = monitored-name)

At least one JP1 event was deleted during retry processing of remote monitoring.

(S)

Continues remote monitoring.

(O)

Check for any problems that are due to the deletion of JP1 events.

KAVA3917-E

The Event service cannot be connected even after the specified number of retries, so the processing will now stop. (event server = event-server-name, target host = monitored-host, monitor name = monitored-name)

The event service cannot be connected to even after the specified number of retries, so the processing will stop.

(S)

Terminates remote monitoring abnormally.

(O)

Correct the problem that prevents connection to the event service, and then restart the remote monitoring.

KAVA3918-W

The status retention file is in an invalid state. (event server = event-server-name, target host = monitored-host, monitor name = monitored-name)

The status retention file is in an invalid state.

(S)

Continues remote monitoring.

(O)

The machine was forcibly stopped due to a sudden power stoppage. Alternatively, a disk failure might have occurred. Ensure that sudden power stoppages never occur or check whether a disk has been damaged.

If the relevant remote monitoring process is retrying connection to the event server (KAVA3911-W), all messages output to the monitored log from the time the KAVA3911-W message was output until this message was output are not output as JP1 events. Check whether monitored messages have been output to the monitored log.

2.5 Startup control messages (KAVA4001 to KAVA4614)

KAVA4001-E

An effective key does not exist in the section-name section of the parameter giving the startup sequence.

No effective parameter exists in the specified section.

(S)

Ignores the section.

(O)

Add an effective parameter to the section.

KAVA4002-E

The ServiceName key does not exist in the section-name section of the parameter giving the startup sequence.

The ServiceName=service-name parameter is missing from the section.

(S)

Cancels processing.

(O)

Add the ServiceName=service-name parameter to the section.

KAVA4003-E

The service-name service could not start because an unexpected error occurred.

A system error occurred at execution of the process indicated in service-name.

(S)

Cancels processing.

(O)

Make sure that the definitions in the relevant section in the start sequence definition file (Jp1svprm.dat) neither have errors nor violate any restrictions described in the notes for this definition file. If the definitions do not have any error, contact the system administrator.

KAVA4004-E

The service-name service could not start because the service does not exist.

service-name is specified incorrectly in the ServiceName= parameter, or the service is unregistered.

(S)

Cancels processing of the service.

(O)

Specify a correct service name.

KAVA4005-W

The Wait key specification contains an error so the default value is assumed. (service = service-name)

The Wait= parameter is specified incorrectly.

(S)

Assumes the default (60 seconds).

(O)

Specify a correct value in the Wait= parameter.

KAVA4006-W

The service-name service is already running.

The service indicated in service-name is already active.

(S)

Does not perform startup sequence control for the indicated service.

(O)

Change the startup method of the indicated service from Automatic to Manual. If this service is linked by dependency relationships with other services, release the dependencies.

KAVA4007-E

The service-name service could not start because the command specified in the StartCommand key was not found.

The command set in the StartCommand= parameter does not exist.

(S)

Cancels startup for the indicated service.

(O)

Specify a correct value in the StartCommand= parameter.

KAVA4008-W

Processing was interrupted because an order to stop the startup control service was issued during startup processing for a controlled service.

A service shutdown instruction or system shutdown signal was received during startup processing.

(S)

Cancels processing.

(O)

Avoid power operations using JP1/Power Monitor while startup control (JP1/Base Control Service) is starting.

KAVA4009-E

Startup of the service-name service could not be confirmed during the period specified in the Wait key.

The system cannot confirm that the service indicated in service-name completed startup.

(S)

Stops waiting for startup completion.

(O)

Specify a larger value in the Wait= parameter if the setting is too small. Correct the problem that prevented the specified service from being started.

KAVA4010-E

An error occurred during an attempt to obtain the results of the service-name service startup command.

The service startup command returned an error.

(S)

Does not perform startup sequence control for the service indicated in service-name.

(O)

Make sure that the service startup command returns zero when successful. Investigate and fix the cause of the command error.

KAVA4011-W

The return code of the command specified in the StartCommand key is return-code.

This message reports the execution result code for the command set in the StartCommand= parameter.

KAVA4012-I

Startup-completion notification was received from the service-name service.

Startup of the indicated service has finished.

KAVA4013-E

Startup completion of the service-name service could not be confirmed because an unexpected error occurred.

The system cannot confirm that the service indicated in service-name completed startup.

(S)

Stops startup confirmation of the indicated service, and starts the next service.

(O)

Make sure that the indicated service is in a state that allows normal operation.

KAVA4014-I

Startup of the service-name service was confirmed.

The indicated service started normally.

KAVA4015-E

The service-name service could not be stopped because an unexpected error occurred.

A system error occurred during service shutdown processing.

(S)

Cancels service shutdown processing.

(O)

Make sure that the stop command is specified correctly in the service section of the start sequence definition file.

KAVA4016-E

The service-name service could not be stopped because the service does not exist.

The service specified in the section is unregistered.

(S)

Cancels stop processing of the service indicated in service-name.

(O)

Make sure that the indicated service is registered properly.

KAVA4017-W

The specification of the StopWait key contains an error (service = service-name), so the default value will be assumed.

The StopWait= parameter is specified incorrectly.

(S)

Ignores the setting and waits for service shutdown according to the default (that is, waits for 60 seconds).

(O)

Specify a correct value.

KAVA4018-W

Processing will stop because an instruction to stop the startup control service occurred during processing to stop a controlled service.

An instruction to end startup control (JP1/Base Control Service) was received during shutdown processing of a controlled service.

(S)

Cancels startup sequence control processing.

(O)

Avoid manually starting or ending startup control (JP1/Base Control Service) because the service will not function properly.

KAVA4019-E

Stop-completion of the service-name service could not be confirmed during the period specified in the StopWait key.

The service did not complete shutdown within the time set in the StopWait= parameter after execution of the command set in the StopCommand= parameter.

(S)

Stops waiting for the service to complete shutdown.

(O)

If necessary, set a larger value in the StopWait= parameter. Check the operation of the command set in the StopCommand= parameter, and fix any problems.

KAVA4020-E

An error occurred during an attempt to obtain the results of the command that stops the service-name service.

A system error occurred during an attempt to obtain the results of the command set in the StopCommand= parameter.

(S)

Stops waiting for the service to complete shutdown.

(O)

Check the operation of the command set in the StopCommand= parameter, and fix any problems.

KAVA4021-W

The return code of the command specified in the StopCommand key is return-code.

Execution of the service shutdown command has finished.

KAVA4022-E

Stop completion of the service-name service could not be confirmed because an unexpected error occurred.

A system error occurred during service shutdown processing.

(S)

Cancels service shutdown processing.

(O)

Make sure that the command is specified correctly in the StopCommand= parameter. Check the command operation and fix any problems.

KAVA4023-I

The stop of the service-name service was confirmed.

The service indicated in service-name has stopped.

KAVA4026-E

The service stopped because an unexpected error occurred.

A system error occurred during startup sequence control processing.

(S)

Cancels startup sequence control processing.

(O)

Make sure that there is sufficient memory. Also, check whether an error message of the OS is not output. If no such message is output, use the data collection tool to collect data, and then contact the system administrator.

KAVA4027-I

Startup of the startup control service will now start.

Startup sequence control processing has started.

KAVA4028-E

The service will now stop because an attempt to read the registry has failed.

Information is corrupted in JP1/Base or JP1/Power Monitor.

(S)

Cancels startup sequence control processing.

(O)

Make sure that JP1/Base or JP1/Power Monitor is installed correctly.

KAVA4029-E

Power control is not available because an unexpected error occurred.

An error related to JP1/Power Monitor has occurred.

(S)

Cancels startup sequence control processing.

(O)

Check that the JP1/Power Monitor is installed normally. Also, check that JP1/Power Monitor is running normally.

KAVA4030-E

An attempt to notify the power control process of the termination of shutdown processing for a controlled service has failed.

An error occurred during communication with JP1/Power Monitor.

(S)

Cancels startup sequence control processing.

(O)

Make sure that JP1/Power Monitor is operating normally.

KAVA4031-I

The startup control service has started.

The local power operation of JP1/Power Monitor has started.

KAVA4032-E

Startup control is not available because an unexpected error occurred.

An error occurred during an attempt to read data from the startup sequence definition file.

(S)

Cancels startup sequence control processing.

(O)

Check the content of the startup sequence definition file. Also, check whether there is sufficient memory in the system.

KAVA4035-I

The startup control service will now stop.

Startup sequence control processing has ended.

KAVA4036-I

Startup processing for a controlled service has finished.

All service startup processing has finished.

KAVA4037-W

Startup processing for a controlled service has finished, but startup of a service could not be confirmed.

The system cannot confirm that one or more services completed startup.

(O)

Use the integrated trace log to check the message that could not be started, and then fix the error in that service.

KAVA4038-W

Startup control is not available because the parameter giving the startup sequence does not exist.

There is no start sequence definition file.

(S)

Does not control the service startup sequence.

(O)

If you want to use startup control (JP1/Base Control Service), execute the cpysvprm command to create a start sequence definition file.

KAVA4040-E

Startup control is not available because a valid section does not exist in the parameter giving the startup sequence.

The section is unspecified or invalid.

(S)

Does not control the service startup sequence.

(O)

Set the section correctly to control the service startup sequence.

KAVA4041-E

Startup control is not available because valid data does not exist in the parameter giving the startup sequence.

The start sequence definition file has no definitions or the definitions are invalid.

(S)

Does not control the service startup sequence.

(O)

Write the information correctly in the start sequence definition file to control the service startup sequence.

KAVA4042-E

There is a controlled service for which startup completion cannot be confirmed because an unexpected error occurred.

One or more services failed to start due to a system error.

(O)

Check whether there is an error in the StartCommand= parameter setting or other definition.

KAVA4043-E

An error occurred during command execution processing after completion of startup processing for a controlled service.

Processing ended abnormally during execution of the command set in the ReadyCommand= parameter.

(O)

Check whether there is an error in the command set in the ReadyCommand= parameter.

KAVA4044-I

The return code of the command specified in the ReadyCommand key is return-code.

This message reports the return code for the command set in the ReadyCommand= parameter.

KAVA4045-W

Processing was interrupted because an instruction to stop the startup control service was issued during the wait for the end of the command specified in the ReadyCommand key.

Processing was canceled because an instruction to end startup control occurred during the wait for the command set in the ReadyCommand= parameter to complete execution.

(S)

Cancels all processing.

(O)

Avoid manually starting or ending startup control (JP1/Base Control Service) because the service may not be functioning properly.

KAVA4046-E

The service-name service could not stop because the command specified in the StopCommand key was not found.

The command set in the StopCommand= parameter does not exist.

(S)

Cancels execution processing of the command set in the StopCommand= parameter.

(O)

Specify a valid command.

KAVA4047-I

JP1/Power Monitor is not installed, so only startup-sequence processing will be performed.

JP1/Power Monitor is not installed.

(S)

Executes startup sequence processing, but does not execute sequenced shutdown.

(O)

Install JP1/Power Monitor to execute shutdown sequence processing.

KAVA4048-I

The return code of the command specified in the StopReadyCommand key is return-code.

This message reports the return code of the command set in the StopReadyCommand= parameter.

KAVA4049-W

Processing was interrupted because an instruction to stop startup control occurred during the wait for the end of the command specified in the StopReadyCommand command key.

Processing was canceled because an instruction to end startup control occurred during the wait for the command set in the StopReadyCommand= parameter to complete execution.

(S)

Cancels all processing.

(O)

Avoid manually starting or ending startup control (JP1/Base Control Service) because the service may not be functioning properly.

KAVA4101-I

Service starting processing of a starting management function is started.

The service will now start by using the startup control functionality.

(S)

Continues processing.

KAVA4102-I

Service stopping processing of a starting management function is ended.

The service has finished by using the startup control functionality.

(S)

Continues processing.

KAVA4103-I

The start of service starting processing of a starting management function is delayed.(Delaytime=service-startup-delay-time)

The service will start after service-startup-delay-time seconds.

(S)

Continues processing.

KAVA4104-I

Start delay of service starting processing of a starting management function is ended.

The start sequence control function that was started after a delay has ended.

(S)

Continues processing.

KAVA4105-I

Service starting processing timer surveillance is started.(Time=service-startup-processing-timer-monitoring-period)

The timer surveillance of startup processing will be performed for the time indicated in service-startup-processing-timer-monitoring-period (seconds).

(S)

Continues processing.

KAVA4106-I

Service starting processing timer surveillance is ended.

The timer surveillance of startup processing will now end.

(S)

Continues processing.

KAVA4107-W

Completion of service starting processing was undetectable within timer surveillance time.

The service could not be started within the timer monitoring period. Some services may not have been started.

(S)

Continues the start of the service by using the startup control functionality.

(O)

Make sure that the service is running. If it is not, start it manually. If you cannot start the service, restart the machine.

KAVA4108-E

Abnormalities occurred in timer surveillance processing. Timer surveillance is ended. RC2=reason-code

An error occurred during timer surveillance processing.

(S)

Continues the start of the service by using the startup control functionality.

(O)

Make sure that the service is running. If it is not, start it manually. If you cannot start the service, restart the machine.

KAVA4109-I

Service starting processing of a starting management function was not performed.

There was no service to be started.

(S)

Continues processing.

KAVA4110-I

Timer surveillance processing thread stop event creation failure. RC2=reason-code

An attempt to create an event for timer monitoring has failed.

(S)

Does not perform the timer monitoring, but continues the start of the service.

KAVA4111-E

Timer surveillance processing thread starting failure. RC2=reason-code

An attempt to create a thread for timer monitoring has failed. Timer monitoring cannot be performed.

(S)

Does not perform the timer monitoring, but continues the start of the service.

(O)

Make sure that the service is running. If it is not, start it manually. If you cannot start the service, restart the machine.

KAVA4501-I

The JP1/Base Control service will now start.

Startup control (JP1/Base Control Service) is now starting.

KAVA4502-I

Startup of the JP1/Base Control service ended successfully.

Startup control (JP1/Base Control Service) has finished startup.

KAVA4503-I

The JP1/Base Control service will now stop.

Startup control (JP1/Base Control Service) is now stopping.

KAVA4504-E

Power control is not available because an unexpected error occurred.

A system error occurred during processing by the startup control service (JP1/Base Control Service).

(O)

Make sure that JP1/Power Monitor is installed correctly.

KAVA4505-E

Startup control is not available because an unexpected error occurred.

The parameter is unspecified or invalid.

(S)

Cancels processing.

(O)

Specify the parameter correctly.

KAVA4506-W

Startup control is not available because the parameter giving the startup sequence does not exist.

There are no startup sequence parameters.

(S)

Does not perform startup control (JP1/Base Control Service) for the service startup sequence.

(O)

Set the startup sequence parameters correctly.

KAVA4507-E

Startup control is not available because valid data does not exist in the parameter giving the startup sequence.

There are no startup sequence parameters.

(S)

Does not perform startup control (JP1/Base Control Service) for the service startup sequence.

(O)

Set the startup sequence parameters correctly.

KAVA4508-E

The service-name service could not start because an unexpected error occurred.

An error occurred at startup of the service indicated in service-name.

(S)

Cancels startup processing of the indicated service.

(O)

Make sure that the indicated service can be started. Make sure that the settings are correct.

KAVA4509-E

The service-name service could not start because this service does not exist.

The service indicated in service-name does not exist.

(S)

Cancels processing of the indicated service.

(O)

If an error occurs in service-name of JP1/IM and JP1/AJS in a configuration in which JP1/IM and JP1/AJS are not installed, delete the corresponding service name from the startup sequence definition file or add a # mark to make a comment.

If an error occurs in service-name which is not a service of JP1/IM and JP1/AJS, specify a correct service name after checking that the service name specified in the startup sequence definition file is correct.

KAVA4510-W

The service-name service already started.

The service indicated in service-name has already started.

(S)

Does not perform startup sequence control for the indicated service.

(O)

Change the start method of the indicated service from automatic to manual. If this service is linked by dependency relationships with other services, release those dependencies.

KAVA4511-E

Startup completion of the service-name service could not be confirmed because an unexpected error occurred.

The system cannot confirm that the service indicated in service-name completed startup.

(S)

Stops waiting for startup completion.

(O)

Specify a larger value in the Wait= parameter if the setting is too small. Fix the problem that prevented the specified service from starting.

KAVA4512-E

Startup completion of the service-name service could not be confirmed during the period specified in the Wait key.

The system cannot confirm that the service indicated in service-name completed startup.

(S)

Stops waiting for startup completion.

(O)

Specify a larger value in the Wait= parameter if the setting is too small. Fix the problem that prevented the specified service from starting.

KAVA4513-E

The service-name service could not stop because an unexpected error occurred.

A system error occurred during service shutdown processing.

(S)

Cancels service shutdown processing.

(O)

Make sure that a correct value is specified for the stop command in the service section.

KAVA4514-E

The service-name service could not be stopped because the service does not exist.

The service specified in the section is unregistered.

(S)

Cancels shutdown processing of the service indicated in service-name.

(O)

Make sure that the indicated service is registered properly.

KAVA4515-E

Shutdown completion of the service-name service could not be confirmed because an unexpected error occurred.

A system error occurred during service shutdown processing.

(S)

Cancels service shutdown processing.

(O)

Make sure that the command is specified correctly in the StopCommand= parameter. Check the command operation and fix any problems.

KAVA4516-E

Shutdown completion of the service-name service could not be confirmed during the period specified in the StopWait key.

The service did not complete shutdown within the time set in the StopWait= parameter after execution of the command set in the StopCommand= parameter.

(S)

Stops waiting for the service to complete shutdown.

(O)

If necessary, set a larger value in the StopWait= parameter. Check the operation of the command set in the StopCommand= parameter and fix any problems.

KAVA4517-E

An attempt to notify the power control process of the end of shutdown processing for a controlled service has failed.

An error occurred during communication with JP1/Power Monitor.

(S)

Cancels startup sequence control processing.

(O)

Make sure that JP1/Power Monitor is operating normally.

KAVA4518-E

An error occurred during command execution after the end of startup processing for a controlled service.

An attempt to execute the execution file specified in the start sequence definition file (Jp1svprm.dat) has failed.

(S)

Cannot execute the command.

(O)

The details of the error are output to the integrated trace log. According to the output error message, see the start sequence definition file (Jp1svprm.dat) to check whether the paths to and the names of the defined commands are correct, or whether the file can be executed. If the execution file name is incorrect, specify the correct name.

KAVA4519-E

The JP1/Base Control service cannot continue because an unexpected error occurred.

A system error occurred during startup sequence control processing.

(S)

Cancels startup sequence control processing.

(O)

Check the details of the error that are output to the integrated trace log.

KAVA4520-E

The service-name service cannot start because the command specified in the StartCommand key was not found.

The command set in the StartCommand= parameter does not exist.

(S)

Cancels startup of the service indicated in service-name.

(O)

Specify a correct value in the StartCommand= parameter.

KAVA4521-E

The service-name service cannot stop because the command specified in the StopCommand key was not found.

The command set in the StopCommand= parameter does not exist.

(S)

Cancels shutdown of the service indicated in service-name.

(O)

Specify a correct value in the StopCommand= parameter.

KAVA4522-I

Startup processing of controlled services has finished.

All services registered in startup sequence control have finished startup.

KAVA4523-W

Startup processing of controlled services has finished but there is a service for which startup could not be confirmed.

The system cannot confirm startup of one of the services.

(O)

Check the cause of the problem from the log messages.

KAVA4602-E

The parameter file was not found.

No file name is specified in the -d option.

(O)

Specify a file name.

KAVA4603-E

An attempt to delete a parameter file has failed.

There is no file to be deleted.

KAVA4604-I

The parameter file was successfully deleted.

The file was successfully deleted.

KAVA4605-E

No file name is specified after the -n option.

No file name is specified after the -n option.

(O)

Specify a file name.

KAVA4606-E

The JP1/AOM data directory was not found.

There is no JP1/AOM start sequence definition file.

(O)

Make sure that JP1/AOM is installed correctly.

KAVA4607-E

The JP1/IM data directory was not found.

There is no JP1/IM start sequence definition file.

(O)

Make sure that JP1/IM is installed correctly.

KAVA4608-Q

The parameter file (file-name) already exists. Is it OK to overwrite it?

A JP1/Base start sequence definition file already exists.

KAVA4609-E

An attempt to copy the parameter file has failed.

An attempt to copy the start sequence definition file has failed.

(O)

Make sure that the file attributes of the copy-from and copy-to files are correct. If you specified -a, -i, or -n in the command arguments, make sure that the copy-from file exists.

KAVA4610-I

The parameter file copy was successfully copied.

Copying of the start sequence definition file was successful.

KAVA4611-E

A parameter option contains an error.

A parameter option contains an error.

(O)

Specify the correct parameter.

KAVA4612-E

The JP1/Base installation directory is corrupted.

The JP1/Base status is invalid.

(O)

Make sure that JP1/Base is installed correctly.

KAVA4613-E

The JP1/Base data directory was not found.

The JP1/Base status is invalid.

(O)

Make sure that JP1/Base is installed correctly.

KAVA4614-E

Execute the command from the administrator console.

This command must be executed on the administrator console.

(S)

Terminates command processing.

(O)

Re-execute the command on the administrator console.

2.6 User management messages for the authentication server (KAVA5001 to KAVA5902)

KAVA5001-I

The user was successfully added.

The processing for adding the specified user to the authentication server ended normally.

KAVA5002-E

An attempt to add a user has failed.

An attempt to add a user to the authentication server has failed.

(S)

Terminates command processing.

(O)

See the log file to determine the cause of the error.

KAVA5003-I

The command has started.

The jbsadduser command has started.

KAVA5004-E

The logical host name or authentication server is not specified.

The logical host name or authentication server name is not specified in the -h or -s option.

(S)

Terminates command processing.

(O)

Check that the logical host name is specified in the -h option and that the authentication server name is specified in the -s option.

KAVA5006-E

The user name is not specified.

No JP1 user name is specified for registration.

(S)

Terminates command processing without registering a JP1 user.

(O)

Make sure that a user name is specified in an argument on the command line.

KAVA5007-E

The length of the user name exceeds 31 characters.

The length of the JP1 user name exceeds 31 characters.

(S)

Terminates command processing.

(O)

Specify a JP1 user name in an argument on the command line, using no more than 31 characters.

KAVA5008-E

The user JP1-user-name already exists.

The JP1 user name specified for registration already exists.

(S)

Cancels registering a new user.

(O)

Do not specify an already registered user name.

KAVA5011-E

The maximum number of users has been reached.

The number of users on the authentication server has reached the upper limit.

(S)

Terminates command processing without registering the user.

(O)

Check whether the number of users on the authentication server has reached the upper limit.

KAVA5014-E

The password length is invalid. Specify 6 to 32 characters.

The system enters the input mode.

(S)

Enters the input mode.

(O)

Enter the correct password.

KAVA5016-E

An invalid character is specified in the user name.

The JP1 user name cannot contain spaces, tabs, control characters or the following characters: *"'^[]{}():;|\/=,+?<>

(S)

Terminates command processing.

(O)

Specify a user name with valid characters, and then re-execute the command.

KAVA5017-E

Memory is insufficient.

There is not enough system memory to execute the command.

(S)

Terminates command processing.

(O)

Re-execute the command.

Check for insufficient memory.

KAVA5018-E

An error occurred during execution of the jbsadduser command.

An error occurred during execution of the jbsadduser command.

(S)

Terminates command processing.

(O)

Check the OS resources.

KAVA5019-E

An invalid argument was passed to the function function-name.

An invalid argument was passed to the function.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5022-E

The authentication server authentication-server-name is either not running or not responding.

The authentication server is not running or is not responding.

(S)

Terminates command processing because the authentication server is not responding.

(O)

Make sure that:

The JP1/Base service is running.

The specified authentication server exists.

The network connection is correct.

Both the host on which the command was executed and the authentication server use the same IP address version (IPv4 or IPv6).

For details about how to check the IP address version (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the Job Management Partner 1/Base User's Guide.

KAVA5023-E

An argument passed to the authentication server is invalid.

An invalid argument was passed to the authentication server.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5024-E

The logical host logical-host-name does not exist.

The specified logical host does not exist.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified on the command line is correct, and that the value in the JP1_HOSTNAME environment variable is correct.

KAVA5026-E

Common definition information does not exist for the authentication server.

The SVNAME label does not exist in the common definition information.

(S)

Terminates command processing.

(O)

Check whether the SVNAME label exists in the common definition for the logical host.

KAVA5027-W

The buffer went out of range during execution of the JP1/Base common definition API function jp1BsCnfGetStringValue().

A memory shortage occurred during execution of the API function jp1BsCnfGetStringValue().

KAVA5028-E

The user lacks permission to reference the common definition information.

There is no permission to read a value from the common definition information.

(S)

If an error occurred during acquisition of the SVNAME value from the common definition information, the system terminates command processing. If an attempt to acquire any other value from the common definition information failed, the system uses the default to continue processing.

(O)

The common definition information may contain incorrect settings. Check the settings.

KAVA5031-E

An attempt to send data to the authentication server has failed.

The command failed to send data to the authentication server.

(S)

Terminates command processing.

(O)

Make sure that the network connection is correct.

KAVA5032-W

Due to a timeout, {connect|send|receive} has failed.

The authentication server could not be connected.

Data could not be sent to or received from the authentication server because the connection line did not respond properly in time.

Connection could not be established because of a timeout.

KAVA5033-E

An attempt to receive data from the authentication server has failed.

Data could not be received from the authentication server. Alternatively, the authentication server does not support the function.

(S)

Terminates command processing.

(O)

Make sure that the network connection is correct and the version of the authentication server is correct.

KAVA5034-W

An attempt to create a socket has failed.

A socket could not be created. The command retries creating a socket for communication.

KAVA5038-E

An error occurred during creation of a hashed password.

A hashed password could not be created.

(S)

Terminates command processing.

(O)

Make sure that the correct version of the hash library is being used.

KAVA5041-E

An error occurred during initialization of the base communication functionality.

The API function jp1BsCommInit() failed during initialization of the base communication functionality for the specified logical host.

(S)

Terminates command processing.

(O)

Check whether the JP1_HOSTNAME label exists in the common definition information for the logical host.

KAVA5042-W

A temporary error occurred while data was being sent to the authentication server. The system will try again.

A temporary sending error occurred. The command will retry sending data to the authentication server.

KAVA5043-W

A temporary error occurred while data was being received from the authentication server. The system will try again.

A temporary reception error occurred. The command will retry receiving data from the authentication server.

KAVA5044-E

An attempt to bind the socket has failed.

The socket cannot be bound.

(S)

Terminates command processing.

(O)

Make sure that the logical-host entry matches the IP address of the local machine.

KAVA5045-E

An attempt to change the socket to non-blocking mode has failed.

The command failed to change the socket to the non-blocking mode.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5046-E

An attempt to change the socket to blocking mode has failed.

The command failed to change the socket to the blocking mode.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5049-E

An error occurred on the authentication server authentication-server-name.

An error occurred on the authentication server.

(S)

Terminates command processing.

(O)

Check the log on the authentication server.

KAVA5051-E

An attempt to execute the common definition API function (jp1BsCnfGetStringValue() or jp1BsCnfGetULongValue()) has failed. (error number = error-number)

A value could not be read from the common definition information.

(S)

If an error occurred during acquisition of the SVNAME value from the common definition information, the system terminates command processing. If an attempt to acquire any other value from the common definition information failed, the system uses the default to continue processing.

(O)

The common definition information may contain incorrect settings. Check the settings.

KAVA5055-E

The authentication server authentication-server-name was unable to be recognized.

The specified authentication server could not be recognized.

(S)

Terminates command processing.

(O)

Make sure that the specified authentication server exists.

KAVA5057-E

An attempt to obtain the label value of JP1_HOSTNAME from the common definition information has failed.

The host-name value could not be obtained from the common definition information.

(S)

Terminates command processing.

(O)

Check whether the JP1_HOSTNAME label exists in the common definition information.

KAVA5058-E

The specified address family cannot be used in TCP networks.

The address family of the specified authentication server is not supported in TCP networks.

(S)

Terminates command processing.

(O)

Check the OS environment.

KAVA5059-E

The password encryption library could not be loaded.

The hash library for passwords cannot be loaded.

(S)

Terminates command processing.

(O)

Make sure that the hash library exists.

KAVA5060-E

The specified hash value type is not supported.

The specified hash algorithm is not supported.

(S)

Terminates command processing.

(O)

Use a supported hash library.

KAVA5062-E

Root privileges are required to execute the command.

Executing the jbsadduser command requires root privileges.

(S)

Terminates command processing.

(O)

Only a user who has root privileges can execute the jbsadduser command. Execute the command as a user who has root privileges.

KAVA5063-W

The label entry does not exist in the common definition information.

The label does not exist in the common definition information.

KAVA5064-W

The value of JP1_BIND_ADDR in the common definition information is invalid. Startup will use ANY.

The value of the JP1_BIND_ADDR label in the common definition information is not ANY or IP.

KAVA5065-E

The command line has a syntax error.

The command line has a syntax error.

(S)

Terminates command processing.

(O)

Make sure that proper arguments are specified on the command line.

KAVA5069-E

The authentication server authentication-server-name cannot be reached.

The authentication server cannot be reached.

(S)

Terminates command processing.

(O)

Check the network.

KAVA5070-E

The length of the logical hostname exceeds 255 characters.

The specified logical host name exceeds 255 characters.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified in the -h option on the command line, or the value of the JP1_HOSTNAME environment variable, does not exceed 255 characters.

KAVA5071-E

The length of the authentication server name exceeds 255 characters.

The specified authentication server name exceeds 255 characters.

(S)

Terminates command processing.

(O)

Make sure that the specified authentication server name does not exceed 255 characters.

KAVA5072-E

An error occurred during execution of the API function jp1BsCommInit(). (error number = error-number)

The API function jp1BsCommInit() failed.

(S)

Terminates command processing.

(O)

Check whether the JP1_HOSTNAME label exists under the JP1/Config/logical-host/JP1BASE key in the common definition information.

KAVA5073-E

An attempt to open the catalog file has failed. (error number = error-number)

The jp1BsSessAclCmdMsg.cat catalog file could not be opened.

(S)

Terminates command processing because the catalog file cannot be loaded.

(O)

Make sure that the catalog file exists.

KAVA5074-E

The catalog file path exceeded the maximum limit while the catalog file was being opened.

A memory shortage occurred while the jp1BsSessAclCmdMsg.cat catalog file was being opened.

(S)

Terminates command processing because there is insufficient memory.

(O)

Re-execute the command.

Make sure that the catalog file does not exceed the maximum length.

KAVA5075-E

An attempt to open the catalog file has failed.

The jp1BsSessAclCmdMsg.cat message catalog file cannot be opened.

(S)

Terminates command processing.

(O)

Check this file for read permission.

KAVA5076-W

An attempt to acquire the label value from the common definition information has failed.

The specified label value could not be read from the common definition information.

KAVA5077-W

The path exceeded the maximum length while the log file was being opened.

The path to the individual log file (JP1BASE_LOGDIR label value) exceeded the maximum length.

KAVA5078-W

An error occurred during initialization of the HNTR Library. (error number = error-number)

The HNTR library could not be initialized.

KAVA5079-W

Due to an error in the API function FormatMessage(), an attempt to acquire the message has failed. (error number = error-number)

An attempt to acquire the message using the API function FormatMessage() failed.

KAVA5080-E

An internal error occurred in the JP1/BASE common definition library.

An internal error occurred in the common definition library.

(S)

If an error occurred during acquisition of the SVNAME value from the common definition information, the system terminates command processing. If an attempt to acquire any other value from the common definition information failed, the system uses the default to continue processing.

(O)

The common definition information may contain incorrect settings. Check the settings.

KAVA5081-W

An error occurred during execution of the API function API-name. (error number = error-number)

A temporary error occurred during execution of an API function.

KAVA5082-W

The system will attempt to connect to the authentication server authentication-server-name again.

A temporary connection error occurred. Connection to the authentication server will be reattempted.

KAVA5083-E

An attempt to create a socket has failed.

A socket could not be created.

(S)

Terminates command processing.

(O)

Check the OS resources.

KAVA5084-E

The hash library function API-name has failed. (error number = error-number)

The hash library could not be opened or loaded.

(S)

Terminates command processing.

(O)

Make sure that the jp1bshash DLL exists.

This message is output with one of the following message IDs. Check that message.

KAVA5*17, KAVA5*38, KAVA5*59, KAVA5*60

KAVA5085-E

An attempt to retrieve host information for the specified logical host logical-host-name has failed.

The host information for the specified logical host is invalid.

(S)

Terminates command processing.

(O)

Make sure that the /etc/hosts file contains valid settings for the specified logical host.

KAVA5089-E

An invalid character is specified in the password.

(S)

Enters the input mode.

(O)

Enter the correct password.

KAVA5092-W

An attempt to acquire common definition information for logical host logical-host-name has failed. Further logging will not be done.

This message reports that the log data will not be output to the specified logical host because an attempt to obtain the common definition information for the logical host has failed.

KAVA5094-E

The logical-host-name/JP1BASE/LOG_CONTROL/JBSSESS key was not found.

The JBSSESS key was not found on the specified logical host.

(S)

Terminates command processing.

(O)

Make sure that the JBSSESS key exists in the common definition information for the specified logical host.

KAVA5095-E

The JP1_DEFAULT/JP1BASE/LOG_CONTROL/JBSSESS key was not found.

The JBSSESS key was not found on the physical host.

(S)

Terminates command processing.

(O)

Make sure that the JBSSESS key exists in the common definition information for the physical host.

KAVA5096-E

Due to an error in the API function jp1BsCommInit(), an attempt to initialize the base communication functionality for the physical host has failed. (error number = error-number)

An error occurred during initialization of the base communication functionality for the physical host (JP1_DEFAULT).

(S)

Terminates command processing.

(O)

Wait a while, and then re-execute the command.

KAVA5099-E

The password is not specified.

(S)

Enters the input mode.

(O)

Enter the correct password.

KAVA5101-I

The user was successfully deleted.

The processing for deleting the specified user from the authentication server ended normally.

KAVA5102-E

An attempt to delete a user has failed.

An attempt to delete a user from the authentication server has failed.

(S)

Terminates command processing.

(O)

See the log file to determine the cause of the error.

KAVA5103-I

The command has started.

The jbsrmuser command has started.

KAVA5104-E

The logical host name or authentication server is not specified.

The logical host name or authentication server name is not specified in the -h or -s option.

(S)

Terminates command processing.

(O)

Check that the logical host name is specified in the -h option and that the authentication server name is specified in the -s option.

KAVA5106-E

The user name is not specified.

No JP1 user name is specified for deletion.

(S)

Terminates command processing without deleting a JP1 user.

(O)

Make sure that a user name is specified in an argument on the command line.

KAVA5107-E

The length of the user name exceeds 31 characters.

The length of the JP1 user name exceeds 31 characters.

(S)

Terminates command processing.

(O)

Specify a JP1 user name in an argument on the command line, using no more than 31 characters.

KAVA5109-E

The user JP1-user-name does not exist.

The specified JP1 user name is not registered in the authentication server.

(S)

Cancels deletion of the user.

(O)

Make sure that the user name is registered before you attempt to delete it.

KAVA5116-E

An invalid character is specified in the user name.

The JP1 user name cannot contain spaces, tabs, control characters or the following characters: *"'^[]{}():;|\/=,+?<>

(S)

Terminates command processing.

(O)

Specify a user name with valid characters, and then re-execute the command.

KAVA5117-E

Memory is insufficient.

There is not enough system memory to execute the command.

(S)

Terminates command processing.

(O)

Re-execute the command.

Check for insufficient memory.

KAVA5118-E

An error occurred during execution of the jbsrmuser command.

An error occurred during execution of the jbsrmuser command.

(S)

Terminates command processing.

(O)

Check the OS resources.

KAVA5119-E

An invalid argument was passed to the function function-name.

An invalid argument was passed to the function.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5122-E

The authentication server authentication-server-name is either not running or not responding.

The authentication server is not running or is not responding.

(S)

Terminates command processing because the authentication server is not responding.

(O)

Make sure that:

The JP1/Base service is running.

The specified authentication server exists.

The network connection is correct.

Both the host on which the command was executed and the authentication server use the same IP address version (IPv4 or IPv6).

For details about how to check the IP address version (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the Job Management Partner 1/Base User's Guide.

KAVA5123-E

An argument passed to the authentication server is invalid.

An invalid argument was passed to the authentication server.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5124-E

The logical host logical-host-name does not exist.

The specified logical host does not exist.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified on the command line is correct, and that the value in the JP1_HOSTNAME environment variable is correct.

KAVA5126-E

Common definition information does not exist for the authentication server.

The SVNAME label does not exist in the common definition information.

(S)

Terminates command processing.

(O)

Check whether the SVNAME label exists in the common definition information for the logical host.

KAVA5127-W

The buffer went out of range during execution of the JP1/Base common definition API function jp1BsCnfGetStringValue().

A memory shortage occurred during execution of the API function jp1BsCnfGetStringValue().

KAVA5128-E

The user does not have permission to reference the common definition information.

There is no permission to read the common definition information.

(S)

If an error occurred during acquisition of the SVNAME value from the common definition information, the system terminates command processing. If an attempt to acquire any other value from the common definition information failed, the system uses the default to continue processing.

(O)

The common definition information may contain incorrect settings. Check the settings.

KAVA5131-E

An attempt to send data to the authentication server has failed.

The command failed to send data to the authentication server.

(S)

Terminates command processing.

(O)

Make sure that the network connection is correct.

KAVA5132-W

Due to a timeout, {connect|send|receive} has failed.

The authentication server could not be connected.

Data could not be sent to or received from the authentication server because the connection line did not respond properly in time.

Connection could not be established because of a timeout.

KAVA5133-E

An attempt to receive data from the authentication server has failed.

Data could not be received from the authentication server.

(S)

Terminates command processing.

(O)

Make sure that the network connection is correct.

KAVA5134-W

An attempt to create a socket has failed.

A socket could not be created. The command retries creating a socket for communication.

KAVA5141-E

An error occurred during initialization of the base communication functionality.

The API function jp1BsCommInit() failed during initialization of the base communication functionality for the specified logical host.

(S)

Terminates command processing.

(O)

Check whether the JP1_HOSTNAME label exists in the common definition information for the logical host.

KAVA5142-W

A temporary error occurred while data was being sent to the authentication server. The system will try again.

A temporary sending error occurred. The command will retry sending data to the authentication server.

KAVA5143-W

A temporary error occurred while data was being received from the authentication server. The system will try again.

A temporary reception error occurred. The command will retry receiving data from the authentication server.

KAVA5144-E

An attempt to bind the socket has failed.

The socket cannot be bound.

(S)

Terminates command processing.

(O)

Make sure that the logical-host entry matches the IP address of the local machine.

KAVA5145-E

An attempt to change the socket to non-blocking mode has failed.

The command failed to change the socket to the non-blocking mode.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5146-E

An attempt to change the socket to blocking mode has failed.

The command failed to change the socket to the blocking mode.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5149-E

An error occurred on the authentication server authentication-server-name.

An error occurred on the authentication server.

(S)

Terminates command processing.

(O)

Check the log on the authentication server.

KAVA5151-E

An attempt to execute the common definition API function (jp1BsCnfGetStringValue() or jp1BsCnfGetULongValue()) has failed. (error number = error-number)

An attempt to read a value from the common definition information has failed.

(S)

If an error occurred during acquisition of the SVNAME value from the common definition information, the system terminates command processing. If an attempt to acquire any other value from the common definition information failed, the system uses the default to continue processing.

(O)

The common definition information may contain incorrect settings. Check the settings.

KAVA5155-E

The authentication server authentication-server-name was unable to be recognized.

The specified authentication server could not be recognized.

(S)

Terminates command processing.

(O)

Make sure that the specified authentication server exists.

KAVA5157-E

An attempt to obtain the label value of JP1_HOSTNAME from the common definition information has failed.

The host-name value could not be obtained from the common definition information.

(S)

Terminates command processing.

(O)

Make sure that the JP1_HOSTNAME label exists in the common definition information.

KAVA5158-E

The specified address family cannot be used in TCP networks.

The address family of the specified authentication server is not supported in TCP networks.

(S)

Terminates command processing.

(O)

Check the OS environment.

KAVA5162-E

Root privileges are required to execute the command.

Executing the jbsrmuser command requires root privileges.

(S)

Terminates command processing.

(O)

Only a user who has root privileges can execute the jbsrmuser command. Execute the command as a user who has root privileges.

KAVA5163-W

The label entry does not exist in the common definition information.

The label does not exist in the common definition information.

KAVA5164-W

The value of JP1_BIND_ADDR in the common definition information is invalid. Startup will use ANY.

The value of the JP1_BIND_ADDR label in the common definition information is not ANY or IP.

KAVA5165-E

The command line has a syntax error.

The command line has a syntax error.

(S)

Terminates command processing.

(O)

Make sure that proper arguments are specified on the command line.

KAVA5169-E

The authentication server authentication-server-name cannot be reached.

The authentication server cannot be reached.

(S)

Terminates command processing.

(O)

Check the network.

KAVA5170-E

The length of the logical hostname exceeds 255 characters.

The specified logical host name exceeds 255 characters.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified in the -h option on the command line, or the value of the JP1_HOSTNAME environment variable, does not exceed 255 characters.

KAVA5171-E

The length of the authentication server name exceeds 255 characters.

The specified authentication server name exceeds 255 characters.

(S)

Terminates command processing.

(O)

Make sure that the specified authentication server name does not exceed 255 characters.

KAVA5172-E

An error occurred during execution of the API function jp1BsCommInit(). (error number = error-number)

The API function jp1BsCommInit() failed.

(S)

Terminates command processing.

(O)

Check whether the JP1_HOSTNAME label exists under the JP1/Config/logical-host/JP1BASE key in the common definition information.

KAVA5173-E

An attempt to open the catalog file has failed. (error number = error-number)

The jp1BsSessAclCmdMsg.cat catalog file could not be opened.

(S)

Terminates command processing because the catalog file cannot be loaded.

(O)

Make sure that the catalog file exists.

KAVA5174-E

The catalog file path exceeded the maximum limit while the catalog file was being opened.

A memory shortage occurred while the jp1BsSessAclCmdMsg.cat catalog file was being opened.

(S)

Terminates command processing because there is insufficient memory.

(O)

Re-execute the command.

Make sure that the catalog file does not exceed the maximum length.

KAVA5175-E

An attempt to open the catalog file has failed.

The jp1BsSessAclCmdMsg.cat message catalog file cannot be opened.

(S)

Terminates command processing.

(O)

Check this file for read permission.

KAVA5176-W

An attempt to acquire the label value from the common definition information has failed.

The specified label value could not be read from the common definition information.

KAVA5177-W

The log file path exceeded the maximum length.

The path to the individual log file (JP1BASE_LOGDIR label value) exceeded the maximum length.

KAVA5178-W

An error occurred during initialization of the HNTR Library. (error number = error-number)

The HNTR library could not be initialized.

KAVA5179-W

Due to an error in the API function FormatMessage(), an attempt to acquire the message has failed. (error number = error-number)

An attempt to acquire the message using the API function FormatMessage() failed.

KAVA5180-E

An internal error occurred in the JP1/BASE common definition library.

An internal error occurred in the common definition library.

(S)

If an error occurred during acquisition of the SVNAME value from the common definition information, the system terminates command processing. If an attempt to acquire any other value from the common definition information failed, the system uses the default to continue processing.

(O)

The common definition information may contain incorrect settings. Check the settings.

KAVA5181-W

An error occurred during execution of the API function API-name. (error number = error-number)

A temporary error occurred during execution of an API function.

KAVA5182-W

The system will attempt to connect to the authentication server authentication-server-name again.

A temporary connection error occurred. Connection to the authentication server will be reattempted.

KAVA5183-E

An attempt to create a socket has failed.

A socket could not be created.

(S)

Terminates command processing.

(O)

Check the OS resources.

KAVA5185-E

An attempt to retrieve host information for the specified logical host logical-host-name has failed.

The host information for the specified logical host is invalid.

(S)

Terminates command processing.

(O)

Make sure that the /etc/hosts file contains valid settings for the specified logical host.

KAVA5192-W

An attempt to acquire the common definition information for logical host logical-host-name has failed. Further logging will not be done.

This message reports that the log data will not be output to the specified logical host because an attempt to obtain the common definition information for the logical host has failed.

KAVA5194-E

The logical-host-name/JP1BASE/LOG_CONTROL/JBSSESS key was not found in the common definition information.

The JBSSESS key was not found on the specified logical host.

(S)

Terminates command processing.

(O)

Make sure that the JBSSESS key exists in the common definition information for the specified logical host.

KAVA5195-E

The JP1_DEFAULT/JP1BASE/LOG_CONTROL/JBSSESS key was not found.

The JBSSESS key was not found on the physical host.

(S)

Terminates command processing.

(O)

Check whether the JBSSESS key exists in the common definition information for the physical host.

KAVA5196-E

Due to an error in the API function jp1BsCommInit(), an attempt to initialize the base communication functionality for the physical host has failed. (error number = error-number)

An error occurred during initialization of the base communication functionality for the physical host (JP1_DEFAULT).

(S)

Terminates command processing.

(O)

Wait a while, and then re-execute the command.

KAVA5201-I

The password was successfully changed.

The processing for changing the password for the specified user ended normally.

KAVA5202-E

An attempt to change the password has failed.

An attempt to change the password for the specified user has failed.

(S)

Terminates command processing.

(O)

See the log file to determine the cause of the error.

KAVA5203-I

The command has started.

The jbschgpasswd command has started.

KAVA5204-E

The logical host name or authentication server is not specified.

The logical host name or authentication server name is not specified in the -h or -s option.

(S)

Terminates command processing.

(O)

Check that the logical host name is specified in the -h option and that the authentication server name is specified in the -s option.

KAVA5206-E

The user name is not specified.

No JP1 user name is specified for password change.

(S)

Terminates command processing without changing the password of a JP1 user.

(O)

Make sure that a user name is specified in an argument on the command line.

KAVA5207-E

The length of the user name exceeds 31 characters.

The length of the JP1 user name exceeds 31 characters.

(S)

Terminates command processing.

(O)

Specify a JP1 user name in an argument on the command line, using no more than 31 characters.

KAVA5209-E

The user JP1-user-name does not exist.

The JP1 user name specified for password change is not registered in the authentication server.

(S)

Cancels changing the password of the user.

(O)

Make sure that the user name is registered before you attempt to change the password.

KAVA5214-E

The password length is invalid. Specify 6 to 32 characters.

(S)

Enters the input mode.

(O)

Enter the correct password.

KAVA5215-E

The old password is incorrect.

The entered password is not the old password.

(S)

Terminates command processing.

(O)

Re-execute the command and enter the correct old password.

KAVA5216-E

An invalid character is specified in the user name.

The JP1 user name cannot contain spaces, tabs, control characters or the following characters: *"'^[]{}():;|\/=,+?<>

(S)

Terminates command processing.

(O)

Specify a user name with valid characters, and then re-execute the command.

KAVA5217-E

Memory is insufficient.

There is not enough system memory to execute the command.

(S)

Terminates command processing.

(O)

Re-execute the command.

Check for insufficient memory.

KAVA5218-E

An error occurred during execution of the jbschgpasswd command.

An error occurred during execution of the jbschgpasswd command.

(S)

Terminates command processing.

(O)

Check the OS resources.

KAVA5219-E

An invalid argument was passed to the function function-name.

An invalid argument was passed to the function.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5220-E

An exception occurred while the password file was being used.

An error occurred on the server while the password file was being used.

(S)

Terminates command processing.

(O)

Make sure that the JP1_Passwd file in the conf/user_acl directory is valid.

KAVA5222-E

The authentication server authentication-server-name is either not running or not responding.

The authentication server is not running is not responding.

(S)

Terminates command processing because the authentication server is not responding.

(O)

Make sure that:

The JP1/Base service is running.

The specified authentication server exists.

The network connection is correct.

Both the host on which the command was executed and the authentication server use the same IP address version (IPv4 or IPv6).

For details about how to check the IP address version (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the Job Management Partner 1/Base User's Guide.

KAVA5223-E

An argument passed to the authentication server was invalid.

An invalid argument was passed to the authentication server.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5224-E

The logical host logical-host-name does not exist.

The specified logical host does not exist.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified on the command line is correct, and that the value in the JP1_HOSTNAME environment variable is correct.

KAVA5226-E

Common definition information does not exist for the authentication server.

The SVNAME label does not exist in the common definition information.

(S)

Terminates command processing.

(O)

Check whether the SVNAME label exists in the common definition information for the logical host.

KAVA5227-W

The buffer went out of range during execution of the JP1/Base common definition API function jp1BsCnfGetStringValue().

A memory shortage occurred during execution of the API function jp1BsCnfGetStringValue().

KAVA5228-E

The user lacks permission to reference the common definition information.

There is no permission to read the common definition information.

(S)

If the error occurred during acquisition of the SVNAME value from the common definition information, the system terminates command processing. If an attempt to acquire any other value from the common definition information failed, the system uses the default to continue processing.

(O)

The common definition information may contain incorrect settings. Check the settings.

KAVA5231-E

An attempt to send data to the authentication server has failed.

The command failed to send data to the authentication server.

(S)

Terminates command processing.

(O)

Make sure that the network connection is correct.

KAVA5232-W

Due to a timeout, {connect|send|receive} has failed.

The authentication server could not be connected.

Data could not be sent to or received from the authentication server because the connection line did not respond properly in time.

Connection could not be established because of a timeout.

KAVA5233-E

An attempt to receive data from the authentication server has failed.

Data could not be received from the authentication server.

(S)

Terminates command processing.

(O)

Make sure that the network connection is correct.

KAVA5234-W

An attempt to create a socket has failed.

A socket could not be created. The command retries to create a socket for communication.

KAVA5238-E

An error occurred during creation of a hashed password.

A hashed password could not be created.

(S)

Terminates command processing.

(O)

Make sure that the correct version of the hash library is being used.

KAVA5241-E

An error occurred during initialization of the base communication functionality.

The API function jp1BsCommInit() failed during initialization of the base communication functionality for the specified logical host.

(S)

Terminates command processing.

(O)

Check whether the JP1_HOSTNAME label exists in the common definition information for the logical host.

KAVA5242-W

A temporary error occurred while data was being sent to the authentication server. The system will try again.

A temporary sending error occurred. The command will retry to send data to the authentication server.

KAVA5243-W

A temporary error occurred while data was being received from the authentication server. The system will try again.

A temporary reception error occurred. The command will retry to receive data from the authentication server.

KAVA5244-E

An attempt to bind the socket has failed.

The socket cannot be bound.

(S)

Terminates command processing.

(O)

Make sure that the logical-host entry matches the IP address of the local machine.

KAVA5245-E

An attempt to change the socket to non-blocking mode has failed.

The command failed to change the socket to the non-blocking mode.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5246-E

An attempt to change the socket to blocking mode has failed.

The command failed to change the socket to the blocking mode.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5249-E

An error occurred on the authentication server authentication-server-name.

An error occurred on the authentication server.

(S)

Terminates command processing.

(O)

Check the log on the authentication server.

KAVA5251-E

An attempt to execute the common definition API function (jp1BsCnfGetStringValue() or jp1BsCnfGetULongValue()) has failed. (error number = error-number)

A value could not be read from the common definition information.

(S)

If the error occurred during acquisition of the SVNAME value from the common definition information, the system terminates command processing. If an attempt to acquire any other value from the common definition information failed, the system uses the default to continue processing.

(O)

The common definition information may contain incorrect settings. Check the settings.

KAVA5255-E

The authentication server authentication-server-name was unable to be recognized.

The specified authentication server could not be recognized.

(S)

Terminates command processing.

(O)

Make sure that the specified authentication server exists.

KAVA5257-E

An attempt to get the label value of JP1_HOSTNAME from the common definition information has failed.

The host-name value could not be obtained from the common definition information.

(S)

Terminates command processing.

(O)

Make sure that the JP1_HOSTNAME label exists in the common definition information.

KAVA5258-E

The specified address family cannot be used in TCP networks.

The address family of the specified authentication server is not supported in TCP networks.

(S)

Terminates command processing.

(O)

Check the OS environment.

KAVA5259-E

The password encryption library cannot be loaded.

The hash library for passwords cannot be loaded.

(S)

Terminates command processing.

(O)

Make sure that the hash library exists.

KAVA5260-E

The specified hash value type is not supported.

The specified hash algorithm is not supported.

(S)

Terminates command processing.

(O)

Use a supported hash library.

KAVA5262-E

Root privileges are required to execute the command.

Executing the jbschgpasswd command requires root privileges.

(S)

Terminates command processing.

(O)

Only a user who has root privileges can execute the jbschgpasswd command. Execute the command as a user who has root privileges.

KAVA5263-W

The label entry does not exist in the common definition information.

The label does not exist in the common definition information.

KAVA5264-W

The value of JP1_BIND_ADDR in the common definition information is invalid. Startup will use ANY.

The value of the JP1_BIND_ADDR label in the common definition information is not ANY or IP.

KAVA5265-E

The command line has a syntax error.

The command line has a syntax error.

(S)

Terminates command processing.

(O)

Make sure that proper arguments are specified on the command line.

KAVA5269-E

The authentication server authentication-server-name could not be reached.

The authentication server cannot be reached.

(S)

Terminates command processing.

(O)

Check the network.

KAVA5270-E

The length of the logical hostname exceeds 255 characters.

The specified logical host name exceeds 255 characters.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified in the -h option on the command line, or the value of the JP1_HOSTNAME environment variable, does not exceed 255 characters.

KAVA5271-E

The length of the authentication server name exceeds 255 characters.

The specified authentication server name exceeds 255 characters.

(S)

Terminates command processing.

(O)

Make sure that the specified authentication server name does not exceed 255 characters.

KAVA5272-E

An error occurred during execution of the API function jp1BsCommInit(). (error number = error-number)

The API function jp1BsCommInit() failed.

(S)

Terminates command processing.

(O)

Check whether the JP1_HOSTNAME label exists under the JP1/Config/logical-host/JP1BASE key in the common definition information.

KAVA5273-E

An attempt to open the catalog file has failed. (error number = error-number)

The jp1BsSessAclCmdMsg.cat catalog file could not be opened.

(S)

Terminates command processing because the catalog file cannot be loaded.

(O)

Make sure that the catalog file exists.

KAVA5274-E

The catalog file path exceeded the maximum limit while the catalog file was being opened.

A memory shortage occurred while the jp1BsSessAclCmdMsg.cat catalog file was being opened.

(S)

Terminates command processing because there is insufficient memory.

(O)

Re-execute the command.

Make sure that the catalog file does not exceed the maximum length.

KAVA5275-E

An attempt to open the catalog file has failed.

The jp1BsSessAclCmdMsg.cat message catalog file cannot be opened.

(S)

Terminates command processing.

(O)

Check this file for read permission.

KAVA5276-W

An attempt to acquire the label value from the common definition information has failed.

The specified label value could not be read from the common definition information.

KAVA5277-W

The log file path exceeded the maximum length.

The path to the individual log file (JP1BASE_LOGDIR label value) exceeded the maximum length.

KAVA5278-W

An error occurred during initialization of the HNTR Library. (error number = error-number)

The HNTR library could not be initialized.

KAVA5279-W

Due to an error in the API function FormatMessage(), an attempt to acquire the message has failed. (error number = error-number)

An attempt to acquire the message using the API function FormatMessage() failed.

KAVA5280-E

An internal error occurred in the JP1/BASE common definition library.

An internal error occurred in the common definition library.

(S)

If an error occurred during acquisition of the SVNAME value from the common definition information, the system terminates command processing. If an attempt to acquire any other value from the common definition information failed, the system uses the default to continue processing.

(O)

The common definition information may contain incorrect settings. Check the settings.

KAVA5281-W

An error occurred during execution of the API function API-name. (error number = error-number)

A temporary error occurred during execution of an API function.

KAVA5282-W

The system will attempt to connect to the authentication server authentication-server-name again.

A temporary connection error occurred. Connection to the authentication server will be reattempted.

KAVA5283-E

An attempt to create a socket has failed.

A socket could not be created.

(S)

Terminates command processing.

(O)

Check the OS resources.

KAVA5284-E

The hash library function API-name has failed. (error number = error-number)

The hash library could not be opened or loaded.

(S)

Terminates command processing.

(O)

Make sure that the jp1bshash DLL exists.

This message is output with one of the following message IDs. Check that message.

KAVA5*17, KAVA5*38, KAVA5*59, KAVA5*60

KAVA5285-E

An attempt to retrieve host information for the specified logical host logical-host-name has failed.

The host information for the specified logical host is invalid.

(S)

Terminates command processing.

(O)

Make sure that the /etc/hosts file contains valid settings for the specified logical host.

KAVA5289-E

An invalid character is specified in the password.

(S)

Enters the input mode.

(O)

Enter the correct password.

KAVA5292-W

An attempt to acquire the common definition information for logical host logical-host-name has failed. Further logging will not be done.

This message reports that the log data will not be output to the specified logical host because the common definition information for the logical host could not be acquired.

KAVA5294-E

The logical-host-name/JP1BASE/LOG_CONTROL/JBSSESS key was not found.

The JBSSESS key was not found on the specified logical host.

(S)

Terminates command processing.

(O)

Make sure that the JBSSESS key exists in the common definition information for the specified logical host.

KAVA5295-E

The JP1_DEFAULT/JP1BASE/LOG_CONTROL/JBSSESS key was not found.

The JBSSESS key was not found on the physical host.

(S)

Terminates command processing.

(O)

Check whether the JBSSESS key exists in the common definition information for the physical host.

KAVA5296-E

Due to an error in the API function jp1BsCommInit(), an attempt to initialize the base communication functionality for the physical host has failed. (error number = error-number)

An error occurred during initialization of the base communication functionality for the physical host (JP1_DEFAULT).

(S)

Terminates command processing.

(O)

Wait a while, and then re-execute the command.

KAVA5299-E

The password is not specified.

(S)

Enters the input mode.

(O)

Enter the correct password.

KAVA5301-I

Registered users were successfully listed.

An attempt to list the users registered in the authentication server ended normally.

KAVA5302-E

An attempt to list registered users has failed.

An attempt to list the registered JP1 users has failed.

(S)

Terminates command processing.

(O)

See the log file to determine the cause of the error.

KAVA5303-I

The command has started.

The jbslistuser command has started.

KAVA5304-E

The logical host name or authentication server is not specified.

The logical host name or authentication server name is not specified in the -h or -s option.

(S)

Terminates command processing.

(O)

Check that the logical host name is specified in the -h option and that the authentication server name is specified in the -s option.

KAVA5317-E

Memory is insufficient.

There is not enough system memory to execute the command.

(S)

Terminates command processing.

(O)

Re-execute the command.

Check for insufficient memory.

KAVA5318-E

An error occurred during execution of the jbslistuser command.

An error occurred during execution of the jbslistuser command.

(S)

Terminates command processing.

(O)

Check the OS resources.

KAVA5319-E

An invalid argument was passed to the function function-name.

An invalid argument was passed to the function.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5322-E

The authentication server authentication-server-name is either not running or is not responding.

The authentication server is not running or is not responding.

(S)

Terminates command processing because the authentication server is not responding.

(O)

Make sure that:

The JP1/Base service is running.

The specified authentication server exists.

The network connection is correct.

Both the host on which the command was executed and the authentication server use the same IP address version (IPv4 or IPv6).

For details about how to check the IP address version (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the Job Management Partner 1/Base User's Guide.

KAVA5324-E

The logical host logical-host-name does not exist.

The specified logical host does not exist.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified on the command line is correct, and that the value in the JP1_HOSTNAME environment variable is correct.

KAVA5326-E

Common definition information does not exist for the authentication server.

The SVNAME label does not exist in the common definition information.

(S)

Terminates command processing.

(O)

Check whether the SVNAME label exists in the common definition information for the logical host.

KAVA5327-W

The buffer went out of range during execution of the JP1/Base common definition API function jp1BsCnfGetStringValue().

A memory shortage occurred during execution of the API function jp1BsCnfGetStringValue().

KAVA5328-E

The user lacks permission to reference the common definition information.

There is no permission to read the common definition information.

(S)

If the error occurred during acquisition of the SVNAME value from the common definition information, the system terminates command processing. If an attempt to acquire any other value from the common definition information failed, the system uses the default to continue processing.

(O)

The common definition information may contain incorrect settings. Check the settings.

KAVA5331-E

An attempt to send data to the authentication server has failed.

The command failed to send data to the authentication server.

(S)

Terminates command processing.

(O)

Make sure that the network connection is correct.

KAVA5332-W

Due to a timeout, {connect|send|receive} has failed.

The authentication server could not be connected.

Data could not be sent to or received from the authentication server because the connection line did not respond properly in time.

Connection could not be established because of a timeout.

KAVA5333-E

An attempt to receive data from the authentication server has failed.

Data could not be received from the authentication server. Alternatively, the authentication server does not support the function.

(S)

Terminates command processing.

(O)

Make sure that the network connection is correct and the version of the authentication server is correct.

KAVA5334-W

An attempt to create a socket has failed.

A socket could not be created. The command retries to create a socket for communication.

KAVA5341-E

An error occurred during initialization of the base communication functionality.

The API function jp1BsCommInit() failed during initialization of the base communication functionality for the specified logical host.

(S)

Terminates command processing.

(O)

Check whether the JP1_HOSTNAME label exists in the common definition information for the logical host.

KAVA5342-W

A temporary error occurred while data was being sent to the authentication server. The system will try again.

A temporary sending error occurred. The command will retry sending data to the authentication server.

KAVA5343-W

A temporary error occurred while data was being received from the authentication server. The system will try again.

A temporary reception error occurred. The command will retry receiving data from the authentication server.

KAVA5344-E

An attempt to bind the socket has failed.

The socket cannot be bound.

(S)

Terminates command processing.

(O)

Make sure that the logical-host entry matches the IP address of the local machine.

KAVA5345-E

An attempt to change the socket to non-blocking mode has failed.

The command failed to change the socket to the non-blocking mode.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5346-E

An attempt to change the socket to blocking mode has failed.

The command failed to change the socket to the blocking mode.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5351-E

An attempt to execute a common definition API function (jp1BsCnfGetStringValue() or jp1BsCnfGetULongValue()) has failed. (error number = error-number)

A value could not be read from the common definition information.

(S)

If the error occurred during acquisition of the SVNAME value from the common definition information, the system terminates command processing. If an attempt to acquire any other value from the common definition information failed, the system uses the default to continue processing.

(O)

The common definition information may contain incorrect settings. Check the settings.

KAVA5355-E

The authentication server authentication-server-name was unable to be recognized.

The specified authentication server could not be recognized.

(S)

Terminates command processing.

(O)

Make sure that the specified authentication server exists.

KAVA5357-E

An attempt to get the label value of JP1_HOSTNAME from the common definition information has failed.

The host-name value could not be obtained from the common definition information.

(S)

Terminates command processing.

(O)

Check whether the JP1_HOSTNAME label exists in the common definition information.

KAVA5358-E

The specified address family cannot be used in TCP networks.

The address family of the specified authentication server is not supported in TCP networks.

(S)

Terminates command processing.

(O)

Check the OS environment.

KAVA5362-E

Root privileges are required to execute the command.

Executing the jbslistuser command requires root privileges.

(S)

Terminates command processing.

(O)

Only a user who has root privileges can execute the jbslistuser command. Execute the command as a user who has root privileges.

KAVA5363-W

The label entry does not exist in the common definition information.

The label does not exist in the common definition information.

KAVA5364-W

The value of JP1_BIND_ADDR in the common definition information is invalid. Startup will use ANY.

The value of the JP1_BIND_ADDR label in the common definition information is not ANY or IP.

KAVA5365-E

The command line has a syntax error.

The command line has a syntax error.

(S)

Terminates command processing.

(O)

Make sure that proper arguments are specified on the command line.

KAVA5369-E

The authentication server authentication-server-name could not be reached.

The authentication server cannot be reached.

(S)

Terminates command processing.

(O)

Check the network.

KAVA5370-E

The length of the logical hostname exceeds 255 characters.

The specified logical host name exceeds 255 characters.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified in the -h option on the command line, or the value of the JP1_HOSTNAME environment variable, does not exceed 255 characters.

KAVA5371-E

The length of the authentication server name exceeds 255 characters.

The specified authentication server name exceeds 255 characters.

(S)

Terminates command processing.

(O)

Make sure that the specified authentication server name does not exceed 255 characters.

KAVA5372-E

An error occurred during execution of the API function jp1BsCommInit(). (error number = error-number)

The API function jp1BsCommInit() failed.

(S)

Terminates command processing.

(O)

Check whether the JP1_HOSTNAME label exists under the JP1/Config/logical-host/JP1BASE key in the common definition information.

KAVA5373-E

An attempt to open the catalog file has failed. (error number = error-number)

The jp1BsSessAclCmdMsg.cat catalog file could not be opened.

(S)

Terminates command processing because the catalog file cannot be loaded.

(O)

Make sure that the catalog file exists.

KAVA5374-E

The catalog file path exceeded the maximum limit while the catalog file was being opened.

A memory shortage occurred while the jp1BsSessAclCmdMsg.cat catalog file was being opened.

(S)

Terminates command processing because there is insufficient memory.

(O)

Re-execute the command.

Make sure that the catalog file does not exceed the maximum length.

KAVA5375-E

An attempt to open the catalog file has failed.

The jp1BsSessAclCmdMsg.cat message catalog file cannot be opened.

(S)

Terminates command processing.

(O)

Check this file for read permission.

KAVA5376-W

An attempt to acquire the label value from the common definition information has failed.

The specified label value could not be read from the common definition information.

KAVA5377-W

The path exceeded the maximum length while the log file was being opened.

The path to the individual log file (JP1BASE_LOGDIR label value) exceeded the maximum length.

KAVA5378-W

An error occurred during initialization of the HNTR Library. (error number = error-number)

The HNTR library could not be initialized.

KAVA5379-W

Due to an error in the API function FormatMessage(), an attempt to acquire the message has failed. (error number = error-number)

An attempt to acquire the message using the API function FormatMessage() failed.

KAVA5380-E

An internal error occurred in the JP1/BASE common definition library.

An internal error occurred in the common definition library.

(S)

If the error occurred during acquisition of the SVNAME value from the common definition information, the system terminates command processing. If an attempt to acquire any other value from the common definition information failed, the system uses the default to continue processing.

(O)

The common definition information may contain incorrect settings. Check the settings.

KAVA5381-W

An error occurred during execution of the API function API-name. (error number = error-number)

A temporary error occurred during execution of the API function.

KAVA5382-W

The system will attempt to connect to the authentication server authentication-server-name again.

A temporary connection error occurred. Connection to the authentication server will be reattempted.

KAVA5383-E

An attempt to create a socket has failed.

A socket could not be created.

(S)

Terminates command processing.

(O)

Check the OS resources.

KAVA5385-E

An attempt to retrieve host information for the specified logical host logical-host-name has failed.

The host information for the specified logical host is invalid.

(S)

Terminates command processing.

(O)

Make sure that the /etc/hosts file contains valid settings for the specified logical host.

KAVA5392-W

An attempt to acquire the common definition information for logical host logical-host-name has failed. Further logging will not be done.

This message reports that the log data will not be output to the specified logical host because an attempt to obtain the common definition information for the logical host has failed.

KAVA5394-E

The logical-host-name/JP1BASE/LOG_CONTROL/JBSSESS key was not found.

The JBSSESS key was not found on the specified logical host.

(S)

Terminates command processing.

(O)

Check whether the JBSSESS key exists in the common definition information for the specified logical host.

KAVA5395-E

The JP1_DEFAULT/JP1BASE/LOG_CONTROL/JBSSESS key was not found.

The JBSSESS key was not found on the physical host.

(S)

Terminates command processing.

(O)

Check whether the JBSSESS key exists in the common definition information for the physical host.

KAVA5396-E

Due to an error in the API function jp1BsCommInit(), an attempt to initialize the base communication functionality for the physical host has failed. (error number = error-number)

An error occurred during initialization of the base communication functionality for the physical host (JP1_DEFAULT).

(S)

Terminates command processing.

(O)

Wait a while, and then re-execute the command.

KAVA5401-I

Permission definitions were successfully reloaded.

The processing for reloading the definitions of operating permissions to the authentication server ended normally.

KAVA5402-E

An attempt to reload permission definitions has failed.

An attempt to reload the definitions of operating permissions to the authentication server has failed.

(S)

Terminates command processing.

(O)

See the log file to determine the cause of the error.

KAVA5403-I

The command has started.

The jbsaclreload command has started.

KAVA5404-E

The logical host name or authentication server is not specified.

The logical host name or authentication server name is not specified in the -h or -s option.

(S)

Terminates command processing.

(O)

Check that the logical host name is specified in the -h option and that the authentication server name is specified in the -s option.

KAVA5417-E

Memory is insufficient.

There is not enough system memory to execute the command.

(S)

Terminates command processing.

(O)

Re-execute the command.

Check for insufficient memory.

KAVA5418-E

An error occurred during execution of the jbsaclreload command.

An error occurred during execution of the jbsaclreload command.

(S)

Terminates command processing.

(O)

Check the OS resources.

KAVA5419-E

An invalid argument was passed to the function function-name.

An invalid argument was passed to the function.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5422-E

The authentication server authentication-server-name is either not running or not responding.

The authentication server is not running is not responding.

(S)

Terminates command processing because the authentication server is not responding.

(O)

Make sure that:

The JP1/Base service is running.

The specified authentication server exists.

The network connection is correct.

Both the host on which the command was executed and the authentication server use the same IP address version (IPv4 or IPv6).

For details about how to check the IP address version (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the Job Management Partner 1/Base User's Guide.

KAVA5424-E

The logical host logical-host-name does not exist.

The specified logical host does not exist.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified on the command line is correct, and that the value in the JP1_HOSTNAME environment variable is correct.

KAVA5426-E

Common definition information does not exist for the authentication server.

The SVNAME label does not exist in the common definition information.

(S)

Terminates command processing.

(O)

Check whether the SVNAME label exists in the common definition information for the logical host.

KAVA5427-W

The buffer went out of range during execution of the JP1/Base common definition API function jp1BsCnfGetStringValue().

A memory shortage occurred during execution of the API function jp1BsCnfGetStringValue().

KAVA5428-E

The user lacks permission to reference the common definition information.

There is no permission to read the common definition information.

(S)

If the error occurred during acquisition of the SVNAME value from the common definition information, the system terminates command processing. If an attempt to acquire any other value from the common definition information failed, the system uses the default to continue processing.

(O)

The common definition information may contain incorrect settings. Check the settings.

KAVA5431-E

An attempt to send data to the authentication server has failed.

The command failed to send data to the authentication server.

(S)

Terminates command processing.

(O)

Make sure that the network connection is correct.

KAVA5432-W

Due to a timeout, {connect|send|receive} has failed.

The authentication server could not be connected.

Data could not be sent to or received from the authentication server because the connection line did not respond properly in time.

Connection could not be established because of a timeout.

KAVA5433-E

An attempt to receive data from the authentication server has failed.

Data could not be received from the authentication server.

(S)

Terminates command processing.

(O)

Make sure that the network connection is correct.

KAVA5434-W

An attempt to create a socket has failed.

A socket could not be created. The command retries creating a socket for communication.

KAVA5441-E

An error occurred during initialization of the base communication functionality.

The API function jp1BsCommInit() failed during initialization of the base communication functionality for the specified logical host.

(S)

Terminates command processing.

(O)

Check whether the JP1_HOSTNAME label exists in the common definition information for the logical host.

KAVA5442-W

A temporary error occurred while data was being sent to the authentication server. The system will try again.

A temporary sending error occurred. The command will retry sending data to the authentication server.

KAVA5443-W

A temporary error occurred while data was being received from the authentication server. The system will try again.

A temporary reception error occurred. The command will retry receiving data from the authentication server.

KAVA5444-E

An attempt to bind the socket has failed.

The socket cannot be bound.

(S)

Terminates command processing.

(O)

Make sure that the logical-host entry matches the IP address of the local machine.

KAVA5445-E

An attempt to change the socket to non-blocking mode has failed.

The command failed to change the socket to the non-blocking mode.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5446-E

An attempt to change the socket to blocking mode has failed.

The command failed to change the socket to the blocking mode.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5449-E

An error occurred on the authentication server authentication-server-name.

An error occurred on the authentication server.

(S)

Terminates command processing.

(O)

Check the log on the authentication server.

KAVA5451-E

An attempt to execute the common definition API function (jp1BsCnfGetStringValue() or jp1BsCnfGetULongValue()) has failed. (error number = error-number)

A value could not be read from the common definition information.

(S)

If the error occurred during acquisition of the SVNAME value from the common definition information, the system terminates command processing. If an attempt to acquire any other value from the common definition information failed, the system uses the default to continue processing.

(O)

The common definition information may contain incorrect settings. Check the settings.

KAVA5455-E

The authentication server authentication-server-name was unable to be recognized.

The specified authentication server could not be recognized.

(S)

Terminates command processing.

(O)

Make sure that the specified authentication server exists.

KAVA5457-E

An attempt to get the label value of JP1_HOSTNAME from the common definition information has failed.

The host-name value could not be obtained from the common definition information.

(S)

Terminates command processing.

(O)

Check whether the JP1_HOSTNAME label exists in the common definition information.

KAVA5458-E

The specified address family cannot be used in TCP networks.

The address family of the specified authentication server is not supported in TCP networks.

(S)

Terminates command processing.

(O)

Check the OS environment.

KAVA5462-E

Root privileges are required to execute the command.

Executing the jbsaclreload command requires root privileges.

(S)

Terminates command processing.

(O)

Only a user who has root privileges can execute the jbsaclreload command. Execute the command as a user who has root privileges.

KAVA5463-W

The label entry does not exist in the common definition information.

The label does not exist in the common definition information.

KAVA5464-W

The value of JP1_BIND_ADDR in the common definition information is invalid. Startup will use ANY.

The value of the JP1_BIND_ADDR label in the common definition information is not ANY or IP.

KAVA5465-E

The command line has a syntax error.

The command line has a syntax error.

(S)

Terminates command processing.

(O)

Make sure that proper arguments are specified on the command line.

KAVA5469-E

The authentication server authentication-server-name could not be reached.

The authentication server cannot be reached.

(S)

Terminates command processing.

(O)

Check the network.

KAVA5470-E

The length of the logical hostname exceeds 255 characters.

The specified logical host name exceeds 255 characters.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified in the -h option on the command line, or the value of the JP1_HOSTNAME environment variable, does not exceed 255 characters.

KAVA5471-E

The length of the authentication server name exceeds 255 characters.

The specified authentication server name exceeds 255 characters.

(S)

Terminates command processing.

(O)

Make sure that the specified authentication server name does not exceed 255 characters.

KAVA5472-E

An error occurred during execution of the API function jp1BsCommInit(). (error number = error-number)

The API function jp1BsCommInit() failed.

(S)

Terminates command processing.

(O)

Check whether the JP1_HOSTNAME label exists under the JP1/Config/logical-host/JP1BASE key in the common definition information.

KAVA5473-E

An attempt to open the catalog file has failed. (error number = error-number)

The jp1BsSessAclCmdMsg.cat catalog file could not be opened.

(S)

Terminates command processing because the catalog file cannot be loaded.

(O)

Make sure that the catalog file exists.

KAVA5474-E

The catalog file path exceeded the maximum limit while the catalog file was being opened.

A memory shortage occurred while the jp1BsSessAclCmdMsg.cat catalog file was being opened.

(S)

Terminates command processing because there is insufficient memory.

(O)

Re-execute the command.

Make sure that the catalog file does not exceed the maximum length.

KAVA5475-E

An attempt to open the catalog file has failed.

The jp1BsSessAclCmdMsg.cat message catalog file cannot be opened.

(S)

Terminates command processing.

(O)

Check this file for read permission.

KAVA5476-W

An attempt to acquire the label value from the common definition information has failed.

The specified label value could not be read from the common definition information.

KAVA5477-W

The path exceeded the maximum length while the log file was being opened.

The path to the individual log file (JP1BASE_LOGDIR label value) exceeded the maximum length.

KAVA5478-W

An error occurred during initialization of the HNTR Library. (error number = error-number)

The HNTR library could not be initialized.

KAVA5479-W

Due to an error in the API function FormatMessage(), an attempt to acquire the message has failed. (error number = error-number)

An attempt to acquire the message using the API function FormatMessage() failed.

KAVA5480-E

An internal error occurred in the JP1/BASE common definition library.

An internal error occurred in the common definition library.

(S)

If the error occurred during acquisition of the SVNAME value from the common definition information, the system terminates command processing. If an attempt to acquire any other value from the common definition information failed, the system uses the default to continue processing.

(O)

The common definition information may contain incorrect settings. Check the settings.

KAVA5481-W

An error occurred during execution of the API function API-name. (error number = error-number)

A temporary error occurred during execution of an API function.

KAVA5482-W

The system will attempt to connect to the authentication server authentication-server-name again.

A temporary connection error occurred. Connection to the authentication server will be reattempted.

KAVA5483-E

An attempt to create a socket has failed.

A socket could not be created.

(S)

Terminates command processing.

(O)

Check the OS resources.

KAVA5485-E

An attempt to retrieve host information for the specified logical host logical-host-name has failed.

The host information for the specified logical host is invalid.

(S)

Terminates command processing.

(O)

Make sure that the /etc/hosts file contains valid settings for the specified logical host.

KAVA5492-W

An attempt to acquire the common definition information for logical host logical-host-name has failed. Further logging will not be done.

This message reports that log data will not be output to the specified logical host because an attempt to obtain the common definition information for the logical host has failed.

KAVA5494-E

The logical-host-name/JP1BASE/LOG_CONTROL/JBSSESS key was not found.

The JBSSESS key was not found on the specified logical host.

(S)

Terminates command processing.

(O)

Check whether the JBSSESS key exists in the common definition information for the specified logical host.

KAVA5495-E

The JP1_DEFAULT/JP1BASE/LOG_CONTROL/JBSSESS key was not found.

The JBSSESS key was not found on the physical host.

(S)

Terminates command processing.

(O)

Check whether the JBSSESS key exists in the common definition information for the physical host.

KAVA5496-E

Due to an error in the API function jp1BsCommInit(), an attempt to initialize the base communication functionality for the physical host has failed. (error number = error-number)

An error occurred during initialization of the base communication functionality for the physical host (JP1_DEFAULT).

(S)

Terminates command processing.

(O)

Wait a while, and then re-execute the command.

KAVA5501-I

The permission definitions were successfully listed.

The processing for listing the definitions of operating permissions for the authentication server ended normally.

KAVA5502-E

An attempt to list permission definitions has failed.

An attempt to list the definitions of operating permissions for the authentication server has failed.

(S)

Terminates command processing.

(O)

See the log file to determine the cause of the error.

KAVA5503-I

The command has started.

The jbsacllint command has started.

KAVA5505-E

The logical host name is not specified.

The logical host name is not specified in the -h option.

(S)

Terminates command processing.

(O)

Make sure that the logical host name is specified in the -h option.

KAVA5517-E

Memory is insufficient.

There is not enough system memory to execute the command.

(S)

Terminates command processing.

(O)

Re-execute the command.

Check for insufficient memory.

KAVA5518-E

An error occurred during execution of the jbsacllint command.

An error occurred during execution of the jbsacllint command.

(S)

Terminates command processing.

(O)

Check the OS resources.

KAVA5519-E

An invalid argument was passed to the function function-name.

An invalid argument was passed to the function.

(S)

Terminates command processing.

(O)

Re-execute the command.

KAVA5521-E

The API function API-name has terminated abnormally. (error number = error-number)

A call to the standard OS API or the common definition API of JP1/Base terminated abnormally.

(S)

Terminates command processing.

(O)

This message is output with one of the following message IDs. Check that message.

KAVA5*22, KAVA5*31, KAVA5*33, KAVA5*43, KAVA5*44, KAVA5*45, KAVA5*46, KAVA5*55, KAVA5*57, KAVA5*69, KAVA5*83, KAVA5*85, KAVA5598

KAVA5524-E

The logical host logical-host-name does not exist.

The specified logical host does not exist.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified on the command line is correct, and that the value in the JP1_HOSTNAME environment variable is correct.

KAVA5528-E

The user lacks permission to reference the common definition information.

There is no permission to read the common definition information.

(S)

Terminates command processing.

(O)

The common definition information may contain incorrect settings. Check the settings.

KAVA5539-E

An error occurred while the file file-name was being opened.

An error occurred while the file was being opened.

(S)

Terminates command processing.

(O)

Make sure that the JP1_AccessLevel and JP1_UserLevel files exist in the conf/user_acl directory.

KAVA5540-E

An error occurred while the file file-name was being read.

An error occurred while the file file-name was being read.

(S)

Cannot read the file, and terminates command processing.

(O)

Make sure that:

The file exists.

You have appropriate permissions for the file.

KAVA5541-E

An attempt to initialize the base communication functionality has failed.

The API function jp1BsCommInit() failed during initialization of the base communication functionality for the specified logical host.

(S)

Terminates command processing.

(O)

Check whether the JP1_HOSTNAME label exists in the common definition information for the logical host.

KAVA5562-E

Root privileges are required to execute the command.

Executing the jbsacllint command requires root privileges.

(S)

Terminates command processing.

(O)

Only a user who has root privileges can execute the jbsacllint command. Execute the command as a user who has root privileges.

KAVA5565-E

The command line has a syntax error.

The command line has a syntax error.

(S)

Terminates command processing.

(O)

Make sure that proper arguments are specified on the command line.

KAVA5566-W

An error occurred while the file full-path-file-name was being closed.

An error occurred while the file was being closed.

KAVA5567-E

An attempt to acquire the directory path where the configuration file exists from the common definition information has failed.

The directory path to the definition file could not be acquired from the common definition information.

(S)

Terminates command processing.

(O)

Check whether the common folder or label is specified in the common definition information.

KAVA5570-E

The length of the logical hostname exceeds 255 characters.

The specified logical host name exceeds 255 characters.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified in the -h option on the command line, or the value of the JP1_HOSTNAME environment variable, does not exceed 255 characters.

KAVA5572-E

An error occurred during execution of the API function jp1BsCommInit(). (error number = error-number)

The API function jp1BsCommInit() failed.

(S)

Terminates command processing.

(O)

Check whether the JP1_HOSTNAME label exists under the JP1/Config/logical-host/JP1BASE key in the common definition information.

KAVA5573-E

An attempt to open the catalog file has failed. (error number = error-number)

The jp1BsSessAclCmdMsg.cat catalog file could not be opened.

(S)

Terminates command processing because the catalog file cannot be loaded.

(O)

Make sure that the catalog file exists.

KAVA5574-E

The catalog file path exceeded the maximum limit while the catalog file was being opened.

A memory shortage occurred while the jp1BsSessAclCmdMsg.cat catalog file was being opened.

(S)

Terminates command processing because there is insufficient memory.

(O)

Re-execute the command.

Make sure that the catalog file does not exceed the maximum length.

KAVA5575-E

An attempt to open the catalog file has failed.

The jp1BsSessAclCmdMsg.cat message catalog file cannot be opened.

(S)

Terminates command processing.

(O)

Check this file for read permission.

KAVA5576-W

An attempt to acquire the label value from the common definition information has failed.

The specified label value could not be read from the common definition information.

KAVA5577-W

The path exceeded the maximum length while the log file was being opened.

The path to the individual log file (JP1BASE_LOGDIR label value) exceeded the maximum length.

KAVA5578-W

An error occurred during initialization of the HNTR Library. (error number = error-number)

The HNTR library could not be initialized.

KAVA5579-W

Due to an error in the API function FormatMessage(), an attempt to acquire the message has failed. (error number = error-number)

An attempt to acquire the message using the API function FormatMessage() failed.

KAVA5580-E

An internal error occurred in the JP1/Base common definition library.

An internal error occurred in the common definition library.

(S)

Terminates command processing.

(O)

The common definition information may contain incorrect settings. Check the settings.

KAVA5590-E

The JP1BASE_CONFDIR entry does not exist in the common definition information.

The JP1BASE_CONFDIR label does not exist in the common definition information.

(S)

Terminates command processing.

(O)

Check whether the JP1BASE_CONFDIR label exists in the common definition information.

KAVA5592-W

An attempt to acquire the common definition information for logical host logical-host-name has failed. Further logging will not be done.

This message reports that the log data will not be output to the specified logical host because the attempt to obtain the common definition information for the logical host has failed.

KAVA5594-E

The logical-host-name/JP1BASE/LOG_CONTROL/JBSSESS key was not found.

The JBSSESS key was not found on the specified logical host.

(S)

Terminates command processing.

(O)

Check whether the JBSSESS key exists in the common definition information for the specified logical host.

KAVA5595-E

The JP1_DEFAULT/JP1BASE/LOG_CONTROL/JBSSESS key was not found.

The JBSSESS key was not found on the physical host.

(S)

Terminates command processing.

(O)

Check whether the JBSSESS key exists in the common definition information for the physical host.

KAVA5596-E

Due to an error in the API function jp1BsCommInit(), an attempt to initialize the base communication functionality for the physical host has failed. (error number = error-number)

An error occurred during initialization of the base communication functionality for the physical host (JP1_DEFAULT).

(S)

Terminates command processing.

(O)

Wait a while, and then re-execute the command.

KAVA5597-E

The buffer went out of range while the JP1BASE_CONFDIR value was being obtained from the common definition information.

A memory shortage occurred while the JP1BASE_CONFDIR value was being obtained from the common definition information.

(S)

Terminates command processing.

(O)

Make sure that the JP1BASE_CONFDIR value does not exceed the buffer length.

KAVA5598-E

An error occurred while the JP1BASE_CONFDIR value was being obtained from the common definition information.

The JP1BASE_CONFDIR value could not be read from the common definition information.

(S)

Terminates command processing.

(O)

Check the common definition information.

KAVA5700-E

Execute the command from the administrator console.

This command must be executed on the administrator console.

(S)

Terminates command processing.

(O)

Re-execute the command on the administrator console.

KAVA5702-E

An attempt to modify a directory server settings has failed.

An attempt to set up the directory server has failed.

(S)

Terminates command processing.

(O)

See the log file to determine the cause of the error.

KAVA5703-I

The command has started.

The jbschgds command has started.

KAVA5705-E

The logical host name is not specified.

The logical host name is not specified for the -h option of the jbschgds command.

(S)

Terminates command processing.

(O)

Specify the logical host name for the -h option, and then re-execute the jbschgds command.

KAVA5706-I

The directory server settings will be modified temporarily.

The directory server settings will be modified temporarily.

KAVA5707-I

The temporary modification of a directory server settings has been released.

The temporary modification of the directory server settings has been released..

KAVA5708-E

A directory server definition file is not specified.

A directory server definition file is not specified for the -f option of the jbschgds command.

(S)

Terminates command processing.

(O)

Specify a directory server definition file for the -f option, and then re-execute the jbschgds command.

KAVA5709-E

Processing cannot continue because there is an error in the directory server definition file.

Processing cannot continue because there is an error in the directory server definition file.

(S)

Terminates command processing.

(O)

A syntax error was found in the specified directory server definition file. Check the contents of the file.

KAVA5710-E

The directory server definition file cannot be opened.

The directory server definition file cannot be opened.

(S)

Terminates command processing.

(O)

Check the following items regarding the -f option of the jbschgds command, and then re-execute the command.

Make sure that the specified file name is correct.

Make sure that you have not specified a directory (folder) instead of a file.

KAVA5718-E

An error occurred during execution of the jbschgds command.

An error occurred during execution of the jbschgds command.

(S)

Terminates command processing.

(O)

Check the OS resources.

KAVA5724-E

The logical host logical-host-name does not exist.

The specified logical host does not exist.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified on the command line is correct, and that the value in the JP1_HOSTNAME environment variable is correct.

KAVA5762-E

Administrator authorization is required.

Execute the jbschgds command as a user who has Administrators permissions.

(S)

Terminates command processing.

(O)

Only a user who has Administrators permissions can execute the jbschgds command.

Execute the command as a user who has Administrators permissions.

KAVA5765-E

The command line has a syntax error.

The command line has a syntax error.

(S)

Terminates command processing.

(O)

Make sure that proper arguments are specified on the command line.

KAVA5770-E

The length of the logical hostname exceeds 255 characters.

The length of the specified logical host name exceeds 255 characters.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified in the -h option on the command line or the value of the JP1_HOSTNAME environment variable does not exceed 255 characters.

KAVA5778-W

An error occurred during initialization of the HNTR Library. (error number = error-number)

An attempt to initialize the HNTR library failed.

KAVA5802-E

An attempt to check the directory server has failed.

An attempt to check the connection to the directory server has failed.

(S)

Terminates command processing.

(O)

See the log file to determine the cause of the error.

KAVA5803-I

The command has started.

The jbschkds command has started.

KAVA5805-E

The logical host name is not specified.

The logical host name is not specified in the -h option of the jbschkds command.

(S)

Terminates command processing.

(O)

Specify the logical host name in the -h option of the jbschkds command, and then re-execute the command.

KAVA5806-E

The user name is not specified.

The name of the user to be authenticated by the directory server is not specified.

(S)

Terminates command processing.

(O)

Specify the user name in the -u option of the jbschkds command, and then re-execute the command.

KAVA5807-E

The length of the user name exceeds 31 characters.

The length of the JP1 user name exceeds 31 characters.

(S)

Terminates command processing.

(O)

Specify a JP1 user name in an argument on the command line, using no more than 31 characters.

KAVA5808-I

The directory server is now connected.

The directory server can now be connected.

KAVA5809-I

User authentication succeeded.

The user was authenticated successfully.

KAVA5810-E

A connection to the directory server could not be established.

The directory server could not be connected.

(S)

Terminates command processing.

(O)

Check the following:

Make sure that the directory server name and port number specified in the common definition are correct.

Make sure that the directory server is running.

If SSL is enabled, make sure that the environment is such that SSL can be used.

Make sure that the directory server connection settings are correct.

Make sure that the firewall settings are correct.

In the following cases, check the status of the directory server:

If the connection with the directory server timed out.

If the directory server is in a busy state.

KAVA5811-E

User authentication failed.

An attempt to authenticate a user failed.

(S)

Terminates command processing.

(O)

Make sure that:

The specified user name and password are correct.

The identification name specified in the common definition or the attribute name used as the authentiation ID is correct.

The status of the user account on the directory server is correct.

Make sure that the account is valid.

Make sure that the account has not expired.

Make sure that the account is not locked out.

Make sure that the password has not expired.

Make sure that the User must change password at next login setting is not specified for the user.

KAVA5812-I

The directory server linkage functionality is disabled.

The directory server linkage functionality is disabled.

KAVA5813-E

An attempt to acquire the common definition information failed. (lavel = label-name, code= error-number)

An attempt to acquire the common definition information failed.

(S)

Terminates command processing.

(O)

The common definition information may contain incorrect settings. Make sure that the settings for linking to the directory server are correct.

KAVA5814-E

The password length is invalid. Specify 6 to 32 characters.

The password length is invalid.

(S)

Terminates command processing.

(O)

Make sure that the password specified on the command line is correct.

KAVA5815-E

The label-name value is invalid.

The value specified for linking to the directory server is invalid.

(S)

Terminates command processing.

(O)

Specify a correct value, and then re-execute the command.

KAVA5816-E

An invalid character is specified in the user name.

The JP1 user name cannot contain spaces, tabs, control characters or the following characters: *"'^[]{}():;|\/=,+?<>

(S)

Terminates command processing.

(O)

Specify a user name with valid characters, and then re-execute the command.

KAVA5818-E

An error occurred during execution of the jbschkds command.

An error occurred during execution of the jbschkds command.

(S)

Terminates command processing.

(O)

Check the OS resources.

KAVA5822-I

The information-search user was successfully authenticated.

The information-search user was successfully authenticated.

KAVA5823-E

Authentication of the information-search user failed. (dn = identification-name, func = function-name, code = LDAP-error-number)

An attempt to authenticate the information-search user failed.

(S)

Terminates command processing.

(O)

Make sure that:

The password of the information-search user registered in the password management system is correct.

The status of the user account on the directory server is correct.

- Make sure that the account is valid.

- Make sure that the account has not expired.

- Make sure that the account is not locked out.

- Make sure that the password has not expired.

- Make sure that the password contains at least one character.

- Make sure that the User must change password at next login setting is not specified for the user.

KAVA5824-E

The logical host logical-host-name does not exist.

An error occurred during execution of the jbschkds command.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified on the command line is correct, and that the value in the JP1_HOSTNAME environment variable is correct.

KAVA5862-E

Administrator authorization is required.

To execute the jbschkds command, you must be logged on as a user who has Administrators permissions.

(S)

Terminates command processing.

(O)

Only a user who logged on as a user who has Administrators permissions can execute the jbschkds command.

Execute the command as a user who has Administrators permissions.

KAVA5865-E

The command line has a syntax error.

The command line has a syntax error.

(S)

Terminates command processing.

(O)

Make sure that proper arguments are specified on the command line.

KAVA5870-E

The length of the logical hostname exceeds 255 characters.

The specified logical host name exceeds 255 characters.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified in the -h option on the command line or the value of the JP1_HOSTNAME environment variable does not exceed 255 characters.

KAVA5878-W

An error occurred during initialization of the HNTR Library. (error number = error-number)

An attempt to initialize the HNTR library failed.

KAVA5889-E

An invalid character is specified in the password.

An invalid character is specified in the password.

(S)

Terminates command processing.

(O)

Enter the correct password.

KAVA5899-E

The password is not specified.

No password is specified.

(S)

Terminates command processing.

(O)

Make sure that the password is specified in an argument on the command line.

KAVA5901-E

The user name (user-name) does not exist or a linked user is specified.

The specified JP1 user name is not registered in the authentication server. Alternatively, the specified user is a linked user.

(S)

Terminates command processing.

(O)

Make sure that the specified JP1 user name is registered in the authentication server. Alternatively, make sure that the specified user is not a linked user. You cannot change the password for a linked user.

KAVA5902-E

Root privileges or JP1/Base administrator privileges are required to execute the command.

(S)

Terminates command processing.

(O)

Re-execute the command as a user who has root privileges or JP1/Base administrator privileges.

2.7 Plug-in service messages (KAVA6002 to KAVA6855)

KAVA6002-E

An attempt to obtain a communication handle for the process management failed.

An attempt to obtain a communication handle for the process management daemon failed.

(S)

Stops the plug-in service.

(O)

Make sure that the process management is running correctly.

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

KAVA6003-W

The [CONNECT] request timed out.

A CONNECT request was not sent within 60 seconds after a TCP connection was established.

(S)

Disconnects the TCP connection.

(O)

Wait a while, and then re-execute the command.

KAVA6005-E

An attempt to start a child process failed.

A child process to manipulate the plug-in service could not start.

(S)

Terminates the start of communication manipulation process.

(O)

Check the status of the OS resources and available memory. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KAVA6007-I

The response was [BUSY].

A busy signal was returned because the number of child processes reached the upper limit.

KAVA6008-E

An attempt to return a [BUSY] response failed.

A busy signal indicating that the number of child processes reached the upper limit could not be returned.

(S)

Cancels responding.

(O)

The network may have failed. Check the local host resources and the status of the network with the higher-level host.

KAVA6017-E

An attempt to generate a socket for connection failed.

A socket for connection could not be generated.

(S)

Stops the main process.

(O)

Check the OS resources and available memory, and then restart JP1/Base.

KAVA6030-I

The plugin service will now end.

The plug-in service ends.

KAVA6037-E

An invalid request was received from the process management. (process management request code = value)

The plug-in service ends because the process management issued an invalid request.

(S)

Stops the main process.

(O)

Check the OS resources and available memory, and then restart JP1/Base.

KAVA6038-I

A reload request was received from the process management.

The settings for the plug-in service are updated in response to a reloading request from the process management.

KAVA6039-I

A stop request was received from the process management.

The plug-in service ends according to a stop request from the process management.

KAVA6040-E

An attempt to send the start notification to the process management failed.

The plug-in service ends because a start notification could not be sent to the process management.

(S)

Stops the main process.

(O)

Check the OS resources and available memory, and then restart JP1/Base.

KAVA6041-E

An attempt to send the reload notification to the process management failed.

The plug-in service ends because reloading could not be reported to the process management.

(S)

Stops the main process.

(O)

Check the OS resources and available memory, and then restart JP1/Base.

KAVA6042-W

An attempt to send the termination notification to the process management failed.

A termination notification could not be sent to the process management. Processing continues.

(S)

Continues processing.

(O)

Check the OS resources and available memory, and then restart JP1/Base.

KAVA6043-I

The reloading ended normally.

The reload command ended normally.

KAVA6044-E

The reloading ended abnormally.

The reload command ended abnormally.

(S)

Stops the main process.

(O)

Check the OS resources and available memory, and then re-execute the reload command.

KAVA6045-I

The settings for the plug-in service will be updated.

Reloading is performed.

KAVA6046-E

A request from a host without access permissions was rejected. (host-name-or-IP-address-of-the-requesting-host)

A request from a host without the required access permissions was received.

If reverse mapping is possible by converting the IP address of the requesting host to the host name, the host name is indicated in host-name-or-IP-address-of-the-requesting-host. If reverse mapping is not possible, the IP address of the host is indicated.

(S)

Cancels processing.

(O)

Specify the host name or IP address of the requesting host for CLIENT_HOSTS in the common definition information.

KAVA6047-W

An invalid host name is specified. (host = host-name)

An invalid host name was specified for CLIENT_HOSTS in the common definition information.

(S)

During startup: Continues processing, assuming that CLIENT_HOSTS is not specified in the common definition.

During reloading: Continues processing with the definitions used before the reloading.

(O)

Make sure that:

The specified host name contains not more than 255 bytes.

An IP address is assigned to the host name in the settings for the hosts information, DNS, or jp1hosts2.

KAVA6048-W

The specified host (host-name) already exists.

The host name specified for CLIENT_HOSTS in the common definition is already in use.

(S)

During startup: Continues processing, assuming that CLIENT_HOSTS is not specified in the common definition.

During reloading: Continues processing with the definitions used before the reloading.

(O)

Revise the specification of CLIENT_HOSTS in the common definition.

KAVA6049-W

The number of specified hosts exceeds the maximum number allowed. (maximum).

The number of hosts specified for CLIENT_HOSTS in the common definition exceeds the maximum.

(S)

During startup: Continues processing, assuming that CLIENT_HOSTS is not specified in the common definition.

During reloading: Continues processing with the definitions used before the reloading.

(O)

Revise the specification of CLIENT_HOSTS in the common definition.

KAVA6050-W

An error occurred while the IP address information was being obtained.

An error occurred during an attempt to obtain the IP address information for the host name specified for CLIENT_HOSTS in the common definition. This error mostly occurs if memory is insufficient.

(S)

During startup: Continues processing, assuming that CLIENT_HOSTS is not specified in the common definition.

During reloading: Continues processing with the definitions used before the reloading.

(O)

Check whether there is sufficient memory in the system. Make sure that sufficient memory is available, and then execute the jbs_spmd_reload command.

KAVA6101-E

An attempt to initialize failed.

The communication process could not be initialized.

(S)

Terminates the communication process.

(O)

Check the OS resources and available memory. If JP1/Base has started on the logical host, make sure that the specified logical host name is correct.

KAVA6117-W

An attempt to send the termination notification to the process management failed.

A termination notification could not be sent to the process management.

(S)

Continues processing.

(O)

Check the OS resources and available memory, and then restart JP1/Base.

KAVA6118-E

An attempt to receive a request failed.

A request could not be received.

(S)

Cancels processing.

(O)

Check the OS resources, available memory, and the status of the network with the higher-level host.

KAVA6119-W

An attempt to send a response failed.

A response could not be sent.

(S)

Continues processing.

(O)

Check the OS resources, available memory, and the status of the network with the higher-level host.

KAVA6129-W

The Plugin manager API function API-name failed. (return code = return-code)

The Plugin Manager API function returned an error.

(S)

Continues processing.

(O)

Check the system status based on the return code. If the system does not recover properly, use the data collection tool to collect data, and then contact the system administrator.

Return code: 50

Description: The process reached the upper limit.

Action: Wait a while, and then re-execute the command.

Return code: 53

Description: The request has timed out.

Action: Wait a while, and then re-execute the command.

Return code: 54

Description: The adapter command has output error information.

Action: Error information has been output during the acquisition of information for a linked product. Check the output error information for the linked product, and take the corrective action.

Return code: 100

Description: An adapter command that can process the request does not exist.

Action: An adapter command for the linked product does not exist in the host where you want to collect data. Check the documentation for the linked product, and then install the command.

Return code: 101

Description: The parameter is invalid.

Action: This is a system error. Use the data collection tool to collect data, and then contact the system administrator.

Return code: 103

Description: The environment is invalid.

Action: Check the environment settings.

Return code: 104

Description: Memory is insufficient.

Action: Check the system memory.

Return code: 105

Description: An error occurred during acquisition of information for a linked product.

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

Return code: 108

Description: The logical host name is invalid.

Action: Make sure that the logical host name is correct.

Return code: 109

Description: A plug-in that can process the request does not exist.

Action: Make sure that the file exists in Base_Path\plugin\lib.

Return code: 110

Description: An attempt to dynamically load a plug-in has failed.

Action: Make sure that you have the permissions to execute the files in Base_Path\plugin\lib.

Return code: 111

Description: The request transmission settings file does not exist.

Action: Make sure that the request transmission settings file for the plug-in service exists.

Return code: 112

Description: An invalid value exists in the request transmission settings file.

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

Return code: 113

Description: Protocol error for collecting plug-in definition.

Action: Use the data collection tool in the host where you want to collect data from, and then contact the system administrator.

Return code: 114

Description: Unattainable network error, or communication connection error.

Action: Check the settings and the status of the network. Also, check whether JP1/Base is running on the host where you want to collect data from.

Return code: 115

Description: An error occurred during transmission processing.

Action: Check the settings and the status of the network. Also, check whether JP1/Base is running on the host where you want to collect data from.

Return code: 116

Description: An error occurred during reception processing.

Action: Check the settings and the status of the network. Also, check whether JP1/Base is running on the host where you want to collect data from.

Return code: 117

Description: The connection was lost.

Action: Check the settings and the status of the network. Also, check whether JP1/Base is running on the host where you want to collect data from.

Return code: 118

Description: Communication governed by an invalid protocol has been received.

Action: Invalid data may have been received temporarily. Re-execute the command.

Return code: 119

Description: Initialization has not been performed.

Action: This is a system error. Use the data collection tool to collect data, and then contact the system administrator.

Return code: 199

Description: An unexpected error occurred.

Action: This is a system error. Use the data collection tool to collect data, and then contact the system administrator.

KAVA6641-E

An attempt to open the catalog file failed.

A message file could not be opened.

(S)

Continues processing.

(O)

The system environment is invalid. Make sure that the installation has ended successfully and that JP1/Base files have not been deleted by mistake.

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

KAVA6642-W

The message is not registered. (message ID = message-ID)

The message ID is unregistered.

(S)

Continues processing.

(O)

The system environment is invalid. Make sure that the installation has ended successfully and that JP1/Base files have not been deleted by mistake.

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

KAVA6643-W

The message file is not open. (message ID = message-ID)

The message file is not open.

(S)

Continues processing.

(O)

The system environment is invalid. Make sure that the installation has ended successfully and that JP1/Base files have not been deleted by mistake.

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

KAVA6651-E

An invalid protocol communication was received.

Communication governed by an invalid protocol was detected.

(S)

Terminates processing.

(O)

Invalid data may have been received temporarily. Re-execute the command.

KAVA6653-E

An attempt to establish a TCP session failed.

A TCP session could not be established.

(S)

Terminates processing.

(O)

Check the network.

KAVA6671-E

Memory allocation failed due to insufficient memory.

An area could not be allocated because of insufficient memory.

(S)

Terminates processing.

(O)

Terminate unused programs so that memory can be allocated.

KAVA6676-I

Initialization was done with the logical host logical-host-name.

Initialization was performed on the logical host (logical-host-name).

KAVA6677-I

Initialization was done with the physical host.

Initialization was performed on a physical host.

KAVA6678-E

An unexpected error occurred.

An unexpected error occurred.

(S)

Terminates processing.

(O)

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

KAVA6679-E

The system call (system-call-name) failed. (return code = return code)

The system call (system-call-name) could not be executed.

(S)

Terminates processing.

(O)

Check the OS resources, available memory, and the status of the network with the higher-level host. If the error persists, use the data collection tool to collect data, and then contact the system administrator.

KAVA6680-E

The system call system-call-name failed. (errno = error-number)

The system call (system-call-name) could not be executed.

(O)

Check the OS resources, available memory, and the status of the network with the higher-level host. If the error persists, use the data collection tool to collect data, and then contact the system administrator.

KAVA6682-E

The JP1/Base communication base could not be initialized. (internal error code = value)

The JP1/Base communications base could not be initialized.

(S)

Terminates processing.

(O)

If JP1/Base has started on the logical host, make sure that the logical host is correct. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KAVA6684-E

Initialization of the common definition API failed.

The common definition API could not be initialized.

(S)

Terminates processing.

(O)

If JP1/Base has started on the logical host, make sure that the logical host is correct. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KAVA6693-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 for the label name has failed.

(S)

During startup: Continues processing, assuming that the common definition for the label name is not defined.

During reloading: Continues processing with the definitions used before the reloading.

(O)

Make sure that:

The settings in the common definition information for the label name are correct.

Sufficient system resources and adequate memory are allocated.

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

KAVA6701-E

A connection to the execution host could not be established. (host = host-name)

A connection to the execution host could not be established.

(S)

Terminates processing.

(O)

On the execution host, check whether:

JP1/Base is Version 8 or later.

The modules for Version 8 or later are installed and active, if JP1/Base is Version 7.

A connection can be established with the execution host.

Both the local host and the execution host use the same IP address version (IPv4 or IPv6).

An error message KAVA6xxx-E has been output to the integrated trace log.

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

For details about how to check the IP address version (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the Job Management Partner 1/Base User's Guide.

KAVA6703-E

The command could not execute because the attempt to start the command failed.

The specified command could not be executed.

(S)

Terminates processing.

(O)

On the execution host, check whether:

The specified command is available.

You have access permissions for the specified command.

The host has sufficient memory.

You have access permissions for the directories and files specified as the output destinations for standard output and standard error output.

An error message KAVA6xxx-E has been output to the integrated trace log.

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

KAVA6705-I

The command will now operate in interchangeable character encoding mode. (jbsrmt)

The interchangeable character encoding mode was enabled when a general command for remote execution was started.

(S)

Continues processing.

KAVA6706-W

The value specified for the interchangeable character encoding mode is invalid. (jbsrmt)

A value that is not 0 or 1 was set for the function that converts the encoding from Japanese UTF-8 into Japanese EUC in the common definition information. Accordingly, the interchangeable character encoding mode was disabled.

(S)

Disables the interchangeable character encoding mode.

(O)

Check the option value set for the interchangeable character encoding mode.

KAVA6707-E

The upper limit for processing on the execution host was exceeded.

The upper limit for processing on the execution host was exceeded.

(S)

Terminates processing.

(O)

Wait a while, and then re-execute the command. If the error persists, check the execution status of commands or jobs connected to other execution hosts.

KAVA6709-I

A cancellation request was received.

A cancellation request was received.

(S)

Continues processing.

KAVA6711-E

An argument is incorrect.

An argument is incorrect.

(S)

Terminates processing.

(O)

Check the command arguments, and then re-execute the command.

KAVA6713-E

An invalid logical host name was specified.

The specified logical host is invalid.

(S)

Terminates processing.

(O)

Check the logical host name. Then re-execute the command, specifying the correct logical host name.

KAVA6715-E

Initialization of the common definition API has failed.

The common definition API could not be initialized.

(S)

Terminates processing.

(O)

If JP1/Base is running on a logical host, make sure that the logical host is correct. If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

KAVA6717-E

Initialization of log output processing was not completed. (maintenance-information)

Log output processing could not be initialized. The probable causes are as follows:

The user may not have access permissions for files under the log directory.

Disk capacity may be insufficient.

The maximum number of files that can be opened may have been reached.

The location of the log directory is as follows:

In Windows

On physical hosts: JP1/Base-installation-folder\log\plugin

On logical hosts: shared-folder\jp1\base\log\plugin

In UNIX

On physical hosts: /var/opt/jp1base/log/plugin

On logical hosts: shared-directory/jp1base/log/plugin

(S)

Terminates processing.

(O)

Remove the cause of the error, 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.

KAVA6719-E

Initialization of communication with the plug-in service has failed.

The plug-in service API could not be initialized.

(S)

Terminates processing.

(O)

Make sure that JP1/Base has been installed successfully and that JP1/Base files have not been deleted by mistake.

If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

KAVA6721-E

Memory allocation failed due to insufficient memory.

Memory could not be allocated because of insufficient memory.

(S)

Terminates processing.

(O)

Make sure that sufficient memory is available, and then re-execute the command.

KAVA6722-E

The environment file (file-name) was not found.

The specified environment variable file could not be found.

(S)

Terminates processing.

(O)

Make sure that the specified file exists on the execution host and that the path is correct.

KAVA6723-E

An error occurred during processing to send a request to the execution host.

An error occurred during processing to send a request to the execution host. The probable causes are as follows:

The status and setup of the network connecting to the execution host does not allow normal communication.

Memory is insufficient.

(S)

Terminates processing.

(O)

Remove the cause of the error, 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.

KAVA6724-E

Loading of the environment file (file-name) failed.

The environment variable file could not be loaded.

(S)

Terminates processing.

(O)

Check whether a folder name or directory name is specified as the file name. Also make sure that the contents of the file are correct, and that you have appropriate permissions for it.

KAVA6725-E

An error occurred during reception of data from the execution host.

An error occurred during reception processing.

(S)

Terminates processing.

(O)

Make sure that the status and setup of the network connecting to the execution host allows normal communication.

KAVA6726-E

The command could not execute because the attempt to simulate the user environment failed.

The user could not be masked.

(S)

Terminates processing.

(O)

Make sure that:

The OS user defined in the user mapping exists.

In Windows, the password of the OS user defined in the user mapping has not changed.

In Windows, the OS user defined in the user mapping has the user rights Logon as a service and Local logon.#

In UNIX, the user ID of the OS user defined in the user mapping is valid.

#: For details about how to set the user rights, see 8.1.5(2) Assigning a user right to an OS user in the Job Management Partner 1/Base User's Guide.

KAVA6727-E

Invalid protocol data was sent or received.

Invalid protocol data was received.

(S)

Terminates processing.

(O)

Invalid data was encountered during communication. Re-execute the command.

KAVA6728-E

The command could not execute because the attempt to perform user mapping failed.

User mapping failed.

(S)

Terminates processing.

(O)

Make sure that the specified JP1 user is defined in the user mapping.

KAVA6730-E

The command could not execute because the attempt to set an environment variable failed.

The environment variable could not be set.

(S)

Terminates processing.

(O)

Make sure that the execution host has sufficient memory.

KAVA6731-E

"item" exceeds the prescribed length.

The specified item exceeds the prescribed length.

(S)

Terminates processing.

(O)

Reduce the number of characters, and then re-execute the command.

KAVA6732-E

A communication error occurred. Processing will now end.

A communication error occurred.

(S)

Terminates processing.

(O)

Check whether JP1/Base is running on the execution host. If JP1/Base is running, check whether there is a problem with the network.

KAVA6733-E

An error occurred. Processing ended.

Processing was terminated because an error occurred.

(S)

Terminates processing.

(O)

An error is recorded before this message in the integrated trace log. Check and remove the cause of error, and then re-execute the command.

KAVA6735-E

The signal SIGTERM was received. Processing ended.

Processing was terminated because a signal was received.

(S)

Terminates processing.

(O)

Check the source of the signal.

KAVA6737-E

Thread generation failed.

The thread could not be generated.

(S)

Terminates processing.

(O)

Check whether there is sufficient memory. If memory is insufficient, close other applications and then re-execute the command. If the error was caused by something else, use the data collection tool to collect data, and then contact the system administrator.

KAVA6739-E

The environment variable environment-variable-name is incorrect.

The environment variable is invalid.

(S)

Terminates processing.

(O)

Set the environment variable correctly, and then re-execute the command.

KAVA6741-E

Exceeded The limit (value) of receiving size.

The volume of data received exceeded the maximum.

(S)

Terminates processing.

(O)

Re-execute the command so that the volume of data received does not exceed the maximum.

KAVA6743-E

Pipe processing failed.

An error occurred during pipe processing.

(S)

Terminates processing.

(O)

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

KAVA6745-E

The environment variable environment-variable-name is required but is not set up.

A mandatory item has not been set.

(S)

Terminates processing.

(O)

Set the mandatory item, and then re-execute the command.

KAVA6747-E

An error occurred during data reception.

An error occurred while receiving data.

(S)

Terminates processing.

(O)

Check whether there is sufficient memory. If memory is insufficient, close other applications and then re-execute the command. If the error was caused by something else, use the data collection tool to collect data, and then contact the system administrator.

KAVA6748-E

Root privileges or JP1/Base administrator privileges are required to execute the command.

(S)

Terminates command processing.

(O)

Re-execute the command as a user who has root privileges or JP1/Base administrator privileges.

KAVA6801-I

File placement will now start.

Processing to install the Version 7 compatible file in directories will now start.

(S)

Continues processing.

KAVA6803-E

A file was not placed correctly.

A Version 7 compatible file could not be placed correctly in a directory.

(S)

Cancels processing.

(O)

Make sure that:

The directory to which the files are expanded has sufficient free space.

The JP1/Base installation directory has sufficient free space.

The executing user has superuser permission.

If none of these apply, use the data collection tool to collect data, and then contact the system administrator.

KAVA6805-E

The user does not have permission to execute the command.

The user who attempted to execute the command did not have Administrators permissions.

(S)

Cancels processing.

(O)

Execute the command as a user who has Administrators permissions.

KAVA6807-E

JP1/Base is not installed.

JP1/Base is not installed.

(S)

Cancels processing.

(O)

Check whether JP1/Base Version 7 is installed.

KAVA6809-E

This is not a supported version.

This version is not supported.

(S)

Cancels processing.

(O)

Check whether JP1/Base is Version 7. If so, JP1/Base may not be installed correctly. Reinstall JP1/Base, and then re-execute the command.

KAVA6811-E

A log file could not be opened.

A log file could not be opened.

(S)

Cancels processing.

(O)

Make sure that the executing user has the appropriate operating permission (deletion and creation permission) for the files 0800_jbs_setup_V7.log and 0800_jbs_setup_V7_bak.log in the folder JP1/Base-installation-folder\jp1base\log\.

KAVA6813-I

File placement ended successfully.

Indicates that file placement ended successfully.

(S)

Terminates processing.

KAVA6815-W

file-name will not be copied because the modification time of the existing file is more recent.

Indicates that the file already exists at the destination, and the existing file is newer.

(S)

Continues processing.

KAVA6817-E

The directory directory-name does not exist.

The destination directory does not exist.

(S)

Cancels processing.

(O)

JP1/Base may not be installed correctly. Re-install JP1/Base, and then re-execute the command.

KAVA6851-I

The command will now start. (host-name)

The command will now start.

(S)

Continues processing.

KAVA6853-I

The command will now end. (host-name)

The command will now end.

(S)

Terminates processing.

KAVA6855-E

An attempt to start the command failed.(cause-of-error)

The command could not be started.

(S)

Terminates processing.

(O)

Eliminate the cause of the error, and then re-execute the command.

2.8 Health check messages (KAVA7001 to KAVA7560)

KAVA7001-I

The health check function will now start. (logical-host-name)

The health check function will now start.

(S)

Continues processing.

KAVA7002-I

The health check function will now stop. (logical-host-name)

The health check function will now stop.

(S)

Terminates the health check function.

KAVA7003-E

The health check function stopped because an error occurred. (host name = host-name)

The health check function will now stop because an error occurred.

(S)

Terminates the health check function.

(O)

Check the contents of the error message that was output immediately before this message.

KAVA7013-W

function-name has been processing for nn seconds. After passes of mm seconds, becomes error condition. (host name = host-name, process name = process-name, internal function name = internal-function-name, pid = process-ID, tid = thread-ID)

The function indicated in function-name was placed in a warning status due to retention of processing in the process or thread.

(S)

Continues processing.

(O)

Check the status of the indicated function. Also take action as described in the chapter about troubleshooting in the manual Job Management Partner 1/Base User's Guide.

KAVA7014-E

function-name has been processing for nn seconds. (host name = host-name, process name = process-name, internal function name = internal-function-name, pid = process-ID, tid = thread-ID)

The function indicated in function-name was placed in an error status due to retention of processing in the process or thread.

(S)

Continues processing.

(O)

Check the status of the indicated function. Also take action as described in the chapter about troubleshooting in the manual Job Management Partner 1/Base User's Guide.

KAVA7016-I

function-name has a normal status. (host name = host-name, process name = process-name, internal function name = internal-function-name, pid = process-ID, tid = thread-ID)

The function indicated in function-name has returned to a normal status.

(S)

Continues processing.

KAVA7017-E

function-name ended abnormally. (host name = host-name, process name = process-name, internal function name = internal-function-name, pid = process-ID, tid = thread-ID)

The function indicated in function-name terminated abnormally.

(S)

Continues processing.

(O)

Check the status of the indicated function. Also take action as described in the chapter about troubleshooting in the manual Job Management Partner 1/Base User's Guide.

KAVA7020-E

Event transmission has failed. (Event ID = numeric-value)

An attempt to send a JP1 event has failed.

(S)

Continues processing.

(O)

Make sure that:

The event service is running. (You can check this by using the jevstat command.)

The service name specified for the ports parameter as an application port in the event server settings file (conf) is set in the services file.

Communication is possible between the address specified for the ports parameter in the event server settings file (conf) and the addresses specified for the server and client parameters in the API settings file.

When JP1/Base is operating with the ANY binding method on a host that uses IPv6 addresses, the IPv6 address of the local host is set in the jp1hosts2 information.

KAVA7023-I

The daemon does not supervise because the health check function is invalid. (logical-host-name)

Monitoring will not be performed because the health check function is invalid.

(S)

Continues processing.

KAVA7026-E

The logical hostname is invalid. (logical hostname = logical-host-name)

The logical host name is invalid.

(S)

Terminates the health check function.

(O)

If the JP1_HOSTNAME environment variable has been set, make sure that the setting is correct.

KAVA7027-E

An attempt to initialize the common configuration information has failed. (error code = numeric-value)

An attempt to initialize the common configuration information has failed.

(S)

Terminates the health check function.

(O)

The setting in the common configuration information may have an error. Make sure that the setting is correct.

KAVA7028-E

An attempt to initialize the log library has failed. (error code = numeric-value)

An attempt to initialize the log output has failed.

(S)

Terminates the health check function.

(O)

Make sure that:

You have access permission for the log directory.

The message file exists.

The disk has sufficient free space.

KAVA7030-E

The shared memory is locked. (host name = host-name, process name = process-name, internal function name = internal-function-name, pid = process-ID, tid = thread-ID)

The status of the process cannot be checked because the shared memory is locked.

(S)

Continues processing.

(O)

Check the status of the indicated function.

KAVA7031-E

An attempt to reference shared memory has failed.

An attempt to reference shared memory has failed.

(S)

Continues processing.

(O)

If this message was output repeatedly, stop all the JP1/Base services, and then restart them.

KAVA7032-W

The status of function-name cannot be confirmed. (host name = host-name, process name = process-name, internal function name = internal-function-name, pid = process-ID, tid = thread-ID)

The status of the process could not be checked because the shared memory for the indicated function could not be referenced.

(S)

Continues processing.

(O)

If the KAVA7034-I message was output after this message, the status has already been restored. If the KAVA7033-E message, not the KAVA7034-I message, was output, take action as described in (O) for the KAVA7033-E message.

KAVA7033-E

The status of function-name still cannot be confirmed. (host name = host-name, process name = process-name, internal function name = internal-function-name, pid = process-ID, tid = thread-ID)

Because the status in which the shared memory for the indicated function could not be referenced continued, the status of the process could not be checked.

(S)

Continues processing.

(O)

If the KAVA7034-I message was output after this message, the status has already been restored. If the KAVA7034-I message was not been output, restart JP1/Base.

If the status still cannot be restored, use the data collection tool to collect data, and then contact the system administrator.

KAVA7034-I

The status of function-name can now be confirmed. (host name = host-name, process name = process-name, internal function name = internal-function-name, pid = process-ID, tid = thread-ID)

The shared memory for the indicated function can now be referenced.

(S)

Continues processing.

KAVA7050-W

The definition file of the health check function does not exist. The default value will be used for startup. (host name = host-name)

The health check definition file does not exist. The default value will be used for startup.

(S)

Continues processing.

(O)

Copy the jbshc.conf.model file, and then re-set the health check definition file.

KAVA7051-W

There is an error in the definition file of the health check function. (line line-number: detailed-information) The default value will be used. (host name = host-name)

The health check definition file contains an error.

(S)

Continues processing, using the default value.

(O)

Correct the indicated line in the health check definition file, and then restart.

KAVA7052-W

There is an error in the definition file of the health check function. (line line-number: detailed-information) Processing of the following will be invalid: (host name = host-name)

The health check definition file contains an error.

(S)

Continues processing, using the default value.

(O)

Correct the indicated line in the health check definition file, and then restart.

KAVA7053-E

The health check function will now stop because the startup notification for the process manager has failed.

A startup notification on the health check function could not be sent to the process manager.

(S)

Terminates the health check function.

(O)

Make sure that the process manager is running correctly.

KAVA7054-E

An attempt to acquire the path of the definition file has failed. The health check function will end abnormally.

The path of the health check definition file could not be acquired.

(S)

Terminates the health check function.

(O)

Make sure that JP1/Base is installed and set up correctly.

KAVA7055-I

Data from the health check function will now be updated due to a reload request from the process manager.

Data from the health check function will now be reloaded because a reload request was sent from the process manager.

(S)

Continues processing.

KAVA7056-W

An attempt to reread the definition file has failed. Processing will continue by using the data from before the reread attempt.

An attempt to reread the health check definition file has failed.

(S)

Continues processing, using the data in effect before the reread.

(O)

Make sure that the health check definition file is placed in the correct location. If the health check definition file does not exist, copy the jbshc.conf.model file and then re-set the health check definition file.

KAVA7057-E

The health check function will now stop because there was an invalid request from the process manager. (process management request code = numeric-value)

An invalid request from the process manager was received.

(S)

Terminates the health check function.

(O)

Make sure that the process manager is running correctly.

KAVA7058-I

The health check function will now stop due to a stop request from the process manager.

A stop request from the process manager was received.

(S)

Terminates the health check function.

KAVA7201-E

An attempt to initialize the communication base of JP1/Base has failed. (internal error code = numeric-value)

An attempt to initialize the communication base of JP1/Base has failed.

(S)

Terminates the health check function.

(O)

Make sure that the system has sufficient memory. Also make sure that the OS is running correctly.

KAVA7202-W

The jp1hosts contents will not become effective because the jp1hosts definition is incorrect.

The setting in jp1hosts will not be effective because the jp1hosts definition is incorrect.

(S)

Continues processing.

(O)

Check the setting in the jp1hosts definition file.

KAVA7203-E

An attempt to initialize the plugin service has failed.

An attempt to initialize the plugin service has failed.

(S)

Terminates the health check function.

(O)

Make sure that one of the following log folders or log directories exists.

In Windows XP and Windows Server 2003:

Physical host: installation-folder\log\plugin\

Logical host: shared-folder\jp1base\log\plugin\

In Windows Vista:

Physical host: %ALLUSERSPROFILE%\Hitachi\jp1\jp1_default\JP1Base\log\plugin\

Logical host: %ALLUSERSPROFILE%\Hitachi\jp1\logical-host-name#\JP1Base\log\plugin\

#: logical-host-name is the actual host name.

In UNIX:

Physical host: /var/opt/jp1base/log/plugin/

Logical host: shared-directory/jp1base/log/plugin/

If these log folders or log directories exist, make sure that the system has sufficient memory. If you did not find any problems, use the data collection tool to collect data, and then contact the system administrator.

KAVA7204-I

The health check function will now stop. (logical-host-name)

Terminates the health check function.

(S)

Terminates the health check function.

KAVA7205-W

An attempt to initialize the event service has failed.

An attempt to initialize the event service has failed.

(S)

Continues processing.

(O)

Make sure that the system has sufficient memory. Also make sure that the OS is running correctly.

KAVA7206-E

The health check function will now stop because the startup notification for the process manager has failed.

A startup notification on the health check function could not be sent to the process manager.

(S)

Terminates the health check function.

(O)

Make sure that the process manager is running correctly.

KAVA7207-I

The health check function will now start. (logical-host-name)

The health check function will now start.

(S)

Continues processing.

KAVA7208-E

Communication processing with the process manager cannot be performed.

Communication with the process manager cannot be performed.

(S)

Terminates the health check function.

(O)

Make sure that the process manager is running correctly.

KAVA7209-I

A host subject to monitoring does not exist.

Other hosts will not be monitored because a host to be monitored is not specified in the health check definition file.

(S)

Continues processing.

KAVA7210-E

The health check function will now stop because an error occurred. (host name = host-name)

The health check function will now stop because an error occurred.

(S)

Terminates the health check function.

(O)

Check the contents of the error message that was output immediately before this message, and then take action.

KAVA7211-I

Data from the health check function will now be updated due to a reload request from the process manager.

Data will now be reloaded because a reload request was sent from the process manager.

(S)

Continues processing.

KAVA7212-E

Reload processing has failed.

An attempt to reload data has failed.

(S)

Continues processing.

KAVA7213-E

The health check function will now stop because there was an invalid request from the process manager. (process manager request code = numeric-value)

An invalid request from the process manager was received.

(S)

Terminates the health check function.

(O)

Make sure that the process manager is running correctly.

KAVA7214-I

The health check function will now stop due to a stop request from the process manager.

A stop request from the process manager was received.

(S)

Terminates the health check function.

KAVA7215-E

Event transmission has failed. (Event ID = numeric-value)

An attempt to send a JP1 event/ has failed.

(S)

Continues processing.

(O)

Make sure that:

The event service is running. (You can check this by using the jevstat command.)

The service name specified for the ports parameter as an application port in the event server settings file (conf) is set in the services file.

Communication is possible between the address specified for the ports parameter in the event server settings file (conf) and the addresses specified for the server and client parameters in the API settings file.

When JP1/Base is operating with the ANY binding method on a host that uses IPv6 addresses, the IPv6 address of the local host is set in the jp1hosts2 information.

KAVA7219-W

The starting time for the next monitoring period has arrived, but monitoring will be waited because the last monitoring period has not finished.

The starting time for the next monitoring period has arrived, but monitoring will be held up because the last monitoring period has not finished yet.

(S)

Continues processing.

(O)

Check the monitoring interval for monitoring other hosts.

KAVA7220-E

An attempt to initialize the health check API.

An attempt to initialize the health check API has failed.

(S)

Continues processing.

(O)

Monitoring with the health check function will not be performed. If you want monitoring using the health check function, restart the service.

KAVA7221-E

Reload notification for the process manager has failed.

Reload notification for the process manager has failed.

(S)

Continues processing.

(O)

Make sure that the process manager is running correctly.

KAVA7222-E

Monitoring notification cannot be performed at host-name because service-name is not functioning.

Monitoring is impossible because the service indicated in service-name on the monitored host has stopped.

(S)

Continues processing.

(O)

Check whether the service for which the error was reported is running correctly on the monitored host.

KAVA7223-E

Monitoring cannot be performed because a connection with host-name cannot be established.

Monitoring is impossible because the host to be monitored cannot be connected.

(S)

Continues processing.

(O)

To correct the cause of the error, check the environment to make sure that:

The network is in the normal status.

Both the local host and the host to be monitored use the same IP address version (IPv4 or IPv6).

JP1/Base is running on the host to be monitored.

JP1/Base 07-51 or a later version is installed on the host to be monitored.

The health check function is valid on the host to be monitored.

If the problem cannot be corrected, use the data collection tool to collect data for the host to be monitored and the monitoring host, and then contact the system administrator.

For details about how to check the IP address version (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the Job Management Partner 1/Base User's Guide.

KAVA7224-I

host-name can now be monitored.

The host can now be monitored.

(S)

Continues processing.

KAVA7225-I

The daemon does not supervise because the health check function is invalid. (host-name)

Monitoring will not be performed because the health check function is invalid.

(S)

Continues processing.

KAVA7226-E

The health check function will now stop because an error occurred. (details)

The health check function will now stop because an error occurred.

(S)

Terminates the health check function.

(O)

Check the contents of the error message that was output immediately before this message, and then take action.

KAVA7227-I

Monitoring resumes because the last monitoring period has finished.

Monitoring resumes because the last monitoring period has finished.

(S)

Continues processing.

KAVA7228-I

The host host-name will not be monitored because it is not running.

The indicated host will not be monitored because it is not running.

(S)

Continues processing.

KAVA7229-W

Monitoring cannot be performed because a connection cannot be established with host-name, which is not receiving stop notifications.

The indicated host cannot be monitored because a connection to the host cannot be established. Because a stop notification event has not been received#, it is impossible to determine whether the host has stopped or failed.

#

Even if a stop notification event was received, this message might also be output if the manager host was restarted after the reception of the notification event. This is because the status of the monitored host retained on the manager host is reset.

(S)

Continues processing.

(O)

To correct the cause of the error, check the environment to make sure that:

The network is in the normal status.

Both the local host and the host to be monitored use the same IP address version (IPv4 or IPv6).

JP1/Base is running on the host to be monitored.

The version of JP1/Base installed on the monitored host is 10-00 or later.

The health check function is enabled on the monitored host.

If the problem cannot be corrected, use the data collection tool to collect data for the host to be monitored and the monitoring host, and then contact the system administrator.

For details about how to check the IP address version (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the Job Management Partner 1/Base User's Guide.

KAVA7230-I

Start and stop notification events will not be monitored for.

Start and stop notification events will not be monitored.

(S)

Continues processing.

KAVA7231-I

Start and stop notification events will be monitored for.

Start and stop notification events will be monitored.

(S)

Continues processing.

KAVA7560-E

Root privileges or JP1/Base administrator privileges are required to execute the command.

Execute the command as a user who has root privileges or JP1/Base administrator privileges.

(S)

Terminates command processing.

(O)

Re-execute the command as a user who has root privileges or JP1/Base administrator privileges.

2.9 Command execution messages (KAVB2002 to KAVB2638)

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 execution of the entered command.

However, the command is not executed if this message is output via the first execution after a restart caused by a physical disconnection, such as the power being cut for host host-name.

(O)

This message may be output for a host whose formal name cannot be resolved by the host indicated in host-name, where host-name indicates the host name at the level defined in the configuration definition.

Check the registration of the host-name host in the hosts file and in DNS, and check the configuration definition.

Re-execute the command if this message is output via the first execution after a restart caused by a physical disconnection, such as the power being cut for host host-name.

If none of the above conditions apply, make sure there are no problems with the communication environment, and then check various items, such as the system logs and the communication device logs.

KAVB2003-E

Cannot connect to host-name host; so, the command-name command cannot be executed.

The command cannot be executed because the command destination host cannot be connected.

(S)

Does not execute the command.

(O)

To correct the cause of the error, check the environment to make sure that:

The network is in the normal status.

Both the local host and the command destination host use the same IP address version (IPv4 or IPv6).

JP1/Base is running on the command destination host.

If the problem cannot be corrected, use the data collection tool to collect data for the local host and the command destination host, and then contact the system administrator.

For details about how to check the IP address version (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the Job Management Partner 1/Base User's Guide.

KAVB2005-E

The command-name command was rejected because it could not be relayed to the local host.

The same IP address is specified for the JP1/IM host that issued the command execution request and the host to which the command is to be transferred.

(S)

Does not execute the command.

(O)

Make sure that:

IP address resolution of the command destination host in the configuration definition is correct.

The host name and IP address for which the message was output are specified 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=end-code

Execution of the command indicated in command-name has ended. In Windows, the entered command is executed as cmd.exe. In UNIX, this command is executed as a shell argument of the execution user. The values of the cmd.exe or the argument are output as the process ID and end code.

KAVB2022-E

Reception of the command was rejected because it exceeds the maximum length of 1024 bytes.

The length of the command including arguments exceeds 1,024 bytes.

(S)

Does not execute the command.

(O)

Check and, if necessary, revise the length of the command including arguments.

KAVB2023-E

Could not find the command-name command.

The indicated command does not exist.

(S)

Does not execute the command.

(O)

In Windows, make sure that cmd.exe exists. In UNIX, make sure that the shell of the execution user exists.

KAVB2024-E

Command cannot be executed because the corresponding host (host-name) is not registered in hosts.

The address of the host indicated in host-name cannot be resolved.

(S)

Does not execute the command.

(O)

Modify the settings so that the address of the indicated host can be resolved.

KAVB2027-E

Cannot execute the command. Failed to simulate the user user-name environment.

The command cannot be executed because the user mapping failed.

(S)

Does not execute the command.

(O)

Make sure that:

The JP1 user (user-name) is defined in the user mapping for the command execution host.

The OS user defined in the user mapping exists, and the OS user distinguishes the domain user from the local user.

An asterisk (*) or a manager host name is set for Server host name for the JP1 user (user-name) defined in the user mapping.

If the operating system of the execution host is Windows and the OS user defined in the user mapping has the user rights Log on as a service and Log on locally.#1

If the operating system of the execution host is Windows, the password of the OS user defined in the user mapping has not changed.

If the operating system of the execution host is Windows and both physical and logical hosts are started at the same time, the jp1hosts information or jp1hosts2 is set.#2

If the operating system of the execution host is UNIX, the user ID of the OS user defined in the user mapping is valid.

If the OS user defined in the user mapping is a domain user, the domain controller is not restarted.

#1: For details about how to set the user rights, see 8.1.5(2) Assigning a user right to an OS user in the Job Management Partner 1/Base User's Guide.

#2: For details about how to set the information, see 5.4.5 Settings to configure both physical and logical host environments on the same logical host in the Job Management Partner 1/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.

An attempt was made to execute the command for a host that was not being managed, or the host name of the execution host cannot be resolved.

(S)

Does not execute the command.

(O)

In the configuration definition, define the host specified as the execution host.

For the execution host, specify a host that is defined in the system configuration definition and that is under the logged-on manager host.

Specify the settings so that the host name of the execution host and the host name in the configuration definition can be resolved.

KAVB2037-I

Terminated Command Control.

Command control has stopped.

KAVB2041-E

Could not find the Environment file(file-name).

The environment variable file specified in the Execute Command window or action definition is not found.

(O)

Make sure that the specified file exists on the execution host and that the path is correct.

KAVB2042-E

Jcocmd received an illegal request from process manager.

Command control received an invalid request from the process manager.

(S)

Terminates the remote command.

(O)

Check the following:

Make sure that sufficient system resources and available memory are allocated.

Make sure that the OS is running normally.

In UNIX, make sure that sufficient disk space is allocated under /var/opt/jp1base.

In UNIX, make sure that there are appropriate permissions under /var/opt/jp1base.

If the problem cannot be corrected, use the data collection tool to collect data, and then contact the 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]

The connected host does not send a response.

(S)

Continues execution of the entered command.

(O)

Make sure that JP1/Base is running on the host indicated in host-name.

KAVB2052-I

Since the connection with host [host-name] was released, command response processing was interrupted.

The command response is canceled because the connection with the host was released. This message may be output if JP1/Base on the host indicated in host-name was stopped during command execution of if execution of the command requires a long time.

(S)

Cancels the command response because the connection with the host was released. If execution of the command requires a long time, the system temporarily releases the connection, but executes the command normally.

(O)

If the command execution does not require a long time, make sure that JP1/Base is running on the host indicated in host-name. If JP1/Base is running, check the network for errors.

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]

The output IP address could not be bound.

(S)

Cannot start at the output IP address, or does not execute the command.

(O)

Make sure that the output IP address is available.

KAVB2054-E

Socket listen error. An attempt to listen to the host [host-name] has failed. [internal-message].

A listen system call has failed.

(S)

Cannot receive communication at the output host IP address.

(O)

Make sure that there are sufficient resources.

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)

Modify the settings 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)

Check the communication environment for invalid packets.

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 has failed.

(S)

Does not send the command execution results.

(O)

Make sure that the command execution host has sufficient resources.

KAVB2058-E

The command request has been rejected, since the command queueing limit has been exceeded.

The number of received command execution requests exceeded the command queuing limit.

(S)

Does not execute the command.

(O)

Use the jcocmddef command to increase the number of commands that can be queued.

If this message still appears, do the following:

Reduce the number of requests for commands whose execution requires a long time.

Reduce the number of commands requested.

KAVB2059-E

Due to an internal error, an attempt to execute the command [command-name] has failed. [internal-message].

A system call has failed during execution of the command on the command execution host.

(S)

Does not execute the command.

(O)

Make sure that the command execution host has sufficient resources.

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 of the host for which command execution was specified.

(S)

Does not display the command execution results.

(O)

Make sure that the host for which command execution was specified has sufficient resources.

KAVB2061-E

Due to an internal error, the command request [command-name] has been rejected.

An error occurred during transfer of the command name between internal processes of the host for which command execution was specified.

(S)

Does not execute the command.

(O)

Make sure that the host for which command execution is specified has sufficient resources.

KAVB2062-E

The command [command-name] cannot be sent from host [host-name] to host [host-name].

An error occurred while the command execution request was being sent.

(S)

Does not execute the command.

(O)

Make sure that the destination host has sufficient resources.

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)

Starts at the default port.

(O)

Make sure that the port number for the jp1imcmda or jp1imcmdc service is defined in the services file.

KAVB2064-E

Error in writing execution results to Command execution log.

An attempt to write the command execution log file has failed.

(S)

Does not save the command execution results in the command execution log file.

(O)

Check the following. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

Make sure that there are sufficient system resources.

Make sure that the operating system is running normally.

Make sure that the disk to which the command execution log file is output has sufficient free space.

Make sure that the output destination of the command execution log file has appropriate permissions.

The command execution log file may be corrupted. In this case, execute either of the following commands to recover the execution log file:

For details on how to check the status of the command execution log file and how to recover the file, see the chapter about troubleshooting in the Job Management Partner 1/Integrated Management - Manager Administration Guide.

If the command execution log file is in normal status, execute the data collection tool of JP1/IM, and then contact the system administrator.

KAVB2065-W

Failed to load the Environment file(file-name).

An attempt to read the environment variable file has failed.

(S)

Executes the command, but does not validate the contents of the environment variable file.

(O)

Check whether a folder name or directory name is specified as the file name. Also make sure that the contents of the file are correct, and that you have appropriate permissions for it.

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

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

Maintenance information is shown using the end-code:error-information format. Check this information as follows:

When the end code is 10000, or in the range from 10011 to 10099:

Make sure that there are sufficient resources on the command execution host.

When a signal is indicated in the error information:

Check whether a process output the indicated signal on the command execution host.

If neither of the above conditions occurred or if the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KAVB2069-E

command-name was rejected because forward transmission processing could not be performed. (host-name)

The command (command-name) to be sent was rejected. This is because other commands being sent had accumulated in the execution control queue on the host indicated in host-name, and sending any more commands might affect the operation.

(S)

Does not execute the command.

(O)

Check whether a network error occurred between the host indicated in host-name and the host where the command was executed.

KAVB2070-W

Acquisition of the command execution results was interrupted because the specified maximum of xx lines was reached.

Acquisition of further command execution results was interrupted because data for the specified number of lines was acquired.

(S)

Executes the command, but does not acquire the execution results.

KAVB2071-W

In target-host-name, the number of queued commands requested from requesting-host-name has exceeded the threshold (xx).

On the host indicated in target-host-name, the number of automated actions requested from the host indicated in requesting-host-name reached the threshold (xx) for the number of queued automated actions. Automated actions requested by the host indicated in requesting-host-name may have been delayed.

(S)

Continues processing.

(O)

Make sure that:

Too many actions were generated on the requesting host. If they were, consider suppressing the automated actions or increasing the number of commands that can be executed concurrently.

A command was still being executed on the target host. Use the jcocmdshow command to check for a command that has not terminated on the target host. If you find such a command, terminate it by using the jcocmddel command.

KAVB2072-I

In target-host-name, the number of queued commands requested from requesting-host-name has become 0.

On the host indicated in target-host-name, the number of queued automated actions requested from the host indicated in requesting-host-name has become 0.

(S)

Continues processing.

KAVB2100-I

[host-name:JP1-user-name] Command execution started.

Command execution has started.

KAVB2101-I

[host-name:JP1-user-name] Command execution ended normally.

Command execution has ended.

KAVB2102-E

[host-name:JP1-user-name] Command execution ended abnormally.

Command execution has ended abnormally.

(S)

Cancels command execution.

(O)

Take the appropriate action according to the error message indicated in the Execute Command window.

KAVB2103-E

An attempt to send a command execution operation event failed. (ret = [return-code])

An attempt to send a command execution operation event has failed.

(S)

Cancels sending of the event, and continues processing.

(O)

Make sure that:

The event service is running. (You can check this by using the jevstat command.)

The service name specified for the ports parameter as an application port in the event server settings file (conf) is set in the services file.

Communication is possible between the address specified for the ports parameter in the event server settings file (conf) and the addresses specified for the server and client parameters in the API settings file.

When JP1/Base is operating with the ANY binding method on a host that uses IPv6 addresses, the IPv6 address of the local host is set in the jp1hosts2 information.

KAVB2200-E

The [option] option is invalid.

An option specified in the command line is invalid.

(S)

Cancels command processing.

(O)

Execute the command with the correct syntax.

KAVB2201-E

The [option] option is defined more than once.

The same option is specified more than once.

(S)

Cancels command processing.

(O)

Eliminate the duplicated option, and then re-execute the command.

KAVB2202-E

The value for the [option] option is not specified.

A value is not specified in the option.

(S)

Cancels command processing.

(O)

Execute the command with the correct syntax.

KAVB2203-E

Specify between 1 and number-of-bytes bytes for Connected Host | Logical Host | Source Host Name.

The range of values specified in the option is invalid.

(S)

Cancels command processing.

(O)

Check the length of one of the following host names according to the information in the message:

For Connected Host: The host name specified in the -s option

For Logical Host: The host name specified in the -h option

For Source Host Name: The host name specified in the-ph option

KAVB2204-E

The number of arguments is invalid.

The number of arguments is too large or too small.

(S)

Cancels command processing.

(O)

Execute the command with the correct syntax.

KAVB2205-E

jcocmdshow was interrupted.

An interrupt occurred during execution of the command.

(S)

Cancels command processing.

(O)

The command was interrupted by the user. If necessary, re-execute the command.

KAVB2206-E

Super user privilege is required to execute the command.

The execution user does not have Administrators permissions.

(S)

Cancels command processing.

(O)

Execute the command as a user who has Administrators permissions or root privileges.

KAVB2207-E

The specified logical host [host-name] does not exist.

The value of the logical host is invalid.

(S)

Cancels command processing.

(O)

Check the logical host name specified in the -h option.

KAVB2208-E

The specified connected host [host-name] is unknown.

The connected host does not exist.

(S)

Cancels command processing.

(O)

Check the connected host name specified in the -s option.

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)

Cancels command processing.

(O)

The common definition settings for the logical host have a problem. Check the settings of the logical host and, if necessary, respecify the settings.

KAVB2210-E

No response has been received from the connected host [host-name].

The specified connected host does not send a response.

(S)

Cancels 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 for command execution control does not exist.

KAVB2212-E

Memory is insufficient at the jcocmdshow command executing host.

A memory allocation error occurred.

(S)

Cancels command processing.

(O)

Provide sufficient memory, and then re-execute the command.

KAVB2213-E

The maximum number of connections has been exceeded.

The maximum number of connections available for the connected host was exceeded.

(S)

Cancels command processing.

(O)

The maximum number of connections available for the connected host was exceeded. Wait for a while, and then re-execute the command.

KAVB2214-E

Processing at the connected host has been interrupted.

The adapter command on the connected host was stopped due to an interrupt.

(S)

Cancels command processing.

(O)

The command was canceled on the connected host. Re-execute the command.

KAVB2215-E

Command execution control is not responding at the connected host.

The adapter command on the connected host does not send a response.

(S)

Cancels 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 on the logical host is not running normally.

(S)

Cancels command processing.

(O)

The logical host settings for the connected host have a problem. Re-set the connected logical host.

KAVB2217-E

The connected host environment is invalid.

The adapter command on the logical host does not run due to insufficient privileges.

(S)

Cancels command processing.

(O)

Make sure that JP1/Base on the connected host is running with Administrators permissions.

KAVB2218-E

Invalid protocol data was received from command execution control.

The adapter command on the logical host received invalid data.

(S)

Cancels command processing.

(O)

Invalid data was found during communication. Re-execute the command.

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)

Cancels 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 has failed.

(S)

Continues command processing without outputting log data.

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 the log output settings from the common definition information has failed.

(S)

Continues command processing without outputting log data.

KAVB2224-W

An attempt to initialize the HNTR library has failed. Processing will continue without logging messages.

An attempt to initialize HNTRLib2 has failed.

(S)

Continues command processing without outputting log data.

KAVB2225-E

Invalid protocol data was received from command execution control.

Invalid data was received from command execution control.

(S)

Cancels command processing.

(O)

Invalid data was found during communication. Re-execute the command.

KAVB2227-I

jcocmdshow started.

The jcocmdshow command has started.

KAVB2228-I

jcocmdshow terminated. return code: [return-code].

The jcocmdshow command has ended.

KAVB2229-E

Invalid source host name

The string specified in the -ph option contains an invalid character.

(S)

Cancels command processing.

(O)

Check the argument of the -ph option.

KAVB2230-E

The value for the -state option [argument] is invalid.

A character other than r or q is specified for the -state option.

(S)

Cancels command processing.

(O)

Check the argument of 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 available concurrent connections was exceeded.

(O)

The number of connections reached the maximum. Wait for a while, and then re-execute the command.

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 has failed.

(S)

Cancels command processing.

(O)

Make sure that:

Sufficient system resources and available memory are allocated.

The OS is running normally.

There is no problem in the network to the host specified in the -s option.

If the problem cannot be corrected, use the data collection tool to collect data, and then contact the 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)

Cancels command processing.

(O)

Make sure that:

Sufficient system resources and available memory are allocated.

The OS is running normally.

There is no problem in the network to the host specified in the -s option.

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

KAVB2234-E

An error occurred while a request was being processed on the connected host.

The connected host environment is invalid.

(S)

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

A data reception error

(S)

Cancels command processing.

(O)

Make sure that the status and settings of the network with the connected host can be used normally.

KAVB2236-E

An error occurred during data transmission to command execution control.

The following error occurred in the plug-in API:

A data send error

(S)

Cancels command processing.

(O)

Make sure that:

JP1/Base is running on the connected host.

The status and settings of the network with the connected host can be used normally.

KAVB2237-E

The connected host version does not support this command.

The following errors occurred in the plug-in API:

An invalid version

Missing required component

(S)

Cancels command processing.

(O)

Make sure that the version of JP1/Base on the connected host is 07-51 or later.

KAVB2238-E

The connection with the connected host terminated. Try again.

The following error occurred in the plug-in API:

The connection was disconnected.

(S)

Cancels command processing.

(O)

Make sure that the status and settings of the network with the connected host can be used normally.

KAVB2239-E

A network connection with the connected host could not be established.

The following errors occurred in the plug-in API:

A connection error

The plug-in service was busy.

(S)

Cancels command processing.

(O)

To correct the cause of the error, check the environment to make sure that:

The network is in the normal status.

Both the local host and the connection destination host use the same IP address version (IPv4 or IPv6).

JP1/Base is running on the connection destination host.

If the problem cannot be corrected, use the data collection tool to collect data for the local host and the connection destination host, and then contact the system administrator.

For details about how to check the IP address version (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the Job Management Partner 1/Base User's Guide.

KAVB2240-E

The environment is invalid on the jcocmdshow command executing host.

The following errors occurred in the plug-in API:

A syntax error in the settings file

The settings file was not found.

The common definition information for the logical host was not found.

(S)

Cancels command processing.

(O)

The common definition information for the host that executed the jcocmdshow command or the contents of the plug-in service settings file are 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)

Cancels command processing.

(O)

Invalid data was found during communication. Re-execute the command.

KAVB2242-E

JP1/Base does not support this command.

The following error occurred in the plug-in API:

The plug-in was not found.

(S)

Cancels command processing.

(O)

Make sure that the version of JP1/Base on the connected host is 07-51 or later. If the version is correct, the environment may be invalid. Re-install JP1/Base to recover the environment.

KAVB2243-E

A timeout occurred during communication with the plug-in service. Try after a while.

The following errors occurred in the plug-in API:

A request timed out.

The plug-in service was busy.

An attempt to connect to the plug-in service has failed.

(S)

Cancels command processing.

(O)

Wait for a while, and then re-execute the command.

KAVB2244-E

The connection with connected host terminated.

The following error occurred in the plug-in API:

Communication with the plug-in service has failed.

(S)

Cancels 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 request timed out.

(S)

Cancels command processing.

(O)

Wait for a while, and then re-execute the command.

KAVB2246-E

Failed to open catalog file /opt/jp1base/lib/nls/C/jp1BsCmdShow.cat

An attempt to open the catalog file has failed.

(S)

Does not execute the jcocmdshow command.

(O)

In UNIX, check the following. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

Make sure that the catalog file exists under the /opt/jp1base/lib/nls directory.

Make sure that you have read permission for the catalog file and the 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. The catalog file may be corrupted.

(S)

Does not output the message.

(O)

Change the LANG environment variable, and then re-execute the command. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KAVB2248-E

Memory allocation failed due to insufficient memory.

An attempt to allocate space has failed due to insufficient memory.

(S)

Interrupts command processing.

(O)

Allocate sufficient memory, and then re-execute the command.

KAVB2249-E

catopen() API failed. Error number: error-code

An attempt to open the catalog file has failed.

(S)

Does not execute the jcocmdshow command.

(O)

In UNIX, check the following. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

Make sure that the catalog file exists under the /opt/jp1base/lib/nls directory.

Make sure that you have read permission for the catalog file and the 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 for a specific trace log has failed.

(S)

Continues command processing without outputting log data.

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 for a specific trace log has failed.

(S)

Continues command processing without outputting log data.

KAVB2252-E

The specified host to be connected is not subject to configuration management.

The host to be connected could not be connected because it was not subject to configuration management.

(S)

Interrupts command processing.

(O)

Check the connection-destination host name specified in the -s option.

KAVB2253-E

A reply was not returned during communication processing at the host where the jcocmdshow command was executed.

Communication with the connection-destination host has failed during communication processing.

(S)

Interrupts command processing.

(O)

On the host where the command was executed, execute the jbs_spmd_status command to make sure that all the services are running, and then re-execute the command.

KAVB2276-E

The [option] option is invalid.

The option specified in the command line is invalid.

(S)

Cancels command processing.

(O)

Execute the command with the correct syntax.

KAVB2277-E

The [option] option is defined more than once.

The same option is specified more than once.

(S)

Cancels command processing.

(O)

Eliminate the duplicated option, and then re-execute the command.

KAVB2278-E

The value for the [option] option is not specified.

A value is not specified in the option.

(S)

Cancels command processing.

(O)

Execute the command with the correct syntax.

KAVB2279-E

Specify between 1 and [number-of-bytes] bytes for Connected Host.

The range of values specified in the option is invalid.

(S)

Cancels command processing.

(O)

Execute the command with the correct value.

KAVB2280-E

The number of arguments is invalid.

The number of arguments is too large or too small.

(S)

Cancels command processing.

(O)

Execute the command with the correct syntax.

KAVB2281-E

jcocmddel was interrupted.

An interrupt occurred during execution of the command.

(S)

Cancels command processing.

(O)

The command was interrupted by the user. If necessary, re-execute the command.

KAVB2282-E

Superuser privilege is required to execute the command.

The execution user does not have Administrators permissions.

(S)

Cancels command processing.

(O)

Execute the command as a user who has Administrators permissions or root privileges.

KAVB2283-E

The specified logical host host-name does not exist.

The value of the logical host is invalid.

(S)

Cancels command processing.

(O)

Check the logical host name specified in the -h option.

KAVB2284-E

The specified connected host [host-name] is unknown.

The connected host does not exist.

(S)

Cancels command processing.

(O)

Check the connected host name specified in the -s option.

KAVB2285-E

The specified logical host [host-name] does not exist.

The logical host name is invalid or does not exist.

(S)

Cancels command processing.

(O)

The common definition settings for the logical host have a problem. Check the settings of the logical host and, if necessary, respecify the settings.

KAVB2286-E

No response has been received from the connected host [host-name].

The specified connected host does not send a response.

(S)

Cancels command processing.

(O)

Make sure that JP1/Base is running on the connected host.

Make sure that the specified host exists.

Make sure that network communication with the connected host is possible.

KAVB2287-I

No command exists in command execution control.

The command specified for command execution control does not exist.

KAVB2288-E

Memory is insufficient on the jcomddel command executing host.

A memory allocation error occurred.

(S)

Cancels command processing.

(O)

Provide sufficient memory, and then re-execute the command.

KAVB2289-E

<CommandID(s)>/ALL option is required.

The command ID or the ALL option is not specified.

(S)

Cancels command processing.

(O)

Specify the command ID of the command you want to delete, or specify the ALL option to delete all commands.

KAVB2290-E

Command ID(s) cannot be specified with the ALL option.

The command ID and the ALL option are specified at the same time.

(S)

Cancels command processing.

(O)

Specify the command ID of the command you want to delete, or specify the ALL option to delete all commands.

KAVB2291-Q

Do you want to delete the specified command ID(s) [Y/y or N/n] ->

This message confirms that you want to delete the command.

(S)

Suspends command processing until the user enters a response.

(O)

Enter Y or y to continue processing. Enter N or n to cancel processing.

KAVB2292-I

The user cancelled the deletion of command(s).

The jcocmddel command was canceled.

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 ID does not exist.

(S)

Could not 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)

Cancels command processing.

(O)

Specify the command ID within the valid range.

KAVB2296-E

The maximum number of connections on the connected host has been exceeded.

The maximum number of connections available for the connected host was exceeded.

(S)

Cancels command processing.

(O)

Wait for a while, and then re-execute the command.

KAVB2297-E

Processing on the connected host was interrupted.

The adapter command on the connected host was stopped due to an interrupt.

(S)

Cancels command processing.

(O)

The command was canceled on the connected host. Re-execute the command.

KAVB2298-E

Command execution control is not responding on the connected host.

The adapter command on the connected host does not send a response.

(S)

Cancels 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 running normally.

(S)

Cancels command processing.

(O)

The logical host settings for the connected host have a problem. Respecify the settings for the connected logical host.

KAVB2300-E

The connected host environment is invalid.

The adapter command on the logical host does not run due to insufficient privileges.

(S)

Cancels command processing.

(O)

Make sure that JP1/Base on the connected host is running with Administrators permissions.

KAVB2301-E

Invalid protocol data was received in command execution control.

The adapter command on the logical host received invalid data.

(S)

Cancels command processing.

(O)

Invalid data was found during communication. Re-execute the command.

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)

Cancels 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 has failed.

(S)

Continues command processing without outputting log data.

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 has failed.

(S)

Continues command processing without outputting log data.

KAVB2307-W

An attempt to initialize the hntr library has failed. Processing will continue without logging messages.

An attempt to initialize HNTRLib2 has failed.

(S)

Continues command processing without outputting log data.

KAVB2308-E

Invalid protocol data was received from command execution control.

Invalid data was received from command execution control.

(S)

Cancels command processing.

(O)

Invalid data was found during communication. Re-execute the command.

KAVB2310-I

jcocmddel started.

The jcocmddel command has started.

KAVB2311-I

jcocmddel terminated. return code: [return-code].

The jcocmddel command has ended.

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 concurrent connections available was exceeded.

(S)

Cancels processing because the connection was canceled.

(O)

The number of connections reached the maximum. Wait for a while, and then re-execute the command.

KAVB2314-E

An invalid command ID was specified.

An invalid command ID is specified.

(S)

Cancels command processing.

(O)

For the command ID, specify a numeric value from 0 to 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 has failed.

(S)

Cancels command processing.

(O)

Make sure that:

Sufficient system resources and available memory are allocated.

The OS is running normally.

There is no problem in the network to the host specified in the -s option.

If the problem cannot be corrected, use the data collection tool to collect data, and then contact the 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)

Cancels command processing.

(O)

Make sure that:

Sufficient system resources and available memory are allocated.

The OS is running normally.

There is no problem in the network to the host specified in the -s option.

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

KAVB2318-E

An error occurred during request processing on the connected host.

The connected host environment is invalid.

(S)

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

A data reception error

(S)

Cancels command processing.

(O)

Make sure that the status and settings of the network with the connected host can be used normally.

KAVB2320-E

An error occurred during data transmission to command execution control.

The following error occurred in the plug-in API:

A data send error

(S)

Cancels command processing.

(O)

Make sure that:

JP1/Base is running on the connected host.

The status and settings of the network with the connected host can be used normally.

KAVB2321-E

The connected host version does not support this command.

The following errors occurred in the plug-in API:

An invalid version

Missing required component

(S)

Cancels command processing.

(O)

Make sure that the version of JP1/Base on the connected host is 07-51 or later.

KAVB2322-E

Connection with the connected host terminated. Try again.

The following error occurred in the plug-in API:

The connection was disconnected.

(S)

Cancels command processing.

(O)

Make sure that the status and settings of the network with the connected host can be used normally.

KAVB2323-E

A network connection with the connected host could not be established.

The following errors occurred in the plug-in API:

A connection error

The plug-in service was busy.

(S)

Cancels command processing.

(O)

To correct the cause of the error, check the environment to make sure that:

The network is in the normal status.

Both the local host and the connection destination host use the same IP address version (IPv4 or IPv6).

JP1/Base is running on the connection destination host.

If the problem cannot be corrected, use the data collection tool to collect data for the local host and the connection destination host, and then contact the system administrator.

For details about how to check the IP address version (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the Job Management Partner 1/Base User's Guide.

KAVB2324-E

The environment is invalid on the jcocmddel command executing host.

The following errors occurred in the plug-in API:

A syntax error in the settings file

The setting file was not found.

The common definition information for the logical host was not found.

(S)

Cancels command processing.

(O)

The common definition information for 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:

Invalid data was received.

(S)

Cancels command processing.

(O)

Invalid data was found during communication. Re-execute the command.

KAVB2326-E

JP1/Base does not support this command.

The following error occurred in the plug-in API:

The plug-in was not found.

(S)

Cancels command processing.

(O)

Make sure that the version of JP1/Base on the connected host is 07-51 or later. If the version is correct, the environment may be invalid. Re-install JP1/Base to recover the environment.

KAVB2327-E

A timeout occurred during communication with the plug-in service. Try after a while.

The following errors occurred in the plug-in API:

A request timed out.

The plug-in service was busy.

An attempt to connect to the plug-in service has failed.

(S)

Cancels command processing.

(O)

Wait for a while, and then re-execute the command.

KAVB2328-E

The connection with the connected host terminated.

The following error occurred in the plug-in API:

Communication with the plug-in service has failed.

(S)

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

A request timed out.

(S)

Cancels command processing.

(O)

Wait for a while, and then re-execute the command.

KAVB2330-E

Failed to open catalog file /opt/jp1base/lib/nls/C/jp1BsCmdDel.cat

An attempt to open the catalog file has failed.

(S)

Does not execute the jcocmddel command.

(O)

In UNIX, make sure that the catalog file exists under 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. The catalog file may be corrupted.

(S)

Does not output the message.

(O)

Change the LANG environment variable, and then re-execute the command. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KAVB2332-E

Memory allocation failed due to insufficient memory.

An attempt to allocate space has failed due to insufficient memory.

(S)

Interrupts command processing.

(O)

Allocate sufficient memory, and then re-execute the command.

KAVB2333-E

catopen() API failed. Error number: error-code

An attempt to open the catalog file has failed.

(S)

Does not execute the jcocmddel command.

(O)

In UNIX, make sure that the catalog file exists under 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 for a specific trace log has failed.

(S)

Continues command processing without outputting log data.

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 for a specific trace log has failed.

(S)

Continues command processing without outputting log data.

KAVB2336-E

The specified host to be connected is not subject to configuration management.

The host to be connected could not be connected because it was not subject to configuration management.

(S)

Interrupts command processing.

(O)

Check the connection-destination host name specified in the -s option.

KAVB2337-E

A reply was not returned during communication processing at the host where the jcocmddel command was executed.

Communication with the connection-destination host has failed during communication processing.

(S)

Interrupts command processing.

(O)

On the host where the command was executed, execute the jbs_spmd_status command to make sure that all the services are running, and then re-execute the command.

KAVB2339-E

An attempt to delete the commands has failed. Try again.

An error occurred during deletion of commands.

(S)

Interrupts command processing.

(O)

Wait for a while, and then re-execute the command.

KAVB2356-E

The value for the logical logical-host-name is invalid.

The value for the logical host is invalid.

(S)

Interrupts command processing.

(O)

Check the logical host name specified in the -h option.

KAVB2401-I

The logs of commands executed are not displayed for a setup which do not save them.

The command execution logs are not saved due to the settings.

(S)

Continues command processing.

(O)

If you want to save the command execution logs, execute the following command on the host that contains JP1/IM:

jcocmddef -actresult ON

KAVB2402-W

[host-name]The execution time of command execution exceeded the regulation value (numeric-value sec)

The execution time of an executing command exceeded the predefined value.

(S)

Continues command execution.

(O)

Execution of the current command is taking a long time for some reason. Use the jcocmdshow command to check the contents of the command, and then use 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 has failed.

(S)

Cancels processing.

(O)

Re-install JP1/Base.

KAVB2501-E

A value is invalid. (option = option-name value)

The indicated option and value are invalid.

(S)

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

Cancels processing.

(O)

Specify the 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)

Cancels processing.

(O)

Specify the name of an existing logical host.

KAVB2504-E

The host group file file-name cannot be opened.

The specified host group file is not found.

(S)

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

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

Cancels processing.

(O)

The host group file contains a syntax error. Make sure that:

Curly brackets ({}) are written correctly in the host group definitions.

Only one host group name is written before a left curly bracket ({) in the host group definitions.

Correct the syntax error in the host group file, and then re-execute the command.

KAVB2507-E

The group name group-name is too long.

The group name specified in the host group file is too long.

(S)

Cancels processing.

(O)

Specify the group name, using no more than 32 characters.

KAVB2508-E

Access permission is lacking.

A permission error occurred during access to the common definition.

(S)

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

Cancels processing.

(O)

Specify the 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)

Cancels processing.

(O)

The group file name can contain no more than 1,023 characters. Change the file name, and then re-execute the command.

KAVB2511-E

An error occurred at the API of the common definition. (Access permission was lacking.)

An error occurred during access to the common definition.

(S)

Cancels processing.

(O)

Make sure that:

Sufficient system resources and available memory are allocated.

The OS is running normally.

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

KAVB2512-E

An error occurred at the API of the common definitions. (No entry was found.)

An error occurred during access to the common definition.

(S)

Cancels processing.

(O)

Make sure that:

Sufficient system resources and available memory are allocated.

The OS is running normally.

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

KAVB2513-E

An error occurred at the API of the common definitions. (An invalid parameter was used.)

An error occurred during access to the common definition.

(S)

Cancels processing.

(O)

Make sure that:

Sufficient system resources and available memory are allocated.

The OS is running normally.

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

KAVB2514-E

An error occurred at the API of the common definitions. (An internal error occurred.)

An error occurred during access to the common definition.

(S)

Cancels processing.

(O)

Make sure that:

Sufficient system resources and available memory are allocated.

The OS is running normally.

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

KAVB2515-E

An error occurred at the API of the common definitions. (An initialization error occurred.)

An error occurred during access to the common definition.

(S)

Cancels processing.

(O)

Make sure that:

Sufficient system resources and available memory are allocated.

The OS is running normally.

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

KAVB2516-E

An error occurred at the API of the common definitions. (A logic conflict occurred.)

An error occurred during access to the common definition.

(S)

Cancels processing.

(O)

Make sure that:

Sufficient system resources and available memory are allocated.

The OS is running normally.

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

KAVB2517-E

Super user privilege is required to execute the command.

The user who executes the command does not have required permissions.

(S)

Cancels processing.

(O)

Execute the command as a user who has Administrators permissions or root privileges.

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 path to the directory where the command execution log file is saved.

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.

(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 was not 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 execution log of the command executed from the Execute Command window was not found.

(S)

Does not output the execution log of the command executed from the Execute Command window.

(O)

Execute the command from 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 for the command executed from the Execute Command window cannot be opened.

(S)

Does not output the execution log of the command executed from the Execute Command window.

(O)

Check the following. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

Make sure that appropriate permission is set for the destination where the command execution log file is saved.

Check whether the command execution log file is corrupted.

For details on how to check the status of the command execution log file and how to recover the file, see the chapter about troubleshooting in the Job Management Partner 1/Integrated Management - Manager Administration Guide.

If the command execution log file is normal, execute the data collection tool of JP1/IM, and then contact the system administrator.

KAVB2524-W

The command-execution log file for the automatic action does not exist.

An execution log for a command executed by an automated action was not found.

(S)

Does not output the execution log of a command executed by an automated action.

(O)

Execute the automated action, and then re-execute the command.

KAVB2525-E

The command-execution log file for the automatic action cannot be opened.

The command execution log file for an automated action cannot be opened.

(S)

Does not output the execution log of the command executed by an automated action.

(O)

Check the following. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

Make sure that appropriate permission is set for the destination where the command execution log file is saved.

The command execution log file may be corrupted.

For details on how to check the status of the command execution log file and how to recover the file, see the chapter about troubleshooting in the Job Management Partner 1/Integrated Management - Manager Administration Guide.

If the command execution log file is normal, execute the data collection tool of JP1/IM, and then contact the system administrator.

KAVB2526-W

Reading of the command-execution log file was interrupted.

Reading of the command execution log file was interrupted because another process locked this file.

(S)

Interrupts the output of the command execution log.

(O)

Make sure that none of the following processing has been performed, and then re-execute the jcocmdlog command:

Execution of an automated action

Execution of a command from the Execute Command window

Execution of another jcocmdlog command

KAVB2527-E

An attempt to read the command-execution log file has failed.

Processing was canceled because an error occurred while the command execution log file was being read.

(S)

Cancels the output of the command execution log.

(O)

The command execution log file may be corrupted.

For details on how to check the status of the command execution log file and how to recover the file, see the chapter about troubleshooting in the Job Management Partner 1/Integrated Management - Manager Administration Guide.

If the command execution log file is normal, execute the data collection tool of JP1/IM, and then contact the system administrator.

KAVB2528-E

The date is invalid.(date-and-time)

The specified date or time has an error. Make sure that:

If the date has an error, check whether a date that does not exist in the calendar is specified.

If the time has an error, check whether an invalid value is specified for the hour, minute, or second.

(The valid values are 00-23 for the hour, 00-59 for the minute, and 00-59 for the second.)

(S)

Does not execute the command.

(O)

Specify an appropriate value in the date format (YYYYMMDDhhmmss), and then re-execute the command.

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 date earlier than the end date as the start date, and then re-execute the command.

KAVB2530-I

The jcocmdconv command started.

The jcocmdconv command has started.

(S)

Executes the command.

KAVB2531-I

The jcocmdconv command terminated. (return code = return-code)

The jcocmdconv command has ended.

(S)

The command has finished processing.

KAVB2532-I

The user cancelled the conversion of the command-execution log file.

The user has canceled processing of the jcocmdconv command.

(S)

Cancels command processing.

KAVB2534-E

The specified option option-name is invalid.

An invalid option was specified in the command line.

(S)

Cancels command processing.

(O)

Specify the correct options, and then re-execute the command.

KAVB2535-E

The number of arguments is invalid.

The option has invalid arguments.

(S)

Cancels command processing.

(O)

Specify the correct options, and then re-execute the command.

KAVB2536-E

The option option-name is specified more than once.

An option that should only specified once is specified more than once.

(S)

Cancels command processing.

(O)

Specify the correct options, and then re-execute the command.

KAVB2537-E

The value for the option option-name is not specified.

The value for the specified option is invalid.

(S)

Cancels command processing.

(O)

Specify the correct options, and then re-execute the command.

KAVB2538-E

The directory does not exist. (directory-path = directory-name)

The specified source or target directory does not exist.

(S)

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

Cancels command processing.

(O)

Specify a valid 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 the logical host does not exist.

(S)

Cancels command processing.

(O)

The common definition information for the logical host may be set up incorrectly. Check the settings of the logical host and, if necessary, set it up again.

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)

Cancels command processing.

(O)

Check the logical host name specified in the -h option.

KAVB2542-E

Superuser permissions are required to execute the command.

The execution user does not have Administrators permissions.

(S)

Cancels command processing.

(O)

Execute the command as a user who has Administrators permissions or root privileges.

KAVB2543-E

Command execution will now stop because memory is insufficient.

An attempt to allocate memory resulted in an error.

(S)

Cancels command processing.

(O)

Terminate other programs that are using memory, and then re-execute the command.

KAVB2544-E

Command execution will now stop because disk space is insufficient.

The destination directory has insufficient disk space.

(S)

Cancels command processing.

(O)

Free up some disk space, and then re-execute the command.

KAVB2545-E

The user does not have access permission for the file file-name.

The command cannot be executed because the user does not have access permission for the command execution log file.

(S)

Cancels command processing.

(O)

Make sure that the user has access permission for the command execution log file.

KAVB2546-E

The jcocmdconv command was interrupted.

The command was interrupted.

(S)

Cancels command processing.

(O)

Re-execute the command.

KAVB2547-E

Another jcocmdconv command is already running.

The jcocmdconv command was stopped because another jcocmdconv command is being executed on the same logical host.

(S)

Cancels command processing.

(O)

Check whether a jcocmdconv command is already running.

KAVB2548-I

The specified file file-name contains no data to be converted.

The specified execution log file does not contain any valid records.

(S)

Cancels command processing.

KAVB2549-E

The source file file-name could not be deleted.

The specified command execution log file formatted in the previous version could not be deleted after conversion.

(S)

Ends command processing without deleting the source file.

(O)

Make sure that the user has access permission for the command execution log file of the previous version.

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 a converted command execution log file already exists in the specified location.

(S)

Cancels command processing.

(O)

Delete the existing command execution log file from that 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 could not be performed because the old-format execution log of the command executed from the Execute Command window was not found.

(S)

Does not convert the execution log file for the command executed from the Execute Command window.

KAVB2552-W

The command-execution log file for the automatic action does not exist.

Conversion could not be performed because the command execution file for the automated action does not exist.

(S)

Does not convert the command execution file for the automated action.

KAVB2553-Q

Do you want to convert the command-execution log file? [Y/y or N/n] ->

This is a message confirming processing of the command execution log file.

(S)

Suspends command processing until the user enters a response.

(O)

Enter Y or y to continue processing. To stop processing, enter N or n.

KAVB2554-Q

Do you want to delete the old-format command-execution log file file-name? [Y/y or N/n] ->

This is a confirmation message asking the user to confirm deletion of the command execution log file.

(S)

Suspends command processing until the user enters a response.

(O)

Enter Y or y to delete the old-format command execution log file and continue processing. To continue processing without deleting the old-format command execution log file, enter N or n.

KAVB2555-W

An attempt to initialize the HNTR library has failed. Processing will continue without logging messages.

An attempt to initialize HNTRLib2 has failed.

(S)

Continues command processing without logging messages.

KAVB2556-W

An attempt to initialize an individual trace log has failed. Processing will continue without logging messages.

The individual trace log could not be initialized.

(S)

Continues command processing without logging messages.

KAVB2557-W

An attempt to initialize integrated and individual trace logs has failed. Processing will continue without logging messages.

HNTRLib2 and the individual trace logs could not be initialized.

(S)

Continues command processing without logging messages.

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)

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

The log directory could not be obtained from the common definition information.

(S)

Continues command processing without logging messages.

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.

The log directory could not be obtained from the common definition information.

(S)

Continues command processing without logging messages.

KAVB2563-E

An attempt to get user input has failed.

The user's response to a confirmation message could not be obtained from standard output.

(S)

Cancels command processing.

(O)

Re-execute the command. If the problem persists, contact the system administrator.

KAVB2564-E

An attempt to initialize the common definition information has failed.

The common definition information could not be initialized.

(S)

Cancels command processing.

(O)

Make sure that the product has been installed correctly. If the problem cannot be corrected, contact the system administrator.

KAVB2565-E

An error occurred during command processing.

One of the following errors occurred during command processing:

The common definitions could not be read.

The execution source file could not be opened or read.

The lck file used during command processing could not be created or deleted.

(S)

Cancels command processing.

(O)

Use the Jischk command to check if the command execution log file is corrupted. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KAVB2566-E

Execute the command from the administrator console.

This 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 the command as a user who has root privileges or JP1/Base administrator privileges.

(S)

Terminates command processing.

(O)

Re-execute the command as a user who has root privileges or JP1/Base administrator privileges.

KAVB2600-I

New [process-name] Process with PID:[process-ID] is created.

The process-name process has been 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 that was set as the limit that the product can process safely.

(S)

Rejects the command execution request.

(O)

Check the configuration based on the maximum number of hosts that one JP1/IM can manage, as described below:

When close is specified for the communication type in the event server settings file (conf) for JP1/Base on the manager host: 1,024 hosts

When other than close is specified for the communication type in the event server settings file (conf) for JP1/Base on the manager host: 100 hosts (in UNIX) or 62 hosts (in Windows)

However, note that the numbers of hosts described here are for the maximum configuration. The number of hosts that can be managed is restricted, depending on the system configuration and 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 exceeded the maximum that was set as the limit that the product can process safely. An automated action request will not be processed until the number of commands drops below the maximum set by the system.

(S)

Aborts the automated action request.

(O)

Use the jcocmdshow command to check the commands currently being executed, and then use the jcocmddel command to delete insignificant commands.

Make sure that the network connection to the host where the command was executed 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 processed by the process exceeded the maximum that was set as the limit that the product can process safely. A command execution request will not be processed until the number of commands drops below the maximum set by the system.

(S)

Aborts the command execution request.

(O)

Use the jcocmdshow command to check the commands currently being executed, and then use the jcocmddel command to delete insignificant commands.

Make sure that the network connection to the host where the command was executed is functioning.

KAVB2608-E

The process process-name with the pid process-ID terminated abnormally. (return code = return-code)

The process terminated abnormally because a system error occurred.

(S)

Terminates the command execution control abnormally if one of the following is indicated in process-name:

JCOCMDROUTER

JCOCMDEXE

JCOCMDCOM

Stops further command processing on each client if the following is indicated in process-name:

JCOCMDAPI

(O)

Check the following. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator:

Make sure that JP1/Base is installed normally.

Make sure that the operating system is running normally.

KAVB2609-I

The process process-name with the pid process-ID has started.

The process indicated in process-name has started.

KAVB2610-I

The process process-name with the pid process-ID finished normally.

The process indicated in process-name terminated normally.

KAVB2611-E

An attempt to create the process process-name has failed.

An attempt to create the process has failed.

(S)

Could not start the process due to a limitation on the system or an internal error.

(O)

Make sure that there are sufficient system resources. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KAVB2613-E

An attempt to allocate memory has failed. (process = process-name, pid = process-ID)

An attempt to allocate memory has failed.

(S)

Continues processing.

(O)

Terminate other programs 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 has failed.

(S)

Terminates command execution control.

(O)

In UNIX, check the following. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

Make sure that the message catalog file (Jcocmdmsg.cat) exists 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 has failed due to insufficient memory.

(S)

Does not execute the command.

(O)

Check the following. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

Make sure that there are sufficient memory and other system resources required for executing 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 has failed because the command did not exist or because the resources were insufficient.

(S)

Does not execute the command.

(O)

Check the following. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

Make sure that you have appropriate permission to execute the command.

KAVB2618-E

An internal error occurred while processing the results.

An error occurred during processing of the command results. This error occurs on a host that issues a command execution request.

(S)

Does not output the command results to the command execution log file.

(O)

Check the following. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

Make sure that the host that issued the command execution request has sufficient resources.

KAVB2619-E

An attempt to initialize the log has failed. (function name = function-name, error code = error-code)

An attempt to initialize the log output has failed during startup of the process due to either of the following reasons:

The common definition parameter was not found or was incorrect.

Too many processes were being executed simultaneously.

(S)

Does not output a log, but continues processing of command execution control.

(O)

Check the following. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

Use the jcocmdshow command to check the commands currently being executed, and then use the jcocmddel command to delete insignificant commands.

KAVB2620-E

An error occurred during startup of the process process-name. (internal-message)

An error occurred during startup of the service due to one of the following reasons:

The length of the JP1_HOSTNAME environment variable exceeded 256 characters.

The resources required for starting the process did not exist.

An internal error occurred during startup of the process.

(S)

Terminates the service abnormally.

(O)

Check the following. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

Make sure that the environment variable has been specified using 255 or fewer characters.

Make sure that there are sufficient memory and other system resources required for executing the command.

KAVB2621-E

An attempt to acquire the message from the message file has failed.

The message could not be acquired from the catalog file.

(S)

Does not output the message.

(O)

In UNIX, check the following. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

Make sure that the message catalog file (Jcocmdmsg.cat) exists under the /opt/jp1base/lib/nls directory.

KAVB2623-E

The command cannot be forwarded to the host host-name because the command length is 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 commands of that length.

(S)

Does not execute the command.

(O)

Check the version of JP1/Base on the host where the command is to be executed. 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 rejected a command execution request.

(S)

Does not execute the command.

(O)

Make sure that there are sufficient resources on the manager host. If you did not find any problems, execute the data collection tools of both JP1/Base and JP1/IM, and then contact the system administrator.

KAVB2627-E

The jcocmdconv command is accessing the command execution log file.

A jcocmdapi process was started during execution of the jcocmdconv command.

(S)

Stops the jcocmdapi process.

(O)

Check whether the jcocmdconv command is being executed. You cannot execute the jcocmdconv command while JP1/Base is active.

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 in length was received.

(S)

Does not execute the command.

(O)

Check the length of commands specified in the Execute Command window and commands invoked by automated actions.

KAVB2630-E

A request from a host without access permissions was rejected. (host-name-or-IP-address-of-the-requesting-host)

A request from a host without the required access permissions was received.

If reverse mapping is possible by converting the IP address of the requesting host to the host name, the host name is indicated in host-name-or-IP-address-of-the-requesting-host. If reverse mapping is not possible, the IP address of the host is indicated.

(S)

Cancels command processing.

(O)

Make sure that a higher-level host is specified in the configuration definition, and that the name of that host matches the name of the requesting host.

To receive requests from a host other than the higher-level host, specify the host name or IP address of the requesting host for ALT_CLIENT_HOSTS in the common definition.

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 for the label name failed.

(S)

During startup: Continues processing, assuming that the common definition for the label name is not defined.

During reloading: Continues processing with the definitions used before the reloading.

(O)

Make sure that:

The settings in the common definition information for the label name are correct.

Sufficient system resources and adequate memory are allocated.

If the problem cannot be corrected, use the data collection tool to collect data, and then contact the 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 definition.

(S)

During startup: Continues processing, assuming that 0 is specified for UPPER_ONLY in the common definition.

During reloading: Continues processing with the value used before the reloading.

(O)

Revise the specification of UPPER_ONLY in the common definition.

KAVB2633-W

An invalid host name is specified. (host = host-name)

An invalid host name was specified for ALT_CLIENT_HOSTS in the common definition.

(S)

During startup: Continues processing, assuming that ALT_CLIENT_HOSTS is not specified in the common definition.

During reloading: Continues processing with the definitions used before the reloading.

(O)

Make sure that:

The specified host name contains not more than 255 bytes.

An IP address is assigned to the host name in the settings for hosts, DNS, or jp1hosts2.

KAVB2634-W

The specified host (host-name) already exists.

The host name specified for ALT_CLIENT_HOSTS in the common definition is already in use.

(S)

During startup: Continues processing, assuming that ALT_CLIENT_HOSTS is not specified in the common definition.

During reloading: Continues processing with the definitions used before the reloading.

(O)

Revise the specification of ALT_CLIENT_HOSTS in the common definition.

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 definition exceeds the maximum.

(S)

During startup: Continues processing, assuming that ALT_CLIENT_HOSTS is not specified in the common definition.

During reloading: Continues processing with the definitions used before the reloading.

(O)

Revise the specification of ALT_CLIENT_HOSTS in the common definition.

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 an upper-host failed.

(S)

Continues processing. However, the system will reject any requests from the higher-level host.

(O)

Make sure that an IP address is assigned to the host name in the settings for hosts, DNS, or jp1hosts2.

KAVB2637-W

The IP address for the upper-host (host-name) could not be obtained.

The IP address information for the higher-level host could not be obtained. This error mostly occurs if memory is insufficient.

(S)

Continues processing. However, the system will reject any requests from the higher-level host.

(O)

Check whether there is sufficient memory in the system.

KAVB2638-W

An error occurred while the IP address information was being obtained.

An error occurred during an attempt to obtain the IP address information for the host name specified for ALT_CLIENT_HOSTS in the common definition. This error mostly occurs if memory is insufficient.

(S)

During startup: Continues processing, assuming that ALT_CLIENT_HOSTS is not specified in the common definition.

During reloading: Continues processing with the definitions used before the reloading.

(O)

Check whether there is sufficient memory in the system. Make sure that sufficient memory is available, and then execute the jbs_spmd_reload command.

2.10 Configuration management messages (KAVB3001 to KAVB3172)

Note

In addition to the messages in the following list, the system may output messages with message IDs, such as internal error messages.

KAVB3001-E

Fail to get conf directory path. jp1BsCnfGetStringValue fail.

The conf directory path could not be acquired from the common definition.

(S)

Terminates processing.

(O)

Make sure that the path of the conf directory for JP1/Base is defined in the common definition.

KAVB3002-E

Fail to get log directory path. jp1BsCnfGetStringValue fail.

The log directory path could not be acquired from the common definition.

(S)

Terminates processing.

(O)

Make sure that the path of the log directory for JP1/Base is defined in the common definition.

KAVB3003-E

HNTRLib Initialize fail. bslog NULL.

An attempt to initialize the message output has failed.

(S)

Does not output messages.

(O)

Make sure that the setup of JP1/Base terminated normally.

KAVB3004-E

HNTRLib Initialize fail.

An attempt to initialize the message output has failed.

(S)

Does not output messages.

(O)

Make sure that the setup of JP1/Base terminated normally.

KAVB3005-E

Fail to open message file.

An attempt to open the message file has failed.

(S)

Does not output messages.

(O)

In UNIX, make sure that the catalog file exists under the /opt/jp1base/lib/nls directory.

KAVB3006-E

Fail to load resource.

An attempt to read a message file has failed.

(S)

Does not output messages.

(O)

Make sure that the setup of JP1/Base terminated normally.

KAVB3007-E

Fail to load catalog file.

An attempt to read a message file has failed.

(S)

Does not output messages.

(O)

In UNIX, make sure that the message file (jbsrt.cat) exists under the /opt/jp1base/lib/nls directory, and that you have read permission.

KAVB3008-E

vsprintf error.

An error occurred during internal processing of the message output.

(S)

Does not output messages.

(O)

Make sure that there are sufficient system resources.

KAVB3010-I

Cannot move to the log directory.

An attempt to move to the log output directory has failed.

(S)

Does not move to the log directory.

KAVB3011-E

Failed to initialize JP1/IM communication infrastructure. Error Type = JBS_EJP1HOSTS

An attempt to initialize the communication infrastructure has failed. The jp1hosts data was invalid and could not be read.

(S)

Terminates processing.

(O)

Check and, if necessary, revise the jp1hosts value 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 has failed.

(S)

Aborts processing.

(O)

Make sure that the setup of JP1/Base completed normally.

KAVB3013-I

Failed to acquire the port number. The default port number is used.

The port number could not be acquired.

(S)

Starts at the default port.

(O)

Make sure that the port number for configuration management is defined in the services file.

KAVB3015-E

Failed to initialize JP1/IM communication infrastructure. Terminating.

An attempt to initialize communication has failed because the port was already used.

(S)

Terminates processing.

(O)

Make sure that the configuration management port has not been used yet.

If the IP binding method is selected as the communication protocol, make sure that a valid IP address is specified for the local host.

KAVB3016-E

Failed to create a thread communication to the process management. Terminating.

An attempt to create a thread for communication with process management has failed.

(S)

Terminates the configuration management.

(O)

Make sure that there is sufficient memory, and then re-execute the command.

KAVB3017-E

jbsspm_getfd function failed. Terminating

An attempt to create a communication file descriptor has failed.

(S)

Terminates processing.

(O)

Exit other programs, and then re-execute the command.

KAVB3018-I

jbsroute is running.

Configuration management has started.

(S)

Runs configuration management.

KAVB3023-I

Reload request was received.

A reload request was received from process management.

(S)

Starts reload processing.

KAVB3024-I

jbsroute terminate.

Configuration management will now end.

(S)

Terminates configuration management.

KAVB3025-E

Cannot get JP1_BIND_ADDR. jp1BsCnfGetStringValue = return-value-of-function

The value of JP1_BIND_ADDR in the common definition could not be acquired.

(S)

Assumes ANY for the binding method.

(O)

Make sure that the common definition contains JP1_BIND_ADDR.

KAVB3031-I

There is no definition of conf directory path for JP1/IM - Console.

The definition of a conf directory for JP1/IM - Manager could not be acquired.

(S)

Starts as JP1/Base.

(O)

Ignore this message for a machine on which only JP1/Base is installed.

KAVB3032-I

There is not JP1/IM - Console product Information.

The product type for JP1/IM - Manager (JP1/IM - Central Console) cannot be acquired.

This message always appears for a machine on which only JP1/Base is installed.

(S)

Starts as JP1/Base.

(O)

Ignore this message for a machine on which only JP1/Base is installed.

KAVB3033-I

JP1/IM - Central Console

JP1/IM - Central Console is installed.

(S)

Lets configuration management run as JP1/IM - Central Console.

KAVB3034-I

JP1/IM - Satellite Console

JP1/IM - Satellite Console is installed.

(S)

Lets configuration management run as JP1/IM - Satellite Console.

KAVB3035-I

JP1/Base

JP1/Base is installed.

(S)

Lets configuration management run as JP1/Base.

KAVB3049-E

Failed to create communication data. jbsroute_make_rtdata Error Code = error-code. error-code-description

An attempt to create communication data has 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-description

An attempt to send communication data has failed.

(S)

Continues processing.

(O)

Check the configuration definition for a lower-level host that cannot communicate.

KAVB3051-E

Received configuration distribution request from JP1/Base

A definition distribution request was received from JP1/Base. A machine where only JP1/Base is installed cannot distribute definitions.

(S)

Cancels definition distribution.

(O)

Check and, if necessary, revise the configuration definition file so that a lower-level host is not defined in the machine where only JP1/Base is installed.

KAVB3052-E

JP1/IM - Central Console received configuration distribution request from JP1/IM - Satellite Console.

In the configuration definition, JP1/IM - Central Console is defined under JP1/IM - Satellite Console.

(S)

Does not distribute the definition to the host.

(O)

Correct the configuration definition file so that JP1/IM - Central Console is not defined under JP1/IM - Satellite Console.

KAVB3053-E

JP1/Base defines lower-level hosts.

In the configuration definition, lower-level hosts are defined for JP1/Base.

(S)

Does not distribute the definition to the hosts.

(O)

Make sure that:

Correct the configuration definition file so that lower-level hosts are not defined for JP1/Base.

If this message appears for a logical host, check whether the logical host has been set up. If it has not, use either of 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-description

The function for acquiring the lower-level host in the definition file has failed. This error most likely occurs when memory is insufficient.

(S)

Cannot distribute definitions on the host.

(O)

Make sure that there is sufficient memory.

KAVB3055-E

Wrong attempt to distribute the configuration definition to the highest-level host from other host.

Another definition file was sent from another host to the host defined as the highest-level host.

(S)

Cannot distribute definitions to the host.

(O)

No other hosts can distribute configuration definitions to the host defined as the highest-level host. Delete the configuration information from the highest-level host, and then execute the definition distribution command.

KAVB3056-E

Failed to get upper-level host. jbsroute_get_parent_host Error Code = error-code. error-code-description

The higher-level host could not be acquired.

(S)

Cannot distribute definitions.

(O)

Make sure that there is sufficient memory.

KAVB3057-E

Failed to get lower-level host. jbsroute_get_child_host Error Code = error-code. error-code-description

The lower-level host could not be acquired.

(S)

Cannot distribute definitions.

(O)

Make sure that there is sufficient memory.

KAVB3059-E

Failed to write data to configuration information file. jbsroute_write_rtdata Error Code = error-code. error-code-description

An attempt to write to the configuration definition file has failed.

(S)

Cannot distribute definitions.

(O)

Make sure that you have write permission for the conf/route/ directory.

KAVB3060-E

Failed to send communication data. jbsroute_send_rtdata_hosts Error Code = error-code. error-code-description

An attempt to send communication data has failed.

(S)

Cannot distribute definitions to the destination host.

(O)

Make sure that JP1/Base is running on the connected host. Also make sure that communication is possible from that host.

KAVB3073-E

Failed to get lower-level host information. jbsrt_getunderhost Error Code = error-code. error-code-description

The lower-level host could not be acquired.

(S)

Terminates the configuration management command.

(O)

Make sure that there is sufficient memory.

KAVB3074-E

Failed to delete configuration information file. jbsroute_del_rtdata Error Code = error-code. error-code-description

The configuration definition file could not be deleted.

(S)

Terminates the jbsrt_distrib command.

(O)

Make sure that you have write permission for the conf/route/ directory.

KAVB3078-E

Failed to communication initialization. jbsroute_send_rtdata_init Error Code = error-code. error-code-description

An attempt to initialize communication has failed.

(S)

Terminates the jbsrt_distrib or jbsrt_sync command.

(O)

To correct the cause of the error, check the environment to make sure that:

The network is in the normal status.

Both the local host and the server use the same IP address version (IPv4 or IPv6).

JP1/Base is running on the server.

If the problem cannot be corrected, use the data collection tool to collect data for the local host and the server, and then contact the system administrator.

For details about how to check the IP address version (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the Job Management Partner 1/Base User's Guide.

KAVB3079-E

Failed to receive communication data. jbsroute_recv_rtdata Error Code = error-code. error-code-description

An attempt to receive communication data has failed.

(S)

Terminates the jbsrt_distrib or jbsrt_sync command.

(O)

Make sure that no error occurred in the connected host.

KAVB3080-E

Failed to open the definition file.

An attempt to open the definition file has failed.

(S)

Terminates the jbsrt_distrib command.

(O)

Make sure that the conf/route/directory contains the configuration definition file.

Also make sure that you have read permissions for the configuration definition file.

KAVB3081-E

Memory allocation failed.

Memory could not be allocated.

(S)

Lets the configuration management continue processing, and terminates the command abnormally.

(O)

Make sure that there is sufficient memory.

KAVB3082-E

A line with more than two entries exists.

The definition file contains multiple instances of the same host name.

(S)

Terminates the jbsrt_distrib command.

(O)

Make sure that the same host is not defined more than once in the configuration definition file.

KAVB3083-E

No entries in a line.

The definition file contains no host name.

(S)

Terminates the jbsrt_distrib command.

(O)

Check the configuration definition file.

KAVB3084-E

Length of host name exceeds 256 characters. host-name

The host name in the definition file contains more than 255 characters.

(S)

Terminates the jbsrt_distrib command.

(O)

Check and, if necessary, revise the configuration definition file so that the host name contains no more 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 indicated management host name is correctly enclosed in square brackets ([]).

KAVB3086-E

The host is specified more than once. host-name

The same host is defined more than once in the definition file.

(S)

Terminates the jbsrt_distrib command.

(O)

Check and, if necessary, revise the configuration definition file so that the same host is not defined more than once.

KAVB3087-E

Managed host does not exist. host-name

A management host without a host subject to management is defined.

(S)

Terminates the jbsrt_distrib command.

(O)

Check and, if necessary, revise the configuration definition file, and then enter a host subject to management for the management host.

KAVB3088-E

The host is in a loop status. host-name

The definition file contains a definition of a loop layer.

(S)

Terminates the jbsrt_distrib command.

(O)

Check and, if necessary, revise the configuration definition file to correct the system configuration that contains a loop.

KAVB3089-E

The highest-level host is different. host-name host-name

The definition file contains two or more highest-level hosts.

(S)

Terminates the jbsrt_distrib command.

(O)

Check and, if necessary, revise the configuration definition file so that it contains only one highest-level host.

KAVB3090-E

Cannot get conf path from common definition.

The conf directory path could not be acquired from the common definition.

(S)

Terminates the configuration management or command.

(O)

Make sure that the path of the conf directory for JP1/Base is defined in the common definition.

KAVB3091-E

HNTRLib could not be initialized.

An attempt to initialize the message output has failed.

(S)

Does not output messages.

(O)

Make sure that the setup of JP1/Base terminated normally.

KAVB3092-E

HNTRLib could not be initialized.

An attempt to initialize the message output has failed.

(S)

Does not output messages.

(O)

Make sure that the setup of JP1/Base terminated normally.

KAVB3093-E

No execution authorization.

A user who does not have operator privileges attempted to perform an operation. In Windows, the user was not a member of the Administrators group. In UNIX, the user did not have root privileges or JP1/Base administrator privileges.

(S)

Cannot execute processing.

(O)

Try again as a user who has operator privileges.

KAVB3094-I

Failed to acquire the port number. The default port number is used.

The port number could not be acquired.

(S)

Starts at the default port.

(O)

Make sure that the port number for the configuration management is defined in the services file.

KAVB3095-E

Failed to load definition file.

An attempt to read the definition file has failed.

(S)

Does not execute the jbsrt_distrib command.

(O)

Make sure that the configuration definition file is 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 the lower-level host was being acquired from the definition file.

(S)

Does not execute the configuration management command.

(O)

Make sure that there is sufficient memory.

KAVB3098-E

JP1/Base defines lower-level hosts.

An attempt to distribute the configuration containing definitions of lower-level hosts failed because JP1/IM - Manager was not installed.

(S)

Does not execute the jbsrt_distrib command.

(O)

To distribute the configuration, install JP1/IM - Manager.

If this message appears for a logical host, set up the logical host for JP1/IM - Manager.

KAVB3099-E

Failed to get the definition data.

An I/O error occurred while the configuration definition file was being read.

(S)

Does not execute the configuration management command.

(O)

Make sure that you have write permission for the conf/route/ directory.

KAVB3100-E

Failed to create communication data.

An attempt to create communication data has failed. This error most likely occurs when memory is insufficient.

(S)

Does not execute the configuration management command.

(O)

Make sure that there is sufficient memory.

KAVB3101-E

Failed to connect to the server.

An attempt to connect to the server has failed.

(S)

Does not execute the configuration management command.

(O)

To correct the cause of the error, check the environment to make sure that:

The network is in the normal status.

Both the local host and the server use the same IP address version (IPv4 or IPv6).

JP1/Base is running on the server.

If the problem cannot be corrected, use the data collection tool to collect data for the local host and the server, and then contact the system administrator.

For details about how to check the IP address version (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the Job Management Partner 1/Base User's Guide.

KAVB3102-E

Failed to send the data. Error Code = error-code. error-code-description

An attempt to send data to the configuration management server has failed.

(S)

Terminates the jbsrt_distrib or jbsrt_sync command.

(O)

Make sure that configuration management is running and that there is sufficient memory.

KAVB3103-E

Failed to receive the data.

An attempt to receive data from the configuration management server has failed.

(S)

Causes an error in the jbsrt_distrib or jbsrt_sync command.

(O)

Make sure that:

JP1/Base is restarted after JP1/IM is installed.

There is sufficient memory.

You have read and write permissions 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 for some hosts could not be deleted.

(O)

Use the jbsrt_del command to delete the configuration information for the displayed host and lower-level hosts separately.

KAVB3105-E

The server is processing.

An operation such as definition distribution was attempted during processing of the configuration management server.

(S)

Causes an error in the jbsrt_distrib or jbsrt_sync command.

(O)

Wait for a while, and then re-execute the command.

KAVB3106-I

Deleted the current configuration definition

The jbsrt_distrib command deleted configuration information.

(S)

Continues processing.

KAVB3107-E

Cannot set configuration in the host. host-name

A host was found for which configuration information could not be set during confirmation of the configuration definition.

(S)

Causes an error in the jbsrt_distrib command.

(O)

Make sure of the following for the host where the error occurred:

JP1/Base is running. (You can check this by using the jbs_spmd_status command.)

The configuration management port (default: 20237/tcp) is running. (You can check this by using the netstat command.)

The configuration management port (default: 20237/tcp) is not filtered by a firewall.

The name of the host that caused the error can be resolved by its higher-level host. (You can check this by using the jp1ping command.)

The correct IP address you intended is obtained by name resolution.

The host that caused the error was not defined as the highest-level host. (You can check this by using the jbsrt_get command.) If this host is defined as the highest-level host in any configuration information, use the jbsrt_del command to delete that configuration information.

There is sufficient memory.

You have read and write permissions for the conf/route/ directory.

If you did not find any problems, perform the following procedure to check the host on which the error occurred:

Execute the jbsrt_get command.

Check whether one of the following occurred:

- The KAVB3162-E message appeared.

- The jbsrt_get command terminated abnormally.

- The local host name appeared in Upper host or Lower host.

- A host name other than that of the local host appeared in Local host.

- The host name is garbled.

If any of the above problems occurred, use the following procedure for recovery:

1. Use the jbsrt_del command to delete the configuration definition.

2. From the manager host, use the jbsrt_distrib command to re-distribute the configuration definition.

KAVB3108-E

Failed in definition distribution. Cannot set configuration information in the host. host-name

A host was found for which configuration information could not be distributed during distribution of the configuration definition.

(O)

Re-execute the jbsrt_distrib command. This distributes the definition without deleting the configuration information. If you can confirm that the definition has been distributed to the host that previously caused the error and its lower-level hosts, this means that the configuration definition has been distributed to the entire system.

KAVB3109-I

Succeed the jbsrt_distrib command

The definition distribution command ended successfully.

(S)

Terminates the jbsrt_distrib command normally.

KAVB3110-E

Definition data is not found.

Configuration information is not set up.

(S)

Does not execute the jbsrt_sync command.

(O)

Execute the jbsrt_distrib command, and then execute the jbsrt_sync command.

If the jbsrt_sync command has been executed, make sure that the conf/route/ directory exists and that you have read and write permissions.

If JP1/Base is running in a cluster system, make sure that the defined conf directory exists and that you have read and write permissions.

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 where the error occurred.

(O)

Make sure that JP1/Base is running on the host where the error occurred.

If JP1/Base is running, perform the following procedure:

Execute the jbsrt_get command.

Check whether one of the following occurred:

- The KAVB3162-E message appeared.

- The jbsrt_get command terminated abnormally.

- The local host name appeared in Upper host or Lower host.

- A host name other than the local host appeared in Local host.

- The host name is garbled.

If any of the above problems occurred, use the following procedure for recovery:

1. Use the jbsrt_del command to delete the configuration definition.

2. From the manager host, use the jbsrt_distrib command to re-distribute the configuration definition.

KAVB3112-I

Succeed the jbsrt_sync command

The synchronization command ended successfully.

(S)

Terminates the jbsrt_sync command normally.

KAVB3113-I

Definition does not exist.

Configuration information is not set up.

(S)

Terminates the jbsrt_get or jbsrt_del command.

(O)

Execute the jbsrt_distrib command, and then re-execute the command.

If the jbsrt_distrib command has been executed, make sure that the conf/route/ directory exists and that you have read and write permissions.

If JP1/Base is running in a cluster system, make sure that the defined conf directory exists and that you have read and write permissions.

KAVB3114-E

Cannot access definition.

An attempt to read the configuration information has failed.

(S)

Terminates the jbsrt_get, jbsrt_del command.

(O)

Make sure that you have write permission for the conf/route/ directory.

KAVB3115-I

Deleted the definition data.

The jbsrt_del command ended successfully.

(S)

Terminates the jbsrt_del command.

KAVB3116-I

Get the logical host name from the environment variable of JP1_HOSTNAME

The logical host name was acquired from the JP1_HOSTNAME environment variable.

(S)

Starts as a logical host with the name acquired from the JP1_HOSTNAME environment variable.

(O)

To start the host as a physical host, cancel the specification of JP1_HOSTNAME environment variable.

KAVB3118-E

jbsrt_distrib command is time out.

The jbsrt_distrib command timed out.

(S)

Terminates the jbsrt_distrib command, with an error.

(O)

Check the following:

Make sure that no error occurred in the lower-level host.

If definition distribution takes too long time, the jbsrt_distrib command times out. Check and, if necessary, revise the system configuration.

KAVB3119-E

jbsrt_sync command is time out.

The jbsrt_sync command timed out.

(S)

Terminates the jbsrt_sync command, with an error.

(O)

Check the following:

Make sure that no error occurred in the lower-level host.

If synchronization processing takes too long time, the jbsrt_sync command times out. Check and, if necessary, revise the system configuration.

KAVB3120-E

Failed to initialize JP1/IM communication infrastructure. Error Type = JBS_EJP1HOSTS

An attempt to initialize the communication infrastructure has failed. The jp1hosts data was invalid and could not be read.

(S)

Terminates processing.

(O)

Check and, if necessary, revise the jp1hosts value in the common definition.

KAVB3121-E

Failed to initialize JP1/IM communication infrastructure. jp1BsCommInit Error Code = error-code

An attempt to initialize the communication infrastructure has failed.

(S)

Terminates the configuration management command.

(O)

Make sure that the setup of JP1/Base completed normally.

Collect data, and then contact the system administrator.

KAVB3123-E

Too many lower-level host. The maximum number is maximum-number-of-lower-level hosts

The number of lower-level hosts specified in the configuration definition exceeds the limit.

(S)

Does not set configuration information for the indicated hosts.

(O)

Make sure that no more than six lower-level hosts are defined directly under JP1/IM - Central Console 5 Node, and no more than 11 lower-level hosts are defined directly under JP1/IM - Central Console 10 Node.

KAVB3124-E

Cannot get conf path from common definition with specified logical host name.

The conf path of the logical host name could not be acquired from the common definition.

(S)

Terminates the configuration management or the command.

(O)

Make sure that the specified logical host name is correct and that the conf directory for JP1/Base has been defined in the common definition for 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)

Make sure that there is sufficient memory.

KAVB3134-E

Failed to get install path.

The JP1/Base installation path could not be acquired in Windows.

(S)

Does not execute the jevreload command.

(O)

Make sure that JP1/Base is installed and set up correctly.

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

KAVB3135-E

Failed to create jevreload process.

The jevreload command could not be executed.

(S)

Does not execute the jevreload command.

(O)

Make sure that there is sufficient memory.

KAVB3148-E

An attempt to use the jp1gethostname function has failed.

A failure occurred during communication initialization processing.

(S)

Cancels processing.

(O)

For a physical host, make sure that the local host name is set correctly. For a logical host, make sure that the logical host name is set correctly.

KAVB3149-E

An attempt to use the jp1gethostbyname (hostname: host-name) function has failed.

A failure occurred during communication initialization processing.

(S)

Cancels processing.

(O)

Make sure that jp1ping communication is possible for the host name. For the DNS operation, make sure that a network error has not occurred.

KAVB3150-E

An attempt to create a socket has failed.

A communication socket could not be generated.

(S)

Cancels processing.

(O)

Make sure that there is sufficient system resources.

KAVB3151-E

An attempt to set socket options has failed.

An attempt to set socket options has failed.

(S)

Cancels processing.

(O)

Make sure that there is sufficient system resources.

KAVB3152-W

An attempt to bind has failed (IP address: IP-address).

A failure occurred during communication initialization processing.

(S)

Continues processing.

(O)

Make sure that the indicated IP address is assigned correctly to the network card.

KAVB3153-W

An attempt to listen has failed (IP address: IP-address).

A failure occurred during communication initialization processing.

(S)

Continues processing until the system retries communication wait processing at all the IP addresses defined in the local host.

(O)

Make sure that the indicated IP address is assigned correctly to the network card. Also make sure that the communication environment is set up.

KAVB3154-I

Bind and listen attempt has succeeded (IP address: IP-address).

The communication environment was initialized successfully.

(S)

Continues processing.

KAVB3155-E

No appropriate bind and listen IP address was found.

A failure occurred during communication initialization processing.

(S)

Cancels processing.

(O)

Set up the communication environment, and then re-execute the command.

KAVB3156-W

An attempt to connect has failed (hostname: host-name, IP address: IP-address).

A failure occurred during communication initialization processing.

(S)

Continues processing until the system retries connection to all the IP addresses defined in the host name.

(O)

To correct the cause of the error, check the environment to make sure that:

The network is in the normal status.

Both the local host and the server use the same IP address version (IPv4 or IPv6).

JP1/Base is running on the server.

If the problem cannot be corrected, use the data collection tool to collect data for the local host and the server, and then contact the system administrator.

For details about how to check the IP address version (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the Job Management Partner 1/Base User's Guide.

KAVB3157-I

An attempt to connect has succeeded (hostname: host-name, IP address: IP-address).

Communication is successful.

(S)

Continues processing.

KAVB3158-E

No appropriate bind and connect IP address was found. (hostname: host-name)

A failure occurred during communication initialization processing.

(S)

Cancels processing.

(O)

Review the hosts information of the OS and either the DNS settings or the jp1hosts2 information to make sure that an IP address is assigned to the host name of the connection destination host. In addition, assign at least one IP address that is the same version (IPv4 or IPv6) as the IP address assigned to the connection destination host.

KAVB3159-E

Please set the logical host name to within 255 characters.

The logical host name contains more than 255 characters.

(S)

Cancels processing.

(O)

Specify the logical host name using no more than 255 characters.

KAVB3160-W

Part of TCP/IP wait response processing has failed, but jbsroute processing will continue.

Part of TCP/IP wait response processing has failed.

(S)

Continues processing.

(O)

Some IP addresses may have not been set correctly. Although the JP1/Base configuration management continues processing in the fallback mode, part of communication processing will not be performed normally. Correct the problem, and the restart.

KAVB3161-E

An error occurred in system call. : maintenance-information

An error occurred during an OS system call.

(S)

Cancels processing.

(O)

Make sure of the following. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

The system has sufficient resources.

The operating system is running normally.

The communication environment is used normally.

KAVB3162-E

The configuration information file is invalid.

The configuration definition file cannot be read because it is invalid.

(S)

Continues processing of configuration management, and terminates the jbsrt_distrib, jbsrt_sync, and jbsrt_get commands.

(O)

Perform the following procedures for recovery:

On the host for which the message was output, execute the jbsrt_del command to delete the configuration definition.

From the highest level host, execute the jbsrt_distrib command to re-distribute the configuration definition.

KAVB3163-E

Execute the command from the administrator console.

This command must be executed on the administrator console.

(S)

Terminates command processing.

(O)

Execute the command on the administrator console.

KAVB3164-E

A request from a host without access permissions was rejected. (host-name-or-IP-address-of-the-requesting-host)

A request from a host without the required access permissions was received.

If reverse mapping is possible by converting the IP address of the requesting host to the host name, the host name is indicated in host-name-or-IP-address-of-the-requesting-host. If reverse mapping is not possible, the IP address of the host is indicated.

(S)

Cancels command processing.

(O)

Make sure that the name of the requesting host matches the name of the higher-level host specified in the configuration definition.

To receive requests from a host other than the higher-level host, specify the host name or IP address of the requesting host for ALT_CLIENT_HOSTS in the common definition.

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 for the label name has failed.

(S)

During startup: Continues processing, assuming that the common definition for the label name is not defined.

During reloading: Continues processing with the definitions used before the reloading.

(O)

Make sure that:

The settings in the common definition information for the label name are correct.

Sufficient system resources and adequate memory are allocated.

If the problem cannot be corrected, use the data collection tool to collect data, and then contact the 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 definition.

(S)

During startup: Continues processing, assuming that 0 is specified for UPPER_ONLY in the common definition.

During reloading: Continues processing with the value used before the reloading.

(O)

Revise the specification of UPPER_ONLY in the common definition.

KAVB3167-W

An invalid host name is specified. (host = host-name)

An invalid host name was specified for ALT_CLIENT_HOSTS in the common definition.

(S)

During startup: Continues processing, assuming that ALT_CLIENT_HOSTS is not specified in the common definition.

During reloading: Continues processing with the definitions used before the reloading.

(O)

Make sure that:

The specified host name contains not more than 255 bytes.

An IP address is assigned to the host name in the settings for hosts, DNS, or jp1hosts2.

KAVB3168-W

The specified host (host-name) already exists.

The host name specified for ALT_CLIENT_HOSTS in the common definition is already in use.

(S)

During startup: Continues processing, assuming that ALT_CLIENT_HOSTS is not specified in the common definition.

During reloading: Continues processing with the definitions used before the reloading.

(O)

Revise the specification 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 definition exceeds the maximum.

(S)

During startup: Continues processing, assuming that ALT_CLIENT_HOSTS is not specified in the common definition.

During reloading: Continues processing with the definitions used before the reloading.

(O)

Revise the number of specified hosts.

KAVB3170-W

An attempt to resolve the name of an upper-host (host-name) failed. (code = error-number)

(S)

Continues processing. However, the system will reject any requests from the higher-level host.

(O)

Make sure that an IP address is assigned to the higher-level host name in the settings for hosts, DNS, or jp1hosts2.

KAVB3171-W

The IP address for the upper-host (host-name) could not be obtained.

The IP address information for the higher-level host could not be obtained. This error mostly occurs if memory is insufficient.

(S)

Continues processing. However, the system will reject any requests from the higher-level host.

(O)

Check whether there is sufficient memory in the system.

KAVB3172-W

An error occurred while the IP address information was being obtained.

An error occurred during an attempt to obtain the IP address information for the host name specified for ALT_CLIENT_HOSTS in the common definition. This error mostly occurs if memory is insufficient.

(S)

During startup: Continues processing, assuming that ALT_CLIENT_HOSTS is not specified in the common definition.

During reloading: Continues processing with the definitions used before the reloading.

(O)

Check whether there is sufficient memory in the system. Make sure that sufficient memory is available, and then execute the jbs_spmd_reload command.

2.11 Process management messages (KAVB3501 to KAVB3914)

Notes

In addition to the messages in the following list, the system may output messages with message IDs, such as internal error messages.

For details on process management messages when using JP1/AJS, see the manuals Job Management Partner 1/Automatic Job Management System 2 Messages, Job Management Partner 1/Automatic Job Management System 3 Messages 1, and Job Management Partner 1/Automatic Job Management System 3 Messages 2.

KAVB3501-E

An attempt to open the message file has failed.

An attempt to open the message file has failed.

(S)

Terminates process management.

(O)

In Windows:

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

In UNIX:

The probable causes are as follows. Check the environment.

The user may not have read permission for the files under /opt/jp1base/lib/nls. Grant the user read permission.

The maximum number of files that can be opened in the system may have been reached. Check and, if necessary, revise the kernel parameter.

A temporary memory shortage may have occurred. Re-execute the command, or terminate unnecessary processes.

The directories or files may have been deleted. Re-install them.

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

KAVB3502-E

An attempt to read the message file has failed.

An attempt to read a message file has failed.

(S)

Does not output messages.

(O)

Make sure that the setup of JP1/Base terminated normally.

KAVB3503-E

An attempt to read the message file has failed.

An attempt to read a message file has failed.

(S)

Does not output messages.

(O)

Make sure that the message file (jbsspm.cat) exists under the /opt/jp1base/lib/nls directory, and that you have read permission for it.

KAVB3504-E

An error occurred in internal processing to output a message.

An error occurred during internal processing of the message output.

(S)

Does not output messages.

(O)

Make sure that there are sufficient system resources.

KAVB3516-E

An attempt to start the process management has failed. (errno = request-code)

Process management could not start.

(S)

Terminates process management.

(O)

Make sure that the product has been installed correctly.

KAVB3552-E

JP1_BASE management-target-process-name has timed out.

The request has timed out. management-target-process-name is the name of a process that makes up a component managed by the process management.

(S)

Continues processing.

(O)

For a reload request, increase the timeout value, and then re-execute the request. For other requests, wait a while, and then re-execute the request. If the same phenomenon recurs after the re-execution, use the data collection tool to collect data, and then contact the system administrator.

KAVB3553-E

SIGKILL was sent to management-target-process-name of JP1_BASE, but termination could not be detected.

Although the system sent SIGKILL, it cannot detect termination. management-target-process-name is the name of a process that makes up a component managed by the process management.

(S)

Terminates the process management.

(O)

Make sure that the process indicated by management-target-process-name is not running. If it is running, stop it manually.

KAVB3554-I

A JP1_BASE reload request has finished.

The reload request has finished.

(S)

Continues processing.

KAVB3564-I

jxx_spmd: JP1_BASE will now start all inactive processes.

The system starts all the inactive management-target processes.

(S)

Continues processing.

KAVB3574-I

jbs_spmd_reload: A reload request will now be sent to all running processes of JP1_BASE.

The system sends a reload request to all the active management-target processes.

(S)

Continues processing.

KAVB3577-I

jbs_spmd_stop: A stop request will now be sent to all processes of JP1_BASE.

The system sends a stop request to all the management-target processes.

(S)

Continues processing.

KAVB3578-I

JP1_BASE has ended.

The system terminates the process management.

(S)

Terminates the process management.

KAVB3586-I

JP1_BASE has terminated.

The system terminates the process management.

(S)

Terminates the process management.

KAVB3597-I

jbs_spmd_stop -kill: A forced stop (kill) will be performed on all processes of JP1_BASE.

The system forcibly stops all the management-target processes.

(S)

Continues processing.

KAVB3599-E

main_loop: An invalid request was received for Service Control Manager. (event ID = request-type)

The system received an invalid request.

(S)

Continues processing.

(O)

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

KAVB3602-I

JP1_BASE received a startup report from management-target-process-name.

The system received a startup completion notification. management-target-process-name is the name of a process that makes up a component managed by the process management.

(S)

Continues processing.

KAVB3603-I

All processes of JP1_BASE are running.

All the management-target processes have started.

(S)

Continues processing.

KAVB3604-I

JP1_BASE startup has finished.

The service startup has finished.

(S)

Continues processing.

KAVB3605-I

JP1_BASE completed to send the start up request to the managed-process-name.

Restart of the managed process that had terminated abnormally was completed. managed-process-name indicates the name of one of the processes that make up the component managed by the process manager.

(S)

Continues processing.

KAVB3608-I

JP1_BASE received a reload-completed notification from management-target-process-name.

The system received a reload completion notification from the management-target process. management-target-process-name is the name of a process that makes up a component managed by the process management.

(S)

Continues processing.

KAVB3609-I

A JP1_BASE reload request has finished.

The management-target process has completed reloading.

(S)

Continues processing.

KAVB3610-I

JP1_BASE received an termination notification from management-target-process-name.

The system received a termination notification from the management-target process. management-target-process-name is the name of a process that makes up a component managed by the process management.

(S)

Continues processing.

KAVB3612-I

A stop request will now be sent to all processes of JP1_BASE.

The system sends a stop request to all the management-target processes.

(S)

Continues processing.

KAVB3613-W

A JP1_BASE timeout occurred in management-target-process-name. Processing continues.

A startup timeout occurred in the management-target process. management-target-process-name is the name of a process that makes up a component managed by the process management.

(S)

Continues processing.

(O)

Wait a while. If the startup of the management-target process does not finish and the service does not start, use jbs_spmd_stop -kill to forcibly stop the process, and then restart it.

KAVB3614-E

Process management will now stop because an invalid JP1_BASE status occurred.

The system stops the process management since it is in the invalid status.

(S)

Terminates the process management.

(O)

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

KAVB3616-I

Restart of the JP1_BASE management-target-process-name has finished.

The restart of the process to be managed that ended abnormally has finished. management-target-process-name is the name of a process that makes up a component managed by the process management.

(S)

Continues processing.

KAVB3617-W

An error occurred during initialization of the operation log. (function-name, code = error-number)

An error occurred during initialization of the operation log.

(S)

Continues processing.

KAVB3619-I

JP1_BASE send the reload request to the management-target-process-name.

The system sends a reload request to active management-target processes. The name indicated by management-target-process-name is the name of a process that makes up a component managed by the process management.

(S)

Continues processing.

KAVB3620-E

The user does not have permission to execute the command command-name.

A user who does not have operator privileges attempted to execute the command. In Windows, the user was not a member of the Administrators group. In UNIX, the user did not have root privileges or JP1/Base administrator privileges.

(S)

Cannot execute the command.

(O)

Execute the command as a user who has operator privileges.

KAVB3621-E

A fork system call failed during initialization: JP1_BASE

The system failed to execute a fork system call in the background when process management started.

(S)

Terminates the process management.

(O)

Make sure that system memory is sufficient. Also check that the OS is operating normally.

KAVB3623-E

The setsid function failed. (error-description)

The setsid system call failed.

(S)

Terminates the process management.

(O)

Make sure that system memory is sufficient. Also check that the OS is operating normally.

KAVB3624-E

An attempt to create a process management table has failed.

The system failed to create the process management table.

(S)

Terminates the process management command.

(O)

Make sure that system memory is sufficient and the product has been installed correctly. Check also whether the preset values in the extended startup process definition file (jp1bs_service_0700.conf) are correct. In addition, check whether there is any process to be managed by the process management that has not ended normally.

Delete the extended startup process definition file, and then start the process manager.

KAVB3625-E

An internal error occurred. Execution Command names differ. execution-command-name

The execution command names are inconsistent.

(S)

Terminates the process management.

(O)

Check the execution command names. If you change their names, they cannot be executed properly.

KAVB3626-E

An attempt to create a lock file has failed. lock-file-path-error-description

An attempt to create a lock file has failed.

(S)

Terminates the process management command.

(O)

Check that the conf directory exists or that you have the read permission and the write permission. If you are using a cluster system, check that the defined conf directory exists and that you have the required read/write permissions.

KAVB3627-I

JP1_BASE is already running.

The service has been started twice.

(S)

Terminates the process management command.

KAVB3631-E

build_proc_table : The return value NULL was returned to the getfield function. set-value

An entry in the extended startup process definition file (jp1bs_service_0700.conf) has not been set correctly.

(S)

Terminates the process management.

(O)

Make sure that the relevant entry of the extended startup process definition file has been set correctly.

KAVB3642-E

An internal error occurred. Component names differ. JP1_BASE

The component names do not match.

(S)

Terminates the process management.

(O)

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

KAVB3643-E

An attempt to open the environment definition file file-name has failed.

The system could not open the environment definition file.

(S)

Terminates the process management.

(O)

Check that the product is correctly installed.

KAVB3644-E

An attempt to expand the environment variables has failed.

The system failed to read environment variables from jp1bs_env.conf.

(S)

Terminates the process management.

(O)

Make sure that system memory is sufficient.

KAVB3645-I

The logical hostname for process management is logical-host-name.

The process management has started in a logical host.

(S)

Continues processing.

KAVB3646-I

The option-name option is specified.

The process management starts with options.

(S)

Continues processing.

KAVB3647-E

The expiration of the time limit. JP1_BASE

The time limit of the JP1/Base trial version has expired.

(S)

Continues processing.

KAVB3649-E

The environment variable of JP1_HOSTNAME is empty.

The JP1_HOSTNAME environment variable is not set correctly.

(S)

Terminates the process management command.

(O)

Set a correct logical host name in the JP1_HOSTNAME environment variable or delete the JP1_HOSTNAME environment variable.

KAVB3651-I

Startup processing for JP1_BASE has started.

The process management starts the management-target process.

(S)

The process management starts the management-target process.

KAVB3652-E

A timeout occurred during the wait for a response. (timeout period = timeout-in-second seconds)

A timeout occurred during the wait for a response.

(S)

Terminates the process management command.

(O)

Change a timeout value, and then re-execute the command.

KAVB3653-E

An attempt to send a request to the process management has failed.

Communication between the process management command and the process management failed.

(S)

Terminates the process management command.

(O)

Check that the /var/opt/jp1base/tmp directory exists.

KAVB3654-E

An attempt to receive a response from the process management has failed.

The process management command failed to receive data from the process management.

(S)

Terminates the process management command.

(O)

Restart the process management, and then re-execute the command.

KAVB3655-E

Invalid data was received from the process management.

The process management command received invalid data from the process management.

(S)

Terminates the process management command.

(O)

Invalid data may have been received temporarily. Restart the process management, and then re-execute the command.

KAVB3656-I

The startup command terminated normally.

The startup command of the process management is terminated normally.

(S)

Terminates the process management command.

KAVB3657-E

The startup command terminated abnormally

The startup command terminated abnormally.

(S)

Terminates the process management command.

(O)

Use the jbs_spmd_status command to check the status, and then re-execute the command.

KAVB3658-E

The startup command terminated abnormally due to an inconsistent state.

A command was executed while the process management was performing some other processing.

(S)

Terminates the process management command.

(O)

Use the jbs_spmd_status command to check the status, and then re-execute the command.

KAVB3659-E

There were no processes that could run.

There is no process to start.

(S)

Terminates the process management command.

KAVB3660-E

Invalid data was received.

The process management command received invalid data from the process management.

(S)

Terminates the process management command.

(O)

Invalid data may have been received temporarily. Restart the process management, and then re-execute the command.

KAVB3661-E

An unexpected result code was received. (return code = return-code)

The process management command received an unexpected result code from the process management.

(S)

Terminates the process management command.

(O)

Use the jbs_spmd_status command to check the status, and then re-execute the command.

KAVB3662-E

The process management is not running.

The process management has stopped.

(S)

Terminates the process management command.

KAVB3663-E

Execute the command from the administrator console.

This command must be executed on the administrator console.

(S)

Terminates command processing.

(O)

Execute the command on the administrator console.

KAVB3664-I

JP1/Base has started on the host host-name.

JP1/Base started.

(S)

Continues processing.

KAVB3665-I

JP1/Base will now end on the host host-name.

JP1/Base will stop.

(S)

Continues processing.

KAVB3666-E

An attempt to issue a start or stop notification has failed. (function = function-name, status = status-code)

A start or stop notification for JP1/Base could not be issued.

(S)

Continues processing.

(O)

Check whether the event server is running. If the event server is not running, start it. If the event server is running, use the data collection tool to collect data, and then contact the system administrator.

KAVB3672-I

A forced termination (kill) of JP1_BASE has started.

The forced termination processing starts for the process management.

(S)

Terminates the process management command.

KAVB3674-I

Termination processing of JP1_BASE has started.

Termination processing of process management will now start.

(S)

Terminates the process management command.

KAVB3675-I

The stop command terminated normally.

The stop command for process management terminated normally.

(S)

Terminates the process management command.

KAVB3676-E

The stop command terminated abnormally.

The stop command terminated abnormally.

(S)

Terminates the process management command.

(O)

Wait a while. Then use jbs_spmd_status to check the status, and then re-execute the command.

KAVB3677-E

The stop command terminated abnormally due to an inconsistent state.

The command was executed while the process management was performing some other processing.

(S)

Terminates the process management command.

(O)

Wait a while, and then re-execute the command.

KAVB3678-I

There were no processes that could terminate.

There is no process to terminate.

(S)

Terminates the process management command.

KAVB3680-I

Reload processing for JP1_BASE has started.

The system starts the reload processing for the process to be managed by the process management.

(S)

Terminates the process management command.

KAVB3681-I

The reload command terminated normally.

The reload command of the process management terminated normally.

(S)

Terminates the process management command.

KAVB3682-E

The reload command terminated abnormally.

The reload command terminated abnormally.

(S)

Terminates the process management command.

(O)

Check that there is no process for which reload processing failed, from among the processes to be managed.

KAVB3683-E

The reload command terminated abnormally due to an inconsistent state.

The command was executed while the process management performed other processing.

(S)

Terminates the process management command.

(O)

Wait a while, and then re-execute the command.

KAVB3684-E

There were no processes that could be reloaded.

There is no process to reload.

(S)

Terminates the process management command.

(O)

Check if the process to be managed is running.

KAVB3685-E

A timeout occurred in management-target-process-name.

A timeout occurred while the process indicated by management-target-process-name was being reloaded.

(S)

Terminates the process management command.

(O)

Check that there is no process for which reloading failed, from among the processes to be managed.

KAVB3686-W

An error occurred during initialization of the operation log. (function-name, code = error-number)

An error occurred during initialization of the operation log.

(S)

Continues processing.

KAVB3687-W

An attempt to output the operation log has failed. (code = error-number)

The operation log was not output because an error occurred during initialization of the operation log.

(S)

Continues processing without outputting the operation log.

KAVB3690-I

Processing to report the status of JP1_BASE has started.

The system starts the status notification processing for the process management.

(S)

Terminates the process management command.

KAVB3691-I

All the processes have started.

All the management-target processes have started.

(S)

Terminates the process management command.

KAVB3692-I

Some of the processes have started.

Some of the management-target processes have started.

(S)

Terminates the process management command.

KAVB3693-I

All of the processes have stopped.

All the management-target 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 the process management.

KAVB3705-I

management-target-process-name is now starting. (process ID = process-ID)

The management-target process is being started. management-target-process-name is the name of a process that makes up a component managed by the process management. process-ID is the process ID of the management-target process that is being started.

(S)

Continues processing.

KAVB3732-I

JP1_BASE detected the termination of management-target-process-name. (process ID = process-ID)

The system detected that the management-target process was stopped. management-target-process-name is the name of a process that makes up a component managed by the process management. process-ID is the process ID of the management-target process that is being started.

(S)

Continues processing.

KAVB3736-I

All processes of JP1_BASE have stopped.

All the management-target processes have stopped.

(S)

Terminates the process management.

KAVB3737-E

The JP1_BASE management-target-process-name terminated abnormally

The system detected that the management-target process terminated abnormally. management-target-process-name is the name of a process that makes up a component managed by the process management.

(S)

Continues processing.

(O)

Check the integrated trace log that is output by the management-target process that terminated abnormally, and eliminate the cause of the error. Use the jbs_spmd_status command to check the status, and then restart. If the management-target process does not output any message, use the data collection tool to collect data, and then contact the system administrator.

KAVB3743-I

JP1_BASE has terminated.

The system terminates the process management.

(S)

Terminates the process management.

KAVB3744-I

JP1_BASE startup has finished.

The service startup has finished.

(S)

Continues processing.

KAVB3745-I

The JP1_BASE startup request has finished.

The startup request has finished.

(S)

Continues processing.

KAVB3751-E

The process stopped in response to the signal. pid = process-ID. signal = signal-number.

The management-target process stopped in response to the signal. process-ID is the process ID of the management-target process that was being started. signal-number is the number of the signal that causes the process to stop.

(S)

Continues processing.

(O)

Check the integrated trace log output by the management-target process that was terminated anbormally, and eliminate the cause of the error. Use the jbs_spmd_status command to check the status, and then restart the process management. If the management-target process did not output any messages, use the data collection tool to collect data, and then contact the system administrator.

KAVB3752-E

An attempt to start management-target-process-name has finished. (return code = return-code, detail code = reason-code)

The process to be managed could not start. management-target-process-name is the name of a process that makes up a component managed by the process management.

(S)

Continues processing.

(O)

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

KAVB3760-I

The changes to file-name were not applied.

The setting changes in the extended startup process definition file (jp1bs_service_0700.conf) were not applied.

(S)

Continues processing.

(O)

Change the preset value, and then re-execute the command.

KAVB3761-E

In the file file-name, the restart-or-not value is invalid. (restart-or-not = preset-value)

The value to enable or disable restart specified in the extended startup process definition file (jp1bs_service_0700.conf) is invalid.

(S)

Continues processing.

(O)

Change the preset value, and then re-execute the command.

KAVB3762-I

Set 0 or 1 for the restart-or-not value.

The value to enable or disable restart specified in the extended startup process definition file (jp1bs_service_0700.conf) must be 0 or 1.

(S)

Continues processing.

(O)

Specify 0 or 1 as the value to enable or disable restart.

KAVB3763-E

In the file file-name, the number-of-restarts value is invalid. (restart num. = preset-value)

The number of times for trying restart that is specified in the extended startup process definition file (jp1bs_service_0700.conf) is invalid.

(S)

Continues processing.

(O)

Change the preset value, and then re-execute the command.

KAVB3764-I

Set 0 to 99 for the number-of-restarts value.

The number of times for trying restart that is specified in the extended startup process definition file (jp1bs_service_0700.conf) must be from 0 to 99.

(S)

Continues processing.

(O)

Specify a value from 0 to 99 as the number of times for trying restart.

KAVB3765-E

In the file file-name, the restart interval value is invalid. (restart interval = preset-value)

The retry interval value specified in the extended startup process definition file (jp1bs_service_0700.conf) is invalid.

(S)

Continues processing.

(O)

Change the preset value, and then re-execute the command.

KAVB3766-I

Set 0 to 3600 for the restart interval value.

The retry interval value specified in the extended startup process definition file (jp1bs_service_0700.conf) must be from 0 to 3,600.

(S)

Continues processing.

(O)

Specify a value from 0 to 3,600 as the retry interval.

KAVB3767-E

In the file file-name, the restart-count reset time is invalid. (restart-count reset time = preset-value)

The restart-count reset time specified in the extended startup process definition file (jp1bs_service_0700.conf) is invalid.

(S)

Continues processing.

(O)

Change the preset value, and then re-execute the command.

KAVB3768-I

Set 3600 to 2147483647 for the restart-count reset time.

The restart-count reset time specified in the extended startup process definition file (jp1bs_service_0700.conf) must be from 3,600 to 2,147,483,647.

(S)

Continues processing.

(O)

Specify a value from 3,600 to 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 (jp1bs_service_0700.conf).

(S)

Continues processing.

(O)

Check the entries in the extended startup process definition file.

KAVB3777-I

JP1_BASE: The stopped management-target-process-name will be restarted. (restart count = restart-count)

The stopped process to be managed restarts. management-target-process-name is the name of one of the processes comprising each component managed by process management.

(S)

Restarts the process to be managed.

KAVB3778-I

JP1_BASE: A startup request was sent to the process management-target-process-name.

A startup request was sent to the process to be managed. management-target-process-name is the name of one of the processes comprising each component managed by process management.

(S)

Continues processing.

KAVB3779-I

JP1_BASE: An attempt to send a startup request to the process management-target-process-name failed.

A request to start the process to be managed could not be sent. management-target-process-name is the name of one of the processes comprising each component managed by process management.

(S)

Continues processing.

KAVB3786-E

To process ID-of-child-process-of-management-target-process, the system sent the signal signal-name.

A signal was sent to the child process of a process to be managed. ID-of-child-process-of-management-target-process is the ID of a process generated by an active process to be managed.

(S)

Continues processing.

KAVB3788-E

JP1_BASE: The number of restarts of management-target-process-name exceeded the specified restart count.

The restart count for the process to be managed exceeded the preset value. management-target-process-name is the name of one of the processes comprising each component managed by process management.

(S)

Continues processing.

(O)

Check the integrated trace log that is output by the management-target process which was terminated, and eliminate the cause of the error. Use the jbs_spmd_status command to check the status, and then restart the process management. If the management-target process does not output any message, use the data collection tool to collect data, and then contact the system administrator.

KAVB3792-E

JP1_BASE: A start parameter is invalid: [-hot | -cold [-q {clear | noclear}]| -warm]

A start parameter is invalid.

(S)

Terminates process management.

(O)

Check the start parameter, and then re-execute the command.

KAVB3802-W

The process manager will not be monitored because an attempt to initialize the health check function failed.

The process manager will not be monitored because an attempt to initialize the health check function has failed.

(S)

Continues processing.

(O)

To monitor the process manager by using the health check function, restart the process manager.

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 because there were not enough resources.

(S)

Cancels processing.

(O)

Confirm that there are enough system resources.

Reacquire product information after the insufficient-resources issue has been resolved. If the issue cannot be resolved, use the data collection tool to collect data, and then contact the system administrator.

KAVB3841-E

The product information could not be acquired because the environment is invalid. (Detailed information: function-name, return-value)

Acquisition of product information failed because the environment is invalid.

(S)

Cancels processing.

(O)

Confirm that there are no failures in the system.

Uninstall, reinstall, and then re-acquire the program information.

If the issue is not resolved, use the data collection tool to collect data, and then contact the system administrator.

KAVB3846-I

JP1_BASE completed the reload request.

The reload processing has finished.

(S)

Continues processing.

KAVB3855-I

The process management-target-process-name will be terminated by SIGKILL. (process ID = process-ID)

SIGKILL will be sent to the management-target process. management-target-process-name is the name of a process that makes up a component managed by the process management. process-ID is the process ID of the management-target process that is being started.

(S)

Continues processing.

KAVB3862-E

JP1_BASE: No processes could be started.

No management-target process has started.

(S)

Terminates the process management.

(O)

Make sure that system memory is sufficient, and that the product is correctly installed.

KAVB3863-E

JP1_BASE: No processes can be reloaded.

All the management-target processes were not in the status to be reloaded.

(S)

Continues processing.

(O)

Wait a while, and then re-execute the command.

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

(S)

Terminates the process management command.

(O)

The common definition information is not defined. Make sure that the settings are correct.

If you are using JP1/Base in a cluster system:

Make sure that the logical host name is specified correctly in the argument of the process management command. Also make sure that the logical host name is specified correctly in the JP1_HOSTNAME environment variable. If the setup for operation in a cluster system described in the manual Job Management Partner 1/Base User's Guide has not been completed, perform the setup.

If you are not using JP1/Base in a cluster system:

Make sure that JP1/Base has not started with the JP1_HOSTNAME environment variable specified. If this environment variable is not specified, perform the following for recovery:

In Windows:

Perform an overwrite installation.

In UNIX:

Execute the jp1base_setup command.

If this error occurred when you uninstalled JP1/Base, reinstall it according to the notes on installation and uninstallation in the manual Job Management Partner 1/Base User's Guide.

KAVB3871-E

The conf directory path cannot be obtained by using the specified logical hostname.

The system could not acquire the conf directory path from the common definition information using the specified logical host name.

(S)

Terminates the process management command.

(O)

It is assumed that you are using a cluster system. Make sure that the specified logical host name is correct, and that setup terminated 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 information.

(S)

Terminates the process management command.

(O)

If you are using a cluster system, make sure that the logical host name is set correctly and that setup terminated normally. If you are not using a cluster system, perform the following for recovery:

In UNIX:

Execute the setup command.

In Windows:

Perform a corrective installation.

KAVB3873-E

The log directory path cannot be obtained by using the specified logical hostname.

The system could not acquire the log directory path from the common definition information using the specified logical host name.

(S)

Terminates the process management command.

(O)

It is assumed that you are using a cluster system. Make sure that the specified logical host name is correct, and that setup terminated normally.

KAVB3874-E

HNTRLib could not be initialized.

HNTRLib2 could not be initialized. No log is output.

(S)

Continues processing.

(O)

If the process management is running, stop and then restart it.

KAVB3875-E

HNTRLib could not be initialized.

HNTRLib2 could not be initialized. No log is output.

(S)

Continues processing.

(O)

If the process management is running, stop and then restart it.

KAVB3899-E

The work directory path cannot be acquired from the common definition information. (return code = return-code)

The path to the work directory could not be obtained from the common definition information.

(S)

Terminates the process management command.

(O)

If you are using a cluster system, make sure that the logical host name is set correctly and that setup terminated normally. If you are not using a cluster system, perform the following for recovery:

In Windows:

Perform a correction installation.

In UNIX:

Execute the setup command.

KAVB3905-I

A stop request was sent to the process management-target-process-name. (process ID = process-ID)

A stop request was sent to the management-target process. management-target-process-name is the name of a process that makes up a component managed by the process management. process-ID is the process ID of the management-target process that is being started.

(S)

Continues processing.

KAVB3908-I

A reload request was sent to the process management-target-process-name. (process ID = process-ID)

A reload request was sent to the management-target process. management-target-process-name is the name of a process that makes up a component managed by the process management. process-ID is the process ID of the management-target process that is being started.

(S)

Continues processing.

KAVB3910-I

SIGTERM will terminate the process management-target-process-name. (process ID = process-ID)

SIGTERM will be sent to the management-target process. management-target-process-name is the name of a process that makes up a component managed by the process management. process-ID is the process ID of the management-target process that is being started.

(S)

Continues processing.

KAVB3911-E

The process management daemon is busy.

A command is being executed

(S)

Terminates the process management command.

(O)

Wait a while, and then re-execute the command. If this message appears when you execute the jbs_spmd, jbs_spmd _stop, or jbs_spmd _reload command during starting, terminating, or reloading, wait for the completion of the processing, and then re-execute the command.

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 system could not open the lock file in the conf directory.

(S)

Terminates the process management command.

(O)

Check that the conf directory exists and that you have the write permission for it. If you are using a cluster system, check that the defined conf directory exists and that you have write permission for it.

2.12 ISAM file messages (KAIU001 to KAIU999)

KAIU001-E (Windows)

ISAM access function error (xx...x, yy...y).

An ISAM error occurred in an ISAM access function.

xx...x is the name of the ISAM access function in which the error occurred. yy...y is the error code of the ISAM access function. The message does not contain yy...y if the error occurred in a system call used in the ISAM function.

(S)

Cancels processing.

(O)

Correct the error, and then re-execute the command.

KAIU001-E (UNIX)

Error on ISAM access function, function name: xx...x yy...y

An ISAM error occurred in an ISAM access function.

xx...x is the name of the ISAM access function in which the error occurred. yy...y is the error code of the ISAM access function.

yy...y is not output if the error occurred in a system call used in an ISAM function.

(S)

Cancels processing.

(O)

Correct the error, and then re-execute the command.

KAIU002-E (Windows)

I/O error in xx...x

An I/O error occurred in the file indicated by xx...x.

(S)

Closes all open files, and then cancels processing.

(O)

Correct the error, and then re-execute the command.

KAIU002-E (UNIX)

I/O error on file xx...x

An I/O error occurred in the file indicated by xx...x.

(S)

Closes all open files, and then cancels processing.

(O)

Correct the error, and then re-execute the command.

KAIU003-E (Windows)

No primary key file.

A key item name or physically ordered output was not specified for an ISAM file having no primary key.

(S)

Cancels processing.

(O)

Specify a key item name or physically ordered output, and then re-execute the command.

KAIU003-E (UNIX)

No primary key exists in this file ISAM file: xx...x

A key item name or physically ordered output was not specified for an ISAM file having no primary key.

xx...x is the name of the ISAM file.

(S)

Cancels processing.

(O)

Specify a key item name or physically ordered output, and then re-execute the command.

KAIU004-E (Windows)

xx...x is not found.

The file having the name indicated by xx...x is not found.

(S)

Cancels processing.

(O)

Specify the correct file name, and then re-execute the command.

KAIU004-E (UNIX)

Cannot copy file xx...x on to same file yy...y

In copying a file, the source file and the destination file are the same.

(S)

Cancels file copying.

(O)

Check the filename and the link status, and then re-execute the command.

KAIU005-E (Windows)

xx...x is not a directory.

xx...x is not a directory.

(S)

Cancels processing.

(O)

Specify the correct directory name, and then re-execute the command.

KAIU005-E (UNIX)

Specified name xx...x to copy is not a directory

In copying a file, the file specified in xx...x was not a directory.

(S)

Cancels file copying.

(O)

Check the filename, and then re-execute the command.

KAIU006-E (Windows)

Sum of key location and key length exceeds record length (xx...x).

The sum of the key location and key length exceeds the minimum or maximum record length.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct values, and then re-execute the command.

KAIU006-E (UNIX)

Sum of key position and key length has exceeded maximum range, line no. of key des parameter file: xx...x

The total of the key location and key length exceeded the record length or the minimum record length.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct values, and then re-execute the command.

KAIU008-E (Windows)

File is not an ISAM file (xx...x).

The file is not an ISAM file or is a corrupted ISAM file.

xx...x is a filename.

(S)

Cancels the processing of the file.

(O)

Check the file-name. If the file is a corrupted ISAM file, re-create the key definition file.

KAIU008-E (UNIX)

This file xx...x is not an ISAM file or is a corrupted ISAM file

The file is not an ISAM file or is a corrupted ISAM file.

(S)

Cancels the processing of the file.

(O)

Check the filename. If the file is a corrupted ISAM file, re-create the key definition file.

KAIU009-E (Windows)

Invalid key definition file (xx...x).

The information in the key definition file is invalid.

xx...x is a filename.

(S)

Cancels processing.

(O)

Re-create the key definition file.

KAIU009-E (UNIX)

Invalid key description file: xx...x

The information in the key definition file is invalid.

xx....x is a filename.

(S)

Cancels processing.

(O)

Re-create the key definition file.

KAIU010-I (Windows)

Extracting records xx...x.

xx...x records were extracted from the data file.

KAIU010-I (UNIX)

Extracted xx...x records from data file

xx...x records were obtained from the data file

KAIU012-E (Windows)

File is already in use (xx...x).

The ISAM file xx...x to be processed is being used exclusively by another process.

Alternatively, the sequential file xx...x to be extracted is being used exclusively by another process.

(S)

Cancels the processing of the file.

(O)

Wait until the other process ends, and then re-execute the command.

KAIU012-E (UNIX)

This file xx...x is locked by another process

The ISAM file xx...x to be processed is being used exclusively by another process.

Alternatively, the sequential file xx...x to be extracted is being used exclusively by another process.

(S)

Cancels the processing of the file.

(O)

Wait until the other process ends, and then re-execute the command.

KAIU013-E (Windows)

Invalid key definition file detected.

File name: xx...x

Key definition file name: yy...y

Error detected: zz...z

An error was detected in the key definition file yy...y of the ISAM file xx...x for the reason zz...z.

(S)

Cancels processing.

(O)

Re-create the ISAM file according to the procedure for recovering ISAM files.

KAIU013-E (UNIX)

Invalid key description file is detected,

ISAM file name: xx...x

key des file name: yy...y

reason: zz...z

An error was detected in the key definition file yy...y of the ISAM file xx...x for the reason zz...z.

(S)

Cancels processing.

(O)

Re-create the ISAM file according to the procedure for recovering ISAM files.

KAIU014-E (Windows)

Invalid key file detected.

File name: xx...x

Key file name: yy...y

Key item name: kk...k

Error detected: zz...z aa...a

An error was detected in the key file yy...y of the ISAM file xx...x for the reason zz...z.

aa...a (hexadecimal) indicates the offset position in the key file.

(S)

Starts verifying the next key file if the next key is defined.

(O)

Reorganize the key file containing the error.

KAIU014-E (UNIX)

Invalid key file is detected,

ISAM file name: xx...x

key file name: yy...y

key item name: kk...k

reason: zz...z aa...a

An error was detected in the key file yy...y of the ISAM file xx...x for the reason zz...z. aa...a (hexadecimal number) is the offset in the key file.

(S)

Starts verifying the next key file if the next key is defined.

(O)

Reorganize the key file containing the error.

KAIU015-E (Windows)

Invalid data file detected.

File name: xx...x

Data file name: yy...y

Error detected: zz...z

An error was detected in the data file yy...y of the ISAM file xx...x for the reason zz...z.

(S)

Cancels processing.

(O)

Re-create the ISAM file according to the procedure for recovering ISAM files.

KAIU015-E (UNIX)

Invalid data file is detected,

ISAM file name: xx...x

data file name: yy...y

reason: zz...z

An error was detected in the data file yy...y of the ISAM file xx...x for the reason zz...z.

(S)

Cancels processing.

(O)

Re-create the ISAM file according to the procedure for recovering ISAM files.

KAIU019-I (Windows)

Verifying ISAM file (xx...x)

Verification of the ISAM file xx...x will now start.

KAIU019-I (UNIX)

Checking of ISAM file xx...x is starting

Verification of the ISAM file xx...x will now start.

KAIU020-I

ISAM file was found to be normal

The verified file was normal.

KAIU021-I

There are no records in the specified file to display.

The specified file does not contain a record to be displayed.

KAIU022-E (Windows)

Record for display start key does not exist.

The specified display start key value is greater than any key value in the specified key file.

(S)

Terminates processing because the record for the specified display start key value does not exist.

(O)

Check the specified display start key value, and then re-execute the command.

KAIU022-E (UNIX)

Cannot find record for specified display start key, specified value may be too large

The specified display start key value is greater than any key value in the specified key file.

(S)

Terminates processing because the record for the specified display start key value does not exist.

(O)

Check the specified display start key value, and then re-execute the command.

KAIU023-E

Incorrect key specified.

The specified key is invalid.

(S)

Cancels processing.

(O)

Specify the key correctly, and then re-execute the command.

KAIU024-E (Windows)

The key item name xx...x already exists.

The key item name indicated by xx...x already exists in the key definition file.

(S)

Does not perform processing on the key item name indicated by xx...x.

(O)

Check the specified key item name, and then re-execute the command.

KAIU024-E (UNIX)

Additional key item name xx...x is already in key description file

The key item name indicated by xx...x already exists in the key definition file.

(S)

Does not perform processing on the key item name indicated by xx...x.

(O)

Check the specified key item name, and then re-execute the command.

KAIU025-E (Windows)

Key information for key item name xx...x is already in the key description file (xx...x).

The key information specified in the ke- parameter for the key item name indicated by xx...x is already in the key definition file.

(S)

Does not perform processing on the key item name indicated by xx...x.

(O)

Check the specified information, and then re-execute the command.

KAIU025-E (UNIX)

Key information for key item name xx...x is already in key description file

Key information specified in the ke- parameter for the key item name indicated by xx...x is already present in the key definition file.

(S)

Does not perform processing on the key item name indicated by xx...x.

(O)

Check the specified information, and then re-execute the command.

KAIU026-E (Windows)

Key to be deleted does not exist (xx...x).

The key item name indicated by xx...x does not exist in the key definition file.

(S)

Does not perform processing on the key item name indicated by xx...x.

(O)

Check the specified key item name, and then re-execute the command.

KAIU026-E (UNIX)

Cannot find key item name xx...x to delete in key description file

The key item name indicated by xx...x is not present in the key definition file.

(S)

Does not perform processing on the key item name indicated by xx...x.

(O)

Check the specified key item name, and then re-execute the command.

KAIU027-E (Windows)

The primary key cannot be deleted (xx...x).

The key item name indicated by xx...x cannot be deleted because it references the primary key file.

(S)

Does not perform processing on the key item name indicated by xx...x.

(O)

Check the specified key item name, and then re-execute the command.

KAIU027-E (UNIX)

Key item name xx...x is a primary key file: cannot delete

The key item name indicated by xx...x cannot be deleted because it references the primary key file.

(S)

Does not perform processing on the key item name indicated by xx...x.

(O)

Check the specified key item name, and then re-execute the command.

KAIU028-E (Windows)

Key to be reconstructed does not exist (xx...x).

The key item name indicated by xx...x does not exist in the key definition file.

(S)

Does not perform processing on the key item name indicated by xx...x.

(O)

Check the specified key item name, and then re-execute the command.

KAIU028-E (UNIX)

Cannot find key item name xx...x to recreate in key description file

The key item name indicated by xx...x is not present in the key definition file.

(S)

Does not perform processing on the key item name indicated by xx...x.

(O)

Check the specified key item name, and then re-execute the command.

KAIU029-E (UNIX)

Keyword xx...x has invalid key item name yy...y

The key item name yy...y specified in xx...x was invalidated by another parameter.

(S)

Does not perform processing on the parameter shown in this message.

(O)

Check the specified key item name, and then re-execute the command.

KAIU030-E (Windows)

Cannot add/delete/recreate key for xx...x.

A key cannot be added, deleted, or re-created because a parameter or the ISAM file indicated by xx...x is invalid, or for some other reason.

(S)

Cancels the addition, deletion, or re-creation of the key for the ISAM file indicated by xx...x.

(O)

Correct the cause of the error according to the information in the message output before this message, and then re-execute the command.

KAIU030-E (UNIX)

Invalid parameter or invalid ISAM file xx...x: cannot add, delete, or recreate key

A key cannot be added, deleted, or recreated because a parameter or the ISAM file indicated by xx...x is invalid or for some other reason.

(S)

Cancels the addition, deletion, or reorganization of the key for the ISAM file indicated by xx...x.

(O)

Correct the error according to the information in the message output before this message, and then re-execute the command.

KAIU031-E (Windows)

Cannot add/recreate key for xx...x.

A key cannot be added or re-created because a parameter or the ISAM file indicated by xx...x is invalid, or for some other reason.

(S)

Cancels the addition or re-creation of the key for the ISAM file indicated by xx...x.

(O)

Correct the cause of the error according to the instruction given in the message that was output before this message, and then re-execute the command.

KAIU031-E (UNIX)

Invalid parameter or invalid ISAM file xx...x: cannot add or recreate key

A key cannot be added or recreated because a parameter or the ISAM file indicated by xx...x is invalid or for some other reason.

(S)

Cancels the addition or reorganization of the key for the ISAM file indicated by xx...x.

(O)

Correct the error according to the information in the message output before this message, and then re-execute the command.

KAIU032-E (Windows)

Cannot add a key for xx...x.

A key cannot be added because a parameter is invalid, or the ISAM file indicated by xx...x is invalid.

(S)

Cancels the addition of a key to the ISAM file indicated by xx...x.

(O)

Correct the error according to the information in the message output before this message, and then re-execute the command.

KAIU032-E (UNIX)

Invalid parameter or invalid ISAM file xx...x: cannot add key

A key cannot be added because a parameter or the ISAM file indicated by xx...x is invalid.

(S)

Cancels the addition of a key to the ISAM file indicated by xx...x.

(O)

Correct the error according to the information in the message output before this message, and then re-execute the command.

KAIU033-Q

Delete ISAM file xx...x: ? (y/n)

Specify whether to delete the ISAM file indicated by xx...x.

(S)

Waits for you to enter y or n.

(O)

Enter y to delete the file.

Enter n in order not to delete the file.

KAIU034-E

Cannot find key xx...x to recreate.

The specified key item name does not exist in the key definition file.

xx...x indicates the key item name. The system does not output xx...x if the error was detected before the start of the addition, deletion, or re-creation of the key.

(S)

Cancels processing.

(O)

Check the specified key item name, and then re-execute the command.

KAIU035-Q (Windows)

Do you want to overwrite xx...x? (y/n):

The i option is specified, and the copy-destination file exists.

(S)

Waits for you to enter y or n.

(O)

Enter n to not copy the file.

Enter y to copy the file and overwrite the copy-destination file.

KAIU035-Q (UNIX)

File xx...x already exists. Overwrite file: ? (y/n)

The i option is specified, and the copy-destination file exists.

(S)

Waits for you to enter y or n.

(O)

Enter n in order not to copy the file.

Enter y to overwrite and copy the file.

KAIU036-I

Maximum number of keys has been specified.

The number of specified keys or the sum of the number of specified keys and keys in the key definition file reached the limit.

KAIU037-E (Windows)

Key name must be specified (xx...x).

A parameter to specify a key item name is omitted.

xx...x is a keyword.

(S)

Cancels processing.

(O)

Specify a parameter to specify a key item name, and then re-execute the command.

KAIU037-E (UNIX)

Must specify parameter specifying key item name, keyword: xx...x

A parameter to specify a key item name is omitted.

xx...x is a keyword.

(S)

Cancels processing.

(O)

Specify a parameter to specify a key item name, and then re-execute the command.

KAIU038-E (Windows)

Number of keys exceeds the maximum allowed (xx...x).

The total of the number of specified keys or keys in the key definition file and the number of specified keys exceeded the limit.

xx...x is a key item name.

(S)

Cancels the creation of the key definition file.

(O)

Check the number of specified keys, and then re-execute the command.

KAIU038-E (UNIX)

Number of specified keys, or sum of it and number of key in key description file has exceeded maximum, ISAM file: xx...x

The total of the number of specified keys or keys in the key definition file and the number of specified keys exceeded the limit.

xx...x is a key item name.

(S)

Cancels the creation of the key definition file.

KAIU039-E (Windows)

xx...x exists.

An ISAM file that is the same as the ISAM file indicated by xx...x exists.

xx...x is an ISAM filename.

(S)

Cancels processing.

(O)

Take action according to the information in the message output after this message.

KAIU039-E (UNIX)

ISAM file xx...x already exists

The ISAM file that is the same as the ISAM file indicated by xx...x is present.

xx...x is an ISAM filename.

(S)

Cancels processing.

(O)

Take action according to the information in the message output after this message.

KAIU040-E (Windows)

xx...x has not been specified (yy...y).

The parameter indicated by xx...x is missing.

xx...x is a keyword.

yy...y is a line number in the key definition parameter file or in the organization parameter file.

(S)

Cancels processing.

(O)

Specify the correct parameter, and then re-execute the command.

KAIU040-E (UNIX)

Parameter indicated by keyword xx...x must be specified, line no. in key des parameter file: yy...y

The parameter indicated by xx...x is missing.

xx...x is a keyword.

yy...y is a line number in the key definition parameter file or in the organization parameter file.

(S)

Cancels processing.

(O)

Specify the correct parameter, and then re-execute the command.

KAIU041-E (Windows)

xx...x or yy...y has not been specified (zz...z).

The parameter indicated by xx...x or yy...y is missing.

xx...x and yy...y are keywords.

zz...z is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct parameter, and then re-execute the command.

KAIU041-E (UNIX)

Parameter indicated by keyword xx...x or yy...y must be specified, line no. in key des parameter file: zz...z

The parameter indicated by xx...x or yy...y is missing.

xx...x and yy...y are keywords.

zz...z is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct parameter, and then re-execute the command.

KAIU042-E (Windows)

The value for sp must be two digits (xx...x).

The value specified in the sp parameter is not a two-digit value.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct parameter, and then re-execute the command.

KAIU042-E (UNIX)

sp parameter cannot exceed 2 digits, line no. in key des parameter file: xx...x

The value specified in the sp parameter is not a two-digit value.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct parameter, and then re-execute the command.

KAIU043-E (Windows)

The value for cp must be four digits (xx...x).

The value specified in the cp parameter is not a four-digit value.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct parameter, and then re-execute the command.

KAIU043-E (UNIX)

cp parameter cannot exceed 4 digits, line no. in key des parameter file: xx...x

The value specified in the cp parameter is not a four-digit value.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct parameter, and then re-execute the command.

KAIU044-E (Windows)

xx...x is invalid (yy...y).

An invalid parameter was specified.

xx...x is the invalid parameter.

yy...y is a line number in the key definition parameter file or in the organization parameter file.

(S)

Cancels processing.

(O)

Specify the correct parameter, and then re-execute the command.

KAIU044-E (UNIX)

Invalid parameter xx...x is specified, line no. in key des parameter file: yy...y

An invalid parameter was specified.

xx...x is the invalid parameter.

yy...y is a line number in the key definition parameter file or in the organization parameter file.

(S)

Cancels processing.

(O)

Specify the correct parameter, and then re-execute the command.

KAIU045-E (Windows)

xx...x parameter sequence is invalid (yy...y).

The order of the parameter indicated by xx...x is incorrect.

xx...x is a keyword.

yy...y is a line number in the key definition parameter file or in the organization parameter file.

(S)

Cancels processing.

(O)

Specify the parameter in the correct order, and then re-execute the command.

KAIU045-E (UNIX)

Parameter indicated by keyword xx...x is in invalid sequence, line no. in key des parameter file: yy...y

The order of the parameter indicated by xx...x is incorrect.

xx...x is a keyword.

yy...y is a line number in the key definition parameter file or in the organization parameter file.

(S)

Cancels processing.

(O)

Specify the parameter in the correct order, and then re-execute the command.

KAIU046-E (Windows)

Key item name for xx...x exceeds 31 characters (yy...y).

The key item name indicated by xx...x is longer than 31 bytes.

xx...x is a keyword.

yy...y is a line number in the key definition parameter file or in the organization parameter file.

(S)

Cancels processing.

(O)

Specify the correct key item name, and then re-execute the command.

KAIU046-E (UNIX)

Key item name in parameter indicated by keyword xx...x has exceeded 31 bytes, line no. in key des parameter file: yy...y

The key item name indicated by xx...x has exceeded 31 bytes.

xx...x is a keyword.

yy...y is a line number in the key definition parameter file or in the organization parameter file.

(S)

Cancels processing.

(O)

Specify the correct key item name, and then re-execute the command.

KAIU047-E (Windows)

yy...y cannot be specified for parameter xx...x key item name (zz...z).

An invalid key item name was specified in the parameter indicated by xx...x.

xx...x is a keyword.

yy...y is the invalid key item name.

zz...z is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct key item name, and then re-execute the command.

KAIU048-E (Windows)

ke parameter specified more than 8 times (xx...x).

The ke parameter is specified more than 8 times.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the ke parameter no more than eight times, and then re-execute the command.

KAIU048-E (UNIX)

Specification count for ke parameter has exceeded 8, line no. in key des parameter file: xx...x

Specification count for ke parameter exceeded 8.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the ke parameter no more than eight times, and then re-execute the command.

KAIU049-E (Windows)

Key location exceeds range (xx...x).

A key is located beyond the specified range. For example, the key may be located beyond the record length.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the key in the correct location, and then re-execute the command.

KAIU049-E (UNIX)

Key position is out of range, line no. in key des parameter file: xx...x

Key position was out of range. For example, the key may be located beyond the record length.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the key in the correct location, and then re-execute the command.

KAIU050-E (Windows)

Key length exceeds range (xx...x).

A key is longer than the limit.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the key with the correct length, and then re-execute the command.

KAIU050-E (UNIX)

Key length is out of range, line no. or keyword in key des parameter file: xx...x

Key length was out of range.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the key with the correct length, and then re-execute the command.

KAIU051-E (Windows)

Multiple mn parameters are specified (xx...x).

The mn parameter is specified more than once.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the mn parameter only once, and then re-execute the command.

KAIU051-E (UNIX)

Two or more mn parameter are specified, line no. in key des parameter file: xx...x

The mn parameter is specified more than once.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the mn parameter only once, and then re-execute the command.

KAIU052-E (Windows)

Record length exceeds range (xx...x).

The record length or the minimum record length is longer than the limit.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Reduce the record length to the limit or less, and then re-execute the command.

KAIU052-E (UNIX)

Record length is out of range, line no. in key des parameter file: xx...x

The record length or the minimum record length is out of range.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Reduce the record length to the limit or less, and then re-execute the command.

KAIU053-E (Windows)

Minimum record length is greater than record length (xx...x).

The minimum record length is longer than the record length.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the minimum record length correctly, and then re-execute the command.

KAIU053-E (UNIX)

Record length is less than minimum record length, line no. in key des parameter file: xx...x

The record length is less than the minimum record length

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the minimum record length correctly, and then re-execute the command.

KAIU054-E (Windows)

Minimum record length for fixed length ISAM files cannot be specified (xx...x).

The minimum record length was specified for an ISAM file with fixed-length records.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Do not specify the record length, and then re-execute the command.

KAIU054-E (UNIX)

Cannot specify minimum record length for fixed length ISAM file, line no. in key des parameter file: xx...x

The minimum record length was specified for an ISAM file with fixed-length records.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct record length, and then re-execute the command.

KAIU055-E (Windows)

Minimum record length for variable length ISAM files must be specified (xx...x).

The minimum record length is not specified for an ISAM file with variable-length records.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the record length correctly, and then re-execute the command.

KAIU055-E (UNIX)

Must specify minimum record length for variable length ISAM file, line no. in key des parameter file: xx...x

The minimum record length is not specified for an ISAM file with variable-length records.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct record length, and then re-execute the command.

KAIU056-E (Windows)

ISAM file name is invalid (xx...x).

The name of an ISAM file is longer than the system limit or invalid.

xx...x is a line number in the key definition parameter file or the name of the ISAM file.

(S)

Cancels processing.

(O)

Specify the correct name, and then re-execute the command.

KAIU056-E (UNIX)

Name for ISAM file is too long or invalid, line no. in key des parameter file: xx...x

The name for ISAM file is longer than the system limit or invalid.

xx...x is a line number in the key definition parameter file or the name of the ISAM file.

(S)

Cancels processing.

(O)

Specify the correct name, and then re-execute the command.

KAIU057-E (Windows)

ISAM file name must be specified (xx...x).

The name of an ISAM file is omitted.

xx...x is a line number in the key definition parameter file or a keyword.

(S)

Cancels processing.

(O)

Specify the correct name, and then re-execute the command.

KAIU057-E (UNIX)

Must specify name for ISAM file, line no. or keyword in key des parameter file: xx...x

The name for ISAM file is omitted.

xx...x is a line number in the key definition parameter file or a keyword.

(S)

Cancels processing.

(O)

Specify the correct name, and then re-execute the command.

KAIU058-E (Windows)

Data file record information must be specified (xx...x).

Data file information is omitted.

xx...x is a line number in the key definition parameter file or a keyword.

(S)

Cancels processing.

(O)

Specify the correct data file record information, and then re-execute the command.

KAIU058-E (UNIX)

Must specify record information, line no. or keyword in key des parameter file: xx...x

Data file information is omitted.

xx...x is a line number in the key definition parameter file or a keyword.

(S)

Cancels processing.

(O)

Specify the correct data file record information, and then re-execute the command.

KAIU059-E (Windows)

Record attributes must be specified (xx...x).

A record attribute is omitted.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct record attribute, and then re-execute the command.

KAIU059-E (UNIX)

Must specify record attribute, line no. in key des parameter file: xx...x

A record attribute is omitted.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct record attributes, and then re-execute the command.

KAIU060-E (Windows)

Record length must be specified (xx...x).

The record length is omitted.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct record length, and then re-execute the command.

KAIU060-E (UNIX)

Must specify record length, line no. in key des parameter file: xx...x

The record length is omitted.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct record length, and then re-execute the command.

KAIU061-E (Windows)

Key item name for parameter xx...x must be specified (yy...y).

A key item name is omitted in the parameter indicated by xx...x.

xx...x is a keyword.

yy...y is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct key item name, and then re-execute the command.

KAIU061-E (UNIX)

Must specify key item name in parameter indicated by keyword xx...x, line no. in key des parameter file: yy...y

A key item name is omitted in the parameter indicated by xx...x.

xx...x is a keyword.

yy...y is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct key item name, and then re-execute the command.

KAIU062-E (Windows)

Detailed information for key item must be specified (xx...x).

Detailed key information is omitted.

xx...x is a line number in the key definition parameter file or a keyword.

(S)

Cancels processing.

(O)

Specify the detailed key information correctly, and then re-execute the command.

KAIU062-E (UNIX)

Must specify detail information for key, line no. or keyword in key des parameter file: xx...x

Detailed key information is omitted.

xx...x is a line number in the key definition parameter file or a keyword.

(S)

Cancels processing.

(O)

Specify the correct detailed key information, and then re-execute the command.

KAIU063-E (Windows)

Key attribute must be specified (xx...x).

A key attribute is omitted.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct key attribute, and then re-execute the command.

KAIU063-E (UNIX)

Must specify key attribute, line no. in key des parameter file: xx...x

A key attribute is omitted.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct key attributes, and then re-execute the command.

KAIU064-E (Windows)

Key location must be specified (xx...x).

The key location is omitted.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct key location, and then re-execute the command.

KAIU064-E (UNIX)

Must specify key position, line no. in key des parameter file: xx...x

The key location is omitted.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct key location, and then re-execute the command.

KAIU065-E (Windows)

Key length must be specified (xx...x).

The key length is omitted.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct key length, and then re-execute the command.

KAIU065-E (UNIX)

Must specify key length, line no. in key des parameter file: xx...x

The key length is omitted.

xx...x is a line number in the key definition parameter file.

(S)

Cancels processing.

(O)

Specify the correct key length, and then re-execute the command.

KAIU066-E (Windows)

Key compression and duplicate information must be specified (xx...x).

Key compression and duplication information are omitted.

xx...x is a line number in the key definition parameter file or a keyword.

(S)

Cancels processing.

(O)

Specify the key compression and duplication information correctly, and then re-execute the command.

KAIU066-E (UNIX)

Must specify key compression or key duplication information, line no. or keyword in key des parameter file: xx...x

Key compression and duplication information are omitted.

xx...x is a line number in the key definition parameter file or a keyword.

(S)

Cancels processing.

(O)

Specify the key compression and duplication information correctly, and then re-execute the command.

KAIU067-E (Windows)

Sparse character must be specified (xx...x).

A sparse character is omitted.

xx...x is a line number in the key definition parameter file or a keyword.

(S)

Cancels processing.

(O)

Specify the correct sparse character, and then re-execute the command.

KAIU067-E (UNIX)

Must specify sparse character, line no. or keyword in key des parameter file: xx...x

A sparse character is omitted.

xx...x is a line number in the key definition parameter file or a keyword.

(S)

Cancels processing.

(O)

Specify the correct sparse character, and then re-execute the command.

KAIU068-E (Windows)

Parameter group in key definition parameter file is invalid (xx...x).

A parameter in the key definition parameter file is invalid.

xx...x is a key definition parameter filename.

(S)

Cancels processing.

(O)

Delete the invalid parameter, and then re-execute the command.

KAIU068-E (UNIX)

Invalid parameter group in key description parameter file xx...x

A parameter in the key definition parameter file is invalid.

xx...x is a key definition parameter filename.

(S)

Cancels processing.

(O)

Delete the invalid parameter, and then re-execute the command.

KAIU069-E (UNIX)

Invalid key description file xx...x: parameter cannot be output

The information in the key definition file is invalid, so key definition parameters cannot be output.

xx...x is the key definition filename.

(S)

Cancels key definition parameter output.

(O)

Re-create the ISAM file according to the procedure for recovering ISAM files.

KAIU071-E (Windows)

Key item name already exists (xx...x).

The same key item name is present in key definition information.

xx...x is the key item name.

(S)

Cancels processing.

(O)

Specify a different key item name, and then re-execute the command.

KAIU071-E (UNIX)

Key item name xx...x already exists in key description information

The same key item name already exists in key definition information.

xx...x is the key item name.

(S)

Cancels processing.

(O)

Specify a different key item name, and then re-execute the command.

KAIU072-E (Windows)

Cannot find key for the key item name specified (xx...x).

The specified key item name is not present in the key definition information.

Alternatively, the key file for the specified key item does not exist.

xx...x is the ISAM file name or key item name.

(S)

Cancels processing.

(O)

Specify the correct key item name, and then re-execute the command.

KAIU072-E (UNIX)

Cannot find key for specified key item name, ISAM file: xx...x

The specified key item name is not present in the key definition information.

Alternatively, the key file for the specified key item does not exist.

xx...x is the ISAM file name or key item name.

(S)

Cancels display of the contents of the record.

(O)

Check the specified key item name, and then re-execute the command.

KAIU083-E (Windows)

Execute the command from the administrator console.

This command must be executed on the administrator console.

(S)

Terminates command processing.

(O)

Execute the command on the administrator console.

KAIU100-E (Windows)

Error occurred during sort process.(xx...x).

An I/O error occurred when the work file was sorted while key files were being organized for an ISAM file. xx...x indicates the error number for the sort process.

(S)

Deletes all the key files that were being organized and the work file, and cancels processing on the ISAM file in which the error occurred.

(O)

Correct the cause of the error, and then re-execute the command.

KAIU100-E (UNIX)

I/O error on sort processing

An I/O error occurred when the work file was sorted while key files were being organized for an ISAM file.

(S)

Deletes all the key files that were being organized and the work file, and cancels processing on the ISAM file in which the error occurred.

(O)

Correct the cause of the error, and then re-execute the command.

KAIU101-E (Windows)

Record xx...x is invalid.

A record in the data file of the input ISAM file or in a sequential file is invalid.

xx...x is the name of the file in which the error occurred.

(S)

Cancels processing.

(O)

If the error occurred in an ISAM file, use the Jischk command to verify the file.

KAIU101-E (UNIX)

Input data file in ISAM file or record in sequential file is invalid, errored file: xx...x

A record in the data file of the input ISAM file or in a sequential file is invalid.

xx...x is the name of the file in which the error occurred.

(S)

Cancels processing.

(O)

If the error occurred in an ISAM file, verify that file with the Jischk command.

KAIU102-E (Windows)

Duplicate key value (xx...x).

The duplication of a key value was found when key files for which key value duplication is not allowed were organized.

xx...x is the key item name or key file name of the key that caused the error.

(S)

Deletes all the key files that were being organized, and cancels processing on the ISAM file in which the error occurred.

(O)

Correct the error, and then re-execute the command.

KAIU102-E (UNIX)

Key value is duplicated, key item name or key file name: xx...x

The duplication of a key value was found when key files for which key value duplication is not allowed were organized.

xx...x is the key item name or key file name of the key that caused the error.

(S)

Deletes all the key files that were being organized, and cancels processing on the ISAM file in which the error occurred.

In addition, the system generates a maintenance information file (ISAMxx...x.dmp1) under /usr/tmp or /tmp.

(O)

Correct the error, and then re-execute the command.

KAIU103-E (Windows)

Record format of input file and ISAM file are different.

In the Jisconv command, the record format is different between the specified input and output files.

(S)

Cancels processing.

(O)

Make sure that the record format is the same between the input and output files, and then re-execute the command.

KAIU103-E (UNIX)

Record in input file and output ISAM file must be in same format

In the Jisconv command, the record format is different between the specified input and output files.

(S)

Cancels processing.

(O)

Make sure that the record format is the same between the input and output files, and then re-execute the command.

KAIU104-E (Windows)

Cannot convert file (xx...x).

Key files could not be organized when a sequential file was converted into an ISAM file by using the Jisconv command.

xx...x is the organization level, and indicates the organized status of the ISAM file.

(S)

Deletes all the key files that were being organized, and cancels processing.

(O)

If the organization level is 001, correct the cause of the error, and then re-execute the command.

If the organization level is 002, use the Jiskeymnt command to reorganize the key, or re-execute the Jisconv command.

KAIU104-E (UNIX)

Cannot create key file on file conversion, level of creation: xx...x

Key files could not be organized when a sequential file was converted into an ISAM file with the Jisconv command.

xx...x is the organization level, and indicates the organized status of the ISAM file.

(S)

Deletes all the key files that were being organized, and cancels processing.

(O)

If the organization level is 001, correct the cause of the error, and then re-execute the command.

If the organization level is 002, reorganize the key with the Jiskeymnt command or re-execute the Jisconv command.

KAIU105-E (Windows)

Cannot compress file (xx...x).

Key files could not be organized while an ISAM file was being compressed by using the Jiscond command.

xx...x is the organization level, and indicates the organized status of the ISAM file.

(S)

Deletes all the key files that were being organized, and cancels processing.

(O)

If the organization level is 001, correct the error, and then re-execute the command.

If the organization level is 002, use the Jiskeymnt command to reorganize the key.

KAIU105-E (UNIX)

Cannot create key file on file compression, level of creation: xx...x

Key files could not be organized while an ISAM file was being compressed with the Jiscond command.

xx...x is the organization level, and indicates the organized status of the ISAM file.

(S)

Deletes all the key files that were being organized, and cancels processing.

(O)

If the organization level is 001, correct the cause of the error, and then re-execute the command.

If the organization level is 002, reorganize the key with the Jiskeymnt command.

KAIU106-E (Windows)

Input file is not sorted in primary key order.

The records in the input sequential file that was to be converted into an ISAM file are not sorted in the ISAM primary key order.

(S)

Deletes all the key files that were being organized, and cancels processing.

(O)

Sort the records in the sequential file in the primary key order, and then re-execute the command.

KAIU107-E (Windows)

I/O error in work file.

An I/O error occurred in the work file while key files were being organized for an ISAM file.

(S)

Deletes all the key files that were being organized and the work file, and cancels processing on the ISAM file in which the error occurred.

(O)

Correct the cause of the error, and then re-execute the command.

KAIU107-E (UNIX)

I/O error in work file.

An I/O error occurred in the work file while key files were being organized for an ISAM file.

(S)

Deletes all the key files that were being organized and the work file, and cancels processing on the ISAM file in which the error occurred.

(O)

Correct the cause of the error, and then re-execute the command.

KAIU108-E (Windows)

File format is invalid (xx...x)

The syntax of the sequential file indicated by xx...x is invalid, or the file is corrupted.

(S)

Cancels processing.

(O)

Correct the error, and then re-execute the command.

KAIU108-E (UNIX)

Invalid format on sequential file xx...x

The syntax of the sequential file indicated by xx...x is invalid, or the file is corrupted.

(S)

Cancels processing.

(O)

Correct the cause of the error, and then re-execute the command.

KAIU109-E (Windows)

Duplicate key range(xx...x).

The ISAM file cannot be converted because the range of integer keys or floating-point keys overlaps with the range of other keys.

If the ranges of keys in the parameter file overlap, xx...x indicates the parameter file name.

(S)

Cancels processing.

(O)

If the ranges of keys in the parameter file overlap, correct the cause of the error, and then re-execute the command.

KAIU300-I (Windows)

Jislckclear:The program was ended normally.

The Jislckclear command ended normally.

The KAIU314-I and KAIU315-I messages may be output before this message.

KAIU310-E (Windows)

Jislckclear:The user who performed does not have execution authority.

The user who attempted to execute the Jislckclear command does not have execution permission.

(S)

Cancels processing.

(O)

Execute the command as a user who has Administrators permissions.

KAIU311-E (Windows)

Jislckclear:The parameter is wrong.

A required option for the Jislckclear command is not specified, or an unusable option is specified.

(S)

Cancels processing.

(O)

Specify the correct option, and then re-execute the command.

KAIU312-I (Windows)

Jislckclear:The Processing was stopped, because any program which has accessed the ISAM file was not performed in this system.

The memory-mapped table does not exist because no executing program is accessing the ISAM file.

The file and records are not locked.

(S)

Cancels processing.

(O)

You do not need to execute the Jislckclear command because the file and records are not locked.

KAIU314-I (Windows)

Jislckclear:The occupancy state changed into the state where it does not occupy. (xx...x)

All the lock statuses owned by the process that no longer exists have been released.

xx...x indicates the number of lock statuses that were released. This message is output if the -d option is specified in the Jislckclear command. This message is not output if there is no lock information owned by the process that no longer exists.

KAIU315-I (Windows)

Jislckclear:There is unjust occupancy information. (xx...x)

Lock information owned by the process that no longer exists remains. xx...x indicates the number of items of lock information. This message is output if the -C option is specified in the Jislckclear command. This message is not output if there is no lock information owned by the process that no longer exists.

KAIU321-I (Windows)

Extraction of ISAM file will now start.

key item name: xx...x

ISAM file name: yy...y

Output file: zz...z

Extraction of valid records from the key file that corresponds to the key item name (xx...x) will now start.

yy...y is the ISAM file name.

zz...z is the name of a sequential file to which records are output.

KAIU321-I (UNIX)

Extraction of ISAM file will now start.

key item name: xx...x

ISAM file name: yy...y

Output file: zz...z

Extraction of valid records from the key file that corresponds to the key item name (xx...x) will now start.

yy...y is the ISAM file name.

zz...z is the name of a sequential file to which records are output.

KAIU322-I (Windows)

Checking of ISAM key file will now start.

key item name: xx...x

ISAM file name: yy...y

Verification of the logical structure of the key file that corresponds to the key item name (xx...x) will now start.

yy...y is the ISAM file name.

KAIU322-I (UNIX)

Checking of ISAM key file will now start.

key item name: xx...x

ISAM file name: yy...y

Verification of the logical structure of the key file that corresponds to the key item name (xx...x) will now start.

yy...y is the ISAM file name.

KAIU323-I (Windows)

The record has been successfully extracted from the key file.

key item name: xx...x

Number of extractions: yy...y

Number of registrations: zz...z

ISAM file name: aa...a

Output file: bb...b

All valid records were extracted from the key file that corresponds to the key item name (xx...x).

yy...y is the number of extracted records.

zz...z is the number of data records registered in the definition file.

aa...a is the ISAM file name.

bb...b is the name of a sequential file to which records were output.

KAIU323-I (UNIX)

The record has been successfully extracted from the key file.

key item name: xx...x

Number of extractions: yy...y

Number of registrations: zz...z

ISAM file name: aa...a

Output file: bb...b

All valid records were extracted from the key file that corresponds to the key item name (xx...x).

yy...y is the number of extracted records.

zz...z is the number of data records registered in the definition file.

aa...a is the ISAM file name.

bb...b is the name of a sequential file to which records were output.

KAIU324-I (Windows)

The state of the key file is normal.

key item name: xx...x

Number of extractable items: yy...y

Number of registrations: zz...z

ISAM file name: aa...a

The verified result of the logical structure of the key file that corresponds to the key item name (xx...x) is normal.

yy...y is the number of extractable records as a result of verification of the logical structure.

zz...z is the number of data records registered in the definition file.

aa...a is the ISAM file name.

KAIU324-I (UNIX)

The state of the key file is normal.

key item name: xx...x

Number of extractable items: yy...y

Number of registrations: zz...z

ISAM file name: aa...a

The verified result of the logical structure of the key file that corresponds to the key item name (xx...x) is normal.

yy...y is the number of extractable records as a result of verification of the logical structure.

zz...z is the number of data records registered in the definition file.

aa...a is the ISAM file name.

KAIU325-I (Windows)

The record was successfully extracted from the key file, even though an unmanaged record existed.

key item name: xx...x

Number of extractions: yy...y

Number of registrations: zz...z

ISAM file name: aa...a

Output file: bb...b

The data file contains a record that is not managed in the key file that corresponds to the key item name (xx...x). Therefore, only managed valid records were extracted to the sequential file (bb...b).

yy...y is the number of extracted records.

zz...z is the number of data records registered in the definition file.

aa...a is the ISAM file name.

KAIU325-I (UNIX)

The record was successfully extracted from the key file, even though an unmanaged record existed.

key item name: xx...x

Number of extractions: yy...y

Number of registrations: zz...z

ISAM file name: aa...a

Output file: bb...b

The data file contains a record that is not managed in the key file that corresponds to the key item name (xx...x). Therefore, only managed valid records were extracted to the sequential file (bb...b).

yy...y is the number of extracted records.

zz...z is the number of data records registered in the definition file.

aa...a is the ISAM file name.

KAIU326-W (Windows)

The record was extracted, but part of the operation cannot be guaranteed.

key item name: xx...x

Number of extractions: yy...y

Number of registrations: zz...z

ISAM file name: aa...a

Output file: bb...b

Key information managed in the key file that corresponds to the key item name (xx...x) and key information for the records in the data file do not match. Therefore, only valid records were extracted to the sequence file (bb...b), excluding records whose format was invalid.

yy...y is the number of extracted records.

zz...z is the number of data records registered in the definition file.

aa...a is the ISAM file name.

(S)

Cancels the processing of the key file and verifies the next key file.

(O)

Check the output message.

KAIU326-W (UNIX)

The record was extracted, but part of the operation cannot be guaranteed.

key item name: xx...x

Number of extractions: yy...y

Number of registrations: zz...z

ISAM file name: aa...a

Output file: bb...b

Key information managed in the key file that corresponds to the key item name (xx...x) and key information for the records in the data file do not match. Therefore, only valid records were extracted to the sequence file (bb...b), excluding records whose format is invalid.

yy...y is the number of extracted records.

zz...z is the number of data records registered in the definition file.

aa...a is the ISAM file name.

(S)

Cancels the processing of the key file and verify the next key file.

(O)

Check the output message.

KAIU327-I (Windows)

The key file can now be extracted.

key item name: xx...x

Number of extractable items: yy...y

Number of registrations: zz...z

ISAM file name: aa...a

The data file contains a record that is not managed in the key file that corresponds to the key item name (xx...x). However, records can be extracted.

yy...y is the number of extractable records as a result of verification of the key file.

zz...z is the number of data records registered in the definition file.

aa...a is the ISAM file name.

KAIU327-I (UNIX)

The key file can now be extracted.

key item name: xx...x

Number of extractable items: yy...y

Number of registrations: zz...z

ISAM file name: aa...a

There are records in the data file, which are not managed in the key file that corresponds to the key item name (xx...x). However, records can be extracted.

yy...y is the number of extractable records as a result of verification of the key file.

zz...z is the number of data records registered in the definition file.

aa...a is the ISAM file name.

KAIU328-W (Windows)

The integrity of part of the key file cannot be guaranteed.

key item name: xx...x

Number of extractable items: yy...y

Number of registrations: zz...z

ISAM file name: aa...a

Key information managed in the key file that corresponds to the key item name (xx...x) and key information for the records in the data file do not match. Alternatively, the data file contains a record that has an invalid format.

yy...y is the number of extractable records as a result of verification of the key file.

zz...z is the number of data records registered in the definition file.

aa...a is the ISAM file name.

(S)

Cancels the processing of the key file and verify the next key file.

(O)

Check the output message.

KAIU328-W (UNIX)

The integrity of part of the key file cannot be guaranteed.

key item name: xx...x

Number of extractable items: yy...y

Number of registrations: zz...z

ISAM file name: aa...a

Key information managed in the key file that corresponds to the key item name (xx...x) and key information for the records in the data file do not match. Alternatively, the data file contains a record that has an invalid format.

yy...y is the number of extractable records as a result of verification of the key file.

zz...z is the number of data records registered in the definition file.

aa...a is the ISAM file name.

(S)

Cancels the processing of the key file and verify the next key file.

(O)

Check the output message.

KAIU329-E (Windows)

An error occurred during processing to extract the file.

key item name: xx...x

ISAM file name: yy...y

An error occurred while valid records were being extracted from the key file that corresponds to the key item name (xx...x).

yy...y is the ISAM file name.

(S)

Cancels processing.

(O)

Re-execute the command by specifying 1 for the -l option, and then check the detailed error message information.

KAIU329-E (UNIX)

An error occurred during processing to extract the file.

key item name: xx...x

ISAM file name: yy...y

An error occurred while valid records were being extracted from the key file that corresponds to the key item name (xx...x).

yy...y is the ISAM file name.

(S)

Cancels processing.

(O)

Re-execute the command by specifying 1 for the -l option, and then check the detailed error message information.

KAIU330-E (Windows)

An error occurred during processing to verify the key file.

key item name: xx...x

ISAM file name: yy...y

An error occurred during verification of the logical structure of the key file that corresponds to the key item name (xx...x).

yy...y is the ISAM file name.

(S)

Cancels processing.

(O)

Re-execute the command by specifying 1 for the -l option, and then check the detailed error message information.

KAIU330-E (UNIX)

An error occurred during processing to verify the key file.

key item name: xx...x

ISAM file name: yy...y

An error occurred during verification of the logical structure of the key file that corresponds to the key item name (xx...x).

yy...y is the ISAM file name.

(S)

Cancels processing.

(O)

Re-execute the command by specifying 1 for the -l option, and then check the detailed error message information.

KAIU331-E (Windows)

An error occurred during processing to verify the key file.

key item name: xx...x

ISAM file name: yy...y

An error occurred during verification of the logical structure of the key file that corresponds to the key item name (xx...x).

yy...y is the ISAM file name.

(S)

Cancels processing.

(O)

Re-execute the command by specifying 1 for the -l option, and then check the detailed error message information.

KAIU331-E (UNIX)

An error occurred during processing to verify the key file.

key item name: xx...x

ISAM file name: yy...y

An error occurred during verification of the logical structure of the key file that corresponds to the key item name (xx...x).

yy...y is the ISAM file name.

(S)

Cancels processing.

(O)

Re-execute the command by specifying 1 for the -l option, and then check the detailed error message information.

KAIU332-W (Windows)

The previous pointer on the first leaf page is invalid.

key item name: xx...x

ISAM file name: yy...y

Offset: zz...z

The first leaf page of the key file that corresponds to the key item name (xx...x) is in a half-finished state. However, records can be extracted.

yy...y is the ISAM file name.

zz...z (hexadecimal number) is the offset of the first leaf page.

(S)

Continues processing.

(O)

Check the contents.

KAIU332-W (UNIX)

The previous pointer on the first leaf page is invalid.

key item name: xx...x

ISAM file name: yy...y

Offset: zz...z

The first leaf page of the key file that corresponds to the key item name (xx...x) is in a half-finished state. However, records can be extracted.

yy...y is the ISAM file name.

zz...z (hexadecimal number) is the offset of the first leaf page.

(S)

Continues processing.

(O)

Check the contents.

KAIU333-W (Windows)

The leaf page does not match the record key. key item name: xx...x ISAM file name: yy...y Offset: zz...z

There is a record whose key information in the data file does not match the key information managed in the key file that corresponds to the key item name (xx...x). However, records can be extracted.

yy...y is the ISAM file name.

zz...z (hexadecimal number) is the offset of the record whose key information does not match.

(S)

Cancels the processing of the key file.

(O)

Check the contents of the file.

KAIU333-W (UNIX)

The leaf page does not match the record key. key item name: xx...x ISAM file name: yy...y Offset: zz...z

There are records whose key information in the data file does not match the key information managed in the key file that corresponds to the key item name (xx...x). However, records can be extracted.

yy...y is the ISAM file name.

zz...z is the offset of the record whose key information does not match.

(S)

Cancels the processing of the key file.

(O)

Check the contents of the file.

KAIU334-E (Windows)

The next pointer on the leaf page is invalid.

key item name: xx...x

ISAM file name: yy...y

Offset: zz...z

Records cannot be extracted because the key file that corresponds to the key item name (xx...x) contains an invalid leaf page.

yy...y is the ISAM file name.

zz...z (hexadecimal number) is the offset of the invalid leaf page.

(S)

Cancels the processing of the key file.

(O)

Re-create the file.

KAIU334-E (UNIX)

The next pointer on the leaf page is invalid.

key item name: xx...x

ISAM file name: yy...y

Offset: zz...z

Records cannot be extracted because the key file that corresponds to the key item name (xx...x) contains an invalid leaf page.

yy...y is the ISAM file name.

zz...z (hexadecimal number) is the offset of the invalid leaf page.

(S)

Cancels the processing of the key file.

(O)

Re-create the file.

KAIU335-E (Windows)

The next pointer on the leaf page is duplicated.

key item name: xx...x

ISAM file name: yy...y

Offset: zz...z

Records cannot be extracted because of the invalid structure of the leaf page in the key file that corresponds to the key item name (xx...x).

yy...y is the ISAM file name.

zz...z (hexadecimal number) is the offset of the leaf page whose structure is invalid.

(S)

Cancels the processing of the key file.

(O)

Re-create the file.

KAIU335-E (UNIX)

The next pointer on the leaf page is duplicated.

key item name: xx...x

ISAM file name: yy...y

Offset: zz...z

Records cannot be extracted because of the invalid structure of the leaf page in the key file that corresponds to the key item name (xx...x).

yy...y is the ISAM file name.

zz...z (hexadecimal number) is the offset of the leaf page whose structure is invalid.

(S)

Cancels the processing of the key file.

(O)

Re-create the file.

KAIU336-E (Windows)

The keys are not arranged in ascending or descending order.

key item name: xx...x

ISAM file name: yy...y

Offset: zz...z

Records cannot be extracted because the keys are not arranged in ascending or descending order in the key file that corresponds to the key item name (xx...x).

yy...y is the ISAM file name.

zz...z (hexadecimal number) is the offset of the leaf page whose structure is invalid.

(S)

Cancels the processing of the key file.

(O)

Re-create the file.

KAIU336-E (UNIX)

The keys are not arranged in ascending or descending order.

key item name: xx...x

ISAM file name: yy...y

Offset: zz...z

Records cannot be extracted because the keys are not arranged in ascending or descending order in the key file that corresponds to the key item name (xx...x).

yy...y is the ISAM file name.

zz...z (hexadecimal number) is the offset of the leaf page whose structure is invalid.

(S)

Cancels the processing of the key file.

(O)

Re-create the file.

KAIU337-E (Windows)

The same record offset is managed from the key. key item name: xx...x ISAM file name: yy...y Offset: zz...z

Records cannot be extracted because, in the key file that corresponds to the key item name (xx...x), the same record is managed from the different key information.

yy...y is the ISAM file name.

zz...z (hexadecimal number) is the offset of the leaf page that contains duplicated key information.

(S)

Cancels the processing of the key file.

(O)

Re-create the file.

KAIU337-E (UNIX)

The same record offset is managed from the key. key item name: xx...x ISAM file name: yy...y Offset: zz...z

Records cannot be extracted because, in the key file that corresponds to the key item name (xx...x), the same record is managed from the different key information.

yy...y is the ISAM file name.

zz...z (hexadecimal number) is the offset of the leaf page that contains duplicated key information.

(S)

Cancels the processing of the key file.

(O)

Re-create the file.

KAIU338-W (Windows)

An invalid record exists. ISAM file name: xx...x Offset: yy...y

The data file contains an invalid fixed-length record.

xx...x is the ISAM file name.

yy...y (hexadecimal number) is the offset of the invalid fixed-length record.

(S)

Skips an invalid record and continues processing.

(O)

Check the contents of the file.

KAIU338-W (UNIX)

An invalid record exists. ISAM file name: xx...x Offset: yy...y

The data file contains an invalid fixed-length record.

xx...x is the ISAM file name.

yy...y (hexadecimal number) is the offset of the invalid fixed-length record.

(S)

Skips an invalid record and continues processing.

(O)

Check the contents of the file.

KAIU339-W (Windows)

An invalid variable-length record exists. ISAM file name: xx...x Offset: yy...y

The data file contains an invalid variable-length record.

xx...x is the ISAM file name.

yy...y (hexadecimal number) is the offset of the invalid variable-length record.

(S)

Skips an invalid record and continues processing.

(O)

Check the contents of the file.

KAIU339-W (UNIX)

An invalid variable-length record exists. ISAM file name: xx...x Offset: yy...y

The data file contains an invalid variable-length record.

xx...x is the ISAM file name.

yy...y (hexadecimal number) is the offset of the invalid variable-length record.

(S)

Skips an invalid record and continues processing.

(O)

Check the contents of the file.

KAIU340-W (Windows)

A record not managed from the key file exists.

key item name: xx...x

ISAM file name: yy...y

Offset: zz...z

Offset: zz...z

...

There is a record that is not managed by the key file that corresponds to the key item name (xx...x).

yy...y is the ISAM file name.

zz...z (hexadecimal number) is the offset of the record that is not managed by the key file.

(S)

Continues processing.

(O)

Check the contents of the file.

KAIU340-W (UNIX)

A record not managed from the key file exists.

key item name: xx...x

ISAM file name: yy...y

Offset: zz...z

Offset: zz...z

...

There is a record that is not managed by the key file that corresponds to the key item name (xx...x).

yy...y is the ISAM file name.

zz...z (hexadecimal number) is the offset of the record that is not managed by the key file.

(S)

Continues processing.

(O)

Check the contents of the file.

KAIU341-E (Windows)

The Directory is not found. Directory name: xx...x Error code: yy...y

The directory (xx...x) in which the sort work file specified in the -T or -d option is to be created does not exist.

yy...y is a system error code.

(S)

Cancels processing.

(O)

Specify a correct directory, and then re-execute the command.

KAIU341-E (UNIX)

The Directory is not found. Directory name: xx...x Error code: yy...y

The directory (xx...x) in which the sort work file that is specified in the -T or -d option is to be created does not exist.

yy...y is a system error code.

(S)

Cancels processing.

(O)

Specify a correct directory, and then re-execute the command.

KAIU342-W (Windows)

A definition file entry does not match the number of key file records.

key item name: xx...x

Number of valid records: yy...y

Number of registrations: zz...z

ISAM file name: aa...a

The number of valid records managed in the key file that corresponds to the key item name (xx...x) and the number of records registered in the definition file do not match.

yy...y is the number of valid records managed in the key file.

zz...z is the number of data records registered in the definition file.

aa...a is the ISAM file name.

(S)

Continues processing.

(O)

Check the contents of the file.

KAIU342-W (UNIX)

A definition file entry does not match the number of key file records.

key item name: xx...x

Number of valid records: yy...y

Number of registrations: zz...z

ISAM file name: aa...a

The number of valid records managed in the key file that corresponds to the key item name (xx...x) and the number of records registered in the definition file do not match.

yy...y is the number of valid records managed in the key file.

zz...z is the number of data records registered in the definition file.

aa...a is the ISAM file name.

(S)

Continues processing.

(O)

Check the contents of the file.

KAIU343-W (Windows)

A definition file entry does not match the number of data file records.

Number of valid records: xx...x

Number of registrations: yy...y

ISAM file name: zz...z

The number of valid records in the data file and the number of records registered in the definition file do not match.

xx...x is the number of valid records in the data file.

yy...y is the number of records registered in the definition file do not match.

zz...z is the ISAM file name.

(S)

Continues processing.

(O)

Check the contents of the file.

KAIU343-W (UNIX)

A definition file entry does not match the number of data file records.

Number of valid records: xx...x

Number of registrations: yy...y

ISAM file name: zz...z

The number of valid records in the data file and the number of records registered in the definition file do not match.

xx...x is the number of valid records in the data file.

yy...y is the number of records registered in the definition file do not match.

zz...z is the ISAM file name.

(S)

Continues processing.

(O)

Check the contents of the file.

KAIU344-W (Windows)

The data file size is invalid. ISAM file name: xx...x Data size: yy...y

The size of the data file of the fixed-length ISAM file (xx...x) is invalid.

yy...y (hexadecimal number) is the size of the data file.

(S)

Skip the verification of the data file and then continue the processing.

(O)

Check the contents of the file.

KAIU344-W (UNIX)

The data file size is invalid. ISAM file name: xx...x Data size: yy...y

The size of the data file of the fixed-length ISAM file (xx...x) is invalid.

yy...y (hexadecimal number) is the size of the data file.

(S)

Skip the verification of the data file and then continue the processing.

(O)

Check the contents of the file.

KAIU345-E (Windows)

The file is not found. File name: xx...x Error code: yy...y

The specified file name (xx...x) does not exist.

yy...y is a system error code.

(S)

Cancels processing.

(O)

Make sure that the file exists.

KAIU345-E (UNIX)

The file is not found. File name: xx...x Error code: yy...y

The specified file name (xx...x) does not exist.

yy...y is a system error code.

(S)

Cancels processing.

(O)

Make sure that the file exists.

KAIU346-E (Windows)

You do not have permission to access this directory. Directory name: xx...x Error code: yy...y

The directory (xx...x) in which the sort work file specified in the -T or -d option is to be created does not exist.

yy...y is a system error code.

(S)

Cancels processing.

(O)

Make sure that the file exists.

KAIU346-E (UNIX)

You do not have permission to access this directory. Directory name: xx...x Error code: yy...y

The directory (xx...x) in which the sort work file that is specified in the -T or -d option is to be created does not exist.

yy...y is a system error code.

(S)

Cancels processing.

(O)

Make sure that the file exists.

KAIU347-I (Windows)

Checking of ISAM data file will now start.

ISAM file name: xx...x

Verification of the data file of the ISAM file (xx...x) will now start.

KAIU347-I (UNIX)

Checking of ISAM data file will now start.

ISAM file name: xx...x

Verification of the data file of the ISAM file (xx...x) will now start.

KAIU348-I (Windows)

Checking of ISAM data file was finished normally.

ISAM file name: xx...x

Verification of the data file of the ISAM file (xx...x) ended successfully.

KAIU348-I (UNIX)

Checking of ISAM data file was finished normally.

ISAM file name: xx...x

Verification of the data file of the ISAM file (xx...x) ended successfully.

KAIU349-E (Windows)

The extension of the specified file is invalid.(xx...x)

An extension used by ISAM was specified for the extension of a sequential file.

xx...x is the specified sequential file.

(S)

Cancels processing.

(O)

Specify an extension that is not used by ISAM, and then re-execute the command.

KAIU349-E (UNIX)

The extension of the specified file is invalid.(xx...x)

An extension used by ISAM was specified for the extension of a sequential file.

xx...x is the specified sequential file.

(S)

Cancels processing.

(O)

Specify an extension that is not used by ISAM, and then re-execute the command.

KAIU350-E (Windows)

The name of the output file is too long or it is invalid. xx...x

The name specified for the sequential file xx...x is longer than the system limit or invalid.

(S)

Cancels processing.

(O)

Specify the correct name, and then re-execute the command.

KAIU350-E (UNIX)

The name of the output file is too long or it is invalid. xx...x

The name specified for the sequential file xx...x is longer than the system limit or invalid.

(S)

Cancels processing.

(O)

Specify the correct name, and then re-execute the command.

KAIU989-E (Windows)

A message cannot be read. (maintenance-information)

A message cannot be read.

(S)

Terminates command processing.

(O)

Make sure that the following file exists and that you have read permission for it, and then re-execute the command.

installation-folder\jp1base\bin\Jutilmsg.dll

KAIU991-E (Windows)

Insufficient memory.

There is not enough memory.

(S)

Cancels processing.

(O)

Perform the processing when enough memory can be allocated.

KAIU991-E (UNIX)

Memory shortage occurred.

There is not enough memory.

(S)

Cancels processing.

(O)

Perform the processing when enough memory can be allocated.

KAIU998-E (Windows)

Program logic error (xx...x y...y).

A logical error in the program occurred.

xx...x and yy...y indicate the causes of the error.

(S)

Cancels processing.

(O)

Contact the system administrator.

KAIU998-E (UNIX)

Error on program logic, reason: xx...x, yy...y

A logical program error occurred.

xx...x and yy...y indicate the causes of the error.

(S)

Cancels processing.

(O)

Contact the system administrator.

KAIU999-E (Windows)

System call error.

An error occurred in a system call.

(S)

Cancels processing.

(O)

Correct the cause of the error, and then re-execute the command.

KAIU999-E (UNIX)

Error on system call

(S)

Cancels processing.

(O)

Correct the cause of the error, and then re-execute the command.

KAIU999-E

System call error. xx...x yy...y zz...z

xx...x, yy...y, and zz...z indicate the causes of the error.

(S)

Cancels processing.

(O)

Correct the cause of the error indicated by yy...y, and then re-execute the command.

2.13 Inter-process messages (KNAM1001 to KNAM1514)

KNAM1001-I

The interprocess communication daemon will now start.

KNAM1002-I

The interprocess communication daemon will now stop.

KNAM1003-E

The interprocess communication daemon will now stop due to an error that prevents processing.

(S)

Terminates the daemon abnormally.

(O)

See the operator's action provided in the message that was output immediately before this message.

KNAM1004-E

An attempt to initialize Windows Socket has failed. (error number = error-number)

(S)

Terminates the processing abnormally.

(O)

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

KNAM1005-E

An error occurred during initialization of the communications base. (error number = error-number)

(S)

Terminates the processing abnormally.

(O)

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

KNAM1006-E

An attempt to obtain the name of the local host has failed. (error number = error-number)

(S)

Terminates the processing abnormally.

(O)

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

KNAM1007-E

An attempt to initialize the common definition has failed. (error number = error-number)

(S)

Terminates the processing abnormally.

(O)

If an error occurred on a physical host, reinstall JP1/Base. If an error occurred on a logical host, set up the logical host again. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KNAM1008-E

definition-name could not be acquired from the common definition. (error number = error-number)

Definition information indicated by definition-name could not be obtained from the common definition.

(S)

Terminates the processing abnormally.

(O)

If an error occurred on a physical host, reinstall JP1/Base. If an error occurred on a logical host, set up the logical host again. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KNAM1009-E

An attempt to initialize the integrated trace log has failed. (error number = error-number)

(S)

Terminates the processing abnormally.

(O)

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

KNAM1010-W

An attempt to acquire a port number has failed. (service name = service-name, error number = error-number)

A port number cannot be obtained from the service name that was output to detailed information.

(S)

Continues processing using the default port number (20600).

(O)

Make sure that the service name output to detailed information is defined in the services file. If it is not defined, reinstall JP1/Base. If it is defined, use the data collection tool to collect data, and then contact the system administrator.

KNAM1012-I

The configuration file was successfully read. (file name = file-name, last updated = last-updated-time)

The interprocess communication daemon read the definition information file.

The path to the definition information file and last updated time are output to detailed information.

KNAM1014-E

Communication with the local host has failed. (detailed-information)

Communication within the same host failed for the reason shown in detailed-information.

(S)

If an error occurred during startup of the interprocess communication daemon, the system terminates the processing. If an error occurred during the processing of a request from the program, the system cancels the target processing and continues other processing.

(O)

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

KNAM1015-I

The interprocess communication daemon has started.

KNAM1016-E

An error occurred in a system call. (function name = function-name, error number = error-number)

(S)

See the system action shown in the message output after this message.

(O)

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

KNAM1020-E

subprocess will now stop due to an error that prevents processing.

(S)

Terminates the subprocess abnormally.

(O)

See the operator's action provided in the message that was output immediately before this message.

KNAM1023-E

An invalid environment error occurred. (detailed-information)

Action information required for installation is not defined.

(S)

Terminates the processing abnormally.

(O)

Reinstall JP1/Base.

KNAM1024-E

A logic error occurred.

(S)

Terminates the processing abnormally.

(O)

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

KNAM1025-E

The installation path of JP1/Base is too long.

(S)

Terminates the processing abnormally.

(O)

Uninstall JP1/Base, and then reinstall it using a path of the appropriate length.

KNAM1026-E

An attempt to start subprocess has failed. (function name = function-name, error number = error-number)

(S)

Terminates the processing abnormally.

(O)

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

KNAM1027-E

A timeout occurred during communication with the local host. (destination = connection-destination-subprocess-name)

(S)

Terminates the processing abnormally.

(O)

There might be abnormal processing load on the machine. Restart the machine when it has a light processing load. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KNAM1028-E

Invalid data was received during communication with the local host. (invalid data = invalid-data)

(S)

Cancels the processing requested from the program where an error occurred, and continues processing.

(O)

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

KNAM1029-E

subprocess terminated abnormally.

(S)

Terminates the subprocess abnormally.

(O)

See the operator's action provided in the message that was output immediately before this message.

KNAM1038-W

An attempt to distribute processing has failed.

(S)

Although the performance of the program might be degraded, the system continues processing.

(O)

See the operator's action provided in the message that was output immediately before this message.

KNAM1040-E

Distributed processing terminated abnormally.

(S)

Continues processing.

(O)

See the operator's action provided in the message that was output immediately before this message.

KNAM1049-W

An attempt to acquire definition-name from the common definition has failed. (default-value will be assumed)

The definition information indicated by definition-name could not be acquired from the common definition.

(S)

Continues processing, assuming the default value shown in detailed information.

(O)

If an error occurred on a physical host, reinstall JP1/Base. If an error occurred on a logical host, set up the logical host again. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KNAM1050-E

An attempt to resolve a local hostname has failed. (hostname = host-name, error number = error-number)

(S)

Terminates the processing abnormally.

(O)

Check and, if necessary, revise the settings for jp1hosts, hosts, or DNS.

KNAM1051-E

A valid IP address is not registered in the local host.

(S)

Terminates the processing abnormally.

(O)

Check and, if necessary, revise the settings for jp1hosts, hosts, or DNS.

KNAM1054-E

An attempt to resolve host-name has failed. (error number = error-number)

(S)

Cancels the processing requested from the program where an error occurred, and continues processing.

(O)

Check and, if necessary, revise the settings for jp1hosts, hosts, or DNS.

KNAM1055-E

An error status of a communication socket has been detected. (error number = error-number)

(S)

Disconnects the session of the communication socket where an error occurred, and continues processing.

(O)

Make sure that the system can communicate normally with the connection destination host.

KNAM1060-E

Invalid data was received from the remote host.

(S)

Cancels the processing requested from the program where an error occurred, and continues processing.

(O)

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

KNAM1061-E

Communication with host-name has failed.

An error occurred in the communication between hosts.

(S)

Continues processing.

(O)

Check the error message that was output immediately before this message, and then take action according to the cause of the error.

KNAM1062-E

An attempt to report the status to the process management has failed.

(S)

Terminates the processing abnormally.

(O)

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

KNAM1063-E

An attempt to acquire a request from the process management has failed.

(S)

Terminates the processing abnormally.

(O)

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

KNAM1064-E

An error occurred in the health check function. (function name = function-name, error number = error-number)

(S)

Continues processing.

(O)

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

KNAM1067-W

An attempt to notify process management of startup of a grandchild process has failed. (error number = error-number)

(S)

Continues processing.

(O)

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

KNAM1068-W

An attempt to notify process management of termination of a grandchild process has failed. (error number = error-number)

(S)

Continues processing.

(O)

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

KNAM1069-E

The security level is not defined.

(S)

Continues processing.

(O)

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

KNAM1070-E

The applicable security level is not defined.

(S)

Continues processing.

(O)

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

KNAM1071-W

An invalid line in the configuration file was ignored. (token= token, line = line-number)

(S)

Continues processing.

(O)

Correct the error in the operation settings file, and then re-execute the jbs_spmd_reload command.

KNAM1084-E

An error occurred in a connect. (source = IP-address, target = IP-address, error number = error-number)

(S)

Continues processing.

(O)

To correct the cause of the error, check the environment to make sure that:

The network is in the normal status.

Both the local host and the connection destination use the same IP address version (IPv4 or IPv6).

JP1/Base is running on the connection destination.

If the problem cannot be corrected, use the data collection tool to collect data for the local host and the connection destination, and then contact the system administrator.

For details about how to check the IP address version (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the Job Management Partner 1/Base User's Guide.

KNAM1088-E

An attempt was made to connect to the local host as a remote host. (target=host-name-or-IP-address)

(S)

Continues processing.

(O)

Make sure that:

The IP address of the connection destination is not included in the local host's IP address list in the jp1hosts information, the hosts file, or the DNS settings.

Binding of remote host IP addresses is disabled in the OS communication settings.

In Linux, if 1 is set for net.ipv4.ip_nonlocal_bind, remote host IP addresses can be bound. If 1 is set, change the value to 0, and then restart JP1/Base or the OS.

KNAM1093-E

No IP addresses exist that can connect to the remote host. (target = connection-target-IP-address)

An IP address of the type (IPv4 or IPv6) that can connect to the remove host is not assigned.

(S)

Cancels the processing requested from the program where an error occurred, and continues processing.

(O)

If JP1/Base is operating with the ANY binding method, set anybind_all.conf.

If JP1/Base is operating with the IP binding method, specify the valid IPv4 address or IPv6 address on the local host.

KNAM1500-E

A specified argument contains an error.

(S)

Terminates the processing abnormally.

(O)

Specify a proper argument on the command line.

KNAM1501-E

The user lacks permission to execute this command.

(S)

Terminates the command abnormally.

(O)

Re-execute the command as a user who has Administrators permissions.

KNAM1505-E

An attempt to acquire Path00 from the registry has failed. (detailed-information)

(S)

Terminates the processing abnormally.

(O)

Re-install JP1/Base.

KNAM1509-I

A JP1 service was registered. (JP1 service name = JP1-service-name, JP1 port number = JP1-port-number)

KNAM1511-E

An attempt to open a file has failed. (file name = file-name, function name=function-name, error number = error-number)

(S)

Terminates the processing abnormally.

(O)

Make sure that the indicated file can be opened in write mode.

KNAM1513-E

A message cannot be read. (maintenance-information)

A message string for display or logging cannot be read.

(S)

Continues processing.

(O)

Make sure that you can access the following file:

In UNIX: /opt/jp1base/lib/nls/C/jbscom.cat

KNAM1514-I

The specified JP1 service already exists. (JP1 service name=JP1-service-name)

2.14 Operating information acquisition messages (KNAM2000 to KNAM2012)

KNAM2000-E

A command option is specified incorrectly.

The specified command option contains an error.

(S)

Terminates command processing.

(O)

Make sure that the command argument is correct, and then re-execute the command.

KNAM2001-E

The user does not have permission to execute the command.

A user who does not have operator privileges attempted to execute the command. In Windows, the user was not a member of the Administrators group. In UNIX the user did not have root privileges or JP1/Base administrator privileges.

(S)

Terminates command processing.

(O)

Re-execute the command as a user who has operator privileges.

KNAM2002-E

Execute the command from the administrator console.

This command must be executed on the administrator console.

(S)

Terminates command processing.

(O)

Execute the command on the administrator console.

KNAM2003-E

Operation information for the specified service does not exist. (host = host-name, service = operation-information-name,...)

Operation information for the specified service does not exist.

(S)

Terminates command processing.

(O)

Make sure that:

The specified service is running on the specified host.

Operation information has been successfully created (the KNAM2008-E or KNAM2009-E message is not output to the integrated trace log at startup of the service).

If the specified service is not running, start the service and then re-execute the command. If operation information could not be created, remove the cause of the error, restart the service, and then re-execute the command. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KNAM2004-E

Reload information for the specified service is not up to date. (host = host-name, service = operation-information-name)

Reload information is not reflected in the operation information.

(S)

Terminates command processing.

(O)

Make sure that:

Operation information has been successfully created (the KNAM2008-E or KNAM2009-E message is not output to the integrated trace log during reload processing).

If operation information could not be created, remove the cause of the error, restart the service, and then re-execute the command. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KNAM2005-E

The operation information file is being used. (host = host-name, service = operation-information-name)

The operation information file is being used by another process.

(S)

Terminates command processing.

(O)

Make sure that:

The specified host service is not running or is not being reloaded.

The operation information acquisition command is not executed simultaneously.

If the specified service is running or is being reloaded, wait until the service starts or the reload processing finishes, and then re-execute the command. If the operation information acquisition command is executed simultaneously, check and revise the operation so that the command is not executed simultaneously. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KNAM2006-E

Memory is insufficient.

Enough memory required for the processing could not be allocated.

(S)

Terminates command processing.

(O)

Terminate other programs that might be using memory, and then re-execute the command.

KNAM2007-E

An attempt to acquire operation information has failed. (host = host-name, service = operation-information-name)

An attempt to acquire operation information has failed.

(S)

Terminates command processing.

(O)

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

KNAM2008-E

An attempt to initialize output for operation information has failed. (host=host-name, service=service-name, code=error-code)

Output processing of operating information could not be initialized.

(S)

Continues processing.

(O)

If error-code is 254 (insufficient memory):

Make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

If error-code is not 254:

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

KNAM2009-E

An attempt to output operation information has failed. (host=host-name, service=service-name, code=error-code)

Operating information could not be output.

(S)

Continues processing.

(O)

If error-code is 254 (insufficient memory):

Make sure that there has been no severe deterioration in OS resources, available memory, or the communication environment.

If error-code is not 254:

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

KNAM2010-E

An attempt to terminate output for operation information has failed. (host=host-name, service=service-name, code=error-code)

Output processing of operating information could not be terminated.

(S)

Continues processing.

(O)

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

KNAM2011-E

The logical host logical-host-name does not exist.

The specified logical host does not exist.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified on the command line is correct, and that the value in the JP1_HOSTNAME environment variable is correct.

KNAM2012-E

The operation information file is corrupted. (host = host-name, service = operation-information-name)

The operation information file is corrupted.

(S)

Terminates command processing.

(O)

Operation information cannot be acquired because the operation information file is corrupted. If you reload the definition of the relevant service, you can acquire part or all of the operation information.

If you cannot acquire all the operation information, restart the relevant service, and then you can acquire all the operation information retained by that service.

If the problem cannot be corrected even after the relevant service is restarted, use the data collection tool to collect data, and then contact the system administrator.

2.15 Local action messages (KNAM3000 to KNAM3369)

KNAM3000-I

A local action process has started.

A local action process has started.

KNAM3010-I

The local action function will now start. (last updated = YYYY/MM/DD hh:mm:ss)

The local action function will now start. The last updated time is the date and time when the local action execution definition file was last updated.

KNAM3016-I

The local action function will now stop.

The local action function will now stop.

KNAM3017-E

An invalid request was received from the process management function.

The local action will now stop because an invalid request was issued from the process management function.

(S)

Stops the process.

(O)

Check whether the process management is running. If it is not running, restart JP1/Base.

KNAM3020-I

The local action function has reloaded. (last updated = YYYY/MM/DD hh:mm:ss)

The local action function has reloaded. The last updated time is the date and time when the local action execution file was last updated.

KNAM3021-W

The local action function cannot be reloaded because the local action execution definition file does not exist.

The local action function cannot be reloaded because the local action execution definition file does not exist.

(S)

Continues the local action function in the state before the reload attempt was made.

(O)

Make sure that the local action execution definition file exists.

KNAM3024-I

The local action function cannot be reloaded because the local action execution definition file cannot be read.

The local action function cannot be reloaded because the local action execution definition file cannot be read.

(S)

Continues the local action function in the state before the reload attempt was made.

(O)

Make sure that the local action execution definition file can be read.

KNAM3025-I

The local action function cannot be reloaded because there is an error in the local action execution definition file. (last updated = YYYY/MM/DD hh:mm:ss)

The local action function cannot be reloaded because there is an error in the definitions in the local action execution definition file. The last update time is the date and time when the local action execution file was last updated.

(S)

Continues the local action function in the state before the reload attempt was made.

(O)

Make sure that the definitions in the local action execution definition file are correct.

KNAM3030-W

An attempt to acquire the common definition for local actions has failed. (label = label-name, code = error-number)

An attempt to acquire the label value set in the common definition has failed.

(S)

Continues processing, assuming the initial value.

(O)

Re-execute the jevlogstart command after you have made sure that:

The event service is running. (You can check this by using the jevstat command.)

The service name specified for the ports parameter as an application port in the event server settings file (conf) is set in the services file.

Communication is possible between the address specified for the ports parameter in the event server settings file (conf) and the addresses specified for the server and client parameters in the API settings file.

When JP1/Base is operating with the ANY binding method on a host that uses IPv6 addresses, the IPv6 address of the local host is set in the jp1hosts2 information.

KNAM3031-W

An error exists in the common definition for local actions. (label = label-name, value = value)

There is an error in the label value set in the common definition.

(S)

Continues processing, assuming the initial value.

(O)

Check the settings in the common definition.

KNAM3040-I

The local action function will now pause.

The local action function will now pause because it is set to pause.

KNAM3099-E

An attempt to open the catalog file failed.

The message file could not be opened.

(S)

Continues processing.

(O)

The system environment is invalid. Make sure that the installation has ended successfully, or that JP1/Base files have not been deleted by mistake.

KNAM3100-I

The execution definition file does not exist. (file = file-name)

The local action execution definition file does not exist.

KNAM3101-E

An attempt to access the execution definition file has failed. (file = file-name)

You do not have access permissions for the local action execution definition file.

(S)

Does not start the local action function.

(O)

Make sure that you have access permissions for the file.

KNAM3102-E

An attempt to read the execution definition file has failed. (file = file-name, code = error-number)

An attempt to read the local action execution definition file has failed.

(S)

Does not start the local action function.

(O)

Make sure that there are sufficient OS resources.

KNAM3103-E

An invalid parameter specification exists in the execution definition file. (line = line-number, last updated = YYYY/MM/DD hh:mm:ss)

A parameter specified in the local action execution definition file is invalid. The last updated time is the time and date when the local action execution definition file was last updated.

(S)

Does not start the local action function.

(O)

Check the parameter.

KNAM3104-E

A syntax error exists in a parameter of the execution definition file. (line = line-number, parameter = parameter-name, last updated = YYYY/MM/DD hh:mm:ss)

A syntax error exists in a parameter in the local action execution definition file. The last updated time is the time and date when the local action execution definition file was last updated.

(S)

Does not start the local action function.

(O)

Check the syntax of the parameter.

KNAM3105-E

An invalid value is specified for a parameter in the execution definition file. (line = line-number, parameter = parameter-name, last updated = YYYY/MM/DD hh:mm:ss)

An invalid value is specified for a parameter in the local action execution definition file. The last updated time is the time and date when the local action execution definition file was last updated.

(S)

Does not start the local action function.

(O)

Check the value specified for the parameter.

KNAM3106-E

A required parameter is not specified in the execution definition file. (parameter = parameter-name, last updated = YYYY/MM/DD hh:mm:ss)

A required parameter is not specified in the local action execution definition file. The last updated time is the time and date when the local action execution definition file was last updated.

(S)

Does not start the local action function.

(O)

Check the value set for the parameter.

KNAM3120-E

The environment variable file does not exist. (actno = action-number, actnm = action-name, file = file-name)

The local action environment variable file does not exist.

(S)

Does not execute the local action command line.

(O)

Make sure that the local action environment variable file exists.

KNAM3122-E

An attempt to read the environment variable file has failed. (actno = action-number, actnm = action-name, file = file-name, code = error-number)

An attempt to read the local action environment variable file has failed.

(S)

Does not execute the local action command line.

(O)

Make sure that there are sufficient OS resources.

KNAM3130-E

The local action functions cannot connect to the event server. (host = host-name, code = error-number)

An attempt to connect to the event server from a local action has failed.

(S)

Sets the local action to the pause state.

(O)

Make sure that:

The event service is running. (You can check this by using the jevstat command.)

The service name specified for the ports parameter as an application port in the event server settings file (conf) is set in the services file.

Communication is possible between the address specified for the ports parameter in the event server settings file (conf) and the addresses specified for the server and client parameters in the API settings file.

When JP1/Base is operating with the ANY binding method on a host that uses IPv6 addresses, the IPv6 address of the local host is set in the jp1hosts2 information.

KNAM3131-E

An attempt to acquire an event has failed. (host = host-name, code = error-number)

An attempt to acquire an event from a local action has failed.

(S)

Retries acquiring an event or sets the local action to the pause state.

(O)

Check the operating status of the event server.

KNAM3132-E

Preparation of the environment for connecting with the event server is incomplete. (host = host-name, code = error-number)

An attempt to connect to the event server from a local action has failed.

(S)

Sets the local action to the pause state.

(O)

Check the status of resources in the operating environment.

KNAM3133-W

The local action functions lost the connection to the event server. (host = host-name, code = error-number)

An attempt to connect to the event server from a local action has failed.

(S)

Retries connecting to the event server.

(O)

Check the operating status of the event server.

KNAM3134-I

The local action functions will try reconnecting to the event server. (host = host-name)

The local action will retry connecting to the event server.

KNAM3135-E

An error occurred during judgment processing for the event filter. (actnm = action-name)

Judgment of the local action using the conditions has failed.

(S)

Does not perform judgment of the local action using the conditions.

(O)

Check the contents of the judgment conditions and the operating environment.

KNAM3137-I

The local action functions connected to the event server. (host = host-name)

The connection from the local action to the event server has recovered.

KNAM3140-E

The local action functions cannot access the command execution log file. (file = file-name, code = error-number)

The command execution log file could not be created.

(S)

Stops the local action functions.

(O)

Make sure that the file can be created.

KNAM3142-E

An attempt to write to the command execution log file has failed. (file = file-name, code = error-number)

An attempt to write to the command execution log file has failed.

(S)

Stops the local action functions.

(O)

Make sure that there are sufficient OS resources.

KNAM3150-E

Event registration failed. (eventid = event-ID, actno = action-number, host = host-name, code = error-number)

An attempt to register a JP1 event to the event server has failed.

(S)

Continues processing.

(O)

Check the operating status of the event server.

KNAM3160-E

The length of the parameter setting after expanding the attribute variable name is outside the valid range. (actno = action-number, actnm = action-name, parameter = parameter-name)

The length of the parameter setting after expanding the attribute variable name is outside the valid range.

(S)

Continues processing.

(O)

Check the value for the attribute variable name.

KNAM3170-E

An attempt to perform user mapping for command execution failed. (actno = action-number, actnm = action-name, JP1user = JP1-user-name)

An attempt to map the JP1 user name failed.

(S)

Continues processing.

(O)

Make sure that:

Mapping information for the JP1 user is correct.

The OS user defined in the user mapping exists.

In Windows, the password of the OS user defined in the user mapping has not changed.

In Windows, the OS user defined in the user mapping has the user right Log on locally.#

In UNIX, the user ID of the OS user defined in the user mapping is valid.

#: For details about how to set the user rights, see 8.1.5(2) Assigning a user right to an OS user in the Job Management Partner 1/Base User's Guide.

KNAM3201-I

An action condition has been satisfied. (actno = action-number, actnm = action-name, host = execution-host-name)

An action condition for the local action has been satisfied.

KNAM3202-E

An action cannot be executed, because simultaneous execution of the same action is suppressed. (actno = action-number, actnm = action-name, host = execution-host-name)

An action condition was satisfied, but it could not be executed because simultaneous execution of the same action was suppressed.

(S)

Continues processing for the next event.

(O)

Make sure that the setting for suppressing simultaneous execution of the same action is appropriate.

KNAM3203-I

An action execution start request was accepted. (actno = action-number, actnm = action-name, host = execution-host-name, eventid = event-ID, eventseq = sequence-number-in-event-DB)

The action waits to be executed after the action condition was satisfied.

KNAM3204-E

An action cannot be executed because the preceding input count reached the upper limit. (actno = action-number, actnm = action-name, host = execution-host-name)

The action could not be changed to the waiting-to-execute state because the preceding input count reached the upper limit.

(S)

Continues processing from the next event.

(O)

Make sure that the setting for the upper limit of the preceding input count is appropriate.

KNAM3205-E

An action cannot be executed because preparation of the execution environment for the action is incomplete. (actno = action-number, actnm = action-name, host = execution-host-name, JP1 user = JP1-user-name)

The environment was not set up to allow an action to be executed.

(S)

Continues processing from the next event.

(O)

Make sure that the execution environment is set up.

KNAM3206-I

The command will now start. (actno = action-number, actnm = action-name, host = execution-host-name, JP1 user = JP1-user-name, OS user = OS-user-name, proc-ID = process-ID, cmd = command-line)

Command execution has started.

KNAM3207-E

An attempt to start a command has failed. (actno = action-number, actnm = action-name, host =execution-host-name, JP1 user = JP1-user-name, OS user = OS-user-name, cmd = command-line)

An attempt to start the command line specified by the action has failed.

(S)

Continues processing from the next event.

(O)

Make sure that the execution environment is set up.

KNAM3208-I

A command has ended. (actno = action-number, actnm = action-name, host = execution-host-name, JP1 user = JP1-user-name, OS user = OS-user-name, proc-ID = process-ID, result = command-output-result)

The command line specified by the action has ended.

KNAM3209-W

An action was cancelled (actno = action-number, actnm = action-name, host = execution-host-name, JJP1 user = JP1-user-name, OS user = OS-user-name, proc-ID = process-ID, cmd = command-line)

The action was canceled.

(S)

Continues processing from the next event.

KNAM3210-I

An action has completed. (actno = action-number, actnm = action-name, host = execution-host-name, JP1 user = JP1-user-name, OS user = OS-user-name, proc-ID = process-ID, code = command-end-code)

Execution of the action ended.

KNAM3211-E

An action ended without being executed. (actno = action-number, actnm = action-name, host = execution-host-name, JP1 user = JP1-user-name, OS user = OS-user-name, proc-ID = process-ID, cmd = command-line)

The action command ended without being executed.

(S)

Continues the action from the next event.

(O)

Make sure that the execution environment is set up.

KNAM3212-W

An action ended because it was cancelled. (actno = action-number, actnm = action-name, host = execution-host-name, JP1 user = JP1-user-name, OS user = OS-user-name, proc-ID = process-ID, cmd = command-line)

The action ended because it was canceled.

(S)

Continues the action from the next event.

KNAM3310-I

The command jbslistlcact started.

Execution of the jbslistlcact command started.

KNAM3311-I

The command jbslistlcact ended.

Execution of the jbslistlcact command ended.

KNAM3312-E

No logical host exists. (host = host-name)

The specified logical host does not exist.

(S)

Terminates command processing.

(O)

Make sure that the specified logical host name is correct.

KNAM3313-E

A connection to the local action function cannot be established.

The local action has not started.

(S)

Terminates command processing.

(O)

Make sure that the local action has started.

KNAM3314-I

No waiting or running actions exist.

There is no action that can be displayed because no actions are running.

KNAM3315-E

The user does not have permission to execute the command.

The command cannot be executed because the user does not have administrator privileges# (in Windows Server 2003 or earlier, or UNIX).

(S)

Terminates command processing.

(O)

Execute the command with Administrators permissions#.

#: In Windows, execute the command as a member of the Administrators group. In UNIX, execute the command as a user who has root privileges or JP1/Base administrator privileges.

KNAM3316-E

Execute the command from the administrator console.

You cannot execute the command because you do not have Administrators permissions (in Windows Vista or later).

(S)

Terminates command processing.

(O)

Re-execute the command on the administrator console.

KNAM3317-E

An attempt to initialize the common definition has failed.

The command cannot be executed because the common definition could not be initialized.

(S)

Terminates command processing.

(O)

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

KNAM3318-E

An attempt to initialize the communication base has failed.

The command cannot be executed because the communication base could not be initialized.

(S)

Terminates command processing.

(O)

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

KNAM3319-E

The logical host name is invalid. (host = host-name)

The command cannot be executed because the operating environment for the logical host is not set up.

(S)

Terminates command processing.

(O)

Check the access permissions for the shared directory.

KNAM3320-E

An attempt to initialize a log has failed. (host = host-name, errcode = error-code, errpos = error-position-code)

The command cannot be executed because a log could not be initialized.

(S)

Terminates command processing.

(O)

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

KNAM3321-E

An attempt to connect with the local action has failed. (errno = error-code)

The command cannot be executed because a socket could not be created.

(S)

Terminates command processing.

(O)

Make sure that there is sufficient memory. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KNAM3322-E

An attempt to acquire data has failed. (errno = error-code)

The command cannot be executed because an attempt to send or receive data failed.

(S)

Terminates command processing.

(O)

Make sure that there is sufficient memory. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KNAM3323-E

An unexpected error occurred.

The command cannot be executed because an unexpected error occurred.

(S)

Terminates command processing.

(O)

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

KNAM3329-E

An attempt to open the catalog file failed.

A message file could not be opened.

(S)

Terminates command processing.

(O)

The system environment is invalid. Make sure that the installation has ended successfully or that JP1/Base files have not been deleted by mistake.

KNAM3350-I

The command jbscancellcact has started.

Execution of the jbscancellcact command started.

KNAM3351-I

A local action was successfully canceled. (actno = action-number)

A local action was successfully canceled.

KNAM3352-E

The logical host does not exist. (host = host-name)

The specified logical host does not exist.

(S)

Terminates command processing.

(O)

Make sure that the specified logical host name is correct.

KNAM3353-E

A connection to the local action function cannot be established.

The local action has not started.

(S)

Terminates command processing.

(O)

Make sure that the local action has started.

KNAM3354-W

The specified action does not exist as running or waiting action. (actno = action-number)

The specified action does not exist as running or waiting action.

(S)

Terminates command processing.

(O)

Check the execution status by using the jbslistlcact command or the execution log file.

KNAM3355-E

The user does not have permission to execute the command.

The command cannot be executed because the user does not have administrator privileges# (in Windows Server 2003 or earlier, or UNIX).

(S)

Terminates command processing.

(O)

Execute the command with Administrators permissions#.

#: In Windows, execute the command as a member of the Administrators group. In UNIX, execute the command as a user who has root privileges or JP1/Base administrator privileges.

KNAM3356-E

Execute the command from the administrator console.

You cannot execute the command because you do not have Administrators permissions (in Windows Vista or later).

(S)

Terminates command processing.

(O)

Re-execute the command from the administrator console.

KNAM3357-E

An attempt to initialize the common definition has failed.

The command cannot be executed because the common definition could not be initialized.

(S)

Terminates command processing.

(O)

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

KNAM3358-E

An attempt to initialize the communication base has failed.

The command cannot be executed because he communication base could not be initialized.

(S)

Terminates command processing.

(O)

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

KNAM3359-E

The logical host name is invalid. (host = host-name)

The command cannot be executed because the shared directory could not be viewed.

(S)

Terminates command processing.

(O)

Check the access permission for the shared directory.

KNAM3360-E

An attempt to initialize a log has failed. (host = host-name, errcode = error-code, errpos = error-position-code)

The command cannot be executed because a log could not be initialized.

(S)

Terminates command processing.

(O)

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

KNAM3361-E

An attempt to connect with a local action has failed. (errno = error-code)

The command cannot be executed because a socket could not be created.

(S)

Terminates command processing.

(O)

Make sure that there is sufficient memory. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KNAM3362-E

An attempt to acquire data has failed. (errno = error-code)

The command cannot be executed because an attempt to send or receive data failed.

(S)

Terminates command processing.

(O)

Make sure that there is sufficient memory. If the problem cannot be corrected, use the data collection tool to collect data, and then contact the system administrator.

KNAM3363-E

An attempt to cancel a local action has failed. (actno = atcion-number)

The command cannot be executed because an attempt to cancel the local action failed.

(S)

Terminates command processing.

(O)

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

KNAM3364-E

An unexpected error occurred.

The command cannot be executed because an unexpected error occurred.

(S)

Terminates command processing.

(O)

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

KNAM3369-E

An attempt to open the catalog file failed.

A message file could not be opened.

(S)

Terminates command processing.

(O)

The system environment is invalid. Make sure that the installation has ended successfully or that JP1/Base files have not been deleted by mistake.

2.16 Service management control messages (KNAM4000 to KNAM4412)

KNAM4000-I

Service management control has started.

Service management control has started.

KNAM4001-I

Service management control has terminated.

Service management control has terminated.

KNAM4002-E

Service management control has terminated abnormally. (detailed code = error-number)

Service management control has terminated abnormally.

(S)

Does not start service management control.

(O)

Check the operator's action to take for the immediately preceding error and make sure that there is sufficient OS resources.

KNAM4003-I

Reloading of service management control will now start.

Reloading of service management control will now start.

KNAM4006-W (Windows)

An attempt to create a message resource file name has failed. Processing will continue using the default message.

The default message will be output to the integrated trace log because the resource file name could not be created.

(S)

After this message is output, the system will output the default message to the integrated trace log.

(O)

Make sure that there has been no severe deterioration is OS resources or available memory.

KNAM4006-W (UNIX)

An attempt to create a message catalog file name has failed. Processing will continue using the default message.

The default message will be output to the integrated trace log because the catalog file name could not be created.

(S)

After this message is output, the system will output the default message to the integrated trace log.

(O)

Make sure that there has been no severe deterioration is OS resources or available memory.

KNAM4007-W (Windows)

An attempt to load a message resource file has failed. Processing will continue using the default message.

The default message will be output to the integrated trace log because the resource file could not be loaded.

(S)

After this message is output, the system will output the default message to the integrated trace log.

(O)

Make sure that there has been no severe deterioration is OS resources or available memory.

KNAM4007-W (UNIX)

The message catalog file cannot be opened. Processing will continue using the default message.

The default message will be output to the integrated trace log because the catalog file could not be opened.

(S)

After this message output, the system will output the default message to the integrated trace log.

(O)

Make sure that there has been no severe deterioration is OS resources or available memory.

Make sure that the catalog file (jbssrvmgr.cat) exists in the /opt/jp1base/lib/nls directory.

KNAM4008-W

An attempt to reload the definition has failed. Processing will continue with the previous data.

Reloading failed because an error occurred during reloading.

(S)

Continues processing using the data from before reloading.

(O)

Check the access permission for the definition file for service management control, or whether the file exists. Also, make sure that there has been no severe deterioration is OS resources or available memory.

KNAM4011-E

Service management control will now stop because an invalid request was received from process management. (request code = numeric-value)

Service management control will now stop because there was an invalid request from the process management.

(S)

Terminates service management control.

(O)

Check for invalid termination of the process management. Also, make sure that there has been no severe deterioration is OS resources, available memory, or the communication environment.

KNAM4012-E

Service management control will now stop because an attempt to notify process management of startup failed.

Service management control will now stop because an attempt to notify process management of startup failed.

(S)

Terminates service management control.

(O)

Check for invalid termination of the process management. Also, make sure that there has been no severe deterioration is OS resources, available memory, or the communication environment.

KNAM4200-W

Access from a host without access permission has occurred. (host-name)

A host for which access permission has not be granted attempted access.

(S)

Rejects the access.

(O)

Make sure that the host access control definition file does not contain an error.

KNAM4201-W

An access request was made for a directory or file for which access permission has not been granted. (file-path-or-directory-path)

An access request was made for a directory or file for which access permission has not been granted.

(S)

Rejects the access.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4202-W

An error exists in the host access control definition file. (error-occurrence-line)

An error exists in the host access control definition file.

(S)

Starts by enabling the definitions other than the definition that contains an error.

(O)

Check the definitions in the host access control definition file.

KNAM4204-W

The session could not be started.

The session could not be started.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4206-W

The session could not be stopped.

The session could not be stopped.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4208-W

Locking failed.

Locking failed.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4210-W

Unlocking failed.

Unlocking failed.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4212-W

The current directory could not be obtained.

The current directory could not be obtained.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4214-W

The current directory could not be changed. (directory-name)

The current directory could not be changed.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4216-W

A directory could not be deleted. (directory-name)

A directory could not be deleted.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4218-W

A directory could not be created. (directory-name)

A directory could not be deleted.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4220-W

A directory name could not be changed. (before change = directory-name, after change = directory-name)

A directory name could not be changed.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4222-W

The list of files in the current directory could not be obtained.

The list of files in the current directory could not be obtained.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4224-W

The file-transfer type could not be changed. (file-transfer-type)

The file-transfer type could not be changed.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4226-W

A file could not be sent. (file-name)

A file could not be sent.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4228-W

A file could not be received. (file-name)

A file could not be received.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4230-W

A file attribute could not be changed. (file name = file-name, attribute = attribute)

A file attribute could not be changed

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4232-W

The file owner could not be changed. (file name = file-name, owner = owner, group = group)

The file owner could not be changed.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4234-W

A file could not be deleted. (file-name)

A file could not be deleted.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4236-W

The file name could not be changed. (before change = file-name, after change = file-name)

The file name could not be changed.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4238-W

A file could not be copied. (source = file-name, destination = file-name)

A file could not be copied.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4240-W

A file could not be moved. (source = file-name, destination = file-name)

A file could not be moved.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4402-W

A service could not be started. (product name = product-name, service name = service-name)

A service could not be started.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4404-W

A service could not be stopped. (product name = product-name, service name = service-name)

A service could not be stopped.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4406-W

Service definition information could not be reloaded. (product name = product-name, service name = service-name)

Service definition information could not be reloaded.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4408-W

A list of product names could not be obtained.

A list of product names could not be obtained.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4410-W

The status of service could not be obtained. (product name = product-name, service name = service-name)

The status of a service could not be obtained.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

KNAM4412-W

A list of definition file names could not be obtained. (product name = product-name, service name = service-name)

A list of definition file names could not be obtained.

(S)

Continues processing.

(O)

Make sure that there is no problem in JP1/IM - Manager.

2.17 Setup information collection messages (KNAM9001 to KNAM9028)

KNAM9001-I

Processing to collect setup information will now start.

KNAM9002-I

Processing to collect setup information has finished.

KNAM9003-E

The setup information collection command ended abnormally.

The setup information collection command (jbsparamdump command) ended abnormally.

(S)

Terminates command processing.

(O)

Take action according to the information in the message output before this message, and then re-execute the command. If the problem is not solved, use the data collection tool to collect the required data, and then contact the system administrator.

KNAM9004-E

The specified option contains an error.

The command option is invalid.

(S)

Terminates command processing.

(O)

Specify the correct option.

KNAM9005-E

The user does not have permission to execute the command.

You cannot execute the command because you do not have administrator permissions# (Windows Server 2003 or earlier or UNIX).

(S)

Terminates command processing.

(O)

Execute the command as a user who has administrator permissions#.

#: In Windows, Administrator permissions. In UNIX, root privileges or JP1/Base administrator privileges.

KNAM9006-E

Execute the command from the administrator console.

Execute the command from the administrator console.

(S)

Terminates command processing.

(O)

Re-execute the command from the administrator console.

KNAM9007-E

An attempt to access the destination directory failed. (directory-name)

An attempt to access the destination directory failed.

(S)

Terminates command processing.

(O)

Make sure that:

The directory specified in the command exists.

You have permission to access the directory.

The length of the directory path does not exceed the limit of the OS.

KNAM9008-E

A syntax error was found in the collection information file. (line=line-number)

A syntax error was found in the collection information file.

(S)

Terminates command processing.

(O)

Revise the format of the definition file.

KNAM9009-E

Memory is insufficient.

A memory shortage occurred during execution of the command.

(S)

Terminates command processing.

(O)

Terminate other processes that might be using memory, and then re-execute the command.

KNAM9010-E

An internal error occurred.(detailed-information)

An internal error occurred during execution of the command.

(S)

Terminates command processing.

(O)

Re-execute the command. If the problem is not solved, use the data collection tool to collect data, and then contact the system administrator.

KNAM9011-W

Setup information cannot be obtained because the shared disk is not mounted. (logical-host-name)

Setup information for the logical host saved on the shared disk cannot be obtained because the shared disk is not mounted.

(S)

Continues command processing.

(O)

Mount the shared disk, and then re-execute the command.

KNAM9012-I

Setup information of the authentication server will not be output because the -s option is not specified.

KNAM9013-E

An attempt to read a collection information file failed.

An attempt to read a collection information file failed.

(S)

Terminates command processing.

(O)

Make sure that the collection information file can be read.

Make sure that you have read permission for the collection information file.

Make sure that no other process has set the read-lock for the collection information file.

KNAM9014-E

The logical host information could not be obtained.

The logical host information could not be obtained because an error occurred during access to the common definition.

(S)

Continues command processing. However, setup information only for the physical host is output.

(O)

A temporary memory or resource shortage might have occurred. Re-execute the command. If the problem is not solved, use the data collection tool to collect the required data, and then contact the system administrator.

KNAM9015-W

The directory path of the logical host (logical-host-name) could not be obtained.

The directory path of the logical host could not be obtained because an error occurred during access to the common definition.

(S)

Continues command processing. However, definition file information for the logical host cannot be obtained.

(O)

The setting of common definition information for the logical host might have an error. Check the setting, and then set up the logical host again if necessary. If the problem is not solved, use the data collection tool to collect data, and then contact the system administrator.

KNAM9016-W

Setup information cannot be retrieved because the directory that the event server uses cannot be accessed. (event-server-name)

Setup information for the event server saved in the directory cannot be obtained because the directory that the event server uses cannot be accessed.

(S)

Continues command processing.

(O)

Check the following, and then re-execute the command:

Make sure that the correct directory is set in the event server index file (index).

Make sure that you have permission to access the directory set in the event server index file (index).

If you want to use information in the shared disk, make sure that the shared disk is mounted.

KNAM9020-I

Setup information for the physical host was output successfully. (file-name)

KNAM9021-E

An attempt to output setup information for the physical host failed. (file-name)

An attempt to output setup information for the physical host failed.

(S)

Continues command processing.

(O)

Check the following items, and then re-execute the command:

If a file having the same name as file-name already exists, make sure that the file is writable.

Make sure that the length of the file name does not exceed the limit of the OS path.

Make sure that sufficient disk space is allocated at the output destination.

If the problem is not solved, use the data collection tool to collect data, and then contact the system administrator.

KNAM9022-I

Setup information for the logical host was output successfully. (file-name)

KNAM9023-E

An attempt to output setup information for the logical host failed. (file-name)

An attempt to output setup information for the logical host failed.

(S)

Continues command processing.

(O)

Check the following items, and then re-execute the command:

If a file having the same name as file-name already exists, make sure that the file is writable.

Make sure that the length of the file name does not exceed the limit of the OS path.

Make sure that sufficient disk space is allocated at the output destination.

If the problem is not solved, use the data collection tool to collect data, and then contact the system administrator.

KNAM9024-I

Setup information for the event server was output successfully. (file-name)

KNAM9025-E

An attempt to output setup information for the event server failed. (file-name)

An attempt to output setup information for the event server failed.

(S)

Continues command processing.

(O)

Check the following items, and then re-execute the command:

If a file having the same name as file-name already exists, make sure that the file is writable.

Make sure that the length of the file name does not exceed the limit of the OS path.

Make sure that sufficient disk space is allocated at the output destination.

If the problem is not solved, use the data collection tool to collect data, and then contact the system administrator.

KNAM9026-I

Setup information specified in the collection information file was output successfully. (file-name)

KNAM9027-E

An attempt to output setup information specified in the collection information file (file-name) failed.

(S)

Continues command processing.

(O)

Check the following items, and then re-execute the command:

If a file having the same name as file-name already exists, make sure that the file is writable.

Make sure that the length of the file name does not exceed the limit of the OS path.

Make sure that sufficient disk space is allocated at the output destination.

If the problem is not solved, use the data collection tool to collect data, and then contact the system administrator.

KNAM9028-W

Part of the setup information could not be acquired. (output-file-name)

(S)

Continues command processing.

(O)

Open the output file indicated by output-file-name to check the setup information that could not be acquired. If a file could not be acquired, make sure that the file can be read. If common definition information could not be acquired, make sure that the settings are correct.

Index

A

"Administrator permissions" as used in this manual[1]

C

contents of syslog[1]

contents of Windows event log[1]

conventions

"Administrator permissions" as used in this manual[1]

directory names[1]

fonts and symbols[1]

installation folder for JP1/Base[1]

version numbers[1]

D

directory name conventions[1]

F

font conventions[1]

K

KAIU001 to KAIU999[1]

KAJP1001 to KAJP1871[1]

KAVA0200 to KAVA1694[1]

KAVA1700 to KAVA1946[1]

KAVA2000 to KAVA3918[1]

KAVA4001 to KAVA4614[1]

KAVA5001 to KAVA5902[1]

KAVA6002 to KAVA6855[1]

KAVA7001 to KAVA7560[1]

KAVB2002 to KAVB2638[1]

KAVB3001 to KAVB3172[1]

KAVB3501 to KAVB3914[1]

KNAM1001 to KNAM1514[1]

KNAM2000 to KNAM2012[1]

KNAM3000 to KNAM3369[1]

KNAM4000 to KNAM4412[1]

KNAM9001 to KNAM9028[1]

M

message

format[1]

format of explanations[1]

list of output destinations[1]

type[1]

message ID

manuals containing corresponding messages[1]

N

note to system administrator[1]

O

output destinations of messages

KAIU001 to KAIU999[1]

KAJP1001 to KAJP1871[1]

KAVA0200 to KAVA1694[1]

KAVA1700 to KAVA1946[1]

KAVA2000 to KAVA3918[1]

KAVA4001 to KAVA4614[1]

KAVA5001 to KAVA5902[1]

KAVA6002 to KAVA6855[1]

KAVA7001 to KAVA7560[1]

KAVB2002 to KAVB2638[1]

KAVB3001 to KAVB3172[1]

KAVB3501 to KAVB3914[1]

KNAM1001 to KNAM1514[1]

KNAM2000 to KNAM2012[1]

KNAM3000 to KNAM3369[1]

KNAM4000 to KNAM4412[1]

KNAM9001 to KNAM9028[1]

S

symbol conventions[1]

syntax conventions[1]

V

version number conventions[1]