Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Messages 2

3021-3-330-20(E)

Notices

Relevant program products

For details about the applicable OS versions, and the service packs and patches required for Job Management Partner 1/Automatic Job Management System 3, see the Release Notes.

Job Management Partner 1/Automatic Job Management System 3 - Manager (For Windows):

P-2W12-3KAL Job Management Partner 1/Automatic Job Management System 3 - Manager version 10-50

The above product includes the following:

P-CC2A12-3KAL Job Management Partner 1/Automatic Job Management System 3 - Manager: version 10-50 (For Windows Server 2012 and Windows Server 2008)

P-CC2412-3KAL Job Management Partner 1/Automatic Job Management System 3 - Manager version 10-50 (For Windows Server 2003 and Windows Server 2003(x64))

Job Management Partner 1/Automatic Job Management System 3 - Manager (For UNIX):

P-1J12-27AL Job Management Partner 1/Automatic Job Management System 3 - Manager version 10-50 (For HP-UX(IPF))

P-9312-27AL Job Management Partner 1/Automatic Job Management System 3 - Manager version 10-50 (For Solaris 11 (SPARC) and Solaris 10 (SPARC))

P-1M12-27AL Job Management Partner 1/Automatic Job Management System 3 - Manager version 10-50 (For AIX)

P-8112-27AL Job Management Partner 1/Automatic Job Management System 3 - Manager version 10-50 (For Linux 6.1 (x86) or later, Linux 6.1 (x64) or later, Linux 5.1 (x86) or later, and Linux 5.1 (AMD/Intel 64) or later)

Job Management Partner 1/Automatic Job Management System 3 - Agent (For Windows):

P-2W12-33AL Job Management Partner 1/Automatic Job Management System 3 - Agent version 10-50

The above product includes the following:

P-CC2A12-33AL Job Management Partner 1/Automatic Job Management System 3 - Agent version 10-50 (For Windows Server 2012 and Windows Server 2008)

P-CC2412-33AL Job Management Partner 1/Automatic Job Management System 3 - Agent version 10-50 (For Windows Server 2003 and Windows Server 2003(x64))

Job Management Partner 1/Automatic Job Management System 3 - Agent (For UNIX):

P-1J12-29AL Job Management Partner 1/Automatic Job Management System 3 - Agent version 10-50 (For HP-UX(IPF))

P-9312-29AL Job Management Partner 1/Automatic Job Management System 3 - Agent version 10-50 (For Solaris 11 (SPARC) and Solaris 10 (SPARC))

P-1M12-29AL Job Management Partner 1/Automatic Job Management System 3 - Agent version 10-50 (For AIX)

P-8112-29AL Job Management Partner 1/Automatic Job Management System 3 - Agent version 10-50 (For Linux 6.1 (x86) or later, Linux 6.1 (x64) or later, Linux 5.1 (x86) or later, and Linux 5.1 (AMD/Intel 64) or later)

Job Management Partner 1/Automatic Job Management System 3 - View (For Windows):

P-2W12-34AL Job Management Partner 1/Automatic Job Management System 3 - View version 10-50

The above product includes the following:

P-CC2A12-34AL Job Management Partner 1/Automatic Job Management System 3 - View version 10-50 (For Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008 and Windows Vista)

P-CC2412-34AL Job Management Partner 1/Automatic Job Management System 3 - View version 10-50 (For Windows Server 2003, Windows Server 2003(x64), and Windows XP Professional)

Job Management Partner 1/Base# (For Windows):

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

The above product includes the following:

P-CC2A2C-6LAL Job Management Partner 1/Base# version 10-50 (For Windows Server 2012 and Windows Server 2008)

P-CC242C-6LAL Job Management Partner 1/Base# version 10-50 (For Windows Server 2003 and Windows Server 2003(x64))

Job Management Partner 1/Base# (For UNIX):

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

P-9D2C-6LAL Job Management Partner 1/Base# version 10-50 (For Solaris 11 (SPARC) and Solaris 10 (SPARC))

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

P-812C-6LAL Job Management Partner 1/Base# version 10-50 (For Linux 6.1 (x86) or later, Linux 6.1 (x64) or later, Linux 5.1 (x86) or later, and Linux 5.1 (AMD/Intel 64) or later)

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

Adobe is either a registered trademark or a trademark of Adobe Systems Incorporated in the United States and/or other countries.

CONNECT:Queue is a registered trademark of Sterling Commerce, Inc.

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

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.

IBM, AS/400 are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide.

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

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

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

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 Excel are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

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

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

Microsoft Exchange server is a product name of Microsoft Corporation in the U.S. and other countries.

Microsoft Office and Excel 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.

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

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

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

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

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

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

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

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

The following program products contain some parts whose copyrights are reserved by Oracle and/or its affiliates: P-9312-27AL, P-9312-29AL, and P-9D2C-6LAL.

The following program products contain some parts whose copyrights are reserved by UNIX System Laboratories, Inc.: P-9312-27AL, P-9312-29AL, and P-9D2C-6LAL.

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

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

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

Excel

Microsoft(R) Excel

Microsoft(R) Office Excel

Exchange Server

Microsoft(R) Exchange 2000 Enterprise Server

Microsoft(R) Exchange 2000 Server

Microsoft(R) Exchange Server

IE

Internet Explorer

Microsoft(R) Internet Explorer(R)

Windows(R) Internet Explorer(R)

Microsoft Mail

Microsoft(R) Mail

Microsoft SQL Server

Microsoft(R) SQL Server

Microsoft(R) SQL Server Enterprise Edition

MSCS

Microsoft(R) Cluster Server

MSMQ

Microsoft(R) Message Queue Server

Outlook

Outlook 2003

Microsoft(R) Outlook(R) 2003

Outlook 2007

Microsoft(R) Outlook(R) 2007

Outlook 2010

Microsoft(R) Outlook(R) 2010

Outlook Express

Microsoft(R) Outlook(R) Express

Windows 7

Microsoft(R) Windows(R) 7 Enterprise

Microsoft(R) Windows(R) 7 Professional

Microsoft(R) Windows(R) 7 Ultimate

Windows 8

Windows(R) 8 Enterprise

Windows(R) 8 Pro

Windows 8.1

Windows(R) 8.1 Enterprise

Windows(R) 8.1 Pro

Windows Server 2003

Windows Server 2003

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

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

Windows Server 2003 R2

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, Enterprise x64 Edition

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

Windows Server 2003 R2 (x64)

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 Standard

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 Professional

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

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

Restrictions

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

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

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

Issued

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

Copyright

Copyright (C) 2012, 2014, Hitachi, Ltd.

Copyright (C) 2012, 2014, Hitachi Solutions, Ltd.

Summary of amendments

The following table lists changes in the manuals (3021-3-318-20(E), 3021-3-319-20(E), 3021-3-320-20(E), 3021-3-321-20(E), 3021-3-322-20(E), 3021-3-323-20(E), 3021-3-324-20(E), 3021-3-325-20(E), 3021-3-326-20(E), 3021-3-327-20(E), 3021-3-328-20(E), 3021-3-329-20(E), and 3021-3-330-20(E)) and product changes related to these manuals.

Changes

Location

A virtual machine on which JP1/AJS3 has been installed and configured can now be duplicated.

System Design (Configuration) Guide:

F

Configuration Guide 1:

2.2, 3.1, 3.2, 12.2, 13.1, 13.2, H

Troubleshooting:

2.14

Messages 2:

KFPS00615-W, KFPU00219-E

Functionality was expanded so that a disaster recovery environment can be set up with the main and remote hosts whose logical host names are the same.

Configuration Guide 1:

9.1, 9.2.1, 9.2.2, 9.2.3, 9.3, 18.1, 18.2.1, 18.2.2, 18.2.3, 18.3

Administration Guide:

12.1.2, 12.1.3, 12.1.4, 12.2.1, 12.2.2, 12.2.3, 12.3.1, 12.4.1, 12.4.2

Command Reference 2:

2. jajs_rpenvexport, 2. jajs_rpenvimport, 2. jajs_rpsite

Messages 1:

1.3.3, 1.3.9, 1.4.1, KAVS3702-E, KAVS3710-I, KAVS3711-E, KAVS3754-E

Messages 2:

KNAD3994-E

A setting for shifting the start day by a number of days (counting both open and closed days) was added.

Overview:

3.3.2

System Design (Work Tasks) Guide:

3.5.5

Operator's Guide:

15.3.17

Command Reference 1:

2. ajschgnet, 2. ajsprint

Command Reference 2:

4.2.4

Messages 1:

KAVS0188-E

Messages 2:

KAVV455-E

A function that holds jobnet execution during immediate execution registration was added.

Overview:

3.4.2, 4.1.1

System Design (Work Tasks) Guide:

2.2.3

Operator's Guide:

15.3.1, 15.3.22, 15.3.38, 15.3.47, 15.10.1

Command Reference 1:

2. ajsentry

A function that can execute some commands from JP1/AJS3 - View to JP1/AJS3 - Manager was added.

System Design (Configuration) Guide:

4.5.4

Configuration Guide 1:

C.1

Administration Guide:

2.2.2, 2.2.4, 2.3.5, 13.1, 13.1.8

Troubleshooting:

A.1, A.3

Operator's Guide:

10.4, 11.1.1, 11.3.9, 11.3.18, 15.3.2, 15.3.3, 15.3.52, 15.3.53, 15.3.54, 15.4.2, 15.4.3, 15.7.2, 15.7.3, 15.8.2, 15.8.3, 15.9.2, 15.9.3, 15.10.2, 15.10.3

Command Reference 1:

2. ajslogprint, 2. ajsprint, 2. ajsshow, 2. ajsstatus

Command Reference 2:

2. jajs_setup_cluster

Messages 1:

1.3.3, KAVS0901-E, KAVS0538-I, KAVS0539-I

Messages 2:

KAVV263-E, KAVV269-E, KAVV385-E, KAVV418-E, KAVV419-E, KAVV2507-E, KAVV3900-Q to KAVV3910-E, KAVV3912-E to KAVV3919-E, KAVV3922-E to KAVV3929-E, KAVV3931-E, KAVV3932-E, KAVV3934-E to KAVV3936-Q

The files jajs_log.bat and jajs_log, which have the same functionality as the data collection tool (_04.bat and _04), are now available. In addition, an option was added to the Windows version of the data collection tools that allows you to specify the location to which data is output.

System Design (Configuration) Guide:

5.1.1, 9.4

Configuration Guide 1:

2.2.1, 2.2.2, 7.1.1, 7.1.2, 12.2.1, 16.1.1, 16.1.2

Administration Guide:

2.2.5, 2.3.6

Troubleshooting:

1.4.1, 1.4.2, 2.7.2

Command Reference 1:

1.5.8, 1.6, 2. jajs_log or _04 (UNIX only), 2. jajs_log.bat or _04.bat (Windows only)

Command Reference 2:

1.5.8, 1.6

Messages 2:

KAVU5287-E, KAVU5501-E

An option was added to the ajsprint command so that relation line information can be output in order of the unit name.

Configuration Guide 2:

2.2.1, 2.2.2

Administration Guide:

13.1, 13.1.8

Command Reference 1:

2. ajsprint

The procedure for changing the IP address of an agent host was changed.

Configuration Guide 1:

6.3.19, 15.3.19

Configuration Guide 2:

2.4.1, 2.4.2

Administration Guide:

8.9.2

Messages 1:

1.3.4, KAVT0198-E, KAVT0199-E, KAVT0528-E, KAVT0658-E to KAVT0661-E, KAVT0664-E

UTF-8 was added to the list of character encodings that can be used in AIX, HP-UX, and Solaris 10.

Overview:

10.1.1

System Design (Configuration) Guide:

2.4.3, 7.2.2, 8.2.2

Configuration Guide 1:

13.4.1, 15.1.9, C.2, D.2

Configuration Guide 2:

2.2.2, 2.7.1, 2.8.2

Administration Guide:

4.4.2

Operator's Guide:

15.3.6

Command Reference 1:

1.4.1

Command Reference 2:

1.4.1, 2. ajsembdbsetup, 2. jajs_setup, 2. jajs_setup_cluster

Messages 2:

KAVV179-E, KAVV503-E, KAVV601-E, KAVV882-E, KAVV883-E, KAVV1503-E, KAVV2119-E

The number of characters that can be used when specifying a logical host name for the command jajs_killall.cluster was increased.

Administration Guide:

11.6.1

Command Reference 1:

2. jajs_killall.cluster

Legend:

Overview: Job Management Partner 1/Automatic Job Management System 3 Overview

System Design (Configuration) Guide: Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide

System Design (Work Tasks) Guide: Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide

Configuration Guide 1: Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1

Configuration Guide 2: Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2

Administration Guide: Job Management Partner 1/Automatic Job Management System 3 Administration Guide

Troubleshooting: Job Management Partner 1/Automatic Job Management System 3 Troubleshooting

Operator's Guide: Job Management Partner 1/Automatic Job Management System 3 Operator's Guide

Command Reference 1: Job Management Partner 1/Automatic Job Management System 3 Command Reference 1

Command Reference 2: Job Management Partner 1/Automatic Job Management System 3 Command Reference 2

Linkage Guide: Job Management Partner 1/Automatic Job Management System 3 Linkage Guide

Messages 1: Job Management Partner 1/Automatic Job Management System 3 Messages 1

Messages 2: Job Management Partner 1/Automatic Job Management System 3 Messages 2

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

Preface

This manual describes the format of messages for Job Management Partner 1/Automatic Job Management System 3 (abbreviated hereafter to JP1/AJS3), and lists the messages (messages beginning with KAVU to KNAD). This manual also describes how to take actions for the messages.

Intended readers

This manual is intended for:

Those who wish to operate an automatic job execution system with JP1/AJS3 and those who design automatic job execution systems.

Those who operate an automatic job execution system with JP1/AJS3.

Organization of this manual

This manual consists of the following chapters. The manual is a common reference for all supported operating systems. Any platform-dependent differences in functionality are noted in the manual.

1. Messages

Chapter 1 lists the messages (messages beginning with KAVU to KNAD) output by JP1/AJS3, and describes how to take actions for them.

Conventions: Fonts and symbols

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

Text formatting

Convention

Bold

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

From the File menu, choose Open.

Click the Cancel button.

In the Enter name entry box, type your name.

Italic

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

Write the command as follows:

copy source-file target-file

The following message appears:

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

Italic characters are also used for emphasis. For example:

Do not delete the configuration file.

Monospace

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

At the prompt, enter dir.

Use the send command to send mail.

The following message is displayed:

The password is incorrect.

The following table explains the symbols used in this manual:

Symbol

Convention

|

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

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

{ }

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

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

[ ]

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

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

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

...

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

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

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

x

Multiplication sign

/

Division sign

The calculation result is rounded up to the next whole number.

Example:

The result of 34 / 3 is 12.

(tilde)

The item shown before this symbol must be specified in accordance with the conventions shown for angle brackets, double parentheses, and double angle brackets (below).

< >

(angle brackets)

Indicates the characters and lexical elements that can be specified.

<characters>

One or more Kanji characters, katakana characters, upper-case alphabetic characters, lower-case alphabetic characters, or numeric characters

<numeric>

0, 1, 2, 3, 4, 5, 6, 7, 8, or 9

<alphabetic character>

A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z, \, #, or @

<alphanumeric character>

Alphabetic or numeric character

<symbolic name>

No more than eight alphanumeric characters beginning with an alphabetic character

<unsigned integer>

One or more numeric characters

<hexadecimal character>

0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, or F

<file name>

A system-determined name assigned to a file

<path>

The directories contained in the path, with each name separated by a forward slash (/) or backslash (\). The path notation is OS-dependent.

(( ))

(double parentheses)

Indicates the range of specifiable values.

<< >>

(double angle brackets)

Indicates the default assumed by the system when a value is unspecified.

Example:

If you do not specify days-to-keep-form ~<numeric> ((0 to 365)) <<365>>, 365 is assumed as the number of days to keep the form.

MAX

Choose the largest of the calculation results.

Example:

The result of MAX (3 x 6, 4 + 7) is 18.

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.

JP1 program reorganization in version 8

The following are the major changes that have been made to the JP1 product suite in version 8:

JP1/AJS2 - Advanced Manager was eliminated, and the database provided by JP1/AJS2 - Advanced Manager was integrated into JP1/AJS2 - Manager in JP1 Version 8.

JP1/AJS2 - Client Toolkit was eliminated.

JP1/AJS2 - View products for platforms other than Windows were eliminated.

Organization of JP1/AJS3 manuals and choosing the right manuals

There are 13 JP1/AJS3 manuals. The following table summarizes their contents.

Note that Job Management Partner 1/Automatic Job Management System 3 has been omitted from the manual titles in the table.

No.

Manual

Contents

1

Overview

(3021-3-318(E))

JP1/AJS3 features

Description of functions

2

System Design (Configuration) Guide

(3021-3-319(E))

Information that must be considered when designing a system

Cautionary notes on designing a system

3

System Design (Work Tasks) Guide

(3021-3-320(E))

Information that must be considered when constructing jobs and jobnets

Cautionary notes on designing jobs and jobnets

4

Configuration Guide 1

(3021-3-321(E))

Installation and setup procedures

Environment setup procedure by operation type

5

Configuration Guide 2

(3021-3-322(E))

Description of environment setting parameters

Description of operation profiles

6

Administration Guide

(3021-3-323(E))

Information required to operate a system

Know-how useful for JP1/AJS3 operation

7

Troubleshooting

(3021-3-324(E))

How to troubleshoot errors

Data required when an error occurs

8

Operator's Guide

(3021-3-325(E))

How to operate JP1/AJS3 - View

How to operate JP1/AJS3 Console View

Description of windows and dialog boxes

9

Command Reference 1

(3021-3-326(E))

Command syntax

10

Command Reference 2

(3021-3-327(E))

Syntax of commands used for setup and special operations

Syntax and coding examples of information definition files

11

Linkage Guide

(3021-3-328(E))

Description of functions that can be used when linked with other products and the setup method

12

Messages 1

(3021-3-329(E))

Messages output by JP1/AJS3 (messages beginning with KAJS to KAVT)

13

Messages 2

(3021-3-330(E))

Messages output by JP1/AJS3 (messages beginning with KAVU to KNAD)

Use the following illustration and table as a guide to determine the manuals you need to read.

Purpose

Required reading

Read as necessary

To learn about JP1/AJS3's functionalities

Overview

(3021-3-318(E))

Linkage Guide

(3021-3-328(E))

To configure a system (including installation and setup) that automatically runs jobs

System Design (Configuration) Guide

(3021-3-319(E))

Configuration Guide 1

(3021-3-321(E))

Configuration Guide 2

(3021-3-322(E))

Linkage Guide

(3021-3-328(E))

To design work tasks that will be automated (including job definitions and schedule definitions)

System Design (Work Tasks) Guide

(3021-3-320(E))

Operator's Guide

(3021-3-325(E))

To learn about monitoring and maintaining a running system

Administration Guide

(3021-3-323(E))

Troubleshooting

(3021-3-324(E))

Messages 1

(3021-3-329(E))

Messages 2

(3021-3-330(E))

To learn about what action you need to take for problems that occur during operation

Troubleshooting

(3021-3-324(E))

Messages 1

(3021-3-329(E))

Messages 2

(3021-3-330(E))

To learn about operating JP1/AJS3

Operator's Guide

(3021-3-325(E))

Command Reference 1

(3021-3-326(E))

Command Reference 2

(3021-3-327(E))

1 Messages

This chapter explains the messages output by JP1/AJS3 and how to take actions for them.

1.1 Messages beginning with KAVU (Messages about the job execution control)

This section lists messages that begin with KAVU (messages about job execution control).

function-name: of some messages may not be displayed.

In some cases, destination-host-name, port-number, and system-error-number might not be displayed for messages that have these elements.

When a job other than a QUEUE job or a submit job is executed, the queue element of the message that is output indicates the execution agent or execution agent group.

When a job other than a QUEUE job or a submit job is executed, the agent-host-name and agent-name elements of the message that is output indicate the execution agent name or execution agent group. Note, however, that the target host is displayed in the following messages:

KAVU4220-E, KAVU4221-E, KAVU4222-E, KAVU4223-E, KAVU4294-I, KAVU4295-W, KAVU4296-E, KAVU4297-W, KAVU4299-I, KAVU4504-W, KAVU4530-W, KAVU4531-W, KAVU4534-W, KAVU4535-I, KAVU4538-W, KAVU4546-W, KAVU4547-W, KAVU4548-W, KAVU4549-W, KAVU4550-W, KAVU4551-W, KAVU4552-W, KAVU4553-W, KAVU4554-W, KAVU4555-W, KAVU4556-W, KAVU4557-W, KAVU4558-W, KAVU4559-W, KAVU4560-W, KAVU4561-W, KAVU4562-W, KAVU4563-W, KAVU4564-W, KAVU4565-W, KAVU4566-W, KAVU4567-W, KAVU4568-W, KAVU4569-W, KAVU4570-W, KAVU4571-W, KAVU4572-W, KAVU4573-W, KAVU4574-W, KAVU4575-W, KAVU4576-W, KAVU4578-W, KAVU4580-W, KAVU4581-W, KAVU4582-W, KAVU4583-W, KAVU4584-W, KAVU4585-W, KAVU4586-W, KAVU4587-W, KAVU4588-W, KAVU4589-W, KAVU4590-W, KAVU4591-W, KAVU4596-W, KAVU4597-W, KAVU4598-W, KAVU4700-E, KAVU4701-E, KAVU4702-E, KAVU4703-E, KAVU4704-E, KAVU4717-E, KAVU4718-E

To distinguish the job execution control managers that output messages, (scheduler-service-name) might be appended to the message. If (scheduler-service-name) is displayed, the message has been output by the job execution control manager for the indicated scheduler service. If (scheduler-service-name) is not displayed, the message has been output by the submit-job execution control manager.

For operation in the compatible ISAM configuration, see the JP1/AJS2 manual.

KAVU0200-E

function-name: A logical contradiction occurred.

A logical contradiction occurred.

(S)

Cancels the requested processing.

(O)

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

KAVU0201-E

function-name: The parameter is specified incorrectly.

The function has a parameter error.

(S)

Cancels the requested processing.

(O)

Make sure that the argument specified for the command is correct.

Also check the message output to the standard error output. Also check the integrated trace log for whether a KAVUxxxx message was output before or after this message. If a KAVUxxxx message was output, read the message explanation.

If the character encoding on the host on which you executed the command is different from the encoding on the manager host, the data size might have increased due to character code conversion during data transfer.

If character codes are converted on the manager host, make sure that the number of characters for each argument does not exceed the specifiable number of characters.

Remove the cause of the error, and then retry the operation.

KAVU0202-E

function-name: An internal factor caused an error.

An error occurred because of an internal factor.

(S)

Cancels the requested processing.

(O)

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

KAVU0203-E

function-name: JpqInit function is not issued.

The JpqInit function is not issued.

(S)

Cancels the requested processing.

(O)

Make sure that the JpqInit function is correctly called, and then retry.

KAVU0204-E

function-name: An environment setting or logical host name information is invalid.

An environment setting or logical host name information is invalid.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then call the function again.

KAVU0205-E

function-name: Memory became insufficient.

Memory became insufficient.

(S)

Cancels the requested processing.

(O)

Terminate any other unnecessary applications, and then call the function again. If the same message reappears, re-estimate memory.

KAVU0206-E

function-name: A logical contradiction occurred.

An error was found in a communication protocol parameter during processing of a request from the client. Alternatively, an attempt to acquire information about a logical host name or environment setting has failed at the function issuer. If a request is issued while the hosts file is being copied by overwriting the current one at the function issuer, an attempt to acquire the logical host name may fail.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation in that message to correct the cause of the error, and then reissue the request. If no such message was output or if the problem persists, use the data collection tool to collect data, and then contact the system administrator.

KAVU0207-E

function-name: The file cannot be opened because file path or file does not exist at the send source.

The file cannot be opened because file path or file does not exist at the send source.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0208-E

function-name: The file cannot be opened because you lack access permission for the file at the send source.

The file cannot be opened because you lack access permission for the file at the send source.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0209-E

function-name: The file cannot be opened because some other process is using the file at the send source.

The file cannot be opened because some other process is using the file at the send source.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0210-E

function-name: The file at the send source cannot be opened.

The file at the send source cannot be opened.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the original file name of the job definitions.

KAVU0211-E

function-name: The file at the send source cannot be read.

The file at the send source cannot be read.

(S)

Cancels the requested processing.

(O)

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

KAVU0212-E

function-name: Insufficient disk space. The file specified as the acquisition destination of the standard output or standard error output file cannot be written.

Insufficient disk space. The file specified as the acquisition destination of the standard output or standard error output file cannot be written.

(S)

Cancels the requested processing.

(O)

Increase the free space in the disk, and then call the function again.

KAVU0213-E

function-name: The file specified as the acquisition destination of the standard output or standard error output file could not be written.

The file specified as the acquisition destination of the standard output or standard error output file could not be written.

(S)

Cancels the requested processing.

(O)

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

KAVU0214-W

function-name: The standard (error) output file at the manager consists of 0 bytes of data.

No file was found when an attempt was made to collect data in the standard output file or the standard error output file by using the jpqjobget command.

(S)

Terminates the requested processing.

KAVU0215-E

function-name: TCP/IP communication could not be connected to the manager.

A connection for TCP/IP communication could not be established with the job execution control manager process.

(S)

Cancels the requested processing.

(O)

Make sure that TCP/IP communication is possible between the manager host specified for executing the request and the requesting client host. If TCP/IP communication is possible or if the manager host and the requesting client host are the same, check the startup status of the following processes.

For Windows

If the message output process is the flow control process (ajsflowd.exe) or the job completion wait process (ajssubwd.exe), check whether the KAVU6100-I message has been output to the integrated trace log and whether the job execution control status notification process (jpqnfyd.exe) has been started. If the message output process is any other process (when the process name in the integrated trace log is UAP), make sure that the job execution control manager process (jpqman.exe) has started. If any of these processes has not started, restart the JP1/AJS3 service and retry the operation.

For UNIX

If the message output process is the flow control process (ajsflowd) or the job completion wait process (ajssubwd), check whether the KAVU6100-I message has been output to the integrated trace log and whether the job execution control status notification process (jpqnfyd) has been started. If the message output process is any other process (when the process name of the integrated trace log is UAP), check that the job execution control manager process (jpqman) has been started. If any of these processes has not started, restart the JP1/AJS3 service and retry the operation.

Also check the integrated trace log of the manager host for whether a KAVUxxxx message indicating a TCP/IP communication connection error was output before or after this message. If a KAVUxxxx message was output, read the message explanation. If no KAVUxxxx message has been output or if you cannot identify the cause of the problem, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the requesting client host.

KAVU0216-E

function-name: A timeout occurred for the request to acquire status notification.

A timeout occurred for the request to acquire status notification.

When acquiring the information on status notification for the job using the JpqGetReport and JpqOpenEnumReport functions supplied by JP1/AJS2 - Client Toolkit or JP1/AJS2 - SDK, the information on status notification could not be received within the period of time specified for the ulTimeout argument of these functions.

(S)

Cancels the requested processing.

(O)

Make sure that the job that will receive the status notification is correct, and then call the function again.

When acquiring the information on status notification for the job using the JpqGetReport and JpqOpenEnumReport functions supplied by JP1/AJS2 - Client Toolkit or JP1/AJS2 - SDK, retry in the application, or re-execute the application depending on the configuration of the application.

KAVU0217-E

function-name: The IP address could not be converted.

The network must be set up correctly so that the IP address can be determined from the specified host name by using the hosts file or the DNS server.

(S)

Cancels the requested processing.

(O)

Make sure that TCP/IP communication is available under the specified logical host name, and then call the function again.

KAVU0218-E

function-name: The manager cannot accept requests in the present status.

The manager cannot accept requests in the present status.

(S)

Cancels the requested processing.

(O)

Check the following possible causes, and then call the function again:

Check whether daemon operation has started.

Check whether the manager is running in reduced mode.

KAVU0219-E

function-name: The specified queue or agent does not exist.

The specified queue or agent does not exist.

(S)

Cancels the requested processing.

(O)

Check whether any of the following probable causes are present:

You changed the local host name after installing JP1, and then executed a job for the local agent.

The agent specified as the execution host in the jobnet or job definition was not defined in the manager.

The agent name defined in the manager is invalid.

No queue has been added.

The queue name or agent was specified incorrectly when a command with a name beginning with jpq was used.

The execution host of the job was specified using an IP address.

Take one of the following actions according to the cause of the error, and then re-execute.

Change the host name correctly according to 8.9.1 Changing the name of the host that runs JP1/AJS3 in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

Check the specification of the execution host name. If an incorrect host name is specified, specify the correct one. To add an agent definition to the manager, perform step 3, below.

Execute one of the following commands to define the correct agent.

- For a PC job, Unix job, action job, or custom job:

ajsagtadd command

- For a QUEUE job or submit job:

jpqimport or jpqagtadd command

Use the jpqqueadd command to add a queue.

Check the queue name or agent name.

As the execution host of the job, specify the name defined as an agent in the manager.

For details about the commands, see 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1 and 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0220-E

function-name: There is no response from the manager.

The manager does not respond.

(S)

Cancels the requested processing.

(O)

Check whether any of the following probable causes are present:

The specified port number is invalid.

A communication error occurred.

The manager is heavily loaded.

The specified transfer file size exceeds the value set in LimitReceiveFileSize environment setting parameter when the setting for limiting file reception was specified.

Take one of the following actions according to the cause of the error, and then re-execute.

Recheck the port number.

Check the network status.

Also check whether hardware, including network cards, cables, and hubs, is operating correctly.

Use the top command (in UNIX) or Task Manager (in Windows) to check the process that is causing a heavy load on the manager.

Also check whether the requested processing is performed just around the same time as the deletion of JP1/AJS3 job information.

If they are performed at the same time, change the schedule to delete the JP1/AJS3 job information when few jobs are being executed.

Check whether the size of the transfer file exceeds the value set in LimitReceiveFileSize environment setting parameter.

KAVU0221-E

function-name: An internal factor at the manager caused an error.

An error occurred because of an internal factor of the manager.

(S)

Cancels the requested processing.

(O)

Check the integrated trace log for whether a KAVUxxxx message was output before or after this message. If a KAVUxxxx message was output, read the message explanation to identify the cause of the error, remove the cause, and then call the function again. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU0222-E

function-name: The queue is closed.

No jobs can be registered because the queue entrance is closed.

(S)

Cancels the requested processing.

(O)

The action to be taken differs depending on the type of the job.

For a PC job, Unix job, action job, or custom job:

Use the ajsagtalt command to change the status of delivery-limitations for the execution agent to enabled, and then issue the request again.

For a QUEUE job or submit job:

Use the jpqqueopen command to open the queue entrance, and then issue the request again.

For details about the ajsagtalt command, see ajsagtalt in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1

For details about the jpqqueopen command, see jpqqueopen in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0223-E

function-name: The number of queued jobs in the specified queue reached the limit or the queue resources reached the limit.

The number of jobs registered in the queue has reached the maximum number of jobs allowed in the queue or the maximum number of jobs allowed in the system.

(S)

Cancels the requested processing.

(O)

Either wait for an executing job to end and then issue another request, or review the queue definition information and adjust the maximum number of jobs allowed in the queue or the system.

If the maximum number of jobs allowed in the queue has been reached, the KAVU4515-W message is output to the integrated trace log. If the maximum number of jobs allowed in the system has been reached, the KAVU4520-W message is output to the integrated trace log.

Take the corrective action specified in the message that is output.

KAVU0224-E

function-name: You lack operate permission.

The user requesting execution by the manager process for job execution control does not have the required JP1 permission level for the operation.

(S)

Cancels the requested processing.

(O)

Check the JP1 permission level of the user that issued the execution request.

Before you execute a command for job execution control, you must register the requesting OS user as a JP1 user on the authentication server. Also, if required, grant the JP1 user execute permission. For details about the execute permission required for commands, see 1.5 Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2. For details about how to set JP1 permission levels, see 3.1.1(1) Setting user information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 13.1.1(1) Setting user information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

KAVU0225-W

function-name: The job does not exist.

The job does not exist.

(S)

Cancels the requested processing.

(O)

No corresponding job was found when a command was executed for enumerating jobs. Make sure that the specified host name, queue name, and job status are correct, and then retry the operation.

If a command other than a command for enumerating jobs was executed, make sure that the specified job number is correct, and then retry the operation. Check the specified job number against the KAVUxxxx message that was output before or after this message to the standard error output or the integrated trace log.

KAVU0226-E

function-name: You cannot perform this operation because this job is being executed (or has not ended).

You cannot perform this operation because this job is being executed (or has not ended).

(S)

Cancels the requested processing.

(O)

Wait for the job to end, and then retry the operation.

KAVU0227-E

function-name: The destination queue does not exist.

The destination queue does not exist.

(S)

Cancels the requested processing.

(O)

Check the queue name specified as the name of the destination queue, check whether the queue exists, and then retry the operation.

KAVU0228-E

function-name: The destination queue has reached the queuing limit.

The number of jobs registered in the queue specified as the destination queue has reached the maximum number of jobs allowed in the queue.

(S)

Cancels the requested processing.

(O)

Either wait for an executing job to end before issuing another request, or check the queue definition information and adjust the maximum number of jobs allowed in the queue.

To check the number of jobs registered in the queue, which is the sum of the QUEUING and EXECUTING values, use the -q or -ah option in the jpqqueshow command. Also, to change the maximum number of jobs allowed in the queue, you can use the jpqquealt command. For details about these commands, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0231-W

function-name: There is no queue in the manager.

The manager host does not have any queue definition information.

(S)

Terminates the requested processing.

KAVU0232-E

function-name: No agent is connected to the manager.

There is no agent definition information on the manager host.

(S)

Cancels the requested processing.

(O)

You can use the jpqagtshow command to check the agent definition information. After checking for whether the specified agent definition information exists, retry the operation.

If you did not find the agent definition information, use the jpqagtadd command to add it dynamically.

For details about commands, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0233-E

function-name: The macro variable (macro-variable-name) has not been inherited.

The macro variable has not been inherited.

(S)

Places the job in the failed to start status.

(O)

The macro variable has not been inherited from the preceding job. Recheck the jobnet definition, and then re-execute the job.

KAVU0234-W

function-name: The status notification process is closed.

The status monitoring process has terminated because a JpqCloseReport or JpqCloseReportp function was issued while the request for acquiring the job status notification information was being processed.

(S)

Cancels the requested processing.

KAVU0235-E

function-name: The request to acquire status notification was already issued.

A request to acquire status notification for the specified job has already been issued.

(S)

Cancels the requested processing.

(O)

Make sure that no other process issued a request to acquire status notification, and then call the function again.

KAVU0236-E

function-name: The status was acquired by another acquisition status notification request.

Another request to acquire status notification already acquired status notification.

(S)

Cancels the requested processing.

(O)

Make sure that no other process issued a request to acquire status notification, and then call the function again.

KAVU0237-E

function-name: The manager (job status notification process) is busy.

The manager or job status notification process is busy.

(S)

Cancels the requested processing.

(O)

Re-execute the function after a while.

KAVU0238-E

function-name: Memory became insufficient at the manager (job status notification process).

Memory became insufficient at the manager or job status notification process.

(S)

Cancels the requested processing.

(O)

Terminate any other unnecessary applications, and then call the function again. If the same message reappears, re-estimate memory.

KAVU0239-E

function-name: VOS3 user information is invalid.

VOS3 user information is incorrect.

(S)

Cancels the requested processing.

(O)

Use the jpqreguser command to check whether the specified user is correctly registered, and then retry.

KAVU0240-E

function-name: A fatal error occurred in the manager (job status notification process).

A fatal error occurred in the manager or job status notification process.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then call the function again.

KAVU0241-E

function-name: A logical contradiction occurred in the manager (job status notification process).

An error was found in a communication protocol parameter in the manager or job status notification process. If this error message appears when JP1/AJS3 links to another system such as JP1/OJE for VOS3 or JP1/NQSEXEC, the other system may have a problem.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, see the explanation provided in that message to correct the cause of the error, and then reissue the request. If no such message was output or if the problem persists, use the data collection tool to collect data, and then contact the system administrator.

KAVU0242-E

function-name: The requested the manager does not support the request.

This message may be displayed if you operate a queue or agent in JP1/NQSEXEC or JP1/OJE for VOS3.

(S)

Cancels the requested processing.

(O)

Ask the system administrator whether the requested manager (product) can process the request.

KAVU0243-E

function-name: An error occurred after submission.

An error occurred after a job was submitted.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then call the function again.

KAVU0244-E

function-name: The execution environment is invalid.

An error disabling job execution has been detected. The cause of the error is an invalid system environment for job execution control.

(S)

Cancels the requested processing.

(O)

The authentication server may not be started. If this is the case, start the authentication server. If a KAVU2227-E message was output before this message, the IP address of the host issuing the request might be invalid. If this message was output, check whether the IP address output in the message is usable.

For all other cases, check the integrated trace log for whether a KAVUxxxx message was output before or after this message. If a KAVUxxxx message was output, read the message explanation, remove the cause of the problem, and then retry the request. If no KAVUxxxx message was output or if you are unable to solve the problem, use the data collection tool to collect data, and then contact the system administrator.

KAVU0245-E

function-name: The same external identifier already exists.

The same external identifier already exists.

(S)

Cancels the requested processing.

(O)

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

KAVU0246-E

function-name: The transfer file could not be created on the manager.

The function failed to create the file transferred when the job was submitted in the manager.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then call the function again.

KAVU0247-E

function-name: The transfer file could not be written on the manager.

The function failed to write the file transferred when the job was submitted in the manager.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then call the function again.

KAVU0248-E

function-name: The job was forcibly terminated, but it might not have terminated.

An attempt was made to forcibly terminate the job but the job may still be running.

(S)

Terminates the requested processing.

(O)

Use the integrated trace log to check the cause of the error.

KAVU0249-E

function-name: The job status notification has already been received in the same process.

The reception of the job status notification has already been started in the same process.

(S)

Cancels starting of the daemon.

(O)

Check whether the request is called more than once in the same process.

KAVU0250-E

function-name: The job status notification process cannot be created.

The job status notification process could not be created.

(S)

Cancels starting of the daemon.

(O)

Use the integrated trace log to determine the cause of the error and correct it. Then, call the function again.

KAVU0251-E

function-name: The job status notification could not be received because resources were insufficient when the notification started.

The reception of the job status notification could not be started because resources became insufficient when the notification started.

(S)

Cancels starting of the daemon.

(O)

Use the integrated trace log to determine the cause of the error and correct it. Then, call the function again.

KAVU0252-E

function-name: The job status notification process could not be started.

The job status notification process could not be started.

(S)

Cancels starting of the daemon.

(O)

Use the integrated trace log to determine the cause of the error and correct it. Then, call the function again.

KAVU0253-E

function-name: The file cannot be created because there is no path to the file specified as the acquisition destination of the standard output or standard error output file.

The file cannot be created because there is no path to the file specified to acquire the standard output or standard error output file.

(S)

Only acquires the information.

(O)

Check the path to the file, and then call then the function again.

KAVU0254-E

function-name: The file cannot be created because you lack access permission to the file specified as the acquisition destination of the standard output or standard error output file.

The file cannot be created because you do not have access permission for the file specified to acquire the standard output or standard error output file.

(S)

Only acquires the information.

(O)

Check the access permission for the path to the file, and then call the function again.

KAVU0255-E

function-name: The file cannot be opened because some other process is using the file specified as the acquisition destination of the standard output or standard error output file.

The file cannot be opened because another process is using the file specified to acquire the standard output or standard error output file.

(S)

Only acquires the information.

(O)

Terminate the process that is accessing the file, and then call the function again.

KAVU0256-E

function-name: The file specified as the acquisition destination of the standard output or standard error output file cannot be created.

The file specified to acquire the standard output or standard error output file cannot be created.

(S)

Only acquires the information.

(O)

Use the integrated trace log to determine the cause of the error and correct it. Then, call the function again.

KAVU0257-W

function-name: The specified exclusive execution resource name does not exist.

The system does not contain the specified exclusive execution resource name.

(S)

Cancels the requested processing.

(O)

Specify the correct exclusive execution resource name, and then call the function again.

KAVU0258-W

function-name: The specified queue or agent already exists.

The specified queue or agent already exists.

(S)

Cancels the requested processing.

(O)

Specify the correct queue name or agent name, and then call the function again.

KAVU0259-W

function-name: The specified exclusive execution resource name already exists.

The specified exclusive execution resource name already exists.

(S)

Cancels the requested processing.

(O)

Specify the correct exclusive execution resource name, and then call the function again.

KAVU0260-E

function-name: Failed to process because some job is being executed.

Some jobs cannot be changed or deleted because they are being executed.

(S)

Cancels the requested processing.

(O)

Waits until the job execution terminates, and then call the function again.

KAVU0261-E

function-name: Failed to process because of exceeding the maximum number defined in the environment settings.

Addition is impossible because the number of queues, agents, or exclusive execution resources exceeded the maximum number in the environment settings.

(S)

Cancels the requested processing.

(O)

Recheck the maximum number of definitions in the environment settings, and then call the function again.

KAVU0262-E

function-name: The specified agent cannot be deleted because some queue is connected.

The agent cannot be deleted because the agent is not disconnected from the queue.

(S)

Cancels the requested processing.

(O)

Disconnect the agent from the queue, and then call the function again.

KAVU0263-E

function-name: The specified agent is not connected.

The specified agent is not connected.

(S)

Cancels the requested processing.

(O)

Specify the correct agent, and then call the function again.

KAVU0264-E

function-name: The agent is already connected.

The specified agent has already been connected.

(S)

Cancels the requested processing.

(O)

Specify the correct agent, and then call the function again.

KAVU0265-W

function-name: There is no exclusive execution resource in the manager.

The specified exclusive execution resource is not defined.

(S)

Cancels the requested processing.

(O)

Correct the error, and then call the function again.

KAVU0266-W

function-name: The agent to be changed the priority is not connected.

The agent which priority you want to change is not connected.

(S)

Cancels the requested processing.

(O)

Specify the correct agent, and then call the function again.

KAVU0267-E

function-name: The agent cannot be added because the Event Action Manager is processing the modification of the agent.

The Event Action Control Manager is notified of addition of an agent. However, the Event Action Manager has already been modifying the agent configuration preventing the agent from being added due to a notification error.

(S)

Cancels the requested processing.

(O)

Waits until modification of the other agent terminates, and then call the function again.

KAVU0268-E

function-name: The agent cannot be deleted because the Event Action Manager is processing the modification of the agent.

The Event Action Control Manager is notified of deletion of an agent. However, the Event Action Manager has already been modifying the agent configuration preventing the agent from being deleted due to a notification error.

(S)

Cancels the requested processing.

(O)

Waits until modification of the other agent terminates, and then call the function again.

KAVU0269-E

function-name: Job could not be submitted because agent host was failed to create automatically.

The agent could not be automatically created. This prevented the job from being submitted.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then re-execute the job.

KAVU0270-W

function-name: The job might not be executable because a communication error occurred in the start processing. (scheduler-service-identification-number, maintenance-information)

A communication error occurred during the start processing.

(S)

Continues processing.

(O)

The job might not be executable by the scheduler service that uses the identification number output in the message.

If the job executed after this error message is still queued, check whether a KAVUxxxx message was output to the integrated trace log before or after this error message. If so, see the message explanation, remove the cause of the error, and then take the following action:

If maintenance-information is 0

No action is needed if no QUEUE jobs are to be executed.

If QUEUE jobs are to be executed, restart the scheduler service that uses the identification number output in the message.

If maintenance-information is not 0

No action is needed if the indicated scheduler service executes QUEUE jobs only.

If jobs other than QUEUE jobs or submit jobs are to be executed, restart the scheduler service that uses the identification number output in the message.

identification-number refers to the number specified in the -n option when you set a logical host using the jajs_setup_cluster command or set concurrent execution of the scheduler service using the jajs_setup command. If you are running JP1/AJS3 with the defaults set at installation, the identification number is 1. For details, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2 and 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0300-E

function-name: The logical host name could not be acquired.

The function cannot acquire the logical host name.

(S)

Cancels the requested processing.

(O)

Correct the error in the environment settings or correct the invalid definitions. Then, call the function again.

KAVU0301-E

function-name: No agent host name is specified.

An agent host name is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0302-E

function-name: The agent host name is too long.

The agent host name is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0303-E

function-name: The agent host name is invalid.

An incorrect agent host name is specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0304-E

function-name: No destination is specified for storing the acquired number of agent information.

The storage area for the number of agent information items is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0305-E

function-name: The standard error output file name at the agent is too long.

The name of the standard error output file at the agent is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0306-E

function-name: The standard output file name at the agent is too long.

The name of standard output file at the agent is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0307-E

function-name: The standard input file name at the agent is too long.

The name of standard input file at the agent is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0308-E

function-name: The destination for storing the agent name is too small.

The agent name storage area is too small.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0309-E

function-name: The type of open/close is specified incorrectly.

The queue open/close type is incorrectly specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0310-E

function-name: The status of job exit from the queue is invalid.

The status of the job exit of the queue is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0311-E

function-name: No destination is specified for storing the acquired number of connection information items about the queue and the agent.

The storage area for the number of information items on the connection between the queue and agent is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0312-E

function-name: The acquired number of connection information items about the queue and the agent is invalid.

The number of information items on the connection between the queue and agent is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0313-E

function-name: The destination for storing the connection information about the queue and the agent is invalid.

The storage area for information on the connection between the queue and agent is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0314-E

function-name: The destination for storing the connection information about the queue and agent is too small.

There are too few storage areas for information on the connection between the queue and agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0315-E

function-name: The status of job entrance for the queue is invalid.

The status of the job entrance of the queue is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0316-E

function-name: The process for the queue exit is invalid.

The invalid processing is specified for the job exit of the queue.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0317-E

function-name: No destination is specified for storing queue information.

The queue information storage area is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0318-E

function-name: The process for the queue entrance is invalid.

The invalid processing is specified for the job entrance of the queue.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0319-E

function-name: No queue name is specified.

A queue name is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0320-E

function-name: The queue name is too long.

A queue name is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0321-E

function-name: The queue name is invalid.

A queue name is invalid.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0322-E

function-name: No size is specified for the queue name storing destination.

The size of the queue name storage area is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0323-E

function-name: The client computer name could not be acquired.

The function failed to acquire the name of the client computer.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0324-E

function-name: The client host name is too long.

The client host name is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0325-E

function-name: The service name (service-name) could not be acquired.

The function failed to acquire the service name.

(S)

Cancels the requested processing.

(O)

Check the services file, specify a correct port number and then call the function again.

KAVU0326-E

function-name: The request destination user name is too long.

The name of the VOS3 user you registered is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0327-E

function-name: The request destination password is too long.

The password of the VOS3 user you registered is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0328-E

function-name: The request group name is too long.

The group name of the VOS3 user you registered is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0329-E

function-name: The type of the submit destination name is invalid.

The type of the submit destination is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0330-E

function-name: No destination is specified for storing the submit destination name type.

The storage area for the type of the submit destination name is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0331-E

function-name: The job number is invalid.

The job number is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0332-E

function-name: No destination is specified for storing the job number.

The storage area for the job number is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0333-E

function-name: No job submit date is specified.

The date/time when the job will be submitted is not specified.

(S)

Cancels the requested processing.

(O)

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

KAVU0334-E

function-name: The job submit date is invalid.

The job submit date/time is incorrect.

(S)

Cancels the requested processing.

(O)

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

KAVU0335-E

function-name: No external identifier is specified to the job.

The external identifier to be assigned to the job is not specified.

(S)

Cancels the requested processing.

(O)

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

KAVU0336-E

function-name: The external identifier to the job is too long.

The length of the external identifier to be assigned to the job is incorrect.

(S)

Cancels the requested processing.

(O)

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

KAVU0337-E

function-name: The job recovery status is specified incorrectly.

An incorrect job recovery status is specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0338-E

function-name: The job execution method is specified incorrectly.

An incorrect job execution method is specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0339-E

function-name: The method for judging the job end status is specified incorrectly.

The method of judging the job end status is incorrectly specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0340-E

function-name: No file name is specified for the job end judgment.

The name of the file for determining whether the job is terminated normally or abnormally is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0341-E

function-name: The file name for the job end judgment is too long.

The name of the file for determining whether the job is terminated normally or abnormally is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0342-E

function-name: The job request user name is too long.

The name of the user who requested the job is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0343-E

function-name: Job moving destination queue name is too long.

The name of the queue to which you want to move jobs is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0344-E

function-name: Job execution account name is too long.

The name of the job execution account is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0345-E

function-name: No job execution start date is specified.

The job start date/time is not specified.

(S)

Cancels the requested processing.

(O)

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

KAVU0346-E

function-name: The job execution start date is invalid.

The job start date/time is incorrect.

(S)

Cancels the requested processing.

(O)

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

KAVU0347-E

function-name: No job execution end date is specified.

The job end date/time is not specified.

(S)

Cancels the requested processing.

(O)

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

KAVU0348-E

function-name: The job execution end date is invalid.

The job end date/time is incorrect.

(S)

Cancels the requested processing.

(O)

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

KAVU0349-E

function-name: The job time-out period is out of range.

The timeout for job execution is out of range.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0350-E

function-name: No job owner name is specified.

The job owner name is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0351-E

function-name: The job owner name is too long.

The job owner name is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0352-E

function-name: The job owner name cannot be specified.

You cannot specify a job owner name.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0353-E

function-name: No detailed information is specified about the job.

The details of the job are not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0354-E

function-name: The destination for storing job information is specified incorrectly.

The job information storage area is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0355-E

function-name: The job status is invalid.

The job status is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0356-E

function-name: The requested amount of information is invalid.

The number of requests for information is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0357-E

function-name: The direction of the job insert relative position is specified incorrectly.

The direction for the relative position where the job should be inserted is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0358-E

function-name: The job definition information is invalid.

The job definition has an error.

(S)

Cancels the requested processing.

(O)

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

KAVU0359-E

function-name: The size of the job definition information is invalid.

The size of the job definition information is invalid.

(S)

Cancels the requested processing.

(O)

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

KAVU0360-E

function-name: A parameter error occurred during the analysis of the job definition information.

A parameter error occurred while the function was analyzing the job definition.

(S)

Cancels the requested processing.

(O)

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

KAVU0361-E

function-name: Memory became insufficient while analyzing the job definition information.

Memory became insufficient while the function was analyzing the job definition.

(S)

Cancels the requested processing.

(O)

Terminate any other unnecessary applications, and then call the function again. If the same message reappears, re-estimate memory.

KAVU0362-E

function-name: An unknown error occurred while analyzing the job definition information.

An error of unknown origin occurred while the function was analyzing the job definition.

(S)

Cancels the requested processing.

(O)

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

KAVU0363-E

function-name: No job name is specified.

A job name is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0364-E

function-name: The job name is too long.

A job name is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0366-E

function-name: The script is too long.

A script statement is too long.

(S)

Cancels the requested processing.

(O)

If you are using a macro variable, make sure that passed information is not too long.

If you are using the option that validates a double quotation mark ("), passed information may become longer than the limit of the number of characters because " in the passed information is replaced by \".

KAVU0367-E

function-name: The process priority is invalid.

The process priority is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0368-E

function-name: The port number is invalid.

A port number is incorrect.

(S)

Cancels the requested processing.

(O)

Check the services file, specify a correct port number, and then call the function again.

KAVU0369-E

function-name: The process of analyzing the macro valuable failed.

The function failed to analyze macro variables.

(S)

Cancels the requested processing.

(O)

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

KAVU0370-E

function-name: The macro variable is specified incorrectly.

An incorrect macro variable is specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0371-E

function-name: The response data from the manager is invalid.

The response from the manager is incorrect.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then call the function again.

KAVU0372-E

function-name: Enumerated information returned from the manager is invalid.

Enumerated information returned from the manager is incorrect.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then call the function again.

KAVU0373-E

function-name: The host name of manager is too long.

The manager host name is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0374-E

function-name: No destination is specified for storing the operating status of the manager.

The storage area for the manager operation status is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0375-E

function-name: Memory could not be allocated.

The function failed to allocate memory.

(S)

Cancels the requested processing.

(O)

Terminate any other unnecessary applications, and then call the function again. If the same message reappears, re-estimate memory.

KAVU0376-E

function-name: The exclusive execution resource name is too long.

The name of an exclusive execution resource is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0377-E

function-name: The work path name is too long.

The work path name is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0378-E

function-name: The abnormal end threshold is invalid.

The threshold for the abnormal termination status is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0379-E

function-name: The transmission source file name is too long.

The transmission source file name is too long.

(S)

Places the job in the failed to start status.

(O)

The macro variable specified for the transmission source file name may be too long as a result of replacement.

Recheck the specification of the inherited information and the transmission source file name, and then re-execute the job.

KAVU0380-E

function-name: The transmission destination file name is too long.

The transmission destination file name is too long.

(S)

Places the job in the failed to start status.

(O)

The macro variable specified for the transmission destination file name may be too long as a result of replacement.

Recheck the specification of the inherited information and the transmission destination file name, and then re-execute the job.

KAVU0383-E

function-name: The environment variable information is invalid.

Environment variable information is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0384-E

function-name: The environment variable information is too big.

The amount of environment variable information is too large.

(S)

Cancels the requested processing.

(O)

If you are using a macro variable, make sure that passed information is not too large.

KAVU0385-E

function-name: The size of the environment variable information is invalid.

The amount of environment variable information is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0386-E

function-name: The environment variable information file name is too long.

The name of the file for environment variable information is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0389-E

function-name: The warning end threshold is invalid.

The threshold for warned termination is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0390-E

function-name: The user name of the own process cannot be acquired.

The function cannot acquire the user name of the local process.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then call the function again.

KAVU0391-E

function-name: The execution shell path name is too long.

The path name of the shell to execute is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0392-E

function-name: A command parameter for the execution file is too long.

The command parameters for the executable file are too long.

(S)

Cancels the requested processing.

(O)

If you are using a macro variable, make sure that passed information is not too large.

If you are using the option that validates a double quotation mark ("), passed information may become larger than the limit of the number of characters because " in the passed information is replaced by \".

KAVU0393-E

function-name: The execution file name is too long.

The name of the executable file is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0395-E

function-name: Neither the execution file name nor the execution script is specified.

Neither an executable file name nor an execution script statement is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0396-E

function-name: The time out value for reception-waiting is invalid.

The timeout for reception is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0397-E

function-name: The start date is invalid in enumerating the end time of the end job.

The start date/time from which to enumerate the terminated jobs based on their end times is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0398-E

function-name: The end date is invalid in enumerating the end time of the end job.

The end date/time to which to enumerate the terminated jobs based on their end times is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0399-E

function-name: The status report identifier is invalid.

The identifier for status notification is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0400-E

function-name: No destination is specified for storing the status report identifier.

The storage area for the identifier for status notification is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0401-E

function-name: The destination for storing the status report information is invalid.

The storage area for the information on status notification is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0402-E

function-name: No information is specified about the host to which the status is reported.

The information on the destination host for status notification is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0403-E

function-name: The specified client computer name is too long.

A too long client computer name is defined.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0404-E

function-name: The start time of the concurrently-executable job limit information is invalid.

The start time of the concurrently-executable job limit information is invalid.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0405-E

function-name: The end time for the concurrently-executable job limit information is invalid.

The end time for the concurrently-executable job limit information is invalid.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0406-E

function-name: The number for storing the concurrently-executable job limit information is too small.

The number for storing the concurrently-executable job limit information is too small.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0407-E

function-name: The destination for storing the concurrently-executable job limit information is invalid.

The destination for storing the concurrently-executable job limit information is invalid.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0408-E

function-name: No transfer file information is specified.

Information on the file to be transferred is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0409-E

function-name: The number of transfer files is invalid.

The number of files to be transferred is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0410-E

function-name: The specification of whether to output the standard error output file is invalid.

Whether to output errors to the standard error output file is incorrectly specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0411-E

function-name: The method for writing the standard error output file is specified incorrectly.

How to write data to the standard error output file is incorrectly specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0414-E

function-name: The path name for the standard error output file is too long.

The path name of the standard error output file is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0415-E

function-name: The file name for the standard error output file and the additional write flag specification do not match.

The name of the standard error output file and the specification of the Append flag do not match.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0416-E

function-name: The specification of whether to output the standard output file is invalid.

Whether to output data to the standard output file is incorrectly specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0417-E

function-name: The method for writing the standard output file is specified incorrectly.

How to write data to the standard output file is incorrectly specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0420-E

function-name: The standard output file path name is too long.

The path name of the standard output file is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0421-E

function-name: The file name for the standard output file and the additional write flag specification do not match.

The name of the standard output file and the specification of the Append flag do not match.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0422-E

function-name: The path name for the standard input file is too long.

The path name of the standard input file is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0423-E

function-name: An invalid agent name was returned.

An incorrect agent name is returned.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then call the function again.

KAVU0424-E

function-name: An invalid queue name was returned.

An incorrect queue name is returned.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then call the function again.

KAVU0425-E

function-name: The character code is specified incorrectly.

An incorrect character code is specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0426-E

function-name: The number of agent information to be changed is invalid.

The number of agent information items to be changed is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0427-E

function-name: The flag specifying hold or release is invalid.

The flag for determining whether to hold jobs is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0428-E

function-name: The flag for registering hold jobs is invalid.

The flag for registering the jobs to hold is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0429-E

function-name: The destination for storing the number of enumerated jobs is specified incorrectly.

The storage area for the number of enumerated job information items is incorrectly specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0430-E

function-name: The flag indicating the job status to be enumerated is invalid.

The flag for the status of jobs to enumerate is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0431-E

function-name: The enumerated handle is invalid.

An enumeration handle is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0432-E

function-name: The password could not be created.

The function failed to create a password for the VOS3 user.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then call the function again.

KAVU0433-E

function-name: The execution start date for the specified job is too long.

The start date/time for the specified job is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0434-E

function-name: The name of the host to which the status is reported is too long.

The name of the destination host for status notification is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0435-E

function-name: No destination is specified for storing the current concurrently-executable job limit.

The storage area for the current number of concurrently-executable job limit to acquire is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0436-E

function-name: No destination is specified for storing the number of currently executing jobs.

The storage area for the number of currently executed jobs to acquire is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0437-E

function-name: No type is specified for the job status to be reported.

The job status type for the status notification to send is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0438-E

function-name: The warning end threshold value exceeds the abnormal end threshold value.

The threshold for warned termination exceeds the threshold for abnormal termination.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0439-E

function-name: The moving destination queue cannot be specified when the home agent host name is specified.

You cannot specify the destination queue if you specify an agent host as the host from which to move jobs.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0440-E

function-name: The direction of the job insert relative position cannot be specified when moving to another queue.

You cannot specify the direction of the relative position where to insert jobs when moving jobs to another queue.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0441-E

function-name: The job insert relative position cannot be specified when moving to another queue.

You cannot specify the relative position where to insert jobs when moving jobs to another queue.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0442-W

function-name: The standard output file used in the system could not be deleted.

The function failed to delete the standard output file that the system uses.

(S)

Continues requested processing.

KAVU0443-W

function-name: The standard error output file used in the system could not be deleted.

The function failed to delete the standard error output file that the system uses.

(S)

Continues requested processing.

KAVU0451-E

function-name: The exclusive execution resource name is not specified.

The exclusive execution resource name is missing. The information cannot be displayed.

(S)

Cancels the requested processing.

(O)

Specify the exclusive execution resource name, and then call the function again.

KAVU0452-E

function-name: The size of exclusive execution resource name buffer is not specified.

The size of the buffer for the exclusive execution resource name is missing. The information cannot be acquired.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to determine the cause of the error and correct it. Then, call the function again.

KAVU0453-E

function-name: The maximum number of queuing jobs is out of range.

The maximum number of queued jobs is out of range (1 to 4,294,967,295).

(S)

Cancels the requested processing.

(O)

Specify the appropriate value for the maximum number of queued jobs, and then call the function again.

KAVU0454-E

function-name: The warning number of queuing jobs is out of range.

The number of queued jobs that causes a warning message is out of range (1 to 4,294,967,295).

(S)

Cancels the requested processing.

(O)

Specify the appropriate value for the warning number of queued jobs, and then call the function again.

KAVU0455-E

function-name: The priority value is not specified.

The priority is missing.

(S)

Cancels the requested processing.

(O)

Specify the priority, and then call the function again.

KAVU0456-E

function-name: The exclusive execution resource information is not specified.

The information about the exclusive execution resource is not set.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to determine the cause of the error and correct it. Then, call the function again.

KAVU0457-E

function-name: The job number is not specified.

The job number is missing.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to determine the cause of the error and correct it. Then, call the function again.

KAVU0458-E

function-name: The concurrently-executable job limit is invalid.

The time value of the concurrently-executable job limit is invalid, or the concurrently-executable job limit is out of range (0 to 4,294,967,295).

(S)

Cancels the requested processing.

(O)

Specify the appropriate value for the concurrently-executable job limit, and then call the function again.

KAVU0459-E

function-name: The maximum number of jobs is not specified.

The maximum number of queued jobs is missing.

(S)

Cancels the requested processing.

(O)

Specify the maximum number of queued jobs, and then call the function again.

KAVU0460-E

function-name: The warning number of jobs is not specified.

The warning number of queued jobs is missing.

(S)

Cancels the requested processing.

(O)

Specify the warning number of queued jobs, and then call the function again.

KAVU0461-E

function-name: The exclusive execution resource status is invalid.

The status of the exclusive execution resource is invalid.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to determine the cause of the error and correct it. Then, call the function again.

KAVU0462-E

function-name: Job number that use the exclusive execution resource is invalid.

The number of the jobs that is using the exclusive execution resource is invalid.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to determine the cause of the error and correct it. Then, call the function again.

KAVU0463-E

function-name: The warning number of jobs cannot be larger than the max number of jobs.

The warning number of queued jobs for the specified queue is larger than the maximum number of queued jobs allowed for that queue, or the maximum number is smaller than the warning number.

If you modify the warning number of queued jobs, compare it to the maximum number currently set for the queue. If you modify the maximum number, compare it to the warning number currently set for the queue.

(S)

Cancels the requested processing.

(O)

Check the values you specified or the values currently set for the queue, and modify them to appropriate values. Then, call the function again.

KAVU0464-E

function-name: An invalid exclusive execution resource name was returned.

The manager returned an invalid exclusive execution resource name.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to determine the cause of the error and correct it. Then, call the function again.

KAVU0465-E

function-name: The specified port number is invalid.

If you set the option to specify the port number, the system recognizes the value following the colon (:) in the queue name as the port number. Specify the port number that consists of five digits or less.

(S)

Cancels the requested processing.

(O)

Specify the correct port number, and then call the function again.

KAVU0466-E

function-name: The agent name cannot be changed.

The agent host name is specified for modifying the queue name.

(S)

Cancels the requested processing.

(O)

Specify the correct queue name, and then call the function again.

KAVU0467-E

function-name: The specification of the manager host name is invalid (host-name).

The host name specified as the manager host name is invalid.

(S)

Cancels command execution.

(O)

Check whether a remote host name is specified for an urgent command, and then call the function again.

KAVU0470-E

The job termination request failed.

The agent host was requested to forcibly terminate a job, but the attempt to forcibly terminate the job has failed.

(S)

Cancels the requested processing.

(O)

See the explanation of the KAVUxxxx message that was output before or after this message. Also use the integrated trace logs for the manager host and agent host to check whether a KAVUxxxx message for this job was output. If it was output, also see the explanation of that message. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU0471-W

The job does not exist. But the job might have ended.

A forced termination of a job was requested, but the requested job was not found.

(S)

Terminates the requested processing.

(O)

The job might not have been executed, or the job might have terminated on the agent host before the forced termination. Use either of the following methods to check the status of the job.

For a PC job, Unix job, action job, or custom job:

Check JP1/AJS - View or execute the ajsshow command.

For a QUEUE job or submit job:

Execute the jpqjobget command.

Other probable causes of the error are:

The JP1/AJS3 service on the agent host stopped after the sending of job information from the agent host to the manager host failed.

The JP1/AJS3 service terminated abnormally while the job was running on the agent host.

Use the integrated trace logs for the manager host and agent host to check whether a KAVUxxxx message for this job was output. If it was output, also see the explanation of that message. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU0474-E

function-name: The job execution environment database is currently undergoing maintenance.

The job execution environment is undergoing maintenance.

(S)

Cancels maintenance of the job execution environment.

(O)

Check whether the jajs_maintain process exists, and if necessary, re-execute the command.

KAVU0476-E

function-name: The job number cannot be assigned.

The job number cannot be assigned because the number of jobs that have not ended yet has exceeded the limit.

(S)

Terminates the requested processing.

(O)

Wait for an executing job to end, and then re-execute the job.

KAVU0477-E

function-name: Insufficient tablespace or RDAREA.

There is no free space in the tablespace or RDAREA.

(S)

Terminates the requested processing.

(O)

Create free space (for example, reorganize the tablespace or RDAREA or increase the tablespace), and then re-execute the job.

A detailed error message regarding the database is output to the Windows event log or syslog. For an embedded DB, the KFPH00211-I message is output. For details about how to reorganize the database, see 10.2.2 Reorganizing a database in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

KAVU0478-E

function-name: The database table is locked.

The database table is now locked.

(S)

Terminates the requested processing.

(O)

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

KAVU0479-E

function-name: You lack operate permission for the database.

The user attempting the operation does not have operate permission for the database.

(S)

Terminates the requested processing.

(O)

Specify a user that has the required permission, and re-issue the call.

KAVU0480-E

function-name: Could not connect to the database.

The system could not connect to the database.

(S)

Terminates the requested processing.

(O)

Check whether the database is running.

If this message is output while JP1/AJS3 is running, start the database and then restart JP1/AJS3

KAVU0481-E

function-name: A system error occurred during a database process.

A system error occurred during database processing.

(S)

Terminates the requested processing.

(O)

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

If this message is output while JP1/AJS3 is running, check whether the database is running. If the database is not running, start the database and then restart JP1/AJS3.

KAVU0482-E

function-name: A logical contradiction occurred during a database process.

An invalid parameter was detected during database processing.

(S)

Terminates the requested processing.

(O)

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

KAVU0483-E

function-name: The system file (system-file-name) cannot be opened.

An attempt to open the system file has failed.

(S)

Terminates the requested processing.

(O)

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

KAVU0484-E

function-name: The system file cannot be closed. (number of files: number-of-files)

An attempt to close the system file has failed.

(S)

Terminates the requested processing.

(O)

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

KAVU0485-E

function-name: The system file (system-file-name) cannot be accessed.

An attempt to access the system file has failed.

(S)

Terminates the requested processing.

(O)

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

KAVU0486-E

function-name: The system file (system-file-name) cannot be written.

An attempt to write to the system file has failed.

(S)

Terminates the requested processing.

(O)

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

KAVU0487-E

function-name: The system file (system-file-name) cannot be read.

An attempt to read the system file has failed.

(S)

Terminates the requested processing.

(O)

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

KAVU0488-E

function-name: A system call error occurred in the internal process.

A system call error occurred in the internal process.

(S)

Terminates the requested processing.

(O)

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

KAVU0489-E

function-name: The system file (system-file-name) could not be removed because a system call error occurred.

The system file (a temporary file for job execution control) could not be deleted due to a system call error.

(S)

Cancels the deletion of the system file.

(O)

The system file is stored in the scheduler service's directory for temporary files.

Check whether the directory specified in the AJSTMPDIR environment setting parameter for the definition key [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name] exists, and also check the access permissions.

For details about the AJSTMPDIR environment setting parameter, see 2.2.2(53) AJSTMPDIR in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVU0490-W

function-name: The system file (system-file-name : reason-code) could not be removed because a system call error occurred.

The system file (a temporary file for job execution control) could not be deleted due to a system call error.

(S)

Cancels the deletion of the system file.

(O)

The system file is stored in the scheduler service's directory for temporary files.

Check whether the directory specified in the AJSTMPDIR environment setting parameter for the definition key [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name] exists, and also check the access permissions. If necessary, delete the file indicated by system-file-name in the message.

For details about the AJSTMPDIR environment setting parameter, see 2.2.2(53) AJSTMPDIR in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVU0491-E

function-name: Execution of a job at a destination that does not permit execution was suppressed according to the settings specified in the execution agent profile. (logical-host-name:scheduler-service-name:agent-host:maintenance-information)

The execution agent specified when requesting job execution is not permitted to be a target host in its execution agent profile.

(S)

Ends the job abnormally in Failed to start status.

(O)

The probable causes are:

An incorrect execution agent name is specified in the detailed definition of the job.

The permitted target host is wrongly specified in the execution agent profile.

If the execution agent name is incorrectly specified in the detailed definition of the job, correct the value and then re-execute the job.

If the execution agent profile is wrong, correct the settings and then execute the ajsprofalter command to apply the correct profile to the scheduler service. Then re-execute the job.

KAVU0492-E

The request was rejected.

The request was rejected because the IP address of the connecting host was not registered in the manager connection permission configuration file on the destination host.

(S)

Continues processing.

(O)

Take the corrective action specified in the KAVU4335-E message that was output to the integrated trace log on the manager host that received the request.

KAVU0500-E

function-name: Database information could not be obtained.

Database information about the job execution environment could not be obtained.

(S)

Cancels the requested processing.

(O)

Check the following, and then call the function again:

Check whether system resources are sufficient.

Check whether the environment settings for JP1/AJS3 have been made correctly.

Check whether the database has been created correctly.

KAVU0800-I

The user profile was registered.

The jpqreguser command registered VOS3 user information in the JP1/AJS3 host.

(S)

Continues processing.

KAVU0801-I

The user profile was deleted.

The jpqreguser command deleted VOS3 user information from the JP1/AJS3 host.

(S)

Continues processing.

KAVU0802-I

The user profile was updated.

The jpqreguser command updated VOS3 user information.

(S)

Continues processing.

KAVU0803-I

The user profile information will be enumerated.

The jpqreguser command will now start the enumeration of registered VOS3 user information.

(S)

Continues processing.

KAVU0804-I

Enumerating user profile information ended normally.

The jpqreguser command terminated the enumeration of registered VOS3 user information normally.

(S)

Continues processing.

KAVU0810-I

The job (job-number) was submitted.

The job was registered.

(S)

Continues processing.

KAVU0811-I

The job (job-number) was canceled.

The job was terminated forcibly. A job that is waiting for execution, being held, or waiting for time is canceled. Alternatively, a job being executed is terminated forcibly.

(S)

Continues processing.

KAVU0812-I

The job (job-number) status was changed (held / released).

The job status was changed to held or released.

(S)

Continues processing.

KAVU0813-I

The job (job-number) was moved.

The job in the queue was moved.

(S)

Continues processing.

KAVU0814-I

The job (job-number) information was deleted.

The job information and the result file for the terminated job have been deleted from the job execution environment database.

(S)

Continues processing.

KAVU0815-I

The job (job-number) information will be displayed.

The job information (including the job number, job name, job status, and registration time) will be output.

(S)

Continues processing.

KAVU0816-I

Displaying the job information ended normally.

The display of job information terminated normally.

(S)

Continues processing.

KAVU0817-I

JP1 user (assumed-JP1-user-name) is registered for assumed JP1 user.

The system registers the specified JP1 user as an assumed JP1 user and enables the JP1 user assuming function.

(S)

Continues processing.

KAVU0818-I

Assumed JP1 user (assumed-JP1-user-name) is deleted.

The assumed JP1 user was deleted.

(S)

Continues processing.

KAVU0819-I

Assumed JP1 user (assumed-JP1-user-name) is registered.

The currently registered assumed JP1 user is displayed.

(S)

Continues processing.

KAVU0820-I

The job information will be enumerated.

The list of job information for unfinished jobs will be displayed.

(S)

Continues processing.

KAVU0821-I

Enumerating the job information ended normally.

The display of job information (including the job number, job name, and job status) for unfinished jobs terminated normally.

(S)

Continues processing.

KAVU0822-I

Assumed JP1 user is not registered.

The assumed JP1 user is not currently registered.

(S)

Continues processing.

KAVU0825-I

The end job information will be enumerated.

The list of job information for terminated jobs will be displayed.

(S)

Continues processing.

KAVU0826-I

Enumerating the end job information ended normally.

The display of a job information list (including the job number, job name, and job status) for terminated jobs terminated normally.

(S)

Continues processing.

KAVU0835-I

Queue Entrance / Queue Exit of the queue (queue-name) was opened.

The job entrance or exit interface of the queue was opened.

(S)

Continues processing.

KAVU0836-I

Queue Entrance / Queue Exit of the queue (queue-name) was closed.

The job entrance or exit interface of the queue was closed.

(S)

Continues processing.

KAVU0837-I

The queue (queue-name) information will be displayed.

The queue information (including the queue name, the maximum number of jobs that can be registered, the warning value for the registered jobs, and the number of registered jobs) will be displayed.

(S)

Continues processing.

KAVU0838-I

Default queue (queue-name) information will be displayed.

The default queue information (including the queue name, the maximum number of jobs that can be registered, the warning value for the registered jobs, and the number of registered jobs) will be displayed.

(S)

Continues processing.

KAVU0839-I

All queue information except default queue will be displayed.

Information about queues other than the default queue will be displayed.

(S)

Continues processing.

KAVU0840-I

All queue information including default queue will be displayed.

Information about all of the queues including the default queue will be displayed.

(S)

Continues processing.

KAVU0841-I

The queue names will be enumerated.

The queue names other than the default queue will be output.

(S)

Continues processing.

KAVU0842-I

Displaying the queue information ended normally.

The display of queue information terminated normally.

(S)

Continues processing.

KAVU0850-I

The agent (agent-name) definition was changed.

The agent definition information (maximum number of concurrently executable jobs) was changed.

(S)

Continues processing.

KAVU0851-I

The agent host (agent-name) information will be displayed.

The agent host information will be displayed.

(S)

Continues processing.

KAVU0852-I

All agent host information will be displayed.

All agent host information will be displayed.

(S)

Continues processing.

KAVU0853-I

The agent host names will be enumerated.

All the agent host names will be displayed.

(S)

Continues processing.

KAVU0854-I

Displaying the agent host information ended normally.

The display of agent host information terminated normally.

(S)

Continues processing.

KAVU0860-I

The queue (queue-name) was added.

The queue was added.

(S)

Continues processing.

KAVU0861-I

The queue (queue-name) was deleted.

The queue was deleted.

(S)

Continues processing.

KAVU0862-I

The queue (queue-name) definition was changed.

The queue definition information was changed.

(S)

Continues processing.

KAVU0863-I

The agent (agent-name) was connected.

The queue was connected to the agent.

(S)

Continues processing.

KAVU0864-I

The agent (agent-name) was released.

The connection between the queue and the agent was released.

(S)

Continues processing.

KAVU0865-I

The agent (agent-name) was added.

The agent host was added.

(S)

Continues processing.

KAVU0866-I

The agent (agent-name) was deleted.

The agent host was deleted.

(S)

Continues processing.

KAVU0867-I

The exclusive execution resource name (execution-locked-resource-name) was added.

The exclusive execution resource was added.

(S)

Continues processing.

KAVU0868-I

The exclusive execution resource name (execution-locked-resource-name) was deleted.

The exclusive execution resource was deleted.

(S)

Continues processing.

KAVU0869-I

The exclusive execution resource name will be enumerated.

All the exclusive execution resource names will be displayed.

(S)

Continues processing.

KAVU0870-I

The exclusive execution resource (execution-locked-resource-name) information will be displayed.

Information about the exclusive execution resource will be displayed.

(S)

Continues processing.

KAVU0871-I

All exclusive execution resource information will be displayed.

Information about all the exclusive execution resources will be displayed.

(S)

Continues processing.

KAVU0872-I

Enumerating the exclusive execution resource name ended normally.

Enumerating the exclusive execution resource names locked for execution terminated normally.

(S)

Continues processing.

KAVU0873-I

Displaying the exclusive execution resource (execution-locked-resource-name) information ended normally.

The display of information about the exclusive execution resource terminated normally.

(S)

Continues processing.

KAVU0874-I

Displaying all exclusive execution resource information ended normally.

The display of information about all the exclusive execution resources terminated normally.

(S)

Continues processing.

KAVU0875-I

The agent (agent-name) priority was changed.

The priority of the connected agent host was changed.

(S)

Continues processing.

KAVU0900-E

Invalid option (option-name).

An invalid option is specified.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0901-E

The option (option-name) is used more than once.

The option is used more than once.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0902-E

A required option (option-name) is missing.

A required option is not specified.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0903-E

Only administrator can use option (option-name).

Only the administrator can use the option.

(S)

Cancels command execution.

(O)

Re-execute the command as an administrator.

KAVU0904-E

Illegal character (invalid-character) in operand (operand-name).

The argument includes an invalid character.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0905-E

The operand (operand-name) exceeds the specifiable number of characters (number-of-characters).

The number of characters used in the argument exceeds the maximum.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0906-E

A required operand (operand-name) is missing.

A required argument is not specified.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0907-E

Value (preset-value) in operand (operand-name) exceeds the limit.

A value exceeding the maximum is specified in an argument.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0908-E

Character (invalid-character) in operand (operand-name) is not a number.

An argument includes a non-numeric character.

(S)

Cancels command execution.

(O)

Specify a number for the argument, and then re-execute the command.

KAVU0909-E

Invalid data format in operand (operand-name).

The data format of the argument is incorrect.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0910-E

An unexpected error occurred. (reason code:reason-code)

Invalid data was detected during parameter analysis.

(S)

Cancels command execution.

(O)

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

KAVU0911-E

The options (option-name) and (option-name) cannot be specified simultaneously.

The indicated two options cannot be both present.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0912-E

Environment settings or the logical host name is invalid.

The environment settings are incorrect or the logical host name is invalid.

(S)

Cancels command execution.

(O)

Check the environment settings or the logical host name, and then re-execute the command.

KAVU0913-E

Unexpected error occurred. Aborted. (module:reason-location[reason-location], reason code:reason-code)

Initialization failed at the time of a command startup.

(S)

Cancels command execution.

(O)

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

KAVU0914-E

Insufficient options specified.

The required option is missing.

(S)

Cancels command execution.

(O)

Specify the option, and then re-execute the command.

KAVU0917-E

The specification of the manager host name is invalid.

The host name specified as the manager host name is invalid.

(S)

Cancels command execution.

(O)

Check whether a remote host name is specified for an urgent command, and then call the function again.

KAVU0920-E

Parameter is specified incorrectly.

An incorrect parameter is specified.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

If the character encoding on the host on which you executed the command is different from the encoding on the manager host, the data size might have increased due to character code conversion during data transfer.

If character codes are converted on the manager host, make sure that the number of characters for each argument does not exceed the specifiable number of characters.

KAVU0921-E

The command could not be executed because of internal factor.

The system failed to execute the command because of an internal factor.

(S)

Cancels command execution.

(O)

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

KAVU0922-E

Memory became insufficient.

Memory became insufficient.

(S)

Cancels command execution.

(O)

Terminate any other unnecessary applications, and then re-execute the command. If the same message reappears, re-estimate memory.

KAVU0923-E

A logical contradiction occurred.

An invalid error was detected during command initialization.

(S)

Cancels command execution.

(O)

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

KAVU0924-E

The file cannot be opened because file path or file does not exist at the send source.

The system cannot open the file because the file path of the transfer source file is incorrect or the file does not exist.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0925-E

The file cannot be opened because you lack access permission for the file at the send source.

The system cannot open the file because the access authority for the transfer source file is not granted.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0926-E

The file cannot be opened because some other process is using the file at the send source.

The system cannot open the file because another process is using the transfer source file.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0927-E

The file at the send source cannot be opened.

The system cannot open the transfer source file.

(S)

Cancels command execution.

(O)

The system may not accept the format or the length of the file name. Check the original file name specified.

KAVU0928-E

The file at the send source cannot be read.

The system failed to read the transfer source file.

(S)

Cancels command execution.

(O)

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

KAVU0929-E

No file path is specified for the file that acquires the standard output file or standard error output file, so the file cannot be created.

A file cannot be created because no file path has been specified for the file used to acquire the data in the standard output file or the standard error output file.

If the jpqjobget command was used, no file was specified in the -oso or -ose option.

(S)

Cancels command execution.

(O)

Check whether a file (and its path) has been specified for the file used to acquire the data in the standard output file or the standard error output file. If there is neither a file nor a path, create them both, and then re-execute the command.

KAVU0930-E

You lack access permission for the file specified as the file that acquires the standard output file or standard error output file, so the file cannot be created.

A file cannot be created because no access permissions have been set for the file used to acquire the data in the standard output file or the standard error output file.

If the jpqjobget command was used, there is no write permission on the file specified in the -oso or -ose option.

(S)

Cancels command execution.

(O)

Check the access permissions on the file specified as the file used to acquire the data in the standard output file or the standard error output file. If there is no write permission, set write permission, and then re-execute the command.

KAVU0931-E

Insufficient disk space. The file specified as the file that acquires the standard output file or standard error output file cannot be written.

The system cannot write the standard output file and standard error output file to the disk because the disk does not have sufficient free space.

(S)

Cancels command execution.

(O)

Increase the free space in the disk, and then re-execute the command.

KAVU0932-E

The file specified as the file that acquires the standard output file or standard error output file is being used in another process, so it cannot be opened.

The file cannot be opened because another process is using the file specified as the file used to acquire the data in the standard output file or the standard error output file.

(S)

Cancels command execution.

(O)

Check whether another process is accessing the file specified as the file used to acquire the data in the standard output file or the standard error output file. If necessary, terminate the process accessing the specified file, and then re-execute the command.

KAVU0933-E

The file specified as the file that acquires the standard output file or standard error output file cannot be created.

The file specified to be used to acquire the data in the standard output file or the standard error output file cannot be created.

(S)

Cancels command execution.

(O)

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

KAVU0934-E

The file specified as the file that acquires the standard output file or standard error output file could not be written.

An attempt to write to the file specified as the file used to acquire the data in the standard output file or the standard error output file failed.

(S)

Cancels command execution.

(O)

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

KAVU0935-W

The standard output file or standard error output file contains 0 bytes of data.

No file was found when the jpqjobget command was used to acquire data in the standard output file or the standard error output file.

(S)

Terminates command processing.

KAVU0936-E

Environment settings or the logical host name information is invalid.

An error occurred during reading of the environment setting parameters because the environment settings or logical host name information was invalid.

(S)

Cancels command execution.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then re-execute the command. For UNIX, also check whether the user executing the command has read permission for /opt/jp1/hcclibcnf/regdir/HKEY_LOCAL_MACHINE.dat.

Also, if the integrated trace log contains the KAVU7221-E message (Environment setting parameter (parameter-name=parameter value) on the logical host (logical-host-name) is invalid.), the OS user executing the command might not have been granted write and read permissions for the output path. If this is the case, grant write and read permissions, and then re-execute the command.

KAVU0937-E

Job could not be submitted because agent host (agent-host-name) was failed to create automatically.

The agent could not be automatically created. This prevented the job from being submitted.

(S)

Cancels command execution.

(O)

For details about the cause of the error, check the integrated trace log for a KAVUxxxx message output before or after this message, remove the cause of the error, and then re-execute the submit job.

KAVU0938-E

Assumed JP1 user is not registered.

The assumed JP1 user has not been registered, or an invalid assumed JP1 user has been registered.

(S)

If the assumed JP1 user has not been registered, the system cancels the requested processing. If an invalid assumed JP1 user has been registered, the system deletes it.

(O)

Execute the jpqregguestuser command to check whether the assumed JP1 user has already been registered. For details about the jpqregguestuser command, see jpqregguestuser in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0939-E

Cannot access registry. Aborted. (module: error-location [error-location], reason code: reason-code)

Processing of the jpqregguestuser command was canceled because the configuration definition information could not be accessed.

(S)

Cancels the requested processing.

(O)

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

KAVU0942-E

The agent (agent-host-name) cannot be added because the Event Action Manager is processing the modification of the agent.

The Event Action Control Manager is notified of addition of an agent. However, the Event Action Manager has already been modifying the agent configuration preventing the agent from being added due to a notification error.

(S)

Cancels command execution.

(O)

Wait until the agent configuration definition has been changed by the other jpqagtadd and jpqagtdel commands, and then retry the operation.

KAVU0943-E

The agent (agent-host-name) cannot be deleted because the Event Action Manager is processing the modification of the agent.

The Event Action Control Manager is notified of deletion of an agent. However, the Event Action Manager has already been modifying the agent configuration preventing the agent from being deleted due to a notification error.

(S)

Cancels command execution.

(O)

Wait until the agent configuration definition has been changed by the other jpqagtadd and jpqagtdel commands, and then retry the operation.

KAVU0944-E

The information cannot be displayed because of adding or changing processing.

The information could not be displayed because a queue, agent, or exclusive execution resource is being added or modified.

(S)

Cancels the requested processing.

(O)

Wait until the addition or modification terminates, and then re-execute the command.

KAVU0945-E

The manager cannot be connected.

The system cannot connect the manager.

(S)

Cancels command execution.

(O)

Make sure that the daemon is started, TCP/IP communication is available under the specified logical host name. Then, re-execute the command.

KAVU0946-E

IP address could not be acquired from the manager host name.

The network must be set up correctly so that the IP address can be determined from the specified host name by using the hosts file or the DNS server.

(S)

Cancels command execution.

(O)

Make sure that TCP/IP communication is available under the specified logical host name, and then re-execute the command.

KAVU0947-E

The agent (agent-host-name)cannot be deleted because some event job is being executed.

The specified agent host cannot be deleted because there are event jobs being executed.

(S)

Cancels command execution.

(O)

Wait until the event job execution terminates, and then re-execute the command.

KAVU0948-E

The maximum number of jobs or the warning number of jobs must be specified.

Specify either the maximum number or the warning number of queued jobs. It is a required option.

(S)

Cancels command execution.

(O)

Specify either the maximum number or the warning number of queued jobs. Then, re-execute the command.

KAVU0949-E

The specified agent (agent-host-name) cannot be released because some job is being executed.

The specified agent cannot be disconnected because there are jobs being executed.

(S)

Cancels command execution.

(O)

Wait until the job terminates, and then re-execute the command.

KAVU0950-E

The manager status does not accept requests.

The current status of the manager process for job execution control does not permit it to accept requests.

(S)

Cancels command execution.

(O)

Make sure that the JP1/AJS3 service on the manager host is not in either of the following states and then re-execute the command.

Being started or being stopped

In maintenance mode

KAVU0951-E

The specified queue does not exist.

The specified queue definition information does not exist.

(S)

Cancels command execution.

(O)

You can use the jpqqueshow command to check the queue definition information. After checking for whether the specified queue definition information exists, retry the operation.

If you did not find the queue definition information, use the jpqqueadd command to add it dynamically.

For details about commands, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0952-E

The specified agent does not exist.

The specified agent definition information does not exist.

(S)

Cancels command execution.

(O)

You can use the jpqagtshow command to check the agent definition information. After checking for whether the specified agent definition information exists, retry the operation.

If you did not find the agent definition information, use the jpqagtadd command to add it dynamically.

For details about the commands, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0953-E

No response from the manager.

There was no response from the manager process for job execution control.

(S)

Cancels command execution.

(O)

Use the integrated trace log to determine the cause of the error and correct it if there is. Then, re-execute the command. If you did not find an error, then no response was returned because the manager process for job execution control was processing another request. In this case, the processing continues even if the command execution is canceled. Use the command or the integrated trace log to check the result of the requested processing.

KAVU0954-E

The command could not be executed because of internal factor at the manager.

Execution of the command failed for a reason internal to the manager process for job execution control.

(S)

Cancels command execution.

(O)

Check the integrated trace log for whether a KAVUxxxx message was output before or after this message. If a KAVUxxxx message was output, read the message explanation, remove the cause of the error, and then retry the operation. If no KAVUxxxx message has been output or if you cannot solve the problem, use the data collection tool to collect data, and then contact the system administrator.

KAVU0955-E

The specified queue is closed.

No jobs can be registered because the specified queue entrance is closed.

(S)

Cancels command execution.

(O)

The job entrance interface of the specified queue may be closed. Execute the jpqqueopen command to open the interface of the specified queue, and then re-execute the command. For details about the command, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0956-E

The number of queued jobs in the specified queue reached the limit or the queue resources reached the limit.

The number of jobs registered in the queue has reached the maximum number of jobs allowed in the queue or the maximum number of jobs allowed in the system.

(S)

Cancels command execution.

(O)

Either wait for an executing job to end and then issue another request, or review the queue definition information and adjust the maximum number of jobs allowed in the queue or the system.

If the maximum number of jobs allowed in the queue has been reached, the KAVU4515-W message is output to the integrated trace log. If the maximum number of jobs allowed in the system has been reached, the KAVU4520-W message is output to the integrated trace log.

Take the corrective action specified in the message that is output.

KAVU0957-E

You lack execute permission for this command.

The user trying to execute the command does not have permission for the command operation. An access permission error occurred on the authentication server used by the manager requested to perform the processing.

(S)

Cancels command execution.

(O)

When a command for job execution control (jpqxxxx command) is used to perform an operation on a single job in the job execution environment or on the job execution environment itself, check the permissions for the JP1 user name that is the same as the OS user name executing the command.

Check whether the OS user executing the command has been registered as a JP1 user on the authentication server and whether the JP1 permission level required for command execution has been set for the JP1 resource group (JP1_Queue) for that JP1 user (OS user).

For details about the execute permission required for commands, see 1.5 Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2. For details about how to set JP1 permission levels, see 3.1.1(1) Setting user information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 13.1.1(1) Setting user information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

For Windows, if UAC is being used, the administrator must re-execute the command.

KAVU0958-W

The job does not exist.

For jpqjobshow or jpqendjobshow execution, output occurs when there are no corresponding jobs at all. However, for execution of any other command, output occurs when there is no corresponding job for the specified job number.

(S)

For the jpqjobshow or jpqendjobshow command, the system terminates the command. For a command other than jpqjobshow and jpqendjobshow commands, the system cancels executing the command.

(O)

If you executed a command other than jpqjobshow and jpqendjobshow commands, check the specified job number is correct and then re-execute the command.

KAVU0959-E

The job has already started.

The job has already started. You cannot execute the jpqjobmove or jpqjobalt command for any job for which execution has already started.

(S)

Cancels command execution.

(O)

Execute the jpqjobmove or jpqjobalt command for a job whose execution has not started yet.

KAVU0960-E

The job did not end yet.

The job is not terminated yet.

(S)

Cancels command execution.

(O)

The jpqjobdel command cannot be executed for any job whose execution has not ended yet. Wait for the job to end, and then retry the operation.

KAVU0961-E

The specified destination queue does not exist.

The specified destination queue does not exist.

(S)

Cancels command execution.

(O)

Make sure there is a destination queue, and then re-execute the command.

KAVU0962-E

The job cannot be moved. There are too many queued jobs in destination queue.

You cannot move jobs to the destination queue because the maximum number of jobs that the queue can contain is reached.

(S)

Cancels command execution.

(O)

Either wait for an executing job to end before issuing another request, or check the queue definition information and adjust the maximum number of jobs allowed in the queue.

To check the number of jobs registered in the queue, which is the sum of the QUEUING and EXECUTING values, use the -q or -ah option in the jpqqueshow command. Also, to change the maximum number of jobs allowed in the queue, you can use the jpqquealt command. For details about these commands, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0963-W

There is no queue in the manager.

There is no queue definition information on the manager host specified by the jpqqueshow command.

(S)

Terminates command processing.

KAVU0964-E

No agent is connected to the manager.

The specified agent definition information does not exist.

(S)

Cancels command execution.

(O)

You can use the jpqagtshow command to check the agent definition information. After checking for whether the specified agent definition information exists, retry the operation.

If you did not find the agent definition information, use the jpqagtadd command to add it dynamically.

For details about commands, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0965-E

The manager is busy.

The manager is busy.

(S)

Cancels command execution.

(O)

Re-execute the command after a while.

KAVU0966-E

Memory became insufficient at the manager.

Memory became insufficient at the manager.

(S)

Cancels command execution.

(O)

Terminate any other unnecessary applications, and then re-execute the command. If the same message reappears, re-estimate memory.

KAVU0967-E

VOS3 user information is invalid.

The JP1/OJE for VOS3 user information registered by the jpqreguser command is invalid.

(S)

Cancels command execution.

(O)

Execute the -a option in the jpqreguser command to check whether the user information has been registered correctly, and then re-execute the command.

For details about the jpqreguser command, see jpqreguser in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0968-E

A fatal error occurred in the manager.

A fatal error occurred in the manager.

(S)

Cancels command execution.

(O)

Check the integrated trace log for whether a KAVUxxxx message was output before or after this message. If a KAVUxxxx message was output, read the message explanation, remove the cause of the error, and then retry the operation. If no KAVUxxxx message was output or if you cannot solve the problem, use the data collection tool to collect data, and then contact the system administrator.

KAVU0969-E

A logical contradiction occurred in the manager.

A logical contradiction occurred in the manager.

(S)

Cancels command execution.

(O)

Check the integrated trace log for whether a KAVUxxxx message was output before or after this message. If a KAVUxxxx message was output, read the message explanation, remove the cause of the error, and then retry the operation. If no KAVUxxxx message was output or if you cannot solve the problem, use the data collection tool to collect data, and then contact the system administrator.

KAVU0970-E

That request is not supported by the requested manager.

An unsupported request (such as queue operation and agent operation) might have been executed on a non-JP1/AJS3 host such as JP1/NQSEXEC or JP1/OJE for VOS3.

(S)

Cancels command execution.

(O)

Check whether the request is supported by another system product of the requester.

For details about the supported functions of each command, see 1.3 Linkage with other programs in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0971-E

An error occurred after submission.

An error occurred after a job was submitted.

(S)

Cancels command execution.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then re-execute the command.

KAVU0972-E

The execution environment is invalid.

The execution environment is incorrect.

(S)

Cancels command execution.

(O)

The authentication server may not be started. If this is the case, start the authentication server. If the authentication server has been started, use the integrated trace log to determine the cause of the error and correct it. Then, call the function again.

KAVU0973-E

The transfer file could not be created on the manager.

The system failed to create a transferred file in the manager.

(S)

Cancels command execution.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then re-execute the command.

KAVU0974-E

The transfer file could not be written on the manager.

The system failed to write a transferred file to the manager.

(S)

Cancels command execution.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then re-execute the command.

KAVU0975-E

The job was forcibly terminated, but it might not have terminated.

An attempt was made to forcibly terminated the job but the job may still be running.

(S)

Terminates command execution.

(O)

Use the integrated trace log to check the cause of the error.

KAVU0976-E

The exclusive execution resource name (exclusive-execution-resource-name) cannot be deleted because some job is being executed.

The specified exclusive execution resource cannot be deleted because there are jobs being executed.

(S)

Terminates command execution.

(O)

Wait until the job execution terminates, and then re-execute the command.

KAVU0977-E

The specified agent (agent-host-name) is not connected.

The specified agent host is not connected to the queue.

(S)

Terminates command execution.

(O)

Specify the correct agent host name, and then re-execute the command.

KAVU0978-E

The agent (agent-host-name) is already connected.

The specified agent host has already been connected.

(S)

Terminates command execution.

(O)

Specify the correct agent host name, and then re-execute the command.

KAVU0979-E

The queue (queue-name) definition cannot be changed because some job is being submitted.

The queue definition could not be changed because jobs are being submitted in the queue.

(S)

Terminates command execution.

(O)

Wait until the job execution terminates, and then re-execute the command.

KAVU0980-E

The agent (agent-host-name) cannot be registered because the agents exceeds the maximum number defined in the environment settings.

The agent cannot be added because the number of agents exceeds the maximum number defined in the environment settings.

(S)

Terminates command execution.

(O)

Delete unnecessary agents or recheck the maximum number defined in the environment settings. Then, re-execute the command.

KAVU0981-E

The queue (queue-name) cannot be registered because the queue exceeds the maximum number defined in the environment settings.

The queue cannot be added because the number of queues exceeds the maximum number defined in the environment settings.

(S)

Terminates command execution.

(O)

Delete unnecessary queues or recheck the maximum number defined in the environment settings. Then, re-execute the command.

KAVU0982-E

The exclusive execution resource (exclusive-execution-resource-name) cannot be registered because the exclusive execution resource exceeds the maximum number defined in the environment settings.

The exclusive execution resource cannot be added because the number of exclusive execution resources exceeds the maximum number defined in the environment settings.

(S)

Terminates command execution.

(O)

Delete unnecessary exclusive execution resources or recheck the maximum number defined in the environment settings. Then, re-execute the command.

KAVU0983-E

The warning number of jobs is larger than the number of maximum number of jobs.

The warning number of queued jobs cannot be larger than the maximum number of queued jobs.

(S)

Terminates command execution.

(O)

Specify the appropriate warning number of queued jobs, and then re-execute the command.

KAVU0984-E

The maximum number of jobs is less than the number of warning number of jobs.

The maximum number of queued jobs cannot be smaller than the warning number of queued jobs.

(S)

Terminates command execution.

(O)

Specify the appropriate maximum number of queued jobs, and then re-execute the command.

KAVU0985-E

The user profile is not registered. (user:user-name, remote-host:remote-host-name)

User information is not registered.

(S)

Cancels command execution.

(O)

Check the user to be deleted, and then re-execute the command.

KAVU0986-W

The user profile does not exist.

No user information is registered.

(S)

Terminates command processing.

KAVU0987-E

The password could not be scrambled. (reason code:reason-code)

The system failed to scramble the password.

(S)

Cancels command execution.

(O)

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

KAVU0988-E

The password could not be unscrambled. (reason-code)

The system failed to unscramble the password.

(S)

Cancels command execution.

(O)

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

KAVU0989-E

You lack access permission for, so process cannot be done.

The operation is impossible because you do not have high enough access authority.

(S)

Cancels command execution.

(O)

Check the access permission for the user who issued the request.

KAVU0990-E

The queue (queue-name) cannot be deleted because some job is being executed.

You cannot delete the queue because jobs are being executed in the queue.

(S)

Cancels command execution.

(O)

Wait until the job execution terminates, and then re-execute the command.

KAVU0991-E

The specified agent (agent-host-name) cannot be deleted because some queue is connected.

You cannot delete the agent because the agent is not disconnected from the queue.

(S)

Cancels command execution.

(O)

Use the jpqagtunlink command to cancel the agent-queue connection, and then re-execute the original command. For details about the jpqagtunlink command, see jpqagtunlink in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0992-E

The specified exclusive execution resource name (exclusive-execution-resource-name) does not exist.

The specified exclusive execution resource name is not defined.

(S)

Cancels command execution.

(O)

Specify the correct exclusive execution resource name, and then re-execute the command.

KAVU0993-W

There is no exclusive execution resource information to enumerate.

There is no exclusive execution resource information.

(S)

Cancels command execution.

KAVU0994-E

The maximum number of jobs or the warning number of jobs or the new queue name must be specified.

The maximum number of jobs allowed in the queue, the warning value for number of jobs in the queue, and the new queue name cannot all be omitted. At least one of these values must be specified.

(S)

Cancels command execution.

(O)

Specify one of the maximum number of queued jobs, the warning number of queued jobs, and the new name of the queue. Then, re-execute the command.

KAVU0995-E

The specified agent (agent-host-name) does not exist.

The specified agent is not defined.

(S)

Cancels command execution.

(O)

Specify the correct agent host name.

You can use the jpqagtshow command to check the agent definition information. After checking for whether the specified agent definition information exists, retry the operation.

If you did not find the agent definition information, use the jpqagtadd command to add it dynamically.

For details about commands, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0996-E

The agent (agent-host-name) cannot be deleted because some job is being executed.

You cannot delete the agent because jobs are being executed in the agent.

(S)

Cancels command execution.

(O)

Wait until the job execution terminates, and then re-execute the command.

KAVU0997-E

The agent information (agent-host-name) already exists.

The information about the specified agent has already been defined preventing it from being added.

(S)

Cancels command execution.

(O)

Specify the correct agent host name, and then re-execute the command.

KAVU0998-E

The queue information (queue-name) already exists.

The information about the specified queue has already been defined preventing it from being added.

(S)

Cancels command execution.

(O)

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

KAVU0999-E

The exclusive execution resource information (exclusive-execution-resource-name) already exists.

The information about the specified exclusive execution resource name has already been defined preventing it from being added.

(S)

Cancels command execution.

(O)

Specify the correct exclusive execution resource name, and then re-execute the command.

KAVU1100-I

Started process monitor (logical-host-name).

The process monitor started.

(S)

Continues starting the daemon.

KAVU1101-I

Process monitor (logical-host-name) ended normally.

The process monitor terminated normally.

(S)

Stops the daemon.

KAVU1102-E

Process monitor (logical-host-name) ended abnormally. (reason code:reason-code)

The process monitor for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message to correct the cause of the error, and then restart JP1/AJS3. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1103-I

Process monitor (logical-host-name) is already running on the same host.

You cannot activate more than one daemon in the same host.

(S)

Stops starting the daemon.

(O)

Check whether the JP1/AJS3 service is running.

If the JP1/AJS3 service is not running, this message might be output if the JP1/AJS3 service is restarted after abnormal termination. In this case, see 2.1.2(1) A JP1/AJS3 service has not started in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting, and take corrective action as necessary.

KAVU1104-E

An abnormal end of job execution control was detected.

The process monitor terminated abnormally because it detected the end of the agent process for job execution control.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message to correct the cause of the error, and then restart JP1/AJS3. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1105-E

An abnormal end of job queuing control was detected.

The process monitor terminated abnormally because it detected the end of the manager process for job execution control.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message to correct the cause of the error, and then restart JP1/AJS3. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1106-E

Job execution control process ended abnormally. (name : process-name, code : return-code, pid : process-ID, sig : signal-number)

The process indicated in process-name terminated abnormally with the return code indicated in return-code.

In UNIX:

When the signal number is other than 0, the process terminated abnormally in response to the signal for the signal number.

In Windows:

The signal number is 0.

The probable causes are:

A JP1/AJS3 resident process was terminated abnormally by a signal.

A JP1/AJS3 resident process was terminated forcibly by jajs_killall.cluster command.

(S)

Terminates job execution control.

(O)

If you cannot determine the cause of the error, collect data and then contact the system administrator (see 1.2.3 To the system administrators in the manual Job Management Partner 1/Automatic Job Management System 3 Messages 1).

To continue the operation, collect data and then restart JP1/AJS3.

There is no problem if this message appears when jajs_killall.cluster command is executed.

KAVU1201-E

The logical host (logical-host-name) is invalid.

The length of the logical host name specified in the JP1_HOSTNAME environment variable is invalid.

(S)

Stops the JP1/AJS3 service.

(O)

Check the logical host name specified in the JP1_HOSTNAME environment variable for error, correct the cause of the error, and then restart JP1/AJS3.

KAVU1202-E

An error occurred while obtaining environment settings on the logical host (logical-host-name). (reason code:reason-code)

An error occurred while obtaining environment settings of the logical host.

(S)

Stops the daemon.

(O)

Correct the error in the common definition information or correct the invalid definitions, and then restart.

KAVU1203-E

The agent process could not be started. (reason code:reason-code)

The system failed to start the agent process.

(S)

Stops the daemon.

(O)

In UNIX, reason code 12 indicates insufficient memory. For reason code 12, allocate sufficient memory required for execution and then retry.

When the message contains reason code 11, the number of processes that started concurrently may temporarily exceed the limit determined by the system. If this message (reason code 11) still appears even after you restart JP1/AJS3, use the kernel parameter to increase the maximum number of processes that can start concurrently. For details on how to estimate the value to be set in the kernel parameter, see Release Notes.

If you cannot determine the cause of the error by rechecking the above items or if this message appears in Windows, use the data collection tool to collect data, and then contact the system administrator.

KAVU1204-E

The manager process could not be started. (reason code:reason-code)

The system failed to start the manager process.

(S)

Stops the daemon.

(O)

In UNIX, reason code 12 indicates insufficient memory. For reason code 12, allocate sufficient memory to enable execution and then retry.

When the message contains reason code 11, the number of processes that started concurrently may temporarily exceed the limit determined by the system. If this message (reason code 11) still appears even after you restart JP1/AJS3, use the kernel parameter to increase the maximum number of processes that can start concurrently. For details on how to estimate the value to be set in the kernel parameter, see Release Notes.

If you cannot determine the cause of the error by rechecking the above items or if this message appears in Windows, use the data collection tool to collect data, and then contact the system administrator.

KAVU1205-E

A logical contradiction occurred. (module:reason-location[reason-location], reason code:reason-code)

A logical contradiction occurred due to a parameter error during inter-process communication for job execution control.

(S)

Stops the JP1/AJS3 service.

(O)

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

KAVU1206-E

The wait for the agent initialization completion was timed out.

A timeout occurred when the system was waiting for the agent process for job execution control to be initialized.

(S)

Terminates the JP1/AJS3 service forcibly.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message to correct the cause of the error, and then restart JP1/AJS3. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1207-E

The wait for the manager initialization completion was timed out.

A timeout occurred when the system was waiting for the manager process for job execution control to be initialized.

(S)

Terminates the JP1/AJS3 service forcibly.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message to correct the cause of the error, and then restart JP1/AJS3. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1208-E

The manager or the agent could not be forcibly terminated. (reason code:reason-code)

The system failed to forcibly terminate the manager or agent process for job execution control. Reason code 0x00010025 indicates unsuccessful termination of the manager process. Reason code 0x00010024 indicates unsuccessful termination of the agent process.

(S)

Continues forced termination of JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message to correct the cause of the error, and then restart JP1/AJS3. Manually check whether a manager or agent process exists. If the process exists, forcibly terminate it manually, and then restart JP1/AJS3. If no other message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1211-E

The wait for an event from the agent or the manager failed. (module:reason-location, reason code:reason-code)

The system could not receive an event indicating that initialization had completed from the manager or agent process for job execution control.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message to correct the cause of the error, and then restart JP1/AJS3. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1212-E

The wait for an event from the agent or the manager was timed out. (module:reason-location[reason-location], reason code:reason-code)

A timeout occurred when the system was waiting for the manager or agent process for job execution control to be initialized.

(S)

Terminates the JP1/AJS3 service forcibly.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation of that message to correct the cause of the error, and then restart JP1/AJS3. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1220-E

The start daemon could not be notified that initialization was completed. (reason code:reason-code)

The system could not notify the JP1/AJS3 startup process (jajs_spmd) that initialization had completed.

(S)

Stops the JP1/AJS3 service.

(O)

Check whether a KNADxxxx message was output to the integrated trace log. If it was output, see the manual Job Management Partner 1/Base Messages to check the explanation and correct the cause of the error. Then, restart the JP1/AJS3 service. If no such message was output or if you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU1221-E

The start daemon could not be notified that planned termination was completed. (reason code:reason-code)

The system could not notify the JP1/AJS3 startup process (jajs_spmd) that the planned termination had completed.

(S)

Continues processing to stop the JP1/AJS3 service.

(O)

Check whether a KNADxxxx message was output to the integrated trace log. If it was output, see the manual Job Management Partner 1/Base Messages to check the message explanation and correct the cause of the error. Then, restart JP1/AJS3 service. If no such message was output or if you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU1222-E

The start daemon could not be notified that forced termination was completed. (reason-code)

The system could not notify the JP1/AJS3 startup process (jajs_spmd) that the forced termination had completed.

(S)

Continues processing to stop the JP1/AJS3 service.

(O)

Check whether a KNADxxxx message was output to the integrated trace log. If it was output, see the manual Job Management Partner 1/Base Messages to check the message explanation and correct the cause of the error. Then, restart JP1/AJS3 service. If no such message was output or if you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU1224-E

A logical contradiction occurred in pipe communication process. (module:reason-module[reason-module], reason code:reason-code)

An error occurred during inter-process pipe communication for the process monitor for job execution control.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message to correct the cause of the error, and then restart JP1/AJS3. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1225-E

Forced termination started because the start daemon ended abnormally.

The forced termination started because the start daemon (jajs_spmd) abnormally terminated.

(S)

Stops the daemon.

(O)

Use the integrated trace log and other information to determine the cause of the termination of the start daemon and correct the error. Then, restart.

KAVU1232-E

An error occurred in process monitoring. Forced termination was sent to the agent and the manager.

A forced termination request was sent to the agent and manager processes because an error occurred in the process monitor for job execution control.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message to correct the cause of the error, and then restart JP1/AJS3. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1240-I

A forced termination request was received from the start daemon.

The system received a forced termination request from the JP1/AJS3 startup process (jajs_spmd).

(S)

Stops the JP1/AJS3 service.

KAVU1241-I

The start daemon was notified about the forced termination.

The system successfully notified the JP1/AJS3 startup process (jajs_spmd) of the completion of forced termination.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU1242-I

A forced termination was sent to the agent or the manager.

The system sent a forced termination request to the agent and manager processes for job execution control.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU1243-I

Forced termination of the agent was confirmed.

The system confirmed the forced termination of the agent process for job execution control.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU1244-I

Forced termination of the manager was confirmed.

The system confirmed the forced termination of the manager process for job execution control.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU1250-I

A planned termination request (while waiting for a job in the queue to terminate) was received from the start daemon.

The system received a planned termination request (waiting for the termination of a job in the queue) from the JP1/AJS3 startup process (jajs_spmd).

(S)

Waits until the queued job terminates, and then stops the JP1/AJS3 service.

KAVU1255-I

Planned termination of the agent was confirmed.

The system confirmed the planned termination of the agent process for job execution control.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU1256-I

Planned termination of the manager was confirmed.

The system confirmed the planned termination of the manager process for job execution control.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU1290-I

A jobnet restriction stop request was received from the start daemon.

The system received a jobnet restriction stop request from the JP1/AJS3 startup process (jajs_spmd).

(S)

Waits until all the jobnets being executed terminate, and then stops the JP1/AJS3 service.

KAVU1291-I

A restriction stop request was received from the start daemon.

The system received a job restriction stop request from the JP1/AJS3 startup process (jajs_spmd).

(S)

Waits until all the jobs being executed terminate, and then stops the JP1/AJS3 service.

KAVU1931-E

The command execution request was rejected.

The command execution request was rejected because the IP address of the connecting host was not registered in the manager connection permission configuration file on the connection destination host.

(S)

Continues processing.

(O)

Take the corrective action specified in the KAVU4335-E message that was output to the integrated trace log on the manager host specified in the command arguments.

KAVU2200-W

Any transmission processing over the 100-file limit will be ignored.

The system ignored a request to transfer more than 100 files.

(S)

Cancels transferring files.

(O)

Reduce the number of files to be transferred to 100 or fewer.

KAVU2201-E

The communication protocol parameter (parameter-name) exceeded the limit.

An attempt to analyze the communication protocol has failed in the TCP/IP communication protocol.

(S)

Cancels the requested processing.

(O)

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

KAVU2210-W

User mapping (user-name) failed in the file transmission process.

A user could not be mapped during file transfer.

(S)

Cancels the requested processing.

(O)

Check the definition of the user mapping, and then reissue the request.

KAVU2211-W

The user (user-name) could not be masked in file transmission process.

A user could not be masked during file transfer.

(S)

Cancels the requested processing.

(O)

Check the definition of the user mapping, and then reissue the request.

KAVU2212-W

No work path exists, so the transfer file or the result file cannot be created.

A transfer file or result file cannot be created because no work path exists.

(S)

Cancels the requested processing.

(O)

Check whether the following items defined in the environment setting parameters exist: the work directory for executing the manager process, the work directory for executing the agent process, and the work path for executing the job. Then reissue the request.

KAVU2213-W

You lack access permission for the work path, so the transfer file or the result file could not be created.

A transfer file or result file cannot be created because you do not have access permission for the work path.

(S)

Cancels the requested processing.

(O)

Check the access permission for the following items defined in the environment setting parameters: the work directory for executing the manager process, the work directory for executing the agent process, and the work path for executing the job. Then reissue the request.

KAVU2214-W

No path (file-name) is specified to the destination for storing transfer files or result files.

No path exists for storing transfer files or result files. If the file name is M_JPQSTDO_job-number or M_JPQSTDE_job-number, the error occurred during creation of a result file. If any other file name is displayed, the error occurred during creation of a transfer file.

(S)

Cancels the requested processing.

(O)

Check whether the following items defined in the environment setting parameters exist: the work directory for executing the manager process, the work directory for executing the agent process, and the work path for executing the job. Then reissue the request.

KAVU2215-W

You lack access permission for the path to the destination for storing transfer files, result files or the file (file-name).

You do not have access permission for the file or for the path for storing transfer files or result files. If the file name is M_JPQSTDO_job-number or M_JPQSTDE_job-number, the error occurred during creation of a result file. If any other file name is displayed, the error occurred during creation of a transfer file.

(S)

Cancels the requested processing.

(O)

Check the access permission for the following items defined in the environment setting parameters: the work directory for executing the manager process, the work directory for executing the agent process, and the work path for executing the job. Then reissue the request.

KAVU2216-W

The transfer file or the result file (file-name) cannot be opened.

The transfer file or the result file cannot be opened. If the file name is M_JPQSTDO_job-number or M_JPQSTDE_job-number, the error occurred during creation of a result file. If any other file name is displayed, the error occurred during creation of a transfer file.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the original or destination file name. If the file name is M_JPQSTDO_job-number or M_JPQSTDE_job-number, use the data collection tool to collect data, and then contact the system administrator.

KAVU2217-W

Another process is using the transfer file or the result file (file-name).

Another process is using the transfer file or the result file. If the file name is M_JPQSTDO_job-number or M_JPQSTDE_job-number, the error occurred during creation of the result file. If any other file name is displayed, the error occurred during creation of the transfer file.

(S)

Cancels the requested processing.

(O)

Check whether another process is using the file specified at the transfer source or destination, and then reissue the request.

If the file name is M_JPQSTDO_job-number or M_JPQSTDE_job-number, use the data collection tool to collect data, and then contact the system administrator.

KAVU2218-W

The transfer file or the result file (file-name) could not be accessed.

An attempt to access the transfer file or the result file has failed. If the file name is M_JPQSTDO_job-number or M_JPQSTDE_job-number, the error occurred during creation of the result file. If any other file name is displayed, the error occurred during creation of the transfer file.

(S)

Cancels the requested processing.

(O)

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

KAVU2219-W

Because there is no environment settings work path, the transfer file cannot be processed.

The transfer file cannot be processed because no work path exists in the common definition information.

(S)

Cancels the requested processing.

(O)

Check the common definition information, and then reissue the request.

KAVU2220-E

Memory could not be allocated. (size:size, module:reason-location[reason-location], reason code:reason-code)

The system failed to allocate memory.

(S)

Cancels the requested processing.

(O)

Terminate any other unnecessary applications, and then reissue the request. If the same message still appears, re-estimate the memory requirements.

Memory might be insufficient because an extremely large file was transferred from the agent to the manager. Check whether any of the following probable causes are present:

A standard output file name is specified in the definition of a job that outputs a large amount of standard output data.

A job is defined that will output a large amount of standard error output data.

The data append option is specified for the standard output file and standard error output file for the job.

A large file is specified for the transfer source file name in the job definition.

Take one of the following actions according to the cause of the error:

Specify a NULL device for the standard output file name in the job definition. In particular, enter /dev/null for a job running in UNIX, and enter NUL for a job running in Windows. Redirect the standard output in the script file or batch file for the job.

If the standard error output file name is specified in the job definition:

Specify a NULL device for the standard error output file name in the job definition. In particular, enter /dev/null for a job running in UNIX, and enter NUL for a job running in Windows.

If the standard error output file name is not specified in the job definition:

Specify a NULL device for the standard error output file name in the job definition. In particular, enter /dev/null for a job running in UNIX, and enter NUL for a job running in Windows. Alternatively, redirect the standard error output in the script file or batch file for the job.

Disable the data append option.

Do not specify a large file for the transfer source file name.

Alternatively, for the causes described in 1 to 3 above, delete or save standard output files and standard error output files on a regular basis.

KAVU2221-E

There is insufficient disk space. (module:reason-location[reason-location], reason code:reason-code)

There is an insufficient amount of disk space.

(S)

Cancels the requested processing.

(O)

Increase the free space in the disk, and then reissue the request.

KAVU2222-W

You lack access permission for the environment settings work path, so the transfer file cannot be processed.

The transfer file cannot be processed because you do not have access permission for the work path in the common definition information.

(S)

Cancels the requested processing.

(O)

Check the common definition information, and then reissue the request.

KAVU2223-E

The file name of the transfer file (file-name) could not be changed because the file does not exist.

An attempt was made to rename the specified transfer file to the name of a temporary file on the manager host, but the transfer file was not found due to invalid communication protocol data.

(S)

Cancels the requested processing for submitting the job.

(O)

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

KAVU2224-E

The file name of the transfer file (file-name) could not be changed because there was no access permission to the file (file-name).

An attempt was made to rename the specified transfer file to the name of a temporary file on the manager host, but access permission for the transfer file could not be acquired due to invalid communication protocol data.

(S)

Cancels the requested processing for submitting the job.

(O)

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

KAVU2225-E

The file name of the transfer file (file-name) could not be changed because a system call error occurred (system-error-number).

An attempt was made to rename the specified transfer file to a temporary file name on the manager host, but a system call error occurred due to invalid communication protocol data.

(S)

Cancels the requested processing for submitting the job.

(O)

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

KAVU2226-E

The file name of the transfer file (file-name) could not be changed.

An attempt was made to rename the specified transfer file to a temporary file name on the manager host, but an error occurred due to invalid communication protocol data.

(S)

Cancels the requested processing.

(O)

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

KAVU2227-E

A connection error occurred during TCP/IP communication. (connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system error number: system-error-number)

A connection error occurred during TCP/IP communication.

(S)

Cancels the requested processing.

(O)

Probable causes are listed below. Check whether any of them following probable causes are present:

JP1/AJS3 at the connection destination has not started yet.

The port numbers used for submitting a job do not match between the manager and the host where the job was executed.

You changed the default gateway while JP1/AJS3 was running.

The IP address of the logical host manager and that of the agent belong to different networks.

The network, including hardware, has a problem.

No more socket ports can be used in the entire system.

Memory was insufficient.

For a cluster configuration, the system is set up so that the logical IP address is released before JP1/AJS3 stops when a failover occurs.

Take one of the following actions according to the cause of the error, and then reissue the request.

Start JP1/AJS3.

If you changed the port number for JP1/AJS3 or if JP1/AJS3 links to another system such as JP1/NQSEXEC or JP1/OJE for VOS3, correct the port number in the services file.

Before changing the network configuration, stop the JP1/AJS3 service.

Correct the setting so that the IP addresses belong to the same network. Alternatively, see 2.3 Determining the network configuration in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide to specify the setting for communication using multiple network addresses.

Recheck the setting of the network including hardware. For example, execute the ping command to check whether communication is possible.

Check the socket status and wait until no more sockets remains in the TIME_WAIT status. You can also prevent a communication error by reducing the recovery time for the TIME_WAIT ports managed by the OS.

Check the memory status and re-estimate the memory requirements.

Modify the setting so that the logical IP address is released after JP1/AJS3 has stopped.

KAVU2228-E

Connection processing timed out during TCP/IP communication. (connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system error number: system-error-number)

A timeout occurred when a connection request was issued to the remote host during TCP/IP communication for job execution control.

(S)

Cancels the requested processing.

(O)

One of the following problems may have occurred in the connection destination host. Check the following and correct the cause of the error, and then reissue the request.

If JP1/AJS3 at the connection destination has not started, start it.

Check whether the port numbers used for submitting a job match between the manager and the host where the job was executed. If JP1/AJS3 links to another system such as JP1/NQSEXEC or JP1/OJE for VOS3, also check whether the port number in the services file is correct.

If you changed the default gateway while JP1/AJS3 was running, stop the JP1/AJS3 service, and then change the default gateway.

Check and, if necessary, change the setting so that the IP address of the logical host and that of the agent belong to the same network. Also see 2.3 Determining the network configuration in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide to specify the setting for communication using multiple network addresses.

Recheck the setting of the network, including hardware, for a problem in the network. For example, execute the ping command to check whether communication is possible.

For a cluster configuration, if the system is set up so that the logical IP address is released before JP1/AJS3 stops when a failover occurs, correct the setting so that the logical IP address is released after JP1/AJS3 stops.

Note that if you specify too small a value for the connection timeout, retry count, or retry interval, a communication error cannot be prevented due to a too short retry interval for communication. This may cause the error to occur frequently.

Normally, the connection timeout value is set to 90 seconds. For details about how to change the connection timeout value, see 6.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under Windows), or 15.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under UNIX).

KAVU2229-E

A transmission error occurred during TCP/IP communication. (connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system error number: system-error-number)

An attempt to send protocol data has failed during TCP/IP communication for job execution control.

(S)

Cancels the requested processing.

(O)

JP1/AJS3 at the connection destination may have terminated abnormally during communication. For a cluster configuration, a node switch may have occurred, resulting in forced termination of JP1/AJS3.

Check the status of JP1/AJS3 on the destination host and the contents of the integrated trace log, and then correct the cause of the error. If JP1/AJS3 has stopped, restart it. Then reissue the request. If you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU2230-E

Transmission processing timed out during TCP/IP communication. (connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system error number: system-error-number)

A timeout occurred when protocol data was sent to the remote host during TCP/IP communication for job execution control.

(S)

Cancels the requested processing.

(O)

JP1/AJS3 at the connection destination may have terminated abnormally during communication. For a cluster configuration, a node switch may have occurred, resulting in forced termination of JP1/AJS3.

Check the status of JP1/AJS3 on the destination host and the contents of the integrated trace log, and then correct the cause of the error. If JP1/AJS3 has stopped, restart it. Then reissue the request. If you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU2231-E

A reception error occurred during TCP/IP communication. (connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system error number: system-error-number)

An attempt to receive protocol data has failed during TCP/IP communication for job execution control.

(S)

Cancels the requested processing.

(O)

JP1/AJS3 at the connection destination may have terminated abnormally during communication. For a cluster configuration, a node switch may have occurred, resulting in forced termination of JP1/AJS3.

Check the status of JP1/AJS3 on the destination host and the contents of the integrated trace log, and then correct the cause of the error. If JP1/AJS3 has stopped, restart it. Then reissue the request. If you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU2232-E

Reception processing timed out during TCP/IP communication. (connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system error number: system-error-number)

A timeout occurred when the system was waiting for a response after sending protocol data during TCP/IP communication for job execution control. The probable causes are:

When the agent host sends a result file to the manager host at the end of a job, analysis takes a long time because the result file is too large.

When an attempt is made to execute a job with a transfer file specified, analysis takes a long time because the transfer file is too large.

The CPU on the manager host or agent host at the communication destination is heavily loaded. Alternatively, the system resources are insufficient.

Job information is being deleted on the manager host.

(S)

Cancels the requested processing.

(O)

Take one of the following actions according to the cause of the error, and then reissue the request:

Make sure that the result file for the job is not too large. Also, make sure that too much data will not be output even if additional writes are specified for the standard output file or standard error output file.

When you define the job, do not specify too large a transfer file.

Check the CPU load. Also see the kernel parameter settings to check the limit values of system resources.

Adjust the schedule to execute the job at a different time from that when job information was deleted. You must also prevent a lot of jobs from being deleted at the same time. For example, to reduce the number of jobs to be deleted, reduce the number of days for which job information is saved.

For 1 and 2 above, you can also limit the size of a file to be received in advance to prevent processing on some jobs from affecting the entire system. For details, see 6.2.7 Placing restrictions on file reception in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under Windows), or 15.2.7 Placing restrictions on file reception in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under UNIX).

KAVU2235-E

Another process is using the specified port number(reason code:reason-code). Could not start process(host name:host-name, port number:port-number).

The port cannot be activated because another process may be using the port or port-number is specified more than once.

(S)

Cancels starting of the daemon.

(O)

Check whether port-number which JP1/AJS3 is using is duplicated or another program is using port-number. Also check whether the network is set up correctly so that the IP address can be obtained from the specified host name.

KAVU2236-E

The initialization for TCP/IP communication was failed(reason code:reason-code). Could not start process(host name:host-name, port number:port-number).

The daemon cannot be started because TCP/IP communication could not be initialized.

(S)

Cancels starting of the daemon.

(O)

Check whether the environment is suitable for TCP/IP communication or memory is sufficient for operation. If you still cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU2237-E

Socket could not be opened because the process has too many open files. (host name: host-name, port number: port-number, module: reason-module[reason-module], system error number: system-error-number)

The socket could not be opened because the number of opened files reached the maximum set by the kernel parameter.

(S)

When accepting the request, retries the acceptance. If the error persists, the system outputs the message KAVU2241-E. When processing the request, the system cancels the processing.

(O)

Use the kernel parameter to increase the maximum number of files that can be opened., and then reissue the request. If the message KAVU2241-E is not output, the error has been corrected by a retry. If the message KAVU2241-E is output, the problem may persist. Recheck the setting. For details on how to estimate the value to be set in the kernel parameter, see Release Notes.

KAVU2238-E

The local host name could not be acquired in the TCP/IP communication. (host name: host-name, port number: port-number, module: reason-module[reason-module], system error number: system-error-number)

You could not obtain the local host name during TCP/IP communication.

(S)

When accepting the request, retries the acceptance. If the error persists, the system outputs the message KAVU2241-E. When processing the request, the system cancels the processing.

(O)

If the system does not output the message KAVU2241-E after this message while accepting the request, the error has been corrected by a retry. If the system outputs the message KAVU2241-E, or when processing the request, a problem might occur in the name service. Check the status of the local host and correct the error. Then, reissue the request.

KAVU2239-E

Detected the failure of the network subsystem. (host name: host-name, port number: port-number, module: reason-module[reason-module], system error number: system-error-number)

An error is detected in the network subsystem.

(S)

When accepting the request, retries the acceptance. If the error persists, the system outputs the message KAVU2241-E. When processing the request, the system cancels the processing.

(O)

If the system does not output the message KAVU2241-E after this message while accepting the request, the error has been corrected by a retry. If the system outputs the message KAVU2241-E, or when processing the request, an error might occur in the network subsystem. Check the status of the local host and correct the error. Then, reissue the request.

KAVU2240-E

The acceptance error occurred during TCP/IP communication. (host name: host-name, port number: port-number, module: reason-module[reason-module], system error number: system-error-number)

A request could not be accepted during TCP/IP communication.

(S)

Retries the acceptance. If the error persists, the system outputs the message KAVU2241-E.

(O)

If the system does not output the message KAVU2241-E after this message, the error has been corrected by a retry. If the system outputs the message KAVU2241-E, use the data collection tool to collect data, and then contact the system administrator.

KAVU2241-E

The fatal error occurred during TCP/IP communication. (host name: host-name, port number: port-number, module: reason-module[reason-module], system error number: system-error-number)

An error that prevents further processing, even after a retry, occurred during TCP/IP communication.

(S)

Stops the daemon.

(O)

Stop JP1/AJS3.

KAVU2242-W

The error occurred during TCP/IP communication. (host name: host-name, port number: port-number, module: reason-module[reason-module], system error number: system-error-number)

An error occurred during TCP/IP communication.

(S)

Continues processing. However, communication is impossible for some sockets that have been set.

(O)

Check whether the settings (such as an IP address) for communication are correct or the communication status does not have any problem. Then, correct the cause of the error.

To perform communication with the settings after correcting the error, restart the service (daemon).

KAVU2243-I

The size of the transmission source file of the job (job-name) executed on the client (client-host-name) exceeds the limit (bytes). (The transmission destination file name (transfer-destination-file-name))

The size of the transfer source file exceeds the maximum.

(S)

Continues processing.

(O)

Since the system may be over-loaded, check the following setting according to your operation.

We recommend you reduce the size of the specified transfer source file so it is smaller than the maximum file size (the value set in LimitReceiveFileSize environment setting parameter).

How to search for the transfer file:

Search for the file specified in the job indicated in job-name, which was executed on the host indicated in client-host-name.

Cautionary notes

If you did not specify anything for transfer-destination-file-name, JPQ_TEMP is displayed.

If you did not specify anything for job-name, none is displayed.

One of the following is displayed for client-host-name:

1. The name of the host on which the jpqjobsub command was executed

2. The name of the host on which the jobnet was defined and executed

3. The name of the host on which the JpqSubmitJob function was executed

In UNIX, none is displayed.

KAVU2244-E

The size of the transmission source file of the job (job-name) executed on the client (client-host-name) exceeds the limit (bytes). (The transmission destination file name (transfer-destination-file-name))

The size of the transfer source file exceeds the maximum.

(S)

Does not receive the transfer file.

(O)

Reduce the size of the specified transfer source file so it is smaller than the maximum file size (the value set in LimitReceiveFileSize environment setting parameter) or recheck the maximum value of the file size, and then re-execute the job.

How to search for the transfer file:

Search for the file specified in the job indicated in job-name that was executed on the host indicated in client-host-name.

Cautionary notes

If you did not specify anything for transfer-destination-file-name, JPQ_TEMP is displayed.

If you did not specify anything for job-name, none is displayed

One of the following is displayed for client-host-name:

1. The name of the host on which the jpqjobsub command was executed

2. The name of the host on which the jobnet was defined and executed

3. The name of the host on which the JpqSubmitJob function was executed

In UNIX, none is displayed.

If the job terminated abnormally because the size of the file reached the maximum, the message KAVU0220-E is output to the Execution Result Details dialog box.

KAVU2245-W

Because a connection error occurred during TCP/IP communication, it will be retried.

(connection destination host name: connection-destination-host-name, IP address: IP-address, port number: port-number, system error number: system-error-number)

Connection processing is retried because a connection error occurred during TCP/IP communication.

(S)

Retries connection processing for TCP/IP communication. If the connection cannot be restored by the retry, the system outputs the message KAVU2227-E.

(O)

If the message KAVU2227-E is not output after this message, there is no problem because the connection was restored by the retry. If the message KAVU2227-E is output, take action according to the instructions in the message.

If the system error number is 10048, there was a shortage of socket ports when the job was executed. See 3.1.1(5) OS tuning in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide and consider adjusting the OS parameters.

KAVU2246-W

Because a connection time-out occurred during TCP/IP communication, it will be retried. (connection destination host name: connection-destination-host-name, IP address: IP-address, port number: port-number, system error number: system-error-number)

Connection processing is retried because a connection timeout occurred during TCP/IP communication.

(S)

Retries connection processing for TCP/IP communication. If the connection cannot be restored by the retry, the system outputs the message KAVU2228-E.

(O)

If the message KAVU2228-E is not output after this message, there is no problem because the connection was restored by the retry. If the message KAVU2228-E is output, take action according to the instructions in the message.

KAVU3100-I

Job execution control (logical-host-name) was started.

The system started job execution control.

(S)

Starts the daemon.

KAVU3101-I

Job execution control (logical-host-name) is terminating.

The system is terminating job execution control.

(S)

Continues stopping the daemon.

KAVU3104-I

Job execution control (logical-host-name) ended normally.

Job execution control terminated normally.

(S)

Stops the daemon.

KAVU3105-I

The boot environment of the job execution control (logical-host-name). : maintenance-information

The boot environment for job execution control is displayed.

(S)

Continues the boot processing.

KAVU3110-E

Job execution control (logical-host-name) ended abnormally. (reason code:reason-code)

The agent process for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU3111-E

Job execution control (logical-host-name) is already running on the same host.

An attempt was made to start more than one agent process for job execution control on the same logical host.

(S)

Cancels the startup of the JP1/AJS3 service.

(O)

Check whether the JP1/AJS3 service (agent process for job execution control) has already started.

If this message is output when no agent process for job execution control has started, a job process started from JP1/AJS3 (including a process started from a job process) might be running.

If you can identify a job process that was started from JP1/AJS3, either wait for the job process to finish or forcibly terminate the job process, and then start the JP1/AJS3 service. If you are unable to identify such a job process, restart the OS to remedy the situation.

KAVU3112-E

Job execution control process ended abnormally. (name : process-name, code : return-code, pid : process-ID, sig : signal-number)

The process indicated in process-name terminated abnormally with the return code indicated in return-code.

When the signal number is other than 0, the process terminated abnormally in response to the signal for the signal number.

The probable causes are:

A JP1/AJS3 resident process was terminated abnormally by a signal.

A JP1/AJS3 resident process was terminated forcibly by jajs_killall.cluster command.

(S)

Terminates job execution control when the process name is jpqagtdmn.

Cancels the requested processing if the process name is jpqagtchild.

(O)

If you cannot determine the cause of the error, collect data and then contact the system administrator (see 1.2.3 To the system administrators in the manual Job Management Partner 1/Automatic Job Management System 3 Messages 1).

To continue the operation, collect data and then restart JP1/AJS3 (you do not have to restart JP1/AJS3 when the abnormally terminated process is jpqagtchild).

There is no problem in the following cases:

This message appears when you execute jajs_killall.cluster command.

The message KAVU3589-E has been output immediately before this message.

If this is the case and the KAVU3589-E message was output, read the message explanation and take corrective action.

KAVU3200-E

The user (user-name) request (request-name) for the parameter (parameter-name=parameter value) is invalid.

Invalid data was found in the request parameter during analysis of the request to the agent process for job execution control.

(S)

Cancels the analysis of the request to the agent process for job execution control.

(O)

The request received by the agent process for job execution control might be invalid for the process. Check the services files on the manager and agent hosts to see whether the port number for the jp1ajs2qagt service is also used for other services.

If the port number for the jp1ajs2qagt service is also used for other services, assign a unique port number for the jp1ajs2qagt service, and then restart JP1/AJS3.

In other cases, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU3201-E

The user (user-name) request (request-name) failed. (reason code:reason-code)

The request to the agent process for job execution control has failed.

(S)

Cancels the analysis of the request to the agent process for job execution control.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU3205-W

The system detected a change in the size of the environment variable file (environment-variable-file-name) while the job (job-number) was starting.

The environment variable file that was being read according to the job definition at job startup was overwritten before reading was completed.

The job might have been started with an invalid environment variable.

(S)

Continues the job startup processing.

If the increase in the environment variable file size was less than 4,096 bytes, the job was started with all environment variables having been read. However, the job might have been started with an invalid environment variable because of the rewriting occurred during reading.

If the increase in environment variable file size was 4,096 bytes or more, the job was started after 4,096 bytes had been added to the pre-change file size.

(O)

Check the job status. If any environment variables might not have been read, take corrective action. Also create or update the environment variable file before the job is delivered to the agent. After the job has been delivered to the agent, do not update the environment variable file until the job is running.

KAVU3210-E

Communication thread (logical-host-name) ended abnormally. (reason code:reason-code)

The thread for receiving a communication request for the agent process for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

The CPU may be over-loaded. Check the load on the CPU. Also use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU3211-E

The agent daemon process ended abnormally. (host name:host-name, process name:process-name, process id:process-number)

The agent process for job execution control terminated abnormally.

(S)

Terminates the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU3212-E

The monitoring process for job (job-number) ended abnormally. (host name:host-name, process name:process-name, process id:process-number)

The job monitoring process for job execution control terminated abnormally.

(S)

Cancels the monitoring of the job indicated in job-number.

(O)

Check the status of the job process that was started as a job. If the job process is re-executable, re-execute it.

Also use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU3213-E

Failed to acquire permission to read environment variable file (file-name) for the user (user-name). (system call name: system-call-name, reason code: reason-code)

The system failed to access the environment variable file.

(S)

Cancels the requested processing.

(O)

Make sure that, based on the file permission (ls -l command) and access control list settings, the file path to the environment variable file specified by the executing OS user can be accessed, and then call the function again.

KAVU3214-E

Failed to acquire permission to execute the execution file (file-name) for the user (user-name). (system call name: system-call-name, reason code: reason-code)

The system failed to access the executable file.

(S)

Cancels the requested processing.

(O)

Make sure that, based on the file permission (ls -l command) and access control list settings, the file path to the execution file specified by the executing OS user can be accessed, and then call the function again.

KAVU3215-E

Failed to read the temporary file (file-name) for the transmission source for the user (user-name). (system call name: system-call-name, reason code: reason-code)

An attempt to read the transfer source file has failed.

(S)

Cancels the requested processing.

(O)

Make sure that, based on the file permission (ls -l command) and access control list settings, the file path to the transfer source file specified by the executing OS user can be read, and then call the function again.

KAVU3216-E

Failed to write the transmission destination file (file-name) for the user (user-name). (system call name: system-call-name, reason code: reason-code)

An attempt to write to the transfer destination file has failed.

(S)

Cancels the requested processing.

(O)

Make sure that, based on the file permission (ls -l command) and access control list settings, the file path to the transfer source file specified by the executing OS user can be written to, and then call the function again.

KAVU3217-W

An attempt to transmit the result file for the job (job-number, manager-host-name) has failed.

An error occurred during transfer of the result file for the job.

(S)

Continues processing.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message.

Cautionary note

Although the standard error output file was not defined in the detailed definition of the job, if you execute the job by using a jobnet, a temporary standard error output file is created and transferred to the manager host. For details about the standard error output file, see 7.8.1 Notes on the standard output file and standard error output file in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

The return code of the job process is set for the return code of the job, and the job is placed into the Ended normally, Ended with warning, or Ended abnormally status depending on the final judgment. In addition, the result file is not re-sent, because termination of the job is preferred. Accordingly, you cannot use the Execution Result Details dialog box of JP1/AJS3 - View to view the contents of the standard error output file.

Because the result file for the job is not re-sent, the values set for the NotfyJobStateInterval and NotfyJobStateCount environment setting parameters will not be enabled. (These parameters specify the interval for resending the result file for the job and the number of times it is re-sent.)

KAVU3221-E

The manager (logical-host-name) could not be notified about job status. (reason code:reason-code)

The system failed to notify the manager process for job execution control of the job status. When a means of preventing duplicated reception of the job result file is set, a job end notification cannot be accepted, probably because the result file (standard output file or standard error output file) is being analyzed on the manager host. If this is the case, the manager host accepts the KAVU4297-W message. If the setting for preventing duplicate reception of job result files is not defined, the manager host may stop or a communication with the manager host may be impossible.

For details on how to prevent duplicated reception of the job result file, see 6.2.6 Preventing duplicated reception of job result files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under Windows), or 15.2.6 Preventing duplicated reception of job result files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under UNIX).

(S)

Cancels the job status notification to the manager process.

(O)

Check the integrated trace log for the manager host to check the running status of the manager process for job execution control.

Also use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU3270-E

Memory could not be allocated. (size:size, module:reason-location[reason-location], reason code:reason-code)

The system failed to allocate memory.

(S)

Cancels the requested processing.

(O)

Terminate any other unnecessary applications, and then reissue the request. If the same message reappears, re-estimate memory.

Cautionary note

If the KAVU3217-W message was output before or after this message, an error occurred during the transfer processing for a result file. If 1 is set for the IgnoreResultFileError environment setting parameter, the return code of the job process is set for the return code of the job, and the job is placed into the Ended normally, Ended with warning, or Ended abnormally status depending on the final judgment. In addition, the result file is not re-sent, because termination of the job is preferred. Accordingly, you cannot use the Execution Result Details dialog box of JP1/AJS3 - View to view the contents of the standard error output file.

Because the result file for the job is not re-sent, the values set for the NotfyJobStateInterval and NotfyJobStateCount environment setting parameters will not be enabled. (These parameters specify the interval for resending the result file for the job and the number of times it is re-sent.)

For details about the IgnoreResultFileError environment setting parameter, see 2.3 Setting up the job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVU3271-E

There is insufficient disk space. (module:reason-location[reason-location], reason code:reason-code, file name:file-name)

The disk does not contain sufficient amount of free space.

(S)

Cancels the requested processing.

(O)

Secure sufficient free space on the disk that contains the file indicated by file-name, and then issue the request again.

KAVU3272-E

A system call error occurred when starting process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred during startup of the agent process for execution control.

(S)

Stops the JP1/AJS3 service.

(O)

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

KAVU3274-W

A system call error occurred in the communication process (logical-host-name). (module:reason-location, reason code:reason-code)

A system call error occurred in the communication process.

(S)

Cancels the requested processing.

(O)

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

KAVU3275-E

A logical contradiction occurred in the communication process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

The probable causes are:

Memory could not be allocated at the transmission-destination manager host because the job's result files (standard output file and standard error output file) are too large.

If this message is followed by messages KAVU2220-E and KAVU3512-E, a memory shortage on the destination manager host is likely. See the explanation of the messages output at the manager host.

The temporary file used for job execution control did not exist. (reason-code = 0xe002110d)

You did not have access permission for the temporary file used for job execution control. (reason-code = 0xe002110e)

The amount of free space on the disk was insufficient when the temporary file used for job execution control was being created. (reason-code = 0xe002110f)

The temporary file used for job execution control was locked and opened. (reason-code = 0xe0021110)

An attempt to acquire the logical host name or IP address has failed. (reason-code = 0xe0021120)

Note

For details on the temporary files used for job execution control, see 7.8.1 Notes on the standard output file and standard error output file in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

If the KAVU3217-W message was output before or after this message, an error occurred during the transfer processing for a result file. If 1 is set for the IgnoreResultFileError environment setting parameter, the return code of the job process is set for the return code of the job, and the job is placed into the Ended normally, Ended with warning, or Ended abnormally status depending on the final judgment. In addition, the result file is not re-sent, because termination of the job is preferred. Accordingly, you cannot use the Execution Result Details dialog box of JP1/AJS3 - View to view the contents of the standard error output file.

Because the result file for the job is not re-sent, the values set for the NotfyJobStateInterval and NotfyJobStateCount environment setting parameters will not be enabled. (These parameters specify the interval for resending the result file for the job and the number of times it is re-sent.)

For details about the IgnoreResultFileError environment setting parameter, see 2.3 Setting up the job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no other KAVUxxxx message was output, or if a reason code other than that shown above was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU3276-W

A system call error occurred in the request process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred in the request process.

(S)

Cancels the requested processing.

(O)

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

KAVU3278-W

A system call error occurred in the user mapping process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred in the user mapping process.

(S)

Cancels the requested processing.

(O)

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

KAVU3280-W

A system call error occurred in the variable solution process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred in the variable solution process.

(S)

Cancels the requested processing.

(O)

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

KAVU3281-E

A logical contradiction occurred in the variable solution process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A logical contradiction occurred during solution of the macro variable for the agent process for job execution control.

(S)

Cancels the requested processing.

(O)

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

KAVU3282-W

A system call error occurred in the standard input/output process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred in the standard input/output process.

(S)

Cancels the requested processing.

(O)

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

KAVU3283-E

A logical contradiction occurred in the standard input/output process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A logical contradiction occurred during the check of access permission for the file used for job execution.

(S)

Cancels the requested processing.

(O)

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

KAVU3284-W

A system call error occurred in the internal process (logical-host-name). (module:reason-location[reason-location], reason code1:reason-code-1, system call name:system-call-name, reason code2:reason-code-2)

A system call error occurred in the internal process.

(S)

Cancels the requested processing.

(O)

Determine the cause of the error from system-call-name and reason-code-1 or reason-code-2.

The following value is output in reason-code-1 or reason-code-2.

Windows

Value obtained by Win32 API function GetLastError

UNIX

Value obtained by errno

The following describes the cause of the error that corresponds to each reason-code, and the corrective action to be taken.

In Windows:

reason-code-2: 0x00000020

If system-call-name in the message indicates CreateFile, an attempt to open the result file (standard output file or standard error output file) failed. Another process might be using the result file.

Check the following:

- Check whether the result file is used in a program that will be executed as a job. In the detailed definition of the job, specify unique names for the file used in the program that will be executed as a job, and for the result file. Then, re-execute the job.

- Check whether concurrent accesses were made to a result file that was used by a job. Either eliminate the concurrent file accesses, or specify unique file names in the detailed definition of the job, and then re-execute the job.

In UNIX:

reason-code-1: 0x00000016

reason-code-1: 0x0000002b

If no value is indicated in system-call-name in the message, the shared memory used by JP1/AJS3 to execute jobs might have been deleted. Restart the JP1/AJS3 service to recover from the error. Also review the operation to make sure that the shared memory has not been deleted.

KAVU3285-E

A logical contradiction occurred in the internal process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A logical contradiction occurred during internal processing for the agent process for job execution control.

(S)

Cancels the requested processing.

(O)

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

KAVU3289-W

The authentication server could not be connected, but initialization will continue.

The authentication server could not be connected.

(S)

Continues the daemon.

(O)

If the authentication server is not started, start it.

KAVU3290-W

You lack access permission for the temporary file (file-name). (reason code:reason-code)

You do not have access permission for the following files or directories:

Work directory used for executing the agent process, or files in the work directory

System file directory or files in the system file directory

(S)

Cancels the requested processing.

(O)

Examine the cause which may be one of the following:

A privilege to the system file directory (the default is /var/opt/jp1ajs2/sys) has been changed.

A privilege to the work directory (the default is /var/opt/jp1ajs2/tmp) used for executing the agent process has been changed.

A privilege to the jpqagtlock file or the temporary work file in the system file directory has been changed.

Another program is accessing the above directories or the temporary work file.

If a privilege to the file or the directory has been changed, give the write and read permissions to the OS user that executes jobs. The temporary work file (the file that begins with A_JPQ) may remain in the work directory used for executing the agent process even if the job terminates. If this is the case even after JP1/AJS3 stops, delete the temporary work file.

KAVU3291-W

The temporary file (file-name) cannot be accessed (system-call-name). (reason code:reason-code)

You could not access the following files or directories:

Work directory used for executing the agent process, or files in the work directory

System file directory or files in the system file directory

(S)

Cancels the requested processing.

(O)

Examine the cause which may be one of the following:

The system file directory (the default is /var/opt/jp1ajs2/sys) has been deleted.

The work directory (the default is /var/opt/jp1ajs2/tmp) used for executing the agent process has been deleted.

Write permission has not been set for the work directory used for executing the agent process (default work directory: /var/opt/jp1ajs2/tmp).

The jpqagtlock file or the temporary work file has been deleted from the system file directory.

Another program is accessing the above directories or the temporary work file.

If the jpqagtlock file or the above directories have been deleted, reinstall JP1/AJS3.

If the work directory used for executing the agent process exists, check whether write permission is set for the directory. If write permission is not set, set write permission for the directory or change the work directory to a directory for which write permission has been set.

The temporary work file (the file that begins with A_JPQ) may remain in the work directory used for executing the agent process even if the job terminates normally. If this is the case even after JP1/AJS3 stops, delete the temporary work file.

KAVU3293-E

The process has too many open files. (reason code:reason-code)

The number of opened files reached the maximum set by the kernel parameter.

(S)

Cancels the requested processing.

(O)

Use the kernel parameter to increase the maximum number of files that can be opened.

For details on how to estimate the value to be set in the kernel parameter, see Release Notes.

KAVU3295-E

No more process can be generated. (reason code:reason-code)

The number of processes reached the maximum set by the kernel parameter.

(S)

Cancels the requested processing.

(O)

Use the kernel parameter to increase the maximum number of processes.

Set the sufficient number of processes considering the number of JP1/AJS3 processes plus the number of job processes that are executed at the same time.

For details about JP1/AJS3 processes, see the explanation of process status checking in 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KAVU3296-E

The request sent from the host(source-IP-address) was ignored. (reason, host-name)

A request from the host (source-IP-address) was ignored. The probable causes are as follows.

When the reason is Restricted:

The IP address indicated in source-IP-address was not registered in the agent connection permission configuration file on the host on which this message was output.

When the reason is Error:

An error occurred during processing intended to obtain the connection source IP address.

For a physical host, JP1_DEFAULT is indicated in host-name.

(S)

Ignores the request and continues processing.

(O)

When the reason is Restricted:

If the request from the IP address indicated in source-IP-address must be accepted, perform the following:

Add the connection source IP address by editing the agent connection permission configuration file on the host on which this message was output.

Execute the jajs_pmtcon command to apply the changes you made in the connection permission configuration file.

If necessary, perform the request processing again.

When the reason is Error:

Follow the instructions given in the KAVS8033-E message that was output immediately before this message.

KAVU3500-W

The operating status (operating-status) does not allow executing request (request-name).

The operating status does not allow executing the request.

(S)

Cancels the requested processing.

(O)

Make sure that the daemon is started, and then reissue the request.

KAVU3502-W

The specified job (job-number) does not exist, or termination notification is already complete.

The specified job does not exist. Alternatively, the termination of the job is already reported.

(S)

Cancels the requested processing.

(O)

Check whether the job is already terminated.

KAVU3503-E

The job (job-number) could not be executed.

The job could not be executed.

(S)

Cancels the request to execute the job.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message and correct the cause of the error. Then, re-execute the job.

KAVU3504-W

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

The file cannot be deleted because the transfer file no longer exists.

(S)

Continues requested processing.

(O)

The transfer file specified to be deleted may have been deleted before job termination. Check whether any program or script is accessing the transfer file.

KAVU3505-W

You lack delete permission for the transfer file (file-name).

You cannot delete the transfer file because you are not permitted to delete it.

(S)

Continues requested processing.

(O)

The permission for the transfer file specified to be deleted may have been changed before job termination. Check whether any program or script is accessing the transfer file.

KAVU3506-W

The transfer file (file-name) could not be deleted. (reason code: reason-code)

The transfer file could not be deleted.

(S)

Continues the requested processing.

(O)

The attribute of the transfer file specified to be deleted may have been changed before job termination. Check whether any program or script is accessing the transfer file.

KAVU3511-E

Memory could not be allocated at the transmission source agent (agent-host-name) because the size of the result files (standard-output-file-name, standard-error-file-name) for the job (job-number, manager-host-name) was too large.

Memory could not be allocated at the transmission source agent because the job's result files (standard output file and standard error output file) are too large.

(S)

Cancels the requested processing.

(O)

For details about how to avoid memory shortages due to large result files, see 7.8.1 Notes on the standard output file and standard error output file in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

Although the job is placed in the Ended abnormally status with the return code -1, the job process itself may have terminated normally. Check the end status of the job process on the agent host.

Cautionary notes

File names are not output in the message unless the standard output file and standard error output file are specified in the job definition. However, when the standard error output file is undefined, if the job in question is executed within a jobnet, a temporary file will be created and sent to the manager host. In this case, A_JPQSTDE_*_job-number is set in standard-error-file-name. Take appropriate action, referring to 7.8.1 Notes on the standard output file and standard error output file in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

If 1 is set for the IgnoreResultFileError environment setting parameter, the return code of the job process is set for the return code of the job, and the job is placed into the Ended normally, Ended with warning, or Ended abnormally status depending on the final judgment. In addition, the result file is not re-sent, because termination of the job is preferred. Accordingly, you cannot use the Execution Result Details dialog box of JP1/AJS3 - View to view the contents of the standard error output file.

Because the result file for the job is not re-sent, the values set for the NotfyJobStateInterval and NotfyJobStateCount environment setting parameters will not be enabled. (These parameters specify the interval for resending the result file for the job and the number of times it is re-sent.)

For details about the IgnoreResultFileError environment setting parameter, see 2.3 Setting up the job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVU3512-E

Memory could not be allocated at the transmission destination manager(manager-host-name) because the size of the result files(standard-output-file-name, standard-error-file-name) for the job(job-number) was too large.

Memory could not be allocated at the transmission-destination manager host because the job's result files (standard output file and standard error output file) are too large.

(S)

Cancels the requested processing.

(O)

For details about how to avoid memory shortages arising from large result files, see 7.8.1 Notes on the standard output file and standard error output file in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

Although the job is placed in the Ended abnormally status with the return code -1, the job process itself may have terminated normally. Check the end status of the job process on the agent host.

Cautionary notes

File names are not output in the message unless the standard output file and standard error output file are specified in the job definition. However, when the standard error output file is undefined, if the job in question is executed within a jobnet, a temporary file will be created and sent to the manager host. In this case, A_JPQSTDE_*_job-number is set in standard-error-file-name. Take appropriate action, referring to 7.8.1 Notes on the standard output file and standard error output file in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

If 1 is set for the IgnoreResultFileError environment setting parameter, the return code of the job process is set for the return code of the job, and the job is placed into the Ended normally, Ended with warning, or Ended abnormally status depending on the final judgment. In addition, the result file is not re-sent, because termination of the job is preferred. Accordingly, you cannot use the Execution Result Details dialog box of JP1/AJS3 - View to view the contents of the standard error output file.

Because the result file for the job is not re-sent, the values set for the NotfyJobStateInterval and NotfyJobStateCount environment setting parameters will not be enabled. (These parameters specify the interval for resending the result file for the job and the number of times it is re-sent.)

For details about the IgnoreResultFileError environment setting parameter, see 2.3 Setting up the job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVU3520-E

The monitoring thread for job (job-number) could not be generated. (reason code:reason-code)

The system failed to generate a thread for monitoring the job.

(S)

Cancels the requested processing.

(O)

The following describes the cause of the error that corresponds to each reason-code, and the corrective action to be taken.

In Windows:

reason-code: 8

Memory might be insufficient. Stop unnecessary applications, and then reissue the request. If the same message reappears, re-estimate memory.

reason-code: 1455

Resources might have been temporarily insufficient. Check for any processing that might have caused resources to be insufficient.

In UNIX:

reason-code: 12

Memory might be insufficient. Stop unnecessary applications, and then reissue the request. If the same message reappears, re-estimate memory.

reason-code: 28

The file system might not have sufficient free space. If free space is insufficient, delete unnecessary files to free more space, and then retry the operation.

KAVU3521-W

The job (job-number) process could not be generated. (reason code:reason-code)

The system failed to generate the job process.

(S)

Cancels the requested processing.

(O)

Memory may be insufficient. Check the memory estimate. If there is no problem with the available memory, use the data collection tool to collect data, and then contact the system administrator.

KAVU3522-W

The job (job-number) return code could not be acquired. (reason code:reason-code)

The system failed to acquire the job return code.

(S)

Cancels the requested processing.

(O)

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

KAVU3523-W

The job (job-number) could not be forcibly terminated. (reason code:reason-code)

The system failed to forcibly terminate the job.

(S)

Cancels the requested processing.

(O)

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

KAVU3530-W

The manager (logical-host-name) might have stopped, or an obstacle occurred.

The manager might have stopped or an error might have occurred in the manager.

(S)

Cancels the requested processing.

(O)

Check the following and then call the function again:

Check whether the daemon has been started.

Check whether the TCP/IP communication is possible with logical-host-name.

Check whether the port number is set correctly.

Check whether the size of the file specified as the standard output or standard error output file is too large.

Cautionary note

If the KAVU3217-W message was output before or after this message, an error occurred during the transfer processing for a result file. If 1 is set for the IgnoreResultFileError environment setting parameter, the return code of the job process is set for the return code of the job, and the job is placed into the Ended normally, Ended with warning, or Ended abnormally status depending on the final judgment. In addition, the result file is not re-sent, because termination of the job is preferred. Accordingly, you cannot use the Execution Result Details dialog box of JP1/AJS3 - View to view the contents of the standard error output file.

Because the result file for the job is not re-sent, the values set for the NotfyJobStateInterval and NotfyJobStateCount environment setting parameters will not be enabled. (These parameters specify the interval for resending the result file for the job and the number of times it is re-sent.)

For details about the IgnoreResultFileError environment setting parameter, see 2.3 Setting up the job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVU3531-W

The manager (logical-host-name) host name might be invalid.

The network must be set up so that the IP address can be determined from the specified host name by using the hosts file or the DNS server.

(S)

Cancels the requested processing.

(O)

Make sure that TCP/IP communication is available under the specified logical host name, and then reissue the request.

Cautionary note

If the KAVU3217-W message was output before or after this message, an error occurred during the transfer processing for a result file. If 1 is set for the IgnoreResultFileError environment setting parameter, the return code of the job process is set for the return code of the job, and the job is placed into the Ended normally, Ended with warning, or Ended abnormally status depending on the final judgment. In addition, the result file is not re-sent, because termination of the job is preferred. Accordingly, you cannot use the Execution Result Details dialog box of JP1/AJS3 - View to view the contents of the standard error output file.

Because the result file for the job is not re-sent, the values set for the NotfyJobStateInterval and NotfyJobStateCount environment setting parameters will not be enabled. (These parameters specify the interval for resending the result file for the job and the number of times it is re-sent.)

For details about the IgnoreResultFileError environment setting parameter, see 2.3 Setting up the job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVU3532-W

The host name (logical-host-name) IP address could not be acquired.

The network must be set up correctly so that the IP address can be determined from the manager host name by using the hosts file or the DNS server.

(S)

Cancels the requested processing.

(O)

Check whether the TCP/IP communication is possible with the manager host name and then call the function again.

KAVU3540-I

Planned termination of the agent (agent-name) started.

The agent process for job execution control started planned termination.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU3541-I

Forced termination of the agent (agent-name) started.

The agent process for job execution control started forced termination.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU3542-I

The agent (agent-name) is monitoring job termination.

The agent process for job execution control will monitor the termination of running jobs.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU3544-W

Shared memory could not be allocated, but startup processing will continue. (logical host name:logical-host-name, system call name:system-call-name, reason code:reason-code)

An attempt to allocate shared memory (a system resource) failed. If an OS user different from the service account executes the job, forced termination of jobs that use the jp1exec command might not be possible.

(S)

Continues requested processing.

(O)

If you need to force termination of a job that uses the jp1exec command, stop unnecessary applications, and then restart the JP1/AJS3 service on the logical host indicated in the message.

KAVU3545-W

Shared memory could not be acquired, but job execution will continue. (logical host name:logical-host-name, system call name:system-call-name, reason code:reason-code)

An attempt to acquire shared memory (a system resource) failed during execution of the jp1exec command. If an OS user different from the service account executes the job, forced termination of the job that uses the jp1exec command might not be possible.

(S)

Continues requested processing.

(O)

Stop unnecessary applications.

If the same message reappears during execution of a job that uses the jp1exec command and it is necessary to forcibly terminate that job, restart the JP1/AJS3 service on the logical host indicated in the message. If you are executing a queueless job, restart the JP1/AJS3 Queueless Agent service.

KAVU3546-E

The temporary file (file-name) could not be opened. (system call name:system-call-name, reason code:reason-code)

The temporary file cannot be opened because the directory for the temporary file does not exist.

(S)

Cancels the request processing.

(O)

Make sure that the directory to which the temporary file is to be output exists.

Also make sure that access permission that allows the OS user who executes the job to access the directory is set on the directory.

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

KAVU3547-E

An attempt to start the job process has failed because the user (user-name) does not have permission to execute the executable file (file-name). (reason code:reason-code)

An attempt to start the job process has failed because the user does not have permission to execute the executable file.

(S)

Cancels the requested processing.

(O)

reason-code indicates the value obtained by the GetLastError function of the Win32 API.

If you are using the Windows UAC function and the OS user executing the job belongs to the Administrators group, Administrators permission might be disabled for this job. Either execute the job by using the built-in Administrator account, or enable the settings for executing jobs as a user with administrator permissions when the UAC is enabled, and then execute the job. For details, see 6.2.22 Settings for executing jobs as a user with administrator permissions when the UAC is enabled in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

For details on the Windows UAC function, see the Microsoft website.

KAVU3548-E

The size of argument and environment variable in job definition is greater than the system-imposed limit. (system call name:system-call-name, reason code:reason-code)

The total size of the parameters and environment variables specified in the job definition and the environment variable statements specified in the environment variable file exceeds the OS limit on the size of environment variable strings.

(S)

Cancels the request processing.

(O)

Review the parameters and environment variables specified in the job definition, and environment variable statements specified in the environment variable file.

KAVU3549-E

A system call (function-name) error occurred in a job execution process. (reason code:reason-code)

A system call error occurred during execution of the job.

(S)

Cancels the requested processing.

(O)

When function-name is write and reason-code is 0x0000001c, check whether the home directory of the OS user mapped to the execution user or the directory specified in the work path has been placed in the DiskFull status.

If the directory is placed in the DiskFull status, delete unnecessary files to increase free space, and then execute the job. For other cases, use the data collection tool to collect data, and then contact the system administrator.

Check whether the option described in 6.2.16 Executing a job that requires a user profile in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 is enabled. If it is enabled, enable the setting described in 6.2.17 Reusing access tokens for job execution in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

KAVU3550-W

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

The executable file does not exist.

(S)

Cancels the requested processing.

(O)

Check whether any of the following probable causes are present:

The relative path to the executable file has been specified, but the folder or directory necessary for execution has not been set in the PATH environment variable.

The specified executable file is on a network drive.

In a WOW64 environment, an executable file in %systemroot%\system32 has been specified.

If this message is output after execution of an action job, the platform set in the detailed definition of the action job is incorrect.

When a job is executing, the specified executable file is not found.

Take one of the following actions according to the cause of the error, and then reissue the request.

Make sure that the folder or directory necessary for the PATH environment variable has been correctly set.

Do not specify the path beginning with a network drive name. Instead, specify the path beginning with a computer name (for example, \\computer-name\shared-folder\executable-file-name).

In a WOW64 environment, if a file in %systemroot%\system32 is specified, file access is redirected to %systemroot%\syswow64. Take either of the following corrective actions:

- In Windows Server 2012 or the 64-bit version of Windows Server 2008, specify %systemroot%\sysnative instead of %systemroot%\system32, and then re-execute the job.

- In Windows Server 2003 (x64), when you execute a job in a WOW64 environment, disable file system redirection, and then re-execute the job.

For details about how to execute a job in a WOW64 environment, see 6.6.2 Disabling file system redirection when jobs are executed in a WOW64 environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Recheck the detailed definition of the action job, and then re-execute the action job.

Make sure that the executable file exists, and then re-execute the job. Also, make sure that the executable file will not be moved or deleted.

KAVU3551-W

You lack access permission for the execution file (file-name).

You do not have access permission for the executable file.

(S)

Cancels the requested processing.

(O)

The probable causes are:

Access permissions for the OS user who is executing the job are not set in the specified file or file path.

In UNIX, the owner group of the specified file or its directory is the secondary group of the OS user who is executing the job.

Take one of the following actions according to the cause of the error:

In the specified file or file path, set access permissions that allow the OS user to execute the job.

Take either of the following actions:

- Change the owner group of the specified file and its directory from the secondary group of the OS user who executes the job, to the primary group.

- Enable the option described in 15.2.18 Enabling the file access permission check for the ACL and secondary group settings during job execution in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

KAVU3552-W

The environment variable file (file-name) was not found.

The environment variable file does not exist.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3553-W

You lack access permission for the environment variable file (file-name).

You do not have access permission for the environment variable file.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3554-W

The environment variable file (file-name) cannot be opened.

The system cannot open the environment variable file.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the environment variable file name.

KAVU3555-W

The environment variable file (file-name) cannot be accessed (function-name). (reason code:reason-code)

The system failed to access the environment variable file.

(S)

Cancels the requested processing.

(O)

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

KAVU3556-W

The standard input file (file-name) cannot be found.

The standard input file does not exist.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3557-W

You lack access permission for the standard input file (file-name).

You do not have access permission for the standard input file.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3558-W

The standard input file (file-name) cannot be opened.

The system cannot open the standard input file.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the standard input file name.

KAVU3559-W

The standard input file (file-name) could not be accessed (function-name). (reason code:reason-code)

The system failed to access the standard input file.

(S)

Cancels the requested processing.

(O)

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

KAVU3560-W

You lack access permission for the standard output file (file-name).

You do not have access permission for the standard output file.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3561-W

The standard output file (file-name) cannot be opened.

The system cannot open the standard output file.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the standard output file name.

KAVU3562-W

The standard output file (file-name) could not be accessed (function-name). (reason code:reason-code)

The system failed to access the standard output file.

(S)

Cancels the requested processing.

(O)

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

Cautionary note

If the KAVU3217-W message was output before or after this message, an error occurred during the transfer processing for a result file. If 1 is set for the IgnoreResultFileError environment setting parameter, the return code of the job process is set for the return code of the job, and the job is placed into the Ended normally, Ended with warning, or Ended abnormally status depending on the final judgment. In addition, the result file is not re-sent, because termination of the job is preferred. Accordingly, you cannot use the Execution Result Details dialog box of JP1/AJS3 - View to view the contents of the standard error output file.

Because the result file for the job is not re-sent, the values set for the NotfyJobStateInterval and NotfyJobStateCount environment setting parameters will not be enabled. (These parameters specify the interval for resending the result file for the job and the number of times it is re-sent.)

For details about the IgnoreResultFileError environment setting parameter, see 2.3 Setting up the job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVU3563-W

You lack access permission for the standard error output file (file-name).

You do not have access permission for the standard error output file.

(S)

Cancels the requested processing.

(O)

The probable causes are:

Access permissions for the OS user who is executing the job are not set in the standard error output file or file path.

Access permissions for the OS user who is executing the job are not set in the work path for executing the agent process defined in the environment setting parameter.

Take one of the following actions according to the cause of the error:

In the standard error output file or file path, set access permissions for the OS user who is executing the job.

In the work path for executing the agent process defined in the environment setting parameter, set access permissions for the OS user who is executing the job.

KAVU3564-W

The standard error output file (file-name) could not be opened.

The system cannot open the standard error output file.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the standard error output file name.

KAVU3565-W

The standard error output file (file-name) could not be accessed (function-name). (reason code:reason-code)

The system failed to access the standard error output file.

(S)

Cancels the requested processing.

(O)

The probable causes are:

Access permissions for the OS user who is executing the job are not set in the standard error output file or file path.

In UNIX, if reason code 0x0000001c is indicated, check whether there is sufficient free space on the disk containing the directory indicated in file-name.

Take one of the following actions according to the cause of the error:

In the standard error output file or file path, set access permissions for the OS user who is executing the job.

If free space on the disk is insufficient, delete unnecessary files to free more space, and then retry the operation.

Cautionary note

If the KAVU3217-W message was output before or after this message, an error occurred during the transfer processing for a result file. If 1 is set for the IgnoreResultFileError environment setting parameter, the return code of the job process is set for the return code of the job, and the job is placed into the Ended normally, Ended with warning, or Ended abnormally status depending on the final judgment. In addition, the result file is not re-sent, because termination of the job is preferred. Accordingly, you cannot use the Execution Result Details dialog box of JP1/AJS3 - View to view the contents of the standard error output file.

Because the result file for the job is not re-sent, the values set for the NotfyJobStateInterval and NotfyJobStateCount environment setting parameters will not be enabled. (These parameters specify the interval for resending the result file for the job and the number of times it is re-sent.)

For details about the IgnoreResultFileError environment setting parameter, see 2.3 Setting up the job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVU3566-W

The work path name (path-name) is too long, so the file cannot be created.

The work path name is too long, so the file cannot be created.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3567-W

The work path (path-name) cannot be found.

The work path does not exist, or you do not have access permission for the work path.

(S)

Cancels the requested processing.

(O)

Check whether the work path exists. If it exists, check whether the user who started the JP1/AJS3 service has permission to access the work path. Remove the cause of the error, and then reissue the request.

KAVU3568-W

You lack access permission for the work path (path-name).

You do not have access permission for the work path.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3569-W

The file path (path-name) variable could not be resolved.

The system failed to resolve the file path variable.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3570-W

The parameter (path-name) variable could not be resolved.

The system failed to resolve the parameter variable.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3571-W

User mapping (JP1-user-name) failed.

User mapping failed.

(S)

Cancels the requested processing.

(O)

Check whether any of the following probable causes are present:

The user mapping definition for the agent host does not contain the JP1 user.

The user mapping definition for the agent host contains a non-existent OS user.

The user mapping definition for the agent host contains an OS user with an invalid password (Windows only).

There is no JP1 user that has the same name as the OS user who executed the ajsentry command.

Memory was insufficient.

When User who owns is specified for Executed by and the Owner column is blank, an OS user whose name is not registered as a JP1 user is set for the JP1/AJS3 service startup account on the manager host.

If the JP1/AJS3 service startup account has been changed from a system account to a user account, the user account does not have the necessary permissions (Windows only).

Take one of the following actions according to the cause of the error:

In the user mapping definition for the agent host that executes the job, register the JP1 user indicated in JP1-user-name in the message, and then map the JP1 user to the OS user.

In the user mapping definition for the agent host that executes the job, register an existing OS user.

Execute the jbsumappass command to reset the OS user's password. For password, specify the OS user's password (Windows only).

Do either of the following, and then re-execute the ajsentry command:

- Add a JP1 user that has the same name as the OS user, and then map the JP1 user to the OS user.

- In the job definition, specify the owner as the user who executes the job.

Check the memory status, and re-estimate memory requirements.

In the user mapping definition, register the JP1 user indicated in JP1-user-name in the message. Alternatively, in Windows, set the OS user whose user name is registered as a JP1 user for the JP1/AJS3 service startup account on the manager host.

Set the necessary permissions for the user account that starts the JP1/AJS3 service. For details, see 4.2.3 Changing the JP1/AJS3 service settings (Windows only) in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

For details on how to set up user mapping, see 3. Setup in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under Windows)or 13. Setup in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under UNIX).

For details on the JP1/AJS3 commands, see 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

For details about the JP1/Base commands, see the Job Management Partner 1/Base User's Guide.

For cases other than the above, check the integrated trace log for whether a KAVUxxxx message was output before or after this message. If a KAVUxxxx message was output, read the message explanation.

KAVU3572-W

The user (user-name) could not be masked.

The system failed to mask the user.

(S)

Cancels the requested processing.

(O)

The user mapping definition may contain an error. Check the following:

The user mapping definition contains an OS user that does not exist.

The user mapping definition contains the OS user with an invalid password.

KAVU3573-W

The job priority could not be changed.

The system failed to change the job priority.

(S)

Cancels the requested processing.

(O)

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

KAVU3574-W

An error occurred while generating a job process. (reason code:reason-code)

An error occurred while the system was generating a job process.

(S)

Cancels the requested processing.

(O)

reason-code indicates either of the following values:

In Windows:

The value obtained by the GetLastError function of the Win32 API

In UNIX:

The value obtained by errno

The following describes probable causes for reason codes, and suggests corrective actions:

In Windows

reason-code: 87

The size of the environment variable statement specified by the environment variable and environment variable file name might exceed the upper limit of character strings permitted by the OS. Review the environment variable statement specified by the environment variable and environment variable file name.

reason-code: 740

If you are using the Windows UAC function and the OS user executing the job belongs to the Administrators group, Administrators permission might be disabled for this job. Either execute the job by using the built-in Administrator account, or enable the settings for executing jobs as a user with administrator permissions when the UAC is enabled, and then execute the job. For details, see 6.2.22 Settings for executing jobs as a user with administrator permissions when the UAC is enabled in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

For details on the Windows UAC function, see the Microsoft website.

reason-code: 1816

The OS resources might be insufficient. Check whether the OS resources are sufficient for executing the job.

In UNIX

reason-code: 28

The OS resources might be insufficient. Check whether the OS resources are sufficient for executing the job.

If reason-code indicates a value other than the one indicated above, check the meaning of your OS error codes, and then take appropriate action. If the error persists, collect the internal trace log, and then contact the system administrator.

KAVU3575-W

An error occurred while starting a job process. (reason code:reason-code)

An error occurred while the system was starting a job process.

(S)

Cancels the requested processing.

(O)

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

KAVU3576-W

The standard error file or standard error output file could not be sent.

The system failed to transfer the standard error file or standard error output file.

(S)

Cancels the requested processing.

(O)

If a process is accessing the standard output or standard error output file specified for the job, stop the process and ensure that no processes access the file while the job is being executed.

For any other case, check the integrated trace log for whether a KAVUxxxx message was output before or after this message. If a KAVUxxxx message was output, read the message explanation.

Cautionary note

If the KAVU3217-W message was output before or after this message, an error occurred during the transfer processing for a result file. If 1 is set for the IgnoreResultFileError environment setting parameter, the return code of the job process is set for the return code of the job, and the job is placed into the Ended normally, Ended with warning, or Ended abnormally status depending on the final judgment. In addition, the result file is not re-sent, because termination of the job is preferred. Accordingly, you cannot use the Execution Result Details dialog box of JP1/AJS3 - View to view the contents of the standard error output file.

Because the result file for the job is not re-sent, the values set for the NotfyJobStateInterval and NotfyJobStateCount environment setting parameters will not be enabled. (These parameters specify the interval for resending the result file for the job and the number of times it is re-sent.)

For details about the IgnoreResultFileError environment setting parameter, see 2.3 Setting up the job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVU3577-W

A system call (function-name) error occurred in a job execution process. (reason code:reason-code)

A system call error occurred in a job execution process.

(S)

Continues processing.

(O)

If function-name is UnloadUserProfile, the UnloadUserProfile function for Win32API has failed. In this case, processing continues, but a resource leak may have occurred.

If this message has been output many times for the UnloadUserProfile function, restart the JP1/AJS3 service.

If this message has been output a number of times in succession, or if an error occurred in a function other than the UnloadUserProfile function, use the data collection tool to collect data, and then contact the system administrator.

Check whether the option described in 6.2.16 Executing a job that requires a user profile in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 is enabled. If it is enabled, enable the setting described in 6.2.17 Reusing access tokens for job execution in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

KAVU3578-W

The execution file (file-name) could not be accessed (function-name). (reason code:reason-code)

The system failed to access the executable file.

(S)

Cancels the requested processing.

(O)

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

KAVU3579-W

A logical contradiction occurred in the job execution process. (module:reason-module[reason-module], reason code:reason-code)

A logical contradiction occurred in the job execution process.

(S)

Cancels the requested processing.

(O)

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

KAVU3580-W

The user (user-name) does not have administrator permission.

If you specify the execution priority of the Unix job to 4 or 5, the user that attempts to log in to the OS must have superuser privileges.

(S)

Cancels the requested processing.

(O)

Reissue the request as a user who has superuser privileges.

KAVU3581-W

The execution file (file-name) is not an executable file.

The file specified as the executable file cannot be executed.

(S)

Cancels the requested processing.

(O)

Probable causes are shown below. Remove the cause of the error, and then reissue the request.

The file specified for the executable file name is not associated with an appropriate application.

The file specified for the executable file name was not found.

If the executable file name was specified by using a UNC path, the file specified for the executable file name was not found due to a network failure.

Take one of the following actions according to the cause of the error:

Associate the file specified for the executable file name with an appropriate application.

Check whether the file specified for the executable file name exists.

If a network failure occurred, check and then correct the cause of the network failure. Alternatively, specify a file on the local drive for the executable file name.

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

KAVU3582-W

The specified execution file (file-name) cannot be merged with the command statement.

The execution file cannot be merged with the command statement.

(S)

Cancels the requested processing.

(O)

Correct the error, and then reissue the request.

KAVU3583-W

No path is specified to the destination for storing transfer files in the manager (logical-host-name).

The path to store transfer files is missing at the manager.

(S)

Cancels the requested processing.

(O)

Check whether the work path is specified in the common definition information for the manager.

KAVU3584-W

The transfer files at the manager (logical-host-name) could not be accessed.

The transfer file on the manager could not be accessed.

(S)

Cancels the requested processing.

(O)

Check whether the work path specified in the common definition information for the manager can be accessed.

KAVU3585-W

The manager (logical-host-name) disk is full.

There is an insufficient amount of disk space on the manager.

(S)

Cancels the requested processing.

(O)

Increase the free space in the disk on the manager.

KAVU3586-W

The privilege for service account was not set.

If the service account is set to the user account, privileges necessary for executing the process must be set.

(S)

Terminates the job.

(O)

Check the service account and privileges necessary for it. For details on the necessary privileges when the service account is set to the user account, see 4.2.3(1)(d) Privileges for running JP1/AJS3 services under a user account in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVU3587-W

Failed to set a limit (limit) on a system resource (system-resource-name). (reason code: reason-code)

You attempted to specify limit on system-resource-name but it could not be set.

(S)

Executes the job with the default limit.

(O)

Set the appropriate limit.

KAVU3588-E

Shared memory identifier could not be allocated.

The shared memory ID could not be allocated because the maximum number of shared memory IDs available for the system was exceeded.

(S)

Stops the daemon.

(O)

Use the kernel parameter to increase the maximum number of shared memory IDs available for the system, and then restart. For details on how to estimate the value to be set in the kernel parameter, see Release Notes.

KAVU3589-E

A pipe timeout error occurred in a job execution process (timeout value(second): seconds)

A timeout occurred during pipe communication in a job execution process.

(S)

Cancels the requested processing.

(O)

A cause may be one of the following:

Too many jobs are executed at once.

The CPU is heavily loaded.

The agent process for job execution control was swapped out for more than 300 seconds and not executed due to insufficient real memory.

If one of these causes persists and a timeout error frequently occurs during pipe communication, we recommend that you specify a timeout period longer for pipe communication on the host where the agent process is executed.

In case of Cause No. 3, check the memory usage for the entire system and increase the memory or suppress the startup of unnecessary processes to gain sufficient real memory.

For details on how to change a timeout value for pipe communication, see 15.2.15 Changing the timeout value for pipe communication of the agent in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

If the error persists even after changing the timeout value, use the data collection tool to collect data, and then contact the system administrator.

KAVU3590-W

The size of argument and environment variable in job definition is greater than the system-imposed limit.

The size of the parameter and the environment variable specified in the job definition plus the environment variable statement specified in the environment variable file name exceeds the upper limit specified for the system.

(S)

Cancels the requested processing.

(O)

Recheck the parameter or the environment variable specified in the job definition and the environment variable statement specified in the environment variable file name.

KAVU3591-W

The shell (shell-name) is not an executable file. (reason code:reason-code)

The execution shell of the job is not an executable shell.

(S)

Cancels the requested processing.

(O)

Check whether the login shell of the user that attempted to log in to the OS can be started. Alternatively, if the shell is specified by the jpqjobsub command or the JpqSubmitJob function, check whether the shell can be started.

KAVU3592-W

The agent does not have permission for changing owner of the file (type=file-name).

The agent does not have permission to change the owner of the file.

(S)

Cancels the requested processing.

(O)

If the file is stored in a directory mounted on an NFS or similar file system connected to a network, you might not be able to change the owner of the file. Check whether you can access the file and its directory using the JP1/AJS3 service account. Then, change the access permission for the file and its directory or change the directory so that they can be accessed using the JP1/AJS3 service account. The directory differs depending on a file type. Change the directory according to the following file types:

Temporary script file: The work path in the job definition, or the home directory of the execution user.

Standard output file: The directory to output to

Temporary standard output file: The work directory used for executing the agent process

Standard error output file: The directory to output to

Temporary standard error output file: The work directory used for executing the agent process

KAVU3593-W

The PATH variable for the user (user-name) could not be acquired.

The PATH environment variable for the user that attempted to log in to the OS could not be acquired.

(S)

Cancels the requested processing.

(O)

Check the following:

If the set -u or the script command is included in the login script of the executing OS user, check whether there is a condition that will terminate the processing before it is completed. If the login script contains a statement that is unnecessary for job execution by JP1/AJS3, delete the relevant location or use the JP1JobID environment variable to skip the relevant location. For details about how to change the login script, see 13.4.2 Changing the login scripts in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

For the work directory used for agent-process execution, check whether access permissions are set for the user starting the JP1/AJS3 service and the OS user executing the job. If read permission and write permission are not set, set these permissions.

For all other cases, check whether there is too little disk space for the directory used as the work directory when the agent process for job execution control is executed. If the disk capacity is insufficient, create free space and issue another request.

KAVU3594-W

The work path (work-path-name) or the file path (file-name) is too long.

The work directory for the common definition information, the work path for the job definitions, or the name of the file is too long.

(S)

Cancels the requested processing.

(O)

Some work path names or file names may have an allowable length that exceeds the upper limit for the system. This depends on a system.

Set the work path name or the file name according to the upper limit for the system.

KAVU3595-W

The execution shell (execution-shell-name) was not found.

There is no shell used to execute the job.

(S)

Cancels the requested processing.

(O)

Check the shell used to execute the job.

KAVU3596-W

The temporary script file (file-name) for job (job-number) was not found. (system call name:system-call-name, reason code:reason-code)

There is no temporary script file for the job.

(S)

Cancels the requested processing.

(O)

A temporary script file for the job (a file whose name begins with JPQ_EXEC) was not created in either of the following directories: the home directory of the OS user mapped to the JP1 user, or the directory specified for the work path in the job definition.

Make sure that the home directory of the OS user mapped to the JP1 user or the directory specified for the work path in the job definition exists. Also make sure that you have write permissions as a superuser.

For cases other than the above, check whether the temporary script file for the job was deleted during operation of the JP1/AJS3 service.

KAVU3597-W

The temporary script file (file-name) for job (job-number) was busy. (system call name:system-call-name, reason code:reason-code)

The temporary script file for the job could not be deleted because the file was running.

(S)

Cancels the requested processing.

(O)

A temporary script file for the job (file whose name begins with JPQ_EXEC) was temporarily created in the home directory of the OS user mapped to the user who executes the job or in the directory in the work path.

Check whether any other program accesses this file illegally during operation. If an invalid file remains when JP1/AJS3 stops, delete it.

KAVU3598-W

The work path (path-name) is not a full path.

The work path must be specified with an absolute path name.

(S)

Cancels the requested processing.

(O)

Check the work path in the job definition.

KAVU3599-W

The end judgment file (file-name) could not be accessed. (reason code:reason-code)

The end judgment file could not be accessed.

(S)

Cancels the requested processing.

(O)

Check whether the access permission is changed illegally for the end judgment file used in the job definition.

KAVU3800-I

Execution of command step (command-line) terminated. (return code : return-code)

Execution of the command step specified in the jp1exec command terminated.

(S)

Continues processing.

KAVU3900-E

The command step (command-line) could not be started. (reason code:reason-code)

The reason code indicates a Win32API detail code.

(S)

Cancels executing the jp1exec or jp1exit command.

(O)

Make sure that the command exists and you have permission to execute the command, and then re-execute the command.

If the Windows UAC function is enabled and the reason code is 0x000002e4, Administrator permission might be disabled for this job. Either execute the job by using the built-in Administrator account, or enable the settings for executing jobs as a user with administrator permissions when the UAC is enabled, and then execute the job. For details, see 6.2.22 Settings for executing jobs as a user with administrator permissions when the UAC is enabled in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

For details on the Windows UAC function, see the Microsoft website.

KAVU3901-E

The return code for the command step (command-line) could not be acquired. (reason-code)

The system failed to acquire the return code for the command step.

(S)

Cancels executing the jp1exec or jp1exit command.

(O)

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

KAVU3902-E

The temporary file for the command step (command-line) could not be opened. (reason code:reason-code)

The system cannot open the temporary file for the command step.

(S)

Cancels executing the jp1exec or jp1exit command.

(O)

If write or read permissions for the OS user who executes the job are not set in the path in which the temporary file for the command step will be created, grant the required permissions.

Note that the system searches the environment variables below for the path, and then creates the temporary file for the command step only in the path it finds first. If the path is not set in any environment variable, the temporary file for the command step is created in the Windows installation folder.

The tmp environment variable for the user who started the JP1/AJS3 service

The tmp system environment variable

The temp environment variable for the user who started the JP1/AJS3 service

The temp system environment variable

KAVU3903-E

The temporary file for the command step (command-line) could not be accessed. (reason code:reason-code)

The system failed to access the temporary file for the command step.

(S)

Cancels executing the jp1exec or jp1exit command.

(O)

The detail code of Win32API is shown in reason-code.

If reason-code is 0, the jp1exit command may be written more than once in succession in one batch file. Check the batch file containing the jp1exit command.

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

KAVU3904-E

The temporary file for the command step (command-line) could not be deleted. (reason code:reason-code)

The system cannot delete the temporary file for the command step.

(S)

Cancels executing the jp1exec or jp1exit command.

(O)

More than one jp1exit command may be described in one batch file. Check the batch file containing the jp1exit command.

KAVU3905-E

The host name could not be acquired in the command step. (reason code:reason-code)

The system failed to acquire the host name in the command step.

(S)

Cancels executing the jp1exec or jp1exit command.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then call the function again.

KAVU3906-E

Invalid environment settings were detected in the command step. (reason code:reason-code)

The system detected invalid environment settings in the command step.

(S)

Cancels executing the jp1exec or jp1exit command.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then call the function again.

If the integrated trace log contains the message KAVU7221-E (Environment setting parameter (parameter-name=parameter value) on the logical host (logical-host-name) is invalid.), the OS user executing the command might not have been granted write and read permissions for the output path. If this is the case, grant write and read permissions, and then re-execute the command.

KAVU4100-I

Job queuing control (logical-host-name) was started.

Job queuing control was started.

(S)

Starts the daemon.

KAVU4101-I

Job queuing control (logical-host-name) is terminating.

Job queuing control is being terminated.

(S)

Continues stopping the daemon.

KAVU4102-I

Job queuing control (logical-host-name) was paused.

Job queuing control was temporarily terminated.

(S)

Stops the daemon temporarily.

KAVU4103-I

Job queuing control (logical-host-name) was restarted.

Job queuing control was restarted.

(S)

Starts the daemon.

KAVU4104-I

Job queuing control (logical-host-name) ended normally.

Job queuing control terminated normally.

(S)

Stops the daemon.

KAVU4105-I

The queuing control (logical-host-name) has changed to reduced manager operation mode.

Queuing control is placed in reduced manager operation mode.

(S)

Places queuing control in reduced manager operation mode. The system does not accept job execution requests or requests from commands.

KAVU4110-E

Job queuing control (logical-host-name) ended abnormally. (reason code:reason-code)

The manager process for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU4111-E

Job queuing control (logical-host-name) or jpqimport command is already running on the same host.

An attempt was made to start more than one manager process for job execution control on the same logical host. Alternatively, the jpqimport command is running.

(S)

Cancels the startup of the JP1/AJS3 service.

(O)

Check whether the JP1/AJS3 service has already started or whether the jpqimport command is running.

KAVU4112-E

The system will wait because the database could not be connected. (Waittime: maximum-wait-time, Host: host-name)

The database could not be connected within the specified maximum wait time.

(S)

Cancels the requested processing.

(O)

Check whether the database is running.

For details about how to check this, see the manual for the appropriate database.

If the database is starting, recheck the value of the maximum wait time.

KAVU4113-W

The database could not be connected within the specified time. (Waittime: maximum-wait-time, Host: host-name)

The system will wait because the database could not be connected.

(S)

Retries the connection after a predefined period of time.

(O)

Check whether the database is running.

For details about how to check this, see the manual for the appropriate database.

KAVU4200-E

The user (user-name) request (request-name) for the parameter (parameter=parameter value) is invalid.

Invalid data was found in the request parameter during analysis of the request to the manager process for job execution control.

(S)

Cancels the analysis of the request to the manager process for job execution control.

(O)

Check the following:

If the requesting host is a JP1/AJS3 host and the parameter name is jobNumber, check whether the number of digits in the specified job number is from 1 to 6. If 7 or more digits have been used, specify another job number that consists of only 1 to 6 digits, and then retry the operation.

If the requesting host is a JP1/AJS3 host and the parameter name is controlStdFile, and if the same file name is specified for the standard output file and the standard error output file for the job, check whether the append option settings match. If there is no match, correct the settings, and then retry the operation. In addition, if you need to change the settings, specify different file names for the standard output file and the standard error output file.

If the character encoding on the requesting host is different from the encoding on the manager host, the data size for some items specified in the job definition (such as executable file name and environment variables) might have increased due to character code conversion during data transfer. If character codes are converted on the manager host, make sure that the number of specified characters does not exceed the specifiable number of characters. If you are not certain whether the limit has been exceeded, check the number of characters for the items specified in the job definition, and then retry.

If the requesting host is JP1/AJS3 and the parameter name is szExecAgentName, make sure that the specified execution agent does not have any characters that cannot be used. If there are any, specify a name that does contain the unusable characters, and then retry the operation.

For cases not covered above, a request that the manager process for job execution control does not accept might have been accepted. Check the services file for the manager host and the requesting host, and make sure that the port number for jp1ajs2qman or jp1ajs2qnfy is not the same as that of another port name. If there is a duplication, change the port number that is set, and restart JP1/AJS3.

For all other cases, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the requesting client host.

KAVU4202-E

The user (user-name) lacks permission for the request (request-name). (reason code:reason-code)

The user who issued a request to the manager process for job execution control does not have the permissions required to issue the request.

A user with the JP1_JPQ_User permission level might have operated a job for another user.

(S)

Cancels the analysis of the request to the manager process for job execution control.

(O)

If you executed a command (jpqxxxx command) or issued a function for job execution control, check the permissions for the JP1 user name that is the same as the OS user name performing the operation. Check whether the OS user executing the command or issuing the function for job execution control has been registered as a JP1 user on the authentication server. Also check whether the JP1 resource group (JP1_Queue) to which the JP1 user (OS user) belongs has the JP1 permission level required to execute the command or issue the function.

If the executing JP1 user has only the JP1_JPQ_User permission, operations available to the JP1 user and what that JP1 user can reference does not extend to jobs other than jobs submitted by the executing JP1 user. Accordingly, execution is limited to the user who submitted the job, a user who has the JP1_JPQ_Admin permission, and a user who has the JP1_JPQ_Operator permission.

You therefore need to register the OS user as a JP1 user on the authentication server, and if necessary, grant the JP1 user execute permission.

For details about the execute permission for the commands for job execution control, see 1.5 Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU4203-E

An error occurred while checking permission for the user (user-name) request (request-name). (reason code:reason-code)

An error occurred while checking permissions for a user who issued a request to the manager process for job execution control.

(S)

Cancels the analysis of the request to the manager process for job execution control.

(O)

Make sure that the authentication server has started. If the authentication server has not started, start it and then reissue the request. If this error occurs even though the authentication server is running, use the data collection tool to collect data, and then contact the system administrator.

KAVU4210-E

The Communication thread (logical-host-name) ended abnormally. (reason code:reason-code)

The thread for accepting a communication request for the manager process for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

The CPU may be over-loaded. Check the load on the CPU. Also use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU4211-E

The job dispatcher thread (logical-host-name) ended abnormally. (reason code:reason-code)

The job dispatcher thread for the manager process for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU4212-E

The scheduled monitoring thread (logical-host-name) ended abnormally. (reason code:reason-code)

The thread for monitoring scheduled jobs in a wait state for the manager process for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU4213-E

The thread (logical-host-name) for monitoring the number of concurrently-executable jobs terminated abnormally. (reason code:reason-code)

The thread for monitoring the number of concurrently-executable jobs for the manager process for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU4214-E

The automatic log deletion thread (logical-host-name) ended abnormally. (reason code:reason-code)

The job information deletion thread for the manager process for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU4215-E

The agent monitoring thread (logical-host-name) ended abnormally. (reason code:reason-code)

The agent monitoring thread for the manager process for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU4220-E

The job execution request to the agent (agent-host-name) failed. (reason code:reason-code)

The job execution request to the agent process for job execution control has failed. The probable causes are:

Memory was insufficient. (reason-code = 0xe00a0002)

File transfer has failed. (reason-code = 0xe00a000e)

The agent host has stopped. (reason-code = 0xe00a0007)

The JP1/AJS3 service on the agent host has stopped. (reason-code = 0xe00a0007)

For communication between the manager host and the agent host, an attempt was made to use address families that are not able to communicate with each other. (reason-code = 0xe00a0007)

Example: Communication was attempted when the name resolution result for the manager host was an IPv4 address only and the name resolution result for the agent host on the manager host was an IPv6 address only.

The agent host name is invalid. (reason-code = 0xe00a0008)

The JP1/AJS3 service on the agent host is starting or terminating. (reason-code = 0xe00a0009)

The error was caused by the agent host (reason-code = 0xe00a000d)

The communication protocol is not supported. (reason-code = 0xe00a000e)

The request was rejected on the agent host by the connection source restriction function. (reason-code = 0xe00a0017)

(S)

Cancels the job execution request to the agent host.

(O)

Use the integrated trace log to check whether a KAVUxxxx or KNACxxxx message was output before or after this message. If it was output, also see the explanation provided in that message.

If the reason code is 0xe00a000d, indicating that the error was caused by the agent host, also check the integrated trace log for the agent host. If no such messages were output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4221-E

The job termination request to the agent (agent-host-name) failed. (reason code:reason-code)

The job termination request to the agent process for job execution control has failed. The probable causes are:

Memory was insufficient. (reason-code = 0xe00a0002)

The agent host has stopped. (reason-code = 0xe00a0007)

The JP1/AJS3 service on the agent host has stopped. (reason-code = 0xe00a0007)

For communication between the manager host and the agent host, an attempt was made to use address families that are not able to communicate with each other. (reason-code = 0xe00a0007)

Example: Communication was attempted when the name resolution result for the manager host was an IPv4 address only and the name resolution result for the agent host on the manager host was an IPv6 address only.

The agent host name is invalid. (reason-code = 0xe00a0008)

The JP1/AJS3 service on the agent host is starting or terminating. (reason-code = 0xe00a0009)

The error was caused by the agent host (reason-code = 0xe00a000d)

The communication protocol is not supported. (reason-code = 0xe00a000e)

No job exists on the agent host. (reason-code = 0xa00a0005)

The request was rejected on the agent host by the connection source restriction function. (reason-code = 0xe00a0017)

(S)

Cancels the job termination request to the agent host.

(O)

Use the integrated trace log to check whether a KAVUxxxx or KNACxxxx message was output before or after this message. If it was output, also see the explanation provided in that message.

If the reason code is 0xe00a000d, indicating that the error was caused by the agent host, also check the integrated trace log for the agent host.

If the reason code is 0xa00a0005, indicating that no job exists on the agent host, the job may have already terminated on the agent host before the forced termination. Use either of the following methods to check the status of the job.

For a PC job, Unix job, action job, or custom job:

Check JP1/AJS - View or execute the ajsshow command.

For a QUEUE job or submit job:

Execute the jpqjobget command.

If no other message has been output and you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4222-E

The job confirmation request to the agent (agent-host-name) failed. (reason code:reason-code)

The job confirmation request to the agent process for job execution control has failed. The probable causes are:

Memory was insufficient. (reason-code = 0xe00a0002)

The agent host has stopped. (reason-code = 0xe00a0007)

The JP1/AJS3 service on the agent host has stopped. (reason-code = 0xe00a0007)

For communication between the manager host and the agent host, an attempt was made to use address families that are not able to communicate with each other. (reason-code = 0xe00a0007)

Example: Communication was attempted when the name resolution result for the manager host was an IPv4 address only and the name resolution result for the agent host on the manager host was an IPv6 address only.

The agent host name is invalid. (reason-code = 0xe00a0008)

The JP1/AJS3 service on the agent host is starting or terminating. (reason-code = 0xe00a0009)

The error was caused by the agent host (reason-code = 0xe00a000d)

The communication protocol is not supported. (reason-code = 0xe00a000e)

No job exists on the agent host. (reason-code = 0xa00a0005)

The request was rejected on the agent host by the connection source restriction function. (reason-code = 0xe00a0017)

(S)

Cancels the job confirmation request to the agent host.

(O)

Use the integrated trace log to check whether a KAVUxxxx or KNACxxxx message was output before or after this message. If it was output, also see the explanation provided in that message.

If the reason code is 0xe00a000d, indicating that the error was caused by the agent host, also check the integrated trace log for the agent host.

If the reason code is 0xa00a0005, indicating that no job exists on the agent host, the JP1/AJS3 service on the agent may have been restarted during execution of the job. In this case, the job was terminated forcibly.

If no other message has been output and you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4223-E

The operating status confirmation request to the agent (agent-host-name) failed. (reason code:reason-code)

The operating status confirmation request to the agent process for job execution control has failed. The probable causes are:

Memory was insufficient. (reason-code = 0xe00a0002)

The agent host has stopped. (reason-code = 0xe00a0007)

The JP1/AJS3 service on the agent host has stopped. (reason-code = 0xe00a0007)

For communication between the manager host and the agent host, an attempt was made to use address families that are not able to communicate with each other. (reason-code = 0xe00a0007)

Example: Communication was attempted when the name resolution result for the manager host was an IPv4 address only and the name resolution result for the agent host on the manager host was an IPv6 address only.

The agent host name is invalid. (reason-code = 0xe00a0008)

The JP1/AJS3 service on the agent host is starting or terminating. (reason-code = 0xe00a0009)

The error was caused by the agent host. (reason-code = 0xe00a000d)

The communication protocol is not supported. (reason-code = 0xe00a000e)

The request was rejected on the agent host by the connection source restriction function. (reason-code = 0xe00a0017)

(S)

Cancels the operating status confirmation request to the agent host.

(O)

Use the integrated trace log to check whether a KAVUxxxx or KNACxxxx message was output before or after this message. If it was output, also see the explanation provided in that message.

If the reason code is 0xe00a000d, indicating that the error was caused by the agent host, also check the integrated trace log for the agent host. If no such messages were output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4224-E

Client (client-host-name) could not be notified about job status. (reason code:reason-code)

The system failed to notify the status notification process of job execution control or of the client host of the job status. The probable causes are:

Memory was insufficient. (reason-code = 0xe00a0002)

The client host has stopped. (reason-code = 0xe00a0007)

The status notification process has stopped. (reason-code = 0xe00a0007)

For communication between the manager host and the agent host, an attempt was made to use address families that are not able to communicate with each other. (reason-code = 0xe00a0007)

Example: Communication was attempted when the name resolution result for the manager host was an IPv4 address only and the name resolution result for the agent host on the manager host was an IPv6 address only.

The client host name is invalid (reason-code = 0xe00a0008)

The status notification process for the client host is starting or terminating. (reason-code = 0xe00a0009)

The error was caused by the client host. (reason-code = 0xe00a000d)

The communication protocol is not supported. (reason-code = 0xe00a000e)

(S)

Cancels the job status notification to the status notification process.

(O)

Use the integrated trace log to check whether a KAVUxxxx or KNACxxxx message was output before or after this message. If it was output, also see the explanation provided in that message.

If the reason code is 0xe00a000d, indicating that the error was caused by the client host, also check the integrated trace log for the client host. If no such messages were output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4225-W

The operating status of the manager (logical-host-name) could not be acquired. (reason code:reason-code)

The system failed to acquire the operating status of the manager.

(S)

Cancels the requested processing.

(O)

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

KAVU4226-W

The operating status of the manager (logical-host-name) could not be changed(operating-status). (reason code:reason-code)

The system failed to change the operating status of the manager.

(S)

Cancels the requested processing.

(O)

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

KAVU4250-E

The database (logical-host-name) is not created correctly. (reason code:reason-code)

The database directory path or database file for the job execution environment was not found.

(S)

Stops the JP1/AJS3 service.

(O)

Make sure that the path and database file are correctly created for the database directory name for the job execution environment specified in the DatabasePath environment setting parameter. If they are not, use the jpqimport command to create a database, and then restart the JP1/AJS3 service.

KAVU4251-E

You lack operate permission for the database (logical-host-name). (reason code:reason-code)

You do not have access permissions for the database directory path or database file for the job execution environment.

(S)

Stops the JP1/AJS3 service.

(O)

Check the access permissions for the path and database file for the database directory name for the job execution environment specified in the DatabasePath environment setting parameter. You require the write and read permissions for the account that uses the JP1/AJS3 service. If the required permissions are not set, set the required permissions and then restart the JP1/AJS3 service.

The database file contains an ISAM file beginning with JPQ and the .jpqdb.lck file.

KAVU4252-E

A logical contradiction occurred in the database (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

An inconsistency was found in the database key file for the job execution environment. The database may have been damaged when JP1/AJS3 was stopped suddenly because the system was turned off inadvertently.

(S)

Stops the JP1/AJS3 service.

(O)

Reorganize the job execution environment database, and then restart the JP1/AJS3 service. If this error occurs again, use the data collection tool to collect data, and then contact the system administrator.

If this error still occurs after re-organizing the database, you must re-create the database.

KAVU4253-E

Environment setting (logical-host-name) does not match current information in the database.

The maximum number of configuration definitions read from the environment settings is smaller than the number of definitions in the job execution environment database. The environment settings may have been changed after a job execution environment (including job execution agents, queues, and execution-locked resources) was created with the configuration definition file for the submit job execution environment (jpqsetup.conf) or after the job was queued.

(S)

Stops the JP1/AJS3 service.

(O)

Make sure that the maximum value for the agent ID, queue ID, or locked resource ID does not exceed the maximum number of definitions specified in the configuration definition file for the (jpqsetup.conf) used for creating the submit job execution environment. To check which configuration definition of the agent ID, queue ID, or execution-locked resource ID exceeds the maximum, see the KAVU45xx message that was output immediately before this message. If the number of registered jobs exceeds the maximum, check whether the maximum number of jobs within the system specified in the environment settings is smaller than the actual number of registered jobs.

KAVU4254-E

It cannot access the database (logical-host-name). (reason code:reason-code)

An attempt to access the job execution environment database has failed. The probable causes are:

The specified database file does not exist. (reason code = 0xe00b0004)

An attempt to lock the database has failed. (reason code = 0xe00b0008)

The system resources (semaphores) were insufficient. (reason code = 0xe00b000f)

The disk has insufficient free space. (reason code = 0xe00b0010)

The number of open files reached the maximum for the system. (reason code = 0xe00b0011)

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the reason code. Check for the system resource limits that you must change. Correct the cause of the error, and then reissue the request.

KAVU4255-E

It cannot connect the database ( logical-host-name). (reason code: reason-code)

An attempt to connect to the job execution environment database has failed. The probable causes are:

The user name or password is invalid. (reason code = 0xe00b0016)

The number of database connections exceeded the server limit. (reason code = 0xe00b0017)

The database is not running. (reason code = 0xe00b0018)

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message.

If one was output, also see the explanation provided by the message. If no message was output or if a reason number other than one indicated above was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU4256-E

The system file(system-file-name) cannot be removed because it lacks access authority.

A system file (a temporary file for job execution control) cannot be deleted because access permissions have not been set.

(S)

Cancels the deletion of the system file.

(O)

The system file is stored in the scheduler service's directory for temporary files.

Check whether access permissions on the directory specified in the AJSTMPDIR environment setting parameter for the definition key [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name] have been set.

For details about the AJSTMPDIR environment setting parameter, see 2.2.2(53) AJSTMPDIR in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVU4257-E

The system file(system-file-name) could not be removed because a system call error occurred.

The system file (a temporary file for job execution) could not be deleted due to a system call error.

(S)

Cancels the deletion of the system file.

(O)

The system file is stored in the scheduler service's directory for temporary files.

Check whether the directory specified in the AJSTMPDIR environment setting parameter for the definition key [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name] exists, and also check the access permissions.

For details about the AJSTMPDIR environment setting parameter, see 2.2.2(53) AJSTMPDIR in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVU4258-E

The system file(system-file-name) cannot be opened. (reason code:reason-code)

An attempt to open the system file has failed.

(S)

Cancels the requested processing.

(O)

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

KAVU4259-E

The system file cannot be closed. (number of files: number-of-files)

An attempt to close the system file has failed.

(S)

Cancels the requested processing.

(O)

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

KAVU4260-E

The system file(system-file-name) cannot be accessed(function-name). (reason code:reason-code)

An attempt to access the system file has failed.

(S)

Cancels the requested processing.

(O)

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

KAVU4261-E

The system file(system-file-name) cannot be written(function-name). (reason code:reason-code)

An attempt to write to the system file has failed.

(S)

Cancels the requested processing.

(O)

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

KAVU4262-E

The system file(system-file-name) cannot be deleted. (reason code:reason-code)

An attempt to delete the system file has failed.

(S)

Cancels the requested processing.

(O)

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

KAVU4263-E

The system file(system-file-name) cannot be read. (reason code:reason-code)

An attempt to read the system file has failed.

(S)

Cancels the requested processing.

(O)

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

KAVU4264-E

A logical contradiction occurred in the system file access process. (reason code:reason-code)

A logical contradiction occurred during access to the system file.

(S)

Cancels the requested processing.

(O)

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

KAVU4265-E

Memory could not be allocated during the system file access. (reason code:reason-code)

Memory could not be secured during access to the system file.

(S)

Cancels the requested processing.

(O)

Stop unnecessary applications, and then retry the operation causing the error. If the same message is output again, review the memory estimate.

KAVU4266-E

A system call error occurred in the system file access process. (reason code:reason-code)

A system call error occurred during access to the system file.

(S)

Cancels the requested processing.

(O)

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

KAVU4267-E

The agent manager function has stopped and the exec-agent cannot be registered.

The probable cause is one of the following:

The logical host name contains an error.

The execution agent cannot be registered because the agent manager function has stopped.

(S)

Cancels the requested processing.

(O)

Check the logical host name specified in the JP1_HOSTNAME environment variable, and then re-execute the job.

If the agent manager function is not running, start it, and then re-execute the job.

KAVU4268-E

The agent manager function host name cannot be resolved.

The probable cause is one of the following:

The logical host name specified in the JP1_HOSTNAME environment variable could not be resolved.

Connection to the authentication server failed.

(S)

Cancels the requested processing.

(O)

If the JP1_HOSTNAME environment variable contains a logical host name, review the specified value, check the hosts file and other settings, and then re-execute the job.

If the authentication server is not running, start JP1/Base.

KAVU4269-E

An attempt to connect to the agent manager function host failed.

An attempt to connect to the host on which the agent manager function runs has failed.

(S)

Cancels the requested processing.

(O)

Make sure that there is a host on which the agent manager function runs, and then re-execute the job.

KAVU4270-E

The system file name(system-file-name) cannot be changed. (reason code:reason-code)

An attempt to change the system file name has failed.

(S)

Cancels the requested processing.

(O)

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

KAVU4271-E

The system file(system-file-name) cannot be moved. (reason code:reason-code)

An attempt to move the system file has failed.

(S)

Cancels the requested processing.

(O)

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

KAVU4272-E

A system call error occurred in the system file convert process. (system call name: system-call-name,module:reason-location[reason-location], reason code:reason-code)

A system call error occurred during system file conversion processing.

(S)

Cancels the requested processing.

(O)

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

KAVU4273-W

The temporary directory(temporary-directory-name) could not be deleted in the system file convert process.

An attempt to delete the temporary directory failed during system file conversion processing.

(S)

Continues processing.

(O)

If necessary, delete the directory indicated by temporary-directory-name.

KAVU4280-E

Memory could not be allocated. (size:size, module:reason-location[reason-location], reason code:reason-code)

The system failed to allocate memory.

(S)

Cancels the requested processing.

(O)

Terminate any other unnecessary applications, and then reissue the request. If the same message reappears, re-estimate memory.

KAVU4281-E

Insufficient disk space. (module:reason-location[reason-location], reason code:reason-code)

The amount of free space in the disk is insufficient.

(S)

Cancels the requested processing.

(O)

Increase the free space in the disk, and then reissue the request.

KAVU4282-E

A system call error occurred when starting process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred when the manager process for job execution control was starting.

(S)

Stops the JP1/AJS3 service.

(O)

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

KAVU4284-W

A system call error occurred in the communication process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred during pipe communication for the manager process for job execution control.

(S)

Cancels the requested processing.

(O)

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

KAVU4286-W

A system call error occurred in the request process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred during analysis of the request for the manager process for job execution control.

(S)

Cancels processing to analyze the request for the manager process for job execution control.

(O)

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

KAVU4287-E

A logical contradiction occurred in the request process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

An invalid parameter was found during analysis of the request for the manager process for job execution control.

(S)

Cancels processing to analyze the request for the manager process for job execution control.

(O)

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

KAVU4288-W

A system call error occurred in the internal process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred in the manager process for job execution control.

(S)

Cancels processing to analyze the request for the manager process for job execution control.

(O)

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

KAVU4289-E

A logical contradiction occurred in the internal process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A logical contradiction occurred during internal processing for the manager process for job execution control. Alternatively, a shutdown request from the monitoring process for job execution control could not be accepted because the request was invalid.

(S)

Cancels processing to analyze the request for the manager process for job execution control.

(O)

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

KAVU4290-E

User authentication could not be initialized because the logical host name (logical-host-name) or the authentication server is invalid.

The user authentication could not be initialized since the logical host name or the authentication server name was not set or the IP address of the name could not be resolved.

(S)

Stops the JP1/AJS3 service.

(O)

Recheck the environment settings to see whether the logical host name and authentication server name are correctly set. Check the environment settings to make sure that a format error or data error did not occur in definition information below the logical host name key or JP1_DEFAULT key. Also make sure that the IP address can be determined from the specified host name. Correct the cause of the error, and then restart the JP1/AJS3 service.

KAVU4291-E

A logical contradiction occurred during the initialization of user authentication (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

An invalid parameter was found during initialization of user authentication for the manager process for job execution control.

(S)

Stops the JP1/AJS3 service.

(O)

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

KAVU4292-E

A system call error occurred during the initialization of user authentication (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred during initialization of user authentication for the manager process for job execution control.

(S)

Stops the JP1/AJS3 service.

(O)

Check whether a JP1/Base KAVA message was output to the integrated trace log for the agent host. If it was output, also see the explanation provided in that message. If you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU4293-W

The authentication server could not be connected, but initialization will continue.

The authentication server could not be connected.

(S)

Continues startup processing of the JP1/AJS3 service.

(O)

Check the authentication server setting to make sure that the authentication server name is set correctly. If the authentication server is not started, start it.

KAVU4294-I

The total file size of the result files, i.e. STANDARD-OUTPUT-FILE and STANDARD-ERROR-FILE, of the job with the Job (job-number) and the Agent (agent-host-name), exceed the limit (bytes) of the size of the receiving file.

The result file size exceeds the maximum.

(S)

Continues processing.

(O)

Since the system may be over-loaded, check the following settings according to your operation:

We recommend you reduce the size of the result file (standard output file or standard error output file) specified for the job so it is smaller than the maximum file size (the value set in LimitReceiveFileSize environment setting parameter).

KAVU4295-W

The total file size of the result files, i.e. STANDARD-OUTPUT-FILE and STANDARD-ERROR-FILE, of the job with the Job (job-number) and the Agent (agent-host-name), exceed the limit (bytes) of the size of the receiving file.

The result file size exceeds the maximum.

(S)

Receives the result file up to the maximum reception size.

(O)

Reduce the size of the result file. Then, if you need information on the standard output file or standard error output file, re-execute the job.

Reduce the size of the result file (standard output file or standard error output file) specified for the job so it is smaller than the maximum file size (the value set in LimitReceiveFileSize environment setting parameter). Alternatively, recheck the maximum file size.

KAVU4296-E

The total file size of the result files, i.e. STANDARD-OUTPUT-FILE and STANDARD-ERROR-FILE, of the job with the Job (job-number) and the Agent (agent-host-name), exceed the limit (bytes) of the size of the receiving file.

The result file size exceeds the maximum.

(S)

Receives the result file up to the maximum reception size.

(O)

Reduce the size of the result file. Then, if you need information on the standard output file or standard error output file, re-execute the job.

Reduce the size of the result file (standard output file or standard error output file) specified for the job so it is smaller than the maximum file size (the value set in LimitReceiveFileSize environment setting parameter). Alternatively, recheck the maximum file size.

KAVU4297-W

The result files (standard-output-file, standard-error-output-file) of the job (job-number, agent-host-name) are being analyzed.

This message appears when a means of preventing duplicated reception of the job result file is set.

A job end notification from the agent host cannot be accepted because a result file (standard output file or standard error output file) is being analyzed on the manager host. Since the job end notification from the agent host will be accepted when the analysis of the result file finishes, detection of the job end will be delayed. The agent host outputs the message KAVU3221-E.

For details on how to prevent duplicated reception of the job result file, see 6.2.6 Preventing duplicated reception of job result files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1(for hosts under Windows), or 15.2.6 Preventing duplicated reception of job result files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under UNIX).

(S)

Aborts the job end notification.

(O)

Transferring a large result file containing more than one megabyte causes an unsuccessful request or may require a long time. If you do not need to reference the details about execution results and want to suppress unnecessary file output, specify a NULL device name for standard-output-file-name or standard-error-output-file-name in the job definition. In UNIX, assign /dev/null. In Windows, assign NUL. In particular, enter /dev/null for a job that runs in UNIX and enter NUL for a job that runs in Windows. If a file name is specified, redirect the standard output within the script file or batch file for the job. If the data append option is specified for standard output data or standard error output data, disable this option or delete and save the standard output data file or standard error output data file on a regular basis.

KAVU4299-I

The job at the agent (agent-name) was forcibly terminated.

The running job was forcibly terminated.

(S)

Cancels the requested processing.

KAVU4300-E

Failed to confirm the execution of event job at agent (agent-host-name). (reason code: reason-code)

A request to confirm the existence of the event jobs being executed at the agent failed.

(S)

Stops the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU4301-E

The alteration of agent (agent-host-name) cannot be noticed to the Event Action Manager. (reason code: reason-code)

Changes of the agent could not be reported to the Event Action Control Manager.

(S)

Stops the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU4302-E

Confirming the execution of event job at the agent (agent-host-name) was failed because the Event Action Manager is not started.

The requested processing failed because the Event Action Control Manager process has not been started or has not been running.

(S)

Stops the requested processing.

(O)

Check the activation status of the Event Action Control Manager, and then call the function again.

KAVU4303-E

Confirming the execution of event job at the agent (agent-host-name) was timed out.

The event jobs being executed at the Event Action Control Manager could not be confirmed due to a timeout.

(S)

Stops the requested processing.

(O)

Check the execution status of the Event Action Control Manager, and then call the function again.

KAVU4304-E

Confirming the execution of event job at the agent (agent-host-name) was failed because the Event Action Manager is processing other request.

The execution of the event job cannot be confirmed because the Event Action Control Manager process is currently processing another request for adding or deleting agents.

(S)

Stops the requested processing.

(O)

Wait for a while, and then call the function again.

KAVU4305-E

The alteration of the agent (agent-host-name) cannot be noticed because the Event Action Manager is not started.

The requested processing failed because the Event Action Control Manager process has not been started or has not been running.

(S)

Stops the requested processing.

(O)

Check the activation status of the Event Action Control Manager, and then call the function again.

KAVU4306-E

The alteration of the agent (agent-host-name) cannot be noticed because the Event Action Manager is processing other request.

The requested processing failed because the Event Action Control Manager process has not been started or has not been running.

(S)

Stops the requested processing.

(O)

Check the activation status of the Event Action Control Manager, and then call the function again.

KAVU4307-E

Completion of the alteration of the agent (agent-host-name) cannot be noticed to the Event Action Manager. (reason code: reason-code)

The completion of the alteration of the agent could not be reported to the process of the Event Action Control Manager.

(S)

Modifies the agent definitions.

(O)

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

KAVU4308-I

Job information delete process started. (host name: logical-host-name)

The system has started the job information deletion process.

If you execute jobs concurrently with the deletion of job information, job execution performance may degrade. If the time for deleting job information is a concern during job operation, you can estimate the required deletion time by checking the time when this message was output and the number of job information items to be deleted.

This message is not output when the number of days for storing job information is set to 0. For details on job information deletion, see 7.1.8 Option for deleting job information asynchronously in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

(S)

Starts the job information deletion process.

KAVU4309-I

Job information is deleted. (host name: logical-host-name, the number of job information: number-of-deleted-items)

The job information deletion process has terminated.

If you execute jobs concurrently with the deletion of job information, job execution performance may degrade. If the time for deleting job information is a concern during job operation, you can estimate the required deletion time by checking the time when this message was output and the number of job information items to be deleted.

This message is not output when the number of days for storing job information is set to 0. For details on job information deletion, see 7.1.8 Option for deleting job information asynchronously in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

(S)

Terminates the job information deletion process.

KAVU4310-I

The number of executing jobs reaches the concurrently-executable-job-limit (maximum-number-of-concurrently-executable-jobs) at the agent (agent-host-name). (host name:host-name,job number:job-number)

The number of jobs being executed on the agent host has reached the concurrently-executable job limit.

(S)

Outputs this message when a job cannot be registered because the number of jobs being executed on the agent host has reached the concurrently-executable job limit. The system outputs this message if you have enabled the output of a confirmation message indicating that the number of jobs being executed has reached the limit.

(O)

If the number of jobs being executed on the agent host has reached the concurrently-executable job limit, the job that cannot be executed is queued until the jobs being executed terminate. If this message appears frequently, recheck the setting of the concurrently-executable job limit. Use any of the following commands to change the concurrently-executable job limit.

For a PC job, Unix job, action job, or custom job:

ajsagtalt command

For a QUEUE job or submit job:

jpqagtalt command

For details on the ajsagtalt command, see ajsagtalt in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

For details on the jpqagtalt command, see jpqagtalt in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

For details on the setting for outputting a confirmation message when the number of jobs being executed has reached the limit, see 6.2.13 Outputting a message that reports that the maximum number of concurrently executable jobs has been reached in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under Windows) or 15.2.13 Outputting a message that reports that the maximum number of concurrently executable jobs has been reached in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under UNIX).

KAVU4311-E

The specified value of a job number is out of range. Specify a job number in the range of 1 to 999999.

The value specified as a job number is outside the range of values that can be specified.

(S)

Cancels the request processing.

(O)

Specify a job number in the range from 1 to 999,999.

If the destination of the request is another system, check whether the specified manager host name is correct.

KAVU4312-E

A system call error occurred while initializing the database of the job execution environment. (system call name:system-call-name, module : reason-location[reason-location], reason code : reason-code)

During a cold start, a system call error occurred while the database in the job execution environment was being initialized.

(S)

Interrupts the initialization of the job execution environment database, and continues the startup processing.

(O)

Determine the cause of the error from the system call name and the reason code.

The reason code is a system error number. If you are still unable to determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU4331-E

The job execution environment database is currently undergoing maintenance. (host name:host-name)

The job execution environment is undergoing maintenance.

(S)

Cancels JP1/AJS3 service startup processing.

(O)

Check whether the jajs_maintain process is active, and if necessary, restart JP1/AJS3.

KAVU4335-E

The request sent from the host(source-IP-address) was ignored. (reason, host-name)

A request from the host (source-IP-address) was ignored. The probable causes are as follows.

When the reason is Restricted:

The IP address indicated in source-IP-address was not registered in the manager connection permission configuration file on the host on which this message was output.

When the reason is Error:

An error occurred during processing intended to obtain the connection source IP address.

For a physical host, JP1_DEFAULT is indicated in host-name.

If the source IP address could not be resolved, a null character string is output for source-IP-address.

(S)

Ignores the request and continues processing.

(O)

When the reason is Restricted:

If the request from the IP address indicated in source-IP-address must be accepted, perform the following:

Add the connection source IP address by editing the manager connection permission configuration file on the host on which this message was output.

Execute the jajs_pmtcon command to apply the changes you made in the connection permission configuration file.

If necessary, perform the request processing again.

When the reason is Error:

Follow the instructions given in the KAVS8033-E message that was output immediately before this message.

KAVU4500-W

The operating status (operating-status) does not allow the executing request (request-name). (host = manager-host-name, rec_IPaddress = IP-address-of-requesting-host, reason-location, reason-code)

The system cannot execute the request in the operating status.

(S)

Cancels the requested processing.

(O)

Check the following possible causes, and then reissue the request:

Check whether daemon operation has started.

Check whether the manager is running in reduced mode.

KAVU4501-W

The request (request-name) cannot be executed in the current job status (status). (host = manager-host-name, rec_IPaddress = IP-address-of-requesting-host, reason-location, reason-code)

The job cannot execute the request in the current status.

(S)

Cancels the requested processing.

(O)

Check the status of the job.

KAVU4502-W

The user (user-name) lacks permission for that job (job-number).

The user does not have permission for the job.

(S)

Cancels the requested processing.

(O)

Check the access permission of the user who issued the request, and the owner name of the job. Then, reissue the request.

KAVU4503-E

Agent host (agent-host-name) was failed to create automatically. (scheduler-service-name)

An unsuccessful attempt was made to create the agent automatically.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then re-execute the job.

KAVU4504-W

A pipe timeout error occurred in a job execution process at the agent(agent-host-name).

A timeout occurred during pipe communication in a job execution process.

(S)

Cancels the requested processing.

(O)

A cause may be one of the following:

Too many jobs are executed at once.

The CPU is heavily loaded.

The agent process for job execution control was swapped out for more than 300 seconds and not executed due to insufficient real memory.

If one of these causes persists and a timeout error frequently occurs during pipe communication, we recommend that you specify a timeout period longer for pipe communication on the host where the agent process is executed.

In case of Cause No. 3, check the memory usage for the entire system and increase the memory or suppress the startup of unnecessary processes to gain sufficient real memory.

For details on how to change a timeout value for pipe communication, see 15.2.15 Changing the timeout value for pipe communication of the agent in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

If the error persists even after changing the timeout value, use the data collection tool to collect data, and then contact the system administrator.

KAVU4505-W

The job execution environment database could not be initialized. Initialization is canceled.

The job execution environment database could not be initialized during a cold start.

(S)

Performs the normal-start process.

(O)

Check the following:

Check whether the available space on the disk containing the work directory is insufficient for executing the manager process in the job execution environment.

Check whether memory is insufficient.

Check whether any process is accessing a database file in the job execution environment (in Windows).

If this message is output, the job execution environment database has not been initialized.

If you want to initialize the database, correct the above causes and then restart JP1/AJS3.

In some cases, the integrated trace might contain the KAVU4312-E, KAVU5311-E, or KAVU7238-E message. Check them altogether.

KAVU4509-E

The specified agent (agent-host-name) cannot be released because some job is being executed.

The agent could not be disconnected because there are jobs being executed.

(S)

Cancels the requested processing.

(O)

Wait until the jobs terminate, and then call the function again.

KAVU4510-W

The specified job (job-number) does not exist.

The specified job does not exist.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4511-W

The specified agent (agent-host-name) does not exist.

The specified agent does not exist.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4512-W

The specified queue (queue-name) does not exist.

The specified queue does not exist.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4513-W

The specified exclusive execution resource (exclusive-execution-resource-name) does not exist.

The specified exclusive execution resource does not exist.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4514-W

The job cannot be registered because the entrance to queue (queue-name) is closed.

The job cannot be registered because the entrance of the queue is closed.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4515-W

The job cannot be registered because the queue (queue-name) reached the maximum number of jobs (maximum-number).

The job cannot be registered because the number of jobs registered in the queue has reached the maximum number of jobs allowed in the queue.

(S)

Cancels the requested processing.

(O)

Either wait for an executing job to end before issuing another request, or check the queue definition information and adjust the maximum number of jobs allowed in the queue.

To check the number of jobs registered in the queue, which is the sum of the QUEUING and EXECUTING values, use the -q or -ah option in the jpqqueshow command. Also, to change the maximum number of jobs allowed in the queue, you can use the jpqquealt command. For details about these commands, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU4516-W

The queue (queue-name) reached warning number of jobs (warning-number).

The number of jobs in the queue reached the warning level.

(S)

Continues processing the request.

KAVU4518-W

Information (agent-ID) about the agent connected to the queue (queue-name) is missing.

The database does not contain the information about the agent connected to the queue.

(S)

Stops the daemon.

(O)

Check the contents in the database, and then restart.

KAVU4519-E

Some event job is being executed at specified agent (agent-host-name).

The requested processing failed because some event jobs were being executed in agent-host-name.

(S)

Cancels the requested processing.

(O)

Stops the event jobs, and then call the function again.

KAVU4520-W

The job cannot be registered because the system already reached the maximum number of jobs (maximum-number), as stipulated in environment setting (logical-host-name).

The job cannot be registered. The probable causes are:

The job cannot be registered because the number of jobs registered in the queue has reached the maximum number of jobs allowed in the system as defined in the environment settings.

The job cannot be registered because the number of jobs registered in the database for QUEUE jobs and submit jobs has reached the maximum number of jobs.

(S)

Cancels the requested processing.

(O)

Take one of the following actions according to the cause of the error, and then reissue the request:

Either wait for an executing job to end and then issue another request, or review the value for the maximum number of jobs allowed in the system defined in the environment settings for the job execution environment. For the definition of the maximum number of jobs allowed in the system, see the values that can be specified the MaximumContentJob environment setting parameter.

In the standard configuration, the number of jobs that can be registered in the database for QUEUE jobs and submit jobs is less than 200,000.

Information about the execution results of jobs is registered in the database. The total number of jobs in the database is the number of jobs for the days that job information is stored, plus the number of jobs for one day. For example, if the number of jobs executed per day is 10,000 and the number of days that jobs are stored is 10 days, a total of 110,000 jobs will be registered.

Adjust the number of days that job information is stored so that the number of job execution-result information items to be registered in the database is less than 200,000. When you define the number of days that job information is stored, refer to the value set in the PreserveTerm environment setting parameter. For details about the PreserveTerm environment variable parameter, see 2.3.2(4) PreserveTerm in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVU4521-W

The agent cannot be registered because the system already reached the number of definitions (number-of-definitions) stipulated in environment setting (logical-host-name).

No more agents can be registered because the number of registered agents reached the maximum defined in the environment settings.

(S)

Cancels the requested processing.

(O)

Delete unnecessary agents, or review the number of definitions defined in the environment settings.

KAVU4522-W

The queue cannot be registered because the system already reached the number of definitions (number-of-definitions) stipulated in environment setting (logical-host-name).

No more queues can be registered because the number of queues reached the maximum defined in the environment settings.

(S)

Cancels the requested processing.

(O)

Check the number of queues defined in the environment settings.

KAVU4523-W

The exclusive execution resource could not be registered because the system already reached the number of definitions (number-of-definitions) stipulated in environment setting (logical-host-name).

No more exclusive execution resources can be registered because the number of registered exclusive execution resources reached the maximum defined in the environment settings.

(S)

Cancels the requested processing.

(O)

Check the number of exclusive execution resources defined in the environment settings.

KAVU4524-W

The registered jobs exceed the warning number for the system (warning-number), as stipulated in environment setting (logical-host-name).

The number of jobs in the queue reached the warning level defined in the environment settings.

(S)

Continues processing the request.

KAVU4525-W

The agent cannot be registered because the system already reached the maximum number of execution jobs (maximum-number) stipulated in environment setting (logical-host-name).

No more agents can be registered because the maximum number of jobs to be executed is reached.

(S)

Cancels the requested processing.

(O)

Check the number of jobs defined in the environment settings.

KAVU4526-I

The system recovered from the number of warning statuses, as stipulated in environment setting (manager-host-name).

The system recovered from the warning status because the number of jobs dropped below the number of warning jobs in the environment setting.

(S)

Continues processing.

KAVU4527-E

A logical contradiction occurred during the JP1 assume user check (logical-host-name). (reason module: error-location [error-location], reason code: reason-code)

The assumed JP1 user function had a logical contradiction.

(S)

Cancels the requested processing.

(O)

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

KAVU4528-E

Cannot set assume user (user-name) because this user is not found.

The user indicated by user-name has not been registered as a JP1 user. The system could not assume it as a JP1 user.

(S)

Cancels the requested processing.

(O)

Register the user indicated by user-name as a JP1 user.

Alternatively, use the jpqregguestuser command to register the assumed JP1 user correctly, and then restart the JP1/AJS3 service.

KAVU4529-I

The information was recovered because the request for (request-destination) was rejected. (reason code : reason-code)

The information was returned to the status in effect before the request was executed because the request to the request destination was canceled due to some unspecified reason. The request destination is a queue name, agent name, or exclusive execution resource name.

(S)

Continues processing.

KAVU4530-W

The agent (agent-host-name) might have stopped, or an obstacle might have occurred.

The agent might have stopped or an error might have occurred in the agent.

(S)

Cancels the requested processing.

(O)

Check whether any of the following probable causes are present:

The agent is not running.

The port numbers for service name jp1ajs2qagt on the manager and the agent are inconsistent.

There is a problem with the network, including the hardware, on either the manager or agent, or both.

Check the integrated trace log of the manager for whether a KAVUxxxx message was output before or after this message. Also check whether a KAVUxxxx message was output to the integrated trace log of the agent when this message was output. If a KAVUxxxx message was output, read the message explanation.

KAVU4531-W

The agent (agent-host-name) host name might be invalid.

The network must be set up correctly so that the IP address can be determined from the specified host name by using the hosts file or the DNS server.

(S)

Cancels the requested processing.

(O)

Make sure that TCP/IP communication is available under the specified agent host name.

KAVU4532-W

The client (client-host-name) might have stopped, or an obstacle might have occurred.

The client might have stopped or an error might have occurred in the client.

(S)

Cancels the requested processing.

(O)

Make sure that the client application is started, TCP/IP communication is available under the client host name and port number is valid.

KAVU4533-W

The client (client-host-name) host name might be invalid.

The network must be set up so that the IP address can be determined from the specified host name by using the hosts file or the DNS server.

(S)

Cancels the requested processing.

(O)

Make sure that TCP/IP communication is available under the client host name.

KAVU4534-W

No response was received from the agent (agent-host-name), so the status of job (job-number) was changed to recovered (status).

A request to check the status of, or forcibly terminate, a job was issued to the agent host, but no response was returned from the agent host.

(S)

Cancels the requested processing and changes the job to the status indicated in status.

(O)

A communication error may have occurred. Use the integrated trace logs for the manager host and agent host to check whether a KAVUxxxx or KNACxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no such messages were output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4535-I

The agent (agent-host-name) operating status was changed to recovered.

An operation recovery (recovery from an error or stopped status) was detected during monitoring of the execution host. When an operation recovery for the execution host is detected, the system resumes registering jobs for execution in the execution host. For details on monitoring the target host, see 5.4.8(2) Monitoring execution hosts (agents) in the manual Job Management Partner 1/Automatic Job Management System 3 Overview.

(S)

Continues processing.

KAVU4536-W

The transfer file could not be accessed. (reason-code)

The system failed to access the file to be transferred.

(S)

Cancels the requested processing.

(O)

The following describes probable causes for reason codes, and suggests corrective actions. Note that the transfer file refers to the transfer source file applicable to job registration or the applicable result file when a job end notification is received.

Reason code = 0xE002110D

Cause

An attempt was made to transfer a transfer file, but there was no source file for the transfer.

Corrective action

Make sure that there is a source file for the transfer.

Reason code = 0xE002110E

Cause

There are no access permissions on the transfer file.

Corrective action

Make sure that the transfer file has access permissions.

Reason code = 0xE0021110

Cause

The transfer file is being used by another process.

Corrective action

Check whether another process is using the transfer file.

Check whether another job is using the same transfer source file or the same result file.

Reason code = 0xE0021111

Cause

An attempt to create (open) a transfer file has failed.

Corrective action

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

Reason code = 0xE0021112

Cause

An attempt to read a transfer file has failed.

Corrective action

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

If any other reason code has been output, use the data collection tool to collect data, and then contact the system administrator.

KAVU4537-W

Job information is removed because inappropriate job information was detected in the database. (job number=job-number, job name=job-name, file name=execution-file-name, submitted time=date/time-of-registration, start time=date/time-to-start-execution, end time=date/time-to-end-execution)

The job was deleted because the job data is corrupted.

(S)

An inconsistency occurred in the database since the JP1/AJS3 process terminated while registering a job or deleting job data.

Delete the job data and returns the database to the normal status. Then, continues processing.

KAVU4538-W

The status of job (job-number) missed at the agent (agent-host-name) was changed to recovered (status).

A request to check the status of, or forcibly terminate, a job was issued to the agent host, but the specified job did not exist on the agent host.

(S)

Cancels the requested processing and changes the job to the status indicated in status.

(O)

The probable causes are:

The JP1/AJS3 service on the agent host stopped while a job end notification from the agent host failed.

The JP1/AJS3 service terminated abnormally while the job was running on the agent host.

A communication error may have occurred. Use the integrated trace logs for the manager host and agent host to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4539-W

No agent can execute the job (job-number).

No agent can execute the job.

(S)

If no agent can execute the jog after the waiting time for the job execution expires, change the status of the job.

(O)

The action to be taken differs depending on the type of the job.

For a PC job, Unix job, action job, or custom job:

Check whether the JP1/AJS service is running on the execution host defined for the execution agent.

For a QUEUE job or submit job:

Check whether the JP1/AJS service is running on the agent that is connected to the queue.

KAVU4540-I

The manager (manager-host-name) started planned termination.

The manager process for job execution control started planned termination.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU4541-I

The manager (manager-host-name) started forced termination.

The manager process for job execution control started forced termination.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU4542-I

The manager (manager-host-name) is monitoring queuing job termination.

The manager process for job execution control monitors the end of a queued job.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU4543-I

The manager (manager-host-name) is monitoring executing job termination.

The manager process for job execution control monitors the end of a running job.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU4545-I

The cold start processing will start in the manager (manager-host-name).

Cold start processing will start on the manager.

(S)

Continues processing.

KAVU4546-W

The PATH variable could not be acquired at the agent (agent-host-name).

The PATH environment variable for the user that attempted to log in to the OS could not be acquired at the agent.

(S)

Cancels the requested processing.

(O)

Check the following:

Check whether there is sufficient free space in the disk.

Check whether the login script for the user that attempted to log in to the OS has any conditions that cause processing to abort.

If the login script has any coding unnecessary for job execution by JP1/AJS3, delete that portion or use the JP1JobID environment variable to skip the portion.

KAVU4547-W

You are not authorized to access the temporary file at the agent (agent-host-name).

You do not have access permission for the following files or directories:

Work directory used for executing the agent process, or files in the work directory

System file directory or files in the system file directory

(S)

Cancels the requested processing.

(O)

Probable causes are listed below. Check the status of the agent host.

A privilege to the system file directory (the default is /var/opt/jp1ajs2/sys) has been changed.

A privilege to the work directory (the default is /var/opt/jp1ajs2/tmp) used for executing the agent process has been changed.

A privilege to the jpqagtlock file or the temporary work file in the system file directory has been changed.

Another program is accessing the above directories or the temporary work file.

If a privilege to the file or the directory has been changed, give the write and read permissions to the OS user that executes jobs. The temporary work file (the file that begins with A_JPQ) may remain in the work directory used for executing the agent process even if the job terminates. If this is the case even after JP1/AJS3 stops, delete the temporary work file.

KAVU4548-W

The temporary file at the agent (agent-host-name) cannot be accessed.

You could not access the following work directories or files:

Work directory used for executing the agent process, or files in the work directory

System file directory or files in the system file directory

(S)

Cancels the requested processing.

(O)

Examine a cause that may be one of the following at the agent host and check the status of the agent host:

The system file directory (the default is /var/opt/jp1ajs2/sys) has been deleted.

The work directory (the default is /var/opt/jp1ajs2/tmp) used for executing the agent process has been deleted.

The jpqagtlock file or the temporary work file has been deleted from the system file directory.

Another program is accessing the above directories or the temporary work file.

The home directory specified in /etc/passwd for the mapped OS user does not exist.

Write permission has not been set for the work directory used for executing the agent process (default work directory: /var/opt/jp1ajs2/tmp).

If the jpqagtlock file or any of the directories indicated above have been deleted, re-install JP1/AJS3.

If the work directory used for executing the agent process exists, check whether write permission is set for the directory. If write permission is not set, set write permission for the directory or change the work directory to a directory for which write permission has been set.

The temporary work file (the file that begins with A_JPQ) might remain in the work directory used for executing the agent process even if the job terminates normally. If this is the case even after JP1/AJS3 stops, delete the temporary work file.

KAVU4549-W

The process has too many open files at the agent (agent-host-name).

The number of opened files reached the maximum set by the kernel parameter at the agent.

(S)

Cancels the requested processing.

(O)

Use the kernel parameter at the agent to increase the maximum number of files that can be opened. For details on how to estimate the value to be set in the kernel parameter, see Release Notes.

KAVU4550-W

The execution file (file-name) is missing at the agent (agent-host-name).

The agent does not contain the executable file.

(S)

Cancels the requested processing.

(O)

Check whether any of the following probable causes are present:

The relative path to the executable file has been specified, but the folder or directory necessary for execution has not been set in the PATH environment variable on the agent host.

The specified executable file is on a network drive.

The agent host runs in a WOW64 environment, and an executable file in %systemroot%\system32 has been specified.

If this message is output after execution of an action job, the platform set in the detailed definition of the action job is incorrect.

The specified executable file was not found on the agent host when the job was executed.

Take one of the following actions according to the cause of the error, and then reissue the request.

Make sure that the folder or directory necessary for the PATH environment variable on the agent host has been set correctly.

Do not specify the path beginning with a network drive name. Instead, specify the path beginning with a computer name (for example, \\computer-name\shared-folder\executable-file-name).

In a WOW64 environment, if a file in %systemroot%\system32 is specified, file access is redirected to %systemroot%\syswow64. Take either of the following corrective actions:

- In Windows Server 2012 or the 64-bit version of Windows Server 2008, specify %systemroot%\sysnative instead of %systemroot%\system32, and then re-execute the job.

- In Windows Server 2003 (x64), when you execute a job in a WOW64 environment, disable file system redirection, and then re-execute the job.

For details about how to execute a job in a WOW64 environment, see 6.6.2 Disabling file system redirection when jobs are executed in a WOW64 environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Recheck the detailed definition of the action job, and then re-execute the action job.

Make sure that the executable file is on the agent host, and then re-execute the job. Also, make sure that an operation that moves or deletes the executable file is not performed.

KAVU4551-W

You are not authorized to access the execution file (file-name) at the agent (agent-host-name).

You are not authorized to access the executable file at the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4552-W

The environment file (file-name) is missing at the agent (agent-host-name).

The agent does not contain the environment variable file.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4553-W

You lack access permission for the environment file (file-name) at the agent (agent-host-name).

You do not have permission for the environment variable file at the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4554-W

The environment file (file-name) at the agent (agent-host-name) cannot be opened.

The system cannot open the environment variable file at the agent.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the environment variable file name.

KAVU4555-W

The environment file (file-name) at the agent (agent-host-name) cannot be accessed.

The system failed to access the environment variable file at the agent.

(S)

Cancels the requested processing.

(O)

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

KAVU4556-W

The standard input file (file-name) is missing at the agent (agent-host-name).

The agent does not contain the standard input file.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4557-W

You lack access permission for the standard input file (file-name) at the agent (agent-host-name).

You do not have permission to access the standard input file at the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4558-W

The standard input file (file-name) at the agent (agent-host-name) cannot be opened.

The system cannot open the standard input file at the agent.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the standard input file name.

KAVU4559-W

The standard input file (file-name) at the agent (agent-host-name) cannot be accessed.

The system failed to access the standard input file at the agent.

(S)

Cancels the requested processing.

(O)

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

KAVU4560-W

You lack access permission for the standard output file (file-name) at the agent (agent-host-name).

You do not have permission to access the standard output file at the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4561-W

The standard output file (file-name) at the agent (agent-host-name) cannot be opened.

The system cannot open the standard output file at the agent.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the standard output file name.

KAVU4562-W

The standard output file (file-name) at the agent (agent-host-name) cannot be accessed.

The system failed to access the standard output file at the agent.

(S)

Cancels the requested processing.

(O)

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

KAVU4563-W

You lack access permission for the standard error output file (file-name) at the agent (agent-host-name).

You do not have permission to access the standard error output file at the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4564-W

The standard error output file (file-name) at the agent (agent-host-name) cannot be opened.

The system cannot open the standard error output file at the agent.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the standard error output file name.

KAVU4565-W

The standard error output file (file-name) at the agent (agent-host-name) cannot be accessed.

The system failed to access the standard error output file at the agent.

(S)

Cancels the requested processing.

(O)

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

KAVU4566-W

The work path name is too long at the agent (agent-host-name), so the file cannot be created.

The system cannot create the file because the work path name at the agent is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4567-W

There is no work path at the agent (agent-host-name).

The agent does not have a work path.

(S)

Cancels the requested processing.

(O)

The directory specified in the WorkPath environment setting parameter for the work directory name for execution of the agent process for job execution control may not exist.

Remove the cause of the error, and then reissue the request.

KAVU4568-W

You lack access permission for the work path at the agent (agent-host-name).

You do not have permission to access the work path of the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4569-W

The file path (path-name) variable at the agent (agent-host-name) could not be resolved.

The system failed to resolve the file path at the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4570-W

The parameter (parameter-name) variable at the agent (agent-host-name) could not be resolved.

The system failed to resolve the parameter at the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4571-W

The user mapping (JP1-user-name) at the agent (agent-host-name) failed.

User mapping failed at the agent.

(S)

Cancels the requested processing.

(O)

Check whether any of the following probable causes are present. Also check the integrated trace log for the agent to which a message indicating error details may have been output.

In the agent host, the manager host name specified for the server host name for the JP1 user is invalid.

The default queue setting for the agent contains multiple agents to be connected. Because the priority setting contains an error or because an incorrect agent is connected, the job was executed on an unexpected agent.

The user mapping definition for the agent host does not contain the JP1 user.

The user mapping definition for the agent host contains an OS user that does not exist.

The user mapping definition for the agent host contains an OS user with an invalid password (Windows only).

A JP1 user with the same name as that of the OS user who executed the ajsentry command does not exist.

The OS user specified in the detailed job definition is not mapped to the JP1 user.

The JP1 user for the owner differs from the JP1 user who registered the job for execution.

Memory was insufficient.

The execution agent group setting contains multiple associated execution agents. Because the priority setting contains an error or because an incorrect execution agent is associated, the job was executed on an unexpected agent.

In the detailed definition of the job, User who owns is specified for Executed by and the Owner text box is blank. At the same time, an OS user whose name has not been registered as a JP1 user is set for the JP1/AJS3 service startup account on the manager host.

Take one of the following actions according to the cause of the error, and then reissue the request:

Set the correct manager host name for the JP1 user.

Execute the jpqagtlink command to change the priority of agents, or execute the jpqagtunlink command to release the connection between the default queue of the agents and the unexpected agent.

In the user mapping definition for the agent host that executes the job, register the JP1 user indicated in JP1-user-name in the message, and then map the JP1 user to the OS user.

In the user mapping definition for the agent host that executes the job, register an existing OS user.

Execute the jbsumappass command to re-set the password of the OS user. For password, specify the OS user password (Windows only).

Do either of the following, and then re-execute the ajsentry command:

- Add a JP1 user with the same name as that of the OS user, and map the JP1 user to the OS user.

- Specify the owner as the job execution user in the job definition.

Check the OS user specified in the detailed job definition. Map the OS user to the JP1 user on the agent where the job is to be executed.

Determine whether the owner or the JP1 user who registered the job for execution registers the job for execution, and then set the execution-user type correctly.

Check the memory status and then re-estimate memory requirements.

Execute the ajsagtalt command to change the priority, or exclude the association between the execution agent group and the unexpected execution agent.

In the user mapping definition, register the JP1 user indicated in JP1-user-name in the message. Alternatively, in Windows, set the OS user who has the user name registered for the JP1 user for the JP1/AJS3 service startup account on the manager host.

For details on how to set up user mapping, see 3. Setup in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under Windows) or 13. Setup in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under UNIX).

For details on the JP1/AJS3 commands, see 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1 or 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

For details about the JP1/Base commands, see the Job Management Partner 1/Base User's Guide.

KAVU4572-W

The user (user-name) could not be masked at the agent (agent-host-name).

The system failed to mask the user at the agent.

(S)

Cancels the requested processing.

(O)

Check the user mapping definition, and then reissue the request.

KAVU4573-W

The job priority at the agent (agent-host-name) could not be changed.

The system failed to change the job priority at the agent.

(S)

Cancels the requested processing.

(O)

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

KAVU4574-W

An error occurred when a job process was generated at the agent (agent-host-name).

An error occurred while the system was generating a job process at the agent.

(S)

Cancels the requested processing.

(O)

In Windows, check whether account permissions for the agent host are set correctly. For details on how to set account permissions, see the explanation about how to give user rights to an OS user in an Active Directory environment in Before setting user mapping in the Job Management Partner 1/Base User's Guide.

To change the JP1/AJS3 service startup account from the system account to the user account, you also need permission for replacing a process level token.

For details on the permission necessary when the service account is set to the user account, see 4.2.3(1)(c) When multiple scheduler services are activated and you want to avoid desktop heap shortages in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

For other cases, use the data collection tool to collect data, and then contact the system administrator.

KAVU4575-W

An error occurred when a job process was started at the agent (agent-host-name).

An error occurred while the system was starting a job process at the agent.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log of the agent to remove the cause of the error, and then reissue the request.

KAVU4576-W

The standard error file or standard error output file could not be sent at the agent (agent-host-name).

The system failed to transfer the standard output file or standard error output file at the agent.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then reissue the request.

KAVU4578-W

Execution file (file-name) could not be accessed at the agent (agent-host-name).

The system failed to access the executable file at the agent.

(S)

Cancels the requested processing.

(O)

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

KAVU4580-W

The user (user-name) does not have administrator permission at the agent (agent-host-name).

If you specify the execution priority of the Unix job to 4 or 5, the user that attempts to log in to the OS must have superuser privileges.

(S)

Cancels the requested processing.

(O)

Reissue the request as a user who has superuser privileges.

KAVU4581-W

The execution file (file-name) at the agent (agent-host-name) is not an executable file.

The file you attempted to execute at the agent is not an executable file.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4582-W

The execution file (file-name) cannot be merged with the command statement at the agent (agent-host-name).

The execution file of the agent cannot be merged with the command statement.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4583-W

The execution shell is missing at the agent (agent-host-name).

The shell being used to execute the job is missing at the agent.

(S)

Cancels the requested processing.

(O)

Check the shell being used to execute the job.

Also check whether the login shell specified in /etc/passwd for the mapped OS user exists.

KAVU4584-W

The agent (agent-host-name) does not have permission for changing owner of the file.

You do not have permission to change the owner of the file using the agent.

(S)

Cancels the requested processing.

(O)

Check the contents of the message KAVU3592-W that is output to the integrated trace log of the agent, and then change the access permission for the file and its directory, or change the directory.

KAVU4585-W

No path is specified to the destination for storing transfer files at the agent (agent-host-name).

The path to store transfer files is missing at the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4586-W

You are not authorized to access the path to the destination for storing transfer files or the files at the agent (agent-host-name).

You do not have access permission for transfer files of the agent or the path to store them.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4587-W

The agent (agent-host-name) transfer files cannot be opened.

The transfer file of the agent cannot be opened.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the transfer file name.

KAVU4588-W

Another process is using the agent (agent-host-name) transfer files.

Another process is using the transfer file of the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4589-W

The transfer files could not be accessed at the agent (agent-host-name).

The transfer file could not be accessed at the agent.

(S)

Cancels the requested processing.

(O)

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

KAVU4590-W

The job format is unacceptable at the agent (agent-host-name).

A job execution request was issued to the agent host, but the request was rejected due to an invalid parameter.

(S)

Cancels the requested processing to execute the job.

(O)

Use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4591-W

The agent (agent-host-name) job execution environment is invalid.

A job execution request was issued to the agent host, but the request was rejected due to an invalid execution environment on the agent host. The probable causes are:

You do not have permission to execute the specified executable file.

For a JP1/Script job, the JP1/Script version is not supported or the format of the JP1/Script executable file is not used.

The manager host name could not be converted to an IP address.

Shared memory was insufficient on the agent host.

The agent process has failed to initialize the log.

(S)

Cancels the requested processing to execute the job.

(O)

Use the integrated trace log on the agent host to check the cause of the error. Correct the cause of the error, and then reissue the request. If you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4593-W

An executable the agent does not exist.

A job execution request was issued to the agent host, but an executable agent host was not found.

(S)

Cancels the requested processing to execute the job.

(O)

Check whether any of the following probable causes are present:

The agent host or the JP1/AJS3 service on the agent host has stopped.

The agent host name has not been resolved on the manager.

The network, including hardware, has a problem.

The port number is not set correctly between the manager and the agent.

Take one of the following actions according to the cause of the error, and then reissue the request.

Restart the agent host or JP1/AJS3 service.

Define the agent host name in the hosts file for the manager.

Recheck the settings of the network, including hardware.

Recheck the port number.

Use the integrated trace logs for the manager host and agent host to check whether a KAVUxxxx or KNACxxxx message was output before or after this message. If it was output, also see the explanation provided in that message.

If you still cannot determine the cause after checking the above items, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4594-W

The job execution was canceled.

The system canceled executing the job.

(S)

Terminates the requested processing.

KAVU4596-W

No response was received from the agent (agent-host-name), so the job was forcibly terminated.

A request to check the status of, or forcibly terminate, a job was issued to the agent host, but no response was returned from the agent host.

(S)

Cancels the requested processing and changes the job to the Killed status.

(O)

A communication error may have occurred. Use the integrated trace logs for the manager host and agent host to check whether a KAVUxxxx or KNACxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no such messages were output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4597-W

A missed job at the agent (agent-host-name) was forcibly terminated.

A request to check the status of, or forcibly terminate, a job was issued to the agent host, but the specified job did not exist on the agent host.

(S)

Cancels the requested processing and changes the job to the Killed status.

(O)

The probable causes are:

The JP1/AJS3 service on the agent host stopped after a job end notification from the agent host failed.

The JP1/AJS3 service terminated abnormally while the job was running on the agent host.

Use the integrated trace logs for the manager host and agent host to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4598-W

The work path (path-name) at the agent (agent-host-name) is not a full path.

The work path must be specified with an absolute path name.

(S)

Cancels the requested processing.

(O)

Check the work path in the job definition.

KAVU4626-I

Assume from OS user (OS-user-name) to JP1 user (JP1-user-name).

JP1-user-name is assumed for the specified OS user that has not been registered as a JP1 user.

(S)

Continues processing.

KAVU4700-E

A system call error occurred in a job execution process at the agent (agent-host-name).

A system call error occurred during execution of the job on the agent.

(S)

Cancels the requested processing.

(O)

Check the integrated trace log for the agent to which a message indicating error details may have been output. If you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU4701-E

A logical contradiction occurred in a job execution process at the agent (agent-host-name).

A logical contradiction occurred during execution of the job on the agent host.

(S)

Cancels the requested processing.

(O)

Check whether a KAVUxxxx message was output to the integrated trace log for the agent host. If it was output, also see the explanation provided in that message. If you cannot determine the cause or if no such message was output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4702-E

Memory at the agent (agent-host-name) could not be allocated.

An attempt to acquire memory on the agent has failed.

(S)

Cancels the requested processing.

(O)

Check the memory requirements on the agent host, terminate any other unnecessary applications, and then reissue the request. If the same message reappears, re-estimate memory.

KAVU4703-E

The agent (agent-host-name) disk is full.

A job execution request was issued to the agent host, but the request was rejected due to insufficient space on the disk.

(S)

Cancels the requested processing to execute the job.

(O)

Free up space on the disk, and then reissue the request.

KAVU4704-E

No more process can be generated at the agent (agent-host-name).

The number of processes reached the maximum set in the kernel parameter for the agent.

(S)

Cancels the requested processing.

(O)

Increase the maximum number of processes set in the kernel parameter for the agent. Set a sufficient value, considering the number of concurrently executable job processes, in addition to the number of JP1/AJS3 processes.

For details on the JP1/AJS3 processes, see the description of how to check the status of processes in 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KAVU4717-E

An attempt by the agent (agent-host-name) to transmit the result file for the job (job-number) has failed. (reason code : reason-code)

An attempt to transfer a result file from the agent host to the manager host failed at the end of the job.

Although the job is placed in the Ended abnormally status with the return code -1, the job process itself may have terminated normally. Check the end status of the job process on the agent host.

(S)

Cancels the requested processing.

(O)

Check whether any of the following probable causes are present:

If the reason code is 0xe0021101, memory could not be allocated at the agent host when transferring a result file. The probable cause is that the result files (standard output file and standard error output file) are too large. See 7.8.1 Notes on the standard output file and standard error output file in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

If the size of the result files does not appear to be the problem, stop applications not in use and then retry. If the same message appears, review your memory estimates. If messages KAVU2220-E and KAVU3511-E are output at the agent host at about the same time as this message, see the message explanations.

If the reason code is 0xe0021127, transfer might have failed because the result file was too large. In this case, make sure that the result file for the job is not too large.

For other reason codes, use the integrated trace logs for the manager host and agent host to check the cause of the error, correct the cause of the error, and then retry.

If you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4718-E

An error occurred in the end processing of the job (job-number) at the agent (agent-host-name). (reason code : reason-code)

Termination processing failed after the job process terminated on the agent host.

(S)

Cancels the requested processing.

(O)

Although the job is placed in the Ended abnormally status with the return code -1, the job process itself may have terminated normally. Check the end status of the job process on the agent host.

If messages KAVU2220-E and KAVU3512-E are output at about the same time as this message, the probable cause is that memory could not be allocated because the result files (standard output file and standard error output file) are too large. For details about how to avoid memory shortages due to large result files, see 7.8.1 Notes on the standard output file and standard error output file in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

Use the integrated trace logs for the manager host and agent host to check the cause of the error, correct the cause of the error, and then retry.

If you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4721-E

The request was rejected. (job-number)

The request was rejected because the IP address of the connecting host was not registered in the agent connection permission configuration file on the destination host.

(S)

Continues processing.

(O)

Take action according to the instructions given by the KAVU3296-E message that was output to the integrated trace log of the host on which the job is to be executed.

KAVU5002-E

A command executed during reorganization of the job execution environment dataset ended abnormally.: Jischk l3 table-name: return code=return-code-of-Jischk Please look at maintenance-log-file-name)

While maintenance was being performed with the jajs_maintain command, invalid data was detected in the Jischk command, which verifies ISAM file consistency. For details of the error message output by Jischk, see the maintenance log file.

(S)

Cancels command execution. If there are unprocessed tables, the system continues command execution.

(O)

Correct the cause of the abnormal termination of maintenance processing by checking the maintenance log file, and then re-execute the maintenance processing.

For details on the maintenance log file, see the notes in jajs_maintain in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

For details on the Jischk command, see the Job Management Partner 1/Base User's Guide.

KAVU5003-E

A command executed during reorganization of the job execution environment dataset ended abnormally.: Jisext table-name file-name.back: return code=return-code-of-Jisext

While maintenance was being performed with the jajs_maintain command, an error occurred in the Jisext command, which extracts data from ISAM files.

(S)

Cancels command execution. If there are unprocessed tables, the system continues command execution.

(O)

Execute the command as a superuser or an administrator. If the error occurred in the script for automatic reorganization of the ISAM database, check whether the service is starting, there is a process that is using the file, or the disk has sufficient free space. Then, re-execute the command.

KAVU5004-E

A command executed during reorganization of the job execution environment dataset ended abnormally.: Jisconv -t SI table-name.back table-name_NEW: return code=return-code-of-Jisconv

While maintenance was being performed with the jajs_maintain command, an error occurred in the Jisconv command, which re-creates ISAM files from extracted data.

(S)

Cancels command execution. If there are unprocessed tables, the system continues command execution.

(O)

Execute the command as a superuser or an administrator. Check whether the disk has sufficient free space, and then re-execute the command. If you cannot determine the cause of the error, collect data and then contact the system administrator.

KAVU5005-E

A backup directory could not be created during reorganization of the job execution environment database. (directory-name): return code=return-code

While maintenance was being performed with the jajs_maintain command, a work directory could not be created.

(S)

Cancels command execution.

(O)

Check whether you have the permission to write into the directory for the temporary file for the job execution environment or the disk has sufficient free space.

KAVU5007-E

A file to back up or recover an ISAM file could not be copied during reorganization of the job execution environment database. (table-name): return code=return-code

While maintenance was being performed with the jajs_maintain command, a file to back up or recover an ISAM file could not be copied.

(S)

Cancels command execution. If there are unprocessed tables, the system continues command execution.

(O)

Check whether the disk has sufficient free space, and then re-execute the command.

KAVU5009-E

An attempt to rename files for recovering ISAM files during reorganization of the job execution environment database failed. (table-name) : return code=return-cod

While executing the script for automatically reorganizing the ISAM database of the job execution environment (jpqautocond) or while maintenance was being performed with the jajs_maintain command, the file could not be renamed to recover the ISAM file.

(S)

Cancels command execution. If there are any tables in the service still being unprocessed, the system continues command execution.

(O)

Check whether you have permission to write to the directory specified in the directory for the job execution environment database.

KAVU5012-E

The script to reorganize the job execution environment table (table-name) could not be started.: maintenance-information

While maintenance was being performed with the jajs_maintain command, the script to reorganize the table could not be started.

(S)

Cancels command execution. If, however, any tables remain unprocessed, the system continues command execution.

(O)

Memory may have become insufficient, or the number of processes started in the system may have reached the limit. If you cannot determine the cause, collect data and then contact the system administrator.

KAVU5013-E

The script to reorganize the job execution environment table (table-name) ended abnormally.: maintenance-information

While maintenance was being performed with the jajs_maintain command, the script to reorganize the table ended abnormally because of an unexpected error.

(S)

Cancels command execution. If, however, any tables remain unprocessed, the system continues command execution.

(O)

Execute Jischk -l3 table-name to check whether a problem has occurred with the table for which reorganization ended abnormally. In addition, collect data and then contact the system administrator.

KAVU5014-E

Preparations for job execution environment reorganization could not be made.: maintenance-information

While maintenance was being performed with the jajs_maintain command, preparations for table reorganization could not be made.

(S)

Cancels command execution.

(O)

System resources may be insufficient because of insufficient memory. If you cannot determine the cause, collect data and then contact the system administrator.

KAVU5015-I

Job execution environment maintenance ended normally.

The maintenance of the job execution environment ended normally.

(S)

Terminates maintenance of the job execution environment normally.

KAVU5016-E

Job execution environment maintenance ended abnormally.: maintenance-information

The maintenance of the job execution environment ended abnormally.

(S)

Terminates maintenance of the job execution environment abnormally.

(O)

See the maintenance log file, and investigate the cause of abnormal termination of maintenance. Then, perform maintenance again.

KAVU5100-E

The database construction is invalid. (module:reason-location[reason-location], reason code:reason-code)

The configuration is invalid. The probable cause is:

Installation or migration of JP1/AJS3 is not yet complete.

The value set for the DEFLENTYPE environment setting parameter does not match the format of the scheduler service database.

The value of the AJSCHARCODE environment setting parameter is invalid.

(S)

Cancels processing.

(O)

If installation or migration of JP1/AJS3 is not yet complete, re-install JP1/AJS3 or make sure that migration has been performed correctly.

If the value set for the DEFLENTYPE environment setting parameter does not match the format of the scheduler service database:

Check the value set for the DEFLENTYPE environment setting parameter.

- If byte is specified for the DEFLENTYPE environment setting parameter:

Execute the ajsembdbsetup command with the -del option specified to delete the database environment. Then execute the ajsembdbsetup command to set up the database environment again.

- If sjis is specified for the DEFLENTYPE environment setting parameter:

Execute the ajsembdbsetup command with the -del option specified to delete the database environment. Then execute the ajsembdbsetup command with the -e sjis option to set up the database environment again.

Note that if the database environment is deleted by executing the ajsembdbsetup command with the-del option specified, the unit definition defined in the scheduler service and information about execution results are also deleted. Before deleting the database environment, execute the ajsprint command to back up the definitions.

If the value of the AJSCHARCODE environment setting parameter is invalid:

If sjis is specified for the DEFLENTYPE environment setting parameter, you need to specify UTF-8 for the AJSCHARCODE environment setting parameter.

After specifying the above setting, retry the operation.

KAVU5200-E

The database version (version) is invalid.

The version of the job execution environment database is invalid.

(S)

Stops the JP1/AJS3 service.

(O)

Re-create the job execution environment database, and then restart the JP1/AJS3 service.

KAVU5280-E

Memory could not be allocated. (size:size, module:reason-location[reason-location], reason code:reason-code)

The system failed to allocate memory.

(S)

Cancels the requested processing.

(O)

Terminate any other unnecessary applications, and then reissue the request. If the same message reappears, re-estimate memory.

KAVU5281-E

Disk space is insufficient. (module:reason-location[reason-location], reason code:reason-code)

The amount of free space in the disk is insufficient.

(S)

Cancels the requested processing.

(O)

Increase the free space in the disk, and then reissue the request.

KAVU5282-W

A system call error occurred during a database process. (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred in a database process.

(S)

Cancels the requested processing.

(O)

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

If this message is output while JP1/AJS3 is running, check whether the database is running. If the database is not running, start the database and then restart JP1/AJS3.

KAVU5283-E

A logical contradiction occurred during a database process. (module:reason-location[reason-location], reason code:reason-code)

An invalid parameter was found in a database process for job execution control.

(S)

Cancels the database process for job execution control.

(O)

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

KAVU5284-E

It is short of the system resources. (reason-location)

The number of files opened in the system reached the maximum, or semaphores are insufficient.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the contents of the message KAVU5501-E.

If the number of files opened in the system reached the maximum, use the kernel parameter to increase the number of files that can open in the system. If semaphores are insufficient, increase the number of semaphores set in the kernel parameter.

For details on how to estimate the values to be set in the kernel parameters, see Release Notes.

KAVU5285-E

There is no the database table, or it is short of the system resources. (reason-location)

The database table does not exist or system resources are insufficient.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the contents of the KAVU5501-E message.

If the database table does not exist, check whether the database table exists in the directory specified in the DatabasePath environment setting parameter for job execution control. If the database table does not exist, you must re-create the database for job execution control.

If the database table exists, check the estimate of the kernel parameters. For details on how to estimate the values to be set in the kernel parameters, see Release Notes.

KAVU5286-E

A disk difficulty occurred. (reason-location)

An input or output error occurred on the disk.

(S)

Cancels the requested processing.

(O)

Check whether there is no problem on the disk volume itself.

KAVU5287-E

The database table is locked. (reason-location)

Another program locks the database table.

(S)

Cancels the requested processing.

(O)

This error may occur if one of the following was being executed when you attempted to execute the job:

The JP1/AJS3 data collection tool (for Windows only)

A command (except the jpqdbcond -L command) that uses an ISAM database such as verifying and condensing the ISAM database for JP1/Base or JP1/AJS3

A backup software

In addition to the above cases, this error may occur when you are running a program that opens a database file for the job execution environment in the monopoly mode or in a mode that only shares reading of files.

When you schedule the above operation, make sure that the operation will be performed at a different time from when jobs are executed

If you want to display the ratio of unused area in the ISAM file used for the job execution environment during operation of JP1/AJS3, execute the jpqdbcond command with the -L option.

KAVU5288-E

The database table (table-name) could not condense.

Reorganizing the database for the job execution environment has abnormally terminated.

(S)

Cancels the requested processing.

(O)

Also check the integrated trace log for the KAVU5501-E message.

Check the cause of the error, remove the cause, and then retry reconfiguring the ISAM file in the job execution environment.

KAVU5289-E

Not supported on related programs (product-name).

An attempt was made to use functions that are unsupported in the related programs.

(S)

Cancels the requested processing.

(O)

Check the supported version of a related program, and upgrade the version of the program.

KAVU5290-E

The database file size is larger than the limit, or memory could not be allocated. (reason location: reason-location [reason-location], reason number: reason-number)

The file size may have exceeded the limit or memory could not be allocated during database access.

(S)

Cancels the requested processing.

(O)

The possible causes are:

A file that is equal to or greater than 2 gigabytes, which is the limit on ISAM file size, exists in the job execution environment.

The ISAM file is in an invalid status.

Memory is insufficient.

If the cause of the error is 1, recheck the estimated number of days for job information storage and re-create the job execution environment database.

For details on the number of days for job information storage, see 2.3 Setting up the job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

For details on how to re-create a job execution environment database, see the explanation for creating a job execution environment in 2.3.3 Recovering the JP1/AJS3 - Manager setup information in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide

You can use the Jischk command to check for cause number 2. Use this command to check the status of the ISAM file. If the status is invalid, re-create the ISAM file. For details on how to check the status of the ISAM file and how to re-create the ISAM file, see 2.12 Troubleshooting problems related to invalid ISAM files in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

If the cause is number 3, terminate all unnecessary applications, and then reissue the request. If the same message reappears, recheck the memory estimate.

If the cause is none of the above, use the data collection tool to collect data, and then contact the system administrator.

KAVU5291-E

The database file size exceeded the limit. (reason location: reason-location [reason-location], reason number: reason-number)

The request was not processed because the size of the job execution environment database exceeded the limit for the size of ISAM files.

(S)

Cancels the requested processing.

(O)

The probable cause of the error is that a file equal to or greater than 2 gigabytes, which is the limit on ISAM file size, exists in the job execution environment.

Recheck the estimated number of days for job information storage and re-create the job execution environment database.

For details on the number of days for job information storage, see 2.3 Setting up the job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

For details on how to re-create a job execution environment database, see the explanation for creating a job execution environment in 2.3.3 Recovering the JP1/AJS3 - Manager setup information in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

KAVU5292-E

The specified tablespace or RDAREA does not exist. (module:reason-location[reason-location])

The table could not be created because the specified tablespace or RDAREA did not exist.

(S)

Cancels the requested processing.

(O)

Specify the correct tablespace or RDAREA, and then retry.

KAVU5293-E

The specified tablespace or RDAREA is invalid. (module : reason-location[reason-location])

The table could not be created because the specified tablespace or RDAREA was invalid.

(S)

Cancels the requested processing.

(O)

Specify the correct tablespace or RDAREA, and then retry.

KAVU5294-E

Could not connect to the database because the upper limit of a server setting was exceeded. (module:reason-location[reason-location])

The system could not connect to the database because the limit value defined on the database server was exceeded.

(S)

Cancels the requested processing.

(O)

Either stop other processes connected to the database or re-set the limit for the database, and then retry.

KAVU5295-E

Could not connect to the database because the username or password was invalid. (module:reason-location[reason-location])

Connection to the database was not possible because an invalid user name or password was used.

(S)

Cancels the requested processing.

(O)

Specify the correct user name and password, and then retry.

KAVU5296-E

Could not connect to the database. (module:reason-location[reason-location])

The system could not connect to the database.

(S)

Cancels the requested processing.

(O)

Check whether the database is running.

If this message is output while JP1/AJS3 is running, start the database and then restart JP1/AJS3

KAVU5309-E

A system call error occurred while checking the administrator permissions. (system call name:system-call-name,module:reason-location[reason-location],reason code:reason-code)

A system call error occurred when the jpqimport, jpqexport, or jpqdbcond command was used to check the administrator permissions.

(S)

Cancels the requested processing.

(O)

Determine the cause of the error from the system call name and the reason code.

The reason code is the value acquired by the GetLastError function of Win32API. If you cannot identify the cause of the error, use the data collection tool to collect data, and then contact the system administrator.

KAVU5310-E

Memory allocation failed while checking the administrator permissions. (size:size,module:reason-location[reason-location],reason code:reason-code)

Memory could not be secured when the jpqimport, jpqexport, or jpqdbcond command was used to check the administrator permissions.

(S)

Cancels the requested processing.

(O)

Stop unnecessary applications and issue another request.

If the same message is still output, review the memory estimate.

KAVU5311-E

A system call error occurred while initializing the database of the job execution environment. (system call name : system-call-name, module : reason-location[reason-location], reason code : reason-code)

During a cold start, a system call error occurred while the database in the job execution environment was being initialized.

(S)

Interrupts the initialization of the job execution environment database, and continues the startup processing.

(O)

Determine the cause of the error from the system call name and the reason code.

The reason code is a system error number.

If the system call name is mkdir and the reason code indicates insufficient write and read permissions, set the write and read permissions for the user starting JP1/AJS3 on the work directory relevant to execution of the manager process in the job execution environment. Then, if necessary, restart.

The default work folder for Windows Server 2012 or Windows Server 2008, if the installation folder is in the default folder or a folder protected by the system

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\tmp

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

The default work folder for Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used

JP1/AJS3 - Manager-installation-folder\tmp

Default Windows Server 2003 work directory

JP1/AJS3 - Manager-installation-folder\tmp

Default UNIX work directory

/var/opt/jp1ajs2/tmp

If you cannot identify the cause of the error, use the data collection tool to collect data, and then contact the system administrator.

KAVU5501-E

message-from-database-system

This is a message from the database system.

(O)

Check whether any of the following probable causes are present:

The message contains File lock error:

The database file could not be accessed because it was busy.

The probable cause of the busy database are:

- Backup was being executed.

- A command (except the jpqdbcond -L command) that uses an ISAM database was being executed.

- A virus check program was running.

- The JP1/AJS3 data collection tool (for Windows only)

The message contains SHMMNI insufficient:

The shared memory ID was insufficient.

The message contains File not found or insufficient system resources:

Free space on the disk was insufficient.

The message contains File not found or insufficient system resources:

The job execution environment database does not exist.

The message contains System error occurred:

The ISAM file is in an invalid state.

Take one of the following actions according to the cause of the error, and then reissue the request:

Adjust the schedule to execute the program or command that exclusively used the database file at a different time from when other jobs are executed.

Check the values set in the kernel parameters to check (ipcs) the current usage, and then recheck the kernel parameter settings.

Check the disk status. If the message appears during reorganization, estimate the disk space requirements for each database, allocate sufficient free space on the disk, and then reorganize the database. For details on how to reorganize the database, see 10.3 Reorganizing a database when QUEUE jobs and submit jobs are used in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

Use the jpqimport command to create a job execution environment database.

For details on this command, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

Check the status of the ISAM file. If the status is invalid, re-create the ISAM file.

For details on how to check the status of the ISAM file and how to re-create the ISAM file, see 2.12 Troubleshooting problems related to invalid ISAM files in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KAVU5800-I

The definition process for configuration definition ended normally.

The submit job configuration definitions for the configuration definition file for the execution environment (jpqsetup.conf) are defined in the job execution environment database all at one time.

(S)

Continues processing.

KAVU5801-I

The output process for configuration definition ended normally.

The job configuration definitions for the job execution environment were output to a file.

(S)

Continues processing.

KAVU5900-E

There is no daemon starting control lock file.

There is no daemon starting control lock file.

(S)

Cancels command execution.

(O)

Check the lock file .jpqmanlock under the system file directory (/var/opt/jp1ajs2/sys). When you are creating a database for logical hosts, the file name is .jpqmanlock. logical-host-name.

If the system file directory or the lock file shown above has been deleted, you must re-install JP1/AJS3. For logical hosts, you must set up the environment for a cluster again.

For details on how to set up the environment for a cluster, see 17.2 Setting up the operating environment for cluster system operation in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

KAVU5901-E

The specified file cannot be found.

No file was specified in the jpqimport or jpqexport command.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU5902-E

The specified file already exists.

The specified file already exists.

(S)

Cancels command execution.

(O)

The information in a file to which the jpqexport command outputs the job execution environment cannot be overwritten. Specify a new file.

Before outputting the job execution environment to a file, always delete or save the existing file.

Remove the cause of the error, and then re-execute the command.

KAVU5903-E

You lack access permission for the specified file.

There are no access permissions on the file specified in the jpqimport command or on the destination directory for the file, or on the destination directory for the file specified in the jpqexport command.

(S)

Cancels command execution.

(O)

Check the access permissions on the file specified in the jpqimport command or on the destination directory for the file, or on the destination directory for the file specified in the jpqexport command. The jpqimport command requires read permission and the jpqexport command requires write permission for the account that executes the command.

Remove the cause of the error, and then re-execute the command.

KAVU5904-E

The specified directory (folder) is missing.

The specified directory (folder) does not exist.

(S)

Cancels command execution.

(O)

Check whether the directory specified in the jpqimport or jpqexport command exists.

Remove the cause of the error, and then re-execute the command.

KAVU5905-W

The system file (file-name) cannot be removed because it lacks access authority.

The system file (a temporary file for job execution control) cannot be deleted since you do not have access permission for it.

(S)

Cancels the deletion of the system file.

(O)

A system file (a temporary file for job execution control) is stored in the relevant work directory when the manager process is executed in the job execution environment. Check the access permissions on the directory specified in the WorkPath environment variable parameter for [{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Process].

For details about the WorkPath environment variable parameter, see 2.3.2(1) WorkPath in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVU5906-W

The system file (file-name) could not be removed because a system call error occurred.

The system file (a temporary file for job execution control) could not be deleted due to a system call error.

(S)

Cancels the deletion of the system file.

(O)

The system file (a temporary file for job execution control) is stored in the relevant work directory when the manager process is executed in the job execution environment. Check whether the directory specified in the WorkPath environment variable parameter for [{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Process] exists, and also check the access permissions.

For details about the WorkPath environment variable parameter, see 2.3.2(1) WorkPath in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVU5910-E

There is no the database table, or it is short of the system resources.

There is no database table for job execution control, or the system resources are insufficient.

(S)

Cancels command execution.

(O)

Check whether the database table file exists in the directory specified in the -dp option of the jpqexport command or in the directory specified in the DatabasePath environment setting parameter for job execution control, and then re-execute the command. If there is no database table, you need to create another database for job execution control.

For a database table in the UNIX environment, the system resources could also be insufficient. Therefore, check the estimate in the kernel parameter.

For information about how to estimate the kernel parameter, see Release Notes.

KAVU5911-E

The specified database table already exists.

The specified database already exists.

(S)

Cancels command execution.

(O)

Check the database table file under the directory containing the database for the job execution environment.

If the database table file is in the directory specified in the DatabasePath environmental setting parameter, create a backup, delete the file, and then re-execute the command.

For details about the DatabasePath environmental setting parameter, see 2.3.2(3) DatabasePath in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVU5912-E

You lack connect permission for that database.

You do not have permission to connect the database.

(S)

Cancels command execution.

(O)

Check your database access permission.

KAVU5913-E

You lack access permission for the database.

You do not have permission to access the database.

(S)

Cancels command execution.

(O)

Check your database access permission.

KAVU5914-E

You do not have administrator permission to execute the command.

You do not have permission to execute the command (administrator permission).

(S)

Cancels command execution.

(O)

Re-execute the command as an administrator.

Windows requires administrator permission and UNIX requires the superuser permission.

For Windows, if UAC is being used, the administrator must re-execute the command.

Check whether the KAVU5309-E or KAVU5310-E message was output together with this message. If a KAVU message was output, read the message explanation.

KAVU5915-E

There is no path for storing the database.

The database storage path does not exist.

(S)

Cancels command execution.

(O)

Make sure the directory specified in the command or the directory specified in the DatabasePath environmental setting parameter for job execution control is correct, and then re-execute the command.

If there is no directory for storing the database for job execution control, you need to create another database for job execution control.

KAVU5920-E

The manager or the jpqimport command is running on the same logical host (logical-host-name).

The JP1/AJS3 service or the jpqimport command is running on the same logical host.

(S)

Cancels command execution.

(O)

If the JP1/AJS3 service is running, stop the JP1/AJS3 service and then re-execute the command.

If the jpqimport command is running, wait for the jpqimport command to complete processing, and then retry the operation.

Before creating another database in the job execution environment, you must always stop the JP1/AJS3 service. Delete or save the files under the directory for saving the created database for job execution control. The files to be deleted means all files under the directory specified in the -dp option or all files under the directory specified in the DatabasePath environment setting parameter for job execution control.

KAVU5921-E

Environment settings or the logical host name is invalid.

The environment settings or the logical host name is invalid.

(S)

Cancels command execution.

(O)

Check whether the specified logical host name is correct and whether the specified logical host name is the same as that in the environment setting parameters. If the logical host name is not specified in the jpqdbcond command, the system assumes the logical host name specified in the JP1_HOSTNAME environment variable. If the JP1_HOSTNAME environment variable is specified, check whether the specified host name is correct.

KAVU5930-E

Memory could not be allocated.

The system failed to allocate memory.

(S)

Cancels command execution.

(O)

Terminate any other unnecessary applications, and then re-execute. If the same message reappears, re-estimate memory.

KAVU5931-E

The disk is full.

The amount of free space in the disk is insufficient.

(S)

Cancels command execution.

(O)

Increase the free space in the disk, and then re-execute.

KAVU5932-E

A system call error occurred. (reason code:reason-code)

A system call error occurred.

(S)

Cancels command execution.

(O)

Also check the integrated trace log for the KAVU5501-E message.

Check the cause of the error, remove the error, and then retry the operation.

If you cannot identify the cause, use the data collection tool on the manager host to collect data, and then contact the system administrator.

KAVU5933-E

A logical contradiction occurred. (reason code:reason-code)

A logical contradiction occurred.

(S)

Cancels command execution.

(O)

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

KAVU5934-E

It is short of the system resources.

System resources became insufficient.

(S)

Cancels command execution.

(O)

Also check the integrated trace log for the message KAVU5501-E.

In a UNIX environment, check the value specified in the kernel parameter.

For information about how to estimate the kernel parameter, see Release Notes.

KAVU5935-E

A disk difficulty occurred.

An input or output error occurred on the disk.

(S)

Cancels command execution.

(O)

Check whether there is no problem on the disk volume itself.

KAVU5936-E

The database table is locked.

Another program locks the database table.

(S)

Cancels command execution.

(O)

Check whether the backup program or another program is accessing the JP1/AJS3 file or directory.

If the integrated trace log contains the KAVU5501-E message, also read the suggested corrective action.

KAVU5937-E

The database version is invalid.

The version of the database is invalid.

(S)

Cancels command execution.

(O)

Make sure that a database is correctly created. Then, re-execute the command.

KAVU5938-E

Condense failed.

Reorganizing the job execution environment database abnormally terminated.

(S)

Cancels command execution.

(O)

Use the integrated trace log to determine the cause of the error and correct it. Then, re-execute the command.

KAVU5939-E

This version does not support the request so the request cannot be processed.

The request cannot be processed using the current JP1/Base version.

(S)

Cancels command execution.

(O)

Check the supported version of JP1/Base, and upgrade the version.

KAVU5940-E

The database file size is larger than the limit, so processing cannot be performed.

The request was not processed because the size of the job execution environment database exceeded the limit on ISAM file size.

(S)

Cancels the requested processing.

(O)

The probable cause of the error is that a file equal to or greater than 2 gigabytes, which is the limit on ISAM file size, exists in the job execution environment.

Recheck the estimated number of days for job information storage and re-create the job execution environment database.

For details on the number of days for job information storage, see 2.3 Setting up the job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

For details on how to re-create a job execution environment database, see the explanation for creating a job execution environment in 2.3.3 Recovering the JP1/AJS3 - Manager setup information in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

KAVU5941-E

The specified tablespace or RDAREA does not exist.

The table could not be created because the tablespace or RDAREA specified in the jpqimport command did not exist.

(S)

Cancels command execution.

(O)

Specify the correct tablespace or RDAREA as an argument of the jpqimport command, and then retry.

KAVU5942-E

The specified tablespace or RDAREA is invalid.

The table could not be created because the tablespace or RDAREA specified in the jpqimport command was invalid.

(S)

Cancels command execution.

(O)

Specify the correct tablespace or RDAREA for the argument of the jpqimport command, and then retry.

KAVU5943-E

Could not connect to the database because the upper limit of a server setting was exceeded.

The system could not connect to the database because the limit value defined on the database server was exceeded.

(S)

Cancels command execution.

(O)

Either stop other processes connected to the database or re-set the limit on the database, and then re-execute the command.

KAVU5944-E

Could not connect to the database because the username or password was invalid.

Connection to the database was not possible because an invalid user name or password was used.

(S)

Cancels command execution.

(O)

Specify the correct user name and password, and then re-execute the command.

KAVU5945-E

Could not connect to the database.

The system could not connect to the database.

(S)

Cancels command execution.

(O)

Check whether the database is running.

KAVU5948-E

A system call error occurred while checking the administrator permissions. (system call name:system-call-name,module:reason-location[reason-location],reason code:reason-code)

A system call error occurred when the jpqimport, jpqexport, or jpqdbcond command was used to check the administrator permissions.

(S)

Cancels the requested processing.

(O)

Determine the cause of the error from the system call name and the reason code.

The reason code is the value acquired by the GetLastError function of Win32API. If you cannot identify the cause of the error, use the data collection tool to collect data, and then contact the system administrator.

KAVU5949-E

Memory allocation failed while checking the administrator permissions. (size:size,module:reason-location[reason-location],reason code:reason-code)

Memory could not be secured when the jpqimport, jpqexport, or jpqdbcond command was used to check the administrator permissions.

(S)

Cancels the requested processing.

(O)

Stop unnecessary applications and issue another request.

If the same message is output again, review the memory estimate.

KAVU5950-E

The same identifier or object name is already specified. (line:line-number)

This message is output if the defined queue name, agent name, or exclusive execution resource name is duplicated or if a defined identifier (queue ID, agent ID, or exclusive execution resource name) is duplicated.

For these cases, the line number indicates the end of a definition block (where $end is coded).

(S)

Cancels command execution.

(O)

Check the definition information indicated by a line number in the configuration definition file in the submit-job execution environment. Remove the cause of the error, and then re-execute the command.

KAVU5951-E

There is an invalid character in the object name. (line:line-number)

The object name includes an invalid character.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5952-E

The object name is too long. (line:line-number)

The length of the object name exceeds the maximum.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5953-E

The object number is specified incorrectly. (line:line-number)

This message appears if an invalid numeric value is specified.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5954-E

Invalid time specification. (line:line-number)

An invalid time is specified.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5955-E

The concurrently-executable job limit is invalid. (line:line-number)

The maximum number of concurrently-executable job limit is incorrectly specified.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5956-E

No default queue is defined. (line:line-number)

In this message, line-number indicates the number of the last line of the definition block (that is, the line containing $end).

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5957-E

More than one default queue is defined. (line:line-number)

More than one default queue is defined.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5958-E

The connection to the agent is incorrect. (line:line-number)

The agent ID of the agent host that is connected to the default queue of the agent or the specification method for the order of priority is invalid.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5959-E

The maximum number of queuing jobs is specified incorrectly. (line:line-number)

The specified maximum number of jobs allowed in the queue is invalid.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5960-E

The warning number of queuing jobs is specified incorrectly. (line:line-number)

The specified warning value for number of jobs in the queue is invalid.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5961-E

The priority value is invalid. (line:line-number)

The priority value is invalid.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5962-E

A syntax error occurred. (line:line-number)

A syntax error occurred.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5963-E

An object number exceeds the number defined in the environment settings. (line:line-number)

The agent ID, queue ID, or exclusive-execution resource ID contains a value that exceeds the maximum number of definitions specified in the environment settings.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5970-E

The definition process for configuration definition ended abnormally.

The definition process for configuration definition for job execution environment terminated abnormally.

(S)

Cancels command execution.

(O)

Investigate the cause of the error by also using the KAVUxxxx message that was output to the standard error output.

Remove the cause of the error, and then re-execute.

KAVU5971-E

The output process for configuration definition ended abnormally.

The output process for configuration definition for job execution environment terminated abnormally.

(S)

Cancels command execution.

(O)

Investigate the cause of the error by also using the KAVUxxxx message that was output to the standard error output.

Remove the cause of the error, and then re-execute.

KAVU5980-I

Database condensing of the job execution environment started. start-date-and-time

The database reorganization of the job execution environment started.

(S)

Continues the database reorganization.

KAVU5981-I

Database condensing of the job execution environment ended normally. start-date-and-time - termination-date-and-time (required-time)

The database reorganization of the job execution environment has normally terminated.

(S)

Normally terminates the database reorganization.

KAVU5982-E

Database condensing of the job execution environment ended abnormally. start-date-and-time - termination-date-and-time (required-time)

The database reorganization of the job execution environment terminated abnormally.

(S)

Cancels command execution.

(O)

Check for the message KAVU5501-E in the integrated trace log. Use the integrated trace log to check the cause of the error, correct the error, and then reorganize the ISAM file of the job execution environment.

KAVU5983-I

The ISAM unused area size on job execution environment is size-in-megabytes.

The size of the unused area of the ISAM file of the job execution environment is output.

(S)

Outputs the size of the unused area of the ISAM file.

KAVU5984-W

The ISAM unused area size of the job execution environment is size-in-megabytes, which exceeds the size-in-megabytes threshold value.

The size of the unused area of the ISAM file of the job execution environment reached the specified size for that area.

(S)

Continues command execution.

(O)

Reorganize the ISAM file of the job execution environment.

KAVU5986-W

The JP1 event could not be sent. (line:line, reason code:reason-code)

An unsuccessful attempt was made to send the JP1 event with the option specified.

(S)

Continues processing.

(O)

Check whether the system resources are sufficient and whether JP1/AJS3 is installed correctly. To send the JP1 event correctly, re-execute the command.

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

KAVU5987-E

An attempt to obtain the AJS administrator failed.

An attempt to obtain the AJS administrator caused an error. The probable causes are:

The AJS administrator is not set correctly.

Memory is insufficient.

(S)

Cancels command execution.

(O)

Use the jajsshowadminusr command to make sure that the AJS administrator is set correctly.

If the AJS administrator is not set correctly, correct the setting, and then re-execute the command.

For details about operation by AJS administrators, see E. Operating JP1/AJS3 By Using an AJS Administrator Account (UNIX Only) in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

If the AJS administrator is set correctly, a temporary error might have occurred. Re-execute the command.

KAVU6100-I

Job status notification process (host name:logical-host-name, port number:port-number) was started.

The job status notification process was started.

(S)

Starts the daemon.

KAVU6101-I

Job status notification process (host name:logical-host-name, port number:port-number) ended normally.

Job status notification process terminated normally.

(S)

Stops the daemon.

KAVU6102-E

Logical contradiction occurred (reason code:reason-code). Could not start job status notification process (host name:logical-host-name, port number:port-number).

The system failed to start the status notification process because a logical contradiction occurred.

(S)

Stops starting the daemon.

(O)

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

KAVU6103-E

Invalid environment settings (reason code:reason-code). Could not start job status notification process (host name:logical-host-name, port number:port-number).

The system failed to start the status notification process because the environment settings have an error.

(S)

Stops starting the daemon.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then restart.

KAVU6104-E

Another process is using the specified port number (reason code:reason-code). Could not start job status notification process (host name:logical-host-name, port number:port-number).

More than one process cannot use the same port number on the same logical host.

(S)

Stops starting the daemon.

(O)

Check whether another process is started with the specified port. If another process is using the specified port, change the port number and then restart.

KAVU6105-E

Specified port number is out of range. Could not start job status notification process (host name:logical-host-name, port number:port-number).

You can specify a port number from 1024 to 65535.

(S)

Stops starting the daemon.

(O)

Specify a correct port number, and then restart.

KAVU6106-E

Insufficient memory (reason code:reason-code). Could not start job status notification process (host name:logical-host-name, port number:port-number).

The system failed to start the status notification process because memory was insufficient.

(S)

Stops starting the daemon.

(O)

Terminate any other unnecessary applications, and restart. If the same message reappears, re-estimate memory.

KAVU6107-E

Job status notification process (host name:logical-host-name, port number:port-number) is already running on the same host. (reason code:reason-code)

You cannot start more than one daemon with the same port on the same logical host.

(S)

Stops starting the daemon.

(O)

Check whether a daemon is already started. If a daemon is already started, change the port number and then restart.

KAVU6108-E

Job status notification process (host name:logical-host-name, port number:port-number) ended abnormally. (reason code:reason-code)

The status notification process terminated abnormally. This message may also appear when the scheduler service stops or when the jajs_killall.cluster command is executed.

(S)

Stops the daemon.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then restart.

KAVU6109-E

Polling of job status notification process (host name:logical-host-name, port number:port-number) ended abnormally. (reason code:reason-code)

The polling for the status notification process terminated abnormally.

(S)

Stops the daemon.

(O)

Use the integrated trace log to check the cause of the error, correct the error, and then restart.

KAVU6200-I

Polling for the job status notification process (host name : host-name, port number : port-number) was started.

The status notification process for job execution control started polling.

(S)

Continues processing.

KAVU6201-I

Polling for the job status notification process (host name : host-name, port number : port-number) ended normally.

Polling for the status notification process for job execution control terminated normally.

(S)

Continues processing.

KAVU6202-E

Data overflowed in the job status notification process(host name:logical-host-name, port number:port-number), so the job status notification from the manager (logical-host-name) is being ignored.

The system ignored the status notification from the manager because the number of registered status notifications reached the maximum.

(S)

Ignores the job status notification at this polling, and receives the latest status at the next polling.

(O)

If the JpqSetReport function is not issued, check the job status.

KAVU6203-E

The job status report information (manager descriptor=manager-name, job number=job-number, job status=job-status) could not be restored because memory became insufficient.

The information on status notification could not be restored due to insufficient memory.

(S)

Loses the information on status notification of the job.

(O)

Set the polling monitoring of the job again.

KAVU6204-E

The job status report information (manager descriptor=manager-name, job number=job-number, job status=job-status) could not be restored.

The information on status notification could not be restored.

(S)

Loses the information on status notification of the job.

(O)

Set the polling monitoring of the job again.

KAVU6205-E

The job status report information (manager descriptor=manager-name, job number=job-number, job status=job-status) was deleted because the job status report information was not acquired during the specified period.

The information on status notification was deleted because it could not be acquired within the specified period of time.

(S)

Loses the information on status notification of the job.

(O)

Set the polling monitoring of the job again.

KAVU6206-E

In the polling for the job status report process, a TCP/IP communication connection to the manager could not be made. (manager descriptor=manager-name, job number=job-number)

TCP/IP communication could not be connected to the manager during the polling for the status notification process.

(S)

Reports that the job has terminated.

(O)

If the manager has not started, starts it. Then, check the job status.

KAVU6207-E

In the polling for the job status report process, the manager's IP address could not be converted. (manager descriptor=manager-name, job number=job-number)

The IP address of the manager could not be converted during the polling for the status notification process.

(S)

Reports that the job terminates.

(O)

Correct the error and check the job status.

KAVU6208-E

In the polling for the job status report process, the corresponding job did not exist. (manager descriptor=manager-name, job number=job-number)

The job is missing during the polling for the status notification process.

(S)

Reports that the job terminates.

(O)

Check whether the manager contains the job data and check the job status.

KAVU6209-E

In the polling for the job status report process, the specified queue or agent did not exist. (manager descriptor=manager-name, job number=job-number)

The queue or the agent is missing during the polling for the status notification process.

(S)

Reports that the job terminates.

(O)

Check the queue or the agent and check the job status.

KAVU6210-E

In the polling for the job status report process, you lack operator permission. (manager descriptor=manager-name, job number=job-number)

You do not have operator permission for the polling for the status notification process.

(S)

Reports that the job terminates.

(O)

Check whether the user specified for setting the polling has permission to refer to the job data, and then check the job status.

KAVU6211-E

In the polling for the job status report process, an internal factor at the manager caused an error. (manager descriptor=manager-name, job number=job-number)

An error occurred during the polling for the status notification process due to an internal cause of the manager.

(S)

Reports that the job terminates.

(O)

Use the manager log to correct the error, and then check the job status.

KAVU6212-E

In the polling for the job status report process, an internal factor caused an error. (manager descriptor=manager-name, job number=job-number)

An error occurred during the polling for the status notification process due to an internal cause.

(S)

Reports that the job terminates.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If one was output, see the explanation provided in that message. If no KAVUxxxx message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU6213-W

The file cannot be created because there is no path to the file specified as the acquisition destination of the standard output or standard error output file. (manager descriptor=manager-name, job number=job-number)

The file cannot be created because there is no path to the file specified to acquire the standard output or standard error output file.

(S)

Acquired the job data.

(O)

Check the path, and then reissue the request.

KAVU6214-W

The file specified as the acquisition destination of the standard output or standard error output file could not be written. (manager descriptor=manager-name, job number=job-number)

The file specified to acquire the standard output or standard error output file cannot be written into.

(S)

Acquired the job data.

(O)

Check the path, and then reissue the request.

KAVU6215-W

Insufficient disk space. The file specified as the acquisition destination of the standard output or standard error output file cannot be written. (manager descriptor=manager-name, job number=job-number)

The file specified to acquire the standard output or standard error output file cannot be written into because there is an insufficient amount of disk space.

(S)

Acquired the job data.

(O)

Check the free space in the disk, and then reissue the request.

KAVU6216-W

The file cannot be opened because some other process is using the file specified as the acquisition destination of the standard output or standard error output file. (manager descriptor=manager-name, job number=job-number)

The file cannot be opened because another process is using the file specified to acquire the standard output or standard error output file.

(S)

Acquired the job data.

(O)

Remove the cause of the error, and then reissue the request.

KAVU6217-W

The file specified as the acquisition destination of the standard output or standard error output file cannot be created. (manager descriptor=manager-name, job number=job-number)

The file specified to acquire the standard output or standard error output file cannot be created.

(S)

Acquired the job data.

(O)

Remove the cause of the error, and then reissue the request.

KAVU6218-W

In the job status notification process, the job information was not acquired because the error occurred during TCP/IP communication. But the job might have ended normally. (manager descriptor=manager-name, job number=job-number)

When the status notification process confirmed the status of the job to the manager process, an error occurred during TCP/IP communication. This error prevented obtaining the job information.

(S)

Cancels the requested processing.

(O)

The job status displayed by JP1/AJS3 - View shows termination with error detection. However, the job may normally be terminated in the manager. Specify the job number in the message for the -j option, and execute the jpqjobget command to check the job information.

KAVU7110-E

System call error occurred in initializing log process.

A system error occurred while the system was initializing log output control.

(S)

Cancels daemon startup processing or command execution.

(O)

Check the integrated trace log for the cause of the stoppage, remove the cause, and then restart the service or daemon. For a command, also retry the operation.

KAVU7111-E

Logical contradiction occurred in initializing log process.

A logical contradiction occurred while the system was initializing log output control.

(S)

Cancels daemon startup processing or command execution.

(O)

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

KAVU7112-E

Environment setting parameter (environment-setting-parameter=environment-setting-parameter-value) on logical host (logical-host-name) is invalid. Value (value) is used.

The environment setting parameter on the logical host indicated by logical-host-name is invalid.

(S)

Continues daemon startup processing or command execution under an assumed value.

(O)

Correct the cause of the invalid data in the common definition information or insufficient definition. If the assumed value is different from the intended value, remove the cause of the error, and then restart the service or daemon. For a command, also retry the operation.

KAVU7113-E

An attempt to read the environment settings parameter (environment-setting-parameter) on the logical host (logical-host-name) has failed (reason-code). The value (value) will be assumed.

An attempt to read the environment setting parameter on the logical host indicated by logical-host-name has failed.

(S)

Continues daemon startup processing or command execution under an assumed value.

(O)

If the assumed value is different from an intended value, remove the cause of the error, and then restart the service or daemon. For a command, also retry the operation. The probable cause of the error is insufficient memory. Use the integrated trace log to check whether a log indicating insufficient memory was output at the same time the error occurred. If a log indicating insufficient memory was output, check the memory estimate. If other unnecessary applications are running, stop them. If the cause of the error is not insufficient memory, use the data collection tool to collect data, and then contact the system administrator.

KAVU7200-E

Memory could not be allocated. (size:size, module:reason-module[reason-module], reason code:reason-code)

The system failed to allocate memory.

(S)

Cancels daemon startup processing or command execution.

(O)

Stop unnecessary applications. For a service or a daemon, restart the service or daemon. For a command, retry the operation. If the same message reappears, re-estimate memory.

KAVU7201-E

Startup of the job failed because the OS user (OS-user-name) does not have permission to log on as a batch job.

The job failed to start because the OS user of the host for which 1 is set in the UACAdministratorsExec environment setting parameter does not have the permission Log on as a batch job.

(S)

Cancels the requested processing.

(O)

Set Log on as a batch job in the security policy for the OS user and then re-execute the job. For details, see 6.2.22 Settings for executing jobs as a user with administrator permissions when the UAC is enabled in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

KAVU7220-E

Environment settings could not be read because logical host name (logical-host-name) is invalid.

The system failed to import the environment settings because the logical host name was invalid.

(S)

Cancels daemon startup processing or command execution.

(O)

Check for an invalid logical host name in the JP1_HOSTNAME environment variable, remove the cause, and then restart the service or daemon. For a command, also retry the operation.

KAVU7221-E

Environment setting parameter (parameter-name=parameter value) on logical host (logical-host-name) is invalid.

An invalid parameter is specified in the environment settings of the logical host.

(S)

Cancels daemon startup processing or command execution.

(O)

Remove anything invalid in the common definition information or an insufficiently defined factor. For a service or a daemon, restart the service or daemon. For a command, retry the operation.

If this message appears while the definition is correct, memory may be insufficient. Use the integrated trace log to check whether a log for insufficient memory has been output. If such a log has been output, re-estimate the memory. Also, stop any unnecessary applications that are running. Then restart the service or daemon, or for a command, retry the operation.

If parameter-name is ReportStatusPort=, an urgent command may have been executed on a host where JP1/AJS3 - Agent was installed. The urgent command cannot be executed on JP1/AJS3 - Agent.

If the parameter-name is TraceLogPath=, there is also a chance that write and read permissions have not been set for the OS user starting the command, service, or job for the path that was output. If this is the case, set write and read permissions, and re-execute the command, service, or job.

KAVU7222-E

A system error occurred while acquiring environment settings on logical host name (logical-host-name). (module:reason-module[reason-module], reason code:reason-code)

A system error occurred while the system was acquiring the environment settings of the logical host.

(S)

Cancels daemon startup processing or command execution.

(O)

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

KAVU7223-E

A logical contradiction occurred while acquiring environment settings on logical host name (logical-host-name). (module:reason-module[reason-module], reason code:reason-code)

A logical contradiction occurred while the system was acquiring the environment settings of the logical host.

(S)

Cancels daemon startup processing or command execution.

(O)

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

KAVU7224-E

No physical host name can be acquired that corresponds to logical host name (logical-host-name).

The system cannot acquire the physical host name for the logical host name.

(S)

Cancels daemon startup processing or command execution.

(O)

Remove anything invalid in the common definition information or an insufficiently defined factor, and then restart the service or daemon. For a command, also retry the operation.

This message also appears when the IP address of the logical host cannot be acquired.

Make sure that the network is set up using the hosts file or the DNS server so that the IP address can be obtained from the logical host name.

KAVU7225-E

An environment setting on the logical host (logical-host-name) is invalid, or memory became insufficient.

The logical host contains an invalid common definition or memory is insufficient.

(S)

Cancels daemon startup processing or command execution.

(O)

Remove anything invalid in the common definition information, check free memory in the system, and restart the service or daemon. For a command, also retry the operation.

KAVU7226-E

An environment setting parameter (JP1HOSTS) on the logical host (logical-host-name) is invalid.

The logical host contains an invalid jp1hosts or jp1hosts2 definition.

(S)

Cancels daemon startup processing or command execution.

(O)

Check the information in jp1hosts or jp1hosts2, and then restart the service or daemon. For a command, also retry the operation.

KAVU7227-E

Ineffective environment setting parameter (environment-setting-parameter=environment-setting-parameter-value) on logical host (logical-host-name) is specified.

The environment settings contain an invalid parameter.

(S)

Cancels daemon startup processing or command execution.

(O)

Check the common definition information, and then restart the service or the daemon. If this message was output when a command was being executed, re-execute the command.

In Solaris, specifying the IsLimitWorkSize parameter causes this error to occur.

If the OS is Solaris and environment-setting-parameter in the message is IsLimitWorkSize, review the common definition information and make sure that the IsLimitWorkSize parameter is not used.

KAVU7230-E

User mapping could not be initialized because logical host name (logical-host-name) is invalid.

The system failed to initialize user mapping because the logical host name was invalid.

(S)

Stops daemon startup processing.

(O)

Remove anything invalid in the common definition information or an insufficiently defined factor, and restart the service or daemon. If the problem persists, the limit for number of open files in a process might have been reached. Accordingly, make sure that the limit for number of open files in a process has not been reached, and restart the service or daemon.

KAVU7231-E

A system error occurred during the initialization of user mapping (logical-host-name). (module:reason-module[reason-module], reason code:reason-code)

A system error occurred while the system was initializing user mapping.

(S)

Cancels daemon startup processing.

(O)

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

KAVU7232-E

A logical contradiction occurred during initialization of user mapping (logical-host-name). (module:reason-module[reason-module], reason code:reason-code)

A logical inconsistency occurred while initializing the user mapping.

(S)

Cancels starting the daemon.

(O)

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

KAVU7233-E

A Win32API error (Win32API-function-name) occurred during of get user account. (module:reason-module[reason-module], reason code:reason-code)

A Win32API error occurred when acquiring the account while the system was initializing user mapping.

(S)

Cancels daemon startup processing.

(O)

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

KAVU7234-E

The OS user name cannot be acquired. (reason code:reason-code)

The name of the user who starts the command or process could not be acquired.

(S)

Cancels the requested processing.

(O)

The error might be due to registration or deletion of the OS user or a changed password. In such cases, re-execute the command after registration or deletion of the OS user, or the password change, is complete.

KAVU7235-W

The user registered for assumed JP1 user is invalid. Assumed JP1 user was ignored.

An unsuccessful attempt was made to register the assumed JP1 user.

(S)

Disables the assumed JP1 user function, and continues startup of the service.

(O)

Use the jpregguestuser command to delete the assumed JP1 user, and restart the JP1/AJS3 service. To use the assumed JP1 user function, use the jpregguestuser command to register the assumed JP1 user correctly. Then, restart the JP1/AJS3 service.

KAVU7236-W

The port number for service (service-name) on logical host (logical-host-name) could not be acquired. Default value (port-number) is used.

The port number could not be obtained for the service of the specified logical host.

(S)

Uses the default port number to start the daemon or continue command execution.

(O)

Recheck the port number of the services file, and restart the service or the daemon.

KAVU7237-W

Environment setting parameter (environment-setting-parameter=value) on logical host (logical-host-name) is invalid. Value (value) is used.

An invalid parameter is specified in the environment settings of the logical host.

(S)

Assumes a value and continues processing.

(O)

Correct the error in the environment settings or in the definitions. If the assumed value is not an intended one, correct the error, and then reissue the request.

KAVU7238-E

A system call error occurred. (system call name : system-call-name, module : reason-location[reason-location], reason code : reason-code)

A system call error occurred.

(S)

Cancels the requested processing.

(O)

Determine the cause of the error from the system call name and the reason code.

The reason code is a system error number.

If the system call name is rename and the reason code indicates insufficient write and read permissions, set the write and read permissions for the user starting JP1/AJS3 on the work directory relevant to execution of the manager process in the job execution environment. Then, if necessary, restart.

If you cannot identify the cause of the error, use the data collection tool to collect data, and then contact the system administrator.

KAVU7240-E

A double start confirmation file (file-name) cannot be accessed.

The system cannot access the double start confirmation file.

(S)

Terminates the daemon or cancels executing the command.

(O)

Check the lock file .jpqmonlock, .jpqmanlock, or .jpqagtlock in the system file directory (/var/opt/jp1ajs2/sys).

For logical hosts, the file name must be .jpqmonlock.logical-host-name,.jpqmanlock.logical-host-name, or .jpqagtlock.logical-host-name.

If the system file directory or these files have been deleted, you must re-install JP1/AJS3. In addition, for logical hosts, you must set up the environment for a cluster again.

For details on how to set up the environment for a cluster, see 17.2 Setting up the operating environment for cluster system operation in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

KAVU7242-E

The port number for service(service-name) on logical host(logical-host-name) could not be acquired.

The port number for a service on the specified logical host could not be acquired.

(S)

Cancels starting of the daemon.

(O)

Check the services file, set a port number, and restart the service or daemon.

KAVU7530-E

A logical contradiction occurred in the mapping process for JP1 user (user-name). (module:reason-module[reason-module], reason code:reason-code)

A logical contradiction occurred in the mapping process for the JP1 user.

(S)

Cancels the requested processing.

(O)

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

KAVU7531-E

A system error occurred in the mapping process for JP1 user (user-name). (module:reason-module[reason-module], reason code:reason-code)

A system error occurred in the mapping process for the JP1 user.

(S)

Cancels the requested processing.

(O)

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

KAVU7532-E

JP1 user account (host name=logical-host-name, JP1 user name=user-name) could not be mapped.

The user mapping definition does not contain a JP1 user account of the user name.

(S)

Cancels the requested processing.

(O)

The user mapping definition may contain an error. Check the following:

The user mapping definition does not contain the OS user.

The user mapping definition contains an OS user that does not exist.

The user mapping definition contains the OS user with an invalid password.

An OS user that has not been mapped is used to register a jobnet by the ajsentry command.

If the user mapping definition does not contain any error, memory may be insufficient. In this case, re-estimate memory.

KAVU7533-E

The execution user (user-name) mapped from JP1 user (host name=host-name, JP1 user name=user-name) is invalid. (reason code:reason-code)

An invalid execution user name is mapped.

(S)

Cancels the requested processing.

(O)

The reason code is given as follows:

For Windows

Value obtained by Win32 API function GetLastError

For UNIX

Value obtained by errno

The following describes probable causes for reason codes, and suggests corrective actions:

For Windows

If reason-code is 1326

The access token for the OS user executing the job might not have been acquired. Note the following points:

- If the user who executes the job is a domain user, the status of the domain controller might be the cause of the error. For a user account to be referenced, the domain user must be able to log on. However, because JP1/AJS3 does not take into account the number and status of domain controllers, use care when restarting a domain controller during the execution of a job.

- Acquisition of the access token might not be possible due to a temporary error in a Win32 API function. For details, see 5.4.1 User account for job execution in the manual Job Management Partner 1/Automatic Job Management System 3 Overview.

If reason-code is 1330

When the job is executed with a user account that is different from a JP1/AJS3 service account, check whether the user password has expired.

If reason-code is 1385

Check whether message KAVU7201-E was ouput to the integrated trace log before or after this error message. If so, see the message explanation.

If message KAVU7201-E was not output, set Allow Log On Locally in the security policy for the OS user and then re-execute the job.

If reason-code is 1792

When the job is executed with a user account that is different from a JP1/AJS3 service account, check whether the NetLogon service is running.

If reason-code is 1909

The account of the OS user executing the job might be locked out. Check whether an invalid password was set for the OS user who executed the job.

If the account is locked out, unlock it and then re-execute the job.

For details about how to unlock an account, see the Microsoft website.

For UNIX

Even though the OS user executing the job is currently registered, a temporary error might occur due to an OS system call when the OS user is registered or unregistered, or the OS user's password is changed. If a temporary error occurs, wait until the registration, unregistration, or password change is completed and then re-execute the job.

You can change the retry settings for acquriring user information. For details, see 15.2.20 Changing the settings for retries when user information is acquired in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

If reason-code is other than the above, inappropriate OS users might have been registered in the user mapping definition.

Check the following points, and if any applies, register an appropriate OS user.

Whether a non-existent OS user has been registered

Whether an invalid password has been registered for an OS user

Whether an OS user with an invalid account has been registered

Whether an OS user who does not have permission to log on has been registered

If the user mapping definition has no errors, memory might have become insufficient. If so, review memory estimates.

If the OS is Windows, you can reduce the frequency of this error by reusing an access token during job execution. For details on how to enable reuse of an access token during job execution, see 6.2.17 Reusing access tokens for job execution in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

KAVU7534-E

JP1 user account (host name=logical-host-name, JP1 user name=user-name) does not correspond to execution user name (user-name).

The JP1 user account does not correspond to the execution user name.

(S)

Cancels the requested processing.

(O)

The user mapping definition may contain an error. Check the following:

The user mapping definition contains an OS user that does not exist.

The user mapping definition contains the OS user with an invalid password.

KAVU7535-E

Win32API error (Win32API-function-name) occurred during of check Administrator account. (module:reason-module[reason-module], reason code:reason-code)

A Win32API error occurred when checking administrator permission while the system was performing the JP1 user mapping process.

(S)

Cancels the requested processing.

(O)

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

KAVU8901-E

An attempt to obtain a list of scheduler services failed. (module:reason-location[reason-location], reason code:reason-code)

While environment setting parameters for job execution control were being migrated during JP1/AJS3 setup processing by the jajs_migrate command, an attempt to obtain the list of scheduler services failed.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

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

KAVU8904-I

Processing of migrating the environment setting parameters of job execution control started.

Processing to migrate the environment setting parameters for job execution control has started. This processing is actually part of the JP1/AJS3 setup processing performed by the jajs_migrate command.

(S)

Continues the JP1/AJS3 setup processing.

KAVU8905-E

Processing of migrating the environment setting parameters of job execution control ended abnormally. (module:reason-location[reason-location], reason code:reason-code)

Processing to migrate the environment setting parameters for job execution control has terminated abnormally. This processing is actually part of the JP1/AJS3 setup processing performed by the jajs_migrate command.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

Take corrective action according to the message that was output immediately before this message, and then re-execute the jajs_migrate command.

KAVU8906-E

An attempt to register the environment setting parameters of job execution control failed. (module:reason-location[reason-location], reason code:reason-code)

During JP1/AJS3 setup processing by the jajs_migrate command, an attempt to register the environment setting parameters for job execution control that were being migrated failed.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

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

KAVU8907-I

Processing of migrating the environment setting parameters of job execution control ended normally.

Processing to migrate the environment setting parameters for job execution control has terminated normally. This processing is actually part of the JP1/AJS3 setup processing performed by the jajs_migrate command.

(S)

Continues the JP1/AJS3 setup processing.

KAVU8908-I

Job information delete process started.

Processing to delete the job information has started. This processing is actually part of the JP1/AJS3 setup processing performed by the jajs_migrate command.

(S)

Continues the JP1/AJS3 setup processing.

KAVU8909-E

Could not change the current directory. (module:reason-location[reason-location], reason code:reason-code)

During JP1/AJS3 setup processing by the jajs_migrate command, an attempt to change the work directory during processing to delete job information failed.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

The work directory referred to here is the work directory used when the manager process in the job execution environment is executed. Check whether the directory specified in the WorkPath environment setting parameter in the definition key [{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Process] exists.

For details about the WorkPath environment variable parameter, see 2.3.2(1) WorkPath in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

If the work directory is missing, create a new one and re-execute the jajs_migrate command. If the work directory exists, use the data collection tool to collect data, and then contact the system administrator.

KAVU8910-E

An attempt to output the job execution environment files failed. (module:reason-location[reason-location], reason code:reason-code)

During JP1/AJS3 setup processing by the jajs_migrate command, an attempt to output the job execution environment files during processing to delete the job information failed.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

Make sure that the JP1/AJS3 service has stopped. If the JP1/AJS3 service is running, stop it, and then re-execute the jajs_migrate command. If the JP1/AJS3 service has stopped, use the data collection tool to collect data, and then contact the system administrator.

KAVU8911-E

An attempt to obtain the path for the job execution environment database failed. (module:reason-location[reason-location], reason code:reason-code)

During JP1/AJS3 setup processing by the jajs_migrate command, an attempt to acquire the path to the database in the job execution environment during processing to delete the job information failed.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

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

KAVU8912-E

An attempt to delete the folder that contains the job execution environment database failed. (module:reason-location[reason-location], reason code:reason-code)

During JP1/AJS3 setup processing by the jajs_migrate command, an attempt to delete the folder containing the database in the job execution environment during the deletion of job information failed.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

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

KAVU8913-E

An attempt to re-create the job execution environment database failed. (module:reason-location[reason-location], reason code:reason-code)

During JP1/AJS3 setup processing by the jajs_migrate command, an attempt to re-create a database in the job execution environment during the deletion of job information failed.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

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

KAVU8914-I

The job information delete processing ended normally.

The processing to delete the job information has terminated normally. This processing is actually part of the JP1/AJS3 setup processing performed by the jajs_migrate command.

(S)

Continues the JP1/AJS3 setup processing.

KAVU8915-E

The job information delete processing ended abnormally. (module:reason-location[reason-location], reason code:reason-code)

The processing to delete the job information has terminated abnormally. This processing is actually part of the JP1/AJS3 setup processing performed by the jajs_migrate command.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

Take corrective action according to the message that was output immediately before this message, and then re-execute the jajs_migrate command.

KAVU8916-I

Processing of analyzing the job execution environment database started.

Analysis of the database in the job execution environment has started. This processing is actually part of the JP1/AJS3 setup processing performed by the jajs_migrate command.

(S)

Continues the JP1/AJS3 setup processing.

KAVU8917-I

Processing of analyzing the job execution environment database ended normally.

Analysis of the database in the job execution environment has terminated normally. This processing is actually part of the JP1/AJS3 setup processing performed by the jajs_migrate command.

(S)

Continues the JP1/AJS3 setup processing.

KAVU8918-E

Processing of analyzing the job execution environment database ended abnormally. (module:reason-location[reason-location], reason code:reason-code)

Analysis of the database in the job execution environment has terminated abnormally. This processing is actually part of the JP1/AJS3 setup processing performed by the jajs_migrate command.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

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

1.2 Messages beginning with KAVV (Messages about JP1/AJS3 - View)

This section lists the messages that begin with KAVV (messages about JP1/AJS3 - View).

KAVV100-E

During process-name exception-name occurred. JP1/AJS3 - View will now end. Detailed information: detailed-information-1, detailed-information-2

An exception indicated in exception-name occurred during processing indicated in process-name.

(S)

Terminates JP1/AJS3 - View.

(O)

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

A hardcopy of the window

JP1/AJS3 - View log files

Click the OK button in this message dialog box, and then collect the JP1/AJS3 - View log files.

KAVV101-E

During (process-name) memory became insufficient. JP1/AJS3 - View will now end. detailed information: detailed-information-1, detailed-information-2

A memory shortage occurred during processing.

(S)

Terminates JP1/AJS3 - View.

(O)

Change the amount of memory that JP1/AJS3 - View uses, and then restart JP1/AJS3 - View.

For details on how to change the memory size, see 11.2.5 Setting the amount of memory used in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

KAVV102-E

A required class file (class-file-name) was not found.

The class file required for executing JP1/AJS3 - View is not found.

(S)

Terminates JP1/AJS3 - View.

(O)

The configuration of JP1/AJS3 - View may have been corrupted. Perform a repair installation.

KAVV103-E

The value in the keyword (keyword) in the setting file (file-name) is specified incorrectly. The default value (default-value) will be assumed and processing will continue.

The keyword defined in the setting file is invalid.

(S)

Assumes the indicated default and continues processing.

(O)

Correct the value specified for keyword, and then restart JP1/AJS3 - View.

KAVV107-E

An error occurred while outputting the setting file (file-name).

An error occurred during output of the setting file. The probable causes are:

You do not have access permission for files under the folder for storing settings files.

The disk does not have sufficient free space.

The file is being edited in another program.

The locations of the folders for storing settings files are as follows:

For Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\conf

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

For Windows Server 2003 or Windows XP Professional

JP1/AJS3 - View-installation-folder\conf

(S)

Cancels processing.

(O)

Correct the cause of the error. If you cannot correct the error, the configuration of JP1/AJS3 - View may have been corrupted. Perform a repair installation.

KAVV108-E

An error occurred while inputting the setting file (file-name).

An error occurred during input of the setting file. The probable causes are:

You do not have access permission for files under the folder for storing settings files.

The disk does not have sufficient free space.

The file is being edited in another program.

The locations of the folders for storing settings files are as follows:

File extensions other than .cjx

For Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\conf

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

For Windows Server 2003 or Windows XP Professional

JP1/AJS3 - View-installation-folder\conf

File extension .cjx

For Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

For Windows Server 2003 or Windows XP Professional

JP1/AJS3 - View-installation-folder\custom.dir

(S)

Cancels processing.

(O)

Correct the cause of the error. If you cannot correct the error, the configuration of JP1/AJS3 - View may have been corrupted. Perform a repair installation.

KAVV109-E

Enter the values (lower-limit-value) - (upper-limit-value) in (field-name).

The value entered for field-name is invalid.

(S)

Cancels processing.

(O)

Reenter a value from lower-limit-value to upper-limit-value for field-name.

KAVV110-E

The specified (object) has already been defined.

The specified object has already been defined.

(S)

Cancels processing.

(O)

Reenter a unique object using the name, number format.

KAVV111-E

Enter the (field-name).

The indicated field name is not defined.

(S)

Cancels processing.

(O)

Enter a value for field-name.

KAVV112-E

A period (.) and an at sign (@) cannot be specified at the beginning of the (object).

A period (.) or an at mark (@) is specified at the beginning of the indicated object.

(S)

Cancels processing.

(O)

Reenter a name without the period (.) or the at mark (@) at the beginning of the indicated object.

KAVV113-E

The unit name is duplicated.

A duplicate unit name is specified.

(S)

Cancels processing.

(O)

Specify a unit name that is not duplicated within the same unit level.

KAVV114-E

The log output processing could not be initialized. Detailed information (detailed-information-1, detailed-information-2)

An error occurred during initialization for log output processing. The probable causes are:

You do not have access permission for files under the log folder.

The disk does not have sufficient free space.

The locations of the log folders are as follows:

For Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\log

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

For Windows Server 2003 or Windows XP Professional

JP1/AJS3 - View-installation-folder\log

(S)

Cancels processing.

(O)

Correct the cause of the error. If you cannot correct the error, the configuration of JP1/AJS3 - View may have been corrupted. Perform a repair installation.

KAVV115-E

The log could not be output. Detailed information (detailed-information-1, detailed-information-2)

An error occurred during log output processing. The probable causes are:

You do not have access permission for files under the log folder.

The disk does not have sufficient free space.

The locations of the log folders are as follows:

For Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\log

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

For Windows Server 2003 or Windows XP Professional

JP1/AJS3 - View-installation-folder\log

(S)

Cancels processing.

(O)

Correct the cause of the error. If you cannot correct the error, the configuration of JP1/AJS3 - View may have been corrupted. Perform a repair installation.

KAVV116-E

Select a unit.

No unit is selected.

(S)

Cancels processing.

(O)

Select a unit you want to manipulate.

KAVV117-E

Select a schedule that you want to change from the list of executions.

The target generation is not selected from the list of execution results.

(S)

Cancels processing.

(O)

Select the target generation from the list of execution results, and then retry.

KAVV118-E

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

The setting file (file-name) required for starting JP1/AJS3 - View is not found.

(S)

Cancels processing.

(O)

The configuration of JP1/AJS3 - View may have been corrupted. Perform a repair installation.

KAVV119-E

An error occurred while displaying the message box.

An error occurred during processing to display a message box.

(S)

Outputs, to the log, the information indicating that an error occurred while a message box was being displayed.

(O)

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

JP1/AJS3 - View log files

KAVV120-E

The unit cannot be specified in an exclusive jobnet.

You cannot specify the local jobnet for an exclusive jobnet.

(S)

Cancels processing.

(O)

For an exclusive jobnet, specify a jobnet other than the local jobnet at the same unit level or a planning group.

KAVV121-E

The value in the keyword (keyword) in the setting file (file-name) is specified incorrectly. The specification will be ignored and processing will continue.

The keyword specified in the setting file is incorrect.

(S)

Ignores the specification and continues processing.

(O)

Specify a correct value for the keyword, and then restart JP1/AJS3 - View.

KAVV122-E

The value in the keyword (jajsDisableMenu) of the common definition in the manager (manager-name) is specified incorrectly. The specification will be ignored and processing will continue. Detailed information: "value-1", "value-2", ..., "value-n"

The JP1/AJS3 - View customize file (jajsDisableMenu) to be set in JP1/AJS3 - Manager at the connection destination contains an error.

(S)

Ignores the specification and continues processing.

(O)

On JP1/AJS3 - Manager at the connection destination, correct the incorrectly-specified values ("value-1", "value-2", ..., "value-n") in the customized file (jajsDisableMenu keyword), and then log in to JP1/AJS3 - View again.

For details about the value to specify with a customized file (jajsDisableMenu), see 11.3.9 Disabling menus in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

KAVV124-E

The help file could not be restarted.

The system failed to start the help file.

(S)

Cancels processing.

(O)

Make sure that the htm file is associated with the browser correctly.

KAVV125-I

Two or more units are being processed. Please wait.

This message indicates that multiple units are being manipulated.

(S)

Waits for a response.

(O)

To cancel processing, click the Cancel button.

KAVV126-I

Now connecting with the Manager. Please wait.

The system is being connected to the manager.

(S)

Reports that the system is being connected to the manager.

(O)

Click Cancel button to cancel the operation or editing. If you want to continue the operation or editing, wait until the message dialog box closes.

KAVV127-E

Enter the (field-name).

Nothing is entered for field-name.

(S)

Cancels processing.

(O)

Enter a value for field-name.

KAVV128-I

When only the calendar is packaged, the calendar information will be overwritten to the job group specified as an import destination.

This is a message about packaging.

(S)

Reports a message about packaging.

(O)

If you do not want to overwrite the calendar data, click OK button and then uncheck the item.

KAVV130-E

Specify the root jobnet. (unit-name)

The system cannot execute the selected operation for unit-name.

(S)

Cancels processing.

(O)

Select the root jobnet, and then retry.

KAVV131-E

Specify a jobnet. (unit-name)

Nothing can be pasted because no unit has been copied or cut.

(S)

Cancels processing.

(O)

Copy or cut a unit before you attempt to paste it.

KAVV132-E

A unit that is cut or copied was not found.

A unit cannot be pasted because a copied or cut unit was not found.

(S)

Cancels processing.

(O)

Before pasting a unit, you must copy or cut it.

KAVV134-E

You cannot paste a unit of a different scheduler service.

An attempt was made to paste a unit of a different scheduler service.

(S)

Cancels processing.

(O)

Copy or cut a unit within the same scheduler service, and then paste it.

KAVV137-E

Specify a value greater than (the minimum-value) in the field (field-name).

The specified value is smaller than minimum-value for field-name.

(S)

Cancels processing.

(O)

Specify a value equal to or greater than minimum-value.

KAVV138-E

Add a unit name to the (field-name).

Add a unit name to the field-name.

(S)

Cancels processing.

(O)

To use the Backup page, add a unit you want to back up from the Unit elements field to the Units to backup field. To use the Restore page, add a unit you want to restore from the Backup file field to the Units to restore field.

KAVV140-E

The keyword (keyword-name) of the login information file (file-name) is not specified.

Automatic login has failed because the keyword indicated in keyword-name was not specified in the login information file. The probable causes are:

The keyword indicated in keyword-name has not been set.

Spaces or tabs precede or follow the keyword indicated in keyword-name.

(S)

Cancels automatic login, and displays the Login screen.

(O)

Enter the necessary information in the Login screen, and then log in again.

Also check the contents of the login information file according to ajs in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

KAVV141-E

This operation is executable only during exclusive editing.

The system can execute the operation only in the exclusive edit mode.

(S)

Cancels processing.

(O)

Place a check mark on Exclusive edit in the Jobnet Editor window, and then retry.

KAVV142-E

This operation cannot be executed because the map information is being loaded.

The system cannot execute the operation during loading of the map information.

(S)

Cancels processing.

(O)

Wait for loading of map information to complete, and then retry.

KAVV143-E

There is no place to paste.

There is no place to paste a unit.

(S)

Cancels processing.

(O)

Increase the map size or delete unnecessary units, and then retry.

KAVV144-E

This operation is not possible when two or more units are selected.

This operation cannot be performed when more than one unit is selected.

(S)

Cancels processing.

(O)

Select one unit only, and then retry.

KAVV145-E

Two or more units are selected.

The system cannot execute the operation because multiple units are selected.

(S)

Cancels processing.

(O)

Select one unit only, and then retry.

KAVV146-E

Select a jobnet.

The system cannot execute the operation because no jobnet is selected.

(S)

Cancels processing.

(O)

Select a jobnet, and then retry.

KAVV147-E

The upper jobnet does not exist.

An attempt was made to display the parent jobnet while the root jobnet was being displayed.

(S)

Cancels processing.

(O)

Check the level of the jobnet that is currently displayed.

KAVV148-E

Specify (field-name).

Nothing is specified for field-name.

(S)

Cancels processing.

(O)

Enter a value for the field name, and then retry.

KAVV149-E

Specify both start and end days in the fixed schedule period.

A job cannot be registered for fixed execution because neither the start nor end dates of the fixed schedule period are specified.

(S)

Cancels processing.

(O)

To register a job for fixed execution with the fixed schedule period specified, specify both the start and end dates.

KAVV150-E

Specify the fixed schedule period or the number of future generations.

A job cannot be registered for fixed execution because the fixed schedule period or the number of future generations is not specified.

(S)

Cancels processing.

(O)

To register a job for fixed execution, specify the fixed schedule period or the number of future generations.

KAVV151-E

For the beginning date of the fixed schedule period, specify a date before the end day.

A job cannot be registered for fixed execution because the specified start date is later than the end date of the fixed schedule period.

(S)

Cancels processing.

(O)

To register a job for fixed execution with the fixed schedule period specified, specify a start date earlier than the end date.

KAVV152-E

No schedule exists. (unit-name)

Operation is impossible because no target generation is specified.

The probable causes are:

The execution ID was lost.

Registration was canceled.

An operation was performed on a dummy schedule.

An operation was performed on an execution schedule for an unregistered unit.

(S)

Cancels processing.

(O)

Select a schedule or result, and then retry.

KAVV153-E

The root job group cannot be deleted.

You attempted to delete the root job group.

(S)

Cancels processing.

(O)

Delete a unit other than the root job group.

KAVV154-E

The root jobnet cannot be deleted.

You attempted to use the Jobnet Editor window to delete the root jobnet.

(S)

Cancels processing.

(O)

Use the JP1/AJS3 - View window to delete the root jobnet.

KAVV155-E

Select a jobnet.

No target jobnet is selected.

(S)

Cancels processing.

(O)

Select a jobnet, and then retry.

KAVV156-E

Select a job group.

No target job group is selected.

(S)

Cancels processing.

(O)

Select a job group, and then retry.

KAVV158-E

Only an event icon can be used as a start condition.

You attempted to place a unit other than an event icon for a start condition.

(S)

Cancels processing.

(O)

Only use an event icon for the start condition.

KAVV159-E

A relation cannot be used as a start condition.

You attempted to define a relation line between units for a start condition.

(S)

Cancels processing.

(O)

Do not define a relation line between units for a start condition.

KAVV160-E

There is no (Jobnet Monitor | Detailed Information) that can be displayed in (Status | Result | Next Schedule)

The Jobnet Monitor window or Detailed Information dialog box cannot be displayed because the generation of the specified status, result, or next schedule does not exist for the specified jobnet.

(S)

Cancels processing.

(O)

Before you specify the status of the result, make sure that the status for the corresponding generation is displayed in the JP1/AJS3 - View window.

You can display neither the Jobnet Monitor window nor the Detailed Information dialog box for a jobnet that is not yet registered.

KAVV161-E

Select a job group or a jobnet.

Neither job group nor jobnet is selected for operation.

(S)

Cancels processing.

(O)

Select a job group or jobnet, and then retry.

KAVV162-E

(unit-name) was not found. It might have been deleted or the unit complete name might have been changed. Explore the hierarchy again.

The selected unit-name is not found.

(S)

Cancels processing and, if possible, selects a unit above the specified unit.

(O)

Expand the hierarchy again and check whether the specified unit exists.

KAVV163-E

A schedule cannot be set as a start condition.

You attempted to define a schedule for a start condition.

(S)

Cancels processing.

(O)

Set a schedule for the root jobnet.

KAVV164-E

The port number could not be obtained. Confirm whether the service name is defined correctly.

The system failed to obtain the port number.

(S)

Cancels processing.

(O)

Make sure that the service name and the port number for jp1ajs2monitor have been set correctly in the services file.

If the port number is defined correctly, memory or free space on the disk may be insufficient. Terminate unnecessary applications, and then restart JP1/AJS3 - View.

KAVV165-E

A start condition can be neither cut nor copied.

You attempted to copy or cut a start condition.

(S)

Cancels processing.

(O)

Do not to copy or cut a start condition.

KAVV166-E

The root jobnet cannot be cut.

You attempted to cut the root jobnet.

(S)

Cancels processing.

(O)

Do not cut the root jobnet.

KAVV167-E

You cannot paste a unit of a different scheduler service, a manager jobnet, or a manager job group.

You attempted to paste a unit of a different scheduler service, a job group, a manager job group, a manager jobnet, or a planning group to the jobnet.

(S)

Cancels processing.

(O)

Copy or cut a job or jobnet in the same scheduler service as the destination jobnet, and then paste it again.

The manager jobnet cannot be pasted to the jobnet.

KAVV168-E

Only an event icon can be pasted in a start condition.

You attempted to paste a unit other than an event icon for a start condition.

(S)

Cancels processing.

(O)

Copy or cut an event icon and paste it again to the start condition.

KAVV169-E

When you select 'Enable' in 'Concurrent Exec.', you cannot select 'Hold if prev. was "abend" or 'Hold if prev. = "warning" or "abend" in 'Hold'.

In the Define Details dialog box for a root jobnet or root remote jobnet, Enable is selected for Concurrent exec. concurrently with Hold if prev. = 'abend' or Hold if prev. = 'warning' or 'abend'.

(S)

Cancels processing.

(O)

Select Disable for Concurrent exec., or select No or Yes for Hold.

KAVV170-E

This operation cannot be executed because the Find dialog box is displayed.

The system cannot execute this operation because the Find dialog box is displayed.

This message appears only when the version of JP1/AJS2 - Manager at the connection destination is 06-00.

(S)

Cancels processing.

(O)

Close the Find dialog box, and then retry.

KAVV171-E

Up to (number) icons can be located in a start condition.

You attempted to place more than number icons for a start condition.

(S)

Cancels processing.

(O)

Place up to number icons for the start condition.

KAVV172-E

Specify a job or root jobnet. (unit-name)

Only a job or root jobnet can perform the selected operation.

(S)

Cancels processing.

(O)

Select a job or root jobnet, and then retry.

KAVV173-E

The Define Detail dialog box cannot be displayed for an unknown unit.

The Define Details dialog box cannot be displayed because the specified unit has been added for the upgraded version or is a custom job that has not been registered in the current version of JP1/AJS3 - View.

(S)

Cancels processing.

(O)

If the specified unit is a custom job, terminate JP1/AJS3 - View and then register the required custom job.

If the version of JP1/AJS3 - View is earlier than the version of JP1/AJS3 - Manager at the connection destination, upgrade JP1/AJS3 - View to the version of JP1/AJS3 - Manager at the connection destination.

KAVV175-E

A date before 1994 cannot be specified.

You attempted to display a date earlier than the year 1994 in the Daily Schedule or Monthly Schedule window.

(S)

Cancels processing.

(O)

In the Daily Schedule or Monthly Schedule window, display a date in the range from the year 1994 to the year 2036.

KAVV176-E

A date after 2037 cannot be specified.

You attempted to display a date after the year 2037 in the Daily Schedule or Monthly Schedule window.

(S)

Cancels processing.

(O)

In the Daily Schedule or Monthly Schedule window, display a date in the range from the year 1994 to the year 2036.

KAVV177-E

Cannot be moved because the cut part and the paste destination are the same.

The specified unit cannot be moved because the cut source and the paste destination are in the same level.

(S)

Cancels processing.

(O)

To move a unit, paste it to a different level from the cut source.

KAVV178-E

Cannot be moved because the cut part and the paste destination overlap.

You cannot paste a cut unit to a lower level.

(S)

Cancels processing.

(O)

Paste the cut unit to a higher level or a different level.

KAVV179-E

A unit cannot be defined because the unit hierarchy exceeded the maximum.

The unit hierarchy exceeds the maximum.

(S)

Cancels processing.

(O)

Define the unit hierarchy within the maximum.

The maximum value for the unit hierarchy is 30 levels from directly under the root job group (not including the root job group).

In a UTF-8 environment, when the setting for changing the number of characters specifiable for unit names or other items is enabled, note that the maximum value for the unit hierarchy is 10, counting from directly under the root job group (excluding the root job group). For details about how to set that the number of characters used to specify unit names or other items can be changed in a UTF-8 environment, see 15.1.9 Setting for changing the number of characters specifiable for a unit name in a UTF-8 environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

KAVV181-E

(field-name) is specified incorrectly.

The value specified for field-name is invalid.

(S)

Cancels processing.

(O)

Specify a correct value for field-name.

KAVV182-E

Cannot edit exclusively because the jobnet has already been registered.

You attempted to change the registered jobnet to the exclusive edit mode.

(S)

Cancels processing.

(O)

Unregister the jobnet, and then place a check mark on Exclusive edit in the Jobnet Editor window.

KAVV183-E

A jobnet that is the basis of exclusive editing can be neither cut nor deleted.

You attempted to cut a jobnet used in exclusive editing.

(S)

Cancels processing.

(O)

If you want to cut anything in the Jobnet Editor window, select a unit on the map area.

KAVV184-E

A package cannot be used as the root job group.

You attempted to package the root job group.

(S)

Cancels processing.

(O)

Select a unit other than the root job group, and then retry.

KAVV185-E

(unit-name) was not found. It might have been deleted or the unit name might have been changed. Select 'Refresh' to update the list area.

You attempted operation for a unit that may be deleted or whose name may be changed.

(S)

Cancels processing.

(O)

In the JP1/AJS3 - View window, choose Refresh to update the list area, and then retry.

KAVV186-E

Specify a job. (unit-name)

Only jobs can perform the selected operation.

(S)

Cancels processing.

(O)

Select a job, and then retry.

KAVV187-E

The scheduler service does not exist.

The scheduler service does not exist. The probable causes are:

The scheduler service specified in the -F option of the ajs command was not defined in JP1/AJS3 - Manager at the connection destination.

The scheduler service is not defined in JP1/AJS3 - Manager at the connection destination.

If the HIDEOTHERSERVICE environment setting parameter is set to prevent the viewing of scheduler services, scheduler services cannot be viewed.

(S)

Cancels processing.

(O)

Terminate JP1/AJS3 - View, and then check the configuration of the scheduler service in JP1/AJS3 - Manager at the connection destination.

If the restriction on viewing scheduler services is enabled, check the following settings in JP1/AJS3 - Manager:

Check whether a JP1 resource group has been set for the root job group. If one has not been set, use the ajschange command to set an appropriate JP1 resource group.

Check whether the JP1 login user has View permission for the JP1 resource group that is set for the root job group.

Check whether the OS user mapped to the JP1 login user can access the following directories that make up the scheduler service:

- Database directory

- Temporary directory

- Job information directory

- Backup information directory

KAVV188-E

The status could not be obtained. The execution ID being monitored might have been lost or the registration might have been canceled.

The system failed to obtain the status of the displayed jobnet in the Jobnet Monitor window.

Alternatively, the system failed to display the Jobnet Monitor window or detailed information for a remote jobnet. The probable causes are:

The execution ID being monitored was lost.

Registration was canceled.

(S)

Cancels processing.

(O)

Close the Jobnet Monitor window if it is displayed. If Fixed Monitor is selected for Monitor Mode, select another monitor mode.

KAVV189-I

The specified windows is minimized.

The window could not be maximized because it has been minimized.

(S)

Reports that the window could not be maximized because it has been minimized.

(O)

Change the size of the minimized window back to the original size manually.

KAVV190-E

There is an ineffective parameter. [(parameter)]

The ajs command contains an ineffective parameter specified as an argument.

This message is output for the ineffective parameter that is detected first.

(S)

Ignores the ineffective parameter and continues processing.

(O)

Check the specified parameters, remove the ineffective parameter, and then re-execute the command.

KAVV191-E

There is an invalid parameter. [(parameter)]

The ajs command contains an invalid parameter specified as an argument.

(S)

Cancels processing.

(O)

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

KAVV192-E

A required parameter is missing. [(parameter)]

The ajs command does not have the parameter that must be specified as argument.

(S)

Cancels processing.

(O)

Add the necessary parameter, and then retry.

KAVV193-E

The same argument has already been defined. [(parameter)]

The same parameter is specified more than once for an ajs command argument.

(S)

Cancels processing.

(O)

Remove the duplicate parameter, and then retry.

KAVV194-E

Select a unit in the tree area.

No unit is selected in the tree area.

(S)

Cancels processing.

(O)

Select a unit in the tree area, and then retry.

KAVV195-E

The root job group cannot be copied.

You attempted to copy the root job group.

(S)

Cancels processing.

(O)

Copy a unit other than the root job group.

KAVV196-E

There is no start condition.

The system attempted to delete the start condition when no start condition was defined.

(S)

Cancels processing.

(O)

Check whether the start condition is defined.

KAVV198-E

An unrestorable unit exists.

A unit cannot be recovered due to the following reasons:

An attempt was made to recover a job group under a jobnet.

An attempt was made to recover the unit being executed under the root jobnet that is in the suspended status.

The root jobnet to recover has been registered.

The job group to recover contains the root jobnet that has been registered.

An attempt was made to recover the manager jobnet as the nested jobnet.

(S)

Cancels processing.

(O)

If the unit cannot be recovered because it has already been registered, unregister the unit.

The manager jobnet cannot be created under the jobnet. Do not recover it under the jobnet.

KAVV199-E

A calendar cannot be set in the manager job group.

You attempted to set calendar information in the manager job group.

(S)

Cancels processing.

(O)

Open the reference destination job group, and then set the calendar information.

KAVV202-I

(edition) of (definition) (definition-type) was done.

The definition was edited.

(S)

Outputs to the log that Register for execution, Suspend, or Release Suspension was performed for the unit (the-full-name-of-the-unit).

Outputs to the log that the schedule rule (rule-number) is defined, added, edited, copied or deleted.

Outputs to the log that the schedule (the-full-name-of-the-unit) was defined.

Outputs to the log that the calendar (standard-week/year) was requested, acquired, or stored.

KAVV204-I

(window-name) was opened.

window-name was opened.

(S)

Outputs to the log that window-name opened.

KAVV205-I

(window-name) was closed.

window-name was closed.

(S)

Outputs to the log that window-name closed.

KAVV210-I

An auto refresh was performed on (window-name).

window-name was automatically updated.

(S)

Outputs to the log that window-name was automatically updated.

KAVV211-I

(menu-item) was selected.

menu-item was selected.

(S)

Outputs to the log that menu-item was selected.

KAVV212-I

The (button-name) button was pressed on [window-name] (window-type).

button-name was clicked on window-name (window-type).

(S)

Outputs to the log that button-name was clicked on window-name (window-type).

KAVV213-I

(menu-item) was selected on (window-name).

menu-item was selected on window-name.

(S)

Outputs to the log that menu-item was selected on window-name.

KAVV214-I

(menu-item) was checked.

menu-item was checked.

(S)

Outputs to the log that menu-item was checked.

KAVV215-I

The check of (menu-item) was released.

menu-item was unchecked.

(S)

Outputs to the log that menu-item was unchecked.

KAVV216-I

JP1/AJS3 - View was started. (Version: version, OS user name: OS-user-name)

JP1/AJS3 - View started.

(S)

Outputs to the log that JP1/AJS3 - View started.

KAVV217-I

JP1/AJS3 - View was stopped.

JP1/AJS3 - View terminated.

(S)

Outputs to the log that JP1/AJS3 - View terminated.

KAVV218-I

CONNECT [F (destination-IP-address, destination-port-number) L (source-IP-address, source-port-number)]

Connection to JP1/AJS3 - Manager succeeded.

(S)

Outputs to the log that succeeded in the connection between F (destination-IP-address, destination-port-number) and L (source-IP-address, source-port-number).

KAVV219-I

SEND: (data-0) (data-1) (data-2) (data-3) (data-4)

Data was sent to JP1/AJS3 - Manager.

(S)

Outputs to the log that data was sent to JP1/AJS3 - Manager.

KAVV220-I

RECV: (data-0) (data-1) (data-2) (data-3) (data-4)

Data was received from JP1/AJS3 - Manager.

(S)

Outputs to the log that data was received from JP1/AJS3 - Manager.

KAVV221-I

CLOSE [F (destination-IP-address, destination-port-number) L (source-IP-address, source-port-number)]

Connection to JP1/AJS3 - Manager was closed.

(S)

Outputs to the log that the connection between F (destination-IP-address, destination-port-number) and L (source-IP-address, source-port-number) was closed.

KAVV222-W

CLOSE ERR (maintenance-information) [F (destination-IP-address, destination-port-number) L (source-IP-address, source-port-number)]

Connection to JP1/AJS3 - Manager could not be closed.

(S)

Outputs to the log that the connection between F (destination-IP-address, destination-port-number) and L (source-IP-address, source-port-number) could not be closed.

KAVV223-W

WARNNIG: (maintenance-information)

An error that allows processing to continue occurred.

(S)

Outputs to the log a warning that an error that allows processing to continue has occurred.

KAVV224-E

MANAGER_ERR: (maintenance-information) / (maintenance-information)

This message reports details about an error response from JP1/AJS3 - Manager.

(S)

Outputs to the log the details about the error response from JP1/AJS3 - Manager.

KAVV225-E

The session token could not be released. ((maintenance-information) : (maintenance-information))

The login information could not be released.

(S)

Outputs to the log that the login information could not be released.

(O)

No action is required because this message is internal log information.

KAVV226-E

SESSION_ERR: (maintenance-information) / (maintenance-information) / (maintenance-information)

This message reports details about an error response from the destination.

(S)

Outputs the details about the error response from the destination.

(O)

No action is required because this message is internal log information.

KAVV227-I

REQ_START: (data-0)

The transmission of a request to JP1/AJS3 - Manager started.

(S)

Outputs to the log that the transmission of the request to JP1/AJS3 - Manager started.

KAVV228-I

REQ_END: (data-0)

A request to JP1/AJS3 - Manager from JP1/AJS3 - View was executed normally.

(S)

Outputs to the log that the correct response from the JP1/AJS3 - Manager was returned and the request to JP1/AJS3 - Manager from JP1/AJS3 - View was executed normally.

KAVV229-E

The registry could not be read. (maintenance-information)

This message indicates that an attempt to read the Windows registry has failed.

(S)

Outputs to the log the information that the registry could not be read. The system assumes the default for the communication option set in the registry.

(O)

Memory may be insufficient. If you want to apply the settings, terminate unnecessary applications and then restart JP1/AJS3 - View. If the error persists, the configuration of JP1/AJS3 - View may have been corrupted. Perform a repair installation.

KAVV230-E

The communication options could not be acquired.

The communication option could not be read.

(S)

Outputs to the log that the communication option could not be read.

Assumes the default and continues processing.

(O)

The configuration of JP1/AJS3 - View may have been corrupted. Perform a repair installation.

KAVV231-I

Communication options (receive timeout value: (value-1)ms, receive retry count: (value-2), connect retry count: (value-3), connect interval value: (value-4)ms)

This message reports the value of the communication option currently set for JP1/AJS3 - View.

(S)

Outputs the value of the communication option currently set for JP1/AJS3 - View to the log.

KAVV232-W

An invalid value is specified in the communication options. ((name) : (value))

name contains an invalid value.

(S)

Outputs to the log that an invalid value is specified.

The system uses the default to continue processing.

KAVV233-I

SDUMP: (data-0)

This message reports the data that is sent.

(S)

Outputs to the log the data that is sent.

KAVV234-I

RDUMP: (data-0)

This message reports the data that is received.

(S)

Outputs to the log the data that is received.

KAVV235-I

THROW CLIENT_EXCEPTION (exception-name)

The request to JP1/AJS3 - Manager from JP1/AJS3 - View could not be executed due to a communication error, an error that occurred in JP1/AJS3 - Manager, or other causes.

(S)

Outputs to the log that the request to JP1/AJS3 - Manager from JP1/AJS3 - View could not be executed due to a communication error or an error that occurred in JP1/AJS3 - Manager, or other causes.

KAVV236-I

There are no execution result details.

An attempt was made to refer to details about execution results but the results were not output.

The standard error output of the job may not be output, or the standard error output file could not be transferred.

(S)

Reports that an attempt was made to refer to the details about execution results but the results were not output.

(O)

Check whether the standard error output of the job is output or the standard error output file can be transferred.

KAVV237-I

An error occurred when updating. The window display might differ from the actual status.

The contents currently displayed may differ from the actual status due to an error that occurred while updating the Jobnet Monitor window or the Jobnet Editor window.

(S)

Reports that the contents currently displayed may differ from the actual status due to an error that occurred while updating the Jobnet Monitor window or the Jobnet Editor window.

(O)

Select Refresh and check the updated contents that are effective on these windows.

KAVV238-I

ER_SDUMP: (data-0)

This message reports data that was sent when an error occurred in JP1/AJS3 - Manager or a communication error occurred.

(S)

Outputs to the log the data that was sent when an error occurred in JP1/AJS3 - Manager or a communication error occurred.

KAVV240-I

ER_RDUMP: (data-0)

This message reports data that was received when a communication error or other errors occurred.

(S)

Outputs to the log the data that was received when a communication error or other errors occurred.

KAVV241-E

ENCODE_ERR: (character-code) : (maintenance-information)

Data could not be converted into the character string because an unsupported character code was specified.

(S)

Outputs to the log that data could not be converted into the character string because an unsupported character code was specified.

KAVV242-E

CONNECT_ERR ((maintenance-information) / (maintenance-information)) [F (destination-IP-address, destination-port-number) L (source-IP-address, source-port-number)]

This message reports an error or a disconnection that occurred during connection. For an error occurred during connection, L (source-IP-address, source-port-number) is not displayed.

(S)

Outputs to the log that the connection could not be made.

(O)

No action is required because this message is internal log information.

KAVV243-E

SEND_ERR ((maintenance-information) / (maintenance-information)) [F (destination-IP-address, destination-port-number) L (source-IP-address, source-port-number)]

Data could not be sent.

(S)

Outputs to the log that data could not be sent.

(O)

No action is required because this message is internal log information.

KAVV244-E

RECV_ERR ((maintenance-information) / (maintenance-information)) [F (destination-IP-address, destination-port-number) L (source-IP-address, source-port-number)]

Data could not be received.

(S)

Outputs to the log that data could not be received.

(O)

No action is required because this message is internal log information.

KAVV245-I

NETMONITOR_START

Connection started to be monitored.

(S)

Outputs to the log that connection started to be monitored.

KAVV246-E

NETMONITOR_ERR ((maintenance-information) : (maintenance-information) : (maintenance-information))

An error occurred while monitoring connection.

(S)

Outputs to the log that an error occurred while monitoring connection.

(O)

No action is required because this message is internal log information.

KAVV247-I

NETMONITOR_STOP

Monitoring of the connection terminated.

(S)

Outputs to the log that Monitoring of the connection terminated.

KAVV248-I

(number) units were selected.

This message indicates the number of selected units.

(S)

Outputs, to the log, the number of units selected for manipulating more than one unit.

KAVV249-E

The (details-of-editing) attempt for (type-of-defined-information) (full-unit-name or unit-name) failed.

This message indicates that the selected unit could not be manipulated.

(S)

Outputs, to the log, the information that the system could not manipulate more than one unit.

(O)

If an attempt to manipulate multiple units has failed, the Multi-execution Results dialog box appears. Check the details for each error.

KAVV250-E

No reference destination host is set, or the execution manager is unknown.

The reference destination unit cannot be displayed. The probable causes are:

If the target is a manager job group or manager jobnet:

A host name is not specified for Host to reference.

If the target is a remote jobnet:

The host name specified for Target manager is unknown.

(S)

Cancels processing.

(O)

Take action as shown below.

If the target is a manager job group or manager jobnet:

Specify a host name correctly for Host to reference.

If the target is a remote jobnet:

An error might have occurred during processing for transferring the definition from JP1/AJS3 - Manager at the connection destination to the host specified for Target manager and registering the definition for execution.

Check the Execution Result Details dialog box and the log output by JP1/AJS3 - Manager at the connection destination, and then correct the error.

KAVV251-E

No reference destination unit name is set.

The system cannot display the reference destination unit because the reference destination unit name is not defined for the manager job group or manager jobnet.

(S)

Cancels processing.

(O)

In the definition of the target manager job group or manager jobnet, correctly set a value for Unit to reference.

KAVV252-E

Reference destination unit name is invalid.

The system cannot display the reference destination unit because the reference destination unit name is specified incorrectly in the manager job group or manager jobnet.

(S)

Cancels processing.

(O)

In the definition of the target manager job group or manager jobnet, correctly set a value for Unit to reference. For Unit to reference, specify the complete unit name including the scheduler service name.

KAVV253-E

An unrestorable unit exists.

There is an unrestorable unit. The probable causes are:

When Original path is selected for Restore to, the hierarchical structure of the unit differs from the one when the unit was backed up.

The manager job group or manager jobnet is selected as the restoration destination.

A unit other than the event job is specified under the start condition.

(S)

Cancels processing.

(O)

Check the specification of the restoration destination.

If the start condition is specified for the restoration destination, in the Restore dialog box, add a file or files for which Event is displayed in the Type column in the Backup file field to Units to restore.

KAVV254-E

A recovery unit must be followed by another recovery unit.

You attempted to define other than a recovery unit after the recovery unit.

(S)

Cancels processing.

(O)

Return the Type setting to Recovery.

KAVV255-E

This operation cannot be performed on the manager jobnet.

You attempted an operation that was impossible for the manager jobnet.

(S)

Cancels processing.

(O)

Retry the operation for the reference destination jobnet for the manager jobnet.

KAVV256-E

A schedule cannot be defined in the manager jobnet.

You attempted to define a schedule in the manager jobnet.

(S)

Cancels processing.

(O)

Define schedule information in the reference destination jobnet for the manager jobnet.

KAVV257-E

The specified (job-group-name|jobnet-name|unit-name) was not found. (unit-name)

The specified unit could not be processed because it was not found or because the unit type was invalid. The probable causes are:

When the manager jobnet is displayed:

The specified unit does not exist.

The specified unit is not a root jobnet (remote jobnet is also unavailable).

When the manager job group is displayed:

The specified unit does not exist.

The specified unit is not a job group.

When restoring the saved status:

The job group that was selected in the tree area when the status was saved in the JP1/AJS3 - View window does not exist.

When starting an ajs command:

The unit specified in the -n option does not exist.

(S)

Cancels processing.

(O)

Correct the cause of the error.

If the status was saved, in the JP1/AJS3 - View window, choose Options, Save Status and then Clear Saved Status. Alternatively, save the status again.

KAVV258-I

(dialog-box-name) was opened.

dialog-box-name dialog box was opened.

(S)

Outputs to the log that dialog-box-name dialog box was opened.

KAVV259-I

(dialog-box-name) was closed.

dialog-box-name dialog box was closed.

(S)

Outputs to the log that dialog-box-name dialog box was closed.

KAVV261-E

Enter the job group name with up to 930 bytes, including the complete name of the upper unit.

A job group name that is too long is specified for the job group for which the calendar is to be referenced.

(S)

Cancels processing.

(O)

Enter the name of the job group for which you want to reference the calendar, using no more than 930 bytes including the full unit name of an upper-level unit.

KAVV262-E

An invalid unit is specified.

The specified unit could not be processed because it was invalid. The probable causes are:

When the saved status was restored:

The unit that was saved with the status was deleted and a unit with the same name and different unit type was created.

When an ajs command was started:

The unit specified in the -n option was not a job or jobnet.

The unit specified in the -n option was a manager jobnet.

(S)

Cancels processing.

(O)

Correct the cause of the error.

If the status was saved, in the JP1/AJS3 - View window, choose Options, Save Status and then Clear Saved Status. Alternatively, save the status again.

KAVV263-E

This operation cannot be executed because the execution ID cannot be acquired.

The operation cannot be executed because the execution ID of the latest status or the latest result cannot be acquired due to the jobnet being unregistered or other reasons.

This message also appears if the execution ID cannot be acquired from the selected unit because a JP1/AJS3 command was executed with a replacement character string (EXEC_ID) specified for the command argument.

(S)

Cancels processing.

(O)

Check whether the jobnet is registered for execution.

If this message appears when you attempt to execute a JP1/AJS3 command, check whether the jobnet is registered for execution. Then, see the description of the replacement character string (EXEC_ID) in 15.3.53 JP1/AJS3 Command Entry dialog box in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

KAVV264-I

There is a canceled operation because an error occurred.

Some operation cannot be executed due to an error that occurred in another processing before executing the operation.

(S)

Cancels processing.

(O)

Execute Refresh, and then retry.

KAVV265-E

A start condition cannot be set in the remote jobnet.

A start condition cannot be set in the remote jobnet.

(S)

Cancels processing.

(O)

Do not set the start condition in the remote jobnet.

KAVV266-E

You cannot use the current login information to connect. Log in again.

Connection could not be made because restarting the authentication server or logging out of View that started the current JP1/AJS3 - View invalidated the current login information.

(S)

Cancels processing and displays the Login screen.

(O)

Log in again. Repeat the same operation after you logged in since the operation immediately before is canceled.

KAVV267-E

An application required for this operation is not installed.

The selected operation cannot be executed because the required application is not installed.

(S)

Cancels processing.

(O)

Install the required application, and then restart JP1/AJS3 - View.

KAVV269-E

This operation cannot be executed for (unit-type).

The operation cannot be performed for the unit type indicated in unit-type.

The probable causes are:

An attempt was made to perform an operation that cannot be performed for unit-type.

(S)

Cancels processing.

(O)

Check whether the specified unit is correct and whether the executed operation is correct.

KAVV270-E

Select a (unit-type).

The unit cannot be used for the operation.

(S)

Cancels processing.

(O)

Select the correct unit.

KAVV271-E

To edit exclusively, you must cancel the registration or be in the suspended state.

The system cannot enter into the exclusive edit mode because the jobnet is being registered for execution.

(S)

Cancels processing, and then returns to the reference mode.

(O)

To enter into the exclusive edit mode, you must select Cancel Registration or Suspend for the root jobnet.

KAVV272-E

This operation cannot be executed for (unit-type) in the suspended state.

The operation cannot be done for the unit of unit-type in the suspended state.

(S)

Cancels processing, and then returns to the reference mode.

(O)

Select a unit other than unit-type, and then retry.

KAVV273-E

This operation cannot be executed in the suspended state.

The operation cannot be done in the suspended state.

(S)

Cancels processing.

(O)

Check the status of the root jobnet in the JP1/AJS3 - View window. We recommend you execute Refresh.

KAVV274-E

The specification with a regular expression is incorrect.

Search cannot be done because the specification with a regular expression is invalid.

(S)

Cancels processing.

(O)

When you specify the name to search in a regular expression, do not use a backslash (\) at the end of the character string.

KAVV275-I

Search results exceeded the max. displayable number, so some search results are not displayed.

The search results exceeded the maximum number of results that can be displayed preventing some results from being displayed.

(S)

Reports that the search results exceeded the maximum number of results that can be displayed preventing some search results from being displayed.

KAVV276-I

No unit satisfies the search condition.

There are no units that satisfy the search conditions.

(S)

Reports that there are no units that satisfy the search conditions.

KAVV277-E

The specified unit does not exist, so it is not selected.

The unit does not exist on JP1/AJS3 - View preventing it from being displayed correctly.

(S)

Cancels processing.

(O)

The unit information in JP1/AJS3 - View may differ from the one in JP1/AJS3 - Manager. We recommend you execute Refresh.

KAVV279-E

From the execution results list, select the schedule to be displayed.

The generation is not selected in the execution results list.

(S)

Cancels processing.

(O)

From the execution results list, display the generation you want to display.

KAVV284-E

The specified unit is now being created or deleted.

The unit is being created or deleted.

(S)

Cancels processing.

(O)

If the system displays this message while starting the window, wait for a while, and then start the window again.

If the system displays this message when you select a unit in the tree area of the JP1/AJS3 - View window, Jobnet Editor window, or Jobnet Monitor window, wait for a while, and then select the unit again.

KAVV285-E

The (value) line of the settings file (file-name) is incorrect.

The management file for wallpaper settings contains an error.

(S)

Ignores the setting on the line that contains the error and continues processing.

When an error is detected in the management file for the first time, the system outputs an error dialog box to notify the user of the error. For subsequent errors, the system outputs error information to the log.

(O)

See 15.4.40 Wall Paper dialog box in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide, and correct the error line in the management file used for setting the wallpaper.

KAVV286-E

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

An attempt to preview a file in the Wall Paper dialog box has failed because the file specified as the image file for the wallpaper was not found.

(S)

Cancels processing.

(O)

Check whether the specified file exists.

KAVV287-E

The number of data items in the settings file (file-name) exceeded 10,000 so registration failed.

The number of wallpaper items exceeded 10,000. No more data item can be registered.

(S)

Cancels processing.

(O)

Register the wallpaper items so that there are 10,000 or fewer of them.

KAVV288-E

The backup box could not be created, so backup is not possible.

The unit cannot be saved because an attempt to create a backup box has failed. The probable causes are:

The OS user mapped to the JP1 user at the connection destination does not have write permission for the directory for backup information.

The disk at the connection destination containing the directory for backup information does not have the free space required for creating a save box.

(S)

Cancels processing.

(O)

Correct the cause of the error, and then save the unit again.

KAVV289-E

The backup box cannot be accessed, so backup is not possible.

The unit cannot be backed up because the backup box cannot be accessed. The probable causes are:

The directory for backup information does not exist at the connection destination.

The OS user mapped to the JP1 user at the connection destination does not have permission to access the directory for backup information.

(S)

Cancels processing.

(O)

Correct the cause of the error, and then save the unit again.

KAVV290-E

An unexpected error occurred in start processing. (Detailed information: maintenance-information-1, maintenance-information-2)

An unexpected error occurred while JP1/AJS3 - View was starting.

(S)

Cancels processing.

(O)

Memory or free space on the disk may be insufficient. Terminate unnecessary applications, and then restart JP1/AJS3 - View.

If the error persists, the configuration of JP1/AJS3 - View may have been corrupted. Perform a repair installation.

KAVV291-E

Failed to start JP1/AJS3 - View. (Detailed information: maintenance-information)

JP1/AJS3 - View failed to start.

(S)

Cancels processing.

(O)

Memory or free space on the disk may be insufficient. Terminate unnecessary applications, and then restart JP1/AJS3 - View. Do not install JP1/AJS3 - View directly to the root level of the drive.

If the error persists, the configuration of JP1/AJS3 - View may have been corrupted. Perform a repair installation.

KAVV293-E

JP1/AJS3 - View is installed in an invalid folder.

Started JP1/AJS3 - View is not installed in the correct folder.

(S)

Cancels processing.

(O)

Make sure that the JP1/AJS3 - View startup file (ajs.exe) is in the following folder:

JP1/AJS3 - View-installation-folder\bin

KAVV295-E

An option specified in ajs2conf is too long.

JP1/AJS3 - View cannot start because an option that is too long is specified for jreparam for ajs2.conf.

(S)

Cancels processing.

(O)

Compare ajscon2.conf against ajs2.conf.model to check for unnecessary options that have been specified.

KAVV296-E

The command line parameter is too long.

JP1/AJS3 - View cannot start because the command line parameter specified for the ajs command is too long.

(S)

Cancels processing.

(O)

Specify the command line parameter correctly, and then restart JP1/AJS3 - View.

KAVV297-E

An attempt to read the product information failed. (Detailed information: function-name, return-value)

An attempt to read product information has failed.

(S)

Cancels processing.

(O)

If the system time has been set to a value earlier than the installation time, restore the time, and then retry the operation.

For any other case, perform an overwrite installation, and then retry the operation.

If this message was output after an overwrite installation, uninstall the product, and then retry the operation.

KAVV307-Q

Are you sure you want to release the changes in selected (number-of-units) units?

This message asks whether you want to release the temporary changes in multiple units.

(S)

Waits for a response.

(O)

Click Yes to release the changes. Click No to cancel.

KAVV308-Q

Are you sure you want to delete the (unit-name)?

The system confirms whether you want to delete the unit.

(S)

Waits for a response.

(O)

Click Yes to delete or No to cancel.

KAVV309-Q

Are you sure you want to cancel the registration of the (unit-name)?

The system confirms whether you want to unregister the unit.

(S)

Waits for a response.

(O)

Click Yes to unregister or No to cancel.

KAVV310-Q

An attempt to (operation) (unit-name) failed. Are you sure you want to continue?

The system could not manipulate the units. The system asks whether you want to continue processing.

(S)

Waits for a response.

(O)

Click Yes to continue. Click Yes for all to continue processing and prevent this message from being displayed again. Click No to cancel.

KAVV311-Q

Are you sure you want to cancel the registration of the selected (n) units?

The system asks whether you want to unregister the units.

(S)

Waits for a response.

(O)

Click Yes to unregister or No to cancel.

KAVV312-Q

Are you sure you want to prohibit execution of the selected (n) units?

The system asks whether you want to cancel the execution of the units.

(S)

Waits for a response.

(O)

Click Yes to cancel or No to continue execution.

KAVV313-Q

Are you sure you want to set the hold attribute for the selected (n) units?

The system asks whether you want to define the suspension attribute of more than one unit.

(S)

Waits for a response.

(O)

Click Yes to define or No to cancel.

KAVV314-Q

Are you sure you want to release the selected (n) units?

The system asks whether you want to release the suspension of more than one unit.

(S)

Waits for a response.

(O)

Click Yes to release or No to cancel.

KAVV315-Q

Are you sure you want to forcibly end the selected (n) units?

The system asks whether you want to forcibly terminate more than one unit.

(S)

Waits for a response.

(O)

Click Yes to forcibly terminate or No to cancel.

KAVV316-Q

Are you sure you want to interrupt the selected (n) units?

The system asks whether you want to cancel more than one unit.

(S)

Waits for a response.

(O)

Click Yes to cancel or No to continue.

KAVV317-E

The operation is not possible for the specified status or result.

The operation is impossible because the generation of the specified status or result does not exist for the specified jobnet.

(S)

Cancels processing.

(O)

Before you specify the status of the result, make sure that the status for the corresponding generation is displayed in the JP1/AJS3 - View window.

KAVV318-Q

Are you sure you want to prohibit execution of (unit-name) (execution-ID)?

The system confirms whether you want to cancel the execution of the unit.

(S)

Waits for a response.

(O)

Click Yes to abort the execution or No to cancel.

KAVV319-Q

Are you sure you want to release the changes in (unit-name) (execution-ID)?

The system confirms whether you want to release the temporary schedule change of the unit.

(S)

Waits for a response.

(O)

Click Yes to release the temporary schedule change or No to cancel.

KAVV320-Q

Are you sure you want to set the hold attribute for (unit-name) (execution-ID)?

The system confirms whether you want to set the hold attribute for the unit.

(S)

Waits for a response.

(O)

Click Yes to set the hold attribute or No to cancel.

KAVV321-Q

Are you sure you want to release (unit-name) (execution-ID)?

The system confirms whether you want to release the hold attribute for the unit.

(S)

Waits for a response.

(O)

Click Yes to release the hold attribute or No to cancel.

KAVV322-Q

Are you sure you want to interrupt (jobnet-name) (execution-ID)?

The system confirms whether you want to interrupt the jobnet.

(S)

Waits for a response.

(O)

Click Yes to interrupt or No to cancel.

KAVV323-Q

Are you sure you want to forcibly end (unit-name) (execution-ID)?

The system confirms whether you want to forcibly terminate the unit.

(S)

Waits for a response.

(O)

Click Yes to forcibly terminate or No to cancel.

KAVV324-Q

Are you sure you want to delete the schedule rule (rule-number)?

The system confirms whether you want to delete the schedule rule.

(S)

Waits for a response.

(O)

Click Yes to delete or No to cancel.

KAVV325-Q

Are you sure you want to save the window status?

The system confirms whether you want to save the window status.

(S)

Waits for a response.

(O)

Click Yes to save the status or No to cancel.

KAVV326-Q

Are you sure you want to clear the saved status?

The system confirms whether you want to clear the saved status of the window.

(S)

Waits for a response.

(O)

Click Yes to clear or No to cancel.

KAVV327-Q

Are you sure you want to delete the (unit-name)?

The system confirms whether you want to delete the unit from the Jobnet Editor window.

(S)

Waits for a response.

(O)

Click Yes to delete or No to cancel.

KAVV328-Q

Are you sure you want to delete the selected (number) units?

The system confirms whether you want to delete the unit.

(S)

Waits for a response.

(O)

Click Yes to delete or No to cancel.

KAVV329-Q

This operation can be done only during exclusive editing. Are you sure you want to edit exclusively?

The system confirms whether you want to enter into the exclusive edit mode.

(S)

Waits for a response.

(O)

Click Yes to edit exclusively or No to cancel.

KAVV330-Q

To delete the start condition, the root jobnet in the exclusive-editing status must be displayed in the map area. Are you sure you want to continue?

The system confirms whether you want to delete the start condition.

(S)

Waits for a response.

(O)

Click Yes to delete or No to cancel.

KAVV332-Q

The calendar has been changed. Are you sure you want to save it?

The system confirms whether you want to save the calendar definition.

(S)

Waits for a response.

(O)

Click Yes to save or No to cancel.

KAVV333-Q

To create a start condition, the root jobnet in the exclusive-editing status must be displayed in the map area. Are you sure you want to continue?

The system confirms whether you want to create a new start condition.

(S)

Waits for a response.

(O)

Click Yes to create a new start condition or No to cancel.

KAVV334-Q

Are you sure you want to log out?

The system confirms whether you want to terminate JP1/AJS3 - View.

(S)

Waits for a response.

(O)

Click Yes to terminate or No to cancel.

KAVV335-Q

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

The system confirms whether you want to terminate JP1/AJS3 - View.

(S)

Waits for a response.

(O)

Click Yes to terminate or No to cancel.

KAVV336-Q

The connection with the Manager was severed. Do you want to re-connect?

The system confirms whether you want to reconnect to the manager.

(S)

Waits for a response.

(O)

Click Yes to reconnect or No to cancel.

KAVV337-Q

Another user changed the schedule while you were editing it. Are you sure you want to save the edited settings?

The system confirms whether you want to overwrite the schedule.

(S)

Waits for a response.

(O)

Click Yes to overwrite or No to cancel.

KAVV338-Q

Registration cannot be executed because the specified job group does not exist or you are not authorized to register it. Are you sure you want to define the schedule?

The system confirms whether you want to define the schedule.

(S)

Waits for a response.

(O)

Click Yes to define or No to cancel.

KAVV339-Q

The changed data will be lost. Are you sure you want to save it?

The system confirms whether you want to save the calendar data.

(S)

Waits for a response.

(O)

Click Yes to save or No to cancel.

KAVV340-Q

Copying the schedule of an upper jobnet to a lower jobnet will delete the existing schedule (if any) of the lower jobnet. Are you sure you want to copy?

The system confirms whether you want to overwrite the schedules that already exist when you copy schedules from the higher-level jobnet.

(S)

Waits for a response.

(O)

Click Yes to copy or No to cancel.

KAVV344-Q

The search might take a long time. Are you sure you want to search?

The system confirms whether you want to search the lower-level units or to search without specifying the name.

(S)

Waits for a response.

(O)

Click Yes to continue to search or No to cancel.

KAVV345-Q

The selected passing information (regular-expression, output-macro-variable) will be deleted. Are you sure you want to continue?

Confirm whether to delete the passed information.

(S)

Waits for a response.

(O)

Click Yes to delete the passed information or No to cancel.

KAVV346-Q

All defined schedule rules will be deleted because the (Depends on upper-level jobnet) check box is selected. Are you sure you want to continue?

(S)

Waits for a response.

(O)

Click Yes to continue the processing. Click No to cancel the processing.

KAVV350-E

When you register for execution a jobnet that is directly under a planning group, you can only perform fixed registration specified with a fixed schedule period.

You cannot perform the scheduled or immediate registration for the jobnet directly under the planning group. You also cannot perform fixed registration with the number of future generations specified.

(S)

Cancels processing.

(O)

Perform the fixed registration for the jobnet directly under the planning group with the fixed schedule period specified.

KAVV351-E

When you add a planning group or a jobnet that is directly under a planning group to a schedule, you can only perform fixed registration specified with a fixed schedule period.

You cannot add the planning group and the jobnet directly under the planning group to a schedule.

(S)

Cancels processing.

(O)

To add a schedule, do the following for the jobnet directly under the planning group.

When adding a schedule based on the existing schedule:

Register the jobnet for fixed execution with a new schedule period specified.

When adding a single schedule independent of the existing schedule:

Add the jobnet to the next schedule in the Change plan field.

You cannot cancel changes in the added schedule. To cancel the changes, you must cancel the execution.

KAVV352-E

Today is shown because the specified date (date) cannot be shown.

The specified date could not be displayed on the Daily Schedule or Monthly Schedule window.

(S)

Continues processing. The displayed date is assumed for Today.

(O)

Check whether the window from which this window is opened displays a date outside the range from the year 1994 to the year 2036.

KAVV353-E

Directly under a planning group, you can only create a jobnet or remote jobnet.

You can only create the unit of the root jobnet and the root remote jobnet directly under the planning group.

(S)

Cancels processing.

(O)

To create the unit directly under the planning group, create the root jobnet or the root remote jobnet.

KAVV354-E

In the cancellation period, for the end day specify a day after the start day.

You cannot cancel registration for the specified period of time because an end date earlier than the start date is specified for Canceling period.

(S)

Cancels processing.

(O)

To cancel registration by using Specify period, specify an end date after the start date for Canceling period.

KAVV355-E

The schedule for canceling the registration does not exist.

There is no schedule to unregister.

(S)

Cancels processing.

(O)

Check whether there is a schedule within the specified period and unregister it again.

KAVV356-E

Directly under a planning group, you can only paste a jobnet or remote jobnet.

You can only paste the unit of the root jobnet and the root remote jobnet directly under the planning group.

(S)

Cancels processing.

(O)

To paste the unit directly under the planning group, paste the root jobnet or the root remote jobnet.

KAVV357-Q

The fixed schedule period is over (value) months. Are you sure you want to register for execution?

This message confirms whether you want to register the jobnet for execution. The fixed schedule period for the fixed registration exceeds the period specified by the user. Check whether the correct value is entered.

(S)

Cancels processing.

(O)

Click Yes to register or No to cancel.

KAVV358-E

A maximum of 50 items can be added to the [User color] list.

You can create up to 50 display colors.

(S)

Cancels processing.

(O)

Delete unnecessary display colors, and then re-create display colors.

KAVV359-E

A color with the specified RGB element already exists, so you cannot specify the RGB element.

You cannot create more than one display color that has the same RGB element.

(S)

Cancels processing.

(O)

Specify a unique RGB value that is not the same for an existing color.

KAVV360-E

A color with the same name already exists, so you cannot specify the name.

You cannot create more than one display color that has the same name.

(S)

Cancels processing.

(O)

Specify the character string that is not the same for an existing color.

KAVV361-Q

The specified color (color-name) is in use. Are you sure you want to delete it?

This message confirms you to delete the display color specified by the user. An attempt is made to delete the colors currently specified for the execution status and delays. If they are deleted, the system applies the default.

(S)

Cancels processing.

(O)

Click Yes to delete or No to cancel.

KAVV363-E

Select an item in the (list-name).

No item is selected in the list indicated in list-name.

(S)

Cancels processing.

(O)

Select an item in the list indicated in list-name:

For the Select Color dialog box, select the item from Available colors.

For the Used Variables dialog box, select the item from Variables.

KAVV364-E

The available file extensions are .jpg (.JPG) and .gif (.GIF). Specify a valid file name.

An extension other than .jpg (.JPG) or .gif (.GIF) was specified for the image file used as wallpaper.

(S)

Cancels processing.

(O)

Specify .jpg (.JPG) or .gif (.GIF) for the extension of the image file used as wallpaper.

KAVV365-Q

Are you sure you want to end specifying wallpaper settings without saving the settings?

This message confirms you to terminate the wallpaper setting without saving the settings.

(S)

Waits for a response.

(O)

Click Yes to terminate or No to cancel.

KAVV366-Q

The specified file (file-name) was not found. Are you sure you want to use the specified file name for wallpaper?

This message confirms whether you want to use the specified file name for the wallpaper even if the file name does not exist.

(S)

Waits for a response.

(O)

Click Yes to use or No to cancel.

KAVV367-E

Specify both start and end days in the cancellation period.

Both the start and end dates must be specified for Canceling period when you cancel registration for the specified period of time.

(S)

Cancels processing.

(O)

To cancel registration for the specified period of time, specify both the start and end dates for Canceling period.

KAVV368-Q

A relation line cannot be pasted when Paste (Extension) is executed under the start condition. Are you sure you want to continue?

This message asks whether you want to execute Paste (Extension).

When you execute Paste (Extension) under the start condition, relation lines cannot be pasted. The relative position of the unit on the coordinate grid can be maintained when the unit is pasted.

(S)

Waits for a response.

(O)

Click Yes to execute Paste (Extension) or No to cancel.

KAVV369-E

The (value) line of the settings file (file-name) is incorrect.

The wallpaper settings file or custom job extended settings file contains an error.

(S)

File extensions other than .cjx

Ignores the setting on the line that contains the error and continues processing.

When an error is detected in the settings file for the first time, the system outputs an error dialog box to notify the user of the error. For subsequent errors, the system outputs error information to the log.

File extension .cjx

The Monitor Details dialog box appears without the customized settings.

(O)

File extensions other than .cjx

Display the Wall Paper dialog box and click the OK button to delete the definition containing the error.

File extension .cjx

Amend the line indicated in value in the custom job extended settings file indicated in file-name, and then open the Monitor Details dialog box again.

KAVV370-Q

The optimization might take a long time. Discontinuation of processing during optimization is possible. Are you sure you want to optimize?

This message confirms whether you want to perform optimization.

(S)

Waits for a response.

(O)

Click Yes to optimize or No to cancel.

KAVV371-I

Now optimizing. You can use the Cancel button to discontinue the processing.

Optimization is proceeding. Select Cancel to cancel the optimization.

(S)

Continues processing.

(O)

Click Cancel to cancel the processing.

KAVV372-E

The number of data items in the settings file (file-name) exceeded 9,999 so registration failed.

You cannot register wallpaper settings for the current connection destination because the number of hosts on which wallpaper can be set exceeded 9,999.

(S)

Cancels processing.

(O)

See Additional information in 15.4.40 Wall Paper dialog box in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide, and delete unnecessary lines from the management file used for setting the wallpaper.

KAVV373-Q

The common user profile of the connection destination will be downloaded. Are you sure you want to overwrite all of the settings for (user-name) on this JP1/AJS3 - View machine?

The system asks whether you want to download the user-common profile.

(S)

Waits for a response.

(O)

Click Yes to download the user-common profile at the connection destination, or No to cancel.

KAVV374-Q

Are you sure you want to upload the setup of (user-name) on this JP1/AJS3 - View machine as the common user profile on the connection destination?

The system asks whether you want to upload the settings of (user-name) of this JP1/AJS3 - View host as the common user profile at the connection destination.

(S)

Waits for a response.

(O)

Click Yes to upload the settings as the user-common profile or No to cancel.

KAVV375-I

The (operation) ended normally.

This message indicates that uploading or downloading ended normally.

(S)

Reports that uploading or downloading ended normally.

KAVV376-E

The common user profile is not uploaded at the connection destination.

The common user profile cannot be downloaded because it has not been uploaded to JP1/AJS3 - Manager at the connection destination.

(S)

Cancels processing.

(O)

Wait until the common user profile is uploaded, and then download it.

KAVV377-Q

All the common user profile values of the connection destination are default values. Are you sure you want to continue downloading?

All of the settings of the common user profile at the connection destination are default values. If processing is continued, all settings will become the default values. The system asks whether you want to download the common user profile the settings using the defaults.

(S)

Waits for a response.

(O)

Click Yes to download the user-common profile at the connection destination or No to cancel.

KAVV378-E

A required option is missing. [option]

Options required for the ajs command are missing.

(S)

Cancels processing.

(O)

Specify the required option, and then re-execute the ajs command. The combinations of required options are as follows:

-v monitor -n jobnet or full-jobnet-name -l execution-ID

-v monitor -n jobnet or full-jobnet-name -m state or result

KAVV379-E

An options that cannot be specified simultaneously is specified. [option]

Options that cannot be specified together are specified.

(S)

Cancels processing.

(O)

Specify the -l or -m option, and then re-execute the ajs command.

KAVV380-E

The login information file (file-name) is not found. Detailed information: detailed-information-1, detailed-information-2

The file specified as the login information file cannot be found.

(S)

Cancels processing.

(O)

Check whether the login information file specified in the -a option has been created in the following location:

JP1/AJS3 - View-installation-folder \conf\

KAVV381-E

Specify the value of login information (keyword-name) in the login information file (file-name).

Automatic login has failed because a value for the keyword indicated in keyword-name was not specified in the login information file.

(S)

Cancels automatic login, and displays the Login screen.

(O)

Enter the necessary information in the Login screen, and then log in.

Also check the contents of the login information file according to ajs in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

KAVV382-E

An error occurred during input to the login information file (file-name). Detailed information: detailed-information-1, detailed-information-2

An error occurred during input to the login information file. The probable causes are:

You do not have access permission for files or directories.

Another program is editing the login information file.

(S)

Cancels processing.

(O)

Correct the cause of the error.

KAVV383-E

The maximum number of selectable units for the specified operation is (number-of-units).

number-of units indicates the maximum number of units that can be selected to perform the specified operation.

(S)

Cancels processing.

(O)

Select as many units as or fewer units than the maximum number indicated in number-of-units, and then perform the operation.

KAVV384-Q

The monitor start delay for the specified jobnet cannot be changed because the jobnet is being executed. Are you sure you want to apply the changes other than the monitor start delay change?

Since the status of the specified jobnet is running, start delay monitoring cannot be changed. The system asks whether you want to change items (such as termination delay monitoring or jobnet monitoring) other than start delay monitoring.

(S)

Waits for a response.

(O)

Click Yes to change items other than start delay monitoring, or click No in order not to change delay monitoring temporarily.

KAVV385-E

The (field-name) is duplicated.

You cannot specify field-name more than one.

(S)

Cancels processing.

(O)

Specify a unique name for field-name, and then retry.

For the Register Tool dialog box, specify the name in Entry name.

For the JP1/AJS3 Command Entry dialog box, specify the name in Entry name.

For the Register Passing Information dialog box, specify the name in Variable.

For the Register for Release dialog box, specify the name in Release ID.

KAVV386-Q

The settings have been changed. Are you sure you want to save the settings?

This message asks whether you want to save the changes to the settings.

(S)

Waits until the operator responds.

(O)

If you want to save the changes, Click Yes. If you do not want to save the changes, Click No. If you want to cancel the changes, Click Cancel.

KAVV387-E

An attempt to start the tool failed. (Entry name:(registered-name), Command:(start-command-name))

The tool could not be started. The probable causes are:

The executable file does not exist.

You do not have the permissions required to execute the executable file.

The PATH environment variable is not set correctly.

A space (in Japanese systems, a Hankaku space) was not placed before and after a replacement character string.

(S)

Cancels processing.

(O)

Correct the cause of the error, and then start the tool again.

KAVV388-I

The tool was started. (Entry name:( registered-name), Command:( start-command-name))

The tool was started.

(S)

Reports that the tool was started.

KAVV389-E

The tool cannot be started because a character that cannot be used in the character string for replacement is included.

The tool cannot be started because a replacement character string (UNIT_NAME) is specified for a registered start command and the full unit name to be replaced includes a character that cannot be used for starting a tool. Characters that cannot be used for starting a tool are as follows (in Japanese systems, these are Hankaku characters):

" & ' * < > ? [ \ ] ^' {|} ~

(S)

Cancels processing.

(O)

Use another method to execute the command.

KAVV390-E

Passing information cannot be set in (unit-type).

An attempt was made to register for execution or add the unit indicated in unit-type with inherited information specified.

(S)

Cancels processing.

(O)

Do not specify inherited information when registering the unit indicated in unit-type for execution or when it is to be added.

KAVV392-I

No variables have been used.

This message indicates that no variables have been used.

Additional information

Variables are displayed for the following units:

Subsequent jobs that reference inherited information.

Judgment jobs for which Variable (char.) or Variable (number) is selected for the judgment type.

Variables are not displayed for jobs contained in a remote jobnet.

(S)

Outputs the fact that no variables have been used to the log.

KAVV393-I

There is no inherited result.

This message indicates that there is no inherited result.

Additional information

Inherited results are displayed for the following units:

A root jobnet that was registered for execution or added with inherited information specified.

Subsequent jobs that reference inherited information.

Inherited results are not displayed for a preceding job for which inherited information is set.

(S)

Outputs the fact that there is no inherited result to the log.

KAVV394-E

An inherited result cannot be displayed for the (unit-type).

An attempt was made to display an inherited result for the unit indicated in unit-type.

(S)

Cancels processing.

(O)

Display the inherited result for a unit other than unit-type.

KAVV397-E

To change a recovery attribute, a judgment job (judgment-job-name) must be followed by another recovery unit.

The dependent unit cannot be changed to a recovery job because a unit that is not a recovery unit is associated with the unit that follows the judgement job.

(S)

Cancels processing.

(O)

Set the type back to Normal and close the Define Details dialog box. Then change all the units that follow the judgement job to recovery units. Finally, change the dependent job to a recovery job again.

KAVV399-E

An error occurred in inter-process communication.

An error occurred during inter-process communication.

(S)

Cancels inter-process communication. As a result, the following function does nor work correctly:

Changing the startup method of the Jobnet Monitor window

(O)

Terminate all the running JP1/AJS3 - View programs. Then, if the following file exists, delete it manually:

For Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\conf\port.conf

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

For Windows Server 2003 or Windows XP Professional

JP1/AJS3 - View-installation-folder\conf\port.conf

KAVV400-E

Cannot connect to the connection destination host (host-name) or JP1/AJS3 service on the connection destination host. Detailed information: port-number, IP-address

The host or the JP1/AJS3 service of the host cannot be connected. The probable causes are:

The JP1/AJS3 service of the host has not started.

The definition of the port number (jp1ajs2monitor) differs from the definition of the port number for the host.

The host is not started.

The host is in the status in which network connection is impossible.

If a firewall is between the system and the host, it does not allow data to pass. For details about the direction in which data passes, see A.2 Directions of traffic through a firewall in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

If the JP1/Base settings at the connection destination specify the IP binding method on the receiving side for physical hosts, connection was attempted using an IP address that was not bound to a physical host or any logical host.

(S)

Cancels processing.

(O)

Correct the error, and then retry.

If connection was attempted using an IP address that was not bound to a physical host or any logical host at the connection destination, connect with a bound IP address or define jp1hosts or jp1hosts2 information at the connection destination. For details about defining jp1hosts or jp1hosts2 information, see the Job Management Partner 1/Base User's Guide.

Connection may be impossible when the connection destination host is busy. If the target JP1/AJS3 - Manager is connected to more than one unit of JP1/AJS3 - View, specify the retry count. The default is 3.

How to set the retry count:

Create the value DWORD of the name CONN_RETRYCOUNT for the registry key HKEY_LOCAL_MACHINE\SOFTWAER\HITACHI\JP1AJS2V, and set the value for the retry count.

KAVV401-E

The data to the connection destination could not be sent or received.

The system failed to send or receive data with JP1/AJS3 - Manager. Alternatively, because the IP address of the connecting JP1/AJS3 - View host was not registered in the manager connection permission configuration file on the destination manager host, connection to the manager host failed.

(S)

Cancels processing.

(O)

A temporary problem may have occurred on the network. If this message appears during update or other operations, update the information, and then check whether your update or operations have become effective. If they do not take effect or if you are obtaining data, retry the same operation.

If the KAVS8040-E message was output to the integrated trace log on the destination manager host, take the corrective action specified in the KAVS8040-E message.

If this message appears frequently, an error may have occurred in JP1/AJS3 - Manager. Use log information such as the Windows event log or the syslog file on the host of JP1/AJS3 - Manager to examine the error. Then, correct the error according to the results. For details on the contents of the log file, see 1.2 Types of log information and storage locations in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

If this message appears immediately after you logged on to the system when the connection destination host is a Windows host, a desktop heap may be too small at the connection destination host. To prevent the consumption of the desktop heap at the connection destination host, check and correct the following settings: REUSELOGON and LOGONSHMAX environment setting parameters. For details about the environment setting parameters, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVV402-E

A timeout occurred while waiting for the response from the connection destination. Detailed information: maintenance-information-1, maintenance-information-2

No response could be received from JP1/AJS3 - Manager within the waiting time.

The default waiting time is 30 minutes. However, note that this message might appear before the waiting time expires if JP1/AJS3 - Manager is disconnected due to the automatic disconnection setting for a network device or due to a temporary network failure.

(S)

Cancels processing.

(O)

If this message appears before the waiting time expires after operation of JP1/AJS3 - View, check that the network status is correct, and then try the operation again.

If this message appears after the waiting time has elapsed after operation of JP1/AJS3 - View, check the processing status of the operation performed by JP1/AJS3 - View.

The following describes how to set the waiting time.

How to set the waiting time:

Create the value DWORD of the name REC_TIMEOUT for the registry key HKEY_LOCAL_MACHINE\SOFTWAER\HITACHI\JP1AJS2V, and set the value for the timeout (seconds). The maximum value of REC_TIMEOUT in hexadecimal is 00093A80 (604,800 in decimal).

Cautionary note

Do not specify zero (0).

KAVV403-E

The transmitted data could not be encoded. (character-code)

The system failed to encode the send/receive data.

(S)

Cancels processing.

(O)

Check whether the character code is correctly defined for JP1/AJS3 - Manager.

KAVV405-E

Processing was interrupted because an error was detected in the received data. Confirm that the port number (jp1ajs2monitor) is the same at the connection destination. Details: maintenance-info, maintenance-info

The system detected that an invalid protocol data was sent from JP1/AJS3 - Manager.

(S)

Cancels processing.

(O)

Check whether the definition of the port number (jp1ajs2monitor) matches the definition for the host.

KAVV406-E

The version of the connection destination is unknown.

Detailed information: maintenance-information-1, maintenance-information-2

The version of the connection destination JP1/AJS3 - Manager is unknown.

(S)

Cancels processing.

(O)

Check whether JP1/AJS3 - Manager is installed correctly in the connection destination host.

KAVV407-E

The character code for the connection destination is unknown. Detailed information: maintenance-information-1, maintenance-information-2

The character code for the connection destination JP1/AJS3 - Manager is unknown.

(S)

Cancels processing.

(O)

Check whether JP1/AJS3 - Manager is installed correctly in the connection destination host.

KAVV408-E

Login information cannot be obtained.

The login information cannot be acquired.

(S)

Cancels processing.

(O)

Collect the following data and contact the system administrator.

A hardcopy of the window

JP1/AJS3 - View log

JP1/AJS3 - Manager log

JP1/Base log (If the authentication server is on another host, also collect the JP1/Base log on the authentication server on that host.)

For details on how to collect the logs, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

For details on how to collect the log of JP1/Base, see the Job Management Partner 1/Base User's Guide.

KAVV409-E

Information about the connection destination cannot be obtained.

Detailed information: maintenance-information-1, maintenance-information-2

The system could not obtain information about the connection destination.

(S)

Cancels processing.

(O)

Check whether JP1/AJS3 - Manager is installed correctly in the connection destination host.

KAVV411-E

Invalid data was detected. Confirm the setting for the Manager's character code-set. (character-code-set)

An invalid data containing an invalid character code set that JP1/AJS3 - View cannot display is detected.

(S)

Cancels processing.

(O)

After logging out, check the following for the setting of the destination JP1/AJS3 - Manager:

Check whether the character code set for the JP1/AJS3 - Manager OS matches the code for JP1/AJS3 - Manager.

Check whether the old data remains after changing the settings of the character code set for JP1/AJS3 - Manager.

Check whether the character code set in the definition of the remote jobnet matches the one for the manager to execute.

Take the same action as above if the system does not display this message and the characters displayed by JP1/AJS3 - View become garbled.

KAVV412-E

The host name is specified incorrectly.

The host name specified as the destination host name can not be resolved.

(S)

Cancels processing.

(O)

Enter the correct host name or the IP address.

KAVV413-E

Invalid data was detected in the file (file-name) at the connection destination.

Invalid data was detected in the common user profile at the connection destination.

(S)

Cancels processing.

(O)

Make sure that in Shift-JIS is coded in the common user profile at the connection destination.

For details on the path to the directory for common user profiles, see 11.1.2 Using common user profiles in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

KAVV414-I

ENUM_RECV : (received-information)

This message indicates that data from JP1/AJS3 - Manager was received.

(S)

Outputs, to the log, information indicating that data from JP1/AJS3 - Manager was received.

KAVV415-I

InterProcess : (communication-data)

This message indicates that inter-process communication is in progress.

(S)

Outputs, to the log, information indicating that inter-process communication was in progress.

KAVV416-W

InterProcess : (maintenance-information)

This message indicates that an error that allows further processing occurred during inter-process communication.

(S)

Outputs, to the log, information indicating that an error that allows further processing occurred during inter-process communication.

(O)

No action is required because this message is internal log information.

KAVV417-E

InterProcess : (maintenance-information)

This message indicates that an error occurred during inter-process communication.

(S)

Outputs, to the log, information indicating that an error occurred during inter-process communication.

(O)

No action is required because this message is internal log information.

KAVV418-E

The specified operation cannot be performed because acquisition of the manager host information failed.

This operation cannot be performed because acquisition of manager host information failed.

(S)

Cancels processing.

(O)

Acquisition of some information might have failed when you logged in to JP1/AJS3 - Manager. Use log information such as the Windows event log or the syslog file on the manager host to examine the error.

Correct the error according to the results, restart JP1/AJS3 - View, and then try the operation again.

For details about types of log information and storage locations, see 1.2 Types of log information and storage locations in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

For details about log information, see C. Log Information in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KAVV419-E

The specified operation cannot be performed by this version of JP1/AJS3 - View.

This operation cannot be performed in the version of JP1/AJS3 - View being used.

(S)

Cancels processing.

(O)

Data that was acquired when you logged in to JP1/AJS3 - Manager cannot be processed in the version of JP1/AJS3 - View being used. Use an appropriate version of JP1/AJS3 - View to try the operation again.

For details about version compatibility between JP1/AJS3 - Manager and JP1/AJS3 - View, see 8.1.2 Version compatibility between JP1/AJS - Manager and JP1/AJS - View in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide and A. JP1/AJS3 - View Compatibility in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

KAVV430-Q

The number of saved generations for a registered jobnet has been reduced. When there is a large number of saved generations that have been reduced, the performance of the jobnet the next time the jobnet is started or the next time the starting conditions for the jobnet are met is affected. Are you sure you want to specify this setting?

Decide whether you really want to change the number of saved generations. This message is displayed if you have reduced the number of saved generations in the Define Details dialog box for a root jobnet that has already been registered for execution.

JP1/AJS3 - Manager deletes the extra number of generations according to the changed setting of saved generations when the jobnet starts execution or when the start condition is established.

With regard to the processing for deleting generations, the amount of processing increases in proportion to the number of detected generations#. If the deletion of generations takes a long time, processing that would normally be executed during that time must wait.

Accordingly, reducing the number of saved generations of a jobnet that has already been registered for execution could delay either the start of jobnet execution, or starting of the jobnet when the start condition is established.

#

For a version-upgrade installation from version 8 or earlier, reducing the number of saved generations of a jobnet with a start condition already registered for execution most strongly affects the number of execution-result generations to be deleted. Specifically:

NER = RN x (NSG + 1), where NER is the number of execution-result generations to be deleted, RN is the reduction in the number of saved generations, and NSG is the number of saved generations before the change.

(S)

Waits for a response.

(O)

Choose whether to change the number of saved generations. Click Yes to change the number. Click No to cancel the operation.

If you reduce the number of saved generations of a jobnet that has already been registered for execution, you must be careful not to increase the number of generations that will be deleted. Specifically, change the setting after you cancel registration of the execution results either one generation at a time or at a specified interval at jobnet startup during a period when the start condition has been established or registration for execution does not operate.

For details about the number of saved generations, see 4.2.3 Jobnet generation management in the manual Job Management Partner 1/Automatic Job Management System 3 Overview and 7.2 Relationship between number of logs to keep and performance in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

If you want to hide a confirmation message, you can suppress output of the message by customizing the file on JP1/AJS3 - View. If required, specify the jajsStopQuestDialog keyword in the file from JP1/AJS3 - View. For details about the customization method, see 11.3.10 Suppressing certain confirmation messages in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

KAVV432-Q

Are you sure you want to delete the relation line? (Source:connection-source-unit-name, Destination:connection-destination-unit-name)

Confirm whether to delete the relation line.

(S)

Waits for a response.

(O)

Click Yes to delete the relation line or No to cancel.

KAVV450-E

An error occurred in session processing.

An invalid data was sent from JP1/AJS3 - View. Alternatively, an unexpected response was received from JP1/AJS3 - Manager.

(S)

Cancels processing.

(O)

For the cluster configuration of JP1/AJS2 - Manager of version 06-00 of the destination host, the system may display this message when you access the scheduler service of the logical host from JP1/AJS3 - View. In this case, select the scheduler service of the logical host and execute File and then New Window.

For other cases, collect the following data and contact the system administrator.

A hardcopy of the window

JP1/AJS3 - View log

JP1/AJS3 - Manager log

For details on how to collect the logs, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KAVV451-E

The JP1/AJS service at the connection destination has not been started.

The probable causes are:

The AJS service has not started at the connection destination.

When the JP1/Base settings on the connection destination specified the IP binding method on the receiving side for physical hosts, connection was attempted using an IP address that was not bound to a physical host or any logical host.

When the connection destination was UNIX, the ajsshmdel command is not executed when the configuration of JP1/AJS3 - Manager is changed at the connection destination. Alternatively, the ajsshmdel command was executed without stopping all the JP1/AJS3 services.

When the connection destination was Windows, all the JP1/AJS3 services were not stopped when the configuration of JP1/AJS3 - Manager was changed at the connection destination.

(S)

Cancels processing.

(O)

Correct the cause of the error, and then retry.

If connection was attempted using an IP address that was not bound to a physical host or any logical host at the connection destination, use a bound IP address to attempt connection. Alternatively, define jp1hosts or jp1hosts2 information at the connection destination. For details on the definition of jp1hosts or jp1hosts2 information, see the Job Management Partner 1/Base User's Guide.

If the operation during the change of the JP1/AJS3 - Manager configuration at the connection destination caused the error, take action at the connection destination according to the following procedure:

Stop all the running JP1/AJS3 processes (services and commands).

When the connection destination is Windows, go to step 3.

When the connection destination is UNIX, go to step 2.

Execute the ajsshmdel command.

Restart JP1/AJS3.

KAVV452-E

Cannot connect because the number of connections exceeded the maximum.

Connection is impossible because the number of connections with JP1/AJS3 - Manager exceeds the maximum.

(S)

Cancels processing.

(O)

Wait until the number of connections drops below the maximum, and then reconnect.

You can change the maximum number of connections in a JP1/AJS3 - Manager environment setting. As required, specify the value in the MAXSESSION or SERVICEMAXSESSION environment setting parameter.

If this message appears even though no other connections have been established, check whether JP1/AJS3 - Manager was set up at the connection destination.

KAVV453-E

The specified scheduler service does not exist.

The scheduler service does not exist. The probable causes are:

The scheduler service specified for the -n option of the ajs command does not exist in JP1/AJS3 - Manager at the connection destination.

When JP1/AJS3 - Manager at the connection destination uses a cluster configuration, you logged on to a logical host. Then, when all the scheduler services were displayed, you accessed a scheduler service outside the logical host to which you logged on.

(S)

Cancels processing.

(O)

When the -n option of the ajs command is specified:

Check whether the specified scheduler service exists in JP1/AJS3 - Manager at the connection destination. Specify the correct scheduler service name, and then re-execute the command.

When the connection destination is the logical host:

Select the scheduler service of the logical host, and then choose File and New Window.

For other cases:

Make sure that the configuration definition for JP1/AJS3 - Manager at the connection destination has not been changed, and then restart JP1/AJS3 - View.

KAVV454-E

The user could not be authenticated at the connection destination.

The system could not authenticate the user at the connection destination.

(S)

Cancels processing.

(O)

Collect the following data and contact the system administrator.

A hardcopy of the window

JP1/AJS3 - View log

JP1/AJS3 - Manager log of the destination

JP1/Base log (If the authentication server is on another host, also collect the JP1/Base log on the authentication server on that host.)

For details on how to collect the logs, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

For details on how to collect the log of JP1/Base, see the Job Management Partner 1/Base User's Guide.

KAVV455-E

The request cannot be processed at the connected JP1/AJS.

Different versions of JP1/AJS3 - Manager and JP1/AJS3 - View exist in the same environment. Either JP1/AJS3 - Manager or JP1/AJS3 - View does not support the requested processing.

(S)

Cancels processing.

(O)

In an environment in which different versions of JP1/AJS3 - Manager and JP1/AJS3 - View exist, only use the functions that are supported in the older version.

To use the new JP1/AJS3 - Manager functions, use the new versions of JP1/AJS3 - Manager and JP1/AJS3 - View.

For details about notes when there are different versions of JP1/AJS3 - Manager and JP1/AJS3 - View, see 8.1.2 Version compatibility between JP1/AJS - Manager and JP1/AJS - View in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide and A. JP1/AJS3 - View Compatibility in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

KAVV456-E

The specified unit has already been registered.

An attempt was made to change the unit configuration of an already registered unit. The probable causes are:

The cut source unit has been registered.

The paste destination unit has been registered.

(S)

Cancels processing.

(O)

Check the status of the cut source and paste destination units.

KAVV457-E

The user name or password is invalid.

Login was impossible due to an invalid JP1 user name or password.

(S)

Cancels processing.

(O)

Enter the JP1 user name and the password that are registered in the destination authentication server and log in properly.

If you cannot correct the problem, contact the system administrator. If the primary authentication server is blocked, the system administrator must check whether the authentication information on the primary authentication server is synchronized with that on the secondary authentication server.

KAVV458-E

User mapping failed. The user was not associated with an OS user at the connection destination.

User mapping failed in the destination preventing you from logging in. The probable causes are:

In the user mapping of the destination JP1/Base, the JP1 user name and the OS user name are not defined.

In the user mapping of the destination JP1/Base, the OS user mapped with the JP1 user name is deleted from the OS definitions or the password is changed.

In the user mapping of the destination JP1/Base, the user ID or group ID of the OS user mapped to the JP1 user name is invalid.

In the password management settings of the destination JP1/Base, the OS user that maps to the JP1 user name is not registered.

In the password management settings of the destination JP1/Base, the account of the OS user to be mapped to the JP1 user name is locked out.

In the user mapping settings of the destination JP1/Base, the OS user mapped to the JP1 user name does not have permission to log on locally.

In the user mapping of the destination JP1/Base, the local host name is not specified for the server host name or the name is incorrect.

Notes on how to specify the local host name, see the description on how to set the user mapping in the Job Management Partner 1/Base User's Guide.

Memory was insufficient during user mapping.

(S)

Cancels processing.

(O)

Correct the cause of the error, and then log in again.

KAVV459-E

An error occurred in JP1/Base at the connection destination.

The destination JP1/Base could not be logged in or connected due to an error occurred at the destination during the user authentication. The probable causes are:

In the settings of the destination JP1/Base, an invalid host name of the authentication server is specified.

If the destination Windows event log or syslog displays the error message "KAVS1005-E Cannot connect to Access Control Server.", the authentication server is not started.

(S)

Cancels processing.

(O)

Correct the error and then retry. When the connection destination is UNIX and the authentication server is specified as the local host, you must set up JP1/Base to start JP1/Base as an authentication server. For details on setup, see the explanation of how to specify an authentication server in the Job Management Partner 1/Base User's Guide.

KAVV460-E

You cannot use the current login information to log in.

When you started JP1/AJS3 - View from the Tool Launcher screen of JP1/IM - View, you could not log in with the current login information because the user authentication bloc of the new destination differed from the current one. Another cause of the error is that the authentication server was restarted before JP1/AJS3 - View started.

When you started JP1/AJS3 - View normally, you could not log in with the current login information because the authentication server was restarted during login processing of JP1/AJS3 - View.

(S)

Cancels processing.

(O)

Log in again.

KAVV461-E

The connection is not possible because the specified scheduler service is under maintenance.

The specified scheduler service cannot be connected because it is undergoing maintenance.

(S)

Cancels processing.

(O)

Wait until the maintenance of the specified scheduler service finishes, and then retry.

KAVV462-E

An unrecovered unit exists because the unit definition is invalid.

There is a unit that cannot be recovered due to an invalid unit definition in the backup file.

(S)

Cancels processing.

(O)

Back up the unit again in the scheduler service at the backup source, and then recover the unit again.

KAVV501-E

An error occurred at the connection destination.

Detailed information: maintenance-information-1, maintenance-information-2

An error occurred at the connection destination.

When this message appears in the Backup dialog box or Restore dialog box, the contents in Backup box might be incorrect.

(S)

Cancels processing.

(O)

Use the Windows event log or the syslog file on the host of JP1/AJS3 - Manager to examine the error. Then, correct the error according to the results.

For details on the contents of the log file, see 1.2 Types of log information and storage locations in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

For details about the log, see C. Log Information in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

When maintenance-information-1 in this message indicates 0 and JP1/AJS3 - Manager at the connection destination is UNIX, check whether the home directory of the OS user mapped to the logged-on JP1 user exists. If the home directory does not exist, create it.

When this message appears in the Backup dialog box or Restore dialog box, depending on the output timing, the following item in the Backup box might be incorrect:

When the Backup dialog box or Restore dialog box is open

The first backup box listed in Backup box

When a backup box is selected in Backup box in the Backup dialog box or Restore dialog box

The selected backup box

When you enter a backup box name in Backup box name in the Backup dialog box and then click the OK button

The backup box entered in Backup box name

If the erroneous backup box is one of the following, delete it from the backup information directory:

A backup box saved in another instance of JP1/AJS3 - Manager

A backup box saved in an environment that uses different character codes

A backup box containing an edited backup information management file

KAVV502-E

The specified unit does not exist.

The specified unit does not exist.

(S)

Cancels processing.

(O)

Choose Refresh, and then check to make sure that the unit is not deleted.

In the case of the Daily Schedule or Monthly Schedule window, relaunch the window to refresh it.

KAVV503-E

The unit cannot be defined because the unit hierarchy exceeded the maximum.

The unit cannot be defined because the unit hierarchy exceeds the maximum.

(S)

Cancels processing.

(O)

Define the unit so that the unit hierarchy is within the maximum.

The maximum value for the unit hierarchy is 30 levels from directly under the root job group (not including the root job group).

In a UTF-8 environment, when the setting for changing the number of characters specifiable for unit names or other items is enabled, note that the maximum value for the unit hierarchy is 10, counting from directly under the root job group (excluding the root job group). For details about how to set that the number of characters used to specify unit names or other items can be changed in a UTF-8 environment, see 15.1.9 Setting for changing the number of characters specifiable for a unit name in a UTF-8 environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

KAVV504-E

Cannot delete - Specified Unit is Registered.

You attempted to delete a registered unit.

(S)

Cancels processing.

(O)

Cancel registration of the unit, and then delete it. We recommend choosing Refresh before canceling the registration.

KAVV505-E

The specified unit can be neither deleted nor renamed because it is registered.

You attempted to delete or rename a registered unit.

Alternatively, you attempted to change the unit definition information for a connection-destination jobnet was already registered. There is a chance that the jobnet has been registered for execution during the period from opening of the Define Details dialog box to clicking of the OK button.

(S)

Cancels processing.

(O)

Unregister the unit, and then delete or rename it. We recommend you choose Refresh before canceling the registration.

For the connection-destination jobnet, click the Cancel button to close the Define Details dialog box. You can then open the Define Details dialog box again to change the unit definition information. We recommend that you choose Refresh before opening the Define Details dialog box again.

KAVV506-E

The job group can be neither deleted nor renamed because a registered jobnet exists.

An attempt was made to delete or rename a job group under which jobnets are registered.

Alternatively, an attempt was made to change the unit definition information for a connection-destination planning group under which jobnets were registered. A lower jobnet has been registered for execution during the period from opening of the Define Details dialog box to clicking of the OK button.

(S)

Cancels processing.

(O)

Unregister all the jobnets under the specified job group, and then retry. We recommend choosing Refresh before canceling the registration.

For the connection-destination planning group, click Cancel to close the Define Details dialog box. You can then open the Define Details dialog box again to change the unit definition information. We recommend that you choose Refresh before opening the Define Details dialog box again.

KAVV507-E

A past date is specified for an execution start day.

A past date is specified for the start date of the fixed schedule period during fixed execution registration. Alternatively, a past date is specified for the start time in the Shift Schedule Date and Time dialog box.

(S)

Cancels processing.

(O)

Specify a date after the current date for the execution start date, and then retry.

KAVV508-E

Cannot treat as Jobnet.

The specified unit cannot be handled as a jobnet. A root jobnet that has the recovery attribute may have been registered for execution.

(S)

Cancels processing.

(O)

Check the jobnet definition for an error. When registering a root jobnet for execution, check whether it has the recovery attribute.

KAVV509-E

It has no schedule.

For a jobnet that does not have a next schedule, you attempted to temporarily change a schedule.

(S)

Cancels processing.

(O)

Check the status of the jobnet, and then retry.

KAVV510-E

Cannot treat as Unit.

The specified unit cannot be handled as a unit. Alternatively, the specified unit does not exist. The probable causes are:

The specified unit has been deleted elsewhere.

The full unit name specified in the ajs command is more than 930 bytes.

(S)

Cancels processing.

(O)

Choose Refresh and check whether the specified unit exists.

If you executed the ajs command with the full unit name specified in the -n option, recheck the specification of the full unit name, and then re-execute the command.

KAVV511-E

Specified jobnet has no information for display.

Specified jobnet does not have any information for display.

(S)

Cancels processing.

(O)

Check the jobnet definition for an error.

KAVV512-E

The unit cannot be defined because the limit has been exceeded.

The unit cannot be defined because the number of units that can be defined exceeded the limit. The probable causes are:

The number of event jobs defined under the start condition jobnet exceeded the limit, that is, 32.

The number of defined units exceeded the limit that depends on the DBMS used by JP1/AJS3 - Manager at the connection destination.

(S)

Cancels processing.

(O)

Delete unnecessary units, and then define the units within the allowable limit.

KAVV513-E

Cannot be registered because the limit on registered jobnet has been exceeded.

Registration is impossible because the number of jobnets that can be registered exceeded the limit.

(S)

Cancels processing.

(O)

Unregister unnecessary jobnets and then register the jobnet for execution.

The maximum number of jobnets that can be registered is 2,147,483,647.

KAVV520-E

Jobnet already registered.

The selected operation cannot be executed on the jobnet being registered.

(S)

Cancels processing.

(O)

Cancel registration, and then retry. We recommend choosing Refresh before canceling the registration.

KAVV521-E

Specified jobnet is not registered.

The selected operation cannot be executed on the jobnet that is not registered.

(S)

Cancels processing.

(O)

Register the jobnet for execution, and then retry. We recommend you choose Refresh before registering the jobnet for execution.

KAVV522-E

The specified job or jobnet is being executed.

The selected operation cannot be executed on the job or jobnet being executed.

(S)

Cancels processing.

(O)

Wait until the execution terminates, and then retry.

KAVV523-E

The specified job or jobnet has no schedule to be executed.

The specified job or jobnet has no schedule to be executed.

(S)

Cancels processing.

(O)

Check the next and subsequent execution schedules and perform the operation for the scheduled generation.

If this message appears during operation of the scheduled generation, execution may have been canceled elsewhere.

Choose Refresh and then check the target generation.

KAVV524-E

Cannot change the schedule temporarily because the execution start day of the specified jobnet differs from that of the upper jobnet.

You cannot change the schedule temporarily because the execution start time of the specified jobnet is not within 48 hours from the base time of the start date of the root jobnet.

(S)

Cancels processing.

(O)

For the execution start time for temporarily changing the schedule, specify a time within 48 hours from the base time of the start date of the root jobnet.

KAVV525-I

The date has not been changed or the execution has not been stopped.

The date has not been changed or the execution has not been canceled.

(S)

Cancels processing.

(O)

Check the target schedule for an error.

KAVV526-E

Cannot operate - wait for activation condition.

Waiting for the start condition made operation impossible.

(S)

Cancels processing.

(O)

Wait until the start condition is satisfied, and then retry.

KAVV527-E

Cannot operate - Jobnet has been shutdown.

The target is being shut down making operation impossible.

The probable causes are:

The job group for which you want to reference the calendar does not exist.

The unit specified in an exclusive schedule does not exist at the same level.

(S)

Cancels processing.

(O)

Correct the cause of the shutdown, and then unregister the shut down jobnet. As required, re-register the jobnet for execution.

KAVV528-E

A unit with the same name already exists.

A unit with the same name already exists.

(S)

Cancels processing.

(O)

Rename the unit, and then retry the update. We recommend choosing Refresh before starting the operation.

KAVV529-E

The backup box is full.

The backup box is full.

(S)

Cancels processing.

(O)

Change the backup box. Alternatively, execute the ajsbkudel command at the connection destination to delete unnecessary backup files from the target backup box, and then retry the backup.

KAVV531-E

The specified registration number was not found.

The operation cannot be processed because no such registration number was found.

The probable causes are:

The specified generation exceeds the number of saved generations.

The specified generation has been unregistered by using Specify period.

The specified jobnet was unregistered and subsequently re-registered for execution.

Execution of the specified generation has been canceled.

(S)

Cancels processing.

(O)

Go back to the window from which you opened the Temporary Changes dialog box, and check whether a generation with the specified registration number exists.

KAVV532-E

The jobnet cannot be registered because no effective start day is defined.

The jobnet cannot be registered because the schedule information does not have an effective start date defined.

The probable causes are:

The registration date exceeded the expiration date.

During fixed execution registration, the start date of the fixed schedule period is after the execution start date.

In the schedule definition, the start date exceeded the expiration date.

Although the registration time exceeded the start time, no processing cycle is specified in the schedule definition.

Although the start time falls on a closed day in the schedule definition, Do not execute is selected for Substitute schedule of closed day job and no processing cycle is specified.

(S)

Cancels processing.

(O)

Correctly specify the jobnet registered for execution, or correctly specify the schedule definition. Then, re-register the jobnet.

KAVV533-E

The jobnet cannot be registered because no schedule is defined.

Schedule information is not defined preventing registration of the jobnet.

(S)

Cancels processing.

(O)

Create a schedule rule, and then re-register the jobnet for execution.

KAVV534-E

There is no execution schedule in the specified period.

There is no execution schedule in the specified period.

(S)

Cancels processing.

(O)

Check the definition of schedule information.

KAVV535-E

The jobnet cannot be registered because the exclusive jobnet is invalid.

The jobnet cannot be registered because the exclusive jobnet is defined incorrectly.

(S)

Cancels processing.

(O)

Check whether the unit specified for the exclusive jobnet is a jobnet or planning group at the same level. Correct the setting, and then re-register the jobnet for execution.

KAVV536-E

The jobnet cannot be registered because the calendar information is invalid.

The jobnet cannot be registered because the calendar information is invalid.

(S)

Cancels processing.

(O)

Check whether the job group for which you want to reference the calendar exists, specify the correct job group, and then re-register the jobnet for execution.

KAVV537-E

The specified unit has neither a forecast nor performance.

The specified unit has neither a forecast nor performance information.

(S)

Cancels processing.

(O)

Specify a unit that has a schedule or result.

KAVV538-E

Specified execution ID was not found.

Processing is impossible because the target execution ID does not exist.

The probable causes are:

The number of target generations exceeded the maximum number of logs to keep.

Registration of the target generation was canceled for the specified period of time.

The target jobnet was unregistered, and then re-registered for execution.

(S)

Cancels processing.

(O)

Choose Refresh, and then retry.

KAVV539-E

The specified jobnet does not exist.

The specified jobnet does not exist.

(S)

Cancels processing.

(O)

Choose Refresh, and then check whether the jobnet exists.

KAVV540-E

Specified Jobnet is not executing.

The operation cannot be executed because the specified jobnet is not running.

(S)

Cancels processing.

(O)

Check the status of the jobnet.

KAVV541-E

Specified Job is not executing.

The operation cannot be executed because the specified job is not running.

(S)

Cancels processing.

(O)

Check the status of the job.

KAVV542-E

Memory became insufficient at the connection destination.

A memory shortage occurred in the connection destination JP1/AJS3 - Manager.

(S)

Cancels processing.

(O)

Check whether the status of JP1/AJS3 - Manager at the connection destination can cause insufficient memory.

KAVV543-E

There is insufficient space for the file at the connection destination.

The file system or device in JP1/AJS3 - Manager at the connection destination has insufficient free space for writing a file.

(S)

Cancels processing.

(O)

Delete unnecessary files in the connection destination to create more free space.

Check whether the tablespace or RDAREA in the database used by JP1/AJS3 - Manager at the connection destination has free space. If there is no free space, see 10.2.2 Reorganizing a database in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide, and create free space.

KAVV544-E

The specified unit is being used elsewhere.

The operation or editing cannot be executed because another user is using the unit.

(S)

Cancels processing.

(O)

Check whether any of the JP1/AJS3 - View instances currently connected to JP1/AJS3 - Manager are using the unit.

To check JP1/AJS3 - View connection information, execute the ajsstatus command on JP1/AJS3 - Manager, specifying the -v option.

If the specified unit or lower units are displayed in any of the following windows, close the window and then retry the operation:

JP1/AJS3 - View window

Jobnet Editor window

Edit Monthly Calendar window

Edit Annual Calendar window

Daily Schedule (Hierarchy) window

Daily Schedule (All Jobs) window

Monthly Schedule window

Jobnet Monitor window

If JP1/AJS3 - View is disconnected due to a communication error, the connection sometimes stays open and the unit remains in use. In this case, wait until the failed connection times out, and then execute the ajsstatus command with the -v option specified. Make sure the failed connection has terminated, and then retry the operation. You can reduce the length of time until a connection is terminated by specifying the SESSIONTIMEOUT environment setting parameter in JP1/AJS3 - Manager. The SESSIONTIMEOUT default is dword:00000078 (120 in decimals; unit: minutes). For details about the environment setting parameters, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVV545-E

No authorization.

Processing is impossible because the JP1/AJS3 service and the OS user mapped to the JP1 user do not have the required permission.

(S)

Cancels processing.

(O)

If this message appears during uploading or downloading of a common user profile, check whether the OS user mapped at the connection destination has access permission for files and directories of the common user profile at the connection destination. For details on the location of common user profiles at the connection destination, see 11.1.2 Using common user profiles in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

For other cases, the probable causes are as follows. Check and correct the cause of the error.

When the connection destination is JP1/AJS3 - Manager for Windows

When you are using the JP1/AJS3 service with a user account, you do not have the required permissions.

For details on the required permissions, see 4.2.3 Changing the JP1/AJS3 service settings (Windows only) in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

The OS user mapped to the logged-in JP1 user is defined incorrectly in the user mapping settings in JP1/Base.

For details about the OS user definition format, see 3.1.1 Setting up JP1/Base in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Read and write permissions for the folder specified by database directory name for the scheduler service, and the files in that folder, have not been set for the OS user mapped to the JP1 user.

When the connection destination is JP1/AJS3 - Manager for UNIX

The OS user mapped to the JP1 user does not have read permission for the configuration definition files (files in /opt/jp1/hcclibcnf/regdir).

Read, write, and execute permissions (rwx) for the directory specified by database directory name for the scheduler service, and the files in that directory, have not been set for the OS user mapped to the JP1 user.

KAVV546-E

You are not authorized to operate those jobs.

You do not have the authority to perform the operation.

(S)

Cancels processing.

(O)

Check the user privileges.

KAVV547-E

Only the superuser can perform that process.

You do not have the authority to perform the operation.

(S)

Cancels processing.

(O)

Check the user privileges.

KAVV548-E

No authority for Specified Unit.

You do not have permission to reference, manipulate, or edit the specified unit.

(S)

Cancels processing.

(O)

Check the JP1 user privileges.

KAVV549-E

The specified scheduler service is not running.

Operation is impossible because the scheduler service to which the target unit belongs has not started.

(S)

Cancels processing.

(O)

Start the scheduler service at the JP1/AJS3 - Manager at the connection destination.

KAVV550-E

An error occurred during the accessing of the database at the connection destination.

An error occurred while accessing the JP1/AJS3 - Manager database at the destination.

(S)

Cancels processing.

(O)

Use the Windows event log or the syslog file on the host of JP1/AJS3 - Manager to examine the error. Then, correct the error according to the results.

For details on the contents of the log file, see 1.2 Types of log information and storage locations in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

For details about the log, see C. Log Information in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KAVV551-E

Resources became insufficient at the connection destination.

Resources became insufficient at the destination.

(S)

Cancels processing.

(O)

Use the Windows event log or the syslog file on the host of JP1/AJS3 - Manager to examine the error. Then, correct the error according to the results.

For details on the contents of the log file, see 1.2 Types of log information and storage locations in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

For details about the log, see C. Log Information in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KAVV552-E

Invalid Unit definition.

The unit is defined incorrectly. The probable causes are:

An attempt was made to update the definition of a job group that was already deleted elsewhere.

When you connected one of the following versions of JP1/AJS2 - View to an upgraded version of JP1/AJS - Manager, an operation that caused an error was performed as shown below:

When the version of JP1/AJS2 - View is 06-51 or later:

Register a jobnet directly under the planning group for execution, using a registration method other than fixed-execution registration with the schedule period specified.

Define anything other than the jobnet or the remote jobnet directly under the planning group.

(S)

Cancels processing.

(O)

If this error occurred when you updated a job group, check whether the specified job group exists. For other cases, correct the cause of the error and then retry.

KAVV554-E

At the connection destination, a required file cannot be accessed.

The required file is not found in JP1/AJS3 - Manager at the destination or the file cannot be accessed.

(S)

Cancels processing.

(O)

The action you must take differs depending on the conditions in effect when this message appears. Take one of the following actions as shown below:

When a backup box is selected in the Backup dialog box:

The specified backup box may have been deleted using the ajsbkudel command while the Backup dialog box was open. Close and then redisplay the Backup dialog box.

During downloading or uploading:

Check whether the OS user mapped to the JP1 user at the connection destination has access permission for files under the directory for common user profiles or for the directories above this directory.

For details about the path to the directory for common user profiles, see 11.1.2 Using common user profiles in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

For other than the above:

Check whether a lock file or ISAM file exists at the connection destination, and then check the settings of the kernel parameters for semaphores and shared memory.

Use the Windows event log or the syslog file on the host of JP1/AJS3 - Manager to examine the error. Then, correct the error according to the results.

For details on the contents of the log file, see 1.2 Types of log information and storage locations in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

For details about log information, see C. Log Information in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KAVV555-E

The unit is not in a re-executable status.

The unit is not in a re-executable status.

The probable causes are:

An attempt was made to re-execute a jobnet that has not been executed.

With the hold option specified, an attempt was made to re-execute a root jobnet that was being executed.

An attempt was made to re-execute a root jobnet that was both being executed and contained in the remote jobnet.

(S)

Cancels processing.

(O)

Choose Refresh and check the status of the unit, and then retry.

KAVV556-E

The unit cannot be operated.

The specified unit could not be processed because it has been deleted or because a start condition was specified for the unit.

(S)

Cancels processing.

(O)

Choose Refresh and check whether the target unit exists and whether the unit is a start condition jobnet or an event job under the jobnet.

For the Daily Schedule or Monthly Schedule window, restart the window. Do not attempt operation on the unit for which a start condition is specified.

For the following version of JP1/AJS2 - View, this message also appears when an upgraded version of JP1/AJS2 - Manager is connected:

In JP1/AJS2 - View 06-00

Although the target unit was suspended, you attempted an operation not applicable to suspended units.

You attempted an operation that was only possible for suspended units.

You deleted a running unit or changed the recovery attribute when the unit was suspended.

KAVV557-E

File processing count exceeds the limit at the connection destination.

The number of files that the connection destination can process exceeded the maximum.

(S)

Cancels processing.

(O)

Close unnecessary windows and dialog boxes at the connection destination, and then re-execute the operation.

If the connection destination is UNIX, see Release Notes, and check the following items in the kernel parameters:

Maximum number of files allowed to be open for a process or system

Maximum number of file descriptors allowed (a limit value related to the file system)

KAVV558-E

Lock resources count exceeds the limit at the connection destination.

The number of locked resources that the connection destination can process exceeded the maximum.

(S)

Cancels processing.

(O)

Close unnecessary windows and dialog boxes at the connection destination, and then re-execute the operation.

If the connection destination is UNIX, see Release Notes, and check the following items in the kernel parameters:

Maximum number of files allowed to be open for a process or system

Maximum number of file descriptors allowed (a limit value related to the file system)

KAVV559-E

Not enough space in file system at the connection destination.

The file system at the connection destination has insufficient area.

(S)

Cancels processing.

(O)

Close unnecessary windows and dialog boxes at the connection destination, and delete unnecessary files to increase available free space. Then re-execute the operation.

If the connection destination is UNIX, see Release Notes, and check the following items of the kernel parameters:

Maximum number of files allowed to be open for a process or system

Maximum number of file descriptors allowed (a limit value related to the file system)

KAVV560-E

System resource became insufficient at the connection destination.

System resources became insufficient at the connection destination.

(S)

Cancels processing.

(O)

Close unnecessary windows and dialog boxes at the connection destination, and then re-execute the operation.

If the connection destination is UNIX, see Release Notes, and check the following items in the kernel parameters:

Maximum number of files allowed to be open for a process or system

Maximum number of file descriptors allowed (a limit value related to the file system)

KAVV561-E

Shared memory is not available at the connection destination.

The system cannot acquire shared memory, one of the system resources, in JP1/AJS3 - Manager at the connection destination. Alternatively, the required shared memory is missing.

(S)

Cancels processing.

(O)

See Release Notes. Then check whether the shared memory for the system is estimated correctly at the connection destination, and then (if necessary) increase the value set in the kernel parameter.

If the shared memory required for running the scheduler service was deleted, restart the scheduler service.

KAVV562-E

The backup box name is invalid.

An invalid character is specified for a backup box name.

(S)

Cancels processing.

(O)

Specify the backup box name correctly, and then retry the backup.

Characters you can use in a backup box name depends on the file system for the connection destination OS. We recommend that you use alphanumeric characters (in Japanese systems, use Hankaku alphanumeric characters).

KAVV563-E

Cannot obtain configuration definition at the connection destination.

The system cannot obtain configuration definition at the connection destination. The probable cause is:

If this message appears during backup, a value of the AJSBKUROOT environment setting parameter is not specified.

(S)

Cancels processing.

(O)

Correct the cause of the error.

KAVV564-E

Cannot add because the execution start date of the specified jobnet differs from that of the upper jobnet.

You cannot add a schedule because the execution start time of the specified jobnet is not within 48 hours from the base time of the start date of the root jobnet.

(S)

Cancels processing.

(O)

For the execution start time for adding a schedule, specify a time within 48 hours from the base time of the start date of the root jobnet.

KAVV565-E

The specified job or jobnet has no schedule to be added.

There is no schedule that can be added in the displayed execution schedule.

You can add a schedule to a specified job or jobnet only if:

The upper-level jobnet has a schedule

There is no schedule of the same generation as the upper-level jobnet

(S)

Cancels processing.

(O)

Check whether you added the correct unit.

KAVV566-E

The date is specified incorrectly.

The date is specified incorrectly.

(S)

Cancels processing.

(O)

Specify the date correctly.

For the following version of JP1/AJS2 - View, this message also appears when an upgraded version of JP1/AJS2 - Manager is connected:

In JP1/AJS2 - View 06-00

When you specify a relative time to change the start date and time, the time after the change is later than the year 2037.

KAVV567-E

There is no place to restore.

When you restore a unit to a jobnet, the map size of the destination jobnet is too small to contain the unit.

(S)

Restores the amount of the unit necessary to fit the map size.

(O)

Increase the map size, and then restore the unit again.

KAVV568-E

This operation cannot be executed for the specified unit's status.

An attempt was made to perform an operation while the status of the unit prevented its execution.

(S)

Cancels processing.

(O)

Check the status of the unit. We recommend you execute Refresh.

If this message appears while the status of the job is being changed, see ajschgstat in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1, and make sure that the new status specified for the current status is valid. Also make sure that the return code can be changed.

KAVV569-E

Cannot hold rerun - specified Jobnet already running.

The jobnet being executed cannot be placed in the hold-reexecution state.

(S)

Cancels processing.

(O)

Check the status of the job. We recommend choosing Refresh.

KAVV570-E

Specified Unit cannot rerun.

The specified unit is not a re-executable unit, or is not in the re-executable status.

The probable causes are:

The status of the job or nested jobnet that you attempted to rerun is one of the following: Now running, Running + Abend, Running + Warning, Wait for prev. to end, Wait for start time, or Being held.

The job or the nested jobnet that you attempted to rerun has the recovery attribute, and the status of the preceding job or jobnet is Ended normally or Ended with warning.

The job or the nested jobnet that you attempted to rerun is a judgement job or a dependent unit for a judgement job.

The upper-level jobnet of the job or the nested job that you attempted to rerun has no schedule.

(S)

Cancels processing.

(O)

Check the type or status of the unit you attempted to re-execute.

We recommend you choose Refresh to check the status.

KAVV571-E

Cannot operate because it is being restrict-processed.

You cannot operate the scheduler service to which the target unit belongs because the operation is restricted.

(S)

Cancels processing.

(O)

Use the ajsstop command at the connection destination to release the restriction on the target scheduler service. Alternatively, wait until the scheduler service is restarted, and then retry.

For the following version of JP1/AJS2 - View, this message also appears when an upgraded version of JP1/AJS2 - Manager is connected:

In JP1/AJS2 - View 06-71 or earlier

You accessed the scheduler service during maintenance.

KAVV572-E

The database files of the scheduler service do not exist.

The database files of the specified scheduler service do not exist.

(S)

Cancels processing.

(O)

Reconnect after checking the environment setting for the scheduler service by the connect JP1/AJS3 - Manager, and the mount status of the disks, and making the files accessible.

KAVV580-E

The suspend function is ineffective at the connection destination.

You cannot use the suspend function because it is disabled in JP1/AJS3 - Manager at the connection destination.

(S)

Cancels processing.

(O)

See 6.1.5 Enabling the suspend function in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under Windows) or 15.1.5 Enabling the suspend function in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under UNIX), and enable the suspend function in JP1/AJS3 - Manager at the connection destination.

Before you set up the suspend function, log off of JP1/AJS3 - View.

KAVV581-E

This operation cannot be executed because the specified unit is currently setting or releasing the suspend setting.

Either the suspend execution or the suspend release operation cannot execute because the specified unit is currently setting or releasing the suspend setting.

(S)

Cancels processing.

(O)

Retry after few minutes.

Before retrial, we recommend you execute Refresh.

KAVV582-E

This operation cannot be executed because the specified unit is in the suspended state.

This operation cannot be executed because the specified unit is in the suspended state.

(S)

Cancels processing.

(O)

Operate after releasing suspend.

KAVV583-E

The specified jobnet is already suspended.

This operation cannot be executed because the specified jobnet is already suspended.

(S)

Cancels processing.

(O)

Check whether the specified jobnet is suspended. We recommend you execute Refresh.

KAVV584-E

The specified jobnet is not suspended.

This operation cannot be executed because the specified jobnet is not suspended.

(S)

Cancels processing.

(O)

Check whether the specified jobnet is suspended. We recommend you execute Refresh.

KAVV585-E

The specified jobnet is now monitoring so it cannot be suspended.

The specified jobnet cannot be suspended because it is currently monitoring the start condition of generations.

(S)

Cancels processing.

(O)

Check the status of the jobnet. We recommend you execute Refresh.

KAVV586-E

The specified jobnet is now running so it cannot be suspended.

The specified jobnet cannot be suspended because it is currently running generations.

(S)

Cancels processing.

(O)

Check the status of the jobnet. We recommend you execute Refresh.

If it is to be suspended, select suspend in the executing generations option for suspend execution in the Suspend dialog box.

KAVV587-E

The system could not connect to the Access Control Server at the connection destination.

The system cannot process because it cannot access the authentication server in the connection destination.

(S)

Cancels processing.

(O)

Check if the authentication server specified in the connected JP1/Base is available.

KAVV588-E

You cannot make a temporary schedule change to the specified execution start day.

A temporary schedule change does not take place because the specified execution start day is after the year 2037.

(S)

Cancels processing.

(O)

If the schedule change is specified in the relative data format, make sure the changed date is not after the year 2037.

KAVV589-E

The configuration definition at the connection destination is specified incorrectly. (configuration-definition-parameter-name)

Processing is impossible because the environment has not been set up correctly in JP1/AJS3 - Manager at the connection destination.

(S)

Cancels processing.

(O)

In the environment settings for JP1/AJS3 - Manager at the connection destination, correctly set the configuration definition parameter shown in the message.

KAVV590-E

The logical host name at the connection destination is specified incorrectly.

Processing is impossible because the host name for the logical host connected in JP1/AJS3 - View is not specified correctly in the environment setting at the connection destination.

(S)

Cancels processing.

(O)

Check whether the logical host name for the IP address connected in JP1/AJS3 - View is specified correctly at the connection destination. Also make sure that the logical host name is correctly set as the logical host in the environment setting at the connection destination.

If the connection destination is JP1/AJS3 - Manager for UNIX, check whether the mapped OS user has permission to read the configuration definition files (files under /opt/jp1/hcclibcnf/regdir).

KAVV591-E

You cannot change a recovery attribute, or delete, because the specified unit is now executing.

Changing or deleting the recovery attribute cannot be executed because the specified unit is currently execution.

(S)

Cancels processing.

If the multiple units are selected before deleting, some units may not be deleted.

(O)

Even if the unit is in the suspend status, deleting or changing the recovery attribute cannot take place. Retry after the unit is in the complete status.

If the multiple units are selected, check if the undeleted units are not running, and reselect the units and delete them.

KAVV592-E

Perform the operation on a jobnet that is not scheduled to execute or is registered for a fixed execution.

A schedule for the root jobnet could not be added because the specified jobnet was in the unscheduled status or was not registered for fixed execution. The probable causes are:

The specified jobnet is registered for planned execution, and the next schedule is defined.

The specified jobnet is registered for immediate execution, but not yet executed.

(S)

Cancels processing.

(O)

To add a schedule for a root jobnet, specify a root jobnet that is in the unscheduled status or that is scheduled for fixed execution.

KAVV593-E

A directory required at the connection destination cannot be accessed. Detailed information: detailed-information-1, detailed-information-2

The required directory was not found or cannot be accessed in JP1/AJS3 - Manager at the connection destination.

(S)

Cancels processing.

(O)

If this message appears during uploading or downloading of a common user profile, make sure that the directory for common user profiles exists in JP1/AJS3 - Manager at the connection destination, and that the disk has sufficient free space.

For details on the path to the directory for common user profiles, see 11.1.2 Using common user profiles in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

KAVV594-E

The unusual end of the specified unit has not been carried out.

The status of the target jobnet is neither Running + Abend nor Ended abnormally, so you cannot select the following options for re-execution starting from the abnormally terminated unit:

From abnormally ended job

From after abnormally ended job

From abnormally ended jobnet

(S)

Cancels processing.

(O)

Use the Multi-execution Results dialog box to check the unit for which this message appears, and then re-execute the unit as required.

KAVV595-E

This operation cannot be executed because the number of jobnet generations had been reached the system limit at the connection destination.

This operation cannot be performed because the number of generations reached the maximum in the connection destination JP1/AJS3 - Manager.

(S)

Cancels processing.

(O)

The number of jobnet generations (excluding the number of generations created when the starting conditions are satisfied) cannot exceed 8,000.

If you want to add a schedule in registering jobnets for fixed execution by specifying a date and in next-time schedule addition for temporary change of the schedule, re-execute the operation after the execution of at least one currently executed generation ends.

For registration of jobnets for fixed execution by specifying a period, generations that do not exceed a total of 8,000 generations have been registered.

For later generations to be scheduled, re-execute the operation after the execution of generations, the number of which matches the number of generations to be registered, is completed.

KAVV596-E

This operation cannot be executed because the system failed to delete an execution result at the connection destination.

This operation cannot be performed because the execution result could not be deleted in JP1/AJS3 - Manager at the connection destination.

(S)

Cancels processing.

(O)

Take action according to the message that was output to Windows event log or syslog in JP1/AJS3 - Manager at the connection destination immediately before the message KAVS0699-E.

KAVV597-E

The jobnet monitor cannot display the next schedule of a remote jobnet.

The next schedule of a remote jobnet cannot be displayed in the Jobnet Monitor window.

(S)

Cancels processing.

(O)

To check the next schedule of a remote jobnet, in the Menu, click Display, Detailed Information, and then Next Schedule. The next schedule appears in the Detailed Information dialog box.

KAVV598-E

The jobnet monitor or detailed information cannot display the next schedule of a manager jobnet.

The next schedule of a manager jobnet cannot be displayed in the Jobnet Monitor window or the Detailed Information dialog box.

(S)

Cancels processing.

(O)

Check the next schedule of a manager jobnet in the Daily Schedule window or the Monthly Schedule window.

KAVV599-E

An unrecovered unit exists because the number of saved generations exceeded the maximum.

The number of logs to keep for the jobnet you attempted to recover exceeded the maximum number of logs to keep specified in the scheduler service at the recovery destination. Those generations cannot be recovered.

(S)

Cancels processing.

(O)

Change the maximum number of logs to keep specified in the scheduler service at the recovery destination to the setting of the scheduler service for the saved units, and then retry the recovery.

Before you change the maximum number of logs to keep, terminate JP1/AJS3 - View.

KAVV600-E

Invalid definition in (item-name).

The definition is invalid.

(S)

Cancels processing.

(O)

Check what you can define for the item, and then reenter it.

KAVV601-E

(item-name) exceeds (numeric) bytes.

The specification of item-name exceeds the limit.

(S)

Cancels processing.

(O)

Specify the item that does not exceed the indicated length#.

#

The length is based on Shift-JIS encoding if the environment at the connection destination is a UTF-8 environment and the setting for changing the number of characters specifiable for unit names or other items is enabled. For details about how to specify this setting, see 15.1.9 Setting for changing the number of characters specifiable for a unit name in a UTF-8 environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

KAVV605-E

Specify the macro variable information to be passed.

The macro variable is not specified for the inherited information.

(S)

Cancels processing.

(O)

Specify the macro variable for the inherited information.

KAVV606-E

Specify the value of the passing information.

No value is specified for the inherited information.

(S)

Cancels processing.

(O)

Specify the value for the inherited information.

KAVV607-E

The value (passing-information) specified for the passing information is invalid.

The value of the inherited information is invalid.

(S)

Cancels processing.

(O)

Re-enter a value that can be defined according to B. Information Passed by Event Jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

KAVV608-E

The setting for passing information exceeds a total of (numeric) bytes.

The definition of the inherited information exceeds the specifiable value.

(S)

Cancels processing.

(O)

Delete unnecessary inherited information, if defined. Check whether you can specify a shorter name for the macro variable.

KAVV610-E

For an event ID, you cannot specify an extension ID only.

The basic code is not specified for the event ID of the Receive JP1 Event job.

(S)

Cancels processing.

(O)

Specify the basic code of the event ID. Alternatively, do not specify the event ID.

KAVV611-E

Specify the end-judgment file name.

A file name for the end judgment is not specified for the Receive JP1 Event job.

(S)

Cancels processing.

(O)

To use a message or detailed information as an end judgment condition, specify a file name for the end judgment.

KAVV612-E

Specify the extension attribute name.

No extension attribute name is specified.

(S)

Cancels processing.

(O)

Specify an extension attribute name.

KAVV613-E

The extension attribute name (extension-attribute-name) is invalid.

The extension attribute name is invalid in the Receive JP1 Event job.

(S)

Cancels processing.

(O)

Re-enter an extension attribute name that can be defined according to 15.4.14 Detailed Definition - [Receive JP1 Event] - [Extended Attribute] dialog box in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

KAVV614-E

Specify a value for the extension attribute name.

No value is specified for an extension attribute name.

(S)

Cancels processing.

(O)

Specify the value of the extension attribute name.

KAVV615-E

The extension attribute name specification exceeds (numeric) bytes.

The extension attribute name specified in the Receive JP1 Event job exceeds the limit.

(S)

Cancels processing.

(O)

If unnecessary extension attributes are defined, delete them.

KAVV616-E

The definition of an extension attribute contains an error.

The definition of the extension attribute is invalid.

(S)

Cancels processing.

(O)

Determine the definition that is valid, and then reenter it.

KAVV617-E

The IP address of the event issuer is invalid.

The IP address of the event issuer specified in the Receive JP1 Event job is invalid.

(S)

Cancels processing.

(O)

Correctly specify the IP address. Alternatively, specify spaces for all the items of the event issuer IP address.

KAVV618-E

Specify 1 to 720 minutes for finding event search.

If Yes is selected for Find event before exec. in the Detailed Definition - [Receive JP1 Event] dialog box, the time for monitoring the events is not specified correctly.

(S)

Cancels processing.

(O)

When you select Yes for Find event before exec., specify the period of time (minutes) for monitoring the events, from 1 to 720 minutes before the job starts monitoring.

KAVV619-E

Specify the value of the event ID when you select "Yes" in the "Find event before exec.".

You must specify an event ID when you select Yes for Find event prior to exec. for the Receive JP1 Event job.

(S)

Cancels processing.

(O)

Select No for Find event prior to exec., or specify an event ID.

KAVV620-E

Enter the name of the file to be monitored.

The name of the file to be monitored is not specified for the Monitoring Files job.

(S)

Cancels processing.

(O)

Specify the file name to be monitored.

KAVV621-E

You cannot simultaneously specify the monitoring options "Size change" and "Latest write time change".

Both the size change and the latest write time change are specified for monitoring conditions for the Monitoring Files job.

(S)

Cancels processing.

(O)

Specify either the size change or the latest write time change for the monitoring conditions. Alternatively, specify neither of them.

KAVV622-E

Specify the monitoring options.

The monitoring condition is not specified for the Monitoring Files job.

(S)

Cancels processing.

(O)

Specify the monitoring condition.

KAVV623-E

Specify from (numeric) to (numeric) seconds for the monitoring interval.

The monitoring interval is specified incorrectly for the Monitoring Files job.

(S)

Cancels processing.

(O)

Do not specify the monitoring interval. Alternatively, specify the monitoring interval within the range indicated in the message. When you do not specify the monitoring interval, the system assumes 60 seconds.

KAVV624-E

When a generic name is specified for a monitoring file, specify the number of seconds (from (numeric) to (numeric)) for the monitoring interval.

The monitoring interval is specified incorrectly for the Monitoring Files job.

(S)

Cancels processing.

(O)

Do not specify the monitoring interval. Alternatively, specify the monitoring interval within the range indicated in the message. When you do not specify the monitoring interval, the system assumes 60 seconds.

KAVV630-E

Specify the profile name.

The profile name is not specified for the Email Reception Monitoring job.

(S)

Cancels processing.

(O)

Specify the profile name.

KAVV631-E

Specify the list of senders, subjects, or message text.

The list of senders, subjects, or message text is not specified for the Email Reception Monitoring job.

(S)

Cancels processing.

(O)

Specify one of the list of senders, subjects, or message text .

KAVV632-E

You can register a maximum of 20 entries in the list of senders.

No more senders can be registered because the number of senders registered in the list of senders has reached the maximum (20 senders) for the Email Reception Monitoring job.

(S)

Cancels processing.

(O)

Delete unnecessary senders, if any, so that the list of senders contains no more than 20 senders registered.

KAVV633-E

You can register a maximum of 20 entries in the list of subjects.

No more subjects can be registered because the number of subjects registered in the list of subjects has reached the maximum (20 subjects) for the Email Reception Monitoring job.

(S)

Cancels processing.

(O)

Delete unnecessary subjects, if any, so that the list of senders contains no more than 20 subjects registered.

KAVV634-E

You can register a maximum of 20 entries in the list of message texts.

No more message texts can be registered because the number of message text sets registered in the list of message texts has reached the maximum (20 sets of message texts) for the Email Reception Monitoring job.

(S)

Cancels processing.

(O)

Delete unnecessary message text, if any, so that the list of senders contains no more than 20 sets of message texts registered.

KAVV635-E

The specification of the message text file exceeds (numeric) bytes.

The specification of a text file exceeds the limit.

(S)

Cancels processing.

(O)

Determine the definition that is valid, and then reenter it.

KAVV636-E

The specification of the folder for saving attached files exceed (numeric) bytes.

The specification of the folder for storing attached files exceeds the limit.

(S)

Cancels processing.

(O)

Determine the definition that is valid, and then reenter it.

KAVV637-E

The specification of the list file exceeds (numeric) bytes.

The list file specification exceeds the maximum.

(S)

Cancels processing.

(O)

Determine the definition that is valid, and then reenter it.

KAVV638-E

The specification of the list of received mail exceeds (numeric) bytes.

The specification of the received mail list exceeds the maximum.

(S)

Cancels processing.

(O)

Determine the definition that is valid, and then reenter it.

KAVV640-E

Specify a correlation ID.

No relative identifier is specified for the Receive MQ message job.

(S)

Cancels processing.

(O)

Specify a relative identifier.

KAVV641-E

Specify a message input queue.

No message input queue is specified for the Receive MQ Message job.

(S)

Cancels processing.

(O)

Specify a message input queue.

KAVV650-E

Enter a path name.

No path name is specified for the Receive MSMQ Message job.

(S)

Cancels processing.

(O)

Specify a path name.

KAVV660-E

Specify a file to be monitored.

No log file name is specified for the Monitoring Log Files job.

(S)

Cancels processing.

(O)

Specify a log file name.

KAVV661-E

Specify the date to be trapped.

Data to be trapped is not specified for the Monitoring Log Files job.

(S)

Cancels processing.

(O)

Specify the data you want to trap.

KAVV662-E

(delimiter) specified for a variable-length delimiter character in the record format is invalid.

An invalid character is used for the delimiter in the action definition of the Monitoring Log Files job.

(S)

Cancels processing.

(O)

For the delimiter, do not specify a backslash (\) or a character string consisting of more than 2 bytes. However, you can specify a backslash (\) as an escape character.

KAVV663-E

Specify from (numeric) to (numeric) bytes for the fixed-length of record format.

The record length is specified incorrectly in the log file action definition for the Monitoring Log Files job.

(S)

Cancels processing.

(O)

Specify the record length within the range indicated in the message.

KAVV664-E

Specify from (numeric) to (numeric) lines for the number of header lines in the header specification.

The number of header lines exceeds the maximum.

(S)

Cancels processing.

(O)

Determine the definition that is valid, and then reenter it.

KAVV665-E

Specify from (numeric) to (numeric) bytes for the header size in the header specification.

The header size exceeds the maximum.

(S)

Cancels processing.

(O)

Determine the definition that is valid, and then reenter it.

KAVV666-E

Specify from (numeric) to (numeric) seconds for the monitoring interval.

The monitoring interval is specified incorrectly in the log file action definition for the Monitoring Log Files job.

(S)

Cancels processing.

(O)

Do not set the monitoring interval. Alternatively, specify the monitoring interval within the range indicated in the message. If you do not specify the monitoring interval, the system assumes 10 seconds.

KAVV667-E

Specify from (numeric) to (numeric) bytes for the event data length.

The event data length is specified incorrectly in the log file action definition for the Monitoring Log Files job.

(S)

Cancels processing.

(O)

Do not set the event data length. Alternatively, specify the event data length within the range indicated in the message. If you do not specify the event data length, the system assumes 512 bytes.

KAVV668-E

You can register a maximum of 8 files to be monitored.

No more log files can be registered because the number of log file names registered has reached the maximum (8 files) for the Monitoring Log Files job.

(S)

Cancels processing.

(O)

Delete unnecessary log files, if any, so that no more than 8 log file names are registered.

KAVV670-E

The setting for the data to be trapped exceeds a total of (numeric) bytes.

The setting of data to be trapped in the Monitoring Log Files job exceeds the maximum.

(S)

Cancels processing.

(O)

Delete unnecessary data to be trapped, if any.

KAVV671-E

The setting for data lines except log information exceeds a total of (numeric) bytes.

Data lines other than log information exceeds the maximum for the Monitoring Log Files job.

(S)

Cancels processing.

(O)

Delete unnecessary data lines, if any, other than log information.

KAVV680-E

Specify the event type.

The event type is not specified for the Monitoring Event Log job.

(S)

Cancels processing.

(O)

Specify the event type.

KAVV681-E

Specify from (numeric) to (numeric) for the event ID.

The event ID is specified incorrectly for the Monitoring Event Log job.

(S)

Cancels processing.

(O)

Do not set the event ID. Alternatively, specify the event ID within the range indicated in the message.

KAVV690-E

Specify the waiting time.

The waiting time is not specified for the Interval Control job.

(S)

Cancels processing.

(O)

Specify the waiting time.

KAVV691-E

Specify from (numeric) to (numeric) minutes for the waiting time.

The waiting time is specified incorrectly for the Interval Control job.

(S)

Cancels processing.

(O)

Specify the waiting time within the range indicated in the message.

KAVV692-E

Enter the correlation.

The inter-relationship is not specified for the Receive MSMQ Message job.

(S)

Cancels processing.

(O)

Enter the inter-relationship.

KAVV701-E

Enter (item-name).

No item name is entered.

(S)

Cancels processing.

(O)

Enter an item name.

KAVV703-E

For the time to reach queue, specify from -2 to 2147483647.

The delivery limit time is specified incorrectly for the Send MSMQ message job.

(S)

Cancels processing.

(O)

Specify the delivery limit time within the range indicated in the message.

KAVV704-E

For the retention time, specify from -1 to 2147483647.

The retention time is specified incorrectly for the Send MSMQ message job.

(S)

Cancels processing.

(O)

Specify the retention time within the range indicated in the message.

KAVV705-E

(exception) occurred at the time of (processing). (processing).

An unexpected error occurred during processing.

(S)

Cancels processing.

(O)

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

A hardcopy of the window

JP1/AJS3 - View log files

KAVV706-E

The number of characters in (item-name) exceeds the size limit.

The length of the item name exceeds the limit.

(S)

Cancels processing.

(O)

Open the help from the dialog box indicating the error message, and then check the limit value of the indicated item name.

KAVV707-E

The input value (item-name) contains an error.

An invalid value is entered.

(S)

Cancels processing.

(O)

Open the help from the dialog box indicating the error message, and then check the definition method of the indicated item name.

KAVV709-E

The maximum number of recipients is 20.

No more addresses can be registered because the number of addresses registered in the list of addresses has reached the maximum (20 addresses ) for the Email Sending job.

(S)

Cancels processing.

(O)

Delete unnecessary addresses, if any, so that the list of addresses contains no more than 20 addresses registered.

KAVV710-E

The maximum number of attached files is 20.

No more attached files can be registered because the number of attached files registered in the list of attached files reached the maximum (20 files) for the Email Sending job.

(S)

Cancels processing.

(O)

Delete unnecessary attached files, if any, so that the list of attached files contains no more than 20 registered files.

KAVV711-E

For an event ID , Specify from 00000000 to 00001FFF, or from 7FFF8000 to 7FFFFFFF.

The event ID is specified incorrectly for the Send JP1 Event job.

(S)

Cancels processing.

(O)

For an event ID, specify a value in the range from 00000000 to 00001FFF, and from 7FFF8000 to 7FFFFFFF.

KAVV712-E

Specify a capital letter at the beginning of the extension attribute name.

A character other than a capital letter is specified for the first character of the extension attribute name for the Send JP1 Event job.

(S)

Cancels processing.

(O)

Specify a capital letter for the first character of the extension attribute name.

KAVV713-E

You cannot specify all spaces for (item-name).

A character string containing only spaces has been specified for item-name.

(S)

Cancels processing.

(O)

For item-name, do not specify a character string that contains only spaces.

KAVV714-E

Specify from 1 to 9999999 minutes for the retention time.

The retention time is specified incorrectly for the Send MQ Message job.

(S)

Cancels processing.

(O)

Do not set the retention time. Alternatively, specify the retention time within the range indicated in the message. If you do not specify the retention time, the system assumes unlimited retention.

KAVV715-E

Specify 3 to 600 seconds for the check intervals.

The check interval is specified incorrectly for the Send JP1 Event job.

(S)

Cancels processing.

(O)

To confirm the arrival of JP1 events, specify a check interval within the range indicated in the message.

KAVV716-E

Specify 0 to 999 times for the check count.

The check count is specified incorrectly for the Send JP1 Event job.

(S)

Cancels processing.

(O)

To confirm the arrival of JP1 events, specify a check count within the range indicated in the message.

KAVV780-Q

Are you sure you want to terminate the monitoring of start condition of unit-name(execution-ID)?

Confirm whether you want to discontinue monitoring the start condition.

(S)

Waits for a response.

(O)

Click Yes to discontinue monitoring the start condition. Click No to continue monitoring.

KAVV781-Q

A monitoring generation for a jobnet with start condition is included in the selected N units. Are you sure you want to terminate the monitoring of start condition?

Confirm whether you want to discontinue monitoring the start condition.

(S)

Waits for a response.

(O)

Click Yes to discontinue monitoring the start condition. Click No to continue monitoring.

KAVV782-Q

There is a possibility that multiple instances of the monitoring generation start running because the processing cycle is specified and the useful range of the start condition has been set to unrestricted. Are you sure you want to specify this setting?

Confirm whether you want to set the schedule rule.

(S)

Waits for a response.

(O)

Click Yes to set the schedule rule. Click No to cancel setting of the schedule rule.

KAVV801-E

File(file-name) cannot be found. Please verify that JP1/AJS3 - View has been correctly installed.

The file required for the custom job definition linkage was not found.

(S)

Cancels processing.

(O)

If this message is displayed when you click the Detail button in the Define tab in the Define Details - [Custom Job] dialog box, check whether the folder (SystemDrive:\temp) exists.

Use the SystemDrive:\temp folder to store temporary files when customized jobs are defined and edited. If this folder does not exist, create the SystemDrive:\temp folder. Alternatively, change the registry value to an arbitrary name of a folder to store temporary files as follows:

HKEY_LOCAL_MACHINE\SOFTWARE\HITACHI\JP1AJS2V\CustomJobTemp

Note that the folder name cannot contain spaces.

KAVV802-E

Error occurred at file(file-name) input/output.

An error occurred during input or output on the file required for the custom job definition linkage.

(S)

Cancels processing.

(O)

Check whether the disk containing the folder used for the custom job definition linkage has sufficient free space. The default is SystemDrive:\temp.

KAVV803-E

Failed to start custom job(custom-job-name). Please check whether custom job(custom-job-name) is correctly installed.

An attempt to start the custom job definition program has failed.

(S)

Cancels processing.

(O)

Check whether the definition program specified in the Register Custom Job dialog box exists.

KAVV804-E

Error occurred at registry input/output.

An error occurred when reading the registry.

(S)

Cancels processing.

(O)

Memory may be insufficient. Terminate unnecessary applications, and then re-execute the operation. If the error persists, the configuration of JP1/AJS3 - View may have been corrupted. Perform a repair installation.

KAVV812-E

The host name (connection-host-name) of the connection host cannot be resolved.

The host name indicated by connection-host-name could not be resolved.

(S)

Cancels processing.

(O)

Check the hosts file and other settings to ensure that the host name can be resolved, and then retry the operation.

KAVV813-E

(execution-ID or unit-name) of the jobnet for the connection-destination could not be obtained. Detailed information: Connection host=connection-host-name, Connection service=connection-service-name, Unit name=unit-name

The execution ID or unit name of the connection-destination jobnet could not be acquired because of an error during communication with the host on which the connection-destination jobnet resides.

(S)

Cancels processing.

(O)

Take corrective action according to the message displayed immediately before this message. If you are unable to check the previous message, start JP1/AJS3 - View and check whether you can log in to the host on which the connection-destination jobnet resides.

KAVV814-E

A different jobnet connector might be defined at the jobnet for the connection-destination. Detailed information: Connection host=connection-host-name, Connection service=connection-service-name, Jobnet Connector=jobnet-connector-name

A jobnet connector cannot be automatically created because Other service is set for Connection range of the connection-destination jobnet in the memory source.

(S)

Cancels processing.

(O)

A jobnet connector can be automatically created only when Same service is set for Connection range. If Other service is set for Connection range, manually create the jobnet connector.

KAVV815-Q

A different jobnet connector might be defined at the jobnet for the connection-destination. Are you sure you want to continue? Detailed information: Connection host=connection-host-name, Connection service=connection-service-name, Jobnet Connector=jobnet-connector-name

Other service is set for Connection range of the unit specified for Connect destination. Confirm whether you want to define a jobnet connector under these circumstances.

(S)

Waits for a response.

(O)

Click Yes to continue. Click No to cancel the processing.

KAVV816-Q

A different jobnet for the connection-destination might be defined at the jobnet connector. Are you sure you want to continue? Detailed information: Connection host=connection-host-name, Connection service=connection-service-name, Connect destination=connection-destination-name

Other service is set for Connection range of the unit specified for Jobnet Connector. Confirm whether you want to define the jobnet as the connection destination under these circumstances.

(S)

Waits for a response.

(O)

Click Yes to continue. Click No to cancel the processing.

KAVV850-Q

The jobnet for the connection-destination is not specified. Are you sure you want to continue?

Confirm whether you want to define a jobnet connector when Connect destination has not been specified.

(S)

Waits for a response.

(O)

Click Yes to continue. Click No to cancel the processing.

KAVV851-Q

The jobnet for the connection-destination does not exist. Are you sure you want to continue?

Confirm whether you want to define a jobnet connector when no unit is specified for Connect destination.

(S)

Waits for a response.

(O)

Click Yes to continue. Click No to cancel the processing.

KAVV852-E

The unit type of the jobnet for the connection-destination is invalid.

A unit other than the root jobnet or a planning group is specified for Connect destination.

(S)

Cancels processing.

(O)

Specify the root jobnet or a planning group for Connect destination.

KAVV853-Q

Another jobnet connector is defined at the jobnet for the connection-destination. Are you sure you want to continue? (unit-name)

The unit specified for Connect destination contains the definition of another jobnet connector. Confirm whether you want to define a jobnet connector under these circumstances.

(S)

Waits for a response.

(O)

Click Yes to continue. Click No to cancel the processing.

KAVV854-Q

A jobnet connector is not specified. Are you sure you want to continue?

Confirm whether you want to define a connection-destination jobnet when Jobnet Connector is not specified.

(S)

Waits for a response.

(O)

Click Yes to continue. Click No to cancel the processing.

KAVV855-Q

The jobnet connector does not exist. Are you sure you want to continue?

Confirm whether you want to define a connection-destination jobnet when no unit is specified for Jobnet Connector.

(S)

Waits for a response.

(O)

Click Yes to continue. Click No to cancel the processing.

KAVV856-E

The unit specified in the jobnet connector name is not the jobnet connector.

A unit other than the jobnet connector is specified for Jobnet Connector.

(S)

Cancels processing.

(O)

Specify a jobnet connector for Jobnet Connector.

KAVV857-Q

Another jobnet for the connection-destination is defined at the jobnet connector. Are you sure you want to continue? (unit-name)

The unit specified in Jobnet Connector contains the definition of a jobnet for another connection destination. Confirm whether you want to define the connection-destination jobnet. The unit-name is displayed in the following format:

When the connection range is the same scheduler service

full-name-of-the-unit

When the connection range is another scheduler service and the connection host name is not specified

scheduler-service-name:full-name-of-the-unit

When the connection range is another scheduler service and the connection host name is specified

host-name:scheduler-service-name:full-name-of-the-unit

(S)

Waits for a response.

(O)

Click Yes to continue. Click No to cancel the processing.

KAVV858-E

Cannot define the jobnet connector under unit-type.

A jobnet connector cannot be defined under unit-type.

(S)

Cancels processing.

(O)

Do not define a jobnet connector under unit-type.

KAVV859-E

Select a root jobnet or a planning group.

The specified operation cannot be performed with a unit other than the root jobnet or a planning group.

(S)

Cancels processing.

(O)

Select the root jobnet or a planning group, and then retry the operation.

KAVV860-E

The relation of the units is looping. (unit-name)

Highlighting cannot be used because the connection defined by the relation lines is a loop.

(S)

Cancels processing.

(O)

Remove the looping, and then retry the operation.

KAVV861-E

Select one unit in the map area.

Highlighting cannot be used because two or more units are selected in the map area.

(S)

Cancels processing.

(O)

Select only one unit in the map area, and then retry the operation.

KAVV862-E

Select the schedule for unit-type in the list of executions.

The specified operation cannot be performed because no unit-type schedule has been selected in the execution-result list.

(S)

Cancels processing.

(O)

Select a unit-type schedule in the execution-result list, and then retry the operation.

KAVV863-E

This operation cannot be executed for the jobnet connector.

The specified operation is not possible for a jobnet connector.

(S)

Cancels processing.

(O)

Perform an operation that is within the scope of a jobnet connector.

KAVV864-E

An attempt to change the definition of the stored jobnet for the connection-destination failed. (unit-name)

Jobnet Connector in the definition of the connection-destination jobnet in the memory source could not be changed.

(S)

Cancels processing.

(O)

Manually change Jobnet Connector in the definition of the connection-destination jobnet.

KAVV865-E

The jobnet for the connection-destination has no generation connected to the jobnet connector (execution-ID).

The connection-destination schedule cannot be displayed because none of the connection-destination jobnet generations is connected to a jobnet-connector generation.

(S)

Cancels processing.

(O)

Retry the operation with a connection relation between a jobnet connector generation and a connection-destination jobnet generation established.

KAVV866-E

No jobnet connector information is stored for auto-creation.

A jobnet connector cannot automatically be created because no information about jobnet connectors to be automatically created has been saved.

(S)

Cancels processing.

(O)

In the JP1/AJS3 - View window, select a connection-destination jobnet, click Option, choose Save as Jobnet Connector, and then retry the operation.

KAVV867-E

Cannot automatically create the jobnet connector because the unit is stored in another scheduler service.

An attempt was made to automatically create a jobnet connector from the information saved by a different scheduler service.

(S)

Cancels processing.

(O)

Choose the same scheduler service for Save as Jobnet Connector and Auto-create Jobnet Connector.

KAVV868-E

Cannot automatically create the jobnet connector because the jobnet for the connection-destination is already registered.

If a connection-destination jobnet has already been registered, you cannot automatically create a jobnet connector because you cannot change Jobnet Connector in the definition of the connection-destination jobnet.

(S)

Cancels processing.

(O)

Cancel registration of the connection-destination jobnet, and then automatically create another jobnet connector.

KAVV869-E

Cannot store a root jobnet in a planning group as the jobnet connector.

The root jobnet in a planning group cannot be saved as a jobnet connector because it cannot be specified as a connection-destination jobnet.

(S)

Cancels processing.

(O)

Save the information as the jobnet connector for the root jobnet in a job group or for a planning group.

KAVV870-E

Cannot delete or paste a unit that has a lower-level jobnet connector.

In suspended status, a unit that has a lower-layer jobnet connector cannot be deleted or pasted.

(S)

Cancels processing.

(O)

For suspended condition, delete or paste a unit that does not contain a jobnet connector. You can delete or paste a unit that has a lower-layer jobnet connector after you cancel registration of the unit.

KAVV871-E

The jobnet for the connection-destination does not exist.

The specified operation cannot be performed because there is no connection-destination jobnet.

(S)

Cancels processing.

(O)

Make sure that there is a connection-destination jobnet, and then retry the operation.

KAVV872-E

Another jobnet connector is defined at the jobnet for the connection-destination. (unit-name)

A jobnet connector cannot be automatically created because the connection-destination jobnet already has a definition for a different jobnet connector.

(S)

Waits for a response.

(O)

Save as a jobnet connector a connection-destination jobnet for which no jobnet connector name is defined, and then retry the operation.

KAVV873-Q

No authority for unit-type. Are you sure you want to continue? (unit-name)

Confirm whether you want to continue the specified operation despite having no reference, operate, or edit permission for the indicated unit name.

(S)

Waits for a response.

(O)

Click Yes to continue. Click No to cancel the processing.

KAVV874-E

A jobnet for the connection-destination is not specified.

Operation is not possible because a connection-destination jobnet is not specified.

(S)

Cancels processing.

(O)

Make sure that a connection-destination jobnet is specified, and then retry the operation.

KAVV875-Q

Are you sure you want to set the control method of execution order to synchronous/asynchronous mode for unit-name (execution-ID)?

Confirm whether you want to change the method for controlling the execution order of units.

(S)

Waits for a response.

(O)

Click Yes to change the method for execution order control. Click No if you do not want to change the method.

KAVV876-E

Cannot paste the jobnet connector directly under unit-type.

An attempt was made to paste a job connector into a layer in which a jobnet connector cannot be defined.

(S)

Cancels processing.

(O)

Paste the job connector into a layer in which a jobnet connector can be defined.

KAVV877-E

No authority for unit-type. (unit-name)

You cannot perform the specified operation because you do not have reference, operate, or edit permission for unit-name. The unit name is displayed in the following format:

When connection-destination jobnets in the memory source are in the same scheduler service

full-name-of-the-unit

When connection-destination jobnets in the memory source are in different scheduler services of the same host

scheduler-service-name:full-name-of-the-unit

When connection-destination jobnets in the memory source are in the scheduler services of different hosts

host-name:scheduler-service-name:full-name-of-the-unit

(S)

Cancels processing.

(O)

Perform the operation for a unit for which you have access permission.

KAVV878-E

The jobnet for the connection-destination is defined under unit-type.

A unit under unit-type cannot be specified as a connection-destination jobnet.

(S)

Cancels processing.

(O)

Specify a unit other than one under unit-type as a connection-destination jobnet, and then retry the operation.

KAVV879-E

There is no place to automatically create a jobnet connector.

A jobnet connector cannot be automatically created because there is not enough free space in the map area.

(S)

Cancels processing.

(O)

Either increase the map size or reorganize several units as nested jobnets, and then create free space in the map area. After creating the free space, retry the operation.

KAVV880-E

An upper-level unit is specified for the jobnet name for the connection-destination.

A jobnet connector cannot be defined because the upper unit is already specified as a connection-destination jobnet.

(S)

Cancels processing.

(O)

Specify a unit other than the upper unit as a connection-destination jobnet, and then retry the operation.

KAVV881-E

A lower-level unit is specified for the jobnet connector name.

A connection-destination jobnet cannot be defined because a lower unit has already been specified as the jobnet connector.

(S)

Cancels processing.

(O)

Specify a unit other than a lower unit as the jobnet connector, and then retry the operation.

KAVV882-E

The specified jobnet name for the connection-destination is invalid.

The unit name specified in Connect destination is invalid.

Probable causes are:

The unit name does not begin with a forward slash ("/").

A part of the unit name between forward slashes exceeds 30 bytes#.

The unit name ends with a forward slash.

#

In a UTF-8 environment, if the setting for changing the number of characters specifiable for unit names or other items is enabled, the length is 30 bytes based on Shift-JIS encoding.

(S)

Cancels processing.

(O)

Specify a correct unit name for Connect destination, and then retry the operation.

KAVV883-E

The specified jobnet connector name is invalid.

The unit name specified for Jobnet Connector is invalid.

Probable causes are:

The unit name does not begin with a forward slash ("/").

A part of the unit name between forward slashes exceeds 30 bytes#.

The unit name ends with a forward slash.

#

In a UTF-8 environment, if the setting for changing the number of characters specifiable for unit names or other items is enabled, the length is 30 bytes based on Shift-JIS encoding.

(S)

Cancels processing.

(O)

Specify a correct unit name for Jobnet Connector, and then retry the operation.

KAVV884-E

Cannot paste a unit that contains a jobnet connector under a remote jobnet.

A unit containing a jobnet connector in a lower-level layer of a remote jobnet cannot be pasted.

(S)

Cancels processing.

(O)

Do not paste the unit containing the jobnet connector because a jobnet connector cannot be defined in a lower-level layer of a remote jobnet.

KAVV885-E

Cannot automatically create the jobnet connector because an upper-level unit is stored as the jobnet connector.

A jobnet connector cannot be automatically created because the upper unit has already been saved as a jobnet connector.

(S)

Cancels processing.

(O)

Save a unit other than the upper unit as the jobnet connector, and then automatically create the jobnet again.

KAVV886-E

The unit to be operated is the jobnet for the connection-destination. The specified operation cannot be performed because unit-type is defined.

The unit subject to the operation is a connection-destination jobnet. The specified operation cannot be performed because a unit-type has already been defined.

(S)

Cancels processing.

(O)

Delete the unit-type, and then retry the operation.

KAVV887-E

The specified operation cannot be performed because the jobnet connector is in a jobnet that has a start condition.

The specified operation cannot be performed because the jobnet connector is in a jobnet that has a start condition.

(S)

Cancels processing.

(O)

To use the jobnet connector, delete the start condition, and then retry the operation.

KAVV888-E

The unit to be operated is a root jobnet that is directly under the planning group for the connection destination. The specified operation cannot be performed because unit-type is defined.

The unit subject to the operation is the root jobnet directly under the connection-destination planning group. The specified operation cannot be performed because a unit-type has already been defined.

(S)

Cancels processing.

(O)

Delete the unit-type, and then retry the operation.

KAVV889-E

The specified operation cannot be performed because the root remote jobnet is directly under the planning group for the connection destination.

The root remote jobnet directly under the connection-destination planning group cannot be registered for execution.

(S)

Cancels processing.

(O)

Define a root remote jobnet that is directly under the job group or directly under a planning group other than the connection-destination planning group, and retry the operation.

KAVV890-E

The specified operation cannot be performed for the unit-type.

The specified operation cannot be performed for the specified unit type.

(S)

Cancels processing.

(O)

Retry the operation for a different type of unit.

KAVV1300-E

The specified operation cannot be performed while the detail information area display line is selected.

This operation is not applicable if a display line has already been selected in the detail information area.

(S)

Cancels processing.

(O)

Select a unit in the list area, and then retry the operation.

KAVV1301-E

The specified operation cannot be performed for the specified type of unit because 'function-menu-name' is selected in the function menu.

An attempt was made to perform an operation on a unit for which the operation is not allowed when function-menu-name has already been selected.

(S)

Cancels processing.

(O)

Change the selected function menu, and then retry the operation.

KAVV1302-E

Cannot paste the specified type of unit because ' function-menu-name ' is selected in the function menu.

An attempt was made to paste a unit that cannot be pasted when function-menu-name has already been selected.

(S)

Cancels processing.

(O)

Change the selected function menu, and then retry the paste operation.

KAVV1303-E

The specified operation cannot be performed for a registered jobnet because ' function-menu-name ' is selected in the function menu.

When function-menu-name is selected, the specified operation cannot be performed for a jobnet registered for execution.

(S)

Cancels processing.

(O)

To view the definition of the jobnet registered for execution, select Status Monitor in the function menu, and then retry the operation.

To update the definition of the jobnet registered for execution, either select Status Monitor in the function menu and then change the status to Suspended, or cancel the registration if necessary and then retry the operation.

KAVV1304-I

' function-menu-name ' was selected in the function menu.

This message reports that function-menu-name has been selected.

(S)

Outputs the information that function-menu-name has been selected to the log.

KAVV1305-E

Select a jobnet, a job, or a planning group.

The selected operation cannot be executed because no job, jobnet, or planning group is selected.

(S)

Cancels processing.

(O)

Select a job, jobnet, or planning group and then retry.

KAVV1314-E

A unit (unit-name) was not found. The unit might have been deleted or the name changed.

An attempt was made to operate on a unit that might have been deleted or renamed.

(S)

Cancels processing.

(O)

Click Refresh or close and open the window again.

KAVV1315-E

The specified operation cannot be performed for the units under the remote jobnet.

An illegal operation was performed on units in a remote jobnet.

(S)

Cancels processing.

(O)

Do not perform such operations on units in a remote jobnet.

KAVV1316-E

An attempt to read the properties of one or more custom jobs failed. One or more registered custom jobs cannot be used.

An error occurred during input to a file.

In the Jobnet Editor window, custom job icons for some or all of the registered custom jobs are not displayed. As a result, a new custom job cannot be created and existing custom jobs cannot be edited.

The probable causes are:

Read and write permissions have not been set for the files in the custom job registration information folder.

A file in the custom job registration information folder was deleted or renamed.

The hidden file attribute is set for the applicable file in the custom job registration information folder.

The location of the custom job registration information folder is as follows:

For Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

For Windows Server 2003 or Windows XP Professional

JP1/AJS3 - View-installation-folder\custom.dir

(S)

Ignores the custom job registration information and continues processing.

(O)

Correct the cause of the error, and then restart JP1/AJS3 - View.

If you cannot correct the error, the custom job registration information might have been corrupted.

Delete all the following files in the custom job registration information folder, and then register all custom jobs again:

type_map.txt

*.CJI

KAVV1500-E

An input value from the execution agent is not allowed on the connection destination.

The connection destination does not permit the value entered to specify an execution agent.

(S)

Cancels processing.

(O)

Check what values can be defined and re-enter a value.

KAVV1501-Q

An input value from the execution agent is not allowed on the connection destination. Do you want to continue processing?

The connection destination does not permit the value entered to specify an execution agent.

(S)

Waits for a response.

(O)

Click Yes to continue the operation or No to cancel.

KAVV1502-Q

Execution agent profile information failed to be acquired. The execution agent profile might have been changed. Do you want to continue processing?

(Detailed information: maintenance-information, maintenance-information)

Information could not be acquired from the execution agent profile due to a temporary lock error or other error. As a result, the system was unable to check whether the execution agent specified in the Define Details dialog box has been set in the execution agent profile.

(S)

Waits for a response.

(O)

Click Yes to continue the operation or No to cancel.

If you click Yes, the system will continue processing without checking whether the execution agent specified in the Define Details dialog box has been set in the execution agent profile.

If you click No, processing will be canceled. To perform the check, click OK in the Define Details dialog box.

If this message appears repeatedly, an error might have occurred in JP1/AJS3 - Manager. Investigate the logged data in the Windows event log or syslog on the manager host. Remove the cause of the error, based on what you find. For details about log file contents, see 1.2 Types of log information and storage locations in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. For log information details, see C. Log Information in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KAVV1503-E

The specified waiting unit (unit-name) is invalid.

The unit name specified in Waiting-target unit is invalid.

Probable causes are:

The unit name does not begin with a forward slash ("/").

A part of the unit name between forward slashes exceeds 30 bytes#1.

A part of the unit name between forward slashes is 0 bytes.

The unit name ends with a forward slash.

The maximum value for the unit hierarchy#2 was exceeded.

#1

If the environment at the connection destination is a UTF-8 environment and the setting#3 for changing the number of characters specifiable for unit names or other items is enabled, the length is 30 bytes based on Shift-JIS encoding.

#2

The maximum value for the unit hierarchy is 30 levels from directly under the root job group (excluding the root job group).

If the environment at the connection destination is a UTF-8 environment and the setting#3 for changing the number of characters specifiable for unit names or other items is enabled, the maximum value for the unit hierarchy is 10, counting from directly under the root job group (excluding the root job group).

#3

For details about how to specify this setting, see 15.1.9 Setting for changing the number of characters specifiable for a unit name in a UTF-8 environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

(S)

Cancels processing.

(O)

Correctly set the unit whose end is being waited for. Specify the full name of the unit in Waiting-target unit.

KAVV1504-Q

The specified unit (unit-name) either does not exist or you do not have the proper permissions. Do you want to continue processing?

The specified unit does not exist or you do not have the proper permission.

(S)

Waits for a response.

(O)

Click Yes to continue processing or No to cancel.

KAVV1505-E

The specified unit or the unit type of the upper-level unit is invalid.

The unit type of the specified unit or its upper-level unit is incorrect. The specified operation cannot be performed.

(S)

Cancels processing.

(O)

Check the unit type of the unit whose end is being waited for.

KAVV1507-E

A waiting unit and a waiting condition unit are the same unit.

A wait condition cannot be set because the unit for which the wait condition is to be set is also specified as Waiting-target unit.

(S)

Cancels processing.

(O)

For Waiting-target unit, specify a unit that is different from the unit for which the wait condition is to be set.

KAVV1508-E

The specified operation cannot be performed for the start conditions.

The specified operation cannot be performed on a start condition.

(S)

Cancels processing.

(O)

Do not perform prohibited operations on a start condition.

KAVV1509-E

The specified operation cannot be performed for the event jobs under the start conditions.

The specified operation cannot be performed on an event job set as a start condition.

(S)

Cancels processing.

(O)

Do not perform prohibited operations on an event job set as a start condition.

KAVV1510-E

The specified waiting unit is already registered.

The wait condition cannot be set because the unit name specified in Waiting-target unit is already registered.

(S)

Cancels processing.

(O)

Check the wait conditions set previously.

KAVV1513-Q

The registered waiting unit will be deleted. Are you sure you want to continue?

Confirm whether to unregister the unit whose end is being waited for.

(S)

Waits for a response.

(O)

Click Yes to continue the operation or No to cancel.

KAVV1514-E

To set waiting conditions, either undone the registration or invoke the suspend status.

Wait conditions cannot be set because the jobnet is already registered for execution.

(S)

Cancels processing.

(O)

To set a wait condition, first unregister or suspend the root jobnet.

KAVV1515-E

The specified waiting unit is a lower-level unit of a unit for which waiting conditions are set.

The wait condition cannot be set because the unit specified in Waiting-target unit is a lower-level unit of the unit for which you are setting the wait condition.

(S)

Cancels processing.

(O)

In Waiting-target unit, specify a unit that is not a lower-level unit of the unit for which you are setting the wait condition.

KAVV1516-E

The specified waiting unit is an upper-level unit of a unit for which waiting conditions are set.

The wait condition cannot be set because the unit specified in Waiting-target unit is an upper-level unit of the unit for which you are setting the wait condition.

(S)

Cancels processing.

(O)

In Waiting-target unit, specify a unit that is not an upper-level unit of the unit for which you are setting the wait condition.

KAVV1700-Q

The selected number-of-rules schedule rules will be deleted. Are you sure you want to continue?

Confirm whether to delete the schedule rules.

(S)

Waits for a response.

(O)

Click Yes to delete the rules or No to cancel.

KAVV1701-Q

Number-of-rules schedule rules will be created for number-of-minutes minutes from time to time. Are you sure you want to continue?

Confirm whether to create the indicated number of schedule rules.

(S)

Waits for a response.

(O)

Click Yes to create the schedule rules or No to cancel.

KAVV1702-Q

There are number-of-rules schedule rules left before the limit is reached. The number-of-rules schedule rules from time and on cannot be created. Are you sure you want to continue?

Confirm whether to continue creating schedule rules until the maximum number of rules is reached.

(S)

Waits for a response.

(O)

Click Yes to continue creating the schedule rules or No to cancel.

KAVV1703-E

Specify an end time that is after the start time.

Repetition cannot be set because the last start time is earlier than the start time. Correct the specified values.

You can create a repeated schedule only within the same day. To set a repeated schedule that runs into the following day, set the repetition based on a 48-hour schedule (00:00 to 47:59) or create separate repetition settings for each consecutive day.

(S)

Cancels processing.

(O)

Retry specifying a last start time that is later than the start time.

KAVV1704-E

Repetition cannot be set because the interval from the start time to the end time is shorter than the start interval.

Repetition cannot be set because the time from the start time to the last start time is shorter than the start interval.

(S)

Cancels processing.

(O)

Check the values set as the start time, last start time, and start interval. Retry the operation, specifying values so that the time from the start time to the last start time is longer than the start interval.

KAVV2100-E

The specified release path is invalid.

The unit name specified for Release target is invalid.

Probable causes are:

The unit name does not begin with a forward slash ("/").

The unit name ends with a forward slash.

(S)

Cancels processing.

(O)

Specify a correct unit name for Release target, and then retry the operation.

KAVV2101-E

The release source jobnet and release target jobnet are the same.

Release entry is not possible because the same unit has been specified for both Release target and Release source.

(S)

Cancels processing.

(O)

Specify different units for Release target and Release source, and then retry release entry.

KAVV2102-E

'AJS' cannot be specified at the beginning of the release ID.

The string AJS was specified at the beginning of Release ID, where it is not allowed.

(S)

Cancels processing.

(O)

Specifying a string other than AJS at the beginning of Release ID.

KAVV2103-Q

The release target jobnet name is not included in the release source jobnet name. Are you sure you want to perform release entry?

This message asks you to confirm that you want to perform release entry if the name of the release-source jobnet does not begin with the jobnet name specified for Release target.

The following shows examples when the confirmation message is displayed and when it is not:

Example 1: When the confirmation message is not displayed

Release-target jobnet name: Jobnet A

Release-source jobnet name: Jobnet A2

Example 2: When the confirmation message is displayed

Release-target jobnet name: Jobnet A

Release-source jobnet name: Jobnet B

Example 3: When the confirmation message is displayed

Release-target jobnet name: Jobnet B2

Release-source jobnet name: Jobnet B

Note that if the release-source jobnet and the release-target jobnet are at different levels but have the same name, the confirmation message is not displayed.

(S)

Waits for a response.

(O)

Click Yes to perform release entry. Click No to cancel release entry.

KAVV2104-E

The specified operation cannot be performed because the state of release wait, delete wait, or release entry wait exists.

The specified operation cannot be executed because the status of the jobnet definition is Release wait, Delete wait, or Release entry wait.

(S)

Cancels processing.

(O)

Check the release status of the jobnet.

KAVV2105-E

The specified operation cannot be performed because a past date is specified for the release date.

A past date/time is specified for Release date.

(S)

Cancels processing.

(O)

Specify the current time or a later value for Release date, and then retry the operation.

KAVV2106-E

The release target jobnet or the release source jobnet does not exist.

There is no unit specified as the release source or release target.

Probable causes are:

The unit name specified for Release target is invalid.

An attempt was made to delete or rename the Release source unit.

(S)

Cancels processing.

(O)

Check whether there is a release source or release-target unit. Also make sure that Release target is correctly specified.

KAVV2107-E

The user does not have access privileges for a release source jobnet or a release target jobnet.

The specified operation cannot be executed because the release-source or release-target jobnet does not have access permissions.

(S)

Cancels processing.

(O)

Perform the operation on a jobnet that has access permissions.

KAVV2108-E

The unit type of the release target jobnet or the release source jobnet is invalid.

The specified operation cannot be executed because the release-source or release-target unit type is invalid.

(S)

Cancels processing.

(O)

Choose Refresh, and make sure that the release-source or release-target jobnet has a unit type that permits release entry. Also make sure that no recovery attribute has been set.

KAVV2109-E

The specified operation cannot be performed because a nest remote jobnet exists in the release source jobnet or the release target jobnet.

The specified operation cannot be executed for a release source or release target that has a nested remote jobnet.

(S)

Cancels processing.

(O)

Delete the nested remote jobnet at the release source or release target, and then retry the operation.

KAVV2111-E

The specified unit is currently being released elsewhere.

The specified operation cannot be executed because another user is releasing the release-target jobnet.

(S)

Cancels processing.

(O)

Make sure that an operation is not being performed on the release-target jobnet.

KAVV2112-E

The specified operation cannot be performed because a generation exists on the release date or later.

The specified operation cannot be executed because a generation at or after the release date exists.

(S)

Cancels processing.

(O)

Change the generation schedule, or set the release date for the planned generation or later, and then retry the operation.

KAVV2113-E

The specified operation cannot be performed because a running generation exists on the release date or later.

The specified operation cannot be executed because there is a generation that is running at the release date or later.

(S)

Cancels processing.

(O)

Terminate the generation running at the release date or later, and then retry the operation.

KAVV2115-E

The specified operation cannot be performed because the start condition and the jobnet connector exist in the release source jobnet or the release target jobnet.

The specified operation cannot be executed for a jobnet that has both a start condition and a job connector.

(S)

Cancels processing.

(O)

Delete the start condition or the jobnet connector from the definition of the release-source or release-target jobnet, and then retry the operation.

KAVV2116-E

The specified operation cannot be performed because the release source jobnet or the release target jobnet is a jobnet for the connection-destination that has a start condition.

The specified operation cannot be executed for a jobnet with a start condition that has been defined as a connection-destination jobnet.

(S)

Cancels processing.

(O)

Delete the start condition in the jobnet definition of the release-source or release-target jobnet, or cancel the execution order control setting, and then retry the operation.

KAVV2117-E

The specified operation cannot be performed because the release source jobnet or the release target jobnet is a jobnet for the connection-destination that has a jobnet connector.

The specified operation cannot be executed for a jobnet that is defined as a connection-destination jobnet if there is a jobnet connector under the jobnet.

(S)

Cancels processing.

(O)

Delete the jobnet connector in the definition of the release-source or release-target jobnet, or cancel the execution order control setting, and then retry the operation.

KAVV2119-E

The specified operation cannot be performed because the unit hierarchy exceeded the maximum value in the release target jobnet.

The number of release-target layers has exceeded the maximum value.

(S)

Cancels processing.

(O)

Reduce the number of layers of the release-source unit.

The maximum value for the unit hierarchy is 30 levels from directly under the root job group (not including the root job group).

In a UTF-8 environment, when the setting for changing the number of characters specifiable for unit names or other items is enabled, note that the maximum value for the unit hierarchy is 10, counting from directly under the root job group (excluding the root job group). For details about how to set that the number of characters used to specify unit names or other items can be changed in a UTF-8 environment, see 15.1.9 Setting for changing the number of characters specifiable for a unit name in a UTF-8 environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

KAVV2120-E

An unnecessary jobnet was defined because it failed the release entry. Resolve the problem, perform release cancel, and then perform the release entry again.

An unnecessary jobnet definition remained when release entry failed.

(S)

Cancels processing.

(O)

Resolve the problem, cancel the release, and then retry release entry.

KAVV2200-Q

jobnet-name will stop the release. Continue?

Confirm whether you want to cancel release of the jobnet.

(S)

Waits for a response.

(O)

Click Yes to cancel release entry. Click No to continue release entry.

KAVV2201-E

The specified unit is not registered for release.

The selected operation cannot be executed for a unit for which release entry is not performed.

(S)

Cancels processing.

(O)

Choose Refresh, check whether the unit subject to the operation is correctly specified, and then retry the operation.

KAVV2202-E

The specified operation cannot be performed because the state of release wait, delete wait, or release entry wait does not exist.

The specified operation cannot be executed because the specified jobnet does not have a jobnet definition whose status is Release wait, Delete wait, or Release entry wait.

(S)

Cancels processing.

(O)

Check the release status of the jobnet.

KAVV2203-E

Failed to delete the jobnet definition while processing release cancel.

Deletion of a jobnet definition failed during processing to cancel release.

(S)

Cancels processing.

(O)

Resolve the problem, and then retry cancellation of the release.

KAVV2300-E

The maximum number of selectable execution status monitor units is number-of-units.

The total number of units for which execution status is to be monitored has exceeded the maximum value.

(S)

Cancels processing.

(O)

Check the maximum number of units that can be monitored.

Note that you need to close JP1/AJS3 - View if you want to change the maximum number of units that can be monitored.

KAVV2301-E

A unit where two or more generations exist has been selected.

Execution is not possible because the operation is intended for a unit that has multiple generations.

(S)

Cancels processing.

(O)

Select a unit that has only one generation, and then retry the operation.

KAVV2302-E

This operation cannot be executed for the specified generation.

Operation is not possible because the specified generation is not in the jobnet for which the operation is intended.

(S)

Cancels processing.

(O)

Make sure that the status of the corresponding generation is displayed in the JP1/AJS3 - View window.

KAVV2304-E

This operation cannot be executed for units selected by the summary list.

The specified operation cannot be performed for a unit selected from the summary list.

(S)

Cancels processing.

(O)

Perform an operation that matches scope of the selected unit.

KAVV2308-E

This operation cannot be executed for units selected by the unit detailed information list.

The specified operation cannot be performed for a unit selected in Unit detailed information list.

(S)

Cancels processing.

(O)

Perform an operation that matches scope of the selected unit.

KAVV2311-E

The selected unit is already set on the monitored units list.

The unit selected in Selectable units is already in Monitored units.

(S)

Interrupts the processing for setting Monitored units.

(O)

Select a unit in Selectable units that has not already been set in Monitored units.

KAVV2312-E

The maximum number of units that can be set on the monitored units list is number-of-units.

Setting of Monitored units is not possible because the maximum value for total number of units that can be set in Monitored units has been reached.

(S)

Cancels processing.

(O)

Open Help from the dialog box in which the error message was displayed, and check the maximum number of units that can be monitored.

Note that you need to close JP1/AJS3 - View if you want to change the maximum number of units that can be monitored.

KAVV2313-E

(unit-name) was not found. It might have been deleted or the unit name might have been changed.

An attempt was made to process a unit that had been deleted or renamed as a target of execution status monitoring.

(S)

Cancels processing.

(O)

If an error occurred while the Summary Monitor window was being opened or was displayed

Display the Monitoring Unit Select dialog box, and check for the unit.

If an error occurred in the Monitoring Unit Select dialog box

Close the Monitoring Unit Select dialog box and then display it again to continue the operation.

KAVV2314-E

This unit cannot be monitored as an execution status monitored unit.

The specified unit is not a unit that can be set as a target of execution status monitoring.

Probable causes are:

The unit type that is set in Summary list was changed before or when the Summary Monitor window was displayed.

The unit type that is set in Monitoring unit list was changed when the Monitoring Unit Select dialog box was displayed.

(S)

Cancels processing.

(O)

Check whether the problem unit is a unit that can be set as the target of monitoring the status of execution.

KAVV2315-E

Under the selected units, there are some units that have already been set on the monitored units list.

The units under the unit selected in Selectable units include units that have already been set in the list of selected units.

(S)

Ignores units that have already been set in the list of selected units, and continues the processing for setting the list of units.

(O)

Select units in Selectable units that have not already been set in the list of selected units.

KAVV2318-E

There are no selectable monitored units.

The Monitoring Unit Select dialog box does not contain any units that are to be displayed in the tree area for selectable units.

(S)

Cancels processing.

(O)

Probable causes are:

A communication error occurred in the connection-destination JP1/AJS3 - Manager.

The database for the scheduler service defined in the connection-destination JP1/AJS3 - Manager is not an embedded database.

KAVV2400-E

The scheduler service name of the location to search is invalid.

The scheduler-service-name specified in Search location is invalid.

(S)

Cancels processing.

(O)

Specify the scheduler service on the connection-destination manager, and then retry the operation.

This message is also displayed in the Jobnet Editor window opened directly from a linkage product or in the Search window opened from the Jobnet Monitor window if you specify anything other than the scheduler service displayed in the originally opened Jobnet Editor window or Jobnet Monitor window.

KAVV2401-E

' field-name' cannot be specified for the comparison method because match-method has not been input.

The comparison method indicated by match-method cannot be specified because a value for the search condition indicated by field-name has not been entered yet.

(S)

Cancels processing.

(O)

If the value for the search condition indicated by field-name has not been entered yet, specify Equals or Does not equal as the comparison method, and then retry the operation.

When Equals is specified, the search result contains units for which the particular item is undefined or for which there is no value (0 bytes). When Does not equal is specified, the search result contains units for which the particular item is defined or there is a value other than 0 bytes.

KAVV2402-Q

The search condition has already been updated in another window. If this operation continues, all of the search conditions, including the specified search condition, will be updated. Are you sure you want to continue?

Confirm whether you want to overwrite all the search conditions saved in the target search conditions file with the contents displayed in the currently active window.

(S)

Waits for a response.

(O)

Click Yes to continue the processing. Click No to cancel the processing.

KAVV2403-Q

Are you sure you want to delete the search condition (search-condition-name)?

Confirm whether you want to delete the search condition for the displayed name.

(S)

Waits for a response.

(O)

Click Yes to delete the condition. Click No to cancel the processing.

KAVV2404-E

Cannot save the search condition because the number of saved conditions has reached the maximum value (upper-limit-value).

The number of saved search conditions has reached the upper limit.

(S)

Cancels processing.

(O)

Delete unnecessary search conditions, and then retry the operation.

KAVV2405-Q

The search condition (search-condition-name) already exists. Are you sure you want to overwrite it?

Confirm whether you want to overwrite and save the search condition for the displayed name.

(S)

Waits for a response.

(O)

Click Yes to overwrite and save the condition. Click No to cancel the processing.

KAVV2406-I

The search condition (search-condition-name) was saved.

This message reports that the search condition has been saved.

(S)

Reports that the search condition has been saved.

KAVV2407-I

The search condition (search-condition-name) was deleted.

This message reports that the search condition has been deleted.

(S)

Reports that the search condition has been deleted.

KAVV2408-E

There is a possibility that the release status of full-unit-name has been changed. Search again and update the search result list area.

An attempt was made to perform an operation on a unit for which the release status had changed.

(S)

Cancels processing.

(O)

Perform the search again, update the area for listing search results, and then retry the operation.

KAVV2409-E

unit-name was not found. It might have been deleted or the unit name might have been changed. Search again and update the search result list area.

An attempt was made to perform an operation on a unit that had been deleted or renamed.

(S)

Cancels processing.

(O)

Perform the search again in the Find window, update the area for listing search results, and then retry the operation.

KAVV2410-E

For the beginning of specify period, specify date and time before the end.

The search could not be performed because the start time specified in Specify period is later than the end time.

(S)

Cancels processing.

(O)

Change the start time specified in Specify period to earlier than the end time.

KAVV2411-E

Cannot monitor the unit (unit-name) because the number of monitored units has reached the maximum value.

The unit indicated in unit-name cannot be monitored in the Summary Monitor (Temporary) window because the number of units that can be monitored in the Summary Monitor window has reached the limit.

(S)

Cancels processing.

(O)

Increase the number of monitored units that can be registered in the summary list area of the JP1/AJS3 - View (Summary Monitor window) and then retry.

If you have already increased the number of monitored units to the maximum allowed, select a unit in the Unit name field in the Search window and open a new Summary Monitor (Temporary) window.

KAVV2412-Q

The change of settings is effective until the Summary Monitor (Temporary) window is closed. Are you sure you want to continue?

Confirm whether to close the Summary Monitor (Temporary) window, discarding all changes.

(S)

Waits for a response.

(O)

Click Yes to discard all changes or No to cancel.

KAVV2500-E

The specified operation cannot be performed for jobnets to which the release status is not currently applied.

The specified operation cannot be executed because the release status is not applicable to the specified jobnet.

(S)

Cancels processing.

(O)

Check the release status of the jobnet.

KAVV2501-E

The specified operation cannot be performed for jobnets for which release entry has been performed.

The specified operation cannot be executed for a jobnet for which release entry has been performed.

(S)

Cancels processing.

(O)

Choose Refresh, check whether the unit for which the operation is intended is correctly specified, and then retry the operation.

KAVV2502-E

The specified operation cannot be performed because release entry has been performed for the jobnet for the connection-destination.

The specified operation cannot be executed because the connection-destination jobnet has already been registered for release.

(S)

Cancels processing.

(O)

Choose Refresh, check whether the unit for which the operation is intended is correctly specified, and then retry the operation.

KAVV2507-E

The specified operation cannot be performed for definitions for which the release status is not being applied.

The specified operation cannot be performed because the release status of the specified unit is not Being applied.

The probable causes are:

An attempt was made to open the Wait Conditions Settings List window for a unit whose release status is not Being applied.

An attempt was made to execute the ajsprint command for a unit whose release status is not Being applied.

(S)

Cancels processing.

(O)

Check the release status of the unit.

KAVV2508-E

The specified range is invalid.

The specified range does not contain an integer value.

(S)

Cancels processing.

(O)

Specify upper and lower limit values that include an integer value in the range.

KAVV2510-E

The specified return code range is invalid.

The specified range does not contain an integer value.

If the retry settings contain an error, the probable causes are:

The lower limit of the return code for a job to be retried automatically is equal to or smaller than the abnormal threshold.

The upper limit of the return code for a job to be retried automatically is equal to or smaller than the abnormal threshold.

The upper limit of the return code for a job to be retried automatically is smaller than the lower limit.

(S)

Cancels processing.

(O)

Specify upper and lower limit values that include an integer value in the range.

KAVV2700-E

The execution ID being monitored and the release ID have been changed. The jobnet definition might have been changed. Please display the Jobnet Monitor window again.

Changes to the execution ID and release ID being monitored might have also caused the currently displayed jobnet definition to change.

(S)

Cancels processing.

(O)

Close the Jobnet Monitor window, and then open it again.

KAVV3100-E

The specified operation cannot be performed because the schedule will be created across the release date.

An attempt was made to create a schedule that spans the release date.

(S)

Cancels processing.

(O)

Check whether the intended operation is correct, and then retry the operation.

KAVV3101-E

The release status might have been changed for full-unit-name Select 'Refresh' to update the list area.

An attempt was made to perform an operation on a unit for which the release status had changed.

(S)

Cancels processing.

(O)

Choose Refresh to update the list area, and then retry the operation.

KAVV3102-E

Connection denied.

Connection to the manager host failed because the IP address of the connecting JP1/AJS3 - View host was not registered in the manager connection permission configuration file on the destination manager host.

(S)

Cancels processing.

(O)

Take the corrective action specified in the KAVS8040-E message that was output to the integrated trace log on the destination manager host.

KAVV3301-E

Failed to copy to the clipboard. Reason: reason

An attempt to copy to the clipboard failed.

(S)

Cancels processing.

(O)

Remove the cause of the error, and then retry the operation.

KAVV3302-E

The display area for the processing target might have been updated during process-name. Try the operation again.

The display area that was to be processed might have been updated during process-name processing.

(S)

Cancels processing.

(O)

Update the display area, and then retry the operation.

KAVV3303-E

The specified operation cannot be performed because multiple root jobnets and nest jobnets or root jobnets and jobs have been selected simultaneously.

This operation cannot be executed because multiple root jobnets and nested jobnets or jobs are selected at the same time.

(S)

Cancels processing.

(O)

Select a combination of only root jobnets or a combination of only nested jobnets or jobs, and then retry the operation.

KAVV3304-E

Select the generation you want to manipulate.

An attempt was made to perform the operation without first selecting a generation.

(S)

Cancels processing.

(O)

Select a generation for executing the operation, and then retry the operation.

KAVV3305-E

Specify a job group or a root jobnet.

The selected operation can be executed only for a job group or root jobnet.

(S)

Cancels processing.

(O)

Select a job group or root jobnet, and then retry the operation.

KAVV3306-E

Specify a job or a jobnet.

The selected operation can be executed only for the job or jobnet.

(S)

Cancels processing.

(O)

Select a job or jobnet, and then retry the operation.

KAVV3307-E

The specified operation cannot be performed for a job that is directly under a job group.

The selected operation is not applicable to any job directly under the job group.

(S)

Cancels processing.

(O)

Select a job directly under the job group, and then retry the operation.

KAVV3308-E

Select some units in the list.

An attempt was made to perform the operation without selecting a unit in the list.

(S)

Cancels processing.

(O)

Select a unit in the list, and then retry the operation.

KAVV3309-E

An attempt to start the external program failed. (cmdline: (command-line), reason: (maintenance-information))

The external program indicated in command-line failed to start. The probable causes are:

No executable file exists.

You do not have execute permission for the executable file.

The environment variable PATH is set incorrectly.

Single-byte spaces are missing before and after the replacement string, if being used.

(S)

Does not start the external program indicated in command-line.

(O)

Remove the cause of the error, and then start the external program.

KAVV3310-I

CJX_OPEN: custom-job-extended-settings-file-name

A log entry reports that the system read the indicated custom job extended settings file.

(S)

Starts JP1/AJS3 - View according to the contents defined in the custom job extended settings file.

KAVV3311-I

The (control-name-2) was (operation) on (control-name-1). (maintenance-information)

Information about a GUI operation in JP1/AJS3 - View was logged.

(S)

Continues processing the operation.

KAVV3312-E

Specify the (item-name) at the settings file. (setting-file-name), (tag-name)

item-name has not been specified in tag-name in setting-file-name.

(S)

Cancels processing.

(O)

Specify item-name in tag-name.

KAVV3313-E

There is already an output macro variable with the same name.

Duplicated input data.

(S)

Cancels processing.

(O)

Enter a value that does not duplicate existing data.

KAVV3314-E

No more passing information can be defined because limit for the total number of bytes that can be used for output macro variables names has been reached.

No more passing information can be defined because the total byte count of the passing information has reached the limit.

Set the macro variable names so that the total number of bytes# for those names in the target unit is no more than 1,023.

#

Number-of-bytes-of-macro-variable-names-excluding-the-beginning-?AJS2-and-the-ending-? + 4 (bytes)

(S)

Cancels processing.

(O)

Delete unneeded passing information and check whether any macro variable names can be shortened.

KAVV3315-E

The specified operation cannot be performed for units for which waiting conditions are not set.

The specified operation cannot be performed because no wait conditions have been set for the specified unit.

(S)

Cancels processing.

(O)

Do not perform this operation on a unit that has no wait conditions.

KAVV3316-E

A maximum of number-of-units units can be set for the field-name field.

The total number of units that can be set for the indicated field exceeds the limit.

(S)

Cancels processing.

(O)

Check the maximum number of units that can be set.

KAVV3318-I

Display items (display-item-names) have not been acquired. Retry your search.

The values of the display item names indicated in the message appear as blanks because their values were not acquired by the previous search.

(S)

Continues processing.

(O)

Retry the search to acquire the values of the display item names indicated in the message.

KAVV3319-I

A temporary change is being re-executed. Please wait...

This message reports that a temporary change is being re-executed.

(S)

Waits for a response.

(O)

Click Cancel if you want to cancel the processing.

KAVV3320-Q

The selected temporary changes (number-selected selected) will be re-executed in ascending order by operation date and time. Are you sure you want to continue?

Confirm whether to re-execute the selected temporary changes in ascending order by operation date and time.

(S)

Waits for a response.

(O)

Click Yes to re-execute the temporary changes or No to cancel.

KAVV3321-Q

An attempt to re-execute a temporary change (operation-time, unit-name, operation-type) failed. Do you want to continue processing?

Re-execution of temporary changes failed. Confirm whether to continue processing.

(S)

Waits for a response.

(O)

Click Yes to continue processing or Yes for all to continue processing without this message appearing again. Click No to cancel processing.

KAVV3322-I

All the temporary changes were successfully re-executed.

This message reports that all the selected temporary changes were successfully re-executed.

(S)

Continues processing.

KAVV3323-I

The re-execution of a temporary change (operation-time, unit-name, operation-type) was cancelled.

This message reports that re-execution of temporary changes has been canceled by the user.

(S)

Cancels re-execution of all temporary changes from operation-time onward.

KAVV3324-E

Temporary change (operation-time, unit-name, operation-type) information does not exist.

An attempt was made to re-execute a temporary change on a deleted unit, an unregistered unit, or a unit that might have expired.

(S)

Cancels processing.

(O)

Click Update in the Temporary Changes dialog box to refresh the listed information and check for any erroneous items.

KAVV3325-I

Temporary change information does not exist.

This message reports that there are no temporary changes to list.

(S)

Continues processing.

KAVV3326-I

Temporary change information is now being acquired. Please wait...

This message reports that temporary change information is being acquired.

(S)

Waits for a response.

(O)

Click Cancel if you want to cancel the processing.

KAVV3327-E

A unit (unit-name) was not found. The unit might have been deleted or the name changed. Confirm this from the window used to open the Temporary Changes dialog box.

An attempt was made to acquire temporary change information for a unit that might have been deleted or renamed.

(S)

Cancels processing.

(O)

Go back to the window from which you opened the Temporary Changes dialog box, and check whether the unit exists.

KAVV3328-I

Temporary change information (unit-name) was successfully acquired.

This message reports that temporary change information for multiple units was successfully acquired.

(S)

Outputs a log entry reporting that temporary change information for multiple units was successfully acquired.

KAVV3329-E

Temporary change information (unit-name) failed to be acquired.

This message reports that temporary change information for the selected units could not be acquired.

(S)

Outputs a log entry reporting that temporary change information for multiple units could not be acquired.

(O)

When the system fails to acquire temporary change information for multiple units, the Multi-execution Results dialog box appears. Check what happened in each case.

KAVV3330-Q

A temporary change (operation-time, unit-name, operation-type) will be re-executed. Are you sure you want to continue?

Confirm whether to re-execute the temporary change.

(S)

Waits for a response.

(O)

Click Yes to re-execute the temporary change or No to cancel.

KAVV3331-I

A temporary change was successfully re-executed.

This message reports that the selected temporary change was successfully re-executed.

(S)

Continues processing.

KAVV3332-I

A temporary change (operation-time, unit-name, operation-type) was successfully re-executed.

This message reports that all the selected temporary changes were successfully re-executed.

(S)

Outputs a log entry reporting that multiple temporary changes were successfully re-executed.

KAVV3333-E

A temporary change (operation-time, unit-name, operation-type) failed to be re-executed.

This message reports that the selected temporary changes could not be re-executed.

(S)

Outputs a log entry reporting that multiple temporary changes could not be re-executed.

(O)

When the system fails to re-execute multiple temporary changes, the Temporary Change Re-execution Processing Results dialog box appears. Check what happened in each case.

KAVV3334-E

The operation management function for temporary changes is disabled at the connection destination.

Temporary change information could not be acquired because the functionality for managing temporary change operations is disabled in JP1/AJS3 - Manager at the connection destination.

(S)

Cancels processing.

(O)

Enable the functionality for managing temporary change operations in JP1/AJS3 - Manager at the connection destination. For the procedure, see 6.1.8 Settings for using the temporary change operation management function in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.1.8 Settings for using the temporary change operation management function in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Log out of JP1/AJS3 - View before you set up this functionality.

KAVV3339-E

An execution generation that is the target of the operation was not found.

The operation cannot be processed because no such generation was found.

The probable causes are:

The specified generation exceeds the number of saved generations.

The specified generation has been unregistered by using Specify period.

The specified jobnet was unregistered and subsequently re-registered for execution.

Execution of the specified generation has been canceled.

No generation matches the execution registration number specified for the target unit in a jobnet for which release entry has been performed.

(S)

Cancels processing.

(O)

Check whether the target generation exists.

KAVV3341-I

The login history cannot be viewed from the Login screen.

The login history is not allowed to appear in the Login screen.

(S)

Continues processing.

KAVV3342-I

The password was successfully changed for a user (JP1-user-name).

The password was successfully changed.

(S)

Continues processing.

KAVV3343-E

The entered passwords do not match.

The password could not be changed because the new password and the confirmation of the new password did not match.

(S)

Cancels processing.

(O)

Type the same value for new password and confirmation of the new password, and then attempt to change the password again.

KAVV3344-E

The password failed to be changed. The entered user name or password is incorrect.

The password could not be changed because the JP1 user name or password was incorrect.

The probable causes are:

The target JP1 user has been deleted.

The current password is different from the password registered on the authentication server at the connection destination.

The JP1 user whose password was to be changed is a linkage user.

(S)

Cancels processing.

(O)

Confirm the following, and then attempt to change the password again:

The target JP1 user has been registered on the authentication server at the connection destination.

The current password matches the password registered in the authentication server at the connection destination.

The target JP1 user is not a linkage user.

If the target JP1 user is a linkage user, you cannot change the password from JP1/AJS3 - View. For details about linkage users, see the explanation of linkage users in the Job Management Partner 1/Base User's Guide.

KAVV3345-E

An error occurred at the connection-destination JP1/Base while changing the password. (detailed information = maintenance-information)

The password could not be changed because an error occurred in JP1/Base at the connection destination.

(S)

Cancels processing.

(O)

If maintenance-information is 8, make sure that the authentication server is running.

If maintenance-information is not 8, if necessary, use the data collection tool to collect data, and then contact the system administrator.

KAVV3346-E

The password cannot be changed because the password-change function is not enabled at the connection destination.

The password could not be changed because the function for changing passwords was disabled on JP1/AJS3 - Manager at the connection destination.

(S)

Cancels processing.

(O)

Enable the function for changing passwords on JP1/AJS3 - Manager, and then attempt to change the password again.

KAVV3347-E

The new password is the same as the current password. Specify a different password.

The password could not be changed because the new password was the same as the current password.

(S)

Cancels processing.

(O)

For the new password, specify a different password from the current password, and then attempt to change the password again.

KAVV3348-E

Specify a password from 6 bytes to 32bytes.(item)

The password could not be changed because the password specified for item was not 6 to 32 bytes long.

(S)

Cancels processing.

(O)

Recheck the password to be specified for item, and then attempt to change the password again.

KAVV3349-E

The password contains invalid characters.(item)

The password could not be changed because the password specified for item contained an invalid character.

You cannot use the following characters for a password:

Non-ASCII characters, control characters, backslashes (\), double quotation marks ("), colons (:), space characters, and tab characters

(S)

Cancels processing.

(O)

Recheck the password to be specified for item, and then attempt to change the password again.

KAVV3350-E

unit-name is being used elsewhere.

The specified operation or editing cannot be performed because another user is using the unit indicated by unit-name.

(S)

Cancels processing.

(O)

Check whether any of the JP1/AJS3 - View instances currently connected to JP1/AJS3 - Manager are using the unit.

To check JP1/AJS3 - View connection information, execute the ajsstatus command with the -v option specified on JP1/AJS3 - Manager at the connection destination.

If the specified unit or lower units are displayed in any of the following windows, close the window, and then try the operation again:

JP1/AJS3 - View window

Jobnet Editor window

Monthly Calendar window

Annual Calendar window

Daily Schedule (Hierarchy) window

Daily Schedule (All Jobs) window

Monthly Schedule window

Jobnet Monitor window

If JP1/AJS3 - View is disconnected due to a communication error, the connection sometimes stays open and the unit remains in use. In this case, wait until the failed connection times out, and then execute the ajsstatus command with the -v option specified. Make sure that the failed connection has terminated, and then try the operation again.

You can reduce the length of time until a connection is terminated by specifying the SESSIONTIMEOUT environment setting parameter in JP1/AJS3 - Manager at the connection destination. The default value for SESSIONTIMEOUT is dword:00000078 (120 in decimal; unit: minutes).

For details about the SESSIONTIMEOUT environment setting parameter, see 2.2.2(37) SESSIONTIMEOUT in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVV3351-E

No authorization. (unit-name)

Processing is impossible because the JP1/AJS3 service and the OS user mapped to the JP1 user do not have the required permission.

The probable causes are:

When the connection destination is JP1/AJS3 - Manager for Windows

When you are using the JP1/AJS3 service with a user account, you do not have the required permissions.

For details on the required permissions, see 4.2.3 Changing the JP1/AJS3 service settings (Windows only) in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

The OS user mapped to the logged-in JP1 user is defined incorrectly in the user mapping settings in JP1/Base.

For details about the OS user definition format, see 3.1.1 Setting up JP1/Base in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Read and write permissions for the folder specified by database directory name for the scheduler service, and the files in that folder, have not been set for the OS user mapped to the JP1 user.

When the connection destination is JP1/AJS3 - Manager for UNIX

The OS user mapped to the JP1 user does not have read permission for the configuration definition files (files in /opt/jp1/hcclibcnf/regdir).

Read, write, and execute permissions (rwx) for the directory specified by database directory name for the scheduler service, and the files in that directory, have not been set for the OS user mapped to the JP1 user.

(S)

Cancels processing.

(O)

Correct the cause of the error.

KAVV3352-E

No authority for unit-name

You do not have permission to reference, manipulate, or edit the unit-name.

(S)

Cancels processing.

(O)

Check the JP1 user privileges.

KAVV3353-E

unit-name does not exist.

The unit-name does not exist.

(S)

Cancels processing.

(O)

Choose Refresh, and then check to make sure that the unit is not deleted.

In the case of the Daily Schedule or Monthly Schedule window, relaunch the window to refresh it.

KAVV3600-E

Select waiting conditions.

No wait condition has been selected.

(S)

Cancels processing.

(O)

Select a wait condition to operate on.

KAVV3601-E

The specified operation cannot be performed for the specified waiting conditions.

The specified operation cannot be performed on the specified wait conditions.

The probable causes are:

An attempt was made to open the Jobnet Editor window from the Wait Conditions Settings List window to operate on a unit specified in an incorrectly defined wait condition.

An attempt was made to open the Jobnet Editor window from the Wait Conditions Settings List window to operate on a unit whose end is to be waited for defined under a planning group.

In the Wait Conditions Statuses window, an attempt was made to open the Jobnet Monitor, Daily Schedule, or Monthly Schedule window for a unit whose end is being waited for with incorrectly defined wait conditions.

In the Wait Conditions Statuses window, an attempt was made to open the Jobnet Monitor, Daily Schedule, or Monthly Schedule window from the Wait Conditions Statuses window for an unregistered unit whose end is being waited for.

In the Wait Conditions Statuses window, an attempt was made to open the Jobnet Monitor, Daily Schedule, or Monthly Schedule window for a unit whose end is being waited for and for which there are no generations to wait for.

An attempt was made to execute the Wait Disabled or Wait Enabled command in the Wait Conditions Statuses window on a wait condition that has been deleted.

(S)

Cancels processing.

(O)

Correct the wait condition if it is defined incorrectly and then retry the operation.

In all other cases, the specified operation cannot be performed.

KAVV3700-Q

Waiting for the selected number-of-wait-processes will be disabled. Are you sure you want to continue?

Confirm whether to disable the selected wait processes.

(S)

Waits for a response.

(O)

Click Yes to continue the operation or No to cancel.

KAVV3701-Q

Waiting for the selected number-of-wait-processes will be enabled. Are you sure you want to continue?

Confirm whether to enable the selected wait processes.

(S)

Waits for a response.

(O)

Click Yes to continue the operation or No to cancel.

KAVV3702-E

The wait function is not enabled at the connection destination.

The operation cannot be performed because the wait function is disabled in JP1/AJS3 - Manager at the connection destination.

(S)

Cancels processing.

(O)

Enable the wait function in JP1/AJS3 - Manager at the connection destination. For details, see 6.1.7 Settings for using wait conditions in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.1.7 Settings for using wait conditions in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

KAVV3703-E

None of the {statuses|results|next schedules} that can be displayed in the list of waiting condition statuses are present.

The Wait Conditions Statuses window cannot be displayed because the selected jobnet does not contain the required generation (specified by status, result, or next schedule).

(S)

Cancels processing.

(O)

Before you specify a status or result, make sure that the status is displayed in the JP1/AJS3 - View window for the generation that you want to view.

You cannot open the Wait Conditions Statuses window if you select an unregistered jobnet.

KAVV3706-E

Perform the operation on a monitoring generation.

Perform the operation on a monitoring generation.

The probable causes are:

An attempt was made to open the Wait Conditions Statuses window for the execution generation of a jobnet with start conditions.

An attempt was made to open the Wait Conditions Statuses window for the execution generation of a unit in a jobnet with start conditions.

(S)

Cancels processing.

(O)

Specify a monitoring generation and then retry the operation.

KAVV3900-Q

Are you sure you want to execute the command?

Entry:entry-name

Command:command

File name:file-name

Confirm whether to execute a command.

(S)

Waits for a response.

(O)

Click Yes to execute a command or No to cancel.

KAVV3901-I

The command is being executed.

Entry:entry-name

Command:command

File name:file-name

This message indicates that a command is being executed.

(S)

Indicates that the command is being executed.

(O)

Wait until command execution is complete.

KAVV3902-I

Command execution is complete.

This message indicates that command execution is complete.

(S)

Indicates that command execution is complete.

(O)

Click the Open File button to display the command execution results.

Click the Open Folder button to display the folder to which the command execution results are output.

Click the Close button to exit the command.

KAVV3903-E

Execution of the command (command) is not allowed at the connection destination.

Execution of the specified command is not allowed at the connection destination. Therefore, the following operations cannot be executed:

Executing the command

Changing command registration information

Copying command registration information

(S)

Cancels processing.

(O)

If necessary, set an executable command settings file (jajsExecutableCommand) on the manager host at the connection destination according to 4.5.4 JP1/AJS3 commands that can be executed from JP1/AJS3 - View in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVV3904-E

An option that cannot be specified from JP1/AJS3 - View is specified for the command argument.

An option that cannot be specified from JP1/AJS3 - View is specified for the command argument.

For details about the options that can be specified for executing commands from JP1/AJS3 - View, see the explanation of commands in Chapter 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

(S)

Cancels processing.

(O)

Check the option specified for the command argument. Then, delete the option that cannot be specified from JP1/AJS3 - View, or use another method to execute the command.

KAVV3905-E

The command cannot be executed because an unusable character is included in the replacement character string.

The command cannot be executed because a replacement character string is specified for the registered command, and the character string to be replaced includes a character that cannot be used (a control character such as a line feed or a tab character).

(S)

Cancels processing.

(O)

Check the character string to be replaced, delete the character that cannot be used, and then try the operation again. Alternatively, use another method to execute the command.

KAVV3906-E

The result of command execution could not be output.

Entry:entry-name

Command:command

File name:file-name

An error occurred during output of the file.

The probable causes are:

There is a folder that has the same name as the output file.

Another program is editing the output file.

You do not have permission to access files in the output folder.

The disk does not have sufficient free space.

(S)

Cancels processing.

(O)

Take one of the following actions according to the cause of the error, and then try the operation again:

Change the file name for Output in the JP1/AJS3 Command Entry dialog box.

If you cannot exit another program because it is editing the output file, change the file name for Output in the JP1/AJS3 Command Entry dialog box.

Set the access permissions required for accessing files in the output folder.

Allocate sufficient free disk space.

Note that part of the command execution results might have been output to the output file. If necessary, check the contents of the output file and delete unnecessary data.

KAVV3907-E

An error occurred during execution of the command.

An error occurred during execution of the command.

(S)

Cancels processing.

(O)

See Job Management Partner 1/Automatic Job Management System 3 Command Reference 1, and correct the cause of the error by checking the error information displayed in the JP1/AJS3 Command Execution Result dialog box.

KAVV3908-E

Failed to display the output of the command file.

An error occurred while displaying the output file of the command.

The probable causes are:

The output file was deleted or renamed.

You do not have permission to access the output file.

Another program is using the output file.

The path specified for the output file name contains the environment variable format (%variable-name%).

The program associated with the extension of the output file was deleted.

You do not have permission to access the program associated with the extension of the output file.

(S)

Cancels processing.

(O)

Take one of the following actions according to the cause of the error:

Check whether the output file exists.

Set the access permissions required for accessing the output file.

Click the Open Folder button, and then open the output file from Windows Explorer.

Check the output destination, and then open the output file from Windows Explorer.

Check whether the program associated with the extension of the output file exists.

Set permissions required for executing the program associated with the extension of the output file.

KAVV3909-E

Failed to display the output folder of the command.

An error occurred while displaying the output folder of the command.

The probable causes are:

The output folder was deleted or renamed.

You do not have permission to access the output folder.

The path specified for Output contains the environment variable format (%variable-name%).

(S)

Cancels processing.

(O)

Take one of the following actions according to the cause of the error:

Check whether the output folder exists.

Set access permissions required for accessing the output folder.

Check the output destination, and then open the output folder from Windows Explorer.

KAVV3910-E

JP1/AJS3 - View cannot be closed while a command is being executed.

You cannot exit JP1/AJS3 - View while a command is being executed.

(S)

Cancels processing.

(O)

Wait for command execution to complete, and then exit JP1/AJS3 - View.

KAVV3912-E

The command for the specified scheduler service (scheduler-service-name) cannot be executed.

The command cannot be executed for the scheduler service specified for the -F option of the command. The probable causes are:

The scheduler service specified for the -F option was not defined in JP1/AJS3 - Manager at the connection destination.

You do not have view permission for the scheduler service specified for the -F option.

JP1/AJS3 - Manager at the connection destination uses a logical host environment, and the scheduler service specified for the -F option is not on the logical host that you are logged in to from JP1/AJS3 - View.

The Jobnet Editor window or Jobnet Monitor window is opened directly from a linkage product or by using the ajs command. Then, a scheduler service name that is not displayed in this window is specified for the -F option.

Another window is opened by selecting a manager jobnet, manager job group, or jobnet connector. Then, a scheduler service name that is not displayed in this window is specified for the -F option.

(S)

Cancels processing.

(O)

Take one of the following actions according to the cause of the error:

Check whether the specified scheduler service name is correct, and then re-execute the command.

Check and, if necessary, set view permissions for the scheduler service, and then re-execute the command.

Use JP1/AJS3 - View to log in to the logical host on which the target scheduler service exists, and then re-execute the command.

For the -F option, specify a scheduler service displayed in the Jobnet Editor window or Jobnet Monitor window, and then re-execute the command.

For the -F option, specify a scheduler service displayed in the window, and then re-execute the command.

KAVV3913-E

The output file name (file-name) is invalid.

The file name or folder name specified for the output file name is invalid.

The probable causes are:

A URI character string (a path beginning with file://) is specified.

An MS-DOS device name (NUL, CON, AUX, CLOCK$, COM1 to COM9, LPT1 to LPT9, or PRN) is specified for the file name or folder name.

A character string beginning with MS-DOS-device-name. (period) is specified for the file name or folder name.

A character string beginning with a period (.) is specified for the file name or folder name.

A character string ending with a backslash (\) or a forward slash (/) is specified for the file name.

The full path of the output file name exceeds 255 bytes.

(S)

Cancels processing.

(O)

Check and, if necessary, correct the specification, and then try the operation again.

KAVV3914-E

The specified unit name (unit-name) is invalid.

The unit name specified for the command argument is invalid.

The probable causes are:

The unit name does not begin with a forward slash (/) or "/.

The unit name begins with a forward slash or "/, but contains a replacement character string.

The unit name does not begin with a replacement character string (UNIT_FULL_NAME).

(S)

Cancels processing.

(O)

Specify the unit name that meets one of the following conditions, and then try the operation again:

The unit name begins with a forward slash (/), and does not contain a replacement character string.

The unit name begins with "/, and does not contain a replacement character string.

The unit name begins with a replacement character string (UNIT_FULL_NAME).

KAVV3915-E

An option (option) is not specified.

The required option is not specified.

The probable causes are:

The required option is not specified.

A command argument is specified incorrectly, and the required option is interpreted as the value of another option.

A command argument is specified incorrectly, and the required option is interpreted as something else, such as a unit name or file name.

(S)

Cancels processing.

(O)

Revise the specification of the command argument, and then re-execute the command.

KAVV3916-E

No value is specified for an option (option).

No value is specified for an option that needs a value.

(S)

Cancels processing.

(O)

Revise the specification of the command argument, and then re-execute the command.

KAVV3917-E

An option (option) is specified more than once.

The same option is specified more than once.

(S)

Cancels processing.

(O)

Specify the option only once, and then re-execute the command.

KAVV3918-Q

The output file already exists. Do you want to continue the output of the command execution result?

Output file name:file-name

This message asks you whether you want to execute the command.

(S)

Waits for a response.

(O)

Click Yes to execute the command. Click No to cancel.

KAVV3919-E

The specified command exceeds 2,047 bytes. (number-of-bytes)

The number of bytes specified for the command exceeds the limit.

The probable causes are:

If this message appears in the JP1/AJS3 Command Entry dialog box, the total number of bytes for the command and command arguments exceeds 2,047 bytes.

If a replacement character string is used, the result of the replacement exceeds 2,047 bytes.

The result of escape processing exceeds 2,047 byes.

(S)

Cancels processing.

(O)

Revise the specification of the command arguments, and then re-execute the command.

KAVV3922-E

The size of the customized file (jajsExecutableCommand) for JP1/AJS3 - View at the connection destination exceeds 32 KB.

JP1/AJS3 commands cannot be executed from JP1/AJS3 - View.

This message indicates that an attempt to read the executable command settings file (jajsExecutableCommand) for JP1/AJS3 - Manager at the connection destination failed.

(S)

Assumes the default settings. JP1/AJS3 commands cannot be executed from JP1/AJS3 - View.

(O)

Revise the contents of the executable command settings file (jajsExecutableCommand) for JP1/AJS3 - Manager at the connection destination according to 11.3.18 Allowing execution of JP1/AJS3 commands in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

KAVV3923-E

The execution result of the command cannot be output.

Output file name:file-name

The execution result of the command cannot be output.

The probable causes are:

There is a folder that has the same name as the output file.

The drive at the output destination does not exist.

Another program is editing the output file.

You do not have permission to access files in the output folder.

The disk does not have sufficient free space.

The folder name or file name specified for the output file name contains a colon (:).

(S)

Cancels processing.

(O)

Take one of the following actions according to the cause of the error, and then try the operation again:

Change the file name for Output in the JP1/AJS3 Command Entry dialog box.

To specify an absolute path, specify the drive at the output destination.

If you cannot exit another program because it is editing the output file, change the file name for Output in the JP1/AJS3 Command Entry dialog box.

Set the access permissions required for accessing files in the output folder.

Allocate sufficient free disk space.

Make sure that the specified output file name is correct, and then try the operation again.

KAVV3924-I

Because the standard error output exceeds the maximum number of items that can be displayed, some results cannot be displayed.

Part of the standard error output was not output because the number of lines in the standard error output exceeds the maximum (1,000 lines).

(S)

Indicates that part of the standard error output was not output because the number of lines of the standard error output exceeds 1,000 (maximum).

KAVV3925-Q

If you run the command by specifying a generic name or the -R option for the unit to be operated on, JP1/AJS3 operation might be affected. Are you sure you want to register the command?

If you use a generic name or the -R option to specify target units, too many units are subject to processing. As a result, the increased load on the network or manager during command execution might affect JP1/AJS3 performance. This message asks you whether you want to register the command as is.

The probable causes are:

A generic name is specified for the unit name for the argument of the ajsprint or ajsshow command.

The -R option is specified for the argument of the ajsprint or ajsshow command.

To specify a generic name or the -R option, also use the -E, -L, or -T option to narrow down the target units.

(S)

Waits for a response.

(O)

Click Yes to register the command. Click No to cancel.

KAVV3926-E

Because the number of registered commands has reached the upper limit (upper-limit), you cannot register any more.

The number of registered commands has reached the upper limit.

(S)

Cancels processing.

(O)

Delete registrations for unnecessary commands, and then re-execute the command.

KAVV3927-Q

Are you sure you want to remove the selected command registration?

This message asks you whether you want to delete the registration of the selected command.

(S)

Waits for a response.

(O)

Click Yes to continue the operation. Click No to cancel.

KAVV3928-E

Execution of the command is not allowed at the connection destination.

Execution of the command is not allowed at the connection destination.

(S)

Cancels processing.

(O)

Set an executable command settings file (jajsExecutableCommand) for JP1/AJS3 - Manager at the connection destination according to 4.5.4 JP1/AJS3 commands that can be executed from JP1/AJS3 - View in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVV3929-E

No unit name is specified.

A unit name is not specified for the command argument.

(S)

Cancels processing.

(O)

Specify a unit name, and then try the operation again.

KAVV3931-E

An abnormality was detected in the received data during output of the results of command execution, and processing was interrupted.

Entry:entry-name

Command:command

File name:file-name

Invalid data was detected in the data sent from JP1/AJS3 - Manager.

(S)

Cancels processing.

(O)

The network might have a problem. If this message appears repeatedly, an error might have occurred in JP1/AJS3 - Manager. Use log information such as the Windows event log or the syslog file on the manager host to examine the error. Then, correct the error according to the results.

For details about types of log information and storage locations, see 1.2 Types of log information and storage locations in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

Note that part of the execution result of the command might have been output to the output file. If necessary, check the contents of the output file and delete unnecessary data.

KAVV3932-E

A specified command argument is invalid.

The specified command argument is invalid.

The probable causes are:

Optional names such as unit names or file names are specified more than necessary.

A name that must be specified is interpreted as a value of another option.

An invalid option is specified.

A character that cannot be used (a control character such as a line feed or a tab character) is contained.

(S)

Cancels processing.

(O)

See the explanation of commands in Chapter 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1, and revise the specification of the command argument. Then, try the operation again.

KAVV3934-E

IO_ERR : maintenance-information

This message includes details about an error that occurred during the input or output of a file.

(S)

Outputs, to the log, details about the error that occurred during the input or output of a file.

KAVV3935-E

The window from which a command is executed cannot be closed while the command is being executed.

The window from which a command is executed cannot be closed while that command is being executed.

(S)

Cancels processing.

(O)

Wait for command execution to complete, and then close the window.

KAVV3936-Q

Are you sure you want to remove the selected number command registrations?

This message asks you whether you want to delete the registration of a command.

(S)

Waits for a response.

(O)

Click Yes to continue the operation or No to cancel.

KAVV4000-E

Multiple "Register Custom Job" dialog boxes cannot be opened at the same time.

An error occurred during an attempt to open the Register Custom Job dialog box.

The probable causes are:

The Register Custom Job dialog box is already open.

Read and write permissions have not been set for the files in the custom job registration information folder.

Another program is editing a file in the custom job registration information folder.

The locations of the custom job registration information folder are as follows:

For Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir\

For Windows Server 2003 or Windows XP Professional

JP1/AJS3-View-installation-folder\custom.dir\

(S)

Cancels processing.

(O)

Correct the cause of the error.

KAVV4001-Q

Do you want to delete the registered information for this Custom Job (custom-job-name)?

Confirm that you want to delete the registered information for the custom job.

(S)

Waits for a response.

(O)

Click the Yes button to delete the registered information for the custom job, or click the No button if you do not want to delete the registered information for the custom job.

KAVV4002-E

Failed to delete the registered information.

The registered information could not be deleted.

The probable causes are:

Read and write permissions have not been set for the files in the custom job registration information folder.

Another program is editing a file in the custom job registration information folder.

The applicable file in the custom job registration information folder has been deleted, or the file name was changed.

The hidden file attribute is set for the applicable file in the custom job registration information folder.

One of the following was specified for Name:

- An MS-DOS device name (NUL, CON, AUX, CLOCK$, COM1 to COM9, LPT1 to LPT9, or PRN)

- A character string beginning with MS-DOS-device-name. (period)

- A control character, such as a line feed character or a tab character

The locations of the custom job registration information folder are as follows:

For Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir\

For Windows Server 2003 or Windows XP Professional

JP1/AJS3-View-installation-folder\custom.dir\

(S)

Cancels processing.

(O)

Correct the cause of the error.

KAVV4003-E

File not found.

The operation was attempted on one of the following types of file:

A deleted file

A file whose name had been changed

A file for which the hidden file attribute is set

(S)

Cancels processing.

(O)

Reopen the Register Custom Job dialog box, and then retry the operation.

KAVV4004-E

Path/File access error.

An error occurred during output of the file.

The probable causes are:

Read and write permissions have not been set for the files in the custom job registration information folder.

Another program is editing a file in the custom job registration information folder.

The locations of the custom job registration information folder are as follows:

For Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir\

For Windows Server 2003 or Windows XP Professional

JP1/AJS3-View-installation-folder\custom.dir\

(S)

Cancels processing.

(O)

Correct the cause of the error.

KAVV4005-E

Permission denied.

An error occurred during output of the file.

The probable causes are:

Read and write permissions have not been set for the files in the custom job registration information folder.

Another program is editing a file in the custom job registration information folder.

The locations of the custom job registration information folder are as follows:

For Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir\

For Windows Server 2003 or Windows XP Professional

JP1/AJS3-View-installation-folder\custom.dir\

(S)

Cancels processing.

(O)

Correct the cause of the error.

KAVV4006-E

Invalid procedure call or argument.

An error occurred during input of the file. The probable causes are:

The custom job registration information folder contained a file whose extension was .CJI and whose name (excluding the extension) was 11 bytes or more in length.

The locations of the custom job registration information folder are as follows:

For Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir\

For Windows Server 2003 or Windows XP Professional

JP1/AJS3-View-installation-folder\custom.dir\

(S)

Cancels processing.

(O)

Correct the cause of the error.

KAVV4007-E

Specify Name.

Name has not been specified.

(S)

Cancels processing.

(O)

Enter a value for Name, and then retry the operation.

KAVV4008-E

Specify the program name for definition.

Defining program has not been specified.

(S)

Cancels processing.

(O)

Enter a value for Defining program, and then retry the operation.

KAVV4009-E

Specify the program for execution.

Executing program has not been specified.

(S)

Cancels processing.

(O)

Enter a value for Executing program, and then retry the operation.

KAVV4010-E

Specify the Version.

Version has not been specified.

(S)

Cancels processing.

(O)

Enter a value for Version, and then retry the operation.

KAVV4014-E

No more custom jobs can be registered.

The number of registered custom jobs has reached the limit.

(S)

Cancels processing.

(O)

Delete any unnecessary custom jobs.

KAVV4015-E

Error occurred: Cannot register the custom job.

An error occurred during output of the file.

The probable causes are:

Read and write permissions have not been set for the files in the custom job registration information folder.

Another program is editing a file in the custom job registration information folder.

The applicable file in the custom job registration information folder has been deleted, or the file name was changed.

The hidden file attribute is set for the applicable file in the custom job registration information folder.

The custom job registration information folder contains a folder with the following name:

character-string-specified-for-"Name".CJI

One of the following was specified for Name:

- An MS-DOS device name (NUL, CON, AUX, CLOCK$, COM1 to COM9, LPT1 to LPT9, or PRN)

- A character string beginning with MS-DOS-device-name. (period)

- A control character, such as a line feed character or a tab character

The locations of the custom job registration information folder are as follows:

For Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir\

For Windows Server 2003 or Windows XP Professional

JP1/AJS3-View-installation-folder\custom.dir\

(S)

Cancels processing.

(O)

Correct the cause of the error.

KAVV4016-E

File (file-name) not found. Verify the correct file name was given.

The specified file was not found.

(S)

Cancels processing.

(O)

Check whether the specified file exists.

KAVV4017-E

The name specified is invalid.

The custom job name specified for Name is invalid.

The probable causes are:

The specified character string contained a single-byte space.

An MS-DOS device name (NUL, CON, AUX, CLOCK$, COM1 to COM9, LPT1 to LPT9, or PRN) was specified.

A character string beginning with MS-DOS-device-name. (period) was specified.

(S)

Cancels processing.

(O)

Check the specified value, and enter a valid name.

KAVV4018-I

The "Register Custom Job" dialog box was opened. (version = version, OS user name = OS-user-name)

The Register Custom Job dialog box was opened.

(S)

Opening of the Register Custom Job dialog box was logged.

KAVV4019-E

The specified custom job name is already registered.

The custom job name specified for Name is already registered.

(S)

Cancels processing.

(O)

Specify a different name.

KAVV4020-E

Specify the name in 8 or fewer characters.

The custom job name specified for Name is too long.

(S)

Cancels processing.

(O)

Specify a value for Name that is no more than 8 bytes long.

KAVV4021-E

Invalid Class name.

The character string specified for Class contains a space.

(S)

Cancels processing.

(O)

Check the specified string, and enter a valid name.

KAVV4022-E

exception-name occurred. Register Custom Job will now end. Detailed information: maintenance-information-1, maintenance-information-2

The exception exception-name occurred.

(S)

Terminates the registration of custom jobs.

(O)

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

Screen dump

Log file for the program used to register custom jobs

Click the OK button in this message dialog box to obtain the log file for the program used to register custom jobs.

KAVV4050-E

An unexpected error occurred in start processing. (Detailed information: maintenance-information-1, maintenance-information-2)

An unexpected error occurred while the Register Custom Job dialog box was opening.

(S)

Cancels processing.

(O)

Memory or free disk space might be insufficient. Terminate unnecessary applications, and then attempt to open the Register Custom Job dialog box again.

If the error persists, the configuration of JP1/AJS3 - View may have been corrupted. Perform a repair installation.

KAVV4051-E

The "Register Custom Job" dialog box failed to open. (Detailed information: maintenance-information)

The Register Custom Job dialog box could not be opened.

(S)

Cancels processing.

(O)

The probable causes are:

Memory or free disk space was insufficient.

Terminate unnecessary applications, and then re-register the custom jobs.

JP1/AJS3 - View has been installed in the root directory of the drive.

Install JP1/AJS3 - View in a location other than the root directory of the drive.

If the error persists, the configuration of JP1/AJS3 - View may have been corrupted. Perform a repair installation.

1.3 Messages beginning with KFP (Messages about an embedded database)

KFPA11561-E

Specified authorization identifier aa....aa has no connect privilege (A)

The specified authorization identifier aa....aa has no CONNECT privilege.

aa....aa: Authorization identifier that has no CONNECT privilege

(S)

Terminates processing.

Action

Check the value of the RDBAUTHID environment setting parameter.

KFPA11720-E

Error occurred in HiRDB/client, inf1=aa....aa, inf2=bbbb (L+A)

An internal contradiction occurred in the client library for the embedded database system.

The probable causes are:

The host specified in the ajsembdbstart command and the host specified in PDHOST cannot communicate with the client system over the network. Alternatively, the communication load is heavy.

aa....aa: Name of the source file in which the error was detected

bbbb: Location where the error was detected (line number)

(S)

Terminates processing.

Action

Back up the error log file to which the error was output, and then contact the system administrator.

KFPA11723-E

Communication error occurred, reason=aa....aa (L+A)

An error occurred during communication with the embedded database system or embedded database server. Alternatively, the embedded database system or embedded database server has gone down.

aa....aa: Character string indicating the details of the error

CLIENT MEMORY: A memory shortage occurred in the client library.

FES (SDS) CLOSE: The server is being terminated.

FES (SDS) NOT UP: The server is not running or is being started.

HiRDB BUSY: The embedded database (server) cannot be connected because it is busy.

HiRDB DATA ERROR: Communication data from the embedded database system or embedded database server is invalid.

HiRDB INITIALIZE: The embedded database system or embedded database server is being initialized.

HiRDB NOT UP: The embedded database system or embedded database server is not running. Alternatively, Listen queues on the embedded database server are insufficient.

HiRDB SYSTEM ERROR: A system error was detected in the embedded database system or embedded database server.

HiRDB MEMORY: A memory shortage occurred in the embedded database system or on the embedded database server.

INIT ERROR: An error occurred during initialization for communication.

INVALID SERVER TYPE: The server type of the embedded database (server) differs from PDSRVTYPE (client environment definition).

NETWORK: A network failure occurred. Alternatively, the connection was released due to abnormal termination of the embedded database server.

(S)

Terminates processing.

(P)

When aa....aa is HiRDB BUSY:

Wait a while, and then retry. If this message reappears, contact the embedded database system administrator.

When aa....aa is not HiRDB BUSY:

Report the details of the error to the embedded database system administrator, and then correct the error and retry.

Action

Determine the cause of the error from the error log file output by the embedded database client, correct the cause of the error, and then retry.

If this message (aa....aa is HiRDB NOT UP) still appears during connection even after the embedded database has started, recheck the JP1/AJS3 environment setting parameters. In addition, use a syslog (or Windows event log in Windows) to check for errors on the embedded database server.

If the values of JP1/AJS3 environment setting parameters are correct and the message KFPZ02444-E (func=connect and errno indicating ETIMEDOUT or ECONNREFUSED) is output to the error log file, it is possible that too many requests have been made to the embedded database server. In this case, wait a while and then retry. Alternatively, increase the value specified for the Listen queues.

Note that when this message appears, connection with the embedded database server has been released. Therefore, you must retry starting from the CONNECT statement.

KFPA11724-E

Environment definition error, variable=aa....aa, reason=bb....bb, identifier="cc....cc" (L+A)

The specification of the environment variable contains an error.

aa....aa: Environment variable name containing the error

bb....bb: Cause of the error

INVALID CHAR: A character string that cannot be specified was found.

NET ENVIRONMENT: The specified contents do not match the network environment.

NO VALUE: No value is specified.

OUT OF RANGE: The specified value is outside the specifiable range.

NOT ENVIRONMENT GROUP: The specified environment variable group was not found in the registry.

INVALID IDENTIFIER: The identifier is invalid.

cc....cc: Invalid identifier (If the identifier exceeds 30 bytes, the first 30 bytes are displayed.)

This information is displayed only when the cause of the error is INVALID IDENTIFIER.

(S)

Terminates processing.

(P)

Specify the environment variable correctly, and then retry.

KFPA11732-E

Time over, no response from HiRDB (L+A)

The embedded database server has stopped. Alternatively, processing for the embedded database server required more time than the timer monitoring period. As a result, a query cannot be sent to the embedded database server.

(S)

Terminates processing.

(P)

If the embedded database server stopped, make sure that it has started again, and then retry.

If the embedded database server has not stopped, increase the timer monitoring period specified in the PDCWAITTIME environment variable, and then re-execute the UAP. Note that when this message appears, connection with the embedded database server has been released. Therefore, you must re-execute the UAP from the CONNECT statement.

KFPA11756-E

No available pages in RDAREA, RDAREA=aa....aa (A)

There are no available pages in the RDAREA.

aa....aa: Name of the RDAREA that has insufficient free space

(S)

Invalidates the transaction.

Action

Take one of the following actions, and then re-execute the transaction:

Expand the RDAREA.

Use the ajsembdbaddarea command to expand the size of the RDAREA that has insufficient free space.

Reorganize the table.

Use the ajsembdbrorg command to reorganize the table stored in the RDAREA.

Reclaim free pages.

Execute the ajsembdbstatus command with the -db option to analyze the status of the RDAREA. If required, execute the ajsembdbreclaim command for the index.

KFPA11770-I

aaaa [bb....bb cc....cc] currently in use, resource id=dd....dd (A)

An exclusive-wait timeout occurred.

aaaa: Maintenance information

bb....bb: Maintenance information

cc....cc: Maintenance information

dd....dd: Maintenance information

(S)

Terminates processing.

(O)

Take corrective action according to the message displayed before or after this message.

KFPA11912-E

Insufficient memory for DB exclusive contr (A)

The work area for exclusive control was insufficient.

(S)

Terminates processing, or cancels command processing.

(P)

If the error occurred during operation of JP1/AJS3:

Check the current resource lock status. Wait until the load decreases, and then retry the operation.

If the error occurred during execution of the ajsembdbrorg command:

Check the current resource lock status. Wait until the load decreases, and then retry the operation.

If the error occurs even when the load is light, the locked resource management table required for the utility to process the appropriate table cannot be allocated.

Action

If the resources for locking tables are insufficient, increase the value specified for the pd_lck_pool_size operand in the system definition of embedded database, and then start the embedded database.

KFPA11928-I

RDAREA aa....aa held pdhold command in proce (L)

The specified RDAREA aa....aa is undergoing block processing.

aa....aa: RDAREA name

(S)

Invalidates the transaction.

Action

Recover the RDAREA and re-execute the transaction.

KFPA11932-E

Number of connect users exceeded max use (A)

The number of connections to the embedded database server exceeded the maximum number of concurrent connections.

(S)

Terminates processing.

(P)

Wait until other jobs or commands terminate, and then re-execute the UAP or the utility.

Action

When this message is output:

If possible, increase the value specified for the pd_max_users operand.

KFPA11990-E

Incompatible character code set, HiRDB=aa....aa, client=bb....bb (A)

The character encodings of the environment variables for the environment linked with the embedded database do not match.

aa....aa: Embedded-database character encoding

bb....bb: Character encoding of the corresponding environment variables for the environment

LANG-C: 7-bit ASCII

SJIS: Shift-JIS

UJIS: EUC

UTF-8: UTF-8

Other than the above: Unsupported

(S)

Cancels processing.

(O)

Change LANG environment variable setting for the command execution environment related to the error or the start environment for JP1/AJS3 services related to the error. Make the new value the setup value corresponding to the character encoding of the embedded database specified in the -lc option in the ajsembdbbuild command. After the change, retry the operation.

KFPH00115-I

aa....aa command fail (L+S)

The embedded database command aa....aa cannot be processed.

aa....aa: Command name

(S)

Ignores the entered command and terminates processing.

KFPH00131-E

pdhold command failed due to RDAREA already held, RDAREA=aa.... (L)

The command cannot block the specified RDAREA because it is already blocked due to an error.

aa....aa: RDAREA name

(S)

Ignores the RDAREA processing and executes other processing.

(O)

Correct the error, release the RDAREA from the blocked state, and then re-execute the command.

KFPH00211-I

RDAREA usage aaa%, RDAREA = "bb....bb"cc....cc (L)

The meaning of the message depends on the situation, as shown below:

For users:

Of the segments in the entire RDAREA "bb....bb", the system began to use the segment whose usage is aaa % . The current number of unused segments is cc....cc.

aaa: Segment usage in the entire RDAREA

bb....bb: Relevant RDAREA name

cc....cc: Additional information for the segment usage , dd....dd segments unused

(dd....dd: number of remaining segments)

(S)

Continues processing.

Even if a new segment cannot be allocated due to insufficient space in the RDAREA for which this message is displayed, the system continues processing by adding or updating existing segments when these segments have free space.

After the segment displayed in the message has been released due to deletion or reorganization of the table, this message appears again if the same segment is used.

(P)

Contact the embedded database system administrator.

Action

Execute the ajsembdbstatus -db command to check the free space in the database, and then do the following:

Check the additional information about the segment usage output by the ajsembdbstatus -db command or displayed in the message to check the usage of the target RDAREA.

Reorganize the table or expand the RDAREA as required.

KFPH00212-I

Table should be reorganized,RDAREA="aa....aa",AUTHID=bb....bb,TABLE=cc....cc (L)

Reorganization of the table is required.

aa....aa: RDAREA name

bb....bb: Authorization identifier

cc....cc: Table identifier

(S)

Continues processing.

Action

Use the ajsembdbreclaim command to perform maintenance or use the ajsembdbrorg command to reorganize the table. However, you must expand the RDAREA size if either of the following situations occurs:

This message appears frequently for a table in the same RDAREA.

This message appears during or immediately after reorganization of a table.

KFPH22014-E

RDAREA "aa....aa" not found in dictionary server (L)

The required RDAREA "aa....aa" was not found on the dictionary server.

aa....aa: RDAREA name

*masterdirectory*: Master directory

*datadirectory*: Data directory

*datadictionary*: Data dictionary

(S)

Abnormally terminates the embedded database.

Action

If the RDAREA has been corrupted, recover the data and then retry the operation.

KFPH22024-W

Extension completed in RDAREA "aa....aa", FILE "bb....bb", ccccc (dd....dd) segments created (L)

The "bb....bb" file in the "aa....aa" database area was incremented by ccccc segments. The total number of segments is dd....dd.

aa....aa: Database area name

bb....bb: File name (If the file name is 113 or more characters long, only the last 112 characters are output.)

ccccc: Incremented number of segments

dd....dd: Total number of segments

(S)

Continues processing.

Action

Take corrective action as follows:

Execute the ajsembdbreclaim command to perform maintenance or the ajsembdbrorg command to reorganize the database area.

Check whether the increase in the amount of job operations (the number of job definitions and the number of executed jobs) is within the intended range.

KFPH22025-E

Error occurred while Extension, RDAREA "aa....aa", FILE "bb....bb", reason code ccccc (L)

An error occurred during automatic incrementing of the "bb....bb" file in the "aa....aa" database area. The reason code is ccccc.

aa....aa: Database area name

bb....bb: File name (If the length is 122 or more characters, only the last 121 characters are output.)

ccccc: Reason code

-1535: Disk capacity shortage or expansion limit

(S)

Continues processing.

Action

Take corrective action as follows:

When the reason code is -1535:

Provisional measures

Delete unnecessary job definitions and unregister the execution of jobnets.

Execute the ajsembdbreclaim command to release free pages and segments.

Execute the ajsembdbrorg command to reorganize the database.

Permanent measure

As required, review (expand) the disk environment or split the scheduler service and embedded database environment.

KFPH23100-E

HiRDB file aa....aa error, errno=bb....bb, HiRDB file name=cc....cc (L)

An error occurred during file access.

aa....aa: File function

close: File closing

creat: File creating

open: File opening

read: File reading

write: Writing to a file

bb....bb: Error code

-1544: Input/output error

cc....cc: File name (If the length is 132 or more characters, only the last 131 characters are output.)

(S)

Terminates processing.

Action

Take corrective action as follows:

When the error code is -1544:

If the database area is blocked because of a fault, recover it from the backup.

KFPH27006-E

DATA DICTIONARY RDAREA information get error (L+S)

An error occurred during collection of information about the data dictionary RDAREA.

(S)

Terminates processing.

(O)

Check whether you have permission to access the database area specified by the -d option of the ajsembdbrstr command. For operations performed by an AJS administrator, make sure that the required authorization has been set for the AJS administrators.

KFPH27008-E

aa....aa command failed due to DATA DICTIONARY RDAREA(bb....bb) status invalid, RDAREA = cc....cc (L+S)

The database operation command aa....aa for the specified RDAREA cc....cc cannot be processed because the data dictionary RDAREA bb....bb cannot be referenced.

aa....aa: Command name

bb....bb: Name of the data dictionary RDAREA

cc....cc: RDAREA name (***** appears if the RDAREA name cannot be obtained.)

(S)

Invalidates the RDAREA processing, and continues processing.

(O)

Correct the status of the data dictionary RDAREA, and then re-execute the command.

KFPH27058-E

Unable to use specified command option aa for bb....bb, command=cc....cc, RDAREA name="dd....dd" (L+S)

The aa option cannot be specified for bb....bb in the command cc....cc.

aa: Option name

-u

bb....bb: Cause of the error

shared RDAREA: Shared RDAREA

cc....cc: Command name

pdhold

dd....dd: RDAREA name

(S)

Invalidates the RDAREA "dd....dd" processing, and continues processing.

Action

Delete the aa option and then re-execute the command.

KFPK00002-E

aa....aa: file open failed, file_kind:bb....bb file_name:cc....cc errno=dd....dd (D+E)

The specified file or the file temporarily created by the command cannot be opened.

aa....aa: Command type

Pddbst: ajsembdbstatus

bb....bb: File type

control file: Control statement file

edit work file: Work file

sort data file: Work file for sort

unload log file: Unload log file

DAT file: DAT file

predict csv file: CSV output file

cc....cc: File name

dd....dd: errno returned by the open system call

(S)

When the message is output to the standard error output:

Terminates processing.

When the message is output to the error message dialog box:

Redisplays the window that was displayed immediately before the error occurred.

(O)

Correct the error indicated by the errno value by using the errno.h file and the documentation for your OS, and then re-execute the command.

KFPK00003-E

aa....aa: file close failed, file_kind:bb....bb file_name:cc....cc errno=dd....dd (D+E)

The file cannot be closed.

aa....aa: Command type

Pddbst: ajsembdbstatus

bb....bb: File type

control file: Control statement file

edit work file: Work file

sort data file: Work file for sort

unload log file: Unload log file

predict csv file: CSV output file

cc....cc: File name

dd....dd: errno returned by the close system call

(S)

When the message is output to the standard error output:

Terminates processing.

When the message is output to the error message dialog box:

Redisplays the window that was displayed immediately before the error occurred.

(O)

Correct the error indicated by the errno value dd....dd, and then re-execute the command.

KFPK00004-E

aa....aa: I/O error, cause:bb....bb file_name:cc....cc errno=dd....dd (D+E)

An I/O error occurred.

aa....aa: Command type

Pddbst: ajsembdbstatus

bb....bb: Type of the system call in which the error occurred

LSEEK: lseek system call

READ: read system call

WRITE: write system call

cc....cc: File name

dd....dd: errno returned by the system call

(S)

When the message is output to the standard error output:

Terminates processing.

When the message is output to the error message dialog box:

Redisplays the window that was displayed immediately before the error occurred.

(O)

Correct the error indicated by the errno value dd....dd, and then re-execute the command.

KFPK00005-E

aa....aa: system call error, func=bb....bb, errno=cc....cc (D+E)

An error occurred in the system call (function).

aa....aa: Command type

Pddbst: ajsembdbstatus

bb....bb: Name of the system call in which the error occurred

cc....cc: errno returned by the system call

(S)

When the message is output to the standard error output:

Terminates processing.

When the message is output to the error message dialog box:

Redisplays the window that was displayed immediately before the error occurred.

(O)

Correct the error indicated by the errno value cc....cc, and then re-execute the command.

KFPK00006-E

aa....aa: unrecovable error, func=bb....bb, errno=ccc (D+E)

An unrecoverable error occurred.

aa....aa: Command type

Pddbst: ajsembdbstatus

bb....bb: Type of the system call in which the error occurred

CLOSEDIR: closedir system call

CREATE: create or open system call

DELETE: unlink system call

OPENDIR: opendir system call

READDIR: readdir system call

ccc: errno returned by the system call

(S)

When the message is output to the standard error output:

Terminates processing.

When the message is output to the error message dialog box:

Redisplays the window that was displayed immediately before the error occurred.

(O)

Correct the error indicated by the errno value ccc, and then re-execute the command. If the error number is ***, determine the cause of the error from the preceding error message.

KFPK00013-E

aa....aa: system call error, func=bb....bb, file_name=cc....cc, errno=dd....dd (D+E)

An error occurred in the system call (function) that accesses the file.

aa....aa: Command type

Pddbst: ajsembdbstatus

bb....bb: Name of the system call in which the error occurred

cc....cc: File name

dd....dd: Error number set for errno

(S)

Terminates processing if the message is output to the standard error output. If the message is output to the message dialog box, the system redisplays the window that was displayed immediately before the error occurred.

(O)

Correct the error indicated by the errno value dd....dd, and then re-execute the command.

KFPK00050-E

aa....aa: insufficient memory, size=bb....bb (D+E)

Memory was insufficient.

aa....aa: Command type

Pddbst: ajsembdbstatus

bb....bb: Size of the memory that was to be allocated (unit: bytes)

(S)

When the message is output to the standard error output:

Terminates processing.

When the message is output to the error message dialog box:

Redisplays the window that was displayed immediately before the error occurred.

(O)

Check whether another process is using a large amount of memory.

If another process is using a large amount of memory:

Wait until the process terminates, and then re-execute the command.

If another process is not using a large amount of memory:

Take one of the following actions to increase the amount of free space in memory:

Reduce the number of processes running concurrently.

Increase the swap area.

Add real memory.

KFPK00100-E

aa....aa: interface error, func:bb....bb, return code=cccc (D+E)

An interface error between program functions occurred.

aa....aa: Command type

Pddbst: ajsembdbstatus

bb....bb: Name of the function that returned the invalid code

cccc: Detail code

(S)

When the message is output to the standard error output:

Terminates processing.

When the message is output to the error message dialog box:

Redisplays the window that was displayed immediately before the error occurred.

(O)

Contact the embedded database system administrator.

KFPK00207-E

aaaaaa: unable to assume user id (E)

The value specified for the -a or -ap option is invalid.

aaaaaa: Utility type

Pddbst: ajsembdbstatus

(S)

Terminates processing.

(O)

Specify the correct value for the -a or -ap option, and then re-execute the command.

KFPK10016-E

Insufficient memory in message buffer pool due to concurrent execution of "pddbst" (D+E)

Memory in the message storage buffer pool for the utility server was temporarily insufficient because more than one ajsembdbstatus command with the -db option was executed concurrently. Note that this error might cause the message KFPS00854-W to be output, although no server error has occurred in this case.

(S)

When the message is output to the standard error output:

Terminates processing.

When the message is output to the message dialog box:

Redisplays the window that was displayed immediately before the error occurred.

(O)

Wait until the ajsembdbstatus command currently being executed terminates, and then retry the operation.

KFPK10101-E

Unable to start pddbst (E)

The ajsembdbstatus -db command cannot be started for either of the following reasons:

The maximum number of concurrent utilities for the entire embedded database system was exceeded.

The embedded database is now terminating.

(S)

Terminates processing.

(O)

Correct the error and restart.

KFPK10107-W

No data

RDAREA="aa....aa" server=bb....bb (E)

The RD area does not contain any tables or indexes, so the status cannot be displayed.

aa....aa: RD area name

bb....bb: Embedded DB name

(S)

When the message is output to the standard error output:

Terminates processing.

(O)

Execute the ajsembdbsetup command to migrate the database to an embedded database, and then re-execute the command.

KFPK10300-I

Pddbst started (E)

Execution of the ajsembdbstatus -db command has started.

(S)

Continues processing.

KFPK10301-I

Pddbst terminated, return code=aa....aa (E)

Execution of the ajsembdbstatus -db command has terminated.

aa....aa: Return code

0: Normal termination

4: Normal termination, but with a warning message output. Alternatively, part of the processing was skipped.

8: Processing was canceled due to an error.

(S)

Terminates processing.

(O)

When the return code is 4 or 8, correct the error by checking the warning message or error message output to the standard error output or message log file.

KFPL00712-I

aa....aa started, table=bb....bb.cc....cc, server=dd....dd,spacelvl=e, generation=ff (L)

Unloading or reloading of the table bb....bb.cc....cc on the server dd....dd has started.

aa....aa: Executed processing

{Reload | Unload}

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: Server name

e: Blank conversion level

(S)

Continues processing.

KFPL00714-I

aa....aa ended, table=bb....bb.cc....cc, server=dd....dd, return code=ee (L)

For the table bb....bb.cc....cc on the server dd....dd, unloading, reloading, releasing of the free page being used, or reading of the page being used has terminated.

aa....aa: Executed processing

{Unload|Reload|Reclaim|Page read}

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: Server name

ee: Return code

(S)

Continues processing if the return code is 0 or 4, or terminates processing if the return code is not 0 or 4.

(O)

If the return code is not 0 or 4, correct the cause of the error according to the error message output to the message log file, and then re-execute the command.

KFPL00715-I

Index load started at aa....aa, index=bb....bb."cc....cc", RDAREA=dd....dd, generation=ee (L)

Index loading has started.

aa....aa: Server name

bb....bb: Authorization identifier

cc....cc: Index identifier

dd....dd: RDAREA name

(S)

Continues processing.

KFPL00716-I

Index load ended at aa....aa, index=bb....bb, RDAREA=cc....cc, return code=dd (L)

Index loading has terminated with the return code dd.

aa....aa: Server name

bb....bb: Index identifier

cc....cc: RDAREA name

dd: Return code

0: Normal termination

8: Abnormal termination

(S)

Continues processing.

(O)

For abnormal termination, correct the cause of the error according to the error message that was output before this message.

KFPL00717-I

Pdrorg started, func=aaaa (L)

Processing aaaa of the ajsembdbrorg command has started.

aaaa: Type of processing

rorg: Table reorganization

unld: Table unloading

reld: Table reloading

ixmk: Batch creation of indexes

ixrc: Index re-creation

ixor: Index reorganization

rclm: Reclaiming of free pages in use

bfon: Reading of pages

(S)

Continues processing.

KFPL00719-I

Pdrorg terminated, return code=aa (E+L)

Processing of the ajsembdbrorg command has terminated.

aa: Return code

0: Normal termination

4: Normal termination, but with a warning-level error not related to the processing occurring.

8: Abnormal termination

(S)

Terminates processing.

(O)

When the return code is not 0 or 4, correct the error by checking the error message output to the standard output or message log file, and then re-execute the command.

When the return code is 4, ignore the message and continue processing.

KFPL00721-I

aa....aa in table bb....bb.cc....cc deleted, RDAREA=dd....dd (L)

Line data in the table bb....bb.cc....cc has been deleted from the RDAREA dd....dd.

aa....aa: Deleted data

Data: Line data

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: RDAREA name

(S)

Continues processing.

KFPL00732-I

aa....aa started, table=bb....bb.cc....cc, spacelvl=d, generation=ee (L)

Unloading or reloading of the table bb....bb.cc....cc has started.

aa....aa: Executed processing

{Reload | Unload}

bb....bb: Authorization identifier

cc....cc: Table identifier

(S)

Continues processing.

KFPL00734-I

aa....aa ended, table=bb....bb.cc....cc, return code=dd (L)

Unloading or reloading of the table bb....bb.cc....cc has terminated.

aa....aa: Type of processing

Unload: Unloading

Reload: Reloading

bb....bb: Authorization identifier

cc....cc: Table identifier

dd: Return code

(S)

When the return code is 0 or 4:

Continues processing.

When the return code is not 0 or 4:

Terminates processing.

(O)

When the return code is not 0 or 4:

Correct the cause of the error according to the error message output to the log file, and then re-execute the command.

KFPL00736-I

Pdrorg restarted, at aa....aa,table=bb....bb."cc....cc"dd....dd (L)

Table reorganization was restarted at aa....aa.

aa....aa: Type of processing

unload: Unloading

delete: Deletion of data

reload: Reloading

ixrc: Index re-creation

status clear: Status clear

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: ", server=server-name" is displayed.

(S)

Continues processing.

KFPL00739-I

Pdreclaim terminated, return code=aaa (L)

Processing of the ajsembdbreclaim command has terminated with return code aaa.

aaa: Return code

0: Normal termination (Reclaiming of free pages in use has finished.)

4: Timeout (Reclaiming of free pages in use is in progress.)

8: Abnormal termination (Reclaiming of free pages in use failed).

Value other than above: Abnormal termination (The ajsembdbreclaim command cannot be started, or has terminated abnormally.)

(S)

Terminates processing.

(O)

When the return code is 4:

Wait for termination of the job that is accessing the table whose free pages are being reclaimed, and then re-execute the command.

When the return code is 8:

Correct the error by checking the message that was output before this message, and then re-execute the command.

When the return code is not 0, 4, or 8

The value is a return value from the system function. Determine the cause of the abnormal termination by checking the standard error output, message log file, Windows event log or syslog, correct the problem, and then re-execute the ajsembdbreclaim command.

KFPL00810-I

aa....aa restart at bb....bbth row (E+L)

Command processing was restarted at line number bb....bb.

aa....aa: Command name

Pdrorg: ajsembdbrorg

bb....bb: Number of lines from the beginning of the unload data file

(S)

Continues processing.

KFPL15046-E

aa....aa error occurred, file=bb....bb (E+L)

A file I/O error occurred.

aa....aa: Name of the process in which the error occurred

Open: Open processing

Read: Read processing

Write: Write processing

Close: Close processing

bb....bb: file name

(S)

Terminates processing. However, the system may continue processing if a file close error occurred.

(O)

Correct the cause of the error according to the message that was output after this message, and then re-execute the command.

KFPL15047-E

File I/O error occurred, reason=aa....aa, func=bb....bb, errno=cc....cc, (dd....dd) (E+L)

An error occurred during file I/O.

aa....aa: Cause of the error

Empty-file:

The specified file is empty (0 bytes).

File-format:

The specified file name is invalid.

File-lock:

Another user is using the file. The file name specified on the command line or in the control statement might be a file name that is being used by another user. Alternatively, file-lock resources specified in an OS kernel parameter might be insufficient.

If the ajsembdbcond-sample script is being executed, wait until the current execution terminates, and then re-execute the command. If the ajsembdbcond-sample script is not being executed, check the values of the kernel parameters for the file system.

Invalid-device:

The entry type (attribute) of the specified file is invalid. A directory name might be specified in a location that requires a file name (or vice versa), or a character type special file might be assigned to a file that cannot use a character type special file.

Invalid-path:

The path name is invalid.

Invalid-permission:

The permission for the specified file is invalid (access permission error). It is possible that the embedded database system administrator does not have access permission to use the file.

No-file:

The file to be read was not found. Alternatively, the file being written to was deleted.

No-space:

The file to be written to does not have sufficient free space.

In UNIX:

If this error occurs when there is sufficient free space on the disk, the embedded database file system area might not be defined as a large file, or the limit value of an OS kernel parameter might have been exceeded.

Specify 2 gigabytes or unlimited as the maximum file size that can be handled in the kernel parameter for file settings. Especially in AIX, care is required because the default file size limit is 1 gigabyte.

bb....bb: Name of the function in which the error occurred

A system function name is displayed if the error was detected in the OS.

A function name, beginning with p_f_ios, for the embedded database file system is displayed if the error was detected in the embedded database file system.

In all other cases, *** is displayed.

cc....cc: Error code

The error number returned by the system function (errno: external reference variable indicating the error status) is displayed if the OS detected the error.

The error code of the embedded database file system is displayed if the error was detected in the embedded database file system. For details about the error codes, see C. Error Codes Returned from Access Requests for an Embedded Database File System. The probable causes of the error and the corrective actions are as follows:

-1511:

The specified file path name might violate the file naming rules of the embedded database file system. Make sure that the area name contains no more than 117 characters and the file name contains no more than 30 characters.

-1532:

The specified file path name might be invalid. Correct the file path name. If you specify the embedded database file system name without specifying a file name, also specify a file name.

-1534:

The specified file name might be a file name that is being used by another job. Change the file name.

-1535:

Insufficient space. If space becomes insufficient as soon as the processing starts, the file size specified on the command line or in the control statement might exceed the limit of the embedded database file system. Use the ajsembdbaddarea command to add space.

-1540:

The embedded database system administrator does not have access permission for the embedded database file system. Grant access permission to the embedded database system administrator.

For any other cause, 0 is displayed.

dd....dd: Troubleshooting information (source file and line number in which the error was detected)

(S)

Terminates processing.

(O)

Using the cause of the error, function name, and error code, correct the error by referring to the errno.h file, the documentation for your OS, and C. Error Codes Returned from Access Requests for an Embedded Database File System. Then retry.

KFPL15227-E

Unable to aa....aa without bbbbbb privilege (E)

The aa....aa command cannot be executed because you do not have access permission for the table.

aa....aa: Command

pdrorg: ajsembdbrorg

pdreclaim: ajsembdbreclaim

bbbbbb: Required access permission

DBA: DBA permission

delete: DELETE permission

insert: INSERT permission

select: SELECT permission

(S)

Terminates processing.

(O)

Re-execute the command as the following user:

In Windows: User who has logged as a member of the Administrators group

In UNIX: User who has superuser privileges

If you executed the ajsembdbsetup command with the -a and -ap options, specify the same values as these options in the ajsembdbrorg or ajsembdbreclaim command and then execute that command.

KFPL20000-E

Internal function (aa....aa) error occurred, code=bbbbb (E)

Embedded DB detected an error by extension of the command processing.

aa....aa: Name of the function that detected error

bbbbbb: Error details code

(S)

Terminates processing.

(O)

Correct the error by referring error details code, and re-execute the command. For details about the error codes, see B. Return Codes of System Calls. The probable causes of the error and the corrective actions are as follows:

Detail code

Error cause

Action to be taken

-307

A timeout occurred.

Review the value that you set to pd_utl_exec_time operand.

Check the server load condition, and then re-execute the command when the server load is low.

-310

-5303

Embedded database for the execution does not operate normally.

Confirm an operation state of the embedded DB. After having started embedded DB when embedded DB does not start, execute a command again.

-314

A communication error occurred.

If the command processes were forcibly terminated by the ajsembdbcancel command, ignore this message.

Confirm the network status. Remove the cause, and then re-execute the command.

-382

A communication error occurred or the allocation handling of process performed timeout.

Confirm the network status. Remove the cause, and then re-execute the command.

Confirm the load situation of the server, and re-execute the command when the load of the server is low.

KFPL20001-E

Insufficient memory in message buffer pool due to concurrent execution of aa....aa (L)

Memory in the message storage buffer pool was temporarily insufficient when the ajsembdbreclaim and ajsembdbrorg commands were executed concurrently or more than one command with the same name was executed concurrently for the same embedded database. Note that this error might cause the message KFPS00854-W to be output, although no server error has occurred in this case.

aa....aa: Program name

{"pdrorg"}

(S)

Terminates processing.

(O)

Wait until the currently executed ajsembdbreclaim and ajsembdbrorg commands terminate, and then retry the operation.

KFPL20020-E

Transaction (aa....aa) error occurred, code=bbbbb (L)

The transaction could not be started or determined.

aa....aa: Type of transaction

{ begin | commit | rollback }

bbbbb: Error details code

(S)

Terminates processing.

(O)

Correct the error by referring to B. Return Codes of System Calls, and then re-execute the command.

KFPL25005-E

Invalid attribute exists in Control file, line=aa....aa (E)

The value of the line number aa....aa in the control information file is invalid.

The probable causes are as follows:

The path specified in the -d option of the ajsembdbrorg command is invalid.

The path specified in the -b option of the ajsrpdbsync command is invalid.

aa....aa: Line number in which the error occurred during analysis

(S)

Terminates processing.

(O)

Specify an absolute path in the -d option of the ajsembdbrorg command or -b option of the ajsrpdbsync command, and then re-execute the command.

KFPL25361-E

Lock time out error occurred, RDAREA=aa....aa (E+L)

The lock on the aa....aa database area for acquiring data timed out.

aa....aa: Database area name

(S)

Terminates processing.

(O)

Wait for a time when there are fewer job operations, and then re-execute the command.

KFPL27500-E

Transaction wait time over,index=aa....aa."bb....bb",RDAREA=cc....cc (L)

A timeout occurred during execution of the ajsembdbreclaim command because a transaction accessing the index could not be determined.

aa....aa: Authorization identifier

bb....bb: Index identifier

cc....cc: RDAREA name

(S)

Terminates processing.

(O)

Retry the operation only when as few jobs as possible are being executed. Alternatively, wait until the operation being performed on the unit by a command or JP1/AJS3 - View terminates, and then retry the operation.

KFPL31010-E

Invalid row length, line=aa....aa (R)

The length of the line data for the line number aa....aa in the input file is invalid.

This message is output when a problem is found in the data file stored in the directory specified in the -d option of the ajsembdbrorg command.

aa....aa: Line number

(S)

Terminates processing.

(O)

The character set or the endian form used in the data file stored in the directory specified in the -d option of the ajsembdbrorg command might be inconsistent. Make sure that the specified file is correct, and then retry the operation.

KFPL90002-I

Process aa....aa ended. return code=bb,yyyy/mm/dd,hh:mm:ss (S)

The processing indicated by aa....aa will now end.

aa....aa: Type of processing

rorg: Reorganization

bb: Return code

0: Normal termination. Reorganization of all tables terminated.

4: Normal termination. Reorganization of tables is in progress.

8: Termination with an error. The data was recovered from the backup.

12: Termination with an error. The data could not be recovered from the backup.

yyyy/mm/dd: Execution end date

hh:mm:ss: Execution end time

(S)

Terminates processing.

(O)

When the return code is 4:

The command might be delayed because of a heavy host load caused by other programs.

Re-execute the command when the host load has decreased.

When the return code is 8 or 12:

For details about the error, see the contents of the execution information file indicated in the message KFPL90003-E. If the ajsembdbcond-sample script is being executed, correct the error and then take appropriate action for the actions to be taken for errors, in Supplementary notes in 10.2.2(2)(c) Customizing the reorganization scripts in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

If the ajsembdbrorg command is being executed, correct the error and then re-execute the command.

KFPL90003-E

Eliminationg the cause of the error, refer to executed information file="aa....aa" (E)

The error indicated in the execution information file is found.

aa....aa: Execution information file name

(S)

Terminates processing.

(O)

Obtain the error details by checking the contents of the execution information file, and then correct the error.

KFPL90021-I

DB hold step ended (S)

Block processing for the database has ended.

(S)

Continues processing.

KFPL90022-I

Before backup step ended (S)

Backup processing before the main processing has ended.

(S)

Continues processing.

KFPL90023-I

aa....aa step started (S)

aa....aa processing will now start.

aa....aa: Type of processing

Reorganize: Reorganization

(S)

Continues processing.

KFPL90024-I

aa....aa step ended (S)

aa....aa processing will now end.

aa....aa: Type of processing

Reorganize: Reorganization

(S)

Continues processing.

KFPL90025-I

After backup step ended (S)

Backup after the main processing has ended.

(S)

Continues processing.

KFPL90026-I

DB release step ended (S)

Processing to release the database from the blocked state has ended.

(S)

Continues processing.

KFPL90027-I

DB stop process started (S)

The database will be stopped for error recovery processing.

(S)

Continues processing.

KFPL90028-I

Recover step started on aa....aa error (S)

Database recovery from the backup file has started.

aa....aa: Type of processing

rorg: Reorganization

(S)

Continues processing.

KFPL90101-I

aa....aa (R)

This message shows the command line used to execute the command.

aa....aa: Command line used to execute the ajsembdbrorg command

(S)

Continues processing.

KFPL90102-I

aa....aa (R)

This message shows one line of the control statement used to execute the ajsembdbrorg command.

aa....aa: Control statement used to execute the ajsembdbrorg command

(S)

Continues processing.

KFPO00107-E

"aa....aa(bb....bb)" failed. errno=cc....cc: dd....dd (E)

An error occurred in a system call issued within the embedded database system.

aa....aa: System call name

bb....bb: Name of the module or function making the system call

cc....cc: Errno value when the system call error occurred

dd....dd: Details on the system call error

(S)

Does one of the following according to the severity of the error:

Cancels processing, and terminates the process abnormally.

Cancels processing, and returns control to the caller of the running service.

Continues processing.

(O)

Determine the cause of the error with the documentation for your OS based on the system call name and the errno value. If a dump has been output to the core file, save the dump and contact the embedded database system administrator.

Action

After determining the cause of the error with the documentation for your OS based on the system call name and the errno value, correct the UAP, change the system definition, or re-create the OS.

The following explains the major corrective actions.

System call name

Calling module

errno

Error details

Action

open

Any

23

The number of open files exceeded the maximum for the system.

If the embedded database server runs on Windows, the work file for shared memory cannot be allocated due to insufficient space on the installation drive.

Increase the value specified in the nfile kernel parameter for the OS. In addition, stop any unnecessary processes and close any unnecessary windows.

If the embedded database server runs on Windows, allocate free space greater than the shared memory size on the installation drive.

24

There are too many open files in the relevant process.

If the embedded database server runs on Windows, the work file for shared memory cannot be allocated due to insufficient space in the installation drive.

If the error occurs during execution of a command that uses the embedded database, increase the value of the maxfiles kernel parameter for the OS.

If the embedded database server runs on Windows, allocate free space greater than the shared memory size on the installation drive.

logblib.c

999

In Windows, the work file in the embedded database may have been corrupted.

Make sure that the embedded database has stopped, and then delete all the following files for recovery.

Note, however, that files after number 4 may not exist.

embedded-database-practical-directory\uxpldir\spool\system\filmng.dat

embedded-database-practical-directory\uxpldir\spool\system\flg.dat

embedded-database-practical-directory\uxpldir\spool\system\shmmng.dat

embedded-database-practical-directory\spool\~pdatmode

embedded-database-practical-directory\spool\~pdipcid

embedded-database-practical-directory\spool\oslmqid

embedded-database-practical-directory\spool\oslsmid

embedded-database-practical-directory\spool\pdprcsts

embedded-database-practical-directory\spool\scdqid1

embedded-database-practical-directory\spool\scdqid2

embedded-database-practical-directory\tmp\pdommenv

All files under embedded-database-practical-directory\uxpldir\spool\shm

embedded-database-practical-directory\uxpldir\spool\system\semmng.dat

embedded-database-practical-directory\uxpldir\spool\system\msgmng.dat

When you start the embedded database after deleting the above files, make sure that no other applications such as Explorer are accessing embedded-database-practical-directory\tmp.

write

uss_dump

uss_dump_h

uss_dump_d

usm_dump

usm_rmdump

usm_svdump

12

The file system containing the embedded database practical directory is full.

Delete the trouble information from under the embedded database practical directory.

To delete the trouble information, use the OS rm command (del command in Windows).

shmat

ommalloc

ommrmalc

22

The shared memory for the embedded database was not found (the shared memory for the embedded database may have been deleted).

Before the OS started, a command that uses the embedded database might have been entered (includes cases in which the command is specified in the /etc/localrc file or any other OS environment file).

In Windows, a work file under the embedded database practical directory might have been deleted while the embedded database was running.

If the shared memory for the embedded database has been deleted, contact system administrator.

If a command for using the embedded database was executed before the OS was started, wait until the OS was started, and then re-execute the command.

If a command that uses the embedded database is specified in the OS environment file /etc/localrc, an error occurred because the command was executed before the OS had started. To prevent such an error, do not specify a command that uses the embedded database in the /etc/localrc file.

In Windows, if the embedded database has not terminated abnormally, forcibly terminate it and then restart the embedded database service.

If this message appears due to execution of a command that can be executed whether or not the embedded database is running, do not treat this message as an error. Since the command is operating normally, check the execution result of the command.

ommrmalc

24

The number of units of shared memory connected to the calling process exceeded the maximum for the system.

Specify an appropriate value for one of the following operating parameters:

In HP-UX: shmseg

In Solaris: shminfo_shmseg

In Linux: SHMSEG

In AIX 5L, set ON for the EXTSHM environment variable.

shmctl

ommfixed

1

The user who executed the command is not a superuser.

The owner of the files under the embedded-database-practical-directory/bin directory might have been changed illegally.

Check the owner of the executable file (the pdommfixed file under embedded-database-practical-directory/bin) and permissions for the owner.

If the owner is not root or does not have s permission (that is, the file mode is not -r-sr-xr-x), the owner of the files under embedded-database-practical-directory/bin was changed after the pdsetup command was executed. A superuser must re-create the embedded database environment. After the environment is created, restart the embedded database.

semget

osysemg

12

In Windows, no more semaphore identifiers are available.

Estimate the number of semaphore identifiers required for the embedded database, and then specify a larger value for the PDUXPLSEMMAX system environment variable. After specifying the setting, terminate the embedded database and then restart the service.

pdi_osm_get

999

For details about other major errno values, see B. Return Codes of System Calls.

KFPR00754-I

Pdcopy started (L+S)

Processing of the ajsembdbbackup command has started.

(S)

Continues processing.

KFPR00756-I

Pdcopy terminated, return code=aa (L+S)

Processing of the ajsembdbbackup command terminated with a return code shown below.

aa: Return code for the ajsembdbbackup command

0: Normal termination

8: Abnormal termination (An error occurred during copy processing, but some backups were created successfully.)

12: Abnormal termination (All copy processing failed.)

(S)

Continues processing.

(O)

For abnormal termination, correct the error by checking the error message that was output before this message, and then retry the operation.

KFPR00764-I

Pdrstr started (L+S)

Processing of the ajsembdbrstr command has started.

(S)

Continues processing.

KFPR00765-I

Pdrstr terminated, return code=aa (L+S)

Internal processing of the ajsembdbrstr command terminated with a return code shown below.

aa: Return code for internal processing of the ajsembdbrstr command

0: Normal termination

4: Termination with a warning (A close error occurred in the backup file or unload log file, or the data of the RDAREA to be recovered was not found in the backup file.)

8: Abnormal termination (An error occurred, but one or more RDAREAs were recovered successfully.)

12: Abnormal termination (Recovery failed for all RDAREAs.)

(S)

Continues processing.

Action

For abnormal termination, correct the cause of the error according to the error message that was output before this message.

KFPR16003-E

aaaaaa error occurred, file=bb....bb (E+L)

A file I/O error occurred.

aaaaaa: Processing in which an error occurred

Close: Close processing

Open: Open processing

Read: Read processing

Reopen: Open processing for the second or later volume in a multi-volume file

Write: Write processing

bb....bb: File name

(S)

Terminates processing. However, the system may continue processing if a file close error occurred.

Action

Correct the cause of the error according to the message that was output after this message, and then re-execute the command.

KFPR16005-E

Insufficient memory for PROCESS, size=aa....aa (L+S)

An attempt to allocate the work area required for executing the ajsembdbbackup command has failed due to insufficient memory.

aa....aa: Size of the area that was to be allocated (unit: bytes)

(S)

Terminates processing.

Action

Terminate unnecessary processes to free memory, and then retry the operation. Alternatively, add real memory for the OS.

KFPR16014-E

Pdcopy version aa....aa and HiRDB version bb....bb do not match (L+S)

The version of the command used internally by the ajsembdbbackup command differs from the version of the embedded database.

The database area specified in the -d option of the ajsembdbbackup command might differ from the area of the embedded database specified in the -id option.

aa....aa: Version or revision number of the command used internally by the ajsembdbbackup command

bb....bb: Version or revision number of the embedded database

(S)

Terminates processing.

(O)

Make sure that the values specified in the -d and -id options of the ajsembdbbackup command match the combination of the values of the -d and -id options used when the ajsembdbbuild command was executed, and then retry the operation.

KFPR16101-E

File I/O error occurred, reason=aa....aa, func=bb....bb, errno=cc....cc, (dd....dd) (L+S)

An error occurred during file I/O processing.

aa....aa: Cause of the error

File-lock:

The file you want to use cannot be read or written to because it has been locked by another utility. The file name specified on the command line or in the control statement might be a file name that is being used by another job. Alternatively, file-lock resources specified in an OS kernel parameter might be insufficient.

Invalid-device:

The entry type (attribute) of the specified file is invalid. A directory name might be specified in a location that requires a file name (or vice versa), or a character type special file might be assigned to a file that cannot use a character type special file.

Invalid-path:

The path name is invalid.

Invalid-permission:

The permission for the specified file is invalid (access permission error). It is possible that the embedded database system administrator does not have access permission to use the file.

No-file:

The file that was to be opened for reading was not found. Alternatively, the file being written to was deleted.

No-space:

The file to be written to does not have sufficient free space. Allocate sufficient free space.

In UNIX, if this error occurs when there is sufficient free space on the disk, the limit value of an OS kernel parameter might have been exceeded.

bb....bb: Name of the function in which the error occurred

A function name, beginning with p_f_ios, for the embedded database file system is displayed if the error was detected in the embedded database file system.

*** is displayed if the error was detected in the embedded file system in those cases in which a function was not being used.

In all other cases, a system function name is displayed.

cc....cc: Error number returned by the function (errno)

The error code of the embedded database file system is displayed if the error was detected in the embedded database file system.

The error number returned by the system function (errno: external reference variable indicating the error status) is displayed if the OS detected the error.

dd....dd: Source file name and line number where the error was detected

(S)

Terminates processing.

Action

Take appropriate action according to the following table.

Cause of the error

Action

The error was detected in the embedded database file system.

Correct the error by referring to C. Error Codes Returned from Access Requests for an Embedded Database File System, and then retry the operation.

The error was not detected in a function.

Correct the error indicated by aa....aa, and then retry the operation.

The OS detected the error.

Correct the error by referring to the OS documentation, and then retry the operation.

KFPR16203-E

aa....aa error occurred, file=bb....bb (L+S)

A file I/O error occurred.

aa....aa: Processing in which an error occurred

Close: Close processing

Open: Open processing

Read: Read processing

Write: Write processing

bb....bb: File name (If a system log file I/O error occurred, the file group name is indicated)

(S)

Terminates processing. In the case of the Close error, the system may resume processing.

Action

Refer to the message that was output after this message to eliminate the cause of the error, and then re-execute the command. If a system log file I/O error occurred, refer to the message output before this message.

KFPR16205-E

Insufficient memory for PROCESS, size=aa....aa (L+S)

An attempt to allocate the work area required for executing the ajsembdbrstr command has failed due to insufficient process-specific area.

aa....aa: Size of the area that was to be allocated (unit: bytes)

(S)

Terminates processing.

Action

Check whether another process is using a large amount of memory.

If another process is using a large amount of memory:

Wait until the process terminates, and then re-execute the command.

If another process is not using a large amount of memory:

Take one of the following actions to increase the amount of free space in memory:

Reduce the number of processes running concurrently.

Increase the swap area.

Add real memory.

KFPR16214-E

Pdrstr version aa....aa and HiRDB version bb....bb do not match (L+S)

The version of the command used internally by the ajsembdbrstr command differs from the version of the embedded database.

The database area specified in the -d option of the ajsembdbrstr command might differ from the area of the embedded database specified in the -id option.

aa....aa: Version or revision number of the database recovery utility

bb....bb: Version or revision number of embedded database

(S)

Terminates processing.

(O)

Make sure that the database area specified in the -d option of the ajsembdbrstr command is the area of the embedded database specified in the -id option.

KFPR16301-E

File I/O error occurred, reason=aa....aa, func=bb....bb, errno=cc....cc, (dd....dd) (L+S)

An error occurred during file I/O processing.

aa....aa: Cause of error:

Empty-file:

The specified file is empty (0 bytes).

File-format:

The specified file format differs from the actual file format. It is possible that the specified file name is incorrect or the file format specified on the command line or in the control statement does not match the contents.

File-lock:

The file to be used is locked by another utility and the file read/write operation cannot be executed. The file name specified in the command line or control statement might be in use by another job. In UNIX, there might be a shortage of file locking resources for an OS kernel parameter.

File-missing:

The specification of the unload log file or the backup file is incorrect.

Invalid-file:

A file was specified that was created incorrectly.

Invalid-parameter:

A combination of specified parameters is invalid.

Invalid-permission:

The specified file version is invalid (access privilege error). The AJS administrator might not have been granted access permission for the file being used.

Invalid-path:

The path name is invalid.

No-file:

File to be opened for the read operation was not found, or a file involved in the write operation was deleted.

No-space:

There is not enough space in the file subject to the write operation.

Unmatch-entry:

Header entry for header file does not match the specification in the control statements file. The name of the unmatched entry is enclosed in parentheses.

bb....bb: Name of the function in which the error occurred

cc....cc: Error number that is returned by the function (errno)

If an error was detected by the embedded database file system, the embedded database file system error code

If an error was detected when a function was not being used, 0

If an error was detected by the operating system, the error number returned by the system function (errno: foreign reference variable that displays the error status)

dd....dd: Maintenance information.

(S)

Terminates processing, or cancels command processing.

Action

Take action based on the following table:

Error cause

Action

Error was detected by the embedded database file system.

Correct the error by referring to C. Error Codes Returned from Access Requests for an Embedded Database File System, and then retry the operation.

Error was detected by mechanism other than a function.

From the error cause aa....aa, remove the cause of the error, and re-execute.

If Invalid-permission is output in an environment in which an AJS administrator is set, check whether the AJS administrator has the appropriate permission for the specified file.

Error was detected by the operating system.

Refer to the operating system manual, remove the cause of the error, and re-execute.

KFPR16318-E

Backup data not found, RDAREA name="aa....aa" (L+S)

The specified backup file does not contain a backup of the RDAREA.

aa....aa: Name of the RDAREA name without backup data

(S)

Recovers the RDAREA without using the backup data. If the unload log file is specified and the update log for the RDAREA is found, the system recovers the RDAREA by using the log only.

(O)

Verify the following, correct the error, and then retry the operation:

Before executing the ajsembdbrstr command, make sure that the RDAREA is in a recoverable state.

Make sure that the backup file is specified correctly.

KFPR16330-E

Log was not found when backup aa....aa at bb....bb-cc....cc, server=dd....dd (L+S)

When the -l option has been specified in the ajsembdbrstr command, the unload log file does not include the information for the period required for recovery.

aa....aa: Dates not included

started: Time copy acquisition started

ended: Time copy acquisition ended

bb....bb: System log record number 1

cc....cc: System log record number 2

dd....dd: Name of the server for which recovery is being performed

(S)

Interrupts embedded database recovery processing.

(O)

When the -l option in the ajsembdbrstr command is specified, specify an unload log file that includes the information for the period required for recovery, and then retry the operation. If the required unload log file does not exist, use only the backup file for recovery.

KFPR26001-E

Communication "aa....aa" error occurred, code=bbbbb (L+S)

A communication error occurred during execution of the ajsembdbbackup command.

aa....aa: Name of the RPC-related function in which the error occurred

bbbbb: Error code of the RPC-related function in which the error occurred

(S)

Terminates processing.

Action

Correct the error by referring to B. Return Codes of System Calls, and then retry the operation. If an error that the embedded database system administrator cannot handle has occurred, contact system administrator.

KFPR26006-E

Invalid parameter aa....aa exists at -b option in command line (L+S)

An option in the command line may contain an invalid parameter. A list RDAREA is not copied or recovered.

aa....aa: Invalid parameter

b: Option name

(S)

Waits until the analysis of the command line terminates, and then cancels processing. However, the system continues processing when all the following conditions are satisfied:

The -J option and the -r option are specified.

The message KFPR26061-W is output.

Action

Correct the specification on the command line, and then re-execute the command.

KFPR26012-E

HiRDB file aa....aa error, errno=bb....bb, HiRDB file name=cc....cc (L+S)

The error indicated in aa....aa occurred in the file indicated in cc....cc.

aa....aa: Error details

close: File close

create: File creation

fstat: Acquisition of file information

open: File open

read: File reading

write: File writing

expand: File expansion

reopen: Open of the second or later file during processing of multiple files

bb....bb: Error code

0: The requested size could not be read or written.

Other than 0: See C. Error Codes Returned from Access Requests for an Embedded Database File System.

cc....cc: Name of the file in which the error occurred

(S)

Cancels processing for a backup file. However, the system continues processing if there is another backup file or if all of the following conditions are satisfied:

The file is an embedded database file in an RDAREA.

The -J option is specified.

The error details indicate open or close.

The message KFPR26061-W was output.

There is another RDAREA that has not been processed yet.

Action

When the file is used for a database:

Recover the appropriate RDAREA, and then retry.

When the file is used for backup:

Correct the cause of the error according to C. Error Codes Returned from Access Requests for an Embedded Database File System, and then retry.

When the error code is -1556 or -1562, the probable causes are as follows:

Error code

Cause

-1556

After the embedded database file exceeded the initial allocation size, an attempt to expand the file using the secondary allocation size failed.

An attempt was made to expand the file beyond the limit on the number of times the embedded database file system area can be increased.

An attempt was made to expand the embedded database file more than the maximum number of times, which is 23.

-1562

The type of the embedded database file system area is not UTL.

If you cannot determine the cause of the error, contact system administrator.

KFPR26017-E

Insufficient memory in message buffer pool due to concurrent execution of "pdcopy" (L+S)

Memory in the message storage buffer pool for the utility server was temporarily insufficient when ajsembdbbackup commands were executed concurrently. Note that this error might cause the message KFPS00854-W to be output, although no server error has occurred in this case.

(S)

Terminates processing.

(O)

Wait until the ajsembdbbackup command currently being executed terminates, and then retry the operation.

KFPR26021-E

Unable to output result of pdcopy (L+S)

The processing result of the ajsembdbbackup command cannot be output because of the error displayed in the message output before this message.

(S)

Terminates processing.

Action

Correct the error, and then re-execute the command. Note that if no other error has occurred, the backup processing has terminated. Accordingly, re-execution is unnecessary if you do not need the execution result.

KFPR26022-I

Output result of pdcopy to aa....aa (L+S)

The processing result of the ajsembdbbackup command will be output to the aa....aa file.

aa....aa: Name of the output file

(S)

Terminates processing.

KFPR26072-E

Invalid time stamp found, RDAREA name=aa....aa, file name=bb....bb, offset=cc....cc, time stamp=(dd....dd,ee....ee) (L+S)

A page containing an invalid time-stamp was found.

aa....aa: RDAREA name

bb....bb: Embedded database file name. The last 64 bytes are displayed.

cc....cc: Decimal number indicating the relative record position of the page containing the invalid time-stamp as calculated from the beginning of the embedded database file

dd....dd: Time-stamp at the beginning of the page, converted to the date format YYYY/MM/DD HH:MM:SS

ee....ee: Time-stamp at the end of the page, converted to the date format YYYY/MM/DD HH:MM:SS

(S)

Terminates processing.

(O)

When using the ajsembdbbackup command with the -s option specified to create a backup:

The backup could not be created because the page to be backed up was being output. Re-execute the ajsembdbbackup command.

When using the ajsembdbbackup command without the -s option specified to create a backup:

The area in the displayed RDAREA is corrupted. You must recover the area by using the previously created backup.

KFPR26201-E

Communication "aa....aa" error occurred, code=bbbbb (L+S)

A communication error occurred during execution of the ajsembdbrstr command.

aa....aa: Name of the RPC-related function in which the error occurred

bbbbb: Error code of the RPC-related function in which the error occurred

(S)

Terminates processing.

Action

Correct the error by referring to B. Return Codes of System Calls, and then retry the operation.

KFPR26203-E

System call error, func=aa....aa, errno=bbb (L+S)

An error occurred during internal processing.

aa....aa: Maintenance information

bbb: Maintenance information

(S)

Terminates processing.

Action

Take corrective action according to the message displayed before or after this message.

KFPR26212-E

HiRDB file aa....aa error, errno=bb....bb, HiRDB file name=cc....cc (L+S)

The error indicated by aa....aa occurred in the file indicated by cc....cc.

aa....aa: Error details

close: File close

create: File creation

fstat: Acquisition of file information

open: File open

read: File reading

write: File writing

expand: File expansion

bb....bb: Error code

0: The requested data size could not be read or written.

Other than 0: See C. Error Codes Returned from Access Requests for an Embedded Database File System.

cc....cc: Name of the file in which the error occurred

(S)

When the file is a database file:

Skips recovery processing of the RDAREA, and continues recovery of other RDAREAs.

When the file is a backup file:

Cancels recovery processing.

(O)

When the file is a database file:

Use the ajsembdbbuild command to re-create the environment of the embedded database, and then retry the operation.

When the file is a backup file:

Retry with another backup file.

When the error details indicate write and the error code is 0, the file system for the OS might not have sufficient free space.

KFPR26217-E

Insufficient memory in message buffer pool due to concurrent execution of "pdrstr" (L+S)

Memory in the message storage buffer pool for the utility server was temporarily insufficient when ajsembdbrstr commands were concurrently executed. Note that this error might cause the message KFPS00854-W to be output, although no server error has occurred in this case.

(S)

Terminates processing.

(O)

Wait until the ajsembdbrstr command currently being executed terminates, and then retry the operation.

KFPR26220-E

System manager "aa....aa" failed, return code=bb....bb (L+S)

A system-related "aa....aa" function error occurred.

aa....aa: Name of the system-related function in which the error occurred

bb....bb: Error code of the system-related function in which the error occurred

(S)

Terminates processing.

Action

When the name of the system function with the error is pdi_omm_attach and the error code is -144:

The probable causes are as follows. Specify the correct host name in the -mh option, and then re-execute the command.

A host name is not specified in the -mh option, and the specified master directory RDAREA was not found on the server host on which the ajsembdbrstr command was entered.

A master directory RDAREA was not found on the server host for the host name specified in the -mh option.

For other cases:

Correct the error by referring to B. Return Codes of System Calls, and then retry the operation.

KFPR26221-E

Unable to output result of pdrstr (L+S)

The processing result of the ajsembdbrstr command cannot be output because of the error that was displayed in the message output before this message.

(S)

Terminates processing.

Action

Correct the error, and then re-execute the command. Note that if no other error has occurred, the backup processing has terminated. Accordingly, re-execution is unnecessary if you do not need the execution result.

KFPR26222-I

Output result of pdrstr to aa....aa (L+S)

The processing result of the ajsembdbrstr command will be output to the aa....aa file.

aa....aa: Name of the output file

(S)

Continues processing.

KFPR26226-E

SystemID of aa....aa is invalid (L+S)

The system cannot recover the database because the system ID for aa....aa does not match the running embedded database.

aa....aa: File type

backup file: Backup file

sys log file: System log file

unload log file: Unload log file

(S)

Terminates processing.

Action

Take one of the following actions:

For a backup file or an unload log file:

Specify the correct file, and then retry the operation.

For a system log file

The system log might have been corrupted. Use the ajsembdbbuild command to re-create the environment of the embedded database, and then recover the data from the backup created with the ajsembdbbackup command.

KFPR26227-E

-l or -d option is not specified for backup file with -M s option (L+S)

An unload log file is not specified when the backup file to be obtained with the -M s option specified is used for recovery.

(S)

Terminates processing.

Action

When the -l option is specified:

Specify the unload log file, and then retry.

When the -d option is specified:

Specify the directory containing the unload log file, and then retry.

KFPR26229-E

To recover Master RDAREA, pdstart should be executed with -r option (L+S)

To recover the master directory RDAREA, use the ajsembdbstart command with the -r option to start the embedded database.

(S)

Terminates processing.

(O)

Use the ajsembdbstop command to terminate the embedded database, use the ajsembdbstart command with the -r option to restart the embedded database, and then retry the operation.

KFPR26270-W

Log information, specified log Run ID=aa....aa Gen No=bb....bb, log Run ID=cc....cc Gen No=dd....dd in RDAREA name="ee....ee" (L)

Not all of the unload log files required for recovering the database are specified in the -l option of the ajsembdbrstr command. This message indicates the log information stored in the RDAREA and the log information in the unload log files specified in the -l option of the ajsembdbrstr command.

Cautionary note

If a backup was created in the following ways, this warning message appears even when all of the unload log files required for recovering the database are specified. In such cases, ignore the warning message.

A backup was created after normal termination of the database:

This message appears even when all of unload log files containing the system logs used after the next normal startup are specified in the -l option.

When the ajsembdbbackup command was executed, the scheduler service database was updated (for example, a jobnet was updated):

This message appears even when all of unload log files containing the system logs used after swapping of the system log file are specified in the -l option.

aa....aa: Log information (log server run ID of the system log file) in the first unload log file#1 specified in the -l option

bb....bb: Log information (generation number of the system log file) in the first unload log file#1 specified in the -l option

cc....cc: Log information (log server run ID of the system log file) stored in the RDAREA#2

dd....dd: Log information (generation number of the system log file) stored in the RDAREA#2

ee....ee: RDAREA name

#1: The first unload log file is the applicable unload log file.

#2: The log information is stored in the RDAREA when the embedded database terminates normally.

Action

According to the values in cc....cc and dd....dd, specify all the unload log files required for recovering the database in the -l option of the ajsembdbrstr command, and then retry the operation.

KFPR26272-W

No unload log file in specified directory, directory name = aa....aa (S+L)

The unload log file was not found under the specified directory.

aa....aa: Directory name (If the length is more than 100 characters, only the last 100 characters are output.)

(S)

Continues processing.

Action

Check the aa....aa directory name. If the directory file is incorrect, correct the error and then retry the operation.

KFPR26273-E

Error occurred directory analysis, directory name = aa....aa (S+L)

An error occurred during analysis of the aa....aa directory name.

aa....aa: Directory name (If the length is more than 100 characters, only the last 100 characters are output.)

(S)

Terminates processing.

Action

Check whether the specified directory name is correct. If the directory file is incorrect, correct the error and then retry the operation.

KFPR26280-E

Specified backup file invalid. filename=aa....aa, code=bb....bb (S+L)

The specified backup file is invalid.

aa....aa: Name of the backup file in which the error occurred (When the name contains more than 100 characters, the last 100 characters of the backup file name are output.)

bb....bb: Cause of the error

other: A backup file that was not created by using the ajsembdbbackup command

error: A backup file created by pdcopy, but which terminated with an error (return code 12)

(S)

Terminates processing.

(O)

Specify the correct backup file name, and then retry the operation.

KFPS00615-W

Multi-connection address definition invalid, reason code=aa, hostname=bb....bb (L)

There is an error in the specification of the system definition file of the embedded database.

aa: Maintenance information

bb....bb: Host name that is specified incorrectly

(S)

Continues processing to start the embedded database.

JP1/AJS3 linkage products cannot connect to the host where this message was output.

(O)

Terminate the embedded database normally, and then change the system definition file of the embedded database. Then, restart the embedded database.

KFPS00705-E

Error found while analyzing definition file (L)

An error was detected during analysis of the system definition file of the embedded database.

(S)

Waits for the embedded database to start.

Action

Check whether the system definition file of the embedded database was unintentionally changed. If the system definition file was changed, restore it to its original state, and then execute the ajsembdbstart command.

If other messages were output before or after this message, also check those messages. If you cannot correct the error, contact system administrator.

KFPS00715-E

Unable to continue processing serious error occurred (reason code=aaa). enter pdrpause (E+L)

An error that prevents further processing of the embedded database occurred.

aaa: Reason code

1: There is a problem with the installation environment of the embedded database.

2: A memory shortage occurred

3, 4, 5, 8, 9, 10, 11, 13, 14, 15, 42, 43, 44, 101, 102, 103, 104, and 105: An attempt to access the system file of the embedded database has failed.

6: Processing to acquire the system time has failed.

7: The embedded database terminated abnormally three consecutive times within 30 minutes during restart processing of the embedded database.

20: The system definition of the embedded database has an error.

(S)

Terminates processing.

Action

Take action as follows:

If the ajsembdbstart command did not terminate after this message was output, execute the ajsembdbstop -f command to terminate it.

If other messages were output before or after this message, also check those messages.

Correct the error indicated by the reason code.

1:

- Make sure that installation of the embedded database terminated normally.

- In UNIX, check whether the /etc/inittab file was unintentionally changed.

2:

- Check the status of the running process to make sure that the amount of memory available is greater than the estimated value.

3, 4, 5, 8, 9, 10, 11, 13, 14, 15, 42, 43, 44, 101, 102, 103, 104, and 105:

- Check whether the system file of the embedded database was unintentionally changed.

6:

- Check the running status of the OS for any problems (for example, insufficient resources).

7:

- Check whether all the system log files of the embedded database are full and unable to be overwritten.

- Check whether the environment settings of the embedded database (such as a directory and port number) duplicate any other settings on the same host.

- In UNIX, make sure that the character set types of the OS and the embedded database match.

20:

- Check whether the system definition file of the embedded database was unintentionally changed.

In UNIX, execute the ajsembdbstart -R command.

In Windows, restart the embedded database service (JP1/AJS3 Database setup-identifier-name). If the service has not stopped, stop the service and then restart it.

If the embedded database does not start automatically, execute the ajsembdbstart command.

If the error persists after you take the above actions, contact system administrator.

KFPS00993-I

Accepted process abnormal end request. PID=aa....aa, TRNGID=bb....bb, TRNBID=cc....cc, REQUEST=dd....dd (L)

This message can be output in the following cases:

The embedded database system has terminated abnormally.

An error has occurred during access to the embedded database.

The ajsembdbcancel command canceled processing of the embedded database operation command.

aa....aa: Maintenance information

bb....bb: Maintenance information

cc....cc: Maintenance information

dd....dd: Maintenance information

(S)

Terminates the processing.

Action

Usually, you can ignore this message. If JP1/AJS3 has output any other error messages, take action based on those messages.

KFPS01040-E

aa....aa error occurred in physical status file bb....bb. reason code=cc....cc (E+L)

An error occurred during access to the system file indicated by bb....bb in the embedded database.

aa....aa: Maintenance information

bb....bb: Path name of the system file

cc....cc: Reason code

(S)

Switches to another system file and continues processing.

Action

Determine the cause of the error from the following reason codes, and take appropriate action.

Reason code

Cause

Action

0000000006

The file was not found.

Make sure that the system file exists in the directory that was specified when the environment of the embedded database was created.

0000000020

You do not have access permissions.

Make sure that you have permission to access the directory that was specified when the environment of the embedded database was created and the created system files.

0000000021

You do not have access permissions.

Make sure that you have permission to access the directory that was specified when the environment of the embedded database was created and the created system files.

0000000022

A lock error (the target is being used by another process) occurred.

Wait a while and then retry the operation.

For a cluster system, check whether both the primary node and secondary node access a system file on the shared disk.

0000000023

System resources (file lock) are insufficient.

Check the system parameters for the OS.

0000000024

You do not have access permissions.

Make sure that you have permission to access the directory that was specified when the environment of the embedded database was created and the created system files.

0000000025

System resources (file descriptors) are insufficient.

Check the system parameters for the OS.

0000000026

The file was not found.

Make sure that the system file exists in the directory that was specified when the environment of the embedded database was created.

0000000027

An I/O error occurred.

Check whether a disk error or other OS-related error occurred. Also check whether you can access the directory that was specified when the environment of the embedded database was created.

0000000028

A memory shortage occurred.

Check the system parameters for the OS.

0000000029

The file was not found.

Make sure that a system file exists in the directory that was specified when the environment of the embedded database was created.

0000000030

In UNIX, the number of open character type special files exceeds the limit. In Windows, the number of open files exceeds the limit.

Check the system parameters for the OS.

0000000031

The file name is invalid.

The probable causes are:

An invalid character is specified in the file name.

The length of the file name exceeds the limit.

Check the directory name that was specified when the environment of the embedded database was created.

0000000037

The file was not found.

Make sure that the system file exists in the directory that was specified when the environment of the embedded database was created.

KFPS01150-E

Auto log unload service terminated. server=aa....aa:create dir=bb....bb:reason=cccc (L)

The auto log unload function has terminated on the aa....aa server.

aa....aa: Embedded database server name

bb....bb: Name of the directory in which unload log files are created

cccc: Reason code indicating the error details

1660: Unloading of the system log file has failed in the directory in which all unload log files are created.

1661: An attempt to create a process for the auto log unload processing has failed.

1664: The unload log file you attempted to create is being used by another process.

(S)

Continues processing.

Action

Take one of the following actions:

When the reason code is 1660:

There is insufficient disk space for the directory containing unload log files, the directory has not been created, or a disk error has occurred. Allocate more free space, create the directory, or correct the disk error. Next, execute the ajsembdboplog -r command or restart the embedded database normally to resume the auto log unload function.

When the reason code is 1661:

Check the maximum number of processes that can be executed on the server host and terminate unnecessary processes. In addition, make sure that sufficient system resources such as memory are available.

When the reason code is 1664:

Check whether any process is using a file in the directory in which unload log files are created. Then, execute the ajsembdboplog -r command to restart the embedded database normally to resume the auto log unload function.

When the reason code is other than above:

Collect the following data, and then contact system administrator:

- All files under embedded-database-practical-directory/spool or embedded-database-practical-directory\spool

- System definition file

- Windows event log or syslog

- Execution result of the ajsembdbstatus -l command

KFPS01153-I

Auto log unload service restart. server=aa....aa:create dir=bb....bb:reason=cccc (L)

The automatic log unload functionality for the embedded database will now restart.

aa....aa: Maintenance information

bb....bb: Name of the directory in which unload log files are created

cccc: Reason code

1662: The ajsembdboplog -r command was executed to restart the automatic log unload functionality.

(S)

Continues processing.

KFPS01154-I

Auto log unload service stopped. server=aa....aa:create dir=bb....bb:reason=cccc (L)

The automatic log unload functionality for the embedded database has stopped.

aa....aa: Maintenance information

bb....bb: Name of the directory in which unload log files are created

cccc: Reason code

1662: The ajsembdboplog -t command was executed to stop the automatic log unload functionality.

(S)

Continues processing.

KFPS01200-E

Failure to open aaaa(xx....xx)log file. element file: bb....bb, system A/B: c,reason code=dddd-ee (L)

An attempt to open the embedded database system file has failed.

aaaa: File type

sys: System log file

xx....xx: Maintenance information

bb....bb: File name

c: System type

a: System A

b: System B

dddd: Reason code

ee: Maintenance information

The following table lists the reason codes and describes the actions to be taken.

(S)

Blocks the file in which the error occurred, and continues processing.

Action

Take action according to the reason codes.

Reason code

Meaning

Action to be taken by the embedded database system administrator

101

A memory shortage occurred.

Re-estimate memory.

201

The file name is invalid.

The probable causes are:

An invalid character is specified in the file name.

The length of the file name exceeds the limit.

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

202

The specified file name is not a RAW file. Alternatively, the device for this file was not found.

Check the settings specified when the environment of the embedded database was created.

203

The embedded database system file was not found.

207

The number of open files exceeded the limit.

Check the system parameters for the OS.

208

You do not have access permissions.

Make sure that you have permission to access the directory that was specified when the environment of the embedded database was created and the created system files.

209

An I/O error occurred.

Check whether a disk error or other OS-related error occurred. Also check whether you can access the directory that was specified when the environment of the embedded database was created.

210

The embedded database system file is inconsistent.

Re-create the environment of the embedded database. If the error persists after re-creating the environment, contact system administrator.

211

You do not have access permissions.

Make sure that you have permission to access the directory that was specified when the environment of the embedded database was created and the created system files.

212

The file was not found.

Make sure that the system file exists in the directory that was specified when the environment of the embedded database was created.

218

219

The specified file cannot be used as a log file.

Use another file. If a new file is required, use the ajsembdbaddlog command to add the new file.

220

The specified file is not a log file.

Check the settings specified when the environment of the embedded database was created.

221

Lock segments are insufficient.

Check the system parameters for the OS.

222

A lock error (the target is being used by another process) occurred.

Wait a while and then retry the operation.

For a cluster system, check whether both the primary node and secondary node access a system file on the shared disk.

KFPS01202-E

Failure to write to aaaa(xx....xx) log file. element file: bb....bb, system A/B: c,reason code=dddd-ee (L)

An attempt to write to the embedded database system file has failed.

aaaa: File type

sys: System log file

xx....xx: Maintenance information

bb....bb: File name

c: System type

a: System A

b: System B

dddd: Reason code

209: An I/O error occurred.

ee: Maintenance information

(S)

Blocks the file in which the error occurred, and continues processing.

Action

Take the following action:

When the reason code is 209

Check whether a disk error or other OS-related error has occurred. Also check whether you can access the directory that was specified when the environment of the embedded database was created.

KFPS01220-E

Request to swap aaaa(xx....xx) log file unable to be executed because there is no standby log file group available. (L)

A factor causing system log swapping occurred, but there was no system log file that could be swapped in.

The reasons for no available system log file are as follows.

There was no standby system log file.

The standby system log file group was one of the following states:

Was waiting for unloading

State in which overwriting was not possible (a sink point dump related to a particular system log file was being collected)

Was being read during recovery processing for the embedded database

Was being used for command processing

aaaa: Maintenance information

xx....xx: Maintenance information

(S)

Stops the embedded database system.

Action

Take appropriate corrective action as follows:

If the automatic unload function has stopped, remove the cause of the stoppage.

Unload the system log file.

Add a system log file.

Restore the system log file to operability.

KFPS01228-W

Error occurred aaaa(bb....bb) log for waiting syncpoint acquisition opportunities. reason code=cccc (L)

A timeout occurred while the system was waiting for the internal processing of the embedded database to finish.

aaaa: Maintenance information

bb....bb: Maintenance information

cccc: Maintenance information

(S)

Continues processing.

Action

If this message appears during execution of the ajsembdbbackup command, wait a while and then re-execute the command. If this message still appears after re-execution of the command or appears at a time other than during execution of the ajsembdbbackup command, contact system administrator.

KFPS01251-E

Aaaa(xx....xx) log file group bb....bb is in invalid state; change file group state. (L)

The status of the bb....bb log file group in aaaa (xx....xx) is invalid. Change the status of the file group.

The invalid status of the log file group is caused by an online fault that has occurred in the previous cycle in the group. If the status is left as is, it will not be possible to acquire log information. Specify the -g or -o option in the ajsembdboplog command to unload the log file. The status of the log file group will change to unloading completed.

aaaa: Log file type

sys: System log file

xx....xx: embedded database server name

bb....bb: Name of a log file group with the invalid status

(S)

Continues processing to start the log service function.

(O)

Execute the ajsembdboplog command to acquire the log information and change the file group status. For details about the ajsembdboplog command, see ajsembdboplog in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

KFPS01256-E

No standby file groups of aaaa(xx....xx) log are available. (L)

There is no system log file group that can be used.

aaaa: Maintenance information

xx....xx: Maintenance information

(S)

Interrupts the processing to start the embedded database.

Action

See the "Action" section for the KFPS01220-E message.

KFPS01271-I

Unloading completed. generation number=aa....aa, start block number=bb....bb, end block number=cc....cc (E+L)

Unloading has been completed. The range of unloaded blocks are indicated.

aa....aa: Generation number of the log file group being unloaded

bb....bb: Number of the first unloaded block

cc....cc: Number of the last unloaded block

Note

If any unloaded log blocks are missing, ******** is displayed for cc....cc. Note that this message is displayed only when the automatic log unloading function is used.

KFPS01277-E

Log point information is invalid. info=aaaa (L)

An environment error was detected when the embedded database was being restored.

aaaa: Maintenance information

(S)

Continues processing.

Action

Check the following and take appropriate action:

Whether the backup file specified in the ajsembdbrstr command is invalid.

If neither of these problems exists, contact system administrator.

KFPS01278-W

Failure to processing log file group. type: aaa(bb....bb),file group: cc....cc,reason code=dddd-ee (L)

The cc....cc log file group used by the bb....bb server will be ignored because the file status cannot be referenced for the reason indicated in dddd.

aaa: Log type (sys or lar)

bb....bb: Embedded database server name

cc....cc: File group name

dddd: Reason code

209: Log file I/O error

213: Log file open error

215: Input to the log file is impossible.

222: Another process is using this file group.

1601: There is no applicable log file.

ee: System maintenance information

(S)

Continues processing, ignoring the log file group indicated in the message.

(O)

There is no problem if you do not use the log file indicated in the message.

During execution of the ajsembdbrstr command

If you have used the log file from the time a backup was obtained until the current time, it may not be possible to recover the database correctly. If the message KFPS01279-W was output, consider its contents, and after contacting the system administrator, take corrective action. After taking corrective action, re-execute the command.

For other cases

Take action according to the reason code, and then re-execute the command. If the message KFPS01279-W was output, take corrective action for the error indicated in the message, and then re-execute the command.

Action

There is no problem if the log file indicated in the message is not required for executing the ajsembdbrstr command. If the log file is required for executing this command, check the following and then take action.

If an error occurred in the log file group or if the log file group was initialized after being used online, check whether the log file can be recovered. If it can be recovered, recover it and then retry.

Check whether the log file specification in the server definition is correct. Correct any error, and then retry.

If neither of the above is applicable, contact system administrator.

KFPS01279-W

Unable to use log file. element file: aa....aa, system A/B: b,reason code=cccc-dd (L)

The status of the aa....aa log file cannot be referenced for the reason indicated in cccc. This log file will be ignored.

aa....aa: Log file name

b: The system where an error occurred (a or b)

cccc: Reason code

dd: System maintenance information

(S)

Continues processing, ignoring the log file.

(O)

There is no problem if you do not use the log file indicated in the message, or if the message KFPS01278-W for the file group containing the log file is not output immediately after this message. If neither of the above is applicable, determine the cause of the error according to the reason code, and then contact the administrator.

Action

There is no problem if the log file shown in the message is not required for executing the ajsembdbrstr command. If the log file is required for executing this command, determine the cause of the error according to the reason code, and perform recovery by following the instructions in the message KFPS01278-W, and then, retry. The following lists the reason codes.

Reason code

Meaning

Operator action

Action by the embedded database system administrator

101

A memory shortage occurred.

Wait until the currently running process terminates, and then re-execute the command.

Re-estimate memory.

201

The file name is invalid.

Probable causes are:

An invalid character is specified in the path name.

The length of the embedded database file name exceeded the limit (30 characters).

Specify the file name correctly, and then re-execute the command

--

202

The name of the embedded database file system area for the specified path is not an embedded database file system area.

Check the name of the embedded database file system area for the specified path, and then re-execute the command

Check the file specification in the pdlogadpf operand.

203

The specified path device is not initialized for the embedded database file system.

--

207

The upper limit was exceeded when the embedded database file system area for the specified path was opened.

--

208

You do not have permission to access the embedded database file system area for the specified path.

Check access permissions for the embedded database file.

Check the file specification in the pdlogadpf operand.

209

An I/O error occurred.

Determine the cause of the I/O error, and take action.

--

210

The version of the embedded database file system is inconsistent.

--

Check the file specification in the pdlogadpf operand.

211

You do not have permission to access the specified file.

Check the access permission for the log.

--

212

The specified file is not found.

--

Check the file specification in the pdlogadpf operand.

221

Lock segments are insufficient.

Check the number of record lock segments that is specified when the OS is started.

222

The system log file is being used by another process.

Check the operation status of the system log file or its file group, and then re-execute the command.

--

603

Management information on the file is corrupted.

Initialize this file.

605

The file structure of the file differs from the current file structure. The file structure might have been changed.

Contact the embedded database system administrator to find out if the file structure has been changed. If the file structure has not been changed, initialize this file.

Check the definition to make sure that the file group that uses the file and the system log file have not been changed. If the file structure has been changed, return the file structure in the definition to its original state.

1607

The file has not been used in the embedded database.

Check the file group.

--

Legend:

--: Not applicable

KFPS01286-E

Unable to perform swapping because no standby log file group is available. (E)

Swapping is not possible because there is no system log file to be swapped in.

(S)

Cancels command processing.

(O)

Take corrective action as follows, and if required, re-execute the command:

If the automatic log unloading function has stopped, remove the cause of the stoppage and then restart the function.

Use the ajsembdbaddlog command to add the system log file.

For details about the ajsembdbaddlog command, see ajsembdbaddlog in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

KFPS01390-W

Unable to expand sys(aa....aa) log file, file group=bb....bb, system A/B=c, reason=dd....dd (L)

The system log file cannot be expanded. From this point, the corresponding system log file is removed as a candidate for expansion.

aa....aa: Maintenance information

bb....bb: System log file name

c: System type

a: System A; b: System B

dd....dd: Reason code

The reason code and the action are summarized in the table below.

(S)

Continues processing.

(O)

Take the corrective action described for the applicable reason code in the table below.

Action

Take the corrective action suggested for the applicable reason code in the following table.

Reason code

Meaning

Operator action

Embedded DB system administrator action

101

A memory shortage occurred.

None

Re-estimate memory.

205

The disk is full.

None

Make sure there is sufficient free disk space.

209

An input/output error occurred.

Read the message displayed before or after this message, identify the cause of the error, and take corrective action.

If the corresponding system log file is included again as a candidate for expansion, you need to reconfigure the embedded database environment.

221

Lock segments are insufficient.

None

Review the OS kernel parameters.

1691

The size of an added system log file has exceeded the limit on file size.

None

For an operation that involves a large number of units, consider distributing the load by dividing the operation into multiple operations. If the job processing load is likely to increase in the future, consider building an embedded database environment with greater capacity.

1694

The size of the system log file has reached the limit on file size.

None

For an operation that involves a large number of units, consider distributing the load by dividing the operation into multiple operations. If the job processing load is likely to increase in the future, consider building an embedded database environment with greater capacity.

KFPS01391-W

Sys(aa....aa) log files expansion bb....bb, {output file name=cc....cc | expanded size=dd....dd} (L)

Expansion of the system log file has started or ended. cc....cc is output when expansion starts, and dd....dd is output when expansion ends.

aa....aa: Maintenance information

bb....bb: Processing description

start: Processing started

complete: Processing ended

cc....cc: Maintenance information

dd....dd: Maintenance information

(S)

Continues processing.

Action

If the automatic log unloading function has stopped, remove the cause (such as a full disk) and try to start the function again.

KFPS01801-E

Unable to start HiRDB unit due to improper operational environment. reason code=aa....aa (E)

The embedded database cannot be started because the operation environment is not ready.

aa....aa: Reason code

(S)

Cancels startup of the embedded database.

Action

Take the appropriate action shown in the following table, and then start the embedded database.

Reason code

Cause

Action

MEMORY

Process-specific memory or shared memory is insufficient.

See the descriptions of SHM_EINVAL, SHM_ENOMEM, and SHM_ENOSPC.

PAUSE

An error that prevents further processing of the embedded database occurred.

See other messages output to the command input window, Windows event log, or syslog.

PROGRAM

A prerequisite product was not found.

Install the prerequisite product.

SETUP

The embedded database is not registered in the OS. In Windows, the embedded database service has stopped.

In UNIX, use the ajsembdbbuild command to register the embedded database in the OS. In Windows, start the embedded database service.

SHM_EINTR

A signal was received during processing to allocate shared memory.

Determine the cause of the signal and take corrective action, and then restart the embedded database.

SHM_EINVAL

The shared memory size exceeded the maximum for the system. In Windows, the work file for shared memory cannot be allocated due to insufficient space on the installation drive.

Increase the maximum size of the shared memory segment for the system. In Windows, allocate free space greater than the shared memory size on the installation drive.

SHM_EMFILE

The number of open files exceeded the maximum for the system.

Reduce the number of the open files, or increase the number of files that can be opened in the system.

SHM_ENOMEM

Memory for the shared memory size was not found in the system.

Increase the amount of real memory in the system.

If the message KFPO00107-E or KFPO00113-E was output before or after this message, also check that message.

SHM_ENOSPC

In UNIX, the number of shared memory IDs exceeded the maximum defined in the system. In Windows, the installation drive does not have sufficient free space required for allocating the required size of shared memory.

In UNIX, reduce the number of shared memory segments, or increase the maximum number of shared memory IDs.

In Windows, if the message KFPO00107-E or KFPO00113-E was output before or after this message, also check that message.

SHM_EOVER

An internal contradiction occurred.

Contact system administrator.

SHM_CALC***

An internal contradiction occurred. *** is any character string (maintenance information).

Contact system administrator.

KFPS01819-I

Server aa....aa failed information. process ID=bb....bb, C-PID=cc....cc(dd....dd), TIME=eeffgg, PROGRAM=hh....hh (L)

This message contains maintenance information for the embedded database.

aa....aa: Maintenance information

bb....bb: Maintenance information

cc....cc: Maintenance information

dd....dd: Maintenance information

eeffgg: Maintenance information

hh....hh: Maintenance information

(S)

Continues processing.

KFPS01820-E

Server aa....aa failed. process ID=bb....bb, service group name=cc....cc, run mode=dd....dd, critical state=e,critical mask=ff....ff, end state=gg....gg, server type=hhh (E+L)

The server aa....aa has stopped. The following status is detected.

Value of gg....gg

Description

007f

0009

The system accepted a request for forced termination of the server process. This message appears when the ajsembdbcancel command is executed. Determine the cause of the forced termination request for the process (including execution of the ajsembdbcancel command) based on the message output before or after this message, and then take action as required.

0003

0083

The system accepted a request of forced termination of the server process. Determine the cause of the forced termination request for the process based on the status of the executed transaction and the message output before or after this message, and then take action as required.

0006

0086

0100

0800

The embedded database process terminated abnormally because an error was detected during processing.

Determine the cause of the abnormal termination based on the message output before or after this message, and then take action as required.

8000

An attempt to start a process failed or a process terminated abnormally due to insufficient memory. Take one of the following actions:

Reduce the number of processes running on the same server host.

Increase the swap area.

Add real memory.

In Windows, check the specified value of the desktop heap.

c000

A connect system call was issued, but connection was not established because the connection destination had gone down or because a network failure occurred.

c100

The second or later SQL response could not be sent because the connection destination had gone down or because a network failure occurred.

c200

A timeout of the embedded database client was detected during a transaction when the embedded database client had control.

c300

The remote communication socket was closed because an error occurred in the destination during communication processing.

c400

A timeout of the client was detected when the client had control and a transaction was not in progress. Alternatively, a timeout related to pd_watch_pc_client_time specified in the embedded database system was detected during connection of a Windows embedded database client.

c500

A special file (FIFO) could not be obtained when the server was started.

c600

The maximum number of transactions that can be processed concurrently on the embedded database was exceeded. Since many rollbacks might have occurred, wait for completion of the rollbacks and then re-execute the UAP.

c700

Abnormal termination was detected on the client requesting SQL (JP1/AJS3 scheduler service process) during execution of SQL on the embedded database.

c800

An attempt to send an SQL request has failed because a network failure occurred between the server and the system manager.

c900

An attempt to receive a second or later SQL request has failed because a network failure occurred between the sender and the system manager.

d000

The child process was killed because the parent process was killed during transaction processing.

d100

Server processing was canceled because the UAP processing did not terminate within the monitoring period specified in PDSWAITTIME and PDSWATCHTIME in the client environment definitions. Alternatively, the related server processing was canceled because the pdcancel command was executed.

d300

Although an error was detected, the system terminated processing without outputting troubleshooting information because the specification of the pd_dump_suppress_watch_time operand was valid.

d500

An error occurred during determination of a transaction.

000f

ff00

The server process of the embedded database was forcibly terminated by the OS kill command.

008b

An OS stack overflow may have occurred while the embedded database was running. The following are the actions to be taken for the causes of the stack overflow.

Cause 1

The probable cause is:

A user-defined routine that performs many calls or enters an infinite loop was executed.

Action

Check the value of the maxssiz kernel parameter, and then increase the stack size.

Cause 2

An attempt to expand the stack failed due to insufficient OS memory.

Action

Terminate unnecessary programs to increase the amount of free space in memory.

aa....aa: Name of the stopped server

bb....bb: Process ID of the stopped server

cc....cc: Service group name of the stopped server

dd....dd: Run mode of the server immediately before it stopped

PDBSV: Embedded database server

PDBSYS: Embedded database being processed

e:

N: Not a critical state

Y: Critical state

Since information on the embedded database is shared by multiple processes, the management table in the shared memory is referenced or updated. If a process that is updating the shared memory terminates abnormally, table information becomes inconsistent, disabling subsequent processing, which includes processing by other processes. As much as possible, the system prevents a forced termination from occurring in this processing period (called the critical period). If the system cannot prevent a forced termination in the critical period due to a failure, the embedded database terminates, and the integrity of the table information will be recovered when the embedded database is restarted.

ff....ff: Critical information

gg....gg: End status of the process returned by wait(2) (**** is displayed for an embedded database command.)

hhh: Server type (*** is displayed for a server other than an embedded database server)

(S)

Terminates processing on the server on which an error occurred, and then restarts the server if necessary.

Action

Determine the cause of the server stop according to the message output before this message or from the troubleshooting information (dump or trace), and then take action. If necessary, restart the server. Note that troubleshooting information is not output when gg....gg is c000, c100, c200, c300, c400, c500, c600, c700, c800, c900, d000, d100, d200, d300, or d500.

KFPS01826-I

HiRDB dir = aa....aaHiRDB vrs = bb....bbunit run ID = cc....ccHiRDB ID = ddddunit ID = eeee (L)

This message shows the environment of the embedded database.

aa....aa: Embedded database practical directory name

bb....bb: Embedded database version

cc....cc: Maintenance information

dddd: Maintenance information

eeee: Maintenance information

(S)

Continues processing.

KFPS01829-E

aa....aa invalid; stops unit startup (E)

The contents of aa....aa were changed without a normal stopping of the embedded database.

aa....aa: Contents of the change

System Version: Embedded database version

(S)

Cancels startup of the embedded database.

Action

Restore the embedded database to its old version, restart the embedded database, and then terminate it normally. Next, change the version of the embedded database and then restart the embedded database.

KFPS01851-E

Server aa....aa initialization error occurred; return code=bb....bb (E+L)

An initialization error occurred during startup of the embedded database.

aa....aa: Maintenance information

bb....bb: Maintenance information

(S)

The embedded database is abnormally terminated.

Action

Restart the embedded database. If this message still appears after the embedded database is restarted, contact system administrator.

KFPS04619-E

Unable to execute aa....aa command due to HiRDB unit not offline or not terminate normally (S+R)

The aa....aa command cannot be executed because the embedded database has not stopped.

aa....aa: Command name

(S)

Terminates processing.

Action

The embedded database might have been running (including start and end processing when the command was executed). This command cannot be executed if the database is running.

If the embedded database is running, use the ajsembdbstop command to perform a normal termination and then retry the operation. If the embedded database is not running, first start the embedded database, use the ajsembdbstop command to perform a normal termination, and then retry the operation.

Cautions applying only to the UNIX version

The ajsembdbunset command cannot be entered if the embedded database has terminated abnormally or if it has been forcibly terminated by the ajsembdbstop -f command.

KFPS05120-W

Waiting for UAP and/or utility disconnect in HiRDB unit aaaa, current connect user count = bbb (L)

The system is waiting for termination of the UAP or a utility.

aaaa: Unit ID for waiting for termination

bbb: Number of connected users who are waiting for termination

(S)

Continues processing. A new user cannot connect to the embedded database. Termination processing of the embedded database is delayed (15 minutes) until the UAP or utility processing terminates. When the UAP or utility processing terminates, the embedded database termination processing starts.

The system outputs detailed information about the user connected to the embedded database to the connected user information file (embedded-database-practical-directory/spool/cnctusrinf or embedded-database-practical-directory\spool\cnctusrinf). The system outputs the execution results of commands to the connected user details file (embedded-database-practical-directory/spool/cnctusrdtl or embedded-database-practical-directory\spool\cnctusrdtl).

If the UAP or utility stops before or after this message is output, the above information may not be included in the detail information for the user connected to the embedded database.

(O)

Check the connected user based on the connected user information file (embedded-database-practical-directory/spool/cnctusrinf or embedded-database-practical-directory\spool\cnctusrinf) and take action. If you cannot determine the connected user, use information output to the connected user details file (embedded-database-practical-directory/spool/cnctusrdtl or embedded-database-practical-directory\spool\cnctusrdtl) to check the connected user, and then take action.

The following shows an output example of the connected user information file.

Output example:

UNIT ID : M350(173420)
UID  PID    GID  SVID  TIME   PROGRAM
C-GRP  C-PID  C-IP
334  22118  300  fes1  173330 uap00
WS     22205  172.17.32.37

UNIT ID:

Indicates the unit ID and the time when the cnctusrinf file was created (hour, minute, and second).

UID:

Indicates the user ID of the user currently connected to the embedded database.

PID:

Indicates the process ID of the user currently connected to the embedded database.

GID:

Indicates the group ID of the user currently connected to the embedded database.

SVID:

Indicates the name of the server to which the user is connected.

Nothing might be displayed immediately after the server process of the embedded database has started.

TIME:

Indicates the time when the embedded database accepted the service request (hour, minute, and second). For a server to which the user is not connected, 999999 is displayed.

PROGRAM:

Indicates the connection process name.

The name of a JP1/AJS3 command or process is output using 30 or fewer characters. If a command for the embedded database is executed, a name other than the name of the executed command may be displayed.

****** may be displayed immediately after the server process of the embedded database has started.

C-GRP:

Always blank.

C-PID:

Indicates the process ID of the client.

C-IP:

Indicates the IP address of the client.

KFPU00219-E

Command argument invalid. file=aa....aa, line=bb....bb, command=cc....cc (E+L)

The format of the definition file of the embedded database is incorrect.

aa....aa: Definition file name

bb....bb: Line in which the error occurred

cc....cc: Maintenance information

(S)

Terminates processing.

(O)

Correct the definition file, and then try the operation again.

1.4 Messages beginning with KNAC (Messages that are output by communication control and agent management)

This section lists messages that begin with KNAC (messages output by communication control and agent management).

Note that, for messages that begin with KNAC, the control responsible for outputting a message is determined by the message ID. The following table lists the message IDs and the applicable control.

Table 1‒1: Message IDs and applicable control

No

MessageID

Applicable control

1

KNAC0001 to KNAC0999

Communication control

2

KNAC1001 to KNAC1999

Agent management

KNAC0001-I

Network service started. (host-name)(maintenance-information)

The communication control function has started.

(S)

Continues processing.

KNAC0002-I

Network service ended. (host-name)

The communication control function has terminated.

(S)

Terminates the communication control function.

KNAC0003-E

An attempt to start the network service failed. (host-name) : maintenance-information-1 maintenance-information-2 maintenance-information-3

Startup of the communication control function has failed. You will not be able to receive notifications about job execution and job termination during agent execution.

(S)

Terminates the communication control function.

(O)

Check the following, and then restart the JP1/AJS3 service:

Whether system resources are sufficient

Whether the user who started JP1/AJS3 has superuser privileges or has logged as a member of the Administrators group

Whether the maximum number of processes that can be started in the entire system is temporarily exceeded

Whether the host name has been resolved

If the host name has not been resolved, check the hosts file, jp1hosts definition file, jp1hosts2 definition file, or DNS server settings.

KNAC0005-E

Memory became insufficient. : maintenance-information-1 maintenance-information-2 maintenance-information-3

A memory shortage has occurred.

(S)

Cancels processing.

The system cancels the communication control function if it detects a memory shortage while memory is being secured for the basic part, for which processing cannot be continued.

(O)

See Release Notes, and check whether the required amount of memory has been allocated.

If the required amount of memory has been allocated, stop other unnecessary applications, and then re-execute the processing during which the memory shortage occurred. If the same message is output again, revise the memory estimate.

KNAC0006-E

Unexpected error occurred during communication control processing.: maintenance-information-1 maintenance-information-2 maintenance-information-3

An unexpected error occurred during communication control processing.

(S)

Continues processing.

(O)

Collect data, and contact the system administrator.

For details about the data to be collected, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KNAC0007-E

Invalid communication control environment settings file: maintenance-information-1 maintenance-information-2 maintenance-information-3

The environment settings file for communication control is invalid.

(S)

Ignores the invalid setting, and continues processing.

(O)

Check the services file and specify the correct service name and port number, and then restart the JP1/AJS3 service. For details about the ports used for JP1/AJS3, see A.1 Tables of port numbers in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

If the problem persists, collect data, and contact the system administrator.

For details about the data to be collected, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KNAC0011-E

System resources became insufficient during communication.

A system resource shortage has occurred during communication processing.

(S)

Interrupts the current processing.

KNAC0013-W

Thread for communication abnormally ended, and then restarted.: maintenance-information-1 maintenance-information-2 maintenance-information-3

A restart occurred because the communication thread terminated abnormally.

(S)

Continues processing.

KNAC0014-E

The port can't change to the reception state.: port_number=port-number maintenance-information-1 maintenance-information-2

The port number specified in the environment settings file for communication control cannot be changed to the receive state.

(S)

Continues processing.

(O)

Check whether the port specified in the services file is being used by another program. If it is being used by another program, terminate the program, and then restart the JP1/AJS3 service.

For details about the ports used for JP1/AJS3, see A.1 Tables of port numbers in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

KNAC0401-W

Received data is invalid. (maintenance-information-1,maintenance-information-2)

Invalid data has been received.

(S)

Ignores the data, and continues processing.

(O)

Check whether the port name or port number defined in the environment settings file for communication control is correct.

KNAC0601-E

An error occurred during TCP/IP communication process-name(connection destination host name: destination-host-name, port number: port-number, system call: system-call-name, system error number: system-error-number).

An error occurred during TCP/IP communication.

(S)

Cancels the requested processing.

(O)

When the process-name is connect or accept:

Check the following probable causes:

JP1/AJS3 was not running.

The port numbers used on the manager and the job execution host when a job was submitted did not match.

The default gateway was changed while JP1/AJS3 was running.

The IP address of the manager on the logical host and the IP address of the agent belong to different networks.

There was a problem with the network (includes the hardware).

The number of socket ports that can be used in the entire system was insufficient.

A memory shortage occurred.

In a cluster configuration, the logical IP address is released faster than JP1/AJS3 stops in the failover settings.

Take corrective action for above causes as described below, and then issue the request again.

Start JP1/AJS3.

Before changing the network configuration, you must stop the JP1/AJS3 service.

Review the network settings, including the hardware settings. For example, execute the ping command to check whether communication is possible.

Check the socket status, and wait until there are fewer TIME_WAIT sockets. You can also suppress communication errors by increasing the recovery time for the TIME_WAIT port managed by the OS.

Check the memory status and re-estimate the memory requirement.

The settings need to be specified so that the logical IP address is released later than JP1/AJS3 stops.

When the process-name is send or recv:

The destination JP1/AJS3 might have terminated abnormally. In a cluster configuration, JP1/AJS3 might have been forcibly terminated because of a failover. Check the JP1/AJS3 status on the destination host and the contents of the integrated trace log. After determining the cause of the error, remove it. If JP1/AJS3 has stopped, restart it and then issue the request again. If you cannot determine the cause, obtain the internal trace log and then contact the system administrator.

KNAC0602-E

Processing timed out during TCP/IP communication process-name(connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system call: system-call-name, system error number: system-error-number).

An error occurred during TCP/IP communication.

(S)

Cancels the requested processing.

(O)

When the process-name is connect or accept:

The status of the destination host might be as described below.

Check the host status, remove the cause of the error, and then issue the request again.

If JP1/AJS3 at the connection destination is not running, start it.

If the default gateway was changed while JP1/AJS3 was running, stop the JP1/AJS3 service before execution starts.

The IP address of the manager on the logical host and the IP address of the agent must belong to the same network.

Review the network settings to determine whether there is a problem with the network (includes the hardware). For example, execute the ping command to check whether communication is possible.

In a cluster configuration, if the logical IP address is released earlier than JP1/AJS3 stops in the failover settings, change the settings so that the logical IP address is released later than JP1/AJS3 stops.

Be careful that the values for timeouts, number of retries, and retry interval for communication connections are not too small. Values that are too small will reduce the retry interval for communication, making it difficult to avoid communication faults that could result in frequent errors of the types described.

When the process-name is send or recv:

The destination JP1/AJS3 might have terminated abnormally. In a cluster configuration, JP1/AJS3 might have been forcibly terminated because of a failover. Check the JP1/AJS3 status on the destination host and the contents of the integrated trace log. After determining the cause of the error, remove it. If JP1/AJS3 has stopped, restart it and then issue the request again. If you cannot determine the cause, obtain the internal trace log and then contact the system administrator.

KNAC0603-E

Processing retried out during TCP/IP communication process-name(connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system call: system-call-name, system error number: system-error-number).

An error occurred during TCP/IP communication.

(S)

Cancels the requested processing.

(O)

When the process-name is connect or accept:

Check the following probable causes:

The destination JP1/AJS3 was not running.

The default gateway was changed while JP1/AJS3 was running.

The IP address of the manager on the logical host and the IP address of the agent belong to different networks.

There was a problem with the network (includes the hardware).

The number of socket ports that can be used in the entire system is insufficient.

A memory shortage occurred.

In a cluster configuration, the logical IP address is released faster than JP1/AJS3 stops in the failover settings.

Take corrective action for above causes as described below, and then issue the request again.

Start JP1/AJS3.

Before changing the network configuration, you must stop the JP1/AJS3 service.

The same network must be used.

Review the network settings, including the hardware settings. For example, execute the ping command to check whether communication is possible.

Check the socket status, and wait until there are fewer TIME_WAIT sockets. You can also suppress communication errors by increasing the recovery time for the TIME_WAIT port managed by the OS.

Check the memory status, and re-estimate the memory requirement.

The settings need to be specified so that the logical IP address is released later than JP1/AJS3 stops.

When the process-name is send or recv:

The destination JP1/AJS3 might have terminated abnormally. In a cluster configuration, JP1/AJS3 might have been forcibly terminated because of a failover. Check the JP1/AJS3 status on the destination host and the contents of the integrated trace log. After determining the cause of the error, remove it. If JP1/AJS3 has stopped, restart it and then issue the request again. If you cannot determine the cause, obtain the internal trace log and then contact the system administrator.

KNAC0604-W

An error (content-of-error) occurred during TCP/IP communication process-name, and the processing will be retried (connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system call: system-call-name, system error number: system-error-number).

A retry occurred because of a TCP/IP communication error.

(S)

Retries TCP/IP communication (process-name).

(O)

If the system error number is 00002740, note that there was a shortage of socket ports when the job was executed. See 3.1.1(5) OS tuning in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide, and consider adjusting the OS parameters.

If job execution failed, there might be an error in the network settings. Referring to your JP1/Base manual, check the settings for cluster operation and make sure the JP1/Base communication settings are correct.

KNAC0605-E

The local host name could not be obtained in the TCP/IP communication process-name(connection destination host name: destination-host-name, port number: port-number, system call: system-call-name, system error number: system-error-number).

An error occurred during TCP/IP communication.

(S)

Retries the request acceptance processing, if the processing was request acceptance processing.

(O)

For request acceptance processing, the name service might have caused a problem. Check the status of the local host, remove the cause of the error, and then issue the request again.

KNAC0606-E

The socket could not be opened because the processing has too many open files (connection destination host name: destination-host-name, port number: port-number, system call: system-call-name, system error number: system-error-number).

An error occurred during TCP/IP communication.

(S)

Retries the request acceptance processing, if the processing was request acceptance processing.

Cancels request processing, if the processing was request processing.

(O)

Increase the maximum number (set in the kernel parameter) of files that can be opened.

For information about how to estimate the kernel parameter, also see Release Notes.

KNAC1001-I

The agent manager function started (host-name)(maintenance-information).

The agent management function has been started.

(S)

Continues processing.

KNAC1002-I

The agent manager function ended (host-name).

The agent management function has been terminated.

(S)

Terminates the agent management function.

KNAC1003-E

An error occurred during start processing of the agent manager function.: maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

Startup of the agent management function has failed.

(S)

Terminates the agent management function.

(O)

Take corrective action according to a previously output message.

If no such message was output, collect data and contact the system administrator.

For details about the data to be collected, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KNAC1100-I

The command ended normally.

The command has terminated normally.

(S)

Continues processing.

KNAC1101-I

The output of the agent manager information started.

Output of agent management information will start.

(S)

Continues processing.

KNAC1102-I

The output of the agent manager information ended.

Output of agent management information will end.

(S)

Continues processing.

KNAC1111-E

The exec-agent already exists.

The name of an agent that has already been registered was specified in the ajsagtadd command.

(S)

Terminates command processing.

(O)

Check the name that has already been registered, specify a different agent name, and then retry the operation.

KNAC1112-E

The exec-agent-group already exists.

The name of an agent group that has already been registered was specified in the ajsagtadd command.

(S)

Terminates command processing.

(O)

Check the agent group name that has already been registered, specify a different agent name, and then retry the operation.

KNAC1113-E

The exec-agent does not exist.

The name of an unregistered agent was specified.

(S)

Terminates command processing.

(O)

Use the name of a registered agent, and then retry the operation.

KNAC1114-E

The exec-agent-group does not exist.

The name of an unregistered agent group was specified.

(S)

Terminates command processing.

(O)

Use the name of a registered agent group, and then retry the operation.

KNAC1115-E

The exec-agent is already connected.

An attempt was made to associate an already associated execution agent with the execution agent group.

(S)

Terminates command processing.

(O)

Check the agent definition information, and then retry the operation.

KNAC1116-E

The status of delivery-limitation is not blocked.

The status of delivery-limitation for the execution agent or execution agent group that is to be deleted is not shutdown.

(S)

Terminates command processing.

(O)

Change the status of delivery-limitation for the execution agent or execution agent group that is to be deleted to shutdown, and then retry the operation.

KNAC1117-E

Cannot execute because some job is being executed.

Command processing cannot be executed because there is a job whose status is running or queuing.

(S)

Terminates command processing.

(O)

Check the job status, and then retry the operation.

KNAC1118-E

Host name cannot be resolved.

Probable causes are:

The logical host name specified in the -h option or the JP1_HOSTNAME environment variable could not be resolved.

An attempt to connect to the authentication server failed.

(S)

Terminates command processing.

(O)

If the -h option or the JP1_HOSTNAME environment variable contains a logical host name, review the specified value and check the hosts file and other settings. Then re-execute the command.

If the authentication server is not running, start JP1/Base.

KNAC1119-E

The agent manager function has stopped and the processing cannot be executed.

Probable causes are:

The logical host name contains an error.

Execution is not possible because the agent management function has stopped.

(S)

Terminates command processing.

(O)

Make sure that the logical host name specified in the -h option or the JP1_HOSTNAME environment variable is identical to the created logical host name, including the use of upper case and lower case, and then re-execute the operation.

If the JP1/AJS3 service is not running, start that service and then re-execute the command.

KNAC1120-E

Cannot delete - the exec-agent is connected to the exec-agent-group.:maintenance-information

The execution agent specified in the -a option in the ajsagtdel command cannot be deleted because it is already connected as the connection-destination execution agent to the execution agent group.

(S)

Terminates command processing.

(O)

Use the ajsagtshow command to check which execution agent group is connected to the connection-destination execution agent. Next, use the ajsagtalt command to exclude the corresponding execution agent that is to be deleted from the execution agent group identified by using the ajsagtshow command, and then retry the operation.

KNAC1121-E

An attempt to connect to the host failed.

An attempt to connect to the host failed.

(S)

Terminates command processing.

(O)

The manager IP address for the host name might have been changed.

The probable causes are:

If automatic startup of the JP1/AJS3 service is set, the IP address for the manager host name was allocated to the NIC after the JP1/AJS3 service started.

If the Windows MediaSense feature is enabled, the IP address was changed due to a temporary network problem.

Take one of the following actions according to the cause of the error:

Make sure that the IP address for the manager host name has been allocated to the NIC, and then restart the JP1/AJS3 service.

In Windows, you can set the JP1/Base service startup delay time to adjust the time when the service starts. See the explanation of the order in which the services are started and terminated in the Job Management Partner 1/Base User's Guide.

Correct the network problem, and then restart the JP1/AJS3 service.

KNAC1122-E

The settings of the agent definition information file (agent-definition-file-name) are invalid (line: line-number, item: item-name).

The agent definition contains an error.

(S)

Terminates command processing.

(O)

Check the definition information on the indicated line (line-number) in the agent definition file, correct the error, and re-execute the command.

line-number indicates the line in the agent definition file causing the error and item-name indicates the item causing the error.

The character strings indicated by item-name and their meanings are as follows:

FLAG: Flag

AGENT: Name of the execution agent

AGENT GROUP: Name of the execution agent group

STATUS: Status of delivery-limitation

HOST: Name of the target host

CON-EXE: Maximum number of concurrently executable jobs

LINKAGENT: Name of the execution agent group to be grouped

DESCRIPTION: Description

*: Items could not be analyzed.

KNAC1123-E

No execution permissions for this command.

The user attempting to execute the command does not have the required permissions for the command operation.

(S)

Cancels command execution.

(O)

Check the following:

Whether the OS user executing the command has been registered as a JP1 user on the authentication server

For details, see 6.5.1(3) JP1 user names when agent management information is operated on with commands in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

Whether the JP1 permission level required to execute the command has been set for the JP1 resource group (JP1_Queue) of the JP1 user (OS user)

For details, see 6.4.1(2)(c) Access permissions for working with agent management information in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

KNAC1124-E

The exec-agent cannot be added because the exec-agent already reached the number of definitions.

An execution agent cannot be added because the number of execution agent definitions has reached the limit.

(S)

Cancels command execution.

(O)

Delete an execution agent, and then retry the operation.

KNAC1125-E

The exec-agent-group cannot be added because the exec-agent-group already reached the number of definitions.

An execution agent group cannot be added because the number of execution agent group definitions has reached the limit.

(S)

Cancels command execution.

(O)

Delete an execution agent group, and then retry the operation.

KNAC1126-E

Valid definition does not exist in the specified agent definition information file.:file-name

Probable causes are:

The execution agent definition file specified in the -f option of the ajsagtadd command does not contain a valid definition.

A directory has been specified in the -f option of the ajsagtadd command.

(S)

Cancels command execution.

(O)

Write the agent definition file correctly, and then re-execute the command. Alternatively, specify the correct file name for the agent definition file, and then re-execute the command.

KNAC1127-E

The number of exec-agent for the connection destination exceeds the limit.:maintenance-information

When the ajsagtadd command was executed to add an execution agent group, the number of connection-destination execution agents specified in the -l option reached the limit for execution agents that can be defined.

(S)

Cancels command execution.

(O)

Review the number of connection-destination execution agents at specified in the -l option of the ajsagtadd command, and then re-execute the command.

KNAC1128-E

The concurrently-executable job limit is invalid.: specified-value

There is a problem with the time period specified in the -c option of the ajsagtadd or ajsagtalt command or with the specification of the maximum number of concurrently executable jobs.

(S)

Cancels command execution.

(O)

Review the element indicated by specified-value, and then re-execute the command.

The maximum number of concurrently executable jobs is specified in time-time=maximum-number-of-concurrently-executable-jobs format, in which the two elements of the time period are specified joined by a hyphen (-). These elements are hours and minutes at 30-minute intervals in hh:mm format.

The values for hh are 0 or a value from 00 to 23.

The values for mm are 0, 00, and 30.

The range of values that can be specified for the maximum number of concurrently executable jobs is from 0 to 4,294,967,295.

KNAC1129-E

The same exec-agent name cannot be specified more than one time.: overlapping-exec-agent-name

The -l option of the ajsagtadd command contains multiple connection-destination execution agents that have the same name.

(S)

Cancels command execution.

(O)

Remove the duplication, and then re-execute the command.

KNAC1130-E

The specified exec-agent for the connection destination does not exist.: exec-agent-name

No connection-destination execution agent is specified in the -l option of the ajsagtadd command or the -l, -m, or -u option of the ajsagtalt command.

(S)

Cancels command execution.

(O)

Use the ajsagtshow or ajsagtprint command to check existing execution agent names, specify the correct execution agent names, and then re-execute the command.

KNAC1131-E

The specified exec-agent is not connected.

The connection-destination execution agent specified in the -m or -u option of the ajsagtalt command has not been connected to the execution agent group specified in the -g option.

(S)

Cancels command execution.

(O)

Use the ajsagtshow or ajsagtprint command to check the name of the execution agent that is connected to the execution agent group, specify the correct execution agent name, and then re-execute the command.

KNAC1500-E

Memory became insufficient.:maintenance-information-1:maintenance-information-2:maintenance-information-3

A memory shortage has occurred.

(S)

Cancels processing.

The system cancels the agent management function if it detects a memory shortage while memory is being secured for the basic part, in which processing cannot be continued.

(O)

Check whether memory use has reached or exceeded the estimated value by examining the status of the process that was running when the problem occurred. Later, if necessary, re-execute the processing in progress when the memory shortage occurred.

KNAC1501-E

An unexpected error occurred during agent management processing.:maintenance-information-1:maintenance-information-2:maintenance-information-3

An unexpected error occurred during agent management processing.

(S)

Continues processing.

(O)

Collect data, and then contact the system administrator.

For details about the data to be collected, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KNAC1503-E

Not enough space in file system for agent management.

There is not enough area in the file system used for agent management.

(S)

Interrupts the current processing.

KNAC1504-E

System resources became insufficient during agent management processing.

A system resource shortage has occurred during agent management processing.

(S)

Interrupts the current processing.

KNAC1505-E

The number of files being processed exceeded the system limit during agent management processing.

The number of files that can be processed exceeded the limit for the system during agent management processing.

(S)

Interrupts the current processing.

KNAC1506-E

Shared memory is invalid. The exec-agent information cannot be obtained.:maintenance-information-1:maintenance-information-2:maintenance-information-3

The agent information cannot be acquired because shared memory is invalid.

(S)

Cancels the requested processing.

(O)

Restart the JP1/AJS3 service.

KNAC1507-E

A system call error occurred. maintenance-information-1 maintenance-information-2 maintenance-information-3

A system call error occurred.

(S)

Cancels the requested processing.

(O)

Take corrective action for the causes as described below, and then issue the request again.

System call name: ftok

Reason code: 2 (ENOENT)

The file used for status monitoring management was not found.

Check whether the JP1/AJS3 service is running on the specified host while the status monitoring function is enabled.

System call name: shmget

Reason code: 22 (ENOENT)

There is no shared memory.

Check whether the JP1/AJS3 service is running on the specified host while the status monitoring function is enabled.

System call name: shmget

Reason code: 12 (ENOMEM)

There is a memory shortage.

Stop unnecessary applications, and then start the JP1/AJS3 service. If the same message is output again, correct the memory estimate.

System call name: shmget

Reason code: 17 (EEXIST)

Shared memory exists.

Check the integrated trace log for whether the KAVU7239-W message was output before or after this message. If the message was output, read the message explanation to determine the cause of the error, remove the cause, and then restart the JP1/AJS3 service.

System call name: shmget

Reason code: 22 (EINVAL)

Shared memory exists.

Check the integrated trace log for whether the KAVU7239-W message was output before or after this message. If the message was output, read the message explanation to determine the cause of the error, remove the cause, and then restart the JP1/AJS3 service.

System call name: open

Reason code: 12 (ENOMEM)

There is a memory shortage.

Stop unnecessary applications, and then start the JP1/AJS3 service. If the same message is output again, correct the memory estimate.

System call name: open

Reason code: 23 (ENFILE)

The total number of files that can be opened has reached the system limit.

Stop unnecessary applications, and then start the JP1/AJS3 service. If the same message is output again, correct the number-of-files estimate.

System call name: open

Reason code: 24 (EMFILE)

The number of files that the process has opened has reached the maximum value.

Stop unnecessary applications, and then start the JP1/AJS3 service. If the same message is output again, correct the number-of-files estimate.

KNAC1508-E

An error occurred while accessing the database.:maintenance-information-1:maintenance-information-2

An error occurred while the database was being accessed.

(S)

If the embedded database was disconnected, the system reconnects the embedded database.

If reconnection is successful, the system outputs the KNAC1520-I message, and continues processing.

If reconnection fails, or for any reason other than above, the system cancels processing.

(O)

Check whether this message was output for the standby logical host in a cluster configuration when the JP1/AJS3 service was started. If it was output, the common definition information on the executing host might not have been set on the standby host after the embedded database was set up. Make sure that the common definition information on the logical host matches on both the executing and the standby hosts. If the information is inconsistent, set the common definition information residing on the executing host, on the standby host. For details, see 8.2.3 Changing the common definition information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under Windows), or 17.2.3 Changing the common definition information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under UNIX).

If this message is output when the ajsagtadd, ajsagtalt, or ajsagtdel command is executed, the embedded database might have been disconnected. If the KNAC1520-I message is output immediately after this message, no problem exists, despite the reported error. If the command terminated abnormally, make sure that the embedded database is running, and then re-execute the command.

If this message is output when the agent automatic definition function is used to execute the job for an undefined execution agent, the embedded database might have been disconnected. If the KNAC1520-I message is output immediately after this message, no problem exists, despite the reported error. If a job terminated abnormally, make sure that the embedded database is running, and then re-execute the job.

If the above does not apply, take corrective action according to a previously output message.

If a message was not output previously, collect data and then contact the system administrator.

For details about the data to be collected, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KNAC1509-E

An error occurred in a job execution control.:maintenance-information-1:maintenance-information-2

An error occurred in job execution control.

(S)

Cancels processing.

(O)

Take corrective action according to a previously output message.

If a message was not output previously, collect data and then contact the system administrator.

For details about the data to be collected, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KNAC1510-E

An error occurred in an event action control.:maintenance-information-1:maintenance-information-2

An error occurred in event action control.

(S)

Cancels processing.

(O)

Take corrective action according to a previously output message.

If a message was not output previously, collect data and then contact the system administrator.

For details about the data to be collected, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KNAC1511-E

An attempt to connect to the database failed.

An attempt to connect to the database failed.

(S)

Cancels the requested processing.

(O)

The embedded database might not be running or might be in the process of starting.

If this message is output when the ajsagtadd, ajsagtalt, or ajsagtdel command is executed, make sure that the embedded database is running, and then re-execute the command.

In any other case, restart JP1/AJS3.

KNAC1512-E

Database type is invalid.

The type of the database is not an embedded database.

(S)

Terminates processing.

(O)

The operation is not possible in the environment for the compatible ISAM configuration. Change the environment to the standard configuration, and then re-execute the command.

KNAC1513-E

An error occurred by the operation check in the event action control. :scheduler-service-name:maintenance-information

An error occurred during an operation check for event action control for an agent management command.

(S)

Terminates processing.

(O)

Take corrective action according to the KAVTxxxx message output previously, and then re-execute the command.

KNAC1514-E

An error occurred by the operation check in the job execution control. :scheduler-service-name:maintenance-information

An error occurred during an operation check for job execution control for an agent management command.

(S)

Terminates processing.

(O)

Take corrective action according to the KAVUxxxx message output previously, and then re-execute the command.

KNAC1515-E

An error occurred by the operation cancel report in the event action control.:scheduler-service-name:maintenance-information

An error occurred during a cancellation notification for event action control for an agent management command.

(S)

Terminates processing.

(O)

Take corrective action according to the KAVTxxxx message output previously, and then restart the scheduler service indicated by scheduler-service-name. If the scheduler-service-name is an asterisk (*), restart the JP1/AJS3 service. After either restart, re-execute the command.

KNAC1516-E

An error occurred by the operation cancel report in the job execution control.:scheduler-service-name:maintenance-information

An error occurred during cancellation notification for job execution control for an agent management command.

(S)

Terminates processing.

(O)

Take corrective action according to the KAVTxxxx message output previously, and then restart the scheduler service indicated by scheduler-service-name. After the restart, re-execute the command.

KNAC1517-E

An error occurred by the operation completion report in the event action control.:scheduler-service-name:maintenance-information

An error occurred during an execution completed notification for event action control for an agent management command.

(S)

Terminates processing.

(O)

Take corrective action according to the KAVTxxxx message output previously, and then restart the scheduler service indicated by scheduler-service-name. If the scheduler service name is an asterisk (*), restart the JP1/AJS3 service.

After the restart, use the ajsagtshow or ajsagtprint command to make sure that the intended result of the operation was reflected. If the intended result was not reflected, re-execute the command.

KNAC1518-E

An error occurred by the operation completion report in the job execution control.:scheduler-service-name:maintenance-information

An error occurred during an execution notification for job execution control for an agent management command.

(S)

Terminates processing.

(O)

Take corrective action according to the KAVUxxxx message output previously, and then restart the scheduler service indicated by scheduler-service-name.

After the restart, use the ajsagtshow or ajsagtprint command to make sure that the intended result of the operation was reflected. If the intended result was not reflected, re-execute the command.

KNAC1519-W

An attempt to connect to the database failed, and the agent manager function cannot use.

The agent manager function cannot be used because an attempt to connect to the database failed.

As a result, the following problems are possible.

The following jobs cannot be executed:

- PC job (other than queueless jobs)

- Unix job (other than queueless jobs)

- Event job

- Action job (other than queueless jobs)

- Custom job

- Passing information setting job

Either information about the execution agent and the execution agent group is not output as the execution result of the following commands, or the following commands terminate abnormally:

- ajsagtadd command

- ajsagtalt command

- ajsagtdel command

- ajsagtshow command

- ajsagtprint command

The following function cannot be used:

- Agent automatic definition function

(S)

Continues processing.

(O)

See the corrective action specified in the KNAC1508-E message.

KNAC1520-I

Reconnect to the database has finished (host-name).

Reconnection to the database finished.

(S)

Continues processing.

1.5 Messages beginning with KNAD (Messages that are output by the installer and system management)

This section lists messages that begin with KNAD (messages output by the installer and system management).

KNAD1000-E

The installation will stop because this product cannot be installed on the same system as a product that has already been installed on this system.

Installation was suspended because the product you are installing is incompatible with an existing product installed on the system. Product incompatibilities are as follows:

With JP1/AJS3 - Manager

JP1/AJS3 - Agent

JP1/AJS2 - Agent

JP1/AJS2 - Light Edition

With JP1/AJS3 - Agent

JP1/AJS3 - Manager

JP1/AJS2 - Manager

JP1/AJS2 - Light Edition

(S)

Suspends installation.

(O)

Take action as follows:

Installing JP1/AJS3 - Manager

Uninstall the existing JP1/AJS3 - Agent, JP1/AJS2 - Agent, or JP1/AJS2 - Light Edition, and then retry installing JP1/AJS3 - Manager.

Installing JP1/AJS3 - Agent

Uninstall the existing JP1/AJS3 - Manager, JP1/AJS2 - Manager, or JP1/AJS2 - Light Edition, and then retry installing JP1/AJS3 - Agent.

KNAD1001-E

The installation will stop because the installed JP1/AJS3 or JP1/AJS2 does not meet the requirements of the applicable OS.

Installation was suspended because an existing JP1/AJS3 or JP1/AJS2 product does not meet the applicable OS conditions.

You cannot perform an upgrade installation from a JP1/AJS3 or JP1/AJS2 product that does not meet the applicable OS conditions.

The probable causes are:

The JP1/AJS3 or JP1/AJS2 product was installed in a Windows Server 2003 environment that has been upgraded to Windows Server 2012 or Windows Server 2008.

A JP1/AJS3 product intended for Windows Server 2003 was mistakenly installed in a Windows Server 2012 or Windows Server 2008 environment.

(S)

Suspends installation.

(O)

Uninstall the JP1/AJS3 or JP1/AJS2 product that does not meet the applicable OS conditions, and then install the correct JP1/AJS3 or JP1/AJS2 product.

If you cannot uninstall the product, collect the following data and contact your system administrator:

Details about performed operations

Installation log (system-folder\Temp\HITACHI_JP1_INST_LOG folder)

Execution results of the data collection tool

KNAD1002-E

This platform is not supported. Installation stops.

Installation was suspended because you attempted to install a JP1/AJS3 product on a platform that does not meet the applicable OS conditions.

The JP1/AJS3 product you are attempting to install cannot be installed on this platform.

(S)

Suspends installation.

(O)

Check what OSs are supported, and install the JP1/AJS3 product on a supported OS. For details about supported OSs, see Release Notes.

KNAD1003-E

The user who executed the installation is not an administrator. An administrator is required to install JP1/AJS3.

The product could not be installed because the user who executed the installation does not have administrator permissions.

(S)

Suspends installation.

(O)

Install JP1/AJS3 products under a user account that has administrator permissions.

KNAD1004-E

JP1/Base is not installed. Install JP1/Base, and then install JP1/AJS3.

JP1/AJS3 could not be installed because JP1/Base is not installed.

(S)

Suspends installation.

(O)

Install JP1/Base and then install JP1/AJS.

KNAD1005-E

Uninstallation of JP1/AJS3 - Manager failed. Please retry the uninstallation.

Uninstallation was suspended because an error occurred.

The probable causes are:

There is insufficient free space on the drive on which the folder set in the system environment variable TEMP resides.

JP1/Base was uninstalled before JP1/AJS3 - Manager, or JP1/Base was uninstalled before JP1/AJS3 - Manager and then re-installed on its own.

(S)

Suspends installation.

(O)

See Release Notes and allocate sufficient free space for the temporary area required at installation. Then retry the uninstallation.

If you uninstalled JP1/Base before JP1/AJS3 - Manager, see Release Notes and take appropriate action.

If you cannot resolve the problem, collect the following data and then contact the system administrator:

Details about performed operations

A hard copy of the dialog box

Installation log (system-folder\Temp\HITACHI_JP1_INST_LOG folder)

Execution results of the data collection tool

KNAD1006-E

The installation will stop because the logical host of JP1/AJS3 is running. Stop the logical host, and then retry the installation.

The overwrite installation or upgrade installation was suspended because a JP1/AJS3 logical host is running.

(S)

Suspends installation.

(O)

Stop all JP1/AJS3 logical hosts and then retry the installation.

KNAD1007-E

A file required for installation of JP1/AJS3 is missing. The installation will stop. (maintenance-information)

Installation was suspended because the file indicated in maintenance-information required for installation could not be found. The probable causes are:

The Hitachi Integrated Installer disk is defective.

The version of the installed JP1/Base does not meet the JP1/AJS3 prerequisites.

(S)

Suspends installation.

(O)

Make sure that the version of the JP1/Base you are using meets the prerequisites for running JP1/AJS3 products. If you have another Hitachi Integrated Installer disk, retry the installation using that disk.

If you cannot resolve the problem, collect the following data and then contact the system administrator:

Details about performed operations

A hard copy of the dialog box

Installation log (system-folder\Temp\HITACHI_JP1_INST_LOG folder)

If you are performing an overwrite or upgrade installation, also collect the following:

Execution results of the data collection tool

KNAD1008-E

Error occurred at opening file. Installation stops. (maintenance-information)

Installation was suspended because the file indicated in maintenance-information needed at installation could not be opened. The probable causes are:

There is insufficient free space on the system drive.

You do not have write or read permission for the folder set in the system environment variable TEMP.

(S)

Suspends installation.

(O)

Remove the cause of the error, and then retry the installation.

If you cannot resolve the problem, collect the following data and then contact the system administrator:

Details about performed operations

A hard copy of the dialog box

A hard copy of the window that appears when you choose the Security tab in the Properties dialog box for the folder set in the system environment variable TEMP

Installation log (system-folder\Temp\HITACHI_JP1_INST_LOG folder)

If you are performing an overwrite or upgrade installation, also collect the following:

Execution results of the data collection tool

KNAD1009-E

Error occurred to access file. Installation stops. (maintenance-information)

Installation was suspended because the file indicated in maintenance-information needed at installation could not be accessed. The probable cause is:

You do not have write or read permission for the folder set in the system environment variable TEMP.

(S)

Suspends installation.

(O)

Remove the cause of the error, and then retry the installation.

If you cannot resolve the problem, collect the following data and then contact the system administrator:

Details about performed operations

A hard copy of the dialog box

A hard copy of the window that appears when you choose the Security tab in the Properties dialog box for the folder set in the system environment variable TEMP

Installation log (system-folder\Temp\HITACHI_JP1_INST_LOG folder)

If you are performing an overwrite or upgrade installation, also collect the following:

Execution results of the data collection tool

KNAD1010-E

Error occurred at reading file. Installation stops. (maintenance-information)

Installation was suspended because the file indicated in maintenance-information needed at installation could not be read. The probable cause is:

You do not have read permission for the folder set in the system environment variable TEMP.

(S)

Suspends installation.

(O)

Remove the cause of the error, and then retry the installation.

If you cannot resolve the problem, collect the following data and then contact the system administrator:

Details about performed operations

A hard copy of the dialog box

A hard copy of the window that appears when you choose the Security tab in the Properties dialog box for the folder set in the system environment variable TEMP

Installation log (system-folder\Temp\HITACHI_JP1_INST_LOG folder)

If you are performing an overwrite or upgrade installation, also collect the following:

Execution results of the data collection tool

KNAD1011-E

Error occurred at closing file. Installation stops. (maintenance-information)

Installation was suspended because the file indicated in maintenance-information needed at installation could not be closed. The probable cause is:

You do not have write or read permission for the folder set in the system environment variable TEMP.

(S)

Suspends installation.

(O)

Remove the cause of the error, and then retry the installation.

If you cannot resolve the problem, collect the following data and then contact the system administrator:

Details about performed operations

A hard copy of the dialog box

A hard copy of the window that appears when you choose the Security tab in the Properties dialog box for the folder set in the system environment variable TEMP

Installation log (system-folder\Temp\HITACHI_JP1_INST_LOG folder)

If you are performing an overwrite or upgrade installation, also collect the following:

Execution results of the data collection tool

KNAD1012-E

Possibility of operation failure. Please setup by Hitachi Integrated Installer.

Installation was suspended because you might be installing the product without using Hitachi Integrated Installer.

The probable causes are:

You executed a file directly from the Hitachi Integrated Installer disk.

You performed the installation with an OS user name set in multi-byte characters.

(S)

Suspends installation.

(O)

Retry the installation using the Hitachi Integrated Installer.

If you performed the installation with an OS user name set in multi-byte characters, retry with an OS user name that does not use multi-byte characters.

If you cannot resolve the problem, collect the following data and then contact the system administrator:

Details about performed operations

A hard copy of the dialog box

Installation log (system-folder\Temp\HITACHI_JP1_INST_LOG folder)

If you are performing an overwrite or upgrade installation, also collect the following:

Execution results of the data collection tool

KNAD1013-E

The Hitachi Integrated Installer disc might be corrupted. Installation cannot continue.

Installation was suspended because an error occurred.

The probable causes are:

The Hitachi Integrated Installer disk is defective.

Copying of the Hitachi Integrated Installer to the local disk failed.

(S)

Suspends installation.

(O)

If you have another Hitachi Integrated Installer disk, retry the installation using that disk.

If you tried to copy the Hitachi Integrated Installer to the local disk, retry the copy operation and then install JP1/AJS3. Alternatively, install JP1/AJS3 from the Hitachi Integrated Installer disk.

If you cannot resolve the problem, collect the following data and then contact the system administrator:

Details about performed operations

A hard copy of the dialog box

Installation log (system-folder\Temp\HITACHI_JP1_INST_LOG folder)

If you are performing an overwrite or upgrade installation, also collect the following:

Execution results of the data collection tool

KNAD1014-E

The installation will stop because setting of common definition information failed. Restart the system, and then retry the installation.

Installation was suspended because setting of the common definition information used by JP1/AJS3 products failed.

(S)

Suspends installation.

(O)

Restart the host on which you are installing JP1/AJS3 and then retry the installation.

If you cannot resolve the problem, collect the following data and then contact the system administrator:

Details about performed operations

A hard copy of the dialog box

Installation log (system-folder\Temp\HITACHI_JP1_INST_LOG folder)

KNAD1015-E

Setting of license management information failed. The installation will stop. (maintenance-information)

Installation was suspended because setting of license management information failed.

(S)

Suspends installation.

(O)

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

Details about performed operations

A hard copy of the dialog box

Installation log (system-folder\Temp\HITACHI_JP1_INST_LOG folder)

If you are performing an overwrite or upgrade installation, also collect the following:

Execution results of the data collection tool

KNAD1016-E

The installation will stop because the trial version of JP1/AJS3 is already installed.

Installation was suspended because you attempted an overwrite or upgrade installation of the full product on a host that has the trial version of JP1/AJS3 installed.

You cannot perform an overwrite or upgrade installation of a product version over a trial version.

(S)

Suspends installation.

(O)

Uninstall the trial version and then install the product version again.

KNAD1017-E

An error occurred during upgrade installation of JP1/AJS3 - View. Check whether JP1/AJS2 - View is running, stop it if it is running, and then retry the installation.

Installation was suspended because an error occurred during an upgrade installation from JP1/AJS2 - View to JP1/AJS3 - View.

(S)

Suspends installation.

(O)

Close all JP1/AJS2 - View windows and then perform the upgrade installation of JP1/AJS3 - View again.

KNAD1018-E

An error occurred during upgrade installation. Installation stops.

Installation was suspended because an error occurred during an upgrade installation from JP1/AJS2 - Manager to JP1/AJS3 - Manager in an environment that uses JP1/AJS2 - Database option.

(S)

Suspends installation.

(O)

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

Details about performed operations

A hard copy of the dialog box

Installation log (system-folder\Temp\HITACHI_JP1_INST_LOG folder)

Execution results of the data collection tool

KNAD1019-E

The installation will stop because the installed JP1/Base does not meet the requirements of the applicable OS.

Installation was suspended because the product code of the installed JP1/Base does not meet the prerequisites for running JP1/AJS3.

The probable cause is:

The Windows Server 2003 environment in which JP1/Base was installed has been upgraded to Windows Server 2012 or Windows Server 2008.

(S)

Suspends installation.

(O)

Uninstall the existing JP1/Base and install JP1/Base with the correct product code to meet JP1/AJS3 requirements. Then install the JP1/AJS3 product again. For the product code of the required JP1/Base, see Release Notes.

KNAD1020-E

The version of the installed JP1/Base is old. Please install after installing JP1/Base version-information or later.

Installation was suspended because the version of the installed JP1/Base does not meet the prerequisites for running JP1/AJS3.

(S)

Suspends installation.

(O)

Install the correct version of JP1/Base to meet JP1/AJS3 requirements, and then install the JP1/AJS3 product again. For the required JP1/Base version, see Release Notes.

KNAD1300-W

JP1/AJS3 - Manager and JP1/AJS3 Console cannot be installed in the same path. Specify the installation path again.

You cannot set the same path as the installation folder for JP1/AJS3 - Manager and JP1/AJS3 Console.

(S)

Open the dialog box for setting the installation folders again.

(O)

Set different paths as the installation folder for JP1/AJS3 - Manager and installation folder for JP1/AJS3 Console.

KNAD1301-W

The drive specified as the installation destination of JP1/AJS3 - Manager does not meet the minimum free space requirements. To install JP1/AJS3 - Manager, specify a drive that has at least required-size of free space.

The specified drive does not have the required free space to install JP1/AJS3 - Manager.

The JP1/AJS3 - Manager installation drive must have free space shown in required-size as a minimum.

(S)

Open the dialog box for setting the installation folder again.

(O)

Allocate at least the free space indicated in the message to the JP1/AJS3 - Manager installation drive.

Alternatively, install JP1/AJS3 - Manager on another drive that has at least the free space indicated in the message.

For the disk space required to install JP1/AJS3 - Manager, see Release Notes.

KNAD1302-W

Setting of the integrated trace log failed.

Setting of the integrated trace log failed when installing JP1/AJS3.

The probable cause is:

As the access permissions to the registry HKEY_LOCAL_MACHINE\SOFTWARE, Full Control is granted to the Everyone group only.

(S)

Continues installation.

(O)

Add the Administrators group to the access permissions to the registry HKEY_LOCAL_MACHINE\SOFTWARE, and grant Full Control to Administrators. Then retry the installation.

If you cannot resolve the problem, collect the following data and then contact the system administrator:

Details about performed operations

A hard copy of the dialog box

A hard copy of the window showing the access permissions to the registry HKEY_LOCAL_MACHINE\SOFTWARE

A hard copy of the window showing the access permissions to the registry HKEY_LOCAL_MACHINE\SOFTWARE\HITACHI\HNTRLIB2\HNTR1

Installation log (system-folder\Temp\HITACHI_JP1_INST_LOG folder)

Execution results of the data collection tool

KNAD1303-W

Unsetting of the integrated trace log failed.

Unsetting of the integrated trace log failed at uninstallation.

(S)

Continues uninstallation.

(O)

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

Details about performed operations

A hard copy of the dialog box

Installation log (system-folder\Temp\HITACHI_JP1_INST_LOG folder)

KNAD1304-W

Deletion of the integrated trace log failed.

Deletion of the integrated trace log failed at uninstallation.

(S)

Continues uninstallation.

(O)

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

Details about performed operations

A hard copy of the dialog box

Installation log (system-folder\Temp\HITACHI_JP1_INST_LOG folder)

KNAD1305-W

Setting of the TCP/IP port numbers to be used by JP1/AJS3 failed. It is necessary to set TCP/IP port numbers before using JP1/AJS3.

Setting of the port numbers to be used by JP1/AJS3 failed.

(S)

Continues installation.

(O)

When installation has finished, set the port numbers to be used by JP1/AJS3 in the services files, referring to A. List of Port Numbers in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

KNAD1306-W

An attempt to build a Scheduler service failed. After installation, please re-build the Scheduler service.

Configuration of the scheduler service failed.

The probable causes are:

Setup of the embedded database failed and message KAVS2128-E was output.

The Startup Type of the Application Experience service or Application Experience Lookup Service is set to Disabled.

(S)

Continues installation.

(O)

If setup of the embedded database failed and error message KAVS2128-E was output, see 2. Messages in the manual Job Management Partner 1/Automatic Job Management System 3 Messages 1 and take appropriate action.

If the Startup Type of the Application Experience service or Application Experience Lookup Service is set to Disabled, change the setting to Automatic or Manual, and then retry the installation.

KNAD1500-I

Restart the system before using JP1/AJS3.

This message tells you that you must restart the system to use the installed products.

(S)

Continues installation.

(O)

Restart the system after installation is completed.

KNAD1501-I

After installation, it is necessary to set up JP1/AJS3 before using it.

This message tells you that you must complete setup after installation to use the installed products.

(S)

Continues installation.

(O)

Complete the required setup after installation. For details, see 8.5 Setup after upgrading from JP1/AJS2 - Manager to JP1/AJS3 - Manager in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

KNAD1700-Q

Do you want to perform overwrite installation of JP1/AJS3?

Confirm whether to proceed with the overwrite or upgrade installation of the installed JP1/AJS3 or JP1/AJS2 product.

(S)

Waits for a response.

(O)

Click Yes to perform the overwrite or upgrade installation. If you do not want to proceed, click No and terminate the installation.

KNAD1701-Q

This platform is not an applicable OS. Do you want to stop the installation?

Confirm whether to cancel installation on a platform that does not meet the applicable OS conditions.

(S)

Waits for a response.

(O)

Click Yes and terminate the installation.

KNAD1702-Q

Upgrade installation from JP1/AJS2 - Manager to JP1/AJS3 - Manager will begin. Do you want to continue?

Confirm whether to proceed with the upgrade installation from JP1/AJS2 - Manager to JP1/AJS3 - Manager.

If you proceed, you will not be able to return to the JP1/AJS2 - Manager environment.

(S)

Waits for a response.

(O)

Click Yes to perform the upgrade installation. If you do not want to proceed, click No and terminate the installation.

KNAD1703-Q

The Hitachi Integrated Installer disc could not be found. Insert the disc into the drive.

The files on the Hitachi Integrated Installer disk could not be found. Confirm whether to proceed with the installation.

(S)

Waits for a response.

(O)

To perform the installation, insert the Hitachi Integrated Installer disk, and then click Yes. To cancel, click No and terminate the installation.

If you cannot resolve the problem after inserting the disk, collect the following data and then contact the system administrator:

Details about performed operations

A hard copy of the dialog box

Installation log (system-folder\Temp\HITACHI_JP1_INST_LOG folder)

If you are performing an overwrite or upgrade installation, also collect the following:

Execution results of the data collection tool

KNAD3501-E

An attempt to open the message file has failed.

An attempt to open the message file has failed.

(S)

Terminates system management.

(O)

For Windows

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

For UNIX

The probable causes are as follows. Check the environment settings:

The user does not have read permission for the files in /opt/jp1ajs2/lib/nls.

Grant read permission to the user.

The number of open files in the system has reached the limit.

Review the kernel parameters.

Temporary memory shortage

Retry, or end unnecessary processes and then retry.

The directory or file has been deleted.

Re-install the directory or file.

If you are unable to solve the problem, use the data collection tool to collect data, and then contact the system administrator.

KNAD3502-E

An attempt to read the message file has failed.

An attempt to read the message file has failed.

(S)

Does not output any messages.

(O)

Check whether JP1/AJS3 setup has terminated normally.

KNAD3503-E

An attempt to read the message file has failed.

An attempt to read the message file has failed.

(S)

Does not output any messages.

(O)

Make sure that the message file (jajsspm.cat) is located under the /opt/jp1ajs2/lib/nls directory, and make sure that the reference permissions are suitable.

KNAD3504-E

An error occurred in internal processing to output a message.

An error occurred during internal processing of message output.

(S)

Does not output any messages.

(O)

Check whether there is a system resource shortage.

KNAD3516-E

An attempt to start the system management has failed. (errno = request-code)

An attempt to start system management has failed.

(S)

Terminates system management.

(O)

Check whether the product has been correctly installed.

KNAD3552-E

JP1/AJS3 management-target-process-name has timed out.

Processing to start or stop the indicated process is taking too long. management-target-process-name is the name of a process configured from all components under the control of system management.

(S)

Continues processing.

KNAD3553-E

SIGKILL was sent to management-target-process-name of JP1/AJS3, but termination could not be detected.

SIGKILL was sent, but termination could not be detected. management-target-process-name is the name of a process configured from all components under the control of system management.

(S)

Terminates system management.

(O)

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

KNAD3564-I

jajs_xxxd: JP1/AJS3 will now start all inactive processes.

All stopped processes under management will be started. jajs_xxxd is one of the following:

jajs_spmd: System management

jajs_dbmd: DB service

jajs_hstd: Host service

jajs_agtd: Agent service

jajs_schd: Scheduler service

(S)

Continues processing.

KNAD3577-I

jajs_xxxd_stop: A stop request will now be sent to all processes of JP1/AJS3.

A stop request will be sent to all processes under management. jajs_xxxd is one of the following:

jajs_spmd: System management

jajs_dbmd: DB service

jajs_hstd: Host service

jajs_agtd: Agent service

jajs_schd: Scheduler service

(S)

Continues processing.

KNAD3578-I

JP1/AJS3 has ended.

System management has terminated.

(S)

Terminates system management.

KNAD3586-I

JP1/AJS3 has terminated.

System management has terminated.

(S)

Terminates system management.

KNAD3597-I

jajs_xxxd_stop -kill: A forced stop (kill) will be performed on all processes of JP1/AJS3.

All processes under management will be forcibly stopped. jajs_xxxd is one of the following:

jajs_spmd: System management

jajs_dbmd: DB service

jajs_hstd: Host service

jajs_agtd: Agent service

jajs_schd: Scheduler service

(S)

Continues processing.

KNAD3599-E

main_loop: An invalid request was received. (event ID = request-type)

An invalid request has been received.

(S)

Continues processing.

(O)

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

KNAD3602-I

JP1/AJS3 received a startup report from management-target-process-name.

A startup completed notification has been received. management-target-process-name is the name of a process configured from all components under the control of system management.

(S)

Continues processing.

KNAD3603-I

All processes of JP1/AJS3 are running.

All processes under management have been started.

(S)

Continues processing.

KNAD3604-I

JP1/AJS3 startup has finished.

Service startup has been completed.

(S)

Continues processing.

KNAD3605-I

JP1/AJS3 completed to send the start up request to the management-target-process-name.

Restart of a process under management that terminated abnormally has been completed. management-target-process-name is the name of a process configured from all components under the control of system management.

(S)

Continues processing.

KNAD3610-I

JP1/AJS3 received an termination notification from management-target-process-name.

A termination notification from a process under management has been received. management-target-process-name is the name of a process configured from all components under the control of system management.

(S)

Continues processing.

KNAD3612-I

A stop request will now be sent to all processes of JP1/AJS3.

A stop request will be sent to all processes under management.

(S)

Continues processing.

KNAD3613-W

A JP1/AJS3 timeout occurred in management-target-process-name. Processing continues.

A startup timeout has occurred for a process under management. management-target-process-name is the name of a process configured from all components under the control of system management.

(S)

Continues processing.

(O)

Wait a while. If startup of the managed process has not been completed or JP1/AJS3 does not start, use the jajs_spmd_stop -kill command to force termination, and then restart the service.

If this message is output after the process terminated abnormally, restart might have failed due to too short a retry interval for the managed process. See 7.3.1 Restarting an abnormally terminated JP1/AJS3 process in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide, and then adjust the retry interval.

KNAD3614-E

Process management will now stop because an invalid JP1/AJS3 status occurred.

System management will stop due to an invalid status.

(S)

Terminates system management.

(O)

Check whether the KAVS2128-E message was output to the Windows event log (in Windows) or syslog (in UNIX). If the KAVS2128-E message was output, setup of the scheduler service has failed, in which case take the corrective action suggested in the message. If this message was output after the setup of the scheduler service terminated normally, use the data collection tool to collect data, and then contact the system administrator.

KNAD3616-I

Restart of the JP1/AJS3 management-target-process-name has finished.

Restart of a process under management that terminated abnormally has been completed. management-target-process-name is the name of a process configured from all components under the control of system management.

(S)

Continues processing.

KNAD3617-I

The JP1/AJS3 management-target-process-name startup has finished.

Startup of a process under management in JP1/AJS3 has been completed.

The name of a process configured from all components under the control of system management is output for management-target-process-name.

(S)

Continues processing.

KNAD3620-E

The user does not have permission to execute the command executed-command-name.

A user that does not have administrator permissions attempted to execute the command.

In environments that allow AJS administrators to perform operations, the probable causes are:

A user who is not an AJS administrator or who does not have superuser privileges attempted to execute the command.

The execution permission environment is invalid.

One or more of: user name, user ID, group name, and group ID on the executing and standby hosts are inconsistent.

(S)

Does not execute the command.

(O)

A user that has administrator permissions must execute the command.

For environments that allow AJS administrators to perform operations, an AJS administrator or a user with superuser privileges must execute the command. Alternatively, set up the environment so that AJS administrators can perform operations, and then retry the operation.

KNAD3621-E

A fork system call failed during initialization: JP1/AJS3

A fork system call to be executed in the background failed when system management started.

(S)

Terminates system management.

(O)

Check whether there is a system memory shortage. Also check whether OS operation is normal.

KNAD3623-E

The setsid function failed. (error-details)

A setsid system call failed.

(S)

Terminates system management.

(O)

Check whether there is a system memory shortage. Also check whether OS operation is normal.

KNAD3624-E

An attempt to create a process management table has failed.

An attempt to create a process management table has failed.

(S)

Terminates the system management command.

(O)

Check whether there is a system memory shortage and whether the product has been installed correctly.

Check whether the settings in the extended startup process definition file (jp1ajs_xxxx_0700.conf) have been specified correctly. xxxx represents service, dbmd, hstd, agtd, or schd.

Make sure that all processes that were managed last time have terminated normally and none of the processes remain in the system.

If any managed processes remain, forcibly terminate all of them, and then restart the service.

Check whether the KAVS2128-E message was output to the Windows event log (in Windows) or syslog (in UNIX).

If the KAVS2128-E message was output, setup of the scheduler service has failed, in which case take the corrective action suggested in the message.

KNAD3625-E

An internal error occurred. Execution Command names differ. executed-command-name

executed-command-name does not match.

(S)

Terminates system management.

(O)

Check executed-command-name. If you change executed-command-name, system management becomes impossible.

In Windows, you cannot execute a command by using a short file name.

KNAD3626-E

An attempt to create a lock file has failed. lock-file-path-error-details

An attempt to create a lock file has failed.

For environments that allow AJS administrators to perform operations, a user who is not an AJS administrator or who does not have superuser privileges might have attempted to execute the command.

(S)

Terminates the system management command.

(O)

Check whether there is a conf directory and whether it has read and write permissions. For cluster operation, check whether a conf directory is defined and whether it has read and write permissions.

For environments that allow AJS administrators to perform operations, an AJS administrator or a user with superuser privileges must execute the command.

KNAD3627-I

JP1/AJS3 is already running.

The service to be started is already running.

(S)

Terminates the system management command.

KNAD3631-E

build_proc_table : The return value NULL was returned to the getfield function. preset-value

An entry in the extended startup process definition file (jp1xx_service_0700.conf) has not been set correctly. The jp1xx part of the file name is jp1ajs.

(S)

Terminates system management.

(O)

Make sure that the entry in the extended startup process definition file has been set correctly.

KNAD3638-E

process-name : Memory allocation failed : return-code

An attempt to allocate memory for the operation has failed.

(S)

Terminates system management.

(O)

Check whether there is a memory shortage.

KNAD3642-E

An internal error occurred. Component names differ. JP1/AJS3

Component names do not match.

(S)

Terminates system management.

(O)

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

KNAD3643-E

An attempt to open the environment definition file file-name has failed.

The environment definition file could not be opened.

(S)

Terminates system management.

(O)

Check whether the product has been installed correctly.

KNAD3644-E

An attempt to expand the environment variables has failed.

An attempt to read environment variables from jp1xx_env.conf has failed. The jp1xx part of the file name is jp1ajs.

(S)

Terminates system management.

(O)

Check whether there is a system memory shortage.

KNAD3645-I

The logical hostname for process management is logical-host-name.

System management by the logical host has started.

(S)

Continues processing.

KNAD3646-I

The option-name option is specified.

System management has started with an option.

(S)

Continues processing.

KNAD3647-E

The expiration of the time limit. JP1/AJS3

The time limit for the JP1/AJS3 test version has expired.

(S)

Cancels processing.

KNAD3649-E

The environment variable of JP1_HOSTNAME is empty.

The JP1_HOSTNAME environment variable setting is not correct.

(S)

Terminates the system management command.

(O)

Either set a correct logical host name in the JP1_HOSTNAME environment variable, or delete the JP1_HOSTNAME environment variable.

KNAD3650-I

JP1/AJS3 start up the management-target-process-name.

Startup processing of the process managed by system management is being performed. management-target-process-name is the name of the process configured from all the components under the control of system management.

(S)

System management starts for the management-target process.

KNAD3651-I

Startup processing for JP1/AJS3 has started.

System management is performing startup processing for a process under management.

(S)

System management starts the process under management.

KNAD3652-E

A timeout occurred during the wait for a response. (timeout period = timeout-in-seconds seconds)

A timeout occurred during the wait for a response.

(S)

Terminates the system management command.

(O)

Change the timeout value, and then retry the operation.

KNAD3653-E

An attempt to send a request to the process management has failed.

Communication with system management from the system management command has failed.

(S)

Terminates the system management command.

(O)

The process might be terminating. Wait a while, and then re-execute the command. In UNIX, make sure that the /var/opt/jp1ajs2/tmp directory exists.

KNAD3654-E

An attempt to receive a response from the process management has failed.

The system management command was unable to receive data from system management.

(S)

Terminates the system management command.

(O)

Restart system management, and then retry the operation.

KNAD3655-E

Invalid data was received from the process management.

The system management command has received invalid data from system management.

(S)

Terminates the system management command.

(O)

Temporary reception of invalid data might have occurred. Use the jajs_spmd_status command to check the command status, and then re-execute the command that caused the error.

KNAD3656-I

The startup command terminated normally.

The command that starts system management has terminated normally.

(S)

Terminates the system management command.

KNAD3657-E

The startup command terminated abnormally

The startup command has terminated abnormally.

(S)

Terminates the system management command.

(O)

Use the jajs_spmd_status command to check the command status, and then retry the operation.

KNAD3658-E

The startup command terminated abnormally due to an inconsistent state.

This message is output when a command is executed while system management is performing other processing.

(S)

Terminates the system management command.

(O)

After waiting a while, use jajs_spmd_status command to check the status, and then retry the operation.

KNAD3659-I

There were no processes that could run.

There is no process that can be started.

(S)

Terminates the system management command.

KNAD3660-E

Invalid data was received. : maintenance-information

The system management command has received invalid data from system management.

(S)

Terminates the system management command.

(O)

Temporary reception of invalid data might have occurred. Use the jajs_spmd_status command to check the command status, and then re-execute the command that caused the error.

KNAD3661-E

An unexpected result code was received. (return code = return-code)

The system management command has received an invalid result code from system management.

(S)

Terminates the system management command.

(O)

Use jajs_spmd_status command to check the status, and then retry the operation.

KNAD3662-I

The process management is not running.

System management is not running.

(S)

Terminates the system management command.

KNAD3663-E

Execute the command from the administrator console.

This command must be executed from the command prompt window opened by a user with administrator permissions or from the JP1/Base administrator console.

(S)

Terminates the command processing.

(O)

Re-execute the command for the command prompt window opened by a user with administrator permissions or from the JP1/Base administrator console.

KNAD3669-E

Specified Scheduler service does not exist.

The specified scheduler service was not found.

(S)

Terminates the system management command.

(O)

Correctly specify the scheduler service to be used for the processing, and then re-execute the command.

KNAD3670-I

JP1/AJS3 start the schedule stop.

Planned termination processing for the process managed by system management has started.

This message is output when JP1/Power Monitor is linked.

(S)

Terminates the system management command.

KNAD3671-I

JP1/AJS3 start the jobnet restriction stop.

Restricted termination processing of jobnets for the process managed by system management has started.

This message is output when JP1/Power Monitor is linked.

(S)

Terminates the system management command.

KNAD3672-I

A forced termination (kill) of JP1/AJS3 has started.

Processing to force termination of system management has started.

(S)

Terminates the system management command.

KNAD3673-I

JP1/AJS3 start the cancel of stop request.

Processing to cancel the termination of the process managed by system management has started.

This message is output when JP1/Power Monitor is linked.

(S)

Terminates the system management command.

KNAD3674-I

Termination processing of JP1/AJS3 has started.

Termination processing for system management has started.

(S)

Terminates the system management command.

KNAD3675-I

The stop command terminated normally.

The command that terminates system management has terminated normally.

(S)

Terminates the system management command.

KNAD3676-E

The stop command terminated abnormally.

The termination command has terminated abnormally.

(S)

Terminates the system management command.

(O)

After waiting a while, use the jajs_spmd_status command to check the status, and then retry the operation.

KNAD3677-E

The stop command terminated abnormally due to an inconsistent state.

A command was executed while system management was performing other processing.

(S)

Terminates the system management command.

(O)

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

KNAD3678-I

There were no processes that could terminate.

No processes that can be stopped were found.

(S)

Terminates the system management command.

KNAD3686-E

Shared memory is not available. return code = return-code

An attempt to secure shared memory has failed.

(S)

Terminates the system management command.

(O)

Probable causes are listed below. Check the environment.

Check the integrated trace log. If an error message related to an environment setting parameter has been output, review the environment setting parameter, and then retry the operation.

In UNIX, review the shared memory size and the kernel parameter settings. For estimates, see the Release Notes.

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

KNAD3687-E

Specified data format is not acceptable for the environment variable. : value

There is a problem with the specification of the environment variable.

(S)

Terminates the system management command.

(O)

Specify the environment setting correctly, and then re-execute the command. For details about environment variables, see 1.4 Environment variables in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

KNAD3690-I

Processing to report the status of JP1/AJS3 has started.

Processing that reports the status of system management has started.

(S)

Terminates the system management command.

KNAD3691-I

All the processes have started.

All processes under management have started.

(S)

Terminates the system management command.

KNAD3692-I

Some of the processes have started.

Some of the processes under management have started.

(S)

Terminates the system management command.

KNAD3693-I

All of the processes have stopped.

All processes under management have stopped.

(S)

Terminates the system management command.

KNAD3694-I

Part of the process is now restarting.

System management has partially restarted.

(S)

Terminates the command reporting the system management status.

KNAD3695-E

Invalid value for option (option-name).

There is a problem with the option value.

(S)

Terminates the system management command.

(O)

Specify the option value correctly, and then re-execute the command.

KNAD3699-E

Shared memory for the operation profile is not available. (maintenance-information)

The operation profile functionality is disabled because shared memory for the operation profile could not be created.

(S)

Continues processing.

(O)

Check the environment settings and take the following action:

Check whether an error message about the operation profile has been output to the integrated trace log. If so, review the operation profile and then retry.

In UNIX, review the shared memory size and the kernel parameter settings. For estimates, see the Release Notes.

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

KNAD3705-I

management-target-process-name is now starting. (process ID = process-ID)

A process under management will start. management-target-process-name is the name of a process configured from all components under the control of system management. process-ID is the process ID of the process that has started.

(S)

Continues processing.

KNAD3732-I

JP1/AJS3 detected the termination of management-target-process-name. (process ID = process-ID)

Stopping of a process under management has been detected. management-target-process-name is the name of a process configured from all components under the control of system management. process-ID is the process ID of a running process.

(S)

Continues processing.

KNAD3736-I

All processes of JP1/AJS3 have stopped.

All processes under management have stopped.

(S)

Terminates system management.

KNAD3737-E

The JP1/AJS3 management-target-process-name terminated abnormally.

Abnormal termination of a process under management has been detected. management-target-process-name is the name of a process configured from all components under the control of system management.

(S)

Continues processing.

(O)

Check the integrated trace log for data output for the process under management that terminated abnormally, and remove the cause of the problem. Next, use the jajs_spmd_status command to check the command status, and then restart the operation.

If the process under management has not output a message, use the data collection tool to collect data, and then contact the system administrator.

If management-target-process-name is evactiona, and if no error message that begins with KAVT is output between the previous KNAD3705-I message and this message, check whether an invalid character is specified for the WaitInfFileOutDir environment setting parameter for event/action control. For details about the WaitInfFileOutDir environment setting parameter, see 2.4 Setting up the event/action control environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

Note also that output of this error message might depend on whether "1 (Restart)" is specified for the restart option in the extended startup process definition file. For details about causes and actions, see 7.3.1 Restarting an abnormally terminated JP1/AJS3 process in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

If ajsdbmgrd is indicated in management-target-process-name and the ajsdbmgrd process previously output the message KAVS0903-E, a desktop heap shortage might have occurred. See 4.2.3 Changing the JP1/AJS3 service settings (Windows only) in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide and, if necessary, change the account of the JP1/AJS3 service. You also need to check the number of concurrent jobs and startup processes for the entire system to prevent errors from occurring due to the desktop heap being too small.

KNAD3743-I

JP1/AJS3 has terminated.

System management has terminated.

(S)

Terminates system management.

KNAD3744-I

JP1/AJS3 startup has finished.

Service startup has been completed.

(S)

Continues processing.

KNAD3745-I

The JP1/AJS3 startup request has finished.

A startup request has been completed.

(S)

Continues processing.

KNAD3746-I

The JP1/AJS3 management-target-process-name terminated.

A process under JP1/AJS3 management has terminated.

The name of a process configured from all components under the control of system management is output for management-target-process-name.

(S)

Continues processing.

KNAD3751-E

The process stopped in response to the signal. pid = process-ID. signal = signal-number.

A process under management has stopped in response to a signal. process-ID is the process ID of a running process under management. signal-number is the signal number that caused the stoppage.

(S)

Continues processing.

(O)

Check the integrated trace log for data output for the process under management that terminated abnormally, and remove the cause of the problem. Next, use the jajs_spmd_status command to check the command status, and then restart the operation.

If the process under management has not output a message, use the data collection tool to collect data, and then contact the system administrator.

KNAD3752-E

An attempt to start management-target-process-name has finished. (return code = return-code, detail code = reason-code)

An attempt to start a process under management has failed. management-target-process-name is the name of a process configured from all components under the control of system management.

(S)

Continues processing.

(O)

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

KNAD3753-E

An attempt to stop management-target-process-name has finished. (return code = return-code detail code = reason-code)

An attempt to stop a process under management has failed. management-target-process-name is the name of a process configured from all components under the control of system management.

(S)

Continues processing.

(O)

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

KNAD3757-E

An attempt to read the product information failed. (Detailed information: detailed-information)

An attempt to read the product information has failed.

(S)

Cancels processing.

(O)

If the system time has been set to a value earlier than the installation time, restore the time, and then retry the operation.

For any other case, perform an overwrite installation, and then retry the operation.

If this message was output after an overwrite installation, uninstall the product, and then retry the operation.

KNAD3759-E

A function-name system call failed. return-code

A function-name system call has failed.

(S)

Terminates system management.

(O)

Check whether there is a system memory shortage. Also check whether OS operation is normal.

KNAD3760-I

The changes to file-name were not applied.

The changes to the settings in the extended startup process definition file (jp1ajs_xxxx_0700.conf) have not been applied. xxxx represents service, dbmd, hstd, agtd, or schd.

(S)

Continues processing.

(O)

Change the settings, and then retry the operation.

KNAD3761-E

In the file file-name, the restart-or-not value is invalid. ( restart-or-not = preset-value)

The value specified for the restart option in the extended startup process definition file (jp1ajs_xxxx_0700.conf) is invalid. xxxx represents service, dbmd, hstd, agtd, or schd.

(S)

Continues processing.

(O)

Change the set value, and then retry the operation.

KNAD3762-I

Set 0 or 1 for the restart-or-not value.

The value specified for the restart option in the extended startup process definition file (jp1ajs_xxxx_0700.conf) must be set to 0 or 1. xxxx represents service, dbmd, hstd, agtd, or schd.

(S)

Continues processing.

(O)

Set the value of the restart option to 0 or 1.

KNAD3763-E

In the file file-name, the number-of-restarts value is invalid. (restart num. = preset-value)

The value specified for number of restarts in the extended startup process definition file (jp1ajs_xxxx_0700.conf) is invalid. xxxx represents service, dbmd, hstd, agtd, or schd.

(S)

Continues processing.

(O)

Change the set value, and then retry the operation.

KNAD3764-I

Set 0 to 99 for the number-of-restarts value.

The value specified for number of restarts in the extended startup process definition file (jp1ajs_xxxx_0700.conf) must be a value from 0 to 99. xxxx represents service, dbmd, hstd, agtd, or schd.

(S)

Continues processing.

(O)

Set the value for number of restarts to a value from 0 to 99.

KNAD3765-E

In the file file-name, the restart interval value is invalid. (restart interval = preset-value)

The value specified for the retry interval in the extended startup process definition file (jp1ajs_xxxx_0700.conf) is invalid. xxxx represents service, dbmd, hstd, agtd, or schd.

(S)

Continues processing.

(O)

Change the set value, and then retry the operation.

KNAD3766-I

Set 0 to 3600 for the restart interval value.

The value specified for the retry interval in the extended startup process definition file (jp1ajs_xxxx_0700.conf) must be a value from 0 to 3,600. xxxx represents service, dbmd, hstd, agtd, or schd.

(S)

Continues processing.

(O)

Set the value of the retry interval to a value from 0 to 3,600.

KNAD3767-E

In the file file-name, the restart-count reset time is invalid. (restart-count reset time = preset-value)

The value specified for the reset time for the number of restarts in the extended startup process definition file (jp1ajs_xxxx_0700.conf) is invalid. xxxx represents service, dbmd, hstd, agtd, or schd.

(S)

Continues processing.

(O)

Change the set value, and then retry the operation.

KNAD3768-I

Set 3600 to 2147483647 for the restart-count reset time.

The value specified for the reset time for the number of restarts in the extended startup process definition file (jp1ajs_xxxx_0700.conf) must be a value from 3,600 to 2,147,483,647. xxxx represents service, dbmd, hstd, agtd, or schd.

(S)

Continues processing.

(O)

Set the value for the reset time for the number of restarts to a value from 3,600 to 2,147,483,647.

KNAD3769-I

In file-name, check the entries: process-name|path|startup-option|restart-or-not|number-of-restarts|restart-interval|restart-count-reset-time|kind|scheduler-flag|start-order|auto-start|stop-path|stop-option|check-status-path|check-status-option|check-status-end|check-status-interval|

Verify the entries in the extended startup process definition file (jp1ajs_xxxx_0700.conf). xxxx represents service, dbmd, hstd, agtd, or schd.

(S)

Continues processing.

(O)

Verify the entries in the extended startup process definition file.

If jp1ajs_xxxx.conf has already been customized to enable the linkage function, make sure that the process that is an entry in jp1ajs_xxxx.conf is also an entry in the extended startup process definition file (jp1ajs_xxxx_0700.conf).

If the entry is missing, view the model file (model appears at the end of the file name) and copy the entry for the corresponding process into the extended startup process definition file.

KNAD3777-I

JP1/AJS3: The stopped management-target-process-name will be restarted. (restart count = restart-count)

The process under management that has stopped will be restarted. management-target-process-name is the name of a process configured from all components under the control of system management.

(S)

Restarts the process under management.

KNAD3778-I

JP1/AJS3: A startup request was sent to the process management-target-process-name.

A startup request has been sent to a process under management. management-target-process-name is the name of a process configured from all components under the control of system management.

(S)

Continues processing.

KNAD3779-I

JP1/AJS3: An attempt to send a startup request to the process management-target-process-name failed.

An attempt to send a request to start a process under management has failed. management-target-process-name is the name of a process configured from all components under the control of system management.

(S)

Continues processing.

KNAD3786-E

To process child-process-ID-of-management-target-process, the system sent the signal signal.

A signal has been sent to a child process of a process under management. child-process-ID-of-management-target-process is the process ID of the process created by the running process under management.

(S)

Continues processing.

KNAD3788-E

JP1/AJS3: The number of restarts of management-target-process-name exceeded the specified restart count.

The number of restarts for the process under management has exceeded the setting. management-target-process-name is the name of a process configured from all components under the control of system management.

(S)

Continues processing.

(O)

Check the integrated trace log for data output for the process under management that terminated abnormally, and remove the cause of the problem. Next, use the jajs_spmd_status command to check the command status, and then restart JP1/AJS3.

If this message is still output after the cause of the problem has been removed, a restart might have failed due to too short a retry interval for the managed process. See 7.3.1 Restarting an abnormally terminated JP1/AJS3 process in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide, and then adjust the retry interval. If the managed process has not output a message or if there is no problem with the retry interval, use the data collection tool to collect data, and then contact the system administrator.

KNAD3792-E

JP1/AJS3 jajs_xxxd: A start parameter is invalid: Usage

A startup parameter is invalid.

jajs_xxxd is one of the following:

jajs_spmd: System management

jajs_hstd: Host service

(S)

Terminates system management.

(O)

Check the startup parameter, and then retry the operation.

KNAD3855-I

The process management-target-process-name will be terminated by SIGKILL. (process ID = process-ID)

SIGKILL has been sent to a process under management. management-target-process-name is the name of a process configured from all components under the control of system management. process-ID is the process ID of a running process under management.

(S)

Continues processing.

KNAD3862-E

JP1/AJS3: No processes could be started.

No processes under management could be started.

(S)

Terminates system management.

(O)

Check whether there is a system memory shortage and whether the product has been installed correctly.

KNAD3870-E

The conf directory path cannot be obtained from the common definition.

An attempt to obtain the conf directory path from the common definition has failed.

(S)

Terminates the system management command.

(O)

This situation occurs because the common definition information has not been set yet. Check whether the settings are correct.

For cluster operation

Check whether the logical host name specified in the argument of the system management command is correct. Also check whether the logical host name specified in the JP1_HOSTNAME environment variable is correct. Also, setup for cluster operation as described in either of the following manuals is required: Job Management Partner 1/Base User's Guide or Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1. Make sure that one or the other has been performed.

Operation other than cluster operation

Check whether the JP1_HOSTNAME environment variable was set at system startup. You cannot start the physical host if JP1_HOSTNAME environment variable has been set. If JP1_HOSTNAME environment variable has not been set but this message still appears, uninstall JP1/AJS3 and then re-install it.

KNAD3871-E

The conf directory path cannot be obtained by using the specified logical hostname.

An attempt to obtain the conf directory path from the common definition under the specified logical host name has failed.

(S)

Terminates the system management command.

(O)

The prerequisite is cluster operation. Make sure that the specified logical host name is correct or that setup has terminated normally.

KNAD3872-E

The log directory path cannot be obtained from the common definition information.

An attempt to obtain the log directory path from the common definition has failed.

(S)

Terminates the system management command.

(O)

For cluster operation, make sure that the logical host name setting is correct or that setup has terminated normally. For operation other than cluster operation, perform the following recovery operation.

For UNIX

Execute the setup command.

For Windows

Perform a rectification installation.

KNAD3873-E

The log directory path cannot be obtained by using the specified logical hostname.

An attempt to obtain the log directory path from the common definition under the specified logical host name has failed.

(S)

Terminates the system management command.

(O)

The prerequisite is cluster operation. Make sure that the specified logical host name is correct or that setup has terminated normally.

KNAD3874-E

HNTRLib could not be initialized.

HNTRLib2 could not be initialized. No logs will be output.

(S)

Continues processing.

(O)

If system management is running, stop it and then restart it.

KNAD3875-E

HNTRLib could not be initialized.

HNTRLib2 could not be initialized. No logs will be output.

(S)

Continues processing.

(O)

If system management is running, stop it and then restart it.

KNAD3876-E

In the file file-name, In the file %s, the kind value is invalid. (kind = preset-value)

The value specified for kind in the extended startup process definition file (jp1ajs_xxxx_0700.conf) is invalid. xxxx represents service, dbmd, hstd, agtd, or schd.

(S)

Continues processing.

(O)

Change the set value, and then retry the operation.

KNAD3877-I

Set 0 - 2 for the kind value.

The value specified for kind in the extended startup process definition file (jp1ajs_xxxx_0700.conf) must be 0, 1, or 2. xxxx represents service, dbmd, hstd, agtd, or schd.

(S)

Continues processing.

(O)

Set the value for kind to 0, 1, or 2.

KNAD3878-E

In the file file-name, In the file %s, the scheduler-flag value is invalid. (scheduler-flag = preset-value)

The value specified for the scheduler flag in the extended startup process definition file (jp1xx_service_0700.conf) is invalid. The jp1xx part of the file name is jp1ajs.

(S)

Continues processing.

(O)

Change the set value, and then retry the operation.

KNAD3879-I

Set 0 - 2 for the scheduler-flag value.

The value specified for the scheduler flag in the extended startup process definition file (jp1xx_service_0700.conf) must be 0, 1, or 2. The jp1xx part of the file name is jp1ajs.

(S)

Continues processing.

(O)

Set the value for the scheduler flag to 0, 1, or 2.

KNAD3880-E

In the file file-name, In the file %s, the scheduler-flag value is invalid. (scheduler-flag = preset-value)

The value specified for the scheduler flag in the extended startup process definition file (jp1ajs_xxxx_0700.conf) is invalid. xxxx represents service, dbmd, hstd, agtd, or schd.

(S)

Continues processing.

(O)

Change the set value, and then retry the operation.

KNAD3899-E

The work directory path cannot be acquired from the common definition information. (return code = return-code)

An attempt to acquire the work directory path from the common definition has failed.

(S)

Terminates the system management command.

(O)

For cluster operation, make sure that the logical host name setting is correct or that setup has terminated normally. For operation other than cluster operation, perform the following recovery operation.

For Windows

Perform a rectification installation.

For UNIX

Execute the setup command.

KNAD3905-I

A stop request was sent to the process management-target-process-name. (process ID = process-ID)

A stop request has been sent to a process under management. management-target-process-name is the name of a process configured from all components under the control of system management. process-ID is the process ID of a running process under management.

(S)

Continues processing.

KNAD3910-I

SIGTERM will terminate the process management-target-process-name. (process ID = process-ID)

SIGTERM has been sent to a process under management. management-target-process-name is the name of a process configured from all components under the control of system management. process-ID is the process ID of a running process under management.

(S)

Continues processing.

KNAD3911-E

The process management daemon is busy.

The command is being processed.

(S)

Terminates the system management command.

(O)

Wait a while, and then re-execute the operation. If, during the startup, or stop processing, output has occurred after execution of the jajs_spmd, or jajs_spmd_stop command, wait until the processing has finished, and then retry the operation.

KNAD3912-I

The process is running.

(S)

Terminates the system management command.

KNAD3913-I

The process is not running.

(S)

Terminates the system management command.

KNAD3914-E

An attempt to open the lock file under the conf directory has failed.

An attempt to open the lock file in the conf directory has failed.

(S)

Terminates the system management command.

(O)

Check whether there is a conf directory and whether it has write permission.

For cluster operation, check whether there is a defined conf directory and whether it has write permission.

KNAD3935-E

create_pre_process_entry: Memory allocation failed. (request-code)

An attempt to create a startup preprocessing management table has failed. Startup preprocessing has not been performed.

(S)

Continues processing.

(O)

Check whether there is a memory shortage.

KNAD3953-E

Startup preprocessing for JP1/AJS3 has failed. (preprocessing name = startup-preprocessing-name)

Startup preprocessing has failed.

(S)

Continues processing.

(O)

Check the contents of the JP1/AJS3 advanced startup process definition file (jp1ajs_spmd_pre.conf).

KNAD3960-I

Startup preprocessing is being performed.

Startup preprocessing for system management is in progress.

(S)

Terminates the command that reports the system management status.

KNAD3961-E

The request could not be accepted because startup preprocessing is being performed.

System management could not accept a command request because startup preprocessing was being performed.

(S)

Terminates the system management command.

(O)

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

KNAD3970-E

The JP1/AJS3 cannot start because the JP1/AJS3 is running in the system block.

JP1/AJS3 could not be started because the system is blocked.

(S)

Terminates the system management command.

(O)

Wait for JP1/AJS3 setup to be completed, and then restart the operation.

KNAD3971-E

The JP1/AJS3 cannot start because status unknown. Termination code = return-code

JP1/AJS3 could not be started because the system status could not be acquired.

(S)

Terminates the system management command.

(O)

Check whether JP1/AJS3 has been correctly installed, wait for setup to be completed, and then retry the operation.

KNAD3972-E

The JP1/AJS3 cannot start individually because the JP1/AJS3 is not running.

If JP1/AJS3 has stopped, separate startups are not possible.

(S)

Terminates the system management command.

(O)

Start JP1/AJS3, and then retry the operation.

KNAD3973-E

The JP1/AJS3 cannot start by command.

If JP1/AJS3 has stopped, separate startups are not possible.

(S)

Terminates the system management command.

(O)

JP1/AJS3 must be executed from the service side.

KNAD3974-E

JP1/AJS3 cannot start because the JP1/AJS3 construction is invalid.

JP1/AJS3 cannot start because the system configuration is invalid.

(S)

Terminates the system management command.

(O)

Make sure the scheduler service has the correct database type. If you have defined more than one scheduler service in the host, check whether they are different database types. If the scheduler services are currently being set up, wait until setup has completed for all scheduler services in the host and then re-execute the command.

KNAD3975-E

JP1/AJS3 cannot start because the construction is unknown. Termination code = termination-code

JP1/AJS3 cannot start because the system configuration could not be acquired.

(S)

Terminates the system management command.

(O)

Make sure that JP1/AJS3 is correctly installed, wait for setup to complete and then re-execute the command.

KNAD3976-W

process-name start in the disaster recovery start mode.

Operation was switched to the remote site while the disk copy and mirroring features of the hardware were in use. JP1/AJS3 will restart the process indicated in process-name in disaster recovery mode.

(S)

Starts the process indicated in process-name in disaster recovery mode.

(O)

Complete the procedure to resume operation at the remote site. For details, see 12.2.1 Switching operation to the remote site in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

KNAD3977-E

JP1/AJS3 cannot start in the remote site.

JP1/AJS3 services will not run at the remote site while the disk copy and mirroring features of the hardware are in use.

(S)

Terminates system management.

(O)

Complete the procedure to switch operation and start JP1/AJS3 services at the remote site. For details, see 12.2.1 Switching operation to the remote site in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

KNAD3978-E

JP1/AJS3 cannot start in the disaster recovery start mode using a compatible ISAM configuration.

Disaster recovery mode cannot be used in a compatible ISAM configuration.

(S)

Terminates system management.

(O)

Restart with a different option specification.

KNAD3979-E

Failed to disable the auto disaster recovery start feature.(maintenance-information)

The functionality for automatically releasing disaster recovery mode after switching sites failed.

(S)

Continues processing.

(O)

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

KNAD3981-I

jajs_xxxd_stop -job: A request to stop job restrictions will be sent to all processes of JP1/AJS3.

A request to stop job restrictions was sent to all processes under management.

jajs_xxxd is one of the following:

jajs_spmd: System management

jajs_dbmd: DB service

jajs_hstd: Host service

jajs_agtd: Agent service

jajs_schd: Scheduler service

(S)

Continues processing.

KNAD3984-I

A request to stop job restrictions has been sent to the process management-target-process-name. (process ID = process-ID)

management-target-process-name is the name of a process configured from all components under the control of system management. process-ID is the process ID of a running process under management.

(S)

Continues processing.

KNAD3985-I

JP1/AJS3 start the job restriction stop of management-target-process-name.

Processing to stop job restrictions for the process managed by system management has started. management-target-process-name is the name of the process configured from all the components under the control of system management.

(S)

Terminates the system management command.

KNAD3986-I

Processing to stop JP1/AJS3 job restrictions has started.

Processing to stop job restrictions in system management has started.

(S)

Terminates the system management command.

KNAD3991-E

Failed to open a system file. (maintenance-information)

A system management file failed to open.

(S)

Terminates system management.

(O)

The probable causes are as follows. Check the environment settings.

Temporary memory shortage

Retry, or end unnecessary processes and then retry.

The number of open files in the system has reached the limit.

Review the kernel parameters.

The contents of directories or files necessary for the system are deleted, or access permissions for the directories or files are changed.

If you operate JP1/AJS3 in disaster recovery mode, execute the jajs_rpsite command with the -v or -V option specified to check whether the disaster recovery environment is correct.

For details about the jajs_rpsite command, see jajs_rpsite in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

If you do not operate JP1/AJS3 in disaster recovery mode, re-install JP1/AJS3. If you cannot resolve the problem, use the data collection tool to collect data, and then contact the system administrator.

KNAD3992-E

The JP1/AJS3 cannot start because the IPv4 environment does not exist in the system. maintenance-information

JP1/AJS3 could not start because there is no IPv4 environment in the system or an attempt to acquire information failed.

(S)

Terminates the system management command.

(O)

Set up an IPv4 environment in the system, and then start JP1/AJS3.

KNAD3993-E

Failed to set the execute permissions environment. maintenance-information

An attempt to set up an execution permission environment failed.

(S)

Terminates the system management command.

(O)

Make sure that the environment is set up correctly to allow AJS administrators to perform operations. After ensuring that setup is correct, retry the operation.

KNAD3994-E

An attempt to read the main site definition failed.reason-code maintenance-information

An attempt to read the main site definition failed. Details of the error are indicated by one of the following reason codes:

CNFERR

An error occurred while common definition information was being accessed.

SYSERR

A conflict occurred in the internal logic of JP1/AJS3.

(S)

Terminates system management.

(O)

Take action according to the reason code of the message.

CNFERR

Check and, if necessary, correct problems such as a disk error.

If an error still occurs after you take corrective action, use the data collection tool to collect data, and then contact the system administrator.

SYSERR

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

Appendixes

A. Reason Codes and System Error Numbers of Messages Beginning with KAVU

This appendix describes the reason codes of messages beginning with KAVU and the system error numbers of messages KAVU2xxx-E and KAVU2xxx-W.

A.1 Reason Codes of Messages Beginning with KAVU

The table below lists the reason codes of messages beginning with KAVU (messages about the job execution control).

Table A‒1: Reason codes of messages beginning with KAVU

Reason code (hexadecimal)

Description

0x00010001

The monitoring process for job execution control has started twice.

0x00010006

The monitoring process for job execution control could not acquire the environment setting parameter.

0x00010007

The manager process for job execution control could not be started.

0x00010008

The agent process for job execution control could not be started.

0x0001000b

The monitoring process for job execution control could not create a pipe.

0xa0080002

The manager process for job execution control has started twice.

0xa0080011

Memory became insufficient in the manager process for job execution control.

0xe0090001

Memory became insufficient in the manager process for job execution control.

0xe0090008

The user has no operator permission.

0xa00a0005

The specified job is missing.

0xe0021101

Memory became insufficient during TCP/IP communication for job execution control.

0xe002110d

The temporary file used for job execution control did not exist.

0xe002110e

You did not have access permission for the temporary file used for job execution control.

0xe002110f

The amount of free space on the disk was insufficient when the temporary file used for job execution control was being created.

0xe0021110

The temporary file used for job execution control was locked and opened.

0xe0021120

An attempt to acquire the logical host name or IP address has failed.

0xe0021127

Reception failed due to a timeout during TCP/IP communication of job execution control.

0xe00a0002

Memory became insufficient in the manager process for job execution control.

0xe00a0003

The amount of free space in the disk became insufficient in the manager process for job execution control.

0xe00a0007

Connection could not be made in the manager process for job execution control.

0xe00a0008

The specified destination host is invalid.

0xe00b0003

There is no path for storing the database for job execution control.

0xe00b0004

The specified database table is missing.

0xe00b0008

The database table for job execution control could not be locked.

0xe00b0009

You have no permission to connect to the database table.

0xe00b000a

You have no access permission for the database table.

0xe00b000f

The semaphore's value became insufficient in the database process for job execution control.

0xe00b0010

A disk error occurred in the database process for job execution control.

0xe00b0011

The number of files to be opened was not enough in the database process for job execution control.

0xe00b0016

The user name or password is invalid.

0xe00b0017

The number of connections with the database exceeded the limit of the server.

0xe00b0018

The database is not running.

0x20100002

The agent process for job execution control has started twice.

0x20100004

Memory became insufficient in the agent process for job execution control.

0xe0800002

Memory became insufficient in the status notification process for job execution control.

0xe080100a

The status notification process for job execution control could not acquire the environment setting parameter.

0xe080100b

A bind error occurred in the status notification process for job execution control.

0xe080100d

The port number that is used for the status notification process for job execution control is invalid.

0xe080100e

The status notification process for job execution control has started twice.

A.2 System Error Numbers of Messages KAVU2xxx-E and KAVU2xxx-W

You can use the system error number output in the messages KAVU2xxx-E and KAVU2xxx-W to narrow down the probable cause of the error.

The table below lists the causes inferred from system error numbers and the corrective action to take in each case. If the error persists after you take the indicated action, use the data collection tool to collect data, and then contact the system administrator.

Table A‒2: System error numbers of messages KAVU2xxx-E and KAVU2xxx-W

No.

System error number

Probable cause

Action

Windows

HP-UX

Solaris

AIX

Linux

1

10048

226

125

67

98

The port number for communication is already in use.

Perform the following:

Make sure the port number used by JP1/AJS3 is not being used by another program.#1

Check the number of sockets output by the netstat command that have TIME_WAIT status.#2

2

10049

227

126

68

99

The IP address for communication by the local host differs from the IP address set in the NIC.

The NIC that has the IP address used for communication by the local host is disabled.

Perform the following:

Check the IP address of the local host set in the hosts file, DNS server, jp1hosts file, and jp1hosts2 file.#1

Check the status of the NIC.#3

3

10053

10054

231

232

130

131

72

73

103

104

The connection was dropped due to a problem on the network.

Perform the following:

Make sure the system has not been shut down.#4

Check the status of the NIC.#3

4

10051

10060

10064

10065

229

238

241

242

128

145

147

148

70

78

80

81

101

110

112

113

The remote system is inactive.

The network to which the local system belongs is not connected to the remote LAN.

Perform the following:

Make sure the remote system is active.#5

Make sure the network to which the local system belongs is connected to the remote system.#6

5

10061

239

146

79

111

The service that uses the specified port number on the remote system is inactive.

Perform the following:

Make sure that the remote service that communicates with JP1/AJS3 is active.#5

Check the port number used by the two systems.#1

#1

If you need to change the port number or IP address settings, stop JP1/AJS3 first.

#2

If there are a large number of sockets in TIME_WAIT status, there might be a temporary shortage of free socket ports. In this case, wait until the number of TIME_WAIT sockets decreases and then re-execute the job.

For details, see 3.1.1(5) OS tuning in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#3

If the NIC is inactive, first stop JP1/AJS3 and then start the NIC.

#4

To find out whether a network problem has occurred, check the system's network log.

#5

If the remote system is inactive or if the service that communicates with JP1/AJS3 is inactive, start the service.

There is no need to restart JP1/AJS3 on the local host (the host that outputs the messages KAVU2xxx-E and KAVU2xxx-W).

#6

If the IP bind method is set for the sending side in the communication settings, JP1/AJS3-based communication sometimes results in an error and a system error number is output, even though communication by the ping command and other OS commands is possible. For details, see 2.3.4 Example configurations with multiple LANs and their communications settings in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide. See also the description about how to use JP1/Base in an environment of distinct networks in the Job Management Partner 1/Base User's Guide.

B. Return Codes of System Calls

The following table describes the causes of return codes of major system calls, and the actions you need to take. For errors not explained in the table, see the documentation for your OS.

Unless otherwise specified, the table covers errno in HP-UX.

The table only explains the major system calls. For a closer examination, check the mnemonic for the errno value shown in the message against the errno definition file for your OS. For example, see the /usr/include/sys/errno.h file in HP-UX and Solaris, or the definition with the errno.h header in Windows and Visual C++. Furthermore, use the manual to check the system call that caused the error and to determine the cause of the error indicated by the mnemonic.

Table B‒1: Causes of return codes for system calls, and actions to be taken

System call

errno

Mnemonic

Probable major causes

Action

fork

11

EAGAIN

There are too many processes, or a temporary memory shortage occurred.

Re-execute. If the error occurs again, stop unnecessary processes.

12

ENOMEM

Either of the following is possible:

A new process cannot be created due to insufficient swap area or virtual memory.

There are too many processes or some processes are consuming large amounts of memory.

If the amount of swap area or virtual memory is insufficient, increase it.

If you cannot increase the amount, stop unnecessary processes.

If some processes are consuming large amounts of memory, check whether you can stop such processes.

malloc

12

ENOMEM

Either of the following is possible:

Process-specific memory cannot be allocated due to insufficient swap area or virtual memory.

There are too many processes or some processes are consuming large amounts of memory.

If the amount of swap area or virtual memory is insufficient, increase it.

If you cannot expand them, stop unnecessary processes.

If some processes are consuming large amounts of memory, check whether you can stop such processes.

22

EINVAL

Invalid memory management information was detected.

Contact the system administrator.

mkdir

13

EACCESS

The access permission is invalid.

Check whether the access permission for files under the embedded database practical directory is correct.

28

ENOSPC

The file system does not have sufficient available free area.

Allocate free space.

msgget

28

ENOSPC

The value specified for msgmni (number of message queue identifiers) is too small.

In Windows, the installation drive does not have sufficient free space or available resources are insufficient.

Estimate the requirements for all programs that run on the server machine applicable to msgmni, change the specified value, and then restart the server machine.

In Windows, allocate free space on the installation drive larger than the size of shared memory.

msgrcv

22

36

EINVAL

EIDRM

A message queue used for the embedded database was deleted.

In Windows, a work file under the embedded database installation directory may have been deleted while the embedded database was running.

Forcibly stop the embedded database if it has not terminated abnormally. Then restart the server machine (In Windows, restart the embedded database service).

msgsnd

11

EAGAIN

The value specified for msgmni (number of message queue identifiers) or msgtql (number of messages) is too small.

Estimate the requirements for all programs that run on the server machine applicable to msgmni or msgtql, change the specified value, and then restart the server machine.

22

EINVAL

A message queue used for the embedded database was deleted.

Forcibly stop the embedded database if it has not terminated abnormally. Then restart the server machine.

open

2

ENOENT

The file or directory was not found.

If logblib.c is output as the calling module in the message KFPO00107-E, the message text file was not found. In this case, an embedded database that is not currently in use may be registered in the OS.

Use the ajsembdbunset command to delete the embedded database that is currently not in use.

6

ENXIO

You do not have access permission for files.

Make sure that the device exists and that it is enabled. If the device is not enabled, enable it. If this situation does not apply, take action according to the manual for your OS.

13

EACCES

You do not have permission for files.

Review the permissions for the target files, directories, or embedded database practical directory.

Check whether the user who executes the operation has permissions for the target files, directories, or embedded database practical directory.

For operations performed by an AJS administrator, make sure that the required authorization has been set for the AJS administrators.

17

EEXIST

The file you attempted to create already exists.

Change the file name and re-execute. Alternatively, delete unnecessary existing files, if any, and then re-execute.

23

ENFILE

The number of open files exceeded the maximum for the system.

In Windows, the installation drive does not have sufficient free space.

Increase the maximum number of open files allowed for a system specified in the kernel parameter of the OS (nfile in HP-UX, or maxuproc x nofiles x number-of-fixed-licenses in AIX 5L, NR_FILE or fs.file-max in Linux). Also stop any unnecessary processes and close any unnecessary windows.

In Windows, allocate free space on the installation drive larger than the size of shared memory.

24

EMFILE

There are too many open files in the process.

In Windows, the installation drive does not have sufficient free space.

Increase the maximum number of open files allowed for a process specified in the kernel parameter of the OS (maxfiles in HP-UX, rlim_fd_cur in Solaris, or nofiles in AIX 5L, INR_OPEN in Linux). In Windows, allocate free space on the installation drive larger than the size of shared memory.

999

ENOENT

In Windows, the work file in the embedded database may have been corrupted.

Make sure that the embedded database has stopped, and then perform recovery by deleting all of the following files.

Note, however, that files after number 4 may not exist.

embedded-database-practical-directory\uxpldir\spool\system\filmng.dat

embedded-database-practical-directory\uxpldir\spool\system\flg.dat

embedded-database-practical-directory\uxpldir\spool\system\shmmng.dat

embedded-database-practical-directory\spool\~pdatmode

embedded-database-practical-directory\spool\~pdipcid

embedded-database-practical-directory\spool\oslmqid

embedded-database-practical-directory\spool\oslsmid

embedded-database-practical-directory\spool\pdprcsts

embedded-database-practical-directory\spool\scdqid1

embedded-database-practical-directory\spool\scdqid2

embedded-database-practical-directory\tmp\pdommenv

All files under embedded-database-practical-directory\uxpldir\spool\shm

embedded-database-practical-directory\uxpldir\spool\system\semmng.dat

embedded-database-practical-directory\uxpldir\spool\system\msgmng.dat

When you start the embedded database after deleting the above files, make sure that no other applications such as Explorer are accessing embedded-database-practical-directory\tmp.

semget

28

ENOSPC

The value specified for semmni (number of semaphore identifiers) or semmns (number of semaphores in the system) is too small.

In Windows, the installation drive does not have sufficient free space.

Estimate the requirements for all programs that run on the server machine applicable to semmni and semmns, change the specified values, and then restart the server machine.

In Windows, allocate free space on the installation drive larger than the size of shared memory.

semop

22

EINVAL

A semaphore used for the embedded database was deleted.

In Windows, a work file under the embedded database installation directory may have been deleted while the embedded database was running.

If the embedded database did not terminate abnormally, forcibly terminate it. Then restart the server machine (In Windows, restart the embedded database service).

shmat

12

ENOMEM

One of the following is possible:

Available resources are insufficient, including cases in which consecutive free areas cannot be allocated to the space of the process to which the shared memory is attached.

In Windows, an error occurred while the Windows registry was being accessed.

In Windows, an embedded database service has not started (when shared memory is allocated to a paging file).

Allocate memory, and then re-execute.

If the Windows registry has been damaged, contact the system administrator.

Check whether the embedded database service has started. If it has stopped, start it.

22

EINVAL

The shared memory for the embedded database was not found.

A command might have been executed before the OS was started (during execution of /etc/rc).

In Windows, a work file under the embedded database installation directory may have been deleted while the embedded database was running.

Alternatively, a command may have been executed before startup of the embedded database was completed.

If the command was executed before the OS was started, wait until the OS has started, and then re-execute the command. If startup of the embedded database was not completed, wait until the startup of the embedded database has been completed, and then execute the command.

In Windows, forcibly stop the embedded database if it has not terminated abnormally. Then restart the embedded database service.

shmdt

12

ENOMEM

In Windows, either of the following is possible.

An error occurred while the Windows registry was being accessed.

The embedded database service has not started (when shared memory is allocated to a paging file).

If the Windows registry has been damaged, contact the system administrator.

When shared memory is allocated to a paging file, check whether the embedded database service has started. If it is in the stop status, start it.

shmctl

1

EPERM

You cannot process the shared memory because you are not the owner.

If the message KFPO00107-E was output, check it.

12

ENOMEM

In Windows, either of the following is possible.

An error occurred while the Windows registry was being accessed.

The embedded database has not started (when shared memory is allocated to a paging file).

If the Windows registry has been damaged, contact the system administrator.

Check whether the embedded database service has started. If it is in the stop status, start it.

shmget

12

ENOMEM

In UNIX, the server machine does not have the amount of memory required for allocating the required size of shared memory.

In Windows, see Table B-2.

In UNIX, reduce memory usage on the server machine. Alternatively, increase the amount of real memory for the OS.

In Windows, see Table B-2.

22

EINVAL

In UNIX, the size of the shared memory you attempted to acquire exceeded the shmmax kernel parameter of the OS.

In Windows, a work file under the embedded database installation directory may have been deleted while the embedded database was running.

In UNIX, increase the value specified in the shmmax kernel parameter for the OS. Then, restart the server machine.

For a Windows embedded database server, forcibly stop the embedded database if it has not terminated abnormally. Then restart the embedded database service.

28

ENOSPC

In UNIX, the number of shared memory IDs exceeded the maximum for the OS.

In Windows, the installation drive does not have sufficient free space. For a Windows embedded database server, the installation drive does not have sufficient free space. If a paging file was allocated as shared memory, the process-specific memory is insufficient for the embedded database service to manage the shared memory.

In UNIX, take at least one of the following actions:

Reduce the number of shared memory segments on the machine.

Increase the value specified for the shmmni kernel parameter of the OS.

In Windows, allocate free space on the installation drive larger than the size of shared memory.

If a paging file was allocated as shared memory, check the maximum memory usage for the entire system, and then increase the physical memory or the size of the paging file.

write

5

EIO

An I/O error occurred.

Take action according to the OS and hardware information.

14

EFAULT

An attempt was made to write to an area that cannot be accessed. The disk to which the write was attempted may have been detached.

If this code is returned when the disk was switched during node switching, ignore this code because there is no problem. If you have inadvertently detached the disk while the embedded database was running, restore the appropriate file from the backup, or initialize that file. For other cases, contact the system administrator.

27

EFBIG

The size of a file exceeded the system limit.

Change the file size limit for the administrator of the embedded database system or the root user to be greater than the size of a file used for the embedded database system, or to an unlimited value. Alternatively, reduce the size of files used for the embedded database system.

28

ENOSPC

The file system does not have sufficient free space.

Allocate free space.

abort, creat, execl, execle, execlp, execv, execvp, fopen, fork, gethostbyaddr, gethostbyname, mmap, msgctl, msgget, msgrcv, msgsnd, open, read, readv, select, semctl, semget, semop, shmat, shmctl, shmdt, shmget, signal, sigrelse, sigset, sigsetmask, sigvector, stat, system, write, writev, and so on

22

EINVAL

In Windows, memory may be insufficient.

In Windows, take either of the following actions:

Reduce the total size of the database on the server machine.

Specify the same value (fixed value) for the initial size and the maximum size of the system's virtual memory.

Table B‒2: Actions to be taken when an error occurs in shmget (Windows)

Location of allocated shared memory

Cause

Check method

Action

File

The installation directory does not have sufficient free space.

Check whether the drive on which the embedded database is installed has sufficient free space.

If the amount of free space is insufficient, delete unnecessary files.

The disk containing the disk paging file does not have sufficient free space because the initial value of virtual memory differs from the maximum value.

Check whether the disk containing the disk paging file has sufficient free space.

If the disk does not have free space, re-allocate virtual memory. To do this, specify the same value (fixed value) for the initial size and the maximum size so that consecutive areas are created on the drive.

Memory is insufficient.

Check the memory usage.

Expand or re-allocate virtual memory. To do this, specify the same value (fixed value) for the initial size and the maximum size so that consecutive areas are created on the drive.

Check whether the disk containing the paging file has sufficient free space.

If an expansion in virtual memory is required, expand it. At this time, specify the same value for the initial value and maximum value of virtual memory.

Paging file

The installation directory does not have sufficient free space.

Check whether the drive on which the embedded database is installed has sufficient free space.

If the amount of free space is insufficient, delete unnecessary files.

The disk containing the disk paging file does not have sufficient free space because the initial value of virtual memory differs from the maximum value.

Check whether the disk containing the disk paging file has sufficient free space.

If the disk does not have free space, re-allocate virtual memory. To do this, specify the same value (fixed value) for the initial size and the maximum size so that consecutive areas are created on the drive.

Memory is insufficient.

Check the memory usage.

Expand or re-allocate virtual memory. To do this, specify the same value (fixed value) for the initial size and the maximum size so that consecutive areas are created on the drive.

Check whether the disk containing the paging file has sufficient free space.

If an expansion in virtual memory is required, expand it. At this time, specify the same value for the initial value and maximum value of virtual memory.

The embedded database service has not started.

Check whether the embedded database service has started.

If the embedded database service is in the stop status, start it.

C. Error Codes Returned from Access Requests for an Embedded Database File System

The following table lists the error reason codes returned from access requests for an embedded database file system.

Table C‒1: Error reason codes returned from access requests for an embedded database file system

Error code

Description

Action

-1511

The path name is specified incorrectly.

An invalid character is specified in the path name.

The length of the path name exceeds the limit (167 characters).

The length of the embedded database file system area name exceeds the limit (165 characters).

The length of the embedded database file name exceeded the limit (30 characters).

Recheck the path name specified on the command line.

If there is no problem, contact the system administrator.

-1514

The sector length is specified incorrectly.

The system does not support embedded database file system areas that are created with a sector length specified.

Use an embedded database file system area that is created without a sector length specified.

If this situation does not apply, contact the system administrator.

-1532

A file other than an ordinary file or a character-type special file (direct disk access in Windows) is specified.

The embedded database file system area was not found.

Recheck the path name specified on the command line.

A file other than an ordinary file or character-type special file (direct disk access in Windows) cannot be used as an embedded database file system area.

Check whether the embedded database file system area indicated in the message is deleted and whether the symbolic link is broken.

-1534

An exclusivity error occurred.

If a command is using the embedded database file system area indicated in the message, wait until the command terminates, and then retry.

If command execution results in this error, stop the embedded database and then execute the command (only for commands that are executed when the embedded database is not running).

If you cannot correct the problem by taking the above actions, contact the system administrator.

-1535

There is not enough free space in the embedded database file system area.

The disk on which the embedded database file system area was created became full because free space was insufficient.

If the disk was full during operation of the embedded database file system area for an ordinary file, delete other files or expand disk capacity to increase free space.

The disk does not become full when you are using an embedded database file system area for a character-type special file. However, if you are using symbolic links, check whether ordinary files have been linked by mistake.

-1538

This area is not an embedded database file system area.

The embedded database file system area may have been corrupted. Contact the system administrator.

-1539

The embedded database was not found.

If an error occurred in an embedded database file in the RDAREA during operation of the embedded database, the probable cause is that a backup existing before the RDAREA configuration was changed was used for recovery. Another probable cause is that the embedded database file was forcibly deleted. Recover the RDAREA using the correct recovery procedure or re-initialize it.

If the situation above does not apply, contact the system administrator.

-1540

You do not have access permission.

Review the access permissions for the files specified on the command line and in the system definition file.

In Windows, if an error occurred in an area using direct disk access, check whether a formatted disk was specified.

-1541

The embedded database file has already been defined.

The embedded database file specified on the command line already exists. Specify a unique name for the embedded database file.

If there is no file that has the same name as the specified file, contact the system administrator.

-1543

Versions are inconsistent.

The version of the operating embedded database is older than the version with which the embedded database file system area was created. Areas created with a new version of HiRDB cannot be used with an old version of the embedded database.

When multiple versions of embedded databases are installed, check the absolute path name you want to use for execution.

-1544

An I/O error occurred.

Take action according to the instructions given for errno in the message KFPO00107-E output to Windows event log or syslog.

If the KFPO00107-E message is not output, contact the system administrator.

-1548

Lock segments are insufficient.

Take action according to the instructions given for errno in the message KFPO00107-E output to Windows event log or syslog. If errno is 46 (ENOLCK), OS lock segments are insufficient.

In HP-UX, recheck nflock.

For other OSs, wait until another process using the lock terminates, and then retry.

If you cannot correct the problem by taking the above actions, contact the system administrator.

-1549

The number of open files exceeded the maximum for the system. Alternatively, it exceeded the maximum for the process.

Take action according to the instructions given for errno in the message KFPO00107-E output to Windows event log or syslog.

Check the following values:

In HP-UX

nfile and maxfiles_lim

In Solaris

rlim_fd_max

In AIX 5L

nofiles_hard

In Linux

NR_FILE, NR_OPEN

-1550

Memory is insufficient.

Review the memory estimate. If you find any problems, take action such as increasing memory or reducing the number of resident processes.

If you cannot correct the problem by taking the above action, contact the system administrator.

-1555

In the parallel I/O function, lock segments are insufficient, the number of open files exceeds the maximum, or memory is insufficient.

Take the actions provided for error codes -1548, -1549, and -1550.

If you cannot correct the problem by taking these actions, contact the system administrator.

Others

--

Contact the system administrator.

Legend:

--: Not applicable

D. Version Revisions

This appendix lists the changes in each version of the JP1/AJS series programs.

D.1 Revisions in 10-50

The following lists the revisions in 10-50 for each program.

(1) JP1/AJS3 - Manager

A virtual machine on which JP1/AJS3 has been installed and configured can now be duplicated.

Functionality was expanded so that a disaster recovery environment can be set up with the main and remote hosts whose logical host names are the same.

A setting for shifting the start day by a number of days (counting both open and closed days) was added.

A function that holds jobnet execution during immediate execution registration was added.

A function that can execute some commands from JP1/AJS3 - View to JP1/AJS3 - Manager was added.

The files jajs_log.bat and jajs_log, which have the same functionality as the data collection tool (_04.bat and _04), are now available. In addition, an option was added to the Windows version of the data collection tools that allows you to specify the location to which data is output.

An option was added to the ajsprint command so that relation line information can be output in order of the unit name.

The procedure for changing the IP address of an agent host was changed.

UTF-8 was added to the list of character encodings that can be used in AIX, HP-UX, and Solaris 10.

The number of characters that can be used when specifying a logical host name for the command jajs_killall.cluster was increased.

(2) JP1/AJS3 - Agent

The files jajs_log.bat and jajs_log, which have the same functionality as the data collection tool (_04.bat and _04), are now available. In addition, an option was added to the Windows version of the data collection tools that allows you to specify the location to which data is output.

The procedure for changing the IP address of an agent host was changed.

UTF-8 was added to the list of character encodings that can be used in AIX, HP-UX, and Solaris 10.

The number of characters that can be used when specifying a logical host name for the command jajs_killall.cluster was increased.

(3) JP1/AJS3 - View

A setting for shifting the start day by a number of days (counting both open and closed days) was added to the Schedule by days from start settings in the Advanced tab of the Schedule Rule dialog box.

A setting for holding jobnet execution if the registration method is Immediate execution was added to the Register for Execution dialog box.

A function that can execute some commands from JP1/AJS3 - View to JP1/AJS3 - Manager was added.

The files jajs_log.bat and jajs_log, which have the same functionality as the data collection tool (_04.bat and _04), are now available. In addition, an option was added to the Windows version of the data collection tools that allows you to specify the location to which data is output.

D.2 Revisions in 10-10

The following lists the revisions in 10-10 for each program.

(1) JP1/AJS3 - Manager

A function was added that uses IP addresses to restrict the hosts that are able to connect to a manager host.

A function was added for checking the execution schedule of unregistered units in the Monthly Schedule window of JP1/AJS3 - View.

A function was added for preventing scheduler services for which the JP1 user logged in to JP1/AJS3 - View has no access privileges from appearing in JP1/AJS3 - View.

A function was added for restricting the maximum number of allowed JP1/AJS3 - View concurrent sessions for a scheduler service.

A function was added for changing the passwords of JP1 users by using JP1/AJS3 - View.

The following OS is supported:

Linux 5.1 (x86) or later

Linux 5.1 (AMD/Intel 64) or later

Content related to Solaris 11 (SPARC) was added.

(2) JP1/AJS3 - Agent

A function was added that uses IP addresses to restrict the hosts that are able to connect to an agent host.

Content related to Solaris 11 (SPARC) was added.

(3) JP1/AJS3 - View

A function was added for checking the execution schedule of unregistered units in the Monthly Schedule window of JP1/AJS3 - View.

A function was added for preventing scheduler services for which the JP1 user logged in to JP1/AJS3 - View has no access privileges from appearing in JP1/AJS3 - View.

A function was added for restricting the maximum number of allowed JP1/AJS3 - View concurrent sessions for a scheduler service.

A function was added for changing the passwords of JP1 users by using JP1/AJS3 - View.

The way in which the Register Custom Job dialog box and the Set Properties of Custom Job dialog box are displayed was changed.

A change was made so that when Jobnet Definition is selected from Function Menu, jobnets for which execution has been registered are displayed in the list area of the JP1/AJS3 - View window (main window).

The function for hiding the icons of unused units in the Jobnet Editor window (a setting in the Set Default Values dialog box) was extended.

A function was added for preventing the history of previously-used login-user names and connection-destination host names from appearing on the Login screen.

D.3 Revisions in 10-00

The following lists the revisions in 10-00 for each program.

(1) JP1/AJS3 - Manager

IPv6 addresses are now supported for communication.

Mirroring by copying a disk is now supported to enable disaster recovery operations.

The AJS administrator, with JP1/AJS3 access permissions that are almost equivalent to superuser permissions, can now be designated when JP1/AJS3 is installed as a new installation.

Wait conditions can now be used as a means for controlling the execution order of units across jobnets.

The number of definition items for which macro variables can be specified has been increased, and the passing information setting job, which uses macro variables to pass information, has been added.

A function that assigns a created or copied unit the attributes inherited from the upper-level unit, and a function that can permanently assign (fix) an execution user to a job have been added.

A function that prevents jobs from being executed on unauthorized execution agents has been added.

A function that allows users to save information about temporary change operations and to re-execute temporary change operations has been added.

A function that automatically retries execution of a job when the executable file defined for the job terminates abnormally has been added.

The dependent job of a judgment job can now be re-executed when the judgment job terminates normally.

Mutually exclusive conditions and range conditions can now be specified as judgment conditions for judgment jobs.

The Monitoring Event Log Job now can monitor the types of log data and events that were added in Windows Server 2008.

An option that can be used when the Interval Control Job is defined as a start condition has been added to forcibly assume that the start condition is satisfied immediately after the monitoring of the start condition starts.

The email sending job now supports a function that sends emails without using Outlook.

SNMP traps can now be issued in Windows Server 2008.

Processes for managing the embedded database have been improved.

The startup type of the JP1/AJS3 Database service has been changed to Manual so that the JP1/AJS3 Database ClusterService service will not be created.

An option has been added that checks the permissions of JP1 users mapped to OS users that have administrator permissions based on the JP1 permission level.

A time period can now be specified when the ajsentry command is used to register a jobnet for fixed execution.

Options that can be specified when the jajs_setup or jajs_setup_cluster command is used to set up the embedded database have been added.

The ajsembdbidlist and ajsembdbstatus commands can now be used to display the status of the embedded database.

The embedded database settings file is now generated when an embedded database is set up. If this file is specified when the ajsembdbbuild command is used to build another embedded database, the other embedded database will be set up with the settings in the file.

Execution user name and Execution time have been added as extended attributes that can be output for JP1 events (specific information) so that JP1 events indicating job termination can be used as job operating information.

JP1/AJS3 - Manager can now link with JP1/DH - AJE, and DHAJEW has been added as a standard custom job.

The following OS is no longer supported:

Solaris 9(SPARC)

Linux 5 (x86)

Linux 5 (AMD/Intel 64)

Linux 5 (IPF)

The following OS is supported:

Windows Server 2012

Solaris 11(SPARC)

Linux 6 (x86)

Linux 6 (x64)

(2) JP1/AJS3 - Agent

IPv6 addresses are now supported for communication.

The AJS administrator, with JP1/AJS3 access permissions that are almost equivalent to superuser permissions, can now be designated when JP1/AJS3 is installed as a new installation.

An option that can be used when the Interval Control Job is defined as a start condition has been added to forcibly assume that the condition is satisfied when the monitoring of the start condition starts.

The email sending job now supports a function that sends emails without using Outlook.

SNMP traps can now be issued in Windows Server 2008.

The Monitoring Event Log Job now can monitor the types of log data and events that were added in Windows Server 2008.

The following OS is no longer supported:

Solaris 9(SPARC)

Linux 5 (x86)

Linux 5 (AMD/Intel 64)

Linux 5 (IPF)

The following OS is supported:

Windows Server 2012

Solaris 11(SPARC)

Linux 6 (x86)

Linux 6 (x64)

(3) JP1/AJS3 - View

The Wait Conditions Settings List window and the Wait Conditions Statuses window have been added as means for managing units with wait conditions and units whose end is being waited for.

A dialog box which lists temporary change operations that have already been performed and which allows users to re-execute (re-apply) specific temporary change operations has been added.

Retry information can now be displayed in the following windows:

Daily Schedule window

Monthly Schedule window

Jobnet Monitor window

Detailed Schedule dialog box

Monitor Details - [icon-name] dialog box

Whether retries are enabled is now displayed in the list area of the Jobnet Editor window.

The Jobnet Monitor window was provided with a function that grays out all relation lines and units other than the day's units (the units that were executed and are to be executed on the day).

Specify period, Reference calendar, Waiting-target, and Execution type have been added as search conditions that can be specified in the Search window.

In the Search window, Retry Settings and Retry execution can now be specified as search conditions. In addition, the search results displayed in the Search window now include items related to automatic retry.

The procedure for displaying the units found in the Search window in the Summary Monitor window has been simplified.

The Display Item Setup dialog box can now be used to set the items to be displayed in the list areas of the Jobnet Editor window and the Jobnet Monitor window.

A function that allows users to define all-at-one-time schedule rules that start execution at regular intervals, and a function that allows users to delete multiple schedule rules at one time have been added.

Definition items related to automatic retry have been added to the detailed definitions of Unix jobs, PC jobs, QUEUE jobs, and custom jobs.

Mutually exclusive conditions and range conditions can now be specified as judgment conditions for judgment jobs.

The types of log data and events that were added in Windows Server 2008 can now be specified as Log type and Event type in the detailed definition of the Monitoring Event Log Job.

The Expire right after starting option has been added in the detailed definition of the Interval Control Job. When the job has been defined as a start condition, this option can be used to forcibly assume that the condition is satisfied immediately after the monitoring of the start condition starts.

An option ensuring that the job groups and planning groups displayed in the list area are initially selected when the JP1/AJS3 - View window (Main window) opens has been added. In addition, an option ensuring that the nested jobnets and nested remote jobnets displayed in the map area are initially selected when the Jobnet Editor window or the Jobnet Monitor window opens has been added.

An option has been added that displays a nested jobnet as being selected at the location at which the jobnet existed before it was moved to the upper layer in the Jobnet Editor window or the Jobnet Monitor window.

When the Depends on upper-level jobnet check box is selected in the schedule settings of a nested jobnet, whether to display a confirmation message before defined schedule rules are deleted can now be selected by using an option.

The Start button, which allows users to launch arbitrary programs, has been added to the Monitor Details - [custom-job-name] dialog box.

Because of the user authentication function added in JP1/AJS3 - Definition Assistant 09-10, specifying the JP1 user name is now mandatory for starting JP1/AJS3 - Definition Assistant from JP1/AJS3 - View. With this specification change, User name has been added as an item that can be selected from the Replace drop-down list in the Tool Entry dialog box.

The following OS is supported:

Windows 8.1

Windows 8

Windows Server 2012

An option for preventing the opening of multiple Jobnet Editor windows and Jobnet Monitor windows has been added.

D.4 Revisions in 09-00

The following lists the revisions in 09-00 for each program.

(1) JP1/AJS3 - Manager

The standard database of JP1/AJS3 is now an embedded database.

Functions related to an embedded database have been changed as follows:

The sizes of the large-scale, medium-scale, and small-scale database models have been changed.

The database area auto-increment function and the system log auto-increment function have been added.

The system log is no longer used.

The functions of the commands used to control an embedded database have been enhanced.

The ISAM database is now used only for QUEUE jobs and submit jobs.

An agent management function has been added for specifying a logical execution agent name as the destination host for a job or jobnet. Previously, users could only specify execution hosts by their real names.

Jobs that are in the Now queuing status when the service is stopped are now returned to the Wait for prev. to end status when the service restarts (in hot-start mode), before being resubmitted.

A jobnet release function has been added for replacing the definition of a jobnet that is registered for execution with another definition.

The job execution control manager process (jpqman) and event/action control manager process (jpomanager) can now be started on a scheduler service basis.

A scheduler log file can now be output for an individual scheduler service or host.

The following functions have been enhanced:

The method by which the number of logs to keep is managed

The process by which monitored generations of jobnets with start conditions are established

The process by which execution generations when a start condition is established are held

A format specification has been added to the ajsshow command for outputting the standard output file name.

The Manager Environment Settings dialog box is no longer provided. Instead, you can use the jajs_config command to set up the manager environment.

The following environment setting parameters have been added:

FixedHostnameForAgent

NotificationConstantRetry

NotificationRetryInterval

NotificationRetryCount

ClientConnectTimeout

A function has been added to support end delay monitoring based on how long a job takes to execute.

The jobnet connector functionality has been enhanced to enable control of the execution order of root jobnets managed by different scheduler services.

The definition pre-check has been enhanced so that if an invalid execution order is found in the units of the jobnet being checked, the names of the units are output to the check results file.

The file permission check performed at execution of a Unix job has been enhanced to include checks of the access control list and secondary group settings as well as file permissions.

A function has been added that enables event jobs to continue executing even if the JP1/AJS3 service stops on the execution host.

A function has been added for exporting and importing the registration statuses of jobnets as registered execution-schedule information.

Linkage with message queues on UNIX hosts (TP1/LiNK, TP1/Message Queue, MQSeries) is no longer supported.

Windows Server 2008 has been added as platforms supported by JP1/AJS3 - Manager.

A unit called a jobnet connector which controls the execution order of root jobnets has been added.

An option has been added to output a detailed history of user operations, such as changes to jobnet definitions, to the scheduler log.

The ajslogprint command for extracting log entries from the scheduler log has been added.

(2) JP1/AJS3 - Agent

The Agent Environment Settings dialog box is no longer provided. Instead, you can use the jajs_config command to set up the agent environment.

Linkage with a message queue system is no longer supported.

The following environment setting parameters have been added:

FixedHostnameForAgent

NotificationConstantRetry

NotificationRetryInterval

NotificationRetryCount

ClientConnectTimeout

The file permission check performed at execution of a Unix job has been enhanced to include checks of the access control list and secondary group settings as well as file permissions.

Linkage with message queues on UNIX hosts (TP1/LiNK, TP1/Message Queue, MQSeries) is no longer supported.

Windows Server has been added as platforms supported by JP1/AJS3 - Agent.

(3) JP1/AJS3 - View

An agent management function has been added for specifying a logical execution agent name as the destination host for a job or jobnet. Previously, users could only specify execution hosts by their real names.

A jobnet release function has been added for replacing the definition of a jobnet that is registered for execution with another definition.

Function menus have been added to the JP1/AJS3 - View window to facilitate task-oriented operation.

The JP1/AJS3 - View window (Summary Monitor window) has been added. In this window, you can view the progress of jobnets and other information.

JP1/AJS3 - View can now be started in the following modes:

Normal mode

In this mode, the JP1/AJS3 - View window is equipped with function menus.

Monitoring mode

A mode dedicated to monitoring jobs and jobnets. Only the JP1/AJS3 - View window (Summary Monitor window) is displayed.

Compatible mode

JP1/AJS3 - View operates in the same way as JP1/AJS2 - View version 8 or earlier.

A Detailed Information area has been added to the JP1/AJS3 - View window (Main window), which displays detailed information about a unit.

The concurrent execution setting of monitored generations and the holding behavior of execution generations (produced when a start condition is satisfied) can now be selected in the detailed definition of a start condition.

A list filter function has been added for filtering the information in a list.

A function has been added for saving list information in CSV format.

You can now click a button in the Daily Schedule window and Monthly Schedule window to move between days and months.

A list area has been added to the Jobnet Editor window and Jobnet Monitor window. This area displays the jobs defined in the jobnet.

A Search window has been added, in which you can set detailed search conditions and perform operations on units listed in the search results.

You can now use a mouse wheel to scroll inside JP1/AJS3 - View.

A function has been added that allows you to select whether Type in list areas are grouped by type or displayed in detailed format.

A function has been added for prohibiting changes to specific definition items in the Define Details dialog box.

A function has been added for removing icons you no longer use from the icon list area in the Jobnet Editor window.

Windows 7 has been added as a supported OS (JP1/AJS3 - View 09-00-05 or later).

A function has been added to support end delay monitoring based on how long a job takes to execute.

The jobnet connector functionality has been enhanced to enable control of the execution order of root jobnets managed by different scheduler services.

An option has been added to the Filter Settings dialog box so that jobnets with hold plans can be treated as jobnets in Being held status for filtering purposes in the Daily Schedule window and Monthly Schedule window.

The ability to define, operate, and monitor jobnet connectors which control the execution order of root jobnets has been added.

A function that displays the preceding and succeeding jobs of a given job or jobnet in bold has been added.

Support for Windows Vista has been added.

D.5 Revisions in 08-00

The following lists the revisions in 08-00 for each program.

(1) JP1/AJS2 - Manager

The recommended values for the environment settings are now set during installation and setup.

A Monitoring Files job can now monitor files larger than 2 gigabytes (large files).

The ajsstatus command can now output the connection status of JP1/AJS2 - View.

The following commands used to control an embedded database have been added:

ajsembdbaddarea command (expands a database area in an embedded database)

ajsembdbaddlog command (expands a log area in an embedded database)

ajsembdbcancel command (cancels execution of a command manipulating an embedded database)

ajsembdboplog command (manipulates embedded database logs)

ajsembdbreclaim command (maintains an embedded database)

ajsembdbrorg command (unloads and reloads an embedded database)

ajsembdbrstr command (backs up and restores an embedded database)

ajsembdbstart command (starts an embedded database)

ajsembdbstatus command (monitors an embedded database)

ajsembdbstop command (stops an embedded database)

ajsembdbunset command (removes the setup of an embedded database)

With support of the ajsembdbreclaim command, the time required to reclaim free pages has been reduced.

JP1/Performance Management - Agent Option for JP1/AJS2 can now be linked with JP1/AJS2 to analyze the operating status.

The jajs_start command and the jajs_start.cluster command can now check whether a process has already been started when JP1/AJS2 is started. (UNIX only)

(2) JP1/AJS2 - Agent

The recommended values for the environment settings are now set during installation and setup.

A Monitoring Files job can now monitor files larger than 2 gigabytes (large files).

(3) JP1/AJS2 - View

Icons have been changed.

D.6 Revisions in 07-50

The following lists the revisions in 07-50 for each program.

(1) JP1/AJS2 - Manager

Macro variables can now be used during registration for execution to specify information to be passed.

Judgment jobs can now perform variable judgment.

A function has been added that suppresses jobnet executions that follow an abnormally terminated jobnet and that will be started when their start conditions are satisfied.

A definition pre-check function has been added for conducting a final check before starting production in the production environment after the unit definitions are migrated from the development environment.

The jpomanevreset command has been added for deleting data accumulated in the event action manager if a large amount of unprocessed data accumulated in the event action manager has caused delay. To identify the start conditions and agents that have caused this problem, the jpomanevshow command has also been added for displaying information about agents that frequently send data to the manager and the start conditions.

A function that alleviates consumption of the Desktop heap has been added. (Windows only)

A function has been added for specifying the maximum wait time for the scheduler service to connect to a database.

Messages that were output to only the integrated trace log can now be output to syslog also. (UNIX only)

The following functions have been added to the data collection tool:

Specifying a logical host name

Filtering the data to be collected

Adding types of data that can be collected

Descriptions of messages have been improved.

An urgent command has been added that can be executed if an error occurs.

A function has been added that places limits on, for example, the size of files that can be received, to prevent a part of job processing from affecting the entire system operation.

A function has been added that performs a synchronized write when updating event job information or the wait information file.

The monitoring interval for linkage with MQ Series can now be specified in seconds.

If a TCP/IP connection error occurs, the retry interval and count can now be changed.

The policy to determine the agent hosts to which a job will be dispatched can now be specified.

All the detailed processes of the event action function can now be stopped to terminate the agent process for the event action function if any of the detailed processes have terminated upon receiving a signal.

Microsoft(R) Visual C++ .NET Version 2003 is now supported as a compiler for the provided code functions.

The ajsshow command can now display the hold attribute of a jobnet or job even when the jobnet or job has already terminated.

(2) JP1/AJS2 - Agent

A definition pre-check function has been added for conducting a final check before starting production in the production environment after the unit definitions are migrated from the development environment.

The following functions have been added to the data collection tool:

Specifying a logical host name

Filtering the data to be collected

Adding types of data that can be collected

Descriptions of messages have been improved.

The monitoring interval for linkage with MQ Series can now be specified in seconds.

All the detailed processes of the event action function can now be stopped to terminate the agent process for the event action function if any of the detailed processes have terminated upon receiving a signal.

A function has been added that performs a synchronized write when updating event job information or the wait information file.

(3) JP1/AJS2 - View

Macro variables can now be used during registration for execution to specify information to be passed.

Judgment jobs can now perform variable judgment.

A function has been added that suppresses the jobnet executions that follow an abnormally terminated jobnet and that will be started when their start conditions are satisfied.

The Add, Change Time, Execute Immediately, and Release Change options have been added to the JP1/AJS2 - View window.

The Paste (Extension) menu command has been added for copying units and relationship lines at the same time.

Relationship lines can now be drawn from multiple units to a single job network element.

When opening the Jobnet Monitor window of JP1/AJS2 - View from JP1/AJS2 Console View, if there is already an activated JP1/AJS2 - View, the window can now be opened in JP1/AJS2 - View.

The following functions have been added to the data collection tool:

Specifying a logical host name

Filtering the data to be collected

Adding types of data that can be collected

Descriptions of messages have been improved.

The maximum log file size for JP1/AJS2 - View has been increased.

The maximum log file size for JP1/AJS2 Console View has been increased.

In JP1/AJS2 - View, log information that previously was output many times in small units can now be output at one time.

In JP1/AJS2 Console View, log information that previously was output many times in small units can now be output at one time.

In the Windows version of JP1/AJS2 - View, Help has been added to the Start menu.

D.7 Revisions in 07-00

The following lists the revisions in 07-00 for each program.

(1) About JP1/AJS2 - Manager

A function was provided to temporarily compress JP1/AJS2 and reconfigure the ISAM database (scheduler database and job execution environment database) without stopping active applications.

ISAM databases can now be reconfigured in parallel.

The number of scheduler services that can be added has been changed from 9 to 20.

An option was added for outputting the execution timings of reference commands, such as ajsshow and the history of service processing requests from operation commands, as the operation log to the scheduler log.

The number of logs to keep for a jobnet has been changed from 99 to 999.

For a cold start of JP1/AJS2, the job execution environment database is deleted so that the startup time of JP1/AJS2 becomes shorter.

A function is now supported for validating the user profile information in the environment setup for job execution control.

By setting the number of days that job information is held to 0 days, jobs that terminate abnormally can now be handled by changing the save time.

The JP1/AJS2 job information deletion can now be suppressed.

Any event job can now be used in a DNS environment (host name in the FQDN format).

Event job reception information can now be inherited as macro variables as the parameters of standard jobs and action jobs without having to pay attention to double quotation marks in the inherited information.

The extended regular expression supported by JP1/Base can now be used in Receive event job monitoring jobs, Monitoring log files jobs, and Monitoring event log jobs according to the JP1/Base settings.

A function to execute queueless jobs is now supported.

(2) About JP1/AJS2 - Agent

Event job reception information can now be inherited as macro variables of the parameters of standard jobs and action jobs without being aware of double quotation marks in the inherited information.

A function for executing queueless jobs was supported.

When JP1/AJS2 - Agent starts, it no longer accesses the authentication server (07-00-/C or later).

(3) About JP1/AJS2 - View

A user profile can now be used to set the JP1/AJS2 - View environment.

A line feed character can now be inserted at any point in a unit name displayed in the map area of the Jobnet Editor and Jobnet Monitor windows.

The default values in the dialog box can now be changed.

Display items (columns) in the following locations can now be selected.

List area in the JP1/AJS2 - View window

Execution result list in the Daily Schedule window

Execution result list in the Monthly Schedule window

E. Reference Material for This Manual

This appendix provides reference information, including various conventions, for this manual.

E.1 Related publications

This manual is part of a related set of manuals. The manuals in the set are listed below (with the manual numbers):

About JP1/AJS:

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Overview (3021-3-318(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide (3021-3-319(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide (3021-3-320(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (3021-3-321(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2 (3021-3-322(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Administration Guide (3021-3-323(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Troubleshooting (3021-3-324(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Operator's Guide (3021-3-325(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Command Reference 1 (3021-3-326(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Command Reference 2 (3021-3-327(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Linkage Guide (3021-3-328(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Messages 1 (3021-3-329(E))

Job Management Partner 1/Automatic Job Management System 2 Description (3020-3-K21(E))

Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide (3020-3-K22(E))

Job Management Partner 1/Automatic Job Management System 2 Setup Guide (3020-3-K23(E))

Job Management Partner 1/Automatic Job Management System 2 Operator's Guide (3020-3-K24(E))

Job Management Partner 1/Automatic Job Management System 2 Command Reference (3020-3-K25(E))

Job Management Partner 1/Automatic Job Management System 2 Linkage Guide (3020-3-K27(E))

Job Management Partner 1/Automatic Job Management System 2 Messages (3020-3-K28(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 - Print Option Description, User's Guide (3021-3-331(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 - Definition Assistant Description, Operator's Guide and Reference (3021-3-332(E))

Job Management Partner 1/Automatic Job Management System 3 - Web Operation Assistant Description, Operator's Guide and Reference (3020-3-S18(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 for Enterprise Applications Description, User's Guide and Reference (3021-3-333(E))

About JP1:

Job Management Partner 1 Version 10 Job Management Partner 1/Base User's Guide (3021-3-301(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Base Messages (3021-3-302(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Base Function Reference (3021-3-303(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Integrated Management - Manager Quick Reference (3021-3-304(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Integrated Management - Manager Overview and System Design Guide (3021-3-305(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Integrated Management - Manager Configuration Guide (3021-3-306(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Integrated Management - Manager Administration Guide (3021-3-307(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Integrated Management - Manager GUI Reference (3021-3-308(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference (3021-3-309(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Integrated Management - Manager Messages (3021-3-310(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Script Description and Reference (3021-3-135(E)), for Windows Systems

Job Management Partner 1 Version 10 Job Management Partner 1/File Transmission Server/FTP Description, Reference, and Operator's Guide (3021-3-334(E)), for Windows systems

Job Management Partner 1 Version 10 Job Management Partner 1/File Transmission Server/FTP Description, Reference, and Operator's Guide (3021-3-335(E)), for UNIX systems

Job Management Partner 1 Version 10 Job Management Partner 1/Data Highway - Automatic Job Executor Operation manual (3021-3-336(E))

Job Management Partner 1/Software Distribution Description and Planning Guide (3020-3-S79(E)), for Windows systems

Job Management Partner 1/Software Distribution Setup Guide (3020-3-S80(E)), for Windows systems

Job Management Partner 1/Software Distribution System Administrator's Guide Volume 1 (3020-3-S81(E)), for Windows systems

Job Management Partner 1/Software Distribution System Administrator's Guide Volume 2 (3020-3-S82(E)), for Windows systems

Job Management Partner 1/Software Distribution Automatic Installation Tool Description and Reference (3020-3-S83(E)), for Windows systems

Job Management Partner 1/Software Distribution Administrator Kit Description and Operator's Guide (3020-3-S84(E))

Job Management Partner 1/Software Distribution Client Description and User's Guide (3020-3-S85(E)), for UNIX systems

Job Management Partner 1/Software Distribution SubManager Description and Administrator's Guide (3020-3-L42(E)), for UNIX systems

Job Management Partner 1/Software Distribution Manager Description and Administrator's Guide (3000-3-841(E))

Job Management Partner 1/Consolidated Management 2/Extensible SNMP Agent Description, Operator's Guide and Reference (3020-3-L04(E)), for UNIX systems

Job Management Partner 1/NQSEXEC System Administrator's Guide (3020-3-F30(E))

Job Management Partner 1/Open Job Entry Description, User's Guide and Reference (6190-3-365(E)), for VOS3 systems

Job Management Partner 1/Open Job Entry Description, User's Guide and Reference (9000-3-365(E)), for MVS systems

Job Management Partner 1/Open Job Entry Description, User's Guide and Reference (9000-3-366(E)), for OSIV/MSP systems

Job Management Partner 1/Open Job Entry for Midrange Computer Description and User's Guide (9000-3-367(E))

E.2 Conventions: Abbreviations for product names

This manual uses the following abbreviations for product names:

Abbreviation

Full name or meaning

JP1/AJS3

JP1/AJS3 - Manager

Job Management Partner 1/Automatic Job Management System 3 - Manager

JP1/AJS3 - Agent

Job Management Partner 1/Automatic Job Management System 3 - Agent

JP1/AJS3 - View

Job Management Partner 1/Automatic Job Management System 3 - View

JP1/AJS2

JP1/AJS2 - Manager

Job Management Partner 1/Automatic Job Management System 2 - Manager

JP1/AJS2 - Agent

Job Management Partner 1/Automatic Job Management System 2 - Agent

JP1/AJS2 - View

Job Management Partner 1/Automatic Job Management System 2 - View

JP1/AJS2 - Advanced Manager

Job Management Partner 1/Automatic Job Management System 2 - Advanced Manager#

JP1/AJS2 - Client Toolkit

Job Management Partner 1/Automatic Job Management System 2 - Client Toolkit#

JP1/AJS3 - Definition Assistant

Job Management Partner 1/Automatic Job Management System 3 - Definition Assistant

JP1/AJS3 for Enterprise Applications

Job Management Partner 1/Automatic Job Management System 3 for Enterprise Applications

JP1/AJS3 - Web Operation Assistant

Job Management Partner 1/Automatic Job Management System 3 - Web Operation Assistant

JP1/DH - AJE

Job Management Partner 1/Data Highway - Automatic Job Executor

JP1/DH - Server

Job Management Partner 1/Data Highway - Server

JP1/FTP

Job Management Partner 1/File Transmission Server/FTP

JP1/IM

JP1/IM - Manager

Job Management Partner 1/Integrated Management - Manager

JP1/IM - View

Job Management Partner 1/Integrated Management - View

JP1/IM - Central Console

Job Management Partner 1/Integrated Manager - Central Console#

JP1/IM - Central Scope

Job Management Partner 1/Integrated Manager - Central Scope#

JP1/OJE

Job Management Partner 1/Open Job Entry

JP1/OJE for Midrange Computer

Job Management Partner 1/Open Job Entry for Midrange Computer

JP1/OJE for VOS3

VOS3 Job Management Partner 1/Open Job Entry

JP1/SES

Job Management Partner 1/System Event Service

NNM

HP NNM

HP Network Node Manager Software version 7.5 or earlier

HP Network Node Manager Software Starter Edition version 7.5 or earlier

AIX

AIX 5L 5.3

AIX V6.1

AIX V7.1

HP-UX

HP-UX (IPF)

HP-UX 11i V2(IPF)

HP-UX 11i V3(IPF)

Linux

Linux 6.1 (x86)

Red Hat Enterprise Linux(R) Server 6.1 (32-bit x86)

Linux 6.1 (x64)

Red Hat Enterprise Linux(R) Server 6.1 (64-bit x86_64)

Linux 5.1 (x86)

Red Hat Enterprise Linux(R) 5.1 (x86)

Linux 5.1 (AMD/Intel 64)

Red Hat Enterprise Linux(R) 5.1 (AMD/Intel 64)

SAP BW

SAP Business Information Warehouse

SAP R/3

SAP R/3(R)

Solaris

Solaris 10(SPARC)

Solaris 11(SPARC)

# Version 7

In this manual, JP1/AJS is sometimes used generically, referring to JP1/AJS3 and JP1/AJS2.

UNIX is sometimes used generically, referring to HP-UX, Solaris, AIX and Linux.

E.3 Conventions: Acronyms

This manual also uses the following acronyms:

Acronym

Full name or meaning

ACL

Access Control List

DB

Database

DBMS

Database Management System

DNS

Domain Name System

EUC

Extended UNIX Code

FQDN

Fully Qualified Domain Name

FTP

File Transfer Protocol

GUI

Graphical User Interface

IME

Input Method Editor

IPF

Itanium(R) Processor Family

ISAM

Indexed Sequential Access Method

LAN

Local Area Network

MAPI

Messaging Application Programming Interface

MIB

Management Information Base

MIME

Multipurpose Internet Mail Extensions

NAT

Network Address Translator

NFS

Network File System

NIC

Network Interface Card

OS

Operating System

PDF

Portable Document Format

RDB

Relational Database

SMTP

Simple Mail Transfer Protocol

SNMP

Simple Network Management Protocol

SUP

Service Using Program

TCP/IP

Transmission Control Protocol/Internet Protocol

UAC

User Account Control

UNC

Universal Naming Convention

WAN

Wide Area Network

WOW64

Windows On Windows 64

WSDL

Web Services Description Language

E.4 Conventions: KB, MB, GB, and TB

This manual uses the following conventions:

1 KB (kilobyte) is 1,024 bytes.

1 MB (megabyte) is 1,024² bytes.

1 GB (gigabyte) is 1,024³ bytes.

1 TB (terabyte) is 1,024⁴ bytes.

E.5 Conventions: Meaning of "directory" and "folder"

As a general rule, Windows folder names are used in this manual if they are identical to UNIX directory names.

E.6 Conventions: Meaning of "member of the Administrators group"

The term member of the Administrators group in this manual refers to a user who is a member of the Administrators group on the local PC only. The privileges of local users, domain users, and Active Directory users are no different as long as these users are members of the Administrators group on the local PC.

E.7 Default installation folders of JP1/AJS3 for Windows

The default installation folders of JP1/AJS3 for Windows are as follows:

Default installation folders of JP1/AJS3 - Manager:

system-drive\Program Files#\HITACHI\JP1AJS2

and

system-drive\Program Files#\HITACHI\JP1AJS2CM

Default installation folder of JP1/AJS3 - Agent:

system-drive\Program Files#\HITACHI\JP1AJS2

Default installation folder of JP1/AJS3 - View:

system-drive\Program Files#\HITACHI\JP1AJS2V

#

For 64-bit versions of Windows, replace Program Files with Program Files (x86).

E.8 About the Start menu in Windows

In Windows Server 2012 or later, instead of using the Start menu, perform the operation as described below.

In Windows 8 or Windows Server 2012 (except Windows Server 2012 R2):

Right-click on the Start screen to display the All Apps screen.

In Windows 8.1 or Windows Server 2012 R2:

Click the down-pointing arrow icon to display the Apps screen.

E.9 Online manual

JP1/AJS3 - View comes with an online manual that you can read in browsers.

The HTML manual contains the same content as the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

In JP1/AJS3 - View, you can view the manual by choosing Help and then Contents. You can also press the F1 key to view the manual contents. Your Web browser must be associated with a file that has the extension htm; otherwise, the online manual will not be displayed correctly. If this happens, associate the htm file with the Web browser.

Cautionary note

Depending on the OS settings, the online manual might appear in the active window of the browser when you launch the manual from the Start menu.

E.10 Regular expressions available in JP1/AJS3

Regular expressions can be used in some items in dialog boxes and commands. For details about regular expressions in Windows, see the Job Management Partner 1/Base User's Guide. For details about regular expressions in UNIX, see your UNIX documentation.

The regular expressions that you can use when executing an event job on a Windows host depend on the JP1/Base settings. For details on setting regular expressions for event job execution, see the explanation about extending the available regular expressions in the Job Management Partner 1/Base User's Guide.

Searching may take a long time if you often use the regular expression .* (which means match any character or characters). In long messages, use .* only where necessary. In UNIX, you can use [^ ]* (repeat characters other than space characters) instead of .* when you want to find a match other than space characters. Using [^ ]* reduces the search time.

E.11 About the 3rd level and 4th level Kanji characters added in JIS 2004 (JIS X 0213:2004)

JP1/AJS3 cannot use the 3rd level and 4th level Kanji characters added in JIS 2004. If these characters are used, operation might not be performed correctly.

E.12 About NNM linkage

JP1/AJS3 supports linkage with the following products:

HP Network Node Manager Software version 6 or earlier

HP Network Node Manager Starter Edition Software version 7.5 or earlier

In this manual, these products are indicated as HP NNM.

Note that linkage with the following products is not supported:

HP Network Node Manager i Software v8.10

F. Glossary

abnormal end

A jobnet ends abnormally if one of the processes defined in the jobnet fails to execute properly. The jobnet is interrupted at that point and subsequent processes are not executed.

A job ends abnormally if it fails to execute properly. The process is interrupted at that point.

The embedded database system ends abnormally when an error causes its status to change from active to stopped or paused, without any intervention by the user. For details, see D. How the Embedded Database Operates in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

abnormal threshold

A value that is compared with a job's return code to evaluate whether the job ended normally or abnormally.

action job

A job that sends email, or sends events reporting the system status to JP1/ IM or the HP NNM.

agent host

A host that executes jobs on request from a manager host. JP1/AJS3 - Agent must be installed on the agent host, or since JP1/AJS3 - Manager also provides JP1/AJS3 - Agent functionality, JP1/AJS3 - Manager might be installed on the agent host.

The agent host executes the job on receipt of a job request from the manager host. At completion of the job, the agent host receives the execution result (return value) of the executable file and forwards it to the manager host.

AJS3 unit monitored object

An object for monitoring the status of root jobnets in JP1/AJS3. By defining the monitoring conditions in this object, you can then switch to monitoring mode and monitor the root jobnets.

AJS administrator

A user that has access permissions almost equivalent to superuser permissions for JP1/AJS3. Only one of the JP1/Base administrators in the JP1 administrators group can be designated as the AJS administrator. An ordinary user designated as the AJS administrator can perform such JP1/AJS3 system management operations as specifying the environment settings and starting and stopping services.

AJSPATH

An environment variable for defining the paths used by JP1/AJS3. When this environment variable is defined, you do not need to specify the full path when specifying a jobnet name in a command.

automatic retry

A function that automatically retries execution of a job if the executable file defined for the job terminates abnormally. Because jobs that have terminated abnormally due to a temporary error might be able to run normally when automatically retried, this function can improve the system availability.

backup box

A directory or a folder for storing backup files.

backup file

A file containing the units defined in JP1/AJS3.

base day

A date specified as the starting day of the month in the calendar information.

base time

The time that marks when a day ends and the next day begins in a JP1/AJS3 system. For example, if 8:00 a.m. is set as the base time, the previous day is regarded as lasting until 7:59 a.m.

calendar information

Information about open days and closed days for jobnet execution. You can define calendar information separately for each job group. The calendar information specifies the days on which jobnets in the job group can and cannot be executed. (When the processing cycle falls on a closed day, the jobnet can be executed on another day if a substitute schedule is defined.) For open days, you can specify the base day, base month, and base time.

closed day

A day on which jobnets are not executed. However, if Execute without shift is specified, the jobnet will be executed on that closed day.

cluster system

A system configured as multiple linked server systems, designed to continue operation even if one system fails. If a failure occurs in the server currently executing applications (primary node), the other standby server (secondary node) takes over and continues processing the applications. Therefore, a cluster system is also referred to as a node switching system.

The term cluster system can also mean load balancing based on parallel processing. In this manual, however, cluster system refers only to node-switching functionality for preventing interruption of application processing.

common user profile

A file containing the environment settings for JP1/AJS3 - View, accessible to all JP1 users. The system administrator saves the common user profile in JP1/AJS3 - Manager. JP1 users can download this file, enabling the same JP1/AJS3 - View environment to be set for all JP1 users.

A common user profile is useful when a large number of JP1 users will be using JP1/AJS3 - View in the same environment.

compatible ISAM configuration

A system configuration in which JP1/AJS3 information is managed exclusively by the ISAM database.

This configuration is offered to help users migrate from JP1/AJS2 version 8 or earlier. It can restrict to the same degree as in previous versions, the use of resources such as hard disk and memory. However, from version 9 only a subset of the new features offered is provided.

correlation ID

Information for identifying sent and received messages. The correlation ID is received in the character code set specified by the sender.

custom job

A predefined job for executing a task with a specific purpose. JP1/AJS3 provides standard custom jobs such as file transfer and job requests to a mainframe. In addition, you can register your own frequently used jobs as custom jobs. When registering a custom job, you can represent it by creating an icon with a special shape and design, and you can create a dialog box for entering job information.

To use a custom job, the requisite program for the job must be installed.

Daily Schedule window

A window that displays each day's execution schedules, execution status, and execution results.

data collection tool

These tools are provided by JP1 for batch collection of log data and other information required to investigate problems. In addition to problems in JP1/AJS3, problems might occur in the OS or user programs or as the result of operational mistakes. The data collection tools collect JP1/AJS3 log data and other information, such as OS log data, at the same time.

default queue

A queue created in an agent host for executing jobs. You must always create a default queue.

When you submit a job for execution, if you specify an agent host name as the destination, the job will be submitted to the default queue of the specified agent host.

dependent job

A job executed when the judgment result of a judgment job is true.

dependent jobnet

A jobnet executed when the judgment result of a judgment job is true.

disaster recovery

Disaster recovery refers to measures that are taken when there are unexpected occurrences such as system shutdown due to a large-scale disaster.

JP1/AJS3 supports a disaster recovery operation that copies JP1/AJS3 data on the shared disk to a shared disk at a remote site. If the JP1/AJS3 system fails because of an event such as a disaster, the JP1/AJS3 system at the remote site can continue operation by using the copied data. The disk copy and mirroring functionality of hardware is used to copy data between shared disks.

embedded database

The standard database of JP1/AJS3. An embedded database offers high reliability, and is well suited to large-scale systems that handle large quantities of information.

embedded database administrator (database administrator)

A user authorized to assign and cancel various permissions for an embedded database (a user with DBA permissions).

Database administrators are managed within an embedded database.

embedded database operation commands

A generic term for commands whose name begins with ajsembdb.

embedded database service

A service that provides the environment for using the embedded database in Windows. This service must be started before you can use the embedded database. The name of the embedded database service is JP1/AJS3 Database setup-identifier.

embedded database system administrator

The owner of an embedded database practical directory and embedded database file system areas (data area and system area). The embedded database system administrator can execute commands for an embedded database.

The OS manages embedded database system administrators.

end with warning

A status indicating that a jobnet finished, but some of the processes defined in the jobnet were executed incorrectly. The jobnet continues to the end without interruption.

This ending method is used when an error is not so serious as to terminate the jobnet.

environment setting parameter

A parameter for defining the information required to operate JP1/AJS3, written in an environment settings file. With these parameters, you can specify the directory in which information about JP1/AJS3 units is stored, whether to output syslog messages, and other such preferences.

environment settings file

A file containing the settings required to operate JP1/AJS3, such as the scheduler service environment and job execution environment.

event

A specific event, such as email reception or file update, that occurred in the system. Events can be used to start a job or jobnet, and can be monitored using an event job.

event job

A job that monitors specific events occurring in the system. When an event job is initiated, it starts monitoring for file updates, incoming messages, or other specified events.

execution agent

The logical name of an agent host that executes jobs or jobnets. Based on the agent information defined in the manager host, the manager maps the execution agent specified in the job or jobnet to the physical host name of the agent host, and distributes the job or jobnet accordingly.

execution agent group

A group of execution agents configured to realize load distribution. The manager distributes jobs among the execution agents according to their assigned priorities.

execution agent restriction

A function that suppresses execution of jobs on an execution agent that the administrator has not permitted to execute the jobs. The execution agents permitted to execute jobs can be set for each unit.

When the execution agent profile is enabled, this function checks for whether the execution agent is permitted to execute jobs at the following times:

When a unit is defined in JP1/AJS3 - View

When the ajschkdef command is used to conduct a definition pre-check

When a job is executed

execution ID

A number assigned to an execution schedule of the uppermost jobnet.

execution-locked resource

A means of preventing multiple jobs from executing at the same time, by specifying the same resource name (execution-locked resource name) for each job.

fixed execution registration

A method of registering a jobnet so that it starts and runs at a predetermined date and time calculated by the system from schedule definitions.

fixed schedule

A schedule set by absolute times when a jobnet is registered for fixed execution.

HP NNM

A suite of integrated network management tools from Hewlett-Packard Co. for managing network configuration, performance, and failures.

immediate execution registration

A method for starting and processing a jobnet immediately after registering it for execution.

ISAM database

The database that manages the execution environment for QUEUE jobs and submit jobs. Data is indexed using the Indexed Sequential Access Method (ISAM) and is managed in the database. The ISAM database is provided as standard with JP1/Base.

job

A group of commands, shell scripts, or Windows executable files.

job execution environment

A job execution environment consists of a JP1/AJS3 manager and agents.

The job execution environment for the manager is used to manage the definition information for execution agents (such as the maximum number of concurrently executable jobs and job transfer restriction status), job distribution method, and job execution results.

The job execution environment for the agent is used mainly to manage how a job is executed.

These job execution environments are managed by using a database and environment setting parameters.

When QUEUE jobs and submit jobs are used, the ISAM database and environment setting parameters are used as the job execution environment for the QUEUE jobs and submit jobs.

Note that queueless jobs are managed in the queueless job execution environment.

job group

A folder for classifying and managing jobnets.

job network element

The generic term for these elements is unit.

jobnet

A set of jobs associated in execution order. When a jobnet is executed, the jobs in the jobnet are automatically executed in their predetermined order.

jobnet connector

A unit for controlling the execution order of root jobnets. A jobnet connector establishes connections between root jobnets and controls their execution order by having connected generations wait for their counterparts to start or finish.

Jobnet Editor window

A window in which you can create new jobnets or edit existing jobnets.

Jobnet Monitor window

A window that displays the execution status or detailed execution results of jobnets or jobs. You can manipulate jobnets or jobs in this window.

JP1 event

Event information that is reported to JP1/Base when an event occurs in the system. JP1 events are reported to other systems via JP1/Base.

JP1 permission level

A name that indicates the operations that a JP1 user is allowed to perform on management targets (resources) defined in JP1/AJS3, including applications and events. Use JP1/Base to define JP1 permission levels.

JP1 resource group

A name given to a specific JP1/AJS3 unit for controlling access by JP1 users to that unit.

JP1 user

A user designation for using JP1/AJS3 or JP1/IM - Manager. Each JP1 user is registered in the authentication server, which controls the user's access to management targets (resources).

JP1/AJS3 - Definition Assistant

This program allows you to register a large amount of JP1/AJS3 definition information edited using an Excel template into a manager host, or to retrieve JP1/AJS3 definition information from a manager host to an Excel template. The Excel templates provided by JP1/AJS3 - Definition Assistant are called definition management templates. With a definition management template in the spreadsheet format, you can enter or edit definition information efficiently by using automatic filling, automatic filtering, and other Excel functionalities.

JP1/AJS3 - Print Option

This program allows you to display or print jobnet or schedule information formatted as needed (for example, as jobnet definition information, an execution schedule table, or an execution result confirmation table).

You can also output jobnet or schedule information in CSV format so that you can edit the information.

JP1/AJS3 Console Agent

A JP1/AJS3 component that regularly monitors the status of objects (root jobnets) on the local host, specified in JP1/AJS3 Console Manager. Any change in status is notified to JP1/AJS3 Console Manager.

JP1/AJS3 Console Manager

A JP1/AJS3 component that stores definitions about monitored objects defined in JP1/AJS3 Console View, and gets status information about monitored objects by issuing requests to JP1/AJS3 Console Agent.

JP1/AJS3 Console View

A JP1/AJS3 component that allows you to define objects to be monitored, using a graphical user interface. The definitions are stored in JP1/AJS3 Console Manager. Using JP1/AJS3 Console View, you can view and monitor the status of target objects notified by JP1/AJS3 Console Agent to JP1/AJS3 Console Manager. You need to log in to JP1/AJS3 Console Manager before using JP1/AJS3 Console View.

JP1/AJS3 for Enterprise Applications

A program that allows you to control jobs in an R/3 system from another system. You can submit, delete, and monitor R/3 jobs.

R/3 jobs can be executed automatically from JP1/AJS3 if you register them as custom jobs for JP1/AJS3 for Enterprise Applications when you define a JP1/AJS3 jobnet.

JP1/AJS3 for Enterprise Applications is the successor to JP1/Application Manager for R/3.

JP1/Base

A program that provides the event service function. JP1/Base allows you to control the order in which services start, and it lets you send and receive JP1 events. JP1/Base is a prerequisite program for JP1/IM and JP1/AJS3. When JP1/IM is deployed in a system with JP1/AJS3, JP1/Base provides functionality for restricting operations by JP1 users.

JP1/DH - AJE

A program that automatically sends data to and receives data from JP1/DH - Server.

JP1/FTP

A program for performing file transfer tasks efficiently, including file transfer/reception linked to application execution, scheduled file transfer, and automated program execution following file reception. JP1/FTP supports monitoring of transfer status, enhancing file transfer reliability.

JP1/IM

A program for centrally monitoring a distributed system. Using the windows in JP1/IM - View, the system administrator can monitor JP1 events, which provide information about job execution status or problems in the distributed system.

JP1/NQSEXEC

A program for executing routine batch processing on a distributed system and for running batch jobs efficiently.

JP1/OJE for Midrange Computer

A program for submitting batch jobs to AS/400 from a Windows or UNIX host, or for submitting batch jobs from AS/400 to a Windows or UNIX host.

JP1/OJE for VOS3

A program that links with JP1/AJS3 for executing and monitoring batch jobs between a Windows or UNIX system and a mainframe (VOS3).

JP1/Script

A program for creating and executing scripts (batch files) that control jobs on Windows. Job operation can be automated by linking JP1/Script with JP1/AJS3.

JP1/Software Distribution

A general term for a system that distributes software and manages clients using batch operations over a network.

By linking with JP1/AJS3 using the JP1/Software Distribution command interface, the user can automate software distribution and other tasks.

judgment job

A job that executes a dependent unit if the judgment result of a specified condition is true.

judgment value

A value for evaluating whether a job ended normally or abnormally.

kill

To forcibly terminate a unit being executed.

When the root jobnet is killed, all the jobs being executed are killed and the jobnets are terminated.

list file

A file containing a list of extracts from sent and received mail.

logical host

A logical server that provides the JP1 execution environment for running a cluster system. If a failure occurs on the primary node, the logical host is switched to the secondary node.

Each logical host has a unique IP address. At failover, the secondary node inherits the IP address. Thus, if the physical server fails, clients can access the secondary node using the same IP address. To the clients, it appears that one server is operating continuously.

macro variable

A variable used to pass information from one job to another job during execution.

A macro variable name and passing information (or for an event job, a passing information name) are specified during unit definition. A macro variable can be used during job execution by specifying the name of the macro variable in the succeeding job.

macro variable name

A character string in ?AJS2xxxxx? format that indicates the name of a macro variable. If a macro variable name is specified during the definition of a unit, the macro variable set in the preceding job can be used during job execution.

mail filtering application

A program or a shell script that converts email formats.

A mail filtering application is required to convert the character set when exchanging email in formats other than RFC822.

mail receipt parameter file

A file containing the mail receipt monitoring parameters defined by the user. The file extension is .prm. This file is created automatically when the user defines a Receive Email Event job.

mail send parameter file

A file containing the mail send parameters defined by the user. The file extension is .prm. This file is created automatically when the user defines a Send Email Action job.

manager host

A host that manages jobnet definitions and schedule information in a database, and requests agent hosts to execute jobs. You must install JP1/AJS3 - Manager on the manager host.

The manager host creates jobnet execution schedules from the defined schedule information. At jobnet run time, the manager host starts the executable files defined as jobs, forwards the job definitions to an agent host, and requests the agent host to execute the jobs. When execution completes, the execution result is received by the agent host and the database is updated. Based on the updated information, the manager host executes a succeeding job or schedules the next execution of the jobnet.

manager job group

A job group for monitoring JP1/AJS3 - Manager applications from another JP1/AJS3 - Manager.

manager jobnet

A jobnet for monitoring JP1/AJS3 - Manager applications from another JP1/AJS3 - Manager.

MAPI (Messaging Application Programming Interface)

The standard messaging API for Windows.

max. shiftable days

A set number of days within which to shift the next scheduled execution date when the recalculated date falls on a closed day.

maximum number of concurrently executable jobs

The maximum number of jobs that can be executed concurrently.

message ID

One item in an MQSeries message descriptor. Message IDs are stored in the character set specified by the sender. They can be used as storage locations to help identify messages.

MIME (Multipurpose Internet Mail Extensions)

An extended SMTP function used for sending and receiving non-ASCII data.

MIME specifies various procedures, such as how data is to be transmitted between email systems, and the format of control messages for email transfer.

Monthly Schedule window

A window that displays each month's execution schedules and execution results.

nested jobnet

A jobnet defined within another jobnet.

node switching system

See cluster system.

normal end

A normal end of a jobnet occurs when all the processes defined in the jobnet have executed correctly and the jobnet has completed.

A normal end of a job occurs when the job has executed correctly.

open day

A day when jobnets run.

passing information

Values specified for macro variables during registration for execution, event IDs, event issuance dates, and other information (values) that is dynamically set in macro variables and passed to succeeding jobs.

passing information name

A variable name indicating the event information to be received by an event job.

Variable names that can be used for this purpose include EVID (event ID) and EVDATE (event issuance date). These variable names are specified during the definition of an event job.

physical host

An environment unique to each of the servers (nodes) in a cluster system. When a secondary node takes over from the primary node, the environment of the physical host remains unchanged and is not inherited by the other server.

planned execution registration

A method of registering a jobnet so that it starts and executes according to schedule definitions.

planning group

A unit for switching execution among multiple root jobnets in a planned manner. Directly under a planning group, you can create a number of root jobnets, each defined differently and with differing execution schedules. This enables the root jobnets to be executed automatically in turn, according to the set schedules.

preceding job

A job executed immediately before another job or jobnet.

preceding jobnet

A jobnet executed immediately before another job or jobnet.

processing cycle

The interval between one execution start date and the next execution start date of a jobnet. By defining a processing cycle, you can execute a jobnet at regular intervals.

queue

An area for temporarily keeping jobs registered for execution. Jobs are submitted to the queue in order of registration, and are sequentially transferred for execution to the agent connected to that queue.

The queue controls the number of jobs that the agent executes concurrently, thereby preventing any degradation in performance caused by a large number of jobs being executed at the same time.

queueless job

A job transferred directly from the manager to an agent host for execution, without using a queue. Queueless jobs simplify processing because they are not managed in a queue by the job execution control. As a result, they offer better performance than ordinary queued jobs, allowing more jobs to be executed within a given period of time. However, job execution control functions such as execution agent names and execution agent groups are not available with queueless jobs.

You can define PC jobs and Unix jobs in a jobnet as queueless jobs by specifying Queueless Agent as the execution service.

Unless otherwise indicated, the descriptions in this manual apply to jobs for which Standard is specified as the execution service.

queueless job execution environment

A queueless job execution environment consists of execution environments for the JP1/AJS3 manager (scheduler service and queueless file transfer service) and queueless agents (queueless agent services). The execution of queueless jobs is managed by using the environment setting parameters for the job execution environment.

Note that the job execution environment must be set up by using the ajsqlsetup command before environment setting parameters are set.

queuing job

A job submitted directly to a queue and waiting to be executed.

recovery job

A job to be executed when a job or jobnet ends abnormally.

recovery jobnet

A jobnet to be executed when a job or jobnet ends abnormally.

schedule by days from start

A schedule defined for recalculating the next scheduled execution date, using as the base day the next scheduled execution date determined from the execution start time, processing cycle, and substitute schedule for closed days.

schedule information file

A text file containing schedule information parameters, entered by command when setting fixed execution registration for a jobnet.

schedule rule

Jobnet information such as execution start time and processing cycle. Up to 144 schedule rules can be defined for a single jobnet.

scheduler service

A service that manages the schedules for jobnet execution, and executes processes according to those schedules. Each scheduler service manages all the units in the root job group whose name matches the scheduler service name.

Multiple scheduler services can be activated in a single manager. This allows root job groups to be managed individually. For example, if you start a separate scheduler service for each application, each scheduler service can run its specific application (jobnet and jobs) in parallel, independently of the other scheduler services.

shift days

A set number of days within which to determine a substitute date when the next execution date falls on a closed day.

shutdown status

A situation in which a jobnet fails to start or end due to an error, and the execution status or the next scheduled execution cannot be verified. If this happens, you must cancel and then re-register the jobnet for execution.

SMTP (Simple Mail Transfer Protocol)

A protocol, generally used in UNIX networks, for transferring ASCII data by TCP/IP between heterogeneous systems.

standard configuration

A system configuration in which JP1/AJS3 information is managed by the embedded database.

Unless otherwise indicated, the descriptions in this manual relate to a system in a standard configuration.

Note that the ISAM database is still used to store some information related to QUEUE jobs and submit jobs.

start condition

A definition of the conditions under which a jobnet starts when the jobnet is driven by a specific event.

subject

A character string written in the subject line of an email message. Non-ASCII characters are supported in JP1/AJS3, but might not be supported in connected email systems.

submit

To request the system to execute a job.

submit job

A standard job registered using the jpqjobsub command.

substitute schedule

A means of executing a jobnet on a different day when the next execution date, determined from the jobnet schedule, falls on a closed day.

succeeding job

A job executed immediately after another job or jobnet.

succeeding jobnet

A jobnet executed immediately after another job or jobnet.

suspend

To suppress the execution of the root jobnet and lower units.

When you change a definition under a root jobnet that has been registered for execution, you should suspend the root jobnet to prevent erroneous operation such as the execution control processing running with the old definition. By suspending the root jobnet, the redefinition processing can be synchronized with the execution control processing.

threshold

A value for evaluating the termination status of a job. You can define an abnormal threshold and a warning threshold for each job.

timeout period

A time interval after which an executed job is forcibly terminated if there was no response from the job or if it failed to complete during the specified period.

TP1/Server Base

Software for distributing transaction processing and server processing in an open system. JP1/AJS2 uses TP1/Server Base transaction processing.

unit

A generic term for any job network element.

unit definition parameter file

A text file containing unit definition parameters, entered by command when defining the units.

unit ID

A unique number allocated to a unit.

unit whose end is being waited for

A unit specified as a wait condition of another unit. The unit for which the unit whose end is being waited for is specified as a wait condition starts when the unit whose end is being waited for terminates.

unit with wait condition

A unit for which another unit (unit whose end is being waited for) is specified as a wait condition. The unit with the wait condition starts execution when the associated unit (unit whose end is being waited for) terminates.

virtual machine

A virtual computer system (host) created on a physical host to run an OS is called a virtual machine. Multiple virtual machines can operate on a single physical host to execute multiple processes simultaneously or to run different OSs concurrently.

By replicating a virtual machine that has already been set up, you can easily increase hosts that have the same environment.

wait condition

A condition set for a unit that allows the execution order of units across jobnets to be controlled. A unit with another unit specified as a wait condition starts execution when the associated unit terminates.

warning threshold

A value for evaluating whether a job ended with a warning.

Windows Messaging

A facility that provides an interface for sending and receiving email. Using Windows Messaging, you can manage, access, and share a variety of information such as data received from an online service.

Index

A

abbreviations for products[1]

abnormal end[1]

abnormal threshold[1]

About the 3rd level and 4th level Kanji characters added in JIS 2004 (JIS X 0213:2004)[1]

About the Start menu in Windows[1]

acronyms[1]

action job[1]

agent host[1]

AJS3 unit monitored object[1]

AJS administrator[1]

AJSPATH[1]

automatic retry[1]

B

backup box[1]

backup file[1]

base day[1]

base time[1]

C

calendar information[1]

closed day[1]

cluster system[1]

common user profile[1]

conventions

abbreviations for products[1]

acronyms[1]

fonts and symbols[1]

KB, MB, GB, and TB[1]

meaning of directory and folder[1]

meaning of member of Administrators group[1]

version numbers[1]

correlation ID[1]

custom job[1]

D

Daily Schedule window[1]

database administrator[1]

data collection tool[1]

default queue[1]

defaults

installation folders of JP1/AJS3 for Windows[1]

dependent job[1]

dependent jobnet[1]

directory

term defined[1]

disaster recovery[1]

E

embedded database

administrator, glossary definition[1]

glossary definition[1]

operation commands, glossary definition[1]

service, glossary definition[1]

system administrator, glossary definition[1]

end with warning[1]

environment setting parameters

glossary definition[1]

environment settings file[1]

error codes returned from access requests for an embedded database file system[1]

event[1]

event job[1]

execution agent[1]

execution agent group[1]

execution agent restriction[1]

execution ID[1]

execution-locked resource[1]

F

fixed execution registration[1]

fixed schedule[1]

folder

term defined[1]

font conventions[1]

G

GB meaning[1]

Glossary[1]

H

HP NNM[1]

term defined[1]

I

immediate execution registration[1]

installation folders

default for JP1/AJS3 for Windows[1]

ISAM

compatible ISAM configuration, glossary definition[1]

database, glossary definition[1]

J

job[1]

job execution environment[1]

job group[1]

jobnet connector[1]

Jobnet Editor window[1]

Jobnet Monitor window[1]

jobnets

glossary definition[1]

job network element[1]

JP1/AJS3 Console Agent[1]

JP1/AJS3 Console Manager[1]

JP1/AJS3 Console View[1]

JP1/AJS3 - Definition Assistant[1]

JP1/AJS3 for Enterprise Applications[1]

JP1/AJS3 - Print Option[1]

JP1/Base[1]

JP1/DH - AJE[1]

JP1/FTP[1]

JP1/IM[1]

JP1/NQSEXEC[1]

JP1/OJE for Midrange Computer[1]

JP1/OJE for VOS3[1]

JP1/Script[1]

JP1/Software Distribution[1]

JP1 event[1]

JP1 permission level[1]

JP1 resource group[1]

JP1 user[1]

judgment job[1]

judgment value[1]

K

KB meaning[1]

kill[1]

L

list file[1]

logical host[1]

M

macro variable[1]

macro variable name[1]

mail filtering application[1]

mail receipt parameter file[1]

mail send parameter file[1]

manager host[1]

manager job group[1]

manager jobnet[1]

MAPI[1]

max. shiftable days[1]

maximum number of concurrently executable jobs[1]

MB meaning[1]

member of the Administrators group

term defined[1]

message ID[1]

MIME[1]

Monthly Schedule window[1]

N

nested jobnet[1]

NNM linkage

supported products[1]

node switching system[1]

normal end[1]

O

online manual

contents[1]

open day[1]

P

passing information[1]

passing information name[1]

physical host[1]

planned execution registration[1]

planning group[1]

preceding job[1]

preceding jobnet[1]

processing cycle[1]

Q

queue[1]

queueless job[1]

queueless job execution environment[1]

queuing job[1]

R

reason codes of messages beginning with KAVU[1]

recovery job[1]

recovery jobnet[1]

Reference Material for This Manual[1]

regular expressions available in JP1/AJS3[1]

Related publications[1]

return codes of system calls[1]

revisions

07-00[1]

07-50[1]

08-00[1]

09-00[1]

10-00[1]

10-10[1]

10-50[1]

S

schedule by days from start[1]

schedule information file[1]

scheduler service[1]

schedule rule[1]

shift days[1]

shutdown status[1]

SMTP[1]

standard configuration[1]

start condition[1]

subject[1]

submit[1]

submit job[1]

substitute schedule[1]

succeeding job[1]

succeeding jobnet[1]

suspend[1]

symbol conventions[1]

system error numbers of messages KAVU2xxx-E and KAVU2xxx-W[1]

T

TB meaning[1]

threshold[1]

timeout period[1]

TP1/Server Base[1]

U

unit[1]

unit definition parameter file[1]

unit ID[1]

unit whose end is being waited for[1]

unit with wait condition[1]

V

version number conventions[1]

version revisions[1]

virtual machine[1]

W

wait condition[1]

warning threshold[1]

Windows Messaging[1]