JP1 Version 11 JP1/Automatic Job Management System 3 Messages

3021-3-B21-20(E)

Notices

Relevant program products

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

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

P-2A12-3KBL JP1/Automatic Job Management System 3 - Manager version 11-50

The above product includes the following:

P-CC2A12-4KBL JP1/Automatic Job Management System 3 - Manager version 11-50 (For Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2)

P-CC2912-39BL JP1/Automatic Job Management System 3 - Web Console version 11-50 (For Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2)

P-CC8212-39BL JP1/Automatic Job Management System 3 - Web Console version 11-50 (For Linux 6.1(x64) or later, Linux 7.1, Oracle Linux 6(x64), Oracle Linux 7, SUSE Linux 12, CentOS 6(x64), CentOS 7)

P-CC2A12-3NBL JP1/Automatic Job Management System 3 - Print Option Manager version 11-10 (For Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2)

JP1/Automatic Job Management System 3 - Manager (For HP-UX):

P-1J12-3KBL JP1/Automatic Job Management System 3 - Manager version 11-50

The above product includes the following:

P-CC1J12-4KBL JP1/Automatic Job Management System 3 - Manager version 11-50 (For HP-UX(IPF))

P-CC2912-39BL JP1/Automatic Job Management System 3 - Web Console version 11-50 (For Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2)

P-CC8212-39BL JP1/Automatic Job Management System 3 - Web Console version 11-50 (For Linux 6.1(x64) or later, Linux 7.1, Oracle Linux 6(x64), Oracle Linux 7, SUSE Linux 12, CentOS 6(x64), CentOS 7)

P-CC1J12-3NBL JP1/Automatic Job Management System 3 - Print Option Manager version 11-10 (For HP-UX(IPF))

JP1/Automatic Job Management System 3 - Manager (For Solaris):

P-9D12-3KBL JP1/Automatic Job Management System 3 - Manager version 11-50

The above product includes the following:

P-CC9D12-4KBL JP1/Automatic Job Management System 3 - Manager version 11-50 (For Solaris 11(SPARC), Solaris 10(SPARC))

P-CC2912-39BL JP1/Automatic Job Management System 3 - Web Console version 11-50 (For Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2)

P-CC8212-39BL JP1/Automatic Job Management System 3 - Web Console version 11-50 (For Linux 6.1(x64) or later, Linux 7.1, Oracle Linux 6(x64), Oracle Linux 7, SUSE Linux 12, CentOS 6(x64), CentOS 7)

P-CC9D12-3NBL JP1/Automatic Job Management System 3 - Print Option Manager version 11-10 (For Solaris 11(SPARC), Solaris 10(SPARC))

JP1/Automatic Job Management System 3 - Manager (For AIX):

P-1M12-3KBL JP1/Automatic Job Management System 3 - Manager version 11-50

The above product includes the following:

P-CC1M12-4KBL JP1/Automatic Job Management System 3 - Manager version 11-50 (For AIX)

P-CC2912-39BL JP1/Automatic Job Management System 3 - Web Console version 11-50 (For Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2)

P-CC8212-39BL JP1/Automatic Job Management System 3 - Web Console version 11-50 (For Linux 6.1(x64) or later, Linux 7.1, Oracle Linux 6(x64), Oracle Linux 7, SUSE Linux 12, CentOS 6(x64), CentOS 7)

P-CC1M12-3NBL JP1/Automatic Job Management System 3 - Print Option Manager version 11-10 (For AIX)

JP1/Automatic Job Management System 3 - Manager (For Linux):

P-8112-3KBL JP1/Automatic Job Management System 3 - Manager version 11-50

The above product includes the following:

P-CC8112-4KBL JP1/Automatic Job Management System 3 - Manager version 11-50 (For Linux 6.1(x64) or later, Linux 7.1, Oracle Linux 6(x64), Oracle Linux 7, SUSE Linux 12, CentOS 6(x64) ,CentOS 7)

P-CC2912-39BL JP1/Automatic Job Management System 3 - Web Console version 11-50 (For Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2)

P-CC8212-39BL JP1/Automatic Job Management System 3 - Web Console version 11-50 (For Linux 6.1(x64) or later, Linux 7.1, Oracle Linux 6(x64), Oracle Linux 7, SUSE Linux 12, CentOS 6(x64), CentOS 7)

P-CC8112-3NBL JP1/Automatic Job Management System 3 - Print Option Manager version 11-10 (For Linux 6.1(x64) or later, Linux 7.1, Oracle Linux 6(x64), Oracle Linux 7, SUSE Linux 12, CentOS 6(x64) ,CentOS 7)

JP1/Automatic Job Management System 3 - Agent (For Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2):

P-2A12-33BL JP1/Automatic Job Management System 3 - Agent version 11-50

JP1/Automatic Job Management System 3 - Agent (For HP-UX(IPF)):

P-1J12-33BL JP1/Automatic Job Management System 3 - Agent version 11-50

JP1/Automatic Job Management System 3 - Agent (For Solaris 11 (SPARC) and Solaris 10 (SPARC)):

P-9D12-33BL JP1/Automatic Job Management System 3 - Agent version 11-50

JP1/Automatic Job Management System 3 - Agent (For AIX):

P-1M12-33BL JP1/Automatic Job Management System 3 - Agent version 11-50

JP1/Automatic Job Management System 3 - Agent (For Linux 6.1(x64) or later, Linux 7.1, Oracle Linux 6(x64), Oracle Linux 7, SUSE Linux 12, CentOS 6(x64) ,CentOS 7):

P-8112-33BL JP1/Automatic Job Management System 3 - Agent version 11-50

JP1/Automatic Job Management System 3 - Agent Minimal Edition (For Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2):

P-2A12-38BL JP1/Automatic Job Management System 3 - Agent Minimal Edition version 11-50

JP1/Automatic Job Management System 3 - Agent Minimal Edition (For Linux 6.1(x64) or later, Linux 7.1, Oracle Linux 6(x64), Oracle Linux 7, SUSE Linux 12, CentOS 6(x64) ,CentOS 7):

P-8112-38BL JP1/Automatic Job Management System 3 - Agent Minimal Edition version 11-50

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

P-2A12-34BL JP1/Automatic Job Management System 3 - View version 11-50

The above product includes the following:

P-CC2A12-44BL JP1/Automatic Job Management System 3 - View version 11-10 (For Windows Server 2016, Windows 10, Windows 8.1, Windows 8, Windows Server 2012 R2, Windows Server 2012, Windows 7, Windows Server 2008 R2)

P-CC2A12-3MBL JP1/Automatic Job Management System 3 - Print Option version 11-50 (For Windows Server 2016, Windows 10, Windows 8.1, Windows 8, Windows Server 2012 R2, Windows Server 2012, Windows 7, Windows Server 2008 R2)

JP1/Base (For Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2):

P-2A2C-6LBL JP1/Base version 11-50

JP1/Base (For HP-UX(IPF)):

P-1J2C-6LBL JP1/Base version 11-50

JP1/Base (For Solaris 11 (SPARC) and Solaris 10 (SPARC)):

P-9D2C-6LBL JP1/Base version 11-50

JP1/Base (For AIX):

P-1M2C-6LBL JP1/Base version 11-50

JP1/Base (For Linux 6.1(x64) or later, Linux 7.1, Oracle Linux 6(x64), Oracle Linux 7, SUSE Linux 12, CentOS 6(x64) ,CentOS 7):

P-812C-6LBL JP1/Base version 11-50

Trademarks

HITACHI, JP1, Job Management Partner 1, uCosminexus, HiRDB are either trademarks or registered trademarks of Hitachi, Ltd. in Japan and other countries.

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

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, 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 is either a registered trademark or a trademark 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.

Microsoft Office and Outlook are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or 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, Windows Server 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.

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

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

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

SUSE is a registered trademark or a trademark of SUSE LLC in the United States and other countries.

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.

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

The following program products contain some parts whose copyrights are reserved by Oracle and/or its affiliates: P-9D12-3KBL, P-9D12-33BL, and P-9D2C-6LBL.

The following program products contain some parts whose copyrights are reserved by UNIX System Laboratories, Inc.: P-9D12-3KBL, P-9D12-33BL, and P-9D2C-6LBL.

This product includes RSA BSAFE Cryptographic software of EMC Corporation.

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

Portions of this software were originally based on the following:

- software copyright (c) 1999, IBM Corporation., http://www.ibm.com.

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

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

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

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

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

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

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

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

1. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)

2. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)

3. This product includes software written by Tim Hudson (tjh@cryptsoft.com)

4. This product includes the OpenSSL Toolkit software used under OpenSSL License and Original SSLeay License. OpenSSL License and Original SSLeay License are as follow:

LICENSE ISSUES

==============

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of

the OpenSSL License and the original SSLeay license apply to the toolkit.

See below for the actual license texts. Actually both licenses are BSD-style

Open Source licenses. In case of any license issues related to OpenSSL

please contact openssl-core@openssl.org.

OpenSSL License

---------------

/* ====================================================================

* Copyright (c) 1998-2016 The OpenSSL Project. All rights reserved.

*

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

*

* 1. Redistributions of source code must retain the above copyright

* notice, this list of conditions and the following disclaimer.

*

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in

* the documentation and/or other materials provided with the

* distribution.

*

* 3. All advertising materials mentioning features or use of this

* software must display the following acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

*

* 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to

* endorse or promote products derived from this software without

* prior written permission. For written permission, please contact

* openssl-core@openssl.org.

*

* 5. Products derived from this software may not be called "OpenSSL"

* nor may "OpenSSL" appear in their names without prior written

* permission of the OpenSSL Project.

*

* 6. Redistributions of any form whatsoever must retain the following

* acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit (http://www.openssl.org/)"

*

* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY

* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR

* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;

* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,

* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED

* OF THE POSSIBILITY OF SUCH DAMAGE.

* ====================================================================

*

* This product includes cryptographic software written by Eric Young

* (eay@cryptsoft.com). This product includes software written by Tim

* Hudson (tjh@cryptsoft.com).

*

*/

Original SSLeay License

-----------------------

/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)

* All rights reserved.

*

* This package is an SSL implementation written

* by Eric Young (eay@cryptsoft.com).

* The implementation was written so as to conform with Netscapes SSL.

*

* This library is free for commercial and non-commercial use as long as

* the following conditions are aheared to. The following conditions

* apply to all code found in this distribution, be it the RC4, RSA,

* lhash, DES, etc., code; not just the SSL code. The SSL documentation

* included with this distribution is covered by the same copyright terms

* except that the holder is Tim Hudson (tjh@cryptsoft.com).

*

* Copyright remains Eric Young's, and as such any Copyright notices in

* the code are not to be removed.

* If this package is used in a product, Eric Young should be given attribution

* as the author of the parts of the library used.

* This can be in the form of a textual message at program startup or

* in documentation (online or textual) provided with the package.

*

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

* 1. Redistributions of source code must retain the copyright

* notice, this list of conditions and the following disclaimer.

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in the

* documentation and/or other materials provided with the distribution.

* 3. All advertising materials mentioning features or use of this software

* must display the following acknowledgement:

* "This product includes cryptographic software written by

* Eric Young (eay@cryptsoft.com)"

* The word 'cryptographic' can be left out if the rouines from the library

* being used are not cryptographic related :-).

* 4. If you include any Windows specific code (or a derivative thereof) from

* the apps directory (application code) you must include an acknowledgement:

* "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"

*

* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND

* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE

* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS

* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

* SUCH DAMAGE.

*

* The licence and distribution terms for any publically available version or

* derivative of this code cannot be changed. i.e. this code cannot simply be

* copied and put under another distribution licence

* [including the GNU Public Licence.]

*/

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

This product includes software developed by Andy Clark.

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 SQL Server

Microsoft(R) SQL Server

Microsoft(R) SQL Server Enterprise Edition

MSMQ

Microsoft(R) Message Queue Server

Outlook

Outlook 2007

Microsoft(R) Office Outlook(R) 2007

Outlook 2010

Microsoft(R) Office Outlook(R) 2010

Outlook 2013

Microsoft(R) Office Outlook(R) 2013

Outlook Express

Microsoft(R) Outlook(R) Express

Windows 10

Windows(R) 10 Enterprise

Windows(R) 10 Pro

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 2008

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 Server 2016

Microsoft(R) Windows Server(R) 2016 Datacenter

Microsoft(R) Windows Server(R) 2016 Standard

Windows is sometimes used generically, referring to Windows Server 2016, Windows 10, Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008.

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

Nov. 2017: 3021-3-B21-20(E)

Copyright

Copyright (C) 2016, 2017, Hitachi, Ltd.

Copyright (C) 2016, 2017, Hitachi Solutions, Ltd.

Colophon

Publisher

Hitachi, Ltd.

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

Summary of amendments

The following table lists changes in the manuals (3021-3-B12-20(E), 3021-3-B13-20(E), 3021-3-B14-20(E), 3021-3-B15-20(E), 3021-3-B16-20(E), 3021-3-B17-20(E), 3021-3-B18-20(E), 3021-3-B19-20(E), 3021-3-B20-20(E), 3021-3-B21-20(E)) and product changes related to these manuals.

Changes

Location

The Web GUI now support the following functions:

Viewing monthly schedules

Adding execution schedules

Change plan (change time)

Change plan (execute immediately)

Change plan (execution prohibited)

Change plan (release change)

Change delay monitor

Overview

6.3, 8.2.1, 8.2.2

System Design (Configuration) Guide

3.2.1(3), 3.2.1(4), 3.4.7

Configuration Guide

3.4.3(4), 3.4.3(5)(n), 3.4.3(6), 13.3.3(4), 13.3.3(5)(m), 13.3.3(6)

Troubleshooting

C.1

Operator's Guide

A.4, A.5, A.6, A.7, A.10, A.19, A.20, A.22, A.23, A.24, A.25, A.26, A.27

Messages

KNAK2023-E, KNAK2427-Q, KNAK2428-Q, KNAK2429-E, KNAK2430-Q

The API now supports the function to acquire unit information.

Command Reference

6.6.1(1), 6.6.1(4), 7.1.2, 7.1.18, 7.3.2, 7.4.5(7), 7.4.5(8), D.1, D.2, D.3, D.4

The maximum size of the Java heap on the Web Console server can now be changed, and the default value was changed from 512 MB to 2,048 MB.

Configuration Guide

3.4.2, 3.4.9, 13.3.2, 13.3.9

Administration Guide

2.2.5(1)(a), 2.2.5(1)(b)

Troubleshooting

A.4(1), A.4(2)

A function was added to enable you to change the colors indicating unit statuses displayed in the windows and dialog boxes of the Web GUI.

Overview

6.1

System Design (Configuration) Guide

4.6.1(3)

Configuration Guide

3.4.2, 3.4.8, 13.3.2, 13.3.8

Administration Guide

2.2.5(1)(a), 2.2.5(1)(b)

Troubleshooting

A.4(1), A.4(2)

Operator's Guide

B.

The map area in the Monitor dialog box and the Monitor screen of the Web GUI can now switch between displaying unit names and comments.

Operator's Guide

A.10, A.11

The following functions were added to improve job throughput when multiple scheduler services are active:

Function to reduce the number of ports that are used during job execution

Function to output trace logs for each scheduler service

In addition to the changes to internal processing, the JP1/AJS3 performance processing that runs when multiple root jobnets start at the same time was improved. As a result, job throughput when a single scheduler service is active was also improved.

System Design (Configuration) Guide

3.1.1(1), 3.1.1(5)(a), 3.4.2, 3.4.2(1), 3.4.2(2)

Configuration Guide

3.5.1(1), 6.1.1(2), 6.1.1(4)(b), 6.1.5, 6.1.12, 7.1.1, 8.2.9(2), 8.2.9(4)(b), 13.4.4(1), 15.1.1(2), 15.1.1(4)(b), 15.1.5, 15.1.13, 16.1.1, 17.2.9(2), 17.2.9(4)(b), 20.4.1, 20.4.2(4), 20.4.2(116), 20.8.1, 20.8.2(4)

Troubleshooting

1.2.3(1), 1.2.4(1), 1.2.4(2)

Command Reference

3. ajstrsetsz

Messages

KAVS0788-E, KAVU0244-E, KAVU2229-E, KAVU2231-E

The maximum number of execution agents that can be registered on one manager host can now be increased to 2,048.

Overview

A.2

System Design (Configuration) Guide

2.1.1, 2.5.1, B.1, B.5

Configuration Guide

6.2.28, 15.2.25, 20.3.1, 20.3.2(16)

Command Reference

3. ajsagtadd

Messages

1.3.7(2), KNAC1521-E

To enable the comments on units to be viewed in JP1/IM windows, commenting on units was added as an extended attribute (specific information) of a JP1 event whose OBJECT_TYPE is JOBNET or JOB.

Configuration Guide

20.4.1, 20.4.2(114), 20.4.2(115)

Administration Guide

A.2(3), A.2(4), A.2(5), A.2(6), A.2(7), A.2(8), A.2(9), A.2(10), A.2(11), A.2(14), A.2(15), A.2(16), A.2(17), A.2(18), A.2(19), A.2(20), A.2(21), A.2(23), A.2(24), A.2(25), A.2(26), A.2(27), A.2(28), A.2(29), A.2(30), A.2(31), A.2(32), A.2(33), A.2(34), A.2(35), A.2(36), A.2(37), A.2(44), A.2(45), A.2(46), A.2(47)

Messages

1.3.2, 1.4.1, KAVS0917-E

Commands to specify settings of environment setting parameters were integrated into the jajs_config command.

Overview

10.5.1(3)(a)

System Design (Configuration) Guide

7.2.2

Configuration Guide

4.2, 4.2.1, 4.2.2, 6.2, 6.2.18(1), 6.2.21(1), 6.2.22(1), 6.2.24(1), 6.4, 6.4.1(1), 6.4.1(3), 6.4.2(1), 6.4.3(1), 13.4.1(1), 14.2, 14.2.1, 14.2.2, 15.2.20(1), 15.2.22(1), 15.4, 15.4.1(1), 15.4.1(3), 20.7.2(5), 20.10.1, 20.10.2(3)

Troubleshooting

1.2.4(1), 1.2.4(2)

Command Reference

2. jajs_config, 4. ajsqlsetup

When the scheduler service is restarted, a job that meets specific conditions now transitions to Wait for prev. to end or to Not executed + Ended status (and not to Unknown end status). This enables you to determine, from the job status after the restart of the scheduler service, whether a user program has started.

Overview

A.2

Administration Guide

6.2.1(3)(a), 6.4, A.1

Command Reference

3. ajsstart

Messages

KAVS0266-I

Descriptions were added concerning JP1/AJS3 - Agent Minimal Edition, which limits the number of jobs that can be executed per day to 10.

System Design (Configuration) Guide

2.1.1, 2.1.2(1), 4.2.1, 8.1.3, A.1(2), A.2, A.4, A.7(1), A.7(2), A.7(3), G.

Configuration Guide

20.5.1, 20.5.2(93), 20.5.2(94), 20.6.1, 20.7.1, 20.11.1

Administration Guide

7.9.3

Troubleshooting

1.2.4(1), 1.2.4(2)

Command Reference

1.5.1, 1.5.9(2), 2. ajsatsetup, 4. ajsqlsetup

Messages

1.3.4, 1.3.8, KAVS1931-E, KAVS4540-E, KAVS8100-E, KAVU3607-I, KAVU3608-E, KNAD1000-E, KNAD1704-Q

Legend:

Overview: JP1/Automatic Job Management System 3 Overview

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

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

Configuration Guide: JP1/Automatic Job Management System 3 Configuration Guide

Administration Guide: JP1/Automatic Job Management System 3 Administration Guide

Troubleshooting: JP1/Automatic Job Management System 3 Troubleshooting

Operator's Guide: JP1/Automatic Job Management System 3 Operator's Guide

Command Reference: JP1/Automatic Job Management System 3 Command Reference

Linkage Guide: JP1/Automatic Job Management System 3 Linkage Guide

Messages: JP1/Automatic Job Management System 3 Messages

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 explains the messages beginning from KAJS to KNAK. 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. Overview of JP1/AJS3 Messages

Chapter 1 lists the manuals that describe the messages output by JP1/AJS3, JP1/Base, and JP1/IM. It also describes the JP1/AJS3 message format, output destinations, syslog and Windows event log messages.

2. Messages beginning with KAJS (Messages about passing information setting jobs)

Chapter 2 explains the messages beginning with KAJS (messages about passing information setting jobs) output by JP1/AJS3, and the responsive action required.

3. Messages beginning with KAVS (Messages about the scheduler and the common processing)

Chapter 3 explains the messages beginning with KAVS (messages about the scheduler and the common processing) output by JP1/AJS3, and the responsive action required.

4. Messages beginning with KAVT (Messages about the event/action control)

Chapter 4 explains the messages beginning with KAVT (messages about the event/action control) output by JP1/AJS3, and the responsive action required.

5. Messages beginning with KAVU (Messages about the job execution control)

Chapter 5 explains the messages beginning with KAVU (messages about job execution control) output by JP1/AJS3, and the responsive action required.

6. Messages beginning with KAVV (Messages about JP1/AJS3 - View)

Chapter 6 explains the messages beginning with KAVV (messages about JP1/AJS3 - View) output by JP1/AJS3, and the responsive action required.

7. Messages beginning with KFP (Messages about an embedded database)

Chapter 7 explains the messages beginning with KFP (messages about embedded databases) output by JP1/AJS3, and the responsive action required.

8. Messages beginning with KNAC (Messages that are output by communication control and agent management)

Chapter 8 explains the messages beginning with KNAC (messages output by JP1/AJS3 communication control and agent management), and the responsive action required.

9. Messages beginning with KNAD (Messages that are output by the installer and system management)

Chapter 9 explains the messages beginning with KNAD (messages output by the JP1/AJS3 installer and system management), and the responsive action required.

10. Messages beginning with KNAK (Messages about JP1/AJS3 - Web Console)

Chapter 10 explains the messages beginning with KNAK (messages about JP1/AJS3 - Web Console) output by JP1/AJS3, and the responsive action required.

Organization of JP1/AJS3 manuals and choosing the right manuals

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

No.

Manual

Contents

1

Getting Started

(3021-3-B11(E))

Basic JP1/AJS3 operations

2

Overview

(3021-3-B12(E))

JP1/AJS3 features

Description of functions

3

System Design (Configuration) Guide

(3021-3-B13(E))

Information that must be considered when designing a system

Cautionary notes on designing a system

4

System Design (Work Tasks) Guide

(3021-3-B14(E))

Information that must be considered when constructing jobs and jobnets

Cautionary notes on designing jobs and jobnets

5

Configuration Guide

(3021-3-B15(E))

Installation and setup procedures

Environment setup procedure

Description of environment setting parameters

How to set up functions according to how the system is used

6

Administration Guide

(3021-3-B16(E))

Information required to operate a system

Know-how useful for JP1/AJS3 operation

7

Troubleshooting

(3021-3-B17(E))

How to troubleshoot errors

Data required when an error occurs

8

Operator's Guide

(3021-3-B18(E))

How to operate JP1/AJS3 - View

Description of windows and dialog boxes

9

Command Reference

(3021-3-B19(E))

Command syntax

Syntax and coding examples of information definition files

API details and syntax

10

Linkage Guide

(3021-3-B20(E))

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

11

Messages

(3021-3-B21(E))

Messages output by JP1/AJS3

Getting Started refers to JP1 Version 11 Job Management: Getting Started (Job Scheduler). "JP1 Version 11 JP1/Automatic Job Management System 3" is omitted in other manual names.

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 the basic usage of JP1/AJS3

Getting Started

(3021-3-B11(E))

Operator's Guide

(3021-3-B18(E))

To learn about JP1/AJS3's functionalities

Overview

(3021-3-B12(E))

Linkage Guide

(3021-3-B20(E))

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

System Design (Configuration) Guide

(3021-3-B13(E))

Configuration Guide

(3021-3-B15(E))

Linkage Guide

(3021-3-B20(E))

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

System Design (Work Tasks) Guide

(3021-3-B14(E))

Operator's Guide

(3021-3-B18(E))

To learn about monitoring and maintaining a running system

Administration Guide

(3021-3-B16(E))

Troubleshooting

(3021-3-B17(E))

Messages

(3021-3-B21(E))

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

Troubleshooting

(3021-3-B17(E))

Messages

(3021-3-B21(E))

To learn about operating JP1/AJS3

Operator's Guide

(3021-3-B18(E))

Command Reference

(3021-3-B19(E))

Replacing the term JP1/AJS3 - Agent with JP1/AJS3 - Agent Minimal Edition in this manual

This manual uses the term JP1/AJS3 - Agent to mean both JP1/AJS3 - Agent and JP1/AJS3 - Agent Minimal Edition. If you use JP1/AJS3 - Agent Minimal Edition, replace the term JP1/AJS3 - Agent with the term JP1/AJS3 - Agent Minimal Edition while reading this manual. If, however, a difference between JP1/AJS3 - Agent Minimal Edition and JP1/AJS3 - Agent is described, both terms (JP1/AJS3 - Agent Minimal Edition and JP1/AJS3 - Agent) are used.

1 Overview of JP1/AJS3 Messages

This chapter lists the manuals that contain information about messages output by JP1/AJS3, JP1/Base, and JP1/IM. This chapter also explains the format of the JP1/AJS3 messages, and lists the output destinations and the Windows event logs and syslogs.

1.1 Types of messages

This chapter lists the manuals that contain information about the messages output by JP1/AJS3, JP1/Base, and JP1/IM.

When you operate a system using JP1/AJS3, the system also outputs messages for JP1/Base that is a prerequisite program, in addition to JP1/AJS3 messages. If you link JP1/AJS3 with JP1/IM, the system also outputs JP1/IM messages.

The following table lists the manuals that contain information about the messages output by JP1/AJS3, JP1/Base, and JP1/IM according to message IDs.

Table 1‒1: Message IDs and corresponding manuals

Message ID

Manual containing the corresponding message

Messages beginning with KAJP

JP1/Base Messages

Messages beginning with KAJS

JP1/Automatic Job Management System 3 Messages

Messages beginning with KAVA

JP1/Base Messages

Messages beginning with KAVS

JP1/Automatic Job Management System 3 Messages

Messages beginning with KAVT

Messages beginning with KAVU

JP1/Automatic Job Management System 3 Messages

KAVV001 to KAVV899

KAVV1300 to KAVV9999

Messages beginning with KAVZ

JP1/Automatic Job Management System 3 Definition Assistant

Messages beginning with KFP

JP1/Automatic Job Management System 3 Messages

Messages beginning with KNAC

JP1/Automatic Job Management System 3 Messages

KNAD0001 to KNAD3160

KNAD4001 to KNAD6000

JP1/Integrated Management - Manager Messages

KNAD3501 to KNAD3986

JP1/Automatic Job Management System 3 Messages

Messages beginning with KNAK

JP1/Automatic Job Management System 3 Messages

1.2 Message format

This section explains the output format of JP1/AJS3 messages and the description format of messages in this manual.

JP1/AJS3 supports both Japanese and English messages. In UNIX, you can use the LANG environment variable to specify for each user which language is to be used to display messages.

1.2.1 Format of output messages

(1) Messages beginning with KAJ

This subsection describes the format of messages related to JP1/AJS3 passing information setting jobs.

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

Messages are output in one of the following formats:

KAJSnnnn-Z message text

K

System identifier

AJS

Indicates a message relating to a JP1/AJS3 passing information setting job.

nnnn

Message serial number

Z

Message type, as one of the following:

E

Error message. Processing is canceled. However, if you specify more than one name using a command, the system outputs this message for each name and continues command processing.

W

Warning message. Processing continues after message output.

I

Information message. Reports information to the user.

Q

Query message. Prompts the user to respond.

The following table shows the correspondence between the message levels and the Windows event logs.

Table 1‒2: Message levels and Windows event logs

Message level

Type of Windows event log

Level

Meaning

-E

Error

System error, abnormal end of a job, monitoring failure, etc.

-W

Warning

End of a job with a warning, delay of a jobnet, read failure of a settings file, etc.

-I

Information

Notice of holding a job, start of job execution, normal end of a job, start of monitoring, etc.

-Q

Not applicable

Not applicable

The following table shows the correspondence between the message levels and the priority levels of UNIX syslogs.

Table 1‒3: Message levels and priority levels of syslogs

Message level

Priority level of syslog

Level

Meaning

-E

LOG_ERR

System error, abnormal end of a job, monitoring failure, etc.

-W

LOG_WARNING

End of a job with a warning, delay of a jobnet, read failure of a settings file, etc.

-I

LOG_NOTICE

Notice of holding a job, start of monitoring, etc.

LOG_INFO

Start of job execution, normal end, etc.

-Q

Not applicable

Not applicable

(2) Messages beginning with KAV

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

Messages are output in one of the following formats:

KAVSnnnn-Z message text

KAVTnnnn-Z message text

KAVUnnnn-Z message text

KAVVnnn-Z message text

The message ID consists of the following:

K

System identifier

AVS, AVT, AVU or AVV

Indicates a message output by JP1/AJS3.

nnnn or nnn

Message serial number

Z

Message type, as one of the following:

E

Error message. Processing is canceled. However, if you specify more than one name using a command, the system outputs this message for each name and continues command processing.

W

Warning message. Processing continues after message output.

I

Information message. Reports information to the user.

Q

Query message. Prompts the user to respond.

K

Continuation message. Processing continues.

The following table shows the correspondence between the message levels and the Windows event logs.

Table 1‒4: Message levels and Windows event logs

Message level

Type of Windows event log

Level

Meaning

-E

Error

System error, abnormal end of a job, monitoring failure, etc.

-W

Warning

End of a job with a warning, delay of a jobnet, read failure of a settings file, etc.

-I

Information

Notice of holding a job, start of job execution, normal end of a job, start of monitoring, etc.

-Q

Not applicable

Not applicable

The following table shows the correspondence between the message levels and the priority levels of UNIX syslogs.

Table 1‒5: Message levels and priority levels of syslogs

Message level

Priority level of syslog

Level

Meaning

-E

LOG_ERR

System error, abnormal end of a job, monitoring failure, etc.

-W

LOG_WARNING

End of a job with a warning, delay of a jobnet, read failure of a settings file, etc.

-I

LOG_NOTICE

Notice of holding a job, start of monitoring, etc.

LOG_INFO

Start of job execution, normal end, etc.

-Q

Not applicable

Not applicable

(3) Messages beginning with KFP

Each message output by an embedded database consists of a message ID, followed by the message text. Messages are output in the following format:

KFPXnnnn-Z message text

KFPX

Indicates a message output by an embedded database.

X

Code identifying the source managing the message

nnnn

Message serial number

Z

Message type, as one of the following:

E

Error message. Processing is canceled. However, if you specify more than one name using a command, the system outputs this message for each name and continues command processing.

W

Warning message. Processing continues after message output.

I

Information message. Reports information to the user.

Q

Query message. Prompts the user to respond.

K

Continuation message. Processing continues.

(4) Messages beginning with KNA

The following describes the format of messages output by JP1/AJS3 system management, agent management, and JP1/AJS3 - Web Console. Each message consists of a message ID, followed by the message text. Messages are output in the following format:

KNACnnnn-Z message text

KNADnnnn-Z message text

KNAKnnnn-Z message text

K

System identifier

NAC

Indicates a message output by JP1/AJS3 communication control or agent management.

NAD

Indicates a message output by the JP1/AJS3 installer or system management.

NAK

Indicates a JP1/AJS3 - Web Console message.

nnnn

Message serial number

Z

Message type, as one of the following:

E

Error message. Processing is canceled. However, if you specify more than one name using a command, the system outputs this message for each name and continues command processing.

W

Warning message. Processing continues after message output.

I

Information message. Reports information to the user.

1.2.2 Format of message explanations

(1) Messages beginning with KAJ

Messages are explained in the following format in this manual.

Characters in italic vary each time the system displays a message. Messages are explained in the ascending order of message IDs.

Message ID

Message text: message text

Explanation of the output message text.

(S)

System action

(O)

Operator action at message output

(2) Messages beginning with KAV

Messages are explained in the following format in this manual.

Characters in italic vary each time the system displays a message. Messages are explained in the ascending order of message IDs. The format is as follows; however, messages beginning with KAVU may be displayed without function-name: even if the message text contains function-name: in the manual.

Message ID

Message text: message text

Explanation of the output message text.

(S)

System action

(O)

Operator action at message output

(3) Messages beginning with KFP

Messages beginning with KFP are explained in the following format in this manual. Messages are explained in the ascending order of message ID. The following shows a message explanation example.

Message ID

Message text: message text (Y#)

Explanation of the output message text.

(S)

System action

(P)

Programmer action at message output

(O)

Operator action at message output

Action

Action that the embedded database system administrator must take when the message is received.

#

Output destination of the message. For details, see 1.3.6 Output destinations of messages beginning with KFP.

(4) Messages beginning with KNA

Messages beginning with KNA are explained in the following format in this manual. Characters in italic vary each time the system displays a message. Messages are explained in the ascending order of message IDs. The following shows a message explanation example.

Message ID

Message text: message text

Explanation of the output message text.

(S)

System action

(O)

Operator action at message output

1.2.3 To the system administrators

If an error occurs during operation, collect log information according to the manual JP1/Automatic Job Management System 3 Troubleshooting, and conduct in an initial check.

To conduct initial check to find the cause of the error, see the log information for the operating system (Windows event logs in Windows and syslogs in UNIX) and log information output by JP1/AJS3. Prevent the error and take corrective actions according to the contents of the log information when the error occurred.

In addition, record the operation that caused the error. If possible, check whether the same error occurs repeatedly.

JP1/AJS3 outputs the messages related to the JP1/Base process monitor. When monitoring troubles in JP1/AJS3, also see the messages related to the JP1/Base process monitor.

1.3 List of output destinations for messages

This section lists the output destinations of the messages that are output by JP1/AJS3.

1.3.1 Output destinations of messages beginning with KAJS

The table below lists the output destinations of messages beginning with KAJS (messages about passing information setting jobs ).

The table uses the following abbreviations for the output destinations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

Exec details: Execution Result Details dialog box

JP1 event: JP1 event

Y: Is output.

--: Is not output.

Table 1‒6: The output destinations of messages beginning with KAJS

Message ID

Output destination

syslog

Event

log

HNTRLib2

stdout

stderr

Exec details

JP1 event

KAJS7620 -

KAJS7626

--

--

--

--

--

Y

--

KAJS7628 -

KAJS7630

--

--

--

--

--

Y

--

1.3.2 Output destinations of messages beginning with KAVS

The table below lists the output destinations of messages whose message ID begins with KAVS. These are messages about the scheduler and the common processing.

The table uses the following abbreviations for the output destinations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

Exec details: Execution Result Details dialog box

JP1 event: JP1 event

Y: Is output.

--: Is not output.

Table 1‒7: The output destinations of messages beginning with KAVS

Message ID

Output destination

syslog

Event

log

HNTRLib2

stdout

stderr

Exec details

JP1 event

KAVS0100 -

KAVS0107

--

--

--

--

Y

--

--

KAVS0108

--

--

--

--

Y

--

--

KAVS0110 -

KAVS0118

--

--

--

--

Y

--

--

KAVS0119

Y

Y

Y

--

Y

--

--

KAVS0120 -

KAVS0124

--

--

--

--

Y

--

--

KAVS0125

Y

Y

Y

--

Y

--

--

KAVS0126 -

KAVS0130

--

--

--

--

Y

--

--

KAVS0132 -

KAVS0135

Y

Y

Y

--

--

--

--

KAVS0141 -

KAVS0167

--

--

--

--

Y

--

--

KAVS0168

Y

Y

Y

--

Y

--

--

KAVS0169 -

KAVS0175

--

--

--

--

Y

--

--

KAVS0176

Y

Y

Y

--

Y

--

--

KAVS0177 -

KAVS0188

--

--

--

--

Y

--

--

KAVS0189

Y

Y

Y

--

Y

--

--

KAVS0190 -

KAVS0199

--

--

--

--

Y

--

--

KAVS0200 -

KAVS0201

Y#1

Y#1

Y

--

--

--

Y

KAVS0202

Y

Y

Y

--

--

--

Y

KAVS0203

Y

Y

--

--

--

--

Y

KAVS0204

Y

Y

Y

--

--

--

Y

KAVS0208 -

KAVS0209

--

--

--

--

Y

--

--

KAVS0210

Y

Y

Y

Y

--

--

--

KAVS0211

Y

Y

--

--

Y

--

--

KAVS0212 -

KAVS0218

Y

Y

Y

--

--

--

--

KAVS0219

--

--

--

--

Y

--

--

KAVS0220 -

KAVS0221

Y#2

Y#2

Y

--

--

--

--

KAVS0222

--

--

--

--

Y

--

--

KAVS0230 -

KAVS0232

Y

Y

Y

--

--

--

--

KAVS0240 -

KAVS0241

Y#3

Y#3

Y

--

--

--

Y

KAVS0242

--

--

--

--

--

--

Y

KAVS0243 -

KAVS0244

Y#3

Y#3

Y

--

--

--

Y

KAVS0245 -

KAVS0246

Y

Y

Y

--

--

--

--

KAVS0247

--

--

Y

--

--

--

--

KAVS0248

Y#5

Y#5

Y

--

--

--

Y

KAVS0249

--

--

Y#4

--

--

--

--

KAVS0260 -

KAVS0262

Y#3

Y#3

Y

--

--

--

Y

KAVS0263 -

KAVS0264

Y#5

Y#5

Y

--

--

--

Y

KAVS0265

Y#5, #6

Y#5

Y

--

--

--

Y

KAVS0266

Y#5

Y#5

--

--

--

--

Y

KAVS0267

Y

Y

Y

--

--

--

--

KAVS0268

Y#3

Y#3

Y

--

--

--

Y

KAVS0269

Y#5

Y#5

Y

--

--

--

Y

KAVS0270

Y#3

Y#3

Y

--

--

--

Y

KAVS0271

Y#5

Y#5

Y

--

--

--

Y

KAVS0272 -

KAVS0273

Y

Y

Y

--

--

--

Y

KAVS0274

Y

Y

Y

--

--

--

--

KAVS0275 -

KAVS0276

Y#3

Y#3

Y

--

--

--

Y

KAVS0277

Y

Y

Y

--

--

--

Y

KAVS0278

--

--

--

--

--

--

Y

KAVS0279

Y#3

Y#3

Y

--

--

--

Y

KAVS0289 -

KAVS0291

--

--

--

--

Y

--

--

KAVS0297

Y#15

Y#15

Y

--

--

--

--

KAVS0300

--

--

--

--

Y

--

--

KAVS0301

Y

Y

Y

--

Y

--

--

KAVS0304 -

KAVS0311

--

--

--

--

Y

--

--

KAVS0314 -

KAVS0319

Y

Y

Y

--

Y

--

--

KAVS0322 -

KAVS0470

--

--

--

--

Y

--

--

KAVS0475

--

--

--

Y

--

--

--

KAVS0476 -

KAVS0478

--

--

--

--

Y

--

--

KAVS0500

Y

Y

Y

--

--

--

--

KAVS0530 -.

KAVS0535

Y#7

Y#7

Y

--

--

--

--

KAVS0536 -

KAVS0537

Y

Y

Y

--

--

--

--

KAVS0538 -

KAVS0539#17

--

--

--

--

--

--

--

KAVS0540 -

KAVS0544

--

--

--

--

Y

--

--

KAVS0545 -

KAVS0546

--

--

--

Y

--

--

--

KAVS0547

--

--

--

--

Y

--

--

KAVS0548

--

--

--

Y

--

--

--

KAVS0549 -

KAVS0550

--

--

--

--

Y

--

--

KAVS0560 -

KAVS0561

Y#7

Y#7

Y

--

--

--

--

KAVS0566 -

KAVS0569#14

--

--

--

--

--

--

--

KAVS0582 -

KAVS0669

--

--

--

--

Y

--

--

KAVS0670

Y

Y

Y

--

--

--

--

KAVS0671 -

KAVS0712

--

--

--

--

Y

--

--

KAVS0715 -

KAVS0716

--

--

--

--

--

--

Y

KAVS0720 -

KAVS0800

--

--

--

--

Y

--

--

KAVS0829 -

KAVS0832

--

--

--

Y

--

--

--

KAVS0849 -

KAVS0858

--

--

--

--

Y

--

--

KAVS0863 -

KAVS0866

Y

Y

Y

--

Y

--

--

KAVS0867

Y

Y

Y

--

Y

--

--

KAVS0868

--

--

--

--

Y

--

--

KAVS0869

Y

Y

Y

--

Y

--

--

KAVS0870

--

--

--

Y

--

--

--

KAVS0872 -

KAVS0877

--

--

--

--

Y

--

--

KAVS0880

--

--

--

Y

--

--

--

KAVS0885 -

KAVS0888

--

--

--

--

Y

--

--

KAVS0889 -

KAVS0893

--

--

Y

--

--

--

--

KAVS0894 -

KAVS0898

--

--

--

--

Y

--

--

KAVS0900

Y

Y

Y

--

--

--

--

KAVS0901

Y

Y

Y

--

Y

--

--

KAVS0902

Y

Y

Y

--

Y

Y

--

KAVS0903 -

KAVS0904

Y

Y

Y

--

Y

--

--

KAVS0905

Y

Y

Y

--

--

--

--

KAVS0907

Y

Y

Y

--

Y

--

--

KAVS0909

Y

Y

Y

--

Y

--

--

KAVS0915

Y

Y

Y

--

Y

--

--

KAVS0916

Y

--

--

--

--

--

--

KAVS0917

Y

Y

Y

--

--

--

--

KAVS0920

Y

Y

--

--

--

--

--

KAVS0921

Y

Y

Y

--

--

--

--

KAVS0930

Y

Y

Y

--

Y

--

--

KAVS0931

--

--

--

--

Y

--

--

KAVS0932

Y

Y

Y

--

Y

--

--

KAVS0933

Y

Y

Y

--

--

--

--

KAVS0934 -

KAVS0935

Y

Y

Y

--

Y

--

--

KAVS0936

Y

Y

Y

--

Y

--

--

KAVS0940 -

KAVS0950

Y

Y

Y

--

--

--

--

KAVS0960 -

KAVS0964

Y

Y

Y

--

Y

--

--

KAVS0965 -

KAVS0971

Y

Y

Y

--

--

--

--

KAVS0980 -

KAVS0990

Y

Y

Y

--

Y

--

--

KAVS0991

--

--

--

--

Y

--

--

KAVS0992

Y

Y

Y

--

Y

--

--

KAVS0993 -

KAVS0994

--

--

--

--

Y

--

--

KAVS0996

--

--

--

--

Y

--

--

KAVS0997

Y

Y

--

--

Y

--

--

KAVS0998 -

KAVS0999

Y

Y

Y

--

--

--

Y

KAVS1002 -

KAVS1008

Y

Y

Y

--

Y

--

--

KAVS1009

Y#8

Y#8

Y#8

--

--

--

--

KAVS1010 -

KAVS1015

--

--

Y

--

--

--

--

KAVS1100

--

--

--

Y

--

--

--

KAVS1101 -

KAVS1118

--

--

--

--

Y

--

--

KAVS1119 -

KAVS1120

--

--

--

Y

--

--

--

KAVS1121 -

KAVS1131

--

--

--

--

Y

--

--

KAVS1132

--

--

--

Y

--

--

--

KAVS1133 -

KAVS1139

--

--

--

--

Y

--

--

KAVS1140 -

KAVS1148

--

--

--

--

Y

--

--

KAVS1200

--

--

--

--

Y

--

--

KAVS1300 -

KAVS1302

Y

Y

Y

--

Y

--

--

KAVS1400 -

KAVS1401

Y

Y

Y

--

--

--

--

KAVS1420

Y

Y

Y

--

--

--

Y

KAVS1500 -

KAVS1504

Y

Y

Y

--

Y

--

Y

KAVS1510

--

--

Y#9

--

--

--

--

KAVS1512

Y

Y

--

--

--

--

--

KAVS1513

--

--

--

--

Y

--

--

KAVS1514 -

KAVS1515

Y

Y

Y

--

--

--

--

KAVS1516

Y

Y

Y

--

Y

--

--

KAVS1517 -

KAVS1518

Y

Y

Y

--

--

--

--

KAVS1570 -

KAVS1572

--

--

Y

--

--

--

--

KAVS1600 -

KAVS1602

--

--

--

--

--

--

--

KAVS1703 -

KAVS1707

--

--

--

--

Y

--

--

KAVS1709

Y

Y

--

--

Y

--

--

KAVS1713

Y

Y

--

--

Y

--

--

KAVS1714 -

KAVS1718

--

--

--

--

Y

--

--

KAVS1719

--

--

Y

Y

--

--

--

KAVS1720

--

--

Y

--

Y

--

--

KAVS1721 -

KAVS1723

--

--

Y

--

--

--

--

KAVS1724

--

--

--

--

Y

--

--

KAVS1725

Y

Y

--

--

Y

--

--

KAVS1726

--

--

Y

--

--

--

--

KAVS1727

--

--

Y

--

--

--

--

KAVS1728

--

--

Y

--

--

--

--

KAVS1729

--

--

Y

--

--

--

--

KAVS1730

--

--

Y

--

--

--

--

KAVS1731 -

KAVS1742

--

--

--

Y

--

--

--

KAVS1751 -

KAVS1759

--

--

--

Y

--

--

--

KAVS1770 -

KAVS1773

--

--

--

Y

--

--

--

KAVS1774 -

KAVS1784

--

--

--

--

Y

--

--

KAVS1785

--

--

--

Y

--

--

--

KAVS1786

--

--

--

--

Y

--

--

KAVS1790

Y

Y

--

--

Y

--

--

KAVS1791

Y

Y

--

--

Y

--

--

KAVS1801 -

KAVS1806

Y

Y

Y

--

--

--

--

KAVS1807 -

KAVS1811

Y

Y

Y

--

--

Y

--

KAVS1812

Y

Y

Y

--

Y

--

--

KAVS1813 -

KAVS1816

Y

Y

Y

--

--

--

--

KAVS1817 -

KAVS1828

Y

Y

Y

--

--

Y

--

KAVS1829

Y

Y

Y

--

Y

Y

--

KAVS1830

Y

Y

Y

--

Y

Y

--

KAVS1831

Y#10

Y#10

Y#10

--

Y

--

--

KAVS1832 -

KAVS1836

Y

Y

Y

--

--

Y

--

KAVS1837 -

KAVS1838

Y

Y

Y

--

--

--

--

KAVS1839 -

KAVS1841

Y

Y

Y

--

--

Y

--

KAVS1842 -

KAVS1845

Y

Y

Y

--

--

--

--

KAVS1846

Y

Y

Y

--

--

Y

--

KAVS1847

--

--

Y

--

Y

Y

--

KAVS1848 -

KAVS1854

Y

Y

Y

--

--

--

--

KAVS1855

Y

Y

Y

--

Y

--

--

KAVS1859

Y

Y

Y

--

--

--

--

KAVS1860

--

Y

Y

--

--

--

--

KAVS1861

Y

Y

Y

--

--

--

--

KAVS1862 -

KAVS1863

--

Y

Y

--

--

--

--

KAVS1864

--

Y

Y

--

Y

--

--

KAVS1865 -

KAVS1872

Y

Y

Y

--

--

--

--

KAVS1873 -

KAVS1874

Y

Y

Y

--

--

Y

--

KAVS1875 -

KAVS1878

Y

Y

Y

--

--

--

--

KAVS1879

Y

Y

Y

--

--

Y

--

KAVS1880

--

Y

Y

--

Y

Y

--

KAVS1881 -

KAVS1886

Y

Y

Y

--

--

Y

--

KAVS1887

Y

Y

Y

--

--

--

--

KAVS1888 -

KAVS1890

Y

Y

Y

--

--

Y

--

KAVS1891 -

KAVS1898

Y

Y

Y

--

--

--

--

KAVS1900 -

KAVS1908

Y

Y

Y

--

--

--

--

KAVS1909

Y

Y

Y

--

--

Y

--

KAVS1920

Y

Y

Y

--

--

--

--

KAVS1921

Y

Y

Y

--

--

Y

--

KAVS1922

Y

Y

Y

--

--

--

--

KAVS1923

Y

Y

Y

--

--

Y

--

KAVS1924

Y

Y

Y

--

--

--

--

KAVS1925

Y

Y

Y

--

Y

Y

--

KAVS1926

--

--

Y

--

Y

Y

--

KAVS1927

Y

Y

Y

--

Y

Y

--

KAVS1928

--

--

--

--

--

Y

--

KAVS1929

Y

Y

Y

--

--

--

--

KAVS1930

Y

Y

Y

--

--

--

--

KAVS1931

--

--

--

--

--

Y

--

KAVS1932

Y

Y

Y

--

--

--

--

KAVS1933

--

--

--

--

--

Y

--

KAVS1939

--

--

Y

--

--

Y

--

KAVS1940 -

KAVS1943

Y

Y

Y

--

--

--

--

KAVS1952

--

--

--

--

Y

--

--

KAVS1953

Y

Y

Y

--

Y

--

--

KAVS1954

--

Y#10

Y#10

--

Y

--

--

KAVS1955

--

--

--

--

Y

--

--

KAVS1956

Y

Y

Y

--

Y

--

--

KAVS1957 -

KAVS1960

--

--

--

--

Y

--

--

KAVS1961

--

Y#10

Y#10

--

Y

--

--

KAVS1962

--

Y#10

Y#10

--

Y

--

--

KAVS1963

Y

Y

Y

--

Y

Y

--

KAVS1964

Y

Y

Y

--

Y

Y

--

KAVS1965

Y

Y

Y

--

--

--

--

KAVS1966 -

KAVS1970

--

Y

Y

--

--

--

--

KAVS1971 -

KAVS1977

Y

Y

Y

--

--

Y

--

KAVS1978

Y

Y

Y

--

--

--

--

KAVS1979

Y

Y

Y

--

--

Y

--

KAVS1980 -

KAVS1983

Y

Y

Y

--

Y

--

--

KAVS1985 -

KAVS1988

--

--

--

--

Y

--

--

KAVS1989 -

KAVS1993

Y

Y

Y

--

Y

--

--

KAVS1994

--

--

--

--

Y

--

--

KAVS1995

Y

Y

Y

--

Y

--

--

KAVS1996

--

--

--

Y

--

--

--

KAVS1997

--

--

--

--

Y

--

--

KAVS1998

--

Y#10

Y#10

--

Y

--

--

KAVS1999

--

--

Y

--

--

Y

--

KAVS2030 -

KAVS2046

--

--

--

--

Y

--

--

KAVS2060

Y

Y

Y

--

--

--

--

KAVS2101 -

KAVS2110

--

--

--

--

Y

--

--

KAVS2113 -

KAVS2126

--

--

--

--

Y

--

--

KAVS2127 -

KAVS2128

Y

Y

--

--

--

--

--

KAVS2129 -

KAVS2130

--

--

--

Y

--

--

--

KAVS3400 -

KAVS3401

--

--

Y

Y

--

--

--

KAVS3402 -

KAVS3403

--

--

Y

--

--

--

--

KAVS3404 -

KAVS3405

--

--

Y

Y

--

--

--

KAVS3406 -

KAVS3407

--

--

Y

--

--

--

--

KAVS3408

--

--

--

Y

--

--

--

KAVS3409 -

KAVS3410

--

--

Y

--

--

--

--

KAVS3411 -

KAVS3413

--

--

--

Y

--

--

--

KAVS3414 -

KAVS3423

--

--

Y

--

--

--

--

KAVS3424

--

--

Y

Y

--

--

--

KAVS3425 -

KAVS3430

--

--

Y

--

--

--

--

KAVS3431

--

--

Y

Y

--

--

--

KAVS3432 -

KAVS3437

--

--

Y

--

--

--

--

KAVS3601

--

--

--

--

Y

--

--

KAVS3701 -

KAVS3702

--

--

--

--

Y

--

--

KAVS3704

--

--

--

--

Y

--

--

KAVS3706

--

--

--

--

Y

--

--

KAVS3707 -

KAVS3710

Y

Y

Y

Y

--

--

--

KAVS3711

--

--

--

--

Y

--

--

KAVS3750 -

KAVS3751

--

--

--

--

Y

--

--

KAVS3752

--

--

--

Y

--

--

--

KAVS3753 -

KAVS3757

--

--

--

--

Y

--

--

KAVS3780 -

KAVS3784

--

--

--

Y

--

--

--

KAVS3800 -

KAVS3805

--

--

--

--

Y

--

--

KAVS3850 -

KAVS3853

--

--

--

Y

--

--

--

KAVS3910

Y

Y

Y

--

Y

--

--

KAVS4091 -

KAVS4092

Y

Y

Y

--

--

--

--

KAVS4200 -

KAVS4204

Y

Y

Y

--

--

--

--

KAVS4209

Y

Y

Y

--

--

--

--

KAVS4210 -

KAVS4212

--

--

--

--

Y

--

--

KAVS4540

--

--

--

--

Y

--

--

KAVS4601 -

KAVS4621

--

--

--

--

Y

--

--

KAVS4624 -

KAVS4630

--

--

--

--

Y

--

--

KAVS4631

Y

Y

Y

--

Y

--

--

KAVS4632 -

KAVS4646

--

--

--

--

Y

--

--

KAVS4647 -

KAVS4656

--

--

Y

--

--

--

--

KAVS4657 -

KAVS4658

--

--

--

--

Y

--

--

KAVS4660 -

KAVS4662

--

--

--

--

Y

--

--

KAVS4670

--

--

--

--

Y

--

--

KAVS4671

Y

Y

Y

--

Y

--

--

KAVS4672 -

KAVS4673

Y

Y

Y

--

--

--

--

KAVS4674

--

--

--

--

Y

--

--

KAVS4675 -

KAVS4676

Y#5

Y#5

Y

--

--

--

Y

KAVS4677

Y#5, #6

Y#5

Y

--

--

--

Y

KAVS4678

--

--

--

--

--

--

Y

KAVS4699

--

--

Y

Y

--

--

--

KAVS4700 -

KAVS4707

Y#3

Y#3

Y

--

--

Y

--

KAVS4708

Y#3

Y#3

Y

--

--

--

--

KAVS4710

--

--

--

--

--

Y

--

KAVS4711 -

KAVS4716

Y#3

Y#3

Y

--

--

Y

--

KAVS4720 -

KAVS4725

Y

Y

Y

--

--

--

--

KAVS4730 -

KAVS4733

Y#3

Y#3

Y

--

--

Y

--

KAVS4750 -

KAVS4752

Y

Y

Y

--

--

--

--

KAVS4822 -

KAVS4824

--

--

--

--

Y

--

--

KAVS4826 -

KAVS4830

--

--

--

--

Y

--

--

KAVS4832 -

KAVS4839

--

--

--

--

Y

--

--

KAVS4900 -

KAVS4918

Y

Y

Y

--

--

--

--

KAVS4931

--

--

--

--

Y

--

--

KAVS4933

--

--

--

Y

--

--

--

KAVS4934 -

KAVS4938

--

--

Y

--

Y

--

--

KAVS4939

Y

--

Y

Y

--

--

--

KAVS4941

--

--

--

--

Y

--

--

KAVS4943

Y

Y

Y

--

Y

--

--

KAVS4944

--

--

Y

--

Y

--

--

KAVS4950

Y#3

Y#3

--

--

--

--

Y

KAVS4951

Y#5

Y#5

--

--

--

--

Y

KAVS4952

--

--

Y

--

--

Y

--

KAVS4954

--

--

Y

--

--

Y

--

KAVS4955

Y#3

Y#3

--

--

--

--

Y

KAVS4956

Y#5

Y#5

--

--

--

--

Y

KAVS4957

Y#3

Y#3

Y

--

--

--

Y

KAVS4958

--

--

Y

--

--

--

Y

KAVS4962

--

--

Y

--

--

--

Y

KAVS4971

Y#5

Y#5

Y

--

--

--

Y

KAVS4973

--

--

Y

--

--

--

Y

KAVS4975

--

--

--

--

--

Y

--

KAVS4976 -

KAVS4977

--

--

Y

--

--

Y

--

KAVS4981 -

KAVS4982

--

--

--

Y

--

--

--

KAVS4991 -

KAVS4995#11

--

--

--

--

--

--

--

KAVS8001

--

--

Y

--

Y

--

--

KAVS8002

--

--

Y

--

--

--

--

KAVS8003 -

KAVS8005

--

--

Y

--

Y

--

--

KAVS8006

--

--

Y#12

--

Y

--

--

KAVS8007

--

--

--

--

Y

--

--

KAVS8008 -

KAVS8011

--

--

Y

--

Y

--

--

KAVS8012

--

--

Y#12

--

Y

--

--

KAVS8013 -

KAVS8014

--

--

Y

--

--

--

--

KAVS8015 -

KAVS8023

--

--

Y#13

--

Y#13

--

--

KAVS8028

--

--

Y

--

Y

--

--

KAVS8029

--

--

Y

--

--

Y

--

KAVS8030

--

--

--

Y

--

--

--

KAVS8032

--

--

--

Y

--

--

--

KAVS8033

Y

Y

Y

--

Y

--

--

KAVS8034

--

--

--

--

Y

--

--

KAVS8036 -

KAVS8037

--

--

Y

--

Y

--

--

KAVS8038

--

--

--

--

Y

--

--

KAVS8039

--

--

Y

--

--

--

--

KAVS8040

Y#16

Y#16

Y

--

--

--

--

KAVS8050 -

KAVS8052

--

--

--

--

Y

Y

--

KAVS8053 -

KAVS8054

--

--

Y

--

Y

Y

--

KAVS8056 -

KAVS8059

--

--

Y

--

Y

Y

--

KAVS8060

--

--

--

--

Y

Y

--

KAVS8061 -

KAVS8062

--

--

Y

--

Y

Y

--

KAVS8100

--

--

Y

--

Y

Y

Y

KAVS8101

--

--

Y

--

Y

Y

Y

KAVS8102

--

--

Y

--

Y

Y

--

KAVS8106

--

--

Y

--

Y

Y

--

KAVS8107

Y

--

Y#18

--

Y#18

--

--

KAVS8108

--

--

Y

--

Y

Y

--

KAVS8109

--

--

Y

--

Y

Y

--

KAVS8110

--

--

--

--

--

--

--

KAVS8111

Y

--

Y#18

--

Y#18

--

--

KAVS8112

--

--

--

--

Y

--

--

KAVS8113

Y

--

Y#18

--

Y#18

--

--

KAVS8114

Y

Y

Y

--

Y

--

--

KAVS8115

--

--

--

--

--

--

--

KAVS8116

--

--

Y

--

Y

Y

Y

KAVS8120 -

KAVS8123

Y

--

Y#18

Y#18

--

--

--

KAVS8124

--

--

--

Y

--

--

--

KAVS8130

--

--

Y

--

Y

Y

--

KAVS8133 -

KAVS8136

--

--

Y

--

Y

Y

--

KAVS8137

--

--

--

--

--

--

--

KAVS8138

--

--

--

--

--

--

Y

KAVS8139 -

KAVS8140

--

--

--

--

--

--

--

KAVS8141 -

KAVS8142

--

--

Y

--

Y

Y

--

KAVS8143

--

--

Y

--

--

--

--

KAVS8144 -

KAVS8147

--

--

Y

--

--

--

--

KAVS8148

--

--

--

--

--

--

--

KAVS8149

--

--

--

--

--

--

Y

KAVS8158

--

--

--

--

--

--

--

KAVS8159

--

--

Y

--

--

--

Y

KAVS8160

--

--

Y

--

--

--

--

KAVS8161

--

--

--

--

Y

--

--

KAVS8162 -

KAVS8163

--

--

Y

--

--

--

--

KAVS8164 -

KAVS8165

--

--

--

--

Y

--

--

KAVS8180

Y

--

Y

--

--

--

--

KAVS8201 -

KAVS8202

Y

Y

Y

--

Y

--

--

KAVS8203 -

KAVS8204

Y

Y

Y

--

Y

Y

--

KAVS8205 -

KAVS8206

Y

Y

Y

Y

Y

Y

--

KAVS8208

Y

Y

Y

--

Y

Y

--

#1

This message is output according to the specifications of the AJSSYSLOG environment setting parameter.

For details about the environment setting parameters, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

#2

This message is output according to the specifications of the LOGDSYSLOG and HLOGDSYSLOG environment setting parameters.

For details about the environment setting parameters, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

#3

This message is output according to the specifications of the NETSYSLOG environment setting parameter.

For details about the environment setting parameters, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

#4

This message is output according to the specifications of the JOBDELAYWARNMSG and HNTRLOGLEVEL environment setting parameters.

For details about the environment setting parameters, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

#5

This message is output according to the specifications of the JOBSYSLOG environment setting parameter.

For details about the environment setting parameters, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

#6

This message is output according to the specifications of the SYSLOGJOBMSG environment setting parameter.

For details about the environment setting parameters, see 20.11 Setting up JP1/AJS3 shared information in the JP1/Automatic Job Management System 3 Configuration Guide.

#7

This message is output according to the specifications of the MONSYSLOG environment setting parameter.

For details about the environment setting parameters, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

#8

This message is output according to the specifications of the AUTHSYSLOG environment setting parameter.

For details about the environment setting parameters, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

#9

This message is output to the reorganization log.

#10

This message is not output when the ajsqlattach command or ajsqldetach command is executed.

#11

This message is output only to the internal log of the ajsmonsvr process.

#12

This message is not output when the ajsprofstatus command is executed.

#13

This message is output as embedded information in message KAVS8004-E.

#14

This message is output only to the internal log of the ajscdinetd process.

#15

This message is output only if an error occurs in the schedule control process.

#16

This message is output according to the specification of the CONRESTRICTSYSLOG environment setting parameter. For details about the environment setting parameters, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

#17

This message is output only to the internal log of the ajsinetd process.

#18

This message is not output in Windows.

1.3.3 Output destinations of messages beginning with KAVT

The following table lists the output destinations of the messages beginning with KAVT (messages about the event and action control).

The table uses the following abbreviations for the output destinations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

Exec details: Execution Result Details dialog box

JP1 event: JP1 event

Y: Is output.

--: Is not output.

Table 1‒8: The output destinations of messages beginning with KAVT

Message ID

Output destination

syslog

Event

log

HNTRLib2

stdout

stderr

Exec details

JP1 event

KAVT0001

--

--

Y#1

--

--

--

--

KAVT0002 -

KAVT0008

Y

Y

Y

--

--

--

--

KAVT0009

--

--

Y#1

--

--

--

--

KAVT0020 -

KAVT0023

--

--

Y#1

--

--

--

--

KAVT0025 -

KAVT0027

--

--

Y#1

--

--

--

--

KAVT0034 -

KAVT0036

--

--

Y#1

--

--

--

--

KAVT0039

--

--

--

--

--

Y

--

KAVT0042

--

--

Y#1

--

--

--

--

KAVT0043 -

KAVT0045

--

--

--

--

--

Y

--

KAVT0058 -

KAVT0094

--

--

Y#1

--

--

--

--

KAVT0098 -

KAVT0099

--

--

Y#1

--

--

--

--

KAVT0101 -

KAVT0106

--

--

Y#1

--

--

--

--

KAVT0108

--

--

Y#1

--

--

--

--

KAVT0110

--

--

Y#1

--

--

--

--

KAVT0116

--

--

Y#1

--

--

--

--

KAVT0118

--

--

Y#1

--

--

--

--

KAVT0145 -

KAVT0147

--

--

Y#1

--

--

--

--

KAVT0157

--

--

Y#1

--

--

--

--

KAVT0171

--

--

Y#1

--

--

--

--

KAVT0178 -

KAVT0187

--

--

Y#1

--

--

--

--

KAVT0193 -

KAVT0194

--

--

Y#1

--

--

--

--

KAVT0198 -

KAVT0199

--

--

Y#1

--

--

--

--

KAVT0247 -

KAVT0250

--

--

Y#1

--

--

--

--

KAVT0261

--

--

Y#1

--

--

--

--

KAVT0268

--

--

Y#1

--

--

--

--

KAVT0271 -

KAVT0273

--

--

Y#1

--

--

--

--

KAVT0280

--

--

Y#1

--

--

--

--

KAVT0281 -

KAVT0285

--

--

Y#1

--

--

--

--

KAVT0287

--

--

Y#1

--

--

--

--

KAVT0288 -

KAVT0289

--

--

Y

--

--

--

--

KAVT0293 -

KAVT0297

--

--

Y#1

--

--

--

--

KAVT0301 -

KAVT0303

--

--

Y#1

--

--

--

--

KAVT0325 -

KAVT0333

--

--

Y#1

--

--

--

--

KAVT0340 -

KAVT0347

--

--

Y

--

--

--

--

KAVT0351

Y#5

Y#5

Y

--

--

--

--

KAVT0352

--

--

Y#1

--

--

--

--

KAVT0353 -

KAVT0357

--

--

Y

--

--

--

--

KAVT0401

--

--

--

--

--

Y

--

KAVT0402 -

KAVT0403

--

--

Y#1

--

--

Y

--

KAVT0404 -

KAVT0406

--

--

--

--

--

Y

--

KAVT0408

--

--

Y#1

--

--

Y

--

KAVT0409 -

KAVT0411

--

--

--

--

--

Y

--

KAVT0412

--

--

Y#1

--

--

--

--

KAVT0413

--

--

Y

--

--

Y

--

KAVT0414

--

--

Y

--

Y#3

Y#4

--

KAVT0415 -

KAVT0416

--

--

Y

--

Y

--

--

KAVT0417

--

--

Y

--

--

--

--

KAVT0498 -

KAVT0499

--

--

--

--

--

--

Y

KAVT0502

--

--

Y#1

--

--

--

--

KAVT0508

--

--

Y#1

--

--

--

--

KAVT0511 -

KAVT0513

--

--

Y#1

--

--

--

--

KAVT0515

--

--

Y#1

--

--

--

--

KAVT0520 -

KAVT0524

--

--

Y#1

--

--

--

--

KAVT0526 -

KAVT0530

--

--

Y#1

--

--

--

--

KAVT0539 -

KAVT0542

--

--

Y#1

--

--

Y

--

KAVT0544

--

--

Y#1

--

--

--

--

KAVT0559

--

--

Y#1

--

--

--

--

KAVT0562 -

KAVT0563

Y

Y

Y

--

--

--

--

KAVT0566

--

--

Y#1

--

--

--

--

KAVT0567

--

--

Y#1

--

--

Y

--

KAVT0570

Y

Y

Y

--

--

--

--

KAVT0572

Y

Y

Y

--

--

--

--

KAVT0582

--

--

Y#1

--

--

--

--

KAVT0588 -

KAVT0590

--

--

Y#1

--

--

--

--

KAVT0591

--

--

Y

--

--

Y

--

KAVT0593

--

--

Y#1

--

--

--

--

KAVT0600

--

--

Y#1

--

--

--

--

KAVT0603

--

--

--

--

--

Y

--

KAVT0606 -

KAVT0618

--

--

Y#1

--

--

--

--

KAVT0620

--

--

Y#1

--

--

Y

--

KAVT0621

--

--

Y#1

--

--

--

--

KAVT0625

--

--

Y#1

--

--

--

--

KAVT0628 -

KAVT0629

--

--

Y#1

--

--

--

--

KAVT0632 -

KAVT0633

--

--

Y#1

--

--

--

--

KAVT0635

--

--

Y#1

--

--

--

--

KAVT0637

--

--

Y#1

--

--

--

--

KAVT0641 -

KAVT0643

--

--

Y#1

--

--

--

--

KAVT0649 -

KAVT0651

--

--

Y#1

--

--

--

--

KAVT0654

--

--

Y#1

--

--

--

--

KAVT0656 -

KAVT0662

--

--

Y

--

--

--

--

KAVT0663

--

--

Y

Y

--

--

--

KAVT0664 -

KAVT0667

--

--

Y

--

--

--

--

KAVT0900 -

KAVT0901

--

--

--

--

--

--

Y

KAVT0910 -

KAVT0911

--

--

Y#1

--

--

--

--

KAVT0912

Y

Y

Y

--

--

--

--

KAVT0950 -

KAVT0963

--

--

--

Y

--

--

--

KAVT0980 -

KAVT0981

--

--

Y#1

--

--

--

--

KAVT0992 -

KAVT0995

--

--

Y

--

--

--

--

KAVT1001 -

KAVT1002

--

--

Y#1

--

--

--

--

KAVT1003

Y

Y

Y

--

--

--

--

KAVT1004 -

KAVT1006

--

--

Y#1

--

--

--

--

KAVT1007

--

--

Y#1

--

--

Y

--

KAVT1008

Y

Y

Y

--

--

--

--

KAVT1013 -

KAVT1015

--

--

Y#1

--

--

Y

--

KAVT1017

--

--

--

--

--

Y

--

KAVT1025 -

KAVT1028

--

--

Y#1

--

--

Y

--

KAVT1029 -

KAVT1030

--

--

Y#1

--

--

--

--

KAVT1031

Y

Y

Y

--

--

Y

--

KAVT1032

Y

Y

Y

--

--

--

--

KAVT1033

--

--

Y#1

--

--

Y

--

KAVT1037 -

KAVT1040

Y

Y

Y

--

--

--

--

KAVT1041

--

--

Y#1

--

--

Y

--

KAVT1042

Y

Y

Y

--

--

--

--

KAVT1045 -

KAVT1048

--

--

Y#1

--

--

Y

--

KAVT1050

Y

Y

Y

--

--

--

--

KAVT1052 -

KAVT1056

--

--

Y#1

--

--

Y

--

KAVT1058 -

KAVT1061

--

--

--

--

--

Y

--

KAVT1062 -

KAVT1067

--

--

Y#1

--

--

--

--

KAVT1068

--

--

Y#1

--

--

Y

--

KAVT1069

--

--

Y#1

--

--

--

--

KAVT1200 -

KAVT1205

--

--

Y#1

--

--

Y

--

KAVT1206 -

KAVT1213

--

--

Y#1

--

--

Y

--

KAVT1214

--

--

Y#1

--

--

--

--

KAVT1217

--

--

Y#1

--

--

Y

--

KAVT1226

--

--

Y#1

--

--

--

--

KAVT2001

--

--

Y#1

--

--

--

--

KAVT2004 -

KAVT2007

--

--

--

--

--

Y

--

KAVT2012

--

--

Y#1

--

--

--

--

KAVT2013 -

KAVT2016

--

--

Y#1

--

--

Y

--

KAVT2017 -

KAVT2018

--

--

--

--

--

Y

--

KAVT2019

--

--

Y#1

--

--

--

--

KAVT2020

--

--

--

--

--

Y

--

KAVT2021 -

KAVT2024

--

--

Y#1

--

--

--

--

KAVT2025 -

KAVT2026

--

--

Y#1

--

--

Y

--

KAVT2028 -

KAVT2029

--

--

Y#1

--

--

--

--

KAVT2030 -

KAVT2033

--

--

Y#1

--

--

Y

--

KAVT2034

--

--

Y#1

--

--

--

--

KAVT2035 -

KAVT2038

--

--

Y#1

--

--

Y

--

KAVT2042

--

--

Y

--

--

--

--

KAVT3001 -

KAVT3015

--

--

Y

--

--

--

--

KAVT3016

--

--

Y

--

--

Y

--

KAVT3017 -

KAVT3040

--

--

Y

--

--

--

--

KAVT3041

--

--

Y

--

--

Y

--

KAVT3042 -

KAVT3206

--

--

Y

--

--

--

--

KAVT3207

--

--

Y

--

--

Y

--

KAVT3210 -

KAVT3212

--

--

Y

--

--

--

--

KAVT3268 -

KAVT3271

--

--

Y

--

--

Y

--

KAVT3273 -

KAVT3274

--

--

Y

--

--

Y

--

KAVT3275

--

--

Y

--

--

--

--

KAVT3276 -

KAVT3295

--

--

Y

--

--

Y

--

KAVT3296 -

KAVT3304

--

--

Y

--

--

--

--

KAVT3306 -

KAVT3307

--

--

Y

--

--

--

--

KAVT3308

--

--

Y

--

--

Y

--

KAVT3401

--

Y

Y

--

--

--

--

KAVT3402

--

--

Y

--

--

--

--

KAVT3403

--

Y

Y

--

--

--

--

KAVT3404 -

KAVT3405

--

--

Y

--

--

--

--

KAVT3406

--

Y

Y

--

--

--

--

KAVT3407

--

--

Y

--

--

--

--

KAVT3408

--

Y

Y

--

--

--

--

KAVT3409 -

KAVT3420

--

--

Y

--

--

--

--

KAVT3451 -

KAVT3457

--

--

Y

--

--

Y

--

KAVT3458 -

KAVT3460

--

--

Y

--

--

--

--

KAVT3461 -

KAVT3468

--

--

Y

--

--

Y

--

KAVT3469

--

--

Y

--

--

--

--

KAVT3473 -

KAVT3499

--

--

Y

--

--

Y

--

KAVT3501 -

KAVT3502

--

--

Y#1

--

--

--

--

KAVT3504

Y

--

Y#1

--

--

Y

--

KAVT3512

--

--

Y#1

--

--

Y

--

KAVT3513

Y

Y

Y

--

--

Y

--

KAVT3514

Y

Y

Y

--

--

--

--

KAVT3515

Y

Y

Y

--

--

Y

--

KAVT3519

--

--

Y#1

--

--

Y

--

KAVT3520

Y

Y

Y

--

--

--

--

KAVT3521

--

--

Y#1

--

--

Y

--

KAVT3522

--

--

Y#1

--

--

--

--

KAVT3523 -

KAVT3524

--

--

Y#1

--

--

Y

--

KAVT3525 -

KAVT3533

--

--

Y#1

--

--

--

--

KAVT3534

Y

Y

Y

--

--

--

--

KAVT3538 -

KAVT3555

--

--

Y#1

--

--

--

--

KAVT3556 -

KAVT3558

--

--

Y#1

--

--

Y

--

KAVT3559 -

KAVT3566

--

--

Y#1

--

--

--

--

KAVT3567 -

KAVT3570

--

--

Y#1

--

--

Y

--

KAVT3571 -

KAVT3586

--

--

Y#1

--

--

--

--

KAVT3587

--

--

Y#1

--

--

Y

--

KAVT3588 -

KAVT3596

--

--

Y#1

--

--

--

--

KAVT3597

--

--

Y#1

--

--

Y

--

KAVT3598 -

KAVT3599

--

--

Y#1

--

--

--

--

KAVT3700 -

KAVT3720

--

--

Y#1

--

--

Y

--

KAVT3721 -

KAVT3723

--

--

--

--

--

Y

--

KAVT3801 -

KAVT3824

--

--

Y#2

--

--

--

--

KAVT3825 -

KAVT3836

--

--

Y

--

--

Y

--

KAVT3837 -

KAVT3844

--

--

Y

--

Y

--

--

KAVT3845 -

KAVT3846

--

--

Y

--

--

Y

--

KAVT3847 -

KAVT3849

--

--

Y

--

Y

--

--

KAVT3850 -

KAVT3852

--

--

Y

--

--

Y

--

KAVT4255 -

KAVT4256

--

--

Y

--

--

Y

--

KAVT6001 -

KAVT6006

--

--

--

--

--

Y

--

KAVT6100 -

KAVT6104

--

--

--

--

--

Y

--

KAVT7001 -

KAVT7002

--

--

Y#1

--

--

--

--

KAVT7003

--

--

--

--

--

Y

--

KAVT7004

--

--

Y#1

--

--

--

--

KAVT7005 -

KAVT7006

--

--

--

--

--

Y

--

KAVT7007 -

KAVT7011

--

--

Y#1

--

--

--

--

KAVT7012 -

KAVT7016

--

--

Y#1

--

--

Y

--

KAVT7017

--

--

--

--

--

Y

--

KAVT7501 -

KAVT7514

--

--

Y#2

--

--

Y

--

KAVT7515

--

--

--

--

--

Y

--

KAVT8001 -

KAVT8340

--

--

Y#2

--

Y

--

--

KAVT8341

--

--

--

--

Y

--

--

KAVT8342

--

--

Y

--

Y

--

--

KAVT8343

--

--

--

--

Y

--

--

KAVT8347

--

--

--

--

Y

--

--

KAVT8351 -

KAVT8352

--

--

Y

--

Y

--

--

KAVT8401 -

KAVT8406

--

--

Y#2

--

--

--

--

KAVT8408 -

KAVT8417

--

--

--

--

Y

--

--

#1

If error messages output for jobs have been specified as going to syslog files, messages with a message type of Error (E) are also output to the syslog. The values of Facility for these messages is LOG_DAEMON.

#2

If error messages output for jobs have been specified as going to syslog files, messages with a message type of Error (E) are also output to the syslog. The values of Facility for these messages is LOG_USER.

#3

This message is output when the jpomanevreset command is executed.

#4

This message is output when one of the following operations is performed:

- Registering an event job or a jobnet with startup condition for execution

- Restarting the agent while an event job or a jobnet with startup conditions is being monitored

- Restarting the manager while an event job or a jobnet with startup conditions is being monitored

- Restarting the scheduler service while an event job or a jobnet with startup conditions is being monitored

#5

This message is output according to the specifications of the AGMPUTSYSLOG environment setting parameter.

For details about the environment setting parameters, see 20.12 Environment settings for monitoring agents in the JP1/Automatic Job Management System 3 Configuration Guide.

For details on the settings for outputting error messages for jobs to syslog, see 15.6.1 Settings for outputting error messages for jobs to syslog in the JP1/Automatic Job Management System 3 Configuration Guide.

1.3.4 Output destinations of messages beginning with KAVU

The following table lists the output destinations of the messages beginning with KAVU (messages for the job execution control). Note that the table excludes the messages KAVU8901-E to KAVU8918-E because they might be output to the log file (jajs_migrate_logical-host-name_N.log) only when the jajs_migrate command with the -convert option specified is run.

The table uses the following abbreviations for the output destinations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

Exec details: Execution Result Details dialog box

JP1 event: JP1 event

Y: Is output.

--: Is not output.

Table 1‒9: The output destinations of messages beginning with KAVU

Message ID

Output destination

syslog

Event

log

HNTRLib2

stdout

stderr

Exec details

JP1

event

KAVU0200

--

--

Y#1

--

--

--

--

KAVU0201 -

KAVU0203

Y#2

Y#2

Y#1

--

--

--

--

KAVU0204

--

--

Y#1

--

--

--

--

KAVU0205 -

KAVU0206

Y#2

Y#2

Y#1

--

--

--

--

KAVU0207 -

KAVU0214

--

--

Y#1

--

--

--

--

KAVU0215 -

KAVU0221

Y#2

Y#2

Y#1

--

--

--

--

KAVU0222 -

KAVU0223

--

--

Y#1

--

--

--

--

KAVU0224 -

KAVU0225

Y#2

Y#2

Y#1

--

--

--

--

KAVU0226 -

KAVU0232

--

--

Y#1

--

--

--

--

KAVU0233

--

--

Y#1

--

--

Y

--

KAVU0234

--

--

Y#1

--

--

--

--

KAVU0235

Y#2

Y#2

Y#1

--

--

--

--

KAVU0236

--

--

Y#1

--

--

--

--

KAVU0237 -

KAVU0242

Y#2

Y#2

Y#1

--

--

--

--

KAVU0243

--

--

Y#1

--

--

--

--

KAVU0244

Y#2

Y#2

Y#1

--

--

--

--

KAVU0245 -

KAVU0247

--

--

Y#1

--

--

--

--

KAVU0248 -

KAVU0252

Y#2

Y#2

Y#1

--

--

--

--

KAVU0253 -

KAVU0268

--

--

Y#1

--

--

--

--

KAVU0269

--

--

Y#1

--

--

Y

--

KAVU0270

--

--

Y#1

--

--

--

--

KAVU0271

--

--

Y

--

--

Y

--

KAVU0300 -

KAVU0467

--

--

Y#1

--

--

--

--

KAVU0470 -

KAVU0471

--

--

--

--

Y

--

--

KAVU0474

--

--

Y#1

--

--

--

--

KAVU0476 -

KAVU0490

--

--

Y#1

--

--

--

--

KAVU0491 -

KAVU0492

--

--

Y

--

--

Y

--

KAVU0500

--

--

Y#1

--

--

--

--

KAVU0800 -

KAVU0875

--

--

--

Y

--

--

--

KAVU0900 -

KAVU0999

--

--

--

--

Y

--

--

KAVU1100 -

KAVU1106

Y

Y

Y

--

--

--

--

KAVU1931

--

--

--

--

Y

--

--

KAVU1201 -

KAVU2236

--

--

Y#3

--

--

--

--

KAVU2237 -

KAVU2242

--

--

Y#3

--

--

--

--

KAVU2243 -

KAVU2246

--

--

Y#3

--

--

--

--

KAVU2249 -

KAVU2252

--

--

Y

--

--

--

--

KAVU2260

--

--

Y

--

--

--

--

KAVU3100 -

KAVU3104

Y

Y

Y

--

--

--

--

KAVU3105

Y

--

Y

--

--

--

--

KAVU3110 -

KAVU3111

Y

Y

Y

--

--

--

--

KAVU3112

Y

--

Y

--

--

--

--

KAVU3200 -

KAVU3212

--

--

Y#3

--

--

--

--

KAVU3213 -

KAVU3217

--

--

Y

--

--

--

--

KAVU3221 -

KAVU3599

--

--

Y#3

--

--

--

--

KAVU3296

--

--

Y

--

--

--

--

KAVU3500 -

KAVU3599

--

--

Y#3

--

--

--

--

KAVU3607#4, #5

--

--

--

--

--

--

--

KAVU3608

--

--

Y#4, #5

--

--

Y#5

--

KAVU3800

--

--

--

Y

--

--

--

KAVU3900 -

KAVU3906

--

--

--

--

Y

--

--

KAVU4100 -

KAVU4113

Y

Y

Y

--

--

--

--

KAVU4200 -

KAVU4293

--

--

Y#3

--

--

--

--

KAVU4294 -

KAVU4296

--

--

Y#3

--

--

Y

--

KAVU4297

--

--

Y#3

--

--

--

--

KAVU4299

--

--

--

--

--

Y

--

KAVU4300 -

KAVU4312

--

--

Y#3

--

--

--

--

KAVU4314 -

KAVU4315

--

--

Y#3

--

--

Y

--

KAVU4331

--

--

Y#3

--

--

--

--

KAVU4333

--

--

Y

--

--

--

--

KAVU4334

--

--

Y#3

--

--

--

--

KAVU4335

--

--

Y

--

--

--

--

KAVU4500 -

KAVU4503

--

--

Y#3

--

--

--

--

KAVU4504

--

--

Y#3

--

--

Y

--

KAVU4505 -

KAVU4526

--

--

Y#3

--

--

--

--

KAVU4529 -

KAVU4538

--

--

Y#3

--

--

--

--

KAVU4540 -

KAVU4545

--

--

Y#3

--

--

--

--

KAVU4546 -

KAVU4576

--

--

Y#3

--

--

Y

--

KAVU4578

--

--

Y#3

--

--

Y

--

KAVU4580 -

KAVU4591

--

--

Y#3

--

--

Y

--

KAVU4593 -

KAVU4594

--

--

Y#3

--

--

Y

--

KAVU4596 -

KAVU4598

--

--

Y#3

--

--

Y

--

KAVU4700 -

KAVU4704

--

--

Y#3

--

--

Y

--

KAVU4717 -

KAVU4718

--

--

Y#3

--

--

--

--

KAVU4720

--

--

Y#3

--

--

--

--

KAVU4721

--

--

Y

--

--

Y

--

KAVU5002 -

KAVU5007

--

--

--

--

Y

--

--

KAVU5009

Y

Y

--

--

Y

--

--

KAVU5012 -

KAVU5014

--

--

--

--

Y

--

--

KAVU5015

--

--

Y#1

Y

--

--

--

KAVU5016

--

--

Y#1

--

Y

--

--

KAVU5100

Y

Y

Y

--

--

--

--

KAVU5200 -

KAVU5296

--

--

Y#1

--

--

--

--

KAVU5309 -

KAVU5311

--

--

Y

--

--

--

--

KAVU5501 -

KAVU5202

--

--

Y#1

--

--

--

--

KAVU5800 -

KAVU5801

--

--

--

Y

--

--

--

KAVU5900 -

KAVU5971

--

--

--

--

Y

--

--

KAVU5980 -

KAVU5984

Y#6

Y#6

--

--

Y#6

--

Y#6

KAVU5986 -

KAVU5987

--

--

--

--

Y

--

--

KAVU5986

--

--

--

--

Y

--

--

KAVU6100 -

KAVU6109

Y

Y

Y

--

--

--

--

KAVU6200 -

KAVU6218

--

--

Y#1

--

--

--

--

KAVU7110 -

KAVU7111

Y

--

Y

--

--

--

--

KAVU7112 -

KAVU7113

Y

Y

Y

--

--

--

--

KAVU7200 -

KAVU7242

--

--

Y#1

--

--

--

--

KAVU7530 -

KAVU7535

--

--

Y#1

--

--

--

--

#1

Messages with a message type of Error (-E) can also be output to syslog according to the specifications of the SYSLOGJOBMSG environment setting parameter. The value of Facility for these messages is LOG_DAEMON or LOG_USER.

For details about the environment setting parameters, see 15.6.1 Settings for outputting error messages for jobs to syslog in the JP1/Automatic Job Management System 3 Configuration Guide.

#2

This message is not output to syslog and the Windows event log when a job execution control command is executed or job registration fails from a jobnet.

#3

Messages with a message type of Error (-E) can also be output to syslog according to the specifications of the SYSLOGJOBMSG environment setting parameter. The value of Facility for these messages is LOG_DAEMON.

For details about the environment setting parameters, see 15.6.1 Settings for outputting error messages for jobs to syslog in the JP1/Automatic Job Management System 3 Configuration Guide.

#4

This message is output only when JP1/AJS3 - Agent Minimal Edition is used.

#5

This message is also output to the job execution history log file for JP1/AJS3 - Agent Minimal Edition.

#6

Output destinations of these messages depend on an option specified for the command.

1.3.5 Output destinations of messages beginning with KAVV

The following table lists the output destinations of the messages beginning with KAVV (messages for the JP1/AJS3 - View).

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\log\ajs2view#nnnn_{1|2}.log

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

Supplementary notes

If a single unit of JP1/AJS3 - View is running, #nnnn_ is not displayed. If more than one unit of JP1/AJS3 - View is running, any value from 0001 to 9999 is assigned to #nnnn_.

JP1/AJS3 uses the JP1/Base process monitor. When monitoring troubles in JP1/AJS3, also monitor messages related to the JP1/Base process monitor.

If the multi-user remote desktop connection function is enabled, the message destination is changed to the following log file:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\log\OS-user-name\ajs2view[#nnnn_]{1|2}.log

1.3.6 Output destinations of messages beginning with KFP

Output destinations of messages whose message ID begins with KFP (messages about embedded databases) can be identified by the output destination type shown in the explanation of each message. The following shows the meaning of the output destination types:

A: Embedded type (output as embedded information in another message)

E: Standard error output

L: Windows event log or syslog

S: Standard output

1.3.7 Output destinations of messages beginning with KNAC

Messages whose message ID begins with KNAC are output by communication control or agent management. The tables in the following subsections list the output destinations for each type of message.

(1) KNAC0001 to KNAC0999 (messages output by communication control)

The table below lists the output destinations of messages output by communication control.

The table uses the following abbreviations for the output destinations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

Exec details: Execution Result Details dialog box

JP1 event: JP1 event

Y: Is output.

--: Is not output.

Table 1‒10: The output destinations of messages output by communication control

Message ID

Output destination

syslog

Event

log

HNTRLib2

stdout

stderr

Exec details

JP1

event

KNAC0001 -

KNAC0002

--

--

Y

--

--

--

--

KNAC0003 -

KNAC0011

Y

Y

Y

--

--

--

--

KNAC0013

--

--

Y

--

--

--

--

KNAC0014

Y

Y

Y

--

--

--

--

KNAC0401

--

--

Y

--

--

--

--

KNAC0604

--

--

Y

--

--

--

--

KNAC0607

--

--

Y

--

--

--

--

KNAC0609 -

KNAC0610

--

--

Y

--

--

--

--

(2) KNAC1001 to KNAC1999 (messages output by agent management)

The table below lists the output destinations of messages output by agent management.

The table uses the following abbreviations for the output destinations:

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

Exec details: Execution Result Details dialog box

JP1 event: JP1 event

Y: Is output.

--: Is not output.

Table 1‒11: The output destinations of messages output by agent management

Message ID

Output destination

syslog

Event

log

HNTRLib2

stdout

stderr

Exec details

JP1

event

KNAC1001 -

KNAC1002

--

--

Y

--

--

--

--

KNAC1003

Y

Y

Y

--

--

--

--

KNAC1100 -

KNAC1102

--

--

--

--

Y

--

--

KNAC1111 -

KNAC1131

--

--

--

--

Y

--

--

KNAC1200 -

KNAC1204

--

--

--

--

Y

--

--

KNAC1500 -

KNAC1501

--

--

Y

--

Y

--

--

KNAC1503 -

KNAC1506

--

--

Y

--

Y

--

--

KNAC1507

--

--

--

--

Y

--

--

KNAC1508 -

KNAC1510

--

--

Y

--

Y

--

--

KNAC1511 -

KNAC1512

--

--

--

--

Y

--

--

KNAC1513 -

KNAC1518

--

--

Y

--

Y

--

--

KNAC1519

--

--

Y

--

--

--

--

KNAC1520

Y

Y

Y

--

--

--

--

KNAC1521

--

--

Y

--

--

--

--

KNAC1701 -

KNAC1711

Y#

Y#

Y

--

--

--

--

KNAC1713 -

KNAC1714

Y#

Y#

Y

--

--

--

--

KNAC1771

--

--

--

--

Y

--

--

KNAC1772 -

KNAC1773

--

--

Y

--

Y

--

--

KNAC1774 -

KNAC1776

Y

Y

Y

--

Y

--

--

KNAC1777 -

KNAC1778

--

--

--

--

Y

--

--

KNAC1801 -

KNAC1809

Y

Y

Y

--

--

--

--

#

This message is output according to the specifications of the AGMPUTSYSLOG environment setting parameter.

For details about the environment setting parameters, see 20.12 Environment settings for monitoring agents in the JP1/Automatic Job Management System 3 Configuration Guide.

1.3.8 Output destinations of messages beginning with KNAD

Messages whose message ID begins with KNAD3501 to KNAD3986 are system management messages. The following table lists the output destinations of those system management messages.

The table uses the following abbreviations for the output destinations:

Dialog: Message dialog box

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

JP1 event: JP1 event

Y: Is output.

--: Is not output.

Table 1‒12: The output destinations of system management messages

Message ID

Output destination

Dialog

syslog

Event

log

HNTRLib2

stdout

stderr

JP1

event

KNAD1000 -

KNAD1021

Y

--

--

--

--

--

--

KNAD1301 -

KNAD1306

Y

--

--

--

--

--

--

KNAD1500 -

KNAD1501

Y

--

--

--

--

--

--

KNAD1700 -

KNAD1704

Y

--

--

--

--

--

--

KNAD3501

--

Y

Y

--

--

--

--

KNAD3502

--

--

--

Y

--

Y

--

KNAD3503

--

--

--

--

--

Y

--

KNAD3504

--

--

--

Y

--

Y

--

KNAD3516

--

Y

--

--

--

Y

--

KNAD3552 -

KNAD3612

--

--

--

Y

--

--

--

KNAD3613

--

Y

Y

Y

--

--

Y

KNAD3614

--

Y

Y

Y

--

--

--

KNAD3616 -

KNAD3617

--

--

--

--

--

--

Y

KNAD3620

--

Y

Y

Y

Y

--

--

KNAD3621

--

Y

--

Y

--

--

--

KNAD3623

--

Y

--

Y

--

--

--

KNAD3624

--

Y

Y

Y

--

--

--

KNAD3625 -

KNAD3626

--

Y

Y

Y

Y

--

--

KNAD3627

--

--

--

Y

--

--

--

KNAD3631

--

--

--

Y

--

--

--

KNAD3638

--

--

--

Y

Y

--

--

KNAD3642 -

KNAD3644

--

Y

Y

Y

--

--

--

KNAD3645 -

KNAD3647

--

--

--

Y

--

--

--

KNAD3649

--

Y

Y

Y

Y

--

--

KNAD3650 -

KNAD3662

--

--

--

Y

Y

--

--

KNAD3663

--

--

--

--

--

Y

--

KNAD3669

--

--

--

--

Y

--

--

KNAD3670 -

KNAD3678

--

--

--

Y

Y

--

--

KNAD3686

--

Y

Y

Y

--

--

--

KNAD3687

--

--

--

--

Y

--

--

KNAD3688 -

KNAD3694

--

--

--

--

Y

--

--

KNAD3695

--

--

--

--

Y

--

--

KNAD3699

--

--

--

Y

--

--

--

KNAD3705 -

KNAD3736

--

--

--

Y

--

--

--

KNAD3737

--

Y

Y

Y

--

--

Y

KNAD3742 -

KNAD3745

--

--

--

Y

--

--

--

KNAD3746

--

--

--

--

--

--

Y

KNAD3747 -

KNAD3751

--

--

--

Y

--

--

--

KNAD3752 -

KNAD3753

--

Y

Y

Y

--

--

--

KNAD3757

--

--

--

Y

--

--

--

KNAD3759

--

--

--

Y

--

--

--

KNAD3760 -

KNAD3769

--

--

--

Y

--

--

--

KNAD3777 -

KNAD3786

--

--

--

Y

--

--

--

KNAD3788

--

Y

Y

Y

--

--

--

KNAD3792

--

--

Y

--

--

--

--

KNAD3855

--

--

--

Y

--

--

--

KNAD3862

--

Y

Y

Y

--

--

--

KNAD3870

--

Y

Y

--

Y

--

--

KNAD3871

--

--

--

--

Y

--

--

KNAD3872

--

Y

Y

--

Y

--

--

KNAD3873

--

--

--

--

Y

--

--

KNAD3874 -

KNAD3875

--

Y

Y

--

Y

--

--

KNAD3876

--

--

--

Y

--

--

--

KNAD3877 -

KNAD3880

--

--

--

Y

--

--

--

KNAD3899

--

Y

Y

--

Y

--

--

KNAD3905 -

KNAD3910

--

--

--

Y

--

--

--

KNAD3911 -

KNAD3914

--

--

--

Y

Y

--

--

KNAD3935

--

--

--

Y

--

--

--

KNAD3953

--

Y

Y

Y

--

--

Y

KNAD3960

--

--

--

--

Y

--

--

KNAD3961

--

--

--

Y

Y

--

--

KNAD3970 -

KNAD3971

--

Y

Y

Y

Y

--

--

KNAD3972 -

KNAD3973

--

--

--

--

Y

--

--

KNAD3974

--

Y

Y

Y

--

--

--

KNAD3975

--

Y

Y

Y

Y

--

--

KNAD3976

--

Y

Y

Y

--

--

--

KNAD3977 -

KNAD3978

--

Y

Y

Y

Y

--

--

KNAD3979

--

Y

Y

Y

--

--

--

KNAD3981 -

KNAD3984

--

--

--

Y

--

--

--

KNAD3985 -

KNAD3986

--

--

--

Y

Y

--

--

KNAD3991 -

KNAD3994

--

Y

Y

Y

Y

--

--

KNAD3995 -

KNAD3996

--

Y

Y

Y

--

--

--

1.3.9 Output destinations of messages beginning with KNAK

Messages whose message ID begins with KNAK are messages about JP1/AJS3 - Web Console. The tables in the following subsections list the output destinations for each type of message.

(1) KNAK1601 to KNAK1700 (messages about the JP1/AJS3 - Web Console installer)

The table below lists the output destinations of messages about the JP1/AJS3 - Web Console installer.

The table uses the following abbreviations for the output destinations:

Dialog: Message dialog box

syslog: syslog

Event log: Windows event log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

JP1 event: JP1 event

Y: Is output.

--: Is not output.

Table 1‒13: Output destinations of messages about the JP1/AJS3 - Web Console installer

Message ID

Output destination

Dialog

syslog

Event

log

HNTRLib2

stdout

stderr

JP1

event

KNAK1601 -

KNAK1610

Y

--

--

--

--

--

--

KNAK1671 -

KNAK1672

Y

--

--

--

--

--

--

(2) KNAK2001 to KNAK2500 (Web GUI messages)

Web GUI messages are displayed on a web browser.

(3) KNAK2501 to KNAK3000 (messages about JP1/AJS3 - Web Console commands)

The table below lists the output destinations of messages about JP1/AJS3 - Web Console commands.

The table uses the following abbreviations for the output destinations:

syslog: syslog

Event log: Windows event log

App log: Application server log

Cmd log: Command log

HNTRLib2: Integrated trace log

stdout: Standard output

stderr: Standard error output

API: API response

Web: Display on the web browser

Y: Is output.

--: Is not output.

Table 1‒14: Output destinations of messages about JP1/AJS3 - Web Console commands

Message ID

Output destination

syslog

Event

log

App log

Cmd log

HNTRLib2

stdout

stderr

Web

API

KNAK2501

--

--

--

Y

--

--

--

--

--

KNAK2502

Y

Y

--

Y

Y

Y

--

--

--

KNAK2503

Y

Y

--

Y

Y

--

Y

--

--

KNAK2504 -

KNAK2505

--

--

--

Y

--

--

Y

--

--

KNAK2506

--

--

--

Y

--

--

--

--

--

KNAK2507

Y

Y

--

Y

Y

Y

--

--

--

KNAK2511 -

KNAK2516

--

--

--

Y

--

--

--

--

--

KNAK2517 -

KNAK2519

--

--

--

Y

--

--

Y

--

--

KNAK2520 -

KNAK2521

--

--

--

Y

--

Y

--

--

--

KNAK2522 -

KNAK2525

--

--

--

Y

--

--

Y

--

--

KNAK2526

--

--

--

Y

--

--

--

--

--

KNAK2528 -

KNAK2529

--

--

--

Y

--

--

--

--

--

KNAK2551 -

KNAK2558

--

--

--

Y

--

--

Y

--

--

KNAK2601

Y

Y

--

Y

--

--

Y

--

--

KNAK2602 -

KNAK2603

--

--

--

Y

--

--

Y

--

--

KNAK2651 -

KNAK2660

--

--

--

Y

--

--

Y

--

--

KNAK2701

--

--

--

--

--

Y

--

--

--

KNAK2702

--

--

--

Y

--

Y

--

--

--

KNAK2703

--

--

--

Y

--

--

Y

--

--

KNAK2708

--

--

--

Y

Y

--

Y

--

--

KNAK2709 -

KNAK2712

--

--

--

Y

--

--

Y

--

--

KNAK2714 -

KNAK2715

--

--

--

Y

--

--

Y

--

--

(4) KNAK3001 to KNAK4000 (messages about the web application server and APIs)

The table below lists the output destinations of messages about the web application server and APIs.

The table uses the following abbreviations for the output destinations:

syslog: syslog

Event log: Windows event log

App log: Application server log

Cmd log: Command log

HNTRLib2: Integrated trace log

stderr: Standard error output

API: API response

Web: Display on the web browser

Y: Is output.

--: Is not output.

Table 1‒15: Output destinations of messages about the web application server and APIs

Message ID

Output destination

syslog

Event

log

App log

Cmd log

HNTRLib2

stderr

Web

API

KNAK3001

--

--

Y

--

--

--

--

--

KNAK3002 -

KNAK3004

--

--

Y

--

--

--

--

--

KNAK3005

--

--

Y

--

--

--

--

--

KNAK3006

--

--

Y

--

--

--

--

--

KNAK3026 -

KNAK3033

--

--

Y

--

--

--

--

--

KNAK3051 -

KNAK3066

--

--

Y

--

--

--

--

--

KNAK3101 -

KNAK3102

--

--

Y

--

--

--

Y

Y

KNAK3103 -

KNAK3106

--

--

Y

--

--

--

--

--

KNAK3151 -

KNAK3153

--

--

Y

--

--

--

--

--

KNAK3201

--

--

Y

--

--

--

--

Y

KNAK3202

--

--

Y

--

--

--

Y

Y

KNAK3203

--

--

Y

--

--

--

--

Y

KNAK3204 -

KNAK3205

--

--

Y

--

--

--

Y

Y

KNAK3206 -

KNAK3208

--

--

Y

--

--

--

--

Y

KNAK3209

--

--

Y

--

--

--

Y

Y

KNAK3210

--

--

Y

--

--

--

--

Y

KNAK3211 -

KNAK3212

--

--

Y

--

--

--

Y

Y

KNAK3213 -

KNAK3214

--

--

Y

--

--

--

--

Y

KNAK3215 -

KNAK3216

--

--

Y

--

--

--

Y

Y

KNAK3218

--

--

Y

--

--

--

--

Y

KNAK3219 -

KNAK3231

--

--

Y

--

--

--

Y

Y

KNAK3232 -

KNAK3233

--

--

Y

--

--

--

--

Y

KNAK3234 -

KNAK3237

--

--

Y

--

--

--

Y

Y

KNAK3238 -

KNAK3240

--

--

Y

--

--

--

--

Y

KNAK3241

--

--

Y

--

--

--

--

Y

KNAK3243 -

KNAK3248

--

--

Y

--

--

--

--

Y

KNAK3249

--

--

Y

--

--

--

Y

Y

KNAK3250 -

KNAK3251

--

--

Y

--

--

--

--

Y

KNAK3401 -

KNAK3403

--

--

Y

--

--

--

Y

Y

KNAK3405

--

--

Y

--

--

--

Y

Y

KNAK3409 -

KNAK3414

--

--

Y

--

--

--

Y

Y

KNAK3460

--

--

Y

--

--

--

Y

Y

KNAK3463

--

--

Y

--

--

--

Y

Y

KNAK3480 -

KNAK3481

--

--

Y

--

--

--

--

--

KNAK3483 -

KNAK3484

--

--

Y

--

--

--

--

--

KNAK3485 -

KNAK3486

--

--

Y

--

--

--

Y

Y

KNAK3601 -

KNAK3688

--

--

Y

--

--

--

Y

Y

KNAK3689

--

--

Y

--

--

--

--

--

KNAK3690 -

KNAK3691

--

--

Y

--

--

--

Y

Y

KNAK3901 -

KNAK3904

--

--

Y

--

--

--

Y

Y

KNAK3905

--

--

Y

--

--

--

--

--

1.4 List of Windows event logs and syslogs

1.4.1 List of messages output to the Windows event log and syslog

This section lists the Windows event logs and syslogs that JP1/AJS3 outputs.

Table 1‒16: Windows event logs and syslogs

Message ID

Windows (Application log)

UNIX (syslog)

Event ID

Type

Facility

Level

KAVC0001-I

10001

Information

LOG_DAEMON

LOG_INFO

KAVC0002-I

10002

Information

LOG_DAEMON

LOG_INFO

KAVC0108-E

10108

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC0330-E

10330

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC0331-E

10331

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC0356-E

10356

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC0802-E

10802

Error

LOG_DAEMON

LOG_ERR

KAVC0805-E

10805

Error

LOG_DAEMON

LOG_ERR

KAVC0807-E

10807

Error

LOG_DAEMON

LOG_ERR

KAVC0901-E

10901

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC0902-E

10902

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC0903-E

10903

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC0904-E

10904

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC0905-E

10905

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC0907-E

10907

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC0916-E

--

--

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC0920-W

10920

Warning

LOG_DAEMON, LOG_USER

LOG_WARNING

KAVC0943-E

10943

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC0950-E

10950

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC0951-E

10951

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC0953-E

10953

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC2001-I

12001

Information

LOG_DAEMON

LOG_INFO

KAVC2002-I

12002

Information

LOG_DAEMON

LOG_INFO

KAVC2108-E

12108

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC2330-E

12330

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC2331-E

12331

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC2805-E

12805

Error

LOG_DAEMON

LOG_ERR

KAVC2901-E

12901

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC2902-E

12902

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC2903-E

12903

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC2904-E

12904

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC2905-E

12905

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC2907-E

12907

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC2916-E

--

--

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC2920-W

12920

Warning

LOG_DAEMON, LOG_USER

LOG_WARNING

KAVC2943-E

12943

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC2950-E

12950

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC2951-E

12951

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVC2953-E

12953

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0119-E

30119

Error

LOG_DAEMON

LOG_ERR

KAVS0125-E

30125

Error

LOG_DAEMON

LOG_ERR

KAVS0132-E

30132

Error

LOG_DAEMON

LOG_ERR

KAVS0135-E

30135

Error

LOG_DAEMON

LOG_ERR

KAVS0168-E

30168

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0176-E

30176

Error

LOG_DAEMON

LOG_ERR

KAVS0189-E

30189

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0200-I

30200

Information

LOG_DAEMON

LOG_INFO

KAVS0201-I

30201

Information

LOG_DAEMON

LOG_INFO

KAVS0202-E

30202

Error

LOG_DAEMON

LOG_ERR

KAVS0203-I

30203

Information

LOG_DAEMON

LOG_INFO

KAVS0204-E

30204

Error

LOG_DAEMON

LOG_ERR

KAVS0210-I

30210

Information

LOG_USER

LOG_INFO

KAVS0211-W

30211

Warning

LOG_DAEMON

LOG_WARNING

KAVS0213-I

30213

Information

LOG_DAEMON

LOG_INFO

KAVS0214-I

30214

Information

LOG_DAEMON

LOG_INFO

KAVS0215-I

30215

Information

LOG_DAEMON

LOG_INFO

KAVS0216-E

30216

Error

LOG_DAEMON

LOG_ERR

KAVS0217-E

30217

Error

LOG_DAEMON

LOG_ERR

KAVS0218-E

30218

Error

LOG_DAEMON

LOG_ERR

KAVS0220-I

30220

Information

LOG_DAEMON

LOG_INFO

KAVS0221-I

30221

Information

LOG_DAEMON

LOG_INFO

KAVS0230-E

30230

Error

LOG_DAEMON

LOG_ERR

KAVS0231-W

30231

Warning

LOG_DAEMON

LOG_WARNING

KAVS0232-W

30232

Warning

LOG_DAEMON

LOG_WARNING

KAVS0240-I

30240

Information

LOG_DAEMON

LOG_INFO

KAVS0241-I

30241

Information

LOG_DAEMON

LOG_INFO

KAVS0243-E

30243

Error

LOG_DAEMON

LOG_ERR

KAVS0244-E

30244

Error

LOG_DAEMON

LOG_ERR

KAVS0245-W

30245

Warning

LOG_DAEMON

LOG_WARNING

KAVS0246-E

30246

Error

LOG_DAEMON

LOG_ERR

KAVS0248-I

30248

Information

LOG_DAEMON

LOG_INFO

KAVS0260-I

30260

Information

LOG_DAEMON

LOG_INFO

KAVS0261-I

30261

Information

LOG_DAEMON

LOG_INFO

KAVS0262-E

30262

Error

LOG_DAEMON

LOG_ERR

KAVS0263-I

30263(31263)

Information

LOG_DAEMON

LOG_INFO

KAVS0264-I

30264(31264)

Information

LOG_DAEMON

LOG_INFO

KAVS0265-E

30265(31265)

Error

LOG_DAEMON

LOG_ERR

KAVS0266-I

30266(31266)

Information

LOG_DAEMON

LOG_INFO

KAVS0267-I

30267

Information

LOG_DAEMON

LOG_INFO

KAVS0268-W

30268

Warning

LOG_DAEMON

LOG_WARNING

KAVS0269-W

30269(31269)

Warning

LOG_DAEMON

LOG_WARNING

KAVS0270-I

30270

Information

LOG_DAEMON

LOG_INFO

KAVS0271-I

30271

Information

LOG_DAEMON

LOG_INFO

KAVS0272-E

30272

Error

LOG_DAEMON

LOG_ERR

KAVS0273-E

30273

Error

LOG_DAEMON

LOG_ERR

KAVS0274-E

30274

Error

LOG_DAEMON

LOG_ERR

KAVS0275-I

30275

Information

LOG_DAEMON

LOG_INFO

KAVS0276-I

30276

Information

LOG_DAEMON

LOG_INFO

KAVS0277-I

30277

Information

LOG_DAEMON

LOG_INFO

KAVS0279-E

30279

Error

LOG_DAEMON

LOG_ERR

KAVS0297-E

30297

Error

LOG_DAEMON

LOG_ERR

KAVS0301-E

30301

Error

LOG_DAEMON

LOG_ERR

KAVS0314-E

30314

Error

LOG_DAEMON

LOG_ERR

KAVS0315-E

30315

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0317-E

30317

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0318-E

30318

Error

LOG_DAEMON

LOG_ERR

KAVS0319-E

30319

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0500-E

30500

Error

LOG_DAEMON

LOG_ERR

KAVS0530-I

30530

Information

LOG_DAEMON

LOG_INFO

KAVS0531-I

30531

Information

LOG_DAEMON

LOG_INFO

KAVS0532-I

30532

Information

LOG_DAEMON

LOG_INFO

KAVS0533-I

30533

Information

LOG_DAEMON

LOG_INFO

KAVS0534-I

30534

Information

LOG_USER

LOG_INFO

KAVS0535-I

30535

Information

LOG_USER

LOG_INFO

KAVS0536-I

30536

Information

LOG_USER

LOG_INFO

KAVS0537-I

30537

Information

LOG_USER

LOG_INFO

KAVS0560-I

30560

Information

LOG_DAEMON

LOG_INFO

KAVS0561-I

30561

Information

LOG_DAEMON

LOG_INFO

KAVS0670-E

30670

Error

LOG_DAEMON

LOG_ERR

KAVS0863-E

30863

Error

LOG_USER

LOG_ERR

KAVS0864-E

30864

Error

LOG_USER

LOG_ERR

KAVS0865-E

30865

Error

LOG_DAEMON,

LOG_USER

LOG_ERR

KAVS0866-E

30866

Error

LOG_USER

LOG_ERR

KAVS0867-E

30867

Error

LOG_USER

LOG_ERR

KAVS0869-E

30869

Error

LOG_DAEMON

LOG_ERR

KAVS0900-W

30900

Warning

LOG_DAEMON

LOG_WARNING

KAVS0901-E

30901

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0902-E

30902

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0903-E

30903

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0904-E

30904

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0905-E

30905

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0907-E

30907

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0909-E

30909

Error

LOG_USER

LOG_ERR

KAVS0915-E

30915

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0916-E

--

--

LOG_DAEMON

LOG_ERR

KAVS0917-E

30917

Error

LOG_DAEMON

LOG_ERR

KAVS0920-W

30920

Warning

LOG_DAEMON, LOG_USER

LOG_WARNING

KAVS0921-W

30921

Warning

LOG_DAEMON

LOG_WARNING

KAVS0930-E

30930

Error

LOG_USER

LOG_ERR

KAVS0932-E

30932

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0933-W

30933

Warning

LOG_USER

LOG_WARNING

KAVS0934-E

30934

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0935-E

30935

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0936-E

30936

Error

LOG_USER

LOG_ERR

KAVS0940-E

30940

Error

LOG_DAEMON

LOG_ERR

KAVS0941-E

30941

Error

LOG_DAEMON

LOG_ERR

KAVS0942-W

30942

Warning

LOG_DAEMON

LOG_WARNING

KAVS0943-E

30943

Error

LOG_DAEMON

LOG_ERR

KAVS0944-E

30944

Error

LOG_DAEMON

LOG_ERR

KAVS0945-E

30945

Error

LOG_DAEMON

LOG_ERR

KAVS0946-E

30946

Error

LOG_DAEMON

LOG_ERR

KAVS0947-E

30947

Error

LOG_DAEMON

LOG_ERR

KAVS0950-E

30950

Error

LOG_DAEMON

LOG_ERR

KAVS0960-E

30960

Error

LOG_DAEMON

LOG_ERR

KAVS0965-E

30965

Error

LOG_DAEMON

LOG_ERR

KAVS0966-E

30966

Error

LOG_DAEMON

LOG_ERR

KAVS0970-E

30970

Error

LOG_DAEMON

LOG_ERR

KAVS0971-E

30971

Error

LOG_DAEMON

LOG_ERR

KAVS0980-E

30980

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0981-E

30981

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0982-E

30982

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0983-E

30983

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0984-E

30984

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0985-E

30985

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0987-E

30987

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0988-E

30988

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0989-E

30989

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0990-E

30990

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS0992-E

30992

Error

LOG_DAEMON

LOG_ERR

KAVS0997-E

30997

Error

LOG_USER

LOG_ERR

KAVS0998-E

30998

Error

LOG_DAEMON

LOG_ERR

KAVS0999-W

30999

Warning

LOG_DAEMON

LOG_WARNING

KAVS1002-E

31002

Error

LOG_DAEMON

LOG_ERR

KAVS1003-E

31003

Error

LOG_DAEMON

LOG_ERR

KAVS1004-E

31004

Error

LOG_DAEMON

LOG_ERR

KAVS1005-E

31005

Error

LOG_DAEMON

LOG_ERR

KAVS1006-W

31006

Warning

LOG_DAEMON

LOG_WARNING

KAVS1007-E

31007

Error

LOG_DAEMON

LOG_ERR

KAVS1008-E

31008

Error

LOG_DAEMON

LOG_ERR

KAVS1009-W

31009

Warning

LOG_USER

LOG_WARNING

KAVS1300-I

31300

Information

LOG_DAEMON

LOG_INFO

KAVS1301-I

31301

Information

LOG_DAEMON

LOG_INFO

KAVS1302-I

31302

Information

LOG_DAEMON

LOG_INFO

KAVS1400-E

31400

Error

LOG_DAEMON

LOG_ERR

KAVS1401-E

31401

Error

LOG_DAEMON

LOG_ERR

KAVS1420-I

31420

Information

LOG_DAEMON

LOG_INFO

KAVS1500-I

31500

Information

LOG_USER

LOG_INFO

KAVS1501-I

31501

Information

LOG_USER

LOG_INFO

KAVS1502-E

31502

Error

LOG_USER

LOG_ERR

KAVS1503-I

31503

Information

LOG_USER

LOG_INFO

KAVS1504-W

31504

Warning

LOG_USER

LOG_WARNING

KAVS1512-E

31512

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS1514-E

31514

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS1515-E

31515

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS1516-E

31516

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS1517-E

31517

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS1518-E

31518

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS1709-E

31709

Error

LOG_USER

LOG_ERR

KAVS1713-E

31713

Error

LOG_USER

LOG_ERR

KAVS1725-E

31725

Error

LOG_USER

LOG_ERR

KAVS1790-E

31790

Error

LOG_USER

LOG_ERR

KAVS1791-E

31791

Error

LOG_USER

LOG_ERR

KAVS1801-I

31801

Information

LOG_DAEMON

LOG_INFO

KAVS1802-I

31802

Information

LOG_DAEMON

LOG_INFO

KAVS1803-E

31803

Error

LOG_DAEMON

LOG_ERR

KAVS1804-I

31804

Information

LOG_DAEMON

LOG_INFO

KAVS1805-E

31805

Error

LOG_DAEMON

LOG_ERR

KAVS1806-I

31806

Information

LOG_DAEMON

LOG_INFO

KAVS1807-E

31807

Error

LOG_DAEMON

LOG_ERR

KAVS1808-E

31808

Error

LOG_DAEMON

LOG_ERR

KAVS1809-E

31809

Error

LOG_DAEMON

LOG_ERR

KAVS1810-E

31810

Error

LOG_DAEMON

LOG_ERR

KAVS1811-E

31811

Error

LOG_DAEMON

LOG_ERR

KAVS1812-E

31812

Error

LOG_DAEMON

LOG_ERR

KAVS1813-E

31813

Error

LOG_DAEMON

LOG_ERR

KAVS1814-E

31814

Error

LOG_DAEMON

LOG_ERR

KAVS1815-E

31815

Error

LOG_DAEMON

LOG_ERR

KAVS1816-E

31816

Error

LOG_DAEMON

LOG_ERR

KAVS1817-E

31817

Error

LOG_DAEMON

LOG_ERR

KAVS1818-E

31818

Error

LOG_DAEMON

LOG_ERR

KAVS1819-E

31819

Error

LOG_DAEMON

LOG_ERR

KAVS1820-E

31820

Error

LOG_DAEMON

LOG_ERR

KAVS1821-E

31821

Error

LOG_DAEMON

LOG_ERR

KAVS1822-E

31822

Error

LOG_DAEMON

LOG_ERR

KAVS1823-E

31823

Error

LOG_DAEMON

LOG_ERR

KAVS1824-E

31824

Error

LOG_DAEMON

LOG_ERR

KAVS1825-E

31825

Error

LOG_DAEMON

LOG_ERR

KAVS1826-E

31826

Error

LOG_DAEMON

LOG_ERR

KAVS1827-E

31827

Error

LOG_DAEMON

LOG_ERR

KAVS1828-E

31828

Error

LOG_DAEMON

LOG_ERR

KAVS1829-E

31829

Error

LOG_DAEMON

LOG_ERR

KAVS1830-E

31830

Error

LOG_DAEMON

LOG_ERR

KAVS1831-E

31831

Error

LOG_DAEMON

LOG_ERR

KAVS1832-E

31832

Error

LOG_DAEMON

LOG_ERR

KAVS1833-E

31833

Error

LOG_DAEMON

LOG_ERR

KAVS1834-E

31834

Error

LOG_DAEMON

LOG_ERR

KAVS1835-E

31835

Error

LOG_DAEMON

LOG_ERR

KAVS1836-E

31836

Error

LOG_DAEMON

LOG_ERR

KAVS1837-E

31837

Error

LOG_DAEMON

LOG_ERR

KAVS1838-E

31838

Error

LOG_DAEMON

LOG_ERR

KAVS1839-E

31839

Error

LOG_DAEMON

LOG_ERR

KAVS1840-E

31840

Error

LOG_DAEMON

LOG_ERR

KAVS1841-E

31841

Error

LOG_DAEMON

LOG_ERR

KAVS1842-E

31842

Error

LOG_DAEMON

LOG_ERR

KAVS1843-E

31843

Error

LOG_DAEMON

LOG_ERR

KAVS1844-E

31844

Error

LOG_DAEMON

LOG_ERR

KAVS1845-E

31845

Error

LOG_DAEMON

LOG_ERR

KAVS1846-E

31846

Error

LOG_DAEMON

LOG_ERR

KAVS1848-W

31848

Warning

LOG_DAEMON

LOG_WARNING

KAVS1849-W

31849

Warning

LOG_DAEMON

LOG_WARNING

KAVS1850-E

31850

Error

LOG_DAEMON

LOG_ERR

KAVS1851-I

31851

Information

LOG_DAEMON

LOG_INFO

KAVS1852-I

31852

Information

LOG_DAEMON

LOG_INFO

KAVS1853-I

31853

Information

LOG_DAEMON

LOG_INFO

KAVS1854-E

31854

Error

LOG_DAEMON

LOG_ERR

KAVS1855-W

31855

Warning

LOG_DAEMON

LOG_WARNING

KAVS1859-W

31859

Warning

LOG_DAEMON

LOG_WARNING

KAVS1860-W

31860

Warning

--

--

KAVS1861-E

31861

Error

LOG_DAEMON

LOG_ERR

KAVS1862-I

31862

Information

--

--

KAVS1863-I

31863

Information

--

--

KAVS1864-I

31864

Error

--

--

KAVS1865-E

31865

Error

LOG_DAEMON

LOG_ERR

KAVS1866-E

31866

Error

LOG_DAEMON

LOG_ERR

KAVS1867-E

31867

Error

LOG_DAEMON

LOG_ERR

KAVS1868-E

31868

Error

LOG_DAEMON

LOG_ERR

KAVS1869-E

31869

Error

LOG_DAEMON

LOG_ERR

KAVS1870-E

31870

Error

LOG_DAEMON

LOG_ERR

KAVS1871-E

31871

Error

LOG_DAEMON

LOG_ERR

KAVS1872-E

31872

Error

LOG_DAEMON

LOG_ERR

KAVS1873-E

31873

Error

LOG_DAEMON

LOG_ERR

KAVS1874-E

31874

Error

LOG_DAEMON

LOG_ERR

KAVS1875-E

31875

Error

LOG_DAEMON

LOG_ERR

KAVS1876-E

31876

Error

LOG_DAEMON

LOG_ERR

KAVS1877-E

31877

Error

LOG_DAEMON

LOG_ERR

KAVS1878-E

31878

Error

LOG_DAEMON

LOG_ERR

KAVS1879-E

31879

Error

LOG_DAEMON

LOG_ERR

KAVS1880-E

31880

Error

--

--

KAVS1881-E

31881

Error

LOG_DAEMON

LOG_ERR

KAVS1882-E

31882

Error

LOG_DAEMON

LOG_ERR

KAVS1883-E

31883

Error

LOG_DAEMON

LOG_ERR

KAVS1884-E

31884

Error

LOG_DAEMON

LOG_ERR

KAVS1885-E

31885

Error

LOG_DAEMON

LOG_ERR

KAVS1886-E

31886

Error

LOG_DAEMON

LOG_ERR

KAVS1887-E

31887

Error

LOG_DAEMON

LOG_ERR

KAVS1888-E

31888

Error

LOG_DAEMON

LOG_ERR

KAVS1889-E

31889

Error

LOG_DAEMON

LOG_ERR

KAVS1890-E

31890

Error

LOG_DAEMON

LOG_ERR

KAVS1891-E

31891

Error

LOG_DAEMON

LOG_ERR

KAVS1892-E

31892

Error

LOG_DAEMON

LOG_ERR

KAVS1893-E

31893

Error

LOG_DAEMON

LOG_ERR

KAVS1894-E

31894

Error

LOG_DAEMON

LOG_ERR

KAVS1896-E

31896

Error

LOG_DAEMON

LOG_ERR

KAVS1897-E

31897

Error

LOG_DAEMON

LOG_ERR

KAVS1898-I

31898

Information

LOG_DAEMON

LOG_INFO

KAVS1900-W

31900

Warning

LOG_DAEMON

LOG_WARNING

KAVS1901-I

31901

Information

LOG_DAEMON

LOG_INFO

KAVS1902-W

31902

Warning

LOG_DAEMON

LOG_WARNING

KAVS1903-E

31903

Error

LOG_DAEMON

LOG_ERR

KAVS1904-E

31904

Error

LOG_DAEMON

LOG_ERR

KAVS1905-W

31905

Warning

LOG_DAEMON

LOG_WARNING

KAVS1906-E

31906

Error

LOG_DAEMON

LOG_ERR

KAVS1907-E

31907

Error

LOG_DAEMON

LOG_ERR

KAVS1908-W

31908

Warning

LOG_DAEMON

LOG_WARNING

KAVS1909-E

31909

Error

LOG_DAEMON

LOG_ERR

KAVS1920-E

31920

Error

LOG_DAEMON

LOG_ERR

KAVS1921-E

31921

Error

LOG_DAEMON

LOG_ERR

KAVS1922-W

31922

Warning

LOG_DAEMON

LOG_WARNING

KAVS1923-E

31923

Error

LOG_DAEMON

LOG_ERR

KAVS1924-E

31924

Error

LOG_DAEMON

LOG_ERR

KAVS1925-E

31925

Error

LOG_DAEMON

LOG_ERR

KAVS1927-E

31927

Error

LOG_DAEMON

LOG_ERR

KAVS1929-I

31929

Information

LOG_DAEMON

LOG_INFO

KAVS1930-W

31930

Warning

LOG_DAEMON

LOG_WARNING

KAVS1932-E

31932

Error

LOG_DAEMON

LOG_ERR

KAVS1940-E

31940

Error

LOG_DAEMON

LOG_ERR

KAVS1941-E

31941

Error

LOG_DAEMON

LOG_ERR

KAVS1942-E

31942

Error

LOG_DAEMON

LOG_ERR

KAVS1943-E

31943

Error

LOG_DAEMON

LOG_ERR

KAVS1953-E

31953

Error

LOG_DAEMON

LOG_ERR

KAVS1954-E

31954

Error

--

--

KAVS1956-E

31956

Error

LOG_DAEMON

LOG_ERR

KAVS1961-E

31961

Error

--

--

KAVS1962-E

31962

Error

--

--

KAVS1963-E

31963

Error

LOG_DAEMON

LOG_ERR

KAVS1964-E

31964

Error

LOG_DAEMON

LOG_ERR

KAVS1965-I

31965

Information

LOG_DAEMON

LOG_INFO

KAVS1966-I

31966

Information

--

--

KAVS1967-I

31967

Information

--

--

KAVS1968-I

31968

Information

--

--

KAVS1969-I

31969

Information

--

--

KAVS1970-I

31970

Information

--

--

KAVS1971-E

31971

Error

LOG_DAEMON

LOG_ERR

KAVS1972-E

31972

Error

LOG_DAEMON

LOG_ERR

KAVS1973-E

31973

Error

LOG_DAEMON

LOG_ERR

KAVS1974-E

31974

Error

LOG_DAEMON

LOG_ERR

KAVS1975-E

31975

Error

LOG_DAEMON

LOG_ERR

KAVS1976-E

31976

Error

LOG_DAEMON

LOG_ERR

KAVS1977-E

31977

Error

LOG_DAEMON

LOG_ERR

KAVS1978-E

31978

Error

LOG_DAEMON

LOG_ERR

KAVS1979-E

31979

Error

LOG_DAEMON

LOG_ERR

KAVS1980-I

31980

Information

LOG_DAEMON

LOG_INFO

KAVS1981-I

31981

Information

LOG_DAEMON

LOG_INFO

KAVS1982-I

31982

Information

LOG_DAEMON

LOG_INFO

KAVS1983-I

31983

Information

LOG_DAEMON

LOG_INFO

KAVS1989-E

31989

Error

LOG_DAEMON

LOG_ERR

KAVS1990-E

31990

Error

LOG_DAEMON

LOG_ERR

KAVS1991-E

31991

Error

LOG_DAEMON

LOG_ERR

KAVS1992-E

31992

Error

LOG_DAEMON

LOG_ERR

KAVS1993-E

31993

Error

LOG_DAEMON

LOG_ERR

KAVS1995-E

31995

Error

LOG_DAEMON

LOG_ERR

KAVS1998-E

31998

Error

--

--

KAVS2127-E

32127

Error

LOG_USER

LOG_ERR

KAVS2128-E

32128

Error

LOG_USER

LOG_ERR

KAVS3707-I

33707

Information

LOG_USER

LOG_INFO

KAVS3708-I

33708

Information

LOG_USER

LOG_INFO

KAVS3709-I

33709

Information

LOG_USER

LOG_INFO

KAVS3710-I

33710

Information

LOG_USER

LOG_INFO

KAVS3910-E

33910

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS4091-E

34091

Error

LOG_DAEMON

LOG_ERR

KAVS4092-I

34092

Information

LOG_DAEMON

LOG_INFO

KAVS4200-E

34200

Error

LOG_DAEMON

LOG_ERR

KAVS4201-E

34201

Error

LOG_DAEMON

LOG_ERR

KAVS4202-E

34202

Error

LOG_DAEMON

LOG_ERR

KAVS4203-E

34203

Error

LOG_DAEMON

LOG_ERR

KAVS4204-E

34204

Error

LOG_DAEMON

LOG_ERR

KAVS4209-W

34209

Warning

LOG_DAEMON

LOG_WARNING

KAVS4631-W

34631

Warning

LOG_DAEMON

LOG_WARNING

KAVS4671-E

34671

Error

LOG_DAEMON

LOG_ERR

KAVS4672-W

34672

Warning

LOG_DAEMON

LOG_WARNING

KAVS4673-W

34673

Warning

LOG_DAEMON

LOG_WARNING

KAVS4675-I

34675

(38675)

Information

LOG_DAEMON

LOG_INFO

KAVS4676-I

34676

(38676)

Information

LOG_DAEMON

LOG_INFO

KAVS4677-E

34677

(38677)

Error

LOG_DAEMON

LOG_ERR

KAVS4700-E

34700

Error

LOG_DAEMON

LOG_ERR

KAVS4701-E

34701

Error

LOG_DAEMON

LOG_ERR

KAVS4702-E

34702

Error

LOG_DAEMON

LOG_ERR

KAVS4703-E

34703

Error

LOG_DAEMON

LOG_ERR

KAVS4704-E

34704

Error

LOG_DAEMON

LOG_ERR

KAVS4705-E

34705

Error

LOG_DAEMON

LOG_ERR

KAVS4706-E

34706

Error

LOG_DAEMON

LOG_ERR

KAVS4707-E

34707

Error

LOG_DAEMON

LOG_ERR

KAVS4708-E

34708

Error

LOG_DAEMON

LOG_ERR

KAVS4711-E

34711

Error

LOG_DAEMON

LOG_ERR

KAVS4712-E

34712

Error

LOG_DAEMON

LOG_ERR

KAVS4713-E

34713

Error

LOG_DAEMON

LOG_ERR

KAVS4714-E

34714

Error

LOG_DAEMON

LOG_ERR

KAVS4715-E

34715

Error

LOG_DAEMON

LOG_ERR

KAVS4716-E

34716

Error

LOG_DAEMON

LOG_ERR

KAVS4720-E

34720

Error

LOG_DAEMON

LOG_ERR

KAVS4721-E

34721

Error

LOG_DAEMON

LOG_ERR

KAVS4722-I

34722

Information

LOG_DAEMON

LOG_INFO

KAVS4723-I

34723

Information

LOG_DAEMON

LOG_INFO

KAVS4724-E

34724

Error

LOG_DAEMON

LOG_ERR

KAVS4725-E

34725

Error

LOG_DAEMON

LOG_ERR

KAVS4730-E

34730

Error

LOG_DAEMON

LOG_ERR

KAVS4731-E

34731

Error

LOG_DAEMON

LOG_ERR

KAVS4732-E

34732

Error

LOG_DAEMON

LOG_ERR

KAVS4733-E

34733

Error

LOG_DAEMON

LOG_ERR

KAVS4750-E

34750

Error

LOG_DAEMON

LOG_ERR

KAVS4751-W

34751

Warning

LOG_DAEMON

LOG_WARNING

KAVS4752-E

34752

Error

LOG_DAEMON

LOG_ERR

KAVS4900-I

34900

Information

LOG_DAEMON

LOG_INFO

KAVS4901-I

34901

Information

LOG_DAEMON

LOG_INFO

KAVS4902-W

34902

Warning

LOG_DAEMON

LOG_WARNING

KAVS4903-I

34903

Information

LOG_DAEMON

LOG_INFO

KAVS4904-I

34904

Information

LOG_DAEMON

LOG_INFO

KAVS4905-E

34905

Error

LOG_DAEMON

LOG_ERR

KAVS4906-I

34906

Information

LOG_DAEMON

LOG_INFO

KAVS4907-I

34907

Information

LOG_DAEMON

LOG_INFO

KAVS4908-E

34908

Error

LOG_DAEMON

LOG_ERR

KAVS4909-E

34909

Error

LOG_DAEMON

LOG_ERR

KAVS4910-E

34910

Error

LOG_DAEMON

LOG_ERR

KAVS4911-E

34911

Error

LOG_DAEMON

LOG_ERR

KAVS4912-E

34912

Error

LOG_DAEMON

LOG_ERR

KAVS4913-E

34913

Error

LOG_DAEMON

LOG_ERR

KAVS4914-E

34914

Error

LOG_DAEMON

LOG_ERR

KAVS4915-I

34915

Information

LOG_DAEMON

LOG_INFO

KAVS4916-W

34916

Warning

LOG_DAEMON

LOG_WARNING

KAVS4917-E

34917

Error

LOG_DAEMON

LOG_ERR

KAVS4918-I

34918

Information

LOG_DAEMON

LOG_INFO

KAVS4939-I

34939

Information

LOG_USER

LOG_INFO

KAVS4943-E

34943

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS4950-I

34950

Information

LOG_DAEMON

LOG_INFO

KAVS4951-I

34951

Information

LOG_DAEMON

LOG_INFO

KAVS4955-I

34955

Information

LOG_DAEMON

LOG_INFO

KAVS4956-I

34956

Information

LOG_DAEMON

LOG_INFO

KAVS4957-E

34957

Error

LOG_DAEMON

LOG_ERR

KAVS4971-E

34971

Error

LOG_DAEMON

LOG_ERR

KAVS8033-E

38033

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVS8040-E

38040

Error

LOG_DAEMON

LOG_ERR

KAVS8107-E

--

--

LOG_DAEMON

LOG_ERR

KAVS8111-E

--

--

LOG_DAEMON

LOG_ERR

KAVS8113-E

--

--

LOG_DAEMON

LOG_ERR

KAVS8114-E

38114

Error

LOG_DAEMON

LOG_ERR

KAVS8120-I

--

--

LOG_DAEMON

LOG_INFO

KAVS8121-I

--

--

LOG_DAEMON

LOG_INFO

KAVS8122-I

--

--

LOG_DAEMON

LOG_INFO

KAVS8123-I

--

--

LOG_DAEMON

LOG_INFO

KAVS8180-E

--

--

LOG_DAEMON

LOG_ERR

KAVS8201-E

38201

Error

LOG_DAEMON

LOG_ERR

KAVS8202-E

38202

Error

LOG_DAEMON

LOG_ERR

KAVS8203-E

38203

Error

LOG_DAEMON

LOG_ERR

KAVS8204-E

38204

Error

LOG_DAEMON

LOG_ERR

KAVS8205-E

38205

Error

LOG_DAEMON

LOG_ERR

KAVS8206-E

38206

Error

LOG_DAEMON

LOG_ERR

KAVS8208-E

38208

Error

LOG_DAEMON

LOG_ERR

KAVT0002-I

10002

Information

LOG_DAEMON

LOG_INFO

KAVT0003-I

10003

Information

LOG_DAEMON

LOG_INFO

KAVT0008-E

10008

Error

LOG_DAEMON

LOG_ERR

KAVT0562-I

10562

Information

LOG_DAEMON

LOG_INFO

KAVT0563-I

10563

Information

LOG_DAEMON

LOG_INFO

KAVT0570-E

10570

Error

LOG_DAEMON

LOG_ERR

KAVT0572-E

10572

Error

LOG_DAEMON

LOG_ERR

KAVT0912-E

10912

Error

LOG_DAEMON

LOG_ERR

KAVT1003-E

11003

Error

LOG_DAEMON

LOG_ERR

KAVT1008-E

11008

Error

LOG_DAEMON

LOG_ERR

KAVT1031-E

11031

Error

LOG_DAEMON

LOG_ERR

KAVT1032-E

11032

Error

LOG_DAEMON

LOG_ERR

KAVT1037-E

11037

Error

LOG_DAEMON

LOG_ERR

KAVT1040-E

11040

Error

LOG_DAEMON

LOG_ERR

KAVT1042-E

11042

Error

LOG_DAEMON

LOG_ERR

KAVT1050-E

11050

Error

LOG_DAEMON

LOG_ERR

KAVT3401-I

13401

Information

--

--

KAVT3403-I

13403

Information

--

--

KAVT3406-I

13406

Information

--

--

KAVT3408-I

13408

Information

--

--

KAVT3504-E

--

--

LOG_DAEMON

LOG_ERR

KAVT3513-E

13513

Error

LOG_DAEMON

LOG_ERR

KAVT3514-E

13514

Error

LOG_DAEMON

LOG_ERR

KAVT3515-E

13515

Error

LOG_DAEMON

LOG_ERR

KAVT3520-E

13520

Error

LOG_DAEMON

LOG_ERR

KAVT3534-E

13534

Error

LOG_DAEMON

LOG_ERR

KAVU0201-E

20201

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0202-E

20202

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0203-E

20203

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0205-E

20205

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0206-E

20206

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0215-E

20215

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0216-E

20216

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0217-E

20217

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0218-E

20218

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0219-E

20219

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0220-E

20220

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0221-E

20221

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0224-E

20224

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0225-W

20225

Warning

LOG_DAEMON, LOG_USER

LOG_WARNING

KAVU0235-E

20235

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0237-E

20237

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0238-E

20238

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0239-E

20239

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0240-E

20240

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0241-E

20241

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0242-E

20242

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0244-E

20244

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0248-E

20248

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0249-E

20249

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0250-E

20250

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0251-E

20251

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU0252-E

20252

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU1100-I

21100

Information

LOG_DAEMON

LOG_NOTICE

KAVU1101-I

21101

Information

LOG_DAEMON

LOG_NOTICE

KAVU1102-E

21102

Error

LOG_DAEMON

LOG_ERR

KAVU1103-I

21103

Information

LOG_DAEMON

LOG_NOTICE

KAVU1104-E

21104

Error

LOG_DAEMON

LOG_ERR

KAVU1105-E

21105

Error

LOG_DAEMON

LOG_ERR

KAVU1106-E

21106

Error

LOG_DAEMON

LOG_ERR

KAVU3100-I

23100

Information

LOG_DAEMON

LOG_NOTICE

KAVU3101-I

23101

Information

LOG_DAEMON

LOG_NOTICE

KAVU3104-I

23104

Information

LOG_DAEMON

LOG_NOTICE

KAVU3105-I

--

--

LOG_DAEMON

LOG_NOTICE

KAVU3110-E

23110

Error

LOG_DAEMON

LOG_ERR

KAVU3111-E

23111

Error

LOG_DAEMON

LOG_ERR

KAVU3112-E

--

--

LOG_DAEMON

LOG_ERR

KAVU4100-I

24100

Information

LOG_DAEMON

LOG_NOTICE

KAVU4101-I

24101

Information

LOG_DAEMON

LOG_NOTICE

KAVU4102-I

24102

Information

LOG_DAEMON

LOG_NOTICE

KAVU4103-I

24103

Information

LOG_DAEMON

LOG_NOTICE

KAVU4104-I

24104

Information

LOG_DAEMON

LOG_NOTICE

KAVU4105-I

24105

Information

LOG_DAEMON

LOG_NOTICE

KAVU4110-E

24110

Error

LOG_DAEMON

LOG_ERR

KAVU4111-E

24111

Error

LOG_DAEMON

LOG_ERR

KAVU4112-E

24112

Error

LOG_DAEMON

LOG_ERR

KAVU4113-W

24113

Warning

LOG_DAEMON

LOG_WARNING

KAVU5009-E

25009

Error

LOG_USER

LOG_ERR

KAVU5100-E

25100

Error

LOG_DAEMON

LOG_ERR

KAVU5980-I

25980

Information

LOG_USER

LOG_NOTICE

KAVU5981-I

25981

Information

LOG_USER

LOG_NOTICE

KAVU5982-E

25982

Error

LOG_USER

LOG_ERR

KAVU5983-I

25983

Information

LOG_USER

LOG_NOTICE

KAVU5984-W

25984

Warning

LOG_USER

LOG_WARNING

KAVU6100-I

26100

Information

LOG_DAEMON, LOG_USER

LOG_NOTICE

KAVU6101-I

26101

Information

LOG_DAEMON, LOG_USER

LOG_NOTICE

KAVU6102-E

26102

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU6103-E

26103

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU6104-E

26104

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU6105-E

26105

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU6106-E

26106

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU6107-E

26107

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU6108-E

26108

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU6109-E

26109

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU7110-E

--

--

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU7111-E

--

--

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU7112-E

27112

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KAVU7113-E

27113

Error

LOG_DAEMON, LOG_USER

LOG_ERR

KNAC0003-E

40003

Error

LOG_DAEMON

LOG_ERR

KNAC0005-E

40005

Error

LOG_DAEMON

LOG_ERR

KNAC0006-E

40006

Error

LOG_DAEMON

LOG_ERR

KNAC0007-E

40007

Error

LOG_DAEMON

LOG_ERR

KNAC0011-E

40011

Error

LOG_DAEMON

LOG_ERR

KNAC0014-E

40014

Error

LOG_DAEMON

LOG_ERR

KNAC1003-E

41003

Error

LOG_DAEMON

LOG_ERR

KNAC1520-I

41520

Information

LOG_DAEMON

LOG_INFO

KNAC1701-W

41701

Warning

LOG_DAEMON

LOG_WARNING

KNAC1702-I

41702

Information

LOG_DAEMON

LOG_INFO

KNAC1703-W

41703

Warning

LOG_DAEMON

LOG_WARNING

KNAC1704-I

41704

Information

LOG_DAEMON

LOG_INFO

KNAC1705-E

41705

Error

LOG_DAEMON

LOG_ERR

KNAC1706-I

41706

Information

LOG_DAEMON

LOG_INFO

KNAC1707-I

41707

Information

LOG_DAEMON

LOG_INFO

KNAC1708-I

41708

Information

LOG_DAEMON

LOG_INFO

KNAC1709-E

41709

Error

LOG_DAEMON

LOG_ERR

KNAC1710-E

41710

Error

LOG_DAEMON

LOG_ERR

KNAC1711-E

41711

Error

LOG_DAEMON

LOG_ERR

KNAC1713-I

41713

Information

LOG_DAEMON

LOG_INFO

KNAC1714-I

41714

Information

LOG_DAEMON

LOG_INFO

KNAC1774-E

41774

Error

LOG_DAEMON

LOG_ERR

KNAC1775-E

41775

Error

LOG_DAEMON

LOG_ERR

KNAC1776-E

41776

Error

LOG_DAEMON

LOG_ERR

KNAC1801-E

41801

Error

LOG_DAEMON

LOG_ERR

KNAC1802-E

41802

Error

LOG_DAEMON

LOG_ERR

KNAC1803-E

41803

Error

LOG_DAEMON

LOG_ERR

KNAC1804-E

41804

Error

LOG_DAEMON

LOG_ERR

KNAC1805-E

41805

Error

LOG_DAEMON

LOG_ERR

KNAC1806-E

41806

Error

LOG_DAEMON

LOG_ERR

KNAC1807-E

41807

Error

LOG_DAEMON

LOG_ERR

KNAC1808-E

41808

Error

LOG_DAEMON

LOG_ERR

KNAC1809-E

41809

Error

LOG_DAEMON

LOG_ERR

KNAD3501-E

1

Error

LOG_USER

LOG_ERR

KNAD3516-E

--

--

LOG_USER

LOG_ERR

KNAD3613-W

2

Warning

LOG_USER

LOG_WARNING

KNAD3614-E

1

Error

LOG_USER

LOG_ERR

KNAD3620-E

1

Error

LOG_USER

LOG_ERR

KNAD3621-E

--

--

LOG_USER

LOG_ERR

KNAD3623-E

--

--

LOG_USER

LOG_ERR

KNAD3624-E

1

Error

LOG_USER

LOG_ERR

KNAD3625-E

1

Error

LOG_USER

LOG_ERR

KNAD3626-E

1

Error

LOG_USER

LOG_ERR

KNAD3642-E

1

Error

LOG_USER

LOG_ERR

KNAD3643-E

1

Error

LOG_USER

LOG_ERR

KNAD3644-E

1

Error

LOG_USER

LOG_ERR

KNAD3649-E

1

Error

LOG_USER

LOG_ERR

KNAD3686-E

1

Error

LOG_USER

LOG_ERR

KNAD3737-E

1

Error

LOG_USER

LOG_ERR

KNAD3752-E

1

Error

LOG_USER

LOG_ERR

KNAD3753-E

1

Error

LOG_USER

LOG_ERR

KNAD3788-E

1

Error

LOG_USER

LOG_ERR

KNAD3792-E

1

Error

--

--

KNAD3862-E

1

Error

LOG_USER

LOG_ERR

KNAD3870-E

1

Error

LOG_USER

LOG_ERR

KNAD3872-E

1

Error

LOG_USER

LOG_ERR

KNAD3874-E

1

Error

LOG_USER

LOG_ERR

KNAD3875-E

1

Error

LOG_USER

LOG_ERR

KNAD3899-E

1

Error

LOG_USER

LOG_ERR

KNAD3953-E

1

Error

LOG_USER

LOG_ERR

KNAD3970-E

1

Error

LOG_USER

LOG_ERR

KNAD3971-E

1

Error

LOG_USER

LOG_ERR

KNAD3974-E

1

Error

LOG_USER

LOG_ERR

KNAD3975-E

1

Error

LOG_USER

LOG_ERR

KNAD3976-W

2

Warning

LOG_USER

LOG_WARNING

KNAD3977-E

1

Error

LOG_USER

LOG_ERR

KNAD3978-E

1

Error

LOG_USER

LOG_ERR

KNAD3979-E

1

Error

LOG_USER

LOG_ERR

KNAD3991-E

1

Error

LOG_USER

LOG_ERR

KNAD3992-E

1

Error

LOG_USER

LOG_ERR

KNAD3993-E

1

Error

LOG_USER

LOG_ERR

KNAD3994-E

1

Error

LOG_USER

LOG_ERR

KNAD3995-I

3

Information

LOG_USER

LOG_INFO

KNAD3996-I

3

Information

LOG_USER

LOG_INFO

KNAK2502-I

1

Information

LOG_USER

LOG_INFO

KNAK2503-E

1

Error

LOG_USER

LOG_ERR

KNAK2507-I

1

Information

LOG_USER

LOG_INFO

KNAK2508-E

1

Error

LOG_USER

LOG_ERR

KNAK2601-E

1

Error

LOG_USER

LOG_ERR

Legend:

-- : Not applicable

1.4.2 Information about the Windows event log

For events output by JP1/AJS3, JP1/AJS2 is set as source. For events output by JP1/AJS3 - Web Console, JP1/AJS3 - Web Console is set as source.

As an exception to this rule, note that the following value is set as source for events output by an embedded database:

For an embedded database: "JP1/AJS3_Database _JFn" (where n is a value from 0 to 9, or A to Z)

2 Messages beginning with KAJS (Messages about passing information setting jobs)

This chapter explains the messages beginning with KAJS (messages about passing information setting jobs).

2.1 List of messages beginning with KAJS

This section lists the messages that begin with KAJS (messages about passing information setting jobs).

KAJS7620-E

An error occurred in internal processing. : maintenance-information

An error occurred during internal processing.

(S)

Cancels execution of the passing information setting job.

(O)

Check whether any of the following probable causes are present:

If you used the ajsdefine command to define the passing information setting job

Review the job definition, checking for the following:

Are the mandatory parameters specified?

Do any of the following apply to the prm parameter?

- No prm parameter is specified.

- No operands are specified.

- The output variable name is too long.

- More than 33 output variables are specified.

Do any regular expressions exceed the maximum length?

If the job is defined incorrectly, correct the definition and then re-execute the job.

If you used JP1/AJS3 - View to define the passing information setting job

The error might only be temporary. Execute the job again. If the same error occurs, use the data collection tool to collect data and contact the system administrator.

If the passing information setting job ends with a return value of 92

Check that the values that can be designated for environment setting parameter PassingInfoUsePreRc are set. For details about the PassingInfoUsePreRc environment Settings, see 20.5 Setting up the job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

KAJS7621-E

The macro variable name (macro-variable-name) when the global macro variable was set is duplicated.

The same macro variable name was specified more than once when setting global macro variables.

(S)

Cancels execution of the passing information setting job.

(O)

Change the repeated macro variable name, and then re-execute the job.

KAJS7622-E

The standard output file of the preceding job, for obtaining the set value of the global macro variable, does not exist.

The standard output file of the preceding job does not exist or is 0 bytes.

(S)

Cancels execution of the passing information setting job.

(O)

Check the following:

Is the preceding job a PC job, Unix job, flexible job, HTTP connection job, or custom job?

Is the standard output file name specified in the preceding job?

Did the preceding job output at least 1 byte of data to the standard output file?

Note that the information in the Execution Result Details dialog box was output by the job to standard error output. This differs from the information output to standard output.

KAJS7623-E

The specification of the regular expression (regular-expression) for analyzing the set value of the global macro variable (macro-variable-name) is invalid.

A regular expression for analyzing the setting of a global macro variable is specified incorrectly.

(S)

Cancels execution of the passing information setting job.

(O)

Correct the regular expression, and execute the job again.

KAJS7624-E

Memory became insufficient during compare processing for the regular expression (regular-expression) for analyzing the set value of the global macro variable (macro-variable-name). : maintenance-information

Insufficient memory was available to compare the value of a global macro variable against a regular expression.

(S)

Cancels execution of the passing information setting job.

(O)

Make more memory available by terminating unnecessary processes, and then re-execute the job.

KAJS7625-E

A line exceeding 1024 bytes (line-number) exists in the standard output file (standard-output-file-name) of the preceding job for obtaining the set value of the global macro variable.

A line in the standard output file of the preceding job for obtaining the value of the global macro variable exceeded 1,024 bytes, preventing the system from comparing it against the regular expression.

(S)

Cancels command execution.

(O)

Make sure that no lines exceed 1,024 bytes in the execution results of the preceding job.

KAJS7626-W

A null string was set for the value of the global macro variable (macro-variable-name) because, in the standard output file of the preceding job, no line matched the regular expression (regular-expression).

A null string was set as the value of the global macro variable because no line in the standard output file of the preceding job matched the regular expression.

(S)

Cancels execution of the passing information setting job.

(O)

Review the regular expression and the standard output of the preceding job, and re-execute the job as necessary.

KAJS7628-E

An error occurred during processing to read the standard output file (standard-output-file-name) of the preceding job for obtaining the set value of the global macro variable. : maintenance-information

An error occurred when reading the standard output file of the preceding job for obtaining the global macro variable value.

(S)

Cancels execution of the passing information setting job.

(O)

The probable causes are as follows:

When the ajsdefine command was used to define the passing information setting job, env="AJS2SO_STDOUTFILE=?AJS2SO_STDOUTFILE?"; was specified incorrectly.

A temporary error occurred.

If env="AJS2SO_STDOUTFILE=?AJS2SO_STDOUTFILE?"; was specified incorrectly, correct it and then execute the job again.

In the case of a temporary error, execute the job again. If the error still occurs, use the data collection tool to collect data and contact the system administrator.

KAJS7629-E

An attempt to create the global macro file (global-macro-file-name) while setting the global macro variable has failed. : maintenance-information

An attempt to create a global macro file failed when setting a global macro variable.

(S)

Cancels execution of the passing information setting job.

(O)

Make sure that the disk where the global macro file is to be created has sufficient free space. The global macro file is created in the job information storage folder. If disk space was insufficient, make more space available and execute the job again. If the disk has sufficient free space, execute the job again in case the error was temporary. If the error still occurs, use the data collection tool to collect data and contact the system administrator.

KAJS7630-E

An error occurred during compare processing for the regular expression (regular-expression) for analyzing the set value of the global macro variable (macro-variable-name). : maintenance-information

An error occurred when comparing a regular expression against the value of a global macro variable.

(S)

Cancels execution of the passing information setting job.

(O)

Execute the job again in case the error was temporary. If the error still occurs, use the data collection tool to collect data and contact the system administrator.

3 Messages beginning with KAVS (Messages about the scheduler and the common processing)

This chapter explains the messages beginning with KAVS (messages about the scheduler and the common processing).

3.1 List of messages beginning with KAVS

This section lists the messages that begin with KAVS (Messages about the scheduler and the common processing).

When using JP1/AJS3 in a compatible ISAM configuration, see the JP1/AJS2 manuals.

Supplementary note

Messages that begin with KAVS also include messages about the queueless job execution facility.

KAVS0100-E

Illegal option (option) exists.

An invalid option was specified.

(S)

Cancels command execution.

(O)

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

KAVS0101-E

Value for option (option) is not specified.

The option does not contain any value.

(S)

Cancels command execution.

(O)

Specify a value for the option, and then re-execute the command.

KAVS0102-E

Extra argument(s) exist.

An unnecessary argument(s) was specified.

(S)

Cancels command execution.

(O)

Delete the unnecessary argument(s), and then re-execute the command.

KAVS0103-E

Invalid value for option (option).

The option contains an invalid value.

(S)

Cancels command execution.

(O)

Correct the value for the option, and then re-execute the command.

KAVS0104-E

Option (option) appears twice or more.

The same option was specified more than once.

(S)

Cancels command execution.

(O)

Specify the option only once, and then re-execute the command.

KAVS0105-E

Jobnet name not specified.

A jobnet name is missing.

(S)

Cancels command execution.

(O)

Specify the jobnet name, and then re-execute the command.

KAVS0106-E

Cannot treat as Jobnet.: name

The system cannot handle name as a jobnet.

For a jobnet entered for release (release target jobnet), there might be no jobnet definition whose status is Being applied.

(S)

Cancels command execution. If you specify more than one jobnet (including specifications of regular expression), the system continues command execution.

(O)

When name is displayed, specify a unit name that the system can handle as a unit, and then re-execute the command.

When name is not displayed, check the jobnet name for invalid characters. Delete the invalid characters, and then re-execute the command.

The invalid characters are:

(

)

, (comma)

: (colon)

; (semicolon)

=

/

Space character

For a jobnet entered for release, use the ajsrelease command or JP1/AJS3 - View to display the release list information and check for a jobnet definition in Being applied status. If such a jobnet definition is not found, use the ajslocaldate command to change the time to a time that there is a jobnet definition in Being applied status, and then delete the relevant jobnet.

KAVS0107-E

Scheduler service has not started.

The scheduler service has not started.

(S)

Cancels command execution.

(O)

Start the scheduler service using the jajs_spmd command, and then re-execute the command.

KAVS0108-E

Only super user or administrator can execute.

A user who does not have superuser privileges or is not logged on as a member of the Administrators group.

A user who does not have administrator privileges or superuser privileges attempted to execute a command. If the environment is managed by AJS administrators, a user who is not an AJS administrator or does not have superuser privileges attempted to execute a command.

(S)

Cancels command execution.

(O)

Execute the command as a superuser or an administrator.

If the UAC function is enabled in Windows, the administrator must re-execute the command.

For an environment managed by AJS administrators, an AJS administrator or a user who has superuser privilege must execute the command.

KAVS0110-E

Jobnet (jobnet-name) is in execution.

The jobnet is being executed.

(S)

Cancels command execution.

(O)

Wait for the jobnet to terminate the execution, and then re-execute the command.

KAVS0111-E

Unit name not specified.

A unit name is missing.

(S)

Cancels command execution.

(O)

Specify a unit name, and then re-execute the command.

KAVS0112-E

Cannot treat as Unit.: name

The system cannot handle name as a unit.

(S)

Cancels command execution. If you specify more than one unit (including specifications of regular expression), the system continues command execution.

(O)

When name is displayed, specify a unit name that the system can handle as a unit, and then re-execute the command.

When name is not displayed, check the jobnet name for invalid characters. Delete the invalid characters, and re-execute the command.

The invalid characters are:

(

)

, (comma)

: (colon)

; (semicolon)

=

/

Space character

KAVS0113-E

No authority for Unit (unit-name).

You do not have an authority for the unit.

(S)

Cancels command execution.

(O)

Execute the command with the authority for the unit.

KAVS0115-E

Unit (unit-name) already registered as Jobnet.

The unit has already been registered as a jobnet. The probable causes are:

A relationship change option is specified for the registered unit.

A jobnet connector information change option is specified for the planning group that contains the registered unit.

A jobnet connector information change option is specified for the registered unit.

A wait condition change option is specified for the registered unit.

(S)

Cancels command execution.

(O)

Unregister the unit, and then re-execute the command. To specify wait condition change options in the ajschange command or relationship change options in the ajschgnet command with a suspended job or jobnet specified as the unit name, re-execute the command with the -S option specified.

KAVS0116-E

Cannot specify these options together.

The combination of options is invalid. The probable causes are:

You attempted to use options that cannot be simultaneously specified.

You attempted to use options that cannot be simultaneously specified for the target physical host or logical host.

You attempted to use options that cannot be simultaneously specified for the primary node or secondary node of the logical host that will be used for processing.

(S)

Cancels command execution.

(O)

Check the specified options, and re-execute the command with options that can be specified together.

KAVS0117-E

Job name not specified.

A job name is missing.

(S)

Cancels command execution.

(O)

Specify a job name, and then re-execute the command.

KAVS0119-E

Cannot use - in use by other user.: unit-name or file-name

Operation is impossible because another user is using the job, jobnet or job group that you attempted to execute with a command. Alternatively, another user is using the file that you attempted to manipulate.

(S)

Cancels command execution.

(O)

Wait for the other user to complete using the job, jobnet or job group and then re-execute the command.

KAVS0123-E

Cannot read configuration definition parameter - no authorization.

You cannot enter the configuration definition parameter.

(S)

Cancels command execution.

(O)

Correct the configuration definition parameter, and then re-execute the command.

KAVS0125-E

Cannot open specified file (file-name).: maintenance-information

The file could not be opened. The probable causes are:

There is no access permission for the specified file.

A file that does not exist is specified.

An attempt was made to create a file with the same name as an existing file.

A read-only file is specified.

A file being used is specified.

Invalid characters are specified for a file name or directory name.

A directory is specified.

There is not enough free space on the file system or device to which you attempted to write a file.

The number of files that can be handled by the process or system exceeds the maximum.

Memory is insufficient.

(S)

Cancels command execution.

(O)

Correct the information about the file, and then re-execute the command.

KAVS0126-E

Operand value exceeds prescribed length.

The value of the operand exceeds the prescribed length.

(S)

Cancels command execution.

(O)

Correct the value of the option, and then re-execute the command.

KAVS0127-E

Specified file (file-name) does not exist.

The file does not exist.

(S)

Cancels command execution.

(O)

Correct the file name or create the file. Then, re-execute the command.

KAVS0129-E

Jobnet (jobnet-name) is not executing.

The jobnet is not being executed.

(S)

Cancels command execution.

(O)

Re-execute the command while executing the jobnet.

KAVS0130-E

Specified Jobnet (jobnet-name) is not registered.

The jobnet is not registered.

(S)

Cancels command execution.

(O)

Register the jobnet, and then re-execute the command.

KAVS0132-E

Job error information directory (directory-name) does not exist.

The job error information directory specified in the JOBINFDIR environment setting parameter does not exist.

(S)

Cancels command execution.

(O)

Create the job error information directory, and then re-execute the command.

For details on the environment setting parameters, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS0135-E

Job error information directory name (directory-name) is invalid.

An invalid job error information directory name was specified in the environment setting parameter.

The specification of the JOBINFDIR environment setting parameter is invalid. The probable cause is:

The directory specified in the environment setting parameter is invalid.

(S)

Cancels command execution.

(O)

Correct the job error information directory name, and then re-execute the command.

For details on the setting of the job error information directory name, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS0141-E

Cannot operate specified Jobnet (unit-name) under current condition.

The jobnet is in an inoperable status.

The probable causes are:

An attempt was made to re-execute a jobnet that has not been executed.

An attempt was made to re-execute a job that was not placed in the termination status.

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 command execution.

(O)

Specify the name of a unit in a state that enables the command to be executed, and then re-execute the command.

For details on re-execution, see 4.5.11 Rerunning a job or jobnet in the manual JP1/Automatic Job Management System 3 Overview.

KAVS0143-E

Cannot execute - currently in process of restriction.

Immediate execution registration and re-execution is impossible because the command has been restricted.

(S)

Cancels command execution.

(O)

Release the status of execution suppression or restricted termination. Then, re-execute the command.

KAVS0144-E

No authority for Job (job-name).

The job does not have any authority.

(S)

Terminates command execution. If you specify more than one job (including specifications of regular expression), the system continues command execution.

(O)

Execute the command with the authority for the job.

KAVS0145-E

Cannot treat as Job.: unit-name

A command that can only be executed for jobs is being executed for a unit other than a job.

(S)

Cancels command execution. If you specify more than one job (including specifications of regular expression), the system continues processing.

(O)

Specify a job name as the unit name, and then re-execute the command.

KAVS0146-E

Options (option) are specified too many times.

Too many options were specified.

(S)

Cancels command execution.

(O)

Check the number of options that can be specified concurrently, and then re-execute the command.

KAVS0150-E

Backup information directory name (directory-name) is too long.

The backup information directory name is specified using a character string of more than 255 bytes.

(S)

Cancels command execution.

(O)

Specify a backup information directory name that has less than 256 bytes, and then re-execute the command.

KAVS0157-E

A relation in opposite direction already exists among elements in the specified Unit (unit-name).

The unit has already been associated in the opposite direction.

(S)

Cancels command execution.

(O)

Recheck the value of the relationship change option, and then re-execute the command.

KAVS0158-E

Invalid value for option (option) on specified Unit (unit-name).

The relationship change option specified for the unit contains an error.

(S)

Cancels command execution.

(O)

Recheck the value of the relationship change option, and then re-execute the command.

KAVS0159-W

Option (option) has been ignored which is incompatible with the Unit (unit-name).

The system invalidates an option that cannot be specified for the unit.

(S)

Continues processing.

KAVS0161-I

Unit does not found for selected option.: unit-name

The probable causes are:

There is no unit for the specified unit name that meets the selected option.

You do not have permission to reference the higher-level unit of the specified unit.

A unit that is inapplicable to the command is specified.

The following causes are probable if the unit is a jobnet registered for release (release target jobnet):

There is no jobnet definition whose status is Being applied because the scheduler service locale has been changed to an earlier date and time.

A jobnet definition in Applied status was deleted.

(S)

Cancels command execution.

(O)

If you find an error, correct it and then re-execute the command.

If the scheduler service locale was changed to an earlier date and time, use the ajslocaldate command to change it back and then re-execute the command.

KAVS0162-E

Invalid scheduler service name.: service-name

An invalid scheduler service name is specified in the -F option or the AJSCONF environment variable.

(S)

Cancels command execution.

(O)

Correct the scheduler service name, and then re-execute the command.

For details on the environment variables, see A.1 Notes on defining environment variables in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS0166-E

Cannot create a plan for the specified period.: jobnet-name

A plan cannot be created for the specified period of time.

(S)

Cancels processing.

(O)

Recheck the schedule definition of the jobnet, and then re-execute the command.

KAVS0167-E

Specified registration number is not found.: jobnet-name

The registration number has not been registered.

(S)

Cancels processing.

(O)

Correct the registration number or register the jobnet. Then, re-execute the command.

KAVS0168-E

Invalid information in definition schedule file (schedule-information-file-name). (sentence: sentence-number, information: information-number)

An invalid parameter was specified in the schedule information file.

(S)

Cancels command execution.

(O)

Correct the contents of the schedule information file according to 5.4 Creating a schedule information file in the manual JP1/Automatic Job Management System 3 Command Reference. Then, re-execute the command.

KAVS0169-E

Cannot operate - Jobnet has been shutdown.: jobnet-name

The jobnet is blocked. The probable causes are:

The unit defined in the calendar to be viewed does not exist.

The unit defined in the exclusive schedule does not exist.

(S)

Terminates processing.

(O)

Unregister the blocked jobnet, and then check and re-register the schedule definition. Re-execute the command as required.

KAVS0170-E

No authority for schedule definition file (schedule-information-file-name).

You do not have permission for the schedule information file.

(S)

Terminates processing.

(O)

Execute the command with the authority for the schedule information file.

KAVS0171-E

Temporary directory (directory-name) does not exist.

The temporary file directory specified in the AJSTMPDIR environment setting parameter does not exist.

(S)

Terminates processing.

(O)

Correct the temporary file directory name or create the temporary file directory. Then, re-execute the command.

For details on the settings, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS0172-E

Temporary directory name (directory-name) is invalid.

The specification of the AJSTMPDIR environment setting parameter contains an error. The probable causes are:

The temporary file directory name is not specified.

The temporary file directory name is more than 180 bytes.

A file name is specified for the temporary file directory name.

Invalid characters are used in a directory name.

(S)

Terminates processing.

(O)

Correct the temporary file directory name specified in the environment setting for the scheduler service, restart the scheduler service, and then re-execute the command.

In Windows, the invalid characters for a directory name are:

\ / ; * ? " < > | : ,

In UNIX, the invalid characters for a directory name are:

\ / ; * ? " < > | space . & ' ` ~ ( )

KAVS0173-E

No authority to use temporary directory (directory-name).

You do not have the required permissions for the temporary file directory specified in the AJSTMPDIR environment setting parameter.

(S)

Terminates processing.

(O)

Execute the command with the authority for the temporary file directory.

KAVS0175-E

Schedule definition file (file-name) contains undefined unit(s).

The schedule information file contains an undefined execution schedule of the unit.

(S)

Cancels command execution.

(O)

Specify the schedule information file for the unit specified in the command, and then re-execute the command.

KAVS0176-E

Table name is invalid.

The configuration definition file contains an invalid table name.

(S)

Cancels command execution.

(O)

Correct the table name in the configuration definition file, and then re-execute the command.

KAVS0177-E

Database type is invalid.

You cannot use the database.

(S)

Terminates processing.

(O)

Correct the database type, and then re-execute the command.

If you want to specify advanced settings and perform a data migration to a standard configuration in an environment in which multiple scheduler services are set up, make sure that the JP1/AJS3 database setup has been completed for all the scheduler services. Then, re-execute the jajs_migrate command with the -S option specified.

KAVS0178-E

Tables already exist.

Tables have been created.

(S)

Cancels command execution.

(O)

You do not have to use the ajssetup command to set up the database again because the tables have already been created. If you want to re-create them, delete the files under the directory storing the database, and then re-execute the command.

KAVS0179-E

Specified Scheduler service not exist.

The scheduler service does not exist.

(S)

Terminates processing.

(O)

Correct the scheduler service name, and then re-execute the command.

KAVS0180-E

Specified execution ID was not found.: maintenance-information

The execution ID has not been registered.

(S)

Terminates processing.

(O)

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

KAVS0181-E

Execution ID cannot be appointed.

The execution ID cannot be specified.

(S)

Terminates processing.

(O)

You do not need to specify the execution ID.

KAVS0182-E

Logical host name cannot be appointed.

The logical host name cannot be specified.

(S)

Terminates processing.

(O)

You cannot execute the command remotely. Execute the command on the desired host without specifying the logical host name.

KAVS0183-E

Unit name (unit-name) is too long.

The unit name is specified using a character string of more than 930 bytes.

(S)

Terminates processing.

(O)

Specify the unit name using no more than 930 bytes, and then re-execute the command.

KAVS0184-E

Invalid execution ID.: maintenance-information

An invalid execution ID was specified.

(S)

Terminates processing.

(O)

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

KAVS0185-E

Cannot operate - wait for activation condition.: unit-name

Processing is impossible because of the start-condition wait status.

(S)

Terminates processing.

(O)

Specify a unit which is not in the start-condition wait status, and then re-execute the command.

KAVS0186-E

Package file name not specified.

A package file name is missing.

(S)

Terminates processing.

(O)

Specify a package file name, and then re-execute the command.

KAVS0187-E

Invalid host name.: host-name

An invalid host name is specified.

(S)

Terminates processing.

(O)

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

KAVS0188-E

Contradiction in options (option) value for the Unit (unit-name).

The values of options for the unit are inconsistent.

The probable causes are:

If -wt, -th, -w, or -a is output for option:

The value specified for the abnormal threshold is equal to or greater than the lower limit of the return code for automatic retry.

If -ej, -el, -eh, -jS, -jG, -lP, or -uP is output for option:

There is no integer value in the range of values for judging the return code or variable (numeric).

If-NL or -Nt is output for option:

- The log type specified for the -NL option is not oth, and a log type is specified for the -Nt option.

- The log type specified for the -NL option is oth, but a log type is not specified for the -Nt option.

If -jd, -Ab, -rs, -re, -rc, or -ri is output for option:

- When automatic retry is enabled by setting y for the -Ab option, a value other than cod (judgment by threshold) is specified for the -jd option as the type of end judgment.

- When the automatic retry setting (-rs, -re, -rc, or -ri option) is changed, a value other than cod (judgment by threshold) is specified for the -jd option as the type of end judgment.

- When n is specified for the -Ab option to disable automatic retry, the automatic retry setting is specified by using the -rs, -re, -rc, or -ri option.

- When automatic retry is enabled by setting y for the -Ab option, the lower limit (-rs option) or upper limit (-re option) of the return code for automatic retry is equal to or less than the abnormal end threshold (-th option).

- The value of the -re option specified as the lower limit of the return code for automatic retry is greater than the upper limit (-rs option).

If -ct, -cc, or -ce is output for option:

- The specified number of shift days for scheduling the jobnet by days from the start time (-ce option) is smaller than the number of days for scheduling the jobnet by days from the start time (-cc option).

- The method for scheduling the jobnet by days from the start time was set to None, or to shift the execution date to a previous day or a subsequent day. When the method is changed to shift the execution date to a previous open day (be is specified for the -ct option) or to subsequent open day (af is specified for the -ct option), both of the following conditions exist.

- 11 or a greater value is specified for the number of shift days for scheduling the jobnet by days from the start time (-cc option).

- The number of days for scheduling the jobnet by days from the start time (-ce option) is omitted.

- For a jobnet with the -cc option set to 11, the method for scheduling the jobnet by days from the start time was set to shift the execution date to a previous day or a subsequent day. When the method is changed by specifying be or af for the -ct option, both the -cc and -ce options are omitted.

If -en is output for option:

For a flexible job, the value specified for an environment variable (-en option) exceeds 10,240 bytes. If multiple -en options are specified, the total length of the specified values exceeds 10,240 bytes.

If -jd is output for option:

For a flexible job, mdf or exf is specified for the type of end judgment (-jd option), and the end judgment file name (-jf option) is omitted.

If -jf is output for option:

For a flexible job for which mdf or exf (judgment by file) is specified for the type of end judgment, "" is specified for the end judgment file name (-jf option) to set an undefined file.

For any other case:

The option values for the unit are inconsistent.

(S)

Cancels command execution.

(O)

If -wt, -th, -w, or -a is output for option:

Change the upper or lower limit of the return code for automatic retry, and then re-execute the command.

If -ej, -el, -eh, -jS, -jG, -lP, or -uP is output for option:

Review, and if necessary, correct the following values so that the range of judgment values contains integer values, and then re-execute the command.

Minimum judgment return code (-el option)

Maximum judgment return code (-eh option)

Minimum numeric value for variable judgment (-jS option)

Maximum numeric value for variable judgment (-jG option)

Minimum boundary condition (-lP option)

Maximum boundary condition (-uP option)

If-NL or -Nt is output for option:

If you want to specify a log type, specify oth for the -NL option and specify the log type for the -Nt option, and then re-execute the command.

If -jd, -Ab, -rs, -re, -rc, or-ri is output for option:

Review and, if necessary, correct the values of options as follows, and then re-execute the command.

To enable automatic retry, specify y for the -Ab option, and then specify cod for the -jd option to specify end judgment by threshold.

To change the automatic retry setting (-rs, -re, -rc, or -ri option), specify cod for the -jd option to specify end judgment by threshold.

If automatic retry is disabled, do not specify an automatic retry setting (-rs, -re, -rc, or -ri option).

If automatic retry is enabled, make sure that the lower limit (-rs option) and the upper limit (-re option) of the return code for automatic retry are greater than the abnormal end threshold (-th option).

Make sure that the lower limit of the return code for automatic retry (-rs option) is equal to or smaller than the upper limit (-re option).

If -ct, -cc, or -ce is output for option:

Make sure that the number of shift days for scheduling the jobnet by days from the start time (-ce option) is equal to or greater than the number of days for scheduling the jobnet by days from the start time (-cc option). Then re-execute the command.

If-en is output for option:

If a flexible job is indicated for unit-name in the message, specify up to 10,240 bytes for the environment variable (-en option), and then re-execute the command.

If-jd or -jf is output for option:

If a flexible job is indicated for unit-name in the message, specify an end judgment file for the -jf option, and then re-execute the command.

For any other case:

A change option that should have been specified together with the option that caused the error was not specified, or the value specified in the option conflicted with the existing unit definition information.

Recheck the value of the option indicated in option in the message, and then re-execute the command.

KAVS0189-E

Database file install directory is invalid.: directory-name return-code

The specification in the AJSDBDIRECTORY environment setting parameter contains an error.

(S)

Abnormally terminates the service.

(O)

Check the directory specified for AJSDBDIRECTORY environment setting parameter, correct the setup, and then restart the service.

For details on the directory settings, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS0190-E

The scheduler service (scheduler-service-name) is not defined on the host (host-name).

The scheduler service is not defined for the execution target host. The probable causes are:

The specified host name is invalid.

The specified scheduler service name is invalid.

(S)

Terminates processing.

(O)

If you executed the ajssetup command, correct the specified host name (specified in the JP1_HOSTNAME environment variable or the -mh option) or the scheduler service name (specified in the AJSCONF environment variable or the -F option). Then re-execute the command.

For other commands, correct the specified host name (specified in the JP1_HOSTNAME environment variable) or the scheduler service name (specified in the AJSCONF environment variable or the -F option), and then re-execute the command.

For details about the environment variables, see 1.4 Environment variables in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS0191-E

Cannot communicate with scheduler service.

Communication with the scheduler service was disabled because the service stopped during communication with the scheduler service or other reasons.

(S)

Terminates processing.

(O)

Make sure that the scheduler service is running. Determine the cause of the error, and then re-execute the command.

KAVS0192-E

Failed to make tables.: return-code

The file could not be created due to insufficient system resources.

(S)

Terminates processing.

(O)

Recheck the settings of the kernel parameters for semaphores and shared memory. Then, re-execute the ajssetup command.

For details about the kernel parameters, see Release Notes.

KAVS0193-E

Cannot use - Unit (unit-name) is in the suspend state.

The unit is suspended and cannot be used.

(S)

Cancels command execution.

(O)

Release the unit from the suspended state, and then re-execute the command.

KAVS0194-E

Cannot use - Unit (unit-name) is not in the suspend state.

The unit is not suspended and cannot be used.

(S)

Cancels command execution.

(O)

Unregister the execution of the unit or suspend the unit, and then re-execute the command.

KAVS0198-E

Cannot use - Unit (unit-name) is currently setting or releasing the suspend setting.

Another user is suspending the unit or releasing it from the suspended state. You cannot use the unit.

(S)

Cancels command execution. If you specify more than one unit (including specifications of regular expression), the system continues command execution.

(O)

Wait until the processing terminates, and then retry.

KAVS0199-E

Cannot use because the suspend function is ineffective.: unit-name

This operation could not be performed because the suspend function has not been set up for use.

(S)

Cancels command execution. If you specify more than one unit (including specifications of regular expression), the system continues command execution.

(O)

Perform setup with ajssetup -m so that the suspend function can be used, and then re-execute the command.

KAVS0200-I

Scheduler service started. (scheduler-service-name)

The scheduler service has started.

(S)

Continues processing.

KAVS0201-I

Scheduler service ended. (scheduler-service-name)

The scheduler service has terminated.

(S)

Terminates the scheduler service.

KAVS0202-E

Log daemon ended abnormally. (code: code)

The log daemon terminated abnormally.

(S)

Cancels the processing of the log daemon, but continues the operation by the scheduler service.

(O)

Contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS0203-I

Log file (scheduler-log-file-name-before-replacement) has been changed to scheduler-log-file-name-after-replacement.

The size of the scheduler log file exceeded the size that the configuration definition parameter specifies. The scheduler log file will be replaced.

(S)

Continues processing.

(O)

Make a backup scheduler log file as required.

KAVS0204-E

Scheduler service (scheduler-service-name) ended (name: process-name, code: return-code), but Scheduler service restart.

The scheduler service has abnormally terminated so it has restarted.

(S)

Continues processing.

(O)

Contact the system administrator, and collect data. For details, see 1.2.3 To the system administrators.

KAVS0208-E

Scheduler service is active.

The scheduler service has already started.

(S)

Terminates processing.

KAVS0209-E

Scheduler service is inactive.

The scheduler service has already stopped.

(S)

Terminates processing.

KAVS0210-I

Local time has been changed from local-date-and-time-before-change to local-date-and-time-after-change.

The local date and time of the scheduler service has been changed.

(S)

Terminates processing.

KAVS0211-W

Standstill of last scheduler service (process-name) was incomplete.

The previous termination of the scheduler service was incomplete. The running job may have been incorrectly stopped. Check the job status.

(S)

Continues startup of the service.

(O)

Check the execution status of jobs for any problem.

KAVS0213-I

The job-execution suppression option is set for the scheduler service (scheduler-service-name).

The job execution suppression option is set, preventing the job from being executed.

(S)

Continues processing.

(O)

Use ajsalter -s none to release the job execution suppression, and continue operation.

KAVS0214-I

The generation management sub-daemon (scheduler-service-name) started.

This message indicates that the generation management sub-process has started.

(S)

Continues processing.

KAVS0215-I

The generation management sub-daemon (scheduler-service-name) ended.

This message indicates that the generation management sub-process has ended.

(S)

Continues processing.

KAVS0216-E

The generation management sub-daemon (scheduler-service-name) ended abnormally. (code: code)

Since the generation management sub-process ended abnormally, the schedule control process (ajsschd) deletes jobnet registration information.

(S)

Continues processing.

(O)

Take actions according to the messages output before and after this error message.

KAVS0217-E

The generation management sub-daemon (scheduler-service-name) ended abnormally, so the generation management sub-daemon will now restart.

Since the generation management sub-process ended abnormally, it will be restarted.

(S)

Continues processing.

(O)

Take actions according to the messages output before and after this error message.

KAVS0218-E

The database is still being accessed, so the cold start of the scheduler service (scheduler-service-name) ended abnormally.

Since the scheduler service for which a cold start was attempted was still accessing the database, database registration information could not be deleted and the cold start of the scheduler could not be performed. The possible causes are:

JP1/AJS3 - View is connected to the object scheduler service.

A JP1/AJS3 command is executing on the object scheduler service.

You can use the ajsstatus or jajs_status command to check the connection status of JP1/AJS3 - View. For details about each command, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

(S)

Cancels processing.

(O)

If JP1/AJS3 - View is connected:

Execute the jajs_hstd_stop command to stop the ajsinetd process temporarily, and then execute the jajs_hstd command to start the ajsinetd process. For details on the jajs_hstd and jajs_hstd_stop commands, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

If a JP1/AJS3 command is executing:

Wait for the command to terminate or cancel the processing.

Remove the process that is accessing the database. Then, use the jajs_spmd command with the -cold and -n jajs_schd options specified to perform a cold start of the object scheduler service again.

KAVS0219-E

Startup will now stop due to a stop request to the scheduler service. (scheduler-service-name)

Startup processing will stop because another user issued a stop request to the scheduler service.

(S)

Cancels command execution.

(O)

If you want to start the scheduler service, re-execute the command.

KAVS0220-I

Scheduler log output process started.

The scheduler log output process has started.

(S)

Continues processing.

KAVS0221-I

Scheduler log output process ended.

The scheduler log output process has ended.

(S)

The scheduler log output process has ended.

KAVS0222-E

Host name (host-name) is too long.

A host name is specified using a character string of more than 32 bytes.

(S)

Terminates processing.

(O)

Specify a host name that has fewer than 33 bytes, and then re-execute the command. For details on the jajs_migrate command, if it has been executed, see jajs_migrate in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS0230-E

Connection to database has been reset.

The system has detected a database disconnection, and will stop the scheduler service.

(S)

Stops the scheduler service.

(O)

See the database message output to Windows event log or the syslog to correct the setting so that the scheduler service can be connected to the database, and then start the scheduler service.

KAVS0231-W

Cannot read job-status reporting port information, service name=service-name

Information for the service name indicated in the message cannot be read. The system assumes 20245 as the port number and starts the scheduler service.

(S)

Continues processing.

(O)

Check the services file, correct the service name, and then restart.

For details on the ports that JP1/AJS3 uses, see A.1 Tables of port numbers in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVS0232-W

Cannot read host name information.: maintenance-information-1 maintenance-information-2

Since information about the local host cannot be obtained, nothing will be set for the host name in termination messages for judgment jobs and OR jobs.

(S)

Continues processing.

(O)

Recheck the settings of JP1/Base host name information (JP1_HOSTNAME environment variable) and the network settings. Use the hostname command to make sure that the local host name is set correctly. Correct the settings, and then restart the scheduler service.

KAVS0240-I

Monitoring of a jobnet's start conditions started. (name: jobnet-name: execution-ID)

The jobnet starts the monitoring of the start condition. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

KAVS0241-I

Monitoring of a jobnet's start conditions ended. (name: jobnet-name: execution-ID, status: status)

The jobnet terminated the monitoring of the start condition. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter. The character strings displayed in status and their meanings are as follows:

u: The monitoring could not be started.

c: The monitoring canceled.

i: The monitoring was interrupted.

n: The monitoring normally terminated.

(S)

Continues processing.

(O)

If the character string displayed in status is u or c, and you need to perform monitoring again, cancel registration, re-register the jobnet, and then start monitoring.

If the character string displayed in status is i or n, no action is required.

KAVS0242-I

The execution request of the event job started. (name : jobnet-name : execution-ID)

The execution request of the event job starts. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

KAVS0243-E

Cannot terminate the jobnet(jobnet-connector-name : execution-ID) - jobnet for the connection destination is not registered.

Although execution of the jobnet connector started, the jobnet connector cannot be terminated because the connection-destination jobnet is not registered for execution.

(S)

Places the jobnet connector into Running + Abend status.

(O)

Check the connection-destination jobnet according to the definition of the jobnet connector displayed in the message, and then register that jobnet for execution.

KAVS0244-E

Cannot start the jobnet for the connection destination (jobnet-name : execution-ID) - jobnet connector is not registered.

Execution of the connection-destination jobnet cannot be started because the root jobnet for which the jobnet connector corresponding to the connection-destination jobnet is defined has not been registered for execution.

(S)

Places the connection-destination jobnet into Wait for start time status.

(O)

Check the jobnet connector according to the definition of the connection-destination jobnet displayed in the message, and then register the root jobnet for which the jobnet connector is defined for execution.

KAVS0245-W

The execution result (execution-ID : execution-ID) of the jobnet (jobnet-name) was deleted to create a new generation.

One generation of the execution result was deleted so that creating a new generation would not cause the number of jobnet generations to exceed the limit. For a jobnet with starting conditions, the execution result of generations that derived from the deleted generation being monitored were also deleted.

(S)

Continues processing.

(O)

The combined total of the number of logs to keep and scheduled generations exceeds the limit. Revise the jobnet definition and execution registration method so that the combined total of the number of logs to keep and the number of scheduled generations does not exceed the limit.

For details about the limits for units, see B.3 Limits for units in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVS0246-E

The system failed to delete the execution result (execution-ID : execution-ID) of the jobnet (jobnet-name).: maintenance-information

The system could not delete the execution result of one generation.

(S)

Continues processing.

(O)

Take actions according to the Windows event log or syslog message output immediately before this error message.

KAVS0247-E

An attempt to delete the execution result (execution-ID : execution-ID) of the jobnet (jobnet-name), which has a start condition, failed. : maintenance-information

The system failed to delete the execution-result generation of a jobnet that has a start condition because memory was insufficient. Also, the oldest generation of execution results was deleted. The system continues processing of the jobnet that has a start condition without aborting.

(S)

The system deletes the oldest generation of the execution results and continues processing.

(O)

Check the following settings:

In UNIX, see Release Notes, and make sure that the value of the kernel parameter for memory is greater than the estimated value.

Check the status of the process that was running when the error occurred to make sure that the amount of memory available is greater than the estimated value.

To confirm the status of the deleted generation of the execution result, refer to the scheduler logs.

KAVS0248-I

End of a Job delayed. (name: job-name: execution-ID)

End of a job is delayed. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

(O)

The end of a job is delayed. Check the job status and the processing status of the program being executed by the job, and then take corrective action if necessary.

KAVS0249-W

The scheduler services stopped before execution of the job(job-name : execution-ID) began.

The scheduler service stopped before the job was placed in Running status. As a result, if execution of the job begins on the agent, the job status changes to Running when the scheduler service is started. This might cause a delay during delay detection for the required execution time for a job.

(S)

Continues processing.

(O)

Use the ajsshow command to check the execution start time or end time of the job executed on another host, and check whether the job has been running for a long time, exceeding the required execution time.

KAVS0251-I

maintenance-information

A queueless job started execution. For details on maintenance information, see C.2 Log entries output by the queueless agent service in the manual JP1/Automatic Job Management System 3 Troubleshooting.

(S)

Continues processing.

KAVS0252-I

maintenance-information

The queueless job terminated normally. For details on maintenance information, see C.2 Log entries output by the queueless agent service in the manual JP1/Automatic Job Management System 3 Troubleshooting.

(S)

Continues processing.

KAVS0253-E

maintenance-information

The queueless job terminated abnormally. For details on maintenance information, see C.2 Log entries output by the queueless agent service in the manual JP1/Automatic Job Management System 3 Troubleshooting.

(S)

Continues processing.

(O)

Determine the cause of the error by checking the integrated trace log or the detailed log of the job, correct the cause of the error, and then restart the appropriate job.

KAVS0254-W

maintenance-information

The queueless job completed with a warning. For details on maintenance information, see C.2 Log entries output by the queueless agent service in the manual JP1/Automatic Job Management System 3 Troubleshooting.

(S)

Continues processing.

(O)

Determine the cause of the error by checking the integrated trace log or the detailed log of the job, correct the cause of the error, and then restart the appropriate job.

KAVS0260-I

Jobnet started. (name: jobnet-name: execution-ID)

The jobnet starts. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

KAVS0261-I

Jobnet ended normally. (name: jobnet-name: execution-ID)

The jobnet has normally terminated. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

KAVS0262-E

Jobnet ended abnormally. (name: jobnet-name: execution-ID)

The jobnet has abnormally terminated.

(S)

Continues processing. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(O)

Check the execution status of the units contained in the jobnet to examine the cause of the unsuccessful execution, and then take action to correct it.

KAVS0263-I

Job started.(name: jobnet-name: execution-ID, host: host-name, JOBID: job-number)

The job starts.

(S)

Continues processing. execution-ID, host-name, and job-number appear if you specified yes for the LOGINFOALL environment setting parameter.

KAVS0264-I

Job ended normally. (name: job-name: exception-ID, host: host-name, code: code, JOBID: job-number)

The job has normally terminated. execution-ID, code, and job-number appear if you specify yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

KAVS0265-E

Job ended abnormally. (name: job-name: exception-ID, status: status, code: code, host: host-name, JOBID: job-number)

The job has abnormally terminated.

The character strings displayed in status and their meanings are as follows:

a: An error was detected.

f: The job could not be started.

c: The job forcibly terminated.

?: Unknown status.

For details, see the Execution Result Details dialog box.

execution-ID and job-number appear if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

(O)

Examine the cause of the error and take action to correct it. 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).

If code 128 is displayed for a PC job, the job may have terminated abnormally due to a desktop heap that is too small.

See 4.2.3 Changing the JP1/AJS3 service settings (Windows only) in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide and, if necessary, check the account of the JP1/AJS3 service. You must also take measures such as checking the number of concurrent jobs or the startup processes for the entire system to prevent errors caused by a desktop heap that is too small.

This message also appears when you start the JP1/AJS3 service after executing the jpomanevreset command without the -e option. In this case, however, ignore the message because it is output as a result of terminating an event job by resetting the event.

KAVS0266-I

To submit Job again, it is canceled. (name: job-name: exception-ID, JOBID: job-number)

When the scheduler service stops, the system cancels the jobs that were queued by job execution control or the jobs were not queued by job execution control when job submission started.

execution-ID and job-number appear if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Cancels the jobs that were queued by job execution control or the jobs that were not queued by job execution control when job submission started, and returns those jobs to the Wait for prev. to end status. Then, the job is resubmitted and placed in the Now queuing status. Note, however, that if the previous unit ended abnormally, the job is not resubmitted, but is placed in the Not executed + Ended status.

KAVS0267-I

All Jobnet entries canceled. (scheduler-service-name)

All jobnet entries have been forcibly canceled.

(S)

Continues the cold-start process for the scheduler service.

(O)

If necessary, inform the jobnet owner, that registration was canceled.

KAVS0268-W

Jobnet ended with warning. (name: jobnet-name: execution-ID)

The jobnet has terminated with a warning. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

(O)

Check the execution status of the units contained in the jobnet to examine the cause of the unsuccessful execution, and then take action to correct it.

KAVS0269-W

Job ended with warning. (name: job-name: exception-ID, code: code, host: host-name, JOBID: job-number)

The job has terminated with a warning. The job has terminated with a warning. execution-ID and job-number appear if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

(O)

Examine the cause of the warning and take action to correct it. For details on the job execution results, check the Execution Result Details dialog box for JP1/AJS3 - View.

KAVS0270-I

Jobnet cannot be executed while being held. (name: jobnet-name: execution-ID)

The jobnet cannot be executed while being held. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

(O)

Release the jobnet from being held as required.

KAVS0271-I

Job cannot be executed while being held. (name: jobnet-name: execution-ID)

The job cannot be executed while being held. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

(O)

Release the job from being held as required.

KAVS0272-E

Jobnet (jobnet-name: execution-ID) cannot be executed - error (maintenance-information) occurred.

The error indicated by maintenance-information occurred. The jobnet cannot be executed. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Blocks the jobnet.

(O)

See the message output before this message to examine the cause of the error and correct it. Then, unregister the blocked jobnet and reregister it.

KAVS0273-E

Jobnet (jobnet-name: execution-ID) cannot be scheduled - error (maintenance-information) occurred.

The error, that prevented processing, indicated by maintenance-information occurred. The jobnet cannot be scheduled. The probable cause is that a unit which does not exist is specified in Exclusive schedule or Refer to a calendar of another job group in the schedule definition of the jobnet. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Blocks the jobnet.

(O)

Make sure that the settings for Exclusive schedule and Refer to a calendar of another job group in the schedule definition of the jobnet are correct. If they are correct, see the message output before this message to examine the cause of the error and correct it.

Then, unregister the blocked jobnet and reregister the jobnet.

KAVS0274-E

The number of jobnets for execution registration exceeded the limit. (Jobnet: jobnet-name, code: code)

The number of jobnets for execution registration exceeded the limit. The jobnet cannot be scheduled.

(S)

Does not schedule the jobnets.

(O)

Unregister unnecessary jobnets and then reregister the jobnets.

KAVS0275-I

Start of a Jobnet delayed. (name: jobnet-name: execution-ID)

The jobnet is delayed starting.

A delayed jobnet might affect succeeding jobnets and might cause overall processing to be delayed.

execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

(O)

An error might have caused the start of the jobnet to be delayed. Check the execution status of the preceding unit and upper-level jobnet, and the status of the jobnet for which the message was output. Then, take corrective action if necessary.

KAVS0276-I

End of a Jobnet delayed. (name: jobnet-name: execution-ID)

The jobnet is delayed stopping.

A delayed jobnet might affect succeeding jobnets and might cause overall processing to be delayed.

execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

(O)

An error might have caused the end of the jobnet to be delayed. Check the status and execution status of the preceding unit, the upper-level jobnet, the jobnet for which the message was output, and the subordinate units. Then, take corrective action if necessary.

KAVS0277-I

Start time for next execution schedule has been reached. (name: jobnet-name: execution-ID)

Since the start time for the next execution schedule was reached or because the start condition was satisfied, an attempt was made to start a new jobnet during execution of another jobnet. However, the multiple startup was not specified. The new jobnet was queued.

Alternatively, a timeout occurred for the jobnet for which start conditions were set.

execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

(O)

Take action according to your operation.

For details on actions to be taken for a jobnet for which start conditions were set, see 8.1.1 Stopping a jobnet that is monitoring start conditions in the JP1/Automatic Job Management System 3 Administration Guide.

KAVS0278-I

Job submit started. (name: jobnet-name: execution-ID)

Submission of the job starts. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

KAVS0279-E

Jobnet ended with execution-deferred status. (name: jobnet-name: execution-ID)

The jobnet terminated with the execution-deferred status. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues performing the scheduler control process.

(O)

Re-execute or re-register the jobnet if the jobnet needs to be executed again.

If a jobnet in the status Skipped so not executed no longer exists, take action such as registering the jobnet again.

For details about the conditions under which a jobnet enters the status Skipped so not executed, see 6.1 Status levels of jobnets, jobs, and jobnet connectors in the manual JP1/Automatic Job Management System 3 Overview.

KAVS0289-E

Manager's host name not specified.

The execution manager for the remote jobnet is not specified.

(S)

Abnormally terminates the remote jobnet.

(O)

Correctly specify the execution manager for the remote jobnet, and then register the remote jobnet for execution.

KAVS0291-E

Specified host name does not exist.: host-name

The specified host name does not exist.

(S)

For job execution: Abnormally terminates the job (as unsuccessful startup) and continues processing.

For command execution: Cancels executing the command.

(O)

Specify the correct host name and then retry.

KAVS0297-E

Cannot create directory or file (directory-name or file-name).: maintenance-information-1 maintenance-information-2 maintenance-information-3

A directory or a file could not be created due to a cause such as no access permission for the temporary file directory.

(S)

Cancels processing.

(O)

Make sure that you have update permission for the temporary file directory.

If this error occurs while you are registering a root jobnet for fixed execution, another user might be performing fixed execution registration. Wait until the other user finishes the fixed execution registration, and then re-execute the fixed execution registration.

KAVS0300-E

Unit does not exist.

The cause may be either of the following:

Another user deleted the specified unit.

The calendar information about the jobnet schedule for execution registration does not contain the specified job group.

(S)

Terminates processing.

(O)

Re-open the window.

KAVS0301-E

No authorization.

The probable causes are as follows:

You do not have authorization for the unit (including the lower-level unit) or the associated file (such as the standard error output file).

Memory became insufficient during user mapping for the JP1 user specified in the JP1_USERNAME environment variable, preventing the authorization check for the unit.

You do not have authorization for the path specified in the -i option of the ajsembdbinstl command.

(S)

Terminates processing.

(O)

Execute processing with the authorization.

For operations performed by an AJS administrator, make sure that the required authorization has been set for the AJS administrators.

KAVS0304-E

In use by other user.

Another user is using the unit.

(S)

Terminates processing.

(O)

Wait for the other user to complete using the unit, and then retry.

KAVS0311-E

Invalid Unit definition.

An invalid definition is made for the unit.

(S)

Cancels processing. If you specify more than one unit definition file name, the system continues processing.

(O)

Specify the unit definition file correctly, and then re-execute the command.

For details about how to set up unit definition files, see 5. Creating Information Definition Files in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS0314-E

File processing count exceeds the limit.

The number of files to be processed exceeded the limit.

(S)

Cancels processing.

(O)

Close unnecessary windows and dialog boxes, and delete unnecessary files to increase available free space. Then re-execute the operation.

In UNIX, 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)

Also see Release Notes, and change the settings for the file system.

KAVS0315-E

Not enough space in file system.

The file system does not have sufficient space.

(S)

Cancels processing.

(O)

Close unnecessary windows and dialog boxes, and delete unnecessary files to increase available free space. Then re-execute the operation.

In UNIX, 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)

Also see Release Notes, and change the settings for the file system.

KAVS0317-E

Lock resources count exceeds the limit.

The number of file lock resources exceeded the limit that the system can process.

(S)

Terminates processing.

(O)

Close unnecessary windows and dialog boxes, and delete unnecessary files to increase available free space. Then re-execute the operation.

In UNIX, 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)

Also see Release Notes, and change the settings for the file system.

KAVS0318-E

System resources became insufficient.

A shortage of system resources occurred.

(S)

Terminates processing.

(O)

Close unnecessary windows or dialog boxes. Then, retry.

In UNIX, 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)

For details about the kernel parameters, see Release Notes.

KAVS0319-E

Files not exist or cannot access files by insufficient system resources.: maintenance-information

The system cannot access files for one of the following reasons:

A lock file or ISAM file does not exist.

The directory specified in the AJSTMPDIR environment setting parameter does not exist.

The target backup box or backup file was deleted by the ajsbkudel command while the Backup or Restore dialog box was displayed in JP1/AJS3 - View.

System resources are insufficient.

(S)

Terminates processing.

(O)

Make sure that a lock file or ISAM file exists in the database directory specified in the AJSDBDIRECTORY environment setting parameter. If the file does not exist, set up the scheduler service. If the file exists, make sure that the directory for temporary files specified in the AJSTMPDIR environment setting parameter exists.

If the target backup box or backup file was deleted by the ajsbkudel command while the Backup or Restore dialog box was displayed in JP1/AJS3 - View, close the Backup or Restore dialog box in JP1/AJS3 - View, and then redisplay it.

For any other case, recheck the settings of the semaphores and shared memory in the kernel parameters.

For details about the kernel parameters, see Release Notes.

KAVS0322-E

Cannot operate - Scheduler service has not started.

Processing is impossible because the specified scheduler name is incorrect or the scheduler service has not started.

Alternatively, processing using the terminal service or remote desktop service is impossible.

(S)

Terminates processing.

(O)

Check the specified scheduler name and start the JP1/AJS3 service, and then retry. If this message appears during execution of a remote jobnet, start the scheduler service specified in either of the following items on the host where the remote jobnet was executed: the REMNETSERVICENAME environment setting parameter. Then, retry.

For the following commands, start the JP1/AJS3 service, and then retry.

ajsalter

ajschgstat

ajsentry

ajsintrpt

ajskill

ajsleave

ajsplan

ajsrelease

ajsrerun

ajsstart

ajsstop

ajssuspend

Alternatively, re-execute the operation in an environment that does not use the terminal service.

KAVS0358-E

Cannot operate - JP1/AJS service has not started. (logical host=logical-host-name)

Operation is impossible because the JP1/AJS3 service has not started.

(S)

Terminates processing.

(O)

Start the JP1/AJS3 service, and then re-execute the command.

KAVS0369-E

Cannot operate - version is different.

Processing is impossible because the version of JP1/AJS3 that manages the unit to be processed does not match that of JP1/AJS3 on the operating side.

(S)

Continues processing.

(O)

Contact a user who has administrator privileges or superuser privileges to check the version.

KAVS0435-E

Environment file name length exceeds 255 bytes.

The length of the environment variable file name exceeded 255 bytes.

(S)

Cancels processing.

(O)

Specify an environment variable file name that is less than 256 bytes, and then retry.

KAVS0439-E

Complete Unit name is too long.

The full name of the specified unit exceeded the limit.

The limits are as follows:

Job name and recovery job name

930 bytes or less

Other names than above

899 bytes or less

(S)

Cancels processing.

(O)

Specify the full unit name within the limit, and then retry.

KAVS0470-E

Among the generations registered in the specified period, there is no generation whose registration can be canceled. (unit-name)

There is no information registered in the specified period. This prevented the registration from being canceled.

(S)

Cancels command execution.

(O)

Check the period specified for canceling the registration, and then re-execute the command.

KAVS0475-I

There is no log record that satisfies the specified conditions.

Information cannot be output because there is no log record that satisfies the specified conditions.

(S)

Cancels command execution.

(O)

Correctly specify the conditions, and then re-execute the command.

KAVS0476-E

Invalid format in the specified scheduler log file. (line:line-number)

An invalid format log record was found in the line indicated in line-number in the specified scheduler log file.

(S)

Continues processing from the next line of the line indicated in line-number.

(O)

Check the contents of the scheduler log file and, if necessary, re-execute the command.

KAVS0477-E

Scheduler log file name not specified.

A scheduler log file name is not specified.

(S)

Cancels command execution.

(O)

Specify a scheduler log file name, and then re-execute the command.

KAVS0478-E

Scheduler log file name is too long.

A scheduler log file name is specified using a character string of more than 255 bytes.

(S)

Cancels command execution.

(O)

Specify a scheduler log file name that has fewer than 256 bytes, and then re-execute the command.

KAVS0500-E

Scheduler service has already started.

The scheduler service has already started.

(S)

Cancels command execution.

(O)

Use Task Manager or the ps command to check the status of the process. If the process still remains, forcibly stop it or restart the OS.

Also make sure that the procedures for adding and deleting a scheduler service and a logical host are correct. For details on the procedures, see 6.1.1 Settings for starting multiple scheduler services in the JP1/Automatic Job Management System 3 Configuration Guide, 8.2 Setting up the operating environment for cluster system operation in the JP1/Automatic Job Management System 3 Configuration Guide, 15.1.1 Settings for starting multiple scheduler services in the JP1/Automatic Job Management System 3 Configuration Guide, and 17.2 Setting up the operating environment for cluster system operation in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS0530-I

JP1/AJS2 Monitor service started.

ajsinetd process starts.

(S)

Continues processing.

KAVS0531-I

JP1/AJS2 Monitor service stopped.

ajsinetd process terminates.

(S)

Terminates the ajsinetd process.

KAVS0532-I

JP1/AJS2 Monitor service started accepted processing. (From: IP-address, To: logical-host-name, JP1-user-name, PID: process-ID)

ajsinetd process starts the processing that is accepted. The monitor server that ajsinetd accepted from IP-address has started on logical-host-name.

(S)

Continues processing.

KAVS0533-I

JP1/AJS2 Monitor service ended accepted processing. (From: IP-address, To: logical-host-name, JP1-user-name, PID: process-ID)

ajsinetd process terminated the processing that was accepted. The monitor server that ajsinetd accepted from IP-address and started on logical-host-name has terminated.

(S)

ajsinetd process terminated the processing that was accepted.

KAVS0534-I

JP1/AJS2 - View has been connected to the scheduler service (scheduler-service-name). (JP1-user-name (OS-user-name), process-ID)

JP1/AJS3 - View was connected to the scheduler service.

(S)

Continues processing.

KAVS0535-I

JP1/AJS2 - View has been disconnected from the scheduler service(scheduler-service-name). (JP1-user-name (OS-user-name), process-ID)

JP1/AJS3 - View was disconnected from the scheduler service.

(S)

JP1/AJS3 - View disconnects from the scheduler service.

KAVS0538-I

Start remote command request. : maintenance-information-1,maintenance-information-2,maintenance-information-3,maintenance-information-4,maintenance-information-5

A remote command request will now start.

(S)

Continues processing.

KAVS0539-I

Finished remote command request. : maintenance-information

A remote command request terminated.

(S)

Continues processing.

KAVS0540-Q

Ok to change the local time? (y:OK/n:NO)

This message checks whether you want to change the local date and time.

(S)

Waits for a response.

(O)

Enter y to change the local date and time.

Enter n not to change the local date and time.

KAVS0541-E

Specified local time is not acceptable.

The local date and time to be changed was specified outside the range (between the year 1994 and 2036).

(S)

Cancels processing.

(O)

Set the local date and time within the range from the year 1994 to 2036.

KAVS0545-I

The shift processing of JP1/AJS3 to a standard composition has started.

The migration processing of JP1/AJS3 to the standard configuration has started.

(S)

Continues processing.

KAVS0546-I

The shift processing of JP1/AJS3 to a standard composition ended normally.

The migration processing of JP1/AJS3 to the standard configuration terminated normally.

(S)

Terminates command processing normally.

KAVS0547-E

The shift processing of JP1/AJS3 to a standard composition ended abnormally.

The migration processing of JP1/AJS3 to the standard configuration terminated abnormally.

(S)

Cancels processing.

(O)

Correct the error and then retry.

KAVS0548-I

The shift processing of JP1/AJS3 to a standard composition has already been completed.

The migration processing of JP1/AJS3 to the standard configuration has already been completed.

(S)

Cancels command execution.

KAVS0549-E

Because the JP1/AJS3 service has started, the shift processing of JP1/AJS3 to a standard composition has been discontinued.

The migration processing of JP1/AJS3 to the standard configuration has been canceled because the JP1/AJS3 service has started. In UNIX, shared memory information might not have been deleted after the JP1/AJS3 service was stopped.

(S)

Cancels processing.

(O)

Stop the JP1/AJS3 service, and then retry.

In UNIX, stop the JP1/AJS3 service, and execute the ajsshmdel command. The path to the ajsshmdel command is /opt/jp1ajs2/bin/ajsshmdel.

The following are examples of executing the command:

For sh:

/opt/jp1ajs2/bin/ajsshmdel >/dev/null 2>&1

For csh:

/opt/jp1ajs2/bin/ajsshmdel >&/dev/null

KAVS0550-E

An error occurred in the shift processing of JP1/AJS3 to the standardized configuration. : maintenance-information-1 maintenance-information-2

An error occurred during migration processing of JP1/AJS3 to the standard configuration.

(S)

Cancels processing.

(O)

Take action according to the information output in the detailed information, and then retry.

KAVS0560-I

The JP1/AJS3 - Software Development Kit connection service will now start.

ajscdinetd process starts.

(S)

Continues processing.

KAVS0561-I

The JP1/AJS3 - Software Development Kit connection service will now start.

ajscdinetd process terminates.

(S)

Terminates the ajscdinetd process.

KAVS0562-I

The JP1/AJS3 - Software Development Kit connection service will now start the accepted processing. (From : IP-address, To : logical-host-name, JP1-user-name, PID : process-ID)

The ajscdinetd process starts the processing accepted from JP1/AJS3 - Software Development Kit. The monitor server accepted from the IP address indicated for From has started on the logical host indicated for To.

(S)

Continues processing.

KAVS0563-I

The JP1/AJS3 - Software Development Kit connection service ended the accepted processing. (From : IP-address, To : logical-host-name, JP1-user-name, PID : process-ID)

The ajscdinetd process terminated the processing accepted from JP1/AJS3 - Software Development Kit. The monitor server accepted from the IP address indicated for From and started on the logical host indicated for To terminated.

(S)

Terminates the processing accepted by the ajscdinetd process.

KAVS0564-I

JP1/AJS3 - Software Development Kit connected to the scheduler service (scheduler-service-name). (JP1-user-name (OS-user-name), process-ID)

JP1/AJS3 - Software Development Kit was connected to the scheduler service.

(S)

Continues processing.

KAVS0565-I

JP1/AJS3 - Software Development Kit disconnected from the scheduler service (scheduler-service-name). (JP1-user-name (OS-user-name), process-ID)

JP1/AJS3 - Software Development Kit was disconnected from the scheduler service.

(S)

JP1/AJS3 - Software Development Kit disconnects from the scheduler service.

KAVS0566-E

A connection cannot be established because the limit on the number of possible concurrent sessions has been exceeded. : maximum-number-of-connections

A connection could not be established because the number of sessions for JP1/AJS3 - Software Development Kit exceeds the maximum number of concurrent sessions specified for the CDMAXSESSION environment setting parameter.

(S)

Cancels command execution.

(O)

Check whether the estimated value of the MAXSESSION environment setting parameter is correct. If necessary, change the value.

If the estimate is correct, wait until other connections have ended, and then try to establish the connection again.

KAVS0567-E

The scheduler service does not exist. : scheduler-service-name

The scheduler service name specified for an argument of the API provided by JP1/AJS3 - Software Development Kit does not exist.

(S)

Cancels command execution.

(O)

Correct the scheduler service name specified for the API argument of JP1/AJS3 - Software Development Kit, and then re-execute the API.

KAVS0568-I

The JP1/AJS3 - Software Development Kit connection service will now start the accepted processing. (From : IP-address, To : logical-host-name, JP1-user-name, PID : process-ID)

The ajscdinetd process starts the processing accepted from JP1/AJS3 - Web Console. The monitor server accepted from the IP address indicated for From has started on the logical host indicated for To.

(S)

Continues processing.

KAVS0569-I

The JP1/AJS3 - Software Development Kit connection service ended the accepted processing. (From : IP-address, To : logical-host-name, JP1-user-name, PID : process-ID)

The ajscdinetd process terminated the processing accepted from JP1/AJS3 - Web Console. The monitor server accepted from the IP address indicated for From and started on the logical host indicated for To terminated.

(S)

Terminates the processing accepted by the ajscdinetd process.

KAVS0582-E

Specified data format is not acceptable for the environment variable.: environment-variable-name

An invalid environment variable was specified.

(S)

Cancels command execution.

(O)

Correct the environment variable, and then re-execute the command.

For details on the environment variables, see 1.4 Environment variables in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS0600-E

Valid calendar definition options not specified.

The calendar definition does not contain the required option.

(S)

Cancels command execution.

(O)

Specify the option in the calendar definition, and then re-execute the command.

KAVS0601-E

Date information file (file-name) does not exist.

The date information file does not exist.

(S)

Continues command execution. Cancels the processing of the uncreated file.

(O)

Create the date information file, and then re-execute the command.

KAVS0602-E

Illegal date (date) specified.

An illegal date was specified.

(S)

Continues command execution. The system invalidates the illegal date.

(O)

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

KAVS0603-E

Illegal character exists in option string (option-character-string).

The option or the date information file contains an illegal character.

(S)

Continues command execution. The system invalidates the illegal character.

(O)

Correct the character in the option or in the date information file. Then, re-execute the command.

KAVS0604-E

Cannot read date information file (file-name) - error occurred.

An error occurred during input into the date information file.

(S)

Continues command execution. The system invalidates the file where the error occurred.

(O)

Check the specified date information file (open day information file, closed day information file, cancellation day information file, or calendar information file) to correct the cause of the error, and then re-execute the command.

KAVS0605-E

Cannot read date information file (file-name) - no authority.

The date information file does not have any access permission.

(S)

Continues command execution. The system invalidates the file for which you have no access permission.

(O)

Set access permission for the specified date information file (open day information file, closed day information file, cancellation day information file, or calendar information file), and then re-execute the command.

KAVS0606-E

The calendar information file(file-name) contains no valid unit definition parameter.

The calendar information file contains no valid unit definition parameter.

(S)

Cancels command execution.

(O)

Specify valid unit definition parameters in the calendar information file, and then re-execute the command.

If the KAVS0602-E or KAVS0603-E error message was output before this one, remove the cause of the error, and then re-execute the command.

KAVS0620-Q

Ok to clear Unit (unit-name) ? (y:OK/n:NO)

This message checks whether you want to clear the unit.

(S)

Waits for a response.

(O)

Enter y to clear the unit.

Enter n not to clear the unit.

KAVS0621-E

Cannot delete - Unit (unit-name) is registered.

The specified unit cannot be deleted because it is contained in a registered root jobnet or a registered jobnet.

(S)

Cancels command execution.

(O)

Unregister the unit, and then re-execute the command. To delete jobnets and jobs defined in a suspended root jobnet, re-execute the command with the -S option.

KAVS0622-E

Cannot delete - Unit (unit-name) has registered Jobnet.

The unit that contains a registered jobnet cannot be deleted.

(S)

Cancels command execution.

(O)

Unregister the jobnet, and then re-execute the command.

KAVS0623-E

Cannot delete - Unit (unit-name) is running.

You cannot delete the running unit.

(S)

Cancels command execution.

(O)

Waits for the processing of the unit to terminate, and then re-execute the command.

KAVS0630-E

Cannot copy - Unit (unit-name) is already registered.

The output destination unit cannot be copied because it has already been registered.

(S)

Cancels command execution.

(O)

Unregister the output destination unit, and then re-execute the command. To copy jobnets and jobs into a suspended root jobnet, re-execute the command with the -S option.

KAVS0631-E

Cannot move - Unit (unit-name) is already registered.

The output destination unit cannot be moved because it has already been registered.

(S)

Cancels command execution.

(O)

Unregister the output destination unit, and then re-execute the command. To move jobnets and jobs into a suspended root jobnet, re-execute the command with the -S option.

KAVS0632-E

Cannot move - Unit (unit-name) contains a registered Jobnet.

The output destination unit cannot be moved because it contains a registered jobnet.

(S)

Cancels command execution.

(O)

Unregister the output destination unit, and then re-execute the command. To move jobnets and jobs into a suspended root jobnet, re-execute the command with the -S option.

KAVS0633-E

Cannot move - Unit of the same name (unit-name) exists.

A unit that with the same name already exists in the move-destination.

(S)

Cancels command execution.

(O)

Change the unit name, and then re-execute the command.

KAVS0634-E

Cannot copy - Unit of the same name (unit-name) exists.

A unit with the same name already exists in the copy-destination.

(S)

Cancels command execution.

(O)

Change the unit name, and then re-execute the command.

KAVS0635-E

Cannot copy - Unit (unit-name) does not exist.

An attempt was made to copy more than one unit. However, copying was impossible because the destination unit does not exist.

(S)

Cancels command execution.

(O)

Create the destination unit, and then re-execute the command.

KAVS0636-E

Cannot move - Unit (unit-name) does not exist.

An attempt was made to move more than one unit. However, moving was impossible because the destination unit does not exist.

(S)

Cancels command execution.

(O)

Create the destination unit, and then re-execute the command.

KAVS0637-E

Output Unit name not specified.

An output unit name is missing.

(S)

Cancels command execution.

(O)

Specify the output destination unit name in the -o option, and then re-execute the command.

KAVS0638-E

Cannot treat as output Unit.: unit-name

The unit indicated in unit-name cannot be handled as an output destination unit.

(S)

Cancels command execution.

(O)

Recheck the conditions for the unit that you attempted to copy or move, and then re-execute the command.

KAVS0639-E

Cannot copy the Unit (unit-name) - currently used by another user.

Another user is using the unit, preventing it from being copied.

(S)

Cancels command execution.

(O)

Wait for the other user to complete using the unit, and then re-execute the command.

KAVS0640-E

Cannot move the Unit (unit-name) - currently used by another user.

Another user is using the unit, preventing it from being moved.

(S)

Cancels command execution.

(O)

Wait for the other user to complete using the unit, and then re-execute the command.

KAVS0641-E

No authority to use output Unit (unit-name).

The output unit does not have any authority, preventing it from being defined. The probable causes are:

You do not have update permission for the output destination unit.

You do not have reference permission for units above the output destination unit.

(S)

Cancels command execution.

(O)

Re-execute the command as a user who has update permission for the output destination unit or who has reference permission for the upper-level unit of the output destination unit.

KAVS0647-E

A unit other than a jobnet in the planning-group cannot be moved.: unit-name

An attempt was made to move a unit other than the jobnet or the remote jobnet into the planning group.

(S)

Terminates processing. If you specify more than one unit, the system continues processing of the units of the jobnet or the remote jobnet.

(O)

Check whether the output destination is the planning group. Correct the unit name, and then re-execute the command.

KAVS0648-E

A unit other than a jobnet in the planning-group cannot be copied.: unit-name

An attempt was made to copy a unit other than the jobnet or the remote jobnet into the planning group.

(S)

Terminates processing. If you specify more than one unit, the system continues processing of the units of the jobnet or the remote jobnet.

(O)

Check whether the output destination is the planning group. Correct the unit name, and then re-execute the command.

KAVS0650-E

Invalid specification in the Unit definition parameter file (file-name). (sentence: sentence-number)

The unit definition parameter file contains an invalid specification. A cause may be one or more of the following:

The syntax of the unit definition parameter is invalid.

The length of the unit definition parameter exceeds the maximum value.

The unit definition parameter file contains the combination of parameters that cannot be specified simultaneously.

A parameter that must be specified together is missing.

The upper limit of the hierarchy was exceeded.

The maximum number of definition units was reached.

An attempt was made to create a job group, planning group, or manager unit in a jobnet.

An attempt was made to create a unit in a job, manager unit or start condition unit.

The root jobnet contains an invalid parameter.

An attempt was made to create more than 32 event jobs in the start condition.

An invalid combination of associated definitions was specified.

An attempt was made to create a unit other than an event job or a unit having the recovery attribute in the start condition.

A unit contained in the remote jobnet used a function not supported by the version of the manager where the jobnet is to be executed.

The custom job contains an invalid parameter.

In the execution sequence definition (ar parameter), the same unit name is specified for the preceding unit and the succeeding unit.

For a flexible job, mdf or exf (judgment by file) is specified for the jd parameter, and the jdf parameter (judgment file name) is omitted.

For a flexible job, an environment variable of 10,240 or more bytes is specified for the env parameter. If multiple env parameters are specified, the total length of the specified values is less than or equal to 10,240 bytes.

If 0 is output for sentence-number in the message, identify the unit that contains the error from the unit name indicated in file-name concurrently with the file name.

The statement indicated by sentence-number in the message might follow the statement containing the error. If the indicated statement number is correct, review the definition parameters in the unit containing the indicated sentence number to identify the location of the error.

(S)

Cancels command execution. If you specify more than one unit definition parameter file name, the system continues processing.

(O)

For a unit definition file, see 5.1 Creating a unit definition file in the manual JP1/Automatic Job Management System 3 Command Reference and correct the unit definition parameter file, and then re-execute the command.

KAVS0651-E

Cannot define - Unit (unit-name) is already registered.

The unit contains the registered jobnet, preventing a unit from being defined.

(S)

Cancels command execution. If you specify more than one unit definition file name, the system continues processing.

(O)

Unregister the unit, and then re-execute the command.

KAVS0652-E

Cannot define - Unit of the same name (unit-name) exists.

A unit with the same name already exists in the definition-destination, preventing it from being defined.

(S)

Cancels command execution. If you specify more than one unit definition file name, the system continues processing.

(O)

Change the unit name, and then re-execute the command.

This message might appear if you retry the operation after the ajsdefine, ajsrestore, ajsimport, or ajscopy command has terminated abnormally, or after an attempt to copy or restore a unit from JP1/AJS3 - View has terminated abnormally. In such cases, take the appropriate action for the operation you performed to recover:

If the ajsdefine command or ajsrestore command was executed:

Perform either of the following operations:

- Delete the unit you attempted to create, and then re-execute the command.

- Specify the -f option or -i option in the command.

If the ajsimport command was executed:

Perform either of the following operations:

- Delete the unit you attempted to create, and then re-execute the command.

- Specify the -f option in the command.

If the ajscopy command was executed or JP1/AJS3 - View was used to copy a unit:

Perform the following:

- Delete the unit at the copy destination, and then retry the copy.

If JP1/AJS3 - View was used to restore a unit:

Perform the following:

- Delete the unit you attempted to restore, and then retry the restoration.

KAVS0653-E

Cannot treat as definition Unit.: unit-name

unit-name cannot be the definition-destination unit. The possible causes are:

The unit specified as the definition-destination does not exist.

The type of the unit specified as the definition-destination is one of the following:

- Job

- Manager jobnet

- Manager job group

(S)

Cancels command execution.

(O)

Correctly specify the definition-destination unit, and then re-execute the command.

KAVS0654-E

Cannot use the unit (unit-name) - currently used by another user.

Another user is using the unit, preventing it from being defined.

(S)

Cancels command execution.

(O)

Wait for the other user to complete using the unit, and then re-execute the command.

KAVS0655-E

Not authorized to access the definition parameter file (file-name).

The unit definition file does not have any access permission.

(S)

Cancels command execution. If you specify more than one unit definition file name, the system continues processing.

(O)

Set the access permission for the unit definition file, and then re-execute the command.

KAVS0656-Q

Ok to update Unit (unit-name) ? (y:OK/n:NG)

This message checks whether you want to update the unit.

(S)

Waits for a response.

(O)

Enter y to update the unit.

Enter n not to update the unit.

KAVS0657-E

Cannot treat as a unit definition parameter file.: file-name

The file was specified in a format that the unit definition parameter file cannot use, preventing it from being analyzed.

(S)

Cancels command execution. If you specify more than one unit definition parameter file name, the system continues processing.

(O)

Specify the file in the format that the unit definition parameter file can use, and then re-execute the command.

KAVS0658-E

Cannot define Unit (unit-name).

It is impossible to define the unit because of the following reasons:

An attempt was made to define a job group in a jobnet.

An attempt was made to define a unit in a job.

An attempt was made to define the start condition (.CONDITION) in a unit other than the root jobnet.

The number of units that can be defined in a unit exceeded the limit (map-size).

The number of event jobs that can be defined in the start condition (.CONDITION) exceeded the limit (32).

The number of hierarchies exceeded the limit.

The length of the full name of the unit exceeded the limit (930 bytes).

After backing up a root jobnet for which a start condition (.CONDITION) was defined, recover the root jobnet as a nested jobnet.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVS0659-E

No authority to use definition unit (unit-name).

The definition unit does not have any authority, preventing it from being defined.

(S)

Cancels command execution.

(O)

Execute the command with the authority for the definition unit.

KAVS0660-E

Unit (unit-name) left over.

An error occurred while creating the units. An attempt to delete them was unsuccessful, and some of them could not be deleted.

(S)

Cancels command execution.

(O)

Use the ajsdelete command to delete the remaining units.

KAVS0661-E

Cannot define - Unit (unit-name) is running.

You cannot forcibly update the running unit.

(S)

Cancels command execution.

(O)

Wait for the unit to terminate execution, and then re-execute the command.

KAVS0665-E

A unit other than a jobnet in the planning-group cannot be defined.: unit-name

An attempt was made to define a unit other than a jobnet or remote jobnet into the planning group.

(S)

Terminates processing.

(O)

Check whether the definition destination is the planning group. Correct the unit name, and then re-execute the command.

KAVS0668-E

The value of the parameter specification range has an error.(unit-name parameter-name-1 parameter-name-2)

The value of the specifiable range of values for related parameters has an error.

The probable causes are:

If tho, rjs, or rje is output for parameter-name:

- The upper or lower limit of the return code for automatic retry is equal to or smaller than the abnormal end threshold.

- The lower limit of the return code for automatic retry is greater than the upper limit.

If ejl or ejh is output for parameter-name:

There is no integer value in the range of values for judging the return code.

If ejs or ejg is output for parameter-name:

There is no integer value in the range of values for judging the variable value.

(S)

Cancels command execution.

(O)

Correct the unit definition parameters, and then re-execute the command.

If tho, rjs, or rje is output for parameter-name, check the following:

tho parameter (abnormal end threshold)

rjs parameter (lower limit of the return code for automatic retry)

rje parameter (upper limit of the return code for automatic retry)

If ejl or ejh is output for parameter-name, check the following:

ejl parameter (minimum judgment return code)

ejh parameter (maximum judgment return code)

ejm parameter (minimum boundary condition)

eju parameter (maximum boundary condition)

If ejs or ejg is output for parameter-name, check the following:

ejs parameter (minimum judgment value for variable (numeric))

ejg parameter (maximum judgment value for variable (numeric))

ejm parameter (minimum boundary condition)

eju parameter (maximum boundary condition)

For details about the unit definition parameters, see 5.2 Definition format and parameters in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS0669-E

The parameter (parameter-name) which cannot be specified as a unit (unit-name) was specified.

A parameter that cannot be specified as a unit was specified.

(S)

Cancels command execution.

(O)

A parameter that can be specified only for a unit defined in a start condition might have been specified for a unit defined in an ordinary jobnet.

Correct the unit definition parameters, and then re-execute the command.

KAVS0670-E

Definition is invalid. (Jobnet: jobnet-name)

Schedule definition information about the jobnet contains errors. The possible causes are:

The specified job group does not exist in the calendar to be referenced.

The specified jobnet does not exist in the exclusive schedule.

(S)

Cancels the execution of the schedule control process.

(O)

Specify schedule definition information about the jobnet correctly.

For details on how to reference a calendar of other job groups and an explanation of exclusive schedules, see 3.3.2 Defining a schedule in the manual JP1/Automatic Job Management System 3 Overview.

KAVS0671-E

Error occurred in file (file-name).: return-code

The following errors occurred during creation of the definition information file in the host where the remote jobnet was executed.

The disk does not have any free space.

An I/O error occurred in the disk.

The file was deleted.

(S)

Abnormally terminates the remote jobnet.

(O)

Determine the cause of the error, and then re-execute the command.

KAVS0674-E

Parameter specifications are contradictory. (unit-name parameter-name-1 parameter-name-2)

The values of parameters set in the unit configuration definition are contradictory.

The probable causes are:

When end judgment for a job was to be performed in a range of condition values, the range to be used as the judgment condition was not specified.

When monitoring is set to monitor logs of a type other than the any-log-type (when parameters other than oth are set for the unit definition parameter ntlgt) for the Windows event-log monitoring job, a log type is specified for any-log-type as the monitoring condition.

When a log type was specified for any-log-type for the Windows event-log monitoring job, log type was not specified as the monitoring condition.

When automatic retrying of jobs that end abnormally was disabled, a parameter was specified that enables retrying.

(S)

Cancels command execution.

(O)

Correct the unit definition parameters, and then re-execute the command.

For details about the unit definition file, see 5.1 Creating a unit definition file in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS0681-E

Jobnet (jobnet-name) already registered.

The jobnet has already been registered.

(S)

Cancels command execution.

(O)

Specify another jobnet, and then re-execute the command.

KAVS0682-E

Registerable Jobnet number exceeds the limit.

The number of jobnets to be registered exceeded the limit.

(S)

Cancels command execution.

(O)

Unregister unnecessary jobnets, and then retry.

KAVS0683-E

Specified Jobnet (jobnet-name) cannot be registered.

The jobnet cannot be registered because of the following reasons:

The effective registration date expired.

The registration date exceeded the execution start date, but the process cycle or an alternate method is missing.

The execution start date is a holiday, but the process cycle is missing.

The next execution date is the year 2037 or later.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVS0684-E

Exclusion Jobnet definition of Jobnet (jobnet-name) is invalid.

A jobnet or local jobnet that is not in the same hierarchy was defined.

(S)

Terminates processing.

(O)

Define a jobnet other than the main jobnet in the same hierarchy, and then re-execute the command.

KAVS0685-E

Calendar definition of Jobnet (jobnet-name) is invalid.

The calendar definition contains invalid information.

(S)

Cancels command execution.

(O)

Correct the calendar information, and then re-execute the command.

For details about the format of the calendar definition, see ajscalendar in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS0686-E

None of the start definitions of the Jobnet (jobnet-name) are defined.

None of the start dates is defined.

(S)

Terminates processing.

(O)

Define the start dates, and then re-execute the command.

KAVS0694-E

Permission for the file (file-name) is lacking, so a jobnet-end wait is impossible.

The jobnet-end wait option (-w) cannot be used, since the jobnet-end wait file does not have update permission.

(S)

Cancels command processing.

(O)

The jobnet-end wait file is AJSNETWT.LCK in the directory storing the database. Give update permission to the file, and then reenter the command.

KAVS0695-E

The file (file-name) does not exist, so a jobnet-end wait is impossible.

The jobnet-end wait option (-w) cannot be used because of the following reasons.

The jobnet-end wait file cannot be allocated because the service has not started.

(S)

Cancels command processing.

(O)

Check whether the service has started.

If it has not started, start the JP1/AJS3 service and reenter the command.

KAVS0696-E

The jobnet-end wait count exceeded the limit, so the operation cannot be performed.

The maximum number of jobnet-end waits that can be executed concurrently was exceeded. The jobnet-end wait option (-w) cannot be used.

(S)

Cancels command processing.

(O)

If the ajsentry or ajsplan command was executed with the -w option specified, wait for the command processing to end, and then re-enter the command.

KAVS0697-E

The jobnet registration method is incorrect.: unit-name

A root jobnet in a planning group can only be registered for fixed execution by using the ajsentry command with the -p option or the -b and -e options specified.

(S)

Cancels command execution. If you specify more than one unit, the system continues processing of the units of the other jobnets.

(O)

Check the unit to register and the command option, correct the error, and then re-execute the command.

KAVS0698-E

A new generation of the jobnet (jobnet-name) could not be created because the number of jobnet generations has reached the system limit.

The system attempted to delete one generation of execution results so that the number of jobnet generations would not exceed the limit at the following times: when a jobnet is registered for fixed execution by specifying a period or date and when an execution a schedule is added in the temporary change of the schedule. The system, however, could not create a new generation because no generations were provided with the execution results.

(S)

Cancels processing.

(O)

The combined total of the number of logs to keep and the number of scheduled generations exceeds the limit.

To register a jobnet for fixed execution by specifying a date or to add an execution schedule in the temporary change of the schedule, re-execute the operation after one or more generations being executed end.

When registering jobnets for fixed execution by specifying a period, note that generations up to the combined total of the number of logs to keep and the number of scheduled generations have been registered.

For generations that exceed 8,000, re-execute the registration after the number of generations that have been executed enables more generations to be registered.

For details about the limits for units, see B.3 Limits for units in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVS0699-E

A new generation of the jobnet (jobnet-name) could not be created because the system failed to delete an execution result.

The system attempted to delete one generation of execution results so that the number of jobnet generations would not exceed the limit at the following times: when a jobnet is registered for fixed execution by specifying a period or date and when an execution a schedule is added in the temporary change of the schedule. The system, however, could not create a new generation because it failed to delete the execution result.

(S)

Cancels processing.

(O)

Take action according to the Windows event log or the syslog message output immediately before this error message.

KAVS0700-W

A unit was deleted during the command processing.

The specified unit no longer exists. It may have been deleted, or moved.

(S)

Cancels command execution. If you specify more than one unit (including specifications of regular expression), the system continues command execution.

(O)

Check whether the specified unit exists. Specify the unit, and then re-execute the command.

KAVS0701-E

A unit that is the target of the operation was not found.: unit-name

You executed a command on an active unit automatically selected from under a planning group, but no unit of the target generation could be found.

The probable causes are as follows:

There is no unit with the specified path name among the target units that have been automatically selected.

You do not have permission to reference the target units that have been automatically selected or the higher-level units of those units.

Use the following methods to execute commands on automatically selected units:

Execute the command with yes or auto specified for the -X option and specify the unit name with the root jobnet name omitted under the planning group.

Execute the command with YES or AUTO specified for the AJSAUTOJUDGE environment variable and specify the unit name with the root jobnet name omitted under the planning group.

Execute the command without the -X option or the AJSAUTOJUDGE environment variable specified, and specify the unit name with the root jobnet name omitted under the planning group.

(S)

Cancels command execution. If you specify more than one unit, the system continues processing of the units of the other jobnets.

(O)

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

KAVS0702-E

An execution generation that is the target of the operation was not found.: unit-name

When a unit under a jobnet registered for release is specified

The generation of the specified unit determined by automatic judgment or by registration number was not found.

For details about how to specify generations, see 4.5.13 Methods of specifying generations when executing commands in the manual JP1/Automatic Job Management System 3 Overview.

When a unit under a planning group is specified

You executed a command on an active unit automatically selected from under a planning group, but the target generation could not be found.

The probable causes are as follows:

When executing the ajsplan command, there is no unit to execute for the next time.

When executing the ajskill, ajsintrpt, ajschgstat, or ajsrerun command, there is no unit that has started execution.

The target generation was lost during command processing because of one of the following reasons:

1. The target generation was deleted because the number of logs to keep was specified.

2. The execution has stopped.

3. The target generation was unregistered.

Use the following methods to execute commands on automatically selected units:

Execute the command with yes or auto specified for the -X option and specify the unit name with the root jobnet name omitted under the planning group.

Execute the command with YES or AUTO specified for the AJSAUTOJUDGE environment variable and specify the unit name with the root jobnet name omitted under the planning group.

Execute the command without the -X option or the AJSAUTOJUDGE environment variable specified, and specify the unit name with the root jobnet name omitted under the planning group.

(S)

Cancels command execution. If you specify more than one unit, the system continues processing of the units of the other jobnets.

(O)

Check the status of the target unit, and then re-execute the command.

KAVS0710-E

There is no permission for the Unit ID (unit-ID).

You do not have permissions for the unit with the specified unit ID.

The probable causes are:

You do not have permissions for the unit with the specified unit ID.

You do not have reference permissions for units above the unit with the specified unit ID.

(S)

Cancels command execution. If you specify more than one unit ID, the system continues processing of another unit ID.

(O)

Execute the command as a user who has permissions for the unit with the unit ID.

KAVS0711-E

There is an error in the specified Unit ID (unit-ID).

The unit ID is specified incorrectly.

(S)

Cancels command execution. If you specify more than one unit ID, the system continues processing of another unit ID.

(O)

Correctly specify the unit ID, and then re-execute the command.

KAVS0712-E

The specified Unit ID (unit-ID) does not exist.

A unit with the specified unit ID does not exist.

(S)

Cancels command execution. If you specify more than one unit ID, the system continues processing of another unit ID.

(O)

Specify the unit ID of an existing unit, and then re-execute the command.

KAVS0715-I

The command or JP1/AJS2 - View operation started. (Operation name : command-name)

A JP1/AJS3 - View, JP1/AJS3 - Web Console, or command operation has started.

(S)

Continues processing.

KAVS0716-I

The command or JP1/AJS2 - View operation ended. (Operation name : command-name)

A JP1/AJS3 - View, JP1/AJS3 - Web Console, or command operation has terminated.

(S)

Continues processing.

KAVS0720-E

Specified execution start date is before current date.

The execution start date is earlier than the current date.

(S)

Cancels command execution.

(O)

Specify an execution start date later than the current date, and then re-execute the command.

KAVS0721-I

Specified Jobnet (jobnet-name) does not accept temporary change in plan.

The plan of the jobnet has not been temporarily changed.

(S)

Cancels command execution.

(O)

Specify another jobnet, and then re-execute the command.

KAVS0722-E

Specified Jobnet (jobnet-name) has already terminated.

The execution of the jobnet has terminated.

(S)

Cancels command execution.

(O)

Specify the jobnet being executed, and then re-execute the command.

KAVS0723-E

Specified Jobnet (jobnet-name) has already accepted temporary change in plan.

The plan of the jobnet has temporarily changed.

(S)

Cancels command execution.

(O)

Specify a jobnet whose plan has not been changed, and then execute the command.

KAVS0724-E

No further plan in specified Jobnet (jobnet-name).

There are no future plans for the jobnet. The plan of the jobnet cannot be temporarily changed or its suspend attribute cannot be changed.

(S)

Cancels command execution.

(O)

Specify a jobnet that has a future plan, and then re-execute the command.

KAVS0729-E

Cannot change plan temporarily - specified execution start date of Jobnet (jobnet-name) is different from that of higher Jobnet.

The execution start date of the jobnet differs from the next execution date of an upper-level jobnet. The plan could not be temporarily changed.

(S)

Cancels command execution.

(O)

Specify the same execution start date for the jobnet as that of the upper-level jobnet, and then re-execute the command.

KAVS0731-E

Options are needed.

No options are specified.

(S)

Cancels command execution.

(O)

Specify the required options, and then re-execute the command.

KAVS0732-E

Cannot temporarily change the plan on the specified start date.: unit-name

The start date and time is in the year 2037 or later. The plan cannot be temporarily changed.

(S)

Cancels command execution.

(O)

Specify the start date and time in the year 2036 or earlier, and then re-execute the command.

KAVS0740-E

Jobnet (jobnet-name) is already suspended.

An attempt was made to suspend the jobnet that was already suspended.

(S)

Cancels command execution.

(O)

As required, use the ajssuspend command with the -C option to release the jobnet from the suspended state, and then re-execute the ajssuspend command with the -S option.

KAVS0741-E

Jobnet (jobnet-name) is not suspended.

An attempt was made to release the suspended state on the jobnet that was no longer suspended.

(S)

Cancels command execution.

(O)

As required, use the ajssuspend command with the -S option to suspend the jobnet, and then re-execute the ajssuspend command with the -C option.

KAVS0742-E

Cannot use - Jobnet (jobnet-name) is now monitoring.

You cannot suspend the jobnet that is monitoring the start condition.

(S)

Cancels command execution.

(O)

Wait for the jobnet to terminate the monitoring of the start condition, and then re-execute the command.

KAVS0743-E

Cannot suspend - Jobnet (jobnet-name) is now running.

You cannot suspend the specified jobnet because it is being executed.

(S)

Cancels command execution.

(O)

Wait for the jobnet execution to terminate, and then re-execute the command. Alternatively, re-execute the command with the -n option specified.

KAVS0763-E

Cannot hold rerun - specified Jobnet (jobnet-name) already running.

The jobnet is being executed. It cannot be re-executed for suspending.

(S)

Cancels command execution.

(O)

Wait for the jobnet to complete the execution, and then re-execute the command.

KAVS0764-E

Specified Unit (unit-name) cannot rerun.

The unit cannot be re-executed. 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 judgment job or a dependent unit of a judgment job.

The upper-level jobnet of the job or the nested job that you attempted to rerun has no schedule.

(S)

Cancels command execution.

(O)

Make sure that the unit is in a status that allows re-execution, and then re-execute the command.

For details on re-execution, see 9.11 Re-executing jobnets and jobs in the JP1/Automatic Job Management System 3 Operator's Guide.

KAVS0771-E

Job (unit-name) condition verify error.

The status of the job does not match the condition. The probable causes are:

Although exit is specified in the -t option, the return code is not set.

The status of the unit differs from the status specified in the -v option.

The combination of statuses is indicated as impossible to change in Table 3-5 Possible combinations (for a job) or Table 3-6 Possible combinations (for a jobnet connector) in ajschgstat in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

(S)

Cancels command execution.

(O)

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

KAVS0780-E

Specified Jobnet (unit-name) has no information for display.

The jobnet does not contain any information to be displayed. There might be no information to output for the specified period, or the information might have been lost because the unit specified in the command was executed during command execution.

(S)

Cancels processing for the target unit. If you specify multiple units (including specifications of regular-expressions), the system continues processing from the next unit.

(O)

Take the following actions:

Specify another unit, and then re-execute the command.

Change the period, if any, specified in the command, and then re-execute the command.

If the unit specified in the command was executed during command execution, re-execute the command after making sure that the unit will not execute.

KAVS0781-E

Invalid formatting directives are specified.

Invalid format directives are specified.

(S)

Cancels command execution.

(O)

Correct the format directives, and then re-execute the command.

KAVS0783-E

Specified user does not exist.

User mapping in the target JP1/Base has failed for the user who registered the remote jobnet.

(S)

Abnormally terminates the remote jobnet.

(O)

Recheck the settings of the target JP1/Base, and specify a user defined in the user mapping. Then register the remote jobnet for execution.

KAVS0784-E

Cannot output the result information with the option "-g 0".

The -g 0 option was specified with the -l option. The -l option is the default option.

(S)

Cancels command execution.

(O)

Re-execute the command without specifying the -g 0 option with the -l option.

KAVS0785-E

Insufficient options specified.

The required option is missing.

(S)

Cancels command execution.

(O)

Specify the option, and then re-execute the command.

KAVS0787-E

Cannot execute - the system management daemon is busy.

The processing request by the following commands cannot be executed because the system management daemon is busy:

The command that starts the scheduler service

The command that stops the scheduler service

The command that starts the embedded database

The command that stops the embedded database

(S)

Terminates command execution.

(O)

Use the jajs_spmd_status command to make sure that the service has either started or stopped, and then re-execute the command.

KAVS0788-E

This option (option) cannot be used because "value" was specified for the value of the environment settings parameter "environment-setting-parameter-name".

The specified option cannot be used when the environment setting parameter is set to that particular value.

(S)

Terminates command execution.

(O)

If an unintended value is specified for the environment setting parameter, revise the value, and then retry the command.

If an incorrect option is specified for the command, specify the correct option, and then retry the command.

KAVS0800-E

Job (job-name) is not executing.

The job that was not being executed has been forcibly canceled.

(S)

Terminates command execution.

(O)

Specify the job being executed, and then re-execute the command.

KAVS0829-I

Reporting the effective information of JP1/AJS has started.

Output of the operating information for the JP1/AJS3 service has started.

(S)

Continues processing.

KAVS0830-I

Reporting the effective information of JP1/AJS has terminated.

Output of the operating information for the JP1/AJS3 service has terminated.

(S)

Terminates processing.

KAVS0831-I

Cannot get View connection information because the JP1/AJS2 service is not started.

JP1/AJS3 - View connection information cannot be obtained because the JP1/AJS3 service has not started.

(S)

Terminates processing.

(O)

Start the JP1/AJS3 service, and then re-execute the command.

KAVS0832-I

The View connection information output is complete.

Output of the JP1/AJS3 - View connection information has terminated.

(S)

Terminates command processing.

KAVS0849-I

Failed to put SNMP trap.: maintenance-information

The SNMP trap could not be issued. The probable causes are:

The SNMP service has not been installed.

A community name for SNMP trap authentication is not set.

An attempt to send an SNMP trap has failed.

(S)

Terminates processing.

(O)

Recheck the SNMP service settings, and then re-execute the command.

For details on the SNMP service settings, see A.2 Setup for linking HP NNM (for a Windows host) in the JP1/Automatic Job Management System 3 Linkage Guide or A.3 Setup for linking HP NNM (for a UNIX host) in the JP1/Automatic Job Management System 3 Linkage Guide.

KAVS0850-E

Specified backup box (backup-box-name) already exists.

The backup box has already been created.

(S)

Terminates processing.

(O)

Check the backup box name, and then re-execute the command.

KAVS0851-E

Specified backup box (backup-box-name) does not exist.

The backup box name does not exist.

(S)

Terminates processing.

(O)

Correct the backup box name, and then re-execute the command.

KAVS0852-E

Cannot use backup box (backup-box-name) - in use by other user.

Another user is using the backup box, preventing it from being processed.

(S)

Terminates processing.

(O)

Wait for the other user to complete using the backup box, and then retry.

KAVS0853-E

No authority to use backup box (backup-box-name).

The backup box does not have any authority.

(S)

Terminates processing.

(O)

Execute the process with the authority for the backup box.

KAVS0854-E

Specified backup file (backup-file-name) already exists.

The backup file has already been created.

(S)

Cancels command execution.

(O)

Check the backup box name, and then re-execute the command.

KAVS0855-E

Specified backup file (backup-file-name) does not exist.

The backup file does not exist.

(S)

Terminates processing.

(O)

Check the backup file name, and then retry.

KAVS0856-E

No authority to use backup file (backup-file-name).

The backup file does not have any authority.

(S)

Terminates processing.

(O)

Execute the processing with the authority for the backup file.

KAVS0857-E

Cannot treat as backup file.: backup-file-name

backup-file-name cannot be a backup file.

(S)

Cancels command execution. If you specify more than one backup file, the system continues processing.

(O)

Correct the backup file name, and then re-execute the command.

KAVS0858-E

Backup box name not specified.

A backup box name is missing.

(S)

Cancels command execution.

(O)

Specify the backup box name, and then re-execute the command.

KAVS0863-E

Interprocess communication failed.: maintenance-information-1 maintenance-information-2 maintenance-information-3

Interprocess communication failed due to one of the following:

The JP1/AJS3 service has not started.

The ajsinetd process at the connection destination has not started.

An error occurred during communication with the JP1/Base event service.

You can use the jajs_spmd_status command to check whether the ajsinetd process has started. For details on the jajs_spmd_statsu command, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

(S)

Terminates processing if the JP1/AJS3 service or the ajsinetd process at the connection destination has not started.

If an errot occurred during communication with the JP1/Base event service, the system follows the specification of the EVENTRETRY environment setting parameter to output subsequent events, and continues processing.

If you specified yes for the EVENTRETRY environment setting parameter, the system connects to the JP1/Base event service to output the next events.

If you omitted the EVENTRETRY environment setting parameter or specified no for this parameter, the system blocks the output of events until the JP1/AJS3 service restarts.

(O)

Examine the cause of the error, and then re-execute the command.

If the JP1/AJS3 service at the connection destination has not started, start the appropriate service.

If the ajsinetd process has not started, execute the jajs_hstd command to start the process. For details on the jajs_hstd command, see jajs_hstd in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

If the message "Failed to put Event." is displayed in maintenance-information-1 and you omitted the EVENTRETRY environment setting parameter or specified no for it, check the status of the JP1/Base event service, and then restart the JP1/AJS3 service.

KAVS0864-E

Connection was reset during interprocess communication.

Connection was reset during interprocess communication. The probable causes are as follows:

Connected by the host that is not registered IP address in the connection permission configuration file.

The scheduler service stops during a command execution to manipulate units.

The execution of a command to manipulate units stopped during remote execution of that command.

JP1/AJS3 - View was killed during an operation through JP1/AJS3 - View.

The host running JP1/AJS3 - View stopped during an operation through JP1/AJS3 - View.

A network failure occurred during connection with other hosts.

The setting does not allow for communication to pass through a firewall installed on a route to other hosts.

The communication encryption function setting is inconsistent between the connection source manager and the connection destination manager.

(S)

Terminates processing.

(O)

Check whether the host is permitted connection.

An operation through JP1/AJS3 - View might not have been completed, or a command execution might have been interrupted. To verify the completion of the operation performed when this message is displayed, check the command execution log output to the scheduler log file (log entry type: I001). If the operation is not completed, execute it again. When no operation log is output to the scheduler log file, a search or update operation might be performed through JP1/AJS3 - View. In this case, no action needs to be taken in JP1/AJS3 - Manager.

The communication encryption function might be disabled on the connection source manager and enabled on the connection destination manager. Make sure that the communication encryption function is set correctly, and then restart the JP1/Base service and JP1/AJS3 service.

Cautionary note

A command execution log (log entry type: I001) might not be output to the scheduler log file, depending on the settings of the environment setting parameters OPELOG, REFLOG, and INFOLOG.

KAVS0865-E

A timeout occurred during interprocess communication.

A timeout occurred during the requested processing.

The probable causes are:

A large jobnet was being executed.

Many JP1/AJS3 commands were being executed.

For a request to another host, that host has not started.

For a request to another host, the network has a problem.

(S)

Terminates processing.

(O)

If a large jobnet is being executed or if many JP1/AJS3 commands are being executed, wait until the relevant processing terminates, and then re-execute the operation. If a timeout occurred during a request to another host, enable communication with other hosts, and then re-execute the operation.

KAVS0866-E

Remote connection failed.: maintenance-information-1 maintenance-information-2

The connection destination host cannot be connected during remote connection due to a network error or routing error.

(S)

Terminates processing.

(O)

Examine the cause of the error, and then re-execute the command.

KAVS0867-E

Remote jobnet ended abnormally - error occurred.: return-code

An unrecoverable error occurred during execution of a remote jobnet.

(S)

Abnormally terminates the remote jobnet.

(O)

Take action according to the message that was output immediately before this message or as indicated in the Execution Result Details dialog box for the remote jobnet, and then retry. If no message was output, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVS0868-E

The user could not be authenticated at the specified host.: host-name maintenance-information

The user could not be authenticated at the specified host. Alternatively, a memory was insufficient during user mapping for the JP1 user name, preventing authentication using user mapping.

(S)

Terminates processing.

(O)

Correct the setting of the user information for the specified host, and then re-execute the command.

If maintenance-information indicates 12,0,0x00000002, correct the setting of JP1/Base user mapping.

If maintenance-information begins with 11,, make sure that the OS user password set in JP1/Base is correct and that the OS user account is not locked out.

If the settings are correct or if the error persists, memory may be insufficient.

Check the shared memory usage for the host indicated in host-name. In UNIX, recheck the memory setting in the kernel parameters.

For details about the kernel parameters, see Release Notes, and the explanation of kernel parameters in the JP1/Base User's Guide.

KAVS0869-E

Invalid data was received.: (IP-address) maintenance-information-1 maintenance-information-2

Invalid data was received from the connection source indicated in IP-address.The probable causes are:

The communication encryption function is enabled at the connection source and is disabled at the connection destination.

Invalid data was detected in the port (jp1ajs2monitor).

(S)

Stops communication.

(O)

Specify the same settings for the communication encryption function at both the connection source and the connection destination. If the communication encryption function is enabled at the connection destination, restart the JP1/Base service and JP1/AJS3 service.

The port (jp1ajs2monitor) may have been accessed incorrectly from the connection source indicated in IP-address. Examine the cause of the trouble.

KAVS0870-I

Saving unit (unit-name) to backup box (backup-box-name).

The backup command starts processing.

(S)

Continues processing.

KAVS0872-E

Unit (unit-name) already saved.

An attempt was made to back up the unit that has the same name as the unit that has already been backed up.

(S)

Cancels processing.

(O)

Check the backup file, delete the backup file as required, and then re-execute the command.

KAVS0873-E

Backup box (backup-box-name) is full.

The number of backup files in the backup box exceeded 1024.

(S)

Cancels processing.

(O)

Change the backup box or delete unnecessary backup files. Then, re-execute the command.

KAVS0874-Q

OK to update backup file (backup-file-name) ? (y:OK/n:NO)

This message checks whether you want to update the backup file.

(S)

Waits for a response.

(O)

Enter y to update the backup file.

Enter n not to update the backup file.

KAVS0875-Q

OK to clear backup box (backup-box-name) ? (y:OK/n:NO)

This message checks whether you want to delete the backup box.

(S)

Waits for a response.

(O)

Enter y to delete the backup box.

Enter n not to delete the backup box.

KAVS0876-Q

OK to clear backup file (backup-file-name) ? (y:OK/n:NO)

This message checks whether you want to delete the backup file.

(S)

Waits for a response.

(O)

Enter y to delete the backup file.

Enter n not to delete the backup file.

KAVS0877-E

A backup box could not be made.: maintenance-information-1 maintenance-information-2

A backup box could not be created because of the following causes.

The backup information directory does not have authorization.

The disk does not have sufficient free space for creating the backup box.

(S)

Terminates processing.

(O)

Remove the cause of the error, and then re-execute the command.

KAVS0880-I

Restoring unit (unit-name) to unit (unit-name).

The recovery command starts processing.

(S)

Continues processing.

KAVS0885-E

Restoration unit (unit-name) does not exist.

The restoration unit does not exist, preventing it from being restored.

(S)

Cancels unit restoration.

(O)

Create the restoration unit or correct the restoration unit. Then, re-execute the command.

KAVS0887-E

Cannot use restoration unit (unit-name) - in use by other user.

Another user is using the restoration unit, preventing it from being restored.

(S)

Cancels unit restoration.

(O)

Wait for the other user to complete using the restoration unit, and then re-execute the command.

KAVS0889-E

An error occurred in the process that starts the remote jobnet (service-name:jobnet-name:execution-ID). : maintenance-information

An error occurred during processing to transfer the definition of a remote jobnet to be registered for execution from the manager host where the jobnet was defined to the manager host where the jobnet is to be executed.

The probable causes are:

A communication error has occurred between the manager host where the jobnet is defined and the manager host on which the jobnet is to be executed.

A memory shortage (including a desktop heap that is too small in Windows) has occurred on the manager host where the jobnet is defined or on the manager host where the jobnet is to be executed.

The scheduler service has not started on the manager host where the jobnet is to be executed.

An error occurred in the user mapping for the manager host where the jobnet is to be executed or for the manager host where the jobnet is defined.

Communication to the manager host on which the jobnet is to be executed has been restricted because the connection source restriction function is enabled.

(S)

Places the remote jobnet in the Ended abnormally status on the manager host where the jobnet is defined.

(O)

Check the status of the manager host where the jobnet is defined and the manager host where the jobnet is to be executed, and then correct the cause of the error.

The jobnet might have been registered for execution on the manager host where the jobnet is to be executed. Check whether the jobnet has been executed, and then take one of the following actions as necessary.

When the jobnet has been executed on the manager host where it was to be executed:

Use a scheduler log to make sure that execution of the jobnet has ended. Then, on the manager host where the jobnet is defined, re-execute the operation according to the jobnet end status to recover the job.

When the jobnet has not been executed on the manager host where it was to be executed:

On the manager host where the jobnet is defined, re-execute the operation from the remote jobnet in the Ended abnormally status.

KAVS0890-E

An error occurred in the process that notifies the defined manager host of the start of the remote jobnet (service-name:jobnet-name:execution-ID). : maintenance-information

An error occurred when the manager host where the jobnet was to be executed notified the manager host where the jobnet was defined that the remote jobnet had started.

The probable causes are:

A communication error has occurred between the manager host where the jobnet is defined and the manager host on which the jobnet is to be executed.

A memory shortage (including a desktop heap that is too small in Windows) has occurred on the manager host where the jobnet is defined or on the manager host where the jobnet is to be executed.

The scheduler service has not started on the manager host where the jobnet is defined.

An error occurred in the user mapping for the manager host where the jobnet is defined.

Communication to the manager host on which the jobnet is to be executed has been restricted because the connection source restriction function is enabled.

(S)

Cancels the start notification processing, and continues remote jobnet execution.

(O)

Although the start notification is unsuccessful, it does not affect execution of the remote jobnet.

Note, however, that an end notification might fail for the same reason. Correct the cause of the error on the manager host where the jobnet is defined and the manager host where the jobnet is to be executed.

If the KAVS0891-E message is output for the target jobnet after this message, end notification has failed.

Recover the status of the remote jobnet according to the operator action provided in the KAVS0891-E message.

KAVS0891-E

An error occurred in the process that notifies the defined manager host of the end of the remote jobnet (service-name:jobnet-name:execution-ID). : (recovery-information-1 recovery-information-2 recovery-information-3 recovery-information-4 recovery-information-5 recovery-information-6) maintenance-information

An error occurred when the manager host on which the jobnet was to be executed notified the manager host where the jobnet was defined that the remote jobnet had ended.

The probable causes are:

A communication error has occurred between the manager host where the jobnet is defined and the manager host on which the jobnet is to be executed.

A memory shortage (including a desktop heap that is too small in Windows) has occurred on the manager host where the jobnet is defined or on the manager host where the jobnet is to be executed.

The scheduler service has not started on the manager host where the jobnet is defined.

An error occurred in the user mapping for the manager host where the jobnet is defined.

Communication to the manager host on which the jobnet is to be executed has been restricted because the connection source restriction function is enabled.

(S)

Cancels the end notification processing.

(O)

Correct the cause of the error on the manager host where the jobnet is defined and the manager host where the jobnet is to be executed.

If the status of the remote jobnet on the manager host where the jobnet is defined is Now running, perform the following recovery procedure to place the remote jobnet in the end status:

Make sure that the scheduler service has started on the manager host where the jobnet is defined.

On the manager host where the jobnet is defined, move to the work folder and execute the following command.

To execute this command, you must have logged on as a user who has administrator privileges (in Windows) or superuser privileges (in UNIX).

In Windows:

JP1/AJS3-installation-folder\tools\ajsremnetrcv.bat

recovery-information-1 recovery-information-2 recovery-information-3

recovery-information-4 recovery-information-5 recovery-information-6

> .\ajsremnetrcv.log

In UNIX:

/opt/jp1ajs2/tools/ajsremnetrcv

recovery-information-1 recovery-information-2 recovery-information-3

recovery-information-4 recovery-information-5 recovery-information-6

> ./ajsremnetrcv.log

Make sure that the remote jobnet is placed in the end status.

If the remote jobnet has not been placed in the end status, collect the following data and then contact the system administrator:

- An error message, if any, output by the ajsremnetrcv command

- ajsremnetrcv.log

Delete the ajsremnetrcv.log file.

Supplementary note

The ajsremnetrcv command is designed for emergency recovery, and cannot be used for any purpose except the recovery procedure described above. Accordingly, the description of this command is not included in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS0892-E

An error occurred in the process that deletes the definition of the remote jobnet (service-name:jobnet-name:execution-ID) transferred to the executing manager host. : (executing-manager-host-name job-group-name-on-the-executing-manager-host) maintenance-information

An error occurred during processing to delete the remote jobnet definition transferred to the manager host where the jobnet is to be executed.

The probable causes are:

A communication error has occurred between the manager host where the jobnet is defined and the manager host on which the jobnet is to be executed.

A memory shortage (including a desktop heap that is too small in Windows) has occurred on the manager host where the jobnet is defined or on the manager host where the jobnet is to be executed.

The scheduler service has not started on the manager host where the jobnet is to be executed.

An error occurred in the user mapping for the manager host where the jobnet is to be executed.

The remote jobnet has not been executed on the manager host where it is to be executed because, for example, the remote jobnet has no execution schedules or has been placed in Skipped so not exe. status.

Communication to the manager host on which the jobnet is to be executed has been restricted because the connection source restriction function is enabled.

(S)

Cancels the processing to delete the remote jobnet definition.

(O)

Correct the cause of the error on the manager host where the jobnet is defined and the manager host where the jobnet is to be executed. However, no action is required for the error message displayed when the remote jobnet has not been executed on the target manager host because the remote jobnet has no execution schedules or has been placed in Skipped so not exe. status.

After the cause of the error is corrected, unregistration or deletion of the jobnet might not have finished. Unregister the jobnet from the displayed job group on the manager host where the jobnet is to be executed. Then delete the job group.

If you delete a suspended remote jobnet, the jobnet name is indicated as a number. However, no operational problems occur because processing is performed normally on the manager host where the jobnet is defined. Unregister the jobnet and delete the job group as described above.

KAVS0893-E

An error occurred in the process that kills the remote jobnet (service-name:jobnet-name:execution-ID). : maintenance-information

An error occurred during processing to forcibly terminate the remote jobnet.

The probable causes are:

A communication error has occurred between the manager host where the jobnet is defined and the manager host on which the jobnet is to be executed.

A memory shortage (including a desktop heap that is too small in Windows) has occurred on the manager host where the jobnet is defined or on the manager host where the jobnet is to be executed.

The scheduler service has not started on the manager host where the jobnet is to be executed.

An error occurred in the user mapping for the manager host where the jobnet is to be executed.

The jobnet on the manager host where the jobnet is to be executed has already terminated.

Communication to the manager host on which the jobnet is to be executed has been restricted because the connection source restriction function is enabled.

(S)

Cancels the processing to forcibly terminate the remote jobnet.

(O)

Correct the cause of the error on the manager host where the jobnet is defined and the manager host where the jobnet is to be executed. Check the status of the applicable jobnet, and then forcibly terminate it if necessary.

If you cancel the registration or delete the definition after the forced termination, the jobnet name might be indicated as a number. However, there is no problem because the remote jobnet has ended on the manager host where it was to be executed.

KAVS0898-E

The suspend function is set up already.

The suspend function is already set up. Execution of the ajssetup -m command is unnecessary.

(S)

Terminates processing.

KAVS0900-W

Minor error occurred.: maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

An error that allows processing to continue occurred.

(S)

Continues processing.

(O)

If the maintenance information contains the character string SPMD communication error, check whether the jajs_spmd process is operating normally.

This error message might be output when a system error occurs and the jajs_spmd process terminates first. In such a case, there is no problem with the operation, despite the output of the message.

For any other case, follow the instructions given in the messages output before and after this one.

KAVS0901-E

I/O error occurred.: maintenance-information-1 maintenance-information-2 maintenance-information-3

An I/O error occurred during processing such as inputting into or outputting from a file.

(S)

Cancels the processing for the file where the error occurred, and continues the process. If the I/O error of the system file prevented processing, the system cancels the process.

(O)

If Permission denied is output for maintenance-information-1:

An attempt to read the file indicated by maintenance-information-3 failed.

Check and, if necessary, set appropriate permissions for the file and directory path. Make sure that the correct file is specified.

For any other case:

Take action according to the error information in the Windows event log or syslog output by the OS, and other OS-specific error information. If you cannot take corrective action, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS0902-E

Insufficient memory occurred.: maintenance-information-1 maintenance-information-2 maintenance-information-3

A memory shortage occurred. If the KFPA11912-E message is indicated in the maintenance information, the system load is excessive because either too many processes are running concurrently, or the value of pd_lck_pool_size for the embedded database is too small.

(S)

Cancels the processing during which insufficient memory was detected. If insufficient memory was detected during allocation of memory for a key component that could not continue processing, the system aborts the process.

(O)

Check the following settings:

In UNIX, see Release Notes, and make sure that the value of the kernel parameter for memory is greater than the estimated value.

Check the status of the process that was running when the error occurred to make sure that the amount of memory available is greater than the estimated value.

If the KFPA11912-E message is indicated in the maintenance information, specify yes for the UNITDEFDIVIDEUPDATE environment setting parameter to divide the data into several blocks that can then be written separately to the database. Alternatively, change the value of the pd_lck_pool_size for the embedded database.

For details on the UNITDEFDIVIDEUPDATE environment setting parameter, see 20.4.2(103) UNITDEFDIVIDEUPDATE in the JP1/Automatic Job Management System 3 Configuration Guide.

For details about pd_lck_pool_size, see the description of the single server definition in 23.1.1 Examining the embedded-database operating environment and operating method in the JP1/Automatic Job Management System 3 Configuration Guide.

If necessary, re-execute the processing for which memory was insufficient.

If the KFPA11912-E message was indicated in the maintenance information when you performed one of the following operations in an environment where yes was specified for the UNITDEFDIVIDEUPDATE environment setting parameter, take the appropriate action for the operation you performed:

(1) If the ajsdefine command or ajsrestore command was executed:

Perform either of the following operations:

- Delete the unit you attempted to create, and then re-execute the command.

- Specify the -f option or -i option in the command.

(2) If the ajsimport command was executed:

Perform either of the following operations:

- Delete the unit you attempted to create, and then re-execute the command.

- Specify the -f option in the command.

(3) If the ajscopy command was executed or JP1/AJS3 - View was used to copy a unit:

Perform the following:

- Delete the unit at the copy destination, and then retry the copy.

(4) If the ajsdelete command or ajssuspend command was executed:

Perform the following:

- Re-execute the command.

(5) If the ajsrelease command was executed or JP1/AJS3 - View was used to enter a job or jobnet for release:

Perform the following:

- Cancel the release, and then retry entering the job or jobnet for release.

(6) If JP1/AJS3 - View was used to restore a unit:

Perform the following:

- Delete the unit you attempted to restore, and then retry the restoration.

KAVS0903-E

System error occurred.: maintenance-information-1 maintenance-information-2 maintenance-information-3 system-error-message

A system error occurred during processing.

(S)

Terminates the process where the error occurred.

(O)

Take action according to the error information in the Windows event log or syslog output by the OS, and other OS-specific error information. If you cannot take corrective action, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS0904-E

Unexpected error occurred in JP1/AJS2.: maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

The probable causes are:

An unexpected error occurred during processing.

(S)

Terminates the processing where the error occurred.

(O)

Take action according to the message that was output before or after this error message. If you cannot take corrective action, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVS0905-E

Failed to output message (message-id).: maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

An attempt was made to output a message because an error occurred, but the message could not be output.

(S)

Cancels the process where the error occurred.

(O)

Take action according to the displayed message and the system error message.

KAVS0907-E

No more space in file (file-name).

There is no free space in the file system or the device to which writing the file was attempted.

(S)

Cancels the process where the error occurred.

(O)

Delete unnecessary files to make free space. Output the user file to another file system or device.

KAVS0909-E

Shared memory is not available.: maintenance-information-1 maintenance-information-2

Shared memory, which is one of the system resources, cannot be obtained, or required shared memory does not exist.

(S)

Terminates the process where the error occurred.

(O)

If the size of the system's shared memory is insufficient, increase the value in the kernel parameter. If the shared memory necessary for running the scheduler service has been deallocated, you need to restart the scheduler service.

KAVS0915-E

Resource lack occurred : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

A resource is insufficient. The insufficient resource is indicated in maintenance information.

(S)

Cancels processing.

(O)

Re-estimate the resources according to Release Notes.

KAVS0916-E

A system call (system-call-name) error occurred when starting process.:errno=value-acquired-by-errno

A system call error occurred while the AJS administrator was starting a process.

(S)

Terminates the process.

(O)

Use the data collection tool to collect data and contact the system administrator (see 1.2.3 To the system administrators).

KAVS0917-E

An attempt to acquire the information to be set for the JP1 event expansion attribute failed. : event-ID extension-attribute-name unit-name execution-ID maintenance-information

An attempt was made to acquire the information to be set for the JP1 event expansion attribute, but the attempt failed.

An empty character string is set as the comment information (the A6 attribute) for the JP1 event expansion attribute.

One of the following information items is displayed as the unit name:

unit-name

/unit-ID

If /unit-ID is displayed, you can check the full name of the unit by using the ajsname command. For details on the ajsname command, see ajsname in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

(S)

Issues a JP1 event and continues processing.

(O)

Check the current comment information on the relevant jobnet or job in the unit definition.

KAVS0920-W

Message process failed to initialize.(maintenance-information)

The message output could not be initialized.

(S)

The message is output without text. If HNTR_Initialize Failure is indicated in maintenance-information, the message is not output to the integrated trace log.

(O)

Check whether the resources are sufficient. Also check the running status of Hitachi Network Objectplaza Trace Monitor.

In UNIX, recheck 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)

For details about the kernel parameters, see Release Notes. Then, change the settings for the file system. 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).

KAVS0921-W

Connection to scheduler service has been reset.: maintenance-information

Interprocess communication for the scheduler service was disconnected due to termination of the connected process or other reasons.

(S)

Terminates processing.

(O)

This message may also be output when the scheduler service is terminated forcibly. Determine the cause of the error according to the message and from the contents of operations before and after the message is output, and then take action.

KAVS0930-E

Exclude error occurred.: maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

A lock error occurred.

(S)

Terminates processing.

(O)

The probable causes are as follows. Take action according to the cause of the error. If an error message was output before or after this message, also see the instructions given by that message.

Cause 1

During reorganization of ISAM files or when the ajsdbcond command with the -l option specified was executed, the ISAM files could not be locked because there were processes accessing the ISAM files.

Action

The scheduler service might be running or the unit might have been referenced or updated from JP1/AJS3 - View, a command that operates units, or a related product. Stop the scheduler service and make sure that the unit is not being referenced or updated. Then, retry the operation that resulted in the error.

For details about reorganizing ISAM files, see 9.3 Reorganizing a database when QUEUE jobs and submit jobs are used in the JP1/Automatic Job Management System 3 Administration Guide.

Cause 2

When the OS is AIX and the ISAM lock table split function is used, the ISAM lock table cannot be allocated.

Action

Stop all the related JP1 services, set ON for the EXTSHM environment variable, and then retry the operation that resulted in the error.

Cause 3

The status of the ISAM lock table has become invalid.

Action

Delete the ISAM lock table, and then retry the operation that resulted in the error.

Cause 4

JP1/AJS3 could not access the ISAM files because they were locked by another product such as backup software or anti-virus software.

Action

Make sure that no other products are accessing the ISAM files, and then retry the operation that resulted in the error.

Cause 5

A deadlock occurred when an embedded database was being used.

Action

The deadlock status is canceled automatically. If necessary, retry the operation that resulted in the error.

If an error message still appears after the above actions are taken, contact the system administrator and then collect data (see 1.2.3 To the system administrators).

KAVS0931-E

Condense failed.: maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

The database could not be reorganized.

(S)

Terminates processing.

(O)

Examine the cause of the error, and then reorganize the database of the scheduler service.

The probable causes are:

The disk does not have sufficient free space required for performing automatic reorganization.

The number of open files for a process or system reached the maximum.

Check the process running status of the machine and wait until the number of running processes is reduced. Then, re-execute the command.

Memory was insufficient.

If necessary, recheck and correct the values of the kernel parameters for memory.

For details on the kernel parameters, see Release Notes.

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

KAVS0932-E

Error occurred during database access.: maintenance-information-1 maintenance-information-2 maintenance-information-3

An error occurred while accessing the database.

(S)

Terminates processing.

(O)

The probable causes are as follows. Take action according to the cause of the error. If an error message was output before or after this message, also see the instructions given by that message.

Cause 1

Database files were corrupted due to a disk error, CPU error, or other hardware error.

Action

Reorganize the scheduler database or job execution environment database . If the reorganization does not correct the error, you must re-create the database.

For details about reorganizing ISAM files, see 9.3 Reorganizing a database when QUEUE jobs and submit jobs are used in the JP1/Automatic Job Management System 3 Administration Guide.

For details about re-creating ISAM files, see 2.11 Troubleshooting problems related to invalid ISAM files in the manual JP1/Automatic Job Management System 3 Troubleshooting.

Cause 2

Database files were corrupted because the primary node and secondary node in a cluster configuration accessed the database at the same time.

Action

Same as for Cause 1.

Cause 3

When an embedded database is used as the scheduler database, the embedded database has already stopped by the time the JP1/AJS3 service stopped.

Action

If the JP1/AJS3 service has stopped, there is no problem caused by this error. Do not stop the embedded database first.

Cause 4

When ISAM is used for the scheduler database in a cluster configuration, because sync was not specified for the ISAMWRITEMODE environment setting parameter for the scheduler service, the status of ISAM files becomes inconsistent during failover.

Action

Reorganize the scheduler database. If the reorganization does not correct the error, you must re-create the database.

Cause 5

Database files were corrupted because a disk operation was performed during JP1/AJS3 operation.

Action

Same as for Cause 1.

Cause 6

The file sizes that can be handled on the OS are restricted.

Action

Check the estimated file size in the kernel parameter, and set the appropriate value. For details about estimating the kernel parameters, see Release Notes.

Cause 7

The size of the ISAM file used for the scheduler database or job execution environment database reached 2 GB.

Action

Decrease the size of the ISAM file according to 9.3 Notes on the JP1/AJS3 database in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Cause 8

Database files were corrupted because the OS was stopped unexpectedly due to power interruption while JP1/AJS3 was running or for any other reason.

Action

Same as for Cause 1.

Cause 9

If an access from JP1/AJS3 - View causes an error, the OS user who is mapped to the JP1 user who logs in to JP1/AJS3 - View does not have update permission for the scheduler database.

Action

Check permission for accessing the scheduler database directory and scheduler database files, and set the access permissions appropriately.

Cause 10

If an embedded database is used for the scheduler database, the embedded database is not running.

Action

Start the embedded database, and then restart the scheduler service that is using the embedded database as the scheduler database.

Cause 11

When an unexpected failover occurs in a cluster configuration due to OS power failure or OS error, the status of ISAM files becomes inconsistent.

Action

Same as for Cause 1.

Cause 12

The embedded database was disconnected during operation of JP1/AJS3.

Action

If the KNAC1520-I message was output immediately after this message, there is no problem despite the reported error. If the ajsagtadd, ajsagtalt, or ajsagtdel command terminated abnormally, make sure that the embedded database is running, and then re-execute the command. If a job terminated abnormally when the agent automatic definition function was being used, make sure that the embedded database is running, and then re-execute the job.

KAVS0933-W

RDBUSER (user-name) has connect privilege.

The user specified in the RDBUSER environment setting parameter has sufficient privileges to connect to the database.

The user password may have been changed with the ajssetup command. If the password has been changed, user authentication may fail and the database cannot be accessed.

(S)

Since an existing user was found, the system resets the password as described below by manipulating the ajssetup command:

When the RDBPASSWORD environment setting parameter is specified, the password is reset to the value of RDBPASSWORD.

When the RDBPASSWORD environment setting parameter is not specified, the password is reset to a value scrambled from the RDBUSER environment setting parameter.

(O)

Check whether any problem occurred due to changes in the settings for the user connecting to the DBMS. For details on the environment setting parameters, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS0934-E

The specified tablespace or RDAREA does not exist.

The table area or RDAREA specified in the ajssetup command did not exist. The table could not be created.

(S)

Cancels command execution.

(O)

Specify the correct table area or RDAREA in the argument of the ajssetup command, and then retry.

KAVS0935-E

The specified tablespace or RDAREA is invalid.

The table area or RDAREA specified in the ajssetup command was invalid. The table could not be created.

(S)

Cancels command execution.

(O)

Specify the correct table area or RDAREA in the argument of the ajssetup command, and then retry.

KAVS0936-E

The schema is already defined.

The schema is already defined and cannot be created.

(S)

Cancels command execution.

(O)

The schema has already been defined, so you do not need to use the ajssetup command to set up the schema again. If you want to discard and re-create the existing schema, delete it on the DBMS and then re-execute the ajssetup command.

KAVS0940-E

Event Action Manager is busy.: maintenance-information maintenance-information maintenance-information maintenance-information

The event/action control manager is busy status. Events cannot be processed.

(S)

Cancels operations for event monitoring and start conditions.

(O)

Wait a while and then retry. If the retry does not correct the error, collect data and then contact the system administrator (see 1.2.3 To the system administrators).

KAVS0941-E

No event job in start condition.: jobnet-name

An attempt was made to start the execution of a jobnet whose icon was not registered in the start condition.

(S)

Cancels monitoring of the jobnet.

(O)

Define the event icon in the start condition or delete the start condition.

KAVS0942-W

Connection to job status notification process has been reset.

The status report process was disconnected because the status report process stopped during communication with the job-completion wait process.

(S)

Stops the scheduler service.

(O)

If the KAVU6101-I message is output before and after this message, this message is output at the end of the status report process and there is no problem. If the KAVU6101-I message is not output before and after this message, collect the internal trace log and then contact the system administrator.

KAVS0943-E

Cannot connect to job status notification process.: maintenance-information-1 maintenance-information-2 maintenance-information-3

The status report process could not be connected. The scheduler service cannot start.

(S)

Stops the scheduler service.

(O)

Use the messages that are output before and after this message to determine the cause of the unsuccessful connection, and then take action.

Also make sure that the port number for job status notification is set correctly in the services file. The default for the status notification port is 20245. Correct the cause of the error and then start the scheduler service.

KAVS0944-E

The error occurred during initialization processing of the job execution function(scheduler-service-name) : maintenance-information

An error occurred during initialization processing of job execution control.

(S)

Stops the scheduler service.

(O)

Use the system error messages that are output before and after this message to determine the cause of the error, and take corrective action. After correcting the error, restart the scheduler service. If you cannot determine the cause of the error from the messages, collect data and then contact the system administrator (see 1.2.3 To the system administrators).

KAVS0945-E

A scheduler daemon ended abnormally. (name: daemon-process-name, code: return-code, maintenance-information-1, maintenance-information-2)

The scheduler service(daemon) terminated abnormally.

(S)

Terminates the scheduler service.

(O)

Use the system error messages that are output before and after this message to determine the cause of the error. Then take action. If you cannot determine the cause of the error from the messages, collect data and then contact the system administrator (see 1.2.3 To the system administrators).

KAVS0946-E

The error occurred during scheduler service(scheduler-service-name) start processing. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

An error occurred during startup of the scheduler service.

(S)

Terminates the scheduler service.

(O)

If you specified the setting that automatically restarts the scheduler service when it terminated abnormally, the scheduler service is restarted automatically. When the scheduler service is restarted, the KAVS0946-E message appears again. If an attempt to start the scheduler service has failed, correct the cause of the error according to the instructions given by the message that was output immediately before this message. Then restart the scheduler service indicated in scheduler-service-name.

If a KAVS0903-E message was output immediately before this message, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS0947-E

The error occurred during initialization processing of the Event Action Manager(scheduler-service-name) : maintenance-information

An error occurred during initialization processing of the event/action control manager.

(S)

Stops the scheduler service.

(O)

Use the system error messages that are output before and after this message to determine the cause of the error, and take corrective action. After correcting the error, restart the scheduler service. If you cannot determine the cause of the error from the messages, collect data and then contact the system administrator (see 1.2.3 To the system administrators).

KAVS0950-E

An error (maintenance-information) occurred so the jobnet (root-jobnet-name) cannot be executed according to schedule.

An error occurred when the root jobnet is scheduled to wait for the start time. The jobnet is in the wait status but it cannot be executed. If this root jobnet exists under the planning group, all other root jobnets under the same planning group may not be started correctly.

(S)

The scheduler service stops processing of the root jobnet in which the error occurred. However, the service itself does not stop and continues other processing.

(O)

Unregister the root jobnet in which the error occurred, and then register it again. If the root jobnet exists under the planning group, unregister all the other root jobnets under the same planning group, and then register them again.

KAVS0965-E

Specification of the exclusion schedule specified in the jobnet(jobnet-name-2) inside the jobnet(jobnet-name-1) includes an error.

The definition of the exclusion schedule specified in the jobnet or nested jobnet contains an error.

(S)

Cancels allocation of the schedule for the jobnet.

(O)

Specify the correct jobnet name in the exclusive-schedule definitions, and allocate the schedule with temporary change specified. Alternatively, re-register the jobnet.

KAVS0966-E

Specification of the reference calendar specified in the jobnet(jobnet-name-2) inside the jobnet(jobnet-name-1) includes an error.

The definition of the reference calendar specified in the jobnet or nested jobnet contains an error.

(S)

Cancels allocation of the schedule for the jobnet.

(O)

Specify the correct job group name in the reference calendar definitions, and allocate the schedule with temporary change specified. Alternatively, re-register the jobnet.

KAVS0970-E

Failed in the execution resumption processing after releasing the Suspend setting.: maintenance-information

Recovery from the suspended to the active state failed (suspended state was released).

(S)

Continues processing.

(O)

Contact the system administrator, and collect data (see 1.2.3 To the system administrators). Correct the cause of the error, and then unregister the jobnet and register it again.

KAVS0971-E

The error occurred during suspension processing.: maintenance-information

An error occurred during suspension processing.

(S)

Cancels the requested processing.

(O)

Contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS0981-E

The table is not found.

The database table is not found.

(S)

Terminates processing.

(O)

Check the values of the TABLENAMEPREFIX and TABLENAMEPOSTFIX environment setting parameters.

If there are no tables, use the ajssetup command with the -t option specified to create the table.

KAVS0982-E

Could not connect to the database because the upper limit of a server setting was exceeded.

The limit defined in the database server was exceeded. The database could not be connected.

(S)

Terminates processing.

(O)

Stops other processes connected to the database, or re-set the limit of the database. Then, retry.

KAVS0983-E

Could not connect to the database because the username or password was invalid.

Connection was attempted using an invalid user name or password. The database could not be connected.

(S)

Terminates processing.

(O)

Set the correct user name and password, and then retry.

KAVS0984-E

Could not connect to the database because a required permission was lacking.

The user without permission for the database attempted connection. The database could not be connected.

(S)

Terminates processing.

(O)

Specify the user who has permission for the database, and then retry.

KAVS0985-E

Could not connect to the database.

The database could not be connected.

(S)

Terminates processing.

(O)

Check whether the database is running.

KAVS0986-E

Column size was exceeded because of character set conversion.

Because of character code conversion (for example, from Shift JIS to EUC), an attempt was made to write data longer than the column size.

(S)

Terminates processing.

(O)

Use the same character set for the database and JP1/AJS3 (specified by the AJSCHARCODE environment setting parameter).

For details about the database character set, see the documentation of the database. For details about how to check the character set used by JP1/AJS3 (such as the value of the AJSCHARCODE environment setting parameter), see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS0987-E

A permission required to operate the database is lacking.

You do not have permission to operate the database.

(S)

Terminates processing.

(O)

Specify a user who has appropriate permission, and then retry.

KAVS0988-E

Insufficient tablespace or RDAREA.

The table area or RDAREA does not have any free space.

(S)

Terminates processing.

(O)

Execute the ajsembdbreclaim command to allocate sufficient free space.

If you cannot allocate sufficient free space by executing the ajsembdbreclaim command, perform either of the following operations:

Reorganize the database.

Execute the ajsembdbaddarea command to expand the database area.

If this message appears even if the ajsembdbreclaim command is executed on a regular basis, the scale of the embedded database might be too small for operation. See 23.2 Estimating the database area in the JP1/Automatic Job Management System 3 Configuration Guide, and consider changing the scale of the embedded database.

For details about how to perform maintenance by executing the ajsembdbreclaim command and how to reorganize a database, see 9.2 Performing maintenance in the JP1/Automatic Job Management System 3 Administration Guide.

For details about expanding the database area, see ajsembdbaddarea in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS0989-E

The permission for ISAM files is insufficient.

The appropriate permission for ISAM files is insufficient.

(S)

Terminates processing.

(O)

Give appropriate permission for the ISAM files, and then retry.

KAVS0990-E

Failed to load libraries.

The library required for JP1/AJS3 could not be loaded.

(S)

Terminates processing.

(O)

Correct the environment setting and configuration definition for the linked programs, and re-execute the command.

If the library for linkage with the DBMS could not be loaded, the KAVS0932-E message containing the library name is output to the Windows event log or syslog. Make sure that the DBMS product is installed correctly and environment settings are correct.

For all the OS users using JP1/AJS3, also make sure that the following environment variables that indicate the library loading paths contain the library path for the DBMS product. These environment variables also required for starting the JP1/AJS3 services. When you are using JP1/AJS3 or the JP1/Base startup script, jajs_start, or jajs_start.cluster, also make sure that the environment variables are set up.

In Windows: PATH

In HP-UX: SHLIB_PATH

In Solaris, Linux: LD_LIBRARY_PATH

In AIX: LIBPATH

KAVS0991-E

Not supported on related programs (program-name).

program-name does not support the requested function.

If this error message appears when using the ajsdbcond command with the -L option specified, you need to install JP1/Base version 06-71 or later versions.

(S)

Cancels command processing.

(O)

Check the supported version of a prerequisite program, and upgrade the version of the program.

KAVS0992-E

There is no permission for object-name.: maintenance-information-1, maintenance-information-2, maintenance-information-3

You do not have permission to manipulate the object.

(S)

Terminates processing.

(O)

Obtain the right permission required to manipulate the object indicated in the message, and then re-execute the command.

KAVS0993-E

Invalid database backup file.

The possible causes are:

The name of the database backup file is specified incorrectly.

You attempted to move the database between different tables.

You attempted to move the database between different platforms.

The export process was not performed correctly.

(S)

Cancels command processing.

(O)

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

KAVS0994-E

Record existed in specified database table.

The database table at the import destination contains a record.

(S)

Cancels command processing.

(O)

Re-execute the command with the -c option specified. Executing the command with the -c option deletes all the records in the specified table and then imports the records in the specified database backup file. Once the records are deleted, they cannot be restored.

If you cannot confirm that the records in the table at the import destination are completely unnecessary, back up those records with the ajsdbexport command and then re-execute the import command.

KAVS0996-E

Error exist in option.

The specified option contains errors.

(S)

Cancels command processing.

(O)

Recheck the specified option value.

KAVS0997-E

The scheduler service failed to start.: maintenance-information-1 maintenance-information-2

The scheduler service could not be started with the jajs_spmd or ajsstart command.

(S)

Cancels command processing.

(O)

The cause of the failure to start the scheduler service has been output to the Windows event log or syslog. See the information stored in the above file, and take proper action.

KAVS0998-E

The system will wait because the database could not be connected. (Scheduler service : scheduler-service-name, Waittime : maximum-wait-time, Host : host-name)

The database could not be connected within the specified maximum wait time.

(S)

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

KAVS0999-W

The database could not be connected within the specified time. (Scheduler service : scheduler-service-name, 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 on how to do this, see the documentation for the appropriate database.

KAVS1002-E

AJS daemon ended abnormally. (name: daemon-process-name, code: return-code)

The scheduler service abnormally terminated.

(S)

Terminates processing.

(O)

Take action according to the message output before this message.

KAVS1003-E

Invalid specification in configuration definition. (item-name)

The environment setting parameters contains an invalid specification.

(S)

Terminates processing.

(O)

Specify the value indicated by item-name correctly, and then re-execute the command.

For details on the output item names, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide or20.9 Setting up the flexible-job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS1004-E

Scheduler service does not exist.

The scheduler service does not exist.

(S)

Terminates processing.

(O)

Specify the correct name of the AJS service to be processed, and then re-execute the command.

In addition, check the following:

The environment settings for the started JP1/AJS3 service (on a physical or logical host) contain scheduler service settings.

The scheduler service name specified in the environment settings for the started JP1/AJS3 service (on a physical or logical host) is the same as the name of a scheduler service in a different JP1/AJS3 service (on a physical or logical host).

KAVS1005-E

Cannot connect to Access Control Server.

The access control server could not be connected.

(S)

Terminates processing.

(O)

Check whether the authentication server name is correct, and whether the authentication server is running on the host of the specified authentication server.

Make sure that the authentication server is running and connected, and then re-execute the command.

KAVS1006-W

Change of Logical Host or Scheduler Service is incomplete.

Changes made in the logical host for the configuration definition or the scheduler service is not applied to the operation information.

(S)

Continues processing.

(O)

Take actions according to the following procedure.

Stop all the processes of the running JP1/AJS3 (including services and commands).

Make sure that the JP1/AJS2 services have stopped on all logical and physical hosts.

In Windows, in Control Panel or Administrative Tools, double-click Services, and make sure that the services have stopped. Then go to step 4.

In UNIX, use the jajs_spmd_status command to make sure that the JP1/AJS3 service has stopped. After making sure that the services have stopped, go to step 3.

Execute the ajsshmdel command.

Restart JP1/AJS3.

For details on the ajsshmdel command, see 15.1.1 Settings for starting multiple scheduler services in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS1007-E

Host name cannot be resolved. (logical-host-name)

The logical host name could not be resolved.

(S)

Cancels processing.

(O)

Check the settings of the JP1_HOSTNAME environment variable or the hosts file to resolve the logical host name, and then retry.

KAVS1008-E

An error exists in the certification server setting of the host (host-name). (login point IP address: IP-address)

The settings of the certification server contain an error on the host at the connection destination indicated in IP-address.

(S)

Terminates processing.

(O)

Recheck the settings of the certification server on the host at the connection destination, and correct the errors. In addition, check whether the IP address of the connection (login) destination matches that of the host that you attempted to connect to.

KAVS1009-W

The connection from host (IP address:IP-address, JP1 user name:JP1-user-name) to host (logical-host) was refused.

A connection which the user indicated in JP1-user-name being established from the host indicated in IP-address to the host indicated in logical-host was refused.

The probable causes are:

When JP1/AJS3 - View was connected, either the User mapping settings or the password management for JP1/Base was invalid.

After connecting with JP1/AJS3 - View, the authentication server was restarted, or was blocked.

When you started JP1/AJS3 - View from the Tool Launcher screen of JP1/IM - View, the user authentication bloc was different between JP1/IM - View and JP1/AJS3 - View.

During JP1/IM - View connection, JP1/AJS3 - View was started from the Tool Launcher screen of JP1/IM - View after the authentication server was restarted, or was blocked.

Also, this message is output if all is specified for the AUTHLOG or AUTHSYSLOG environment setting parameter.

(S)

Cancels the connection and waits for the next request.

(O)

Resolve the cause of the problem, follow the message displayed on the host indicated by IP-address, and then start JP1/AJS3 - View.

KAVS1010-I

The password was successfully changed for a user (JP1-user-name).

The password was successfully changed.

(S)

Continues processing.

KAVS1011-E

An attempt to change the password for a user (JP1-user-name) failed. Detailed information : maintenance-information-1, maintenance-information-2

An attempt to change the password failed.

The following information is indicated in the maintenance information:

maintenance-information-1: Return value of the command

maintenance-information-2: Error message of the command

(S)

Terminates processing.

(O)

If maintenance-information-1 is 1:

The probable causes are:

- The password is incorrect.

- The JP1 user was deleted.

- The JP1 user whose password was to be changed is a linkage user.

If maintenance-information-1 is 8:

The authentication server is not running or is not responding.

Check whether the authentication server is running.

If maintenance-information-1 is 24:

The probable causes are:

- The password length was invalid.

- An invalid character was specified for the password.

If maintenance-information-1 is a value other than the above:

If maintenance-information-2 is a JP1/Base error message, take action according to the instructions given by that error message. If nothing is indicated in maintenance-information-2, the command execution failed. Contact the system administrator, and collect data. For details, see 1.2.3 To the system administrators.

KAVS1012-E

A connection cannot be established because the limit on the number of possible concurrent sessions on the host (host-name) has been exceeded. : maximum-number-of-connections

A connection could not be established because the maximum number of concurrent sessions specified in the MAXSESSION environment setting parameter for the host indicated in host-name was exceeded.

If nothing is indicated in host-name, the physical host name was specified.

(S)

Terminates processing.

(O)

Check whether the estimated value of the MAXSESSION environment setting parameter is correct. If necessary, change the value. For details on the environment setting parameter, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

If the estimate is correct, wait until other connections have ended, and then try to establish the connection again.

KAVS1013-E

A connection cannot be established because the limit on the number of possible concurrent sessions on the Scheduler service (scheduler-service-name) has been exceeded. : maximum-number-of-connections

A connection could not be established because the maximum number of concurrent sessions specified in the SERVICEMAXSESSION environment setting parameter for the scheduler service indicated in scheduler-service-name was exceeded.

(S)

Terminates processing.

(O)

Check whether the estimated value of the SERVICEMAXSESSION environment setting parameter is correct. If necessary, change the value. For details on the environment setting parameter, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

If the estimate is correct, wait until other connections have ended, and then try to establish the connection again.

KAVS1014-W

The total of the limit on the number of possible concurrent sessions on the Scheduler service exceeded the limit on the number of possible concurrent sessions on a host.

The probable causes are:

The sum value of the SERVICEMAXSESSION environment setting parameters exceeds the value of the MAXSESSION environment setting parameter.

If the maximum number of concurrent sessions for all scheduler services (the total values of the SERVICEMAXSESSION parameters) exceeds the maximum number of concurrent sessions for a host (the MAXSESSION parameter), JP1/AJS3 - View might not be able to connect.

The SERVICEMAXSESSION environment setting parameter is not specified for some scheduler services.

If there are multiple scheduler services, the SERVICEMAXSESSION environment setting parameter must be specified for all the scheduler services.

(S)

Continues processing.

(O)

Check whether the estimated values of the MAXSESSION and SERVICEMAXSESSION environment setting parameters are correct. If necessary, change the values. For details on the environment setting parameter, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

If you changed the value of a MAXSESSION environment setting parameter, restart the scheduler service on the applicable host. If you changed the value of a SERVICEMAXSESSION environment setting parameter, restart the applicable scheduler service.

KAVS1015-I

The password change for a user (JP1-user-name) will now start.

The password change for the user will now start.

(S)

Continues processing.

KAVS1100-I

The command (command-name) ended normally.

The command terminated normally.

(S)

The command terminated normally.

KAVS1101-E

Illegal option (option) exists.

An invalid option is specified.

(S)

Cancels command execution.

(O)

Specify the correct option and then re-execute the command.

KAVS1102-E

Value for option (option) is not specified.

No value is specified for an option that requires a value.

(S)

Cancels command execution.

(O)

Specify the value for the option and then re-execute the command.

KAVS1103-E

The specified value (value) is already used with other logical hosts or another scheduler service.

The specified value is already used for another logical host or another scheduler service.

(S)

Cancels command execution.

(O)

Specify a unique value, and then re-execute the command.

KAVS1104-W

The specified directory or file (file-name or directory-name) does not exist.

The specified file or directory does not exist.

(S)

Continues the command processing.

(O)

After the command terminates, create the file or directory.

KAVS1105-E

There is an error in the value specified in an environmental parameter (parameter).

The probable causes are:

An invalid value is specified in the environment setting parameter.

The value specified in the environment setting parameter contains more than 1,024 bytes.

(S)

Cancels command execution.

(O)

Specify the correct value and then re-execute the command.

KAVS1106-E

Option (option) appears twice or more.

The same option is specified more than once.

(S)

Cancels command execution.

(O)

Specify the indicated option only once, and then re-execute the command.

KAVS1107-E

The specified definition key cannot be set.

The specified definition key cannot be set.

(S)

Cancels command execution.

(O)

Specify the correct definition key and then re-execute the command.

KAVS1108-E

An environmental parameter that cannot be set in the specified definition key has been specified.

An environment setting parameter that cannot be set in the specified definition key is specified.

(S)

Cancels command execution.

(O)

Specify the correct environment setting parameter and then re-execute the command.

KAVS1109-E

Insufficient options specified.

Required options are not specified.

(S)

Cancels command execution.

(O)

Specify the required options and then re-execute the command.

KAVS1110-E

Invalid value for option (option).

An invalid value is specified for the option.

(S)

Cancels command execution.

(O)

Specify the correct value for the option and then re-execute the command.

KAVS1111-E

This function cannot be used with the compatible ISAM configuration.

This function cannot be used with the compatible ISAM configuration.

(S)

Cancels command execution.

(O)

Use a function that can be used with the compatible ISAM configuration.

KAVS1112-E

The specified directory (directory-name) does not exist.

The specified directory does not exist.

(S)

Cancels command execution.

(O)

Specify the correct directory name and then re-execute the command.

KAVS1113-E

The specified logical host does not exist (host-name).

The specified logical host does not exist.

(S)

Cancels command execution.

(O)

Specify the correct host and then re-execute the command.

KAVS1114-E

The specified scheduler service does not exist (scheduler-service-name).

The specified scheduler service does not exist.

(S)

Cancels command execution.

(O)

Specify the correct scheduler service name, and then re-execute the command.

KAVS1115-E

Failed to create shared directory (directory-name).

An attempt to create a shared directory has failed.

(S)

Cancels command execution.

(O)

Make sure that the following jp1ajs2 directory indicated in the message does not already exist.

In Windows:

specified-shared-directory-name\JP1AJS2

In UNIX:

specified-shared-directory-name/jp1ajs2

If the jp1ajs2 directory exists, make sure that the specified shared directory name is correct. If it is correct, make sure that the jp1ajs2 directory is not needed, delete it, and then re-execute the command (do not delete a shared directory).

If the jp1ajs2 directory does not exist, check whether you have permission to update the specified shared directory.

KAVS1116-E

The specified logical host cannot be omitted.

The logical host specification cannot be omitted.

(S)

Cancels command execution.

(O)

Specify the logical host and then re-execute the command.

KAVS1117-E

The configuration definition of the logical host (host-name) does not exist.

The configuration definition of the logical host does not exist.

(S)

Cancels command execution.

(O)

Specify the correct logical host, and then re-execute the command.

KAVS1118-E

Scheduler service is active.

The scheduler service is running.

(S)

Cancels command execution.

(O)

Stop the scheduler service and then re-execute the command.

KAVS1119-Q

OK to rename Scheduler service from (scheduler-service-name) to (scheduler-service-name)? (Y: OK/N: NO)

This message confirms whether or not you want to continue to rename the scheduler service.

(S)

Waits for a response.

(O)

Enter y to continue processing to rename the scheduler service. Enter n to cancel the processing.

KAVS1120-Q

OK to delete Scheduler service (scheduler-service-name)? (Y: OK/N: NO)

This message confirms whether or not you want to continue to delete the scheduler service.

(S)

Cancels command execution.

(O)

Enter y to continue processing to delete the scheduler service. Enter n to cancel the processing.

KAVS1122-E

An attempt to read the pattern file (file-name) failed.

An attempt to read the pattern file used by the command failed, or an attempt to allocate memory while the file was being read failed.

(S)

Cancels command execution.

(O)

Check whether read or higher permission has been given for the file shown in the message. If the permission is not set, give read or higher permission for the file, and then re-execute the command.

For UNIX, see the Release Notes and make sure that the value of the kernel parameter for memory is greater than the estimated value.

If the file does not exist, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

The file shown in the message is stored in the following directory:

In Windows:

JP1/AJS3-installation-folder\conf

In UNIX:

/etc/opt/jp1ajs2/conf

KAVS1123-E

Failed to rename scheduler service.

An attempt to rename the scheduler service has failed.

(S)

Cancels command execution.

(O)

Check the status of the target scheduler service specified in the command. The most probable cause of the error is that the target scheduler service is running.

Take action according to the message that was output before or after this error message.

After correcting the error, re-execute the command.

KAVS1124-E

Failed to delete scheduler service.

An attempt to delete the scheduler service has failed.

(S)

Cancels command execution.

(O)

Check the status of the target scheduler service specified in the command. The probable causes are:

The target scheduler service is running.

The embedded database is not running.

Take action according to the message that was output before or after this error message.

After correcting the error, re-execute the command.

KAVS1126-E

An error occurred during scheduler service addition or deletion processing. (maintenance-information)

An attempt to set up or remove the embedded database by executing the command has failed.

(S)

Cancels command execution.

(O)

Correct the error according to the cautionary notes for the executed command, and then re-execute the command.

KAVS1127-E

An attempt to access the log file (file-name) failed.

An attempt to access the log file has failed.

(S)

Cancels command execution when the log file is being opened.

If this message appears during writing to the log file, the system continues command processing.

(O)

If this message appears when the log file is being opened, check whether write permission is given for the file shown in the message. If the permission is not set, give write permission for the file and then re-execute the command.

If this message appears during writing to the log file, the system continues command processing without writing log information into the log file. If this message appears, log information will not be written to the log file in subsequent processing until the command terminates.

The file shown in the message is stored in the following directory:

For Windows, if the installation folder is the default installation folder or is in a folder protected by the system:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log

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 Windows, if the installation folder is other than the above:

JP1/AJS3-installation-folder\log

In UNIX:

/var/opt/jp1ajs2/log

KAVS1130-E

An attempt to read the configuration definition information failed.

An attempt to obtain the configuration definition has failed.

(S)

Cancels command execution.

(O)

Contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS1131-E

Cannot use this option(option-name) with the compatible ISAM configuration.

This option cannot be used with the compatible ISAM configuration.

(S)

Cancels command execution.

(O)

Use an option that can be used with the compatible ISAM configuration.

KAVS1132-I

Processing was canceled.

Command processing was canceled.

(S)

Terminates command execution.

KAVS1133-W

An attempt to set scheduler service information (setting-name) has failed.

The scheduler service setting before the change could not be set in the scheduler service after the change.

(S)

Continues command processing.

(O)

After the command terminates, check the setting name indicated in the message, and specify either of the following for the new scheduler service:

If Local date and time is indicated in setting-name, use the ajslocaldate command to specify the AJS local date and time.

If Suspend feature is indicated in setting-name, use the ajssetup command to set up the suspend function.

If Disaster recovery is indicated in setting-name, the feature that automatically starts the scheduler service in disaster recovery mode when the JP1/AJS3 service starts will not work. Take the following actions:

- Configure the target scheduler service not to start automatically when the JP1/AJS3 service starts. For details, see the description of the AUTOSTART environment setting parameter in 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

- Start the JP1/AJS3 service.

- Start the target scheduler service in disaster recovery mode. For details about how to start individual scheduler services in disaster recovery mode, see ajsstart in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference and jajs_spmd in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

- Re-configure the target scheduler service to start automatically.

KAVS1134-E

Cannot be executed because the specified logical host (logical-host) contains the logical host setting of JP1/AJS3.

Setup cannot be executed because the logical host is already set up as a logical host in JP1/AJS3.

(S)

Cancels command execution.

(O)

Correct the error in the specified logical host name (the value of the JP1_HOSTNAME environment variable or the value specified in the -h option), and then execute the command again.

If your last attempt to execute the jajs_setup_cluster command failed, see the description of the action to be taken when an error occurs on the primary node in jajs_setup_cluster in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference, and after deleting the logical host information, execute the command again.

KAVS1135-E

The physical host cannot be specified.

Setup cannot be executed because a physical host (JP1_DEFAULT) is specified.

(S)

Cancels command execution.

(O)

Specify a logical host name (as the value of the JP1_HOSTNAME environment variable or in the -h option), and then re-execute the command.

KAVS1136-E

The value (value) specified for the option (option) overlaps with a set value of other logical hosts or another scheduler service.

The value specified for an option is the same as the value set for another logical host or service.

(S)

Cancels command execution.

(O)

Check for duplicate values and then re-execute the command.

KAVS1137-E

The scheduler service specified for the option (option) does not exist (scheduler-service-name).

The scheduler service specified in an option does not exist.

(S)

Cancels command execution.

(O)

Specify the correct scheduler service name and then re-execute the command.

KAVS1138-E

The directory (directory) specified for the option (option) does not exist.

The directory specified in an option does not exist.

(S)

Cancels command execution.

(O)

Specify the correct directory and then re-execute the command.

KAVS1139-E

A scheduler service cannot be added because the number of scheduler services has already reached the limit.

The system cannot add the scheduler service because the maximum number of scheduler services has already been reached.

(S)

Cancels command execution.

(O)

Re-execute the command after ensuring that the number of scheduler services is less than the maximum.

KAVS1140-E

A parameter that cannot be defined by the compatible ISAM configuration exists. (unit-name parameter-name)

The unit configuration definition contains a parameter that cannot be defined in the compatible ISAM configuration.

(S)

Cancels command execution.

(O)

In the unit configuration definition, only define parameters that conform to the compatible ISAM configuration.

KAVS1141-E

Too many parameters are specified. (unit-name parameter-name)

A repeatable parameter was specified more than the maximum number of times.

(S)

Cancels command execution.

(O)

Check the unit configuration definition, and make sure that no repeatable parameters are specified more times than permitted. In circumstances where an environment setting parameter determines how many times a parameter can be specified, also check the values of such environment setting parameters.

KAVS1142-E

The number of priority unit names for waiting information has exceeded the maximum that can be defined.

The number of preceding unit names in the waiting information exceeds the maximum you can define for one unit.

(S)

Cancels command execution.

(O)

Check the unit definition and the command line, and make sure that the number of preceding unit names in the waiting information does not exceed the maximum you can define.

KAVS1143-E

The waiting condition cannot be defined in the unit (unit-name).

A unit with wait conditions is defined under one of the following unit types:

Remote jobnet

Start condition

(S)

Cancels command execution.

(O)

Check the unit configuration definition and the wait condition settings.

KAVS1144-E

The specification of the wait condition is insufficient (unit-name).

No units whose ends are being waited for are specified for a unit with wait conditions.

(S)

Cancels command execution.

(O)

Check the unit configuration definition and the wait condition settings.

KAVS1145-E

A parameter value that cannot be defined by the compatible ISAM configuration exists. (unit-name parameter-name)

The unit configuration definition contains a parameter value that cannot be defined in a compatible ISAM configuration.

(S)

Cancels command execution.

(O)

Specify for the unit configuration definition a parameter value that can be used with a compatible ISAM configuration.

KAVS1146-E

The value specified as the option (option-name) cannot be used with the compatible ISAM configuration.

The value specified for the option cannot be used with a compatible ISAM configuration.

(S)

Cancels command execution.

(O)

Use a value for the option that can be used with a compatible ISAM configuration.

KAVS1147-E

This unit type cannot be defined in a compatible ISAM configuration. (unit-name, unit-type)

An attempt was made to define the following unit types, which cannot be defined in a compatible ISAM configuration:

HTTP Connection Job (including recovery HTTP connection jobs)

Flexible Job (including recovery flexible job)

(S)

Cancels processing.

(O)

Re-execute the command in the standard configuration.

To define the unit type in a compatible ISAM configuration, specify only the unit type that can be defined in a compatible ISAM configuration, and then re-execute the command.

KAVS1148-E

The specifications for the unit definition parameters are insufficient. (unit-name)

Required parameters are not specified for the following unit types:

HTTP Connection Job(including recovery HTTP connection jobs)

Flexible Job(including recovery flexible jobs)

(S)

Cancels processing.

(O)

Define the required parameters in the unit definition file, and then re-execute the command.

KAVS1200-E

The value of the option (option-name) exceeds the value specified for the environment setting parameter (parameter-name) of the scheduler service (scheduler-service-name).

The value specified in the option to the command is larger than the value specified in the environment-setting parameter of the scheduler service.

(S)

Cancels command execution. However, the system continues processing if two or more units (including specifications by regular expressions) are specified.

(O)

Specify the option value correctly, and then re-execute the command.

In addition, change the value of the environment setting parameter indicated in parameter-name, and then re-execute the command.

When the environment setting parameter indicated in parameter-name is "MAXSAVEGEN"

Check and, if necessary, change the value of the MAXSAVEGEN environment setting parameter. For details on the settings, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS1300-I

An attempt to obtain a host name failed.: maintenance-information-1, maintenance-information-2, maintenance-information-3

The host name could not be obtained.

(S)

Continues processing.

(O)

Check the execution target host (setting of the JP1_HOSTNAME environment variable, for example).

KAVS1301-I

An attempt to obtain the name of the directory for backup information failed.: maintenance-information-1, maintenance-information-2, maintenance-information-3

The directory name for output of the wait information file could not be obtained.

(S)

Continues processing.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the permission environment of the started user is correct.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVS1302-I

An attempt to obtain the name of the directory for installation of JP1/AJS2 failed.: maintenance-information-1, maintenance-information-2, maintenance-information-3

The JP1/AJS3 installation directory name could not be obtained.

(S)

Continues processing.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the permission environment of the started user is correct.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVS1400-E

The status of the jobnet (jobnet-name) whose start condition was being monitored could not be confirmed. (execution-ID)

The status of the jobnet of which the start condition is being monitored could not be confirmed.

(S)

The monitoring of the jobnet will now end.

(O)

Register the jobnet for execution again. If you use the cluster, check whether the directory name for output of the wait information file is set correctly.

This message also appears when you start the JP1/AJS3 service after executing the jpomanevreset command without the -e option. In this case, however, ignore the message because it is output as a result of terminating the monitoring of a start condition by resetting the event.

KAVS1401-E

A notice of a start in the maintenance mode from scheduler service to Event Action Manager failed.: maintenance-information

The scheduler service could not notify the event/action control manager of the activation of the maintenance mode. So events occurring in maintenance mode may not be detected.

(S)

Continues the maintenance mode activation process.

(O)

Deactivate maintenance mode immediately, determine the cause from the message output before this error message, and then remove the cause of the error. Then, re-execute the maintenance command.

KAVS1420-I

A jobnet with a preset start condition (name: jobnet-name: execution-ID) will wait for the termination of its monitoring status generation(execution-ID-of-the-monitoring-generation).

When the time that the jobnet with a start condition starts monitoring of the start condition is reached, the previous monitoring generation was still running. According to the setting of Concurrent exec. of monitoring gen., the jobnet waits in Wait for start time status until the monitoring generation terminates. After the monitoring generation has terminated, the waiting generation starts monitoring of the start condition.

(S)

Lets the jobnet in Wait for start time status wait for the monitoring generation to terminate. When the monitoring generation has terminated, the jobnet starts monitoring of the start condition.

(O)

Perform either of the following according to the needs of the operation.

To immediately start monitoring:

Kill the current monitoring generation.

To wait for the monitoring generation to terminate and start monitoring:

No action is required. Note, however, that if the timeout period expires while the jobnet is waiting for the monitoring jobnet to terminate, the jobnet will be placed into Skipped so not exe. status.

KAVS1500-I

Database condensing of the scheduler service (scheduler-service-name) started. start-date-and-time

The database reorganization of the scheduler service started.

(S)

Continues the database reorganization.

KAVS1501-I

Database condensing of the scheduler service (scheduler-service-name) ended normally. start-date-and-time - termination-date-and-time (required-time)

The database reorganization of the scheduler service has normally terminated.

(S)

Normally terminates the database reorganization.

KAVS1502-E

Database condensing of the scheduler service (scheduler-service-name) ended abnormally. start-date-and-time - termination-date-and-time (required-time)

The database reorganization of the scheduler service terminated abnormally.

(S)

Terminates the database reorganization.

(O)

Use the database reorganization log file and the Windows event log or syslog to examine the cause of the error, and then reorganize the ISAM database of the scheduler service.

KAVS1503-I

The ISAM unused area size of the scheduler service (scheduler-service-name) is size-in-megabytes.

The size of the unused area of the ISAM file of the scheduler service is output.

(S)

Outputs the size of the unused area of the ISAM file.

KAVS1504-W

The ISAM unused area size of the scheduler service (scheduler-service-name) is size-in-megabytes, which exceeds the size-in-megabytes threshold value.

The size of the unused area of the ISAM file of the scheduler service reached the specified size for that area.

(S)

Cancels command execution.

(O)

Reorganize the ISAM file of the scheduler service.

KAVS1510-I

CONDENSE: ISAM reorganization-statistics

The status of the ISAM file of the scheduler service which is being reorganized is output to the database reorganization log.

This message contains the following information:

The start date and time, termination date and time, and required time

The size of the unused area and the total file size of the ISAM file before and after the database reorganization

(S)

The status of the ISAM file is output to the ISAM reorganization log.

KAVS1512-E

The size of ISAM file exceeded the maximum size (2-Gigabyte).

The size of the files composing the ISAM table exceeded the upper limit (2 gigabytes) during database access.

(S)

Terminates processing.

(O)

The database cannot be accessed because the size of the ISAM files exceeded 2 gigabytes. Reduce the size of the ISAM files by unregistering or deleting units unnecessary for operation or by reducing the number of days for storing job information in the job execution environment.

KAVS1513-E

An error occurred during command processing.: maintenance-information

An error occurred when JP1/AJS3 and OS commands were executed in a script.

(S)

Check whether the script execution environment is correct. Set the environment correctly, and then re-execute the script.

(O)

Terminates processing.

KAVS1514-E

An attempt to read the configuration definition failed. (item-name : return-code)

An attempt to read the configuration definition has failed.

(S)

Assumes the default and continues processing.

(O)

If the system assumes an unexpected value, correct the cause of the error and then reissue the request. 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 when the error occurred. If the log indicating insufficient memory was output, recheck the memory estimate. If other unnecessary applications are running, stop them. If the cause of the error is not insufficient memory, collect the internal trace log and then contact the system administrator.

KAVS1515-E

Invalid specification in configuration definition. (item-name : return-code)

The configuration definition contains an invalid specification.

(S)

Assumes the default and continues processing.

(O)

Correctly specify the value indicated by item-name.

The output item names are described in 20. Environment Setting Parameters in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS1516-E

Construction is invalid.(maintenance-information)

The configuration is invalid. The probable causes are:

The installation or migration of JP1/AJS3 might not have finished.

The value of the DEFLENTYPE environment setting parameter is different from the value of DEFLENTYPE in shared memory.

The value of 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)

Specify the following configuration, and then re-execute the operation.

If JP1/AJS3 installation or migration is not yet finished:

Re-install JP1/AJS3, or confirm that JP1/AJS3 has been migrated correctly.

If the value of the DEFLENTYPE environment setting parameter is different from the value of DEFLENTYPE in shared memory:

Check whether the value of the DEFLENTYPE environment setting parameter matches the value of the currently operating DEFLENTYPE environment setting parameter returned by entering the jajs_status command. If the values do not match, take either of the following actions:

Restart the relevant scheduler service.

Stop the JP1/AJS3 services on all the configured hosts. In UNIX, stop the JP1/AJS3 services on all the configured hosts, and then execute the ajsshmdel command to delete the shared memory information.

The path to the ajsshmdel command is /opt/jp1ajs2/bin/ajsshmdel.

The following are examples of executing the command:

For sh:

/opt/jp1ajs2/bin/ajsshmdel >/dev/null 2>&1

For csh:

/opt/jp1ajs2/bin/ajsshmdel >&/dev/null

If the value of the DEFLENTYPE environment setting parameter does not match the format of the scheduler service database:

Check the value of 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.

KAVS1517-E

An error occurred during an attempt to acquire the configuration definition of the host (host-name). (service-name:item-name)

An attempt to obtain the environment setting parameter value for the host indicated in host-name has failed. The specified format for the value output to item-name might be incorrect.

If service-name appears, an attempt to obtain the environment setting parameter value for the scheduler service indicated in service-name on the host indicated in host-name has failed.

If nothing is indicated in host-name, the physical host name is assumed.

(S)

The JP1/AJS3 service terminates abnormally if this message is output during startup of the JP1/AJS3 service.

The scheduler service terminates abnormally if this message is output during startup of the scheduler service.

(O)

Check the integrated trace log to identify the service (process) that output this message.

If a command output this message, make sure that the correct logical host name and scheduler service name are specified for the arguments.

If a process other than a command output this message, set up the environment again for the host indicated in host-name and the scheduler service indicated in service-name, and then restart the JP1/AJS3 service.

If neither of the preceding conditions is met, check the specified format for the value output to item-name. For example, dword: might not be specified or might be specified incorrectly.

For details about the names of output items, see 20. Environment Setting Parameters in the JP1/Automatic Job Management System 3 Configuration Guide.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

To identify the name of the service (process) that output this message, check the AP name that is output to the integrated trace log concurrently with this message. For details about the output content of the integrated trace log file, see 1.2.1(2) Integrated trace log in the manual JP1/Automatic Job Management System 3 Troubleshooting.

KAVS1518-E

Invalid specification in configuration definition of the host (host-name). (service-name:item-name)

An invalid value is specified for the environment setting parameter for the host indicated in host-name.

If service-name appears, an invalid value is specified for the environment setting parameter for the scheduler service indicated in service-name on the host indicated in host-name.

If nothing is indicated in host-name, the physical host name is assumed.

(S)

The JP1/AJS3 service terminates abnormally if this message appears during startup of the JP1/AJS3 service.

The scheduler service terminates abnormally if this message appears during startup of the scheduler service.

(O)

Set the value indicated in item-name correctly.

For details about output item names, see 20. Environment Setting Parameters in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS1570-I

Adapter command (maintenance-information) started.

The adapter command started.

The following information is shown in maintenance-information.

maintenance-information: The adapter command name and the specified option value

(S)

The adapter command started.

KAVS1571-I

Adapter command (maintenance-information-1) ended. (maintenance-information-2)

The adapter command ended.

The following information is shown in maintenance-information.

maintenance-information-1: The adapter command name

maintenance-information-2: The return value of the adapter command

(S)

The adapter command started.

KAVS1572-W

Adapter command (maintenance-information) canceled.

The adapter command was canceled.

The following information is shown in maintenance-information.

maintenance-information: Adapter command name

(S)

The adapter command was canceled.

KAVS1600-E

The specified unit name is invalid.

The status could not be acquired because of one of the following reasons after you specified the unit name.

The unit does not exist.

You have no permission for the unit.

The unit exists under the manager job group, manager jobnet, or the root jobnet. The status of the unit is unavailable.

This message is output to the Information text area in the Detail Information - [object-type] dialog box.

(S)

Stops acquiring the status of the unit.

(O)

Specify the name of the unit whose status is available and for which you have permission.

KAVS1601-E

Requests to the specified unit could not be processed.

The request is not supported for the unit. The status could not be acquired.

This message is output to the Information text area in the Detail Information - [object-type] dialog box.

(S)

Stops acquiring the status of the unit.

(O)

Specify the name of the unit whose status is available.

KAVS1602-E

Maintenance is being performed, so status obtainment is not possible.

The status could not be obtained because database maintenance was in progress.

This message is output to the Information text area in the Detail Information - [object-type] dialog box.

(S)

Terminates the status acquisition processing for the specified unit.

(O)

Wait until maintenance finishes, and then re-execute the operation.

KAVS1703-E

The command executed during reorganization of the scheduler service (scheduler-service-name) database ended abnormally.: Jischk -l3 table-name : return code = return-code-from-Jischk (Please look at maintenance--log-file-name)

While maintenance was being performed by the jajs_maintain command, invalid data was detected by the Jischk command, which verifies consistency between ISAM files. For details of the error message output by Jischk, see the maintenance log file.

(S)

Cancels command execution. If there are any tables in the service still being processed, the system continues command execution.

(O)

Collect data and then contact the system administrator.

KAVS1704-E

The command executed during reorganization of the scheduler service (scheduler-service-name) database ended abnormally.: Jisext table-name table-name.back: return code = return-code-from-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 any tables in the service still being processed, the system continues command execution.

(O)

Execute the command as a superuser or an administrator. 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.

KAVS1705-E

The command executed during reorganization of the scheduler service (scheduler-service-name) database ended abnormally.: Jisconv -t SI-table-name.back table-name_NEW: return code = return-code-from-Jisconv

While maintenance was being performed with the jajs_maintain command, an error occurred for the Jisconv command, which re-creates ISAM files from extracted data.

(S)

Cancels command execution. If there are any tables in the service still being processed, the system continues command execution.

(O)

Execute the command as a superuser or an administrator. Check whether the disk has sufficient free space, and re-execute the command. If you cannot determine the cause of the error, collect data and then contact the system administrator.

KAVS1706-E

An attempt to create a backup directory during reorganization of the scheduler service (scheduler-service-name) database failed. (directory-name): return code = return-code

While maintenance was being performed with the jajs_maintain command, the working directory could not be created.

(S)

Cancels command execution. If there are other services being processed, the system continues command execution.

(O)

Check whether you have the permission to write into the directory for the temporary file for the scheduler service or the disk has sufficient free space.

KAVS1707-E

An attempt to copy files for backing up and recovering ISAM files during reorganization of the scheduler service (scheduler-service-name) database failed. (table-name): return code = return-code

While maintenance was being performed with the jajs_maintain command, the file to back up and recover ISAM files could not be copied.

(S)

Cancels command execution. If there are any tables in the service still being processed, the system continues command execution.

(O)

Check whether the disk has sufficient free space, and then re-execute the command.

KAVS1709-E

An attempt to rename files for recovering ISAM files during reorganization of the scheduler service (scheduler-service-name) database failed. (table-name): return code = return-code

While maintenance was being performed with the jajs_maintain command, the file to recover ISAM files could not be renamed.

(S)

Cancels command execution. If there are any tables in the service still being processed, the system continues command execution.

(O)

Check whether you have the permission to write into the directory for the database of the scheduler service.

KAVS1713-E

An attempt to start the scheduler service (scheduler-service-name) failed.: maintenance-information

While the jajs_maintain command was performing maintenance, the scheduler service could not be started.

The probable causes are:

More than one jajs_maintain command was executed at the same time for the scheduler service.

The scheduler service was started during execution of the jajs_maintain command.

(S)

Cancels command execution. If, however, any other services remain unexecuted, the system continues command execution.

(O)

Wait until the jajs_maintain command terminates. Then manually start the scheduler service that could not be started. If an error message was output before or after this message, also see the instructions given by that message.

KAVS1714-E

An attempt to start the script for reorganizing the scheduler service (scheduler-service-name) table (table-name) failed.: maintenance-information

While the jajs_maintain command was performing maintenance, the script to reorganize tables could not be started.

(S)

Cancels command execution. If, however, any other service has not been processed, the system continues command execution.

(O)

Memory may have become insufficient, or the number of started processes may have reached the limit to the number of processes that the system can start.

In UNIX, check and correct the settings of the kernel parameters for memory and processes.

For details about how to estimate kernel parameters and the size of memory used, see Release Notes.

Check the status of the process that was running when the error occurred to make sure that the amount of memory available is greater than the estimated value.

If you cannot determine the cause, collect data and then contact the system administrator (see 1.2.3 To the system administrators).

KAVS1715-E

The script for reorganizing the scheduler service (scheduler-service-name) table (table-name) failed.: maintenance-information

While the jajs_maintain command was performing maintenance, the script to reorganize tables ended abnormally because of an unexpected error.

(S)

Cancels command execution. If, however, the running service has unprocessed tables, the system continues command execution.

(O)

Execute Jischk -l3 table-name to check whether a problem exists with the table whose reorganization ended abnormally. For details about Jischk, see the JP1/Base User's Guide. After collecting the result of Jischk, contact the system administrator (see 1.2.3 To the system administrators).

KAVS1716-E

An attempt to prepare for reorganization of the scheduler service (scheduler-service-name) database failed.: maintenance-information

While the jajs_maintain command was performing maintenance, the system could not make preparations for reorganizing tables.

(S)

Cancels command execution. If, however, any other services remain unexecuted, the system continues command execution.

(O)

Memory may be insufficient. Alternatively, the number of processes started on the system may have reached the maximum.

In UNIX, check and correct the settings of the kernel parameters for memory and processes.

For details about how to estimate kernel parameters and the size of memory used, see Release Notes.

Check the status of the process that was running when the error occurred. Then make sure that the amount of memory available is greater than the estimated value.

If you cannot determine the cause, collect data and then contact the system administrator (see 1.2.3 To the system administrators).

KAVS1717-E

Maintenance is being performed, so execution is impossible. (maintenance-information)

Since maintenance is in progress, the specified command cannot be executed.

(S)

Cancels command execution.

(O)

Wait until maintenance ends, and then re-execute the command.

KAVS1718-E

The scheduler service (scheduler-service-name) database connection exists, so shifting to the maintenance mode is impossible.

The system could not enter maintenance mode because a process other than services connected to the database.

(S)

Cancels command execution.

(O)

Log off from programs such as JP1/AJS3 - View or JP1/AJS3 Console to make sure that there are no processes accessing the database.

KAVS1719-I

The maintenance processing of the scheduler service ended normally.

The maintenance of the scheduler service ended normally.

(S)

Performs a normal termination of the maintenance of the scheduler service.

KAVS1720-E

The maintenance processing of the scheduler service ended abnormally.: maintenance-information

The maintenance of the scheduler service ended abnormally. The probable causes are:

The disk does not have sufficient free space.

If parallel execution is enabled, sufficient free space is required on the disk of the system.

The number of open files for a process or system reached the maximum.

Check the process running status of the machine and wait until the number of running processes is reduced. Then, re-execute the command.

Memory was insufficient.

In UNIX, recheck the settings of the kernel parameters for memory.

For details on the kernel parameters, see Release Notes.

(S)

Performs an abnormal termination of the maintenance of the scheduler service.

(O)

See the maintenance log file and the Windows event log or syslog to determine the cause of the abnormal termination of the maintenance process according to the output error message, and then take the corrective action. Then re-execute the maintenance process.

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

KAVS1721-I

The jajs_maintain command started.(maintenance-information)

The jajs_maintain command started.

(S)

Starts the jajs_maintain command.

KAVS1722-I

jajs_maintain command ended normally.

The jajs_maintain command ended normally.

(S)

Performs a normal termination of the jajs_maintain command.

KAVS1723-E

jajs_maintain command ended abnormally.

The jajs_maintain command ended abnormally.

(S)

Terminates the jajs_maintain command.

(O)

Check the following items to determine the cause of the abnormal termination of the maintenance process. Then, re-execute the maintenance process.

When -show is specified

The status could not be acquired probably because the operation of the job execution environment was starting or stopping. Wait for a while and then re-execute the command.

When -r start is specified

The job execution environment or scheduler service that you attempted to recover may have been maintained. Check the status of the job execution environment or scheduler service you must recover, and then re-execute the command.

When -m manager or -m scheduler is specified

Take action according to the message that is output to standard error at the same time as this message, and then re-execute the command.

When the job execution environment has been reorganized by using the jpqautocond script

The job execution environment might have been maintained while the JP1/AJS3 service was active. Make sure that the JP1/AJS3 service is stopped, and then re-execute the command as needed.

KAVS1724-E

The scheduler service control file does not exist.

A file necessary for executing the command has not been created.

(S)

Cancels command execution.

(O)

Take the following actions:

Check whether the specified scheduler service name contains errors.

Check whether the specified scheduler service has been set up. If the specified scheduler service has not been set up yet, set it up by executing the ajssetup command.

If this message was output after you upgraded the version, start the JP1/AJS3 service. Starting the JP1/AJS3 service creates control files for all the scheduler services on the physical or logical object host.

If a cluster system is used, you must start the JP1/AJS3 service once when a failover occurs for the first time.

KAVS1725-E

An error occurred in the processing accompanying the reconfiguration of the job execution environment.: maintenance-information-1 (maintenance-information-2)

An error occurred in processing involved in the reorganization of the job execution environment.

(S)

Continues processing.

(O)

The system may have failed to reorganize the job execution environment. Correct the cause of the error according to the instructions given by the messages beginning with KAVU corresponding to one of the following messages indicated in maintenance-information-1, and then re-execute the maintenance command. For details about messages beginning with KAVU, see 5. Messages beginning with KAVU (Messages about the job execution control).

An attempt to acquire the database information failed.

See KAVU0500-E.

Memory became insufficient.

See KAVU0922-E.

A logical contradiction occurred.

See KAVU0923-E.

The manager cannot be connected.

See KAVU0945-E.

The IP address could not be acquired from the manager host name.

See KAVU0946-E.

Starting or stopping is being processed.

See KAVU0950-E.

No response from the manager.

See KAVU0953-E.

The command could not be executed because of internal factor at the manager.

See KAVU0954-E.

Memory became insufficient at the manager.

See KAVU0966-E.

A fatal error occurred in the manager.

See KAVU0968-E or KAVU4335-E.

A logical contradiction occurred in the manager.

See KAVU0969-E.

That request is not supported by the requested manager.

See KAVU0970-E.

The execution environment is invalid.

See KAVU0972-E.

KAVS1726-I

The scheduler service (scheduler-service-name) was shifted to maintenance mode.

The scheduler service was put into maintenance mode.

(S)

Continues processing.

KAVS1727-I

The scheduler service (scheduler-service-name) was stopped.

The scheduler service was stopped.

(S)

Continues processing.

KAVS1728-I

The scheduler service (scheduler-service-name) has already stopped.

(S)

Continues processing.

KAVS1729-I

The start request of the scheduler service (scheduler-service-name) was executed.

A request to start the scheduler service was made.

(S)

Continues processing.

KAVS1730-I

The maintenance mode of the scheduler service (scheduler-service-name) was canceled.

Maintenance mode was canceled for the scheduler service.

(S)

Continues processing.

KAVS1731-E

Back up scheduler database (unit information only).

The system started the backup process only for the unit definition table of the scheduler service.

(S)

Continues processing.

KAVS1732-E

Succeeded in backup of a scheduler service ISAM file.

The system backed up the ISAM files for the scheduler service successfully.

(S)

Continues processing.

KAVS1733-E

Backup directory (backup-directory-name).

The system displays the backup directory name.

(S)

Continues processing.

KAVS1734-E

-F option is not specified.

The -F option is missing.

(S)

Cancels command execution.

(O)

Specify scheduler-service-name in the -F option, and then re-execute the command.

KAVS1735-E

Need to rerun this command.

You need to re-execute this command.

(S)

Cancels command execution.

(O)

See the message output together with this message, and then take proper action.

KAVS1736-E

Backup failed. Command ended abnormally.: ajsgtroot -F service-name option : return code = return-value-from-ajsgtroot-command

The ajsgtroot command could not be executed.

(S)

Cancels command execution.

(O)

Check whether configuration definition information about the specified scheduler service is defined correctly.

KAVS1737-E

Database type of (scheduler-service-name) is not ISAM.

The type of the database that the specified scheduler service is to manipulate is not ISAM.

(S)

Cancels command execution.

(O)

Specify the name of a scheduler service that can manipulate a database of the ISAM type, and then re-execute the command.

KAVS1738-E

Specified name is not directory (directory-name).

The value specified as the database directory name for the specified scheduler service is not a directory. Alternatively, the value specified as the recovery source directory is not a directory.

(S)

Cancels command execution.

(O)

Check whether configuration definition information is defined correctly.

KAVS1739-E

Backup failed. Failed to make directory (directory-name).: return code = return-value-from-mkdir

Since the backup directory could not be created, the ISAM files for the scheduler service could not be backed up.

(S)

Cancels command execution.

(O)

If you specified the -b option, check whether the parent directory of the specified directory has write permission and is a directory. If you did not specify the -b option, check whether the directory of the scheduler service backup destination has write permission and is a directory.

KAVS1740-E

Cannot access backup directory (directory-name).

You cannot access the backup directory.

(S)

Cancels command execution.

(O)

If you specified the -b option, check whether the specified directory has write permission.

KAVS1741-E

Backup failed. Failed to copy (file-name).: return code = return-value-from-cp

Since the file could not be copied, the ISAM files for the scheduler service could not be backed up.

(S)

Cancels command execution.

(O)

Check whether the backup directory has write permission. If you want to make a backup in the backup directory by overwriting data, check whether the files you have write permission for stored in the backup directory.

Check also whether the disk has free space.

Take actions according to the error message of the cp command output together with this message.

KAVS1742-E

Backup failed. Failed to compare (file-name).: return code = return-value-from-cmp

Since the system could not compare files, it could not back up the ISAM files for the scheduler service.

(S)

Cancels command execution.

(O)

The system could not compare the files at the backup source and the backup destination. The database for the scheduler service may have been updated. Take actions according to the error message of the cmp command output together with this message.

KAVS1751-E

Restoring scheduler database (unit information only).

The system restores the unit definition table for the scheduler service.

(S)

Continues processing.

KAVS1752-E

Succeeded in restoring of a scheduler service ISAM file.

The system recovered the unit definition table for the scheduler service successfully.

(S)

Continues processing.

KAVS1753-E

Restore failed. Command ended abnormally.: ajsgtroot -F service-name option : return code = return-value-from-ajsgtroot-command

Since the system could not execute the ajsgtroot command, restoration failed.

(S)

Cancels command execution.

(O)

Check whether configuration definition information about the specified scheduler service is defined correctly.

KAVS1754-E

Cannot access database directory (directory-name).

You cannot access the database directory.

(S)

Cancels command execution.

(O)

If you have specified the -b option, check whether the specified directory has write permission.

KAVS1755-E

A file (file-name) is not found.

The file is not found.

(S)

Cancels command execution.

(O)

The unit definition table for the scheduler service is not stored in the directory specified as the recovery source directory.

KAVS1756-E

Failed to delete ISAM file (file-name).: return code = return-value-from-rm

The system could not delete the ISAM file.

(S)

Cancels command execution.

(O)

Take actions according to the error message of the rm command output together with this message.

KAVS1757-E

Restore failed. Failed to copy (file-name).: return code = return-value-from-cp

The ISAM file could not be copied.

(S)

Cancels command execution.

(O)

Check whether the database directory has write permission.

Check also whether the disk has free space.

Take action according to the error message of the cp command output together with this message.

KAVS1758-E

Restore failed. Failed to compare (file-name) : return code = return-value-from-cmp

The ISAM file could not be copied.

(S)

Cancels command execution.

(O)

Check whether the disk has free space. Take action according to the error message of the cmp command output together with this message.

KAVS1759-E

Restore failed. Command ended abnormally.: command-name option : return code = return-value-from-command

The system could not execute the command, so restoration failed.

(S)

Cancels command execution.

(O)

Check whether the command shown in command-name can be executed in the current environment, and take action according to the error message output together with this message.

KAVS1770-I

The adapter command setup has started.

Adapter command setup has started.

(S)

Continues processing.

KAVS1771-I

The adapter command setup completed normally.

Adapter command setup ended normally.

(S)

Continues processing.

KAVS1772-I

The adapter command unsetup has started.

Adapter command unsetup has started.

(S)

Continues processing.

KAVS1773-I

The adapter command unsetup completed normally.

Adapter command unsetup ended normally.

(S)

Continues processing.

KAVS1774-E

The logon account does not have permission to setup.

Since you do not have permission to execute the command, you cannot execute it.

(S)

Cancels command execution.

(O)

Re-execute the command as a user with permission to execute it.

KAVS1775-E

The argument arguments is incorrect.

The command argument is invalid.

(S)

Cancels command execution.

(O)

Check the command arguments, and then re-execute the command.

KAVS1776-E

There are too many command arguments.

Too many arguments are specified in the command.

(S)

Cancels command execution.

(O)

Check the command arguments, and then re-execute the command.

KAVS1777-E

Setup and unsetup cannot be specified simultaneously.

You cannot perform setup and unsetup at the same time.

(S)

Cancels command execution.

(O)

Check the command arguments, and then re-execute the command.

KAVS1778-E

A duplicated command argument cannot be specified.

You cannot specify a command argument more than once.

(S)

Cancels command execution.

(O)

Check the command arguments, and then re-execute the command.

KAVS1779-E

JP1/Base is not installed, so the adapter command setup failed.

Since a JP1/Base product has not been installed, the system could not set up the adapter command.

(S)

Cancels command execution.

(O)

Check whether related products have been installed.

KAVS1780-E

The JP1/Base installation location is unobtainable.

The system could not obtain the JP1/Base installation location.

(S)

Cancels command execution.

(O)

Check whether the related products have been installed.

KAVS1781-E

The adapter-command adapter command does not exist.

The adapter command does not exist.

(S)

Cancels command execution.

(O)

Check whether the adapter command exists.

KAVS1782-E

The adapter command configuration file storage directory does not exist.

The directory containing the adapter command configuration file does not exist.

(S)

Cancels command execution.

(O)

Check whether the directory containing the adapter command configuration file exists.

KAVS1783-E

An attempt to delete the configuration-file adapter command configuration file failed.

The system could not delete the adapter command configuration file.

(S)

Cancels command execution.

(O)

Check whether the adapter command configuration file exists and what its access permission is.

KAVS1784-E

An attempt to setup an adapter command failed.

The system could not set up the adapter command.

(S)

Cancels command execution.

(O)

Remove the causes of all errors for which messages were output, and then execute the command again.

KAVS1785-W

The adapter-command-configuration-file adapter command configuration file does not exist.

The adapter command configuration file for linking with JP1/IM could not be deleted by the ajs_adapter_setup command. Possible causes are as follows:

The adapter command configuration file for linking with JP1/IM does not exist.

The adapter command configuration file for linking with JP1/IM has already been deleted.

(S)

Command processing will now continue by assuming that the adapter command configuration file for linking with JP1/IM has been deleted.

(O)

No action is required.

KAVS1786-E

An unexpected error occurred.

An unexpected error occurred.

(S)

Cancels command execution.

(O)

Contact the system administrator.

KAVS1790-E

An error occurred in the processing which acquires the process state of job execution environment. : maintenance-information

An error occurred during the processing for acquiring the operating status of the job execution environment.

(S)

Cancels command execution.

However, if the -shown option is specified in the jajs_maintain command, the system continues processing.

(O)

Correct the cause of the error according to the instructions given by the messages beginning with KAVU corresponding to one of the following messages indicated in maintenance-information, and then re-execute the maintenance command. For details about messages beginning with KAVU, see 5. Messages beginning with KAVU (Messages about the job execution control).

An attempt to acquire the database information failed.

See KAVU0500-E.

Memory became insufficient.

See KAVU0922-E.

A logical contradiction occurred.

See KAVU0923-E.

The manager cannot be connected.

See KAVU0945-E.

The IP address could not be acquired from the manager host name.

See KAVU0946-E.

Starting or stopping is being processed.

See KAVU0950-E.

No response from the manager.

See KAVU0953-E.

The command could not be executed because of internal factor at the manager.

See KAVU0954-E.

Memory became insufficient at the manager.

See KAVU0966-E.

A fatal error occurred in the manager.

See KAVU0968-E or KAVU4335-E.

A logical contradiction occurred in the manager.

See KAVU0969-E.

That request is not supported by the requested manager.

See KAVU0970-E.

The execution environment is incorrect.

See KAVU0972-E.

KAVS1791-E

An error occurred in the processing which usually requires operation of job execution environment. :maintenance-information

An error occurred in the processing for a request made to the job execution environment for performing normal operation.

(S)

Cancels command execution.

(O)

Correct the cause of the error according to the instructions given by the messages beginning with KAVU corresponding to one of the following messages indicated in maintenance-information, and then re-execute the maintenance command. For details about messages beginning with KAVU, see 5. Messages beginning with KAVU (Messages about the job execution control).

An attempt to acquire the database information failed.

See KAVU0500-E.

Memory became insufficient.

See KAVU0922-E.

A logical contradiction occurred.

See KAVU0923-E.

The manager cannot be connected.

See KAVU0945-E.

The IP address could not be acquired from the manager host name.

See KAVU0946-E.

Starting or stopping is being processed.

See KAVU0950-E.

No response from the manager.

See KAVU0953-E.

The command could not be executed because of internal factor at the manager.

See KAVU0954-E.

Memory became insufficient at the manager.

See KAVU0966-E.

A fatal error occurred in the manager.

See KAVU0968-E or KAVU4335-E.

A logical contradiction occurred in the manager.

See KAVU0969-E.

That request is not supported by the requested manager.

See KAVU0970-E.

The execution environment is invalid.

See KAVU0972-E.

KAVS1801-I

The queueless agent will now start.

The queueless agent service starts.

(S)

The queueless agent service starts.

KAVS1802-I

The queueless agent will now stop.

The queueless agent service ends.

(S)

Terminates the queueless agent service.

KAVS1803-E

The queueless agent abnormally ended.

The queueless agent service ended abnormally.

(S)

The queueless agent service ended abnormally.

(O)

Take action according to the instructions given by the message that was output immediately before this message.

KAVS1804-I

The queueless agent will now terminate.

The queueless agent service accepted a request for forced termination of the ajsqlstop command.

(S)

Terminates the queueless agent service.

KAVS1805-E

The port (port-name) cannot be used because another user is already using the port.

The service that output this message cannot start because the port indicated in port-name is being used.

(S)

Terminates the service that output this message.

(O)

Take either of the following actions, and then restart the service that output this message :

Use the netstat command or another means to identify the process that is using the port indicated in port-name, and stop that process. To stop the process, use Task Manager in Windows and use the kill command in UNIX.

Edit the services file to change the port number used by the service that output this message.

To identify the name of the service that output this message, check the AP name that is output to the integrated trace log concurrently with this message.

For details about the output content of the integrated trace log file, see 1.2.1(2) Integrated trace log in the manual JP1/Automatic Job Management System 3 Troubleshooting.

KAVS1806-I

The user mapping cache was cleared. : process-name

The user-mapping cache indicated in process-name was cleared. The next Queueless job will be performed without using the user mapping cache.

(S)

Cleared the user-mapping cache indicated in process-name.

KAVS1807-E

The maximum number of waiting jobs has been reached, so the job (job-name) cannot be accepted.

The system cannot accept the job indicated in job-name because both the maximum number of concurrently executable jobs and the maximum number of waiting jobs have been reached.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Use JP1/AJS3 - View to make sure that the number of queueless jobs waiting for execution for the queueless agent service has not reached the maximum number of waiting jobs. Make sure that the number of waiting queueless jobs is within the maximum, and re-execute the queueless job indicated in job-name that caused an error.

The current setting of the maximum number of concurrently executable jobs and the maximum number of waiting jobs might not suit the current operation. Review the values and then change them if necessary.

The maximum number of concurrently executable jobs is set in the AJSQL_JOBMAX environment setting parameter, and the maximum number of waiting jobs is set in the AJSQL_JOBWAITMAX environment setting parameter. For details, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS1808-E

The maximum number of waiting jobs in the class (class-name) has been reached, so the job (job-name) cannot be accepted.

The queueless job indicated in job-name cannot be accepted because both the maximum number of concurrently executable jobs and the maximum number of waiting jobs for the class indicated in class-name have been reached.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Use JP1/AJS3 - View to make sure that the number of queueless jobs waiting for execution for the queueless agent service's class indicated in class-name has not reached the maximum number of waiting jobs. Make sure that the number of waiting queueless jobs is within the maximum, and re-execute the queueless job indicated in job-name that caused an error.

The current setting of the maximum number of concurrently executable jobs and the maximum number of waiting jobs for the class indicated in class-name might not suit the current operation. Review the values and then change them if necessary.

For the class, the maximum number of concurrently executable jobs is set in the AJSQL_CJOBMAX environment setting parameter, and the maximum number of waiting jobs is set in the AJSQL_CJOBWAITMAX environment setting parameter. For details, see 6.4.1 Executing jobs with a class specified in a queueless job environment in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows) or 15.4.1 Executing jobs with a class specified in a queueless job environment in the JP1/Automatic Job Management System 3 Configuration Guide (for UNIX).

KAVS1809-E

The request is to an unattached host (host-name), so the job (job-name) cannot be accepted.

The queueless job indicated in job-name could not be accepted because the job execution request was issued to the unattached host indicated in host-name.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Execute the ajsqlattach command to attach the host indicated in host-name, and then re-execute the queueless job indicated in job-name that resulted in the error.

Example: In this example, the command attaches the logical host Lhost.

Execute the ajsqlattach command as follows:

ajsqlattach -h Lhost

For details on the ajsqlattach command, see ajsqlattach in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1810-E

The specified class (class-name) does not exist, so the job (job-name) cannot be accepted.

The queueless job indicated in job-name cannot be accepted because the class indicated in class-name does not exist.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Take the following actions:

Check whether the correct host name and class name are specified for Execution agent. Correct the invalid host name or class name, and then re-execute the queueless job indicated in job-name that resulted in the error.

Execute the ajsqlstatus command to make sure that the class indicated in class-name is on the host specified for Execution agent.

Example: In this example, the command outputs detailed information for the logical host Lhost.

Execute the ajsqlstatus command as follows:

ajsqlstatus -h Lhost

For details on the ajsqlstatus command, see ajsqlstatus in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

If the class indicated in class-name does not exist, create the class and then re-execute the queueless job indicated in job-name that resulted in the error. For details about how to create a class, see 6.4.1 Executing jobs with a class specified in a queueless job environment in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows) or 15.4.1 Executing jobs with a class specified in a queueless job environment in the JP1/Automatic Job Management System 3 Configuration Guide (for UNIX).

KAVS1811-E

Memory is insufficient, so the job (job-name) cannot be accepted.

The queueless job indicated in job-name cannot be accepted due to insufficient memory.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Check the amount of memory available by using Task Manager in Windows or the top command or another means in UNIX.

Wait until the memory necessary for job execution can be allocated, and then re-execute the queueless job indicated in job-name that resulted in the error.

KAVS1812-E

The configuration definition of the logical host (logical-host-name) does not exist.

The environment of the logical host indicated in logical-host-name is not set up.

(S)

Continues processing if the error occurred during startup of a queueless agent service. However, the logical host is not handled as the host where the job is executed.

The system cancels processing if the error occurred during execution of a command.

(O)

Set up the environment for the logical host indicated in logical-host-name, and then restart the queueless agent service. If the error occurred during execution of a command, make sure that the correct logical host name is specified in the argument.

KAVS1813-E

An error occurred during an attempt to acquire the configuration definition of the logical host (logical-host-name). (function=maintenance-information-1, code=maintenance-information-2)

An attempt to acquire the environment setting parameter value for the logical host indicated in logical-host-name failed.

(S)

If a queueless agent service output this message during startup, the system terminates the queueless agent service abnormally. If this message is output during processing to attach the logical host, the system cancels the attach processing.

If a command related to queueless job execution control output this message, the system cancels command execution.

If the queueless cluster process output this message during startup, the system cancels processing to attach the logical host and continues startup.

(O)

Check the integrated trace log to identify the service (process) that output this message.

If the queueless agent service output this message, set up the environment again for the physical host and the logical host indicated in logical-host-name, and then restart the queueless agent service.

If a command related to queueless job execution output this message, make sure that the correct logical host name is specified in the argument.

If a queueless cluster process output this message, set up the environment again for the logical host indicated in logical-host-name, and then restart the JP1/AJS3 service.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

To identify the name of the service (process) that output this message, check the AP name that is output to the integrated trace log concurrently with this message. For details about the output content of the integrated trace log file, see 1.2.1(2) Integrated trace log in the manual JP1/Automatic Job Management System 3 Troubleshooting.

KAVS1814-E

The host name is invalid. : maintenance-information-1 (maintenance-information-2) maintenance-information-3

The host name indicated in maintenance-information-1 is invalid. Possible causes are:

The manager host name indicated in maintenance-information-1 cannot be resolved to the IP address.

The environment settings for the host name indicated in maintenance-information-1 contain errors.

If nothing is indicated in maintenance-information-1, the physical host name is assumed.

(S)

If a queueless agent service output this message during startup, the system terminates the queueless agent service abnormally. If this message is output during processing to attach the logical host, the system cancels the attach processing. If this message is output during execution or forced termination of a queueless job, the system continues processing.

If the queueless file transfer service output this message during startup, the system terminates the queueless file transfer service abnormally.

(O)

Take the following actions:

Confirm that the host name indicated in maintenance-information-1 has been set in the hosts file, jp1hosts file, or jp1hosts2 file.

If this message is output during processing to forcibly terminate the queueless job, you must stop the program manually by using Task Manager in Windows or the kill command or another means in UNIX.

KAVS1815-E

An attempt to write to the status file (status-file-name) failed.: maintenance-information-1 (maintenance-information-2)

An attempt to write to the status file indicated in status-file-name and managed for one logical host for the queueless agent service has failed.

(S)

Continues processing.

(O)

Take one of the following actions:

If No such file or directory is indicated in maintenance-information-1, the status file indicated in status-file-name might have been deleted. If the file does not exist, restart the queueless agent service, or detach the logical host containing the status file indicated in status-file-name that resulted in the error, and then attach it again.

If Permission denied is indicated in maintenance-information-1, write permission for the status file indicated in status-file-name might have been changed. Change the permission so that the user who started the queueless agent service and the OS user who executes the queueless job can write to the status file indicated in status-file-name. Then, restart the queueless agent service, or detach the logical host containing the status file indicated in status-file-name that resulted in the error, and then attach it again.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message. Also check the following probable causes, and then correct the error, if any.

- The disk does not have sufficient free space.

- Memory is insufficient.

- A directory having the same name as the status file has already been created in the directory in which the status file is to be created.

After correcting the error, restart the queueless agent service or detach the logical host containing the status file indicated in status-file-name that resulted in the error, and then attach it again.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

Examples:

In this example, the command detaches the logical host Lhost.

Execute the ajsqldetach command as follows:

ajsqldetach -h Lhost

For details on the ajsqldetach command, see ajsqldetach in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

In this example, the command attaches the logical host Lhost.

Execute the ajsqlattach command as follows:

ajsqlattach -h Lhost

For details on the ajsqlattach command, see ajsqlattach in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1816-E

An attempt to open the status file (status-file-name) failed.: maintenance-information-1 (maintenance-information-2)

Since the system could not open the status file indicated in status-file-name managed for each logical host for the queueless agent service, the system cannot use the status file for the logical host.

(S)

Terminates the queueless agent service abnormally if a queueless agent service output this message during startup. If this message is output during processing to attach the logical host, the system cancels the processing.

(O)

Take one of the following actions:

If No such file or directory is indicated in maintenance-information-1, the status file indicated in status-file-name might have been deleted. If the file does not exist, restart the queueless agent service, or detach the logical host containing the status file indicated in status-file-name that resulted in the error, and then attach it again.

If Permission denied is indicated in maintenance-information-1, write and read permissions for the status file indicated in status-file-name might have been changed. Change the permissions so that the user who started the queueless agent service and the OS user who executes the queueless job can read and write to the status file indicated in status-file-name. Then, restart the queueless agent service, or detach the logical host containing the status file indicated in status-file-name that resulted in the error, and then attach it again.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message. Also check the following probable causes, and then correct the error, if any.

- The disk does not have sufficient free space.

- Memory is insufficient.

- A directory having the same name as the status file has already been created in the directory in which the status file is to be created.

After correcting the error, restart the queueless agent service or detach the logical host containing the status file indicated in status-file-name that resulted in the error, and then attach it again.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

Examples:

In this example, the command detaches the logical host Lhost.

Execute the ajsqldetach command as follows:

ajsqldetach -h Lhost

For details on the ajsqldetach command, see ajsqldetach in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

In this example, the command attaches the logical host Lhost.

Execute the ajsqlattach command as follows:

ajsqlattach -h Lhost

For details on the ajsqlattach command, see ajsqlattach in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1817-E

IPC initialization failed, so the job (job-name) cannot be executed. (maintenance-information)

The queueless job indicated in job-name cannot be executed due to one of the following causes:

An attempt to acquire the IP address from the name of the host on which the queueless job indicated in job-name was executed has failed (a wrong IP address was acquired).

A communication error occurred.

Memory is insufficient.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Take one of the following actions, and then re-execute the queueless job indicated in job-name that resulted in the error.

In the DNS settings, hosts file, jp1hosts file, or jp1hosts2 file, correctly register the host name and IP address of the host that executes queueless jobs.

Use the ping command or another means to check the network status and correct the network failure.

Use Task Manager in Windows or the top command or another means in UNIX to make sure that memory is sufficient.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1818-E

An error occurred during internal file (file-name) processing, so the job (job-name) cannot be executed.: maintenance-information-1 (maintenance-information-2)

The queueless job indicated in job-name cannot be executed because an error occurred during processing of the internal file indicated in file-name used for execution of the queueless job.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Correct the error as follows, and then re-execute the queueless job indicated in job-name that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, make sure that the directory path specified in the internal file in file-name exists.

If Permission denied is indicated in maintenance-information-1, make sure that read and write permissions for the directory path to the internal file indicated in file-name are set for the user who started the queueless agent service and the OS user who executes the queueless job.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message. Also check the following probable causes, and then correct the error, if any.

- The disk does not have sufficient free space.

- Memory is insufficient.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1819-E

The specified work path (path-name) is invalid, so the job (job-name) cannot be executed.: maintenance-information-1 (maintenance-information-2)

The queueless job indicated in job-name cannot be executed because an attempt to access the work path indicated in path-name or the current directory has failed.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Make sure that the directory path specified in the work path indicated in path-name exists. Alternatively, make sure that the user who started the queueless agent service and the OS user who executed the queueless job can read and write to the work path indicated in path-name. Then, re-execute the queueless job indicated in job-name that resulted in the error.

KAVS1820-E

Memory is insufficient, so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed because of insufficient memory.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Check the amount of memory available by using Task Manager in Windows or the top command or another means in UNIX.

Wait until the memory necessary for executing the queueless job indicated in job-name that resulted in the error can be allocated, and then re-execute the queueless job.

KAVS1821-E

An iconv_open error occurred, so character conversion is not possible.: maintenance-information-1 (maintenance-information-2)

The system does not convert the character set because it could not make preparations for character set conversion.

(S)

Continues processing.

(O)

To convert the character sets, check the character settings and then restart the queueless agent.

KAVS1822-E

The file (file-name) does not exist on the transmission source host (host-name), so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed because the file indicated in file-name does not exist on the manager host indicated in host-name.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Take either of the following actions, and then re-execute the queueless job indicated by job-name that resulted in the error:

Make sure that the file to be transferred (file-name) exists on the transmission source host (host-name).

Make sure that the name of the file to be transferred (file-name) has no more than 254 characters (if the job is a PC job).

KAVS1823-E

No access permission is granted for the file (file-name) on the transmission host (host-name), so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed because there is no access permission for the file indicated in file-name on the manager host indicated in host-name.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

A directory path name might have been specified in the file indicated in file-name. If a directory path name is specified, specify the file name for File to transfer, and then re-execute the queueless job indicated in job-name that resulted in the error.

KAVS1824-E

An error occurred in the file (file-name) on the transmission source host (host-name), so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed because an attempt to read the file indicated in file-name on the manager host indicated in host-name has failed.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Give permission for reading the file indicated in file-name to the user who started the queueless file transfer service, and then re-execute the queueless job indicated in job-name that resulted in the error.

KAVS1825-E

An error occurred in the transmission file (file-name), so the job (job-name) cannot be executed.: maintenance-information-1 (maintenance-information-2)

The queueless job indicated in job-name cannot be executed because an error occurred in the file indicated in file-name on the manager host indicated in host-name.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Correct the error as follows, and then re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, the directory path specified in the destination file indicated in file-name does not exist. Make sure that the directory path exists.

If Permission denied is indicated in maintenance-information-1, an attempt to create the destination file indicated in file-name has failed. To ensure that this destination file can be created, set permissions so that the user who started the queueless agent service and the mapped OS user can read and write to the file or directory path.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1826-E

An IPC error occurred during file transmission, so the job (job-name) cannot be executed.: maintenance-information-1 (maintenance-information-2 maintenance-information-3)

The queueless job indicated in job-name cannot be executed due to a communication error that occurred during file transmission.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Execute the ping or jp1ping command on both the manager host and agent host to make sure they can communicate normally, and then re-execute the queueless job indicated in job-name that resulted in the error.

In addition, correct the error according to the information indicated in maintenance-information-1, and then re-execute the queueless job indicated in job-name that resulted in the error.

If you cannot correct the problem, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS1827-E

The job (job-name) cannot be executed because the processing is restricted.

The queueless job indicated in job-name cannot be executed because the queueless agent service is performing restricted processing.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Restart the queueless agent service, and then re-execute the queueless job indicated in job-name that resulted in the error.

KAVS1828-E

The specified priority value is invalid. (job-name)

If you have specified an execution priority of 4 or 5 for a Unix job, you need the superuser privileges.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Change the OS user who executes the queueless job indicated in job-name to a superuser, or change the execution order to 1, 2, or 3. Then, re-execute the queueless job indicated in job-name that resulted in the error.

KAVS1829-E

A system call (function-name) error occurred in the Queueless Agent service. : maintenance-information-1 maintenance-information-2

A system call error occurred in the queueless agent service.

(S)

Cancels the service startup processing or the requested processing.

(O)

When function-name is CreateDesktop, maintenance-information-2 is 8, and the AJSQL_CREATEWINDOWSTATION environment setting parameter is set to yes, there are too many OS users for the jobs to be executed.

Take action according to 6.4.3 Preventing a queueless job from ending abnormally with return value 128 in the JP1/Automatic Job Management System 3 Configuration Guide.

For details on AJSQL_CREATEWINDOWSTATION, see 6.4.3 Preventing a queueless job from ending abnormally with return value 128 in the JP1/Automatic Job Management System 3 Configuration Guide.

For other cases, ask the system administrator to collect data (1.2.3 To the system administrators).

KAVS1830-E

The job (job-name) cannot be executed because the length of the string (string-before-conversion) after variable substitution is too long.: string-after-conversion

If there are substitutions made for the variables used in the job definition, the length of some definition items might exceed the maximum. In such a case, the queueless job indicated in job-name cannot be executed.

The following shows the maximum length for each definition item after substitutions for the variables.

Executable file name (for PC jobs only): 767 bytes

Script file name (for Unix jobs only): 767 bytes

Parameter: 1535 bytes

Command statement (for Unix jobs only): No limit

Standard input file name: 767 bytes

Standard output file name: 767 bytes

Standard error output file name: 767 bytes

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Edit the job definition so that the lengths of the items do not exceed their maximums after substitutions for the variables, and then re-execute the queueless job indicated in job-name that resulted in the error.

KAVS1831-E

An attempt to attach the logical host (logical-host) has failed.

An attempt to attach the logical host indicated in logical-host failed when the queueless agent service was started, when the ajsqlattach command was executed, or when a queueless cluster process was started.

(S)

The queueless agent service cancels processing for attaching the logical host, and continues processing.

The system terminates the ajsqlattach command abnormally.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

(O)

The probable causes are that the shared disk is not mounted or disk space is insufficient. Take action according to the message that was output to the integrated trace log before or after this message.

After correcting the error, execute the ajsqlattach command to re-attach the logical host that resulted in the error.

If this message appears during startup of a queueless cluster process, correct the error, and then restart the JP1/AJS3 service and re-attach the logical host that resulted in the error.

Example: In this example, the command attaches the logical host.

Execute the ajsqlattach command as follows:

  ajsqlattach -h Lhost

For details on the ajsqlattach command, see ajsqlattach in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1832-E

Reception processing timed out during TCP/IP communication. (name-of-host-to-be-connected, job-name, maintenance-information)

A wait for a response timed out.

Possible causes are as follows:

The CPU load on the host to be connected is very high.

System resources are insufficient.

(S)

If the error occurred when an attempt was made to start the queueless job, the system places the queueless job indicated in job-name into Failed to start status.

If the error occurred when an attempt was made to terminate the queueless job, the system places the queueless job indicated in job-name into ended abnormally status. However, if 1 is specified for the IgnoreResultFileError environment setting parameter, the system places the queueless job indicated in job-name into the Ended normally, Ended with warning, or Ended abnormally status based on the end judgment.

(O)

Check the load on the destination host or the limits on system resources indicated by the kernel parameter settings. Then, if necessary, re-execute the job indicated in job-name that caused the error.

If files are transferred by multiple queueless jobs at the same time, the load on the manager host might increase. In addition, an attempt to establish a connection for communication might fail, and a timeout might occur. In this case, revise the environment setting parameters AJSQL_CONNECTTIMEOUT and AJSQL_CONNECTCOUNT so that connections for communication do not fail.

If the problem cannot be corrected, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

Note:

If the KAVS1859-W message was output before or after this message, an error occurred while transferring the result file. If 1 is specified for the IgnoreResultFileError environment setting parameter, any error that occurs while transferring the result file is ignored. Accordingly, you cannot use the Execution Result Details dialog box of JP1/AJS3 - View to view the contents of the standard error output file.

KAVS1833-E

An error occurred in the standard input file (file-name).: maintenance-information-1 (maintenance-information-2)

An error occurred during access to the standard input file.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Correct the error as follows, and then re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, the standard input file indicated in file-name does not exist. Make sure that the standard input file indicated in file-name exists, and then re-execute the job.

If Permission denied is indicated in maintenance-information-1, an attempt to read the standard input file indicated in file-name has failed. Set appropriate permissions for the file and directory path so that the mapped OS user can read the standard input file indicated in file-name. Then re-execute the job.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1834-E

An error occurred in the standard output file (file-name).: maintenance-information-1 (maintenance-information-2)

An error occurred during access to the standard output file.

(S)

Places the queueless job into Failed to start status.

(O)

Correct the error as follows, and then re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, the standard output file indicated in file-name does not exist. Make sure that the standard output file indicated in file-name exists, and then re-execute the job.

If Permission denied is indicated in maintenance-information-1, an attempt to read or write to the standard output file indicated in file-name has failed. Set appropriate permissions for the file and directory path so that the mapped OS user can read and write to the standard output file indicated in file-name. Then re-execute the job.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1835-E

An error occurred in the standard error output file (file-name).: maintenance-information-1 (maintenance-information-2)

An error occurred in the standard error output file or internal file (indicated in file-name).

(S)

If the error occurred when an attempt was made to start a queueless job, the system places the queueless job into the Failed to start status.

If the error occurred while outputting to the standard error output file, the system places the queueless job into the Ended abnormally status.

If the error occurred while transferring the result file when the queueless job terminated, the system places the queueless job into the Ended abnormally status. However, if 1 is specified for the IgnoreResultFileError environment setting parameter, the system places the queueless job into the Ended normally, Ended with warning, or Ended abnormally status based on the end judgment.

(O)

Correct the cause of the error as described below. Then, if necessary, re-execute the queueless job that caused the error.

If No such file or directory is indicated in maintenance-information-1, the standard error output file indicated in file-name does not exist. Make sure that the standard error output file indicated in file-name exists, and then re-execute the job.

If Permission denied is indicated in maintenance-information-1, an attempt to read or write to the standard error output file or internal file (indicated in file-name) failed. Set appropriate permissions for the file and directory path so that the mapped OS user can read and write to the standard error output file indicated in file-name. Then re-execute the job.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

Note:

If the KAVS1859-W message was output before or after this message, an error occurred while transferring the result file. If 1 is specified for the IgnoreResultFileError environment setting parameter, any error that occurs while transferring the result file is ignored. Accordingly, you cannot use the Execution Result Details dialog box of JP1/AJS3 - View to view the contents of the standard error output file.

KAVS1836-E

An error occurred in the environment variable file (file-name).: maintenance-information-1 (maintenance-information-2)

An error occurred during access to the environment variable file.

(S)

Places the queueless job into Failed to start status.

(O)

Correct the error as follows, and then re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, the environment variable file indicated in file-name does not exist. Make sure that the environment variable file indicated in file-name exists, and then re-execute the job.

If Permission denied is indicated in maintenance-information-1, an attempt to read the environment variable file indicated in file-name has failed. Set appropriate permissions for the file and directory path so that the mapped OS user can read the environment variable file indicated in file-name, and then re-execute the job.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1837-E

A JP1/AJS2 environment setting is incorrect. (logical host=logical-host-name, label=environment-setting-parameter-name)

The value set in the JP1/AJS3 environment settings for the logical host indicated in logical-host-name is incorrect.

(S)

Continues processing the default value of the label indicated in environment-setting-parameter-name.

(O)

Correct the value set in the label indicated in environment-setting-parameter-name on the host indicated logical-host-name. Then, for the physical host, restart the queueless agent service. For a logical host, execute the ajsqlattach command to attach the host indicated in logical-host-name.

If this message appears during startup of a queueless cluster process, correct the value of the label indicated in environment-setting-parameter-name, and then restart the JP1/AJS3 service.

Example: In this example, the command attaches the logical host.

Execute the ajsqlattach command as follows:

  ajsqlattach -h Lhost

For details on the ajsqlattach command, see ajsqlattach in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1838-E

An attempt to read the status file (file-name) failed.: maintenance-information-1 (maintenance-information-2)

An attempt to read the status file indicated in file-name that is managed for one logical host for the queueless agent service has failed.

(S)

Does not write the end status of the queueless job to the status file indicated in file-name that resulted in the error.

(O)

Correct the error as follows, and then re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, the status file indicated in status-file-name does not exist. Make sure that the file indicated in status-file-name exists.

If Permission denied is indicated in maintenance-information-1, an attempt to read the status file indicated in file-name has failed. Check whether appropriate permissions are set for the file and directory path so that the OS user who started the queueless agent service can read the status file indicated in file-name.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1839-E

An error occurred during acquisition of the judgment file (file-name).: maintenance-information-1 (maintenance-information-2)

An error occurred during the acquisition of information from the judgment file indicated in file-name.

(S)

Places the queueless job into Failed to start or Ended abnormally status.

(O)

Correct the error as follows, and then re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, the judgment file indicated in file-name does not exist. Make sure that the judgment file indicated in file-name exists, and then re-execute the job.

If Permission denied is indicated in maintenance-information-1, an attempt to read the judgment file indicated in file-name has failed. Set appropriate permissions for the file and directory path so that the mapped OS user can read the judgment file indicated in file-name. Then re-execute the job.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1840-E

There are too many characters in a line of the environment variable file (file-name).

There are too many characters in a line of the environment variable file indicated in file-name.

(S)

Places the queueless job into Failed to start status.

(O)

Check and correct the contents of the environment variable file so that each line is no more than 1,023 bytes, and then re-execute the job.

KAVS1841-E

Too many processes exist, so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed because too many processes are running on the system.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

The maximum number of processes that can run concurrently on the system might have been exceeded. Use the ps command or another means to check the number of processes running on the system. Make sure that the number of processes are within the maximum, and then re-execute the queueless job indicated in job-name that resulted in the error.

The maximum number of processes specified in the kernel parameter might not suit the current operation. Check the value for the entire system, and then change the value if necessary.

For details about how to estimate the kernel parameters for JP1/AJS3, see 3.2.5 Estimating the values for kernel parameters in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVS1842-E

Job result information cannot be sent because an internal file (file-name) error occurred.: maintenance-information-1 (maintenance-information-2)

The system could not report the contents of the result file to the manager host because an error occurred during processing of the internal file indicated in file-name that is used for execution of the queueless job.

(S)

Places the queueless job into Failed to start status if this message appears before the queueless job is started.

If the error occurred while outputting to the standard error output file, the system places the queueless job into the Ended abnormally status.

If the error occurred while transferring the result file when the queueless job terminated, the system places the queueless job into the Ended abnormally status. However, if 1 is specified for the IgnoreResultFileError environment setting parameter, the system places the queueless job into the Ended normally, Ended with warning, or Ended abnormally status based on the end judgment.

(O)

Correct the cause of the error as described below. Then, if necessary, re-execute the queueless job that caused the error.

If Permission denied is indicated in maintenance-information-1, an attempt to create, read, or write to the internal file indicated in file-name has failed. Set appropriate permissions for the directory path that has the internal file so that the user who started the queueless agent service and the mapped OS user can read or write to the internal file indicated in file-name.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message. Also check the following probable causes, and then correct the error, if any.

- The disk does not have sufficient free space.

- Memory is insufficient.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

Note:

If the KAVS1859-W message was output before or after this message, an error occurred while transferring the result file. If 1 is specified for the IgnoreResultFileError environment setting parameter, any error that occurs while transferring the result file is ignored. Accordingly, you cannot use the Execution Result Details dialog box of JP1/AJS3 - View to view the contents of the standard error output file.

KAVS1843-E

User mapping failed on the remote ftp host (host-name), so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed due to unsuccessful user mapping on the manager host indicated in host-name.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

A message indicating the cause of the error that occurred in the queueless job indicated in job-name is output to the integrated trace log on the manager host indicated in host-name. Take action according to the instructions given by the message.

KAVS1844-E

An error occurred on the remote ftp host (host-name), so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed due to unsuccessful file transmission from the manager host indicated in host-name to the agent host.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

A message indicating the cause of the error that occurred in the queueless job indicated in job-name is output to the integrated trace log on the manager host indicated in host-name. Take action according to the instructions given by the message.

KAVS1845-E

An IPC error occurred during the result notification.: system-error-message (maintenance-information-1, maintenance-information-2)

The system could not report the contents of the result file to the manager host because a communication error occurred.

(S)

Places the queueless job into ended abnormally status. However, if 1 is specified for the IgnoreResultFileError environment setting parameter, the system places the queueless job into the Ended normally, Ended with warning, or Ended abnormally status based on the end judgment.

(O)

Execute the ping and jp1ping commands to make sure that the agent host can communicate with the manager host indicated in host-name, and that the queueless file transfer service is running on this manager host. Then, if necessary, re-execute the queueless job that caused the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

Note:

If the KAVS1859-W message was output before or after this message, an error occurred while transferring the result file. If 1 is specified for the IgnoreResultFileError environment setting parameter, any error that occurs while transferring the result file is ignored. Accordingly, you cannot use the Execution Result Details dialog box of JP1/AJS3 - View to view the contents of the standard error output file.

KAVS1846-E

The job definition (job-name) is invalid.

The same name is assigned to the standard output file and the standard error output file, and different items are specified for additional information to be written.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Recheck the job definition statement and correct the job definition. Then, execute the job.

KAVS1847-W

A job that was waiting for execution was forcibly terminated.

This message is output when a queueless job that is waiting for execution is forcibly terminated.

(S)

Places the queueless job into Failed to start status.

KAVS1848-W

The job (job-name) was forcibly terminated. (process-ID)

This message indicates that the queueless job indicated in job-name was forcibly terminated.

(S)

Forcibly terminates the queueless job indicated in job-name.

KAVS1849-W

The job (job-name) was aborted. (process-ID)

The time-out period expired. The queueless job indicated in job-name is aborted.

(S)

Aborted the queueless job indicated in job-name.

KAVS1850-E

The logical host (host-name) is ignored because the number of logical hosts set for the queueless agent exceeds the limit.

The logical host indicated in host-name cannot be attached because the number of logical hosts attached to the queueless agent service has reached the maximum, that is, 9.

(S)

Continues processing.

(O)

A maximum of 9 logical hosts can be attached to the queueless agent service concurrently.

Execute the ajsqldetach command to detach an unneeded logical host, and then execute the ajsqlattach command to attach the logical host indicated in host-name again.

Examples:

In this example, the command detaches the logical host Lhost.

Execute the ajsqldetach command as follows:

ajsqldetach -h Lhost

For details on the ajsqldetach command, see ajsqldetach in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

In this example, the command attaches the logical host Lhost.

Execute the ajsqlattach command as follows:

ajsqlattach -h Lhost

For details on the ajsqlattach command, see ajsqlattach in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1851-I

The file transmission service will now start.

The queueless file transmission service starts.

(S)

Starts the queueless file transfer service.

KAVS1852-I

The file transmission service will now stop.

The file transmission service ends.

(S)

Terminates the queueless file transfer service.

KAVS1853-I

The file transmission service will now terminate.

The queueless file transfer service aborted because a forced termination request was accepted.

(S)

Terminates the queueless file transfer service.

KAVS1854-E

The file transmission service abnormally ended.

The queueless file transfer service ended abnormally.

(S)

Terminates the queueless file transfer service.

(O)

Take action according to the instructions given by the message that was output immediately before this message, and then restart the queueless file transfer service.

KAVS1855-W

Character code conversion failed. : maintenance-information-1 (maintenance-information-2)

Character set conversion failed, causing the following problems:

Data displayed in the Execution Result Details dialog box contains unreadable characters.

The file specified as the transfer destination file uses an invalid character set.

(S)

Continues processing.

(O)

Contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVS1859-W

An attempt to transmit the result file for the job (job-name) has failed.

An error occurred while transferring the result file for the queueless job.

(S)

Continues processing.

(O)

Check the integrated trace log to see if a message beginning with KAVS was output before or after this message. If a message was output, also see the explanation for that message.

Note:

Even if the standard error output file has not been defined in the detailed definition of the job, a temporary standard error output file is created and transferred to the manager host. For details about the standard error output file, see 7.10.1 Notes on the standard output file and standard error output file in the JP1/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 based on the end judgment. In addition, the result file is not resent because the preferred method to handle the job is termination. Accordingly, you cannot use the Execution Result Details dialog box of JP1/AJS3 - View to view the contents of the standard error output file.

KAVS1860-W

Shared memory could not be allocated, but startup processing will continue. :maintenance-information-1 maintenance-information-2

An attempt to allocate shared memory or a system resource failed. If an account other than the service account is used to execute jobs, jobs that use the jp1exec command might not be able to be stopped.

(S)

Continues request processing.

(O)

If you need to stop a job that uses the jp1exec command, stop other unnecessary applications, and then restart the JP1/AJS3 Queueless Agent service.

KAVS1861-E

The file transmission failed.

File transmission failed due to a communication failure between the manager host and the agent host during file transfer.

(S)

Continues job execution.

(O)

Execute the ping and jp1ping commands to make sure that the manager host and the agent host can communicate normally with each other. Then, re-execute the queueless job that resulted in the error.

If you cannot correct the problem, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS1862-I

The queueless cluster process (logical-host-name) will now start.

The queueless cluster process for the logical host (logical-host-name) will now start.

(S)

Starts the queueless cluster process indicated in logical-host-name.

KAVS1863-I

The queueless cluster process (logical-host-name) has started.

The queueless cluster process for the logical host (logical-host-name) has started.

(S)

Starts the queueless cluster process indicated in logical-host-name.

KAVS1864-E

The queueless cluster process (logical-host-name) ended abnormally.: maintenance-information-1 (maintenance-information-2) maintenance-information-3

The queueless cluster process for the logical host (logical-host-name) terminated abnormally.

(S)

Terminates the queueless cluster process indicated in logical-host-name.

(O)

The probable causes of the abnormal termination of the queueless cluster process are:

The logical host name contains more than 255 bytes.

Memory was insufficient during startup of the process.

An attempt to attach the logical host has failed.

An attempt to detach the logical host has failed.

If maintenance-information-2 is invalid hostname, the logical host name contains 256 or more bytes. Set a logical host name that contains 255 or fewer bytes.

If maintenance-information-2 is attach failed or detach failed, an attempt to attach or detach the logical host has failed. Take action according to the instructions given by the message that was output immediately before this message.

If maintenance-information-2 is insufficient memory, memory is insufficient. Take action according to the instructions given by the message that was output immediately before this message.

For other cases, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVS1865-E

File transmission is impossible because an attempt to create the process failed.: maintenance-information-1 (maintenance-information-2)

File transmission is impossible because an attempt to create a worker process for queueless file transmission has failed due to too many processes running on the system.

(S)

Cancels execution of the worker process for queueless file transmission.

(O)

The maximum number of processes that can run concurrently on the system might have been exceeded. Use the ps command or another means to check the number of processes running on the system. Make sure that the number of processes are within the maximum, and then re-execute the queueless job indicated in job-name that resulted in the error.

The maximum number of processes specified in the kernel parameter might not suit the current operation. Check the value for the entire system, and then change the value if necessary.

For details about how to estimate the kernel parameters for JP1/AJS3, see 3.2.5 Estimating the values for kernel parameters in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVS1866-E

The file transmission failed due to insufficient memory.

The file cannot be transmitted because memory became insufficient during transmission.

(S)

Cancels execution of the worker process for queueless file transmission.

(O)

Check the amount of memory available by using Task Manager in Windows or the top command or another means in UNIX.

Wait until the memory necessary for file transfer can be allocated, and then re-execute the queueless job that resulted in the error.

KAVS1867-E

The file transmission service of the host (host-name) cannot be connected, so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed because the queueless file transfer service on the manager host indicated in host-name cannot be connected.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Execute the ping and jp1ping commands to make sure that the agent host can communicate with the manager host indicated in host-name, and that the queueless file transfer service is running on this manager host. Then, re-execute the queueless job that resulted in the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1868-E

The FTP host (host-name) is unknown, so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed because the manager host name indicated in host-name cannot be resolved to the IP address.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Review the hosts file, jp1hosts file, jp1hosts2 file, or DNS settings to ensure that the IP address of the manager host name indicated in host-name can be resolved on the agent host. Also confirm that the manager host IP address is set correctly. Then, re-execute the queueless job indicated in job-name that resulted in the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1869-E

The FTP server of the host (host-name) cannot be reached, so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed because communication with the manager host indicated in host-name has failed.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Execute the ping and jp1ping commands to make sure that the agent host can communicate with the manager host indicated in host-name. Then, re-execute the queueless job that resulted in the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1870-E

The file transmission service of the host (host-name) cannot be connected, so an attempt to report the result failed.: job-name

An attempt to report the job execution results failed because the queueless file transfer service on the manager host indicated in host-name could not be connected.

(S)

Places the queueless job indicated in job-name into ended abnormally status. However, if 1 is specified for the IgnoreResultFileError environment setting parameter, the system places the queueless job indicated in job-name into the Ended normally, Ended with warning, or Ended abnormally status based on the end judgment.

(O)

Execute the ping and jp1ping commands to make sure that the agent host can communicate with the manager host indicated in host-name, and that the queueless file transfer service is running on this manager host. Then, if necessary, re-execute the queueless job job-name that caused the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

Note:

If the KAVS1859-W message was output before or after this message, an error occurred while transferring the result file. If 1 is specified for the IgnoreResultFileError environment setting parameter, any error that occurs while transferring the result file is ignored. Accordingly, you cannot use the Execution Result Details dialog box of JP1/AJS3 - View to view the contents of the standard error output file.

KAVS1871-E

The manager host (host-name) is unknown, so an attempt to report the result failed.: job-name

An attempt to report the job execution results failed because the manager host indicated in host-name could not be connected due to unsuccessful resolution of the manager host name indicated in host-name to the IP address.

(S)

Places the queueless job indicated in job-name into ended abnormally status. However, if 1 is specified for the IgnoreResultFileError environment setting parameter, the system places the queueless job indicated in job-name into the Ended normally, Ended with warning, or Ended abnormally status based on the end judgment.

(O)

Ensure that the manager host name and IP address are set in the hosts, jp1hosts, or jp1hosts2 file or in the DNS settings so that the IP address of the manager host name indicated in host-name can be resolved on the agent host. Then, if necessary, re-execute the queueless job job-name that caused the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

Note:

If the KAVS1859-W message was output before or after this message, an error occurred while transferring the result file. If 1 is specified for the IgnoreResultFileError environment setting parameter, any error that occurs while transferring the result file is ignored. Accordingly, you cannot use the Execution Result Details dialog box of JP1/AJS3 - View to view the contents of the standard error output file.

KAVS1872-E

The host (host-name) of the manager is unknown, so an attempt to report the result failed.: job-name

An attempt to report the job execution results failed because communication with the manager host indicated in host-name has failed.

(S)

Places the queueless job indicated in job-name into ended abnormally status. However, if 1 is specified for the IgnoreResultFileError environment setting parameter, the system places the queueless job indicated in job-name into the Ended normally, Ended with warning, or Ended abnormally status based on the end judgment.

(O)

The manager host IP address set in the hosts file, jp1hosts file, jp1hosts2 file, or DNS settings might be incorrect. Make sure that the correct IP address is set. In addition, execute the ping and jp1ping commands to make sure that the agent host can communicate with the manager host indicated in host-name. Then, if necessary, re-execute the queueless job job-name that caused the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

Note:

If the KAVS1859-W message was output before or after this message, an error occurred while transferring the result file. If 1 is specified for the IgnoreResultFileError environment setting parameter, any error that occurs while transferring the result file is ignored. Accordingly, you cannot use the Execution Result Details dialog box of JP1/AJS3 - View to view the contents of the standard error output file.

KAVS1873-E

The specified file (file-name) cannot be opened.

The file indicated in file-name cannot be opened.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

The probable causes that prevented the file indicated in file-name from being opened are:

Free disk space is insufficient.

Memory is insufficient.

The file indicated by file-name does not exist.

Access permission that allows the queueless agent service account or the user executing the job to write to or read the directory is not set for the directory in which the file is to be created.

A directory having the same name as the file has already been created in the directory in which the status file is created.

The name of the file indicated by file-name has 255 or more characters.

Make sure that the above conditions are not satisfied, and then re-execute the queueless job that resulted in an error.

KAVS1874-E

You do not have permission for the specified file (file-name).

An attempt was made to execute a queueless job with the indicated file (file-name) specified, but the queueless agent service account was not allowed to access the file. Alternatively, the specified character string (file-name) was a folder name.

(S)

Places the queueless job into Failed to start status.

(O)

For the specified file (file-name), set an appropriate access permission that allows the queueless agent service account to read or write to the file, and then re-execute the queueless job that resulted in an error.

If a folder name was specified, re-execute the queueless job with a file name specified.

KAVS1875-E

The class name is too long. (class-name) (logical host =logical-host)

The class name indicated in class-name specified in the environment setting parameter for the logical host is too long.

(S)

Continues startup processing of the queueless agent service, or the processing to attach the logical host. However, the class is not registered as a class for which the job is executed.

(O)

Define the class name indicated in class-name that caused the error by using no more than 63 bytes, and then restart the queueless agent service. Alternatively, detach the logical host that caused the error, and then attach it again.

KAVS1876-E

The class (class-name) already exists. (logical host =logical-host)

A class with the same name (class-name) is already set in the environment setting parameter for the logical host indicated in logical-host.

(S)

Continues startup of the queueless agent service.

(O)

Make sure that there is no duplicate class name for the logical host, and then restart the queueless agent service. Even if you do not restart the queueless agent service, however, the class can be used as a class for which the job is executed.

KAVS1877-E

Memory is insufficient, so the class (class-name) cannot be used. (logical host =logical-host)

The class indicated in class-name cannot be used due to insufficient memory.

(S)

Cancels creation of the class and continues startup processing of the queueless agent service, or the processing to attach the logical host.

(O)

Check the amount of memory available by using Task Manager in Windows or the top command or another means in UNIX.

Wait until the memory necessary for using the class can be allocated, and then restart the queueless agent service. Alternatively, detach the logical host that caused the error, and then attach it again.

KAVS1878-E

The class (class-name) cannot be created because a JP1/AJS2 environment setting is incorrect. (logical host=logical-host-name, label=environment-setting-parameter-name)

An attempt to create the class indicated in class-name has failed due to an invalid value of an environment setting parameter in the JP1/AJS3 environment setting.

(S)

Cancels creation of the class and continues startup processing of the queueless agent service or the processing to attach the logical host.

(O)

Correct the value set in the label indicated in environment-setting-parameter-name on the host indicated in logical-host-name. Then, restart the queueless agent service or detach the logical host that caused the error, and then attach it again.

KAVS1879-E

An error occurred in the file (file-name).

An error occurred during processing of the file indicated in file-name.

(S)

Places the queueless job into Failed to start status.

(O)

Possible causes of the error in the file (file-name) are as follows:

Free disk space is insufficient.

Memory is insufficient.

There is no write permission for the directory in which the file is created.

A directory having the same name as the file has already been created in the directory in which the status file is created.

The file name (file-name) has 255 or more characters.

Make sure that the above conditions are not satisfied, and then re-execute the queueless job that resulted in an error.

KAVS1880-E

Execution of the job (job-name) failed because the OS user (OS-user-name) does not have permission to log on as a batch job.

The queueless job job-name failed to start because the OS user OS-user-name for which 1 is set in the UACAdministratorsExec environment setting parameter does not have permission to log on as a batch job.

(S)

Places the queueless job job-name in Failed to start status.

(O)

Set log on as a batch job in the security policy for the OS user OS-user-name, and then re-execute the queueless job job-name that resulted in the error. For details, see 6.2.22 Settings for executing jobs as a user with administrator permissions when the UAC is enabled in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS1881-E

An error occurred in the check processing of user mapping. (logical host=logical-host-name, function=maintenance-information-1, code=maintenance-information-2)

Processing failed because user mapping was not set up correctly.

(S)

Places the queueless job into Failed to start status.

(O)

The probable causes are as follows:

An attempt to set up the logical host specified for logical-host-name might have failed.

User who owns is specified for Executed by in the detailed definition of the job, but no value is specified for Owner.

The environment might have been corrupted.

See the integrated trace log to check whether an error messages have been output. If an error message was output, correct the error according to the instructions given by the message, and then restart the queueless agent service and re-execute the queueless job that resulted in the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1882-E

The user mapping definition of the JP1 user (JP1-user-name) on the host (host-name) was not found. (logical host =logical-host-name)

The user mapping definition for the JP1 user indicated in JP1-user-name on the manager host indicated in host-name is not found.

(S)

Places the queueless job into Failed to start status.

(O)

Make sure that the JP1 user indicated in JP1-user-name is defined in the user mapping information for the logical host, and then re-execute the queueless job that resulted in the error.

For details about the user mapping settings, see 3.1.1 Setting up JP1/Base in the JP1/Automatic Job Management System 3 Configuration Guide (in Windows) or 13.1.1 Setting up JP1/Base in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

KAVS1883-E

The JP1 user (JP1-user-name) on the host (host-name) cannot be mapped to the OS user (OS-user-name). (logical host =logical-host-name)

The JP1 user indicated in JP1-user-name on the manager host indicated in host-name cannot be mapped to the OS user indicated in OS- user-name.

(S)

Places the queueless job into Failed to start status.

(O)

The OS user indicated in OS-user-name has not been mapped to the JP1 user indicated in JP1-user-name. On the agent host, make sure that the OS user indicated in OS-user-name has been mapped to the JP1 user indicated in JP1-user-name, and then re-execute the queueless job that resulted in the error.

For details about the user mapping settings, see 3.1.1 Setting up JP1/Base in the JP1/Automatic Job Management System 3 Configuration Guide (in Windows) or 13.1.1 Setting up JP1/Base in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

KAVS1884-E

The OS user (user-name) was not found in the passwd file.

An attempt to obtain information about an OS user who attempted to execute a job failed.

(S)

Places the queueless job into Failed to start status.

(O)

Make sure that the OS user mapped to a JP1 user exists and is able to log on. Next, re-execute the queueless job that caused the error.

This message is sometimes output if you register, delete, or change the password of an OS user while a job is starting or finishing. In this scenario, re-execute the job after the OS user registration, deletion, or password change operation has concluded.

You can avoid this problem altogether by setting the AJSQL_GETPASSWD_FTPRETRYINTERVAL or AJSQL_GETPASSWD_AGTRETRYINTERVAL environment setting parameter. For details, see 15.2.20 Changing the settings for retries when user information is acquired in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS1885-E

An attempt to open the file (file-name) failed.: maintenance-information-1 (maintenance-information-2)

An attempt to open the file indicated in file-name has failed.

(S)

If a queueless agent service output this message during startup, the system cancels startup of the service.

If this message is output during startup of a queueless job, the system places the queueless job into Failed to start status.

If this message is output during termination of a queueless job, the system places the queueless job into Ended abnormally status.

(O)

Correct the error as follows, and then restart the queueless agent service or re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, make sure that the directory path specified in the internal file in file-name exists.

If Permission denied is indicated in maintenance-information-1, make sure that read and write permissions for the directory path to the internal file indicated in file-name are set for the user who started the queueless agent service and the OS user who executes the queueless job.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message. Also check the following probable causes, and then correct the error, if any.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1886-E

A socket communication error occurred.: maintenance-information-1 (maintenance-information-2, maintenance-information-3)

An error occurred during socket communication.

(S)

Places the queueless job into Failed to start status if this message is output during execution of a queueless job. If this message is output during execution of the command related to queueless job execution control, the system terminates the command abnormally.

(O)

Take action according to the message output after this message.

KAVS1887-E

Invalid data was received. (IPCID= IP-address)

The system received invalid data from the connection source shown in IP-address.

(S)

Continues processing.

(O)

Determine the connection source from the IP address, and check that the connection source does not have a problem.

KAVS1888-E

An error occurred during the reading of the passwd file.: maintenance-information-1 (maintenance-information-2)

An error occurred during a read from the password file.

(S)

Places the queueless job into Failed to start status.

(O)

Make sure that the OS user who is mapped during execution of the queueless job exists. Also make sure that appropriate permission is set so that the user who started the queueless agent service can read the passwd file (/etc/passwd). Then, re-execute the queueless job that resulted in the error.

This message is sometimes output if you register, delete, or change the password of an OS user while a job is starting or finishing. In this scenario, re-execute the job after the OS user registration, deletion, or password change operation has concluded.

You can avoid this problem altogether by setting the AJSQL_GETPASSWD_FTPRETRYINTERVAL or AJSQL_GETPASSWD_AGTRETRYINTERVAL environment setting parameter. For details, see 15.2.20 Changing the settings for retries when user information is acquired in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS1889-E

An attempt to read the file (file-name) failed.: maintenance-information-1 (maintenance-information-2)

An attempt to read the file indicated in file-name has failed.

(S)

Places the queueless job into Failed to start status.

(O)

Correct the error as follows, and then re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, the file indicated in file-name does not exist. Make sure that the file indicated in file-name exists.

If Permission denied is indicated in maintenance-information-1, an attempt to read the file indicated in file-name has failed. Set appropriate permissions for the file and directory path so that the user who started the queueless agent service and the mapped OS user can read the file indicated in file-name.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1890-E

An attempt to write to the file (file-name) failed.: maintenance-information-1 (maintenance-information-2)

An attempt to write to the file indicated in file-name has failed.

(S)

Places the queueless job into Ended abnormally status.

(O)

Correct the error as follows, and then re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, make sure that the directory path output to the file indicated in file-name exists.

If Permission denied is indicated in maintenance-information-1, make sure that read and write permissions for the directory path to the file indicated in file-name are set for the user who started the queueless agent service and the OS user who executes the queueless job.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message. Also check the following probable causes, and then correct the error, if any.

- The disk does not have sufficient free space.

- Memory is insufficient.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1891-E

An attempt to open the socket failed.: maintenance-information-1 (maintenance-information-2)

The socket could not be initialized.

(S)

Terminates the service for which this message is output.

(O)

Memory might be insufficient. Check the amount of memory available by using Task Manager in Windows or the top command or another means in UNIX, and then restart the service that could not be started.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1892-E

The shared memory size is invalid. (size=size)

The shared-memory size is invalid.

(S)

Terminates the queueless agent service.

(O)

Take either of the following actions, and then restart the queueless agent service:

Reduce the maximum number of concurrently executable jobs according to the shared memory size that is currently set.

Increase the shared memory size set in the kernel parameter according to the maximum number of concurrently executable jobs.

The maximum number of concurrently executable jobs is set in the AJSQL_JOBMAX environment setting parameter. For details, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

For details about how to estimate the kernel parameters used in JP1/AJS3, see 3.2.5 Estimating the values for kernel parameters in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVS1893-E

Too many shared memories exist on the system.

The queueless agent service cannot use shared memory because the system has used too many segments of shared memory.

(S)

Terminates the queueless agent.

(O)

Calculate the number of shared-memory segments required for the system, and modify the value of the kernel parameter to the appropriate value. Then, restart the queueless agent service.

For details about how to estimate the size of shared memory required for JP1/AJS3 operation, see 3.2.5 Estimating the values for kernel parameters in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVS1894-E

The number of shared memory attaches is invalid.

Shared memory cannot be attached to the queueless agent service.

(S)

Terminates the queueless agent service.

(O)

Set 1 or a greater value for the kernel parameter so that shared memory can be attached to the queueless agent service. Then, restart the queueless agent service.

KAVS1896-E

A log file (file-name) error occurred.: maintenance-information-1 (maintenance-information-2)

An error occurred during processing required to open or write to the log file indicated in file-name.

(S)

If this message is output during startup of a queueless agent service, the system continues startup of the service. However, no log data is output to the log file indicated in file-name.

If this message is output during execution of a queueless job, the system continues queueless job execution. However, no log data about the queueless job is output to the log file indicated in file-name.

(O)

Take one of the following actions:

If No such file or directory is indicated in maintenance-information-1, the log file indicated in file-name might have been deleted. Check whether the log file exists. If it does not exist, restart the queueless agent service.

If Permission denied is indicated in maintenance-information-1, write and read permissions for the log file indicated in file-name might have been changed. Change the permissions so that the user who started the queueless agent service and the OS user who executes the queueless job can read and write to the log file indicated in file-name. Then, restart the queueless agent service.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message, and then restart the queueless agent service.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1897-E

An attempt to start the job (job-name).

An attempt to start the queueless job indicated in job-name has failed due to an internal error.

(S)

Places the queueless job indicated in job-name into Failed to start status or Ended abnormally status.

(O)

Re-execute the queueless job indicated in job-name that resulted in the error. If an attempt to start the queueless job fails again, restart the queueless agent service, and then re-execute the queueless job indicated in job-name that resulted in the error.

If the UAC function is enabled in Windows and the OS user who executed the job is a member of the Administrators group, the Administrators permission might be disabled for the indicated 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 JP1/Automatic Job Management System 3 Configuration Guide.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1898-I

The connection was reset by the peer.

The connection between the queueless agent service and the queueless job request process or between the queueless agent service and the queueless file transfer service was reset.

(S)

Continues processing.

(O)

If the connection was reset due to an error, a message indicating the cause of the error was output before this message. Take action according to the instructions given by that message.

KAVS1900-W

The queueless job request process (scheduler-service-name:identification-number) abnormally ended.: maintenance-information

This message indicates that the queueless job request process ended abnormally.

(S)

Cancels the execution of the queueless job request process.

Attempts to restart the queueless job request process until the abnormal end count reached the threshold. When the threshold is reached, the system blocks the queueless job request process.

(O)

Memory may be insufficient. Alternatively, the number of processes started on the system may have reached the maximum.

In UNIX, check and correct the settings of the kernel parameters for memory and processes.

For details about how to estimate kernel parameters and the size of memory used, see Release Notes.

Check the status of the process that was running when the error occurred.

Then make sure that the amount of memory available is greater than the estimated value.

The maximum number of queueless job requests might be too large. If a value other than 1 is specified for the environment setting parameter QUEUELESSMULTIREQ, change the value to 1, and then restart the scheduler service.

If you cannot determine the cause, collect data and then contact the system administrator (see 1.2.3 To the system administrators).

We recommend that you first make sure that other jobs have terminated by releasing job restrictions, and then restart the scheduler service.

KAVS1901-I

The queueless job request process (scheduler-service-name:identification-number) was rebooted.

This message indicates that the queueless job request process restarted.

(S)

Restarted the queueless job request process.

KAVS1902-W

An attempt to reboot the queueless job request process (scheduler-service-name:identification-number) failed.: maintenance-information

The system could not restart the queueless job request process. The possible causes include system resources becoming insufficient because more than one queueless job request process was started.

(S)

Terminates the queueless job request process.

(O)

Determine the cause of the failure to restart the queueless job request process according to the messages output before and after this message. Then, take proper action.

KAVS1903-E

The queueless job request process (scheduler-service-name:identification-number) was blocked because the maximum number of abnormally ended queueless job request abends was exceeded.

Since the number of times the queueless job request process ended abnormally exceeded the threshold, the queueless job request process is blocked.

(S)

Blocked the queueless job request process because the threshold value was exceeded.

(O)

Memory may be insufficient. Alternatively, the number of processes started on the system may have reached the maximum.

In UNIX, check and correct the settings of the kernel parameters for memory and processes.

For details about how to estimate kernel parameters and the size of memory used, see Release Notes.

Check the status of the process that was running when the error occurred. Then make sure that the amount of memory available is greater than the estimated value.

The maximum number of queueless job requests might be too large. If a value other than 1 is specified for the environment setting parameter QUEUELESSMULTIREQ, change the value to 1, and then restart the scheduler service.

If you cannot determine the cause, collect data and then contact the system administrator (see 1.2.3 To the system administrators).

We recommend that you first make sure that other jobs have terminated by releasing job restrictions, and then restart the scheduler service.

KAVS1904-E

All the queueless job request processes of the scheduler service (scheduler-service-name) are blocked.

All the queueless job request processes on the scheduler service terminated abnormally. The probable cause is insufficient system resources due to startup of multiple queueless job request processes.

(S)

Stops the scheduler service.

(O)

Examine the cause of the error according to the KAVS1903-E message that was output before this message. Correct the cause of the error, and then restart the scheduler service.

KAVS1905-W

The value specified for the maximum number of queueless job request processes in the environment setting parameter is outside the effective range. The default value (concurrently-executable-job-limit) is assumed and processing is continued.

The value of the QUEUELESSMULTIREQ environment setting parameter is outside the valid range.

(S)

Assumes the value specified in maximum-number-of-concurrently-executable-job-limit, and continues processing.

(O)

Correct the value of the concurrently-executable-job-limit, and then restart the scheduler service. For details on the environment setting parameters, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS1906-E

Initialization of a queueless job request process failed.: maintenance-information

The system could not initialize a queueless job request process.

(S)

Stops the scheduler service.

(O)

Determine the cause of the failure to initialize the queueless job request process according to the messages output before and after this message. Then, take proper action.

KAVS1907-E

The starting of a queueless job request process failed.: maintenance-information

The system could not start the queueless job request process. The possible causes include system resources becoming insufficient because more than one queueless job request process was started.

(S)

Stops the scheduler service.

(O)

Determine the cause of the failure to start the queueless job request process according to the messages output before and after this message. Then, take proper action.

KAVS1908-W

An attempt to acquire the queueless job function linkage option failed.: maintenance-information

The system could not obtain an environment setting parameter because the queueless job function linkage option specified in the environment setting parameter was invalid or because of some other error.

(S)

Starts the scheduler service without using the queueless job function. A queueless job, if any, executed in this condition ends in the Failed to start state.

(O)

Use the ajsqlsetup command to set up the queueless job function, and then restart the scheduler service.

If the queueless job function has been set up correctly, determine the cause of the error according to the messages output before and after this message. Then, take proper action.

For details on the ajsqlsetup command, see ajsqlsetup in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1909-E

The queueless job (job-name) cannot be executed.

The queueless job cannot be executed. The possible causes are:

The queueless job function has not been set up correctly.

The maximum number of concurrently-executable queueless job request processes is set to 0.

(S)

Sets the status of the queueless job to Failed to start.

(O)

Use the ajsqlsetup command to set up the queueless job execution environment, and then restart the scheduler service. If the QUEUELESSMULTIREQ environment setting parameter is set to 0, specify a value in the range from 1 to 8. Then, restart the scheduler service.

For details on the ajsqlsetup command, see ajsqlsetup in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1920-E

An error occurred during the starting of the queueless job request process (scheduler-service-name:identification-number).: maintenance-information

An error occurred when the queueless job request process was started.

(S)

Stops the queueless job request process.

(O)

Determine the cause of the failure to start the queueless job request process according to the messages output before and after this message. Then, take proper action.

KAVS1921-E

An attempt to connect with a queueless job execution agent (agent-name) failed.: maintenance-information

The system could not connect to the queueless job execution agent.

(S)

Sets the status of that job to Failed to start if the execution of a queueless job is requested.

If the status of a queueless job is inquired, the system sets the status of that job to Unknown end status.

If an operation on a job is requested, the system invalidates that operation.

(O)

Check that the queueless job execution agent has started correctly, and then re-execute the queueless job.

KAVS1922-W

The connection with the queueless job execution agent (agent-name) was closed.: maintenance-information

The connection to the queueless job execution agent was severed.

(S)

Reconnects the queueless job execution agent.

(O)

Determine the cause of the error according to the messages output by the manager and the agent. Then, take proper actions.

The communication encryption function might be disabled on the manager and enabled on the agent. Make sure that the communication encryption function is set correctly, and then restart the JP1/Base service and JP1/AJS3 service.

KAVS1923-E

A queueless job function cannot be used, processing to the job (job-name) cannot be performed.

The system cannot use a queueless job function, so it cannot process the job. The possible causes are:

The queueless job function has not been set up correctly.

The maximum number of concurrently-executable queueless job request processes is set to 0.

(S)

Sets the status of the job to Unknown end status.

(O)

Use the ajsqlsetup command to set up the queueless job execution environment, and then restart the scheduler service. If the QUEUELESSMULTIREQ environment setting parameter is set to 0, specify a value in the range from 1 to 8. Then, restart the scheduler service.

For details on the ajsqlsetup command, see ajsqlsetup in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1924-E

An attempt to reconnect with a queueless job execution agent (agent-name) failed.: maintenance-information

An attempt to reconnect with a queueless job execution agent has failed.

(S)

Places the job that was running on the relevant queueless job execution agent into Unknown end status status.

(O)

Determine the cause of the error from the messages on the manager and agent, and then take appropriate action.

KAVS1925-E

An attempt to forcibly terminate a queueless job (job-name) failed.

A communication error occurred while a queueless job was being forcibly terminated. Forced termination failed.

(S)

Stops forced termination of the job.

(O)

Retry forced termination of the job.

KAVS1926-E

A class name is specified for the execution destination host name of a Jobnet.

A class name is specified as the target host name of a jobnet.

(S)

Places the job into Failed to start status.

(O)

Remove the class name specified as the target host name, from the jobnet that includes this job.

KAVS1927-E

The queueless job definition is invalid.

The definition of the queueless job is invalid.

(S)

Places the job into Failed to start status.

(O)

Review the job definition.

When macro variables are used, the length of a definition item might exceed the maximum after substitution of macro variables.

Make sure that the lengths of the definition items do not exceed the maximum after substitution, and re-execute the job.

KAVS1928-I

The job at the agent (agent-name) was forcibly terminated.

The running job was forcibly terminated.

(S)

Cancels the requested processing.

KAVS1929-I

The communication with the queueless job execution agent (agent-name) was restored.

Communication with the queueless job execution agent indicated by agent-name has been restored.

(S)

If the message KAVS1922-W was output before this message, you need to check the status of the queueless job that was requested to be executed by the relevant agent. If the message KAVS1930-W was output, re-send the execution, forcible termination, or confirmation request that failed to be sent previously.

KAVS1930-W

Could not connect with the queueless job execution agent (agent-name). Reconnection processing started. : maintenance-information

The queueless job execution agent indicated by agent-name could not be connected, so the re-connection processing started.

If this message is output, the probable causes are:

A network error has occurred (for example, the manager or agent host has not been connected to the LAN).

The agent host name cannot be resolved.

The load for the agent is high, so the connection request cannot be processed.

There was insufficient memory available.

The port number (jplajs2qlag) on the agent for queueless job execution has been set incorrectly.

The queueless job execution agent or the agent host itself has stopped.

(S)

Performs reconnection processing to resend the request for execution, forcible termination, or confirmation, which failed to be sent previously. After this message is output, the system manages the agent as an error agent. The system queues requests to the error agent, and then performs the re-connection processing in the same order as requested.

Although the timeout period for re-connection processing depends on the OS, the maximum period for terminating re-connection processing is specified by the environment setting parameter (REQDAGTRECONNECTTIMEOUT) for which the timeout period of communication recovery processing is set.

The system attempts re-connection twice every 60 seconds, but if the connection cannot be recovered, the system outputs the following error messages in accordance with the processing request, and finally the request is terminated:

Job execution request : KAVS1931-E

Job forcible termination request : KAVS1932-E

Job confirmation request : KAVS1933-E

If reconnection is successful, the system outputs the KAVS1929-I message and then resends the queued requests in sequence to recover from the error.

(O)

Check the logs for the manager host and the agent host, and the network status.

Remove the cause of the connection error.

KAVS1931-E

Could not send the job execution request because an attempt to reconnect with the queueless job execution agent (agent-name) failed. : maintenance-information

Communication with the queueless job execution agent as indicated by agent-name was not recovered, so an attempt to send the job execution request failed.

The probable causes are as follows:

A communication error occurred.

An agent host on which JP1/AJS3 - Agent Minimal Edition is installed is specified as the queueless job execution agent.

(S)

Terminates the job execution request, and then sets the job status to Failed to start.

(O)

Check the network status, and the logs for the manager host and the agent host. Then remove the cause of the connection error.

You cannot execute queueless jobs on an agent host on which JP1/AJS3 - Agent Minimal Edition is installed. Check the job definition, and then change the value of Exec. Service to Standard or change the queueless job execution agent.

KAVS1932-E

Could not forcibly terminate the job (job-name) because an attempt to reconnect with the queueless job execution agent (agent-name) failed. : maintenance-information

Communication with the queueless job execution agent indicated by agent-name has not recovered, so an attempt to request forcible termination of a job has failed.

(S)

Terminates the forcible job termination request.

(O)

Check the logs for the manager host and the agent host, and the network status.

Remove the cause of the connection error, and then re-request the job execution if necessary.

KAVS1933-E

Could not confirm the job status because an attempt to reconnect with the queueless job execution agent (agent-name) failed. : maintenance-information

Communication with the queueless job execution agent indicated by agent-name has not been recovered, so an attempt to check the job status failed.

(S)

Terminates the job status check request, and then sets the job status to Unknown end status.

(O)

Check the logs for the manager host and the agent host, and the network status.

Remove the cause of the connection error, and then re-request the job execution if necessary.

KAVS1939-E

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.

KAVS1940-E

An attempt to initialize the job-ID acquisition processing failed.: maintenance-information

An error occurred when the job ID acquisition process was initialized.

(S)

Cancels the initialization of the job ID acquisition process.

(O)

Contact the system administrator, and determine the cause of the error according to maintenance-information. If you cannot determine the cause, collect data (see 1.2.3 To the system administrators).

KAVS1941-E

The user does not have permission to access the job-ID management file. (file-name)

The right permission is not specified for the job ID management file.

(S)

Cancels the initialization of the job ID acquisition process.

(O)

Specify the right permission for the job ID management file. Alternatively, use the ajsqlsetup command to re-create a job ID management file.

For details on the ajsqlsetup command, see ajsqlsetup in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1942-E

The job-ID management file (file-name) data is invalid.

The data in the job ID management file is invalid.

(S)

Cancels the initialization of the job ID acquisition process.

(O)

Use the ajsqlsetup command to re-create a job ID management file. Then, restart the scheduler service by a cold start.

For details on the ajsqlsetup command, see ajsqlsetup in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1943-E

The job-ID management file (file-name) does not exist.

The job ID management file does not exist.

(S)

Cancels the initialization of the job ID acquisition process.

(O)

Use the ajsqlsetup command to re-create a job ID management file. Then, restart the scheduler service by a cold start.

For details on the ajsqlsetup command, see ajsqlsetup in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1952-E

An attempt to acquire the port information of the queueless agent service failed. (service name: service-name)

The system cannot read information about the port to be connected.

(S)

Cancels command execution.

(O)

Define port information correctly, and then re-execute the command.

KAVS1953-E

The status file specified by the queueless agent environment setup cannot be accessed.

An attempt to open or access the status file has failed due to one of the following causes:

The disk does not have sufficient free space.

Memory is insufficient.

The user who started the queueless agent service does not have read permission for the status file.

The user who started the queueless agent service does not have write permission for the directory in which the status file is to be created.

A directory having the same name as the status file has already been created in the directory in which the status file is to be created.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

(O)

If this message appears during command execution, correct the error and then re-execute the command.

If this message is output for the queueless cluster process, correct the error and then restart the JP1/AJS3 service on the logical host that caused the error.

Example: In this example, the command attaches the logical host Lhost:

Execute the ajsqlattach command as follows:

  ajsqlattach -h Lhost

For details on the ajsqlattach command, see ajsqlattach in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1954-E

The number of already registered logical hosts has reached the maximum, so additional registration is not possible.

A new logical host cannot be attached because the number of logical hosts attached to the queueless agent service has reached the maximum, that is, 10.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

(O)

Execute the ajsqldetach command to detach the logical host on which no queueless job is being executed, and then execute the ajsqlattach command to re-attach the logical host that caused the error.

If the logical hosts are attached directly from the queueless cluster process, restart the JP1/AJS3 service on the logical host that caused the error.

Examples:

In this example, the command detaches the logical host Lhost.

Execute the ajsqldetach command as follows:

ajsqldetach -h Lhost

For details on the ajsqldetach command, see ajsqldetach in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

In this example, the command attaches the logical host Lhost.

Execute the ajsqldetach command as follows:

ajsqlattach -h Lhost

For details on the ajsqlattach command, see ajsqlattach in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1955-E

The specified host (host-name)has already been attached.

The specified host indicated in host-name has already been attached.

(S)

Cancels command execution.

(O)

Execute the ajsqlstatus command to check the status of the host indicated in host-name. If the host indicated in host-name has been detached, execute the ajsqlattach command to attach this host.

Examples:

In this example, the command outputs detailed information for the logical host Lhost.

Execute the ajsqlstatus command as follows:

ajsqlstatus -h Lhost

For details on the ajsqlstatus command, see ajsqlstatus in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

In this example, the command attaches the logical host Lhost.

Execute the ajsqlattach command as follows:

ajsqlattach -h Lhost

For details on the ajsqlattach command, see ajsqlattach in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1956-E

An attempt to read the configuration definition failed.

An attempt to read the environment setting parameter has failed.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

(O)

Confirm that the host name and IP address of the host that executes queueless jobs are correctly registered in the DNS settings, hosts file, jp1hosts file, or jp1hosts2 file. At the same time, make sure that memory is sufficient, and then execute the ajsqlattach command to re-attach the logical host that caused the error. If the logical hosts are attached from the queueless cluster process, restart the JP1/AJS3 service on the logical host that caused the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

Example: In this example, the command attaches the logical host Lhost.

Execute the ajsqlattach command as follows:

  ajsqlattach -h Lhost

For details on the ajsqlattach command, see ajsqlattach in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1957-E

The number of simultaneous job executions is invalid.

The maximum number of concurrently executable jobs is invalid.

(S)

Cancels command execution.

(O)

Specify a value in the range from 0 to 1,024 for the maximum number of concurrently executable jobs, and then re-execute the command.

KAVS1958-E

The number of jobs waiting for execution is invalid.

The maximum number of jobs waiting for execution is invalid.

(S)

Cancels command execution.

(O)

Specify a value in the range from 0 to 102,400 for the maximum number of jobs waiting for execution, and then re-execute the command.

KAVS1959-E

An attempt to acquire the port information for file transmission failed. (service name: service-name)

The system cannot read information about the port to be connected.

(S)

Cancels command execution.

(O)

Define port information correctly, and then re-execute the command.

KAVS1960-E

Specify the logical host name when you specify the class name.

A logical-host name and a class name are not specified together.

(S)

Cancels command execution.

(O)

When you specify a logical host name in the command, specify the logical host name and a class name together, and then re-execute the command.

KAVS1961-E

The candidate host (host-name) is not attached.

The specified logical host indicated in host-name is not attached.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

(O)

Make sure that the target host indicated in host-name exists. If the host indicated in host-name does not exist, create it.

KAVS1962-E

The command cannot be executed because the target host (host-name) is being detached.

The command cannot be executed, because the target host indicated in host-name is being detached.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

If the processing to detach the logical host has been canceled, the system abnormally terminates the queueless cluster process.

(O)

If this message is output when the ajsqlattach command is executed, execute the ajsqlstatus command to make sure that the target host indicated in host-name has already been detached. Then re-execute the ajsqlattach command.

If this message is output when the queueless cluster process is being started, execute the ajsqlstatus command to make sure that the target host indicated in host-name has already been detached. Then restart the JP1/AJS3 service on the target host indicated in host-name.

If this message is output when the queueless cluster process is being stopped or when the ajsqldetach command is executed, no action is required.

Example: In this example, the command outputs detailed information for the logical host Lhost.

Execute the ajsqlstatus command as follows:

  ajsqlstatus -h Lhost

For details on the ajsqlstatus command, see ajsqlstatus in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1963-E

A job (job-name) was not executed because the target host (host-name) will be detached.

The queueless job indicated in job-name that is waiting for execution cannot be executed because the attached target host indicated in host-name is being detached.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Execute the ajsqlattach command to attach the target host indicated in host-name, and then re-execute the queueless job indicated in job-name that is placed into Failed to start status.

Example: In this example, the command attaches the logical host Lhost.

Execute the ajsqlattach command as follows:

  ajsqlattach -h Lhost

For details on the ajsqlattach command, see ajsqlattach in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1964-E

A job (job-name) was not executed because queueless agent will now stop.

The queueless job indicated in job-name that is waiting for execution cannot be executed because the queueless agent service will stop.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Restart the queueless agent service, and then re-execute the queueless job indicated in job-name that is placed into Failed to start status.

KAVS1965-I

The queueless log file (file-name-before-change) has been changed to file-name-after-change.

The queueless log file will be switched to a new queueless log file, because its current size has exceeded the maximum specified in an environment parameter.

(S)

Continues processing.

(O)

If necessary, back up the current queueless log file.

KAVS1966-I

The queueless cluster process (logical-host-name) received a forced termination request from the start daemon.

The queueless cluster process on the logical host (logical-host-name) received a forced termination request from the JP1/AJS3 startup process (jajs_spmd).

(S)

Forcibly terminates the running queuless job on the logical host, and then detaches the logical host indicated in the message. The queueless cluster process stops when the logical host has been detached.

KAVS1967-I

The queueless cluster process (logical-host-name) received a planned termination request from the start daemon.

The queueless cluster process on the logical host (logical-host-name) received a planned termination request from the JP1/AJS3 startup process (jajs_spmd).

(S)

Waits until the running queuless job on the logical host terminates, and then detaches the logical host indicated in the message. The queueless cluster process stops when the logical host has been detached.

KAVS1968-I

The queueless cluster process (logical-host-name) received a restriction stop request from the start daemon.

The queueless cluster process on the logical host (logical-host-name) received a restrictive termination request from the JP1/AJS3 startup process (jajs_spmd).

(S)

Forcibly terminates the running queuless job on the logical host, and then detaches the logical host indicated in the message. The queueless cluster process stops when the logical host has been detached.

KAVS1969-I

The queueless cluster process (logical-host-name) will now stop.

The queueless cluster process on the logical host (logical-host-name) will now terminate.

(S)

Terminates the queueless cluster process indicated in logical-host-name.

KAVS1970-I

The queueless cluster process (logical-host-name) has ended.

The queueless cluster process on the logical host (logical-host-name) has terminated.

(S)

Terminated the queueless cluster process indicated in logical-host-name.

KAVS1971-E

An execution file (file-name) was not found, so the job (job-name) execution was not possible.

The system could not execute the queueless job indicated in job-name because the executable file indicated in file-name was not found.

(S)

Places the queueless job indicated in job-name in the Failed to start status.

(O)

Make sure that the executable file indicated in file-name exists and that the file name has no more than 254 characters, and then re-execute the queueless job (job-name) that failed to start.

KAVS1972-E

The execution file (file-name) was invalid, so the job (job-name) execution was not possible.

The system could not execute the queueless job indicated in job-name because the executable file indicated in file-name was invalid.

(S)

Places the queueless job indicated in job-name in the Failed to start status.

(O)

Make sure that the executable file indicated in file-name can be executed, and then re-execute the queueless job that is placed into Failed to start status.

KAVS1973-E

The resources required for execution are insufficient, so the job (job-name) execution was not possible.

The system could not execute the queueless job indicated in job-name because resources necessary for execution were insufficient.

(S)

Places the queueless job indicated in job-name in the Failed to start status.

(O)

The probable causes of the error in the queueless job indicated in job-name are:

Memory was insufficient.

The disk did not have sufficient free space.

The size of the desk top heap was insufficient.

Correct the cause of the error, and then re-execute the queueless job that is placed into Failed to start status.

KAVS1974-E

The job (job-name) could not be executed because the user does not have the required permission for execution.

The system could not execute the queueless job indicated in job-name because the account of the queueless agent service did not have permissions required for executing the queueless job.

(S)

Places the queueless job indicated in job-name in the Failed to start status.

(O)

Specify permissions required for executing the job in the account of the queueless agent service, and then re-execute the queueless job that is placed into Failed to start status.

For details about permissions that must be set for the account, see 4.2.3 Changing the JP1/AJS3 service settings (Windows only) in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVS1975-E

The disk capacity was insufficient, so a job (job-name) could not be performed. : maintenance-information

The system could not execute the queueless job indicated in job-name because the required disk space was not available.

(S)

Places the queueless job indicated in job-name in the Failed to start status.

(O)

Allocate sufficient free space on the disk, and then re-execute the queueless job indicated in job-name that is placed into Failed to start status.

KAVS1976-E

No right is granted to access the execution file (file-name).

The queueless job could not be executed because the OS user who executed the queueless job indicated in job-name did not have access permission for the executable file indicated in file-name.

(S)

Places the queueless job in the Failed to start status.

(O)

Make sure that the OS user who executes the queueless job has read and execution permissions for the executable file indicated in file-name, and then re-execute the queueless job that is placed into Failed to start status.

KAVS1977-E

No free space is available on the disk.: (maintenance-information-1) (maintenance-information-2)

The directory or file indicated in maintenance-information-1 cannot be created due to insufficient free space on the disk.

(S)

Does not create a directory or file indicated in maintenance-information-1.

(O)

Check the space available on the disk, and then re-execute the processing that caused the error.

KAVS1978-E

The forced termination of a job(job-name) failed. (process-ID) (maintenance-information)

An attempt to forcibly terminate or cancel the queueless job indicated in job-name has failed.

(S)

Continues processing.

(O)

Retry forced termination of the queueless job indicated in job-name. If the forced termination fails again, manually terminate the queueless job indicated in job-name by using Task Manager in Windows or the kill command or another means in UNIX from the process-ID.

KAVS1979-E

The job is of a format that the destination execution host (host-name) cannot accept.

Since an attempt was made to execute a PC job on a UNIX host or execute a Unix job on a Windows host, the attempt to execute the job on the agent host indicated in host-name has failed.

(S)

Places the queueless job in the Failed to start status.

(O)

As the host on which the job is to be executed, specify a Windows host for a PC job or specify a UNIX host for a Unix job. Then, re-execute the queueless job that resulted in the error.

KAVS1980-I

The detach processing for the logical host (host-name) has been changed from planned detach to forced detach.

The detach processing for the logical host indicated in host-name has been changed from planned detach to forced detach.

(S)

Performs forced detach processing.

KAVS1981-I

The logical host (host-name) was attached.

The system accepted a request from the ajsqlattach command or queueless cluster process and attached the logical host indicated in host-name.

(S)

Enables the queueless job to be executed on the logical host indicated in host-name.

KAVS1982-I

The logical host (host-name) was detached.

The system accepted a request from the ajsqldetach command or queueless cluster process and detached the logical host indicated in host-name.

(S)

Prevents the queueless job from being executed on the logical host indicated in host-name.

KAVS1983-I

The execution environment settings are (execution-environment, Number of simultaneously executable jobs=number-of-simultaneously-executable-jobs, Number of jobs waiting for execution=number-of-jobs-waiting-for-execution).

The system accepted a request from the ajsqlalter command and updated the environment for the host indicated in host-name.

(S)

Updates the environment for the host indicated in host-name. If the maximum number of concurrently executable jobs and the maximum number of jobs waiting for execution remain unchanged, the system outputs the values specified before the changes were made.

KAVS1984-I

maintenance-information

A request for submitting a queueless job was accepted. For details about maintenance information, see C.2 Log entries output by the queueless agent service in the manual JP1/Automatic Job Management System 3 Troubleshooting.

(S)

Continues processing.

KAVS1985-E

The setup of the queueless job execution environment could not be updated.: maintenance-information-1 maintenance-information-2 maintenance-information-3

The system could not update the settings of the queueless job execution environment because the ajsqlsetup command could not be executed.

(S)

Cancels command execution.

(O)

If the ajsqlsetup command is executed in the terminal service environment running in application execution mode or the remote desktop environment running in application execution mode, an error occurs and this message is output. Execute the ajsqlsetup command in the following procedure:

Open the command prompt and execute the change user command with the /query option specified.

Check the execution result to make sure that the current execution mode is application execution mode.

Execute the change user command with the /install option specified to change the execution mode to application installation mode.

Execute the ajsqlsetup command.

Execute the change user command with the /execute option specified to return the execution mode to application execution mode.

For details on the change user command, see Windows Help.

For other cases, the cause of the error might be insufficient memory or insufficient disk space. Correct the error and then re-execute the ajsqlsetup command.

If you cannot correct the problem, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

For details on the ajsqlsetup command, see ajsqlsetup in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1986-E

Access permission for the services file is not granted, so the port information cannot be registered.

Setup of the queueless job execution environment or the environment for running the definition pre-check function is canceled because you did not have permission to write to the services file and could not register port information.

(S)

Cancels command execution.

(O)

Check whether the OS user who executed the command has logged on as a user who has administrator privileges (in Windows) or superuser privileges (in UNIX), and has write permission for the services file. Then re-execute the command.

KAVS1987-I

The service (service-name) stopped.

This message indicates that the system will stop the service indicated in service-name.

(S)

Stops the service indicated in service-name.

KAVS1988-E

The specified class name (class-name) does not exist.

The specified class name indicated in class-name does not exist.

(S)

Cancels command execution.

(O)

Specify an existing class name, and then execute the command.

KAVS1989-E

The operation is not possible because the service (service-name) is not running.

The service indicated in service-name has not started, so command operation cannot be performed.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

If the processing to detach the logical host has been canceled, the system abnormally terminates the queueless cluster process.

(O)

Check that the service has started, and then execute the command.

If the service has started, wait a while and then retry the operation. If the retry does not correct the error, contact the system administrator and collect data (see 1.2.3 To the system administrators).

You can use either of the following methods to check whether the service has started:

In Windows:

In Control Panel or Administrative Tools, double-click Services, and check the status of the service.

In UNIX:

Use the ps command to make sure that the service for the process exists.

For details about the process that you should check, see B.3 Processes (for UNIX) in the manual JP1/Automatic Job Management System 3 Troubleshooting.

If this message is output when the queueless cluster process is being started, wait until the service has started, and then take either of the following actions to attach the logical host:

Restart the JP1/AJS3 service.

Use the ajsqlattach command to attach the logical host.

If this message is output when the queueless cluster process is being stopped, no action is necessary because the service has already stopped.

KAVS1990-E

An error occurred during the communication with the service (service-name) because a network access error occurred.: maintenance-information

A network access error occurred during communication with the service indicated in service-name.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

If the processing to detach the logical host has been canceled, the system abnormally terminates the queueless cluster process.

(O)

Execute the ping and jp1ping commands to make sure that communication with the service indicated in service-name is possible. If communication is not possible, confirm that the host name and IP address of the host that executes queueless jobs are correctly registered in the DNS settings, hosts file, jp1hosts file, or jp1hosts2 file.

After taking the above actions, re-execute the command that resulted in the error. If the error occurred when the queueless cluster process was being started, restart the JP1/AJS3 service.

If the error occurred when the queueless cluster process was being stopped, execute the ajsqldetach command to detach the logical host that caused the error.

If you cannot correct the problem, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1991-E

A communication timeout occurred during the communication with the service (service-name).: maintenance-information

A communication timeout error occurred during communication with the service indicated in service-name.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

If the processing to detach the logical host has been canceled, the system abnormally terminates the queueless cluster process.

(O)

A timeout might have occurred due to high load on the network or machine. Use Task Manager in Windows or the top command or another means in UNIX to check the status of the network and machine. Then re-execute the command that resulted in the error.

If the error occurred when the queueless cluster process was being started, restart the JP1/AJS3 service.

If the error occurred when the queueless cluster process was being stopped, execute the ajsqldetach command to detach the logical host that caused the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1992-E

The connection was reset during the communication with the service (service-name).: maintenance-information

The connection was reset during communication with the service.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

If the processing to detach the logical host has been canceled, the system abnormally terminates the queueless cluster process.

(O)

The connection might have been disconnected due to a network failure. Execute the ping and jp1ping commands to make sure that communication with the service indicated in service-name is possible. If the connection is impossible, check the communication environment to correct the cause of the error. Then, re-execute the command that resulted in the error.

If the error occurred when the queueless cluster process was being started, restart the JP1/AJS3 service.

If the error occurred when the queueless cluster process was being stopped, execute the ajsqldetach command to detach the logical host that caused the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1993-E

A buffer shortage occurred during the communication with the service (service-name).: maintenance-information

The available buffer became insufficient during communication with the service.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

If the processing to detach the logical host has been canceled, the system abnormally terminates the queueless cluster process.

(O)

The probable causes of the error include high load on the network and insufficient memory. Check the status of the network and memory, and then re-execute the command that resulted in the error.

If the error occurred when the queueless cluster process was being started, restart the JP1/AJS3 service.

If the error occurred when the queueless cluster process was being stopped, execute the ajsqldetach command to detach the logical host that caused the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1994-E

Database file install directory is invalid.: (directory-name) (return-code)

The directory path specified in AJSDBDIRECTORY is incorrect. Alternatively, if the primary node of a cluster is being set up, the shared disk may have not been mounted.

(S)

Cancels command execution.

(O)

Check the directory path specified in AJSDBDIRECTORY. If this message appears during setup of the primary node of a cluster, check whether the shared disk has been mounted.

After completing the above checks, re-execute the setup command.

KAVS1995-E

The command ended because an attempt to get the detailed information of the queueless agent service failed.

The command ended, because an attempt to acquire the detailed information for the queueless agent service has failed.

(S)

Cancels command execution.

(O)

Resolve the problem, following the instructions given in the message that was output before this one. Then, re-execute the command.

KAVS1996-I

The system has been switched from planned detach to forced detach, and the target host (host-name) has been detached. The command will now end.

The command will terminate because the detach mode has changed from planned detach to forced detach and the target host (host-name) has been detached.

(S)

Terminates the command.

KAVS1997-E

No authority for file(file-name).

The OS user who executed the command does not have permission to read or write the file indicated in file-name.

(S)

Cancels command execution.

(O)

Assign read or write permission for the file indicated in file-name to the OS user who executed the command, and then re-execute the command.

KAVS1998-E

The command cannot be executed because the processing is restricted.

One of the following services is being stopped, so the system cancels the command:

Queueless agent service

Queueless file transfer service

(S)

Cancels the command.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

If the processing to detach the logical host has been canceled, the system abnormally terminates the queueless cluster process.

(O)

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

If this message is output when the queueless cluster process is being started, execute the ajsqlstatus command to make sure that the target host indicated in host-name has stopped, and then restart the JP1/AJS3 service on the target host indicated in host-name.

If this message is output when the queueless cluster process is being stopped or when the ajsqldetach command is executed, no action is required.

Example: In this example, the command outputs detailed information for the logical host Lhost.

Execute the ajsqlstatus command as follows:

  ajsqlstatus -h Lhost

For details on the ajsqlstatus command, see ajsqlstatus in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS1999-E

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:execution-destination:maintenance-information)

An attempt to execute a job failed because the specified execution host is not permitted in the execution agent profile.

(S)

Ends the job abnormally in failed to start status.

(O)

The probable causes are as follows:

The wrong host name is specified as the execution agent in the detailed definition of the job.

The execution host name is specified incorrectly in the execution agent profile.

If the wrong execution host name is specified in the detailed definition of the job, specify the correct host name and then re-execute the job.

If the execution agent profile is configured incorrectly, correct the error. Then, use the ajsprofalter command to apply the corrected profile to the scheduler service, and execute the job again.

KAVS2030-I

Scheduler service (logical-host-name:scheduler-service-name) export started.

Export of the scheduler service will now start.

(S)

Continues processing.

KAVS2031-I

Scheduler service (logical-host-name:scheduler-service-name) export ended normally.

Export of the scheduler service terminated normally.

(S)

Continues processing.

KAVS2032-E

Scheduler service (logical-host-name:scheduler-service-name) export ended abnormally. maintenance-information

Export of the scheduler service terminated abnormally.

(S)

Cancels processing.

(O)

Take action according to the message that was output before or after this error message.

KAVS2033-I

Scheduler service (logical-host-name : scheduler-service-name) import started.

Import of the scheduler service will now start.

(S)

Continues processing.

KAVS2034-I

Scheduler service (logical-host-name : scheduler-service-name) import ended normally.

Import of the scheduler service terminated normally.

(S)

Continues processing.

KAVS2035-W

Scheduler service (logical-host-name : scheduler-service-name) import ended with warning. maintenance-information

Import of the scheduler service terminated with warning.

(S)

Continues processing even though some information cannot be transferred.

(O)

Take action according to the message that was output before or after this error message.

KAVS2036-E

Scheduler service (logical-host-name : scheduler-service-name) import ended abnormally. maintenance-information

Import of the scheduler service terminated abnormally.

(S)

Cancels processing.

(O)

Take action according to the message that was output before or after this error message.

KAVS2037-I

Table (table-name) export started.

Export of the table will now start.

(S)

Continues processing.

KAVS2038-I

Table (table-name) export ended.

Export of the table terminated.

(S)

Continues processing.

KAVS2039-I

Table (table-name) import started.

Import of the table will now start.

(S)

Continues processing.

KAVS2040-I

Table (table-name) import ended.

Import of the table terminated.

(S)

Continues processing.

KAVS2041-E

Environment setting parameters could not be obtained. maintenance-information

The environment setting parameters cannot be obtained.

(S)

Cancels processing.

(O)

Correct the error in the environment settings according to the message that was output before or after this error message, and then re-execute the command.

KAVS2045-I

number-of-items items were exported.

Export of the number of items indicated in number-of-items is completed.

(S)

Continues processing.

KAVS2046-I

number-of-processed-items out of total-number-of-items items were imported.

Export of the number of items indicated in number-of-items-processed in total-number-of-items is completed.

(S)

Continues processing.

KAVS2060-E

Embedded DB operation failed. (setup-identifier)(host-name)

The database management process was unable to perform an embedded database operation.

(S)

Terminates processing.

(O)

The probable causes are below. Take action according to the cause of the error.

Cause 1

The JP1/AJS3 service was started while the JP1/AJS3 Database service was being stopped.

Action

If you are performing JP1/AJS3 Database service operations manually, stop the JP1/AJS3 Database service, and then start the JP1/AJS3 service.

If the embedded database is being stopped, start the JP1/AJS3 service after you confirm that the embedded database has stopped.

Cause 2

The JP1/AJS3 Database service was stopped while the JP1/AJS3 service was being started.

Action

Do not perform JP1/AJS3 Database service operations or start or stop the embedded database while the JP1/AJS3 service is being started.

Stop the JP1/AJS3 Database service or embedded database, and then start the JP1/AJS3 service.

Cause 3

The embedded database was forced to terminate while the JP1/AJS3 service was being started.

Action

See the action for cause 2.

Cause 4

The JP1/AJS3 Database service was started while the JP1/AJS3 service was being stopped.

Action

Do not start the JP1/AJS3 Database service while the JP1/AJS3 service is being stopped.

If the JP1/AJS3 Database service or embedded database was not stopped by stopping the JP1/AJS3 service, stop it separately.

Cause 5

The JP1/AJS3 Database service was stopped while the JP1/AJS3 service was running.

Action

Do not perform JP1/AJS3 Database service operations while the JP1/AJS3 service is running.

If the JP1/AJS3 service terminated abnormally, restart it.

If some JP1/AJS3 service processes have started, stop the JP1/AJS3 service, and then restart it.

Cause 6

An error occurred in the embedded database while the JP1/AJS3 service was being started, being stopped, or while it was running.

Action

Take action as described in 2.7 Troubleshooting problems related to the embedded database in the manual JP1/Automatic Job Management System 3 Troubleshooting.

If you cannot correct the problem, collect data and then contact the system administrator (see 1.2.3 To the system administrators).

KAVS2101-E

Embedded service is inactive.

The embedded database is not running.

(S)

Cancels command execution.

(O)

Make sure that the embedded database has started. Execute the ajsembdbstatus -s ust command to check the status of the embedded database.

KAVS2102-E

Starting/terminating the embedded service.

The embedded database is being started or stopped.

(S)

Cancels command execution.

(O)

Check the start or stop status of the embedded database. Execute the ajsembdbstatus -s ust command to check the status of the embedded database.

KAVS2103-E

Embedded service is active.

The embedded database is running.

(S)

Cancels command execution.

(O)

Make sure that the embedded database has stopped. Execute the ajsembdbstatus -s ust command to check the status of the embedded database.

KAVS2104-E

Embedded service is not set up.

The embedded database has not been set up. Either the embedded database has not been set as the scheduler service database, or the setup ID specified in -id is invalid.

(S)

Cancels command execution.

(O)

Check whether the value of the setup ID specified in -id is correct. Alternatively, use the ajsstatus command to check whether the embedded database has been set as the scheduler service database.

KAVS2105-E

Specified file group (log-file-group-name) does not exist.

The specified log file group does not exist. The log file group name specified in the -g option of the ajsembdboplog command is incorrect.

(S)

Cancels command execution.

(O)

Recheck the specified log file group.

KAVS2106-E

Failed to unload.

An unloading attempt failed. The log file group specified in the ajsembdboplog -g command is being used. Alternatively, the directory specified in the ajsembdbrorg -d command does not have sufficient free space.

(S)

Cancels command execution.

(O)

Execute the ajsembdbstatus -s prc command to make sure that the command you executed has stopped, and then retry.

If the ajsembdboplog command is being executed, use the ajsembdbstatus -l command to make sure that the specified log file group is not being used.

If the ajsembdbrorg command is being executed, check the amount of free space in the directory specified in -d.

KAVS2107-E

Failed to reload.

A reloading attempt failed. This message appears when the embedded database does not have sufficient space during execution of the ajsembdbrorg -k reld command.

(S)

Cancels command execution.

(O)

Execute the ajsembdbstatus -s prc command to make sure that the command you executed has stopped, and then retry.

When unloaded data is reloaded, the embedded database allocates the space required for the operation, sometimes resulting in a shortage of free space in the area that was used before unloading. If this problem occurs, execute the ajsembdbreclaim command to reclaim area that has become invalid, and then re-execute the command. If the ajsembdbreclaim command is unable to reclaim enough area, you must add area.

KAVS2108-E

Invalid Embedded service definition.

The environment of the embedded database does not permit execution of the command. To execute the ajsembdboplog -r -t command, ajsembdbbuild -bl must have been specified for this environment.

(S)

Cancels command execution.

(O)

Check the environment of the embedded database on which you want to execute the command. If ajsembdbbuild -bl was not specified when the environment was created, consider creating the environment of the embedded database again.

KAVS2109-E

Specified file (file-name) exists.

An attempt to create a file has failed. This message appears when an existing file is specified in the -o option of the ajsembdboplog command.

(S)

Cancels command execution.

(O)

Either change the specified file name or delete the existing file, and then re-execute the command.

KAVS2113-E

Failed to read the configuration definition.

An attempt to read the configuration definition has failed. The configuration definition required for operation of the embedded database has not been set. This message appears when the embedded practical directory for the scheduler database cannot be acquired during execution of a data collection tool.

(S)

Cancels command execution.

(O)

Use the ajsstatus command to check whether the embedded database is set as the scheduler service database. If the embedded database is set as the scheduler service database, check whether the setup ID has been set. If the setup ID is not set correctly, use the jbssetcnf command to set it.

KAVS2114-E

Cannot create directory or file (directory-name or file-name).

An attempt to create a directory or file has failed because you do not have permissions for the directory. This message appears when you do not have permissions for the following directories during execution of a data collection tool:

In Windows:

%TEMP%\jp1ajs2\backlog

In UNIX:

/tmp/jp1ajs2/trouble/

(S)

Cancels command execution.

(O)

Assign permissions on the specified directory, and then retry.

KAVS2115-E

Embedded service is not installed.

The embedded database is not installed. The embedded database registered with the setup ID specified in -id might have been uninstalled. Alternatively, the environment might have been deleted.

(S)

Cancels command execution.

(O)

Check the environment of the embedded database registered with -id. If the embedded database has been uninstalled, install the embedded database and set it up. After setup, re-set the embedded database as the scheduler service database.

If the environment of the embedded database has been deleted, set up the embedded database and then re-set the embedded database as the scheduler service database.

KAVS2116-E

There is an error in the specified option.

detailed-information

USAGE

The specified option contains an error.

One of the following is indicated in detailed-information:

Options (option) are needed.

The mandatory or necessary option was not found.

Illegal option (option) exists.

An invalid option is specified.

Extra option (option) exist.

An extra option is specified.

Invalid value for option (option).

The value of the option is invalid.

If -F is indicated in (option), the logical host specified for the -mh option might be invalid. If either or both of -F or -mh is not specified, check the following:

- If -F is not specified, check the AJSCONF environment variable or the DEFAULTSERVICENAME environment setting parameter.

- If -mh is not specified, check the JP1_HOSTNAME environment variable.

Value of option (option) exceeds prescribed length.

The value of the option exceeds the prescribed length.

Value of option (option) is not specified.

The value of the option is not specified.

Option (option) appears twice or more.

The option indicated in option is specified more than once.

No unload file.

There is no unload file.

Cannot specify these options (option) together.

Options that cannot be specified together are specified.

(S)

Cancels command execution.

(O)

Check the option and then retry.

KAVS2117-E

An error has occurred in the command-name command. maintenance-information

An error occurred during execution of the command.

(S)

Cancels command execution.

(O)

See the message output in the maintenance information.

For operations performed by an AJS administrator, permissions for the specified directory or file might be insufficient. Check the access permissions for the specified directory or file. For details about required permissions, see C.2 Access permissions for directories or files required for command operations by the AJS administrator in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS2118-Q

Could not stop the embedded service. Continue process? (y/n)

This message asks you whether you want to continue the processing. If you continue the processing while the embedded database is not stopped, an error occurs and the processing is canceled.

(S)

Waits for a response.

(O)

Execute the ajsembdbstatus -s command to check the status of the embedded database. Make sure that the embedded database has stopped, and then enter y to continue the processing. To cancel the processing, enter n.

If you enter anything other than y or n, the processing is canceled as if you had entered n.

KAVS2119-E

Specified directory (directory-name) does not exist.

The directory part of the output destination file name specified in the -o option of the ajsembdboplog command contains an error.

(S)

Cancels command execution.

(O)

Check and, if necessary, correct the output destination file name (full path specification) specified in the -o option, and then re-execute the command.

KAVS2120-E

A log group cannot add.

A log file group cannot be added because the number of log file groups created will exceed the maximum. For details on the maximum number of log file groups that can be created, see ajsembdbaddlog in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

(S)

Cancels command execution.

(O)

Check the number of log files.

KAVS2121-E

Database file already exists.

The file name of the file for the database area you attempted to create already exists. The file name already exists in the directory specified in the -d option of the ajsembdbaddlog or ajsembdbaddarea command.

(S)

Cancels command execution.

(O)

Re-execute the command.

KAVS2122-E

A temporary file already exists.

A temporary file that has the same name as the file that you attempted to create by using the embedded database operation command already exists.

(S)

Cancels command execution.

(O)

Re-execute the command.

KAVS2123-E

Embedded DB version is invalid.

The version of the embedded database must be a prerequisite version for JP1/AJS3.

(S)

Cancels command execution.

(O)

Upgrade the version of the embedded database to a prerequisite version for JP1/AJS3.

KAVS2124-E

Failed in construction of EmbedDB server.

An attempt to construct an embedded database server has failed.

(S)

Cancels command execution.

(O)

Take action according to the instructions given by the message that was output before this message. Then execute the ajsembdbunset command with the -i option specified to delete the environment of the embedded database, and then execute the ajsembdbbuild command. For details about the error messages and the applicable actions, see Actions to be taken if an error occurs in the ajsembdbbuild in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS2125-E

Cannot create directory or file.

The directory or file cannot be created because, for example, you do not have access permission for the embedded database practical directory.

(S)

Cancels command execution.

(O)

Check whether you have write permission for the embedded database practical directory. Also check whether the disk has sufficient free space.

KAVS2126-E

Embedded setup environment already exists.

The specified embedded database practical directory has already been associated with another setup ID.

(S)

Cancels command execution.

(O)

Make sure that the specified embedded database practical directory is associated correctly.

Use the ajsembdbidlist command to check the association between the embedded database practical directory and the setup ID.

KAVS2127-E

An error has occurred in the command (command-name). : maintenance-information

An error occurred in the command for the embedded database.

(S)

Terminates processing.

(O)

If an attempt to install JP1/AJS3 has failed, take appropriate action for the code and message indicated in maintenance-information according to the 2.7.8(4) Action to be taken if an error occurs during embedded database setup in the manual JP1/Automatic Job Management System 3 Troubleshooting.

This message is also output to the Windows event log or syslog if execution of the ajsembdbbuild command has failed. In this case, take appropriate action for the message output to the standard output according to the action to be taken when an error occurs in the ajsembdbbuild command.

KAVS2128-E

Failed to set up embedded service. : func code=function-code error code=error-code

An attempt to set up the embedded database has failed.

(S)

Terminates processing.

(O)

If an attempt to install JP1/AJS3 has failed, take the following action, and then uninstall JP1/AJS3 and install it again.

If an attempt to uninstall JP1/AJS3 has failed, take the following action, and then uninstall JP1/AJS3 again.

If this message containing the same function code appears repeatedly, back up the following directory below the JP1/AJS3 installation directory, and then contact the system administrator:

Action

For func code=1:

If the KAVS2127-E message was output before this message, take action according to the instructions given by the KAVS2127-E message.

If the KAVS2127-E message was not output, uninstall JP1/AJS3 and then install it again.

For func code=2:

Review the environment where JP1/AJS3 is to be installed.

Make sure that there is sufficient memory and disk space.

For func code=3:

Take action according to the instructions given by the KAVS2127-E message that was output before this message.

For func code=4:

Review the environment where JP1/AJS3 is to be installed.

Make sure that there is sufficient memory and disk space.

For func code=5:

Information about the embedded database that has already been uninstalled might remain in the JP1/AJS3 common definition information. Execute all the following commands to delete the common definition information:

jbsunsetcnf -i -h JP1_DEFAULT -c JP1AJS2 -n EMBDBINSTALL
jbsunsetcnf -i -h JP1_DEFAULT -c JP1AJS2 -n EMBDB
jbsunsetcnf -i -h JP1_DEFAULT -c JP1AJS2 -n EMBDBPORT

For details on the jbsunsetcnf command, see the JP1/Base User's Guide.

For func code=6:

Take action for the output error code according to 2.7.9(1) Action to be taken if a JP1/AJS3 - Manager installation error occurs in the manual JP1/Automatic Job Management System 3 Troubleshooting.

For func code=7:

Take action for the output error code according to 2.7.9(2) Action to be taken if a JP1/AJS3 - Manager uninstallation error occurs in the manual JP1/Automatic Job Management System 3 Troubleshooting.

Note that this message is also output to the Windows event log or syslog if execution of the following commands has failed:

jajs_setup command

jajs_setup_cluster command

ajsembdbuninstl command

In this case, take appropriate action for the message output to the standard output according to the action to be taken when an error occurs in each command.

KAVS2129-I

The Embedded DB configuration file does not exist.

The embedded database configuration file does not exist.

(S)

Cancels command execution.

(O)

The command cannot be executed because the embedded database is not configured, or has been configured with a JP1/AJS3 version earlier than 10-00.

If this message is output for an embedded database configured with JP1/AJS3 10-00 or later, check whether the embedded database configuration file below exists. If the file does not exist, create the embedded database again, and then execute the command.

In Windows:

embedded-database-practical-directory\conf\ajsdbst\ajsembdbsetup-identifier.conf

In UNIX:

embedded-database-practical-directory/conf/ajsdbst/ajsembdbsetup-identifier.conf

KAVS2130-E

There is an error in the Embedded DB configuration file.

The embedded database configuration file contains an error.

(S)

Cancels command execution.

(O)

Specify the file correctly, and then re-execute the command. If this message is output during execution of the ajsembdbstatus command, create the embedded database again, and then execute the command.

KAVS3400-I

An error occurred while adding the JP1/AJS2 Check Manager service. : code=return-value api=API-name err=API-return-value

An error occurred while the JP1/AJS3 Check Manager service was being added.

(S)

Terminates setup processing.

(O)

Memory or free space on the disk may be insufficient. Terminate unnecessary applications or delete unnecessary files to make more free space available. Then re-execute the setup command.

KAVS3401-I

An error occurred while deleting the JP1/AJS2 Check Manager service. : code=return-value api=API-name err=API-return-value

An error occurred while the JP1/AJS3 Check Manager service was being deleted.

(S)

Terminates setup processing.

(O)

Memory or free space on the disk may be insufficient. Terminate unnecessary applications or delete unnecessary files to make more free space available. Then re-execute the setup command.

KAVS3402-I

The JP1/AJS2 Check Manager service will now start.

JP1/AJS3 Check Manager service will now start.

(S)

Continues processing.

KAVS3403-I

The JP1/AJS2 Check Manager service will now stop.

The JP1/AJS3 Check Manager service will now stop.

(S)

Stops the JP1/AJS3 Check Manager service.

KAVS3404-I

An error occurred while adding the JP1/AJS2 Check Agent service. : code=return-value api=API-name err=API-return-value

An error occurred while the JP1/AJS3 Check Agent service was being added.

(S)

Terminates setup processing.

(O)

Memory or free space on the disk may be insufficient. Terminate unnecessary applications or delete unnecessary files to make more free space available. Then re-execute the setup command.

KAVS3405-I

An error occurred while deleting the JP1/AJS2 Check Agent service. : code=return-value api=API-name err=API-return-value

An error occurred while the JP1/AJS3 Check Agent service was being deleted.

(S)

Terminates setup processing.

(O)

Memory or free space on the disk may be insufficient. Terminate unnecessary applications or delete unnecessary files to make more free space available. Then re-execute the setup command.

KAVS3406-I

The JP1/AJS2 Check Agent service will now start.

The JP1/AJS3 Check Agent service will now start.

(S)

Continues processing.

KAVS3407-I

The JP1/AJS2 Check Agent service will now stop.

The JP1/AJS3 Check Agent service will now stop.

(S)

Stops the JP1/AJS3 Check Agent service.

KAVS3408-I

The function for pre-checking definitions is not enabled.

Operation is impossible because the definition pre-check function is not enabled in JP1/AJS3 - Manager.

(S)

Cancels processing.

(O)

Enable the definition pre-check function in JP1/AJS3 - Manager.

KAVS3409-I

An attempt to connect to the Check Agent service (agent-name) has failed. : maintenance-information

An attempt to connect the check agent service has failed.

(S)

Assumes the pre-checking of definitions for the agent to be an error, and continues processing for other check agent services.

(O)

Make sure that the check agent service has started normally on the agent where the error occurred, and then pre-check the definitions again.

KAVS3410-I

The connection with the check agent service (agent-name) was closed. : maintenance-information

The connection with the check agent service was closed.

(S)

Assumes the pre-checking of definitions for the agent to be an error, and continues processing for other check agent services.

(O)

Examine the cause of the error according to the messages on the manager and on the agent, take corrective action, and then pre-check the definitions again.

The communication encryption function might be disabled on the manager and enabled on the agent. Make sure that the communication encryption function is set correctly, and then restart the JP1/Base service and JP1/AJS3 service.

KAVS3411-I

Definitions are being pre-checked elsewhere, so execution is not possible.

Execution is impossible because definitions are being pre-checked elsewhere.

(S)

Terminates processing.

(O)

Wait until the pre-checking of definitions being performed elsewhere terminates, and then re-execute the command.

KAVS3412-I

The host name, scheduler service name, or execution ID cannot be specified for the unit name. : unit-name

You cannot specify a host name, scheduler service name, or execution ID as a unit name.

(S)

Terminates processing.

(O)

Delete the specified host name, scheduler service name, and execution ID, and then re-execute the command.

KAVS3413-I

An attempt to connect to the check manager service has failed. : maintenance-information

An attempt to connect to the check manager service has failed.

(S)

Cancels execution of the command.

(O)

Make sure the check manager service is running normally, and then pre-check the definitions again.

KAVS3414-I

The Check Agent ended abnormally.

The check agent service terminated abnormally.

(S)

Terminates the check agent service.

(O)

Take action according to the instructions given by the message that was output immediately before this message.

KAVS3415-I

JP1/AJS2 Check Agent will now terminate.

A request to forcibly terminate the ajschkstop command was accepted.

(S)

Terminates the check agent service.

KAVS3416-I

The configuration definition of the logical host (logical-host-name) does not exist.

The environment for the logical host indicated in logical-host-name has not been set up.

(S)

Continues processing if the error occurred during startup of a check agent service. However, the logical host is not handled as the host where the job was executed. The system cancels processing if the error occurred during execution of a command.

(O)

Set up the environment for the logical host indicated in logical-host-name, and then restart the check agent service. If the error occurred during execution of a command, make sure that the correct logical host name is specified in the argument.

KAVS3417-I

An error occurred during an attempt to acquire the configuration definition of the logical host (logical-host). (function=maintenance-information-1, code=maintenance-information-2)

An attempt to acquire the value of the environment setting parameter for the logical host indicated in logical-host-name has failed.

(S)

Continues processing if the error occurred during startup of a check agent service. However, the logical host is not handled as the host where the job was executed. The system cancels processing if the error occurred during execution of a command.

(O)

Make sure that the correct value is set in the environment setting parameter for the logical host indicated in logical-host, and then restart the check agent service. If the error occurred during execution of a command, make sure that the correct logical host name is specified in the argument.

KAVS3418-I

Memory is insufficient, so the job (job-name) cannot be accepted.

The job cannot be accepted due to insufficient memory.

(S)

Cancels checking of the job.

(O)

Wait until the required amount of memory for checking the job becomes available, and then pre-check the definitions again.

KAVS3419-I

An iconv_open error occurred, so character conversion is not possible. : maintenance-information-1 (maintenance-information-2)

The character set will not be converted because the preparation for conversion has failed.

(S)

Continues processing.

(O)

To convert the character set, check the settings of the character set and then restart the check agent.

KAVS3420-I

Too many processes exist, so the job (job-name) cannot be checked.

The job indicated in job-name cannot be checked because there are too many processes.

(S)

Cancels checking of the job.

(O)

Wait until the number of processes decreases so that the check is available, and then pre-check the definitions again.

KAVS3421-I

The shared memory size is invalid. (size=size)

The size of shared memory is invalid.

(S)

Terminates the check agent service.

(O)

Recheck the settings of the semaphores and shared memory, and then pre-check the definitions again.

KAVS3422-I

Too many shared memories exist on the system.

The system has too many units of shared memory.

(S)

Terminates the check agent.

(O)

Contact the system administrator. The number of shared memory identifiers exceeded the maximum defined by the system. Recheck the kernel parameters, and then re-execute the command.

KAVS3423-I

The number of shared memory attaches is invalid.

The number of shared memory attaches is invalid.

(S)

Terminates the check agent.

(O)

Contact the system administrator. The number of shared memory segments attached to the process exceeded the maximum defined by the system. Recheck the kernel parameters, and then re-execute the command.

KAVS3424-I

The setup of the function for pre-checking definitions execution environment could not be updated. : maintenance-information-1 maintenance-information-2 maintenance-information-3

The execution environment settings for the definition pre-check function could not be updated because the ajschksetup command failed.

(S)

Cancels execution of the command.

(O)

The setup environment may be invalid. Make sure that the setup of JP1/AJS3 has been completed normally, and then re-execute the command.

KAVS3425-I

An attempt to acquire port information of the check agent service has failed. (service name: service-name)

Port information of the port to be connected cannot be read.

(S)

Cancels execution of the command.

(O)

Define port information correctly, and then re-execute the command.

KAVS3426-I

The function for pre-checking definitions log file (file-name-before-change) has been changed to file-name-after-change.

Since the size of the definition check log file exceeds the value specified in the environment setting parameter, the definition check log file will be replaced with another.

(S)

Continues processing.

(O)

As required, back up the definition check log file.

KAVS3427-I

JP1/AJS2 Check Manager will now terminate.

The check manager service terminated abnormally.

(S)

Terminates the check manager service.

(O)

Take action according to the instructions given by the message that was output immediately before this message. If a message beginning with KAVS34 that indicates the cause of the error was not output immediately before this message, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS3428-I

Failed in the request transmission of the definition check function in JP1/AJS2 Check Agent(agent-name). :maintenance-information

An attempt to issue a request for pre-checking definitions made to the JP1/AJS3 Check Agent indicated in agent-name has failed.

(S)

Assumes the pre-checking of definitions for the agent to be an error, and continues processing for other check agent services.

(O)

Make sure that the check agent service has started normally on the agent host where the error occurred, and then pre-check the definitions again.

KAVS3429-I

The connection with JP1/AJS2 Check Agent(agent-name) is disconnected because there is no response from JP1/AJS2 Check Agent(agent-name).(time)

No response was sent from the check agent for the period of time indicated in time (unit: seconds). The connection with the check agent indicated in agent-name will be released.

(S)

Assumes the pre-checking of definitions for the agent to be an error, and continues processing for other check agent services.

(O)

Examine the cause of the error according to the messages on the manager and on the agent, take corrective action, and then pre-check the definitions again.

KAVS3430-I

The value (item-name), specified in the environment settings parameter (parameter-name) of the definitioncheck function, is out of range. The default value (default) will be assumed and processing will continue.

Since the value specified in the environment setting parameter for the definition pre-check function is outside the valid range, the system assumes the default and continues processing.

(S)

Continues processing, assuming the value indicated in default.

(O)

Set the value in the environment setting parameter correctly, and then restart JP1/AJS3 Check Manager or JP1/AJS3 Check Agent.

KAVS3431-I

The definitioncheck function error detected while processing process-name. (maintenance-information-1, maintenance-information-2)

An error occurred during processing of the definition pre-check function.

(S)

Continues processing.

(O)

Take action according to the instructions given by the messages beginning with KAVS corresponding to the information indicated in maintenance-information-1 and maintenance-information-2, and then pre-check the definitions again.

If maintenance-information-1 is 1989 during execution of the ajschkstop command (UNIX only), the probable causes are as follows:

- The check agent service is not running.

- An IPv6 environment was migrated from an IPv4 environment or an IPv4 environment was migrated from an IPv6 environment while the check agent service was running.

- The ANY bind address was specified incorrectly.

If the check agent service is not running, no action is required. In other cases, you might be unable to stop the check agent service. Therefore, use the kill command to stop the check agent service. The next time you start the check agent service, make sure that the ANY bind address is specified correctly. For details about how to specify and check the ANY bind address, see the JP1/Base User's Guide.

If maintenance-information-1 is 0106 during execution of the ajschkdef command, the probable causes are as follows:

- While a definition pre-check was underway, the target units (including the units under the particular directory path) were added or deleted, or the content of the definitions was changed.

If the JP1/AJS3 Check Manager service has stopped, start the JP1/AJS3 Check Manager service, and then perform a definition pre-check again as needed.

KAVS3432-I

An error has occurred in JP1/AJS2 for the connection host. (connected-host-name)

An error occurred in JP1/AJS3 on the connection host for one of the following reasons:

The ajsinetd process is not running on the connection host.

JP1/AJS3 - Manager on the connection host does not support execution order control for root jobnets.

An error occurred during communication with JP1/AJS3 on the connection host.

(S)

Continues processing.

(O)

Take action to correct the error on the connection host, and then perform a definition pre-check again.

KAVS3433-I

Processing is cancelled due to failure to acquire agent information by using the function for pre-checking definitions. : host-name maintenance-information-1 maintenance-information-2 maintenance-information-3

Processing is canceled because an attempt to acquire agent information by using the definition pre-check function has failed.

The probable causes are:

The JP1/AJS3 service is not running on the host indicated in host-name.

The agent management daemon on the host indicated in host-name terminated abnormally.

(S)

Cancels processing to check the unit subject to the definition pre-check.

(O)

Check whether the JP1/AJS3 service is running on the host indicated in host-name.

If you cannot correct the error by starting the JP1/AJS3 service, restart the JP1/AJS3 service and the JP1/AJS3 Check Manager service on the host indicated in host-name, and then perform the definition pre-check again.

KAVS3434-I

The specified operation profile(profile-name) does not exist.

The operation profile name specified at command execution was invalid, or the operation profile of the scheduler service cannot be found.

(S)

Cancels processing.

(O)

If you specified an operation profile name in a command argument, check whether the operation profile you specified exists. If you did not specify any arguments, place the operation profile for the scheduler service in the appropriate location.

KAVS3435-I

The syntax of the operation profile contains an error. profile-name (maintenance-information-1, maintenance-information-2)

(S)

Cancels processing.

(O)

The system could not apply an operation profile because the syntax of the operation profile specified at command execution or assigned to the scheduler service contains an error. You can identify the cause of the error from the messages beginning with KAVS indicated in maintenance-information-1 and maintenance-information-2.

KAVS3436-I

An attempt to read the operation profile(profile-name) failed.

The system could not load the operation profile specified at command execution or assigned to the scheduler service into memory.

(S)

Cancels processing.

(O)

Review the number of work tasks assigned to the operation profile.

KAVS3437-I

The operation profile contains no valid information. maintenance-information-1, maintenance-information-2

The operation profile specified at command execution or assigned to the scheduler service contains no valid information.

(S)

Cancels processing.

(O)

If you intend to perform a definition pre-check with an operation profile applied, set valid information in the operation profile and then re-execute the command.

KAVS3601-E

The specified function is not supported.

The specified function cannot be used in the version you are using.

JP1/AJS3 - Manager version 11-00 and later does not support the following function:

JP1/AJS2 - Scenario Operation linkage function

(S)

Cancels processing.

(O)

Use a version of JP1/AJS3 - Manager that supports the function above.

KAVS3701-E

The logical host is already configured to operate as the main site.

A logical host is already configured to operate as the main site.

(S)

Terminates processing.

(O)

if you want to change the logical host that operates as the main site in disaster recovery mode, execute the jajs_rpsite command with the -m CHANGE option specified.

KAVS3702-E

The logical host is not configured to operate as the main site.

No logical host is configured to operate as the main site, or the system cannot identify the logical host because the shared disk is not mounted.

(S)

Terminates processing.

(O)

To configure a new logical host to operate as the main site in disaster recovery mode, execute the jajs_rpsite command with the -m SET or -m SETSAME option specified.

If the shared disk of the logical host is not mounted, mount it and then re-execute the command.

Depending on the hardware, you might be unable to mount the disk at the remote site while the disk copy and mirroring functions are being used. See the documentation for your hardware to find out whether this is possible.

KAVS3704-E

The disaster recovery operation cannot be set up because the shared disk cannot be accessed.

The system cannot set up disaster recovery operation because the shared disk cannot be accessed or because the definition file is invalid.

(S)

Terminates processing.

(O)

If the shared disk cannot be accessed, use a hardware operation to make the shared disk accessible, and then re-execute the jajs_rpsite command.

If this message appears even though the shared disk is accessible, carry out the following procedure to cancel the setting for disaster recovery operation:

Delete the following definition file:

- For Windows:

shared-folder\jp1ajs2\sys\jajs_remote_mainsite

- For UNIX:

shared-directory/jp1ajs2/sys/jajs_remote_mainsite

If the logical host names are the same at the main site and remote site, execute the following command:

jajs_rpsite -h logical-host-name -m UNSET

After canceling the setting for disaster recovery operation, if necessary, set up disaster recovery operation again.

For details about jajs_rpsite command, see jajs_rpsite in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVS3706-E

Scheduler service cannot start in the disaster recovery start mode using a compatible ISAM configuration.

You cannot start JP1/AJS3 in disaster recovery mode (-disaster) when using a compatible ISAM configuration.

(S)

Terminates command execution.

(O)

System management is terminated.

Change the start mode option and then restart JP1/AJS3.

KAVS3707-I

The logical host used as the main site has been specified. (host: host-name)

A message indicating that a logical host has been configured as the main site.

(S)

Terminates command execution.

KAVS3708-I

The logical host used as the main site has been changed. (host: host-name)

A message indicating that a logical host used as the main site has been changed.

(S)

Terminates command execution.

KAVS3709-I

The logical host being used as the main site has been removed. (host: host-name)

A message indicating that a logical host used as the main site has been deleted.

(S)

Terminates command execution.

KAVS3710-I

Disaster recovery operation was specified for logical hosts with the same host name.(host:host-name)

This message indicates that the same logical host name is specified for the main site and remote site.

(S)

Terminates command execution.

KAVS3711-E

The disaster recovery environment is being constructed, or the environment is invalid.

The disaster recovery environment being constructed is invalid.

(S)

Cancels execution of the command.

(O)

If the remote site is being constructed or the main site is being reconstructed, start disaster recovery operation after the construction is complete. For other cases, cancel the disaster recovery environment, or set it up again.

KAVS3750-E

Export processing ended abnormally. : maintenance-information

The export process failed.

(S)

Cancels execution of the command.

(O)

If an error message was output before or after this message, take action according to the contents of the error message. 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).

KAVS3751-E

Import processing ended abnormally. : maintenance-information

The import process failed.

(S)

Cancels execution of the command.

(O)

If an error message was output before or after this message, take action according to the contents of the error message. 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).

KAVS3752-Q

Logical Host already exists. OK to delete the settings? (Y: OK/N: NO)

This message indicates that a logical host is already configured, and asks you whether you want to delete the logical host settings and proceed with the import process.

(S)

Waits for a response.

(O)

To delete the logical host settings and proceed with the import process, press Y. To cancel the import process, press N.

KAVS3753-E

Cannot operate - JP1/AJS3 service has not stopped.

The operation cannot be performed because JP1/AJS3 has not completely stopped.

(S)

Cancels execution of the command.

(O)

The probable causes are as follows. Take the appropriate action depending on the cause.

The JP1/AJS3 service has not stopped

Use the jajs_spmd_status command to make sure that the JP1/AJS3 service has stopped, and then re-execute the command.

The command was executed together with the jajs_spmd_status command

An error might occur if you execute this command together with the jajs_spmd_status command. In this case, execute the command again.

KAVS3754-E

Export information is invalid. : maintenance-information

The export information you attempted to import is invalid.

(S)

Cancels execution of the command.

(O)

The probable causes are as follows:

You do not have access permission for the export information specified in the -d option

The export information specified in the -d option has been damaged

In a configuration in which the same logical host name is used at the main site and remote site, export information for another host name is specified

If you do not have access permission for directories and files under the directory specified in the -d option, assign the appropriate access permissions and then re-execute the command. Otherwise, copy the export information output by the jajs_rpenvexport command again and re-execute the command.

KAVS3755-E

Illegal character is present in argument.

A command argument contains an illegal character.

(S)

Cancels execution of the command.

(O)

You cannot specify the following characters in command arguments:

In Windows

^ & = ! @ ~ % " < > | , ; * ?

In UNIX

^ & = ! @ ~ % " < > | , ; * ? \ ' $

Specify the correct character and then re-execute the command.

KAVS3756-E

Contradiction between environment setting parameters and real environment.

An environment setting parameter conflicts with the actual operating environment.

(S)

Cancels execution of the command.

(O)

The JP1/AJS3 - Manager environment is configured incorrectly. Make sure that the environment is suitable for JP1/AJS3 - Manager operation, and then re-execute the command.

KAVS3757-E

File or directory operation failed. : maintenance-information

An operation targeting a file or directory failed.

(S)

Cancels execution of the command.

(O)

The probable causes are as follows. Take action according to the cause of the error. If an error message was output before or after this message, take action according to the contents of the error message.

You do not have access permission for the file or directory

Review access permissions for the following files and directories:

- The export file and directory

- The installation directory of the import destination embedded database

The disk does not have sufficient free space

Check whether sufficient free space is available on the disks where the following directories are located:

- Export target directory

- Installation directory of import destination embedded database

The file or directory does not exist

The JP1/AJS3 - Manager environment is configured incorrectly. Make sure that the environment is suitable for JP1/AJS3 - Manager operation, and then re-execute the command.

The file or directory cannot be created

If you specified the -ld option for the ajsembdbbuild command in the exported environment, make sure that the directory can be created with the same path when imported into the target environment.

After resolving the problem, execute the command again.

KAVS3780-I

Export processing has started.

The export process has started.

(S)

Begins command execution.

KAVS3781-I

Import processing has started.

The import process has started.

(S)

Begins command execution.

KAVS3782-I

Export processing ended normally.

The export process ended normally.

(S)

Command execution has ended normally.

KAVS3783-I

Import processing ended normally.

The import process ended normally.

(S)

Command execution has ended normally.

KAVS3784-I

Processing was canceled.

Command execution has been canceled.

(S)

Ends command execution.

KAVS3800-E

EmbedDB export processing ended abnormally. : maintenance-information

An error occurred when exporting the embedded database.

(S)

Cancels execution of the command.

(O)

If an error message was output before or after this message, take action according to the contents of the error message. 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).

KAVS3801-E

EmbedDB import processing ended abnormally. : maintenance-information

An error occurred when importing the embedded database.

(S)

Cancels execution of the command.

(O)

Run the ajsembdbstatus command with the -s ust option specified, and make sure that the embedded database is stopped (that is, UNIT-STAT is STOP). If the embedded database is paused (UNIT-STAT is PAUSE), run the ajsembdbstart command with the -Rf option specified to release the embedded database from the paused state. If the embedded database is not paused and an error message has been output before or after this message, take corrective action according to the error message.

After taking the corrective action, rerun the jajs_rpenvimport command. 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).

KAVS3802-E

Operation is not possible due to EmbedDB service is starting up.

The operation cannot be performed because the embedded database is starting.

(S)

Cancels execution of the command.

(O)

The embedded database is starting, preparing to start, or in the process of stopping on the import destination host.

Execute the ajsembdbstatus command with the -s ust option specified, and make sure that the embedded database has stopped on the import destination host. Then, re-execute the command.

KAVS3803-E

EmbedDB service is not installed.

The embedded database is not installed.

(S)

Cancels execution of the command.

(O)

The probable causes are as follows:

The embedded database is not installed on the export source host

The embedded database is not installed on the import destination host

The configuration of the embedded database on the export source host does not match that on the import destination host

Install the embedded database and build an environment where JP1/AJS3 - Manager can operate. Then, execute the command again.

Execute the ajsembdbidlist command with the -v option specified to make sure that the configuration of the embedded database on the export host matches that on the import host.

KAVS3804-E

The EmbedDB environment has not been configured.

The embedded database environment has not been configured.

(S)

Cancels execution of the command.

(O)

The probable causes are as follows:

The environment for the embedded database is not configured on the export source host

The JP1/AJS3 - Manager environment is configured incorrectly

Version 09-10 or later of the embedded database environment is not configured on the export source host

After resolving the problem and building an environment where JP1/AJS3 - Manager can operate, execute the command again.

KAVS3805-W

Directory could not be created. : maintenance-information

The storage directory for the automatic log unload file could not be created.

(S)

Continues the command.

(O)

The specified directory is on an inaccessible path or drive.

Create the directory after checking the path you specified in the -bl option when executing the ajsembdbbuild command.

If you do not create this directory, the message KFPS01150-E is output to the Windows event log or syslog when the embedded database starts.

The database will go down if the system runs out of space for embedded database logs before the directory can be created.

KAVS3850-I

EmbedDB export processing has started.

The process of exporting the embedded database configuration has started.

(S)

Continues the command.

KAVS3851-I

EmbedDB import processing has started.

The process of importing the embedded database configuration has started.

(S)

Continues the command.

KAVS3852-I

EmbedDB export processing ended normally.

The process of exporting the embedded database configuration ended normally.

(S)

Continues the command.

KAVS3853-I

EmbedDB import processing ended normally.

The process of importing the embedded database configuration ended normally.

(S)

Continues the command.

KAVS3910-E

Interprocess communication failed. : maintenance-information-1 maintenance-information-2 maintenance-information-3

Interprocess communication failed.

(S)

Connects to the JP1/Base event service the next time that an event is output (if yes is specified in the COMMANDEVENT environment setting parameter).

(O)

Determine the cause of the error, and then re-execute the command.

If the JP1/Base event service has stopped, start it.

If a message Failed to put Event. is displayed in maintenance-information-1 and you omitted the COMMANDEVENT environment setting parameter or specified no for it, check the status of the JP1/Base event service, and then restart the JP1/AJS3 service.

KAVS4091-E

The wrong request was received. (maintenance-information)

The job submit process received invalid information.

(S)

Continues processing.

(O)

Use the data collection tool to collect data and contact the system administrator (see 1.2.3 To the system administrators).

KAVS4092-I

Communication with a command process was disconnected. (maintenance-information)

A process, such as a command prompt or JP1/AJS3 - View at the processing-request source, might have been terminated forcibly before the result of the requested processing was returned.

(S)

Continues processing.

(O)

Check the scheduler log, etc., to make sure that the operation performed before this message was output was performed correctly.

If the operation was not performed correctly, retry the operation if necessary.

KAVS4200-E

Failed to write the file created during unit (unit-name) execution. : maintenance-information

An attempt to write to the database from the file that is created during execution of the unit has failed. As a result, the following problems may occur when a service is started in the disaster mode:

The Execution Result Details dialog box for the unit indicated in unit-name does not display a message.

The macro variables are not inherited correctly during execution of a unit that follows the unit indicated in unit-name.

(S)

Continues execution of the unit.

(O)

Determine the cause of the error from the error message that was output before this message, and correct the cause of the error. Then specify the unit indicated in unit-name and retry.

KAVS4201-E

Failed to save the macro variable specified during jobnet (jobnet-name) execution registration. Execution registration cancelled. : maintenance-information-1 maintenance-information-2

The system cancels execution registration because the system failed to save the macro variable that was specified when the jobnet was registered for execution.

(S)

Cancels processing.

(O)

Determine the cause of the error from the error message that was output before this message, and correct the cause of the error. Then re-register the jobnet.

KAVS4202-E

File creation failed during creating a generation of jobnet (jobnet-name). Generation creation (execution-ID) is canceled. : maintenance-information-1 maintenance-information-2

The system cancels creation of a new generation because an attempt to inherit the macro variables or to record the execution ID of the new generation failed during creation of the new jobnet generation.

(S)

Cancels processing.

(O)

Determine the cause of the error from the error message that was output before this message, and correct the cause of the error. If an attempt to register the jobnet for execution has failed, re-register the jobnet. If the jobnet has been registered for execution successfully and this message appears before the jobnet is executed, the action to take differs depending on the registration method. Take appropriate action as follows:

Fixed execution with the period specified (including the case in which a schedule information file is used):

Make sure that the generations have been created in the specified period, and then add the generations that have not been created. If many generations have not been created yet, cancel all registrations of the relevant jobnet, and then re-register them.

Fixed execution with the number of future generations specified, or planned execution:

No generations will be created after the generation whose creation is canceled. Cancel all registrations of the relevant jobnet, and then re-register them.

Irrespective of the registration method, when the start condition is used and this message appears during execution, the jobnet is placed in the Monitor terminated status. If this message appears when you temporarily change the plan or add a registration, re-execute the same operation.

KAVS4203-E

Deletion of an unnecessary macro variable failed during creating a generation of jobnet (jobnet-name). Generation creation (execution-ID) is canceled. : maintenance-information-1 maintenance-information-2

The system cancels creation of a new generation because an attempt to delete an unnecessary macro variable file or record failed during creation of the new generation of the jobnet.

(S)

Cancels processing.

(O)

Determine the cause of the error from the error message that was output before this message, and correct the cause of the error. If an attempt to register the jobnet for execution has failed, re-register the jobnet. If the jobnet has been registered for execution successfully and this message appears before the jobnet is executed, the action to take differs depending on the registration method. Take appropriate action as shown below:

Fixed execution with the period specified (including the case where a schedule information file is used):

Make sure that the generations have been created in the specified period, and then add the generations that are not created. If many generations have not been created yet, cancel all registrations of the relevant jobnet, and then re-register them.

Fixed execution with the number of future generations specified, or planned execution:

No generations will be created after the generation whose creation is canceled. Cancel all registrations of the relevant jobnet, and then re-register them.

Irrespective of the registration method, when the start condition is used and this message appears during execution, the jobnet is placed in the Monitor terminated status. If this message appears when you temporarily change the plan or add a registration, re-execute the same operation.

KAVS4204-E

Failed to delete unnecessary file or record for unit (jobnet-name:execution-ID) : maintenance-information-1 maintenance-information-2

An attempt to delete unnecessary macro variables or job error information for the unit has failed. An unnecessary file remains, or an unnecessary record remains in the database.

(S)

Continues processing.

(O)

Determine the cause of the error from the error message that was output before this message, and correct the cause of the error. If an attempt to cancel registration of the generation has failed, cancel the registration again without executing or re-executing the jobnet. If registration of a generation is successfully canceled, or if this error message appears during creation of a new generation, during execution of a generation, or during deletion of suspended units, an unnecessary file for the unit remains. If this error message appears often, check the amount of space on the disk.

KAVS4209-W

An error has occurred while restructuring JP1/AJS2 control file from an EmbedDB.

An error occurred during restructuring of a file, such as the standard error output file under the job information storage folder, for one of the following reasons:

You do not have update permission for the job information storage folder and the files in that folder.

The file system does not have sufficient free space.

(S)

Continues processing.

(O)

If this error message appears, the following may occur.

After operation starts, a job using a queue terminates abnormally.

The Execution Result Details dialog box for the job prior to its being restructured does not display a message.

Jobs and jobnets using the inherited information and macro variables of the event job before the restructuring are not re-executed correctly.

KAVS4211-E

The JP1/AJS2 service is not inactive.

The specified command cannot be executed because the JP1/AJS3 service has not stopped.

(S)

Cancels processing.

(O)

Stop the JP1/AJS3 service, and then re-execute the command.

KAVS4540-E

Command (command-name) cannot be executed.

The specified command cannot be executed. The probable causes are:

For the ajsqlsetup command

An attempt was made to set up a queueless job execution environment by using JP1/AJS3 - Agent Minimal Edition.

For the ajsatsetup command

An attempt was made to set up a flexible job execution environment by using JP1/AJS3 - Agent Minimal Edition.

(S)

Cancels command execution.

(O)

For the ajsqlsetup command

You cannot set up queueless jobs execution environment by using JP1/AJS3 - Agent Minimal Edition. Be sure to run the command on the correct host.

For the ajsatsetup command

You cannot set up flexible jobs execution environment by using JP1/AJS3 - Agent Minimal Edition. Be sure to run the command on the correct host.

KAVS4601-E

Cannot treat as jobnet for the connection destination. : unit-name

An option that can be specified only for the connection-destination jobnet is specified for a unit that is not the connection-destination jobnet.

(S)

Cancels command execution. However, the system continues processing if you specify multiple jobs.

(O)

Specify the connection-destination jobnet name, and then re-execute the command.

KAVS4602-E

Invalid information relating to jobnet connector. : unit-name

The execution order control information specified in the unit definition contains an error.

The probable causes are:

The unit containing the execution order control information is created in a unit that is not either of the following:

- A planning group

- A root jobnet (except for a root jobnet under a planning group)

Although a root jobnet or planning group is specified so that connection with a jobnet connector is not established, one of the following information items is specified:

- A value is specified for Jobnet Connector.

- Synchro is specified for Exec. order method.

- Other service is specified for Connection range.

- A value is specified for Connection host.

- A value is specified for Connection service.

Although a root jobnet, planning group, or jobnet connector is specified so that linkage between scheduler services is not established, one of the following information items is specified:

- A value is specified for Connection host.

- A value is specified for Connection service.

Although a root jobnet, planning group, or jobnet connector is specified so that linkage between scheduler services is established, the connection service name is not specified.

(S)

Cancels command execution.

(O)

Check the unit definition, and then execute the command.

KAVS4603-E

Cannot hold rerun jobnet connector. : unit-name

The jobnet connector cannot be rerun because it cannot be placed in the hold state.

(S)

Cancels command execution. However, the system continues processing if you specify multiple jobs.

(O)

Re-execute the command without the hold option (-h) specified.

KAVS4607-E

Cannot define jobnet connector in a registered unit. : unit-name

A unit containing a jobnet connector cannot be defined as a registered unit.

(S)

Cancels command execution.

(O)

Check the unit definition and execute the command.

KAVS4608-E

Cannot delete the unit(unit-name) - jobnet connector exist.

When you delete the registered unit information, a unit that contains a jobnet connector cannot be deleted. To delete the jobnet connector and the unit that contains the jobnet connector, first unregister the unit.

(S)

Cancels command execution.

(O)

Check the registration status of the unit, and then re-execute the command.

KAVS4609-E

Cannot copy the unit(unit-name) - jobnet connector exist.

When you copy unit information to a registered unit, a unit that contains a jobnet connector cannot be copied. To copy the jobnet connector and the unit that contains the jobnet connector to a registered unit, first unregister the copy-destination unit.

(S)

Cancels command execution.

(O)

Check the registration status of the unit, and then re-execute the command.

KAVS4610-E

Cannot move the unit(unit-name) - jobnet connector exist.

When you move unit information to a registered unit, a unit that contains a jobnet connector cannot be moved. To move the jobnet connector and the unit that contains the jobnet connector to a registered unit, first unregister the destination unit.

(S)

Cancels command execution.

(O)

Check the registration status of the unit, and then re-execute the command.

KAVS4611-E

Cannot define the unit(unit-name) - jobnet connector exist.

When you create a unit by overwriting a registered unit with existing unit information that has the same name, a unit that contains a jobnet connector cannot be created. To overwrite the registered unit having the same name as the jobnet connector and the unit that contains the jobnet connector, first unregister the unit to be overwritten.

(S)

Cancels command execution.

(O)

Check the registration status of the unit, and then re-execute the command.

KAVS4612-E

Jobnet connector(unit-name) can only be copy into jobnet.

You cannot copy a jobnet connector into a unit other than a jobnet.

(S)

Cancels command execution.

(O)

Check the copy destination of the unit, and then re-execute the command.

KAVS4613-E

Jobnet connector(unit-name) can only be move into jobnet.

You cannot move a jobnet connector into a unit other than a jobnet.

(S)

Cancels command execution.

(O)

Check the destination of the unit, and then re-execute the command.

KAVS4614-E

A unit including jobnet connector can only be define in jobnet. : unit-name

When you define a unit that contains a jobnet connector, you cannot specify a unit other than a jobnet for the unit under which the unit is to be created.

(S)

Cancels command execution.

(O)

Check the location in which the unit is to be created, and then re-execute the command.

KAVS4615-E

Cannot operate - Condition exist in the jobnet for the connection destination. : unit-name

Operation is impossible because a start condition is defined in the connection-destination jobnet.

(S)

Terminates processing. However, if multiple units are specified, the system continues processing of other units.

(O)

Change the unit configuration, and then re-execute the command.

KAVS4616-E

Cannot operate - Jobnet connector exist in the jobnet for the connection destination. : unit-name

Operation is impossible because a jobnet connector is defined in the connection-destination jobnet.

(S)

Terminates processing. However, if multiple units are specified, the system continues processing of other units.

(O)

Change the unit configuration, and then re-execute the command.

KAVS4617-E

Cannot operate - Jobnet connector exist in the condition. : unit-name

Operation is impossible because a jobnet connector is defined in the jobnet with start conditions.

(S)

Terminates processing. However, if multiple units are specified, the system continues processing of other units.

(O)

Change the unit configuration, and then re-execute the command.

KAVS4618-E

Cannot operate - Condition exist in the planning group for the connection destination. : unit-name

Operation is impossible because a start condition is defined in the connection-destination planning group.

(S)

Terminates processing. However, if multiple units are specified, the system continues processing of other units.

(O)

Change the unit configuration, and then re-execute the command.

KAVS4619-E

Cannot operate - Jobnet connector exist in the planning group for the connection destination. : unit-name

Operation is impossible because a jobnet connector is defined in the connection-destination planning group.

(S)

Terminates processing. However, if multiple units are specified, the system continues processing of other units.

(O)

Change the unit configuration, and then re-execute the command.

KAVS4620-E

Cannot operate - Root remote jobnet exist in the planning group for the connection destination. : unit-name

Operation is impossible because a jobnet connector is defined in the connection-destination planning group.

(S)

Terminates processing. However, if multiple units are specified, the system continues processing of other units.

(O)

Change the unit configuration, and then re-execute the command.

KAVS4621-E

Cannot operate - Jobnet for the connection destination exist in the planning group for the connection destination. : unit-name

Operation is impossible because a connection-destination jobnet is defined in the connection-destination planning group.

(S)

Terminates processing. However, if multiple units are specified, the system continues processing of other units.

(O)

Change the unit configuration, and then re-execute the command.

KAVS4624-E

The release ID has already been used.

The release-target jobnet cannot be registered for release because release information with the same release ID already exists.

(S)

Cancels command execution.

(O)

Change the release ID, and then re-execute the command.

If registering a jobnet for release failed, this message might appear when you retry the operation. In this case, cancel the release and then re-execute the command.

KAVS4625-E

The type cannot be specified for the release target jobnet. : maintenance-information

Specification of the release target jobnet contains an error.

The type of the unit specified as the release source or release target might be one of the following:

Other than a root jobnet

Remote jobnet

Recovery jobnet

Manager jobnet

Root jobnet in a planning group

(S)

Cancels command execution.

(O)

Check the release target jobnet, and then re-execute the command.

KAVS4626-E

The same unit cannot be specified for the release source jobnet and the release target jobnet.

The same unit cannot be specified as the release source and release target jobnets.

(S)

Cancels command execution.

(O)

Change the release source or release target jobnet, and then re-execute the command.

KAVS4627-E

(unit-name) is not the release target jobnet.

An attempt was made to cancel the release or view the release information for a jobnet that has not been entered for release.

(S)

Cancels command execution.

(O)

Check the unit for which you want to cancel the release or view the release information, and then re-execute the command.

KAVS4628-E

The state of release wait, delete wait, or release entry wait does not exist. : unit-name

An attempt was made to cancel the release of a jobnet definition whose status was not Release wait, Delete wait, or Release entry wait.

(S)

Cancels command execution.

(O)

Check the unit for which you want to cancel the release, and then re-execute the command.

KAVS4629-E

The type cannot be specified for the release source jobnet. : maintenance-information

The specification of the release source jobnet contains an error.

The type of the unit specified as the release source or release target might be one of the following:

Other than a root jobnet

Remote jobnet

Recovery jobnet

Manager jobnet

Root jobnet in a planning group

Unit entered for release

(S)

Cancels command execution.

(O)

Check the release source jobnet, and then re-execute the command.

KAVS4630-E

The state of release wait, delete wait, or release entry wait does exist. : unit-name, release-ID

Release entry is impossible because there is a jobnet definition whose status is Release wait, Delete wait, or Release entry wait.

(S)

Cancels command execution.

(O)

Check the release information for the unit you want to enter for release, and then re-execute the command.

If registering a jobnet for release failed, this message might appear when you retry the operation. In this case, cancel the release and then re-execute the command.

KAVS4631-W

The jobnet definition for the applied where the generation did not exist could not be deleted.

Release entry terminated normally, but a jobnet definition that had no generation and whose status was Applied could not be deleted.

(S)

Continues processing.

The jobnet definition in Applied status remains in the database.

(O)

The jobnet definition in Applied status that could not be deleted will be deleted automatically when release entry is performed next time.

Because the cause of the failure was output to the previous message, correct the problem according to the instructions given by that message.

KAVS4632-E

A generation beginning on the release date or later exists.

Release entry or release cancellation cannot be performed because there is a generation that has been generated for fixed execution registration with a period or a date specified after the release date.

(S)

Cancels command execution.

(O)

Cancel registration of the generation generated for fixed execution registration after the release date, and then re-execute the command.

KAVS4633-E

The release time is incorrect.

Release entry cannot be performed if a time earlier than the current time is specified.

(S)

Cancels command execution.

(O)

Specify a time later than the current time, and then re-execute the command.

KAVS4634-E

A definition release being applied does not exist.

The command cannot be executed because a jobnet definition whose status is Being applied does not exist.

(S)

Cancels command execution.

(O)

Make sure that a jobnet definition whose status is Being applied exists, and then re-execute the command.

KAVS4635-E

Cannot operate - Outside the release period.

Operation that extends beyond the release date cannot be performed.

(S)

Cancels command execution.

(O)

Check the release date of the target unit, and then re-execute the command.

KAVS4636-E

Cannot operate - A remote jobnet exists in the specified unit.

A unit containing a remote jobnet cannot be entered for release.

(S)

Cancels command execution.

(O)

Check the definition of the release target unit, and then re-execute the command.

KAVS4638-E

Cannot operate - A jobnet connector exists in the specified condition unit.

Operation is impossible because the release target or release source jobnet is a jobnet with start conditions that contain a jobnet connector.

(S)

Cancels command execution.

(O)

Check the definition of the release target or release source jobnet, and then re-execute the command.

KAVS4639-E

Cannot operate - A condition exists in the specified jobnet for the connection destination.

Operation is impossible because a jobnet with start conditions is specified as the connection-destination jobnet for the release target or release source jobnet.

(S)

Cancels command execution.

(O)

Check the definition of the release target or release source jobnet, and then re-execute the command.

KAVS4640-E

Cannot operate - A jobnet connector exists in the specified jobnet for the connection destination.

Operation is impossible because a jobnet connector is contained in the connection-destination jobnet for the release target or release source jobnet.

(S)

Cancels command execution.

(O)

Check the definition of the release target or release source jobnet, and then re-execute the command.

KAVS4643-E

Cannot operate - Compatible V8 constitution.

Release operation is impossible in the V8 compatible configuration.

(S)

Cancels command execution.

(O)

Change the configuration to the standard configuration, and then re-execute the command.

KAVS4645-E

Cannot move - The moving destination of unit (unit-name) is invalid.

The released unit can be moved only to immediately below the job group.

(S)

Cancels command execution.

(O)

Check the destination, and then re-execute the command.

KAVS4646-E

An unnecessary jobnet was defined. Resolve the problem, cancel the release, and then entry the release again.

An unnecessary jobnet definition was created. After correcting the problem, cancel the release and then perform the release entry again.

(S)

Cancels command execution.

(O)

Take action according to the instructions given by the message that was output immediately before this message. You also need to cancel the release because a jobnet definition whose status is Release entry wait or Delete wait has been created. After canceling the release, perform release entry again.

KAVS4647-E

Cannot operate - The version is different.

Operation is impossible because the version of JP1/AJS that manages the target unit and the version of JP1/AJS that performs the operation do not match.

(S)

Cancels processing.

(O)

Check the versions as a user who has administrator privileges or superuser privileges.

KAVS4648-E

Scheduler service has not started.

The scheduler service is not running.

(S)

Cancels processing.

(O)

Start the scheduler service, and then retry the operation.

KAVS4649-E

Cannot communicate with scheduler service.

During communication with the scheduler service, a situation that prevents communication with the scheduler service occurred because, for example, the service was stopped.

(S)

Cancels processing.

(O)

Check whether the scheduler service is running. After checking the cause of the error, retry the operation.

KAVS4650-E

Cannot operate - Jobnet has been shutdown.

The status of the specified jobnet is Shutdown.

The probable causes are:

The unit defined in the calendar to be referenced does not exist.

The unit defined in the exclusive schedule does not exist.

(S)

Cancels processing.

(O)

Unregister the jobnet in Shutdown status, review the schedule definition, and then retry the operation.

KAVS4651-E

Registerable Jobnet number exceeds the limit.

The number of jobnets that can be registered exceeds the limit.

(S)

Cancels processing.

(O)

Unregister unnecessary jobnets, and then retry the operation.

KAVS4654-E

A unit was deleted during the processing.

A unit was deleted during processing.

(S)

Cancels processing.

(O)

Check whether the specified unit exists, and then retry the operation.

KAVS4655-E

In use by other user.

Another user is using the unit.

(S)

Cancels processing.

(O)

Wait until the other user ends the use of the unit, and then retry the operation.

KAVS4656-E

No authority for Unit.

You do not have authority for the unit.

(S)

Cancels processing.

(O)

Execute the command as a user who has the required authority for the unit.

KAVS4657-E

A unit type that cannot be added is specified in the jobnet where release entry is complete.

A unit type that cannot be added to a jobnet entered for release is specified. The specified unit type might be one of the following:

Jobnet connector

Remote jobnet

Start condition

(S)

Cancels command execution.

(O)

Check the unit type and then re-execute the command.

KAVS4660-E

The specified unit whose end is being waited for (name-of-unit-whose-end-is-being-waited-for) is not defined for the unit (unit-name).

The unit whose end is being waited for by the unit indicated in the message is not defined. The probable causes are as follows:

The unit you specified is not assigned a wait condition

The unit you specified as a unit whose end is being waited for is not defined

The specified unit whose end is being waited for was deleted from the wait condition definition while the command was executing

No unit names match the regular expression

(S)

Cancels command execution. If you specify multiple units (including by regular expression), the system continues processing from the next unit.

(O)

Check the unit whose end is being waited for and then re-execute the command.

KAVS4661-E

This option (option) cannot be used because the preceding unit wait function is not enabled.

The chosen option cannot be used because JP1/AJS is not set up to use wait conditions.

(S)

Cancels command execution. If you specify multiple units (including by regular expression), the system continues processing from the next unit.

(O)

Set up JP1/AJS3 to use wait conditions by following the instructions in 6.1.8 Settings for using wait conditions in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows) or 15.1.8 Settings for using wait conditions in the JP1/Automatic Job Management System 3 Configuration Guide (for UNIX).

KAVS4662-E

Wait conditions is not defined for the unit (unit-name). : maintenance-information

Wait conditions are not defined for the unit indicated in unit-name.

(S)

Cancels command execution. If you specify multiple units (including by regular expression), the system continues processing from the next unit.

(O)

Define wait conditions and then re-execute the command.

KAVS4670-I

Temporary change information does not exist in unit (unit-name).

Temporary change information could not be output. The probable causes are as follows:

No temporary change information exists for the target unit

No temporary change information exists for the target unit after the specified start date

(S)

Cancels command execution. If you specify multiple units (including by regular expression), the system continues processing from the next unit.

(O)

Specify a unit for which a temporary change has been executed, or change the start date to a date before temporary changes were made. Then, re-execute the command.

KAVS4671-E

Information about temporary change operations for the unit (unit-name) could not be saved. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

The system could not save information about temporary change operations for the unit.

(S)

Cancels the process of saving temporary change information, and continues processing.

(O)

Take action according to the instructions provided in the message that was output immediately before this message. If no message was output, temporary change operations might have been performed for the 1,000th or later generation for the day. For the functionality for managing temporary changes, temporary change information for a maximum of 999 generations can be saved for one root jobnet per day. Accordingly, make sure that the number or generations executed by a root jobnet per day does not exceed 999.

The unsaved temporary change information does not appear when you use JP1/AJS3 - View or the ajsplanout command to display a list of temporary change information.

This information can be viewed in the scheduler log.

KAVS4672-W

Temporary change information from the previously executed registration could not be deleted. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4 maintenance-information-5

The temporary change information for the previous execution registration could not be deleted.

(S)

Cancels deletion of the temporary change information for the previous execution registration, and continues processing.

(O)

Note that the temporary change information for the previous execution registration will appear in the list of temporary change information displayed in JP1/AJS3 - View or output by the ajsplanout command.

KAVS4673-W

Temporary change information could not be deleted. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4 maintenance-information-5

Temporary change information could not be deleted.

(S)

Cancels the deletion of temporary change information and continues processing.

(O)

The internal files remain on the disk until you re-register the jobnet for execution, or perform a cold start of the scheduler service.

KAVS4674-E

The command cannot be executed because the operation management function for temporary changes is not enabled.

The command could not be executed because the function for managing temporary changes is not enabled.

(S)

Cancels command execution. If you specify multiple units (including by regular expression), the system continues processing from the next unit.

(O)

Enable the function for managing temporary changes on the connection-destination JP1/AJS3 - Manager by following the instructions in 6.1.9 Settings for using the temporary change operation management function in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows) or 15.1.9 Settings for using the temporary change operation management function in the JP1/Automatic Job Management System 3 Configuration Guide (for UNIX), and then re-execute the command.

KAVS4675-I

A retry wait interval will now begin because the job ended abnormally. (name: job-name: execution-ID, code: code, host: host-name, JOBID: job-number, retry:number-of-retry-executions)

Because a job is specified to be retried if it ends abnormally and matches the retry condition, processing to start the job will be re-executed after the time set for the retry interval elapses.

(S)

Continues processing. execution-ID and job-number appear if you specified yes for the LOGINFOALL environment setting parameter.

KAVS4676-I

Job started as retry execution. (name: job-name: execution-ID, host: host-name, JOBID: job-number, retry:number-of-retry-executions)

The job will start because automatic retrying is specified for jobs that end abnormally.

(S)

Continues processing. execution-ID, host-name, and job-number appear if you specified yes for the LOGINFOALL environment setting parameter.

KAVS4677-E

An error that cannot be recoverd by retry execution occurred.(name: job-name: execution-ID, code: return-code, host: host-name, JOBID: job-number, retry:number-of-retry-executions, cause code: cause-code)

A job that was specified to be retried if it ended abnormally terminated, because retrying was not possible. For details, see cause-code.

The following explains the cause codes:

FATALERR

The job terminated in an end status that does not allow a retry.

ERRCODE

The executable file or script file terminated with a return code that is outside the scope of automatic retry.

RETRYNUM

The number of retry executions can be executed reached the maximum.

For details about automatic retrying, see 2.4.13 Automatic retry for abnormally ending jobs in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

(S)

Continues processing.

(O)

Examine the cause of the error and take action to correct it. 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).

KAVS4678-I

Job submit started as retry execution. (name: job-name: execution-ID, Retry:number-of-retry-executions)

Submission of the job will start because automatic retry is specified for jobs that end abnormally. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

KAVS4699-I

Because the scheduler service is not an ISAM database, the reconfiguration is not performed.

Reorganization is not performed because the scheduler service database is not ISAM.

(S)

Continues processing.

KAVS4700-E

The jobnet connector (jobnet-name:execution-ID) ended abnormally because it failed to connect to the connection destination jobnet.

The jobnet connector cannot be executed because an attempt to connect to the connection-destination jobnet has failed.

(S)

Places the jobnet connector into Ended abnormally status.

(O)

The jobnet cannot be re-executed if the error occurred during re-execution or if relationships are not established between generations of a jobnet for which a jobnet connector is defined and those of its connection-destination jobnet. Re-execute the subsequent unit of the jobnet connector.

If the error occurred during processing other than re-execution, take action according to the error message that was output to the integrated trace log before of after this message. After correcting the error, re-execute the jobnet connector.

KAVS4701-E

The jobnet for the connection destination(jobnet-name:execution-ID) ended abnormally because it failed to connect to jobnet connector.

The connection-destination jobnet cannot be executed because an attempt to connect to the jobnet connector has failed.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Take action according to the error message that was output to the integrated trace log before or after this message. After correcting the error, re-execute the connection-destination jobnet.

KAVS4702-E

Cannot execute the jobnet connector(jobnet-name) because the jobnet name of the connection destination is not specified.

The jobnet connector cannot be executed because the connection-destination jobnet name is not specified.

(S)

Places the jobnet connector into Ended abnormally status.

(O)

Specify the connection-destination jobnet name, and then re-execute the jobnet connector.

KAVS4703-E

Cannot execute the jobnet connector(jobnet-name) because the jobnet name of the connection destination is invalid.

The jobnet connector cannot be executed because the specified connection-destination jobnet is invalid. The probable causes are:

The unit specified for the connection-destination jobnet does not exist.

The type of the unit specified for the connection-destination jobnet is invalid.

(S)

Places the jobnet connector into Ended abnormally status.

(O)

Correct the error, and then re-execute the jobnet connector.

KAVS4704-E

Cannot execute the jobnet connector (jobnet-name) because the jobnet for the connection destination is not defined to connect.

The jobnet connector cannot be executed because connection is not established from the connection-destination jobnet. The probable causes are:

The execution order control is not set for the connection-destination jobnet.

The jobnet connector is not specified for the connection-destination jobnet.

(S)

Places the jobnet connector into Ended abnormally status.

(O)

Correct the error, and then re-execute the jobnet connector.

KAVS4705-E

Cannot execute the jobnet for the connection destination(jobnet-name) because the jobnet connector name is not specified.

The connection-destination jobnet cannot be executed because the jobnet connector name is not specified.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Specify the jobnet connector name, and then re-execute the connection-destination jobnet.

KAVS4706-E

Cannot execute the jobnet for the connection destination(jobnet-name) because the jobnet connector name is invalid.

The connection-destination jobnet cannot be executed because the specified jobnet connector is invalid. The probable causes are:

The unit specified for the jobnet connector does not exist.

The type of the unit specified for the jobnet connector is invalid.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Correct the error, and then re-execute the connection-destination jobnet.

KAVS4707-E

Cannot execute the jobnet for the connection destination(jobnet-name) because the jobnet connector is not defined to connect.

The connection-destination jobnet cannot be executed because connection is not established from the jobnet connector. The probable cause is:

The connection-destination jobnet is not specified for the jobnet connector.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Correct the error, and then re-execute the jobnet connector.

KAVS4708-E

An attempt of job status notification from the jobnet for the connection destination(jobnet-name:execution-ID) has failed. : maintenance-information

The status of the jobnet connector might be incorrect because the connection-destination jobnet failed to send a status notification to the jobnet connector.

(S)

Continues processing.

(O)

Take action according to the Windows event log, syslog, or integrated trace log message that was output immediately before this message.

Note that the relationship between the jobnet connector and the connection-destination jobnet might have been invalid. In this case, the status of the jobnet connector might not have been changed correctly according to the status of the connection-destination jobnet. If necessary, manually change the status of the jobnet connector.

KAVS4710-E

Cannot use the controlling execution order of Root jobnet between scheduler services. (scheduler-service-name) : maintenance-information

The jobnet connector or the connection-destination root jobnet cannot be executed. The probable causes are:

The RJCUSE environment setting parameter is not set to yes.

The scheduler service inter-communication control process has stopped.

The jobnet connector or connection-destination root jobnet for which execution was attempted terminates abnormally after a KAVS4701-E or KAVS4700-E message is output, respectively.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Check the value of the RJCUSE environment setting parameter. For details on the environment setting parameters, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

If the scheduler service inter-communication control process has stopped, restart the JP1/AJS3 service.

KAVS4711-E

Cannot execute the jobnet connector (jobnet-name) because the connection host name of the jobnet of the connection destination is invalid.

The jobnet connector cannot be executed because the connection host name specified for the connection-destination jobnet is invalid. The probable cause is:

The connection host name specified for the connection-destination jobnet does not match the host name for the jobnet connector.

(S)

Places the jobnet connector into Ended abnormally status.

(O)

Correct the error, and then re-execute the jobnet connector.

KAVS4712-E

Cannot execute the jobnet connector (jobnet-name) because the connection service name of the jobnet of the connection destination is invalid.

The jobnet connector cannot be executed because the connection service name specified for the connection-destination jobnet is invalid. The probable cause is:

The connection service name specified for the connection-destination jobnet does not match the scheduler service of the jobnet connector.

(S)

Places the jobnet connector into Ended abnormally status.

(O)

Correct the error, and then re-execute the jobnet connector.

KAVS4713-E

Cannot execute the jobnet connector (jobnet-name) because the connection range of the jobnet of the connection destination is invalid.

The jobnet connector cannot be executed because the connection range specified for the connection-destination jobnet is invalid. The probable cause is:

The connection range specified for the connection-destination jobnet does not match the connection range for the jobnet connector.

(S)

Places the jobnet connector into Ended abnormally status.

(O)

Correct the error, and then re-execute the jobnet connector.

KAVS4714-E

Cannot execute the jobnet of the connection destination (jobnet-name) because the connection host name of the jobnet connector is invalid.

The connection-destination jobnet cannot be executed because the connection host name specified for the jobnet connector is invalid. The probable cause is:

The connection host name specified for the jobnet connector does not match the host name specified for the connection-destination jobnet.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Correct the error, and then re-execute the connection-destination jobnet.

KAVS4715-E

Cannot execute the jobnet of the connection destination (jobnet-name) because the connection service name of the jobnet connector is invalid.

The connection-destination jobnet cannot be executed because the connection service name specified for the jobnet connector is invalid. The probable cause is:

The connection service name specified for the jobnet connector does not match the scheduler service for the connection-destination jobnet.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Correct the error, and then re-execute the connection-destination jobnet.

KAVS4716-E

Cannot execute the jobnet of the connection destination (jobnet-name) because the connection range of the jobnet connector is invalid.

The connection-destination jobnet cannot be executed because the connection range specified for the jobnet connector is invalid. The probable cause is:

The connection range specified for the jobnet connector is different from the connection range for the connection-destination jobnet.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Correct the error, and then re-execute the connection-destination jobnet.

KAVS4720-E

An attempt to connect to the process controlling communication between scheduler services has failed. (scheduler-service-name) : maintenance-information

An attempt to connect to the scheduler service inter-communication control process has failed.

(S)

If the number of reconnections has not reached the threshold, the system outputs a KAVS4722-I message and then starts reconnection processing. If the reconnection is successful, the system outputs a KAVS4723-I message.

If the number of reconnections has reached the threshold, the system outputs a KAVS4724-E message and sets reduced mode for the execution order control for root jobnets between scheduler services.

(O)

Take action according to the message that was output before or after this error message.

KAVS4721-E

The connection with the process controlling communication between scheduler services was closed. (scheduler-service-name) : maintenance-information

The connection with the scheduler service inter-communication control process has been disconnected.

(S)

If the number of reconnections has not reached the threshold, the system outputs a KAVS4722-I message and then starts reconnection processing. If the reconnection is successful, the system outputs a KAVS4723-I message.

If the number of reconnections has reached the threshold, the system outputs a KAVS4724-E message and sets reduced mode for the execution order control for root jobnets between scheduler services.

(O)

Take action according to the message that was output before or after this error message.

KAVS4722-I

Reconnection processing with the process controlling communication between scheduler services started. (scheduler-service-name)

Reconnection processing with the scheduler service inter-communication control process will now start.

(S)

Starts the reconnection processing with the scheduler service inter-communication control process.

KAVS4723-I

Reconnect to the process has finished. (scheduler-service-name)

The scheduler service inter-communication control process is reconnected.

(S)

Continues operation.

KAVS4724-E

The number of times the process controlling communication between scheduler services has Reconnection has exceeded the threshold. Therefore,the process controlling communication between scheduler services has been Reconnection processing blocked. (scheduler-service-name)

Reconnection was attempted because disconnection of communication with the scheduler service inter-communication control process was detected, but the connection could not be established before the number of times reconnection was attempted exceeded the threshold. Therefore, the reconnection processing is canceled.

(S)

Continues processing in reduced mode for the execution order control for root jobnets between processing scheduler services. The system abnormally terminates the running jobnet connector for which Other service is specified for Connection range and any connection-destination jobnet whose status is Wait for start time.

Any jobnet connector or connection-destination jobnet for which execution is attempted in reduced mode for the execution order control also terminates abnormally.

(O)

To control the execution order for root jobnets between scheduler services, restart the scheduler service to cancel reduced mode for the execution order control.

KAVS4725-E

An IPC error occurred in the process controlling communication between scheduler services. (scheduler-service-name) : maintenance-information

An error occurred in the scheduler service inter-communication control process. The probable causes are:

Connection between the scheduler service inter-communication control process and another process is disconnected.

The number of connections that the scheduler service inter-communication control process uses for communication has exceeded the maximum.

The scheduler service inter-communication control process failed to resolve the host name.

The scheduler service specified for the connection service name for the jobnet connector or connection-destination jobnet is not running.

The scheduler service inter-communication control process is not running on the host specified for the connection host name for the jobnet connector or connection-destination jobnet.

(S)

Continues processing.

(O)

Take action according to the message that was output before or after this error message.

If no such message was output, check whether the scheduler service inter-communication control process is running on the host specified for the connection host name, or whether the scheduler service specified for the connection service name is running.

KAVS4730-E

Cannot execute the jobnet connector (jobnet-name) because it failed to resolved to the local host name(host:host-name).

The jobnet connector cannot be executed because an attempt to resolve the local host name has failed.

(S)

Places the jobnet connector into Ended abnormally status.

(O)

Confirm that the name of the host for which the jobnet connector has been defined is set correctly in the hosts, jp1hosts, and jp1hosts2 files.

Correct the settings, and then re-execute the jobnet connector.

KAVS4731-E

Cannot execute the jobnet connector (jobnet-name) because it failed to resolved to the connection host name of the jobnet of the connection destination.

The jobnet connector cannot be executed because an attempt to resolve the connection host name specified for the connection-destination jobnet has failed.

(S)

Places the jobnet connector into Ended abnormally status.

(O)

Confirm that the host specified for the connection host name for the connection-destination jobnet is correctly configured in the hosts, jp1hosts, or jp1hosts2 files of the host for which the destination jobnet has been defined.

Correct the settings, and then re-execute the jobnet connector.

KAVS4732-E

Cannot execute the jobnet (jobnet-name) of the connection destination because it failed to resolved to the local host name (host:host-name).

The connection-destination jobnet cannot be executed because an attempt to resolve the local host name has failed.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Confirm that the name of the host for which the jobnet has been defined is set correctly in the hosts, jp1hosts, and jp1hosts2 files.

Correct the settings, and then re-execute the connection-destination jobnet.

KAVS4733-E

Cannot execute the jobnet (jobnet-name) of the connection destination because it failed to resolved to the connection host name of the jobnet connector.

The connection-destination jobnet cannot be executed because an attempt to resolve the connection host name specified for the jobnet connector has failed.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Confirm that the host specified for the connection host name for the jobnet connector is correctly configured in the hosts, jp1hosts, or jp1hosts2 files of the host for which the jobnet connector has been defined.

Correct the settings, and then re-execute the connection-destination jobnet.

KAVS4750-E

Because of the incomplete description of jobnet(name:unit-name, release ID:release-ID),jobnet(name:unit-name, release ID:release-ID) cannot be scheduled.

A generation could not be created because the jobnet schedule definition contained an error.

(S)

The system operates as follows when a jobnet is registered for execution:

If the jobnet registered for execution is displayed in the message as a jobnet that cannot be scheduled, the registration fails.

If the jobnet displayed in the message as a jobnet that cannot be scheduled has already been registered for execution, the system handles the jobnet as follows:

- If the jobnet is registered for planned execution, the system places the jobnet into Shutdown status.

- If the jobnet is registered for fixed execution, the system does not create a next execution schedule.

(O)

If the status of the jobnet definition that has the release ID indicated in release-ID is Release wait, follow the procedure below:

Unregister the jobnet indicated in unit-name.

Cancel the release for the jobnet indicated in unit-name.

Correct the error in the schedule definition.

Enter the corrected jobnet definition for release again for the jobnet indicated in unit-name.

If the status of the jobnet definition that has the release ID indicated in release-ID is Being applied, follow the procedure below:

Unregister the jobnet indicated in unit-name.

Correct the error in the schedule definition.

Re-register the jobnet indicated in unit-name for execution.

If a jobnet with an invalid definition does not have release information, *** is displayed in release-ID for the jobnet. In this case, take the same action as for a jobnet definition whose status is Being applied.

KAVS4751-W

Since the new generation(execution-ID) is created to change the jobnet definition of the generation(unit-name:execution-ID), information of the temporary change in plan before the definition change is lost.

If an operation that switches a jobnet definition and creates new generations is performed, information about the changes made by using Change Plan before the jobnet definition is switched will be lost.

(S)

Continues processing.

(O)

Use information such as the scheduler log to check the changes made by using Change Plan for the generations before the jobnet definition is switched, and then make these changes again for the new generations after the jobnet definition is switched.

If the release entry or release cancellation switches a jobnet definition, *** appears in execution ID in the message because all generations after the release date are re-created. If necessary, use information such as the schedule log to apply the changes that were made by using Change Plan to the generations that are created after the release date.

KAVS4752-E

The generation(execution-ID) of the jobnet(unit-name) is in invalid status because an error occurred during change processing of the jobnet definition. : maintenance-information-1 maintenance-information-2

An attempt to delete the generations of the old definition has failed during switching of the jobnet definition. As a result, part of the jobnet execution registration information is missing.

(S)

Cancels processing.

(O)

Correct the problem according to the message that was output immediately before this message.

If the message appears when one of the following operations is performed, take appropriate action as shown below.

If the message appears during release entry for the jobnet indicated in the message, cancel the execution registration of the jobnet, cancel the release, and then perform the release entry again. After the release entry is performed, re-register the jobnet for execution.

If the message appears during release cancellation for the jobnet indicated in the message, cancel the execution registration of the jobnet, and then retry the release cancellation. After the release cancellation is performed, re-register the jobnet for execution.

If the message appears while execution is being prohibited for the jobnet indicated in the message, cancel the execution registration of the jobnet, re-register it for execution, and then prohibit execution of unnecessary schedules.

If the message appears when an operation other than the above is performed, cancel the execution registration of the jobnet, and then re-register it for execution.

KAVS4822-I

Execution registration information of the unit (unit-name) was not output, because its registration method is not supported for export.

The registered execution-schedule information for jobnets was not exported because the target unit was registered for immediate execution.

(S)

Continues command processing.

KAVS4823-E

The unit (unit-name) cannot be registered for execution, because it does not exist in the execution registration information file.

The specified unit did not exist in the registered execution-schedule information for jobnets file.

(S)

Continues command processing.

(O)

Check the specified unit name, and then execute the command.

KAVS4824-E

The unit (unit-name) cannot be imported, because you are not the user who exported it.

An attempt to import the registered execution-schedule information for jobnets has failed because the user who registered the unit to which the registered execution-schedule information for jobnets was exported is different from the user who performed the import.

(S)

Cancels command execution.

(O)

Check the user who executes the command, and then execute the command.

If multiple users have registered the root jobnet for fixed execution, only a user who has administrator privileges (in Windows) or superuser privileges (in UNIX) can perform the import. Note, however, that if the value of the ADMACLIMIT environment setting parameter has been changed to yes from the default, a JP1 user mapped to an OS user with administrator permissions or superuser privileges also requires command execution permissions.

KAVS4826-E

Invalid information in execution registration information file (file-name). (sentence-number:n)

The jobnet registered execution-schedule information file is coded incorrectly.

The probable causes are:

Invalid information is entered.

The unit name specified for UNIT= exceeds 930 bytes.

A host name or execution ID is specified for the unit name specified for UNIT=.

A value other than s is specified for ENTRY=.

A left-side value is not specified for the format.

A right-side value is enclosed in double quotation marks (") or single quotation marks (').

(S)

Cancels command execution.

(O)

Check the contents of the jobnet registered execution-schedule information file, and then execute the command.

KAVS4827-E

More than one jobnet is specified.

More than one unit is specified.

(S)

Cancels command execution.

(O)

Specify only one unit, and then re-execute the command.

KAVS4828-E

I/O error occurred. :maintenance-information

An I/O error occurred during input or output processing for a file.

(S)

Cancels processing for the file in which the error occurred, and then terminates the command.

(O)

Take action as shown below.

In Windows:

See the Windows event log and take action according to the output message. If you cannot take corrective action, contact the system administrator.

In UNIX:

See the syslog and take action according to the output message. If you cannot take corrective action, contact the system administrator.

KAVS4829-E

Specified file name (file-name) is too long.

A file name is specified using a character string of more than 255 bytes.

(S)

Cancels command execution.

(O)

Specify a file name that has fewer than 256 bytes, and then re-execute the command.

KAVS4830-E

Execution registration information of some units could not be exported. : maintenance-information

Registered execution-schedule information for jobnets could not be output because command execution failed.

(S)

Cancels command execution.

(O)

Take action according to the instructions given by the error message that was output before this message. Alternatively, the setup environment might be invalid. Make sure that the JP1/AJS3 setup is completed correctly, and then re-execute the command.

KAVS4832-E

An error occurred while processing the unit (unit-name). : maintenance-information

An error occurred during processing for the target unit.

(S)

Continues the command.

(O)

Take action according to the instructions given by the error message that was output before this message. See the output command line and take corrective action for the problem. Then re-execute the command.

KAVS4833-I

Information that is temporarily changed in the plan for the unit (unit-name) is not exported.

A unit in which changes were made by using Change Plan is exported. The information that is changed by using Change Plan is not exported.

(S)

Continues the command.

(O)

Any information that was changed by using Change Plan is not exported. Before you attempt to import the registered execution-schedule information for jobnets, change the plan again.

KAVS4834-E

The upcoming schedule for the specified jobnet (unit-name) was being created, and therefore the execution registration information could not be exported.

The registered execution-schedule information for jobnets could not be exported because the next schedule for the specified jobnet was being created.

(S)

Continues the command.

(O)

Make sure that the jobnet is not running or is not undertaking an operation such as execution registration, and then re-execute the command.

If you are going to export many units at one time, export them in several operations.

KAVS4835-E

The registration information file contains a unit that does not exist. : maintenance-information

The jobnet registered execution-schedule information file contains a unit that does not exist.

(S)

Continues the command.

(O)

Check the definition of the unit name indicated in maintenance-information. Alternatively, delete unnecessary unit information from the schedule information section for the unit indicated in maintenance-information for the jobnet registered execution-schedule information file.

KAVS4836-E

The specified unit (unit-name) can not be exported either because it does not exist or execution registration has not been performed.

The unit could not be exported. The probable causes are:

A unit that does not exist is to be exported.

A unit other than a root jobnet is to be exported.

(S)

Continues the command.

(O)

The specified unit does not exist or is not registered for execution. Check the status of the unit, and then re-execute the command.

KAVS4837-I

There is no information to be exported.

As a result of executing the command, there is no information that can be exported.

(S)

Terminates the command.

(O)

The registered execution-schedule information for jobnets was not output because the unit for the specified unit does not exist or because the specified unit does not exist.

KAVS4838-E

Units that exist in different scheduler services cannot be specified at the same time (unit-name).

Processing was canceled because units that exist in different scheduler services were specified at the same time.

(S)

Terminates the command.

(O)

Specify the units only in the same scheduler service, and then export them.

KAVS4839-I

Registration information for the unit (unit-name) was not output because either the unit has not been registered or there is no future schedule.

The registered execution-schedule information for jobnets was not output because a root jobnet that has not been registered or had no future schedule was specified.

(S)

Continues the command.

(O)

Specify a root jobnet that has a scheduled generation.

KAVS4900-I

The process controlling communication between scheduler services has started.

This message reports that the scheduler service inter-communication control process has started.

(S)

Continues processing.

KAVS4901-I

The process controlling communication between scheduler services has terminated.

This message reports that the scheduler service inter-communication control process has terminated.

(S)

Continues processing.

KAVS4902-W

The process (host:host-name, PID:process-ID) controlling communication between scheduler services has terminated abnormally (maintenance-information).

The scheduler service inter-communication control process terminated abnormally.

(S)

Cancels processing of the scheduler service inter-communication control process.

(O)

Restart the scheduler service inter-communication control process until the number of times this process terminates abnormally reaches the threshold. When the threshold is reached, block the scheduler service inter-communication control process.

KAVS4903-I

The management process for the process controlling communication between scheduler services has started.

This message reports that the management process for the scheduler service inter-communication control process has started.

(S)

Continues processing.

KAVS4904-I

The management process for the process controlling communication between scheduler services has terminated.

This message reports that the management process for the scheduler service inter-communication control process has terminated.

(S)

Continues processing.

KAVS4905-E

The management process for the process controlling communication between scheduler services has terminated abnormally (maintenance-information).

The management process for the scheduler service inter-communication control process terminated abnormally.

(S)

Cancels processing of the management process for the scheduler service inter-communication control process.

(O)

Take action according to the Windows event log or syslog message that was output immediately before this message. If you cannot correct the problem, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS4906-W

The value (item-name), specified in the environment settings parameter (parameter-name), is out of range. The default value (default) will be assumed and processing will continue.

Because the value specified for the environment setting parameter is invalid, the system assumes the default value to continue processing.

(S)

Assumes the value indicated in default and continues processing.

(O)

Correct the value of the environment setting parameter, and then restart the JP1/AJS3 service.

KAVS4907-W

The number of connections for the process (host:host-name) controlling communication between scheduler services has exceeded the maximum value, and therefore the connection could not be made with the connection destination host (host:host-name or IP-address).

The connection could not be established because the number of connections for the scheduler service inter-communication control process has exceeded the maximum.

(S)

Continues processing.

Note that you cannot use the execution order control for root jobnets between processing scheduler services until the number of connections has dropped below the maximum.

Also note that either of the following occurs until a KAVS4918-I message is output.

The connection-destination jobnet for which Synchro is specified for Exec. order method is placed into Ended abnormally status.

The jobnet connector is placed into Ended abnormally status.

(O)

After the KAVS4918-I message is output, re-execute the jobnet connector or connection-destination jobnet that could not be connected.

In addition, re-estimate the value of the GWMAXCONNECTION environment setting parameter according to 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS4908-E

The process(host:host-name) controlling communication between scheduler services failed to communicate with a process (name:process-name) of the same host. : maintenance-information

The scheduler service inter-communication control process failed to communicate with a process of the same host.

For a process that is started for each scheduler service, the process name is output in the scheduler-service-name:process-name format.

(S)

Terminates communication with the process indicated in the message.

(O)

Take action according to the Windows event log or syslog message that was output immediately before this message. If no such message was output, check whether the process indicated in the message is running.

If you cannot correct the problem, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS4909-E

The process(host:host-name) controlling communication between scheduler services failed to communicate with the process (host:host-name or IP-address) controlling communication between scheduler services at the communication destination. : maintenance-information

The scheduler service inter-communication control process failed to communicate with the scheduler service inter-communication control process at the communication destination.

(S)

Terminates communication with the scheduler service inter-communication control process at the communication destination.

(O)

Take action according to the Windows event log or syslog message that was output immediately before this message. If no such message was output, check whether the scheduler service inter-communication control process indicated in the message is running.

If you cannot correct the problem, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS4910-E

An error occurred during the communication with the process (host:host-name or IP-address name:process-name) because a network access error occurred. : maintenance-information

A network access error occurred during communication with the process.

For the process that is started for each scheduler service, the process name is output in the scheduler-service-name:process-name format.

(S)

Terminates communication.

(O)

Check the environment for communication with the process.

KAVS4911-E

A communication timeout occurred during the communication with the process (host:host-name or IP-address name:process-name). : maintenance-information

A communication timeout occurred during communication with the process.

For the process that is started for each scheduler service, the process name is output in the scheduler-service-name:process-name format.

(S)

Terminates communication.

(O)

Check the environment for communication with the process.

KAVS4912-E

A buffer shortage occurred during the communication with the process (host:host-name or IP-address name:process-name). : maintenance-information

A buffer shortage occurred during communication with the process.

For the process that is started for each scheduler service, the process name is output in the scheduler-service-name:process-name format.

(S)

Terminates communication.

(O)

Check the environment for communication with the process.

KAVS4913-E

The port number could not be obtained. Confirm whether the service name is defined correctly.

An attempt to acquire the port number used by the scheduler service inter-communication control process has failed.

(S)

Terminates the scheduler service inter-communication control process.

(O)

Check whether the service name and the port number for jp1ajs2gw are set correctly in the services file. If the port number is correctly defined, memory or disk space might be insufficient. Terminate unnecessary applications, and then restart the JP1/AJS3 service.

KAVS4914-E

The connection was reset while the process (host:host-name) controlling communication between scheduler services was communicating with the process (host:host-name or IP-address) controlling communication between scheduler services at the communication destination. : maintenance-information

The connection was reset while the scheduler service inter-communication control process was communicating with the scheduler service inter-communication control process at the communication destination. The probable causes are:

The JP1/AJS3 service on the destination host has stopped.

An error occurred on the scheduler service inter-communication control process at the communication destination.

The scheduler service inter-communication control process at the communication destination terminated abnormally.

The communication encryption function is disabled on the communication source host and enabled on the communication destination host.

(S)

Terminates communication with the scheduler service inter-communication control process at the communication destination.

(O)

If necessary, check whether the scheduler service inter-communication control process is running on the communication destination host, and whether the communication encryption function is set correctly.

If the communication encryption function is disabled on the communication source host and enabled on the communication destination host, match the settings on both hosts, and then restart the JP1/Base service and JP1/AJS3 service.

KAVS4915-I

The process (host:host-name) controlling communication between scheduler services has restarted.

This message reports that the scheduler service inter-communication control process has restarted.

(S)

Restarts the scheduler service inter-communication control process.

KAVS4916-W

The process (host:host-name) controlling communication between scheduler services failed to start (maintenance-information).

An attempt to start the scheduler service inter-communication control process has failed. A probable cause is insufficient system resources.

(S)

Terminates the scheduler service inter-communication control process.

(O)

Check the reason for the unsuccessful startup of the scheduler service inter-communication control process according to the message that was output before or after this message, and then take appropriate action.

KAVS4917-E

The number of times the process (host:host-name) controlling communication between scheduler services has terminated abnormally has exceeded the threshold. Therefore, the process controlling communication between scheduler services has been blocked.

The scheduler service inter-communication control process was blocked because the number of times this process terminated abnormally has exceeded the threshold.

(S)

Blocked the scheduler service inter-communication control process because the threshold was exceeded.

(O)

Memory might be insufficient, or the maximum number of processes that can be started in the system might have been reached.

In UNIX, review the settings of the kernel parameters related to memory and processes, and then re-set the values. For details about the kernel parameters, see 3.2.5 Estimating the values for kernel parameters in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide. For details about how to estimate the size of memory used, see 3.2.3 Estimating the size of memory used in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Check the status of the processes that were running when the error occurred, and make sure that the amount of memory available is greater than the estimated value.

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

KAVS4918-I

The number of connections for the process (host: host-name)controlling communication between scheduler services is below the maximum value.

Because the number of connections for the scheduler service inter-communication control process is below the maximum value, execution order control for root jobnets between different scheduler services is now possible.

(S)

Continues processing.

KAVS4931-I

The TCP/IP port number is not set, because the AJS administrator executed this command. Set TCP/IP port number. : command-name

The TCP/IP port number was not set because the AJS administrator executed the indicated command. The TCP/IP port number will need to be set manually.

(S)

Continues processing.

(O)

If this message appears when you execute the ajschksetup command, manually register the following communication ports in the services file.

Function

Service name

Port number

Registered in:

JP1/AJS3 - Manager

JP1/AJS3 - Agent

Definition pre-check function that is used

jp1ajs2chkman

23138/tcp

Yes

No

jp1ajs2chkagt

23139/tcp

Yes

No

Legend:

Yes: Register the port number.

No: Do not register the port number.

If this message appears when you execute the ajsqlsetup command, manually register the following communication ports in the services file.

Function

Service name

Port number

Registered in:

JP1/AJS3 - Manager

JP1/AJS3 - Agent

Execute queueless jobs

jp1ajs2qlagt

20300/tcp

Yes

Yes

Transfer queueless files

jp1ajs2qlftp

20301/tcp

Yes

Yes

Legend:

Yes: Register the port.

If this message appears when you execute the ajsatsetup command, manually register the following communication ports in the services file.

Function

Service name

Port number

Registered in:

JP1/AJS3 - Manager

JP1/AJS3 - Agent

Execute flexible jobs

jp1ajs2atmsg

22251/tcp

Yes

Yes

Legend:

Yes: Register the port.

For details about communication ports, see A.1 Tables of port numbers in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVS4933-I

The setup of the AJS administrator(user-name) started.

Setup of the AJS administrator will now start.

(S)

Continues installation.

KAVS4934-E

The AJS administrator name is invalid.

The AJS administrator name specified in the JP1AJS3_ADMINUSR_NAME environment variable is invalid.

(S)

Cancels installation.

(O)

Specify the correct AJS administrator name for the JP1AJS3_ADMINUSR_NAME environment variable, and then retry the installation.

KAVS4935-E

The JP1 administrators group is not set up.

The JP1 administrators group has not been set up.

(S)

Cancels installation.

(O)

Set up the JP1 administrators group, and then retry the installation.

KAVS4936-E

The JP1 administrators group(group-name) does not exist.

The JP1 administrators group (group-name) set up by using the JP1/Base function does not exist.

(S)

Cancels installation.

(O)

Create by using the OS function the OS group that was set up as the JP1 administrators group, and then retry the installation.

KAVS4937-E

The OS user(user-name) specified does not exist.

Only an existing OS user can be specified as an AJS administrator.

(S)

Cancels installation.

(O)

Specify an existing OS user as an AJS administrator, and then retry the installation.

KAVS4938-E

The AJS administrator cannot specify the OS user of a primary group that is not the JP1 administrators group.

An OS user whose primary group is not the JP1 administrators group is specified as an AJS administrator.

(S)

Cancels installation.

(O)

Change the primary group of the OS user specified as an AJS administrator to the JP1 administrators group, and then retry installation.

KAVS4939-I

The AJS administrator is (AJS-administrator-name, uid=user-ID, JP1-administrators-group-name, gid=group-ID).

Information about the AJS administrator that has been set up is output.

(S)

Continues the command processing.

KAVS4941-I

The AJS administrator is not set.

The AJS administrator has not been set up.

(S)

Continues the command processing.

(O)

For details about how to set up the AJS administrator, see D. Installation and Setup for Operation by AJS Administrators (UNIX only) in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS4943-E

The execution permission environment is invalid. maintenance-information

The execution permission environment is invalid. The probable causes are:

The user is neither an AJS administrator nor a superuser.

The JP1 administrators group name was changed.

The OS user specified as the AJS administrator was deleted.

The primary group name of the OS user specified as the AJS administrator was changed.

(S)

Cancels the command.

(O)

Configure the execution permission environment correctly, and then re-execute the operation.

KAVS4944-E

Failed to set the AJS administrator. : maintenance-information, maintenance-information, maintenance-information

An attempt to set the AJS administrator failed.

(S)

Cancels the command.

(O)

Determine the cause of the error and take appropriate corrective action. If you cannot determine the cause, collect data and contact the system administrator (see 1.2.3 To the system administrators).

KAVS4950-I

The wait for the end of the preceding jobnet (name: unit-full-name:execution-ID) has begun.

The unit with wait conditions indicated in the message has begun waiting for the unit whose end is being waited for.

The execution ID is output if yes is specified for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

KAVS4951-I

The wait for the end of the preceding job (name: unit-full-name:execution-ID) has begun.

The unit with wait conditions indicated in the message has begun waiting for the unit whose end is being waited for.

The execution ID is output if yes is specified for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

KAVS4952-E

Waiting for the end of the preceding unit (name: unit-full-name:execution-ID) was not possible because an error occurred. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

The unit with wait conditions indicated in the message could not wait for the unit whose end is being waited for because an error occurred.

(S)

Cancels the wait process by the unit with wait conditions indicated in the message with respect to the unit whose end is being waited for.

(O)

Determine the cause of the error from the error message output before this one, and take appropriate action. Then, re-execute the unit with wait conditions indicated in the message.

KAVS4954-E

The unit (name: unit-full-name:execution-ID), whose end was to be waited for by a unit with wait conditions (name: unit-full-name:execution-ID), is not a unit whose end can be waited for.

Waiting cannot take place because the unit whose end is being waited for indicated in the message is invalid.

(S)

Cancels the wait process by the unit with wait conditions indicated in the message with respect to the unit whose end is being waited for.

(O)

The unit whose end is being waited for indicated in the message cannot be waited for.

The probable causes are as follows:

A unit whose end cannot be waited for is specified as a unit whose end is being waited for.

The unit specified as a unit whose end is being waited for does not exist.

Both an unlimited execution count and an unlimited period are set as the valid range of start conditions for a jobnet that has start conditions and whose end is being waited for.

In the wait conditions of the unit indicated in the message, specify a unit whose end can be waited for and then re-execute the unit.

To extend the units that are specifiable as units whose end is being waited for, use the PREWAITEXTEND environment setting parameter. For details about this environment setting parameter, see 20.4.2(99) PREWAITEXTEND in the JP1/Automatic Job Management System 3 Configuration Guide.

A unit with wait conditions must be suspended before you can amend its wait condition. If you cannot suspend the unit, perform a temporary change that sets the waiting status to Wait complete (manual) with respect to the unit whose end is being waited for indicated in the message, and then re-execute the unit.

If the system cannot determine the execution ID of the unit whose end is being waited for, asterisks (***) appear as the execution ID in the message.

KAVS4955-I

The wait conditions for the jobnet (name: unit-full-name:execution-ID) were approved. (approval factor: approval-factor)

The wait conditions for the jobnet indicated in the message have been satisfied.

The execution ID is output if yes is specified for the LOGINFOALL environment setting parameter.

Approval factor: 1

The wait condition was satisfied according to the AND wait method.

Approval factor: 2

The wait condition was satisfied according to the OR wait method.

Approval factor: 3

The wait condition was satisfied because there are no applicable generations of units whose ends are being waited for, and the system is configured to start executing the jobnet in these circumstances.

(S)

Continues processing.

KAVS4956-I

The wait conditions for the job (name: unit-full-name:execution-ID) were approved. (approval factor: approval-factor)

The wait conditions for the job indicated in the message have been satisfied.

The execution ID is output if yes is specified for the LOGINFOALL environment setting parameter.

Approval factor: 1

The wait condition was satisfied according to the AND wait method.

Approval factor: 2

The wait condition was satisfied according to the OR wait method.

Approval factor: 3

The wait condition was satisfied because there are no applicable generations of units whose ends are being waited for, and the system is configured to start executing the job in these circumstances.

(S)

Continues processing.

KAVS4957-E

A jobnet (name: unit-full-name:execution-ID) cannot finish waiting because the unit whose end was to be waited for (name: unit-full-name:execution-ID) is in a state for which waiting is not possible. (cause number: cause-number)

The status of the unit whose end is being waited for has prevented the jobnet with wait conditions indicated in the message from finishing the waiting process.

The message outputs the execution ID of the jobnet that cannot finish waiting if yes is specified for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

(O)

Take action according to the cause number output in the message.

The appropriate action for each cause number is as follows:

Cause number: 1

The wait condition (wait method AND) was not satisfied because the status of the unit whose end is being waited for indicated in the message does not allow the wait condition to be satisfied. The probable causes are as follows:

The unit finished executing in a status that does not allow waiting to finish

A jobnet with start conditions whose end is being waited for is in a status that does not allow waiting to finish

The unit is suspended

The unit has not been registered

The status was changed by re-executing the succeeding unit

If the unit in the message whose end is being waited for finished executing in a status that does not allow waiting to finish, either rerun that unit or change its status to one that allows waiting to finish. For details about the statuses that allow waiting to finish, see 2.2.5(1)(a) Units with wait conditions and units whose ends are being waited for in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

If the unit in the message whose end is being waited for is suspended, check the following points. Then, release the unit whose end is being waited for from the suspended state.

Does the unit whose end is being waited for exist?

Is the unit a type that can be waited for?

If the unit in the message whose end is being waited for has not been registered, register the unit for execution.

If the status of the unit (indicated in the message) whose end is being waited for is Ended normally, Ended with warning, or Bypassed, the status was changed by re-executing the succeeding unit. Re-execute the unit whose end is being waited for.

If this approach fails to resolve the problem, perform a temporary change operation to disable waiting for the unit to be waited for indicated in the message.

Note that if the unit whose end is being waited for has not been registered, asterisks (***) appear as the execution ID in the message.

Cause number: 2

The wait condition (wait method AND) was not satisfied because there are no applicable generations of the unit whose end is being waited for, and the system is configured not to execute the jobnet in these circumstances. The probable causes are as follows:

There are no generations of the unit whose end is being waited for.

The number of generations of the unit with wait conditions does not match that of the unit whose end is being waited for.

The number of logs to keep of the unit with wait conditions, the unit whose end is being waited for, or both is not sufficient to save the execution results from one day of operation.

Add an execution schedule that satisfies the waiting rule to the unit whose end is being waited for indicated in the message. Alternatively, in the case of 3. above, the system might have been unable to obtain generation information because generations were being deleted. Check whether the execution ID of the unit whose end is being waited for appears in the Wait Conditions Statuses window of JP1/AJS3 - View or in the -xw option of the ajsshow command. If the execution ID appears, the unit can be waited for and the problem is resolved. You can prevent this error message from appearing by ensuring that the number of logs to keep allows the system to save one day's worth of execution results for the unit with wait conditions and the unit whose end is being waited for.

If you cannot take this approach, perform a temporary change operation to disable waiting for the unit to be waited for indicated in the message.

For this cause, asterisks (***) appear as the execution ID of the unit in the message whose end is being waited for.

Cause number: 3

The wait condition (wait method OR) was not satisfied because the unit with wait conditions indicated in the message cannot finish waiting for all units whose ends are being waited for.

The probable reasons are as follows. Check the statuses of all the units whose ends are being waited for, and take the appropriate action.

A unit whose end is being waited for terminated in a status that does not allow waiting to finish.

Take the action described for cause number 1.

The unit is suspended.

Take the action described for cause number 1.

The unit whose end is being waited for is not registered for execution.

Take the action described for cause number 1.

The status was changed by re-executing the succeeding unit.

Take the action described for cause number 1.

There are no applicable generations of the unit whose end is being waited for, and the system is configured not to execute the unit in these circumstances.

Take the action described for cause number 2.

For cause number 3, asterisks (***) appear as the full unit name and execution ID of the unit in the message whose end is being waited for.

KAVS4958-I

The jobnet (name: unit-full-name:execution-ID) is now able to wait for the end of the unit (name: name-of-unit-whose-end-is-being-waited-for:execution-ID).

The jobnet is now able to wait for the unit whose end is being waited for indicated in the message. The execution ID of the jobnet appears if you specified yes for the LOGINFOALL environment setting parameter.

If the wait method of the wait condition is OR, this message is only output for the first unit whose end is being waited for that transitions to a status that allows waiting.

(S)

Continues processing.

KAVS4962-E

Waiting related to a unit (name: unit-full-name:execution-ID) was blocked because an error occurred. (cause number: cause-number) : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

The waiting process was blocked because an error occurred.

(S)

Cancels processing.

(O)

Take action according to the cause number output in the message.

The appropriate action for each cause number is as follows:

Cause number: 1

The unit whose end is being waited for indicated in the message cannot be waited for. Determine the cause from the error message output before this one, and remove the cause of the error. Then, perform the following procedure:

Check the execution start date of the unit whose end is being waited for indicated in the message.

In the Search window of JP1/AJS3 - View, for the unit with wait conditions that waits for the unit indicated in the message, search for the execution schedule that occurs on the start date you checked in step 1.

Select the applicable unit with wait conditions from the search results displayed in step 2, and open the Wait Conditions Statuses window. Make sure that the unit whose end is being waited for indicated in the message is in a status that allows waiting to finish.

If step 3 confirms that the unit whose end is being waited for is in a status that allows waiting to finish, perform a temporary change operation of the wait condition to disable waiting for the unit to be waited for indicated in the message.

If the unit with wait conditions is scheduled to execute multiple times per day or a 48 hour schedule is in effect, the unit might appear more than once in the search results in step 2. In this case, check the wait status of each unit, and perform a temporary change of the wait condition only with respect to the generation of the unit that is waiting for the unit identified by execution ID in the message.

Cause number: 2

A unit with wait conditions that meets any of the following criteria is unable to wait for a unit whose end is being waited for:

The unit indicated in the message is a unit with wait conditions

The unit with wait conditions is defined under the unit indicated in the message

The unit with wait conditions specifies the unit indicated in the message as a unit whose end is being waited for

The unit with wait conditions specifies a unit defined under the unit indicated in the message as a unit whose end is being waited for

Determine the cause from the error message output before this one, and remove the cause of the error. Then, perform the following procedure:

In the Search window of JP1/AJS3 - View, search for a unit with wait conditions that meets the above criteria.

Select the applicable unit with wait conditions from the search results displayed in step 1, and open the Wait Conditions Statuses window. Make sure that the unit whose end is being waited for indicated in the message is in a status that allows waiting to finish.

If step 2 confirms that the unit whose end is being waited for is in a status that allows waiting to finish, perform a temporary change operation of the wait condition to disable waiting for the unit to be waited for indicated in the message.

KAVS4971-E

A job (name: unit-full-name:execution-ID) cannot finish waiting because the unit whose end is to be waited for (name: unit-full-name:execution-ID) is in a state for which waiting is not possible. (cause number: cause-number)

The status of the unit whose end is being waited for has prevented the job with wait conditions indicated in the message from finishing the waiting process.

The message outputs the execution ID of the jobnet that cannot finish waiting if yes is specified for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

(O)

Take action according to the cause number output in the message.

The appropriate action for each cause number is as follows:

Cause number: 1

The wait condition (wait method AND) was not satisfied because the status of the unit whose end is being waited for indicated in the message does not allow the wait condition to be satisfied. The probable causes are as follows:

The unit finished executing in a status that does not allow waiting to finish

A jobnet with start conditions whose end is being waited for is in a status that does not allow waiting to finish

The unit is suspended

The unit has not been registered

The status was changed by re-executing the succeeding unit

If the unit in the message terminated in a status that does not allow waiting to finish, re-execute the unit or change the status so that waiting can finish. Also take this action if a jobnet with start conditions whose end is being waited for is in a status that does not allow waiting to finish. For details about the statuses that allow waiting to finish, see 2.2.5(1)(a) Units with wait conditions and units whose ends are being waited for in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

If the unit in the message whose end is being waited for is suspended, check the following points. Then, release the unit whose end is being waited for from the suspended state.

Does the unit whose end is being waited for exist?

Is the unit a type that can be waited for?

If the unit in the message whose end is being waited for has not been registered, register the unit for execution.

If the status of the unit (indicated in the message) whose end is being waited for is Ended normally, Ended with warning, or Bypassed, the status was changed by re-executing the succeeding unit. Re-execute the unit whose end is being waited for.

If this approach fails to resolve the problem, perform a temporary change operation to disable waiting for the unit to be waited for indicated in the message.

Note that if the unit whose end is being waited for has not been registered, asterisks (***) appear as the execution ID in the message.

Cause number: 2

The wait condition (wait method AND) was not satisfied because there are no applicable generations of the unit whose end is being waited for, and the system is configured not to execute the jobnet in these circumstances. The probable causes are as follows:

There are no generations of the unit whose end is being waited for.

The number of generations of the unit with wait conditions does not match that of the unit whose end is being waited for.

The number of saved generations of the unit with wait conditions, the unit whose end is being waited for, or both is not sufficient to save the execution results from one day of operation.

Add an execution schedule that satisfies the waiting rule to the unit whose end is being waited for indicated in the message. Alternatively, in the case of 3. above, the system might have been unable to obtain generation information because generations were being deleted. Check whether the execution ID of the unit whose end is being waited for appears in the Wait Conditions Statuses window of JP1/AJS3 - View or in the -xw option of the ajsshow command. If the execution ID appears, the unit can be waited for and the problem is resolved. You can prevent this error message from appearing by ensuring that the number of saved generations allows the system to save one day's worth of execution results for the unit with wait conditions and the unit whose end is being waited for.

If you cannot take this approach, perform a temporary change operation to disable waiting for the unit to be waited for indicated in the message.

For this cause, asterisks (***) appear as the execution ID of the unit in the message whose end is being waited for.

Cause number: 3

The wait condition (wait method OR) was not satisfied because the unit with wait conditions indicated in the message cannot finish waiting for all units whose ends are being waited for.

The probable reasons are as follows. Check the statuses of all the units whose ends are being waited for, and take the appropriate action.

A unit whose end is being waited for terminated in a status that does not allow waiting to finish, waiting cannot finish for a jobnet with start conditions and whose end is being waited for, or a unit is suspended.

Take the action described for cause number 1.

The unit whose end is being waited for is not registered for execution.

Take the action described for cause number 1.

The status was changed by re-executing the succeeding unit.

Take the action described for cause number 1.

There are no applicable generations of the unit whose end is being waited for, and the system is configured not to execute the unit in these circumstances.

Take the action described for cause number 2.

For cause number 3, asterisks (***) appear as the full unit name and execution ID of the unit in the message whose end is being waited for.

KAVS4973-I

A job (name: unit-full-name:execution-ID) is now able to wait for the end of a unit (name: name-of-unit-whose-end-is-being-waited-for:execution-ID).

The job is now able to wait for the unit whose end is being waited for indicated in the message. The execution ID of the job that can now wait for the unit is output if yes is specified for the LOGINFOALL environment setting parameter.

If the wait method of the wait condition is OR, this message is only output for the first unit whose end is being waited for that transitions to a status that allows waiting.

(S)

Continues processing.

KAVS4975-E

The preceding unit wait function cannot be used (scheduler-service-name). : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

A unit assigned a wait condition cannot be executed.

The probable causes are as follows:

The JP1/AJS3 database uses a compatible ISAM configuration

yes is not set for the PREWAITUSE environment setting parameter

Each unit you attempted to execute ends abnormally with the message KAVS4952-E.

(S)

Places the unit with wait conditions in Ended abnormally status.

(O)

If the JP1/AJS3 database uses a compatible ISAM configuration, migrate to the standard configuration by following the instructions in 8.5 Upgrading JP1/AJS2 - Manager to JP1/AJS3 - Manager in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

If the database already uses the standard configuration, check the value of the PREWAITUSE environment setting parameter. For details about the environment setting parameters, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS4976-E

A unit (name: unit-full-name:execution-ID) cannot begin waiting because its generation uses a start condition.

The unit indicated in the message is unable to begin the waiting process.

(S)

Cancels waiting by the unit with wait conditions indicated in the message with respect to units whose end is being waited for.

(O)

The unit with wait conditions cannot wait for the preceding unit because its generation uses a start condition. Review the jobnet definition and schedule definition.

KAVS4977-E

A unit (name: unit-full-name:execution-ID) cannot begin waiting because its type is invalid.

The unit indicated in the message is unable to begin the waiting process.

(S)

Cancels waiting by the unit with wait conditions indicated in the message with respect to units whose end is being waited for.

(O)

The unit with wait conditions is an invalid type. For details about which units are capable of accepting wait conditions, see 2.2.5(1)(a) Units with wait conditions and units whose ends are being waited for in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

KAVS4981-I

The output of JP1/AJS3 - Software Development Kit connection information is complete.

The output of JP1/AJS3 - Web Console and JP1/AJS3 - Software Development Kit connection information has terminated.

(S)

Terminates command processing.

KAVS4982-E

JP1/AJS3 - Software Development Kit connection information could not be obtained because the ajscdinetd process is not running.

JP1/AJS3 - Software Development Kit connection information cannot be acquired because the ajscdinetd process is not running.

The probable causes are:

The JP1/AJS3 service has not started.

The ajscdinetd process has not started because JP1/AJS3 - Web Console is not set up correctly.

The ajscdinetd process has not started because JP1/AJS3 - Software Development Kit is not set up correctly.

(S)

Terminates command processing.

(O)

Start the JP1/AJS3 service, and then re-execute the command.

If the JP1/AJS3 service is already running, make sure that JP1/AJS3 - Web Console is set up correctly.

For details about how to set up JP1/AJS3 - Web Console, see the JP1/Automatic Job Management System 3 Configuration Guide.

After the setup, start the JP1/AJS3 service, and then re-execute the command.

KAVS4991-I

The request will now start. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

The request from JP1/AJS3 - Web Console or JP1/AJS3 - Software Development Kit will start.

(S)

Continues processing.

KAVS4992-I

The request ended successfully. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

The request from JP1/AJS3 - Web Console or JP1/AJS3 - Software Development Kit ended.

(S)

Continues processing.

KAVS4993-E

The request ended abnormally. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4 maintenance-information-5 maintenance-information-6

An error occurred in the request from JP1/AJS3 - Web Console or JP1/AJS3 - Software Development Kit.

(S)

Continues processing.

(O)

Take action according to the message output to the host on which JP1/AJS3 - Web Console or JP1/AJS3 - Software Development Kit is running.

KAVS4994-I

The request ended with a warning. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

The request from JP1/AJS3 - Web Console or JP1/AJS3 - Software Development Kit ended with a warning.

(S)

Continues processing.

KAVS4995-I

The request was canceled. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

The request from JP1/AJS3 - Web Console or JP1/AJS3 - Software Development Kit was canceled.

(S)

Continues processing.

KAVS8001-I

The operation profile function was enabled. :maintenance-information

An operation profile was applied to a scheduler service.

(S)

Continues processing.

KAVS8002-I

The operation profile function will be disabled because it does not exist. :maintenance-information

The system disabled an operation profile for a scheduler service.

(S)

Continues processing.

KAVS8003-E

The operation profile does not exist in the environment settings file storage folder. :maintenance-information-1 maintenance-information-2 maintenance-information-3

There is no operation profile for the scheduler service in the environment settings file storage folder.

(S)

Cancels processing.

(O)

Place the operation profile in the environment settings file storage folder, and then execute the ajsprofalter command again.

KAVS8004-E

The syntax of the operation profile contains an error. (detail-message). operation-profile-name maintenance-information-1 maintenance-information-2

The operation profile could not be applied because its syntax contains an error. Details of the error are indicated by detail-message.

For details, see 21.1 Setting up functions by using operation profiles in the JP1/Automatic Job Management System 3 Configuration Guide.

(S)

Cancels processing.

(O)

Review the contents of the operation profile, and apply it again. You can apply an operation profile by the following:

Executing the ajsprofalter command

Restarting the scheduler service to which the operation profile is to be applied

Restarting the JP1/AJS3 service

KAVS8005-I

The operation profile function was disabled. :maintenance-information-1 maintenance-information-2

The operation profile of a scheduler service was disabled.

(S)

Continues processing.

KAVS8006-E

The operation profile function is not enabled. :maintenance-information-1 maintenance-information-2

The operation profile is not enabled for the scheduler service.

This message appears with execution of the following commands:

If output at execution of the ajsprofstatus command

The operation profile# specified in the -t option is invalid.

If output at execution of the ajsprofalter command

An attempt was made to disable the operation profile# specified in the -t option but the operation profile was already disabled.

#

If you specified the -F option, the message relates to the scheduler service you specified. If you did not specify the -F option, the message relates to the operation profile associated with the default scheduler service.

(S)

Cancels processing.

KAVS8007-I

Output of the operation profile information ended.

The system has finished outputting operation profile information.

(S)

Terminates command processing.

KAVS8008-E

You do not have the permissions required to use the operation profile. :maintenance-information

You do not have access permission for the operation profile.

(S)

Terminates command processing.

(O)

Grant access permission for the operation profile and then re-execute the command.

KAVS8009-E

The operation profile cannot be opened. :maintenance-information-1 maintenance-information-2 maintenance-information-3

An I/O error occurred with respect to the operation profile.

(S)

Terminates command processing.

(O)

Take action according to the error information in the Windows event log or syslog output by the OS, and other OS-specific error information. If you are unable to resolve the problem, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVS8010-E

The operation profile contains no valid information. :maintenance-information

The operation profile contains no valid information because it is empty or completely commented out.

(S)

Terminates command processing.

(O)

To disable the operation profile, continue operation.

To enable the operation profile, enter valid information in the operation profile and then re-execute the command.

KAVS8011-E

The size of the shared memory is smaller than the amount required to enable the operation profile function. :maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

The system cannot secure enough shared memory to apply the operation profile because the value specified for the UNITPROFMEMSIZE or AGENTPROFMEMSIZE environment setting parameter is too small.

(S)

Terminates command processing.

(O)

Check the value specified for the UNITPROFMEMSIZE or AGENTPROFMEMSIZE environment setting parameters, and then re-execute the command.

For details about the environment setting parameters, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS8012-E

Exclude error occurred. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

A lock error occurred during processing of the operation profile.

(S)

Cancels processing.

(O)

Make sure that the system file directory is accessible.

If error information has been output to the Windows event log or syslog by the OS, or other OS-specific information has been output in relation to the error, take action according to that information. If you are unable to resolve the problem, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVS8013-E

The job will be executed without applying the operation profile because an error occurred during processing to acquire operation profile information. unit-full-name execution-ID cause-code maintenance-information-1 maintenance-information-2 maintenance-information-3

The job will be executed without applying the operation profile because an error occurred in the process of acquiring operation profile information.

The nature of the error is indicated by its cause code, as follows:

DBERR: An error relating to database access occurred.

LOCKERR: An error relating to internal locking occurred.

SHMERR: An error occurred accessing shared memory.

MEMERR: A memory shortage occurred.

SYSERR: A conflict occurred in the internal logic of JP1/AJS3.

(S)

Continues processing.

(O)

Take action according to the cause code of the message.

DBERR: Take action according to the message beginning with KAVS that was output immediately before this message.

LOCKERR: Check for disk failures or other problems on the disk where the execution agent profile is located.

SHMERR: Review the shared memory size set in the kernel parameter.

MEMERR: Make sure that sufficient memory is available. See the Release Notes for details about the amount of memory required.

SYSERR: Contact the system administrator and collect data.

No cause code: Take action according to the message output immediately before this one.

If you are still unable to resolve the error, contact the system administrator and collect data.

KAVS8014-E

An error occurred during processing to acquire operation profile information. unit-full-name cause-code maintenance-information-1 maintenance-information-2 maintenance-information-3

Because an error occurred in the process of acquiring operation profile information, processing of the unit indicated in unit-full-name will continue without the operation profile being applied. In the case of a unit attribute profile, you might inadvertently define a unit or execute a job outside the scope of its attribute profile.

The nature of the error is indicated by its cause code, as follows:

DBERR: An error relating to database access occurred.

LOCKERR: An error relating to internal locking occurred.

SHMERR: An error occurred accessing shared memory.

MEMERR: A memory shortage occurred.

SYSERR: A conflict occurred in the internal logic of JP1/AJS3.

(S)

Continues processing.

(O)

Take action according to the cause code of the message.

DBERR: Take action according to the message beginning with KAVS that was output immediately before this message.

LOCKERR: Check for disk failures or other problems on the disk where the execution agent profile is located.

SHMERR: Review the shared memory size set in the kernel parameter.

MEMERR: Make sure that sufficient memory is available. See the Release Notes for details about the amount of memory required.

SYSERR: Contact the system administrator and collect data.

If you are still unable to resolve the error, contact the system administrator and collect data.

KAVS8015-E

An invalid line exists. Line=line-number

The line in the operation profile indicated by line-number is invalid.

The probable cause is as follows:

The operation profile contains an error in a line that is not commented or blank.

(S)

Cancels processing.

(O)

Take action according to the message KAVS8004-E together with this message.

KAVS8016-E

The same setting is in multiple lines. Line=line-number

The line in the operation profile indicated by line-number is invalid.

The probable cause is as follows:

The same setting is specified on more than one line.

(S)

Cancels processing.

(O)

Take action according to the message KAVS8004-E together with this message.

KAVS8017-E

The record length exceeds the maximum. Line=line-number

The line in the operation profile indicated by line-number is invalid.

The probable cause is as follows:

A line exceeds the maximum length. The maximum lengths are as follows:

Lines with linefeed characters (LF: 0x0a and CR: 0x0d): 2,047 bytes excluding the linefeed characters

Lines without linefeed characters (LF: 0x0a and CR: 0x0d): 2,048 bytes

(S)

Cancels processing.

(O)

Take action according to the message KAVS8004-E together with this message.

KAVS8018-E

The description order is invalid. Line=line-number

The line in the operation profile indicated by line-number is invalid.

The probable causes are as follows:

For an execution agent profile:

The profile does not begin with a @SYS_RESTRICT_START line

For a unit attribute profile:

The profile does not begin with a @SYS_PROFILE_START line

(S)

Cancels processing.

(O)

Take action according to the message KAVS8004-E together with this message.

KAVS8019-E

The description is insufficient. Line=line-number

The line in the operation profile indicated by line-number is invalid.

The probable causes are as follows:

For an execution agent profile:

@SYS_RESTRICT_START without a corresponding @SYS_RESTRICT_END

unit_path does not exist

@SYS_AGENTLIST_START does not exist

No permitted execution hosts are set between @SYS_AGENTLIST_START and @SYS_AGENTLIST_END

@SYS_AGENTLIST_START without a corresponding @SYS_AGENTLIST_END

For a unit attribute profile:

@SYS_PROFILE_START without a corresponding @SYS_PROFILE_END

unit_path does not exist

(S)

Cancels processing.

(O)

Take action according to the message KAVS8004-E together with this message.

KAVS8020-E

The description position is invalid. Line=line-number

The line in the operation profile indicated by line-number is invalid.

The probable causes are as follows:

For an execution agent profile:

One or more of the following entries is in the wrong location:

@SYS_RESTRICT_START

unit_path

View

ViewCheckLevel

JobExec

@SYS_AGENTLIST_START

@SYS_AGENTLIST_END

For a unit attribute profile:

One or more of the following entries is in the wrong location:

@SYS_PROFILE_START

unit_path

InheritUnitAttr

FixedExecUser

(S)

Cancels processing.

(O)

Take action according to the message KAVS8004-E together with this message.

KAVS8021-E

The value is invalid. Line=line-number

The line in the operation profile indicated by line-number is invalid.

The probable causes are as follows:

For an execution agent profile:

The value of unit_path exceeds 930 bytes.

The value of unit_path is not in the form of a full unit name, or contains a character that cannot be specified in a full unit name.

An invalid value is specified for View, ViewCheckLevel, or JobExec.

Permitted execution hosts are specified using a character string of more than 255 bytes.

A permitted execution host contains a space or tab character.

Example: AAΔBB (where Δ indicates a space)

The escape character is specified incorrectly for a permitted execution host (\ is not followed by # or \).

For a unit attribute profile:

An invalid value is specified for InheritUnitAttr or FixedExecUser.

(S)

Cancels processing.

(O)

Take action according to the message KAVS8004-E together with this message.

KAVS8022-E

The specified of the executing agent exceeds the maximum. Line=line-number

The line in the operation profile indicated by line-number is invalid.

The probable cause is as follows:

More than 2,048 permitted execution hosts are specified.

(S)

Cancels processing.

(O)

Take action according to the message KAVS8004-E together with this message.

KAVS8023-E

There is no valid executing agent. unit_path=unit_path_value

The syntax of the operation profile contains an error.

The probable cause is as follows:

No permitted execution host exists for the unit indicated by unit_path_value.

Execution hosts listed between @SYS_AGENTLIST_START and @SYS_AGENTLIST_END are not acknowledged as permitted execution hosts if they are not permitted by the upper-level unit.

(S)

Cancels processing.

(O)

Take action according to the message KAVS8004-E together with this message.

KAVS8028-E

The content of the connection permission configuration file(file-name) is invalid.

The connection permission configuration file contains an error.

The location of the error is indicated in line-number in the KAVS8036-E message output immediately after this message. Connection from the host specified on the line indicated by this line number is not permitted.

(S)

Continues processing.

(O)

Check and, if necessary, revise the contents of the connection permission configuration file and then execute the jajs_pmtcon command. For details about the connection permission configuration file, see 21.2 Restricting connections to JP1/AJS3 in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS8029-E

The request was rejected. (unit-name)

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 KAVS8039-E message that was output to the integrated trace log of the host on which the job is to be executed.

KAVS8030-I

The connection permitted hosts are listed successfully.

The hosts permitted to connect are displayed.

(S)

Terminates processing.

KAVS8032-I

The settings in the connection permission configuration file are in effect.

The settings in the connection permission configuration file are in effect. For details about the connection permission configuration file, see 21.2 Restricting connections to JP1/AJS3 in the JP1/Automatic Job Management System 3 Configuration Guide.

(S)

Terminates processing.

KAVS8033-E

An error occurred during the processing of the connection source restriction function. (code: cause-code, host: host-name) maintenance-information

An error occurred during the processing of the connection source restriction function.

The nature of the error is indicated as follows in cause-code:

LOCKERR: An error relating to internal locking occurred.

FILEERR: A file access error occurred.

IPERR: An attempt to acquire an IP address failed.

SHMERR: An error relating to shared memory access occurred.

MEMERR: There is insufficient memory.

SYSERR: A conflict occurred in the internal logic of JP1/AJS3.

For a physical host, JP1_DEFAULT is indicated in host-name.

(S)

If this message appears during the execution of the jajs_pmtcon command, command processing stops and then terminates abnormally.

If this message appears while starting up the JP1/AJS3 service or JP1/AJS3 Queueless Agent service, the startup of the service stops and then terminates abnormally.

For other cases, the system continues processing.

(O)

Take action according to the cause code of the message.

LOCKERR

Check for failures on the disk for the following directory:

For Windows: JP1/AJS3-installation-folder\sys

For UNIX: /var/opt/jp1ajs2/sys

FILEERR

Check the settings of the connection permission configuration file, whether the file exists, the file name, and the access permissions.

IPERR

Review the network settings.

SHMERR

Review the shared memory settings specified with the kernel parameters.

MEMERR

Make sure that the amount of memory available satisfies the memory requirements described in the Release Notes.

SYSERR

Collect data and then contact the system administrator.

If the jajs_pmtcon command terminated abnormally, correct the cause of the error, and then re-execute the command.

If this message appears while starting up the JP1/AJS3 service or JP1/AJS3 Queueless Agent service, correct the cause of the error, and then restart the service.

For other cases, correct the cause of the error, and then retry the processing that caused the error.

If an error still occurs after the above actions are taken, collect data and then contact the system administrator.

KAVS8034-E

The connection permitted hosts list cannot be refreshed because the connection source restriction function is disabled.

The list of hosts permitted to connect cannot be updated because the connection source restriction function is disabled.

The probable causes are:

The connection source restriction function was not set.

Neither of the following service is running:

- JP1/AJS3 service

- JP1/AJS3 Queueless Agent service

If a logical host on which processing is to be performed is specified, the logical host is not attached to the queueless agent service.

(S)

Terminates processing.

(O)

Enable the connection source restriction function. For details about how to enable this function, see 21.2 Restricting connections to JP1/AJS3 in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS8036-E

The content of the connection permission configuration file(file-name) is invalid. (line: line-number)

The connection permission configuration file contains an error. The location of the error is indicated in line-number in the message.

(S)

Continues processing.

(O)

Check and, if necessary, revise the contents of the connection permission configuration file, and then re-execute the command. For details about the connection permission configuration file, see 21.2 Restricting connections to JP1/AJS3 in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS8037-E

The number of IP addresses specified in the connection permission configuration file(file-name) exceeded the maximum limit.(line: line-number, maximum: maximum-value)

Because the number of IP addresses specified in the connection permission configuration file exceeded the maximum, any address after the line indicated in line-number has been ignored.

(S)

Continues processing.

(O)

Check and, if necessary, revise the contents of the connection permission configuration file, and then re-execute the command. For details about the connection permission configuration file, see 21.2 Restricting connections to JP1/AJS3 in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVS8038-E

The connection source restriction function cannot be used.

The connection source restriction function cannot be used in a compatible ISAM configuration.

(S)

Ignores the contents of the connection permission configuration file, and continues the processing.

(O)

To use the connection source restriction function, change the configuration to the standard configuration. To continue operating in the compatible ISAM configuration, change the value of the CONNECTIONRESTRICTION environment setting parameter to none.

KAVS8039-E

The request sent from the host(connection-source-IP-address) was ignored. (reason, host-name)

A request from the host (connection-source-IP-address) was ignored. The probable causes are as follows.

If reason is Restricted:

The IP address indicated in connection-source-IP-address was not registered in the agent connection permission configuration file on the host where this message was output.

If reason is Error:

An error occurred during the processing intended to obtain the connection source IP address.

For a physical host, JP1_DEFAULT is indicated in host-name.

If the connection source IP address was not obtained, null characters are output for connection-source-IP-address.

(S)

Ignores the request and continues processing.

(O)

- If reason is Restricted:

If the request from the IP address indicated in connection-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 where this message was output.

Execute the jajs_pmtcon command to apply the change to the connection permission configuration file.

If necessary, perform the request processing again.

- If reason is Error:

Follow the instructions given by the KAVS8033-E message that was output immediately before this message.

KAVS8040-E

The request sent from the host(connection-source-IP-address) was ignored. (reason, host-name)

A request from the host (connection-source-IP-address) was ignored. The probable causes are as follows:

If reason is Restricted:

The IP address indicated in connection-source-IP-address was not registered in the manager connection permission configuration file on the host on which this message was output.

If reason is Error:

An error occurred during processing intended to obtain the connection source IP address.

(S)

Ignores the request and continues processing.

(O)

- If reason is Restricted:

If the request from the IP address indicated in connection-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 where this message was output.

Execute the jajs_pmtcon command to apply the change to the connection permission configuration file.

If necessary, perform the request processing again.

- If reason is Error:

Follow the instructions given by the KAVS8033-E message that was output immediately before this message.

KAVS8050-I

The job finished. (HTTP status = value)

The HTTP connection job ended.

(S)

Ends the HTTP connection job.

KAVS8051-E

A definition item is invalid. (item-name, maintenance-information)

A job definition item is invalid.

The probable causes are as follows:

The value of the item name is invalid.

The length of the item name is invalid. (As a result of a replacement, the length of the specified macro variable might exceed the maximum.)

The item name is not specified by using an absolute path.

A required item is not specified.

The character strings that can be displayed in item-name and their meanings are as follows:

htcfl : Connection configuration file name

htknd : Request type

htrqf : Transfer information file name

htstf : Status file name

htspt : How to store received data

htrhf : Received header file name

htrbf : Received body file name

(S)

Cancels execution.

(O)

Correct the definition item, and then re-execute the operation.

KAVS8052-E

The syntax of the connection configuration file is incorrect. (maintenance-information-1,maintenance-information-2)

The description of the connection configuration file for the HTTP connection job is not correct.

The probable causes are as follows:

A value is not specified.

The length of a value is invalid.

An unspecifiable value is specified.

A value outside the specifiable range is specified.

The specification for URL= does not begin with http:// or https://.

A question mark (?) is specified for URL=.

The specification for URL= contains multibyte characters.

The specification for UserName= or ProxyUserName= contains a colon (:).

A required specification is missing.

An unknown item name is specified.

The values that can be displayed in maintenance-information-1 and their meanings are as follows:

For 0:

A required specification is missing. The probable causes are as follows:

Nothing is specified for URL=.

When y is specified for Authorization=, nothing is specified for UserName= or UserPass=.

When y is specified for ProxyAuthorization=, nothing is specified for Proxy=, ProxyUserName=, or ProxyUserPass=.

For a numeric value of 1 or higher:

The line number for the invalid syntax is displayed.

For a character string:

An item that contains an invalid syntax is displayed after item name=.

(S)

Cancels execution.

(O)

Correct the connection configuration file, and then re-execute the operation.

KAVS8053-E

An error occurred while a file was being accessed. (maintenance-information)

A file access error occurred during processing.

The probable causes are as follows:

The file does not exist.

You do not have access permission for the file.

A directory is specified.

Note that if this error occurs, the files output by the HTTP connection job (status storage file, received-header storage file, and received-body storage file) might not be deleted. If necessary, check the file contents or delete the files.

(S)

Cancels execution.

(O)

Take corrective action, and then re-execute the operation.

If you cannot determine the cause of the error, collect data by using a data collection tool, and then contact the system administrator.

KAVS8054-E

An attempt to resolve the name of the connection destination host failed. (maintenance-information)

An attempt to resolve the name of the connection destination host failed.

The network settings must be specified correctly so that the IP address can be obtained from the connection destination host name by using the hosts file or DNS server.

If a proxy server is specified, the connection destination host is set to the proxy server.

Note that if this error occurs, the files output by the HTTP connection job (status storage file, received-header storage file, and received-body storage file) might not be deleted. If necessary, check the file contents or delete the files.

(S)

Cancels execution.

(O)

Correct the network settings, and then re-execute the operation.

KAVS8056-E

An error occurred in the connection with the connection destination host. (maintenance-information)

An error occurred in the connection with the connection destination host.

If a proxy server is specified, the connection destination host is set to the proxy server.

Note that if this error occurs, the files output by the HTTP connection job (status storage file, received-header storage file, and received-body storage file) might not be deleted. If necessary, check the file contents or delete the files.

(S)

Cancels execution.

(O)

Check the status of the connection destination host, and then correct the cause of the error. Next, re-execute the operation.

If you cannot determine the cause of the error, collect data by using a data collection tool, and then contact the system administrator.

KAVS8057-E

An error occurred in the communication processing. (maintenance-information)

An error occurred in the communication processing with the connection destination host.

Note that if this error occurs, the files output by the HTTP connection job (status storage file, received-header storage file, and received-body storage file) might not be deleted. If necessary, check the file contents or delete the files.

(S)

Cancels execution.

(O)

Check the status of the connection destination host and communication settings, correct the cause of the error, and then re-execute the operation.

If you cannot determine the cause of the error, collect data by using a data collection tool, and then contact the system administrator.

KAVS8058-E

An unexpected error occurred. (maintenance-information)

An unexpected error occurred during processing.

This error is also output if a response with an unexpected HTTP status or HTTP body response is received.

Note that if this error occurs, the files output by the HTTP connection job (status storage file, received-header storage file, and received-body storage file) might not be deleted. If necessary, check the file contents or delete the files.

(S)

Cancels execution.

(O)

Make sure that the connection destination specified for URL or Proxy in the connection configuration file is correct. Also, check the protocol type (HTTP or HTTPS).

If there are no problems in the settings you checked, collect data by using a data collection tool, and then contact the system administrator.

KAVS8059-E

The maximum output size for received information has been reached. (maintenance-information)

Processing is canceled because the value of the HTTP response header Content-Length exceeded the maximum size that can be received, or because the maximum receive size is exceeded during reception.

Note that if this error occurs, the files output by the HTTP connection job (status storage file, received-header storage file, and received-body storage file) might not be deleted. If necessary, check the file contents or delete the files.

(S)

Cancels execution.

(O)

To store all information in the file, specify an appropriate value for MaximumReceivedDataSize in the connection configuration file, and then re-execute the HTTP connection job.

KAVS8060-E

The specifications for a URL are invalid. (maintenance-information)

The probable causes are as follows:

The URL is specified incorrectly.

No resource exists at the reference destination of the URL.

When the request type of the HTTP connection job is GET, the specified send information file contains a linefeed code.

Note that if this error occurs, the files output by the HTTP connection job (status storage file, received-header storage file, and received-body storage file) might not be deleted. If necessary, check the file contents or delete the files.

(S)

Cancels execution.

(O)

Check the following, correct the cause of the error, and then re-execute the operation:

Make sure that the URL is specified correctly in the connection configuration file.

When the request type of the HTTP connection job is GET, make sure that the specified send information file does not contain a linefeed code.

KAVS8061-E

An HTTP connection job timed out. (maintenance-information)

Processing is canceled because the value specified for ConnectTimeout or Timeout in the connection configuration file or the default value was reached.

Note that if this error occurs, the files output by the HTTP connection job (status storage file, received-header storage file, and received-body storage file) might not be deleted. If necessary, check the file contents or delete the files.

(S)

Cancels execution.

(O)

Check the following, correct the cause of the error, and then re-execute the operation:

Make sure that an appropriate value is specified for ConnectTimeout= or Timeout= in the connection configuration file.

If processing is taking a long time, make sure that there are no problems in the communication environment.

KAVS8062-E

An error occurred during HTTPS authentication. (maintenance-information)

An error occurred during HTTPS authentication.

The probable causes are as follows:

HTTPS authentication failed.

A handshake failed.

The certificate is invalid.

An attempt to access the certificate file failed.

The CRL file is invalid.

An attempt to access the CRL file failed.

An attempt to check the issuer (CN (Common Name) or SAN (subject Alt Name)) failed.

The certificate has expired.

The certificate has lapsed.

Note that if this error occurs, the files output by the HTTP connection job (status storage file, received-header storage file, and received-body storage file) might not be deleted. If necessary, check the file contents or delete the files.

(S)

Cancels execution.

(O)

Correct the cause of the error, and then re-execute the operation.

If the cause of the error is not listed above, collect data by using a data collection tool, and then contact the system administrator.

KAVS8100-E

Cannot communicate with the execution environment for flexible jobs (maintenance-information-1, maintenance-information-2, maintenance-information-3, maintenance-information-4)

Communication with the flexible job execution environment could not be performed.

The probable causes are as follows:

The relay agent or destination of the flexible job is specified incorrectly.

The JP1/AJS3 Autonomous Agent service or The JP1/AJS3 Autonomous Agent Messenger service is not running (if maintenance-information-3 is 26 or 84).

You do not have access permission for the files under the folder for storing files used by the JP1/AJS3 Autonomous Agent service and JP1/AJS3 Autonomous Agent Messenger service (if maintenance-information-3 is 51).

Too many flexible jobs are executed at the same time (if maintenance-information-3 is 119 or 125).

A network failure or routing error occurred.

After setup of a broadcast-execution destination agent has been canceled, broadcast execution is performed before the host that was set up as the destination agent is removed from management.

JP1/AJS3 - Agent Minimal Edition is specified as the destination of the flexible job, the broadcast agent, or the relay agent.

(S)

Cancels processing.

(O)

Check the following, take corrective action, and then re-execute the flexible job:

Make sure that the relay agent and destination of the flexible job are specified correctly.

Make sure that the JP1/AJS3 Autonomous Agent service and the JP1/AJS3 Autonomous Agent Messenger service are running.

Make sure that the port number for the jp1ajs2atmsg service is not used for any other services and you have access permission for the files under the folder for storing files used by the JP1/AJS3 Autonomous Agent service and JP1/AJS3 Autonomous Agent Messenger service.

Make sure that you have access permission for the files under the folder for storing files used by the JP1/AJS3 Autonomous Agent service and JP1/AJS3 Autonomous Agent Messenger service.

For details about the folder for storing files used by the JP1/AJS3 Autonomous Agent service and JP1/AJS3 Autonomous Agent Messenger service, see A. List of Files and Directories in the manual JP1/Automatic Job Management System 3 Troubleshooting.

Make sure that the manager or relay agent can communicate with the destination agent.

If a broadcast agent cannot connect to a broadcast-execution destination agent, the hostname of the broadcast-execution destination agent will be displayed in maintenance-information-4. Make sure that the JP1/AJS3 Autonomous Agent Messenger service is running on the host displayed in maintenance-information-4.

Make sure that broadcast execution is performed after the time set for the FXBC_MANAGEDAGT_REMOVEDTIME environment setting parameter passes.

Make sure that JP1/AJS3 - Agent Minimal Edition is not specified as the destination of the flexible job, the broadcast agent, or the relay agent.

If JP1/AJS3 - Agent Minimal Edition is specified as an agent, no flexible jobs can be executed. Change the destination, broadcast agent, or relay agent in the job definition. Alternatively, use PC or UNIX jobs.

KAVS8101-E

Status monitoring of the flexible job will be stopped. (unit-full-name : execution-ID , maintenance-information)

Monitoring of the execution status terminates because the execution time of the flexible job exceeds the time period specified for the FXJOB_MONITOR_TIMEOUT environment setting parameter. The status will be set to Ended abnormally.

The probable causes are as follows:

Execution of the flexible job is taking a long time.

The destination agent failed to report the flexible job execution result to the manager due to one of the following causes.

The JP1/AJS3 Autonomous Agent service on the destination agent stopped.

JP1/AJS3 Autonomous Agent Messenger service on the destination agent or relay agent stopped.

Network error

Routing error

The auto scale function stopped the server on which the flexible job was running.

(S)

Terminates monitoring of the flexible job execution status, and then sets the status to Ended abnormally.

(O)

Take action appropriate for the cause of the error as follows:

The flexible job is still running on the destination agent even after monitoring terminated. Check the job execution status based on the log and execution result file for the destination agent. Next, if necessary, change the job status.

In addition, check and, if necessary, revise the value specified for the FXJOB_MONITOR_TIMEOUT environment setting parameter.

Check the cause of the error, and then, if necessary, re-execute the flexible job.

If you are using the auto scale function, revise the scale-in setting so that a scale-in does not occur during job execution.

KAVS8102-E

Resource lack occurred during the flexible job executing. (maintenance-information-1, maintenance-information-2, maintenance-information-3, maintenance-information-4)

Resources were insufficient during the execution of the flexible job.

(S)

Cancels processing.

(O)

The probable causes of the error in the flexible job are as follows:

Memory is insufficient.

Disk space is insufficient.

The size of the desktop heap is too small.

See the Release Notes, and then re-estimate the resources. Correct the cause of the error, and then re-execute the flexible job that caused the error.

KAVS8106-E

Error occurred during the flexible job executing. (maintenance-information-1, maintenance-information-2, maintenance-information-3)

An error occurred during the execution of the flexible job.

The probable causes are:

You do not have access permission for the files under the folder for storing files used by the JP1/AJS3 Autonomous Agent service and JP1/AJS3 Autonomous Agent Messenger service. (maintenance-information-2: 50, 51, or 53)

The JP1/AJS3 Autonomous Agent Messenger service on the relay agent or manager host stopped. (maintenance-information-2: 84)

Too many flexible jobs are executed at the same time. (maintenance-information-2: 27 or 119)

Broadcast execution was attempted from JP1/AJS3 - Manager 11-10 or later by specifying a relay agent whose version is 11-00. (maintenance-information-2: 0)

(S)

Cancels processing.

(O)

Check the following, take corrective action, and then re-execute the flexible job:

Make sure that you have access permission for the files under the folder for storing files used by the JP1/AJS3 Autonomous Agent service and JP1/AJS3 Autonomous Agent Messenger service.

For details about the folder for storing files used by the JP1/AJS3 Autonomous Agent service and JP1/AJS3 Autonomous Agent Messenger service, see A. List of Files and Directories in the manual JP1/Automatic Job Management System 3 Troubleshooting.

Make sure that the JP1/AJS3 Autonomous Agent Messenger service on the relay agent or manager host is running.

If the service is stopped, start it. Also make sure that the port number for the jp1ajs2atmsg service is not used for any other services.

Make sure that not too many flexible jobs are executed at the same time.

The version of the relay agent is 11-00 or later.

If the version of the relay agent is 11-00, do not use broadcast execution. Alternatively, update the version of the relay agent to 11-10 or later.

If you cannot correct the problem by taking the actions above, collect data by using a data collection tool, and then contact the system administrator.

KAVS8107-E

Cannot read JP1/AJS3 Autonomous Agent Messenger Service port information.

Information for the service name indicated in the message cannot be read.

(S)

Cancels processing.

(O)

Check the services file, correct the service name, and then restart.

For details on the ports that JP1/AJS3 uses, see A.1 Tables of port numbers in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVS8108-E

The execution file (file-name) is missing at the agent (agent-name).

The executable file does not exist on the agent.

(S)

Cancels processing.

(O)

Check whether any of the following probable causes are present:

A relative path to the executable file has been specified, but the folder or directory necessary for execution has not been specified in the PATH environment variable for 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.

The specified executable file is not found on the agent host when the host is executed.

The file path to the specified executable file cannot be accessed.

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 is specified correctly.

Do not specify a path beginning with a network drive name. Instead, specify a path beginning with a computer name (for example, \\computer-name\shared-folder\executable-file-name).

If a file in %systemroot%\system32 is specified in a WOW64 environment, file access is redirected to %systemroot%\syswow64. Take the following action:

In Windows Server 2016, Windows Server 2012 or a 64-bit version of Windows Server 2008, specify a file in %systemroot%\sysnative rather than %systemroot%\system32, and then re-execute the job.

Make sure that the executable file exists 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.

Make sure that the execution OS users can access the file path of the specified executable file.

KAVS8109-E

Failed to acquire permission to execute the execution file (file-name) for the user (user-name).

An attempt to access the executable file failed.

(S)

Cancels processing.

(O)

Make sure that the execution OS users can access the file path of the specified executable file, and then call the function again.

KAVS8110-W

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

The system file (temporary file for a flexible job) could not be deleted because a system call error occurred.

(S)

Cancels deletion of the system file.

(O)

System files (temporary files for flexible jobs) are stored in one of the locations listed below. Check whether the directory exists and whether you have access permission. If necessary, make sure that all flexible jobs have terminated, and then delete the system files.

In Windows, if the installation folder is the default installation folder or is in a folder protected by the system:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\tmp\AJSFX_WORK_00000001

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)

In Windows, if the installation folder is other than the above:

JP1/AJS3-installation-folder\tmp\AJSFX_WORK_00000001

In Linux:

/var/opt/jp1ajs2/tmp/AJSFX_WORK_00000001

KAVS8111-E

The port (port-name) cannot be used because another user is already using the port.

The service that output this message cannot start because the port (port-name) is being used.

(S)

Terminates the service that output this message.

(O)

Take either of the following actions, and then restart the service that output this message:

Use the netstat command to identify the process that is using the port indicated in port-name, and then stop that process by using Task Manager in Windows or by using the kill command in UNIX.

Edit the services file to change the port number used by the service that output this message.

To identify the name of the service that output this message, check the AP name that is output to the integrated trace log concurrently with this message.

For details about the output contents of the integrated trace log file, see 1.2.1(2) Integrated trace log in the manual JP1/Automatic Job Management System 3 Troubleshooting.

KAVS8112-E

Cannot operate - service-nameservice is not set up.

Operation cannot be performed because the service indicated in service-name is not set up.

(S)

Cancels command execution.

(O)

Use the ajsatsetup command to set up the service indicated in service-name, and then re-execute the operation.

KAVS8113-E

An error has occurred in the command (command-name).: maintenance-information-1 maintenance-information-2 maintenance-information-3

An error occurred in the command.

(S)

Cancels processing.

(O)

If you execute the specified command during start or stop processing of the JP1/AJS3 Autonomous Agent service or JP1/AJS3 Autonomous Agent Messenger service, an error might occur. If an error occurs, re-execute the command.

If you cannot correct the problem, collect data by using a data collection tool, and then contact the system administrator.

KAVS8114-E

The setup of the flexible job execution environment could not be updated. maintenance-information-1 maintenance-information-2 maintenance-information-3

The setting of the flexible job execution environment could not be updated because the ajsatsetup command failed.

(S)

Cancels processing.

(O)

If the JP1/AJS3 Autonomous Agent service or JP1/AJS3 Autonomous Agent Messenger service is running, the setup might fail. Stop the relevant service, and then re-execute the ajsatsetup command.

When a host is set up as a broadcast-execution destination agent, this message might be output if an unresolvable host name or incorrectly formatted IP address is specified for the -p option. Check and, if necessary, revise the value of the -p option, and then re-execute the ajsatsetup command.

If the situation above does not apply, possible causes of the error are insufficient memory or insufficient free space on the disk. Correct the cause of the error, and then execute the ajsatsetup command.

If you cannot correct the problem, collect data by using a data collection tool, and then contact the system administrator.

KAVS8115-I

The response of execution request of the flexible job was received.

A response to the execution request of the flexible job was received.

(S)

Continues processing.

KAVS8116-E

Status monitoring will stop, because the start of the flexible job could not be confirmed. (unit-full-name : execution-ID , maintenance-information)

Monitoring of the execution status terminates because the start of the flexible job could not be confirmed within the time specified for the environment setting parameter FXJOB_START_TIMEOUT.

The probable causes are as follows:

The start of the flexible job is delayed on the destination agent due to a heavy processing load on the destination agent.

The destination agent failed to report the flexible job execution result to the manager due to one of the following causes.

The IP address of the host that requested the execution of the flexible job cannot be resolved on the destination agent.

The JP1/AJS3 Autonomous Agent service on the destination agent stopped.

JP1/AJS3 Autonomous Agent Messenger service on the destination agent or relay agent stopped.

Network error

Routing error

The auto scale function stopped the server on which the flexible job was running.

An IPC error occurred because of insufficient resource.

Broadcast execution was performed for a host that was not set up as a broadcast agent in an environment in which the version of JP1/AJS3 - Agent on a relay agent or JP1/AJS3 - Manager was 11-10 or later.

In a broadcast execution environment in which the version of JP1/AJS3 - Manager or JP1/AJS3 - Agent on the relay agent is 11-10 or later, the broadcast agent distributed a job to hosts other than destination hosts.

After setup of a broadcast-execution destination agent was canceled, the ajsatsetup command was used to perform setup again by specifying an option other than -a -p. Then, broadcast execution was performed before the time set for the FXBC_MANAGEDAGT_REMOVEDTIME environment setting parameter passes.

In an environment in which broadcast execution is disabled, the execution host of the flexible job is not set up as a destination agent.

(S)

Terminates monitoring of the flexible job execution status, and then sets the status to Ended abnormally.

(O)

Take action appropriate for the cause of the error as follows:

The flexible job is still running on the destination agent even after monitoring terminated. Check the job execution status based on the log and execution result file for the destination agent. Next, if necessary, change the job status.

In addition, check and, if necessary, revise the value specified for the environment setting parameter FXJOB_START_TIMEOUT.

Check the cause of the error, and then, if necessary, re-execute the flexible job.

If you are using the auto scale function, revise the scale-in setting so that a scale-in does not occur during job execution.

Check the version of JP1/AJS3 - Manager or JP1/AJS3 - Agent on the destination host specified for Destination / Broadcast agent in the Define Details dialog box, and take action according to the version:

If the version is 11-00 or earlier:

Update the version to 11-10 or later.

If the version is 11-10 or later:

Use the ajsfxbcstatus command to check whether the destination host specified for Destination / Broadcast agent is set up as a broadcast agent. If the destination host is not set up as a broadcast agent, execute the ajsatsetup command with the -g option.

Check the version of JP1/AJS3 - Manager or JP1/AJS3 - Agent on the host on which the problem occurred, and take action according to the version:

If the version is 11-00 or earlier:

Update the version to 11-10 or later.

If the version is 11-10 or later:

Use the ajsfxbcstatus command to check whether the host on which the problem occurred is set up as a broadcast-execution destination agent. If the host is not set up as a broadcast-execution destination agent, execute the ajsatsetup command with the -a -p option.

After the time specified for the FXBC_MANAGEDAGT_REMOVEDTIME environment setting parameter passes, perform broadcast execution.

On the execution hosts of the flexible job, execute the ajsatsetup command with the -a option.

KAVS8120-I

The JP1/AJS3 Autonomous Agent service will now start.

The JP1/AJS3 Autonomous Agent service will now start.

(S)

Starts the JP1/AJS3 Autonomous Agent service.

KAVS8121-I

The JP1/AJS3 Autonomous Agent service will now stop.

The JP1/AJS3 Autonomous Agent service will now stop.

(S)

Stops the JP1/AJS3 Autonomous Agent service.

KAVS8122-I

The JP1/AJS3 Autonomous Agent Messenger will now start.

The JP1/AJS3 Autonomous Agent Messenger will now start.

(S)

Starts the JP1/AJS3 Autonomous Agent Messenger service.

KAVS8123-I

The JP1/AJS3 Autonomous Agent Messenger will now stop.

The JP1/AJS3 Autonomous Agent Messenger will now stop.

(S)

Stops the JP1/AJS3 Autonomous Agent Messenger service.

KAVS8124-I

The service (service-name) stopped.

The service indicated in service-name will now stop.

(S)

The service indicated in service-name will now stop.

KAVS8130-E

The execution file (file-name) was invalid, so the flexible job execution was not possible. (maintenance-information)

The flexible job could not be executed because the executable file was invalid.

(S)

Places the flexible job into the Ended abnormally status.

(O)

Make sure that the executable file can be executed independently, and then re-execute the flexible job that caused the error.

KAVS8133-E

The flexible job could not be executed because the user does not have the required permission for execution. (maintenance-information)

The flexible job could not be executed because the account of the JP1/AJS3 Autonomous Agent service did not have the permissions required for executing the queueless job.

(S)

Places the flexible job into the Ended abnormally status.

(O)

Specify the permissions required for executing the job in the account of the JP1/AJS3 Autonomous Agent service, and then re-execute the flexible job that caused the error.

For details about the permissions that must be set for the account, see 4.2.3 Changing the JP1/AJS3 service settings (Windows only) in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVS8134-E

The disk capacity was insufficient, so a flexible job could not be performed. (maintenance-information)

The flexible job could not be executed because there was insufficient disk space.

(S)

Places the flexible job into the Ended abnormally status.

(O)

Allocate sufficient free space on the disk, and then re-execute the flexible job that caused the error.

KAVS8135-E

A flexible job could not be executed because an attempt to access the work path (path-name) failed.(maintenance-information)

The flexible job could not be executed because an attempt to access the work path failed.

(S)

Places the flexible job into the Ended abnormally status.

(O)

Make sure that the directory path specified in the work path exists. Alternatively, make sure that the user who started the JP1/AJS3 Autonomous Agent service and the OS user who executes the flexible job can read and write to the work path. Next, re-execute the flexible job that caused the error.

KAVS8136-E

An attempt to start the job (maintenance-information).

An attempt to start the flexible job failed due to an internal error.

(S)

Places the flexible job into the Ended abnormally status.

(O)

Re-execute the flexible job that caused the error. If an attempt to start the flexible job fails again, restart the JP1/AJS3 Autonomous Agent service, and then re-execute the flexible job that caused the error.

If the UAC function is enabled in Windows and the OS user who executed the job is a member of the Administrators group, the Administrators permission might be disabled for the indicated job. In such a case, execute the job by using the built-in Administrator account.

If you cannot correct the problem by taking the actions above, collect data, and then contact the system administrator. (See 1.2.3 To the system administrators.)

KAVS8137-I

The execution request of the flexible job will start. (unit-full-name : execution-ID , maintenance-information)

The execution request of the flexible job will now start.

(S)

Continues processing.

KAVS8138-I

The flexible job was executed. (unit-full-name : execution-ID , return-code, destination-agent-host-name , maintenance-information)

Execution of the flexible job has terminated.

(S)

Continues processing.

KAVS8139-I

The flexible job will be executed. (requesting-host-name, maintenance-information)

Execution of the flexible job will now start.

(S)

Continues processing.

KAVS8140-I

The flexible job was executed. (return-code, requesting-host-name, maintenance-information)

Execution of the flexible job has terminated.

(S)

Continues processing.

KAVS8141-E

An error occurred in the check processing of user mapping. (host-name, JP1-user-name, maintenance-information)

An error occurred during check processing of user mapping for the JP1 user (indicated in JP1-user-name) on the host indicated in host-name.

The probable causes are as follows:

Host name resolution failed.

If the KAVS8143-E message was output after this message, name resolution failed on the relay agent or manager host.

The JP1 user indicated in JP1-user-name is not defined for user mapping in JP1/Base.

The OS user defined for user mapping in JP1/Base does not exist.

In Windows, the password of the OS user defined for user mapping in JP1/Base is invalid.

In Linux, the group of the OS user defined for user mapping in JP1/Base does not exist.

An attempt to set up JP1/Base failed.

The JP1/Base environment is corrupted.

(S)

Places the flexible job into the Ended abnormally status.

(O)

If the KAVS8143-E message was output after this message, take action according to the instructions given by the KAVS8143-E message.

Make sure that the JP1 user indicated in JP1-user-name is correctly defined for user mapping in JP1/Base, take corrective action, and then re-execute the flexible job.

For details about the user mapping settings, see 3.1.1 Setting up JP1/Base in the JP1/Automatic Job Management System 3 Configuration Guide (in Windows), or 13.1.1 Setting up JP1/Base in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

KAVS8142-E

The destination(destination) cannot be resolved. (maintenance-information)

The name of the destination (destination) of the flexible job cannot be resolved.

(S)

Cancels processing.

(O)

Make sure that the name of the destination (indicated in destination) can be resolved on the relay agent or manager host.

If the name cannot be resolved, define the hosts file or DNS server settings so that the IP address can be obtained from the destination indicated in destination.

If a string that has 129 or more bytes is specified as a destination of the flexible job on the manager host, specify a string that has 128 or fewer bytes.

KAVS8143-E

The host name(host-name) cannot be resolved. (maintenance-information)

The host name indicated in host-name on the relay agent, broadcast agent, or manager host for the flexible job cannot be resolved.

(S)

Cancels processing.

(O)

Make sure that the host name indicated in host-name can be resolved on the destination agent.

If an IP address is used to specify the broadcast agent, make sure that the format of the IP address is correct.

If the host name cannot be resolved, define the hosts file or DNS server settings so that the IP address can be obtained from the destination indicated in host-name.

If the host name of a relay agent, broadcast agent, or manager host has 129 or more bytes, shorten the host name to 128 or fewer bytes.

KAVS8144-I

A destination agent for broadcast execution was added. (host-name, IP-address)

A host was added to the list of managed broadcast-execution destination agents.

(S)

Terminates processing.

KAVS8145-I

The destination agent for broadcast execution was deleted. (host-name, IP-address)

A host was deleted from the list of managed broadcast-execution destination agents because the heartbeat of the host stopped for a certain period of time and a job execution request timed out.

(S)

Terminates processing.

KAVS8146-E

The broadcast agent did not respond to the heartbeat request. (broadcast-agent-IP-address, maintenance-information)

The broadcast agent did not respond to the heartbeat request.

(S)

Terminates processing.

(O)

Perform the following operations. If a problem is found, resolve it. After that, wait for a while, and then make sure this message has not been output again.

Check whether the broadcast agent service is running.

If the ajsatsetup command was used to set up the broadcast agent, check whether the IP address of the broadcast agent specified for the -p option is correct.

Check whether the broadcast agent is under a heavy load.

KAVS8147-I

The broadcast agent responded to the heartbeat request. (broadcast-agent-IP-address)

The broadcast agent responded to the heartbeat request.

(S)

Terminates processing.

KAVS8148-I

Broadcast execution will now start. (manager-host-name , full-unit-name , execution-ID , maintenance-information)

Broadcast execution will now start.

(S)

Continues processing.

KAVS8149-I

Broadcast execution has finished. (return-code , manager-host-name , full-unit-name , execution-ID , maintenance-information)

Broadcast execution has finished.

(S)

Continues processing.

(O)

Check the output information to see whether action is needed.

KAVS8158-I

The execution request of the flexible job will start. (full-unit-name : execution-ID, host-name-of-the-broadcast-execution-destination-agent, maintenance-information)

The execution request of the flexible job will start.

(S)

Continues processing.

KAVS8159-W

There is no destination agent for broadcast execution. (manager-host-name, full-unit-name, execution-ID, maintenance-information)

No destination agents for broadcast execution of the flexible job exist. The probable causes are:

No broadcast agent is set up for the destination agents.

No destination agents are running.

(S)

Terminates execution of the flexible job.

(O)

If no broadcast agent is set up for the destination agents, set one up.

If no destination agents are running, start them.

KAVS8160-E

An error occurred in the internal processing of broadcast execution.: (maintenance-information)

An error occurred in the internal processing of broadcast execution. The probable causes are:

A temporary error occurred during file access.

A network failure occurred when an attempt was made to establish a connection for communication.

(S)

Terminates the internal processing of broadcast execution.

(O)

If this message is output repeatedly, contact the system administrator.

KAVS8161-E

An error occurred in the processing to output information about broadcast execution.: (maintenance-information)

An error occurred in the processing to output information about broadcast execution. A temporary error, such as an error that prevents the internal processing from accessing files, might have occurred.

(S)

Terminates output of information about broadcast execution.

(O)

If this message is output repeatedly, contact the system administrator.

KAVS8162-E

Failed to put JP1 Event. (maintenance-information-1, maintenance-information-2, maintenance-information-3)

Failed to put JP1 Event.

(S)

Stops the processing to send the JP1 event.

(O)

Check whether the JP1/Base event service can start. If the JP1/Base event service is not running, start it.

KAVS8163-W

The maximum number of destination agents for broadcast execution has been reached.: reported-IP-address reported-host-name (maintenance-information)

The maximum number of destination agents for broadcast execution has been reached. The number of destination agents for the relevant broadcast agent might have exceeded the maximum. A maximum of 100 destination agents can be managed.

(S)

Discards the received heartbeats, and then continues processing.

(O)

Use the ajsfxbcstatus command to check whether the destination agents include unnecessary ones. If unnecessary destination agents exist, reduce the number of agents by performing the following operations:

On a destination agent host, stop the JP1/AJS3 Autonomous Agent service and the JP1/AJS3 Autonomous Agent Messenger service.

Perform unsetup of the destination agent.

KAVS8164-E

No environment has been set up for the execution of flexible jobs. : (maintenance-information)

No environment has been set up for the execution of flexible jobs.

(S)

Terminates processing.

(O)

If this message is output during execution of the ajsfxbcstatus command:

Use the ajsatsetup command to set up the execution environment for flexible jobs, and then re-execute the ajsfxbcstatus command.

If this message is output when the ajsatsetup command is used to cancel setup of a broadcast agent or a broadcast-execution destination agent:

No action is required.

KAVS8165-I

The UDP/IP port number is not set, because the AJS administrator executed this command. Set UDP/IP port number. : ajsatsetup

The UDP/IP port number was not set, because the command was executed by an AJS administrator. Manually set the UDP/IP port number.

(S)

Continues processing.

(O)

Manually register the following communication port in the services file.

Function

Service name

Port number

Registered in:

JP1/AJS3 - Manager

JP1/AJS3 - Agent

Broadcast execution of flexible jobs

jp1ajs2atmsg

22251/udp

Yes

Yes

Legend:

Yes: Register the port.

KAVS8180-E

The return code for the flexible job (job-number, manager-host-name) could not be acquired. maintenance-information-1, maintenance-information-2

The system failed to acquire the return code for the flexible job.

(S)

Sets the flexible job status to Ended abnormally status with the return code -1.

(O)

Check the actual return code in the KAVS8138-I message output to the log file of the relay agent and then, if necessary, request the execution of the flexible job again.

KAVS8201-E

An attempt to read the private key failed.(logical-host-name, file-name, maintenance-information)

An attempt to read the file that stores the private key failed. The probable causes are as follows:

The private key does not exist.

You do not have access permission for the private key.

A pass phrase is set for the private key.

A private key that does not correspond to the server certificate is installed.

A temporary file access error occurred.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Cancels startup processing of the process.

(O)

If the private key does not exist:

Install the private key.

If you do not have access permission for the private key:

Set access permissions for the private key.

If a pass phrase is set for the private key:

Cancel the pass phrase for the private key.

If a private key that does not correspond to the server certificate is installed:

Install the correct server certificate or private key.

If a temporary file access error occurred:

Restart the service in which the error occurred.

KAVS8202-E

An attempt to read the server certificate failed.(logical-host-name, file-name, maintenance-information)

An attempt to read the file that stores the server certificate failed. The probable causes are as follows:

The server certificate does not exist.

You do not have access permission for the server certificate.

A temporary file access error occurred.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Cancels startup processing of the process.

(O)

If the server certificate does not exist:

Install the server certificate.

If you do not have access permission for the server certificate:

Set access permissions for the server certificate.

If a temporary file access error occurred:

Restart the service in which the error occurred.

KAVS8203-E

An attempt to read the root certificate failed.(logical-host-name, file-name, maintenance-information)

An attempt to read the root certificate failed. The probable causes are as follows:

The root certificate does not exist.

You do not have access permission for the root certificate.

A temporary file access error occurred.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Cancels startup processing of the process.

(O)

If the root certificate does not exist:

Install the root certificate.

If you do not have access permission for the root certificate:

Set access permissions for the root certificate.

If a temporary file access error occurred:

Restart the service in which the error occurred.

KAVS8204-E

An attempt to read the common definition information specified in JP1/Base failed.(logical-host-name, parameter-name, maintenance-information)

An attempt to read the common definition information specified in JP1/Base on the logical host failed. The value specified for the parameter indicated in parameter-name is incorrect.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Cancels startup processing of the process.

(O)

Correct the value specified for the parameter indicated in parameter-name.

KAVS8205-E

An attempt to verify the server certificate failed.(logical-host-name, name-of-host-to-be-connected, maintenance-information)

An attempt to verify the server certificate sent from the connection destination failed. The probable causes are as follows:

The connection destination host name does not match the CN or SAN.

The root certificate corresponding to the server certificate is not contained in the file specified for CACERTIFICATEFILE in the JP1/Base common definition information.

The current time of the machine in which the error occurred is earlier than the start time of the effective period specified in the server certificate.

The server certificate and the intermediate certificate are joined in an incorrect order.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Cancels communication processing, and then continues subsequent processing.

(O)

If the connection destination host name does not match the CN or SAN:

Match the connection destination host name to the CN or SAN.

If the root certificate corresponding to the server certificate is not contained in the file specified for CACERTIFICATEFILE in the JP1/Base common definition information:

Add the corresponding root certificate to the file specified for CACERTIFICATEFILE in the common definition information.

If the current time of the machine in which the error occurred is earlier than the start time of the effective period specified in the server certificate:

Retry the operation after the start time of the effective period specified in the server certificate.

If the server certificate and the intermediate certificate are joined in an incorrect order:

Join the server certificate and the intermediate certificate in the correct order.

KAVS8206-E

An error occurred in SSL communication processing.(logical-host-name, name-of-host-to-be-connected, maintenance-information)

An error occurred during SSL communication processing. The probable causes are as follows:

The communication encryption function is disabled at the connection destination.

A temporary communication error occurred.

JP1/AJS3 - Manager at the connection destination restricts connections.

If this message is output at the reception side of TCP/IP communication, a null character string is output for connection-destination-host-name.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Cancels communication processing, and then continues subsequent processing.

(O)

If the communication encryption function is disabled at the connection destination:

Enable the communication encryption function for the host indicated in connection-destination-host-name.

If a temporary communication error occurred:

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

If JP1/AJS3 - Manager at the connection destination restricts connections:

Add the IP address of the connection source host to the connection permission configuration file for the destination manager.

KAVS8208-E

An attempt to read the environment setting parameter failed.(logical-host-name, parameter-name, maintenance-information)

An attempt to read the environment setting parameter on the logical host (logical-host-name) failed. The value specified for the parameter name is incorrect.

(S)

Cancels startup processing of the process.

(O)

Correct the value specified for the parameter name.

4 Messages beginning with KAVT (Messages about the event/action control)

This chapter explains the messages beginning with KAVT (messages about the event/action control).

4.1 List of messages beginning with KAVT

This section lists the messages that begin with KAVT (Messages about the event/action control).

KAVT0001-I

Event Action Manager will now start.(maintenance-information)

The event/action control manager starts.

(S)

Continues processing.

KAVT0002-I

Finish Event Action Manager.(maintenance-information)

The event/action control manager has terminated.

(S)

Terminates the event/action control manager.

KAVT0003-I

Event Action Manager has started.(maintenance-information)

The event/action control manager has started.

(S)

Continues processing.

KAVT0008-E

Failed to initialize process. (maintenance-information)

The event/action control manager could not be started.

(S)

Terminates the event/action control manager.

(O)

Check the following and then restart JP1/AJS3:

Check whether JP1/Base is running.

Check whether the system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the contents of the environment settings are correct. In particular, check whether the value set in the environment setting parameter WaitInfFileOutDir or AJSSYSDIR is correct.

If the value of an environment setting parameter is incorrect or the same as that of the same environment setting parameter in a different definition key, stop the JP1/AJS3 service, revise the setting, and then restart the JP1/AJS3 service.

KAVT0009-E

Failed to initialize socket. (maintenance-information, IPAddress=IP-address#)

The event/action control manager could not be started.

#

The IP address is output only when the LOGIPV6INFOALL environment setting parameter is set to yes. If the LOGIPV6INFOALL environment setting parameter is set to yes and the IP address is unknown, unknown is displayed.

(S)

Terminates the event/action control manager.

(O)

Check the following, and then restart JP1/AJS3:

Check whether the JP1/AJS3 that has the same logical host name is running.

Check whether the host name is determined.

If it is not determined, check the settings of the JP1_HOSTNAME environment variable, the hosts file, or the DNS server.

Check whether the JP1/AJS3 port number is registered in the services file.

If it is not registered, register it.

KAVT0020-E

A definition file name could not be created. (maintenance-information)

An attempt to create a configuration definition file name has failed in the event/action control manager.

(S)

Continues processing without changing the status of the jobnet with start conditions or the event job.

(O)

Check the length of the name of the directory for output of the wait information file that was specified when JP1/AJS3 was set up. The maximum length allowed is 160 bytes. Change the configuration definition information (environment setting) and then restart JP1/AJS3.

KAVT0023-E

An error occurred during processing of a request to monitor event icons. (maintenance-information) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred while event job monitoring was starting.

(S)

Terminates the event job in the Failed to start status.

(O)

Check the following, and then use the ajsname command with the -I option to identify the job name from the unit ID. Retry operation on the identified event job:

Check whether the system resources are sufficient. Especially, check whether there is sufficient space on the disk that contains the directory for output of the wait information file.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

Check whether the target host and JP1/AJS3 have started.

KAVT0025-E

The last registered contents cannot be recovered because the processing to recover consistency failed.(maintenance-information)

The system cannot resume the monitoring of the jobnet with start conditions or the event job that was being monitored when the event/action control manager was stopped last time.

(S)

Places the previously registered jobnet with start conditions in the Monitor terminated status or places the event job in the Unknown end status status, and then start the event/action control manager.

(O)

Check the following:

Check whether the system resources are sufficient. Especially, check whether there was sufficient space on the disk containing the directory for output of the wait information file during JP1/AJS3 operation.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

Because the wait information file might have been corrupted, cold-start JP1/AJS3.

KAVT0026-I

The cold start processing will now start.(maintenance-information)

A cold start will now start on the event/action control manager.

(S)

Continues processing.

KAVT0027-E

The cold start processing failed. (maintenance-information)

An attempt to perform a cold start on the event/action control manager has failed.

(S)

Starts the event/action control manager while some of the event jobs being monitored are still running.

(O)

Check the following, and then re-execute the cold start:

Check whether the system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

Check whether the target host and JP1/AJS3 have started.

KAVT0034-E

An error occurred during processing of a request to kill an event icon. (maintenance-information) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred during forced termination of an event job.

(S)

Cancels the forced termination of the event job. The event job is now monitoring an event.

(O)

Check the following, and then use the ajsname command with the -I option to identify the job name from the unit ID. Make sure that the status of the identified event job has not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status of the event job:

Check whether the system resources are sufficient. Especially, check whether there was sufficient space on the disk containing the directory for output of the wait information file during JP1/AJS3 operation.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

Check whether the target host and JP1/AJS3 have started.

KAVT0036-E

An error occurred during processing of a bypass request for an event icon. (maintenance-information) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred during bypass processing of an event job.

(S)

Cancels forced termination of the event job. The event job is now monitoring an event.

(O)

Check the following, and then use the ajsname command with the -I option to identify the job name from the unit ID. Make sure that the status of the identified event job has not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status of the event job:

Check whether the system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

Check whether the target host and JP1/AJS3 have started.

KAVT0039-I

Terminating because of a bypass request.

Event monitoring will now stop, because a bypass request or status change request was accepted.

(S)

Continues processing.

KAVT0042-E

The standard error output file could not be output. (file=file-name) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An attempt to write to the standard error output file has failed during execution of an event job.

(S)

Continues processing without outputting an execution result details message to a file.

(O)

Make sure that the directory specified in the name of the directory for job error information in the configuration definition information (environment setting) exists. Then use the ajsname command with the -I option to identify the job name from the unit ID.

KAVT0043-I

The icon will now end because of a kill request.

Event monitoring will now terminate because a forced termination request was accepted.

(S)

Continues processing.

KAVT0045-E

The icon will now end because an error occurred.

An error occurred during the start of an event.

(S)

Continues processing.

(O)

The error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT0058-E

An error occurred during processing of the request to monitor the start condition. (maintenance-information) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred immediately after monitoring of a jobnet with start conditions started.

(S)

Terminates the jobnet with start conditions.

(O)

Check the following, and then use the ajsname command with the -I option to identify the job name from the unit ID. Re-register the identified jobnet for execution:

Check whether the system resources are sufficient. Especially, check whether there is sufficient space on the disk containing the directory for output of the wait information file.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted unintentionally.

Check whether the target host and JP1/AJS3 have started.

KAVT0059-E

Past time is set as the stop time. (time=set-time) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

The effective period specified for the start condition is earlier than the current time.

(S)

Terminates the jobnet with start conditions.

(O)

Specify an effective period for the start condition later than the current time, and then reregister it.

KAVT0062-E

An error occurred during processing of the request to end start-condition monitoring. (maintenance-information) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred during the termination of monitoring the start condition.

(S)

Cancels the forced termination of the jobnet with start conditions, and continues processing.

(O)

Check the following, and then use the ajsname command with the -I option to identify the unit name from the unit ID. Make sure that the status of the identified jobnet with start conditions has not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status:

Check whether the system resources are sufficient. Especially, check whether there was sufficient space on the disk containing the directory for output of the wait information file during JP1/AJS3 operation.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

Check whether the target host and JP1/AJS3 have started.

KAVT0082-E

An error occurred during processing of phenomena at an event icon end. (maintenance-information) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred during generation of an event for an event job.

(S)

Continues processing without changing the status of the event job.

(O)

Check the following, and then use the ajsname command with the -I option to identify the job name from the unit ID. Make sure that the status of the identified event job has not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status of the event job:

Check whether the system resources are sufficient. Especially, check whether there was sufficient space on the disk containing the directory for output of the wait information file during JP1/AJS3 operation.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

Check whether the scheduler service has started.

KAVT0084-E

The file for storing macro variables could not be output. (file=file-name) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

Output to the macro variable storage file failed.

(S)

Continues processing.

(O)

Check the following, and then use the ajsname command with the -I option to identify the unit name from the unit ID:

Check whether the system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

KAVT0089-E

An error occurred during processing of the phenomena at the start of event-icon monitoring. (maintenance-information) (host=agent-host-name, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred while the agent was reporting the start of an event job.

(S)

Continues processing without monitoring the event job.

(O)

Check the following, and then use the ajsname command with the -I option to identify the job name from the unit ID. Make sure that the status of the identified event job has not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status of the event job:

Check whether the system resources are sufficient. Especially, check whether there was sufficient space on the disk containing the directory for output of the wait information file during JP1/AJS3 operation.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

Check whether the scheduler service has started.

KAVT0092-E

An error occurred during processing of phenomena for the agent machine activation report. (maintenance-information, host=agent-host-name)(maintenance-information)

Although the agent host reported the startup, an error occurred during startup of the agent within the manager.

(S)

Continues processing without monitoring anything on the agent.

(O)

Check the following, and then restart JP1/AJS3 on the agent host:

Check whether the system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

Check whether the target host and JP1/AJS3 have started.

KAVT0094-E

The send source is invalid. (RequestPP=send-source) (maintenance-information)

Invalid data was received.

(S)

Discards the invalid data received, and continues processing.

(O)

Invalid data was detected in the port (jp1ajs2eamgr). The part may have been accessed incorrectly. Examine the cause of the trouble.

KAVT0098-E

An error occurred in the processing of the time-out period of the start condition. (maintenance-information) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred during processing of the timeout period for the jobnet with start conditions.

(S)

Does not stop the jobnet with start conditions even after the period of time specified as the valid range has elapsed. The jobnet with start conditions remains in the Now monitoring status.

(O)

Check the following, and then use the ajsname command with the -I option to identify the unit name from the unit ID. Terminate the identified jobnet with start conditions forcibly. If the jobnet cannot be terminated forcibly, an inconsistency has occurred in the management status of event jobs. Restart the manager and the agent on which the start condition is executed.

Check whether the system resources are sufficient. Especially, check whether there is sufficient space on the disk containing the directory for output of the wait information file.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

Check whether the scheduler service has started.

KAVT0099-I

The start conditions stopped because the time-out period elapsed. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID)

The start condition terminated because the time-out period elapsed.

(S)

Continues processing.

KAVT0101-E

An error occurred during resending of unreported information. (maintenance-information) (host=agent-host-name, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred while re-sending the unreported information to the agent.

(S)

Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)

Check the following, and then use the ajsname command with the -I option to identify the unit name from the unit ID. Make sure that the status of the identified unit (a jobnet with start conditions or an event job) has not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status:

Check whether the system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

Check whether the scheduler service has started.

KAVT0103-E

Even with the specified number of retries, no messages could be sent. (file=unreported-information-file-name) (host=agent-host-name, maintenance-information)

Although the manager continued to retry establishing communication with an agent host for a certain period of time, transmission was not successful.

For details on this time, see Table 2-3 in 2.2.2(4) Notes on manager/agent system configurations in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

(S)

Deletes all communication data that has not been sent to the agent up to this time. As a result, the following symptoms might occur:

If an event job is registered for execution, the status of the job does not change from now queuing to now running.

If an event job (including an event job defined in the start conditions) is forcibly terminated, the now running status of the job does not change.

(O)

Check whether:

Check whether the agent host name# can be resolved on the manager host.

If the name cannot be resolved, specify the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the agent host name can be resolved.

Check whether the IP address obtained by resolving the agent host name on the manager host is the same as the actual IP address of the agent host.

If the IP addresses are different, specify the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the correct IP address can be obtained by resolving the name.

Check whether the JP1/AJS3 service on the agent host is running or whether the agent host machine itself is running.

If JP1/AJS3 on the agent host and the agent host itself are not running, start them.

Check whether there are problems with the network environment.

Use the ping command or another means to check whether the manager host can communicate with the agent host via TCP/IP. If there are communication problems, correct them.

In addition to performing the actions described above, you might also need to perform the following additional actions, depending on the type of deleted communication data:

Check whether the status of an event job registered for execution has changed from now queuing to now running.

If there is no change, forcibly terminate the job, and then re-execute it.

Check whether the now running status of an event job (including an event job defined in the start conditions) that has been forcibly terminated has changed.

If there is no change, forcibly terminate the job, and then re-execute it.

Ensure that no event has been detected within a certain period of time after the relevant message was output.

Because data waiting to be returned remains on the agent, start the agent.

Note that when the agent is restarted, it resends the remaining data to the manager. If the amount of the data is large, manager load might increase severely, succeeding jobs might have to wait a long time in the queue, or event detection might be seriously delayed. To avoid these problems, cold-start the agent if 1,000 or more events have been detected during a certain period of time after this message was output.

#

For a physical host:

For DNS operation, the host name in the FQDN format. For other cases, the host name obtained by executing the hostname command

For a logical host:

In Windows

The host name indicated in xxxxx in JP1/AJS3_xxxxx in the Services window that is displayed by choosing Services or by choosing Administrative Tools and then Services in the Control Panel window on the agent host

In UNIX

The host name indicated after the jajs_spmd process that is displayed by executing the ps command

KAVT0106-I

The start condition stopped because the specified number was detected. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID)

The start condition terminated because the system detected the satisfied start condition the specified number of times.

(S)

Continues processing.

KAVT0108-I

The start condition was satisfied. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID)

The start condition was satisfied.

(S)

Continues processing.

KAVT0110-E

An error occurred during resending of unreported information to scheduler service. (maintenance-information) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID)

An error occurred while resending the unreported information to the scheduler service.

(S)

Continues processing without changing the status of the jobnet with start conditions.

(O)

If this message appears in maintenance mode, you can ignore it. If the message appears in any mode other than maintenance mode, check the items listed below, and then use the ajsname command with the -I option specified to identify the unit name from the unit ID. Make sure that the status of the identified unit (a jobnet with start conditions or an event job) was not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status:

Check whether the system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

Check whether the scheduler service has started.

KAVT0116-E

Some information cannot be reported to scheduler service because the processing to recover consistency failed.(maintenance-information)

During startup of JP1/AJS3, the system failed to acquire information that could not be reported before termination of JP1/AJS3. As a result, some information cannot be reported to the scheduler service.

(S)

Aborts the information that could not be reported to the scheduler service last time, and starts the event/action control manager without changing the status of the unit (a jobnet with start conditions or an event job).

(O)

Check the following and take appropriate action. If neither of the following conditions is met, contact the system administrator and collect data (see 1.2.3 To the system administrators).

Check the following:

Check that the file in the output directory for the queued information has not been deleted.

Check whether there is a unit (a jobnet with start conditions or an event job) whose status has not changed.

Take the following action:

If the condition shown in check item 1 is met, perform a cold start.

If the condition shown in check item 2 is met, check the unit (a jobnet with start conditions or an event job) whose status has not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status.

KAVT0118-E

The shared definition could not be read. (maintenance-information)

The shared definition information could not be read.

(S)

Assumes the default value and continues processing.

If processing cannot be continued, take action according to the message output after this message.

(O)

Use the jbsgetcnf command to check whether you can acquire common definition information for the logical host that caused the error. If you cannot acquire the common definition information, re-install JP1/Base. If you can collect it, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT0145-E

An error occurred during sending of start mode to an agent host. (host=host-name, mode=start-mode, maintenance-information, IPAddress=IP-address#)

An error occurred during sending of start mode to an agent host. Since the startup of the manager host could not be reported to the agent indicated by host-name, monitoring of the events on the agent may be unsuccessful.

#

The IP address is output only when the LOGIPV6INFOALL environment setting parameter is set to yes. If the LOGIPV6INFOALL environment setting parameter is set to yes and the IP address is unknown, unknown is displayed.

(S)

Discards the data, allowing event monitoring on the agent host indicated in host-name to continue.

(O)

Check the following, and then restart JP1/AJS3:

Check whether the network or agent machine has not stopped.

Check whether the host name is determined. If has not, check the settings of the JP1_HOSTNAME environment variable, the hosts file, or the DNS server.

KAVT0147-E

An error occurred during the processing of an event for reporting the shutdown of an agent machine. (maintenance-information) (host=agent-host-name, maintenance-information)

An error occurred during the processing in response to the shutdown report from an agent host.

(S)

Continues processing without changing the status of the event job that is running on the agent.

(O)

Check the following, and then check the event job whose status has not changed. Then use the ajschgstat command or the Change Job Status dialog box or forced termination to change the status of the event job:

Check whether the system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

Check whether the scheduler service has started.

KAVT0157-E

Start condition is cancelled due to failure in receiving new branch-execution ID within specified time interval. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID) (time=specified-time)

A branch-execution ID could not be obtained within the specified time interval. The start condition terminates.

JP1/AJS3 uses branch-execution IDs to manage execution generations of jobnets with start conditions. For details about the execution generations of jobnets with start conditions, see 3.4.2 Monitoring generation and execution generation in the manual JP1/Automatic Job Management System 3 Overview.

(S)

Terminates the jobnet with start conditions in the Monitor terminated status.

(O)

Make sure that the scheduler service has started, and then use the ajsname command with the -I option to identify the unit name from the unit ID. Re-register the jobnet with start conditions for execution.

KAVT0171-E

Connection of the sending pipe failed. (maintenance-information)

The sending pipe could not be connected.

(S)

Terminates the event/action control manager.

(O)

Check the following, and then restart JP1/AJS3:

Check whether the system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted unintentionally.

If the above conditions are not satisfied, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT0178-E

An error occurred during child process creation. (maintenance-information) (maintenance-information)

An error occurred during creation of a child process.

(S)

Terminates the event/action control manager.

(O)

Check whether:

The system resources are sufficient.

The user who started JP1/AJS3 has superuser privileges or administrator privileges.

The directory created during installation of JP1/AJS3 was deleted inadvertently.

If the above conditions are not satisfied, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT0187-E

The process will now stop because Event Action SubManager is finished.(maintenance-information)

The event/action control manager will now stop because the event/action control submanager has stopped.

(S)

Terminates the event/action control manager.

(O)

Confirm that the directory for output of the wait information file can be accessed, and then restart JP1/AJS3.

If the KAVT0325-E message was also output at the same time this message was output, the probable cause is that the directory for output of the wait information file cannot be accessed. Confirm that the directory for output of the wait information file can be accessed. Correct any problems.

If this message appears during failover, allocation of the shared disk might have been canceled before JP1/AJS3 stopped. Review and, if necessary, correct the cluster software settings so that allocation of the shared disk is canceled after JP1/AJS3 and JP1/Base stops.

For details about the prerequisites for using the cluster system, see 10.1.1(1) Prerequisites for a logical host environment in the JP1/Automatic Job Management System 3 Administration Guide.

KAVT0193-W

The events that occurred during the maintenance mode are discarded because the option to improve event job reliability is invalid. (scheduler-service-name)

The reliability improvement option is invalid, so events occurring in maintenance mode are discarded.

(S)

Continues processing.

Discards events occurring in maintenance mode.

(O)

If no event occurs in maintenance mode, you to not need to take any actions. If an event occurs in maintenance mode, validate the reliability improvement option.

KAVT0194-W

Memory became insufficient during the maintenance mode start notification. (scheduler-service-name)

Memory became insufficient during the notification of maintenance mode activation. An error may occur when an activation condition event is detected in maintenance mode.

(S)

Keeps the maintenance mode.

(O)

See 3. Estimates in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide, and make sure that the required amount of memory for executing JP1/AJS3 has been allocated.

KAVT0198-E

Invalid specification in configuration definition. (item-name: value)

The configuration definition contains an invalid specification.

(S)

Terminates the event/action control manager.

(O)

Specify the value indicated by item-name correctly, and then restart JP1/AJS3. For details on the output item names, see 20.6 Setting up the event/action control environment in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVT0199-E

The values of the environment setting parameters on the manager host do not match. (item-name)

Different values are specified for the environment setting parameters that must have the same value on the manager host.

(S)

Terminates the event/action control manager.

(O)

Make sure that the same value is specified for the environment setting parameter (indicated by item-name) that needs to be specified in multiple definition keys on the manager host, and then restart JP1/AJS3. For details about output item names, see 20. Environment Setting Parameters in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVT0247-E

The number of tokens from the send destination is invalid. (maintenance-information) (maintenance-information)

Information from the send destination is invalid.

(S)

Continues processing without changing the status of the jobnet with start conditions or the event job.

(O)

Check whether:

The system resources are sufficient.

The version of the manager matches that of the agent.

The LANG settings match between JP1/Base and JP1/AJS3.

A program other than JP1/AJS3 is using the port defined for jp1ajs2eamgr. Use the netstat command or another means to check this.

KAVT0250-W

Because the total of macro variables exceeded the maximum, part of the data was truncated.(maintenance-information)

The total number of macro variables exceeded the limit. A part of the data was truncated.

(S)

Inherits the macro variables with the part of data truncated.

(O)

Redefine the macro variables so that the sum of the size of the values specified in the macro variables does not exceed 4,096 bytes. In particular, if you define a jobnet with start conditions using AND, the macro variables for all of the event jobs defined in the jobnet with start conditions will be merged. Therefore, make sure that the total size of the values specified in merged macro variables does not exceed 4,096 bytes.

KAVT0261-E

The report to scheduler service failed. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

The data could not be sent to the scheduler service.

(S)

Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)

Check whether the scheduler service has started. If it has started, the unit (a jobnet with start conditions or an event job) indicated by AjsServiceName=scheduler-service-name, UnitID=unit-ID, and ExecID=execution-ID may not have been registered, executed, or operated, or processing may not have been done in response to the event.

Use the ajsname command with the -I option to identify the unit name from the unit ID. Make sure that the status of the identified unit (a jobnet with start conditions or an event job) has not changed, and then re-register the jobnet or job for execution. Alternatively, use the ajschgstat command or the Change Job Status dialog box to change the status.

KAVT0268-W

The data arrival confirmation of a socket failed. (maintenance-information) (host=agent-host-name, maintenance-information, IPAddress=IP-address#)

An attempt to communicate with the agent indicated in agent-host-name has failed due to a temporary communication error. The start time of a jobnet with start conditions or an event job may be delayed.

#

The IP address is output only when the LOGIPV6INFOALL environment setting parameter is set to yes. If the LOGIPV6INFOALL environment setting parameter is set to yes and the IP address is unknown, unknown is displayed.

(S)

Retries communication after the predefined period of time.

For details on this time, see Table 2-3 in 2.2.2(4) Notes on manager/agent system configurations in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

(O)

A communication error may have occurred due to one of the following reasons. For a jobnet with start conditions or an event job, no action is required because the data that caused the communication error will be resent automatically after the predefined period of time:

The network or the agent machine has stopped.

A temporary communication error occurred.

The event job attempted processing exceeding its throughput.

If a network error occurred, examine the cause of the error and correct it.

If the agent machine indicated in agent-host-name has stopped, restart it.

If a one-time communication error occurred due to heavily-loaded communications that are caused by too many event jobs being processed at once, ignore the message and continue the operation. However, if this message frequently appears, the throughput may be exceeded. See 3. Estimates in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide, and recheck the estimates for using event jobs.

KAVT0271-E

An attempt to get the IP address of the host (name-of-host-whose-IP-address-could-not-be-obtained) during the start notification from the agent (name-of-host-notifying-startup-from-agent) failed. (maintenance-information)

During startup of the agent host, an attempt to start a jobnet with start conditions or an event job for the agent started by the manager has failed.

(S)

A jobnet with start conditions or an event job that was being monitored on the host indicated by name-of-host-whose-IP-address-could-not-be-obtained can no longer be monitored.

(O)

On the manager host, use the jp1ping command to check whether the IP address of the host indicated by name-of-host-whose-IP-address-could-not-be-obtained can be obtained. For details on the jp1ping command, see the JP1/Base User's Guide.

If the IP address cannot be obtained, specify the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the correct address can be obtained by resolving the name. Next, forcibly terminate the relevant jobnet with start conditions or event job, and then re-execute it.

KAVT0272-E

An attempt to get the IP address of the host (name-of-host-whose-IP-address-could-not-be-obtained) during the stop notification from the agent (name-of-host-notifying-termination-from-agent) failed. (maintenance-information)

During termination of the agent host, an attempt to stop an event job for the agent started by the manager has failed.

(S)

The status of the event job being executed on the host indicated by name-of-host-whose-IP-address-could-not-be-obtained remains now running.

(O)

On the manager host, use the jp1ping command to check whether the IP address of the host indicated by name-of-host-whose-IP-address-could-not-be-obtained can be obtained. For details on the jp1ping command, see the JP1/Base User's Guide.

If the IP address cannot be obtained, specify the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the correct address can be obtained by resolving the name. Next, start the agent and forcibly terminate the relevant event job.

KAVT0273-W

Too many simultaneous events are generated for a jobnet with a start condition, so processing performance may be degraded. (jobnet-name) (host=agent-host-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

Too many concurrently occurring events for the jobnet with starting conditions may lower processing performance.

(S)

Continues processing.

(O)

Use the ajsname command with the -I option to identify the unit name from the unit ID. Recheck the number of events that occur for the identified jobnet with start conditions, and then reduce the number of events.

KAVT0280-E

An attempt to get the IP address of the host (agent-host-name) during the starting of the manager failed. (maintenance-information)

During starting of the event/action control manager, an attempt to obtain the IP address of the agent host has failed.

(S)

Continues processing.

(O)

Check whether you can obtain the IP address associated with the agent host name. If you cannot obtain it, set the environment so that the IP address can be resolved by DNS or the hosts file.

KAVT0281-E

An error occurred, caused by an internal aspect of the event action function. Execution of the event job will result in an error. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred due to an internal factor of the event/action control. Execution of the event job will result in an error.

(S)

Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)

The error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators).

The unit (a jobnet with start conditions or an event job) indicated by AjsServiceName=scheduler-service-name, UnitID=unit-ID, and ExecID=execution-ID may not have been registered, executed, or operated, or processing may not have been done in response to the event. Use the ajsname command with the -I option to identify the unit name from the unit ID. Make sure that the status of the identified unit (a jobnet with start conditions or an event job) has not changed, and then re-register the jobnet or job for execution. Alternatively, use the ajschgstat command or the Change Job Status dialog box to change the status.

KAVT0282-E

An error occurred, caused by an internal aspect of the event action function. (maintenance-information)

An error occurred due to an internal factor of the event/action control.

(S)

Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)

The error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators).

The unit (a jobnet with start conditions or an event job) may not have been registered, executed, or operated, or processing may not have been done in response to the event. Make sure that the status of the currently running unit (a jobnet with start conditions or an event job) has not changed. Then re-register the jobnet or job for execution, or use the ajschgstat command or the Change Job Status dialog box to change the status.

KAVT0283-E

Memory is insufficient. (maintenance-information)

Memory was insufficient.

(S)

Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)

See 3. Estimates in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide, and make sure that the required amount of memory for executing JP1/AJS3 has been allocated. The unit (a jobnet with start conditions or an event job) may not have been registered, executed, or operated, or processing may not have been done in response to the event. Make sure that the status of the currently running unit (a jobnet with start conditions or an event job) has not changed. Then re-register the jobnet or job for execution, or use the ajschgstat command or the Change Job Status dialog box to change the status.

KAVT0284-E

Memory is insufficient. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

Memory was insufficient.

(S)

Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)

See 3. Estimates in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide, and make sure that the required amount of memory for executing JP1/AJS3 has been allocated. The unit (a jobnet with start conditions or an event job) indicated by AjsServiceName=scheduler-service-name, UnitID=unit-ID, and ExecID=execution-ID may not have been registered, executed, or operated, or processing may not have been done in response to the event. Use the ajsname command with the -I option to identify the unit name from the unit ID. Make sure that the status of the identified unit (a jobnet with start conditions or an event job) has not changed, and then register the job or jobnet for execution. Alternatively, use the ajschgstat command or the Change Job Status dialog box to change the status.

KAVT0285-I

An attempt to communicate with the agent has failed. (host=agent-host-name, maintenance-information)

An attempt to communicate with the agent has failed.

An attempt to communicate with the agent indicated in agent-host-name has failed due to a temporary communication error.

(S)

Retries communication after the predefined period of time.

For details on this time, see Table 2-3 in 2.2.2(4) Notes on manager/agent system configurations in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

(O)

This message might appear when the communication status between the manager and the agent is unstable. Ignore the message and continue the operation because the data that could not be sent will be resent to the manager automatically after a predefined period of time.

If this message appears frequently, check whether:

A network failure has occurred.

JP1/AJS3 on the manager host is running.

A heavy load is placed on the manager.

KAVT0287-E

The files will be deleted, because the internal files of event action control have been destroyed. (maintenance-information)

The files will be deleted because the internal files of the event action control have been corrupted.

(S)

Continues processing.

(O)

Take appropriate action as shown below:

When you use JP1/AJS3 in a manager-agent configuration, perform a cold start for JP1/AJS3 on the agent host.

If this message was output during startup of JP1/AJS3, all jobnets with start conditions or event jobs being registered terminate abnormally. Re-register them for execution.

If this message was output during operation, restart JP1/AJS3. Then, re-register the jobnet with start conditions or the event job for execution.

KAVT0288-I

Disaster-recovery start processing will be performed.

The event/action control manager on the remote site is beginning the disaster recovery start process.

(S)

Continues processing.

KAVT0289-E

Failed to perform the disaster-recovery start process.(maintenance-information)

The event/action control manager on the remote site failed to perform the disaster recovery start process.

(S)

One or more event job that was running on the main site remains in Now running status.

(O)

Check the jobnet status using a command or JP1/AJS3 - View, and forcibly terminate any event jobs or jobnets with start conditions that are in Now running status.

KAVT0293-W

An attempt to communicate with the agent has failed.(host=agent-host-name, maintenance-information, IPAddress=IP-address#)

An attempt to communicate with the agent indicated by host= agent-host-name has failed.

The start time of a jobnet with a start condition or an event job might be delayed.

#

The IP address is output only when the LOGIPV6INFOALL environment setting parameter is set to yes. If the LOGIPV6INFOALL environment setting parameter is set to yes and the IP address is unknown, unknown is displayed.

(S)

Retries communication after the predefined period of time.

For details on this time, see Table 2-3 in 2.2.2(4) Notes on manager/agent system configurations in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

(O)

The cause of the communication error might be one of the following:

There is a network failure.

The agent machine or the JP1/AJS3 has stopped.

The IP address of agent-host-name cannot be acquired.

If there is a network failure, investigate the cause of the network failure and correct the cause.

If the agent machine indicated by host=agent-host-name or JP1/AJS3 has stopped, restart the agent machine or JP1/AJS3.

If the IP address of the agent host indicated by host=agent-host-name cannot be acquired, configure DNS and hosts so that the IP address is resolved, and restart JP1/AJS3.

KAVT0294-W

Unreported information for scheduler-service-name will now be deleted, because the total amount of unreported information for the scheduler service has exceeded threshold.

Unreported information for scheduler-service-name will be deleted because the total amount of unreported information for the scheduler service exceeded the value indicated in threshold.

(S)

Deletes unreported information for the scheduler service, beginning from the oldest item, each time the threshold is exceeded.

(O)

Check whether:

The scheduler service has started.

There is an event job whose status has not changed properly.

If you find such an event job, change the job status or re-execute the job as required.

KAVT0295-W

Unreported information will now be deleted, because the amount of unreported information for scheduler-service-name has exceeded threshold.

Unreported information will be deleted because the amount of unreported information for scheduler-service-name exceeded the value indicated in threshold.

(S)

Deletes unreported information for the indicated scheduler service, beginning from the oldest item, each time the threshold is exceeded.

(O)

Check whether:

The scheduler service has started.

There is an event job whose status has not changed properly.

If you find such an event job, change the job status or re-execute the job as required.

KAVT0296-W

Unreported information for agent-host-name will now be deleted, because the total amount of unreported information for the agent has exceeded threshold.(maintenance-information)

Unreported information for agent-host-name will be deleted because the total amount of unreported information for the agent exceeded the value indicated in threshold.

(S)

Deletes unreported information for the agent, beginning from the oldest item, each time the threshold is exceeded. This action might result in the following symptoms:

When an event job is registered for execution, the status of the job does not change from now queuing to now running.

When an event job (including an event job defined in the start conditions) is forcibly terminated, the now running status of the job does not change.

(O)

Check whether:

The agent host name# can be resolved on the manager host.

If the name cannot be resolved, specify the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the agent host name can be resolved.

The IP address obtained by resolving the agent host name on the manager host is the same as the actual IP address of the agent host.

If the IP addresses are different, specify the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the correct IP address can be obtained by resolving the name.

The JP1/AJS3 service on the agent host is running or the agent host machine itself is running.

If JP1/AJS3 on the agent host and the agent host itself are not running, start them.

There are problems with the network environment.

Use the ping command or another means to check whether the manager host can communicate with the agent host via TCP/IP. If there are communication problems, correct them.

In addition to performing the actions described above, you might also need to perform the following additional actions, depending on the type of deleted communication data:

Check whether the status of an event job registered for execution has changed from now queuing to now running.

If there is no change, forcibly terminate the job, and then re-execute it.

Check whether the now running status of an event job (including an event job defined in the start conditions) that has been forcibly terminated has changed.

If there is no change, forcibly terminate the job, and then re-execute it.

Ensure that no event has been detected within a certain period of time after the relevant message was output.

Because data waiting to be returned remains on the agent, restart the agent.

Note that when the agent is restarted, it resends the remaining data to the manager. If the amount of the data is large, manager load might increase severely, succeeding jobs might have to wait a long time in the queue, or event detection might be seriously delayed. To avoid these problems, cold-start the agent if 1,000 or more events have been detected within a few hours after the relevant message was output.

#

For a physical host:

For DNS operation, the host name in the FQDN format. For other cases, the host name obtained by executing the hostname command

For a logical host:

In Windows:

The host name indicated in xxxxx in JP1/AJS3_xxxxx in the Services window that is displayed by choosing Services or by choosing Administrative Tools and then Services in the Control Panel window on the agent host

In UNIX:

The host name indicated after the jajs_spmd process that is displayed by executing the ps command

KAVT0297-W

Unreported information will now be deleted, because the amount of unreported information for agent-host-name has exceeded threshold.(maintenance-information)

Unreported information will be deleted because the amount of unreported information for the agent indicated in agent-host-name exceeded the value indicated in threshold.

(S)

Deletes unreported information for the indicated agent, beginning from the oldest item, each time the threshold is exceeded. This action might result in the following symptoms:

When an event job is registered for execution, the status of the job does not change from now queuing to now running.

When an event job (including an event job defined in the start conditions) is forcibly terminated, the now running status of the job does not change.

(O)

Check whether:

The agent host name# can be resolved on the manager host.

If the name cannot be resolved, specify the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the agent host name can be resolved.

The IP address obtained by resolving the agent host name on the manager host is the same as the actual IP address of the agent host.

If the IP addresses are different, specify the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the correct IP address can be obtained by resolving the name.

The JP1/AJS3 service on the agent host is running or the agent host machine itself is running.

If JP1/AJS3 on the agent host and the agent host itself are not running, start them.

There are problems with the network environment.

Use the ping command or another means to check whether the manager host can communicate with the agent host via TCP/IP. If there are communication problems, correct them.

In addition to performing the actions described above, you might also need to perform the following additional actions, depending on the type of deleted communication data:

Check whether the status of an event job registered for execution has changed from now queuing to now running.

If there is no change, forcibly terminate the job, and then re-execute it.

Check whether the now running status of an event job (including an event job defined in the start conditions) that has been forcibly terminated has changed.

If there is no change, forcibly terminate the job, and then re-execute it.

Ensure that no event has been detected within a certain period of time after the relevant message was output.

Because data waiting to be returned remains on the agent, restart the agent.

Note that when the agent is restarted, it resends the remaining data to the manager. If the amount of the data is large, manager load might increase severely, succeeding jobs might have to wait a long time in the queue, or event detection might be seriously delayed. To avoid these problems, cold-start the agent if 1,000 or more events have been detected within a few hours after the relevant message was output.

#

For a physical host:

For DNS operation, the host name in the FQDN format. For other cases, the host name obtained by executing the hostname command

For a logical host:

In Windows

The host name indicated in xxxxx in JP1/AJS3_xxxxx in the Services window that is displayed by choosing Services or by choosing Administrative Tools and then Services in the Control Panel window on the agent host

In UNIX

The host name indicated after the jajs_spmd process that is displayed by executing the ps command

KAVT0301-I

Event Action SubManager will now start. (maintenance-information)

The event/action control submanager starts.

(S)

Continues processing.

KAVT0302-I

Event Action SubManager has started. (maintenance-information)

The event/action control submanager has started.

(S)

Continues processing.

KAVT0303-I

Event Action SubManager will now end. (maintenance-information)

The event/action control submanager terminates.

(S)

Continues processing.

KAVT0325-E

Event Action Manager has ended so the process will now stop. (maintenance-information)

The event/action control submanager will terminate because the event/action control manager has terminated.

(S)

Terminates the event/action control submanager.

(O)

Confirm that the directory for output of the wait information file can be accessed, and then restart JP1/AJS3.

If the KAVT0187-E message was also output at the same time this message was output, the probable cause is that the directory for output of the wait information file cannot be accessed. Confirm that the directory for output of the wait information file can be accessed. If there are any problems, correct them.

Especially, if this message appears during failover, allocation of the shared disk might have been canceled before JP1/AJS3 stopped. Review and, if necessary, correct the cluster software settings so that allocation of the shared disk is canceled after JP1/AJS3 and JP1/Base stops.

For details about the prerequisites for using the cluster system, see 10.1.1(1) Prerequisites for a logical host environment in the JP1/Automatic Job Management System 3 Administration Guide.

KAVT0328-E

The file read-in of list for repetition check failed. (maintenance-information)

An attempt to read an internal file used in the event/action control submanager has failed.

(S)

Terminates the event/action control submanager.

(O)

Check whether:

The system resources are sufficient.

The user who started JP1/AJS3 has superuser privileges or administrator privileges.

KAVT0332-W

The number of requests from the scheduler service exceeds threshold. Processing the requests from the scheduler service might be delayed. (maintenance-information)

The number of requests from the scheduler service exceeded the value indicated in threshold. Processing for the requests from the scheduler service might be delayed.

(S)

Continues processing.

(O)

Check the schedule. If a mass of event jobs or jobnets with start conditions are scheduled to be registered for execution at the same time, recheck the operation. For example, schedule the registration of jobs or jobnets at different times.

KAVT0333-W

The number of the reported events from agent-name exceeds threshold. Processing the events from agent-name might be delayed. (maintenance-information)

The number of events reported from the agent indicated in agent-name exceeded the value indicated in threshold. Processing for the events from the agent might be delayed.

(S)

Continues processing.

(O)

Check the definition of the event job or the jobnet with start conditions for which the agent is defined as the execution host. If the definition will cause a mass of events to be generated at the same time, recheck the operation to reduce the number of events to be generated.

If this message is output after JP1/AJS3 on the agent is restarted, do the following:

Check whether the agent host name# can be resolved on the manager host.

If the name cannot be resolved, specify the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the agent host name can be resolved.

Check whether the IP address obtained by resolving the agent host name on the manager host is the same as the actual IP address of the agent host.

If the IP addresses are different, specify the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the correct IP address can be obtained by resolving the name.

Check whether the JP1/AJS3 service on the agent host are running or whether the agent host machine itself is running.

If JP1/AJS3 on the agent host and the agent host itself are not running, start them.

Check whether there are problems with the network environment.

Use the ping command or another means to check whether the manager host can communicate with the agent host via TCP/IP. If there are communication problems, correct them.

#

For a physical host:

For DNS operation, the host name in the FQDN format. For other cases, the host name obtained by executing the hostname command

For a logical host:

In Windows

The host name indicated in xxxxx in JP1/AJS3_xxxxx in the Services window that is displayed by choosing Services or by choosing Administrative Tools and then Services in the Control Panel window on the agent host

In UNIX

The host name indicated after the jajs_spmd process that is displayed by executing the ps command

KAVT0340-W

Communication to check the operation of the Event Action SubManager failed. The communication will be retried.(maintenance-information)

A communication error occurred during processing to periodically check whether the event/action control submanager is running.

The communication will be retried.

(S)

Continues processing.

(O)

Check the following:

Check whether a mass of events has been detected.

For a physical host, check whether the disk that contains the JP1/AJS3 installation directory has sufficient free space. Also check whether the installation directory can be accessed.

For a logical host, check whether the shared disk has sufficient free space and can be accessed.

Check whether communication is possible with all the target hosts displayed by the ajsagtshow command.

Check whether any process is accessing a file in the JP1/AJS3 installation path.

Check whether memory is sufficient.

Correct the above problems, and then check whether the event jobs and start conditions work normally.

If they do not work normally after a while, there might be a problem with the status management of event jobs and start conditions.

Cold-start the scheduler service indicated in maintenance-information, or execute the jpomanevreset command. For details on the jpomanevreset command, see jpomanevreset in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVT0341-W

Communication to check the operation of the Event Action Manager failed. The communication will be retried.(maintenance-information)

A communication error occurred during communication to periodically check whether the event/action control manager is running.

The communication will be retried.

(S)

Continues processing.

(O)

Check the following:

Check whether a mass of events has been detected.

For a physical host, check whether the disk that contains the JP1/AJS3 installation directory has sufficient free space. Also check whether the installation directory can be accessed.

For a logical host, check whether the shared disk has sufficient free space and can be accessed.

Check whether communication is possible with all the target hosts displayed by the ajsagtshow command.

Check whether any process is accessing a file in the JP1/AJS3 installation path.

Check whether memory is sufficient.

Correct the above problems, and then check whether the event jobs and start conditions work normally.

If they do not work normally after a while, there might be a problem with the status monitoring of the event jobs and start conditions.

Cold-start the scheduler service indicated in maintenance-information, or execute the jpomanevreset command. For details on the jpomanevreset command, see jpomanevreset in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVT0342-I

Communication to check the operation of the Event Action SubManager has been restored.(maintenance-information)

Communication to check the operation of the event/action control submanager has been recovered.

(S)

Continues processing.

KAVT0343-I

Communication to check the operation of the Event Action Manager has been restored.(maintenance-information)

Communication to check the operation of the event/action control manager has been recovered.

(S)

Continues processing.

KAVT0344-W

There is no response from the Event Action SubManager.(maintenance-information)

No response has been sent from the event/action control submanager.

(S)

Continues processing.

(O)

Check the following:

Check whether a mass of events has been detected.

For a physical host, check whether the disk that contains the JP1/AJS3 installation directory has sufficient free space. Also check whether the installation directory can be accessed.

For a logical host, check whether the shared disk has sufficient free space and can be accessed.

Check whether communication is possible with all the target hosts displayed by the ajsagtshow command.

Check whether any process is accessing a file in the JP1/AJS3 installation path.

Check whether memory is sufficient.

Correct the above problems, and then check whether the event jobs and start conditions work normally.

If they do not work normally after a while, there might be a problem with the status management of event jobs and start conditions.

Cold-start the scheduler service indicated in maintenance-information, or execute the jpomanevreset command. For details on the jpomanevreset command, see jpomanevreset in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVT0345-W

There is no response from the Event Action Manager.(maintenance-information)

No response has been sent from the event/action control manager.

(S)

Continues processing.

(O)

Check the following:

Check whether a mass of events has been detected.

For a physical host, check whether the disk that contains the JP1/AJS3 installation directory has sufficient free space. Also check whether the installation directory can be accessed.

For a logical host, check whether the shared disk has sufficient free space and can be accessed.

Check whether communication is possible with all the target hosts displayed by the ajsagtshow command.

Check whether any process is accessing a file in the JP1/AJS3 installation path.

Check whether memory is sufficient.

Correct the causes of the above problems, and then check whether the event jobs and start conditions work normally.

If they do not work normally after a while, there might be a problem with the status management of event jobs and start conditions.

Cold-start the scheduler service indicated in maintenance-information, or execute the jpomanevreset command. For details on the jpomanevreset command, see jpomanevreset in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVT0346-I

A response from the Event Action SubManager has been confirmed.(maintenance-information)

A response from the event/action control submanager has been confirmed.

(S)

Continues processing.

KAVT0347-I

A response from the Event Action Manager has been confirmed.(maintenance-information)

A response from the event/action control manager has been confirmed.

(S)

Continues processing.

KAVT0351-W

The obstacle status of the exec-agent (exec-agent-name:exec-host-name) was changed to unconnectable status.(logical-host-name)

Because a communication failure was detected for an execution host, the status of the execution agent indicated by exec-host-name was changed to Unconnectable.

Note that, if the execution host is a physical host, JP1_DEFAULT is output for logical-host-name.

(S)

Changes the status of the execution agent to Unconnectable, and then executes the subsequent processing.

(O)

The probable causes are:

The execution host name cannot be resolved.

The maximum number of file descriptors that can be used by the agent monitoring process was reached.

No ports are available on the manager host.

The execution host has stopped.

JP1/AJS3 is not running on the execution host.

A firewall rejected the connection.

Remove the causes of the communication failure. Then, wait until recovery of the indicated execution agent is confirmed by a communication recovery check. Alternatively, use the ajsagtalt command to change the status of the execution agent to Not checked.

KAVT0352-E

The connection to the network service was released. (maintenance-information)

The connection with the communication control process was lost.

(S)

Continues processing without changing the status of the event job or the jobnet with start conditions.

(O)

Check whether the communication control process has been stopped by the jajs_hstd_stop command.

For details, see jajs_hstd_stop in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

Use the following procedure to find out whether the communication control process has stopped for some other reason.

In Windows

Use the jajs_spmd_status command to make sure the network process is running.

In UNIX

Use the jajs_spmd_status command to make sure the ajsnetwd process is running.

For details, see jajs_spmd_status in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

If the communication control process is not running, take the following action:

If the jajs_hstd_stop command was used to stop the communication control process:

Ignore the message and continue operation.

If the jajs_hstd_stop command was not used to stop the communication control process:

Something other than the jajs_hstd_stop command might have caused the communication control process to stop. Use the error messages that are output before and after this message to determine the cause of the error, and take corrective action.

If the process still does not start, use the following procedure:

In Windows

Use the jajs_hstd command to start the network process.

In UNIX

Use the jajs_hstd command to start the ajsnetwd process.

For details, see jajs_hstd in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

If the communication control process is running, a temporary communication error might have occurred. Take the following action:

If the message KAVT0353-I is output after this message

The connection has recovered. Ignore the message and continue operation.

If the message KAVT0353-I is not output after this message

Identify the cause of the error from the errno value in the maintenance information, and take action to correct it.

errno takes the following values:

In Windows

The value acquired by the GetLastError function of the Win32 API

In UNIX

The value acquired by errno

KAVT0353-I

The connection to the network service was recovered. (maintenance-information)

The connection with the communication control process was restored.

(S)

Continues processing.

KAVT0357-E

An attempt to get the IP address of the host (destination-host-name) during communication with the agent failed. (maintenance-information)

An attempt to obtain the IP address of the host indicated in destination-host-name failed during communication with the agent. The start time of a jobnet with start conditions or an event job might have been delayed, or an event registered for execution might remain in the Now queuing status, rather than being placed in the Now running status.

(S)

Retries communication after the predefined period of time.

For details about this time, see Table 2-3 in 2.2.2(4) Notes on manager/agent system configurations in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

(O)

Use the jp1ping command to confirm that the IP address of the host indicated in destination-host-name can be obtained on the manager host.

For details on the jp1ping command, see the JP1/Base User's Guide.

If the IP address cannot be obtained, specify the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the correct address can be obtained by resolving the name. For details about name resolution, see 2.2.2(4) Notes on manager/agent system configurations in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVT0401-E

An internal error occurred. (maintenance-information)

An error occurred due to an internal factor of the event/action control.

(S)

Determines the event job to be an error.

(O)

The error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT0402-E

Memory became insufficient. (maintenance-information) (maintenance-information)

Memory became insufficient.

(S)

Determines the event job to be an error.

(O)

See 3. Estimates in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide, and make sure that the required amount of memory for executing JP1/AJS3 has been allocated.

KAVT0403-E

The specified agent is not defined in the job execution environment. (host=exec-agent, maintenance-information)

The execution agent name defined for the execution agent is not defined as an execution agent.

(S)

Determines the event job to be an error.

(O)

Make sure that the execution agent name specified for the execution agent for the job is correct, or check whether an execution agent group name is specified.

Event jobs (including those defined as start conditions of jobnets with start conditions) do not support execution agent groups. For details on the operation performed when an execution agent group is specified for the event job, see 7.6 Notes on using event jobs in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

If the execution agent name specified for the job is correct, the execution agent has not been defined in the agent management information. Add the agent specified as the execution agent for the job to the agent management information.

KAVT0404-E

An error occurred during communication with the agent. (maintenance-information)

Communication with the agent failed.

(S)

Determines the event job to be an error.

(O)

Check the following:

Check whether the target host and JP1/AJS3 have started.

If the agent uses the connection source restriction function, check whether the manager's IP address is registered in the agent connection permission configuration file.

KAVT0405-W

Because communication with the agent failed, it will be retried.

An attempt to communicate with the agent failed because of a temporary communication error.

(S)

Retries communication after waiting the predefined period of time.

For details on the wait time, see Table 2-3 in 2.2.2(4) Notes on manager/agent system configurations in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

(O)

Make sure the target host and JP1/AJS3 are running.

KAVT0406-E

Socket communication failed. (maintenance-information)

Communication with the event/action control manager failed.

(S)

Determines the event job to be an error.

(O)

Check whether an error has occurred in the network.

If no error has occurred in the network, the error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT0408-E

The definition information of the specified agent is now being changed so you cannot use the agent. (host=agent-host-name, maintenance-information)

You cannot use the agent host indicated in agent-host-name because its configuration definition information is being changed.

(S)

Determines the event job to be an error.

(O)

Wait until the change of the configuration definition information (environment setting) terminates, than then retry.

KAVT0409-I

The data was sent to the agent.

The data was sent to the agent.

(S)

Continues processing.

KAVT0410-E

The parameter (parameter) after replacing a macro variable is too long (length=parameter-length).

The parameter, after replacing a macro variable, is too long.

(S)

Determines the event job to be an error.

(O)

Recheck the setting of the parameter that caused the error, and then re-execute the event job. If ex is indicated in parameter, also check the setting of the jobnet execution host.

KAVT0411-E

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

The macro variable was not inherited.

(S)

Determines the event job to be an error.

(O)

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

KAVT0412-W

The half at new branch execution ID acquisition waiting time has passed. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID)

One half (30 minutes#2) of the waiting time for acquisition of the branch execution ID (one hour#1) has passed.

30 minutes#2 later, the status of the jobnet with start conditions might change to Monitor terminated.

#1

For the compatible ISAM configuration, 30 minutes.

#2

For the compatible ISAM configuration, 15 minutes.

(S)

Continues processing.

(O)

Startup of a jobnet with start conditions takes a long time due to heavy loading on the schedule control.

The probable causes are:

Many events being monitored by the jobnet with start conditions have occurred.

Many jobnets in a batch or a jobnet containing many jobs was registered for execution or terminated forcibly.

A jobnet with many logs to keep was unregistered.

A jobnet with many fixed generations was unregistered.

Many jobnets set in the schedule have reached the start time at the same time.

A jobnet with start conditions having many generations whose start conditions (AND) are partially satisfied is terminated forcibly, or is placed in Monitor terminated status due to the valid range of start condition.

The system loading is heavy due to a program other than JP1/AJS3.

If any of the above problems occurred and JP1/AJS3 caused the load, wait until processing terminates. If a program other than JP1/AJS3 caused the load, terminate that program as required.

To determine the name of the delayed jobnet with start conditions, you can use the unit ID displayed by executing the ajsname command with the -I option specified.

KAVT0413-E

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:scheduler-service-name:target-host:maintenance-information)

The execution agent specified for a job 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 as follows:

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

A permitted execution host is specified incorrectly in the execution agent profile.

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

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

KAVT0414-E

The request was rejected. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

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 KAVT0992-E message that was output to the integrated trace log of the host where the job is to be executed.

KAVT0415-E

An attempt to verify the server certificate failed.(logical-host-name, name-of-host-to-be-connected, maintenance-information)

An attempt to verify the server certificate sent from the connection destination failed. The probable causes are as follows:

The connection destination host name does not match the CN or SAN.

The root certificate corresponding to the server certificate is not contained in the file specified for CACERTIFICATEFILE in the JP1/Base common definition information.

The current time of the machine in which the error occurred is earlier than the start time of the effective period specified in the server certificate.

The server certificate and the intermediate certificate are joined in an incorrect order.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Cancels communication processing, and then continues subsequent processing.

(O)

If the connection destination host name does not match the CN or SAN:

Match the connection destination host name to the CN or SAN.

If the root certificate corresponding to the server certificate is not contained in the file specified for CACERTIFICATEFILE in the JP1/Base common definition information:

Add the corresponding root certificate to the file specified for CACERTIFICATEFILE in the common definition information.

If the current time of the machine in which the error occurred is earlier than the start time of the effective period specified in the server certificate:

Retry the operation after the start time of the effective period specified in the server certificate.

If the server certificate and the intermediate certificate are joined in an incorrect order:

Join the server certificate and the intermediate certificate in the correct order.

KAVT0416-E

An error occurred in SSL communication processing.(logical-host-name, name-of-host-to-be-connected, maintenance-information)

An error occurred during SSL communication processing. The probable causes are as follows:

The communication encryption function is disabled at the connection destination.

A temporary communication error occurred.

If this message is output at the reception side of TCP/IP communication, a null character string is output for connection-destination-host-name.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Cancels communication processing, and then continues subsequent processing.

(O)

If the communication encryption function is disabled at the connection destination:

Enable the communication encryption function for the host indicated in connection-destination-host-name.

If a temporary communication error occurred:

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

KAVT0417-W

The certificate has expired.(logical-host-name, name-of-host-to-be-connected)

The server certificate sent from the connection destination or the root certificate located on the local host has expired.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Continues processing.

(O)

Acquire a new certificate, and replace the expired certificate with it.

KAVT0498-I

JP1/AJS2 Event Action Manager will now start.

The event/action control manager will now start.

(S)

Continues processing.

KAVT0499-I

JP1/AJS2 Event Action Manager will now end.

The event/action control manager will now terminate.

(S)

Continues processing.

KAVT0502-E

The installation path could not be acquired.

The directory that installs JP1/AJS3 could not be obtained. For Windows, the registry information may be corrupted.

(S)

Terminates the event/action control agent.

(O)

Registry information may have been corrupted. Re-reinstall and then restart JP1/AJS3.

KAVT0508-E

A message-reception pipe could not be opened. (process type=process-type maintenance-information) (process name=process-name, maintenance-information)

An attempt to create a pipe file used in the event/action control agent has failed.

(S)

Continues processing while the function of the process indicated in process-type is disabled.

process-type

0: Receive JP1 Event job, Monitoring Log Files job, or Monitoring Event Log job

1: Monitoring Files job

2: Receive MQ Message job

3: Email Reception Monitoring job

4: Interval Control job

5: Receive MSMQ Message job

(O)

Check the following, and then retry:

Check whether system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT0511-E

Memory became insufficient. (host=manager-host-name, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

A memory shortage occurred.

(S)

Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)

First, use the ajsname command with the -I option specified to identify the name of the relevant jobnet with start conditions or the relevant event job. Next, perform the following operation to change the status of the jobnet or job in an ended status:

For a jobnet with start conditions, forcibly terminate the jobnet.

For an event job, terminate the jobnet forcibly or by changing the job status.

Then, if necessary, re-execute the jobnet or job.

For details on the ajsname command, see ajsname in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

In addition, check whether memory is sufficient. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in the documentation for the product (such as Release Notes).

KAVT0512-E

The socket could not be opened. (Manager=name-of-manager-at-send-destination) (maintenance-information)

If name-of-manager-at-send-destination is My Server Host, an attempt to open the socket failed during startup of an event/action control agent process. If name-of-manager-at-send-destination is not My Server Host, communication with the manager host failed after the process started.

(S)

Terminates the process if this message appears during startup of the event/action control agent process.

If this message appears after the process started, the system continues processing without changing the status of an event job or jobnet with start conditions.

(O)

If name-of-manager-at-send-destination is My Server Host, check the following:

Check whether the local host name is registered in the hosts file.

If the host name is not registered, register it, and then restart JP1/AJS3.

Check whether the JP1/AJS3 port number is registered in the services file.

If the JP1/AJS3 port number is not registered, register it, and then restart JP1/AJS3.

Check whether any process is using port jp1ajs2eaagt.

Use the netstat command to check for such a process. If a process is using port jp1ajs2eaagt, terminate that process, and then restart JP1/AJS3 or the system.

Check whether the port number of port jp1ajs2eaagt is outside the range of ephemeral ports.

If the port number is within the range of ephemeral ports, perform either of the following operations, and then restart JP1/AJS3:

- Change the range of ephemeral ports so that the port number of port jp1ajs2eaagt on the agent host is outside the range.

- Change the port number of port jp1ajs2eaagt to be outside the range of ephemeral ports for the manager host and agent host.

If name-of-manager-at-send-destination is not My Server Host, from the manager indicated in the message, forcibly terminate the jobnet with start conditions and event job that are being executed on the agent. Then, if necessary, re-execute the event job and jobnet with start conditions.

Also check the following:

Check whether the manager indicated in name-of-manager-at-send-destination is currently in use.

If the manager is not currently in use, stop the JP1/AJS3 service on the host that output this message. Then execute the jpoagoec command to delete information about the manager. For details about jpoagoec command, see jpoagoec in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

Check whether the manager host name is resolved.

If the host name cannot be resolved, define the hosts file, DNS server settings, or jp1hosts or jp1hosts2 information so that the IP address can be obtained from the manager host name.

KAVT0513-E

JP1/AJS2 multi-weighting could not be initialized. (maintenance-information)

An unexpected error occurred.

(S)

Terminates the event/action control agent.

(O)

Check the following, and then restart JP1/AJS3:

Check whether the system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

KAVT0515-E

Main loop of an agent failed. (maintenance-information)

An attempt to start the event/action control agent has failed.

(S)

Terminates the event/action control agent.

(O)

Check the following, and then restart JP1/AJS3:

Check whether the system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

KAVT0520-W

The event monitoring function is unusable. (maintenance-information, process name=process-name, maintenance-information)

The functions of the JP1 event reception monitoring job, log file monitoring job, and Windows event log monitoring job cannot be used because an attempt to start the process that executes these jobs has failed.

(S)

Continues processing in a reduced mode for the functions.

(O)

If you want to use these functions, check the following and then restart JP1/AJS3.

If you do not intend to use these functions, ignore this message and continue operation.

Check whether an executable file with the same name as the process name indicated in process name=process-name exists.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether memory is sufficient.

For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT0521-W

The file monitoring function is unusable. (maintenance-information, process name=process-name, maintenance-information)

The function of the file monitoring job cannot be used because an attempt to start the process that executes this job has failed.

(S)

Continues processing in a reduced mode for the function.

(O)

If you want to use this function, check the following and then restart JP1/AJS3.

If you do not intend to use these functions, ignore this message and continue operation.

Check whether an executable file with the same name as the process name indicated in process name=process-name exists.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether memory is sufficient.

For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT0522-W

The message queue monitoring function is unusable. (maintenance-information, process name=process-name, maintenance-information)

The function of the Receive MQ message job cannot be used because an attempt to start the process that executes this job has failed.

(S)

Continues processing in a reduced mode for the function.

(O)

If you want to use this function, check the following and then restart JP1/AJS3.

If you do not intend to use these functions, ignore this message and continue operation.

Check whether an executable file with the same name as the process name indicated in process name=process-name exists.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether memory is sufficient.

For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT0523-W

The mail monitoring function is unusable. (maintenance-information, process name=process-name, maintenance-information)

The function of the email reception monitoring job cannot be used because an attempt to start the process that executes this job has failed.

(S)

Continues processing in a reduced mode for the function.

(O)

If you want to use this function, check the following and then restart JP1/AJS3.

If you do not intend to use these functions, ignore this message and continue operation.

Check whether an executable file with the same name as the process name indicated in process name=process-name exists.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether memory is sufficient.

For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT0524-W

The timer monitoring function is unusable. (maintenance-information, process name=process-name, maintenance-information)

The functions for interval control and timeout cannot be used because an attempt to start the process that executes the jobnet with these functions specified has failed.

(S)

Continues processing in a reduced mode for the function.

(O)

If you want to use this function, check the following and then restart JP1/AJS3.

If you do not intend to use these functions, ignore this message and continue operation.

Check whether an executable file with the same name as the process name indicated in process name=process-name exists.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether memory is sufficient.

For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT0526-E

The JP1/Base definition could not be read. (maintenance-information)

An attempt to read common definition information has failed.

(S)

Terminates the event/action control agent.

(O)

Use the jbsgetcnf command to check whether you can acquire common definition information for the logical host that caused the error. If you cannot acquire the common definition information, re-install JP1/Base. If you can acquire it, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT0528-E

Invalid specification in configuration definition. (item-name: value)

The configuration definition contains an invalid specification.

(S)

Terminates the event/action control agent.

(O)

Specify the value indicated by item-name correctly, and then restart JP1/AJS3. For details on the output item names, see 20.6 Setting up the event/action control environment in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVT0530-E

The end request for the pipe could not be written. (process type=process-type maintenance-information) (process name=process-name, maintenance-information)

An attempt to write to a pipe file used in the event/action control agent has failed.

(S)

Continues processing while the function of the process indicated in process-type is disabled.

process-type

0: Receive JP1 Event job, Monitoring Log Files job, or Monitoring Event Log job

1: Monitoring Files job

2: Receive MQ Message job

3: Email Reception Monitoring job

4: Interval Control job

5: Receive MSMQ Message job

(O)

The process indicated in process-type may still remain in the system.

In UNIX, use the ps command to check whether the process remains in the system. If the process remains, use the kill command to terminate it.

In Windows, restart the system.

Check the following, and then restart JP1/AJS3:

Check whether system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created at JP1/AJS3 installation is unintentionally deleted.

KAVT0539-E

The auxiliary file could not be read. (auxiliary file=auxiliary-file-name) (maintenance-information)

An attempt to write to a communication information file for a monitoring process in the event/action control agent has failed.

(S)

Places the job in the Ended abnormally status, and continues processing.

(O)

Check the following, and then retry:

Check whether system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created at JP1/AJS3 installation is unintentionally deleted.

KAVT0541-E

The pipe could not be written to. (process type=process-type maintenance-information)

An attempt to write to a pipe file used in the event/action control agent has failed.

(S)

Continues processing while the function of the process indicated in process-type is disabled.

process-type

0: Receive JP1 Event job, Monitoring Log Files job, or Monitoring Event Log job

1: Monitoring Files job

2: Receive MQ Message job

3: Email Reception Monitoring job

4: Interval Control job

5: Receive MSMQ Message job

(O)

Check the following, and then retry:

Check whether system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created at JP1/AJS3 installation is unintentionally deleted. If the code indicated in maintenance-information is -1, this means that the agent process has terminated. Restart JP1/AJS3 on the agent.

KAVT0542-E

The auxiliary file name could not be acquired. (maintenance-information)

An attempt to acquire a communication information file for a monitoring process used in the event/action control agent has failed.

(S)

Places the job in the Ended abnormally status, and continues processing.

(O)

Check the following, and then retry:

Check whether system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created at JP1/AJS3 installation is unintentionally deleted.

KAVT0544-E

The auxiliary file could not be read. (auxiliary file=auxiliary-file-name) (maintenance-information)

An attempt to read a communication information file for a monitoring process used in the event/action control agent has failed.

(S)

Places the job in the Ended abnormally status, and continues processing.

(O)

Check the following, and then retry:

Check whether system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created at JP1/AJS3 installation is unintentionally deleted.

KAVT0559-E

The socket sending failed. (Manager=name-of-manager-at-send-destination) (maintenance-information, IPAddress=IP-address#)

The socket could not be sent to the manager.

#

The IP address is output only when the LOGIPV6INFOALL environment setting parameter is set to yes. If the LOGIPV6INFOALL environment setting parameter is set to yes and the IP address is unknown, unknown is displayed.

(S)

Continues or terminates processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)

This message appears when the manager is loaded or when a network error occurred. Check whether the manager host and JP1/AJS3 have started, check the unit (a jobnet with start conditions or an event job) whose status has not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status.

KAVT0562-I

The agent process of the event action function will now start.

The event/action control agent will now start.

(S)

Starts the event/action control agent.

KAVT0563-I

The agent process of the event action function will now end.

The event/action control agent will now end.

(S)

Terminates the event/action control agent.

KAVT0566-E

The size of the working path exceeds the limit.

The length of any of the following directory names exceeded 228 bytes: After correcting the error, stop the JP1/AJS3 service and restart it.

The JP1/AJS3 installation directory name

The WaitInfFileOutDir environment setting parameter for the definition key ([JP1AOMAGENT])

(S)

Terminates processing.

(O)

Correct the length of the following directory names to 228 bytes or smaller.

The JP1/AJS3 installation directory name

The WaitInfFileOutDir environment setting parameter for the definition key ([JP1AOMAGENT])

KAVT0567-E

The requested event icon is unusable. (event type=event-type) (host= manager-host-name, maintenance-information)

The requested event job cannot be used. Alternatively, the manager requested a code that was not supported.

(S)

Continues processing while the function of the event job indicated in event-type is disabled.

event-type

JP1/AJS2_EVACT_MAIL_WATCH: Email reception monitoring job

JP1/AJS2_EVACT_MQ_WATCH: Message queue reception monitoring job

JP1/AJS2_EVACT_MSMQ_WATCH: MSMQ reception monitoring job

(O)

Check whether the function of the requested event job is enabled in the agent configuration definition (environment setting).

For details about the email reception monitoring job, see 2. Linking Mail Systems in the JP1/Automatic Job Management System 3 Linkage Guide.

KAVT0570-E

The handle from the process monitor could not be acquired. (maintenance-information) Stopping via the JPI/AJS2 service is not possible.

Communication with the JP1/AJS3 process monitor failed.

(S)

Continues processing, but does not accept the jajs_spmd_stop command or a stop request from the JP1/AJS3 service.

(O)

To terminate the event/action control agent in UNIX, use the kill command to terminate the jpoagent process. In Windows, restart the system.

The JP1/AJS3 process monitor may not operate correctly. Reinstall JP1/AJS3 and then restart.

KAVT0572-E

A report to the process monitor failed. (maintenance-information)

Communication with the JP1/AJS3 process monitor failed.

(S)

Continues processing, but does not accept the jajs_spmd_stop command or a stop request from the JP1/AJS3 service.

(O)

To terminate the event/action control agent in UNIX, use the kill command to terminate the jpoagent process. In Windows, restart the system.

The JP1/AJS3 process monitor may not operate correctly. Reinstall JP1/AJS3 and then restart.

KAVT0582-W

Unreported information exceeded the warning value. Check whether the manager (manager-name) is running.

The amount of information that cannot be reported to the manager exceeded the warning value.

(S)

Continues processing.

(O)

This message warns you of the number of unprocessed events that exceeded the specified value. Check whether the manager has started, and then check the following.

If the manager is not running

Start the manager so that it can receive notifications from the agent.

If the manager is running

Check the following:

Check whether an event job has terminated normally or whether a jobnet with start conditions has started.

If processing is proceeding without any problems, ignore this message and allow the processing to continue.

Check whether many events that are monitored with start conditions have occurred.

Review the definitions of event jobs or jobnets with start conditions that are defined to be executed on the relevant agent. If a definition will result in many events, review and change operation to reduce the number of events that will occur.

Check whether the manager and agent can communicate with each other.

See the following supplementary notes and check whether the manager and agent can communicate with each other.

Supplementary notes

Check whether the agent host name# can be resolved on the manager host.

If the name cannot be resolved, specify the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the agent host name can be resolved.

Check whether the manager host name# can be resolved on the agent host.

If the name cannot be resolved, specify the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the agent host or in the DNS settings so that the manager host name can be resolved.

Check whether the IP address obtained by resolving the agent host name on the manager host is the same as the actual IP address of the agent host.

If the IP addresses are different, specify the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the correct IP address can be obtained by resolving the name.

Check whether the IP address obtained by resolving the manager host name on the agent host is the same as the actual IP address of the manager host.

If the IP addresses are different, specify the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the agent host or in the DNS settings so that the correct IP address can be obtained by resolving the name.

Check whether there are problems with the network environment.

Use the ping command or another means to check whether the manager host can communicate with the agent host via TCP/IP. If there are communication problems, correct them. Similarly, check whether the agent host can communicate with the manager host, and correct any problems you find.

#

For a physical host:

For DNS operation, the host name in the FQDN format. For other cases, the host name obtained by executing the hostname command

For a logical host:

In Windows

The host name indicated in xxxxx in JP1/AJS3_xxxxx in the Services window that is displayed by choosing Services or by choosing Administrative Tools and then Services in the Control Panel window on the agent host

In UNIX

The host name indicated after the jajs_spmd process that is displayed by executing the ps command

KAVT0588-E

The specified working path does not exist.

The directory specified for any of the following directory names does not exist: After correcting the error, stop the JP1/AJS3 service and restart it.

The JP1/AJS3 installation directory name

The WaitInfFileOutDir environment setting parameter for the definition key ([JP1AOMAGENT])

(S)

Terminates processing.

(O)

Specify the following directory names.

The JP1/AJS3 installation directory name

The WaitInfFileOutDir environment setting parameter for the definition key ([JP1AOMAGENT])

KAVT0590-W

During end processing, an event request (event-request-type) from the manager (manager-name) cannot be accepted.

The agent does not accept new event requests from the manager during termination processing.

(S)

Continues processing.

(O)

Restart JP1/AJS3, and then use the jpoagtjobshow command to make sure that the event job is being monitored. Then continue processing.

KAVT0591-E

The specified function cannot be used on the current platform. (event type=event-type)(Platform=platform-name)(host=agent-host-name, maintenance- information)

The event job function indicated in event-type cannot be used on the platform indicated in platform-name.

The following describes the relationship between event-type and the unit type of an event job.

event-type: unit-type

JP1/AJS2_EVACT_NTLOG_WATCH: Windows event log monitoring job

(S)

Changes the status of the event job to Failed to start.

(O)

If the event type is JP1/AJS2_EVACT_NTLOG_WATCH:

Confirm that the function specified for the event job can be used on the platform indicated in platform-name.

For details, see 7.6.5 Notes on the Monitoring Event Log job in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

KAVT0593-W

The MS message queue monitoring function is unusable. (maintenance- information, process name=process-name, maintenance-information)

The MSMQ monitoring function is unusable.

(S)

Continues processing in a reduced mode for the functions.

(O)

Refer to the message that describes the cause of the error, and then follow the instructions.

KAVT0600-E

Failed in creation of status file. (maintenance-information)

A work file for managing the status of an agent in the event/action control agent could not be created.

(S)

Terminates the event/action control agent.

(O)

Check the following, and then restart JP1/AJS3:

Check whether system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

KAVT0603-W

Elapsed time since restart-time is used for time-out due to temporary interruption of monitoring.

The restart of the agent machine or other reasons temporarily interrupted monitoring. The elapsed time since the monitoring restarted is used for time-out.

(S)

Continues processing.

(O)

Check the time the monitoring restarted, and continue operation.

KAVT0606-W

Sending to the manager failed so the event job status will be re-reported. (Manager=manager-name) (maintenance-information, IPAddress=IP-address#)

The agent attempted to report the status of an event job to the manager, but could not communicate with the manager indicated in manager-name due to a temporary communication error.

#

The IP address is output only when the LOGIPV6INFOALL environment setting parameter is set to yes. If the LOGIPV6INFOALL environment setting parameter is set to yes and the IP address is unknown, unknown is displayed.

(S)

Retries communication after the predefined period of time.

For details on this time, see Table 2-3 in 2.2.2(4) Notes on manager/agent system configurations in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

(O)

This message is output when the manager is loaded. Ignore the message and continue the operation because the data that could not be sent will be resent to the manager automatically after a predefined period of time. If this error message is output repeatedly, however, check whether the manager host and JP1/AJS3 have started.

KAVT0607-W

The socket could not be opened so the event job status will be re-reported. (Manager=manager-name) (maintenance-information)

The agent attempted to report the status of an event job to the manager, but could not communicate with the manager indicated in manager-name due to a temporary communication error.

(S)

Retries communication after the predefined period of time.

For details on this time, see Table 2-3 in 2.2.2(4) Notes on manager/agent system configurations in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

(O)

This message appears when the agent cannot resolve the manager name. Ignore the message and continue the operation because the data that caused the communication error will be resent to the manager automatically after a predefined period of time. If this error message is output repeatedly, however, check whether:

A network error does not occur.

The manager machine has stopped.

The manager host name has been resolved. If it has not, check the settings of the JP1_HOSTNAME environment variable, the hosts file, or the DNS server.

KAVT0608-W

The socket accept failed. (code=return-code) (maintenance-information)

The socket could not receive data.

(S)

Continues processing.

(O)

The job may remain in the queue or in the execution status while the event is established. Check the job execution status.

KAVT0609-W

The socket receiving failed. (IP Address=IP-address host=host-name)

The connection is severed while the socket is receiving data.

(S)

Continues processing.

(O)

The job may remain in the queue or in the execution status while the event is established. Check the job execution status of host-name.

KAVT0610-W

The socket receive error occurred. (IP Address=IP-address host=host-name) (maintenance-information)

An error occurred while the socket is receiving data.

(S)

Continues processing.

(O)

The job may remain in the queue or in the execution status while the event is established. Check the job execution status of host-name.

KAVT0611-W

The socket close error occurred. (IP Address=IP-address host=host-name) (maintenance-information)

An error occurred while the socket is terminating the reception of data.

(S)

Continues processing.

(O)

The job may remain in the queue or in the execution status while the event is established. Check the job execution status of host-name.

KAVT0612-W

Sending to the manager confirm failed so the event job status will be re-reported. (Manager=manager-name) (maintenance-information, IPAddress=IP-address#)

The agent reported the status of an event job to the manager, but could not confirm the arrival of data from the manager indicated in manager-name due to a temporary communication error.

#

The IP address is output only when the LOGIPV6INFOALL environment setting parameter is set to yes. If the LOGIPV6INFOALL environment setting parameter is set to yes and the IP address is unknown, unknown is displayed.

(S)

Retries communication after the predefined period of time.

For details on this time, see Table 2-3 in 2.2.2(4) Notes on manager/agent system configurations in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

(O)

This message might appear when the communication status between the manager and the agent is unstable. Ignore the message and continue the operation because the data that could not be sent will be resent to the manager automatically after a predefined period of time.

If this message appears frequently, check whether:

A network failure has occurred.

JP1/AJS3 on the manager host is running.

A heavy load is placed on the manager.

KAVT0613-W

Sending to the manager confirm failed so the event job status will be re-reported. (Manager=manager-name) (maintenance-information, IPAddress=IP-address#)

The agent reported the status of an event job to the manager, but could not confirm the arrival of data from the manager indicated in manager-name due to a temporary communication error.

#

The IP address is output only when the LOGIPV6INFOALL environment setting parameter is set to yes. If the LOGIPV6INFOALL environment setting parameter is set to yes and the IP address is unknown, unknown is displayed.

(S)

Retries communication after the predefined period of time.

For details on this time, see Table 2-3 in 2.2.2(4) Notes on manager/agent system configurations in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

(O)

This message might appear when the communication status between the manager and the agent is unstable. Ignore the message and continue the operation because the data that could not be sent will be resent to the manager automatically after a predefined period of time.

If this message appears frequently, check whether:

A network failure has occurred.

JP1/AJS3 on the manager host is running.

A heavy load is placed on the manager.

KAVT0615-W

Unreported information resend max over. Unreported information will be abandoned. (Manager=manager-name)

The agent retried communicating with the manager for the predefined period of time, but could not send the status of the event job.

For details on this time, see Table 2-3 in 2.2.2(4) Notes on manager/agent system configurations in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

(S)

Continues processing without reporting the event job status.

(O)

This message appears when the manager machine has not started or when a communication error occurred. Check whether the manager host and JP1/AJS3 have started.

KAVT0616-E

A subagent-message-reception pipe could not be opened. (code=maintenance-code)

An attempt to create a pipe file used in the event/action control subagent has failed.

(S)

Terminates the event/action control subagent.

(O)

Check the following, and then restart JP1/AJS3:

Check whether system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT0618-E

The end request for the subagent pipe could not be written. (code=maintenance-code)

An attempt to write to a pipe file used in the event/action control subagent has failed.

(S)

Terminates the event/action control subagent.

(O)

The jpoagtsub process may still remain in the system.

In UNIX, use the ps command to check whether the process remains in the system. If the process remains, use the kill command to terminate it.

In Windows, restart the system.

Check the following, and then restart JP1/AJS3:

Check whether system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT0620-E

The subagent pipe could not be written to. (code=maintenance-code)

An attempt to write to a pipe file used in the event/action control subagent has failed.

(S)

Continues processing without changing the status of the unit (a jobnet with start conditions or an event job). If the jpoagtsub process is not running, the system terminates the event/action control subagent.

(O)

Check the following, making sure that the status of the unit (a jobnet with start conditions or an event job) has not changed, and then retry:

Check whether system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

Use a command such as a ps command to check whether the jpoagtsub process is running. If it is not running, restart JP1/AJS3.

KAVT0621-E

Waiting for a subagent pipe connection from the monitoring process failed. (code=maintenance-code)

The information could not be obtained from the event/action control subagent.

(S)

Terminates the event/action control agent.

(O)

Check the following, and then restart JP1/AJS3:

Check whether the system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted unintentionally.

Check whether any other program has forcibly terminated the jpoagtsub process illegally.

KAVT0625-E

A subagent-message-reception pipe could not be read. (code=maintenance-code)

The information could not be obtained from the event/action control subagent.

(S)

Terminates the event/action control agent.

(O)

Check the following, and then restart JP1/AJS3:

Check whether system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

Check whether any other program has forcibly terminated the jpoagtsub process illegally.

KAVT0628-E

The subagent function is unusable. (maintenance-information)

An attempt to start the event/action control subagent has failed.

(S)

Terminates the event/action control agent.

(O)

Check the following, and then restart JP1/AJS3:

Check whether system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT0629-E

An agent-message-reception pipe could not be opened. (code=maintenance-code)

An attempt to create a pipe file used in the event/action control agent has failed.

(S)

Terminates the event/action control agent.

(O)

Check the following, and then restart JP1/AJS3:

Check whether system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT0632-E

The agent pipe could not be written to. (code=maintenance-code) (host= manager-host-name, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

The pipe file of the event/action control agent could not be written.

(S)

Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)

Check the following, and then use the ajsname command with the -I option to identify the unit name from the unit ID. Make sure that the status of the identified unit (a jobnet with start conditions or an event job) has not changed, and then retry the operation:

Check whether system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT0633-E

Waiting for an agent pipe connection from the monitoring process failed. (code=maintenance-code)

The information could not be obtained from the event/action control agent.

(S)

Terminates the event/action control subagent.

(O)

Check the following, and then restart JP1/AJS3:

Check whether the system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted unintentionally.

Check whether any other program has forcibly terminated the jpoagent process illegally.

KAVT0635-E

The agent-message-sending pipe could not be connected. (code=maintenance-code)

Reporting to the event/action control agent was impossible.

(S)

Terminates the event/action control subagent.

(O)

Check the following, and then restart JP1/AJS3:

Check whether system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT0637-E

An agent-message-reception pipe could not be read. (code=maintenance-code) (host=manager-host-name, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

The information could not be obtained from the event/action control agent.

(S)

Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)

Check the following, and then use the ajsname command with the -I option to identify the unit name from the unit ID. Make sure that the status of the identified unit (a jobnet with start conditions or an event job) has not changed, and then retry the operation:

Check whether system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT0641-W

An attempt to wait for connection from a host (IP-address) failed. (maintenance-information)

Connection from the host could not be placed in the wait state.

(S)

Continues processing.

(O)

Check jp1hosts or jp1hosts2 to confirm that the definition of the host indicated in IP-address is correct. The jpomgrsub and jpoagent processes may still remain in the system. In UNIX, use the ps command to check whether the processes remain in the system. If the processes remain, use the kill command to terminate them. In Windows, restart the system.

KAVT0642-E

The process will now stop because Event Action Agent finished.

The event/action control agent will stop because the event/action control subagent terminated.

(S)

Terminates the event/action control agent.

(O)

Confirm that the directory for output of the wait information file can be accessed, and then restart JP1/AJS3.

If the KAVT0643-E message was also output at the same time this message was output, the probable cause is that the directory for output of the wait information file cannot be accessed. Confirm that the directory for output of the wait information file can be accessed. If there are any problems, correct them.

Especially, if this message appears during failover, allocation of the shared disk might have been canceled before JP1/AJS3 stopped. Review and, if necessary, correct the cluster software settings so that allocation of the shared disk is canceled after JP1/AJS3 and JP1/Base stops.

For details about the prerequisites for using the cluster system, see 10.1.1(1) Prerequisites for a logical host environment in the JP1/Automatic Job Management System 3 Administration Guide.

KAVT0643-E

The process will now stop because Event Action Subagent finished.

The event/action control subagent will stop because the event/action control agent terminated.

(S)

Terminates the event/action control subagent.

(O)

Confirm that the directory for output of the wait information file can be accessed, and then restart JP1/AJS3.

If the KAVT0642-E message was also output at the same time this message was output, the probable cause is that the directory for output of the wait information file cannot be accessed. Confirm that the directory for output of the wait information file can be accessed. If there are any problems, correct them.

Especially, if this message appears during failover, allocation of the shared disk might have been canceled before JP1/AJS3 stopped. Review and, if necessary, correct the cluster software settings so that allocation of the shared disk is canceled after JP1/AJS3 and JP1/Base stops.

For details about the prerequisites for using the cluster system, see 10.1.1(1) Prerequisites for a logical host environment in the JP1/Automatic Job Management System 3 Administration Guide.

KAVT0649-E

A host name in the FQDN format could not be obtained. Processing is canceled. (code=maintenance-code) (host=host-name, maintenance-information)

The system could not obtain a host name in the FQDN format.

(S)

Terminates processing.

(O)

Check whether the DNS has been set up correctly.

KAVT0650-W

Port information about the event action function cannot be read, so the default port number is used. (port number=default-port-number, code=maintenance-code)

The system terminates processing because information about the port number for the event/action control cannot be read.

(S)

Terminates processing.

(O)

Check whether the port number for the event/action control is set in the services file, and then restart JP1/AJS3.

For details about port numbers, see A.1 Tables of port numbers in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVT0651-E

Port information about the event action function cannot be read. (port=service-name, code=maintenance-code)

The system cannot read information about the port number for the event/action control, so the system terminates processing.

(S)

Terminates processing.

(O)

Check whether the port number for the event/action control is set in the services file, and then restart JP1/AJS3.

For details about port numbers, see A.1 Tables of port numbers in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVT0654-E

The files will be deleted, because the internal files of event action control have been destroyed. (maintenance-information)

The files will be deleted because the internal files used for event action control have been corrupted.

If this message appears, the following phenomena may have occurred:

Information about the events that occurred before JP1/AJS3 stopped was lost.

Monitoring was not resumed for the jobnets with start conditions and event jobs that were running before JP1/AJS3 stopped.

(S)

Continues processing.

(O)

To resume monitoring on the agent, restart JP1/AJS3 on the manager host. Then check the status of the jobnet with start conditions or the event job, and then re-register the job for execution.

KAVT0656-W

Event Action Agent will stop resending the startup notification.(Manager=manager-host-name)(maintenance-information)

Resending is canceled because the number of times a startup notification was resent to the manager host exceeded the upper limit.

(S)

Continues processing without changing the status of a jobnet with start conditions or an event job executed from the manager host.

(O)

Check whether JP1/AJS3 on the manager host is running.

If JP1/AJS3 on the manager host is not running:

Start JP1/AJS3 on the manager host.

If JP1/AJS3 on the manager host is running:

Check the following:

Check whether there are problems with the network environment.

Use some method such as the ping command to check whether the manager host can communicate with the agent host via TCP/IP. If there are communication problems, correct them.

Check whether the manager host name# can be resolved on the agent host.

If the name cannot be resolved, revise the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the agent host or in the DNS settings so that the manager host name can be resolved.

#

For a physical host:

For DNS operation, the host name in the FQDN format. For other cases, the host name obtained by executing the hostname command

For a logical host:

In Windows:

The host name indicated in xxxxx in JP1/AJS3_xxxxx in the Services window that is displayed by choosing Services or by choosing Administrative Tools and then Services in the Control Panel window on the agent host

In UNIX:

The host name indicated after the jajs_spmd process that is displayed by executing the ps command

If a startup notification is successfully sent to the manager host, the system continues monitoring on the agent host. If an attempt to send a startup notification fails, monitoring on the agent host stops, and events to be monitored are not detected. Therefore, after confirming that JP1/AJS3 on the manager host is running, perform the following operations:

Check the jobnet with start conditions or the event job executed from the manager host.

Use the ajschgstat command, or the Change Job Status dialog box, or forced termination to change the status of the jobnet or job to the end status. Then, if necessary, re- register the job or jobnet for execution.

If the manager host name indicated in the message is no longer required, stop the JP1/AJS3 service, and then execute the jpoagoec command to delete the manager host name.

For details about jpoagoec command, see jpoagoec in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVT0657-I

Event Action Agent successfully resent the startup notification. (Manager=manager-host-name)(maintenance-information)

A startup notification was successfully sent to the manager host.

(S)

Continues processing.

KAVT0658-E

Shared memory is not available. (maintenance-information)

Shared memory, which is one of the system resources, cannot be obtained, or required shared memory does not exist.

(S)

Terminates the process where the error occurred.

(O)

Review the shared memory settings specified with the kernel parameters, and then restart JP1/AJS3 service. For details about the kernel parameters, see Release Notes.

If the message still appears after you restart the JP1/AJS3 service, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT0659-E

Memory became insufficient during the registration of Manager data. (host=manager-host-name, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

The size of shared memory required for handling manager information is insufficient.

(S)

Terminates the process if the error occurred during startup of the event/action control agent process.

If the error occurred after the process started, the system continues processing without changing the status of the relevant event job or the jobnet with start conditions.

(O)

If the error occurred during startup of the event/action control agent process, use the jpoagoec command to check the registered manager host names, and then delete unnecessary manager host names. Then, restart the JP1/AJS3 service.

If the error occurred after the process started, perform the following operations:

Use the ajsname command with the -I option specified to identify the unit name from the unit ID.

Change the status of the job to the end status.

- For a jobnet with start conditions, forcibly terminate it.

- For an event job, terminate it forcibly or change the job status.

Stop the JP1/AJS3 services.

Use the jpoagoec command to check the registered manager host names, and then delete unnecessary manager host names.

Restart the JP1/AJS3 services, and then re-execute the job or jobnet you terminated.

For details about jpoagoec command, see jpoagoec in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVT0660-E

The Manager information cannot be obtained because the information in shared memory is incorrect. (maintenance-information)

Manager information cannot be obtained because the information stored in the shared memory is invalid.

(S)

Terminates the process if an error occurred during startup of the event/action control subagent process.

If an error occurred after the process started, the system continues processing.

(O)

Another program might have changed data in shared memory. Restart the JP1/AJS3 service. After the JP1/AJS3 service restarts, re-execute any jobs that terminated abnormally due to the restart of the JP1/AJS3 service.

KAVT0661-E

An exclusion error occurred during an access to shared memory. (maintenance-information)

Shared memory cannot be accessed because an error related to locking between processes occurred.

(S)

Terminates the process if the error occurred during startup of the event/action control agent process or event/action control subagent process.

If the error occurred after the process started, the system continues processing.

(O)

Check the following:

Check whether system resources are sufficient.

Check the system file directory is accessible.

Take action according to the error information in the Windows event log or syslog output by the OS, and other OS-specific error information (if any).

If you cannot take corrective action, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVT0662-I

The number of Event Action Managers connected to the Event Action Agent exceeds the limit.

The number of event/action control managers connected to the event/action control agent exceeds the limit.

(S)

Continues processing.

(O)

Execute the jpoagoec command to check for unnecessary registered manager host names. If there are any unnecessary manager host names, stop the JP1/AJS3 service and then delete them.

For details about the jpoagoec command, see jpoagoec in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

For details about limit values, see B. List of Limits in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVT0663-W

The number of Event Action Managers connected to the Event Action Agent exceeds the limit.

The number of event/action control managers connected to the event/action control agent exceeds the limit.

(S)

Continues processing.

(O)

Execute the jpoagoec command to check for unnecessary registered manager host names. If there are any unnecessary manager host names, stop the JP1/AJS3 service and then delete them.

For details about the jpoagoec command, see jpoagoec in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

For details about limit values, see B. List of Limits in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVT0664-E

Creation of an Event Action Agent system file failed. (maintenance-information)

An attempt to create a system file for use in the event/action control agent failed.

(S)

Terminates the event/action control agent.

(O)

Check the following, and then restart the JP1/AJS3 service:

Check whether system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT0666-W

Event Action Agent failed to send a startup notification to the manager. (Manager=manager-host-name)(maintenance-information)

An attempt to send a startup notification to the manager host failed.

(S)

Continues processing without changing the status of a jobnet with start conditions or an event job executed from the manager host.

If the RetryAgtStartNotification environment setting parameter is set to Y, the system resends a startup notification to the manager after a predefined period of time.

(O)

Check whether JP1/AJS3 on the manager host is running.

If JP1/AJS3 on the manager host is not running:

Start JP1/AJS3 on the manager host.

If JP1/AJS3 on the manager host is running:

Check the following:

Check whether there are problems with the network environment.

Use some method such as the ping command to check whether the manager host can communicate with the agent host via TCP/IP. If there are communication problems, correct them.

Check whether the manager host name# can be resolved on the agent host.

If the name cannot be resolved, revise the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the agent host or in the DNS settings so that the manager host name can be resolved.

#

For a physical host:

For DNS operation, the host name in the FQDN format. For other cases, the host name obtained by executing the hostname command

For a logical host:

In Windows:

The host name indicated in xxxxx in JP1/AJS3_xxxxx in the Services window that is displayed by choosing Services or by choosing Administrative Tools and then Services in the Control Panel window on the agent host

In UNIX:

The host name indicated after the jajs_spmd process that is displayed by executing the ps command

If a startup notification is successfully sent to the manager host, the system continues monitoring on the agent host. If an attempt to send a startup notification fails, monitoring on the agent host stops, and events to be monitored are not detected. Therefore, after confirming that JP1/AJS3 on the manager host is running, perform the following operations:

Check the jobnet with start conditions or the event job executed from the manager host.

Use the ajschgstat command, or the Change Job Status dialog box, or forced termination to change the status of the jobnet or job to the end status. Then, if necessary, re- register the job or jobnet for execution.

If the RetryAgtStartNotification environment setting parameter is set to Y, startup notifications are resent until the KAVT0656-W or KAVT0657-I message is output.

If the KAVT0657-I message was output after this message, monitoring on the agent host was suspended until the KAVT0657-I message was output, and events to be monitored were not detected. Therefore, check whether events that need to be detected occurred in the period from after this message was output until the KAVT0657-I message was output.

If the KAV0656-W message was output, follow the instructions given in the message.

If the manager host name indicated in the message is no longer required, stop the JP1/AJS3 service, and then execute the jpoagoec command to delete the manager host name.

For details about jpoagoec command, see jpoagoec in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVT0667-W

Event Action Agent failed to send a stop notification to the manager. (Manager=manager-host-name)(maintenance-information)

An attempt to send a stop notification to the manager host failed.

(S)

Continues processing.

(O)

Check whether JP1/AJS3 on the manager host is running.

If JP1/AJS3 on the manager host is not running:

Start JP1/AJS3 on the manager host.

If JP1/AJS3 on the manager host is running:

Check the following:

Check whether there are problems with the network environment.

Use some method such as the ping command to check whether the manager host can communicate with the agent host via TCP/IP. If there are communication problems, correct them.

Check whether the manager host name# can be resolved on the agent host.

If the name cannot be resolved, revise the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the agent host or in the DNS settings so that the manager host name can be resolved.

#

For a physical host:

For DNS operation, the host name in the FQDN format. For other cases, the host name obtained by executing the hostname command

For a logical host:

In Windows:

The host name indicated in xxxxx in JP1/AJS3_xxxxx in the Services window that is displayed by choosing Services or by choosing Administrative Tools and then Services in the Control Panel window on the agent host

In UNIX:

The host name indicated after the jajs_spmd process that is displayed by executing the ps command

If a stop notification is successfully sent to the manager host, the status of the event job changes to Ended abnormally#. If an attempt to send a stop notification fails, the status remains Now running. Therefore, after confirming that JP1/AJS3 on the manager host is running, check the event job executed from the manager host. Then, after the agent host starts, if necessary, use the ajschgstat command or the Change Job Status dialog box (or forced termination) to change the status of the event job to the end status. If necessary, re-register the job for execution.

#

The status changes to Ended abnormally only when the EvJobExecContinue environment setting parameter is set to N for the manager host name. If Y is set, the status remains Now running.

If the manager host name indicated in the message is no longer required, stop the JP1/AJS3 service, and then execute the jpoagoec command to delete the manager host name.

For details about jpoagoec command, see jpoagoec in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVT0900-I

JP1/AJS2 event action agent will now start.

The event/action control agent will now start.

(S)

Continues processing.

KAVT0901-I

JP1/AJS2 event action agent will now end.

The event/action control agent will now terminate.

(S)

Continues processing.

KAVT0910-E

Invalid specification in configuration definition. (item-name : maintenance-information)

The configuration definition contains an invalid specification.

(S)

Assumes the default and continues processing.

(O)

Correctly specify the value indicated by item-name. The output item names are described in 20. Environment Setting Parameters in the JP1/Automatic Job Management System 3 Configuration Guide.

KAVT0911-E

An attempt to read the configuration definition failed. (item-name : maintenance-information)

An attempt to read the configuration definition has failed.

(S)

Assumes the default and continues processing.

(O)

If the system assumes an unexpected value, correct the cause of the error and then reissue the request. 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, recheck the memory estimate. If other unnecessary applications are running, stop them. If the cause of the error is not insufficient memory, collect the internal trace log and then contact the system administrator.

KAVT0912-E

Event Action 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 Windows:

The signal number is 0.

In UNIX:

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 the event/action control if the process indicated in process-name is either of the following:

jpomgrsub

jpoagtsub

If one of the following processes is indicated in process-name, the system operates at a reduced level while the function of the process is disabled:

jpoeventwatch: Receive JP1 Event job, Monitoring Log Files job, or Monitoring Event Log job

jpocwtflMain: Monitoring Files job

jpocwtmlmain: Email Reception Monitoring job

jpocwtmqmain: Receive MQ Message job

jpocwttmMain: Interval Control job or an event job with a timeout specified

jpocwtmsmain: Receive MSMQ Message job

- Operations based on the specification of the detail process termination option

When N is specified for the EVProcessHA environment setting parameter to disable the detail process termination option, if a job related to a detail process that terminated abnormally is registered for execution, the job terminates abnormally.

For example, the file monitoring job that is executed when the jpocwtflMain process has terminated abnormally terminates abnormally.

If you use a cluster system or enable the detail process termination option by specifying Y for the EVProcessHA environment setting parameter or using the default, the system terminates the event/action control if an error occurs. At this time, operation does not continue at a reduced level irrespective of the process indicated in process-name.

For details about the detail process termination option, see 20.6 Setting up the event/action control environment in the JP1/Automatic Job Management System 3 Configuration Guide.

(O)

Examine the cause of the error from the system error message that was output before or after the message, and then take action. 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).

To continue processing, collect data and then restart JP1/AJS3.

There is no problem if this message appears when you execute jajs_killall.cluster command.

KAVT0950-I

The JP1/AJS2 monitor resource went online.

The monitored resource was placed online.

(S)

Continues processing.

KAVT0951-I

The JP1/AJS2 monitor resource went offline.

The monitored resource was placed offline.

(S)

Continues processing.

KAVT0952-I

OpenView Environment (maintenance-information) Setup skipped.

Setup of HP NNM Link was skipped.

(S)

Continues processing.

KAVT0953-I

OpenView Environment of JP1/AJS2 was installed normally.

HP NNM Link was installed normally.

(S)

Continues processing.

KAVT0954-I

OpenView Environment of JP1/AJS2 was uninstalled normally.

HP NNM Link was uninstalled normally.

(S)

Continues processing.

KAVT0955-I

Symbol of JP1/AJS2 was deleted normally.

The symbol was deleted normally.

(S)

Continues processing.

(O)

Acquire a new certificate, and replace the expired certificate with it.

KAVT0958-I

Resource monitoring will now start.

Resource monitoring starts.

(S)

Continues processing.

KAVT0959-I

Resource not found.

The resource is not found.

(S)

Continues processing.

KAVT0960-I

Resource status to be offline.

The resource is placed offline.

(S)

Continues processing.

KAVT0961-I

Resource status to be online.

The resource is placed online.

(S)

Continues processing.

KAVT0962-I

Resource monitoring bring to a termination.

Resource monitoring terminated.

(S)

Terminates processing.

KAVT0963-I

Resource monitoring will now end.

Resource monitoring terminates.

(S)

Terminates processing.

KAVT0980-W

Unreported information will now be deleted, because the amount of unreported information for manager-host-name has exceeded threshold.(host=agent-host-name, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID maintenance-information)

Unreported information will now be deleted because the amount of unreported information for manager-host-name has exceeded the threshold.

(S)

Continues processing.

(O)

This message appears when the remaining unprocessed data that could not be reported to the manager is deleted when the amount of data exceeds the threshold, so that resources such as memory and disk space remain available.

For the manager host and agent host indicated in the message, check whether JP1/AJS3 on the manager host is running. If it is not running, start it. If JP1/AJS3 on the manager host is running, check the following:

- Check whether many events being monitored by the jobnet with start conditions have occurred

Check the definition of an event job or a jobnet with start conditions for which the agent is defined as the target host. If the definition will cause a mass of events to be generated at the same time, review the operation and reduce the number of events to be generated. You can obtain the name of the jobnet with start conditions in the following procedure:

Check the scheduler service name and unit ID indicated in AJSServiceName=scheduler-service-name, UnitID=unit-ID in the message.

On the manager host, execute the ajsname command with the scheduler service name and unit ID you obtained in step 1 specified.

Example:

ajsname -F scheduler-service-name -I unit-ID

/name-of-the-jobnet with start conditions/.CONDITION/JP1 event reception monitoring

- Check whether the manager host and the agent host can communicate with each other

Check the following:

Check whether the agent host name# can be resolved on the manager host.

If the name cannot be resolved, review the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the agent host name can be resolved.

Check whether the manager host name# can be resolved on the agent host.

If the name cannot be resolved, review the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the agent host or in the DNS settings so that the manager host name can be resolved.

Check whether the IP address of the agent host obtained by resolving the agent host name on the manager host is the same as the actual IP address of the agent host.

If the IP addresses are different, review the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the correct IP address can be obtained by resolving the name.

Check whether the IP address of the manager host obtained by resolving the manager host name on the agent host is the same as the actual IP address of the manager host.

If the IP addresses are different, review the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the agent host or in the DNS settings so that the correct IP address can be obtained by resolving the name.

Check for any problems with the network environment.

Use the ping command or another means to check whether the manager host can communicate with the agent host via TCP/IP. If there are any problems, correct them. Also check the agent host the same way and correct problems, if any.

#

For a physical host:

For DNS operation, the host name in the FQDN format. For other cases, the host name obtained by executing the hostname command

For a logical host:

In Windows

The host name indicated in xxxxx in JP1/AJS3_xxxxx in the Services window that is displayed by choosing Services or by choosing Administrative Tools and then Services in the Control Panel window on the agent host

In UNIX

The host name indicated after the jajs_spmd process that is displayed by executing the ps command

Also check the following and take action if necessary:

If an event job is registered for execution but the job status does not change from Now queuing to Now running, check the items described in (O), forcibly terminate the job, and then retry the operation.

If a jobnet with start conditions or an event job is forcibly terminated but the job status remains Now running, check the items described in (O), and then forcibly terminate the job or jobnet again.

Check whether an event that must be detected has occurred within a certain period of time after this message was output.

For details on this time, see Table 2-3 in 2.2.2(4) Notes on manager/agent system configurations in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

If such an event occurred, check the items described in (O), re-execute the event job if necessary, and then re-generate the events to be monitored.

KAVT0981-W

Reply queue information is discarded because there is no reply for a certain period of time to the information reported to manager-host-name. (host=agent-host-name, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID maintenance-information)

Reply queue information is discarded because there is no reply to the information reported to manager-host-name within 24 hours.

(S)

Continues processing.

(O)

This message appears when reply queue information is deleted because no response is sent within 24 hours since the data was reported to the manager, so that resources such as memory and disk space remain available.

For the manager host and agent host indicated in the message, check whether JP1/AJS3 on the manager host is running. If it is not running, start it. If JP1/AJS3 on the manager host is running, check the following:

- Check whether many events being monitored by the jobnet with start conditions have occurred

Check the definition of an event job or a jobnet with start conditions for which the agent is defined as the target host. If the definition will cause a mass of events to be generated at the same time, review the operation and reduce the number of events to be generated. You can obtain the name of the jobnet with start conditions in the following procedure:

Check the scheduler service name and unit ID indicated in AjsServiceName=scheduler-service-name, UnitID=unit-ID in the message.

On the manager host, execute the ajsname command with the scheduler service name and unit ID you obtained in step 1 specified.

Example:

ajsname -F scheduler-service-name -I unit-ID

/name-of-the-jobnet with start conditions/.CONDITION/JP1 event reception monitoring

- Check whether the manager host and the agent host can communicate with each other

Check the following:

Check whether the agent host name# can be resolved on the manager host.

If the name cannot be resolved, review the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the agent host name can be resolved.

Check whether the manager host name# can be resolved on the agent host.

If the name cannot be resolved, review the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the agent host or in the DNS settings so that the manager host name can be resolved.

Check whether the IP address of the agent host obtained by resolving the agent host name on the manager host is the same as the actual IP address of the agent host.

If the IP addresses are different, review the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the correct IP address can be obtained by resolving the name.

Check whether the IP address of the manager host obtained by resolving the manager host name on the agent host is the same as the actual IP address of the manager host.

If the IP addresses are different, review the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the agent host or in the DNS settings so that the correct IP address can be obtained by resolving the name.

Check for any problems with the network environment.

Use the ping command or another means to check whether the manager host can communicate with the agent host via TCP/IP. If there are any problems, correct them. Also check the agent host the same way and correct problems, if any.

#

For a physical host:

For DNS operation, the host name in the FQDN format. For other cases, the host name obtained by executing the hostname command

For a logical host:

In Windows

The host name indicated in xxxxx in JP1/AJS3_xxxxx in the Services window that is displayed by choosing Services or by choosing Administrative Tools and then Services in the Control Panel window on the agent host

In UNIX

The host name indicated after the jajs_spmd process that is displayed by executing the ps command

KAVT0992-E

The request sent from the host(connection-source-IP-address) was ignored. (reason, host-name)

A request from the host (connection-source-IP-address) was ignored. The probable causes are as follows:

If reason is Restricted:

The IP address indicated in connection-source-IP-address was not registered in the agent connection permission configuration file on the host where this message was output.

If 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 connection source IP address was not obtained, null characters are output for connection-source-IP-address.

(S)

Ignores the request and continues processing.

(O)

- If reason is Restricted:

If the request from the IP address indicated in connection-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 where this message was output.

Execute the jajs_pmtcon command to apply the change to the connection permission configuration file.

If necessary, perform the request processing again.

- If reason is Error:

Follow the instructions given by the KAVS8033-E message that was output immediately before this message.

KAVT0993-E

An attempt to verify the server certificate failed.(logical-host-name, name-of-host-to-be-connected, maintenance-information)

An attempt to verify the server certificate sent from the connection destination failed. The probable causes are as follows:

The connection destination host name does not match the CN or SAN.

The root certificate corresponding to the server certificate is not contained in the file specified for CACERTIFICATEFILE in the JP1/Base common definition information.

The current time of the machine in which the error occurred is earlier than the start time of the effective period specified in the server certificate.

The server certificate and the intermediate certificate are joined in an incorrect order.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Cancels communication processing, and then continues subsequent processing.

(O)

If the connection destination host name does not match the CN or SAN:

Match the connection destination host name to the CN or SAN.

If the root certificate corresponding to the server certificate is not contained in the file specified for CACERTIFICATEFILE in the JP1/Base common definition information:

Add the corresponding root certificate to the file specified for CACERTIFICATEFILE in the common definition information.

If the current time of the machine in which the error occurred is earlier than the start time of the effective period specified in the server certificate:

Retry the operation after the start time of the effective period specified in the server certificate.

If the server certificate and the intermediate certificate are joined in an incorrect order:

Join the server certificate and the intermediate certificate in the correct order.

KAVT0994-E

An error occurred in SSL communication processing.(logical-host-name, name-of-host-to-be-connected, maintenance-information)

An error occurred during SSL communication processing. The probable causes are as follows:

The communication encryption function is disabled at the connection destination.

A temporary communication error occurred.

If this message is output at the reception side of TCP/IP communication, a null character string is output for connection-destination-host-name.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Cancels communication processing, and then continues subsequent processing.

(O)

If the communication encryption function is disabled at the connection destination:

Enable the communication encryption function for the host indicated in connection-destination-host-name.

If a temporary communication error occurred:

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

KAVT0995-W

The certificate has expired.(logical-host-name, name-of-host-to-be-connected)

The server certificate sent from the connection destination or the root certificate located on the local host has expired.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Continues processing.

(O)

Acquire a new certificate, and replace the expired certificate with it.

KAVT1001-I

The event-receiving process will now end.

The event (such as a JP1 event and log trap) monitoring process will now terminate.

(S)

Terminates the event (such as a JP1 event and log trap) monitoring process.

KAVT1002-I

The event-receiving process will now start

The event (such as a JP1 event and log trap) monitoring process will now start.

(S)

Continues processing.

KAVT1003-E

Failed to get logical host. (maintenance-information) (maintenance-information)

Information required for operating an event (such as a JP1 event and log trap) monitoring process could not be acquired.

(S)

Terminates the event (such as a JP1 event and log trap) monitoring process. A Receive JP1 Event job, a Monitoring Log Files job, or a Monitoring Event Log job cannot be monitored.

(O)

Use the jbsgetcnf command to check whether you can acquire common definition information for the logical host that caused the error. If you cannot acquire the common definition information, re-install JP1/Base. If you can collect it, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT1004-I

The event sever was connected. (event-server-name)

The JP1/Base event service was connected.

(S)

Continues processing.

KAVT1005-W

Connection to the event server is not possible now. (event-server-name)

Connection to the JP1/Base event service was released.

(S)

Retries connection to the JP1/Base event service. A Receive JP1 Event job, a Monitoring Log Files job, or a Monitoring Event Log job cannot be monitored until the JP1/Base event service can be connected again.

(O)

Check whether the JP1/Base event service has started.

KAVT1006-I

Connecting the event server will be retried. (event-server-name)

The system will retry the connection to the JP1/Base event service.

(S)

Continues processing.

KAVT1007-W

The event sever is inactive. (event-server-name)

The JP1/Base event service has not yet started.

(S)

Continues processing while retrying the connection because the JP1/Base event service has not started. A Receive JP1 Event job, a Monitoring Log Files job, or a Monitoring Event Log job cannot be monitored until the JP1/Base event service starts.

(O)

Check whether the JP1/Base event service has started.

KAVT1008-E

Initialization error (maintenance-information) (maintenance-information)

Initialization required for acquiring information has failed.

(S)

Continues processing. The system terminates the event (such as JP1 event and log trap) monitoring process depending on the location where the error occurred. A Receive JP1 Event job, a Monitoring Log Files job, or a Monitoring Event Log job cannot be monitored.

(O)

Check whether the JP1/Base event service can start. If the JP1/Base event service can start, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT1013-E

Failed to analyze job data. (maintenance-information) (maintenance-information)

The definitions of a Receive JP1 Event job, a Monitoring Log Files job, or a Monitoring Event Log job contain an error.

(S)

Terminates the job abnormally because the job definitions contain an error.

(O)

Check the version of JP1/AJS3 that executes the job to see whether a definition not supported by that version is specified.

For Windows event log monitoring jobs, the following items are output when the version of JP1/AJS3 is 10-00 or later.

Log type: Any log type

Event type: Verbose or Critical

KAVT1014-E

An error occurred during the creation of an action definition file. (maintenance-information)

Internal processing (file creation) required for starting the Monitoring Log Files job has failed.

(S)

Abnormally terminates the log file monitoring job.

(O)

Check whether the system resources are sufficient, and then re-execute the Monitoring Log Files job. Especially, check the space available on the disk that contains the JP1/AJS3 system folder (directory). If you cannot find any problem, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT1015-E

The log-file trap command could not start. (maintenance-information)

An attempt to start the Monitoring Log Files job has failed.

(S)

Places the log file monitoring job into Ended abnormally status.

(O)

An error message for the JP1/Base log-file trap function has been output to the Execution Result Details dialog box. Take action according to the instructions given by that message. If you specify SEQ2 for the log file output format for the log file monitoring job, check the following according to the OS on the host specified as the target host for the job.

For a UNIX environment

Check whether the version of JP1/Base and JP1/AJS is 07-00 or later.

For a Windows environment

Check whether the JP1/Base version is 08-10 or later, and the JP1/AJS version is 08-00 or later.

KAVT1017-I

Condition is concluded.( maintenance-information)

The received event satisfied the job conditions.

(S)

Continues processing.

KAVT1025-W

No end judgment file exists. (end-judgment-file-name)

The end judgment file specified in the Receive JP1 Event job was not found.

(S)

Ignores information about end judgment and continues processing.

If Normal if message matches or Normal if details match is specified for End judgement, the system terminates the relevant JP1 event reception monitoring job abnormally.

If Abnormal if message matches or Abnormal if details match is specified for End judgement, the system terminates the relevant JP1 event reception monitoring job normally.

(O)

Check whether the specified file exists in the Receive JP1 Event job. End judgment of the job may not have been performed correctly because the end judgment file is missing. Check the Receive JP1 Event job.

KAVT1026-W

The end judgment file includes no data. (end-judgment-file-name)

The end judgment file specified in the Receive JP1 Event job does not contain data.

(S)

Ignores information about end judgment and continues processing.

If Normal if message matches or Normal if details match is specified for End judgement, the system terminates the relevant JP1 event reception monitoring job abnormally.

If Abnormal if message matches or Abnormal if details match is specified for End judgement, the system terminates the relevant JP1 event reception monitoring job normally.

(O)

Check the contents of the file specified in the Receive JP1 Event job. End judgment of the job may not have been performed correctly. Check the Receive JP1 Event job.

KAVT1027-E

An error occurred during processing of an end judgment file. (end-judgment-file-name)

The end judgment file specified in the Receive JP1 Event job cannot be read.

(S)

Assumes that the end judgment information does not exist. Continues processing.

Terminates the Receive JP1 Event job abnormally.

(O)

Check whether the system resources are sufficient, and whether the user who started JP1/AJS3 can view the file specified in the Receive JP1 Event job. End judgment of the job may not have been performed correctly. Check the Receive JP1 Event job.

KAVT1028-E

Memory became insufficient. (maintenance-information)

Memory was insufficient during processing of the event job.

(S)

Continues processing. The system determines the event job to be an error depending on the location where the error occurred.

(O)

See 3. Estimates in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide, and make sure that the required amount of memory for executing JP1/AJS3 has been allocated.

KAVT1029-E

The event could not be created. (maintenance-information) (maintenance-information)

An attempt to connect to the JP1/Base event service has failed.

(S)

Retries until the JP1/Base event service is connected. The JP1 event reception monitoring job, log file monitoring job, and Windows event log monitoring job cannot be monitored during the retries.

(O)

Check whether the JP1/Base event service can start. If the JP1/Base event service can start, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT1030-E

The event server could not be connected. (maintenance-information) (maintenance-information)

An attempt to connect to the JP1/Base event service has failed.

(S)

Retries until the JP1/Base event service is connected. The JP1 event reception monitoring job, log file monitoring job, and Windows event log monitoring job cannot be monitored during the retries.

(O)

Check whether the JP1/Base event service can start. If the JP1/Base event service can start, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT1031-E

Failed to get Pipe Data. (maintenance-information) (maintenance-information)

An attempt to receive a pipe from the agent or the event search process has failed.

(S)

Cancels pipe processing. The system terminates the event (such as JP1 event and log trap) monitoring process depending on the location where the error occurred. Detection of a Receive JP1 Event job, a Monitoring Log Files job, or a Windows event trap job may have failed.

(O)

Check whether the system resources are sufficient, whether the permission environment of the user who started JP1/AJS3 is correct, and whether the directory created during installation of JP1/AJS3 was deleted unintentionally.

KAVT1032-E

Failed to send Pipe Data. (maintenance-information) (maintenance-information)

An error occurred during inter-process communication.

(S)

Interprocess communication failed. The system continues processing. If the error occurred during registration, registration of the event job will be unsuccessful. If the error occurred after registration, the job execution status may be incorrect.

(O)

Check the following, and then retry the event job that caused the error:

Check whether the system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted unintentionally.

KAVT1033-E

An auxiliary file could not be opened. (maintenance-information) (maintenance-information)

An attempt to open a file used in the event (such as JP1 event and log trap) monitoring process has failed.

(S)

Cannot start monitoring of the job.

(O)

Check whether the system resources are sufficient and whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

After the check, re-register the job.

KAVT1037-E

Failed to get Event. (maintenance-information) (maintenance-information)

An attempt to acquire JP1 events has failed. Some JP1 events could not be acquired.

(S)

Retries connection to the JP1/Base event service.

The JP1 event reception monitoring job, log file monitoring job, and Windows event log monitoring job cannot be monitored until a KAVT1004-I message is output.

(O)

Check whether the JP1/Base event service is running. If the JP1/Base event service has been terminated unintentionally, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVT1040-E

Error occurred in Event function. (maintenance-information) (maintenance-information)

An error occurred during acquisition of JP1 events.

(S)

Retries connection to the JP1/Base event service.

The JP1 event reception monitoring job, log file monitoring job, and Windows event log monitoring job cannot be monitored until a KAVT1004-I message is output.

(O)

See the description of the API settings file (api) in the JP1/Base User's Guide, and check whether the api file is set correctly.

Also check whether the JP1/Base event service is running. If the JP1/Base event service has been terminated unintentionally, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVT1041-W

A macro variable exceeds 4096 bytes.

An event that meets the specified monitoring condition occurred, but the sum of the size of values specified in macro variables exceeded 4,096 bytes.

(S)

Truncates the portion after the 4,096th byte and continues processing. The maximum size of the value for macro variables is 4,096 bytes.

(O)

Redefine the macro variable so that the sum of the size of values specified in the macro variables does not exceed 4,096 bytes. The portion exceeding the 4,096th byte is not passed to the succeeding jobnet or job. Check the status of the succeeding jobnet or job. If you find any problem, recheck the job definition.

KAVT1042-E

Failed to start. maintenance-information maintenance-information

An attempt to initialize the JP1 event monitoring process has failed.

(S)

Terminates the JP1 event monitoring process. A Receive JP1 Event job, a Monitoring Log Files job, or a Monitoring Event Log job cannot be monitored.

(O)

The error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT1045-E

A log-file trap command parameter could not be created. (maintenance-information)

Internal processing required for starting the Monitoring Log Files job has failed.

(S)

Memory was insufficient. The system terminated the Monitoring Log Files job abnormally.

(O)

Check whether the system resources are sufficient, and then re-execute the Monitoring Log Files job.

KAVT1046-E

The event ID is invalid. (maintenance-information)

The event ID defined for the Receive JP1 Event job is invalid.

(S)

Abnormally terminates the Receive JP1 Event job.

(O)

Define the event ID correctly, and then retry.

KAVT1047-W

An error occurred during analysis of macro variables. (maintenance-information) (maintenance-information)

An error occurred while analyzing the macro variable.

(S)

Abnormally terminates the job without creating the macro variable.

(O)

The specification of the macro variable may be incorrect. Recheck the definition and re-execute the job.

KAVT1048-W

The parameter (parameter) is not specified.

The required event monitoring condition is not specified in the Monitoring Log Files job.

(S)

Abnormally terminates the Monitoring Log Files job.

(O)

Specify the required monitoring condition.

KAVT1050-E

Event receiving process ended. (maintenance-information) (maintenance-information)

The JP1 event monitoring process detected an error and terminated.

(S)

Terminated the JP1 event monitoring process because an error that prevents further processing occurred. A Receive JP1 Event job, a Monitoring Log Files job, or a Monitoring Event Log job cannot be monitored.

(O)

Follow the instructions given by the message that was output immediately before this message, and then restart JP1/AJS3.

KAVT1052-W

The log-file trap daemon (service) ended.

The JP1/Base log-file trap management daemon (UNIX) or log file trap management service (Windows) stopped during execution of the log-file trap monitoring job.

(S)

Continue processing while also retrying to start the JP1/Base log file trap management daemon (UNIX) or log-file trap management service (Windows) until the daemon or service starts.

(O)

Start the JP1/Base log-file trap management daemon (UNIX) or log file trap management service (Windows).

KAVT1055-W

The log-file trap daemon (service) is inactive.

The Monitoring Log Files job has started, but the JP1/Base log-file trap daemon (UNIX) or log-file trap service (Windows) has not started yet. The Monitoring Log Files job remains in the Now running status, and cannot monitor log files.

(S)

Assumes the Monitoring Log Files job to be in the Now running status, and retries until the JP1/Base log-file trap daemon (UNIX) or log-file trap service (Windows) starts.

(O)

Start the JP1/Base log-file trap daemon (UNIX) or log-file trap service (Windows).

KAVT1056-W

Log Trap Job is finished.

Log file trapping has terminated.

(S)

Retries and re-executes the command, and then continues monitoring.

(O)

Even if this message appears, there is no problem with operation if the job terminated normally. Ignore the message and continue the operation.

If this error message appears repeatedly, check whether the log-file trap function operates correctly.

KAVT1058-I

retry again.

A temporary error occurred. The system re-executes the log file trapping command.

(S)

Continues processing.

KAVT1059-I

Watching start.

The log file trapping command was successfully executed. The system starts monitoring the log file.

(S)

Continues processing.

KAVT1060-W

A forced-termination request was accepted.

The system accepted a forced-termination request. The job is forcibly terminated.

(S)

Accepts the kill request and forcibly terminates the job.

KAVT1061-W

Cancel time up.

The timeout period had elapsed. The job is canceled.

(S)

Cancels the job due to the specified timeout period being elapsed.

KAVT1062-W

Information could not be output. (maintenance-information) (maintenance-information)

Memory was insufficient. The JP1 event-receiving job could not output a message to the Execution Result Details dialog box.

(S)

Continues processing without outputting the message to the Execution Result Details dialog box because memory was insufficient.

(O)

Check whether memory is sufficient.

For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT1065-W

The log-file trap command could not stop. (process-ID-of-log-file-trap (thread-ID) (operation-definition-file-name-at-executing-log-file-trap-command)

The Monitoring Log Files job terminated normally, but the process for monitoring log files could not stop or the termination could not be confirmed. The process for monitoring log files may not have stopped.

(S)

Ignores the error and continues processing.

(O)

Resources may be insufficient. Check whether the system resources are sufficient.

If this message appears, stop the JP1/Base log-file trap daemon (UNIX) or log-file trap service (Windows) when you stop JP1/AJS3 next time.

If this message appears repeatedly, stop the JP1/AJS3 services and the JP1/Base log-file trap daemon (UNIX) or log-file trap service (Windows).

KAVT1066-E

Main loop of an event-receiving process failed. (maintenance-information)

An attempt to initialize the process has failed.

(S)

Terminates the process for monitoring events (JP1 events and log trapping). A Receive JP1 Event job, a Monitoring Log Files job, or a Monitoring Event Log job cannot be monitored.

(O)

Check whether the system resources are sufficient, and then restart JP1/AJS3.

KAVT1067-E

Language setting could not be acquired. (maintenance-information) (maintenance-information)

The character set in the configuration definition information could not be acquired.

(S)

Assumes LANG=C for the character set, and continues the regular expression check for the monitoring conditions of the JP1 event-monitoring job.

(O)

Check whether the system resources are sufficient.

A monitoring condition using a regular expression may not work correctly. Check the generated JP1 event again, and change the status of the Receive JP1 Event job.

KAVT1068-W

The specified event server is inactive. (EventServerName=event-server-name)

The JP1/Base event service specified in the EventServerName environment setting parameter has not yet started.

(S)

Because the JP1/Base event service has not started, the system continues processing while retrying the connection. A log file monitoring job cannot be monitored until the JP1/Base event service starts.

(O)

This message appears if you execute a log file monitoring job when the JP1/Base event service has not yet started or the wrong event server name is specified in the EventServerName environment setting parameter. Restart the JP1/AJS3 service after making sure that the JP1/Base event service is running and the correct event server name is set in the EventServerName environment setting parameter.

KAVT1069-I

The specified event server was connected. (EventServerName=event-server-name)

A connection was established with the JP1/Base event service specified in the EventServerName environment setting parameter.

(S)

Continues processing.

KAVT1200-E

An error occurred during the search for JP1 events. The JP1 event search will now stop. (maintenance-information)

An error occurred while the pre-execution event search function was searching for a JP1 event.

(S)

Cancels processing.

(O)

Check whether the JP1 event search function is available and whether a problem occurred in the JP1/Base event service.

KAVT1201-E

An attempt was made to start a JP1 event search, but the JP1 events were in a disabled state. (maintenance-information)

The pre-execution event search function cannot search for JP1 events.

(S)

Cancels processing.

(O)

Check whether memory is sufficient.

For details on the amount of memory required, see JP1/Base Release Notes.

KAVT1202-E

The reading of JP1 event search conditions from the file was not possible. (maintenance-information)

The system could not read from a file the search conditions for the JP1 event to be searched for by the pre-execution event search function.

(S)

Cancels processing.

(O)

Check the file system for errors.

KAVT1203-E

The writing of JP1 event search conditions to the file was not possible. (maintenance-information)

The system could not write to a file the JP1 event searched for by the pre-execution event search function.

(S)

Cancels processing.

(O)

Check the file system for errors.

KAVT1204-E

An error occurred during the reading of the event filter file. (maintenance-information, system-error-message)

An error occurred during a read from the event filter file.

(S)

Cancels processing.

(O)

Determine the cause of the error according to the system error message, and then remove the cause.

KAVT1205-E

An error occurred during the opening of the search results output file. (maintenance-information, system-error-message)

An error occurred while the search result output file was being opened.

(S)

Cancels processing.

(O)

Based on the system error message, determine the cause that disabled the read operation. Then, remove the cause.

KAVT1206-E

An error occurred during status file making process. maintenance-information, system-error-message

An error occurred during the creation of a status file.

(S)

Cancels processing.

(O)

Based on the system error message, determine the cause that disabled the read operation. Then, remove the cause.

KAVT1207-E

An error occurred during the renaming of the search results output file. (maintenance-information)

An error occurred while the search result file was being renamed.

(S)

Cancels processing.

(O)

Determine the cause of the error from the maintenance information, and correct the error.

KAVT1210-E

An attempt to create an event search filter file failed. The search for events prior to execution will not start.

Although the option for finding events before starting event monitoring is specified, an event ID is not specified.

(S)

Abnormally terminates the Receive JP1 Event job.

(O)

When using the option for finding events before starting event monitoring, you must also specify an event ID. Recheck the definition of the Receive JP1 Event job, and re-execute it.

KAVT1211-E

An attempt to create an event search filter file failed. file-name, error-code, maintenance-information

The system could not create an event search filter file.

(S)

Cancels processing.

(O)

Correct the cause that disabled the creation of the event search filter file, and then re-execute the operation.

KAVT1212-E

An attempt to start the event search process failed. file-name, error-code, maintenance-information

The system could not start the event search process.

(S)

Cancels processing.

(O)

Correct the cause that disabled the start of the event search process, and then re-execute the operation.

KAVT1213-E

An end that event search process did not expect was detected.

The system detected an unexpected termination of the event search process.

(S)

Cancels processing.

(O)

This message might appear when the agent is under a heavy load, or when resources are insufficient. Check and remove the cause of the problem.

KAVT1214-E

Making of the pipe was failed, and the search for events prior to execution cannot use. maintenance-information

An attempt to create an internal file used for the option for finding events before starting event monitoring has failed. This option cannot be used.

(S)

Cancels initialization of the option for finding events before starting event monitoring. The execution status of the Receive JP1 Event job with this option specified may be invalid.

(O)

Check whether the system resources are sufficient and whether the directory created during installation of JP1/AJS3 was deleted inadvertently. Change the status of the event job that is placed in an invalid status. Alternatively, if you are using a macro variable for inheriting information received by an event job, generate the event that meets the monitoring condition again.

KAVT1217-I

An instance was established by the search for events prior to execution. (job-name, Event Arrived Time=arrival-time-of-event-satisfying-conditions)

As a result of the pre-execution event search, the system found an event that satisfies the job conditions.

(S)

Continues processing.

KAVT1226-W

Old JP1 events will be discarded because the number of preserved JP1 events issued during a search of pre-execution events has exceeded the threshold. (Seq No=serial-number-in-event-DB, Event ID=event-ID-basic-code, Event Arrived Time=event-arrival-time)

JP1 events will be discarded, beginning from the oldest one, because the number of held events generated during a search of pre-execution events has exceeded the threshold.

(S)

Deletes JP1 events generated during a search of pre-execution events, beginning from the oldest one, each time the threshold is exceeded, and continues processing.

(O)

Check whether all of the JP1 events having a serial number greater than the one indicated in serial-number-in-event-DB were detected. If any one of these JP1 messages was not detected, change the status of the job as required. Alternatively, if you are using the status-inherit option, again generate the event that meets the monitoring condition.

KAVT2001-I

The file monitoring process will now start.

The file monitoring process starts.

(S)

Starts the file monitoring process.

KAVT2004-I

The file (file-name) was created.

The file was created.

(S)

Continues processing.

KAVT2005-I

The file (file-name) was deleted.

The file was deleted.

(S)

Continues processing.

KAVT2006-I

The last modification time of file (file-name) has changed.

The last modification time of the file has changed.

(S)

Continues processing.

KAVT2007-I

The size of the file (file-name) has changed.

The size of the file has changed.

(S)

Continues processing.

KAVT2012-I

The file monitoring process will now end.

The file monitoring process terminates.

(S)

Terminates the file monitoring process.

KAVT2013-E

The name of the file to be monitored is not specified.

The name of the file to be monitored is missing.

(S)

Abnormally terminates the job.

(O)

Specify the name of the file to be monitored in the unit definition parameter for the ajsdefine command.

KAVT2014-E

The specified name of the file to be monitored is not a full path name.

The name of the file to be monitored is specified incorrectly.

(S)

Abnormally terminates the job.

(O)

Check the name of the file to be monitored, and then specify the full path name using the correct format.

KAVT2015-E

You cannot specify an asterisk (*) in a directory name.

A wildcard (*) cannot be specified in the directory name.

(S)

Abnormally terminates the job.

(O)

Check whether the wildcard (*) is specified in the directory name of the specified name of the file to be monitored.

KAVT2016-E

The specified name of the file to be monitored already exists as a directory.

The specified name of the file to be monitored already exists as a directory.

(S)

Abnormally terminates the job.

(O)

Specify the correct name of the file to be monitored, or delete the directory.

KAVT2017-W

The time-out period elapsed.

The time-out period expired. Cancels the job.

(S)

Specify the time-out period to cancel the job.

KAVT2018-W

A kill request was accepted.

The request to forcibly cancel a job is accepted. The job is forcibly canceled.

(S)

Forcibly cancel the job by the request.

KAVT2019-E

The file monitoring process ended. (maintenance-information)

The file monitoring process detected an error and terminated.

(S)

Terminated the file monitoring process because an error that prevents further processing occurred during processing. A Monitoring Files job cannot be monitored.

(O)

The error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT2020-I

The watching start option (file-name) is satisfied.

The monitoring start option is satisfied.

(S)

Continues processing.

KAVT2021-W

The memory for message output became insufficient. (file-name, maintenance-information)

Memory became insufficient. The message cannot be output to the detailed log.

(S)

Continues processing without outputting the message to the detailed log due to insufficient memory.

(O)

Check whether memory is sufficient.

For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT2022-W

The open file check cannot execute because memory became insufficient. (file-name, maintenance-information)

Memory was insufficient. The system could not check whether another process opened the file to be monitored.

(S)

Checks again whether there is a process that has opened the file at the next execution interval. Establishment of the file monitoring event job is delayed until the check finishes.

(O)

If this message appears repeatedly, check whether there is sufficient memory for executing the program, and then try again to change the status of the file indicated in file-name.

KAVT2023-E

Memory became insufficient. (maintenance-information)

Memory became insufficient.

(S)

Checks whether the file status was updated again at the next execution interval. Alternatively, abnormally terminates the job.

(O)

Check whether there is sufficient memory for execution.

Use JP1/AJS3 - View to check for a Monitoring Files job that terminated abnormally. If you find a Monitoring Files job that terminated abnormally, re-register it.

KAVT2024-W

The file information could not be obtained. The file monitoring event may not have occurred. (file-name, maintenance-information)

An attempt to acquire the status of the file to be monitored has failed.

(S)

The current status of the file to be monitored was unknown. The system checks the status again at the next execution interval. Any change in the file status that is made before the next execution interval will not be detected.

(O)

Check the following:

Check whether there are sufficient resources.

If the Windows version of JP1/AJS3 is used, check whether the size of the monitored file exceeds 2 GB.

To monitor a file equal to or greater than 2 gigabytes, specify the large file support option.

Make sure that the file to be monitored is not being updated.

If a change in the file status could not be detected, check the file status and then try again to change the status of the file indicated in file-name.

KAVT2025-E

You cannot specify 10 for the file monitoring interval.

Specify at least ten seconds for the monitoring interval.

(S)

Abnormally terminates the file monitoring job due to the invalid monitoring interval specified.

(O)

Check whether the conditions for specifying a 10-second or smaller monitoring interval are satisfied.

KAVT2026-E

The name of the file to be monitored cannot be obtained. (maintenance-information-1) (maintenance-information-2)

The name of the file to be monitored could not be obtained.

(S)

An error occurred while obtaining the name of the file to be monitored. Abnormally terminates the job.

(O)

Check the following:

Check whether you can open the directories and files to be monitored.

In UNIX, if 4096 appears for maintenance-information-1, whether the current directory from which JP1/AJS3 started has been deleted.#

If the directory has been deleted, restart JP1/AJS3.

#

Do not delete the current directory during operation of JP1/AJS. If the directory is unintentionally deleted, you will need to restart JP1/AJS3.

Note that the current directory differs depending on how JP1/AJS3 was started. For details about start methods, see 6.1.1 Starting JP1/AJS3 services manually in the JP1/Automatic Job Management System 3 Administration Guide.

KAVT2028-E

An attempt to start the file monitoring process failed. (maintenance-information) (maintenance-information)

The file monitoring process could not be started.

(S)

Terminates the file monitoring process because an error preventing further processing occurred.

(O)

Check the following, and then restart JP1/AJS3:

Check whether the system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created during installation of JP1/AJS3 was deleted unintentionally.

KAVT2029-E

An attempt to obtain pipe data failed. (maintenance-information) (maintenance-information)

The pipe data could not be received from the agent.

(S)

Terminates the file monitoring process because an error occurred during pipe processing with the agent.

(O)

Check the following, and then restart JP1/AJS3:

Check whether system resources are sufficient.

Check whether the user who started JP1/AJS3 has superuser privileges or administrator privileges.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT2030-E

An attempt to send pipe data failed. (maintenance-information) (maintenance-information)

The pipe data could not be sent to the agent.

(S)

An error occurred while processing the pipe from the agent. Terminates the file monitoring process depending on the location where the error occurred.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the permission environment of the started user is correct.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT2031-E

An error occurred during the operation of a file. (maintenance-information) (maintenance-information)

An error occurred while the file monitoring process is using the file.

(S)

Abnormally terminates the job depending on the location where the error occurred.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the permission environment of the started user is correct.

Check whether the directory created during installation of JP1/AJS3 was unintentionally deleted.

Check whether the following message was output in the same time zone: KAVT2034-W The status passing option file cannot be opened. The status passing cannot be executed. (file-name, maintenance-information).

If this message was output, follow the instructions given by the KAVT2034-W message.

If the Windows version of JP1/AJS3 is used, check whether the size of the monitored file exceeds 2 GB.

To monitor a file equal to or greater than 2 gigabytes, use the large file support option to specify monitoring of large files.

KAVT2032-E

An error exists in the definition contents of the file monitoring job. (maintenance-information) (maintenance-information)

An invalid definition is made for the file monitoring job.

(S)

Abnormally terminates the job because an invalid definition is made for the file monitoring job.

(O)

Check the definition. Then, retry.

KAVT2033-E

An attempt to set the next time monitoring failed. (maintenance-information) (maintenance-information)

The settings of monitoring for the next time could not be done.

(S)

An error occurred while making the settings of monitoring for the next time. Abnormally terminates the job.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the permission environment of the started user is correct.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT2034-W

The status passing option file cannot be opened. The status passing cannot be executed. (file-name, maintenance-information)

The file used for storing inherited status for the Monitoring Files job could not be opened. The status of the monitored file is not inherited. When JP1/AJS3 starts, the status of the file being monitored before JP1/AJS3 stopped is not inherited.

(S)

Does not attempt to read and use the status of the monitored file. When JP1/AJS3 starts, the system processes the Monitoring Files job without inheriting the status of the file being monitored before JP1/AJS3 stopped last time.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

For a cluster system, check whether the setting of the status passing option for a Monitoring Files job between the primary node and the secondary node matches.

For a cluster system that uses event jobs for DNS operation, check whether the setting for operation using the FQDN format between the primary node and the secondary node matches.

For details about the conditions for inheriting the status using the status passing option for the Monitoring Files job, see 7.6.2 Notes on the Monitoring Files job in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

If this message appears when the condition necessary for inheriting the status is not satisfied, this means that the file used for storing inherited status was deleted due to termination of the Monitoring Files job. Ignore the message and continue the operation.

KAVT2035-E

The name of the file to be monitored includes an invalid character. (file-name, maintenance-information)

An invalid character is specified in the name of the file to be monitored.

(S)

An invalid character is specified in the name of the file to be monitored. Abnormally terminates the job.

(O)

Check whether the name of the file to be monitored is created using the character codes that JP1/AJS3 can recognize.

KAVT2036-W

The open file check is impossible because the monitoring target file has no write permission. (file-name, maintenance-information, maintenance-information)

The system cannot perform an open file check for the file to be monitored because there is no permission to write into the file. The system does not assume that the file monitoring condition is satisfied.

(S)

The system does not assume that the file monitoring condition is satisfied. Continues processing.

(O)

Give the JP1/AJS3 service account the permission to write into the file to be monitored. In Windows, if the read-only checkbox for the file to be monitored is selected, deselect it.

KAVT2037-W

A macro variable exceeds 4096 bytes.

A file with the specified monitoring condition was updated, but the sum of the size of the values specified in macro variables exceeded 4,096 bytes.

(S)

The maximum amount of data that can be used for all macro variables per event is 4096 bytes (includes variable names). If the macro variable data exceeds 4096 bytes, the system uses only the first 4096 bytes and continues processing.

(O)

Check the execution status of the succeeding jobnet or job. If you find any problem, recheck the job definition.

KAVT2038-E

Monitoring can not be continued. Because the information on file of 2 Gbytes or more is contained in the status passing option file. (file-name)

Monitoring cannot be continued because the file used for storing the inherited status contains information about a file equal to or greater than 2 gigabytes.

(S)

Terminates the job abnormally.

(O)

Check whether the large file support option is set to no. If it is set to no, the large file support option may have been enabled before JP1/AJS3 stopped and the status passing option for the Monitoring Files job may have been enabled.

When the large file support option can be enabled:

Enable the large file support option, restart JP1/AJS3, and then re-execute the job. Note, however, that the statuses of the files that were monitored before JP1/AJS3 stopped are not inherited.

To enable the large file support option, specify yes for the LARGEFILEUSE environment setting parameter. For details about the environment setting parameters, see 20.11 Setting up JP1/AJS3 shared information in the JP1/Automatic Job Management System 3 Configuration Guide.

When the large file support option cannot be enabled:

Make sure that the file indicated in file-name or any file under the directory specified using the wildcard characters is smaller than 2 gigabytes. Make sure that the size of the file to be monitored does not exceed 2 gigabytes during monitoring, and then re-execute the job. Note, however, that the statuses of the files that were monitored before JP1/AJS3 stopped are not inherited.

For details about the conditions for inheriting the status using the status passing option for the Monitoring Files job, see 7.6.2 Notes on the Monitoring Files job in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

KAVT2042-W

The command to be used by the file monitoring process could not be found.(maintenance-information)

When the file monitoring process started, the command to be used by the file monitoring process could not be found.

If you perform a file monitoring job, files might not be monitored correctly.

(S)

Continues processing.

(O)

If you want to use a file monitoring job, make sure that the fuser command exists in /bin or /sbin. If the fuser command does not exist, contact the system administrator.

If you do not want to use a file monitoring job, ignore this message and continue the operation.

KAVT3001-I

Mail was received.

Mail was received.

(S)

Continues processing.

KAVT3002-I

Mail could not be received.

Mail could not be received.

(S)

Cancels processing.

(O)

Check whether the environment is set up to send and receive mail.

KAVT3003-E

Mail could not be saved.

Saving mail was impossible.

(S)

Cancels processing.

(O)

Check whether the environment is set up to save files for the disk size or authorization.

KAVT3004-E

JP1/AJS2 Mail monitoring Service stopped. Stop processing.

The system stops processing since the JP1/AJS2 mail monitoring service stopped.

(S)

Cancels processing.

(O)

Use the message that is output previously to determine the cause of the error.

KAVT3005-E

JP1/AJS2 Mail monitoring process is terminated. Stop processing.

The system stops processing since the JP1/AJS2 mail monitoring service terminated.

(S)

Cancels processing.

(O)

Use the message that is output previously to determine the cause of the error.

KAVT3006-E

Initialization failed. (reason)

Initialization was impossible.

(S)

Cancels processing.

(O)

Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3012-E

MAPI could not be initialized. (reason)

MAPI used for sending and receiving email could not be initialized.

(S)

Cancels processing.

(O)

If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.9.2(4) Mail sending job and mail reception monitoring job ends abnormally in the manual JP1/Automatic Job Management System 3 Troubleshooting.

In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whether a dialog box prompting the user to respond appears during email sending or receiving. If Microsoft Outlook cannot send or receive email independently or the dialog box appears, review the profile and mail account settings.

KAVT3014-E

Logon failed. (mapi_code=maintenance-information maintenance-information maintenance-information maintenance-information)

Logon was impossible.

(S)

Continues processing.

(O)

Check whether the profile name specified in setup is correct, and then retry.

KAVT3015-I

The result of logon. (mapi_code=maintenance-information maintenance-information maintenance-information maintenance-information)

This message indicates the results of logon to the profile.

(S)

Continues processing.

KAVT3016-E

Profile name used in send processing during logon is not within the definition.

A profile name used during logon is not defined for send processing.

(S)

Cancels processing.

(O)

Check whether the profile name specified in setup is correct, and then retry.

KAVT3017-E

During send processing, logon failed. (reason)

An attempt to log on to the mail system failed during email send processing.

(S)

Cancels processing.

(O)

If reason indicates insufficient memory, secure memory sufficient for execution, and then re-execute the job. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.9.2(4) Mail sending job and mail reception monitoring job ends abnormally in the manual JP1/Automatic Job Management System 3 Troubleshooting.

In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whether a dialog box prompting the user to respond appears during email sending or receiving. If Microsoft Outlook cannot send or receive email independently or the dialog box appears, review the profile and mail account settings.

KAVT3019-E

The send processing could not be initialized. (reason)

Initialization of the email send processing could not be carried out.

(S)

Cancels processing.

(O)

If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.9.2(4) Mail sending job and mail reception monitoring job ends abnormally in the manual JP1/Automatic Job Management System 3 Troubleshooting.

In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whether a dialog box prompting the user to respond appears during email sending or receiving. If Microsoft Outlook cannot send or receive email independently or the dialog box appears, review the profile and mail account settings.

KAVT3023-E

Mail could not be initialized. (reason)

An attempt to initialize the attributes of email to be sent has failed.

(S)

Cancels processing.

(O)

If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.9.2(4) Mail sending job and mail reception monitoring job ends abnormally in the manual JP1/Automatic Job Management System 3 Troubleshooting.

In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whether a dialog box prompting the user to respond appears during email sending or receiving. If Microsoft Outlook cannot send or receive email independently or the dialog box appears, review the profile and mail account settings.

KAVT3025-E

The destination could not be set. (reason)

The email destination could not be set.

(S)

Cancels processing.

(O)

If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.9.2(4) Mail sending job and mail reception monitoring job ends abnormally in the manual JP1/Automatic Job Management System 3 Troubleshooting.

In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whether a dialog box prompting the user to respond appears during email sending or receiving. If Microsoft Outlook cannot send or receive email independently or the dialog box appears, review the profile and mail account settings.

KAVT3027-E

Mail to be sent could not be created. (reason)

Creating mail to send was impossible.

(S)

Cancels processing.

(O)

If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.9.2(4) Mail sending job and mail reception monitoring job ends abnormally in the manual JP1/Automatic Job Management System 3 Troubleshooting.

In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whether a dialog box prompting the user to respond appears during email sending or receiving. If Microsoft Outlook cannot send or receive email independently or the dialog box appears, review the profile and mail account settings.

KAVT3029-I

The text will be reprocessed because memory became insufficient.

The text will be reprocessed due to insufficient memory.

(S)

Continues processing.

KAVT3030-E

The text could not be reprocessed. (reason)

An error occurred during processing of the text file for the email.

(S)

Cancels processing.

(O)

Check the environment settings such as the path to the text file and the access permissions for the file.

If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.9.2(4) Mail sending job and mail reception monitoring job ends abnormally in the manual JP1/Automatic Job Management System 3 Troubleshooting.

In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whether a dialog box prompting the user to respond appears during email sending or receiving. If Microsoft Outlook cannot send or receive email independently or the dialog box appears, review the profile and mail account settings.

KAVT3033-I

The text was re-processed.

The text was re-processed successfully.

(S)

Continues processing.

KAVT3034-E

The attached file could not be defined. (reason)

An attached file for email could not be set.

(S)

Cancels processing.

(O)

Check the environment settings such as the path to the attached file and the access permissions for the file.

If reason indicates insufficient memory, secure memory sufficient for execution, and then re-execute the job. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes. If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.9.2(4) Mail sending job and mail reception monitoring job ends abnormally in the manual JP1/Automatic Job Management System 3 Troubleshooting.

KAVT3036-E

Sending failed. (reason)

Sending was impossible.

(S)

Cancels processing.

(O)

Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

If reason shows mapi_code = xxxxxxxx (eight hexadecimal digits), see 2.9.2(4) Mail sending job and mail reception monitoring job ends abnormally in the manual JP1/Automatic Job Management System 3 Troubleshooting, and correct the problem, and then retry.

KAVT3038-E

The send processing could not be preprocessed.

Preprocessing a send was impossible.

(S)

Cancels processing.

(O)

Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT3039-E

During send processing, logoff failed. (reason)

Logoff from the mail system during email send processing failed.

(S)

Cancels processing.

(O)

If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.9.2(4) Mail sending job and mail reception monitoring job ends abnormally in the manual JP1/Automatic Job Management System 3 Troubleshooting.

In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whether a dialog box prompting the user to respond appears during email sending or receiving. If Microsoft Outlook cannot send or receive email independently or the dialog box appears, review the profile and mail account settings.

KAVT3041-E

The profile name used in the reception processing during logon is not within the definition.

A profile name used during logon is not defined in the environment settings.

(S)

Cancels processing.

(O)

Check whether the profile name specified in setup is correct, and then retry.

KAVT3042-E

During reception processing, logon failed. (reason)

Logoff for reception processing was impossible.

(S)

Cancels processing.

(O)

Check whether the mail server has gone down or a profile is created correctly.

KAVT3044-E

The reception processing could not be initialized. (reason)

Initializing the reception processing was impossible.

(S)

Cancels processing.

(O)

Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3048-E

The list of received mail could not be acquired. (reason)

Acquiring a received mail list was impossible.

(S)

Cancels processing.

(O)

Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3050-E

During reception processing, mail could not be read.

Reading mail was impossible for reception processing.

(S)

Cancels processing.

(O)

Check whether the environment is set up to send and receive mail.

KAVT3051-E

Mail could not be read. (reason)

Reading mail was impossible.

(S)

Cancels processing.

(O)

Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3054-E

The text could not be acquired. (reason)

Acquiring the text was impossible.

(S)

Cancels processing.

(O)

Check whether the environment is set up to send and receive mail or the text is specified correctly. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3057-E

The data length of the text could not be acquired. (reason)

Acquiring the text data length was impossible.

(S)

Cancels processing.

(O)

Check whether the environment is set up to send and receive mail. Also, check whether the text file is set correctly. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3060-E

The reception time could not be acquired.

Acquiring the reception time was impossible.

(S)

Cancels processing.

(O)

Contact the system administrator.

KAVT3061-E

The received mail could not be read. (reason)

Reading mail to receive was impossible.

(S)

Cancels processing.

(O)

Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3064-E

The list of attached files could not be acquired. (reason)

Acquiring an attached file list was impossible.

(S)

Cancels processing.

(O)

Check whether the attached file list is correct.

KAVT3066-E

During reception processing, the attached file could not be read.

Reading an attached file of mail was impossible for reception processing.

(S)

Cancels processing.

(O)

Check whether the disk space is sufficient.

KAVT3067-E

The attached file could not be read. (reason)

Reading an attached file was impossible.

(S)

Cancels processing.

(O)

Check whether the attached file is correct.

KAVT3070-E

The attached file could not be saved. (reason)

Saving an attached file was impossible.

(S)

Cancels processing.

(O)

Check whether the environment is set up to save the attached file. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3073-E

The attached file could not be saved.

Saving an attached file was impossible.

(S)

Continues processing.

(O)

Refer to the message output previously and determine the cause.

KAVT3074-E

The attached file could not be saved because it was an OLE object.

The file attached to email could not be saved because the file was an OLE object.

(S)

Continues processing.

(O)

The JP1/AJS3 mail linkage function cannot save attached files that include OLE objects. Accordingly, do not monitor reception of email to which such files are attached. Alternatively, do not specify the folder for saving attached files as a post-reception option for the email reception monitoring job.

KAVT3075-E

An error occurred during the saving of the attached file. (GetLastError=error-code file=attached-file-name)

An error occurred while a file attached to email was being saved.

(S)

Continues processing.

(O)

Take action according to the error code indicated in the message (return code from the Windows GetLastError() function).

KAVT3076-E

The opening-completed setting failed. (reason)

Setting a piece of opened mail was impossible.

(S)

Cancels processing.

(O)

Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3078-E

The text could not be saved.

The email text could not be saved.

(S)

Continues processing.

(O)

Check the environment settings such as the path for saving the text file, the disk space for saving the text file, and the access permissions for the file.

In addition, allocate sufficient memory for execution. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT3079-E

The list file could not be created.

A list file containing a list of files attached to the email could not be created.

(S)

Continues processing.

(O)

Check the environment settings such as the path for saving the list file, the disk space for saving the list file, and the access permissions for the file.

In addition, allocate sufficient memory for execution. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT3080-E

During reception processing, a file could not be saved.

Saving a file was impossible for reception processing.

(S)

Continues processing.

(O)

Check whether the environment is set up to save a file.

KAVT3081-E

During reception processing, the icon could neither be sent nor received.

Communicating with the icons was impossible for reception processing.

(S)

Cancels processing.

(O)

Check whether the environment is set up to send and receive mail.

KAVT3083-E

Failed to delete mail. (reason)

Deleting mail was impossible.

(S)

Continues processing.

(O)

If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3085-E

The reception processing could not be pre-processed.

Pre-processing the reception processing was impossible.

(S)

Cancels processing.

(O)

Use the message that is output previously to determine the cause of the error.

KAVT3086-E

During reception processing, logoff failed. (reason)

Logoff was impossible for reception processing.

(S)

Cancels processing.

(O)

Check whether the environment is set up to log in the mail server. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3106-I

Mail reception will now start.

Mail reception starts.

(S)

Continues processing.

KAVT3107-I

Mail sending will now start.

Mail sending starts.

(S)

Continues processing.

KAVT3112-E

The parameter is specified incorrectly.

An invalid parameter is found.

(S)

Cancels processing.

(O)

Correct the invalid parameter, and then retry.

KAVT3200-I

Start process of controlling MAPI (Send).

The MAPI send control process starts.

(S)

Continues processing.

KAVT3201-I

Start process of controlling MAPI (Receive).

The MAPI receive control process starts.

(S)

Continues processing.

KAVT3202-I

End process of controlling MAPI (Send).

The MAPI send control process terminates.

(S)

Continues processing.

KAVT3203-I

End process of controlling MAPI (Receive).

The MAPI reception control process terminates.

(S)

Continues processing.

KAVT3204-E

Failed to create a temporary file. file=file-name GetLastError=GetLastError-number

A temporary file to be used for mail system linkage could not be created.

(S)

Cancels processing.

(O)

Use file=file-name GetLastError=GetLastError-number to determine the cause of the error that prevented the indicated file from being created.

KAVT3205-E

Failed to read a temporary file. file=file-name GetLastError=GetLastError-number

A temporary file to be used for mail system linkage could not be read.

(S)

Cancels processing.

(O)

Determine the cause of the error that prevented the file indicated in file=file-name GetLastError=GetLastError-number from being read.

KAVT3206-E

Failed to create a folder. folder-name

A folder could not be created.

(S)

Cancels processing.

(O)

Determine the cause of the error that prevented the folder indicated shown in folder-name from being created.

KAVT3207-W

The mail data was too long, so it was truncated.(maintenance-information)

Because the data size specified in the definition of the email sending job was too long, the excess part was truncated. maintenance-information indicates the truncated part of the data as follows:

Title

The title was truncated.

Text

The text was truncated.

(S)

Truncates the excess part, and continues processing of the email sending job.

(O)

See 12.4.29 Detailed Definition - [Send Mail] dialog box in the JP1/Automatic Job Management System 3 Operator's Guide, and 12.4.30 Detailed Definition - [Send Mail] - [Attached File] dialog box in the JP1/Automatic Job Management System 3 Operator's Guide, and check the maximum number of bytes that can be used for information in the definition of email sending jobs.

KAVT3210-W

The send destination address was not found. (maintenance-information)

The specified email address was not found in the send destination mail system. Alternatively, the mail system in which the email address has been registered was not found.

maintenance-information indicates the number of email addresses that are specified in the email sending job but were not found.

(S)

Ignores the email address that was not found, and continues processing.

(O)

Check whether the specified email address was registered in the send destination mail system, and whether the mail system is running and ready for communication.

For the send destination email address, check whether email can be sent and received by using Microsoft Outlook alone without using JP1/AJS3, and whether a dialog box that requires a response from the user appears during sending or receiving.

If sending or receiving email is not possible or if such a dialog box appears, check and, if necessary, correct the following settings in the profile so that email can be sent and received. Then execute the email sending job.

Check whether the correct mail system name was specified for the send destination.

Check whether the specified email account has been registered in the connected mail system.

Check whether the correct password is set for the email account.

Check whether the profile settings are correct.

KAVT3211-W

The send destination address is ambiguous. maintenance-information

The email sending job cannot identify some of the specified email addresses.

(S)

Deletes the unidentifiable email addresses from the destinations list and continues processing of the email sending job.

(O)

Check whether the specified email addresses are correct by referring to the indicated maintenance information (the number of addresses that cannot be identified).

In addition, export the property information of all accounts registered on the mail server to a file. Then, using each of the specified email addresses as a search string, search the file to check whether the email address is the same as another property (such as a user name or office name).

For details on how to export the property information about accounts registered on the mail server, see the documentation for the mail server software.

KAVT3212-E

None of the specified mail addresses exist or all the mail addresses were specified incorrectly, so sending of the mail will now stop. (mapi_code=MAPI-code)

Sending email is canceled for one of the following reasons:

No email addresses are specified for the email sending job.

None of the specified email addresses can be found in the send destination mail system.

None of the mail systems in which the specified email addresses have been registered can be found.

(S)

Cancels processing.

(O)

If email addresses are not specified for the email sending job, specify them.

Check whether the specified email address was registered in the send destination mail system, and whether the mail system is running and ready for communication.

For details about the contents of mapi_code, see 2.9.2(4) Mail sending job and mail reception monitoring job ends abnormally in the manual JP1/Automatic Job Management System 3 Troubleshooting.

For the send destination email address, check whether email can be sent and received by using Microsoft Outlook alone without using JP1/AJS3, and whether a dialog box that requires a response from the user appears during sending or receiving.

If sending or receiving email is not possible or if such a dialog box appears, check and, if necessary, correct the following settings in the profile so that email can be sent and received. Then execute the email sending job.

Check whether the correct mail system name was specified for the send destination.

Check whether the specified email account has been registered in the connected mail system.

Check whether the correct password is set for the email account.

Check whether the profile settings are correct.

KAVT3268-I

Sent mail.

Mail was sent.

(S)

Continues processing.

KAVT3271-E

Mail could not be sent.

Sending mail was impossible.

(S)

Cancels processing.

(O)

Take action according to the error or warning message about email transmission that was output immediately before this message.

KAVT3273-I

Processing of mail sending will now start.

The mail transmission starts.

(S)

Continues processing.

KAVT3274-I

Processing of mail sending will now end.

The mail transmission terminates.

(S)

Terminates processing.

KAVT3275-E

The environment variable is specified incorrectly. (specified-data)

The environment variables are specified incorrectly.

(S)

Cancels processing.

(O)

Check the system resources, and then retry.

KAVT3276-E

The data is specified incorrectly. (data-type = data-value)

Invalid data is specified in an email sending job.

Data types and corresponding error details are as follows:

"Platform"

The platform type is invalid.

"Additional Information of Destination"

Information about the recipient is invalid.

"Text File"

The name of the text file is invalid.

"Attach File"

The name of an attached file is invalid.

"Attach File List"

The name of a list file for attached files is invalid.

(S)

Cancels processing.

(O)

Check the following according to the data type:

"Platform"

PC is specified as the platform type.

"Additional Information of Destination"

TO:, CC:, or BCC: appear before the recipient.

"Text File", "Attach File", "Attach File List"

The file is specified by full path name and in the correct format for Windows.

After making the necessary corrections, rerun the email sending job.

KAVT3277-E

A required item is missing.

A recipient or profile name is omitted from the definition of an email sending job.

(S)

Cancels processing.

(O)

Specify a recipient or profile name, and then rerun the email sending job.

KAVT3278-E

The parameter is specified incorrectly. (specified-data)

A parameter is specified incorrectly.

(S)

Cancels processing.

(O)

Correct the invalid parameter, and then retry.

KAVT3279-E

The configuration definition could not be read. (return-code)

The settings of the environment setting parameters to be used for mail system linkage cannot be read from the system.

(S)

Cancels processing.

(O)

Check whether JP1/AJS3 is installed correctly and whether the information is correctly set for the environment setting parameters to be used for mail system linkage. For details, see 2.3.4 Setting up the environment for the mail system linkage in the JP1/Automatic Job Management System 3 Linkage Guide.

Also check whether Administrator permissions are set for the following accounts:

Account of the OS user to whom the JP1 user who logs in to JP1/AJS3 - View is mapped

Account of the OS user when an OS user is specified for the account of the JP1/AJS3 service

Account of the OS user set for the JP1/AJS3 Mail service when the mail linkage function is used on the service

If you cannot check the above items, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVT3280-E

You are not authorized to access the configuration definition. (return-code)

There is no authorization to access the configuration definition. If you send mail, try sending with the authorization that can refer to the JP1/AJS3 information.

(S)

Cancels processing.

(O)

Try access with the administrator's authorization.

KAVT3281-E

The specified key does not exist in the configuration definition. (return-code)

The settings of the environment setting parameters to be used for mail system linkage cannot be read from the system.

(S)

Cancels processing.

(O)

Check whether JP1/AJS3 is installed correctly and whether the information is correctly set for the environment setting parameters to be used for mail system linkage. For details, see 2.3.4 Setting up the environment for the mail system linkage in the JP1/Automatic Job Management System 3 Linkage Guide.

Also check whether Administrator permissions are set for the following accounts:

Account of the OS user to whom the JP1 user who logs in to JP1/AJS3 - View is mapped

Account of the OS user when an OS is specified for the account of the JP1/AJS3 service

OS user account set in the JP1/AJS3 Mail service when the mail linkage function is used on the service.

If you cannot check the above items, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVT3282-E

An unexpected error occurred. (return-code-of-GetLastError-function)

An unexpected error occurred in the email sending job.

(S)

Cancels processing.

(O)

Take action according to the message that was output immediately before this message, or by checking the return code of the Windows GetLastError() function.

KAVT3283-E

The process will now stop because the mail monitoring process or service terminated.

Processing is stopped due to the mail monitoring process or service halt.

(S)

Cancels processing.

(O)

Use the message that is output previously to determine the cause of the error.

KAVT3284-E

Contact with the mail monitoring process or service failed. (return-code-of-GetLastError-function)

Contacting the mail monitoring process or service was impossible.

(S)

Cancels processing.

(O)

Check whether the JP1/AJS3 mail monitoring process or the service is running.

KAVT3285-E

Communication with the mail monitoring process or the service failed.

Communication with the mail monitoring process or service was impossible.

(S)

Cancels processing.

(O)

Check whether the JP1/AJS3 mail monitoring process or service is running.

KAVT3286-E

Communication of mail information failed.

Communicating the mail information was impossible.

(S)

Cancels processing.

(O)

Check whether the JP1/AJS3 mail monitoring process or service is running.

KAVT3287-E

The communication pipe could not be created.

Creating a communication pipe was impossible.

(S)

Cancels processing.

(O)

Check whether the JP1/AJS3 mail monitoring process or service is running.

KAVT3288-E

The thread could not be created. (return-code-of-GetLastError-function)

The email sending job has failed to create a thread.

(S)

Cancels processing.

(O)

Check the return code of the Windows GetLastError() function, and then take appropriate action.

If you cannot take corrective action, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVT3289-E

Fail to acquire completion status of thread. (return-code-of-GetLastError-function)

The email sending job has failed to acquire the end status of the thread.

(S)

Cancels processing.

(O)

Check the return code of the Windows GetLastError() function, and then take appropriate action.

If you cannot take corrective action, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVT3290-E

Memory became insufficient.

There is not enough memory.

(S)

Cancels processing.

(O)

Allocate sufficient memory to execute, and then retry.

KAVT3291-E

JP1/AJS2 mail monitoring process or service is not running. (return-code-of-GetLastError-function)

The JP1/AJS3 mail monitoring process or service is not running.

(S)

Cancels processing.

(O)

Start the JP1/AJS3 mail monitoring process or service.

KAVT3292-E

The installation path for JP1/AJS2 could not be acquired. (return-code)

Acquiring a JP1/AJS3 installation path was impossible.

(S)

Cancels processing.

(O)

Check whether JP1/AJS3 is installed correctly. Alternatively, check whether the user who executes the email sending job has permission to reference the registry.

KAVT3293-E

An error was detected in the mail monitoring process or service. (return-code-of-MAPI-function)

An error was detected in the mail monitoring process or service.

(S)

Cancels processing.

(O)

Check the error details by comparing return-code-of-MAPI-function with the following MAPI codes, and then take action. Also see the manual JP1/Automatic Job Management System 3 Troubleshooting.

8004010D: The disk space is insufficient.

8004010E: The resources are insufficient.

80040111: Logon failed.

80040115: A network error occurred.

80040116: A disk I/O error occurred.

80040124: The mail account is invalid.

8004010F: The destination mail address is not found.

80040607: The destination mail address is not found.

80040700: The destination mail address is incomplete.

KAVT3294-E

Operating environment of mail linkage is invalid. (definition=UNIX)

An invalid character has been used in the environment settings for the mail linkage function.

(S)

Cancels processing.

(O)

Specify use of the desktop or service in the environment setting parameter used for mail system linkage. For details, see 2.3.4 Setting up the environment for the mail system linkage in the JP1/Automatic Job Management System 3 Linkage Guide.

KAVT3295-E

No environment has been defined.

The mail linkage is not set up.

(S)

Cancels processing.

(O)

Specify use of the desktop or service in the environment setting parameter used for mail system linkage. Then, start the mail monitoring process or mail service, and execute the email sending job. For details, see 2.3.4 Setting up the environment for the mail system linkage in the JP1/Automatic Job Management System 3 Linkage Guide.

KAVT3296-E

The environment settings include an invalid character. (definition=execution-mode)

An invalid character is used in the environment settings for the mail linkage function.

(S)

Cancels processing.

(O)

Check the contents indicated in execution-mode in the message. Then, on the Mail Linkage page in the Manager Environment Settings dialog box or Agent Environment Settings dialog box, specify the setting requiring use of the mail linkage function on the desktop or on the service.

KAVT3297-E

The length of the text exceeds the maximum.

The length of the text exceeded the upper limit.

(S)

Cancels processing.

(O)

Check the upper limit of the text. For details about the upper limit, see 12. Windows and Dialog Boxes in the JP1/Automatic Job Management System 3 Operator's Guide.

KAVT3298-E

The folder specified for storing mail text files does not exist. (folder-name)

A folder that stores the text file does not exist.

(S)

Cancels processing.

(O)

Check whether a storage folder for the file exists.

KAVT3299-E

The folder specified for storing the attached files does not exist. (folder-name)

A folder that stores the attached files does not exist.

(S)

Cancels processing.

(O)

Check whether a storage folder for the file exists.

KAVT3300-E

The folder specified for storing the list of attached files does not exist. (folder-name)

A folder that stores the attached file lists does not exist.

(S)

Cancels processing.

(O)

Check whether a storage folder for the file exists.

KAVT3301-E

The specified mail text file does not exist. (file-name)

A text file does not exist.

(S)

Cancels processing.

(O)

Check whether the specified file exists.

KAVT3302-E

The text file could not be read. (file-name)

Reading a text file was impossible.

(S)

Cancels processing.

(O)

Check whether the specified file is correct.

KAVT3303-E

The specified attached file or files do not exist.

The file or attached file list does not exist.

(S)

Cancels processing.

(O)

Check whether the specified file exists.

KAVT3304-E

The attached files or list of attached files could not be read.

Reading the attached file or attached file list was impossible.

(S)

Cancels processing.

(O)

Check whether the specified file is correct.

KAVT3306-W

After an email was sent, a timeout occurred in the email sending job.(JOBID = job-number)

After the email sending job sent an email, the email sending process was placed in a wait state before the job finished. Then, a timeout occurred.

The contents of the email defined in the email sending job have already been sent.

(S)

Continues processing.

(O)

If this message is output frequently, check for any of the following phenomena occurring around the time when this message was output, and take necessary measures:

Problem with the network that connects to the mail server

Display of a dialog box or other window that requests a user response

KAVT3307-W

Before an email was sent, a timeout occurred in the email sending job. The processing to send the email will be retried.(JOBID = job-number)

After the email sending job started sending an email, the email sending process was placed in a wait state before sending of the email finished. Then, a timeout occurred.

Because the contents of the email defined in the email sending job have not been sent, the system retries sending of the email.

(S)

Continues processing.

(O)

If this message is output frequently, check for any of the following phenomena occurring around the time when this message was output, and take necessary measures:

Problem with the network that connects to the mail server

Display of a dialog box or other window that requests a user response

KAVT3308-E

The processing to send an email by the email sending job was retried, but the retry timed out.(JOBID = job-number)

After the email sending job started sending an email, the email sending process was placed in a wait state before sending of the email finished. Then, a timeout occurred.

Because the wait state did not stop before retry attempts timed out, the email could not be sent.

(S)

Abnormally terminates the email sending job.

(O)

If this message is output frequently, check for any of the following phenomena occurring around the time when this message was output, and take necessary measures:

Problem with the network that connects to the mail server

Display of a dialog box or other window that requests a user response

KAVT3401-I

Start JP1/AJS2 Mail monitor process.

The JP1/AJS3 mail monitoring process is started.

(S)

Continues processing.

KAVT3402-I

The JP1/AJS2 mail monitoring process started.

The JP1/AJS3 mail monitoring process has started.

(S)

Continues processing.

KAVT3403-I

Start JP1/AJS2 Mail monitoring service.

The JP1/AJS3 mail monitoring process is started.

(S)

Continues processing.

KAVT3404-I

The JP1/AJS2 mail monitoring service started.

The JP1/AJS3 mail monitoring service has started.

(S)

Continues processing.

KAVT3405-I

The JP1/AJS2 mail monitoring process will now end.

The JP1/AJS3 mail monitoring process stops.

(S)

Continues processing.

KAVT3406-I

JP1/AJS2 Mail monitoring process stopped.

The JP1/AJS3 mail monitoring process stopped.

(S)

Cancels processing.

KAVT3407-I

The JP1/AJS2 mail monitoring service will now end.

The JP1/AJS3 mail monitoring service stops.

(S)

Continues processing.

KAVT3408-I

JP1/AJS2 Mail service stopped.

The JP1/AJS3 mail monitoring service was stopped.

(S)

Cancels processing.

KAVT3409-E

The environment definition could not be read.

The settings of the environment setting parameters to be used for mail system linkage cannot be read from the system.

(S)

Cancels processing.

(O)

Check whether JP1/AJS3 is installed correctly and whether the information is correctly set for the environment setting parameters to be used for mail system linkage. For details, see 2.3.4 Setting up the environment for the mail system linkage in the JP1/Automatic Job Management System 3 Linkage Guide.

Also check whether Administrator permissions are set for the following accounts:

Account of the OS user to whom the JP1 user who logs in to JP1/AJS3 - View is mapped

Account of the OS user when an OS user is specified for the account of the JP1/AJS3 service

Account of the OS user set for the JP1/AJS3 Mail service when the mail linkage function is used on the service

If you cannot check the above items, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVT3420-W

The data set for inheritance information (macro-variable-name-of-truncated-data) is too long and was truncated to maximum-macro-variable-size bytes.

The data set for inheritance information was greater than the maximum size of the macro variable. The data was truncated to the maximum size.

(S)

Continues processing.

(O)

Check whether the subsequent job operates correctly.

KAVT3451-I

The mail linkage communication process will now start.

The mail linkage communication process starts.

(S)

Continues processing.

KAVT3452-I

The mail linkage communication process started.

The mail linkage communication process has started.

(S)

Continues processing.

KAVT3453-I

The mail linkage communication process stopped.

The mail linkage communication process has stopped.

(S)

Terminates processing.

KAVT3454-I

Mail reception monitoring will now start.

Monitoring of mail reception starts.

(S)

Continues processing.

KAVT3455-E

Mail reception monitoring will now stop.

Mail reception monitoring stops.

(S)

Continues processing.

(O)

If one of the following operations is performed, the email reception monitoring job is terminated and this message is output:

Changing the status of the email reception monitoring job in the jobnet by intentionally changing the job status or by forcibly terminating the job

Restarting the manager host while the email reception monitoring job in the jobnet is running

Stopping the scheduler service and execute the jpomanevreset command on the manager host while the email reception monitoring job in the jobnet is running

Stopping an agent host while the email reception monitoring job in the jobnet is running

If none of the above operations was performed, determine the cause of the problem by referring to the error message that was output before this one in the integrated trace log.

KAVT3456-I

The reception of messages that satisfy the conditions was confirmed.

The reception of messages that satisfy the conditions was confirmed.

(S)

Continues processing.

KAVT3457-I

Monitoring of mail reception will now end because the time-out period elapsed.

Monitoring of mail reception terminates because the time-out period has elapsed.

(S)

Continues processing.

KAVT3458-I

Method of mail monitor is "JP1/AJS2 Mail Service" -or- "JP1/AJS2 Mail Process".

This message shows the method of mail monitoring.

(S)

Continues processing.

KAVT3459-E

Method of mail monitor is not established. Please set up environment.

Check the environment definition, and then retry.

(S)

Cancels processing.

(O)

Check the environment definition, and then retry.

KAVT3460-E

Cannot recognize method of mail monitoring. Please set up environment again. (settings)

An invalid character was used in the environment settings for the mail linkage function.

(S)

Cancels processing.

(O)

Check the information indicated in settings in the message. Then, specify use of the desktop or service in the environment setting parameters used for mail system linkage. For details, see 2.3.4 Setting up the environment for the mail system linkage in the JP1/Automatic Job Management System 3 Linkage Guide.

KAVT3461-W

An error occurred during creation of a macro variable.

An error occurred while creating a macro variable.

(S)

Continues processing.

(O)

Refer to the error message output previously, and determine the cause of the error.

KAVT3462-W

A macro variable exceeds 4096 bytes. Some macro variables could not be created.

The macro variable exceeded 4,096 bytes. Some macro variables could not be created.

(S)

Continues processing.

(O)

Set a macro variable that does not exceed 4,096 bytes.

KAVT3463-E

The platform is specified incorrectly.

A platform is specified incorrectly.

(S)

Cancels processing.

(O)

Check the platform, and then retry.

KAVT3464-W

The mail monitoring process or service is not running.

The mail monitoring process or service is not running.

(S)

Cancels processing.

(O)

Start the mail monitoring process or service.

KAVT3465-I

Start of the mail monitoring process or service was confirmed.

Start of the mail monitoring process or service was confirmed.

(S)

Continues processing.

KAVT3466-E

The definition of the mail monitoring job is invalid.

The email reception monitoring job is defined incorrectly.

(S)

Cancels processing.

(O)

Correct the definitions of the email reception monitoring job, and then retry.

KAVT3467-E

Memory became insufficient.

A memory shortage occurred.

(S)

Cancels processing.

(O)

Allocate sufficient memory for execution, and then retry.

KAVT3468-E

An event for canceling registration of a job could not be created.

Creating an event for canceling job registration was impossible.

(S)

Cancels processing.

(O)

Check the status of the event server.

KAVT3469-E

The option for not linking mail is selected. Mail reception will not be monitored.

The mail linkage is not set up.

(S)

Cancels processing.

(O)

Specify use of the desktop or service in the environment setting parameter used for mail system linkage. Then, start the mail monitoring process or mail service, and execute the email reception monitoring job. For details, see 2.3.4 Setting up the environment for the mail system linkage in the JP1/Automatic Job Management System 3 Linkage Guide.

KAVT3473-E

The count of the mail monitoring job is over a max job's count. (Max job's count=maximum-registration-count)

The number of registered email reception monitoring jobs has exceeded the limit value.

(S)

Cancels processing.

(O)

If necessary, unregister the email reception monitoring jobs so that the number of registered jobs is below the limit value.

For details about the limit values, see the cautionary notes in 2.6.1(1) Judging whether received email satisfies the monitoring conditions in the JP1/Automatic Job Management System 3 Linkage Guide.

KAVT3499-E

An unexpected error occurred. (maintenance-information)

An error occurred during inter-process communication of the email reception monitoring job.

(S)

Cancels processing.

(O)

Take action according to the message that was output immediately before this message or by checking the maintenance information (return code of the Windows GetLastError function).

KAVT3501-I

The mail reception process will now start.

The mail reception process starts.

(S)

Continues processing.

KAVT3502-I

The mail reception process will now end.

The mail reception process terminates.

(S)

Terminates processing.

KAVT3504-E

Failed to analyze job data. (DB-data) (error-code-of-function)

A failure occurred in the function that analyzes job data.

(S)

Cancels processing.

(O)

Check whether the job is defined correctly.

KAVT3512-E

Memory became insufficient. (maintenance-information)

A memory shortage occurred.

(S)

Cancels the process without enough memory and continues processing.

(O)

Check the system for free space.

KAVT3513-E

Failed to get Pipe Data. (maintenance-information) (maintenance-information)

Acquiring the pipe data from the agent was impossible.

(S)

Cancels the pipe processing. Terminate the mail reception process depending on the place of occurrence.

(O)

Check whether:

The system resources are sufficient.

The permission environment of the started user is correct.

The directory created during installation of JP1/AJS3 is not deleted inadvertently.

KAVT3514-E

Failed to send Pipe Data. (maintenance-information) (maintenance-information)

Sending the pipe data to the agent was impossible.

(S)

Cancels piping and continues processing. The job execution status may be incorrect.

(O)

Check whether:

The system resources are sufficient.

The permission environment of the started user is correct.

The directory created during installation of JP1/AJS3 is not deleted inadvertently.

KAVT3515-E

An auxiliary file could not be opened. (maintenance-information) (maintenance-information)

Unable to open an auxiliary file from the agent.

(S)

Abnormally terminates the job request.

(O)

Check whether:

The system resources are sufficient.

The permission environment of the started user is correct.

The directory created during installation of JP1/AJS3 is not deleted inadvertently.

KAVT3519-W

A macro variable exceeds 4096 bytes.

The macro variable exceeded 4,096 bytes after conversion.

(S)

Since the macro variable exceeded 4,096 bytes after conversion, rounds down the succeeding macro variables and continues processing.

(O)

The part of the macro variable exceeding 4,096 bytes is not passed. Check the macro. If you find any problem, review the job definition.

KAVT3520-E

Failed to start. (maintenance-information) (maintenance-information)

Preparing the process startup was impossible.

(S)

Terminates the mail reception process.

(O)

Restart the mail reception process.

KAVT3521-W

An error occurred during analysis of macro variables. (maintenance-information) (maintenance-information)

An error occurred while analyzing a macro variable.

(S)

Does not create a macro variable and abnormally terminates the job.

(O)

Re-execute the job as required.

KAVT3522-W

Information could not be output. (maintenance-information) (maintenance-information)

Outputting the information to the standard error output was impossible.

(S)

Does not output the information due to insufficient memory and continues processing.

(O)

Check the system for free space.

KAVT3523-W

Forced termination was accepted.

The system accepted a kill request. The job is forcibly terminated.

(S)

Accepts the kill request and forcibly terminates the job.

KAVT3524-W

Cancel time up.

The timeout period had elapsed. The job is canceled.

(S)

Cancels the job due to the specified timeout period being elapsed.

KAVT3525-W

Mail Lock File(maintenance-information)could not be created.( maintenance-information)( maintenance-information)

An error occurred during creation of the lock file used for locking files.

(S)

Cancels processing, and continues processing after a monitoring interval elapses.

(O)

If this message is output more than once, determine the cause of the error from the maintenance information.

KAVT3526-W

Mail File(maintenance-information)can not be locked, because the file is being used by another application.

The lock processing failed because the monitored mail file was already locked.

(S)

Cancels processing, and continues processing after a monitoring interval elapses.

(O)

Use the data collection tool to collect data and contact the system administrator (see 1.2.3 To the system administrators).

KAVT3528-W

Mail File(maintenance-information)could not be opened.( maintenance-information)

The mail file could not be opened.

(S)

Cancels the processing, and continues processing.

(O)

Determine the cause of the error from the maintenance information, and take appropriate action.

KAVT3530-E

A mail lock file (lock-file-name) could not be released. (maintenance-information) (maintenance-information, system-error-message)

Releasing the lock file was impossible.

(S)

Cancels processing.

(O)

Collect data about this internal error and then contact the system administrator.

KAVT3531-W

Mail File(maintenance-information)could not be read.( maintenance-information)( maintenance-information)

The mail file could not be read.

(S)

Cancels the processing, and continues processing.

(O)

Determine the cause of the error from the maintenance information, and take appropriate action.

KAVT3532-W

Mail File(maintenance-information)could not be deleted.( maintenance-information)( maintenance-information)

A mail file could not be deleted.

(S)

Cancels the processing, and continues processing.

(O)

Determine the cause of the error from the maintenance information, and take appropriate action.

KAVT3533-W

A mail file (mail-file-name) could not be written. (maintenance-information) (maintenance-information) (maintenance-information, system-error-message)

Writing a mail file was impossible.

(S)

Cancels the process without enough memory and continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented the file from being written. Then take action.

KAVT3534-E

Mail watching ended. (maintenance-information) (maintenance-information)

The mail reception process detected an error and terminated.

(S)

Terminates the mail reception process because an irrecoverable error occurred during the processing.

(O)

Take action according to the message that is output previously. Restart JP1/AJS3 to ensure correct operation.

KAVT3538-W

The environment definition could not be read. (maintenance-information) (maintenance-information)

Reading an environment definition was impossible.

(S)

Continues processing.

(O)

Check the content of the environment definition, and then restart JP1/AJS3 and reload.

KAVT3539-W

No monitoring user name is specified.

A monitoring user name is not specified in the environment definitions.

(S)

Continues processing.

(O)

Redefine the environment definitions.

KAVT3540-W

No mail file directory is specified.

A mail file directory is not specified in the environment definitions.

(S)

Continues processing.

(O)

Redefine the environment definition.

KAVT3541-W

The file for saving mail is not specified.

A mail save file is not specified in the environment definition.

(S)

Continues processing.

(O)

Redefine the environment definition.

KAVT3542-W

The monitoring user name exceeds (specified-byte-length) bytes.

The monitoring user name in the environment definition exceeds the maximum byte length.

(S)

Continues processing.

(O)

Redefine the environment definition.

KAVT3543-W

The mail file directory name exceeds (specified-byte-length) bytes.

The mail file directory name in the environment definition exceeds the maximum byte length.

(S)

Continues processing.

(O)

Redefine the environment definition.

KAVT3544-W

The name of the file for saving mail exceeds (specified-byte-length) bytes.

The length of the mail for saving file names in the environment exceeds the maximum byte length.

(S)

Continues processing.

(O)

Redefine the environment definition.

KAVT3545-W

No directory is specified for backing up mismatched mail.

A mismatched mail save directory is not specified in the environment definition.

(S)

Continues processing.

(O)

Redefine the environment definition if required.

KAVT3546-W

The name of the directory for backing up mismatched mail exceeds (specified-byte-length) bytes.

The mismatched mail save directory name in the environment definition exceeds the maximum byte length.

(S)

Continues processing.

(O)

Redefine the environment definition.

KAVT3547-W

Information about mail file (maintenance-information) could not be obtained: maintenance-information (maintenance-information, system-error-message)

Obtaining the file information for the mail files was impossible.

(S)

Cancels processing, waits for the monitoring interval and continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented the file information from being obtained. Then take action.

KAVT3548-W

The input file for the mail filtering application could not be opened: (maintenance-information, system-error-message)

Opening an input file was impossible in the mail filter applications.

(S)

Cancels processing, waits for the monitoring intervals, and continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented the file from being opened. Then take action.

KAVT3549-W

The input file for the mail filtering application could not be written to: (maintenance-information, system-error-message)

Writing an input file was impossible in the mail filter applications.

(S)

Cancels processing, waits for the monitoring intervals, and continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented mail from being written. Then take action.

KAVT3550-W

The output file from the mail filtering application could not be read: (maintenance-information, system-error-message)

Reading an input file was impossible from the mail filter applications.

(S)

Cancels processing, waits for the monitoring intervals, and continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented mail from being read. Then take action.

KAVT3551-E

An error occurred in the mail filtering application. Return value: return-code-of-mail-filter-application

An error occurred in the internal mail filter applications and the mail was not converted correctly.

(S)

Cancels processing, waits for the monitoring intervals, and continues processing.

(O)

Check the mail filtering application.

KAVT3552-W

Mail could not be taken out of the mail file.

Fetching the mail from the mail file of the monitoring user was impossible.

(S)

Cancels processing, waits for the monitoring intervals, and continues processing.

(O)

Although an email that met a monitoring condition was received, the monitoring conditions of some email reception monitoring jobs might not have been met.

Check the email reception status to see whether there are email reception monitoring jobs whose monitoring conditions are not met.

After this message is output, if you continue to receive emails that meet some but not all of the monitoring conditions of email reception monitoring jobs, use the data collection tool to collect data, and then contact the system administrator. (see 1.2.3 To the system administrators)

KAVT3553-W

The inherited mail file (file-name) could not be opened: (maintenance-information, system-error-message)

Opening an inheritance mail file was impossible.

(S)

Terminates the corresponding job without inheritance information.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented the file from being opened. Then take action.

KAVT3554-W

The inherited mail file (file-name) could not be written to: (maintenance-information, system-error-message)

Writing an inheritance mail file was impossible.

(S)

Terminates the job without inheritance information.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented mail from being written. Then take action.

KAVT3555-W

The inherited mail file (file-name) could not be closed: (maintenance-information, system-error-message)

Closing an inheritance mail file was impossible.

(S)

Terminates the job without inheritance information.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented the file from being closed, and then take action. Re-execute the job if needed.

KAVT3556-W

The file for saving mail (file-name) could not be opened: (maintenance-information, system-error-message)

Opening a mail save file was impossible.

(S)

Terminates the job and continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented the file from being opened. Then take action. Re-execute the job if needed.

KAVT3557-W

The file for saving mail (file-name) could not be written to: (maintenance-information, system-error-message)

Writing a mail save file was impossible.

(S)

Terminates the job and continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented mail from being written. Then take action. Re-execute the job if needed.

KAVT3558-W

The file for saving mail (file-name) could not be closed: (maintenance-information, system-error-message)

Closing a mail save file was impossible.

(S)

Terminates the job and continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented the file from being closed. Then take action.

KAVT3559-E

The mail filtering application could not be called: (maintenance-information, system-error-message)

Calling a mail filter application was impossible.

(S)

Continues processing.

(O)

Check the mail filter application.

KAVT3560-W

The output file from the mail filtering application could not be opened: (maintenance-information, system-error-message)

Opening an output file in the mail filter applications was impossible.

(S)

Continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented the file from being opened. Then take action.

KAVT3561-W

File information about the mail filtering application could not be obtained: (maintenance-information, system-error-message)

Acquiring the output file information in the mail filter applications was impossible.

(S)

Continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented the file information from being obtained. Then take action.

KAVT3562-E

The file output from the mail filtering application contains no mail.

No mail is found in the output file of the mail filter applications.

(S)

Continues processing.

(O)

Check the mail filter application.

KAVT3563-W

Unrecognized data exists at the beginning of the mail file.

There is unrecognizable data found at the beginning of a mail file.

(S)

Leaves unrecognizable data in the mail and continues processing.

(O)

Stop JP1/AJS3 as required and then delete unrecognizable data.

KAVT3564-W

The mail file has no recognizable data.

Only unrecognizable data is found in the monitoring mail file.

(S)

Leaves unrecognizable data in the mail and continues processing.

(O)

Stop JP1/AJS3 as required and then delete unrecognizable data.

KAVT3565-W

The arrival date of the mail cannot be confirmed.

No arrival data is found for the mail.

(S)

Continues processing.

(O)

Stop JP1/AJS3 and then check the mail system.

KAVT3566-W

Mail File could not be compressed.: maintenance-information (maintenance-information, system-error-message)

Compressing the mail file was impossible.

(S)

Continues processing.

(O)

Use maintenance information and system error message to determine the cause of unsuccessful rewriting. Then take action.

KAVT3567-W

The mail reception list file (file-name) could not be created.

Creating a mail reception list file was impossible.

(S)

Continues processing.

(O)

Take action according to the message that is output previously.

KAVT3568-W

The mail reception list file (file-name) could not be opened: (maintenance-information, system-error-message)

Opening a mail reception list file was impossible.

(S)

Continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented the file from being opened. Then take action.

KAVT3569-W

The mail reception list file (file-name) could not be written to: (maintenance-information, system-error-message)

Writing a mail reception list file was impossible.

(S)

Continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented the mail reception list from being written. Then take action.

KAVT3570-W

The mail reception list file (file-name) could not be closed: (maintenance-information, system-error-message)

Closing a mail reception list file was impossible.

(S)

Continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented the file from being closed. Then take action.

KAVT3571-W

The error mail file (file-name) could not be opened: (maintenance-information, system-error-message)

Opening a mail file for failures was impossible.

(S)

Cancels processing, waits for the monitoring interval and continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented the file from being opened. Then take action.

KAVT3572-W

The error mail file (file-name) could not be written: (maintenance-information, system-error-message)

Writing an error mail file was impossible.

(S)

Cancels processing, waits for the monitoring interval and continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented mail from being written. Then take action.

KAVT3573-W

The error mail file (file-name) could not be closed: (maintenance-information, system-error-message)

Closing an error mail file was impossible.

(S)

Cancels processing, waits for the monitoring interval and continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented the file from being closed. Then take action.

KAVT3574-I

Mail was saved in the error mail file (file-name).

Mail was saved in the error mail file.

(S)

Continues processing. Depending on the location where the error occurred, the system cancels processing, waits for the monitoring intervals, and continues processing.

(O)

Take action according to the message that is output previously.

KAVT3575-W

The file for storing mismatched mail (file-name) could not be opened: (maintenance-information, system-error-message)

Opening a save file for mismatched mail was impossible.

(S)

Cancels processing, waits for the monitoring interval and continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented the file from being opened. Then take action.

KAVT3576-W

The file for storing mismatched mail (file-name) could not be written: (maintenance-information, system-error-message)

Writing a save file for mismatched mail was impossible.

(S)

Cancels processing, waits for the monitoring interval and continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented mail from being written. Then take action.

KAVT3577-W

The file for storing mismatched mail (file-name) could not be closed: (maintenance-information, system-error-message)

Closing a save file for mismatched mail was impossible.

(S)

Cancels processing, waits for the monitoring interval and continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented the file from being closed. Then take action.

KAVT3578-W

The file for storing mismatched mail (file-name) cannot be locked, because another application is using the file.

Since the mismatched mail save file is locked, the lock processing failed.

(S)

Cancels processing, waits until the next monitoring interval, and continues processing.

(O)

Use the data collection tool to collect data and contact the system administrator (see 1.2.3 To the system administrators).

KAVT3580-I

The mail data table could not be created.

The mail data table for retrieving monitored mail and job information could not be created.

(S)

Cancels processing, waits for the monitoring intervals, and continues processing.

(O)

Take action according to the message that is output previously.

KAVT3585-W

No monitoring interval is specified.

The environment definition does not specify the monitoring intervals.

(S)

Assumes ten minutes.

(O)

Redefine the environment definition as required.

KAVT3586-W

Specify a monitoring interval from 1 to 1,440.

The monitoring interval for the environment definition exceeds the range of 1 to 1,440.

(S)

Assumes ten minutes.

(O)

Redefine the environment definition as required.

KAVT3587-W

The inherited mail file could not be created. (file-name)

Creating an inheritance mail file was impossible.

(S)

Does not create the inheritance mail file, but terminates the job.

(O)

See the mail monitoring log file.

KAVT3588-W

The directory could not be created. (directory-name) (maintenance-information)

Creating a directory was impossible.

(S)

Continues processing.

(O)

Use maintenance information and system error message to determine the cause of the error that prevented the directory from being created. Then take action.

KAVT3593-W

The directory to store inherited information is not specified.

A storage directory for inheritance information is not specified to the environment definitions.

(S)

Assumes an inheritance information directory in units of a logical host.

(O)

Redefine the environment definition as required.

KAVT3594-I

Mail will be monitored.

Mail will be monitored in response to the request from the job.

(S)

Continues processing.

KAVT3595-W

Mail cannot be monitored.

Mail cannot be monitored in the current state.

(S)

Continues processing and accepts the job request.

(O)

Check the environment definition, and then restart JP1/AJS3.

KAVT3596-E

Main loop of a mail reception process failed. (maintenance-information)

The main processing of a mail reception process could not start.

(S)

Terminates the mail reception process.

(O)

Check whether the system resources are sufficient and whether the permission environment of the started user is correct, and then retry.

KAVT3597-E

An error occurred during the access of the file(file-name). (maintenance-information) (maintenance-information) (maintenance-information, system-error-message)

An error occurred during the access to the file.

(S)

Continues processing.

(O)

Check whether:

The maintenance information provides a file.

The system resources are sufficient.

The permission environment of the started user is correct.

KAVT3598-E

An error occurred during mail reception monitoring: maintenance-information maintenance-information maintenance-information maintenance-information

An error occurred during monitoring of mail reception.

(S)

Continues processing.

(O)

Collect the data about the internal error, and then contact the system administrator.

KAVT3599-W

The environmental setting parameter is invalid.(parameter-name)

The environment setting parameter is specified incorrectly.

(S)

Assumes the default value and continues processing.

(O)

If necessary, specify the environment definition again.

KAVT3700-I

jposendml command will now start.

The mail sending command starts.

(S)

Continues processing.

KAVT3701-I

sendmail will now start.

sendmail starts.

(S)

Continues processing.

KAVT3702-I

Mail was sent normally.

Mail was sent normally.

(S)

Terminates processing.

KAVT3703-I

temporary file:("temporary-file-name")

The working file name was created.

(S)

Continues processing.

KAVT3704-E

The command was interrupted.

The command was interrupted.

(S)

Cancels processing.

(O)

Determine the cause of the interruption by referring to another output message, and then retry.

KAVT3705-E

Usage: jposendml [-p platform-name]

Sending mail is specified incorrectly.

(S)

Cancels processing.

(O)

Correctly specify sending mail.

KAVT3706-E

A temporary file could not be created. (file: "temporary-file-name")

Creating a temporary file for sending mail was impossible.

(S)

Cancels processing.

(O)

Check that there is sufficient disk spaces, and then retry.

KAVT3707-E

The specified platform is invalid. (Platform: "platform-name")

The specified platform is invalid.

(S)

Cancels processing.

(O)

Check the definitions and re-execute the job.

KAVT3708-E

No platform is specified.

No platform is specified.

(S)

Cancels processing.

(O)

Check the definitions and re-execute the job.

KAVT3709-W

The title was too long, so it was truncated.

An item name for sending it was truncated because it is too long.

(S)

Continues processing.

(O)

Check the JP1/AJS3 job definitions.

KAVT3710-E

The mail-destination address is invalid: ("mail-destination-address")

An invalid mail destination address is specified.

(S)

Cancels processing.

(O)

Check the definitions and then re-execute the job.

KAVT3711-E

No mail-destination address is specified.

A mail destination address is not defined.

(S)

Cancels processing.

(O)

Check the definitions and then re-execute the job.

KAVT3712-E

The mail-destination address exceeds the maximum length: ("mail-destination-address")

You specified the mail send destination address with more than 256 bytes.

(S)

Cancels processing.

(O)

Check the definitions and then re-execute the job.

KAVT3714-E

No mail text file was found.

A mail text file was specified, but the file does not exist.

(S)

Cancels processing.

(O)

Check whether the file exists.

KAVT3715-E

The mail text file cannot be read.

A mail text file name was specified, but the file could not be read.

(S)

Cancels processing.

(O)

Check whether the file can be read.

KAVT3716-W

Mail text was too long, so it was truncated.

Mail text was too long, so it was truncated.

(S)

Continues processing.

(O)

Check the length and contents of text you want to send.

KAVT3717-E

sendmail command caused an error: (error: message-for-sendmail-command)

An error occurred while using the sendmail command for sending mail.

(S)

Cancels processing.

(O)

Use the message of the sendmail command to determine the cause of the error. Re-execute the job if needed.

KAVT3718-I

Mail has been queued.

Mail is not sent immediately. It is queued and then delivered.

(S)

Sends mail normally.

(O)

If mail is not sent after a while, check that there are sufficient disk spaces, and then retry.

KAVT3719-E

sendmail returned an unexpected error. (error: return-code-of-sendmail-command)

The sendmail command for sending mail returned an unexpected error.

(S)

Cancels processing.

(O)

Use the return code of the sendmail command to determine the cause of the error. Re-execute the job if needed.

KAVT3720-E

A required program is missing. (program: program-name)

A program necessary for sending mail does not exist. Check whether the sendmail command is provided.

(S)

Cancels processing.

(O)

Check that there are necessary programs for sending mail, and then set up the environment that allows correct operations.

KAVT3721-E

Message Put error. (error: error-code-at message-output, message-whose-output-was-attempted)

Output of a message was attempted, but an error occurred.

(S)

Continues processing.

(O)

Check that there is sufficient disk spaces, and then retry.

KAVT3722-E

jposendml is unusable.

Emails cannot be sent in the OS of a host on which the email sending job is to be executed.

(S)

Cancels processing.

(O)

Change the target host to a host whose OS environment supports the mail system linkage function, and then re-execute the email sending job.

KAVT3723-E

Message Put error. (reason)

An attempt was made to output a message, but memory became insufficient.

(S)

Cancels processing.

(O)

Check that there are sufficient disk spaces, and then retry.

KAVT3801-E

Illegal option (-character) exists.

You specified an illegal option.

(S)

Cancels processing.

(O)

Specify a correct option.

KAVT3802-E

Value for option (-option) is not specified.

A value is not specified for the option.

(S)

Cancels processing.

(O)

Specify the necessary option.

KAVT3803-E

Extra argument(s) exist.

You specified an extra argument.

(S)

Cancels processing.

(O)

Delete the unnecessary argument.

KAVT3804-E

Invalid value for option (-option).

An invalid option was specified.

(S)

Cancels processing.

(O)

Specify the correct option.

KAVT3805-E

Option (-option) appears twice or more.

An option was specified more than once.

(S)

Cancels processing.

(O)

Specify only one option among the choice of options.

KAVT3806-E

Monitoring User name not specified.

A monitoring user name is missing.

(S)

Cancels processing.

(O)

Specify the monitoring user name.

KAVT3807-W

Retry processing is canceled.

An exclusive retry was canceled because the specified retry cancel time had elapsed.

(S)

Cancels processing.

(O)

Since this error causes mail to bounce to its sending source, re-send it as required.

KAVT3810-E

I/O error occurred: maintenance-information maintenance-information maintenance-information system-error-message

An I/O error occurred in inputting/outputting a file while executing the mail delivery command.

(S)

Cancels processing.

(O)

Check whether:

The system resources are sufficient.

The permission environment of the started user is correct.

The directory created during installation of JP1/AJS3 was deleted inadvertently.

KAVT3811-E

Insufficient memory: maintenance-information maintenance-information maintenance-information

A memory shortage occurred during the execution of the mail delivery command.

(S)

Cancels processing.

(O)

Check that there is free space in memory in the system.

KAVT3814-E

An error occurred in Mail Send Command: maintenance-information maintenance-information (maintenance-information) (system-error-message)

(S)

Cancels processing.

(O)

Use maintenance information and system error message to determine the cause of the error.

KAVT3820-I

Execute Mail Send Command.: maintenance-information maintenance-information

Execute the mail delivery command.

(S)

Continues processing.

KAVT3821-I

Mail Send Command finished.

The mail delivery command terminated.

(S)

Terminates processing.

KAVT3823-I

Read a mail.

The mail delivery command reads mail from standard input.

(S)

Continues processing.

KAVT3824-I

Wrote a mail.

The mail delivery command is written mail into the mail file.

(S)

Continues processing.

KAVT3825-E

Failed to access (profile-name). (maintenance-information)

An error occurred during access to the profile indicated in profile-name.

(S)

Changes the status of the email sending job to Ended abnormally.

(O)

Check the following, and then re-execute the job:

Check whether the correct profile name is specified.

Check whether the execution user permissions are set correctly for the profile name.

Check that the jpomailprof command is not being executed.

KAVT3826-E

Failed to bind (IP-address). (maintenance-information)

An attempt to bind IP-address failed.

(S)

Changes the status of the email sending job to Ended abnormally.

(O)

Check the following, and then re-execute the job:

Check whether the IP address to be bound is correct.

KAVT3828-E

A timeout occurred during a connection to the SMTP server. (SMTP-server-name:port)(maintenance-information)

A timeout occurred during connection to the SMTP server.

(S)

Changes the status of the email sending job to Ended abnormally.

(O)

Confirm that the SMTP server name and port number in the profile are correct, and then re-execute the job.

KAVT3829-E

Connection to the SMTP server was refused. (SMTP-server-name:port)(maintenance-information)

Connection to the destination SMTP server was rejected.

(S)

Changes the status of the email sending job to Ended abnormally.

(O)

Check the following, and then re-execute the job:

Check whether the SMTP server name is correct.

Check whether the SMTP server communication port is correct.

Make sure that the SMTP server is not down.

Make sure that the communication port is not being blocked by a firewall.

KAVT3830-E

The SMTP server rejected the login. (SMTP-server-name:port, SMTP-AUTH-type)(maintenance-information)

The destination SMTP server rejected the login.

(S)

Changes the status of the email sending job to Ended abnormally.

(O)

Check the authentication method in the profile, the authentication account name, and the authentication password, and then re-execute the job.

KAVT3831-E

A timeout occurred during a connection to the POP3 server. (POP3-server-name:port)(maintenance-information)

A timeout occurred during a connection to the POP3 server.

(S)

Changes the status of the email sending job to Ended abnormally.

(O)

Confirm that the POP3 server name and port number in the profile are correct, and then re-execute the job.

KAVT3832-E

Connection to the POP3 server was refused. (POP3-server-name:port)(maintenance-information)

Connection to the destination POP3 server was refused.

(S)

Changes the status of the email sending job to Ended abnormally.

(O)

Check the following, and then re-execute the job:

Check whether the POP3 server name is correct.

Check whether the POP3 server communication port is correct.

Make sure that the POP3 server is not down.

Make sure that the communication port is not being blocked by a firewall.

KAVT3833-E

The POP3 server rejected the login. (POP3-server-name:port)(maintenance-information)

The POP3 server rejected the login.

(S)

Changes the status of the email sending job to Ended abnormally.

(O)

Check the authentication method in the profile, the authentication account name, and the authentication password, and then re-execute the job.

KAVT3834-E

The profile could not be read because it is corrupted. (profile-name)(maintenance-information)

The profile cannot be accessed because it is corrupted.

(S)

Cancels processing.

(O)

Use the jpomailprof command to delete the profile, and the re-create the profile.

KAVT3835-E

A desktop heap shortage occurred. (maintenance-information)

A desktop heap shortage occurred.

(S)

Cancels processing.

(O)

The email sending job might have terminated abnormally due to an insufficient desktop heap area.

See 4.2.3 Changing the JP1/AJS3 service settings (Windows only) in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide and, if necessary, change the JP1/AJS3 service account. In addition, take action such as checking the maximum number of concurrently executable jobs or the maximum number of processes started for all jobs to prevent desktop heap area shortages.

KAVT3836-E

Processing to send the email failed. (profile-name)(maintenance-information)

Processing to send the email failed.

The probable causes are:

The destination domain section contains an error.

The mail server is not running.

The authentication method defined in the profile contains an error.

Memory is insufficient.

A timeout occurred during processing of the email sending job.

(S)

Cancels processing.

(O)

Check the following, and then re-execute the job:

Check whether the destination domain section is correct.

Check whether the mail server is running.

Check whether the authentication method set on the mail server is the same as the authentication method defined in the profile.

Check whether memory is sufficient.

Check whether the timeout value specified for the EmbeddedMailTimeout environment setting parameter is appropriate.

For details about the authentication method defined in the profile, see jpomailprof (Windows only) in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVT3837-E

Failed to access (profile-name). (maintenance-information)

An error occurred during access to the profile indicated in (profile-name).

The probable causes are:

The specified profile name contains an error.

Administrator permissions set in the (profile-name) contain an error.

The jpomailprof command was executed to add, change, or delete the profile during execution of the email sending job.

(S)

Cancels processing.

(O)

Check the following, and then re-execute the command:

Check whether a profile with the same name as the specified profile name already exists.

Check whether there is sufficient free space on the disk.

Check whether Administrator permissions are set in the profile.

Make sure that the email sending job is not being executed.

KAVT3838-E

Failed to write (profile-name). (maintenance-information)

An attempt to write to the file indicated in profile-name has failed.

(S)

Cancels processing.

(O)

Check the following, and then re-execute the command:

Check whether there is sufficient free space on the disk.

Check whether Administrator permissions are set in the profile.

Make sure that the email sending job is not being executed.

KAVT3839-E

Failed to delete (profile-name). (maintenance-information)

An attempt to delete the profile indicated in (profile-name) failed.

(S)

Cancels processing.

(O)

Check the following, and then re-execute the command:

Check whether the correct profile name is specified.

Make sure that the email sending job is not being executed.

KAVT3840-E

The profile could not be created because the number of profiles exceeds the limit. (maintenance-information)

A profile cannot be created because the number of profiles exceeds the maximum.

(S)

Cancels processing.

(O)

Check the number of profiles.

KAVT3841-E

The profile (profile-name) is invalid. (maintenance-information)

The profile (profile-name) is invalid.

(S)

Cancels processing.

(O)

Characters that cannot be used were specified for the profile name.

Do not specify the following profile names:

Names that begin with a one-byte space symbol.

Names that contain only one period (.).

CON, PRN, AUX, CLOCK$, NUL, COM0, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT0, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9

KAVT3842-E

The profile could not be read because it is corrupted. (profile-name)(maintenance-information)

An attempt to read the profile failed because it is corrupted.

(S)

Cancels processing.

(O)

Use the jpomailprof command to delete the profile, and then re-create the profile.

KAVT3843-E

A desktop heap shortage occurred. (maintenance-information)

A desktop heap shortage occurred.

(S)

Cancels processing.

(O)

The jpomailprof command might have terminated abnormally due to an insufficient desktop heap area.

See 4.2.3 Changing the JP1/AJS3 service settings (Windows only) in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide and, if necessary, change the JP1/AJS3 service account. In addition, take action such as checking the maximum number of concurrently executable jobs or the maximum number of processes started for all jobs to prevent desktop heap area shortages.

KAVT3844-E

Failed to create the profile. (maintenance-information)

An attempt to create a profile failed.

(S)

Cancels processing.

(O)

Check the following, and then re-execute the command:

Check whether a process is accessing a file in the JP1/AJS3 installation folder.

Check whether memory is sufficient.

KAVT3845-E

An unexpected error occurred. (maintenance-information) (maintenance-information)

An unexpected error occurred in the email sending job.

(S)

Cancels processing.

(O)

Contact the system administrator.

KAVT3846-E

The list of attached files could not be acquired. (maintenance-information)

Acquiring an attached file list was impossible.

(S)

Cancels processing.

(O)

Check the following, and then re-execute the job:

Check whether the attached file list is correct.

Check whether the execution user permissions for the attached file list are correctly set.

KAVT3847-E

Failed to access (path). (maintenance-information)

An attempt to access the path indicated in path failed.

The probable causes are:

Administrator permissions set for the path contain an error.

Multiple jpomailprof commands were executed concurrently.

(S)

Cancels processing.

(O)

Check the following, and then re-execute the command:

Check whether administrator permissions are set for the path indicated in path.

Make sure that the jpomailprof command is not being executed.

KAVT3848-E

(profile-name) was not found. (maintenance-information)

The profile indicated in profile-name was not found.

(S)

Cancels processing.

(O)

Confirm that the profile name is correct, and then re-execute the command.

KAVT3849-E

An unexpected error occurred. (maintenance-information)

An unexpected error occurred in the command.

(S)

Cancels processing.

(O)

Contact the system administrator.

KAVT3850-E

The SMTP host name cannot be resolved. (host-name)(maintenance-information)

The SMTP host name cannot be resolved.

(S)

Cancels processing.

(O)

Set the hosts file on the agent host and DNS, and confirm that the correct IP address can be obtained by resolving the name, and then re-execute the job.

KAVT3851-E

The POP3 host name cannot be resolved. (host-name)(maintenance-information)

The POP3 host name cannot be resolved.

(S)

Cancels processing.

(O)

Set the hosts file on the agent host and DNS, and confirm that the correct IP address can be obtained by resolving the name, and then re-execute the job.

KAVT3852-E

The attached file could not be defined. (maintenance-information)

The attached file for the email could not be configured.

(S)

Cancels processing.

(O)

Check the following, and then re-execute the command:

Check whether the specified path to the attached file is correct.

Check whether the execution user permissions for the attached file are set correctly.

Make sure that no more than 20 files are specified in the attached file list.

KAVT4255-E

The data length is invalid. (data-name)

The character string length is invalid.

(S)

Cancels processing.

(O)

Check whether the data is correct.

KAVT4256-E

The specified file does not exist. (return-code)

The file does not exist.

(S)

Cancels processing.

(O)

Check whether the file is correct.

KAVT6001-I

The JP1 event send command has started.

The JP1 event send command starts.

(S)

Continues processing.

KAVT6002-I

The JP1 event send command ended.

The JP1 event send command terminates.

(S)

Continues processing.

KAVT6003-E

No event ID is specified.

No event ID is specified.

(S)

Cancels processing.

(O)

Check the definitions to see if an event ID is specified. When an event ID is specified, contact the system administrator.

KAVT6004-E

An error occurred in the event service. (return-code-of-jevsend-command)

An error occurred in the event service.

(S)

Cancels processing.

(O)

Find the cause of the error from the return code of the jevsend command, correct the error, and then retry.

KAVT6005-E

The installation path of JP1/Base could not be obtained.

The system could not obtain the directory to install JP1/Base. The registry information about Windows may be corrupted.

(S)

Cancels processing.

(O)

Check the registry information about JP1/Base. If the registry information is corrupted, reinstall JP1/Base and restart JP1/AJS3. Then, retry.

KAVT6006-E

Memory became insufficient.

Memory became insufficient.

(S)

Cancels processing.

(O)

Check whether there is sufficient memory for executing the program. Then, retry.

KAVT6100-E

Transmission of the JP1 event was not possible.

The system could not send a JP1 event.

(S)

Cancels processing.

(O)

Check whether JP1 events can be sent in the current environment. Check also whether a problem has occurred in the JP1/Base event service.

KAVT6101-E

Confirmation of JP1 event arrival was not possible.

The system checked JP1 event arrival for the specified number of times, but it could not confirm the arrival of any JP1 event.

(S)

Cancels processing.

(O)

Check whether JP1 events can be sent in the current environment. Check also whether a problem has occurred in the JP1/Base event service.

KAVT6102-I

Event sending host=event-destination-host-name

The system displays the name of the event transmission destination host. The system outputs this message only when it checks event arrival.

(S)

Continues processing.

KAVT6103-I

The JP1 event was able to transmit a message.

The JP1 event was transmitted.

(S)

Terminates processing.

KAVT6104-E

An attempt to acquire the event sending source host name (local-host-name) failed. maintenance-information

Since the name of the event transmission source host was not specified, the system assumed the local-host name to be the name of the event transmission source host. The system attempted to obtain the local-host name, but it failed.

(S)

Cancels processing.

(O)

Check whether the network settings are correct and whether the host name is specified correctly. If you cannot solve the problem, specify the event transmission destination host and then re-execute the operation.

KAVT7001-I

Timer monitoring process will now start.

The execution interval control process will now start.

(S)

Continues processing.

KAVT7002-I

Timer (timer-value min) monitoring will now start.

The timer monitoring starts.

(S)

Continues processing.

KAVT7003-I

Timer (timer-value min) is over.

The timer expired.

(S)

Terminates processing.

KAVT7004-I

Timer monitoring process will now end.

The execution interval control process will now terminate.

(S)

Terminates processing.

KAVT7005-W

The time-out period elapsed.

A timeout occurred. The system cancels executing the job.

(S)

Cancels processing.

KAVT7006-W

A kill request was accepted.

The system received a request to terminate the job forcibly, so it terminates the job forcibly.

(S)

Cancels processing.

KAVT7007-E

Timer monitoring process ended. (maintenance-information)

The execution interval control process terminated because it detected an error.

(S)

Terminated the process because an error that prevents further processing occurred during processing. An Interval Control job cannot be monitored.

(O)

The error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT7008-W

The memory for message output became insufficient. (maintenance-information)

Memory became insufficient. The message cannot be output to the detailed log.

(S)

Continues processing without outputting a message to the detailed log because memory is insufficient.

(O)

Check whether memory is sufficient.

For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT7009-E

Memory became insufficient. (maintenance-information)

Memory became insufficient. The job terminates.

(S)

Terminates the job abnormally due to insufficient memory.

(O)

Check whether there is sufficient memory for executing the program. Then, use JP1/AJS3 - View to examine the event job that caused the error, and then re-execute that job.

KAVT7010-E

An attempt to start the timer monitoring process failed. (maintenance-information) (maintenance-information)

An attempt to start the execution interval control process has failed.

(S)

Terminates the process because an error that prevents further processing occurred during startup of the execution interval control process. An Interval Control job cannot be monitored.

(O)

Make sure that resources are sufficient, and then restart JP1/AJS3.

KAVT7011-E

An attempt to obtain pipe data failed. (maintenance-information) (maintenance-information)

The execution interval control process terminates because an error occurred during inter-process communication with the agent process.

(S)

Terminates the execution interval control process because an error occurred during inter-process communication with the agent process. An Interval Control job cannot be monitored.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

After the check, restart JP1/AJS3.

KAVT7012-E

An attempt to send pipe data failed. (maintenance-information) (maintenance-information)

Interprocess communication with the agent has failed.

(S)

An error occurred during inter-process communication with the agent. The system terminates the execution interval control process depending on the location where the error occurred. If this process is terminated, the Interval Control job cannot be monitored. The Interval Control job may have failed to detect an event.

(O)

Check whether the system resources are sufficient and whether the directory created at JP1/AJS3 installation was unintentionally deleted. If the execution interval control process has started, use JP1/AJS3 - View to check the event job that caused the error, and then re-execute that job. If the execution interval control process has stopped, restart JP1/AJS3.

KAVT7013-E

An error occurred during the operation of a file. (maintenance-information) (maintenance-information)

An attempt to open the information file used for the execution interval control process has failed.

(S)

Cannot start monitoring for the job.

(O)

Check whether the system resources are sufficient and whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

After the check, use JP1/AJS3 - View to examine the event job that caused the error, and then re-execute that job.

KAVT7014-E

An error exists in the definition contents of the timer monitoring job. (maintenance-information) (LINE=maintenance-information)

The definition of the Interval Control job contains an error.

(S)

Abnormally terminates the Interval Control job because the definition of the job contains an error.

(O)

If the Interval Control job is specified so that monitoring expires immediately after it starts, confirm that the version of JP1/AJS3 that executes the Interval Control job is 10-00 or later. If the version of JP1/AJS3 is earlier than 10-00, specify the default executing agent @SYSTEM as the execution agent for the Interval Control job, and then re-execute the job.

KAVT7015-E

An attempt to set the next time monitoring failed. (maintenance-information) (maintenance-information)

The Interval Control job terminated abnormally because the system resources were insufficient.

(S)

Sufficient resources for performing the next monitoring are not available. The system abnormally terminates the Interval Control job.

(O)

Check the following:

Check whether system resources are sufficient.

After the check, use JP1/AJS3 - View to check the event job that caused the error, and then re-execute that job.

KAVT7016-W

A macro variable exceeds 4096 bytes.

A converted macro variable has exceeded 4,096 bytes.

(S)

Truncates the portion after the 4,096th byte and continues processing. The maximum value for macro variables is 4,096 bytes.

(O)

The portion of the macro variable exceeding the 4,096th byte is not passed to the succeeding jobnet or job. Check the status of the jobnet or job. If you find any problem, recheck the definition of the job.

KAVT7017-I

Timer (none condition) is over.

The Interval Control job terminated before the wait time expired because the option that causes monitoring to expire immediately after it starts is enabled for the Interval Control job.

(S)

Terminates processing.

KAVT7501-E

Invalid parameter specification. (specified-parameter)

An incorrect parameter is specified in the hp OpenView Status Report job.

(S)

Cancels processing.

(O)

Check the definition of the specified parameter, and then retry.

KAVT7502-E

Invalid environment variable specification. (specified-environment-variable)

An incorrect parameter is specified in the hp OpenView Status Report job.

(S)

Cancels processing.

(O)

Check the definition of the specified parameter, and then retry.

KAVT7503-E

Invalid data specification. (specified-data)

An incorrect parameter is specified in the hp OpenView Status Report job.

(S)

Cancels processing.

(O)

Check the definition of the specified parameter, and then retry.

KAVT7506-I

The status report will now start.

The status report starts.

(S)

Continues processing.

KAVT7507-I

The status report will now end.

The status report terminates.

(S)

Terminates processing.

KAVT7508-E

Could not report status. SNMP service is not installed.

The job failed to report the status because the SNMP service was not installed.

(S)

Cancels processing.

(O)

Install the SNMP service.

KAVT7509-E

Could not report status. SNMP service is not started.

The job failed to report the status because the SNMP service was not started.

(S)

Cancels processing.

(O)

Start the SNMP service.

KAVT7510-E

Could not report status. SNMP service community name is not established.

The job failed to report the status because the community name for the SNMP service was not specified.

(S)

Cancels processing.

(O)

Specify the community name for the SNMP service.

KAVT7511-E

The status could not be reported because the destination of the SNMP service trap was not specified.

The job failed to report the status because the trap destination was not specified for the SNMP service.

(S)

Cancels processing.

(O)

Specify the trap destination for the SNMP service.

KAVT7512-E

Failed to report status. (Code=code-for-status-report-error)

The status could not be reported.

(S)

Cancels processing.

(O)

If the code indicated in code-for-status-report-error is 10, check whether the hp OpenView Status Report job was executed by a JP1 user with superuser privileges...

If the code is other than 10, contact the system administrator.

KAVT7513-E

Error in status specification. (string-specified-as-status)

An incorrect status is specified.

(S)

Cancels processing.

(O)

Specify a correct status.

KAVT7514-I

The status was reported. (status=status-that-has-been-sent, info=additional-information-about-the-status)

The status was reported.

(S)

Terminates processing.

KAVT7515-E

Memory became insufficient.

The job will be terminated due to insufficient memory.

(S)

Terminates the job abnormally due to a memory shortage.

(O)

After making sure that sufficient memory is available for program execution, investigate the action job that caused the error in JP1/AJS3 - View and then re-execute the job.

KAVT8001-I

The common environment definition command will now start.

The common environment definition command starts.

(S)

Starts processing.

KAVT8002-I

The common environment definition command will now end.

The common environment definition command terminates.

(S)

Terminates the command.

KAVT8003-E

The parameter is specified incorrectly.

An incorrect parameter is specified.

(S)

Cancels processing.

(O)

Specify correct definition parameters, and then retry.

KAVT8004-E

The environment variable is specified incorrectly. (specified-environment-variable)

An incorrect environment variable is specified.

(S)

Cancels processing.

(O)

Check the status of the system resource, and then retry.

KAVT8005-E

The data is specified incorrectly. (specified-data)

Incorrect data is specified.

(S)

Cancels processing.

(O)

Check the definition parameter.

KAVT8007-E

The configuration definition could not be read. (error-code)

The system failed to write the configuration information.

(S)

Cancels processing.

(O)

Check whether the user has the superuser privilege.

KAVT8008-E

A required item is missing.

A required item is not specified.

(S)

Cancels processing.

(O)

Check whether all the required items are specified.

KAVT8009-I

The mail linkage setting was canceled.

The settings for the mail linkage were canceled.

(S)

Terminates the command.

KAVT8010-E

The parameter is specified incorrectly.

An incorrect parameter is specified.

(S)

Cancels processing.

(O)

Check whether the correct parameter is specified. Then, retry.

KAVT8011-E

You are not authorized to access the configuration definition. (error-code)

You are not authorized to access the configuration definition.

(S)

Cancels processing.

(O)

Check whether the environment is set up to access the configuration information, and then retry.

KAVT8012-E

The specified key does not exist in the configuration definition. (error-code)

The specified key does not exist in the configuration definition.

(S)

Cancels processing.

(O)

Check whether JP1/AJS3 is correctly installed.

KAVT8013-E

An unexpected error occurred. (error-code)

An unexpected error occurred.

(S)

Cancels processing.

(O)

Contact the system administrator.

KAVT8014-I

The message queue environment setting command will now start.

The command to set the environment of the message queue starts.

(S)

Continues processing.

KAVT8015-I

The message queue environment setting command will now end.

The command to set the environment of the message queue terminates.

(S)

Terminates the command.

KAVT8016-I

The MSMQ environment setting command will now start.

The command to set the environment of MSMQ starts.

(S)

Continues processing.

KAVT8017-I

The MSMQ environment setting command will now end.

The command to set the environment of MSMQ terminates.

(S)

Terminates the command.

KAVT8018-I

The mail environment setting command will now start.

The command to set the mail environment starts.

(S)

Continues processing.

KAVT8019-I

The mail environment setting command will now end.

The command to set the mail environment terminates.

(S)

Terminates the command.

KAVT8020-E

The specified data is not used on the current platform. (specified-data)

The specified data is not used for the current platform.

(S)

Cancels processing.

(O)

Check whether the data can be used in the current platform, and then retry.

KAVT8021-E

Environment setup did not end normally.

The setup of the environment terminated abnormally.

(S)

Terminates the command.

(O)

See the message output before this message to examine the cause of the error.

KAVT8022-E

For execution, you must have Administrator permissions.

The command must be executed by a user who has Administrator permissions.

(S)

Cancels processing.

(O)

Check the authority of the login user, and then retry.

KAVT8023-I

The message queue linkage settings were canceled.

The settings for the message queue linkage were canceled.

(S)

Terminates the command.

KAVT8024-I

The MSMQ linkage setting was canceled.

The settings for the MSMQ linkage were canceled.

(S)

Terminates the command.

KAVT8025-E

The data length is invalid. (error-code)

The data length is incorrect.

(S)

Cancels processing.

(O)

Check whether the data length is within the specifiable range.

KAVT8026-E

Memory became insufficient. (Maintenance-information)

Memory is insufficient.

(S)

Cancels processing.

(O)

Get enough memory to process and re-execute.

KAVT8027-E

The data length is invalid.(option)(maintenance-information)

The data length is incorrect.

(S)

Cancels processing.

(O)

Check whether the data length is within the specifiable range.

For the jpomailprof command, depending on the JP1/AJS3 installation path, it is possible for the profile name specified for the -n option to contain 64 or fewer bytes.

KAVT8107-E

Memory became insufficient.

Memory became insufficient.

(S)

Cancels processing.

(O)

Allocate sufficient memory for execution. Then, retry.

KAVT8301-I

The command terminated normally.

Listing terminated normally.

(S)

Terminates command execution.

KAVT8302-W

The command terminated abnormally.

The command terminated abnormally due to an error.

(S)

Terminates command execution.

(O)

See the message output before this message to examine the cause of the error and correct it. Then, re-execute the command.

KAVT8303-E

Value for option (option) is not specified.

A value is missing for the option that needs a value.

(S)

Cancels command execution.

(O)

Specify the value for the option, and then re-execute the command.

KAVT8304-E

Extra argument(s) exist.

An unnecessary argument exists.

(S)

Cancels command execution.

(O)

Delete the unnecessary argument, and then re-execute the command.

KAVT8305-E

Invalid value for option (option)

The option contains an invalid value.

(S)

Cancels command execution.

(O)

Correct the value for the option, and then re-execute the command.

KAVT8306-E

Option (option) appears twice or more.

The same option is specified more than once.

(S)

Cancels command execution.

(O)

Specify the option only once, and then re-execute the command.

KAVT8307-E

Cannot specify these options together.

You specified the options that could not be used simultaneously.

(S)

Cancels command execution.

(O)

Delete one or the other of the options, and then re-execute the command.

KAVT8308-E

Insufficient memory occurred. (maintenance-information)

Memory became insufficient.

(S)

Cancels command execution.

(O)

Check whether there is sufficient memory.

KAVT8310-W

Because the data was long, the data was truncated and then displayed. (data-truncated (up-to-900-bytes)) (name-of-the-item-displayed)

The data to be displayed was unexpectedly long. The data is truncated and then displayed.

(S)

Continues command execution.

(O)

Check whether JP1/AJS3 runs correctly.

KAVT8311-W

The deleting of files failed. (maintenance-information)

The work file could not be deleted during termination.

(S)

Continues command execution.

(O)

Delete the sys_bak folder (directory) under the folder (directory) that stores the work file.

KAVT8312-E

The copying of files failed. (maintenance-information)

The file could not be opened.

(S)

Cancels command execution.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

This message is output to the standard error output file if you execute the jpomanjobshow command in a system where no event jobs or start conditions have been executed. In this case, ignore the message and continue operation.

KAVT8313-W

An error occurred during the access of job data. (error-code) (function-name) (maintenance-information)

An error occurred while accessing the database.

(S)

Continues command execution. The system cannot display the name of the appropriate job and its jobnet name.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

If maintenance is in progress, wait until the maintenance finishes and then re-execute the command.

KAVT8314-E

An error occurred during communication with the agent. (error-code) (function-name) (maintenance-information)

Pipes could not be created in, written into, or read from the agent.

(S)

Cancels command execution.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

For a cluster system, make sure that the command is not executed in the standby system, and then re-execute the command in the active system.

KAVT8315-W

An error occurred during communication with the monitoring process. (error-code) (function-name) (maintenance-information)

Pipes could not be created in, written into, or read from the monitoring process.

(S)

Continues command execution. The system may not display Status correctly.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8316-E

An error occurred during the access of the agent information file. (error-code) (function-name) (maintenance-information)

An error occurred while accessing (opening, etc.) the information file of the agent.

(S)

Cancels command execution.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8317-W

An error occurred during the access of the monitoring process information file. (error-code) (function-name) (maintenance-information)

An error occurred while accessing (opening, etc.) the information file of the monitoring process.

(S)

Continues command execution. The system may not display Status correctly.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8319-E

For execution, you must have Administrator permission.

You are not logged on as a user with the Administrators permission.

(S)

Cancels command execution.

(O)

Log on as a user with the Administrators permission, and then retry.

If the UAC function is enabled in Windows, the administrator must re-execute the command.

KAVT8320-E

The host name could not be obtained. (error-code) (function-name) (maintenance-information)

The host name could not be obtained.

(S)

Cancels command execution.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether JP1/AJS3 and JP1/Base have been installed correctly.

Check whether the environment of JP1/AJS3 and JP1/Base have been set correctly.

KAVT8321-E

The installation path could not be acquired.

The installation path could not be acquired.

(S)

Cancels command execution.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether JP1/AJS3 and JP1/Base have been installed correctly.

Check whether the environment of JP1/AJS3 and JP1/Base have been set correctly.

KAVT8322-E

The configuration definition could not be read.

The configuration definitions could not be read.

(S)

Cancels command execution.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether JP1/AJS3 and JP1/Base have been installed correctly.

Check whether the environment of JP1/AJS3 and JP1/Base have been set correctly.

KAVT8323-E

The registration file could not be read. (path-name) (function-name) (maintenance-information)

The registration file could not be read.

(S)

Cancels command execution.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8324-W

The definition information file could not be read. (error-code) (function-name) (maintenance-information)

The definition information file could not be read.

(S)

Continues command execution. The system may not display some data.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8325-W

The unreported information file could not be read. (function-name) (maintenance-information)

The agent-unreported information file could not be read.

(S)

Continues command execution. The system may not display the information correctly.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8327-W

There is no data so data cannot be displayed. (name-of-the-item-displayed) (maintenance-information)

There is no data of the requested value. The data cannot be displayed.

(S)

Continues command execution.

(O)

Check whether the JP1/AJS3 service has been started or whether maintenance is being performed on the service.

KAVT8328-E

There is no specified host name. (host-name) (function-name)

There is no host name that is specified by the -h operand or the JP1_HOSTNAME environment variable.

(S)

Cancels command execution.

(O)

Check whether there is the host name specified or the environment of JP1/AJS3 is set correctly.

KAVT8329-E

The exclusion information could not be obtained. (error-code) (function-name)

The exclusion information could not be obtained.

(S)

Cancels command execution.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8330-E

Exclusion failed. (error-code) (function-name)

A lock could not be completed when one of the following commands was executed:

jpoagtjobshow

jpomanevreset

jpomanevshow

jpomanjobshow

(S)

Cancels command execution.

(O)

Check the following, and then re-execute the command:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

Check whether an attempt was made to concurrently execute more than one command with the same name.

For a cluster system, check whether the command was executed on the standby node.

For a cluster system, re-execute the command on the primary node.

KAVT8331-W

Deletion of the exclusion file failed. (error-code) (function-name)

The exclusion file could not be deleted during termination.

(S)

Cancels command execution.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8332-E

Exclusion is being applied. (error-code) (function-name)

A lock is being applied by execution of one of the following commands:

jpoagtjobshow

jpomanevreset

jpomanevshow

jpomanjobshow

(S)

Cancels command execution.

(O)

Check whether an attempt was made to concurrently execute more than one command with the same name. Wait until execution of the preceding command terminates, and then re-execute the command.

KAVT8333-E

The agent is not running.

The agent has not been started.

(S)

Cancels command execution.

(O)

Check whether the agent has been started. Restart JP1/AJS3 as required.

For a cluster system, make sure that the command is not executed in the standby system, and then re-execute the command in the active system.

KAVT8334-E

The manager name storage file could not be created. (error-code) (function-name) (maintenance-information)

The manager name storage file could not be created or written into.

(S)

Cancels command execution.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8335-E

A contradiction was detected during communication.

The event job information which differs from the one acquired by the command is detected.

(S)

Cancels command execution.

(O)

Collect data about this internal error and then contact the system administrator.

KAVT8336-E

Some agent information could not be written.

Some agent information could not be written.

(S)

Lists the event jobs (the system may not display some data), and then abnormally terminates the command.

(O)

Use the integrated trace log to determine the cause of the error which prevented the information to be written and take action to correct it.

KAVT8337-W

Some monitoring process information could not be written. (monitoring-process-name)

Some information about the monitoring process could not be written.

(S)

Continues command execution. The system may not display Status correctly.

(O)

Use the integrated trace log to determine the cause of the error which prevented the information to be written and take action to correct it.

KAVT8338-E

None of the agent information could be written.

None of the agent information could not be written.

(S)

Cancels command execution.

(O)

Use the integrated trace log to determine the cause of the error which prevented the information to be written and take action to correct it.

KAVT8339-W

None of the monitoring process information could be written. (monitoring-process-name)

None of the monitoring process information could be written.

(S)

Continues command execution. The system may not display Status correctly.

(O)

Use the integrated trace log to determine the cause of the error which prevented the information to be written and take action to correct it.

KAVT8340-E

The main loop of the jpoagtjobshow command failed. (maintenance-information)

The main loop of the jpoagtjobshow command could not be started.

(S)

Cancels command execution.

(O)

Check whether the system resource is sufficient or the privilege of the user is valid. Then, retry.

KAVT8341-E

This command cannot be executed because the JP1/AJS2 service is running.

This command cannot be executed because the target JP1/AJS3 scheduler service is running.

(S)

Cancels execution of the command.

(O)

Stop the target JP1/AJS3 scheduler service, and then re-execute the command.

KAVT8342-E

A file access error occurred. (file-name) (maintenance-information)

An error occurred during access to the file indicated in file-name.

(S)

Performs different operations depending on the executed command.

jpomanevreset command

Continues execution of the command. However, the following may occur:

Unnecessary files remain.

Information on the agent is not deleted.

jpomanevshow command

Cancels execution of the command.

(O)

Take appropriate action depending on the executed command.

jpomanevreset command

Do the following:

Check the file indicated in the message. If the file still remains, you must delete it manually before starting JP1/AJS3. If neither remove nor DeleteFile is contained in maintenance-information, do not delete the file. Instead, correct the cause of unsuccessful access to the file, and then re-execute the command.

If you did not specify the -s option, information may still remain on the agent. Perform a cold start manually for JP1/AJS3 on the agent.

jpomanevshow command

Check the following and then re-execute the command:

Check whether the system resources are sufficient.

Check whether the permission environment of the starting user is correct.

Check whether the directory created during installation of JP1/AJS3 was deleted unintentionally.

KAVT8343-W

An attempt to communicate with the agent has failed. (agent-host-name) (maintenance-information, IPAddress=IP-address#)

An attempt to communicate with the agent indicated in agent-host-name has failed.

#

The IP address is output only when the LOGIPV6INFOALL environment setting parameter is set to yes. If the LOGIPV6INFOALL environment setting parameter is set to yes and the IP address is unknown, unknown is displayed.

(S)

Continues execution of the command. Note, however, that information about the agent host indicated by agent-host-name is not deleted.

(O)

Check the following:

Check whether the JP1/AJS3 service on the agent host is running or whether the agent host machine is running.

If JP1/AJS3 on the agent host and the agent host itself are not running, start them.

Check whether the host name is determined.

If the host name could not be determined (resolved), check the JP1_HOSTNAME environment variable, hosts file, DNS settings, or settings in jp1hosts or jp1hosts2 information on the manager host.

Check whether the JP1/AJS3 port number is registered in the services file.

If it is not registered, register it.

Because information about the agent where an error occurred is not deleted, perform a cold start for the JP1/AJS3 service on the agent host indicated by agent-host-name.

KAVT8347-E

A required option (option) is missing.

A required option was omitted.

(S)

Cancels execution of the command.

(O)

Specify the required option indicated in the message and then re-execute the command.

KAVT8351-E

Specified Scheduler service not exist (scheduler-service-name)(maintenance-information).

The scheduler service specified for the -F operand or the DEFAULTSERVICENAME environment setting parameter does not exist.

(S)

Cancels command execution.

(O)

Check whether:

The scheduler service specified in the -F option, AJSCONF environment variable, or DEFAULTSERVICENAME environment setting parameter exists on the host specified for the -h option.

The JP1/AJS3 environment settings are correct.

KAVT8352-E

Shared memory is not available(maintenance-information).

Shared memory required for command execution is not available.

(S)

Cancels command execution.

(O)

Check whether:

The JP1/AJS3 host service is running.

System resources (shared memory) are sufficient.

KAVT8401-E

The initialization of communication with the jpoagtjobshow command failed. (return-code) (line-number)

The communication with the jpoagtjobshow command could not be initialized.

(S)

Continues processing. The system cannot provide the information for the jpoagtjobshow command.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

If you want to display the correct information using the jpoagtjobshow command, restart JP1/AJS3.

KAVT8402-E

The reading of requests from the jpoagtjobshow command failed. (return-code)

Requests could not be read from the pipes for the jpoagtjobshow command.

(S)

Continues processing. The system cannot provide the information for the jpoagtjobshow command.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

If you want to display the correct information using the jpoagtjobshow command, re-execute the command.

KAVT8403-E

A request from jpoagtjobshow command is invalid. (maintenance-information)

Unexpected data was written from the jpoagtjobshow command.

(S)

Continues processing. The system cannot provide the information for the jpoagtjobshow command.

(O)

Collect data about this internal error and then contact the system administrator. If you want to display the correct information using the jpoagtjobshow command, re-execute the command.

KAVT8404-E

The creation of information sent to the jpoagtjobshow command failed. (return-code) (line-number)

The information file could not be created for the jpoagtjobshow command.

(S)

Continues processing. The system cannot provide the information for the jpoagtjobshow command.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

If you want to display the correct information using the jpoagtjobshow command, re-execute the command.

KAVT8405-E

The reporting of information to the jpoagtjobshow command failed. (return-code)

Pipes could not be written into the jpoagtjobshow command.

(S)

Continues processing. The system cannot provide the information for the jpoagtjobshow command.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

If you want to display the correct information using the jpoagtjobshow command, re-execute the command.

KAVT8406-W

The creation of the information to be sent to the jpoagtjobshow command is incomplete. (return-code) (line-number)

Job information could not be written when creating the information file for the jpoagtjobshow command.

(S)

Continues processing. The system cannot provide the complete information for the jpoagtjobshow command.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the privilege of the user is valid.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

If you want to display the correct information using the jpoagtjobshow command, re-execute the command.

KAVT8408-E

There is no logical host name in the environment variable.(return-code)(line-number)

A logical host name is not set for the JP1_HOSTNAME environment variable.

(S)

Cancels command execution.

(O)

Set a logical host name for the JP1_HOSTNAME environment variable, and then re-execute the command.

KAVT8410-E

An attempt to obtain the environmental setting parameter information failed.(return-code)(line-number)

An attempt to obtain environment setting parameter information has failed.

(S)

Cancels command execution.

(O)

Check the following, and then re-execute the command:

Check whether the environment setting parameters for JP1/AJS3 and JP1/Base are specified correctly.

Check whether memory is sufficient.

If memory is insufficient, see 3. Estimates in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide, and make sure that the required amount of memory has been allocated.

KAVT8411-W

An attempt to move then environmental setting parameter failed.(return-code)(line-number)

Migration processing for the environment setting parameters has failed.

(S)

Continues processing. Note, however, that the system terminates migration processing abnormally.

(O)

Check whether the environment setting parameters for JP1/AJS3 and JP1/Base are specified correctly.

Specify the environment setting parameters correctly, and then re-execute the command.

KAVT8412-W

An attempt to create the key of an environmental setting parameter failed.(keyname=key-name)(return-code)(line-number)

An attempt to create a key for the environment setting parameters has failed.

(S)

Continues processing. Note, however, that the system terminates migration processing abnormally.

(O)

Check whether there is an upper-level key for the key that could not be created.

If there is no upper-level key, create it and then re-execute the command.

KAVT8413-E

An attempt to obtain the file name failed.(return-code)(line-number)

An attempt to obtain the file name has failed.

(S)

Cancels command execution.

(O)

Check the following, and then re-execute the command:

Check whether the directory created by JP1/AJS3 during installation has been improperly deleted.

Check whether memory is sufficient.

If memory is insufficient, see 3. Estimates in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide, and make sure that the required amount of memory has been allocated.

KAVT8415-E

An attempt to move the file failed.(filename=file-name)(return-code)(line-number)

Migration processing for the internal file to be used for the event/action control has failed.

(S)

Continues processing. Note, however, that the system terminates migration processing abnormally.

(O)

Check the following:

For a physical host, check whether the disk that contains the JP1/AJS3 installation directory has sufficient free space. Also check whether the installation directory can be accessed.

For a logical host, check whether the shared disk has sufficient free space and can be accessed.

Check whether memory is sufficient.

Check whether the directory created during installation of JP1/AJS2 has been deleted illegally.

Check whether the file for which migration failed is in the migration source.

If this file is in the migration source (JP1/AJS2 system file directory), delete the file and then re-execute the command.

Check whether an asterisk (*) is displayed for file-name in the message.

If an asterisk (*) is displayed for file-name in the message, delete the EVaction_backup directory from the tmp directory in the JP1/AJS2 installation directory, and then re-execute the command.

For other cases, correct the error and then re-execute the command.

KAVT8416-W

The file to be moved is invalid.(filename=file-name)(return-code)(line-number)

The data format of the file to be moved is invalid.

(S)

Renames the file to a name suffixed with _bak, and continues migration processing.

(O)

After setup of the standard configuration has been completed, take the following actions:

For all the scheduler services, execute the jpomanevreset command with the -all option specified.

Cold start the JP1/AJS3 service.

For details on the jpomanevreset command, see jpomanevreset in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVT8417-W

An attempt to back up an invalid file failed.(filename=file-name)(return-code)(line-number)

When the KAVT8416-W message was output, an attempt to rename the file with an invalid data format to a name suffixed with _bak failed.

(S)

Continues migration processing.

(O)

See the corrective actions given for the KAVT8416-W message.

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

This chapter explains the messages beginning with KAVU (messages about the job execution control).

5.1 List of messages beginning with KAVU

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, KAVU4333-W, KAVU4334-E, 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)

Check the access permissions for the transfer source file.

In addition, check the access permissions for the specified file as well as for each directory up to the highest-level directory.

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 7.9.1 Changing the name of the host that runs JP1/AJS3 in the JP1/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, flexible job#, HTTP connection job, action job, or custom job:

ajsagtadd command

#

For a flexible job, replace agent with relay agent.

- 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 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference and 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

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, flexible job#, HTTP connection 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 flexible job, replace execution agent with relay agent.

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 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

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

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 JP1/Automatic Job Management System 3 Command Reference. For details about how to set JP1 permission levels, see 3.1.1(1) Setting user information in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows) or 13.1.1(1) Setting user information in the JP1/Automatic Job Management System 3 Configuration Guide (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 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

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 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

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.

(O)

You can ignore this error message if the message is output when the conditions below are met. If this error message is output when the conditions below are not met, check to see if any error message is output before or after this message. If an error message is output, refer to the described solutions.

Stops the JP1/AJS3 service.

Stops the scheduler service.

KAVU6101-I is output before or after this message.

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, KAVU2229-E, or KAVU2231-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.

#

Indicates the file path for the specified file as well as for each directory up to the highest-level directory.

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 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide and 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.

KAVU0271-E

function-name:A QUEUE job with a host name(host-name) specified cannot be executed.

If the communication encryption function is enabled, a QUEUE job with a host name specified cannot be executed.

(S)

Cancels the requested processing.

(O)

To execute a QUEUE job on the local host, make sure that the Host name field in the detailed definition is left blank.

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.

(O)

Log files are automatically deleted, starting from the oldest log files, when the number of log files exceeds the number of logs to keep. No action is needed.

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.

(O)

Log files are automatically deleted, starting from the oldest log files, when the number of log files exceeds the number of logs to keep. No action is needed.

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, flexible job#, HTTP connection job, action job, or custom job:

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

#

For a flexible job, replace agent host with relay agent.

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 9.2.2 Reorganizing a database in the JP1/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 20.4.2(56) AJSTMPDIR in the JP1/Automatic Job Management System 3 Configuration Guide.

#

Indicates the file path for the specified file as well as for each directory up to the highest-level directory.

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 20.4.2(56) AJSTMPDIR in the JP1/Automatic Job Management System 3 Configuration Guide.

#

Indicates the file path for the specified file as well as for each directory up to the highest-level directory.

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)

Check the access permissions for the transfer source file.

In addition, check the access permissions for the specified file as well as for each directory up to the highest-level directory.

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.

#

Check the access permissions for the specified file as well as for each directory up to the highest-level directory.

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.

#

Indicates the file path for the specified file as well as for each directory up to the highest-level directory.

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 JP1/Automatic Job Management System 3 Command Reference.

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 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

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 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

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 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

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 JP1/Automatic Job Management System 3 Command Reference. For details about how to set JP1 permission levels, see 3.1.1(1) Setting user information in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows) or 13.1.1(1) Setting user information in the JP1/Automatic Job Management System 3 Configuration Guide (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 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

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 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

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 JP1/Automatic Job Management System 3 Command Reference.

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 JP1/Automatic Job Management System 3 Command Reference.

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 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

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 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

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

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 JP1/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 JP1/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 JP1/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.

#

Check the access permissions for the specified file as well as for each directory up to the highest-level directory.

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.

#

Check the access permissions for the specified file as well as for each directory up to the highest-level directory.

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 access permissions for the work path.

In addition, check the access permissions for the specified file as well as for each directory up to the highest-level directory.

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.

A large number of job-start and job-end notifications are output in a short period.

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 JP1/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.

If there is no problem with the network, and this error occurred because a large number of jobs to be executed are concentrated in a short period, take action such as distributing the number of jobs to be executed during the period. Such an action will prevent a large number of job-start and job-end notifications from being output in a short period. Generally, this error might occur when 50 or more jobs are executed per second for the physical or logical host of the manager.

To check the number of jobs that were executed in the short period during which a large number of job-start and job-end notifications were output, check the number of KAVS0263-I messages that were output to the scheduler log file during the corresponding period.

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 JP1/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 timeout period, interval of retries, and number of retries for TCP/IP connections in the JP1/Automatic Job Management System 3 Configuration Guide (for hosts under Windows), or 15.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections in the JP1/Automatic Job Management System 3 Configuration Guide (for hosts under UNIX).

This error might occur if a larger number of job-start and job-end notifications are output in a short period. If there is no problem with the network, and this error occurred because a large number of jobs to be executed are concentrated in a short period, take action such as distributing the number of jobs to be executed during the period. Such an action will prevent a large number of job-start and job-end notifications from being output in a short period. Generally, this error might occur when 50 or more jobs are executed per second for the physical or logical host of the manager.

To check the number of jobs that were executed in the short period during which a large number of job-start and job-end notifications were output, check the number of KAVS0263-I messages that were output to the scheduler log file during the corresponding period.

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. The probable causes are:

JP1/AJS3 at the connection destination terminated abnormally during communication.

The IP address of the host issuing the request became invalid and unusable.

In a cluster configuration, node switching occurred, causing JP1/AJS3 to be terminated forcibly.

(S)

Cancels the requested processing.

(O)

Check the following items, and then correct the cause of the error. After that, restart JP1/AJS3 if it is stopped, and then reissue the request.

Status of JP1/AJS3 on the connection destination host

Status of the IP address of the host issuing the request

Contents of integrated trace log

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 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. The probable causes are:

JP1/AJS3 at the connection destination terminated abnormally during communication.

The IP address of the host issuing the request became invalid and unusable.

In a cluster configuration, node switching occurred, causing JP1/AJS3 to be terminated forcibly.

(S)

Cancels the requested processing.

(O)

Check the following items, and then correct the cause of the error. After that, restart JP1/AJS3 if it is stopped, and then reissue the request.

Status of JP1/AJS3 on the connection destination host

Status of the IP address of the host issuing the request

Contents of integrated trace log

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 JP1/Automatic Job Management System 3 Configuration Guide (for hosts under Windows), or 15.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (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)

Continues processing.

(O)

No action is required. However, if this message is output even after processing continues, 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.

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)

Continues processing.

(O)

No action is required. However, if this message is output even after processing continues, a problem might have occurred in the name service. Check the status of the local host, such as by using the jp1ping command, 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)

Continues processing.

(O)

No action is required. However, if this message is output even after processing continues, an error might have occurred in the network subsystem. Check the status of the network 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)

Continues processing.

(O)

No action is required.

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 JP1/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.

KAVU2249-I

Communication will no longer be retried, because processing to stop the process will now begin.

The running communication retry is canceled because a process stop request was received.

(S)

The running communication retry processing is canceled to start the process stop processing.

KAVU2250-E

An attempt to verify the server certificate failed.(logical-host-name, name-of-host-to-be-connected, maintenance-information)

An attempt to verify the server certificate sent from the connection destination failed. The probable causes are as follows:

The connection destination host name does not match the CN or SAN.

The root certificate corresponding to the server certificate is not contained in the file specified for CACERTIFICATEFILE in the JP1/Base common definition information.

The current time of the machine in which the error occurred is earlier than the start time of the effective period specified in the server certificate.

The server certificate and the intermediate certificate are joined in an incorrect order.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Cancels communication processing, and then continues subsequent processing.

(O)

If the connection destination host name does not match the CN or SAN:

Match the connection destination host name to the CN or SAN.

If the root certificate corresponding to the server certificate is not contained in the file specified for CACERTIFICATEFILE in the JP1/Base common definition information:

Add the corresponding root certificate to the file specified for CACERTIFICATEFILE in the common definition information.

If the current time of the machine in which the error occurred is earlier than the start time of the effective period specified in the server certificate:

Retry the operation after the start time of the effective period specified in the server certificate.

If the server certificate and the intermediate certificate are joined in an incorrect order:

Join the server certificate and the intermediate certificate in the correct order.

KAVU2251-E

An error occurred in SSL communication processing.(logical-host-name, name-of-host-to-be-connected, maintenance-information)

An error occurred during SSL communication processing. The probable causes are as follows:

The communication encryption function is disabled at the connection destination.

A temporary communication error occurred.

If this message is output at the reception side of TCP/IP communication, a null character string is output for connection-destination-host-name.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Cancels communication processing, and then continues subsequent processing.

(O)

If the communication encryption function is disabled at the connection destination:

Enable the communication encryption function for the host indicated in connection-destination-host-name.

If a temporary communication error occurred:

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

KAVU2252-W

The certificate has expired.(logical-host-name, name-of-host-to-be-connected)

The server certificate sent from the connection destination or the root certificate located on the local host has expired.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Continues processing.

(O)

Acquire a new certificate, and replace the expired certificate with it.

KAVU2260-I

The maximum limit(maximum-value(number-of-bytes))of the total file size for the reception processing of result files, i.e. STANDARD-OUTPUT-FILE and STANDARD-ERROR-FILE was reached, but all file data will be received. (job number: job-number)

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 that you reduce the size of the result file (standard output file or standard error output file) specified for the job. The recommended file size is smaller than the maximum size of sent files (value set in the LimitSendFileSize environment setting parameter) and the maximum size of received files (value set in the LimitReceiveFileSize environment setting parameter).

For details about the maximum size of sent files, see 6.2.27 Placing restrictions on file transmission in the JP1/Automatic Job Management System 3 Configuration Guide (in Windows) or 15.2.24 Placing restrictions on file transmission in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

For details about the maximum size of received files, see 6.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (in Windows) or 15.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

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

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.

#

Indicates the file path for the specified file as well as for each directory up to the highest-level directory.

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.

#

Indicates the file path for the specified file as well as for each directory up to the highest-level directory.

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.

#

Indicates the file path for the specified file as well as for each directory up to the highest-level directory.

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.

#

Indicates the file path for the specified file as well as for each directory up to the highest-level directory.

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.10.1 Notes on the standard output file and standard error output file in the JP1/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 JP1/Automatic Job Management System 3 Configuration Guide (for hosts under Windows), or 15.2.6 Preventing duplicated reception of job result files in the JP1/Automatic Job Management System 3 Configuration Guide (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 20.5 Setting up the job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

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.10.1 Notes on the standard output file and standard error output file in the JP1/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 20.5 Setting up the job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

(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 JP1/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.

KAVU3507-I

The total file size of the result files (standard-output-file-name, standard-error-file-name) of a job (job-number, manager-host-name) exceeded the limit(maximum-value(number-of-bytes))for sending files.

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 that you reduce the size of the result file (standard output file or standard error output file) specified for the job. The recommended file size is smaller than the maximum size of sent files (value set in the LimitSendFileSize environment setting parameter) and the maximum size of received files (value set in the LimitReceiveFileSize environment setting parameter).

For details about the maximum size of sent files, see 6.2.27 Placing restrictions on file transmission in the JP1/Automatic Job Management System 3 Configuration Guide (in Windows) or 15.2.24 Placing restrictions on file transmission in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

For details about the maximum size of received files, see 6.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (in Windows) or 15.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

Cautionary note

If the standard output file or standard error output file is not specified in the job definition, no file name is output in the message. However, if the standard error output file is not defined and you execute a job by using a jobnet, a temporary file of the standard error output file is created and transferred to the manager host. At this time, A_JPQSTDE_*_job-number is indicated in standard-error-output-file-name. Take action according to 7.10.1 Notes on the standard output file and standard error output file in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

KAVU3508-I

The total file size of the result files (standard-output-file-name, standard-error-file-name) of a job(job-number, manager-host-name)exceeded the limit(maximum-value(number-of-bytes))for sending files.

The result file size exceeds the maximum.

(S)

Sends the result file up to the maximum send size.

(O)

Reduce the amount of standard output and standard error output for the job. Then, if you need information in 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. Then, confirm that the result file size is smaller than the maximum size of sent files (value of the LimitSendFileSize environment setting parameter) and the maximum size of received files (value of the LimitReceiveFileSize environment setting parameter). Alternatively, revise the maximum file size.

For details about the maximum size of sent files, see 6.2.27 Placing restrictions on file transmission in the JP1/Automatic Job Management System 3 Configuration Guide (in Windows) or 15.2.24 Placing restrictions on file transmission in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

For details about the maximum size of received files, see 6.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (in Windows) or 15.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

Cautionary note

If the standard output file or standard error output file is not specified in the job definition, no file name is output in the message. However, if the standard error output file is not defined and you execute a job by using a jobnet, a temporary file of the standard error output file is created and transferred to the manager host. At this time, A_JPQSTDE_*_job-number is indicated in standard-error-output-file-name. Take action according to 7.10.1 Notes on the standard output file and standard error output file in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

KAVU3509-W

The status of a job(job-number, manager-host-name) changed to warning end because the total file size of the result files of the job exceeded the limit for sending files.

The status of the job changes to Ended with warning because the result file size exceeded the maximum.

(S)

Sends the result file up to the maximum send size.

(O)

Reduce the amount of standard output and standard error output for the job. Then, if you need information in 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. Then, confirm that the result file size is smaller than the maximum size of sent files (value of the LimitSendFileSize environment setting parameter) and the maximum size of received files (value of the LimitReceiveFileSize environment setting parameter). Alternatively, revise the maximum file size.

For details about the maximum size of sent files, see 6.2.27 Placing restrictions on file transmission in the JP1/Automatic Job Management System 3 Configuration Guide (in Windows) or 15.2.24 Placing restrictions on file transmission in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

For details about the maximum size of received files, see 6.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (in Windows) or 15.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

KAVU3510-E

The status of a job(job-number, manager-host-name) changed to warning end because the total file size of the result files of the job exceeded the limit for sending files.

The status of the job changes to Ended abnormally because the result file size exceeded the maximum.

(S)

Sends the result file up to the maximum send size.

(O)

Reduce the amount of standard output and standard error output for the job. Then, if you need information in 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. Then, confirm that the result file size is smaller than the maximum size of sent files (value of the LimitSendFileSize environment setting parameter) and the maximum size of received files (value of the LimitReceiveFileSize environment setting parameter). Alternatively, revise the maximum file size.

For details about the maximum size of sent files, see 6.2.27 Placing restrictions on file transmission in the JP1/Automatic Job Management System 3 Configuration Guide (in Windows) or 15.2.24 Placing restrictions on file transmission in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

For details about the maximum size of received files, see 6.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (in Windows) or 15.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

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.10.1 Notes on the standard output file and standard error output file in the JP1/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.10.1 Notes on the standard output file and standard error output file in the JP1/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 20.5 Setting up the job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

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.10.1 Notes on the standard output file and standard error output file in the JP1/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.10.1 Notes on the standard output file and standard error output file in the JP1/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 20.5 Setting up the job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

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 20.5 Setting up the job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

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 20.5 Setting up the job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

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 JP1/Automatic Job Management System 3 Configuration Guide.

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 JP1/Automatic Job Management System 3 Configuration Guide is enabled. If it is enabled, enable the setting described in 6.2.17 Reusing access tokens for job execution in the JP1/Automatic Job Management System 3 Configuration Guide.

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. Specify a file in %systemroot%\sysnative instead of %systemroot%\system32, and then re-execute the job.

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 JP1/Automatic Job Management System 3 Configuration Guide.

#

Indicates the file path for the specified file as well as for each directory up to the highest-level directory.

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 20.5 Setting up the job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

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.

#

Indicates the file path for the specified file as well as for each directory up to the highest-level directory.

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, there is no 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.

#

Indicates the file path for the specified file as well as for each directory up to the highest-level directory.

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 20.5 Setting up the job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

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 JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

For details on how to set up user mapping, see 3. Setup in the JP1/Automatic Job Management System 3 Configuration Guide (for hosts under Windows)or 13. Setup in the JP1/Automatic Job Management System 3 Configuration Guide (for hosts under UNIX).

For details on the JP1/AJS3 commands, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

For details about the JP1/Base commands, see the JP1/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 probable causes are:

- The size of the environment variable statement specified in the environment variable or environment variable file name might exceed the upper limit of environment-variable character strings permitted by the OS. Review the environment variable statement specified in the environment variable or environment variable file name.

- An invalid format of environment variable statement might be specified in the environment variable or environment variable file name. Use the following format to specify an environment variable statement in the environment variable or environment variable file name.

Example: environment-variable-name = value<return>

For example, if only an environment name, without a value, is specified as an environment variable statement in the environment variable or environment variable file name, the OS determines it as an invalid format, and the job ends abnormally.

Example: environment-variable-name<return>

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 JP1/Automatic Job Management System 3 Configuration Guide.

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 20.5 Setting up the job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

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 JP1/Automatic Job Management System 3 Configuration Guide is enabled. If it is enabled, enable the setting described in 6.2.17 Reusing access tokens for job execution in the JP1/Automatic Job Management System 3 Configuration Guide.

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.

The execution OS user requires superuser privileges if an execution priority of 4 or 5 is specified for any of the following:

Unix job

HTTP connection job executed on a Linux host

Upper-level jobnet of a flexible job

(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)(c) Privileges for running JP1/AJS3 services under a user account in the JP1/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 or a job process execution ready notification.

(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 job priority is low.

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 long timeout period for pipe communication on the host where the agent process is executed, and specify a timeout value for a job process execution ready notification. In case of Cause No. 4, 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 for the execution priority of jobs, see 7.10.2 Notes on the execution priority of jobs in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

If the same timeout value is specified for pipe communication in a job execution process and a job process execution ready notification, errors can be determined by the following process names that output the KAVU3589-E message to the integrated trace log:

If the jpqagtchild process outputs the message, an error occurred in pipe communication in a job execution process.

If the jpqagt or jpqagtdmn process outputs the message, an error occurred in a job process execution ready notification.

For details on how to change a timeout value for pipe communication of 1, 15.2.15 Changing the timeout value for pipe communication of the agent in the JP1/Automatic Job Management System 3 Configuration Guide.

For details on how to change the timeout value for receiving notification from the job process that execution of 2. is ready, 15.2.16 Setting the timeout value for receiving notification from the job process that execution is ready in the JP1/Automatic Job Management System 3 Configuration Guide.

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 JP1/Automatic Job Management System 3 Configuration Guide.

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.

KAVU3607-I

The job(job-name: execution-ID) was accepted.(number-of-jobs, manager-host-name, job-number)

A job execution request was accepted.

This message is output only when JP1/AJS3 - Agent Minimal Edition is used.

In the message, number-of-jobs indicates the number of jobs that have been accepted that day. If JP1/AJS3 - Agent Minimal Edition running on multiple agent hosts on the same computer, number-of-jobs indicates the total number of jobs that have been accepted by those agent hosts.

However, if one of the following conditions is met, the number of accepted jobs is not incremented even when a job is executed, and this message is not output.

After a job is executed, causing this message to be output, the same job is executed within 48 hours.

After a job is executed, causing this message to be output, the same job is retried within 48 hours.

(S)

Continues processing.

KAVU3608-E

The job(job-name: execution-ID) cannot be executed because the number of executions exceeds 10. (manager-host-name, job-number)

The job cannot be executed, because the number of executed jobs has reached the maximum number of jobs that can be executed per day.

This message is output only when JP1/AJS3 - Agent Minimal Edition is used.

(S)

Cancels the requested processing.

(O)

Check the job execution history log file to see whether job requests from unexpected manager hosts have been accepted.

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 JP1/Automatic Job Management System 3 Configuration Guide.

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.

#

Indicates the file path for the specified file as well as for each directory up to the highest-level directory.

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 JP1/Automatic Job Management System 3 Command Reference.

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)

Check the following:

Make sure that the authentication server has started. If the authentication server has not started, start it and then reissue the request.

The setting of whether to enable or disable the communication encryption function might be inconsistent between the authentication server and JP1/AJS3. Match the settings, and then restart the JP1/Base service and JP1/AJS3 service.

If this error still occurs after the above actions have been taken, collect data by using a data collection tool, 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)

The job termination request was suppressed by the job distribution delay reduction function. (reason-code = 0xe00a0018)

(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, flexible job#, HTTP connection job, action job, or custom job:

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

#

For a flexible job, replace agent host with relay agent.

For a QUEUE job or submit job:

Execute the jpqjobget command.

If the reason code is 0xe00a0018 (the job termination request was suppressed by the job distribution delay reduction function), a KAVUxxxx or KNACxxxx message will have been output before or after this one. Remove the cause of the error by referring to the description in that message.

Note that the program corresponding to the job might still be running on the agent host. If you want to forcibly terminate the program, check the job name in the KAVS0265-E message that is output immediately after this one. Then, identify the program corresponding to the job from the job definition and forcibly terminate that program.

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 20.4.2(56) AJSTMPDIR in the JP1/Automatic Job Management System 3 Configuration Guide.

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 20.4.2(56) AJSTMPDIR in the JP1/Automatic Job Management System 3 Configuration Guide.

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.

In addition, the setting of whether to enable or disable the communication encryption function might be inconsistent between the authentication server and JP1/AJS3. Match the settings, and then restart the JP1/Base service and JP1/AJS3 service.

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)

The system might be under a heavy load. Revise the following settings according to your operation:

Reduce the size of the result file specified for the job (standard output file or standard error output file) so that it is smaller than the maximum size of sent files (value set in the LimitSendFileSize environment setting parameter) and smaller than the maximum size of received files (value set in the LimitReceiveFileSize environment setting parameter).

For details about the maximum size of sent files, see 6.2.27 Placing restrictions on file transmission in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows) or 15.2.24 Placing restrictions on file transmission in the JP1/Automatic Job Management System 3 Configuration Guide (for UNIX).

For details about the maximum size of received files, see 6.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows) or 15.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (for UNIX).

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. Then, confirm that the result file size is smaller than the maximum size of sent files (value of the LimitSendFileSize environment setting parameter) and the maximum size of received files (value of the LimitReceiveFileSize environment setting parameter). Alternatively, revise the maximum file size.

For details about the maximum size of sent files, see 6.2.27 Placing restrictions on file transmission in the JP1/Automatic Job Management System 3 Configuration Guide

(in Windows) or 15.2.24 Placing restrictions on file transmission in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

For details about the maximum size of received files, see 6.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (in Windows) or 15.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

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. Then, confirm that the result file size is smaller than the maximum size of sent files (value of the LimitSendFileSize environment setting parameter) and the maximum size of received files (value of the LimitReceiveFileSize environment setting parameter). Alternatively, revise the maximum file size.

For details about the maximum size of sent files, see

6.2.27 Placing restrictions on file transmission in the JP1/Automatic Job Management System 3 Configuration Guide (in Windows) or 15.2.24 Placing restrictions on file transmission in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

For details about the maximum size of received files, see 6.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (in Windows) or 15.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

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 JP1/Automatic Job Management System 3 Configuration Guide(for hosts under Windows), or 15.2.6 Preventing duplicated reception of job result files in the JP1/Automatic Job Management System 3 Configuration Guide (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 JP1/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 JP1/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, flexible job#, HTTP connection job, action job, or custom job:

ajsagtalt command

#

For a flexible job, replace agent host with relay agent.

For a QUEUE job or submit job:

jpqagtalt command

For details on the ajsagtalt command, see ajsagtalt in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

For details on the jpqagtalt command, see jpqagtalt in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

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 JP1/Automatic Job Management System 3 Configuration Guide (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 JP1/Automatic Job Management System 3 Configuration Guide (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.

KAVU4314-E

Timeout occurred for the request to forcibly terminate a job sent to the agent (agent-host-name). Therefore, the job was set to end status (termination-status). (host name:manager-host-name, job number:job-number, reason location:error-location[error-location], reason code:reason-code)

A request to forcibly terminate a job timed out.

(S)

Stops the requested processing, and places the job in the end status.

(O)

Make sure that the manager host indicated by manager-host-name can successfully communicate with the agent host indicated by agent-host-name. 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.

KAVU4315-E

The current status does not allow a request to forcibly terminate a job to be sent to the agent (agent-host-name). Therefore, the job (job number:job-number) was set to end status (termination-status). (host name:manager-host-name,reason location:error-location[error-location],reason code:reason-code)

The status of the job was changed to the end status, because a request to forcibly terminate the job could not be issued.

(S)

Stops the requested processing, and places the job in the end status.

(O)

Make sure that the manager host indicated by manager-host-name can successfully communicate with the agent host indicated by agent-host-name. 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.

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.

KAVU4333-W

The total file size of the result files (standard-output-file-name, standard-error-file-name) of a job (job-number, manager-host-name) exceeded the Agent's limit for sending files.

The status of the job changes to Ended with warning because the size of files to be sent on the agent exceeded the maximum.

(S)

Receives the result file up to the maximum size for sent files.

(O)

Reduce the amount of standard output and standard error output for the job. Then, if you need information in the standard output file or standard error output file, re-execute the job.

Reduce the amount of standard output and standard error output for the job to be smaller than the maximum file size (value set in the LimitSendFileSize environment setting parameter). Alternatively, revise the maximum file size.

KAVU4334-E

The total file size of the result files (standard-output-file-name, standard-error-file-name) of a job (job-number, manager-host-name) exceeded the Agent's limit for sending files.

The status of the job changes to Ended abnormally because the size of files to be sent on the agent exceeded the maximum.

(S)

Receives the result file up to the maximum size for sent files.

(O)

Reduce the amount of standard output and standard error output for the job. Then, if you need information in the standard output file or standard error output file, re-execute the job.

Reduce the amount of standard output and standard error output for the job to be smaller than the maximum file size (value set in the LimitSendFileSize environment setting parameter). Alternatively, revise the maximum file size.

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 JP1/Automatic Job Management System 3 Configuration Guide.

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 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

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.

(O)

The number of executable jobs might have reached the maximum number of concurrently executable jobs.

Set the maximum number of concurrently executable jobs by considering the job execution time and the number of jobs executed per hour.

Use the jpqagtalt command to change the maximum number of concurrently executable jobs. Use the jpqquealt command when you want to change the warning values for the number of jobs in a queue.

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 20.5.2(4) PreserveTerm in the JP1/Automatic Job Management System 3 Configuration Guide.

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, 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 JP1/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, flexible job#, HTTP connection 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 flexible job, replace execution agent with relay 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)

On the agent, 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 JP1/Automatic Job Management System 3 Configuration Guide.

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.

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.

An agent host that does cannot issue requests for flexible jobs was specified as the relay agent for a flexible job. Alternatively, if the OS of the manager host is neither Windows nor Linux, no relay agent was specified.

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 2016, 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.

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.

Specify (as the relay agent) an agent host that can issue requests for flexible jobs, and then retry the operation.

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)

The job might have ended abnormally because the user who executed the job has no access permissions for the executable file of the agent or for the file path# for the executable file.

Check the access permissions necessary for job execution or check the group that owns the directory where the executable file exists, remove the cause of the error, and then reissue a job execution request.

#

Indicates the file path for the specified file as well as for each directory up to the highest-level directory.

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 JP1/Automatic Job Management System 3 Configuration Guide (for hosts under Windows) or 13. Setup in the JP1/Automatic Job Management System 3 Configuration Guide (for hosts under UNIX).

For details on the JP1/AJS3 commands, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference or 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

For details about the JP1/Base commands, see the JP1/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 JP1/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)(b) When multiple scheduler services are activated and you want to avoid desktop heap shortages in the JP1/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).

The execution OS user requires superuser privileges if an execution priority of 4 or 5 is specified for any of the following:

Unix job

HTTP connection job executed on a Linux host

Upper-level jobnet of a flexible job

(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 JP1/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.10.1 Notes on the standard output file and standard error output file in the JP1/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.10.1 Notes on the standard output file and standard error output file in the JP1/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 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

For details on the Jischk command, see the JP1/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 20.5 Setting up the job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

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 JP1/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.11 Troubleshooting problems related to invalid ISAM files in the manual JP1/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 20.5 Setting up the job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

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 JP1/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, if the installation folder is the default installation folder or is in 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)

The default work folder for Windows, f the installation folder is other than the above:

JP1/AJS3 - Manager-installation-folder\tmp

The default work directory for UNIX:

/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 9.3 Reorganizing a database when QUEUE jobs and submit jobs are used in the JP1/Automatic Job Management System 3 Administration Guide.

Use the jpqimport command to create a job execution environment database.

For details on this command, see 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

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.11 Troubleshooting problems related to invalid ISAM files in the manual JP1/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 JP1/Automatic Job Management System 3 Configuration Guide.

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 20.5.2(1) WorkPath (for manager process) in the JP1/Automatic Job Management System 3 Configuration Guide.

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 20.5.2(1) WorkPath (for manager process) in the JP1/Automatic Job Management System 3 Configuration Guide.

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 20.5.2(3) DatabasePath in the JP1/Automatic Job Management System 3 Configuration Guide.

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 20.5 Setting up the job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

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 JP1/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 JP1/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 JP1/Automatic Job Management System 3 Configuration Guide.

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.

KAVU7228-W

No information can be output to the log file(output-destination-folder-of-the-log-file) on logical host(logical-host-name). (reason code:reason-code)

Data cannot be output to the log file.

(S)

Cancels the requested processing.

(O)

Output of the log data might have failed because the output destination folder of the log file does not exist.

Make sure that the output destination folder of the log file exists.

If the output destination folder of the log file has been deleted, an overwrite installation of JP1/AJS3 is required. For a logical host, the cluster environment must be configured again.

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 JP1/Automatic Job Management System 3 Configuration Guide.

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 JP1/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 acquiring user information. For details, see 15.2.20 Changing the settings for retries when user information is acquired in the JP1/Automatic Job Management System 3 Configuration Guide.

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 JP1/Automatic Job Management System 3 Configuration Guide.

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 20.5.2(1) WorkPath (for manager process) in the JP1/Automatic Job Management System 3 Configuration Guide.

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.

6 Messages beginning with KAVV (Messages about JP1/AJS3 - View)

This chapter explains the messages beginning with KAVV (messages about JP1/AJS3 - View).

6.1 List of messages beginning with KAVV

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 JP1/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 settings file has been damaged.

The locations of the folders for storing settings files are as follows:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\conf

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

(S)

Cancels processing.

(O)

Correct the cause of the error.

If the settings file has been damaged, a problem might occur. For example, environment settings might be lost, JP1/AJS3 - View might terminate abnormally, or JP1/AJS3 - View might not be able to start. If such a problem occurs, make sure that all instances of JP1/AJS3 - View have been terminated, and then restore the settings file (indicated by file-name in the message) from a backup file that was created before the problem occurred. Alternatively, delete the settings file, restart JP1/AJS3 - View, and then specify the environment settings again.

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 settings file has been damaged.

The locations of the folders for storing settings files are as follows:

File extensions other than .cjx

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\conf

File extension .cjx

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

(S)

Cancels processing.

(O)

Correct the cause of the error.

If the settings file has been damaged, a problem might occur. For example, environment settings might be lost, JP1/AJS3 - View might terminate abnormally, or JP1/AJS3 - View might not be able to start. If such a problem occurs, make sure that all instances of JP1/AJS3 - View have been terminated, and then restore the settings file (indicated by file-name in the message) from a backup file that was created before the problem occurred. Alternatively, delete the settings file, restart JP1/AJS3 - View, and then specify the environment settings again.

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:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\log

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\log

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

(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 JP1/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 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

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.10 Setting for changing the number of characters specifiable for a unit name in a UTF-8 environment in the JP1/Automatic Job Management System 3 Configuration Guide.

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 in JP1/AJS3 - Manager at the connection destination, scheduler services cannot be viewed.

The DEFLENTYPE environment setting parameter can be used to enable the setting for changing the number of characters specifiable for a unit name in a UTF-8 environment. If the DEFLENTYPE environment setting parameter is set to enable this setting in JP1/AJS3 - Manager at the connection destination, JP1/AJS3 - View of version 09-50 or earlier is connected.

(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 in JP1/AJS3 - Manager at the connection destination, 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

If the setting for changing the number of characters specifiable for a unit name in a UTF-8 environment is enabled in JP1/AJS3 - Manager at the connection destination, connect JP1/AJS3 - View of version 09-50-01 or later.

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.

Note that no action is required because this message indicates maintenance information.

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.

Note that no action is required because this message indicates maintenance information.

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.

Note that no action is required because this message indicates maintenance information.

KAVV233-I

SDUMP: (data-0)

This message reports the data that is sent.

(S)

Outputs to the log the data that is sent.

Note that no action is required because this message indicates maintenance information.

KAVV234-I

RDUMP: (data-0)

This message reports the data that is received.

(S)

Outputs to the log the data that is received.

Note that no action is required because this message indicates maintenance information.

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.

Note that no action is required because this message indicates maintenance information.

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.

Note that no action is required because this message indicates maintenance information.

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.

Note that no action is required because this message indicates maintenance information.

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.

Note that no action is required because this message indicates maintenance information.

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 12.3.54 JP1/AJS3 Command Entry dialog box in the JP1/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.

(O)

Make sure that the search condition is appropriate. If necessary, re-estimate the maximum number of search results that can be displayed. For details about how to change the maximum number of search results that can be displayed, see 11.10.1 Changing the maximum number of units displayable in the search result list area in the JP1/Automatic Job Management System 3 Operator's Guide.

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 12.4.42 Wall Paper dialog box in the JP1/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.

KAVV299-E

The specified function is not supported.

The specified function cannot be used in the version you are using.

JP1/AJS3 - View version 11-00 and later does not support the following function:

JP1/AJS2 Configuration View

(S)

Cancels processing.

(O)

Use a version of JP1/AJS3 - View that supports the function above.

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 12.4.42 Wall Paper dialog box in the JP1/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 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

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.

A character string that contains one or more spaces is not enclosed by double quotation marks (").

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

Outputs to the log that the tool was started.

Note that no action is required because this message indicates maintenance information.

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.

KAVV396-E

Specified operation cannot be executed because the option (file name=file-name, keyword=keyword) is invalid.

The setting of the option indicated in keyword is disabled by downloading the common user profile. If the option setting is disabled, the specified operation cannot be performed.

(S)

Cancels processing.

(O)

If necessary, enable the option, and then restart JP1/AJS3 - View.

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:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\conf\port.conf

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

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 JP1/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 JP1/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.

#

For 64-bit versions of Windows, replace HKEY_LOCAL_MACHINE\SOFTWARE with HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node.

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 JP1/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 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

This message is output if an JP1/AJS3 - View instance with the communication encryption function disabled is connected to a manager host with the communication encryption function enabled. Match the settings of the communication encryption function between the JP1/AJS3 - View host and the manager host.

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 JP1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual JP1/Automatic Job Management System 3 Troubleshooting.

For details on how to collect the log of JP1/Base, see the JP1/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 JP1/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.

Note that no action is required because this message indicates maintenance information.

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 JP1/Automatic Job Management System 3 Troubleshooting.

For details about log information, see C. Log Information in the manual JP1/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/AJS3 - Manager and JP1/AJS3 - View in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide and C. JP1/AJS3 - View Compatibility in the JP1/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 JP1/Automatic Job Management System 3 Overview and 7.2 Relationship between number of logs to keep and performance in the JP1/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 JP1/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 JP1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual JP1/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 JP1/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.

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 JP1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual JP1/Automatic Job Management System 3 Troubleshooting.

For details on how to collect the log of JP1/Base, see the JP1/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/AJS3 - Manager and JP1/AJS3 - View in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide and C. JP1/AJS3 - View Compatibility in the JP1/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 JP1/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 JP1/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 JP1/Automatic Job Management System 3 Troubleshooting.

For details about the log, see C. Log Information in the manual JP1/Automatic Job Management System 3 Troubleshooting.

The probable causes are as follows:

If the connection destination is JP1/AJS3 - Manager for Windows

Read and write permissions for the folder (and the files in that folder) specified by the database directory name for the scheduler service have not been set for the OS user mapped to the JP1 user.

The database for the scheduler service defined in JP1/AJS3 - Manager at the connection destination has stopped.

If the connection destination is JP1/AJS3 - Manager for Unix

The home directory of the OS user mapped to the logged-in JP1 user does not exist.

Update permission (rwx) for the directory (and the files in that directory) specified by the database directory name for the scheduler service has not been set for the OS user mapped to the JP1 user.

The database for the scheduler service defined in JP1/AJS3 - Manager at the connection destination has stopped.

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. The probable causes are:

The unit was deleted.

The name of a unit on a higher-level path to which the specified unit belongs was changed.

After deleting the specified unit, another unit was defined with the same unit name.

(S)

Cancels processing.

(O)

For each window, check that the unit exists.

For the following windows, refresh the window to check that the unit exists:

JP1/AJS3 - View window

Jobnet Editor window

Jobnet Monitor window

For the following windows, close and open the window to check that the unit exists:

Daily Schedule window

Monthly Schedule window

Edit Monthly Calendar window

Edit Annual Calendar window

Wait Conditions Statuses window

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.10 Setting for changing the number of characters specifiable for a unit name in a UTF-8 environment in the JP1/Automatic Job Management System 3 Configuration Guide.

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 9.2.2 Reorganizing a database in the JP1/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 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

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 JP1/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 JP1/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 JP1/Automatic Job Management System 3 Configuration Guide.

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 JP1/Automatic Job Management System 3 Troubleshooting.

For details about the log, see C. Log Information in the manual JP1/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 JP1/Automatic Job Management System 3 Troubleshooting.

For details about the log, see C. Log Information in the manual JP1/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 JP1/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 JP1/Automatic Job Management System 3 Troubleshooting.

For details about log information, see C. Log Information in the manual JP1/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 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference, 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.6 Enabling the suspend function in the JP1/Automatic Job Management System 3 Configuration Guide (for hosts under Windows) or 15.1.6 Enabling the suspend function in the JP1/Automatic Job Management System 3 Configuration Guide (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 JP1/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.10 Setting for changing the number of characters specifiable for a unit name in a UTF-8 environment in the JP1/Automatic Job Management System 3 Configuration Guide.

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 JP1/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 12.4.16 Detailed Definition - [Receive JP1 Event] - [Extended Attribute] dialog box in the JP1/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.

#

For 64-bit versions of Windows, replace HKEY_LOCAL_MACHINE\SOFTWARE with HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node.

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:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

(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 JP1/Automatic Job Management System 3 Troubleshooting. For log information details, see C. Log Information in the manual JP1/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.10 Setting for changing the number of characters specifiable for a unit name in a UTF-8 environment in the JP1/Automatic Job Management System 3 Configuration Guide.

(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.10 Setting for changing the number of characters specifiable for a unit name in a UTF-8 environment in the JP1/Automatic Job Management System 3 Configuration Guide.

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.

KAVV2509-Q

A relation line cannot be pasted when Paste (Units And Relations) is executed under the start condition. Are you sure you want to continue?

If you execute Paste (Units and relations) 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 (Units and relations) or No to cancel.

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.

KAVV3103-E

An error occurred while processing was being performed for SSL communication. (maintenance-information)

An error occurred during SSL communication processing. The probable causes are:

A protocol that cannot be used is specified in the SSLProtocol parameter in the ajs2.conf file.

The communication encryption function is disabled at the connection destination.

The root certificate for the server certificate at the connection destination is not installed.

The current time of the host on which an error occurred is earlier than the start time of the effective period specified in the server certificate.

The current time of the host on which an error occurred is later than the end time of the effective period specified in the server certificate.

A temporary communication error occurred.

Connection is restricted by JP1/AJS3 - Manager at the connection destination.

(S)

Cancels processing.

(O)

If a protocol that cannot be used is specified in the SSLProtocol parameter:

Specify a protocol that can be used.

If the communication encryption function is disabled at the connection destination:

Enable the communication encryption function for JP1/AJS3 - Manager at the connection destination.

If the root certificate for the server certificate at the connection destination is not installed:

Install the root certificate for the server certificate at the connection destination.

If the current time of the host on which an error occurred is earlier than the start time of the effective period specified in the server certificate:

Retry the operation after the start time of the effective period specified in the server certificate.

If the current time of the host on which an error occurred is later than the end time of the effective period specified in the server certificate:

Replace the server certificate located on the connection destination host.

If a temporary communication error occurred:

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

If JP1/AJS3 - Manager at the connection destination restricts connections:

Add the IP address of the connection source host to the connection permission configuration file for the destination manager.

KAVV3104-E

An attempt to read the file for specifying the names of the hosts that use non-encrypted communication failed. file-name (maintenance-information)

An attempt to read the nosslhost.conf file for specifying the names of the hosts that use non-encrypted communication failed. The probable causes are:

The nosslhost.conf file does not exist.

You do not have access permission for nosslhost.conf.

A temporary file access error occurred.

[NO_SSL_HOST] is not entered.

An asterisk (*) is specified incorrectly.

The number of specified host names exceeds the maximum (1,024).

The length of a host name exceeds 255 characters.

The same host name is specified more than once.

(S)

Cancels processing.

(O)

If the file does not exist:

Replace the nosslhost.conf file.

If you do not have access permission for nosslhost.conf:

Set access permission for nosslhost.conf.

If a temporary file access error occurred:

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

If [NO_SSL_HOST] is not entered:

Enter [NO_SSL_HOST] at the beginning of nosslhost.conf.

If an asterisk (*) is specified incorrectly:

Specify * alone.

If the number of specified host names exceeds the maximum (1,024):

Specify 1,023 or fewer host names.

If the length of a host name exceeds 255 characters:

Correct the host name so that it contains 255 or fewer characters.

If the same host name is specified more than once:

Delete the same host names, leaving one host name.

KAVV3105-I

encryption-setting : maintenance-information

This message indicates that communication is performed with encryption enabled (TRUE) or disabled (FALSE).

TRUE or FALSE is displayed in encryption-setting. If encryption is enabled, TRUE is followed by(TRUE) or (FALSE), indicating whether to verify the server certificate. If encryption is disabled, whether to verify the server certificate is not displayed. Therefore, one of the following three patterns is output in the message:

If encryption is enabled and the server certificate is verified: TRUE(TRUE)

If encryption is enabled and the server certificate is not verified: TRUE(FALSE)

If encryption is disabled: FALSE

A binary character string is displayed in maintenance-information.

(S)

Outputs to the log that communication is performed with encryption enabled (TRUE) or disabled (FALSE).

KAVV3106-E

An attempt to verify the server certificate failed. (destination-hostname, maintenance-information)

An attempt to verify the server certificate sent from the connection destination failed. The probable causes are:

The connection destination host name does not match the CN or SAN.

The root certificate corresponding to the server certificate is not installed.

The server certificate and the intermediate certificate are joined in an incorrect order.

(S)

Cancels communication processing, and then continues subsequent processing.

(O)

If the connection destination host name does not match the CN or SAN:

Match the connection destination host name to the CN or SAN.

If the root certificate corresponding to the server certificate is not installed:

Install the corresponding root certificate.

If the server certificate and the intermediate certificate are joined in an incorrect order:

Join the server certificate and the intermediate certificate in the correct order.

KAVV3107-E

A root certificate was not found. (file-name, maintenance-information)

A root certificate is not found. The probable causes are:

A root certificate storage folder does not exist.

You do not have access permission for the root certificate storage folder.

A root certificate has not been installed.

A temporary access error occurred during reading of a root certificate.

(S)

Cancels processing.

(O)

If a root certificate storage folder does not exist:

Create a root certificate storage folder, and then install a root certificate.

If you do not have access permission for the root certificate storage folder:

Set access permission for the root certificate storage folder, and then install a root certificate.

If a root certificate has not been installed:

Install a root certificate.

If a temporary access error occurred during reading of a root certificate:

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

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.9 Settings for using the temporary change operation management function in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows) or 15.1.9 Settings for using the temporary change operation management function in the JP1/Automatic Job Management System 3 Configuration Guide (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.

KAVV3340-I

The multi-user remote operation function is enabled.

This message reports that the multi-user remote desktop connection function is enabled.

(S)

Reports that the multi-user remote desktop connection function was enabled.

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 JP1/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 20.4.2(40) SESSIONTIMEOUT in the JP1/Automatic Job Management System 3 Configuration Guide.

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 JP1/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 JP1/Automatic Job Management System 3 Configuration Guide.

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.

KAVV3355-Q

An unusable control character is specified in a field. Do you want to continue the processing without changing the specified control character?

An unusable control character is specified in a field.

(S)

Waits for a response.

(O)

To continue the processing without changing the specified control character, click Yes. To cancel the processing, click No.

We recommend that you click No to cancel the processing, and then delete the control character by editing the value entered in the field that has a yellow background. If you click Yes to continue the processing, the following problems might occur:

Characters become garbled.

An error occurs when a unit is created or the definition is changed.

A standard job ends with an anomaly detected, or the standard job operates incorrectly.

An event job ends with an anomaly detected, or the event job cannot be detected or is detected incorrectly.

A JP1/AJS3 process (such as a service or command) ends abnormally.

KAVV3356-E

An unusable control character is specified in a field. Delete the control character.

An unusable control character is specified in a field.

(S)

Cancels processing.

(O)

Delete the control character by editing the value entered in the field that has a yellow background, and then try the operation again.

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.8 Settings for using wait conditions in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows) or 15.1.8 Settings for using wait conditions in the JP1/Automatic Job Management System 3 Configuration Guide (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 JP1/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 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

(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 JP1/Automatic Job Management System 3 Command Reference, 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 JP1/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 JP1/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 JP1/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 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference, 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.

Note that no action is required because this message indicates maintenance information.

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:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir\

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir\

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir\

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir\

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir\

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir\

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

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

7 Messages beginning with KFP (Messages about an embedded database)

This chapter explains the messages beginning with KFP (messages about embedded databases).

7.1 List of messages beginning with KFP (messages about embedded databases)

This section lists the messages that begin with KFP (messages about embedded databases).

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.

(O)

Take action by referring to the error message output before this message.

KFPH00131-E

pdhold command failed due to RDAREA already held, RDAREA=aa....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. If you execute the ajsembdbreclaim command in a state in which large quantities of unavailable areas occur in the database because maintenance has not been performed for a long time, a lot of data is sent to the system log. An embedded database terminates abnormally if the system log capacity is insufficient. Therefore, estimate the required system log capacity and, add a system log and then execute the ajsembdbreclaim command. For details about how to check the unavailable area and the system log capacity required for execution of the ajsembdbreclaim command, see 9.1.1 Analyzing the database area in the JP1/Automatic Job Management System 3 Administration Guide.

If this message is output even though you perform maintenance regularly, check whether the increase in the volume of job operations (such as the number of job definitions, the number of executed jobs, and the number of generations to be saved) is within the intended range. Estimate the database capacity from the volume of job operations, and examine the construction of the embedded database environment to make sure the scale is appropriate to the volume of operations. When this message is output several times, depending on the content of the operations (such as whether an operation is performed on a large number of units at one time), the KFPS01220-E message might be output to the event log or to syslog, and the embedded database might terminate abnormally.

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 administrator privileges

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 9.2.2(2)(c) Customizing the reorganization scripts in the JP1/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 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

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 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

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.

8 Messages beginning with KNAC (Messages that are output by communication control and agent management)

This chapter explains the messages beginning with KNAC (messages output by communication control and agent management).

8.1 List of messages beginning with KNAC (messages output by communication control)

This section lists messages that begin with KNAC (messages output by communication control).

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 administrator privileges or superuser privileges

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 JP1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual JP1/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 JP1/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 JP1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual JP1/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.

(O)

Memory might be insufficient. After eliminating the cause of the problem, check the status of the job, and then re-execute the job as needed.

KNAC0014-E

The port can't change to the reception state.: port_number=port-number maintenance-information-1 maintenance-information-2

The specified port number cannot be changed to a receiving state because the port numbers specified in the services file, or the IP addresses specified in the hosts file or the jp1hosts information cannot be used.

(S)

Cancels the requested 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. Even if the contents of the services file are correct, the specified range of ephemeral ports might overlap with that of the ports to be used by JP1/AJS3, and the port numbers to be used by JP1/AJS3 might be being used by other programs. In addition, the specified port numbers might not be changed to a receiving state because the IP addresses specified in the hosts file or the jp1host information cannot be used. Make sure that the IP addresses are defined correctly.

For details about the ports used for JP1/AJS3, see A.1 Tables of port numbers in the JP1/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.

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 JP1/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.

KNAC0607-I

Communication will no longer be retried, because processing to stop the process will now begin.

The running communication retry is canceled because a process stop request was received.

(S)

The running communication retry processing is canceled to start the process stop processing.

KNAC0609-E

An error occurred in SSL communication processing.(logical-host-name, destination-host-name, maintenance-information)

An error occurred during SSL communication processing. The probable causes are:

The communication encryption function is disabled at the connection destination.

A temporary communication error occurred.

If this message is output at the reception side of TCP/IP communication, a null character string is output for connection-destination-host-name.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Cancels communication processing, and then continues subsequent processing.

(O)

If the communication encryption function is disabled at the connection destination:

Enable the communication encryption function for the host indicated in connection-destination-host-name.

If a temporary communication error occurred:

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

KNAC0610-W

The certificate has expired.(logical-host-name, destination-host-name)

The server certificate sent from the connection destination or the root certificate located on the local host has expired.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Continues processing.

(O)

Acquire a new certificate, and replace the expired certificate with it.

8.2 List of messages beginning with KNAC (messages output by agent management)

This section lists messages that begin with KNAC (messages output by agent management).

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 JP1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual JP1/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 Blockade.

(S)

Terminates command processing.

(O)

For the execution agent or execution agent group to be deleted, execute the ajsagtalt command to change the delivery-limitation status to Blockade, and then retry the operation.

For details about ajsagtalt command, see ajsagtalt in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

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 JP1/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 JP1/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 JP1/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.

KNAC1200-I

Request for starting the communication status confirmation was issued to the agent monitoring process.

The agent monitoring process was requested to start conducting a communication status check.

(S)

Continues processing.

KNAC1201-I

Request for stopping the communication status confirmation was issued to the agent monitoring process.

The agent monitoring process was requested to stop conducting a communication status check.

(S)

Continues processing.

KNAC1202-I

The output of the agent monitoring information will now start.

The output of information about the statuses of execution agents will start.

(S)

Continues processing.

KNAC1203-I

The output of the agent monitoring information will now end.

The output of information about the statuses of execution agents will end.

(S)

Continues processing.

KNAC1204-E

Cannot execute because the job distribution delay reduction function is not configured.

The command cannot be executed, because the job distribution delay reduction function is disabled.

(S)

Terminates command processing.

(O)

Make sure that the AGMMONITORING environment setting parameter is set correctly, 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 JP1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual JP1/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.

However, if agent management is stopped, the system continues processing without reconnecting 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.5 Changing the common definition information in the JP1/Automatic Job Management System 3 Configuration Guide (for hosts under Windows), or 17.2.5 Changing the common definition information in the JP1/Automatic Job Management System 3 Configuration Guide (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 this message is output when agent management stops, the embedded database might have been disconnected. Because an update of the embedded database has been completed, no problem exists, despite the reported error.

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 JP1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual JP1/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 JP1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual JP1/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.

Refer to the integrated trace log to see if error messages are output.

If error messages are output in the log, follow the applicable messages to eliminate the cause of the error.

If no message is output immediately before the occurrence of the error, or if no error message is output in the integrated trace log, 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 JP1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual JP1/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 KAVUxxxx 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

- Flexible job

- HTTP connection 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.

KNAC1521-E

The invalid exec-agent information was detected in the database (logical-host-name)(maintenance-information).

The invalid information was detected in the database.

(S)

Terminates processing.

(O)

The embedded database might not have been re-created when the setting to increase of the maximum number of execution agents was disabled. Re-perform the procedure to disable the setting to increase of the maximum number of execution agents.

For details, see 6.2.28(3) Procedure for canceling the increase of the maximum number of execution agents in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows), 15.2.25(3) Procedure for canceling the increase of the maximum number of execution agents in the JP1/Automatic Job Management System 3 Configuration Guide (for UNIX).

KNAC1701-W

The communication status confirmation will now start because the obstacle agent has been detected.(logical-host-name)

A communication status check will be conducted, because a communication failure was detected on an execution agent.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Continues processing.

KNAC1702-I

The communication status confirmation will now start - started by ajsagtcheck command.(logical-host-name)

The ajsagtcheck command will be used to conduct a communication status check.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Continues processing.

KNAC1703-W

The obstacle status of exec-agent was changed to unconnectable status.(the number of exec-agent: number-of-execution-agents-whose-status-changed-to-Unconnectable) (logical-host-name)

Because a communication failure was detected on an execution host, the status of the execution agent was changed to Unconnectable.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Changes the status of the execution agent to Unconnectable, and then executes the subsequent processing.

(O)

The probable causes are:

The name of the execution host cannot be resolved.

The maximum number of file descriptors that can be used by the agent monitoring process was reached.

No ports are available on the manager host.

The execution host is not running.

JP1/AJS3 is not running on the execution host.

A firewall rejected the connection.

To check the execution agents that recovered, use the ajsagtshow command. Remove the causes of the communication failure. Then, wait until recovery of the indicated execution agent is confirmed by a communication recovery check. Alternatively, use the ajsagtalt command to change the status of the execution agent to Not checked.

If, even after you remove the cause of a failure, the status of execution agents that are operating normally is Unconnectable, a timeout might have occurred in the processing that checks the communication status. Based on the number of execution agents that are in the Unconnectable status, increase the amount of time before a communication connection timeout occurs (the value specified for the environment setting parameter AGMCONNECTTIMEOUT). Increase the value by about 5 to 10 seconds for every 100 execution agents. After changing the value specified for the environment setting parameter AGMCONNECTTIMEOUT, restart the JP1/AJS3 service. After the JP1/AJS3 service restarts, execute the ajsagtcheck command, and then make sure that a timeout does not occur in the processing that checks the communication status.

KNAC1704-I

The communication status confirmation ended.(logical-host-name)

The communication status check ended.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Continues processing.

KNAC1705-E

Failed to connect to the exec-agent (exec-agent-name:exec-host-name) because an error occurred while processing.(logical-host-name)

The communication status check or communication recovery check for the execution host was not successful. The status of the relevant host cannot be changed.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Continues conducting the communication status check or communication recovery check.

(O)

Determine the reason why the communication status check or communication recovery check did not succeed by referring to the KNACnnnn error message that was output before this one.

KNAC1706-I

The communication status recovery confirmation will now start.(logical-host-name)

A communication recovery check will be conducted.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Continues processing.

If an execution agent for which a communication has occurred still exists, the system waits the amount of time specified in the environment setting parameter AGMINTERVALFORRECOVER and then conducts another communication recovery check.

KNAC1707-I

The obstacle status of exec-agent was changed to connectable status because it recovered from obstacle. (the number of exec-agent: number-of-execution-agents-whose-status-changed-to-Connectable) (logical-host-name)

Because recovery of the execution host was successful, the status of the execution agent was changed to Connectable.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Continues processing.

(O)

To check the execution agents that recovered, use the ajsagtshow command.

After this message is output, if job distribution still does not succeed, the communication encryption function might be enabled on the execution host. Check whether the KAVU2251-E message has been output to the integrated trace log for the relevant host.

If the KAVU2251-E message has been output:

Make sure that the communication encryption function settings on the manager host and those on the execution host match. After that, enable the communication encryption function on the execution host, and then restart the JP1/Base and JP1/AJS3 services on the execution host.

If the KAVU2251-E message has not been output:

Check whether a KAVUxxxx or KNACxxxx message has been output before or after this message. If such a message has been output, see the description in the message.

KNAC1708-I

The communication status recovery confirmation ended.(logical-host-name)

The communication recovery check ended.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Continues processing.

KNAC1709-E

Failed to confirm the status of the exec-agent (exec-agent-name:exec-host-name,IP-address). : maintenance-information-1 maintenance-information-2 maintenance-information-3 (logical-host-name)

An attempt was made to connect to the execution agent that is obtained from the indicated execution host name and has the indicated IP address. However, the communication status could not be identified because an error occurred.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Continues processing.

(O)

See the description of the KNACxxxx message that was output before this message.

Because the communication status of the execution agent with the IP address indicated by IP-address could not be identified, the status of the execution agent indicated by exec-agent-name in the message is not output by the ajsagtshow command.

KNAC1710-E

The communication status confirmation will now stop because an error occurred.(logical-host-name)

The attempt to start a communication status check will stop because an error occurred.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Continues processing.

(O)

See the description of the KNACxxxx message that was output before this message.

After taking the necessary measures, use the ajsagtcheck command to restart the communication status check.

KNAC1711-E

The communication status recovery confirmation will now stop because an error occurred.(logical-host-name)

The attempt to start a communication recovery check will stop because an error occurred.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Cancels processing.

If there are any execution agents on which a communication failure has not been resolved, the system conducts another communication recovery check after the time specified for the AGMINTERVALFORRECOVER environment setting parameter passes.

(O)

See the description of the KNACxxxx message that was output before this message.

KNAC1713-I

The communication status confirmation will now stop - stopped by ajsagtcheck command.(logical-host-name)

The ajsagtcheck command will be executed to stop the communication status check.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Cancels processing.

KNAC1714-I

The communication status recovery confirmation will now stop so that the communication status confirmation could start.(logical-host-name)

A communication recovery check will stop, and a communication status check will start.

For a physical host, JP1_DEFAULT is indicated in logical-host-name.

(S)

Cancels processing.

KNAC1771-E

Cannot execute because the agent monitoring process is stopped.

The command could not be executed because the agent monitoring process was not running.

(S)

Terminates command processing.

(O)

Check whether the agent monitoring process is running. Remove the cause of the error by taking the measures described below. Then, start the agent monitoring process, and re-execute the command.

If the setting for starting the agent monitoring process is not specified, start the process. For details, see 21.5 Setting up the job distribution delay reduction function in the JP1/Automatic Job Management System 3 Configuration Guide.

If the JP1/AJS3 service is not running, start it.

If the above are not applicable, remove the cause of the error by checking the status of JP1/AJS3 and the contents of the integrated trace log.

KNAC1772-E

Cannot execute because the command cannot communicate with the agent monitoring process. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

The command could not be executed, because communication with the agent monitoring process was impossible.

(S)

Terminates command processing.

(O)

Check whether the agent monitoring process is running. Determine the cause of the error, and then re-execute the command.

KNAC1773-E

The agent monitoring process rejected a request. : maintenance-information-1

The agent monitoring process rejected the request.

(S)

Terminates command processing.

(O)

Follow the instructions in the message output by the agent monitoring process.

KNAC1774-E

Insufficient memory occurred while communicating with the agent monitoring process. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

The command could not be executed, because communication with the agent monitoring process was impossible.

(S)

Terminates command processing.

(O)

Examine the status of each process that was running when the problem occurred, and check whether the estimated amount of memory is available. If necessary, re-execute the processes that caused memory to become insufficient.

KNAC1775-E

Resource lack occurred while communicating with the agent monitoring process. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

The command could not be executed, because communication with the agent monitoring process was impossible.

(S)

Terminates command processing.

(O)

Re-estimate the resources according to Release Notes.

KNAC1776-E

Unexpected error occurred while communicating with the agent monitoring process. : maintenance-information- maintenance-information-2 maintenance-information-3 maintenance-information-4

The command could not be executed, because communication with the agent monitoring process was impossible.

(S)

Terminates command 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 JP1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual JP1/Automatic Job Management System 3 Troubleshooting.

KNAC1777-E

Cannot execute because the agent monitoring process is processing the communication status confirmation.

The agent monitoring process has already started a communication status check.

(S)

Terminates command processing.

(O)

If necessary, re-execute the command after the communication status check finishes.

KNAC1778-E

Cannot execute because the agent monitoring process is not processing the communication status confirmation.

The agent monitoring process has already completed a communication status check.

(S)

Terminates command processing.

KNAC1801-E

Insufficient memory occurred. : maintenance-information-1 maintenance-information-2 maintenance-information-3

There is no shared memory.

(S)

Cancels the processing, and continues the process.

However, if the detected error is such that execution of the process cannot continue, the system stops the process.

(O)

Examine the status of each process that was running when the problem occurred, and check whether the estimated amount of memory is available. If necessary, re-execute the processes that caused memory to become insufficient.

KNAC1802-E

I/O error occurred. : maintenance-information-1 maintenance-information-2 maintenance-information-3

An I/O error occurred during the input or output of a file or during some other processing.

(S)

Cancels the processing for the file where the error occurred, and continues the process. If the I/O error of the system file prevented processing, the system cancels the process.

(O)

Take action according to the error information in the Windows event log or syslog output by the OS, and other OS-specific error information. If you cannot take corrective action, contact the system administrator, and collect data. For details, see 1.2.3 To the system administrators.

KNAC1803-E

File processing count exceeds the limit.

The maximum number of files that can be processed was exceeded.

(S)

Cancels the processing, and continues the process.

However, if the detected error is such that execution of the process cannot continue, the system stops the process.

(O)

Close unnecessary windows and dialog boxes, and delete unnecessary files to increase the amount of available space. Then retry the operation.

In UNIX, recheck 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)

Change the settings for the file system according to the Release Notes.

KNAC1804-E

Shared memory is not available. : maintenance-information-1 maintenance-information-2

Shared memory (a system resource) could not be secured. Alternatively, the necessary amount of shared memory is not available.

(S)

Cancels the processing, and continues the process.

However, if the detected error is such that execution of the process cannot continue, the system stops the process.

(O)

If the shared memory of the system is insufficient, adjust the kernel parameters.

KNAC1805-E

Resource lack occurred : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

A resource is insufficient.

(S)

Cancels the processing, and continues the process.

However, if the detected error is such that execution of the process cannot continue, the system stops the process.

(O)

Re-estimate the resources according to Release Notes.

KNAC1806-E

Not enough space in file system.

The file system does not have sufficient space.

(S)

Cancels the processing, and continues the process.

However, if the detected error is such that execution of the process cannot continue, the system stops the process.

(O)

Close unnecessary windows and dialog boxes, and delete unnecessary files to increase the amount of available space. Then retry the operation.

In UNIX, recheck 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)

Change the settings for the file system according to Release Notes.

KNAC1807-E

Only super user or administrator can execute.

A user who does not have superuser privileges or is not logged on as a member of the Administrators group.

A user who does not have administrator privileges or superuser privileges attempted to execute a command. If the environment is managed by AJS administrators, a user who is not an AJS administrator or does not have superuser privileges attempted to execute a command.

(S)

Cancels command execution.

(O)

Execute the command as a superuser or an administrator.

If the UAC function is enabled in Windows, the administrator must re-execute the command.

For an environment managed by AJS administrators, an AJS administrator or a user who has superuser privilege must execute the command.

KNAC1808-E

System error occurred. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

A system error occurred during processing.

(S)

Cancels the processing, and continues the process.

However, if the detected error is such that execution of the process cannot continue, the system stops the process.

(O)

Take action according to the error information in the Windows event log or syslog output by the OS, and other OS-specific error information. If you cannot take corrective action, contact the system administrator, and collect data. For details, see 1.2.3 To the system administrators.

KNAC1809-E

Unexpected error occurred in JP1/AJS3. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

An unexpected error occurred during processing.

(S)

Cancels the processing, and continues the process.

However, if the detected error is such that execution of the process cannot continue, the system stops the process.

(O)

Take action according to the message that was output before or after this error message. If you cannot take corrective action, contact the system administrator, and collect data. For details, see 1.2.3 To the system administrators.

9 Messages beginning with KNAD (Messages that are output by the installer and system management)

This chapter explains the messages beginning with KNAD (messages output by the installer and system management).

9.1 List of messages beginning with KNAD (messages 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.

If an attempt was made to install JP1/AJS3 - Manager

JP1/AJS3 - Manager cannot be installed on a system where one of the following products is already installed:

- JP1/AJS3 - Agent

- JP1/AJS3 - Agent Minimal Edition

- JP1/AJS2 - Agent

- JP1/AJS2 - Light Edition

If an attempt was made to install JP1/AJS3 - Agent

JP1/AJS3 - Agent cannot be installed on a system where one of the following products is already installed:

- JP1/AJS3 - Manager

- JP1/AJS2 - Manager

- JP1/AJS2 - Light Edition

If an attempt was made to install JP1/AJS3 - Agent Minimal Edition

JP1/AJS3 - Agent Minimal Edition cannot be installed on a system where one of the following products is already installed:

- JP1/AJS3 - Manager

- JP1/AJS3 - Agent

- JP1/AJS2 - Manager

- JP1/AJS2 - Agent

- JP1/AJS2 - Light Edition

(S)

Suspends installation.

(O)

Take action as follows:

Installing JP1/AJS3 - Manager

Uninstall the existing JP1/AJS3 - Agent, JP1/AJS3 - Agent Minimal Edition, 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.

Installing JP1/AJS3 - Agent Minimal Edition

Uninstall the existing JP1/AJS3 - Manager, JP1/AJS3 - Agent, JP1/AJS2 - Manager, JP1/AJS2 - Agent, or JP1/AJS2 - Light Edition, and then retry installing JP1/AJS3 - Agent Minimal Edition.

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 2016, Windows Server 2012, or Windows Server 2008.

A JP1/AJS3 product intended for Windows Server 2003 was mistakenly installed in a Windows Server 2016, 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 uninstallation.

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

The installation was suspended because an attempt was made to perform an overwrite installation or upgrade installation of a product version or evaluation version of JP1/AJS3 on a host on which the trial version is installed.

You cannot perform an overwrite installation or upgrade installation of the product version or evaluation version if the trial version is installed.

(S)

Suspends installation.

(O)

Uninstall the trial version, and then retry the installation of the product version or evaluation version.

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 2016, 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.

KNAD1021-E

An internal error occurred during JP1/AJS3 setup.(maintenance-information-1)

An internal error occurred during the setup that was automatically performed by JP1/AJS3 during the installation.

(S)

Suspends installation.

(O)

If an error occurred during a new installation, make sure that the user who performed the installation has the write permission for the installation folder. If the user does not have the write permission, assign the write permission to the user. Next, empty the installation folder, and then re-install the JP1/AJS3 product.

If you cannot resolve the problem, or if an error occurred at a timing other than during a new installation, collect the following data, and then contact the system administrator:

Details about performed operations

A hard copy of the dialog box displayed on the screen

Installation log (system-folder\Temp\HITACHI_JP1_INST_LOG folder)

If an error occurred during an overwrite installation or upgrade installation, also collect the execution results of the data collection tool.

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

#

For 64-bit versions of Windows, replace HKEY_LOCAL_MACHINE\SOFTWARE with HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node.

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 JP1/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 3. Messages beginning with KAVS (Messages about the scheduler and the common processing) 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 Upgrading JP1/AJS2 - Manager to JP1/AJS3 - Manager in the JP1/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

KNAD1704-Q

Over write installation from JP1/AJS3 - Agent Minimal Edition to JP1/AJS3 - Agent will begin. Do you want to continue?

Confirm whether to proceed with the over write installation from JP1/AJS3 - Agent Minimal Edition to JP1/AJS3 - Agent.

If you proceed, you will not be able to return to the JP1/AJS3 - Agent Minimal Edition.

(S)

Waits for a response.

(O)

Click Yes to perform the over write installation. If you do not want to proceed, click No and terminate the installation.

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.

Probable causes are listed below.

A timeout might have occurred, because the machine was under a heavy load when the system started or stopped, or when the virus scan or backup software started.

If this message is output when the process is started, many jobnets might be registered for execution or the execution generations of a jobnet might have been left unprocessed. Review the job operation settings. For details, see JP1/Automatic Job Management System 3 Overview.

(S)

Continues processing.

(O)

Take action as follows:

Check whether the machine is under a heavy load. If it is, change the operation settings to alleviate the load on the machine. For example, change the times when JP1/AJS3 is to be started and stopped.

If this message is output when the process is started, execute the jajs_spmd_status command to check whether the process indicated by management-target-process-name is running. If you cannot confirm that the process is running, wait a while and then try again. If the process has not started, restart JP1/AJS3. If this message is output while the process is stopped, stop the JP1/AJS3 service, and then check whether the process indicated by management-target-process-name remains. If the process remains, forcibly terminate it.

If you cannot solve the problem, use the data collection tool to collect data, and then contact the system administrator. For details, see 1.2.3 To the system administrators.

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.

KNAD3569-I

jajs_spmd: JP1/AJS3 start up the management-target-process-name

The indicated management target process will be started. management-target-process-name is the name of a process configured from all components under the control of system management.

(S)

Starts the management target process.

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.

KNAD3581-I

jajs_spmd_stop : JP1/AJS3 send the stop request to the management-target-process-name

A stop request will be sent to the indicated management target process. management-target-process-name is the name of a process configured from all components under the control of system management.

(S)

Continues processing.

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.

KNAD3598-I

jajs_spmd_stop -kill : JP1/AJS3 execute the kill stop tomanagement-target-process-name

The indicated management target process will be stopped forcibly. management-target-process-name is the name of a process configured from all components under the control of system management.

(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 6.3.1 Restarting an abnormally terminated JP1/AJS3 process in the JP1/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.

If the environment setting parameters are specified by using the jbssetcnf command, make sure that the specified definition key and environment setting parameters are correct. If the settings are not correct, restore the original settings (before the change) from the backup, and then correct the settings. If there is no backup, install JP1/AJS3 again, and then set the environment setting parameters.

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

(O)

Check whether the process name specified for the -n option of the system management command is correct.

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.

(O)

Check whether the process name specified for the -n option of the system management command is correct.

KNAD3686-E

Shared memory is not available. return code = return-code

An attempt to secure shared memory has failed.

Probable causes are listed below.

Invalid specification in the environment setting parameter.

- In UNIX

The shared memory size and values of the kernel parameter settings exceeds.

After logical hosts or scheduler services were deleted, the ajsshmdel command was not executed.

While at least one instance of JP1/AJS3 was running on a physical or logical host, the configuration of logical hosts or scheduler services was changed or the ajsshmdel command was executed.

(S)

Terminates the system management command.

(O)

Check the environment settings and take the following action:

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.

After logical hosts or scheduler services were deleted, the ajsshmdel command was not executed. Stop all instances of JP1/AJS3 on physical and logical hosts, execute the ajsshmdel command, and then start JP1/AJS3.

While at least one instance of JP1/AJS3 was running on a physical or logical host, the configuration of logical hosts or scheduler services was changed or the ajsshmdel command was executed. Stop all instances of JP1/AJS3 on physical and logical hosts, execute the ajsshmdel command, and then start JP1/AJS3.

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 JP1/Automatic Job Management System 3 Command Reference.

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 20.6 Setting up the event/action control environment in the JP1/Automatic Job Management System 3 Configuration Guide.

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 6.3.1 Restarting an abnormally terminated JP1/AJS3 process in the JP1/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 JP1/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.

KNAD3742-I

JP1/AJS3 completed the individually kill stop

JP1/AJS3 has completed sending of individual forced stop requests.

(S)

Continues processing.

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.

(O)

The process indicated by management-target-process-name might have terminated abnormally. Check for a message that reports abnormal termination, and take action as necessary.

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.

(O)

Check whether there is a system memory shortage and whether the product has been installed correctly. Later, if necessary, restart JP1/AJS3.

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.

(O)

The process indicated by child-process-ID-of-management-target-process might have terminated abnormally. Check for a message that reports abnormal termination, and take action as necessary.

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 6.3.1 Restarting an abnormally terminated JP1/AJS3 process in the JP1/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.

(O)

Stopping the process might have taken longer than usual. Check whether the machine is under a heavy load.

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: JP1/Base User's Guide or JP1/Automatic Job Management System 3 Configuration Guide. 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.

(O)

Stopping the process might have taken longer than usual. Check whether the machine is under a heavy load.

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.

If the environment setting parameters are specified by using the jbssetcnf command, make sure that the specified definition key and environment setting parameters are correct. If the settings are not correct, restore the original settings (before the change) from the backup, and then correct the settings. If there is no backup, install JP1/AJS3 again, and then set the environment setting parameters.

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 11.2.1 Switching operation to the remote site in the JP1/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 11.2.1 Switching operation to the remote site in the JP1/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.

KNAD3982-I

jajs_spmd_stop -job : JP1/AJS3 send the job restriction stop request to the management-target-process-name

A request to stop job restrictions will be sent to the indicated management target process. management-target-process-name is the name of a process configured from all components under the control of system management.

(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 JP1/Automatic Job Management System 3 Command Reference.

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.

KNAD3995-I

SSL communication settings for the logical host are enabled.(logical-host-name, AJS3SSL = preset-value)

The communication encryption function on the logical host (logical-host-name) is enabled.

The value set in the AJS3SSL environment setting parameter indicates the range of encrypted communication.

(S)

Continues processing.

KNAD3996-I

SSL communication settings for the logical host are disabled.(logical-host-name)

The communication encryption function on the logical host (logical-host-name) is disabled.

(S)

Continues processing.

10 Messages beginning with KNAK (Messages about JP1/AJS3 - Web Console)

This chapter explains the messages that begin with KNAK (messages about JP1/AJS3 - Web Console).

10.1 List of messages that begin with KNAK (messages about the JP1/AJS3 - Web Console installer)

This section lists messages that begin with KNAK (messages about the JP1/AJS3 - Web Console installer).

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

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

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

Cancels 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

If an error occurs during an overwrite installation or upgrade installation, also collect the following data:

Execution results of the data collection tool

KNAK1604-E

Setting of license management information failed. The installation will stop.(maintenance-information)

Installation was suspended because setting of license management information failed.

(S)

Cancels 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

If an error occurs during an overwrite installation or upgrade installation, also collect the following data:

Execution results of the data collection tool

KNAK1606-E

The user who executed the installation is not an administrator. An administrator is required to install this product.

The product could not be installed because the user who executed the installation does not have administrator permissions.

(S)

Cancels installation.

(O)

Install the JP1/AJS3 product as a user who has administrator permissions.

KNAK1607-E

An internal error occurred during JP1/AJS3 setup. (maintenance-information)

An error occurred during the setup that was automatically performed by JP1/AJS3 during installation. The probable causes are:

The port number that is to be used by JP1/AJS3 - Web Console is already in use by another program.

The system drive (%systemdrive%) does not have sufficient free space.

The installation drive does not have sufficient free space.

(S)

Cancels 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

Installation log

If an error occurs during an overwrite installation or upgrade installation, also collect the following data:

Execution results of the data collection tool

KNAK1608-E

Error occurred at opening file. Installation stops. (maintenance-information)

Installation was suspended because the file used for installation could not be opened. The probable causes are:

The system drive (%systemdrive%) does not have sufficient free space.

You do not have read or write permission for the folder set in the system environment variable TEMP.

The name of the file that caused the error is indicated in maintenance-information.

(S)

Cancels 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

Installation log

If an error occurs during an overwrite installation or upgrade installation, also collect the following data:

Execution results of the data collection tool

KNAK1609-E

Error occurred at reading file. Installation stops. (maintenance-information)

Installation was suspended because the file used for installation could not be read. The probable cause is:

You do not have read or write permission for the folder set in the system environment variable TEMP.

The name of the file that caused the error is indicated in maintenance-information.

(S)

Cancels 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

If an error occurs during an overwrite installation or upgrade installation, also collect the following data:

Execution results of the data collection tool

KNAK1610-E

An internal error occurred during JP1/AJS3 unsetup. (maintenance-information)

An error occurred during the unsetup that was automatically performed by JP1/AJS3 during uninstallation.

The probable causes are:

An invalid value is specified in the environment settings file.

The file required for unsetup has been deleted.

(S)

Suspends uninstallation.

(O)

If an invalid value is specified in the environment settings file, correct the value. For any other case, perform an overwrite installation, and then perform uninstallation again.

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

Execution results of the data collection tool

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

If an error occurs during an overwrite installation or upgrade installation, also collect the following data:

Execution results of the data collection tool

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

10.2 List of messages that begin with KNAK (messages about the Web GUI)

This section lists messages that begin with KNAK (messages about the Web GUI).

KNAK2001-E

The host name is specified incorrectly.

The host name specified for the connection destination cannot be resolved.

(S)

Cancels processing.

(O)

Enter the correct host name.

KNAK2002-E

Cannot be added a monitoring target units because the number of monitoring target units had been reached the setting limit (upper-limit-value).

The number of monitoring target units that can be set has reached the maximum.

(S)

Cancels processing to add the environment setting.

(O)

Delete unnecessary monitoring target units. Alternatively, change the maximum number of monitoring target units that can be set, and then specify the monitoring target again.

KNAK2003-E

Specify field-name.

Nothing is specified for field-name.

(S)

Cancels processing.

(O)

Enter a value for the field name, and then retry.

KNAK2004-E

Cannot be added a monitoring target because the number of monitoring targets had been reached the display limit (upper-limit-value).

The number of monitoring targets displayed in the Dashboard window has reached the maximum.

(S)

Cancels processing to add the monitoring target.

(O)

Delete unnecessary monitoring targets to be displayed, and then add the monitoring target.

KNAK2005-E

Select a unit.

No unit is selected.

(S)

Cancels processing.

(O)

Select a unit you want to manipulate.

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

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

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

KNAK2009-E

In the cancellation period, for the end day specify a day after 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.

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

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

KNAK2012-E

Enter the values lower-limit-value - upper-limit-value in field-name.

The value entered for field-name is invalid. Alternatively, nothing is entered for field-name.

If this message is displayed for the date you entered, possible causes are as follows:

The format is incorrect.

A date in a year earlier than 1993 was entered.

A date in 2037 or a later year was entered.

A non-existent date was entered.

(S)

Cancels processing.

(O)

Reenter a value from lower-limit-value to upper-limit-value for field-name.

KNAK2013-E

The field-name is specified incorrectly.

The format of the value specified in field-name is incorrect.

(S)

Cancels processing.

(O)

Re-enter the value in the correct format in field-name.

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

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

KNAK2016-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 when the date and time are changed.

(S)

Cancels processing.

(O)

Specify a date after the current date for the execution start date, and then retry.

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

KNAK2018-E

Specify monitored units.

Monitored units are not specified.

(S)

Cancels processing.

(O)

Specify the units to be monitored, and then retry the operation.

KNAK2019-E

Specify the root jobnet. (unit-name)

The selected operation cannot be performed for the unit indicated by unit-name.

(S)

Cancels processing.

(O)

Select a root jobnet, and then retry.

KNAK2020-E

The specified return code range is invalid.

The specified range does not contain an integer value.

If the error pertains to the retry settings, possible causes are as follows:

The lower limit value specified for the return code of jobs that are automatically retried is equal to or smaller than the Abnormal value.

The upper limit value specified for the return code of jobs that are automatically retried is equal to or smaller than the Abnormal value.

The upper limit value specified for the return code of jobs that are automatically retried is smaller than the lower limit value.

(S)

Cancels processing.

(O)

Specify upper and lower limit values so that the range between those values include one or more integers.

KNAK2021-E

An attempt to open the Monitor dialog box failed because the URL was too long.

The Monitor screen was called, but its URL was truncated. The cause might be either of the following:

The maximum length of a URL that can be handled by the JP1/IM event guide function was exceeded.

The maximum length of a URL that can be handled by Internet Explorer was exceeded.

(S)

Stops processing, and closes the window.

(O)

If you are using the JP1/IM event guide function, see the JP1/IM Release Notes for details on the maximum lengths of URLs and how to change the maximum length restrictions.

If you are using Internet Explorer, consider using Firefox as the default browser.

KNAK2022-E

The accessed URL was invalid.

An attempt to access JP1/AJS3 - Web Console failed because the specified URL is invalid.

(S)

Cancels processing.

(O)

If access from a user-created application does not succeed, try again by specifying a valid URL.

If access from a hyperlink does not succeed, go to the Login screen and log in to JP1/AJS3 - Web Console. Then, in the Monitor dialog box, check the unit that is to be displayed.

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

KNAK2401-Q

Are you sure you want to log out?

This message asks you whether you want to log out of JP1/AJS3 - Web Console.

(S)

Waits for a response.

(O)

Click OK to log out, or click Cancel to cancel.

KNAK2402-Q

Are you sure you want to delete the settings for the monitoring target (monitoring-target-name)?

This message asks you whether you want to delete the settings of a monitoring target in the Dashboard window.

(S)

Waits for a response.

(O)

Click OK to delete the settings, or click Cancel to cancel.

KNAK2403-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 OK to set the hold attribute or Cancel to cancel.

KNAK2404-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 OK to release the hold attribute or Cancel to cancel.

KNAK2405-Q

Are you sure you want to operation the unit-name that has been scheduled at end-tim from start-time of YYYY-MM-DD?

Select a generation of the operation target.

This message asks you whether you want to perform operation on a generation of the unit.

(S)

Waits for a response.

(O)

To perform operation, select the target generation, and then click OK. Alternatively, click Cancel to cancel.

KNAK2406-W

Set the monitoring target.

Information about the monitoring target to be displayed in the Dashboard window does not exist.

(S)

This message indicates that information about the monitoring target to be displayed in the Dashboard window does not exist.

(O)

Use the Add Targets button to specify the monitoring target to be displayed in the Dashboard window.

KNAK2407-E

There is no response from the Server.

This message indicates that there is no response from the server or a timeout occurred during a wait for a response from the HTTP server or application server.

The probable causes are as follows:

Update processing is taking a long time due to a huge number of units to be displayed.

The HTTP server or application server is not running.

The HTTP server or application server is busy.

The HTTP server or application server is in a state in which a network connection cannot be established.

(S)

Cancels processing.

(O)

Make sure that the JP1/AJS3 HTTP Server service or the JP1/AJS3 Web Application Server service is running. If the service has stopped, restart it, and then log in again.

If the service has ended abnormally, recover it, and then log in again. Otherwise, correct the error, and then retry.

KNAK2408-E

Cannot connect to the Server.

This message indicates that an attempt to connect to the HTTP server or application server failed. The probable causes are:

The HTTP server or application server is not running.

The HTTP server or application server is busy.

The HTTP server or application server is in a state in which a network connection cannot be established.

(S)

Cancels processing.

(O)

If the HTTP server or application server is not running:

Restart the HTTP server or application server.

If the HTTP server or application server is busy:

A connection might be established by retrying the connection.

If the HTTP server or application server is in a state in which a network connection cannot be established:

Check the network environment of the HTTP server or application server. If a firewall is set up between the client and the HTTP server or application server, check the firewall settings.

If the session has been aborted, log in again.

KNAK2409-Q

The date has changed. Are you sure you want to update the displayed information with the new date? If you click the Cancel button, the currently displayed content will not be lost.

This message asks you whether you want to update the displayed information if the date changes while you are logged in.

(S)

Waits for a response.

(O)

Click OK to update the displayed information. Click Cancel if you do not want to change the displayed information.

KNAK2410-Q

If the selection status of the job group is changed, the settings for units to be monitored are cleared. Are you sure you want to change the selection status?

If you change the job group selected in the Set Monitoring Targets dialog box, this message asks you whether you want to clear the settings of the monitoring target unit added to the monitoring target list.

(S)

Waits for a response.

(O)

Click OK to clear the settings of the monitoring target unit added to the monitoring target list. Click Cancel if you do not want to clear the settings of the monitoring target unit.

KNAK2411-E

An error occurred in connect processing. Detailed information : detailed-information

This message indicates that an error occurred during communication with the HTTP server or application server.

(S)

Cancels processing, and then logs out of JP1/AJS3 - Web Console.

(O)

Correct the cause of the error, and then log in to JP1/AJS3 - Web Console again.

KNAK2412-E

A timeout occurred while waiting for the response from the connection destination.

This message indicates that a timeout occurred during update of displayed information or during a wait for a response from the HTTP server or application server.

The probable causes are as follows:

Update processing is taking a long time due to a huge number of units to be displayed.

The HTTP server or application server is not running.

The HTTP server or application server is busy.

The HTTP server or application server is in a state in which a network connection cannot be established.

(S)

Cancels processing.

(O)

Correct the error, and then retry.

KNAK2413-Q

The display might take a long time. Are you sure you want to display?

This message asks you whether you want to continue processing if displaying the window takes a long time.

This message appears if a very large number of units are to be displayed in the monitor dialog box. This message also appears if a very large number of units are to be displayed when a job flow under the jobnet selected in the tree area of the monitor dialog box is displayed in the map area.

(S)

Waits for a response.

(O)

Click OK to continue the display processing, or click Cancel to cancel.

KNAK2414-E

This operation cannot be executed because the execution ID cannot be acquired.

The specified operation cannot be performed because the execution ID for the operation target does not exist or cannot be acquired because, for example, the jobnet is unregistered.

(S)

Cancels processing.

(O)

Make sure that the execution ID for the operation target exists.

KNAK2415-I

Because the execution result exceeds the maximum size (5MB) of items that can be displayed, some results cannot be displayed.

Part of the execution result was not output because the output size of the execution result exceeds the maximum (5MB).

(S)

Indicates that part of the execution result was not output because the output size of the execution result exceeds 5MB (maximum).

KNAK2416-Q

All of the Web page will be reloaded because the Web browser has been displaying the screen for a long time. If you click the Cancel button, this message will appear again in 5 minutes.

In order to reduce the resource usage of the Web browser, the system checks whether you want to immediately reload all of the Web page when 25 hours passed from login or last reloaded time. The screen set to the initial display screen is displayed after the Web page is reloaded.

(S)

Waits for a response.

(O)

Click the OK button to reload the screen now, or click the Cancel button if you want to reload it later.

KNAK2417-W

A monitoring target unit that does not exist on the destination manager is included. Click the OK button on the monitored target setting dialog box to delete from the monitoring target settings monitoring target units that are not displayed.

This message indicates that a unit set to monitoring target does not exist on the destination manager. A monitoring target unit that does not exist on the destination manager is not displayed on the monitored target setting dialog box.

The probable causes are:

Unit has been deleted.

Unit name has been changed.

Unit has been changed to the unit type that can not set to the monitored.

(S)

Continues processing and displays the monitored target setting dialog box.

(O)

If a unit name has been changed, set a monitoring target unit again with the latest information.

Click the OK button on the monitored target setting dialog box to delete from the monitoring target settings monitoring target units that are not displayed.

If you do not want to change the setting of the monitoring target units, click the Cancel button on the monitored target setting dialog box.

KNAK2418-Q

Are you sure you want to interrupt unit-name (execution-ID)?

The system confirms whether you want to interrupt the jobnet.

(S)

Waits for a response.

(O)

Click OK to interrupt or Cancel to cancel.

KNAK2419-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 OK to forcibly terminate or Cancel to cancel.

KNAK2420-E

You cannot log in because acquisition of the manager information for the connection destination failed.

Information could not be obtained about the JP1/AJS3 - Manager instance to which a connection is to be established.

The probable causes are as follows:

Temporary problem on the network.

The JP1/AJS3 service is not started.

The web server or application server is not running.

The web server or application server is busy.

The web server or application server is in a state in which a network connection cannot be established.

(S)

Cancels processing.

(O)

Correct the cause of the error, and then log in to JP1/AJS3 - Web Console again.

KNAK2422-Q

If you change the tab display, the filter settings for all units will be cleared. Are you sure you want to change the display?

This message asks whether you want to change the tab display even if doing so will clear the filter settings for all units.

(S)

Waits for a response.

(O)

If you want to change the tab display (and, in doing so, clear the filter settings), click the OK button. If you do not want to change the tab display, click the Cancel button.

KNAK2423-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 OK to discontinue monitoring the start condition. Click Cancel to continue monitoring.

KNAK2424-Q

Are you sure you want to close the Monitor screen?

This message asks whether you want to close the Monitor screen.

(S)

Waits for a response.

(O)

If you want to close the Monitor screen, click the OK button. If you do not want to close the Monitor screen, click the Cancel button.

KNAK2425-E

The session that you are logged in to is no longer valid. Re-open the Monitor screen.

The session that you are logged in to is no longer valid, because the session timed out or the login information became invalid.

(S)

Stops processing, and closes the window.

(O)

Re-open the Monitor screen.

KNAK2426-I

There is no (Status|Result|Next-Schedule) that can be displayed in the Monitor dialog box.

The Monitor dialog box cannot be displayed, because the specified generation (status, result, or next schedule) does not exist for the selected jobnet.

(S)

Cancels processing.

(O)

In the List screen, make sure that the status of the generation to be checked is displayed for the selected jobnet.

KNAK2427-Q

Are you sure you want to cancel execution of unit-name (execution-ID)?

This message asks whether you want to cancel the execution of the unit.

(S)

Waits for a response.

(O)

If you want to cancel the execution of the unit, click the OK button. If you do not want to cancel the execution of the unit, click the Cancel button.

KNAK2428-Q

Are you sure you want to release the changes in unit-name (execution-ID)?

This message asks whether you want to release the temporary changes that were made in a unit execution schedule.

(S)

Waits for a response.

(O)

Click OK to release the changes, or Cancel to cancel the release.

KNAK2429-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 only if the specified job or jobnet meets both of the following conditions:

The upper-level jobnet has a schedule

There is no schedule of the same generation as the upper-level jobnet

(S)

Terminates the processing.

(O)

Check whether you added the correct unit.

KNAK2430-Q

There is a possibility that the jobnet will be executed immediately, because the specified start date and time (YYYY-MM-DD hh:mm:ss) is ealier than the present date and time (YYYY-MM-DD hh:mm:ss). Are you sure you want to make this change? (unit-name)

This message asks whether you want to continue the processing to change the date and time.

(S)

Waits for a response.

(O)

Click OK to continue the processing to change the date and time, or Cancel to cancel the processing to change the date and time.

10.3 List of messages that begin with KNAK (messages about JP1/AJS3 - Web Console commands)

This section lists messages that begin with KNAK (messages about JP1/AJS3 - Web Console commands).

KNAK2501-I

The service (service) will now start.

The service (service) will start.

(S)

Continues processing.

KNAK2502-I

The service (service) started.

The service has started normally.

(S)

Outputs to the log that the service has started.

KNAK2503-E

The service (service) failed to start.

An attempt to start the service failed because an error occurred during startup processing of the service.

(S)

Cancels startup processing of the service.

(O)

A message indicating the cause of the error was output to the command log or application server log before this message. Determine the cause of the error from the previously output message, and then take corrective action.

KNAK2504-W

The service (service) is already running.

If the service you want to start has already started, this message is output. The processing to start the service that has already started is skipped and other processing continues.

(S)

Continues processing.

KNAK2505-W

The service (service) is not running.

If the service you want to stop has already stopped, this message is output. The processing to stop the service that has already stopped is skipped and other processing continues.

(S)

Continues processing.

KNAK2506-I

The service (service) will now stop.

The service will now stop.

(S)

Continues processing.

KNAK2507-I

The service (service) has terminated.

The service terminated.

(S)

Outputs to the log that the service terminated.

KNAK2511-I

Setup of JP1/AJS3 - Web Console started.

Setup of JP1/AJS3 - Web Console has started.

(S)

Continues processing.

KNAK2512-I

Setup of JP1/AJS3 - Web Console ended successfully.

Setup of JP1/AJS3 - Web Console ended successfully.

(S)

Continues processing.

KNAK2513-E

Failed to set up JP1/AJS3 - Web Console.

An attempt to set up JP1/AJS3 - Web Console failed.

(S)

Cancels command execution.

(O)

A message indicating the cause of the error was output to the command log before this message. Determine the cause of the error from the previously output message, and then take corrective action.

KNAK2514-I

Unsetup of JP1/AJS3 - Web Console started.

Unsetup of JP1/AJS3 - Web Console has started.

(S)

Continues processing.

KNAK2515-I

Unsetup of JP1/AJS3 - Web Console ended successfully.

Unsetup of JP1/AJS3 - Web Console ended successfully.

(S)

Continues processing.

KNAK2516-E

Failed to perform unsetup of JP1/AJS3 - Web Console.

An attempt to perform unsetup of JP1/AJS3 - Web Console failed.

(S)

Cancels command execution.

(O)

A message indicating the cause of the error was output to the command log before this message. Determine the cause of the error from the previously output message, and then take corrective action.

KNAK2517-E

A system error has occurred. : maintenance-information

A system error occurred during processing. The execution environment of the JP1/AJS3 Web Application Server service might have a problem.

(S)

Terminates the processing where the error occurred.

(O)

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

KNAK2518-E

Insufficient memory occurred. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

Memory became insufficient in the execution environment for the monitored JP1/AJS3 - Manager or JP1/AJS3 Web Application Server service.

(S)

Terminates the processing where the error occurred.

(O)

Check the physical memory usage for the host on which the JP1/AJS3 Web Application Server service is running.

If available physical memory is not sufficient, terminate unnecessary applications to increase the amount of available physical memory. (For details about the physical memory requirements in JP1/AJS3 - Web Console, see the Release Notes.)

KNAK2519-E

Unexpected error occurred in JP1/AJS3 - Web Console. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

An unexpected error occurred during processing. The execution environment of the JP1/AJS3 Web Application Server service might have a problem.

(S)

Terminates the processing where the error occurred.

(O)

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

KNAK2520-I

Output of settings data will now start.

Output of settings information will start.

(S)

Continues processing.

KNAK2521-I

Output of settings data ended.

Output of settings information has ended.

(S)

Continues processing.

KNAK2522-E

A timeout occurred while the service(service) was being started. (maintenance information = maintenance-information-1)

An attempt to start the service failed because a timeout occurred during startup processing.

(S)

Cancels startup processing of the service.

(O)

A timeout might occur during startup of the system or due to a temporarily high load. Correct the cause of the timeout, and then perform the processing again.

KNAK2523-E

A timeout occurred while the service(service) was being stopped. (maintenance information = maintenance-information-1, maintenance-information-2)

An attempt to stop the service failed because a timeout occurred during stop processing of the service.

(S)

Cancels stop processing of the service.

(O)

A timeout might occur during startup of the system or due to a temporarily high load. Correct the cause of the timeout, and then perform the processing again.

KNAK2524-E

An error occurred while the service (service) was being started. (maintenance information = maintenance-information-1, maintenance-information-2)

An attempt to start the service failed because an error occurred during startup processing of the service. The probable causes are:

The definition file contains an error.

A timeout occurred.

JP1/AJS3 HTTP Server is started twice (when the service is JP1/AJS3 HTTP Server).

(S)

Cancels startup processing of the service.

(O)

Correct the cause of the error, and then perform the processing again.

KNAK2525-E

An error occurred while the service (service) was being stopped. (maintenance information = maintenance-information-1, maintenance-information-2, maintenance-information-3, maintenance-information-4)

An attempt to stop the service failed because an error occurred during stop processing of the service. The probable causes are:

The definition file contains an error.

A timeout occurred.

(S)

Cancels stop processing of the service.

(O)

Correct the cause of the error, and then perform the processing again.

KNAK2526-I

SERVICE : maintenance-information

This message indicates the progress of starting or stopping of the service.

(S)

Outputs, to the log, the progress of starting or stopping of the service.

KNAK2528-W

Setup of the JP1/AJS3 - Web Console ended with warning.

When the log output processing could not be initialized, this message is output.

(S)

Continues processing.

(O)

No action is required because setup is completed.

KNAK2529-W

Unsetup of the JP1/AJS3 - Web Console ended with warning.

When the log output processing could not be initialized, this message is output.

(S)

Continues processing.

(O)

No action is required because unsetup is completed.

KNAK2551-E

Failed to load the environment configuration file.

Processing was canceled because an attempt to read the environment settings file failed.

(S)

Terminates the processing where the error occurred.

(O)

Make sure that read permission for the environment settings file is set. If it is not, change the settings, and then re-execute the command.

If this error occurred when the service was started, stop the JP1/AJS3 HTTP Server service, and then restart the JP1/AJS3 Web Application Server service. Then start the JP1/AJS3 HTTP Server service.

KNAK2552-E

The environment configuration file contains incorrect specifications. (detailed-information)

Processing was canceled because the environment settings file contains an incorrect specification.

(S)

Terminates the processing where the error occurred.

(O)

Set the environment settings file correctly. After changing the settings, re-execute the command.

If this error occurred when the service was started, stop the JP1/AJS3 HTTP Server service, and then restart the JP1/AJS3 Web Application Server service. Then, start the JP1/AJS3 HTTP Server service.

KNAK2554-E

The shared directory is specified incorrectly. (shared-directory)

The logical host settings are incorrect. The probable causes are:

The specified shared directory does not exist.

The length of the specified shared directory name exceeds the maximum.

(S)

Terminates the processing where the error occurred.

(O)

Make sure that the specified shared directory can be used.

KNAK2556-E

The same command cannot be executed redundantly.

Processing was canceled because commands were executed concurrently.

(S)

Terminates the processing where the error occurred.

(O)

Executing multiple commands concurrently might cause an error. If an error occurs, re-execute the command.

KNAK2558-E

I/O error occurred. (file-name) : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

An error occurred during file I/O processing. The probable causes are:

You do not have access permission for the file.

Another process is using the file.

(S)

Terminates the processing where the error occurred.

(O)

Correct the cause of the error, and then perform the processing again.

KNAK2601-E

The log output processing could not be initialized. Detailed information (detailed-information-1, detailed-information-2, detailed-information-3, detailed-information-4)

An attempt to initialize output processing of the integrated trace log or the command log failed.

(S)

Cancels startup processing if the error occurs in the JP1/AJS3 Web Application Server service in Windows.

For any other case, the system continues processing.

(O)

If an error message relating to the environment configuration file is output before this message, take action according to the contents of the error message.

For other cases, use the data collection tool to collect data, and then contact the system administrator.

KNAK2602-W

The log could not be output. Detailed information (detailed-information-1, detailed-information-2, detailed-information-3, detailed-information-4)

Output processing of the integrated trace log failed. The integrated trace function might have a problem.

(S)

Cancels output processing of the integrated trace log, and then continues processing.

(O)

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

KNAK2603-W

Log output processing failed to complete. Detailed information (detailed-information-1, detailed-information-2, detailed-information-3, detailed-information-4)

An attempt to terminate output processing of the integrated trace log failed.

(S)

Continues processing.

(O)

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

KNAK2651-E

Illegal option (option) exists.

An invalid option was specified.

(S)

Cancels command execution.

(O)

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

KNAK2652-E

Value for option (option) is not specified.

The option does not contain any value.

(S)

Cancels command execution.

(O)

Specify the value for the option, and then re-execute the command.

KNAK2653-E

Invalid value for option (option).

The option contains an invalid value.

(S)

Cancels command execution.

(O)

Specify the value for the option, and then re-execute the command.

KNAK2654-E

Option (Option) appears twice or more.

The same option is specified more than once.

(S)

Cancels command execution.

(O)

Specify the indicated option only once, and then re-execute the command.

KNAK2655-E

The specified argument is incorrect.

The specified argument is incorrect.

(S)

Cancels command execution.

(O)

Check and, if necessary, revise the specified arguments, and then re-execute the command.

KNAK2657-E

Failed to access shared directory.

An attempt to access the shared directory failed.

(S)

Cancels command execution.

(O)

Make sure that the specified shared directory exists. If it exists, make sure that you have view and update permissions for the specified shared directory.

KNAK2658-E

Failed to create shared directory (directory-name).

An attempt to create a shared directory has failed.

(S)

Cancels command execution.

(O)

Make sure that the following jp1ajs3web directory indicated in the message does not already exist.

In Windows:

specified-shared-directory-name\jp1ajs3web

In UNIX:

specified-shared-directory-name/jp1ajs3web

If the jp1ajs3web directory exists, make sure that the specified shared directory name is correct. If it is correct, make sure that the jp1ajs3web directory is not needed, delete it, and then re-execute the command (do not delete a shared directory).

If the jp1ajs3web directory does not exist, check whether you have permission to update the specified shared directory.

KNAK2660-E

Only super user or administrator can execute.

A user who does not have superuser privileges or administrator privileges attempted to execute a command.

(S)

Cancels command execution.

(O)

Execute the command as a superuser or an administrator.

If the UAC function is enabled in Windows, the administrator must re-execute the command.

KNAK2701-I

The command (command) started.

Processing of the command (command) will start.

(S)

Continues processing.

KNAK2702-I

The command (command) ended normally.

Processing of the command (command) ended normally.

(S)

Outputs to the log that the command ended normally.

KNAK2703-E

The command (command) ended abnormally.

Processing of the command (command) ended abnormally.

(S)

Outputs to the log that the command ended abnormally.

(O)

Messages indicating the cause of the error were output to the standard error output before this message. Determine the cause of the error from these messages.

KNAK2708-E

The expiration of the time limit. JP1/AJS3 - Web Console

The expiration date of the evaluation version has been exceeded.

(S)

Cancels startup processing of the JP1/AJS3 Web Application Server service.

KNAK2709-E

JP1/AJS3 - Web Console service is set up already.

Setup processing of JP1/AJS3 - Web Console was not performed because the JP1/AJS3 - Web Console service has already been set up.

(S)

Terminates setup processing.

(O)

Make sure that the JP1/AJS3 - Web Console service has been set up.

KNAK2710-E

An error occurred during installing JP1/AJS3 - Web Console service. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

An error occurred during setup of the JP1/AJS3 - Web Console service. The execution environment of the JP1/AJS3 - Web Console service might have a problem.

(S)

Terminates setup processing.

(O)

Execute the setup command as an OS user with administrator permissions. If the UAC function is enabled in Windows, the administrator must re-execute the command. Note that memory or free space on the disk might be insufficient. Terminate unnecessary applications, and then re-execute the setup command.

KNAK2712-E

An error occurred during removing JP1/AJS3 - Web Console service. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

An error occurred while the JP1/AJS3 - Web Console service was being set up.

(S)

Terminates setup processing.

(O)

Execute the setup command as an OS user with administrator permissions. Note that memory or free space on the disk might be insufficient. Terminate unnecessary applications, and then re-execute the setup command.

KNAK2714-E

Setup cannot be performed because the service (service) is active.

Setup cannot be performed because the service is running.

(S)

Terminates setup processing.

(O)

Check whether the JP1/AJS3 - Web Console service has stopped.

KNAK2715-W

The command(command) ended warning.

Processing of the command (command) ended with a warning.

(S)

Outputs to the log that the command ended with a warning.

(O)

A message indicating the cause of the warning was output to the log before this message. Determine the cause of the error from the previously output log message, and then take corrective action.

Note that when the JP1/AJS3 Web Application Server service stops, this message might appear at the end of the command even if no error message or warning message was output. In such a case, no action is required for this message. This situation occurs because some processes have already been stopped internally, and the message indicates that stop processing of the JP1/AJS3 Web Application Server service has completed normally.

10.4 List of messages that begin with KNAK (messages about the web application server and APIs)

This section lists the messages that begin with KNAK (messages about the web application server and APIs).

KNAK3001-I

The JP1/AJS3 Web Application Server service will now start.

This message indicates that startup processing of the JP1/AJS3 Web Application Server service has started.

(S)

Outputs to the log that startup processing of the JP1/AJS3 Web Application Server service has started.

KNAK3002-I

The JP1/AJS3 Web Application Server service started.

This message indicates that the JP1/AJS3 Web Application Server service has started.

(S)

This message indicates that the JP1/AJS3 Web Application Server service has started.

KNAK3003-E

An error occurred in the processing to start the JP1/AJS3 Web Application Server service.

This message indicates that an error occurred during startup processing of the JP1/AJS3 Web Application Server service.

(S)

Outputs to the log that an error occurred during startup processing of the JP1/AJS3 Web Application Server service.

(O)

A message indicating the cause of the error was output to the application server log before this message. Determine the cause of the error from the previously output message, and then take corrective action.

KNAK3004-E

An unexpected error occurred in the processing to start the JP1/AJS3 Web Application Server service.

An unexpected error occurred during startup processing of the JP1/AJS3 Web Application Server service.

(S)

Cancels processing.

(O)

The configuration of JP1/AJS3 - Web Console might have been corrupted. Perform a repair installation.

KNAK3005-I

The JP1/AJS3 Web Application Server service will now stop.

This message indicates that stop processing of the JP1/AJS3 Web Application Server service has started.

(S)

Outputs to the log that stop processing of the JP1/AJS3 Web Application Server service has started.

KNAK3006-I

The JP1/AJS3 Web Application Server service stopped.

This message indicates that the JP1/AJS3 Web Application Server service stopped.

(S)

This message indicates that the JP1/AJS3 Web Application Server service stopped.

KNAK3026-I

API processing will now start. (api type = API-type)

This message indicates that API processing will start.

(S)

Outputs to the log that API processing will start.

KNAK3027-I

API processing ended. (api type = API-type)

This message indicates that API processing ended normally.

(S)

Outputs to the log that API processing ended normally.

KNAK3028-E

An error occurred in the API processing. (api type = API-type)

This message indicates that an error occurred during API processing.

(S)

Outputs to the log that an error occurred during API processing.

(O)

Take action according to the message output before or after this message.

KNAK3029-I

exception-class-information

This message indicates the location where an exception occurred.

(S)

Outputs, to the log, the location where an exception occurred.

KNAK3030-I

stack-trace-information

This message indicates stack trace information, which is output according to the language type set in the OS.

(S)

Outputs stack trace information to the log.

KNAK3031-I

API-input-information

This message indicates API input information.

(S)

Outputs API input information to the log.

KNAK3032-I

API-return-value-information

This message indicates API return value information.

(S)

Outputs API return value information to the log.

KNAK3033-I

API-execution-information

This message indicates API execution information.

(S)

Outputs API execution information to the log.

KNAK3051-W

The file was not found. Processing will continue by using the default values. (file =file-name)

The file was not found.

(S)

Assumes the default value and continues processing.

KNAK3052-E

Failed to read the file. (file =file-name, maintenance information = maintenance-information)

An error occurred during input processing of the file indicated in file-name. The probable causes are:

An invalid character is specified in the file name or folder name.

The length of the file name, folder name, or file path is not correct.

You do not have access permission for the file or the folder containing the file.

Free space on the disk is insufficient.

Another program is editing the file.

(S)

Cancels processing.

(O)

Correct the cause of the error, and then stop the JP1/AJS3 HTTP Server service. Then, restart the JP1/AJS3 Web Application Server service, and then start the JP1/AJS3 HTTP Server service.

KNAK3053-W

Failed to read the file. Processing will continue by using the default values. (file =file-name, maintenance information = maintenance-information)

An error occurred during input processing of the file indicated in file-name. The probable causes are:

An invalid character is specified in the file name or folder name.

The length of the file name, folder name, or file path is not correct.

You do not have access permission for the file or the folder containing the file.

Free space on the disk is insufficient.

Another program is editing the file.

(S)

Assumes the default value and continues processing.

KNAK3054-E

An error occurred while the file was being accessed. (file =file-name, maintenance information = maintenance-information)

An error occurred during access to the file indicated in file-name. The probable causes are:

An invalid character is specified in the file name or folder name.

The length of the file name, folder name, or file path is not correct.

You do not have access permission for the file or the folder containing the file.

Free space on the disk is insufficient.

Another program is editing the file.

(S)

Cancels processing.

(O)

Correct the cause of the error, and then stop the JP1/AJS3 HTTP Server service. Then, restart the JP1/AJS3 Web Application Server service, and then start the JP1/AJS3 HTTP Server service.

KNAK3055-W

An error occurred while the file was being accessed. Processing will continue by using the default values. (file =file-name, maintenance information = maintenance-information)

An error occurred during access to the file indicated in file-name. The probable causes are:

An invalid character is specified in the file name or folder name.

The length of the file name, folder name, or file path is not correct.

You do not have access permission for the file or the folder containing the file.

Free space on the disk is insufficient.

Another program is editing the file.

(S)

Assumes the default value and continues processing.

KNAK3056-E

The specified file is incorrect. (file = file-name, line = line-number)

Processing was canceled because the file was specified incorrectly.

(S)

Cancels processing.

(O)

For the environment settings file:

Specify the environment settings file correctly. After changing the settings, stop the JP1/AJS3 HTTP Server service. Then, restart the JP1/AJS3 Web Application Server service, and then start the JP1/AJS3 HTTP Server service.

Note that line-number indicates an approximate location of the incorrect specification. If the specification on the line indicated by line-number is correct, also check the specifications before and after that line.

KNAK3057-W

The specified value for the keyword is invalid. Processing will continue by using the default values. (file = file-name, keyword = keyword, line = line-number)

The value for the keyword is specified incorrectly.

(S)

Assumes the default value and continues processing.

KNAK3058-W

A keyword is not specified. Processing will continue by using the default values. (file = file-name, keyword = keyword)

Because a keyword is not specified, processing continues by using the default value.

(S)

Assumes the default value and continues processing.

KNAK3059-I

configuration-definition-information

This message indicates the configuration definition information loaded into memory.

(S)

Outputs the configuration definition information loaded into memory to the log.

KNAK3060-W

FILE RETRY WAITING ERR (maintenance information = maintenance-information-1, maintenance-information-2)

This message indicates that an attempt to wait for a file access retry failed.

(S)

Outputs to the log that an attempt to wait for a file access retry failed.

KNAK3061-W

FILE CLOSE ERR (maintenance information = maintenance-information-1, maintenance-information-2)

This message indicates that an attempt to close the file failed.

(S)

Outputs to the log that an attempt to close the file failed.

KNAK3062-I

The file (file-name) was read.

This message indicates that reading of the file terminated normally.

(S)

Outputs to the log that reading of the file terminated normally.

KNAK3063-E

Failed to write the file. (file = file-name, maintenance information = maintenance-information)

An error occurred during output processing of the file indicated in file-name. The probable causes are:

An invalid character is specified in the file name or folder name.

The length of the file name, folder name, or file path is not correct.

You do not have access permission for the file or the folder containing the file.

Free space on the disk is insufficient.

Another program is editing the file.

(S)

Cancels processing.

(O)

Correct the error, and then retry.

KNAK3064-I

The file was written. (file = file-name)

This message indicates that writing to the file terminated normally.

(S)

Outputs to the log that writing to the file terminated normally.

KNAK3065-E

The specified value for the keyword is invalid. (location = location, keyword = keyword)

The value for the keyword is specified incorrectly.

(S)

Cancels processing.

(O)

Correct the value specified for the keyword indicated in keyword, and then restart the JP1/AJS3 - Web Console service.

KNAK3066-E

A keyword is not specified. (location = location, keyword = keyword)

The necessary keyword is not specified.

(S)

Cancels processing.

(O)

Specify the necessary keyword and its value, and then restart the JP1/AJS3 - Web Console service.

KNAK3101-E

The connection destination JP1/AJS3 - Manager or scheduler service does not support the system.

The connection destination JP1/AJS3 - Manager or scheduler service does not support the system.

(S)

Cancels processing.

(O)

Make sure that the connection destination JP1/AJS3 - Manager or scheduler service meets the following condition:

The version of JP1/AJS3 - Manager at the connection destination is 11-00 or later.

The database configuration of scheduler service at the connection destination is a standard configuration.

KNAK3102-E

The session that you are logged in to is no longer valid. Log in again.

The session to which you are logged in is already invalid. Log in again.

(S)

Cancels processing.

(O)

Log in again, and then retry the operation.

KNAK3103-W

The session that you are logged in to is no longer valid.

The session to which you are logged in is already invalid.

(S)

Outputs to the log that the session to which you are logged in is already invalid.

KNAK3104-I

Session created. (maintenance information = maintenance-information)

This message indicates that a session is created.

(S)

Outputs to the log that a session is created.

KNAK3105-I

The session timed out. (maintenance information = maintenance-information)

This message indicates that the session timed out.

(S)

Outputs to the log that the session timed out.

KNAK3106-I

The session deleted. (maintenance information = maintenance-information)

This message indicates that the session is deleted.

(S)

Outputs to the log that the session is deleted.

KNAK3151-E

The log output processing could not be initialized. (detailed information = detailed information-1, detailed information-2, detailed information-3, detailed information-4, detailed information-5, detailed information-6)

An error occurred during initialization of the log output processing. The probable causes are:

You do not have access permission for files under the log folder.

Free space on the disk is insufficient.

(S)

Cancels processing.

(O)

Correct the cause of the error. If you cannot resolve the problem, the configuration of JP1/AJS3 - Web Console might have been corrupted. Perform a repair installation.

KNAK3152-W

The log could not be output. (detailed information = detailed information-1, detailed information-2, detailed information-3, detailed information-4, detailed information-5, detailed information-6, detailed information-7)

An error occurred during log output processing. The probable causes are:

You do not have access permission for files under the log folder.

Free space on the disk is insufficient.

(S)

Continues processing.

(O)

Correct the cause of the error. If you cannot resolve the problem, the configuration of JP1/AJS3 - Web Console might have been corrupted. Perform a repair installation.

KNAK3153-W

Log output processing failed to complete. (detailed information = detailed-information-1, detailed-information-2, detailed-information-3, detailed-information-4, detailed-information-5, detailed-information-6, detailed-information-7)

An error occurred during termination of log output processing. The probable causes are:

You do not have access permission for files under the log folder.

Free space on the disk is insufficient.

(S)

Continues processing.

(O)

Correct the cause of the error. If you cannot resolve the problem, the configuration of JP1/AJS3 - Web Console might have been corrupted. Perform a repair installation.

KNAK3201-E

Specify the item-name.

The probable causes are as follows:

The item indicated in item-name is not specified.

A null string is specified for item-name.

The array specified for item-name has no elements. Alternatively, one of the elements of the specified array is a null string.

(S)

Cancels processing.

(O)

Correct the error, and then retry.

If item-name is not specified, specify it.

If a null string is specified for item-name, specify a valid value that is not a null string.

If an array with no elements is specified for item-name, specify an array with at least one element. If an array containing an element that is a null string is specified for item-name, specify a valid value that is not a null string for each valid array element.

KNAK3202-E

Enter a value in the range numeric - numeric (bytes) for the item-name.

The value specified for the item (item-name) is not in the range of specifiable values.

(S)

Cancels processing.

(O)

For the item, specify a value that does not exceed the length indicated in numeric.

KNAK3203-E

Specify a value in the range lower-limit-value - upper-limit-value for the item-name. (specified-value)

The specification of the item indicated in item-name exceeds the limit value.

(S)

Cancels processing.

(O)

For the item indicated in item-name, specify a value in the range from lower-limit-value to upper-limit-value.

KNAK3204-E

The item-name contains an invalid character. (specified-value)

An invalid character is specified for the item indicated in item-name.

(S)

Cancels processing.

(O)

Specify the item by using valid characters.

KNAK3205-E

A specification for a regular expression in the item-name is incorrect. (specified-value)

The regular expression for the item indicated in item-name is specified incorrectly.

(S)

Cancels processing.

(O)

To specify the regular expression, make sure that the specified character string does not end with a yen sign (\).

KNAK3206-E

The item-name is specified incorrectly. (specified-value)

The value for the item indicated in item-name is specified in invalid format.

(S)

Cancels processing.

(O)

Specify the item correctly.

KNAK3207-E

The item-name cannot be omitted if the comparison method is match-method.

The item indicated in item-name or the match method is specified incorrectly.

(S)

Cancels processing.

(O)

Specify a value for item indicated in item-name, or change the method indicated in match-method.

KNAK3208-E

The specification count for the item-name exceeds numeric.

The specification of the item indicated in item-name exceeds the limit value.

(S)

Cancels processing.

(O)

Make sure that the specified number of items is equal to or smaller than the value indicated in numeric.

KNAK3209-E

Specify the item-name or the item-name.

Items indicated in item-name and item-name cannot be specified together.

(S)

Cancels processing.

(O)

Specify either of the items indicated in item-name and item-name.

KNAK3210-E

specified-value and specified-value cannot be specified at the same time.

Parameters that cannot be specified together are specified.

(S)

Cancels processing.

(O)

Specify either of the values indicated in specified-value and specified-value.

KNAK3211-E

The unit hierarchy exceeds the maximum value (maximum-hierarchy-level). (full-unit-name)

The unit hierarchy in the specified full unit name exceeds the maximum.

(S)

Cancels processing.

(O)

Specify the unit hierarchy within the maximum.

KNAK3212-E

The user name or password is invalid.

Login was not possible due to an invalid JP1 user name or password.

(S)

Cancels processing.

(O)

Enter the JP1 user name and the password registered in the authentication server at the connection destination, and then log in again.

KNAK3213-E

For the start date of item-name, specify a date before the end date. (start date = specified-value, end date = specified-value)

A date after the end date is specified for the start date of the item (item-name).

(S)

Cancels processing.

(O)

Change the start date for the item indicated in item-name to a date before the end date.

KNAK3214-E

For the start time of item-name, specify a time before the end time. (start time = specified-value, end time = specified-value)

A time after the end time is specified for the start time of the item (item-name).

(S)

Cancels processing.

(O)

For the start time, specify a time before the end time. You can specify the elapsed time (in seconds) since 00:00:00 on 1970-01-01 (UTC format) converted to ISO 8601 format (YYYY-MM-DDThh:mm:ssTZD).

KNAK3215-E

Immediate registrations with start conditions specified cannot be performed for an Operation Net scheduler service unit.

Start conditions cannot be used with a unit under an Operation Net scheduler service.

(S)

Cancels processing.

(O)

If the unit is under an Operation Net scheduler service, register the unit for execution without specifying a start condition.

KNAK3216-E

The request is incorrect.

Processing is canceled because the request is specified incorrectly.

(S)

Cancels processing.

(O)

Specify the request correctly.

Check the following:

Make sure that api-version is specified in the URI.

Make sure that objects is specified in the URI correctly.

Make sure that a resource ID is specified in the URI correctly.

Make sure that a full unit name is specified in the URI.

Make sure that an execution ID is specified in the URI.

Make sure that a release ID is specified in the URI.

Make sure that the HTTP method is correct.

For an API call for which the message body of the request must be specified, make sure that application/json is specified for request header Content-Type.

To specify Accept, which is an optional request header, make sure that application/json is specified for Accept.

For details about how to specify requests, see 6. Overview of APIs in the manual JP1/Automatic Job Management System 3 Command Reference or 7. Details of API Configuration Components in the manual JP1/Automatic Job Management System 3 Command Reference.

KNAK3218-E

This operation cannot be performed for the job group. (full-unit-name)

The operation was performed with a job group specified.

(S)

Cancels processing.

(O)

Specify a unit other than a job group, and then retry the operation.

KNAK3219-E

This operation cannot be performed for the remote jobnet. (full-unit-name)

The operation was performed with a remote jobnet specified.

(S)

Cancels processing.

(O)

Specify a unit other than a remote jobnet, and then retry the operation.

KNAK3220-E

Specify a job or root jobnet. (full-unit-name)

The specified unit is not applicable for the operation.

(S)

Cancels processing.

(O)

Specify a job or root jobnet, and then retry the operation.

KNAK3221-E

This operation cannot be performed for the units under the remote jobnet. (full-unit-name)

The operation was performed with a unit under the remote jobnet specified.

(S)

Cancels processing.

(O)

Specify a unit that is not under a remote jobnet, and then retry the operation.

KNAK3222-E

Execution result details about the specified jobnet cannot be obtained. (full-unit-name)

The operation was performed by specifying a jobnet that meets none of the following conditions:

remote jobnet

jobnet connector

Connection destination for a jobnet connector

Root jobnet whose parent unit is the connection destination for a jobnet connector

Jobnet for which a wait condition is set

(S)

Cancels processing.

(O)

Specify a jobnet that meets one of the following conditions, and then retry the operation:

remote jobnet

jobnet connector

Connection destination for a jobnet connector

Root jobnet whose parent unit is the connection destination for a jobnet connector

Jobnet for which a wait condition is set

KNAK3223-E

Specify the root jobnet. (full-unit-name)

The specified unit is not applicable for the operation.

(S)

Cancels processing.

(O)

Specify a root jobnet, and then retry the operation.

KNAK3224-E

This operation cannot be performed on the manager jobnet. (full-unit-name)

The operation was performed with the manager jobnet specified.

(S)

Cancels processing.

(O)

Retry the operation for the reference destination jobnet for the manager jobnet.

KNAK3225-E

This operation cannot be performed for the jobnet directly under the planning group. (full-unit-name)

For a jobnet directly under the planning group, you cannot perform planned or immediate execution registration, or cannot add an execution schedule.

(S)

Cancels processing.

(O)

For a jobnet directly under the planning group, specify the fixed schedule period, and then register the jobnet for fixed execution.

KNAK3226-E

This operation cannot be performed on the hostlink jobnet. (full-unit-name)

The operation was performed with a host link jobnet specified.

(S)

Cancels processing.

(O)

Specify a unit other than a host link jobnet, and then retry the operation.

KNAK3227-E

This operation cannot be executed for the jobnet connector. (full-unit-name)

The operation was performed with a jobnet connector specified.

(S)

Cancels processing.

(O)

Specify a unit other than a jobnet connector, and then retry the operation.

KNAK3228-E

Specify a jobnet. (full-unit-name)

The specified unit is not applicable for the operation.

(S)

Cancels processing.

(O)

Specify a jobnet, and then retry the operation.

KNAK3229-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. (full-unit-name)

A jobnet directly under the planning group cannot be registered for fixed execution with the number of future generations specified.

(S)

Cancels processing.

(O)

For a jobnet directly under the planning group, specify the fixed schedule period, and then register the jobnet for fixed execution.

KNAK3230-E

This operation cannot be performed for a job or a hostlink jobnet directly under the job group. (full-unit-name)

The operation was performed with a job or host link jobnet directly under the job group.

(S)

Cancels processing.

(O)

Specify a unit other than a job or host link jobnet directly under a job group, and then retry the operation.

KNAK3231-E

This operation is available only when a specified unit is a jobnet or a start condition. (full-unit-name)

The operation was performed with an invalid unit type specified as an argument. The probable causes are:

A unit other than a jobnet or start condition was specified.

A nested jobnet under the remote jobnet was specified.

(S)

Cancels processing.

(O)

Specify a jobnet or start condition, and then retry the operation.

KNAK3232-E

The macro variable cannot be specified for the root remote jobnet. (full-unit-name)

The operation was performed with a macro variable specified for the root remote jobnet.

(S)

Cancels processing.

(O)

Retry the operation without specifying the macro variable.

KNAK3233-E

Specify a job group or planning group. (full-unit-name)

The specified unit is not applicable for the operation.

(S)

Cancels processing.

(O)

Specify a job group or planning group, and then retry the operation.

KNAK3234-E

The unit type is invalid. (full-unit-name)

The specified unit type is not applicable for the operation.

(S)

Cancels processing.

(O)

Specify a unit type applicable for the operation, and then retry the operation.

KNAK3235-E

The specified release ID does not exist. (release-ID)

The specified release ID does not exist in the specified jobnet.

(S)

Cancels processing.

(O)

Specify the release ID registered for release in the jobnet, and then try again.

KNAK3236-E

The release ID cannot be specified for the unit. (full-unit-name)

The release ID is specified for the unit of a type that cannot be registered for release.

(S)

Cancels processing.

(O)

Make sure that the specified unit is correct, and then try again.

KNAK3237-E

The execution ID cannot be specified for the unit. (full-unit-name)

The execution ID is specified for the unit of a type that cannot be registered for execution.

(S)

Cancels processing.

(O)

Make sure that the specified unit is correct, and then retry the operation.

KNAK3238-E

The message body of the request is incorrect. (line = line-number)

The message body of the request is specified incorrectly.

(S)

Cancels processing.

(O)

Specify the message body of the request correctly.

Note that line-number indicates an approximate location of the incorrect specification. If the specification on the line indicated by line-number is correct, also check the specifications before and after that line.

KNAK3239-E

Specify a request header (request-header).

The request header indicated in request-header is not specified.

(S)

Cancels processing.

(O)

Specify the indicated request header.

KNAK3240-E

The request header (request-header) is incorrect.

The value for request header is invalid.

(S)

Cancels processing.

(O)

Specify the correct value for request-header.

KNAK3241-E

Specify the item-name-1, the item-name-2 or the item-name-3.

Specify a value for at least one of the following: item-name-1, item-name-2, and item-name-3. You cannot omit all three values.

(S)

Cancels processing.

(O)

Specify a value for at least one of the following: item-name-1, item-name-2, and item-name-3.

KNAK3243-E

The specified rerun method (specified-value) cannot be specified for a root jobnet.

The specified rerun method cannot be used for a root jobnet.

(S)

Cancels processing.

(O)

Specify a valid rerun method for the root jobnet, and then retry the operation.

KNAK3244-E

The specified rerun method (specified-value) cannot be specified for a nest jobnet or a job.

The specified rerun method cannot be used for a nested jobnet or job.

(S)

Cancels processing.

(O)

Specify a valid rerun method for the nested jobnet or job, and then retry the operation.

KNAK3245-E

The specified rerun option (specified-value) cannot be specified for a jobnet connector or a hostlink jobnet.

The specified rerun option cannot be used for a jobnet connector or hostlink jobnet.

(S)

Cancels processing.

(O)

Specify a valid rerun option for the jobnet connector or hostlink jobnet, and then retry the operation.

KNAK3246-E

The specified delay monitoring method (specified-value) cannot be specified for a root jobnet.

The specified delay monitoring method cannot be used for a root jobnet.

(S)

Cancels processing.

(O)

Specify a valid delay monitoring method for the root jobnet, and then retry the operation.

KNAK3247-E

The status cannot be changed to specified-value for a unit-type.

The status of the unit type indicated in the message cannot be changed to the specified value.

(S)

Cancels processing.

(O)

Specify a value to which the status of the indicated unit type can be changed, and then retry the operation.

KNAK3248-E

The result code cannot be changed for a unit-type.

The return code cannot be changed for the following unit types:

Hostlink jobnet

Jobnet connector

(S)

Cancels processing.

(O)

Specify a unit type for which the return code can be changed, and then retry the operation.

KNAK3249-E

Specify a unit-type.

This operation cannot be performed for the specified unit. The probable causes are:

A unit for which the operation cannot be performed is specified.

The specified unit type does not allow the operation to be performed.

(S)

Cancels processing.

(O)

Specify a unit type that allows the operation to be performed, and then retry the operation.

KNAK3250-E

"specified-value-2" cannot be specified for item-name-2 when "specified-value-1" is specified for item-name-1.

The values specified for item-name-1 and item-name-2 are mutually exclusive.

(S)

Cancels processing.

(O)

Specify a valid combination of values for item-name-1 and item-name-2, and then retry the operation.

KNAK3251-E

The specified parameter (parameter-name) cannot be processed by the version of the connected JP1/AJS3 - Manager

The specified parameter is not supported by the connected JP1/AJS3 - Manager version. The probable cause is:

The installed JP1/AJS3 - Manager version does not support the specified parameter.

(S)

Cancels processing.

(O)

Correct the error, and then retry.

KNAK3401-E

The data to the connection destination could not be sent or received. (maintenance information = maintenance-information-1, maintenance-information-2)

The system failed to send or receive data with JP1/AJS3 - Manager.

(S)

Cancels processing.

(O)

The probable causes are:

Temporary problem on the network

A temporary problem might have occurred on the network. If this message appears while you are performing an operation on a unit, check whether the operation has taken effect. If the operation does not take effect or if you are obtaining data, retry the operation.

Error in connection destination JP1/AJS3 - Manager

If this message appears frequently, an error might 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 cause of the error according to the results. For details about the contents of the log file, see 1.2 Types of log information and storage locations in the manual JP1/Automatic Job Management System 3 Troubleshooting.

If this message appears immediately after you log in to the system when the connection destination host is a Windows host, a desktop heap might be too small at the connection destination host. Specify the REUSELOGON and LOGONSHMAX environment setting parameters to reduce consumption of the desktop heap at the connection destination host.

For details about the environment setting parameters, see 20.4.2 Details of the environment setting parameters for scheduler services in the JP1/Automatic Job Management System 3 Configuration Guide.

The host is not registered in the connection permission configuration file for the connection destination JP1/AJS3 - Manager

Make sure that the connecting JP1/AJS3 - Web Console host is registered in the connection permission configuration file for connection destination JP1/AJS3 - Manager. If it is not registered, take the corrective action specified in the KAVS8040-E message that was output to the integrated trace log of connection destination JP1/AJS3 - Manager.

Inconsistent settings of the communication encryption function

If a connection is attempted from JP1/AJS3 - Web Console (with the communication encryption function disabled) to the manager host with this function enabled, this message appears. Match the settings of the communication encryption function between the JP1/AJS3 - Web Console host and the manager host.

Other than the above

A probable cause of the error other than the above is that a connection has been established with a port that is being used by another program. Make sure that the port number definition matches the port number (defined for jp1ajs3cdinetd) at the connection destination.

KNAK3402-E

A timeout occurred while waiting for the response from the connection destination. (maintenance information = maintenance-information-1, maintenance-information-2)

A timeout occurred during the wait for a response from JP1/AJS3 - Manager. The probable causes are:

Check whether a problem occurred in JP1/AJS3 - Manager. Because processing of JP1/AJS3 - Manager might be taking a long time, make sure that the request has been applied.

A connection might have been established with a port that is being used by another program. Make sure that the port number definition matches the port number (defined for jp1ajs3cdinetd) at the connection destination.

(S)

Cancels processing.

(O)

Correct the error, and then retry.

KNAK3403-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 encoding is correctly defined for JP1/AJS3 - Manager. If the character encoding is defined in the environment settings file, make sure that the character encoding matches the character encoding for the connection destination JP1/AJS3 - Manager.

KNAK3405-E

Processing was interrupted because an error was detected in the received data.Confirm that the port number (service-name) is the same at the connection destination.

The system detected that an invalid protocol data was sent from JP1/AJS3 - Manager.

(S)

Cancels processing.

(O)

Make sure that the port number definition matches the port number (service-name) at the connection destination.

KNAK3409-E

Information (information-name) about the connection destination cannot be obtained.

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.

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

Connection cannot be established with the connection destination host or the JP1/AJS3 service on the connection destination host. The probable causes are:

The JP1/AJS3 service is not running on the connection destination host.

The port number definition does not match the port number (defined for jp1ajs3cdinetd) at the connection destination.

The connection destination host is not running.

The connection destination host is busy.

The connection destination host is in a state in which a network connection cannot be established.

In the JP1/Base settings at the connection destination, the IP binding method is specified on the receiving side for the physical host. Then, connection is attempted by using an IP address that is not bound to the physical host or any logical host.

Available TCP/IP ports are insufficient.

ajscdinetd is not running.

JP1/AJS3 - Manager of a version that satisfies the request of JP1/AJS3 - Web Console is not installed at the connection destination.

(S)

Cancels processing.

(O)

Correct the error, and then retry.

If the connection destination host is in a state in which a network connection cannot be established:

Check the network environment with the connection destination host. If a firewall is set up between the Web Console server and the connection destination host, check the firewall settings.

If connection is attempted by using an IP address that is not bound to the connection destination physical host or any logical host:

Use a bound IP address to establish a connection, or define jp1hosts information at the connection destination. For details about the definition of jp1hosts information, see the JP1/Base User's Guide.

If there are insufficient TCP/IP ports:

Check the port status, wait until there are fewer ports in the TIME_WAIT status, and then try again. If the user application has made a very large number of calls to the API for JP1/AJS3 - Web Console in a short period of time, revise the number of times the API can be called. If there might be a problem other than the user application (for example, too many applications are using ports), revise the number of applications that can start concurrently and the settings related to TCP/IP ports.

KNAK3411-E

Invalid data was detected. (maintenance information = maintenance-information)

Invalid data that cannot be processed by JP1/AJS3 - Web Console was detected.

(S)

Cancels processing.

(O)

Log out, and then check the following in the JP1/AJS3 - Manager settings at the connection destination:

Make sure that the character encoding set for the OS in which JP1/AJS3 - Manager is running matches the character encoding set for JP1/AJS3 - Manager.

Check whether the old data remains after the character encoding setting for JP1/AJS3 - Manager is changed.

Make sure that the character encoding set in the definition of the remote jobnet matches the character encoding for the execution manager.

If the system does not display this message and the characters displayed by JP1/AJS3 - Web Console become garbled, take the same action as above.

KNAK3412-E

Failed to resolve the host name.

An attempt to resolve the host name failed.

(S)

Cancels processing.

(O)

Make sure that the host name can be resolved.

KNAK3414-E

The request cannot be processed at the connected AJS.

The version of the connected JP1/AJS3 - Manager does not support the request of JP1/AJS3 - Web Console. The probable causes are:

JP1/AJS3 - Manager of a version that satisfies the request of JP1/AJS3 - Web Console is not installed at the connection destination.

(S)

Cancels processing.

(O)

Correct the error, and then retry.

KNAK3460-E

Processing cannot continue by using the current login data.

The JP1/AJS3 service could not be reconnected by using the current login information because the authentication server restarted.

(S)

Cancels processing.

(O)

Log in again, and then retry the operation.

KNAK3463-E

Connection denied. (maintenance information = maintenance-information-1, maintenance-information-2)

Connection with JP1/AJS3 - Manager could not be established because the connecting JP1/AJS3 - Web Console host was not registered in the connection permission configuration file for the connection destination JP1/AJS3 - Manager.

(S)

Cancels processing.

(O)

Take the corrective action specified in the KAVS8040-E message that was output to the integrated trace log of the connection destination JP1/AJS3 - Manager.

KNAK3480-E

An error occurred while processing was being performed for SSL communication. (maintenance information = maintenance-information)

An error occurred during processing for SSL communication between JP1/AJS3 - Web Console host and JP1/AJS3 - Manager. The probable causes are:

The communication encryption function is disabled at the connection destination JP1/AJS3 - Manager.

No root certificate is installed for the server certificate at the connection destination JP1/AJS3 - Manager.

The current time of the host on which an error occurred is earlier than the start time of the effective period specified in the server certificate.

The current time of the host on which an error occurred is later than the end time of the effective period specified in the server certificate.

A temporary communication error occurred.

Connection is restricted by JP1/AJS3 - Manager at the connection destination.

(S)

Cancels processing.

(O)

If the communication encryption function is disabled at the connection destination JP1/AJS3 - Manager:

Enable the communication encryption function for JP1/AJS3 - Manager at the connection destination.

If no root certificate is placed for the server certificate at the connection destination JP1/AJS3 - Manager:

Place a root certificate corresponding to the server certificate at the connection destination JP1/AJS3 - Manager.

If the current time of the host on which an error occurred is earlier than the start time of the effective period specified in the server certificate:

Retry the operation after the start time of the effective period specified in the server certificate.

If the current time of the host on which an error occurred is later than the end time of the effective period specified in the server certificate:

Replace the server certificate located on the connection destination host.

A temporary communication error occurred:

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

If connection is restricted by JP1/AJS3 - Manager at the connection destination:

Add the IP address of the connecting JP1/AJS3 - Web Console host to the connection permission configuration file for the connection destination manager.

KNAK3481-E

An attempt to read the file for specifying the names of the hosts that use non-encrypted communication failed. (file = file-name, maintenance information = maintenance-information)

An attempt to read the nosslhost.conf file for specifying the names of the hosts that use non-encrypted communication failed at the JP1/AJS3 - Web Console host. The probable causes are:

The nosslhost.conf file does not exist.

You do not have access permission for the nosslhost.conf file.

A temporary file access error occurred.

[NO_SSL_HOST] is not entered.

An asterisk (*) is specified incorrectly.

The number of specified host names exceeds the maximum (1,024).

The length of a host name exceeds 255 characters.

The same host name is specified more than once.

(S)

Cancels processing.

(O)

If the file does not exist:

Replace the nosslhost.conf file.

If you do not have access permission for the nosslhost.conf file:

Check and, if necessary, revise access permission for the nosslhost.conf file.

If a temporary file access error occurs:

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

If [NO_SSL_HOST] is not entered:

Enter [NO_SSL_HOST] at the beginning of nosslhost.conf.

If an asterisk (*) is specified incorrectly:

Specify * alone.

If the number of specified host names exceeds the maximum (1,024):

Specify 1,024 or fewer host names.

If the length of a host name exceeds 255 characters:

Correct the host name so that it contains 255 or fewer characters.

If the same host name is specified more than once:

Delete the duplicate host names, leaving only a single instance of a given host name.

KNAK3483-E

An attempt to verify the server certificate failed. (host = name-of-host-to-be-connected, maintenance information = maintenance-information)

An attempt to verify the server certificate sent from the connection destination JP1/AJS3 - Manager failed at the JP1/AJS3 - Web Console host. The probable causes are:

The connection destination manager host name does not match the CN or SAN.

The root certificate corresponding to the server certificate is not installed.

The server certificate and the intermediate certificate are joined in an incorrect order.

(S)

Cancels processing.

(O)

If the connection destination manager host name does not match the CN or SAN:

Establish a connection with the connection destination manager host whose name matches the CN or SAN.

If the root certificate corresponding to the server certificate is not installed:

Install the corresponding root certificate.

If the server certificate and the intermediate certificate are joined in an incorrect order:

Join the server certificate and the intermediate certificate in the correct order.

KNAK3484-E

An attempt to read the root certificate failed. (directory = directory-name, maintenance information = maintenance-information)

An attempt to read the root certificate failed at the JP1/AJS3 - Web Console host. The probable causes are:

A root certificate directory does not exist.

You do not have access permission for the root certificate directory.

A root certificate has not been installed.

A temporary access error occurred during reading of a root certificate.

(S)

Cancels processing.

(O)

If a root certificate directory does not exist:

Create a root certificate directory, and then install a root certificate.

If you do not have access permission for the root certificate directory:

Set access permission for the root certificate directory, and then install a root certificate.

If a root certificate has not been installed:

Install a root certificate.

If a temporary access error occurred during reading of a root certificate:

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

KNAK3485-E

An error occurred during the communication between JP1/AJS3 - Web Console and Manager. (host = name-of-host-to-be-connected, maintenance information = maintenance-information)

An error occurred during the communication between JP1/AJS3 - Web Console and Manager. The probable causes are:

An IP address is specified for Connection host.

Connection host does not match the host name registered on the server certificate at the connection destination manager.

An error occurred for SSL communication at the JP1/AJS3 - Web Console host.

(S)

Cancels processing.

(O)

If an IP address is specified for Connection host:

Specify a host name for Connection host.

If Connection host does not match the host name registered on the server certificate at the connection destination manager:

Make sure Connection host match the host name registered on the server certificate at the connection destination manager, and then log in again

If an error occurred for SSL communication at the JP1/AJS3 - Web Console host:

Contact the system administrator that this error message is displayed, and ask the system administrator to correct the cause of the error referring to app log. After that, log in to JP1/AJS3 - Web Console again.

KNAK3486-E

The operation (Open PFM Report) cannot be performed because acquisition of the host name of JP1/AJS3 - Manager failed.

The Open PFM Report operation cannot be performed because the host name of the connected JP1/AJS3 - Manager host could not be obtained.

(S)

Cancels processing.

(O)

The host name could not be obtained during login 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.

KNAK3601-E

An error occurred during communication processing with the connection destination.

Invalid data was sent from JP1/AJS3 - Web Console. Alternatively, an unexpected response was received from JP1/AJS3 - Manager.

(S)

Cancels processing.

(O)

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

JP1/AJS3 - Web Console log

JP1/AJS3 - Manager log

KNAK3602-E

The JP1/AJS3 service at the connection destination has not been started.

The probable causes are:

The JP1/AJS3 service is not running at the connection destination.

In JP1/Base settings at the connection destination, the IP binding method is specified on the receiving side for the physical host. Then, connection is attempted by using an IP address that is not bound to any physical host or logical host.

If the connection destination is UNIX, the ajsshmdel command is not executed when the configuration of JP1/AJS3 - Manager is changed at the connection destination. Alternatively, the ajsshmdel command is executed without stopping all the JP1/AJS3 services.

If the connection destination is Windows, all the JP1/AJS3 services are not stopped when the configuration of JP1/AJS3 - Manager is changed at the connection destination.

(S)

Cancels processing.

(O)

Correct the error, and then retry.

If connection is attempted by using an IP address that is not bound to any physical host or logical host at the connection destination:

Use a bound IP address to establish a connection, or define jp1hosts information at the connection destination. For details about the definition of jp1hosts information, see the JP1/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 (such as services and commands).

If the connection destination is Windows, go to step 3.

If the connection destination is UNIX, go to step 2.

Execute the ajsshmdel command.

Restart JP1/AJS3.

KNAK3603-E

Cannot connect because the number of connections exceeded the maximum.

Connection cannot be established because the number of connections with JP1/AJS3 - Manager exceeds the maximum.

(S)

Cancels processing.

(O)

Wait until a connection with JP1/AJS3 - Manager is released, and then retry the connection. If reconnection still fails, forcibly release the connection on JP1/AJS3 - Manager.

If this error frequently occurs, revise the maximum number of connections.

If this message appears even though no other connection has been established, make sure that JP1/AJS3 - Manager is set up at the connection destination.

KNAK3604-E

The specified scheduler service does not exist.

The specified scheduler service does not exist. The probable causes are:

The scheduler service specified for the operation does not exist in JP1/AJS3 - Manager at the connection destination.

When JP1/AJS3 - Manager at the connection destination uses a cluster configuration and all scheduler services are displayed, a user who logged in to a logical host accesses a scheduler service outside the logical host used for login.

(S)

Cancels processing.

(O)

Check whether the specified scheduler service exists based on the latest status of the scheduler service. Then, specify the correct scheduler service name, and then retry the operation.

KNAK3605-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 then contact the system administrator.

P1/AJS3 - Web Console 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 log of JP1/Base, see the JP1/Base User's Guide.

KNAK3606-E

The request cannot be processed at the connected AJS.

The version of the connected JP1/AJS3 - Manager does not support the request of JP1/AJS3 - Web Console.

(S)

Cancels processing.

(O)

Correct the error, and then retry.

A connection might have been established with a port that is being used by another program. Make sure that the value specified for port_number in the network-settings file matches the port number (defined for jp1ajs3cdinetd) at the connection destination.

KNAK3608-E

User mapping failed. The user was not associated with an OS user at the connection destination.

User mapping at the connection destination failed. 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 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 JP1/Base User's Guide.

Memory was insufficient during user mapping.

(S)

Cancels processing.

(O)

Take either of the following actions, depending on the API call that caused the error:

If the error occurred in the API call used for login:

Correct the cause of the error, and then log in again.

If the error occurred in an API call not used for login:

Log out, correct the cause of the error, and then log in again.

KNAK3609-E

An error occurred in the Access Control Server 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 JP1/Base User's Guide.

KNAK3610-E

You cannot use the current login information to log in.

You could not log in by using the current login information because the authentication server restarted during login processing of JP1/AJS3 - Web Console.

When JP1/AJS3 - Web Console was started from JP1/IM - View, the attempt to log in by using the current login information did not succeed because of either of the following reasons:

An attempt was made to connect to an incorrect authentication bloc.

The authentication server restarted before JP1/AJS3 - Web Console started.

(S)

Cancels processing.

(O)

Log in again.

KNAK3611-E

The connection is not possible because the specified scheduler service is under maintenance.

The target scheduler service cannot be accessed because it is under maintenance.

(S)

Cancels processing.

(O)

After you confirm that maintenance of the target scheduler service terminated, retry the operation.

KNAK3612-E

Connection denied.

Connection with JP1/AJS3 - Manager could not be established because the connecting JP1/AJS3 - Web Console host was not registered in the connection permission configuration file for connection destination JP1/AJS3 - Manager.

(S)

Cancels processing.

(O)

Take the corrective action specified in the KAVS8040-E message that was output to the integrated trace log of the connection destination JP1/AJS3 - Manager.

KNAK3613-E

An error occurred at the connection destination.

An error occurred at the connection destination.

(S)

Cancels processing.

(O)

Use log information, such as the Windows event log or the syslog file on the host of JP1/AJS3 - Manager at the connection destination, 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 JP1/Automatic Job Management System 3 Troubleshooting.

For details about the log, see C. Log Information in the manual JP1/Automatic Job Management System 3 Troubleshooting.

If maintenance information for this message is set to 1 or 0 and JP1/AJS3 - Manager at the connection destination is for UNIX, check the home directory of the OS user mapped to the logged-in JP1 user. If the home directory does not exist, create it.

KNAK3614-E

The specified unit does not exist.

The specified unit does not exist.

(S)

Cancels processing.

(O)

Update the unit information, and then make sure that the unit has not been deleted.

KNAK3615-E

A past date is specified for an execution start day.

Operation failed. The probable causes are:

A past date is specified for the start date of the fixed schedule period during fixed execution registration.

A past date is specified for the start time when an execution schedule is added.

A past date is specified for the start time when the date and time are changed.

(S)

Cancels processing.

(O)

Specify a date later than the current data for the execution start date, and then retry the operation.

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

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

KNAK3618-E

Cannot treat as Unit.

The specified unit cannot be handled as a unit. Alternatively, the specified unit does not exist. The target unit might have been deleted elsewhere.

(S)

Cancels processing.

(O)

Update the unit information, and then make sure that the operation target unit exists.

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

KNAK3620-E

Jobnet already registered.

The specified operation cannot be performed for a registered jobnet.

(S)

Cancels processing.

(O)

Update the unit information, and then check whether the unit has already been registered. If the unit has been registered, unregister it, and then re-execute the operation if necessary.

KNAK3621-E

Specified jobnet is not registered.

The specified operation cannot be performed for a jobnet that is not registered.

(S)

Cancels processing.

(O)

Update the unit information, and then check whether the unit has not been registered. If the unit has not been registered, register it for execution, and then re-execute the operation.

KNAK3622-E

The specified job or jobnet is being executed.

The specified operation cannot be performed for a job or jobnet that is being executed.

(S)

Cancels processing.

(O)

Update the unit information, and then check whether the unit is being executed. If the unit is being executed, wait until the execution ends, and then re-execute the operation.

KNAK3623-E

The specified job or jobnet has no schedule to be executed.

The specified job or jobnet has no execution schedule.

(S)

Cancels processing.

(O)

Update the unit information, and then check the operation target generation.

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

KNAK3625-E

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.

KNAK3626-E

Cannot execute the method - wait for start condition.

Waiting for the start condition made operation impossible.

(S)

Cancels processing.

(O)

Wait until the start condition is satisfied, and then retry.

KNAK3627-E

Cannot execute the method - 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. Then, if necessary, re-register the jobnet for execution.

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

Specify the information for execution registration, and then re-register the jobnet for execution.

KNAK3629-E

The jobnet cannot be registered because no schedule is defined.

The jobnet cannot be registered because schedule information is not defined.

(S)

Cancels processing.

(O)

Create a schedule rule, and then re-register the jobnet for execution.

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

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

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

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

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

Update the unit information. Then, specify the correct execution ID, and then try again.

KNAK3635-E

The specified jobnet does not exist.

The specified jobnet does not exist.

(S)

Cancels processing.

(O)

Update the unit information. Then, make sure that the jobnet exist, and then try again.

KNAK3636-E

Specified Jobnet is not executing.

The operation cannot be executed because the specified jobnet is not running.

(S)

Cancels processing.

(O)

Update the unit information, and then check the status of the jobnet.

KNAK3637-E

Specified Job is not executing.

The operation cannot be executed because the specified job is not running.

(S)

Cancels processing.

(O)

Update the unit information, and then check the status of the job.

KNAK3638-E

Memory became insufficient at the connection destination.

A memory shortage occurred in the connection destination JP1/AJS3 - Manager.

(S)

Cancels processing.

(O)

Make sure that there is sufficient memory in JP1/AJS3 - Manager at the connection destination.

KNAK3639-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. For details about how to create free space, see 9.2.2 Reorganizing a database in the JP1/Automatic Job Management System 3 Administration Guide.

KNAK3640-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 the unit is being used by JP1/AJS3 - SDK, JP1/AJS3 - Web Console, or JP1/AJS3 - View instances currently connected to JP1/AJS3 - Manager.

To check connection information for JP1/AJS3 - SDK, JP1/AJS3 - Web Console, and JP1/AJS3 - View, execute the ajsstatus command with the -c or -v option specified on JP1/AJS3 - Manager at the connection destination.

Note that if JP1/AJS3 - SDK, JP1/AJS3 - Web Console, or JP1/AJS3 - View is disconnected because of a communication error, the connection sometimes stays open and the unit remains in use. In this case, wait until the failed connection is terminated, and then check the connection information in JP1/AJS3 - Manager. Make sure that all connections have been disconnected, and then retry the operation.

You can specify the SESSIONTIMEOUT environment setting parameter in JP1/AJS3 - Manager at the connection destination to reduce the length of time until a connection with JP1/AJS3 - SDK and JP1/AJS3 - Web Console is terminated. The default value of this environment setting parameter is dword:00000003 (3 in decimal; unit: minutes). For details about the environment setting parameters, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

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

Check whether any one of the following causes of the error exists, depending on the OS of JP1/AJS3 - Manager at the connection destination:

In Windows:

You do not have the permissions required to operate the JP1/AJS3 service with your user account.

For details on the required permissions, see 4.2.3 Changing the JP1/AJS3 service settings (Windows only) in the JP1/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 JP1/Automatic Job Management System 3 Configuration Guide.

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.

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

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

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

KNAK3644-E

No authority for Specified Unit.

You do not have permission to edit the specified unit.

(S)

Cancels processing.

(O)

Check the JP1 user privileges.

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

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

KNAK3647-E

Resources became insufficient at the connection destination.

Resources were insufficient in JP1/AJS3 - Manager at the connection 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.

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

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.

KNAK3649-E

The unit is not in a re-executable status.

The specified unit cannot be re-executed.

The probable causes are:

An attempt was made to re-execute a jobnet that has yet to be executed.

An attempt was made to re-execute a currently running root jobnet by specifying the Hold attribute.

An attempt was made to re-execute a root remote jobnet that is currently running.

(S)

Cancels processing.

(O)

Refresh the unit information, check the unit status, and then retry the operation.

KNAK3650-E

The unit cannot be operated.

Operation cannot be performed on the specified unit.

The probable causes are:

The specified unit was not found because it was deleted.

The specified unit is in a start condition.

You do not have view permission for the scheduler service to which the specified unit belongs.

(S)

Cancels processing.

(O)

Update the unit information, and then check the following:

Make sure that the operation target unit exists.

Make sure that the specified unit is not in a start condition (including start conditions).

Make sure that the JP1 user has the required permissions.

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

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

KNAK3653-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 then delete unnecessary files to increase available free space. Then, retry 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)

KNAK3654-E

System resources 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)

KNAK3655-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 the Release Notes, and then make sure that the shared memory for the system is estimated correctly at the connection destination. Then, increase the value set in the kernel parameter.

If the shared memory required for running the scheduler service was deleted, restart the scheduler service.

KNAK3656-E

Cannot obtain configuration definition at the connection destination.

The system cannot obtain configuration definition at the connection 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.

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

KNAK3658-E

The date is specified incorrectly.

The date is specified incorrectly.

(S)

Cancels processing.

(O)

Specify the date correctly.

KNAK3659-E

This operation cannot be executed for the specified unit's status.

This operation cannot be performed for the status of the specified unit.

(S)

Cancels processing.

(O)

Update the unit information, and then check the status of the specified unit.

If this message appears when you are changing the status of the job, see ajschgstat in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference, and then confirm the following:

The new status specified for the current status is valid.

The return code can be changed.

KNAK3660-E

Cannot hold rerun - specified Jobnet already running.

The jobnet being executed cannot be placed in the hold-reexecution state.

(S)

Cancels processing.

(O)

Update the unit information, and then check the status of the specified unit.

KNAK3661-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 nested jobnet or job you attempted to re-execute is one of the following:

- Now running

- Running + Abend

- Running + Warning

- Wait for prev. to end

- Wait for start time

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

Update the unit information, and then check the status and type of the unit you attempted to re-execute.

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

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

In JP1/AJS3 - Manager at the connection destination, check the environment setting for the scheduler service and the mount status of the disks. Then, make the files accessible, and then re-establish a connection from the Web Console server to JP1/AJS3 - Manager at the connection destination.

KNAK3664-E

You can perform fixed registration only, because the specified jobnet has a hostlink jobnet.

A jobnet that contains a host link jobnet can be registered only for fixed execution.

(S)

Cancels processing.

(O)

To register a jobnet containing a host link jobnet for execution, use fixed registration.

KNAK3665-E

You cannot perform the operation because the hostlink jobnet is in a jobnet that has a start condition.

A jobnet containing both a start condition and a host link jobnet cannot be registered for execution.

Alternatively, you cannot release a jobnet (including a host link jobnet) from the suspended status because a start condition is set for this jobnet.

(S)

Cancels processing.

(O)

Delete the start condition or host link jobnet, and then retry the operation. Note, however, that you cannot delete a host link jobnet that contains a suspended jobnet. If the jobnet is suspended, delete the start condition.

KNAK3666-E

This operation cannot be executed because JP1/AJS2 - Manager for Mainframe has not started at the connection destination.

You cannot perform this operation for a unit that contains a host link jobnet because JP1/AJS2 - Manager for Mainframe is not running at the connection destination.

(S)

Cancels processing.

(O)

Start the JP1/AJS2 - Manager for Mainframe service at the connection destination.

KNAK3667-E

An abnormality occurred in JP1/AJS2 - Manager for Mainframe or in the mainframe at the connection destination.

Operation failed because an error occurred in JP1/AJS2 - Manager for Mainframe or in the mainframe at the connection destination.

(S)

Cancels processing.

(O)

Use log information, such as the Windows event log or the syslog file on the host of JP1/AJS3 - Manager at the connection destination, to examine the error. For details about the log file contents and information, see the manual for JP1/AJS2 - Manager for Mainframe.

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

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

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

Change the specified execution date to a date that is not after the year 2037.

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

KNAK3672-E

The logical host name at the connection destination is specified incorrectly.

Processing cannot be performed because the host name for the logical host connected in JP1/AJS3 - Web Console is not specified correctly in the environment settings at the connection destination.

(S)

Cancels processing.

(O)

Make sure that the logical host name for the IP address connected in JP1/AJS3 - Web Console 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 settings 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).

KNAK3673-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. You can add a schedule only to a jobnet that is in the unscheduled status or that is 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.

KNAK3674-E

A directory required at the connection destination cannot be accessed.

The required directory was not found or cannot be accessed in JP1/AJS3 - Manager at the connection destination.

(S)

Cancels processing.

(O)

Use log information, such as the Windows event log or the syslog file on the host of JP1/AJS3 - Manager at the connection destination, to examine the error. For details about the log file contents and information, see the manual for JP1/AJS2 - Manager for Mainframe.

KNAK3675-E

This operation cannot be executed because the number of jobnet generations had been reached the system limit at the connection destination.

The specified operation cannot be performed because the number of generations reached the maximum in JP1/AJS3 - Manager at the connection destination.

(S)

Cancels processing.

(O)

The maximum number of jobnet generations is 8,000, excluding the number of generations that are created when the starting conditions are satisfied.

To register jobnets for fixed execution on a specified date or to add a generation for the next execution by temporarily changing the schedule, add a generation after the execution of at least one generation finishes.

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. To add more generations to be scheduled, wait until execution of curently reigstered generations is complete.

KNAK3676-E

This operation cannot be executed because the system failed to delete an execution result at the connection destination.

The specified operation cannot be performed because an attempt to delete execution results failed 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.

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

KNAK3678-E

The specified unit is a jobnet of the connection destination. The specified operation cannot be performed because unit-type has been 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.

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

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

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

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

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

Update the unit information, specify the correct unit, and then try again.

KNAK3685-E

The specified execution generation was not found.

Processing cannot be performed because the specified generation was not found. The probable causes are:

The number of specified generations exceeds the number of saved generations.

Registration of the specified generation was canceled for the specified period of time.

The specified jobnet was unregistered and then re-registered for execution.

Execution of the specified generation was canceled.

The JP1 user does not have view permission.

(S)

Cancels processing.

(O)

Update the unit information. Then, make sure that the target generation exists and that the JP1 user has view permission, and then retry the operation.

KNAK3686-E

Acquisition of the generation failed.

An attempt to acquire information about the specified generation failed. The probable causes are:

The number of operation target generations exceeded the number of saved generations.

The operation target generation is unregistered.

(S)

Cancels processing.

(O)

Update the unit information, specify the correct unit, and then try again.

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

KNAK3688-E

The specified unit was not found.

The specified unit does not exist, or the user does not have view permission.

(S)

Cancels processing.

(O)

Update the unit information. In addition, make sure that the unit exists and that the JP1 user has view permission, and then retry the operation.

KNAK3689-W

An attempt to release the login information failed. (maintenance information = maintenance-information-1, maintenance-information-2)

This message indicates that an attempt to release the login information failed.

(S)

Outputs to the log that an attempt to release the login information failed.

KNAK3690-E

The monitor start delay for the specified jobnet cannot be changed because the jobnet is being executed.

The delay monitoring mode cannot be changed from Monitor start delay, because the jobnet is currently running. Note that, even if you change the delay monitoring mode for a jobnet that has already ended, delay monitoring will not be performed for that jobnet.

(S)

Cancels processing.

(O)

Do not change the delay monitoring mode. Alternatively, change the delay monitoring mode other than Monitor start delay (Monitor end delay or Monitor jobnet).

KNAK3691-E

The specified jobnet has no schedule to be executed.

The specified jobnet does not have any generations that are scheduled to be executed.

(S)

Cancels processing.

(O)

Perform the operation for a jobnet that has at least one generation that is scheduled to be executed the next time or at a later time.

KNAK3901-E

An unexpected error occurred during processing. (maintenance information = maintenance-information-1, maintenance-information-2)

An unexpected error occurred during processing. The probable causes are:

The configuration of JP1/AJS3 - Web Console has been corrupted.

The API call being processed was forcibly aborted because JP1/AJS3 - Web Console was stopped or restarted.

(S)

Cancels processing.

(O)

If you changed the configuration of JP1/AJS3 - Web Console, perform a repair installation.

If you stopped or restarted JP1/AJS3 - Web Console, check to what extent the API processing was applied.

For any other case, correct the cause of the error. If you cannot resolve the problem, collect data, and then contact the system administrator.

KNAK3902-E

An system error occurred during processing. (maintenance information = maintenance-information)

A system error occurred during processing. The execution environment of the JP1/AJS3 Web Application Server service might have a problem.

(S)

Cancels processing.

(O)

Correct the cause of the error. If you cannot resolve the problem, collect data, and then contact the system administrator.

KNAK3903-E

Memory became insufficient during processing. (maintenance information = maintenance-information)

Memory became insufficient in the execution environment of the JP1/AJS3 Web Application Server service.

(S)

Cancels processing.

(O)

Check the physical memory usage of the host on which the JP1/AJS3 Web Application Server service is running.

If available physical memory is not sufficient, increase the amount of available physical memory by, for example, terminating unnecessary applications.

For details about the physical memory requirements in JP1/AJS3 - Web Console, see the Release Notes.

KNAK3904-E

A required class file was not found. (maintenance information = maintenance-information-1, maintenance-information-2)

The class file required for executing JP1/AJS3 - Web Console is not found.

(S)

Cancels processing.

(O)

The configuration of JP1/AJS3 - Web Console might have been corrupted. Perform a repair installation.

KNAK3905-W

An unexpected error occurred during processing. (maintenance information =maintenance-information-1, maintenance-information-2)

This message indicates that an unexpected error occurred during processing.

(S)

Continues processing.

(O)

The configuration of JP1/AJS3 - Web Console might have been corrupted. Perform a repair installation.

If you cannot resolve the problem, collect data, and then contact the system administrator.

Appendixes

A. 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 JP1/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.3 Connecting multiple LANs in the JP1/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 JP1/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 11-50

The following lists the revisions in 11-50 for each program.

(1) JP1/AJS3 - Manager

The Web GUI now support the following functions:

Viewing monthly schedules

Adding execution schedules

Change plan (change time)

Change plan (execute immediately)

Change plan (execution prohibited)

Change plan (release change)

Change delay monitor

The API now supports the function to acquire unit information.

The maximum size of the Java heap on the Web Console server can now be changed, and the default value was changed from 512 MB to 2,048 MB.

A function was added to enable you to change the colors indicating unit statuses displayed in the windows and dialog boxes of the Web GUI.

The map area in the Monitor dialog box and the Monitor screen of the Web GUI can now switch between displaying unit names and comments.

The following functions were added to improve job throughput when multiple scheduler services are active:

Function to reduce the number of ports that are used during job execution

Function to output trace logs for each scheduler service

In addition to the changes to internal processing, the JP1/AJS3 performance processing that runs when multiple root jobnets start at the same time was improved. As a result, job throughput when a single scheduler service is active was also improved.

The maximum number of execution agents that can be registered on one manager host can now be increased to 2,048.

To enable the comments on units to be viewed in JP1/IM windows, commenting on units was added as an extended attribute (specific information) of a JP1 event whose OBJECT_TYPE is JOBNET or JOB.

Commands to specify settings of environment setting parameters were integrated into the jajs_config command.

When the scheduler service is restarted, a job that meets specific conditions now transitions to Wait for prev. to end or to Not executed + Ended status (and not to Unknown end status). This enables you to determine, from the job status after the restart of the scheduler service, whether a user program has started.

(2) JP1/AJS3 - Agent

Commands to specify settings of environment setting parameters were integrated into the jajs_config command.

(3) JP1/AJS3 - Agent Minimal Edition

Descriptions were added concerning JP1/AJS3 - Agent Minimal Edition, which limits the number of jobs that can be executed per day to 10.

D.2 Revisions in 11-10

The following lists the revisions in 11-10 for each program.

(1) JP1/AJS3 - Manager

The Web GUI and API now support the following functions:

Web GUI

Check execution schedule

Interrupt

Kill

Rerun

Change job status

Change detailed definitions for PC jobs and Unix jobs

Filter monitoring targets by execution status

API

Fixed execution registration (specifying a specific date and time)

Change plan (change time)

Change plan (execute immediately)

Change plan (execution prohibited)

Change plan (release change)

Change hold attribute

Interrupt

Kill

Rerun

Change delay monitor

Change job status

Obtain execution result details for units

Obtain the protocol version of JP1/AJS3 - Manager

JP1/IM and JP1/AJS3 - Web Console can now be linked so that the Web GUI can be displayed from an email sent by an automated action of JP1/IM - View or JP1/IM.

JP1/PFM and JP1/AJS3 - Web Console can now be linked so that PFM - Web Console can be launched from the Web GUI.

The ajscalutil command was added. This command calculates multiple calendars and outputs the results.

A function was added to set a hold attribute for the first execution generation created by registering a jobnet for planned execution or fixed execution.

The job distribution delay reduction function was added. (When a job is to be executed concurrently on multiple execution agents, if a communication failure occurs on some execution agents, this function reduces the delay in job distribution to the normally operating execution agents.)

In HP-UX, AIX, and Linux, the architecture of most JP1/AJS3 - Manager processes was changed to 64-bit architecture. Note that the following processes were not changed to 64-bit architecture: jpqman32, jpqimport, jpqexport, jpqdbcond, jajs_maintain, and jajs_migrate.

The broadcast function was added. This function distributes a job to multiple execution agents by using a flexible job.

When the ajswebsetup command is run with the -s option (option for setting up the standby system) specified, the command now ends normally even if no shared disk is mounted.

(2) JP1/AJS3 - Agent

In HP-UX, AIX, and Linux, the architecture of most JP1/AJS3 - Agent processes was changed to 64-bit architecture.

The broadcast function was added. This function distributes a job to multiple execution agents by using a flexible job.

(3) JP1/AJS3 - View

A function was added to set a hold attribute for the first execution generation created by registering a jobnet for planned execution or fixed execution.

The broadcast function was added. This function distributes a job to multiple execution agents by using a flexible job.

The multiuser remote desktop connection function was added. This function allows multiple users to use JP1/AJS3 - View via remote desktop connections.

A function was added that allows each JP1 user to use different custom jobs in JP1/AJS3 - View.

D.3 Revisions in 11-00

The following lists the revisions in 11-00 for each program.

(1) JP1/AJS3 - Manager

The supported language types were changed. The specific combinations of languages that are supported when using JP1/AJS3 in multi-language environments was also changed.

JP1/AJS3 - Web Console was added as a component of JP1/AJS3 - Manager. JP1/AJS3 - Web Console allows you to monitor units over the Internet from a web browser, and develop custom programs that use APIs to perform operations on units.

JP1/AJS3 - Print Option was incorporated into JP1/AJS3 - Manager. You can use JP1/AJS3 - Print Option to display and print unit information with a customized layout.

Messages between hosts such as agent hosts and JP1/AJS3 - View hosts can now be encrypted using SSL.

A flexible job was added as a job type. This job allows processing to be executed on an agent host that cannot be managed directly from the manager host. For example, you might use a flexible job with an execution agent in an auto-scaling environment. Although the definition of a flexible job is not OS-dependent, flexible jobs can only be executed in Windows and Linux environments.

An HTTP connection job was added as a job type. This job can send requests to HTTP interfaces such as web APIs provided by cloud environments and web servers. Although the definition of an HTTP connection job is not OS-dependent, HTTP connection jobs can only be executed in Windows and Linux environments.

The initial values of the following environment setting parameters were changed to reflect the recommended values:

UNITDEFDIVIDEUPDATE

AJSPRINTSORTUNITINF

ReceiveFileSizeStatus

LoadUserProfile

IsAccessTokenCache

MergeEnvMode

NotfyJobStateCount

PassingInfoUsePreRc

FileWriteMode

ResolveAgentInfo

RetryAgtStartNotification

The environment setting parameters that require assessment in the design stage of JP1/AJS3 were reviewed, and corresponding improvements were made to the manual.

An option was added that causes JP1/AJS3 - Manager to continue waiting when the status of a unit whose end is being waited for changes after re-execution of its succeeding unit. The behavior of JP1/AJS3 - Manager when waiting is enabled after a new installation of JP1/AJS3 was also changed.

The following OS is supported:

CentOS 6(x64)

CentOS 7

Linux 6.1(x64)

Linux 7.1

Oracle Linux 6(x64)

Oracle Linux 7

SUSE Linux 12

The following OS is no longer supported:

Windows Server 2008 (excluding Windows Server 2008 R2)

Windows Server 2003

Windows Server 2003(x64)

Linux 6.1(x86) or later

Linux 5.1(x86) or later

Linux 5.1(AMD/Intel 64) or later

Support for Outlook 2003 linkage was eliminated. JP1/AJS3 - Manager now supports linkage with Outlook 2013 (32 bit) and Outlook 2010 (32 bit).

JP1/AJS3 Console is now compatible with earlier versions.

(2) JP1/AJS3 - Agent

The supported language types were changed. The specific combinations of languages that are supported when using JP1/AJS3 in multi-language environments was also changed.

Messages exchanged with JP1/AJS3 - Manager can now be encrypted using SSL.

Flexible jobs can now be executed (Windows and Linux only).

HTTP connection jobs can now be executed (Windows and Linux only).

The initial values of the following environment setting parameters were changed to reflect the recommended values:

LoadUserProfile

IsAccessTokenCache

MergeEnvMode

NotfyJobStateCount

FileWriteMode

ResolveAgentInfo

RetryAgtStartNotification

The environment setting parameters that require assessment in the design stage of JP1/AJS3 were reviewed, and corresponding improvements were made to the manual.

The following OS is supported:

CentOS 6(x64)

CentOS 7

Linux 6.1(x64)

Linux 7.1

Oracle Linux 6(x64)

Oracle Linux 7

SUSE Linux 12

The following OS is no longer supported:

Windows Server 2008 (excluding Windows Server 2008 R2)

Windows Server 2003

Windows Server 2003(x64)

Linux 6.1(x86) or later

Linux 5.1(x86) or later

Linux 5.1(AMD/Intel 64) or later

Support for Outlook 2003 linkage was eliminated. JP1/AJS3 - Manager now supports linkage with Outlook 2013 (32 bit) and Outlook 2010 (32 bit).

(3) JP1/AJS3 - View

The supported language types were changed. The specific combinations of languages that are supported when using JP1/AJS3 in multi-language environments was also changed.

Messages exchanged with JP1/AJS3 - Manager can now be encrypted using SSL.

Flexible jobs can now be defined in the Define Details dialog box.

HTTP connection jobs can now be defined in the Define Details dialog box.

The paste commands in the menu of the Jobnet Editor window were replaced with two new commands. One is the Paste (Units and relations) command, which pastes icons, the coordinates of the icons, and the relation lines between icons. The other is the Paste (Units only) command which pastes icons and their coordinates.

An option was added that allows you to set the display order of items in the tree area and list area of the JP1/AJS3 - View window (Main window).

An option was added that allows you to change where the current day is positioned in the Time area and Schedule area of the Monthly Schedule window.

The settings below now apply as the default settings for all windows. You can customize these settings in JP1/AJS3 - View.

A question mark (?) is used as the icon for unregistered custom jobs.

Units in the tree area are displayed in the same order as the list area.

The settings below now apply as the default settings in JP1/AJS3 - View windows. You can customize these settings in JP1/AJS3 - View.

Job groups and planning groups are selected in the list area when the JP1/AJS3 - View window (Main window) is displayed

The same units remain selected and the scroll position is maintained when you refresh the window contents or specify list filtering

A confirmation message is displayed before deleting a defined schedule rule for a nested jobnet for which the Depends on upper-level jobnet check box is selected

Jobnets that have been registered for execution appear in the list area when Jobnet Definition is selected in Function Menu

The following settings now apply as the default settings in the Jobnet Editor window. You can customize these settings in JP1/AJS3 - View.

Nested jobnets and nested remote jobnets are selected in the map area when the Jobnet Editor window is displayed

Users are prevented from opening multiple Jobnet Editor windows

The following settings now apply as the default settings in the Jobnet Monitor window. You can customize these settings in JP1/AJS3 - View.

The contents of the Execution Result Details dialog box are not automatically refreshed

The Execution Result Details dialog box is displayed in large size

Users are prevented from opening multiple Jobnet Monitor windows

Jobs are displayed directly in the map area when displaying the Jobnet Monitor window from JP1/IM - View

Color images are now used to represent the execution status, execution results, and delays in Status and Result in the list area and Status in the detailed information area of the JP1/AJS3 - View window (Main window).

The following units are now hidden by default in the icon list in the Jobnet Editor window:

Remote jobnet

Receive MQ Message job

Receive MSMQ Message job

Send MQ Message job

Send MSMQ Message job

Support for Windows 10 has been added.

The following OS is no longer supported:

Windows Server 2008 (excluding Windows Server 2008 R2)

Windows Vista

Windows Server 2003

Windows Server 2003(x64)

Windows XP Professional

D.4 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.5 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.6 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.7 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.

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:

JP1 Version 11 Job Management: Getting Started (Job Scheduler) (3021-3-B11(E))

JP1 Version 11 JP1/Automatic Job Management System 3 Overview (3021-3-B12(E))

JP1 Version 11 JP1/Automatic Job Management System 3 System Design (Configuration) Guide (3021-3-B13(E))

JP1 Version 11 JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide (3021-3-B14(E))

JP1 Version 11 JP1/Automatic Job Management System 3 Configuration Guide (3021-3-B15(E))

JP1 Version 11 JP1/Automatic Job Management System 3 Administration Guide (3021-3-B16(E))

JP1 Version 11 JP1/Automatic Job Management System 3 Troubleshooting (3021-3-B17(E))

JP1 Version 11 JP1/Automatic Job Management System 3 Operator's Guide (3021-3-B18(E))

JP1 Version 11 JP1/Automatic Job Management System 3 Command Reference (3021-3-B19(E))

JP1 Version 11 JP1/Automatic Job Management System 3 Linkage Guide (3021-3-B20(E))

JP1 Version 11 JP1/Automatic Job Management System 3 - Print Option (3021-3-B26(E))

JP1 Version 11 JP1/Automatic Job Management System 3 - Definition Assistant (3021-3-B25(E))

JP1 Version 11 JP1/Automatic Job Management System 3 for Enterprise Applications Description, User's Guide and Reference (3021-3-B27(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 - Web Operation Assistant Description, Operator's Guide and Reference (3020-3-S18(E))

About JP1:

JP1 Version 11 JP1/Base User's Guide (3021-3-A01(E))

JP1 Version 11 JP1/Base Messages (3021-3-A02(E))

JP1 Version 11 JP1/Base Function Reference (3021-3-A03(E))

JP1 Version 11 Integrated Management: Getting Started (Integrated Console) (3021-3-A06(E))

JP1 Version 11 JP1/Integrated Management - Manager Overview and System Design Guide (3021-3-A07(E))

JP1 Version 11 JP1/Integrated Management - Manager Configuration Guide (3021-3-A08(E))

JP1 Version 11 JP1/Integrated Management - Manager Administration Guide (3021-3-A09(E))

JP1 Version 11 JP1/Integrated Management - Manager GUI Reference (3021-3-A10(E))

JP1 Version 11 JP1/Integrated Management - Manager Command and Definition File Reference (3021-3-A11(E))

JP1 Version 11 JP1/Integrated Management - Manager Messages (3021-3-A12(E))

JP1 Version 11 JP1/Performance Management Planning and Configuration Guide (3021-3-A37(E))

JP1 Version 11 JP1/Performance Management User's Guide (3021-3-A38(E))

JP1 Version 11 JP1/Performance Management Reference (3021-3-A39(E))

JP1 Version 11 Job Management: Getting Started (Scripting Language) (3021-3-B31(E))

JP1 Version 11 JP1/Advanced Shell (3021-3-B32(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Script Description and Reference (3021-3-135(E)), for Windows Systems

JP1 Version 11 JP1/File Transmission Server/FTP Description, Reference, and Operator's Guide (3021-3-B36(E)), for Windows systems

JP1 Version 11 JP1/File Transmission Server/FTP Description, Reference, and Operator's Guide (3021-3-B37(E)), for UNIX systems

JP1 Version 11 Job Management: Getting Started (High-speed Transfer of Huge Amounts of File) (3021-3-B41(E))

JP1 Version 11 JP1/Data Highway - Automatic Job Executor Operation manual (3021-3-B46(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

JP1/Automatic Job Management System 3 - Manager

JP1/AJS3 - Agent

JP1/Automatic Job Management System 3 - Agent

JP1/AJS3 - View

JP1/Automatic Job Management System 3 - View

JP1/AJS3 - Web Console

JP1/Automatic Job Management System 3 - Web Console

JP1/AJS3 - Print Option

JP1/AJS3 - Print Option Manager

JP1/Automatic Job Management System 3 - Print Option Manager

JP1/AJS3 - Print Option

JP1/Automatic Job Management System 3 - Print Option

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/AJS3 - Definition Assistant

JP1/Automatic Job Management System 3 - Definition Assistant

JP1/AJS3 - Web Operation Assistant

Job Management Partner 1/Automatic Job Management System 3 - Web Operation Assistant

JP1/AJS3 for Enterprise Applications

JP1/Automatic Job Management System 3 for Enterprise Applications

JP1/DH - AJE

JP1/Data Highway - Automatic Job Executor

JP1/DH - Server

JP1/Data Highway - Server

JP1/FTP

JP1/File Transmission Server/FTP

JP1/IM

JP1/IM - Manager

JP1/Integrated Management - Manager

JP1/IM - View

JP1/Integrated Management - View

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

JP1/Open Job Entry for VOS3

JP1/PFM

PFM - Manager

JP1/Performance Management - Manager

PFM - Base

JP1/Performance Management - Base

PFM - Web Console

JP1/Performance Management - Web Console

PFM - Agent Option for Platform

JP1/Performance Management - Agent Option for Platform(For UNIX Systems)

JP1/Performance Management - Agent Option for Platform(For Windows Systems)

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 V6.1

AIX V7.1

Firefox

Firefox ESR

Mozilla(R) Firefox(R) Extended Support Release

HP-UX

HP-UX (IPF)

HP-UX 11i V3(IPF)

Linux

CentOS 6(x64)

CentOS 6(x64)

CentOS 7

CentOS 7

Linux 6.1(x64)

Red Hat Enterprise Linux(R) Server 6.1 (64-bit x86_64)

Linux 7.1

Red Hat Enterprise Linux(R) Server 7.1

Oracle Linux 6(x64)

Oracle Linux(R) Operating System 6 (x64)

Oracle Linux 7

Oracle Linux(R) Operating System 7

SUSE Linux 12

SUSE Linux(R) Enterprise Server 12

SAP BW

SAP Business Information Warehouse

SAP R/3

SAP R/3(R)

Solaris

Solaris 10(SPARC)

Solaris 11(SPARC)

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

API

Application Programming Interface

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

HTTP

Hyper Text Transfer Protocol

HTTPS

Hyper Text Transfer Protocol Security

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

REST

Representational State Transfer

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

This manual uses the following conventions in diagrams:

E.5 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.

E.6 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.7 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.8 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.

E.9 About administrator privileges

In this manual, the term "administrator privileges" refers to the execution privileges of the built-in administrator account for a local PC.

If a user has administrator privileges for the local PC, operations do not vary in local user, domain user, and Active Directory environments.

E.10 About the Start menu in Windows

If you are using Windows Server 2016, Windows 8.1, Windows 8, or Windows Server 2012, instead of using the Start menu, perform the operations as described below.

In Windows Server 2016, Windows 8.1 or Windows Server 2012 R2:

Click the down-pointing arrow icon to display the Apps screen.

In Windows 8 or Windows Server 2012 (except Windows Server 2012 R2):

Right-click on the Start screen to display the All Apps screen.

E.11 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 (x86)\HITACHI\JP1AJS2

The default installation folders of JP1/AJS3 Web Console are as follows:

system-drive\Program Files\HITACHI\JP1AJS3WEB

Default installation folder of JP1/AJS3 - Agent:

system-drive\Program Files (x86)\HITACHI\JP1AJS2

Default installation folder of JP1/AJS3 - View:

system-drive\Program Files (x86)#\HITACHI\JP1AJS2V

#

For 32-bit versions of Windows, replace Program Files (x86) with Program Files.

E.12 Online manual

JP1/AJS3 - View comes with an online manual that you can read in browsers.

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.13 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 JP1/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 JP1/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.14 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.15 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 JP1/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.

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.

broadcast agent

An agent that broadcasts a job to multiple destination agents for broadcast execution. The broadcast agent automatically manages the destination agents to which a job is to be broadcast. For example, in an environment in which the number of execution agents is increased or decreased by automatic scaling, the broadcast agent automatically expands or reduces the job distribution range. Therefore, in such an environment, you do not need to modify the job definition, or add or delete jobs manually.

broadcast execution

To broadcast a flexible job to multiple execution agents where the flexible job is to be executed. Use a broadcast execution if you want multiple execution agents to run the same processing.

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

destination agent

An agent that executes a flexible job. A destination agent might be an execution agent in an auto-scaling environment.

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.

flexible job

A standard job that executes processing on an agent host that is not managed directly by the manager host.

Because flexible jobs allow you to execute jobs in an environment where processing is distributed by a load balancer, you can use them to execute processing via an execution agent in a cloud environment (auto-scaling environment).

HP NNM

A suite of integrated network management tools from Hewlett-Packard Co. for managing network configuration, performance, and failures.

HTTP connection job

A job that uses the HTTP protocol to send requests and receive responses. By using a HTTP connection job, you can request processing by an API with an HTTP interface, such as the REST API. This allows you to integrate a business system based on JP1/AJS3 with other web-based business systems.

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 - Agent Minimal Edition

A program that can execute a maximum of 10 jobs per day by request from JP1/AJS3 - Manager. JP1/AJS3 - Agent Minimal Edition has the same functionality as JP1/AJS3 - Agent, except for some limitations. JP1/AJS3 - Agent Minimal Edition is suitable for use on a computer that executes only a few jobs per day.

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

A component of JP1/AJS3 - Manager.

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

A program that collects operating information from numerous monitoring targets throughout the system for more stable system operation.

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.

relay agent

An agent that relays the execution requests associated with a flexible job. The execution requests relayed by the relay agent are executed by the destination agent of the flexible job.

By using relay agents, you can execute jobs defined for local execution in a cloud environment.

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.

If descriptions in this manual do not explicitly distinguish between QUEUE jobs and submit jobs, descriptions for submit jobs also apply to QUEUE jobs.

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.

Web Console server

A host on which JP1/AJS3 - Web Console is installed.

A Web Console server operates as a web server and a web application server, and controls HTTP communication and the behavior of web applications. It also acquires unit information from JP1/AJS3 - Manager in response to client requests, and sends the information as a response to the client.

The Web Console server also provides an API that can be used to perform operations in JP1/AJS3. You can use this API to develop custom applications that interact with JP1/AJS3.

Web GUI

An interface used on a client terminal to monitor units defined on the manager host. The Web GUI is displayed in a web browser, and connects to a Web Console server from a client terminal.

You can use the Web GUI to perform various tasks over the Internet, such as monitoring the execution status and progress of units and executing jobnets.

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 administrator privileges[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]

AJS administrator[1]

AJSPATH[1]

automatic retry[1]

B

backup box[1]

backup file[1]

base day[1]

base time[1]

broadcast agent[1]

broadcast execution[1]

C

calendar information[1]

closed day[1]

cluster system[1]

common user profile[1]

conventions

abbreviations for products[1]

acronyms[1]

diagrams[1]

fonts and symbols[1]

KB, MB, GB, and TB[1]

meaning of directory and folder[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]

destination agent[1]

diagram conventions[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]

flexible job[1]

folder

term defined[1]

font conventions[1]

format of message explanations[1]

format of output messages[1]

G

GB meaning[1]

Glossary[1]

H

HP NNM[1]

term defined[1]

HTTP connection job[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 - Agent Minimal Edition[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/PFM[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]

list of output destinations for messages[1]

list of windows event logs and syslogs[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]

message format[1]

message ID[1]

messages

event and action control[1]

job execution control[1]

JP1/AJS3 - View[1]

output by agent management[1]

output by communication control[1]

passing information setting jobs[1]

system management[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]

output destination

messages about embedded databases[1]

messages about JP1/AJS3 - Web Console commands[1]

messages about JP1/AJS3 - Web Console installer[1]

messages about scheduler and common processing[1]

messages about web application server and APIs[1]

messages about Web GUI[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]

relay agent[1]

return codes of system calls[1]

revisions

09-00[1]

10-00[1]

10-10[1]

10-50[1]

11-00[1]

11-10[1]

11-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]

to system administrators[1]

TP1/Server Base[1]

types of messages[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]

Web Console server[1]

Web GUI[1]

Windows Messaging[1]