JP1 Version 13 JP1/Automatic Job Management System 3 Troubleshooting

3021-3-L47(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-3KDL JP1/Automatic Job Management System 3 - Manager version 13-00

The above product includes the following:

P-CC2A12-4KDL JP1/Automatic Job Management System 3 - Manager version 13-00 (For Windows Server 2022, Windows Server 2019, Windows Server 2016)

P-CC2912-39DL JP1/Automatic Job Management System 3 - Web Console version 13-00 (For Windows Server 2022, Windows Server 2019, Windows Server 2016)

P-CC8412-39DL JP1/Automatic Job Management System 3 - Web Console version 13-00 (For Linux 7, Linux 8, Linux 9, Oracle Linux 7, Oracle Linux 8, Oracle Linux 9, SUSE Linux 12, SUSE Linux 15)

P-CC2A12-3NDL JP1/Automatic Job Management System 3 - Print Option Manager version 13-00 (For Windows Server 2022, Windows Server 2019, Windows Server 2016)

P-CC2A2C-6LDL JP1/Base version 13-00 (For Windows Server 2022, Windows Server 2019, Windows Server 2016)

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

P-8412-3KDL JP1/Automatic Job Management System 3 - Manager version 13-00

The above product includes the following:

P-CC8412-4KDL JP1/Automatic Job Management System 3 - Manager version 13-00 (For Linux 7, Linux 8, Linux 9, Oracle Linux 7, Oracle Linux 8, Oracle Linux 9, SUSE Linux 12, SUSE Linux 15)

P-CC2912-39DL JP1/Automatic Job Management System 3 - Web Console version 13-00 (For Windows Server 2022, Windows Server 2019, Windows Server 2016)

P-CC8412-39DL JP1/Automatic Job Management System 3 - Web Console version 13-00 (For Linux 7, Linux 8, Linux 9, Oracle Linux 7, Oracle Linux 8, Oracle Linux 9, SUSE Linux 12, SUSE Linux 15)

P-CC8412-3NDL JP1/Automatic Job Management System 3 - Print Option Manager version 13-00 (For Linux 7, Linux 8, Linux 9, Oracle Linux 7, Oracle Linux 8, Oracle Linux 9, SUSE Linux 12, SUSE Linux 15)

P-CC842C-6LDL JP1/Base version 13-00 (For Linux 7, Linux 8, Linux 9, Oracle Linux 7, Oracle Linux 8, Oracle Linux 9, SUSE Linux 12, SUSE Linux 15)

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

P-2A12-33DL JP1/Automatic Job Management System 3 - Agent version 13-00

The above product includes the following:

P-CC2A12-43DL JP1/Automatic Job Management System 3 - Agent version 13-00 (For Windows Server 2022, Windows Server 2019, Windows Server 2016)

P-CC2A2C-6LDL JP1/Base version 13-00 (For Windows Server 2022, Windows Server 2019, Windows Server 2016)

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

P-1M12-33DL JP1/Automatic Job Management System 3 - Agent version 13-00

The above product includes the following:

P-CC1M12-43DL JP1/Automatic Job Management System 3 - Agent version 13-00 (For AIX)

P-CC1M2C-6LDL JP1/Base version 13-00 (For AIX)

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

P-8412-33DL JP1/Automatic Job Management System 3 - Agent version 13-00

The above product includes the following:

P-CC8412-43DL JP1/Automatic Job Management System 3 - Agent version 13-00 (For Linux 7, Linux 8, Linux 9, Oracle Linux 7, Oracle Linux 8, Oracle Linux 9, SUSE Linux 12, SUSE Linux 15)

P-CC842C-6LDL JP1/Base version 13-00 (For Linux 7, Linux 8, Linux 9, Oracle Linux 7, Oracle Linux 8, Oracle Linux 9, SUSE Linux 12, SUSE Linux 15)

JP1/Automatic Job Management System 3 - Agent Minimal Edition (For Windows):

P-2A12-38DL JP1/Automatic Job Management System 3 - Agent Minimal Edition version 13-00

The above product includes the following:

P-CC2A12-48DL JP1/Automatic Job Management System 3 - Agent Minimal Edition version 13-00 (For Windows Server 2022, Windows Server 2019, Windows Server 2016)

P-CC2A2C-6LDL JP1/Base version 13-00 (For Windows Server 2022, Windows Server 2019, Windows Server 2016)

JP1/Automatic Job Management System 3 - Agent Minimal Edition (For Linux):

P-8412-38DL JP1/Automatic Job Management System 3 - Agent Minimal Edition version 13-00

The above product includes the following:

P-CC8412-48DL JP1/Automatic Job Management System 3 - Agent Minimal Edition version 13-00 (For Linux 7, Linux 8, Linux 9, Oracle Linux 7, Oracle Linux 8, Oracle Linux 9, SUSE Linux 12, SUSE Linux 15)

P-CC842C-6LDL JP1/Base version 13-00 (For Linux 7, Linux 8, Linux 9, Oracle Linux 7, Oracle Linux 8, Oracle Linux 9, SUSE Linux 12, SUSE Linux 15)

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

P-2A12-34DL JP1/Automatic Job Management System 3 - View version 13-00

The above product includes the following:

P-CC2A12-44DL JP1/Automatic Job Management System 3 - View version 13-00 (For Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows 11, Windows 10)

P-CC2A12-3MDL JP1/Automatic Job Management System 3 - Print Option version 13-00 (For Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows 11, Windows 10)

Trademarks

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

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

Amazon Web Services, AWS, the Powered by AWS logo are trademarks of Amazon.com, Inc. or its affiliates.

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

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

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

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

Microsoft is a trademark of the Microsoft group of companies.

Microsoft, Active Directory are trademarks of the Microsoft group of companies.

Microsoft, Azure are trademarks of the Microsoft group of companies.

Microsoft, Excel are trademarks of the Microsoft group of companies.

Microsoft, Internet Explorer are trademarks of the Microsoft group of companies.

Microsoft, Outlook are trademarks of the Microsoft group of companies.

Microsoft, SQL Server are trademarks of the Microsoft group of companies.

Microsoft, Windows are trademarks of the Microsoft group of companies.

Microsoft, Windows Server are trademarks of the Microsoft group of companies.

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

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

Red Hat, and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the United States and other countries.

SAP C/4HANA is the trademark or registered trademark of SAP SE or its affiliates in Germany and in several other countries.

UNIX is a trademark of The Open Group.

SPARC(R) is a registered trademark of SPARC International, Inc. Products bearing SPARC trademarks are based on an architecture developed by Sun Microsystems, Inc.

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

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

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/

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

OpenSSL License

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

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

* Copyright (c) 1998-2019 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 IAIK of Graz University of Technology.

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

This product includes software developed by Andy Clark.

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

Microsoft product name abbreviations

This manual uses the following abbreviations for Microsoft product names.

Abbreviation

Full name or meaning

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

Internet Explorer

Windows(R) Internet Explorer(R)

Microsoft Edge

Microsoft(R) Edge

Microsoft SQL Server

Microsoft(R) SQL Server

Microsoft(R) SQL Server Enterprise Edition

MSMQ

Microsoft(R) Message Queue Server

Outlook

Outlook 2016

Microsoft(R) Office Outlook(R) 2016

Outlook 2019

Microsoft(R) Office Outlook(R) 2019

Outlook 2021

Microsoft(R) Office Outlook(R) 2021

Outlook Express

Microsoft(R) Outlook(R) Express

Windows 10

Windows(R) 10 Enterprise

Windows(R) 10 Pro

Windows(R) 10 Home

Windows 11

Windows(R) 11 Enterprise

Windows(R) 11 Pro

Windows(R) 11 Home

Windows Server 2016

Microsoft(R) Windows Server(R) 2016 Datacenter

Microsoft(R) Windows Server(R) 2016 Standard

Windows Server 2019

Microsoft(R) Windows Server(R) 2019 Datacenter

Microsoft(R) Windows Server(R) 2019 Standard

Windows Server 2022

Microsoft(R) Windows Server(R) 2022 Datacenter

Microsoft(R) Windows Server(R) 2022 Standard

Windows is sometimes used generically, referring to Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows 11, and Windows 10.

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

Jun. 2023: 3021-3-L47(E)

Copyright

Copyright (C) 2023, Hitachi, Ltd.

Copyright (C) 2023, Hitachi Solutions, Ltd.

Colophon

Publisher

Hitachi, Ltd.

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

Summary of amendments

For details about the amendments, see the manual JP1/Automatic Job Management System 3 Overview.

Preface

This manual describes how to troubleshoot errors for JP1/Automatic Job Management System 3 (abbreviated hereafter to JP1/AJS3).

For details on the prerequisites before reading this manual, see the manual JP1/Automatic Job Management System 3 Overview.

Organization of this manual

This manual organized into 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. Troubleshooting Procedure and Required Data

Chapter 1 describes the general troubleshooting procedure, the logs that are available to facilitate troubleshooting, and the data you need to collect if a problem occurs during JP1/AJS3 operation.

2. Troubleshooting Typical Problems

Chapter 2 describes how to troubleshoot typical problems that might occur when JP1/AJS3 is being used.

1 Troubleshooting Procedure and Required Data

This chapter describes the general troubleshooting procedure, logs that are available to facilitate troubleshooting, and the data you need to collect if a problem occurs during JP1/AJS3 operation.

1.1 Troubleshooting procedure

If a problem occurs in JP1/AJS3, use the following procedure to troubleshoot:

Check the status.

Check the status of the problem. If a message is output, read it. For details about why each message is output and how to troubleshoot, see the manual JP1/Automatic Job Management System 3 Messages.

For details about the information that is logged by JP1/AJS3, see 1.2 Types of log information and storage locations.

Collect data.

You need to collect data to identify the cause of a problem. Collect the necessary data after reading 1.3 Data to be collected when a problem occurs and 1.4 Collecting data for troubleshooting.

Investigate the problem.

Identify the cause of the problem based on the data you have collected. Either pinpoint where the problem occurred or narrow down the problem range.

1.2 Types of log information and storage locations

JP1/AJS3 logs four types of information while it is running:

System failure log

Scheduler log

Execution result log

Trace log

The following figure shows where these four types of log information are stored.

Figure 1‒1: Storage locations for log information

1.2.1 System failure log

System failure log refers to the information logged for system problems. This information is used by system administrators.

System failure log consists of the common message log and the integrated trace log.

(1) Common message log

The common message log is output to the Windows event log file or the syslog file.

(2) Integrated trace log

The integrated trace log contains the trace information that is output by different programs via Hitachi Network Objectplaza Trace Library (HNTRLib2). This information is stored in output files. The integrated trace log contains more detailed messages than those provide by the common message log.

The integrated trace log is output to integrated trace log files.

For details about how to obtain the integrated trace log, see the JP1/Base User's Guide.

The integrated trace log is output to the following files by default:

In Windows:

system-drive\Program Files (x86)#1, #2\HITACHI\HNTRLib2\spool\hntr2{1|2|3|4}.log

In UNIX:

/var/opt/hitachi/HNTRLib2/spool/hntr2{1|2|3|4}.log

#1

For 32-bit versions of Windows, replace Program Files (x86) with Program Files.

#2

For JP1/AJS3 - Web Console, replace Program Files (x86) with Program Files.

You can specify the type of system failure log to be collected in the integrated trace log. To do this, use the jajs_config command to specify the type of information to be logged in the HNTRLOGLEVEL environment setting parameter.

You can use a text editor to read the integrated trace log files. The following figure shows an example of output to an integrated trace log file.

Figure 1‒2: Example of output to an integrated trace log file

The following tables describe the headers and output items in the integrated trace log file.

Table 1‒1: Meaning of headers in the integrated trace log file

Header

Explanation

OS information

The OS on which Hitachi Network Objectplaza Trace Library (HNTRLib2) is running.

Host name

The name of the host on which Hitachi Network Objectplaza Trace Library (HNTRLib2) is running.

Time zone

In Windows:

The time zone set for the OS.

In UNIX:

The value of the TZ environment variable for the integrated trace log.

If the TZ environment variable is not specified, Unknown is displayed.

Time HNTRLib2 started

The time that Hitachi Network Objectplaza Trace Library (HNTRLib2) started

Table 1‒2: Meaning of the output items in the integrated trace log file

Output item

Explanation

Number (4 digits)

The sequence number of the trace record.

A number is assigned for each process for which information is logged.

Date (10 bytes)

The date the trace was collected: yyyy/mm/dd (year/month/day)

Time (12 bytes)

The local time the trace was collected: hh:mm:ss.sss (hour:minutes:seconds.milliseconds)

Application name (16 bytes or less)

The name of an application (application identification name).

JP1/AJS3 generally outputs the following application names:

The JP1/AJS3 service: JAJS_SPMD

The scheduler process: ajsmasterd

The flow control process: ajsflowd (ajsflowd.exe for Windows)

The job submit process: ajssubd (ajssubd.exe for Windows)

The job completion wait process: ajssubwd (ajssubwd.exe for Windows)

The job execution control status notification process: jpqnfyfd (jpqnfyfd.exe for Windows)

The schedule control process: ajsschd

The event/action control manager process: jpomanager

The event/action control agent process: jpoagent

The execution interval control process: jpocwttmMain

The event (JP1 events, log traps, etc.) monitoring process: jpoeventwatch

The event/action control submanager process: jpomgrsub

The event/action control subagent process: jpoagtsub

The job execution control process: jpqmon

The job execution control manager process: jpqman

The job execution control agent process: jpqagt

The network control process: ajsinetd

The process that starts when a user logs in to JP1/AJS3 - View: ajsmonsvr

The JP1/AJS3 - Queueless Agent service (queueless agent process): ajsqlagtd

The JP1/AJS3 - Queueless File Transfer service (queueless file transfer process): ajsqlftpd

The JP1/AJS3 Check Manager service: ajschkmand (ajschkmand.exe for Windows)

The JP1/AJS3 Check Agent service: ajschkagtd

Other processes and commands: The process or command name

pid

The process ID assigned by the OS.

A pid is output as a hexadecimal number.

tid

The thread ID that identifies a thread.

A tid is output as a hexadecimal number.

Message ID

A message ID appearing in 1.2.1 Format of output messages in the manual JP1/Automatic Job Management System 3 Messages. The message IDs in this log are only those used by JP1/AJS3.

Message text

The text of a message output to the integrated trace log. The message texts in this log are those output by JP1/AJS3.

Important

The time that information is recorded in the integrated trace log is the time in the time zone to which the source process belongs. If a user changes the value of the TZ environment variable and then starts a service or executes a command, the time of log information might not match the time zone set for the OS.

1.2.2 Scheduler log

Scheduler log is logged by the JP1/AJS3 scheduler services, and is used by operations administrators. The scheduler log indicates when execution of a jobnet or job started or ended, and how jobnets and jobs were handled.

The JP1/AJS3 scheduler log can be recorded separately for each scheduler service on a JP1/AJS3 - Manager host or for the entire host. To make this specification, use the AJSLOGOUTPUTDEST environment setting parameter. By default, scheduler log is recorded separately for each scheduler service.

Logging scheduler log for each scheduler service

Scheduler log is logged for each scheduler service when schedule is specified in the AJSLOGOUTPUTDEST environment setting parameter. The logged information is output to the file specified in the AJSLOGFILE1 environment setting parameter or AJSLOGFILE2 environment setting parameter. The default destination file is as follows:

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\schedule\scheduler-service-name\ajs-log1.log or %ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\schedule\scheduler-service-name\ajs-log2.log

The default value 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\schedule\scheduler-service-name\ajs-log1.log or JP1/AJS3-installation-folder\log\schedule\scheduler-service-name\ajs-log2.log

For UNIX:

/var/opt/jp1ajs2/log/schedule/scheduler-service-name/ajs-log1.log or /var/opt/jp1ajs2/log/schedule/scheduler-service-name/ajs-log2.log

Logging scheduler log for the entire host

Scheduler log is logged for the entire host when host is specified in the AJSLOGOUTPUTDEST environment setting parameter. In this case, the scheduler log logged by different scheduler services is output to one file. The logged information is output to the file specified in the HOSTLOGFILE1 environment setting parameter or HOSTLOGFILE2 environment setting parameter. The default destination file is as follows:

For Windows, if the installation folder is in the default folder or a folder protected by the system:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\ajs-host-log1.log or %ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\ajs-host-log2.log

The default value 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 in which an installation folder other than the above is used:

JP1/AJS3-installation-folder\log\ajs-host-log1.log or JP1/AJS3-installation-folder\log\ajs-host-log2.log

For UNIX:

/var/opt/jp1ajs2/log/ajs-host-log1.log or /var/opt/jp1ajs2/log/ajs-host-log2.log

Logging format for scheduler log

The logging format for scheduler log is as follows:

log-typeΔdateΔtimeΔadditional-information

Legend:

Δ: 1-byte space character

For details about scheduler log, see C.1 Log entries output by the scheduler services.

1.2.3 Execution result log

The log data in execution result logs allows a user on an agent host to check information about the executions of event jobs and other jobs. A user on the manager host might not be able to check the execution statuses of event jobs and other jobs that are run on an agent host because of, for example, a communication error. In such cases, a user on the agent host can check the execution statuses of event jobs and other jobs by using the execution result logs.

There are two execution result logs:

Job execution result log file

Event job execution result log file

(1) Job execution result log file

The log data in the job execution result log file allows a user on an agent host to check the execution statuses of jobs. This file is output if 1 or 2 is set for the JOBEXECRESULTLOG environment parameter.

(a) Output destination of the job execution result log file

The job execution result log file is output to the directory that is specified in the JOBEXECRESULTLOGPATH environment setting parameter. The following shows the default directory.

For Windows, if the installation folder is the default installation folder or is in a folder protected by the system:

For a physical host:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\jobexecresult

The default value 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 a logical host:

shared-folder\jp1ajs2\log\jobexecresult

For Windows, if the installation folder is other than the above:

For a physical host:

JP1/AJS3-installation-folder\log\jobexecresult

For a logical host:

shared-folder\jp1ajs2\log\jobexecresult

For UNIX/Linux:

For a physical host:

/var/opt/jp1ajs2/log/jobexecresult

For a logical host:

shared-dircetory/jp1ajs2/log/jobexecresult

(b) Format of data output to the job execution result log file

The contents of the job execution result log file can be viewed in a text editor. The following figure shows an example of output to a job execution result log file.

Figure 1‒3: Example of output to a job execution result log file

The following tables describe the headers and output items in the job execution result log file.

Table 1‒3: Meaning of headers in the job execution result log file

Header

Explanation

OS information

The OS on which the log output function is running.

Host name

The name of the host on which the log output function is running.

Time zone

The time zone set for the OS.

Time the log output function started

The time that the log output function started

Table 1‒4: Meaning of the output items in the job execution result log file

Output item

Explanation

Number (4 digits)

The sequence number of the message record.

Date (10 bytes)

The date the message was collected: yyyy/mm/dd (year/month/day)

Time (12 bytes)

The local time the message was collected: hh:mm:ss.sss (hour:minutes:seconds.milliseconds)

Application name (16 bytes or less)

The name of the process for which the message is output.

One of the following application names is output:

jpqagt

jpqagtchild

Process ID

Process ID

A process ID is output as a hexadecimal number.

Thread ID

Thread ID

A thread ID is output as a hexadecimal number.

Message ID

Message ID

The messages that are output to the job execution result log file are as follows:

KAVU3613-I: Message indicating a job was accepted

KAVU3614-I: Message indicating that a job started (in Windows)

KAVU3615-I: Message indicating that a job started (in UNIX)

KAVU3616-I: Message indicating that a job ended

Message text

The text of a message output to the job execution result log file.

For information about the message text for each message ID, see 5.1 List of messages beginning with KAVU in the manual JP1/Automatic Job Management System 3 Messages.

(2) Event job execution result log file

The log data in the event job execution result log file allows a user on an agent host to check the execution statuses of event jobs. This file is output if 1 or 2 is set for the EVJOBEXECRESULTLOG environment parameter.

(a) Output destination of the event job execution result log file

The event job execution result log file is output to the directory that is specified in the EVJOBEXECRESULTLOGPATH environment setting parameter. The following shows the default directory.

For Windows, if the installation folder is the default installation folder or is in a folder protected by the system:

For a physical host:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\evjobexecresult

The default value 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 a logical host:

shared-folder\jp1ajs2\log\evjobexecresult

For Windows, if the installation folder is other than the above:

For a physical host:

JP1/AJS3-installation-folder\log\evjobexecresult

For a logical host:

shared-folder\jp1ajs2\log\evjobexecresult

For UNIX/Linux:

For a physical host:

/var/opt/jp1ajs2/log/evjobexecresult

For a logical host:

shared-dircetory/jp1ajs2/log/evjobexecresult

(b) Format of data output to the event job execution result log file

The contents of the event job execution result log file can be viewed in a text editor. The following figure shows an example of output to an event job execution result log file.

Figure 1‒4: Example of output to an event job execution result log file

The following tables describe the headers and output items in the event job execution result log file.

Table 1‒5: Meaning of headers in the event job execution result log file

Header

Explanation

OS information

The OS on which the log output function is running.

Host name

The name of the host on which the log output function is running.

Time zone

The time zone set for the OS.

Time the log output function started

The time that the log output function started

Table 1‒6: Meaning of the output items in the event job execution result log file

Output item

Explanation

Number (4 digits)

The sequence number of the message record.

Date (10 bytes)

The date the message was collected: yyyy/mm/dd (year/month/day)

Time (12 bytes)

The local time the message was collected: hh:mm:ss.sss (hour:minutes:seconds.milliseconds)

Application name (16 bytes or less)

The name of the process for which the message is output.

One of the following application names is output:

jpoagent

jpoagtsub

Process ID

Process ID

A process ID is output as a hexadecimal number.

Thread ID

Thread ID

A thread ID is output as a hexadecimal number.

Message ID

Message ID

The messages that are output to the event job execution result log file are as follows:

KAVT0966-I: Message indicating that event monitoring started

KAVT0967-I: Message indicating that an event was detected

KAVT0968-I: Message indicating that event monitoring ended

Message text

The text of a message output to the event job execution result log file.

For information about the message text for each message ID, see 4.1 List of messages beginning with KAVT in the manual JP1/Automatic Job Management System 3 Messages.

1.2.4 Trace log

A trace log contains trace information that can be used in investigating how a problem has occurred and in determining how time was required to execute each process when a problem has occurred.

The JP1/AJS3 trace information is output to multiple trace log files. The internal format of each trace log file is not public information. In addition, a text editor cannot be used to view the files because the files are binary files.

(1) Scheduler trace

There are two types of scheduler trace log files as follows:

Common scheduler trace log file

Trace log file to which trace information of all scheduler services is output.

The scheduler trace information on the physical host and all logical hosts is output to a single trace log file.

A JP1/AJS3 - Manager host uses one file, which wraps around to the beginning when the end of the file is reached. The default file size is 102,400 kilobytes. The logging format is binary.

Scheduler trace log file of each scheduler service

The scheduler trace information of scheduler service is output to this log file in units of scheduler service.

Trace log file to which trace information on a scheduler service is output.

One log file is used for each scheduler service. When the maximum file size is reached, the log records in the file wrap around. The default file size is 102,400 kilobytes. The logging format is binary.

For details about how to output trace log data for individual scheduler services, see 6.1.5 Setting to output a scheduler trace log per scheduler service in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows), or 15.1.5 Setting to output a scheduler trace log per scheduler service in the JP1/Automatic Job Management System 3 Configuration Guide (for UNIX).

Note that you can use the ajstrsetsz command to increase the trace log file size.

For details about this command, see ajstrsetsz in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

(2) Job execution trace

The trace log data related to job execution control is divided by function and recorded in separate files on the JP1/AJS3 - Manager and JP1/AJS3 - Agent hosts. For details about the names of files, see 1.2.5 List of log files and directories.

(3) Event and action trace

The trace log data related to event/action control is divided by function and recorded in separate files on the JP1/AJS3 - Manager and JP1/AJS3 - Agent hosts. For details about the names of these files, see 1.2.5 List of log files and directories.

(4) Queueless job trace

A JP1/AJS3 - Manager host uses one file, which wraps around to the beginning when the end of the file is reached. A JP1/AJS3 - Agent host also uses one file that wraps around to the beginning when the end of the file is reached. The default file size is 15,360 kilobytes. The logging format is binary. You can change the size of these trace log files by using the ajsqltrsetsz command. For details about this command, see ajsqltrsetsz in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

(5) Other traces

JP1/AJS3 Check Manager and JP1/AJS3 Check Agent, which pre-check definitions, each use one trace log file that wraps around to the beginning when the end of the file is reached. The default file size is 3,072 kilobytes. The logging format is binary. You can change the size of these trace log files by using the ajschktrsetsz command. For details about this command, see ajschktrsetsz in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

A JP1/AJS3 - Manager host or a JP1/AJS3 - Agent host logs trace information related to system management in multiple trace log files for each function. For details about the names of files, see 1.2.5 List of log files and directories. The default size of each file is 384 kilobytes.

1.2.5 List of log files and directories

(1) Log files and directories in Windows

Table 1-8 to Table 1-11 describe the log file names and folder names of the scheduler logs and the trace logs for each function in JP1/AJS3 for Windows.

The Log name column lists the names of the logs created by JP1/AJS3.

In Log file and folder names column, the following abbreviations are used for folders:

Mgr_Path

If the installation folder is the default installation folder or is in a folder protected by the system#1:

%ALLUSERSPROFILE%#2\Hitachi\JP1\JP1_DEFAULT\JP1AJS2

If the installation folder is other than the above:

JP1/AJS3 - Manager-installation-folder

The default installation folder is system-drive\Program Files (x86)\HITACHI\jp1ajs2.

Agt_Path

If the installation folder is the default installation folder or is in a folder protected by the system#1:

%ALLUSERSPROFILE%#2\Hitachi\JP1\JP1_DEFAULT\JP1AJS2

If the installation folder is other than the above:

JP1/AJS3 - Agent-installation-folder

The default installation folder is system-drive\Program Files (x86)\HITACHI\jp1ajs2.

View_Path

%ALLUSERSPROFILE%#2\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V

Web_Path

If the installation folder is the default installation folder or is in a folder protected by the system#1:

%ALLUSERSPROFILE%#2\Hitachi\JP1\JP1_DEFAULT\JP1AJS3web

If the installation folder is other than the above:

JP1/AJS3 - Web Console-installation-folder

The default installation folder is system-drive\Program Files\HITACHI\jp1ajs3WEB.

#1

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)

#2

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

In a cluster system, unless otherwise specified, make the substitutions shown in the following table for the indicated abbreviations.

Table 1‒7: Log output folders in a cluster system

Abbreviation in Table 1-8 to Table 1-11

Log output folder in a cluster system

Mgr_Path

shared-disk-name\jp1ajs2

Agt_Path

shared-disk-name\jp1ajs2

Web_Path

shared-disk-name\jp1ajs3web

The Default disk space column indicates the disk space allocated to a log file when the default environment settings is used for operation, and is the total disk space size when there are multiple log files. If the user has not changed the size of a log file, the disk space indicated in the table is the disk space allocated to that log file.

The Maximum disk space column indicates the maximum amount of disk space that a log file uses. This value includes changes to definitions, and is the total disk space size when there are multiple log files. The values in this column are the maximum values for log files whose size varies according to the definitions.

The Timing for switching files column indicates either a limit or the point at which JP1/AJS3 switches the log file (output file for the log) to another file. A value in this column indicates that there are multiple log files, and that the file with the oldest update date is overwritten when the maximum disk space has been reached.

The Details on changing settings column shows sections in 1.2.6 Whether log file settings can be changed that describe in detail whether log file settings can be changed and how to change them. An N indicates a log file whose settings cannot be changed.

Table 1‒8: Log files and folders in JP1/AJS3 - Manager (for Windows)

Log name

Log file and folder names

Logged information

Default disk space#1

Maximum disk space#1

Timing for switching files#2

Details on changing settings

System management log

Mgr_Path\log\JAJS_SPMD{1|2|3}.log

Trace log related to starting, stopping, and checking the status of the JP1/AJS3 service#3

384

33,554,432

(32 gigabytes)

Log size specified during log setup

(128)

1.2.6(1)

Mgr_Path\log\JAJS_SPMD_COMMAND{1|2|3}.log

384

33,554,432

(32 gigabytes)

Log size specified during log setup

(128)

Mgr_Path\log\JAJS_SERVICE{1|2|3}.log

384

33,554,432

(32 gigabytes)

Log size specified during log setup

(128)

Mgr_Path\log\JAJS_DBMD_[embedded-database-setup-ID]{1|2|3}.log

384

33,554,432

(32 gigabytes)

Log size specified during log setup

(128)

Mgr_Path\log\JAJS_HSTD{1|2|3}.log

384

33,554,432

(32 gigabytes)

Log size specified during log setup

(128)

Mgr_Path\log\JAJS_AGTD{1|2|3}.log

384

33,554,432

(32 gigabytes)

Log size specified during log setup

(128)

Mgr_Path\log\JAJS_SCHD_[scheduler-service-name]{1|2|3}.log

384

33,554,432

(32 gigabytes)

Log size specified during log setup

(128)

License management log

Mgr_Path\log\hliclibtrc{1|2|3|4|5}.log

License management log file#3

5,120

5,120

1,024

N

Mgr_Path\log\hlicliberr{1|2|3|4|5}.log

5,120

5,120

1,024

Mgr_Path\log\hliclibmgrtrc{1|2|3|4|5}.log

5,120

5,120

1,024

Mgr_Path\log\hliclibmgrerr{1|2|3|4|5}.log

5,120

5,120

1,024

Mgr_Path\log\hliclibtrc.conf

Management file for the license management log file#3

256 bytes

256 bytes

Wraparound

Mgr_Path\log\hlicliberr.conf

256 bytes

256 bytes

Wraparound

Mgr_Path\log\hliclibmgrtrc.conf

256 bytes

256 bytes

Wraparound

Mgr_Path\log\hliclibmgrerr.conf

256 bytes

256 bytes

Wraparound

Scheduler log

Mgr_Path\log\schedule\scheduler-service-name\ajs-log{1|2}.log

Operating information related to jobnets, jobs, and scheduler services (when scheduler log is logged separately for each scheduler service)

81,920

4,000,000

Size of the scheduler log file specified in the environment settings

(40,960)

1.2.6(2)

Mgr_Path\log\ajs-host-log{1|2}.log

Operating information related to jobnets, jobs, and scheduler services (when scheduler log is logged for the entire host)

20,480

4,000,000

Size of the scheduler log file for the host specified in the environment settings

(10,240)

1.2.6(2)

ajsinetd internal log

Mgr_Path\log\ajsinetd{1|2}.log

Internal information related to the network control process#3

256

4,000,000

Size of the ajsinetd internal log

(128)

1.2.6(2)

ajscdinetd internal log

Mgr_Path\log\ajscdinetd{1|2}.log

Internal log for the network control process of JP1/AJS3 - Web Console#3

When a new installation is performed

4,000

When a upgrade installation is performed

256

4,000,000

Size of the ajscdinetd internal log

(When a new installation is performed : 4,000, When a upgrade installation is performed : 128)

1.2.6(2)

ajsmonsvr internal log

Mgr_Path\log\ajscdmonsvr_scheduler-service-name_{1|2}.log

Internal log for the ajsmonsvr process that JP1/AJS3 - Web Console connects to#3

8,192

32,768

Size of the ajsmonsvr internal log

(4,096)

1.2.6(2)

Common scheduler trace log#4

Mgr_Path\log\tracelog

Trace log and information about operations related to scheduler services and jobnets#3, #5

102,400

2,097,151

Wraparound

1.2.6(2)

Scheduler trace log of each scheduler service#4

Mgr_Path\log\tracelog_ scheduler-service-name

Trace log and information about operations related to scheduler services and jobnets#3, #5

102,400

2,097,151

Wraparound

1.2.6(2)

Job execution manager log

Mgr_Path\log\schedule\scheduler-service-name\jpqmanexec{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log

Trace log related to the job execution control manager process when a job is executed#3

15,360

524,288

Log size specified during log setup

(1,024)

1.2.6(3)

Mgr_Path\log\jpqmanexec{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log#6

Job execution agent log

Mgr_Path\log\jpqagtexec{1|2|3|4|5|6|7|8}.log#9

Trace log related to the job execution control agent process when a job is executed#3

4,096

524,288

Log size specified during log setup

(512)

1.2.6(3)

Mgr_Path\log\jpqagtexecmon{1|2|3|4|5|6|7|8}.log#10

4,096

524,288

Job execution client log

Mgr_Path\log\jpqcliexec{1|2}.log#11

Execution trace log related to jpqxxxx commands and JpqxxxxAPI functions#3

1,024

524,288

Log size specified during log setup

(512)

1.2.6(3)

Job execution status report log

Mgr_Path\log\schedule\scheduler-service-name\jpqnfyexec{1|2}.log

Trace log related to job execution control communication when a job is executed#3

1,024

524,288

Log size specified during log setup

(512)

1.2.6(3)

Event/action control manager log

Mgr_Path\log\schedule\scheduler-service-name\jpomanager{1|2|3|4|5|6|7|8|9|10|11|12|13}.log

Trace log related to the event/action control manager when an event job is executed#3

53,248

16,777,216

(16 gigabytes)

Log size specified during log setup

(4,096)

1.2.6(4)

Mgr_Path\log\jpomanager{1|2|3|4|5|6}.log

12,288

16,777,216

(16 gigabytes)

Log size specified during log setup

(2,048)

Mgr_Path\log\schedule\scheduler-service-name\jpomgrsub{1|2|3|4|5|6|7|8}.log

24,576

16,777,216

(16 gigabytes)

Log size specified during log setup

(3,072)

Mgr_Path\log\jpomgrsub{1|2|3|4|5|6|7|8}.log

Event/action control agent log

Mgr_Path\log\jpoagent{1|2|3|4|5|6|7|8}.log

Trace log related to the event/action control agent when an event job is executed#3

24,576

16,777,216

(16 gigabytes)

Log size specified during log setup

(3,072)

1.2.6(4)

Mgr_Path\log\jpoagtsub{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16}.log

32,768

16,777,216

(16 gigabytes)

Log size specified during log setup

(2,048)

Event monitoring log

Mgr_Path\log\jpoeventwatch{1|2|3|4|5|6|7|8}.log#13

Execution trace log related to the JP1 event reception monitoring job, Windows event log monitoring job, and log file monitoring job#3

73,728

16,777,216

(16 gigabytes)

Log size specified during log setup

(9,216)

1.2.6(4)

Event search log

Mgr_Path\log\jpoevsearch{1|2}.log#13

Trace log related to event searching before the JP1 event reception monitoring job is executed#3

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

1.2.6(4)

File monitoring log

Mgr_Path\log\jpocwtflMain{1|2|3|4|5|6|7|8|9|10|11|12|13}.log#13

Execution trace log related to the file monitoring job#3

26,624

16,777,216

(16 gigabytes)

Log size specified during log setup

(2,048)

1.2.6(4)

Execution interval control log

Mgr_Path\log\jpocwttmMain{1|2|3|4|5|6}.log#13

Execution trace log related to the execution interval control job#3

1,536

16,777,216

(16 gigabytes)

Log size specified during log setup

(256)

1.2.6(4)

Mail monitoring log (common)

Mgr_Path\log\jpocwtmlmain{1|2}.log#13

Execution trace log related to the mail reception monitoring job and mail sending job when the mail linkage function is used#3

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

1.2.6(4)

Mgr_Path\log\jpomlapisend{1|2}.log#18

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

Mgr_Path\log\jpomlapirec{1|2}.log#18

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

Mgr_Path\log\jpomlapisend2{1|2}.log#18

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

Mgr_Path\log\jpomlapirec2{1|2}.log#18

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

Mail monitoring log (when mail linkage is performed on the desktop)

Mgr_Path\log\jpomldsk{1|2}.log#18

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

1.2.6(4)

Mail monitoring log (when mail linkage is performed in the service)

Mgr_Path\log\jpomlsrv{1|2}.log#18

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

1.2.6(4)

Email sending job log (when Outlook not used)

Mgr_Path\sys\prf\profile-name\telsmail.{log|old}#13

Trace log related to email sending job execution when Outlook not used#3

4,096

19,998

Log size specified during log setup

(2,048)

1.2.6(4)

Mgr_Path\sys\prf\profile-name\smaildbg.{log|old}#13

4,096

19,998

Log size specified during log setup

(2,048)

Mgr_Path\sys\prf\profile-name\protocol.{log|old}#13

4,096

19,998

Log size specified during log setup

(2,048)

NNM linkage log

Mgr_Path\log\jpoovlink{1|2}.log#4

Trace log related to monitoring HP NNM is used#3

512

512

256

N

Job execution internal log

Mgr_Path\log\jpqagent\jpqagt_{00|01|02|03|04|05|06|07}.log

--#3, #5

12,288

1,048,576

Log size specified during log setup

(1,536)

1.2.6(3)

Mgr_Path\log\jpqagent\jpqmon_{00|01|02|03|04|05|06|07}.log

--#3, #5

12,288

1,048,576

Log size specified during log setup

(1,536)

Mgr_Path\log\jpqagent\jpqnjpagt_{00|01|02|03|04|05|06|07}.log

--#3, #5

12,288

1,048,576

Log size specified during log setup

(1,536)

Mgr_Path\log\jpqagent\jpqnjpdata_{00|01}.log

--#3, #5

1,024

1,048,576

Log size specified during log setup

(512)

Job execution internal log

Mgr_Path\log\jpqclient\jpqclient_{00|01|02|03|04|05|06|07|08|09}.log

--#3, #5

30,720

1,048,576

Log size specified during log setup

(3,072)

Mgr_Path\log\jpqclient\jpqclientnjp_{00|01|02|03|04|05|06|07|08|09}.log

--#3, #5

30,720

1,048,576

Log size specified during log setup

(3,072)

Mgr_Path\log\jpqclient\jpqnjpdata_{00|01}.log

--#3, #5

1,024

1,048,576

Log size specified during log setup

(512)

Job execution internal log

Mgr_Path\log\schedule\scheduler-service-name\jpqmanager\jpqman_{00|01|02|03}.log

--#3, #5

6,144

1,048,576

Log size specified during log setup

(1,536)

Mgr_Path\log\jpqmanager\jpqman_{00|01|02|03}.log

Mgr_Path\log\schedule\scheduler-service-name\jpqmanager\jpqmandb_{00|01|02|03}.log

--#3, #5

6,144

1,048,576

Log size specified during log setup

(1,536)

Mgr_Path\log\jpqmanager\jpqmandb_{00|01|02|03}.log

Mgr_Path\log\schedule\scheduler-service-name\jpqmanager\jpqmannjp_{00|01|02|03}.log

--#3, #5

6,144

1,048,576

Log size specified during log setup

(1,536)

Mgr_Path\log\jpqmanager\jpqmannjp_{00|01|02|03}.log

Mgr_Path\log\schedule\scheduler-service-name\jpqmanager\jpqnjpdata_{00|01}.log

--#3, #5

1,024

1,048,576

Log size specified during log setup

(512)

Mgr_Path\log\jpqmanager\jpqnjpdata_{00|01}.log

Job execution internal log

Mgr_Path\log\schedule\scheduler-service-name\jpqnotify\jpqnotify_{00|01}.log

--#3, #5

3,072

1,048,576

Log size specified during log setup

(1,536)

Mgr_Path\log\schedule\scheduler-service-name\jpqnotify\jpqnotifynjp_{00|01}.log

--#3, #5

3,072

1,048,576

Log size specified during log setup

(1,536)

Mgr_Path\log\schedule\scheduler-service-name\jpqnotify\jpqnjpdata_{00|01}.log

--#3, #5

1,024

1,048,576

Log size specified during log setup

(512)

Flow control subprocess internal log

Mgr_Path\log\schedule\scheduler-service-name\ajsflbd{1|2}.log

Trace log related to a unit with wait conditions#3

20,480

4,000,000

Size of the flow control subprocess internal log (10,240)

1.2.6(2)

Job execution environment database reorganization log

Mgr_Path\database\queue\CONDENSE{1|2}.log

--

1,024

1,024

512

N

Event/action common log#4

Mgr_Path\log\jpocommonerr{1|2}.log

--#3

16,384

4,194,304

(4 gigabytes)

Log size specified during log setup

(8,192)

1.2.6(4)

Event/action common error log#4

Mgr_Path\log\jpoproccomerr{1|2}.log

--#3

256

256

128

N

jajs_migrate command trace log

Mgr_Path\log\jajs_migrate_logical-host-name_{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20}.log#17

Trace log related to the command that changes the system environment from JP1/AJS2 to JP1/AJS3#3

10

200

When the jajs_migrate command is executed

N

jajs_setup command trace log#4

Mgr_Path\log\jajs_setup_{01|02|03|04|05|06|07|08|09|10|11|12|13|14|15|16|17|18|19|20}.log#15

Trace log related to the command that specifies environment settings#3

200

200

When the jajs_setup command is executed

N

jajs_config command trace log

Mgr_Path\log\jajs_config_{1|2}.log

Trace log related to the command that specifies an environment setting parameter#3

1

256

128

N

jajs_setup_cluster command trace log#4

Mgr_Path\log\jajs_setup_cluster_{01|02|03|04|05|06|07|08|09|10|11|12|13|14|15|16|17|18|19|20}.log#15

Trace log related to the command that configures a cluster environment#3

200

200

When the jajs_setup_cluster command is executed

N

jajs_pmtcon command trace log

Mgr_Path\log\jajs_pmtcon_{1|2}.log

Log output when restricting of connection sources is set#3

1

256

128

N

Queueless log

Mgr_Path\log\ajsql-log{1|2}.log

Information related to the jobs executed by the queueless agent service

16,384

4,000,000

Queueless log file size specified in environment settings (8,192)

1.2.6(5)

Queueless trace log#4

Mgr_Path\log\tracelog.ql

Execution trace log related to queueless jobs and commands related to execution control of queueless jobs#3, #5

15,360

2,097,151

Wraparound

1.2.6(5)

Queueless job execution internal log

Mgr_Path\log\ajsqlexeclog#4, #14

Execution trace log related to queueless jobs#3, #5

24,576

2,097,151

Wraparound

1.2.6(5)

Mgr_Path\log\ajsqlexeclog_ftpd#4

10,240

2,097,151

Wraparound

The status file used to store information about running queueless jobs

Mgr_Path\log\ajsqlstat.dat

Information about running queueless jobs#3, #5

2,048

2,000,000

Wraparound

1.2.6(5)

Maintenance log#4

Mgr_Path\log\jajs_maintain_manager{1|2|3|4}.log#7

Information related to database reorganization that is executed during maintenance#3

1,484

1,484

When maintenance is performed

N

Mgr_Path\log\jajs_maintain_[scheduler-service-name]{1|2|3|4}.log#7

1,484

1,484

When maintenance is performed

Automatic reorganization log#4

Mgr_Path\log\jpqautocond{1|2|3|4}.log#8

Information related to database reorganization that is executed during automatic reorganization#3

764

764

When automatic reorganization is performed

N

Mgr_Path\log\ajsautocond{1|2|3|4}.log#8

764

764

When automatic reorganization is performed

Definition check log#4

Mgr_Path\log\ajscheck{1|2}.log

Information related to definition pre-checks

8,192

4,000,000

Definition check log file size specified in the environment settings

1.2.6(6)

Definition check trace log#4

Mgr_Path\log\tracelog.ch

Trace log related to definition pre-checks#3, #5

3,072

2,097,151

Wraparound

1.2.6(6)

Execution log for embedded database operation commands#4

Mgr_Path\log\ajsembdbbackup.log

Information related to execution of commands manipulate the embedded database#3

--

--

--#16

N

Mgr_Path\log\ajsembdbrstr.log

--

--

--#16

Mgr_Path\log\embdb\ajsembdboplog[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

Mgr_Path\log\embdb\ajsembdbrorg[host-name][scheduler-service-name]{1|2|3|4}.log

4,096

4,096

1,024

Mgr_Path\log\embdb\ajsembdbreclaim[host-name][scheduler-service-name]{1|2|3|4}.log

4,096

4,096

1,024

Mgr_Path\log\embdb\ajsembdbreclaim_nv_[host-name][scheduler-service-name]{1|2|3|4}.log

4,096

4,096

1,024

Mgr_Path\log\embdb\ajsembdbaddarea[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

Mgr_Path\log\embdb\ajsembdbaddlog[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

Mgr_Path\log\embdb\ajsembdbstop[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

Mgr_Path\log\embdb\ajsembdbstop_nv[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

Mgr_Path\log\embdb\ajsembdbstart[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

Mgr_Path\log\embdb\ajsembdbstart_nv[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

Mgr_Path\log\embdb\ajsembdbcancel[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

Mgr_Path\log\embdb\ajsembdbunset[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

Mgr_Path\log\embdb\ajsembdbbuild[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

Mgr_Path\log\embdb\ajsembdbsetup[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

Mgr_Path\log\embdb\ajsembdbstatus[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

Mgr_Path\log\embdb\ajsembdbinstl{1|2|3|4}.log

4,096

4,096

1,024

Mgr_Path\log\embdb\ajsembdbuninstl{1|2|3|4}.log

4,096

4,096

1,024

Mgr_Path\log\embdb\ajsembdbmaintain{1|2|3|4}.log

4,096

4,096

1,024

Embedded database maintenance log#5

Mgr_Path\log\embdb\dbautomaintenance[host-name].{log|old}

Log data that is output during the automatic maintenance of an embedded database

4,096

4,096

When automatic maintenance is performed

N

Execution log for jajs_dbbackup command#4

Mgr_Path\log\jajs_dbbackup_[embedded-database-setup-ID]_{1|2}.log

Log data that is output when the embedded DB is backed up

8,192

8,192

4,096

N

Execution log for jajs_dbrestore command#4

Mgr_Path\log\jajs_dbrestore_[embedded-database-setup-ID]_{1|2}.log

Log data that is output when the embedded DB is restored

8,192

8,192

4,096

N

Mgr_Path\log\embdb\ajsembdb_ebrstr[embedded-database-setup-ID].log

1,024

1,024

When the jajs_dbrestore command is executed

Agent management trace log#4

Mgr_Path\log\ajsagttrace

--#3, #5

20,480

20,480

Wraparound

N

Agent management log

Mgr_Path\log\ajsagtmd{1|2}.log

Agent information for agent management control#3

8,192

8,192

4,096

1.2.6(7)

Communication control trace log

Mgr_Path\log\tracelog-nw

--#3, #5

40,960

40,960

Wraparound

N

Communication control log

Mgr_Path\log\ajsnetwd{1|2|3|4|5}.log

--#3

51,200

51,200

10,240

N

Export command trace log #4

Mgr_Path\log\jajs_rpenvexport_[logical-host-name]_{1|2|3|4}.log

--#3

256

256

32

N

Mgr_Path\log\ajsdbenvexport_[logical-host-name]_{1|2|3|4}.log

--#3

256

256

32

Import command trace log#4

Mgr_Path\log\jajs_rpenvimport_[logical-host-name]_{1|2|3|4}.log

--#3

256

256

32

N

Mgr_Path\log\ajsdbenvimport_[logical-host-name]_{1|2|3|4}.log

--#3

256

256

32

Migration command execution log #4

Mgr_Path\log\JP1AJS3_DBCnvExport_{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20}.log#17

Log information related to execution of a migration command#3

10

200

When the ajscnvdbexport command is executed

N

Mgr_Path\log\JP1AJS3_DBCnvImport_{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20}.log#17

10

200

When the ajscnvdbimport command is executed

ajsdbmgrd internal log

Mgr_Path\log\ajsdbmgrd_[embedded-database-setup-ID]{1|2}.log

Internal log for the database operation control process#3

8,192

8,192

4,096

1.2.6(9)

Flexible job execution requester log file#4

Mgr_Path\log\ajsfxreq{1|2}.log

Log storing log data output by the flexible job execution requester (manager host#19)

20,480

4,000,000

Log file size specified in environment settings (10,240)

1.2.6(10)

Flexible job execution host log file#4

Mgr_Path\log\ajsfxexec{1|2}.log

Log storing log data output by the flexible job execution host (destination agent)

20,480

4,000,000

Log file size specified in environment settings (10,240)

1.2.6(10)

Flexible job trace log#4

Mgr_Path\log\ajsfxtrace

--#3, #5

20,480

20,480

Wraparound

N

Log file for the broadcast agent and broadcast-execution destination agents#4

Mgr_Path\log\ajsfxbcctl{1|2}.log

--#3

20,480

4,000,000

Log file size specified in environment settings (10,240)

1.2.6(10)

Broadcast agent log file#4

Mgr_Path\log\ajsfxdstr{1|2}.log

Log storing log data output by the broadcast agent

40,960

4,000,000

Log file size specified in environment settings (20,480)

1.2.6(10)

Internal trace log file for HTTP connection job execution#4

Mgr_Path\log\ajshttptrace

--#3, #5

20,480

20,480

Wraparound

N

Agent monitoring trace log#4

Mgr_Path\log\tracelog.agm

--#3, #5

20,480

20,480

Wraparound

N

performance log file

Files under Mgr_Path\log\schedule\scheduler-service-name\ajsreport

Log storing the operating status of each process#3, #5

604,800

1,814,400

Wraparound

1.2.6(2)

jajs_extdb command trace log

Mgr_Path\log\jajs_extdb_{1|2}.log

--#3

256

256

128

N

ODBC internal error log

Mgr_Path\log\ajsodbc{1|2}.log

--#3

4,096

4,096

2,048

N

Internal trace log file for JP1/IM2 linkage command

Mgr_Path\log\IMDDAdapter_HITACHI_JP1_AJS3_{00|01}.log

--#3

2,048

2,048

1,024

N

Mgr_Path\log\ajsimlinktrend_{1|2}.log

--#3

4,096

4,096

Size of the internal trace log file for JP1/IM2 linkage command (2,048)

Mgr_Path\log\ajsimlinkunitshow_{1|2}.log

--#3

4,096

4,096

Size of the internal trace log file for JP1/IM2 linkage command (2,048)

Internal information log file for JP1/IM2 linkage command

If a linkage function is run for a logical host:

Mgr_Path\log\IMAC_[logical-host-name]_{00|01}.log

If a linkage function is run for a physical host:

Mgr_Path\log\IMAC_{00|01}.log

--#3

--#20

--#20

When a linkage function with JP1/IM2 is run

N

Internal error log file for JP1/IM2 linkage command

If a linkage function is run for a logical host:

Mgr_Path\log\IMACE_[logical-host-name]_{00|01}.log

If a linkage function is run for a physical host:

Mgr_Path\log\IMACE_{00|01}.log

--#3

20

20

When a linkage function with JP1/IM2 is run

N

Temporary output file for JP1/IM2 linkage command

If a linkage function is run for a logical host:

Mgr_Path\tmp\IMAgps_[logical-host-name]

If a linkage function is run for a physical host:

Mgr_Path\tmp\IMAgps

--#3

--#20

--#20

When a linkage function with JP1/IM2 is run

Job execution result log file

Mgr_Path\log\jobexecresult\ajsjobexecresult{1|2|3|4|5|6|7|8|9|10|11|12}.log

Information about job executions on an agent host

196,608

1,048,576

Log file size specified in environment settings (16,384)

1.2.6(3)

Event job execution result log file

Mgr_Path\log\evjobexecresult\ajsevjobexecresult{1|2|3|4}.log

Information about event job executions on an agent host

65,536

1,048,576

Log file size specified in environment settings (16,384)

1.2.6(4)

Execution log for jajs_cnvdb command#4

Mgr_Path\log\jajs_cnvdb[_logical-host-name]{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20}.log

--#3

10

10

When the jajs_cnvdb command is executed

N

Management portal execution environment internal log

Mgr_Path\log\jajs_sysshow_{1|2}.log

--#3

8,192

8,192

4,096

N

ajssysctlmd internal log

Mgr_Path\log\ajssysctlmd{1|2}.log

Internal log of the management portal execution environment (for manager processes)

Stores information about process start and stop, information about process acceptance begin and end, and results of API function executions by JP1/Base.

8,192

4,000,000

Size of the ajssysctlmd internal log

(4,096)

1.2.6(14)

ajssysctlad internal log

Mgr_Path\log\ajssysctlad{1|2}.log

Internal log of the management portal execution environment (for agent processes)

Stores information about process start and stop, information about process acceptance begin and end, and results of API function executions by JP1/Base.

8,192

4,000,000

Size of the ajssysctlad internal log

(4,096)

1.2.6(14)

ajssysctl trace log

Mgr_Path\log\tracelog.sc

Process trace log

20,480

20,480

Wraparound

N

ajssysctlmd log

Mgr_Path\log\ajsscm-log{1|2}.log

Log storing information about connections and operations performed by clients.

20,480

4,000,000

Log file size specified in environment settings (10,240)

1.2.6(14)

ajssysctlad log

Mgr_Path\log\ajssca-log{1|2}.log

Log storing information about the operations performed by the manager host.

20,480

4,000,000

Log file size specified in environment settings (10,240)

1.2.6(14)

Legend:

N : The log file settings cannot be changed.

#1

The unit is kilobytes unless otherwise specified. The value in parentheses is the kilobyte value expressed in gigabytes.

#2

The unit is kilobytes. The value in parentheses in this column indicates the default timing for switching log files.

#3

The format of the logged information is not publicly available outside the company.

#4

Information is also output to the default folder in a cluster system.

#5

The information is in binary format and cannot be read.

#6

In a cluster system, the file names vary depending on how JP1/AJS3 has been installed.

If JP1/AJS3 09-00 or later has been installed as a new installation:

jpqmanexec{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log

If JP1/AJS3 has been installed as an upgrade installation from JP1/AJS2:

If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system.

jpqExecLog_man{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log

#7

In a cluster system, the file names are different:

jajs_maintain_manager_[logical-host-name]{1|2|3|4}.log

jajs_maintain_[scheduler-service-name]_[logical-host-name]{1|2|3|4}.log

#8

In a cluster system, the file names are different:

jpqautocond_[logical-host-name]{1|2|3|4}.log

schedule\ajsautocond_[logical-host-name]{1|2|3|4}.log

#9

In a cluster system, the file names vary depending on how JP1/AJS3 has been installed.

If JP1/AJS3 09-00 or later has been installed as a new installation:

jpqagtexec{1|2|3|4|5|6|7|8}.log

If JP1/AJS3 has been installed as an upgrade installation from JP1/AJS2:

If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system.

jpqExecLog_agt{1|2|3|4|5|6|7|8}.log

#10

In a cluster system, the file names vary depending on how JP1/AJS3 has been installed.

If JP1/AJS3 09-00 or later has been installed as a new installation:

jpqagtexecmon{1|2|3|4|5|6|7|8}.log

If JP1/AJS3 has been installed as an upgrade installation from JP1/AJS2:

If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system.

jpqExecLog_agtmon{1|2|3|4|5|6|7|8}.log

#11

In a cluster system, the file names vary depending on how JP1/AJS3 has been installed.

If JP1/AJS3 09-00 or later has been installed as a new installation:

jpqcliexec{1|2}.log

If JP1/AJS3 has been installed as an upgrade installation from JP1/AJS2:

If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system.

jpqExecLog_cli{1|2}.log

#12

You can change the log output folders. To do so, change the value specified in the AJSLOGDIR environment setting parameter for the [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name] definition key.

#13

You can change the Mgr_Path part differs depending on the value specified in the WaitInfFileOutDir environment setting parameter for the [{JP1_DEFAULT|logical-host-name}\JP1AOMMANAGER] and [{JP1_DEFAULT|logical-host-name}\JP1AOMAGENT] definition keys.

#14

The file name is different in a cluster system:

Mgr_Path\log\ajsqlexeclog-[logical-host-name]

If the full path name is 256 bytes or more, [logical-host-name] becomes the first 30 bytes of the logical host name.

#15

The latest execution result is output to the log file numbered 01. When the command is executed, log files are renamed by incrementing their numbers by 1, and a new log file with 01 is created. If the command is executed when a log file with the largest allowed number already exists, the log information in that log file is discarded.

#16

The size of the file increases without limit. Save or delete information in the file as necessary.

#17

The latest execution result is output to the log file with the largest number. If the command is executed when a log file with the largest allowed number already exists, the information in the log file numbered 01 is discarded.

#18

Information is also output to a folder on the physical host in a cluster system. Therefore, you can change the value of Mgr_Path even in a cluster system by specifying the value in the WaitInfFileOutDir environment setting parameter for the [JP1_DEFAULT\JP1AOMAGENT] definition key.

#19

If a relay agent exists, log data is output to the relay agent. If a relay agent does not exist, log data is output to the manager host.

#20

The file size increases in proportion to the number of defined units and execution agents.

Table 1‒9: Log files and folders in JP1/AJS3 - Agent (for Windows)

Log name

Log file and folder names

Logged information

Default disk space#1

Maximum disk space#1

Timing for switching files#2

Details on changing settings

System management log

Agt_Path\log\JAJS_SPMD{1|2|3}.log

Trace log related to starting, stopping, and checking the status of the JP1/AJS3 service#3

384

33,554,432

(32 gigabytes)

Log size specified during log setup

(128)

1.2.6(1)

Agt_Path\log\JAJS_SPMD_COMMAND{1|2|3}.log

384

33,554,432

(32 gigabytes)

Log size specified during log setup

(128)

Agt_Path\log\JAJS_SERVICE{1|2|3}.log

384

33,554,432

(32 gigabytes)

Log size specified during log setup

(128)

License management log

Agt_Path\log\hliclibtrc{1|2|3|4|5}.log

License management log file#3

5,120

5,120

1,024

N

Agt_Path\log\hlicliberr{1|2|3|4|5}.log

5,120

5,120

1,024

Agt_Path\log\hliclibmgrtrc{1|2|3|4|5}.log

5,120

5,120

1,024

Agt_Path\log\hliclibmgrerr{1|2|3|4|5}.log

5,120

5,120

1,024

Agt_Path\log\hliclibtrc.conf

Management file for the license management log file#3

256 bytes

256 bytes

Wraparound

Agt_Path\log\hlicliberr.conf

256 bytes

256 bytes

Wraparound

Agt_Path\log\hliclibmgrtrc.conf

256 bytes

256 bytes

Wraparound

Agt_Path\log\hliclibmgrerr.conf

256 bytes

256 bytes

Wraparound

Job execution agent log

Agt_Path\log\jpqagtexec{1|2|3|4|5|6|7|8}.log#6

Trace log related to the job execution control agent process when a job is executed#3

4,096

524,288

Log size specified during log setup

(512)

1.2.6(3)

Agt_Path\log\jpqagtexecmon{1|2|3|4|5|6|7|8}.log#7

4,096

524,288

Log size specified during log setup

(512)

Job execution client log

Agt_Path\log\jpqcliexec{1|2}.log#8

Execution trace log related to jpqxxxx commands and JpqxxxxAPI functions#3

1,024

524,288

Log size specified during log setup

(512)

1.2.6(3)

Event/action control agent log

Agt_Path\log\jpoagent{1|2|3|4|5|6|7|8}.log#9

Trace log related to the event/action control agent when an event job is executed#3

24,576

16,777,216

(16 gigabytes)

Log size specified during log setup

(3,072)

1.2.6(4)

Agt_Path\log\jpoagtsub{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16}.log#9

32,768

16,777,216

(16 gigabytes)

Log size specified during log setup

(2,048)

Event monitoring log

Agt_Path\log\jpoeventwatch{1|2|3|4|5|6|7|8}.log#9

Execution trace log related to the JP1 event reception monitoring job, Windows event log monitoring job, and log file monitoring job#3

73,728

16,777,216

(16 gigabytes)

Log size specified during log setup

(9,216)

1.2.6(4)

Event search log

Agt_Path\log\jpoevsearch{1|2}.log#9

Trace log related to event searching before the JP1 event reception monitoring job is executed#3

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

1.2.6(4)

File monitoring log

Agt_Path\log\jpocwtflMain{1|2|3|4|5|6|7|8|9|10|11|12|13}.log#9

Execution trace log related to the file monitoring job#3

26,624

16,777,216

(16 gigabytes)

Log size specified during log setup

(2,048)

1.2.6(4)

Execution interval control log

Agt_Path\log\jpocwttmMain{1|2|3|4|5|6}.log#9

Execution trace log related to the execution interval control job#3

1,536

16,777,216

(16 gigabytes)

Log size specified during log setup

(256)

1.2.6(4)

Mail monitoring log (common)

Agt_Path\log\jpocwtmlmain{1|2}.log#9

Execution trace log related to the mail reception monitoring job and mail sending job when the mail linkage function is used#3

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

1.2.6(4)

Agt_Path\log\jpomlapisend{1|2}.log#12

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

Agt_Path\log\jpomlapirec{1|2}.log#12

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

Agt_Path\log\jpomlapisend2{1|2}.log#12

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

Agt_Path\log\jpomlapirec2{1|2}.log#12

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

Mail monitoring log (when mail linkage is performed on the desktop)

Agt_Path\log\jpomldsk{1|2}.log#12

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

1.2.6(4)

Mail monitoring log (when mail linkage is performed in the service)

Agt_Path\log\jpomlsrv{1|2}.log#12

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

1.2.6(4)

Email sending job log (when Outlook not used)

Agt_Path\sys\prf\profile-name\telsmail.{log|old}#9

Trace log related to email sending job execution when Outlook not used#3

4,096

19,998

Log size specified during log setup

(2,048)

1.2.6(4)

Agt_Path\sys\prf\profile-name\smaildbg.{log|old}#9

4,096

19,998

Log size specified during log setup

(2,048)

Agt_Path\sys\prf\profile-name\protocol.{log|old}#9

4,096

19,998

Log size specified during log setup

(2,048)

NNM linkage log

Agt_Path\log\jpoovlink{1|2}.log#5

Trace log related to monitoring when HP NNM is used#3

512

512

256

N

Job execution internal log

Agt_Path\log\jpqagent\jpqagt_{00|01|02|03|04|05|06|07}.log

--#3, #4

12,288

1,048,576

Log size specified during log setup

(1,536)

1.2.6(3)

Agt_Path\log\jpqagent\jpqmon_{00|01|02|03|04|05|06|07}.log

--#3, #4

12,288

1,048,576

Log size specified during log setup

(1,536)

Agt_Path\log\jpqagent\jpqnjpagt_{00|01|02|03|04|05|06|07}.log

--#3, #4

12,288

1,048,576

Log size specified during log setup

(1,536)

Agt_Path\log\jpqagent\jpqnjpdata_{00|01}.log

--#3, #4

1,024

1,048,576

Log size specified during log setup

(512)

Job execution internal log

Agt_Path\log\jpqclient\jpqclient_{00|01|02|03|04|05|06|07|08|09}.log

--#3, #4

30,720

1,048,576

Log size specified during log setup

(3,072)

1.2.6(3)

Agt_Path\log\jpqclient\jpqclientnjp_{00|01|02|03|04|05|06|07|08|09}.log

--#3, #4

30,720

1,048,576

Log size specified during log setup

(3,072)

Agt_Path\log\jpqclient\jpqnjpdata_{00|01}.log

--#3, #4

1,024

1,048,576

Log size specified during log setup

(512)

Event/action common log#5

Agt_Path\log\jpocommonerr{1|2}.log

--#3

16,384

4,194,304

(4 gigabytes)

Log size specified during log setup

(8,192)

1.2.6(4)

jajs_config command trace log

Agt_Path\log\jajs_config_{1|2}.log

Trace log related to the command that specifies an environment setting parameter#3

1

256

128

N

jajs_setup_cluster command trace log#5

Agt_Path\log\jajs_setup_cluster_{01|02|03|04|05|06|07|08|09|10|11|12|13|14|15|16|17|18|19|20}.log#11

Trace log related to the command that configures a cluster environment#3

200

200

When the jajs_setup_cluster command is executed

N

jajs_pmtcon command trace log

Agt_Path\log\jajs_pmtcon_{1|2}.log

Log data output when restricting of connection sources is set#3

1

256

128

N

Queueless log

Agt_Path\log\ajsql-log{1|2}.log

Information related to jobs executed by the queueless agent service

16,384

4,000,000

Queueless log file size specified in the environment settings (8,192)

1.2.6(5)

Queueless trace log#5

Agt_Path\log\tracelog.ql

Execution trace log related to queueless jobs and commands related to execution control of queueless jobs#3, #4

15,360

2,097,151

Wraparound

1.2.6(5)

Queueless job execution internal log

Agt_Path\log\ajsqlexeclog#5, #10

Execution trace log related to queueless jobs#3, #4

24,576

2,097,151

Wraparound

1.2.6(5)

The status file used to store information about running queueless jobs

Agt_Path\log\ajsqlstat.dat

Information about running queueless jobs #3, #4

2,048

2,000,000

Wraparound

1.2.6(5)

Definition check log#5

Agt_Path\log\ajscheck{1|2}.log

Information related to definition pre-checks

8,192

4,000,000

Definition check log file size specified in the environment settings

1.2.6(6)

Definition check trace log#5

Agt_Path\log\tracelog.ch

Trace log related to definition pre-checks#3, #4

3,072

2,097,151

Wraparound

1.2.6(6)

Flexible job execution requester log file#5

Agt_Path\log\ajsfxreq{1|2}.log

Log storing log data output by the flexible job execution requester (manager host#13)

20,480

4,000,000

Log file size specified in environment settings (10,240)

1.2.6(10)

Flexible job execution host log file#5

Agt_Path\log\ajsfxexec{1|2}.log

Log storing log data output by the flexible job execution host (destination agent)

20,480

4,000,000

Log file size specified in environment settings (10,240)

1.2.6(10)

Flexible job trace log#5

Agt_Path\log\ajsfxtrace

--#3, #4

20,480

20,480

Wraparound

N

Log file for the broadcast agent and broadcast-execution destination agents#5

Agt_Path\log\ajsfxbcctl{1|2}.log

--#3

20,480

4,000,000

Log file size specified in environment settings (10,240)

1.2.6(10)

Broadcast agent log file#5

Agt_Path\log\ajsfxdstr{1|2}.log

Log storing log data output by the broadcast agent

40,960

4,000,000

Log file size specified in environment settings (20,480)

1.2.6(10)

Internal trace log file for HTTP connection job execution#5

Agt_Path\log\ajshttptrace

--#3, #4

20,480

20,480

Wraparound

N

Job execution history log file#14

Agt_Path\log\jpqjobhistory{0|1}.log

Job execution history log output by JP1/AJS3 - Agent Minimal Edition

1,024

65,536

Log file size specified in environment settings (512)

1.2.6(3)

Job execution result log file

Agt_Path\log\jobexecresult\ajsjobexecresult{1|2|3|4|5|6|7|8|9|10|11|12}.log

Information about job executions on an agent host

196,608

1,048,576

Log file size specified in environment settings (16,384)

1.2.6(3)

Event job execution result log file

Agt_Path\log\evjobexecresult\ajsevjobexecresult{1|2|3|4}.log

Information about event job executions on an agent host

65,536

1,048,576

Log file size specified in environment settings (16,384)

1.2.6(4)

Management Portal execution environment internal log

Agt_Path\log\jajs_sysshow_{1|2}.log

--#3

8,192

8,192

4,096

N

ajssysctlad internal log

Agt_Path\log\ajssysctlad{1|2}.log

Internal log of the management portal execution environment (for agent processes)

Stores information about process start and stop, information about process acceptance begin and end, and results of API function executions by JP1/Base.

8,192

4,000,000

Size of the ajssysctlad internal log

(4,096)

1.2.6(14)

ajssysctl trace log

Agt_Path\log\tracelog.sc

Process trace log

20,480

20,480

Wraparound

N

ajssysctlad log

Agt_Path\log\ajssca-log{1|2}.log

Log storing information about the operations performed by the manager host.

20,480

4,000,000

Log file size specified in environment settings (10,240)

1.2.6(14)

Legend:

N : The log file settings cannot be changed.

#1

The unit is kilobytes unless otherwise specified. The value in parentheses is the kilobytes value expressed in gigabytes.

#2

The unit is kilobytes. The value in parentheses in this column indicates the default timing for switching log files.

#3

The format of the logged information is not publicly available outside the company.

#4

The information is in binary format and cannot be read.

#5

Information is also output to the default folder in a cluster system.

#6

In a cluster system, the file names vary depending on how JP1/AJS3 has been installed.

If JP1/AJS3 09-00 or later has been installed as a new installation:

jpqagtexec{1|2|3|4|5|6|7|8}.log

If JP1/AJS3 has been installed as an upgrade installation from JP1/AJS2:

If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system

jpqExecLog_agt{1|2|3|4|5|6|7|8}.log

#7

In a cluster system, the file names vary depending on how JP1/AJS3 has been installed.

If JP1/AJS3 09-00 or later has been installed as a new installation:

jpqagtexecmon{1|2|3|4|5|6|7|8}.log

If JP1/AJS3 has been installed as an upgrade installation from JP1/AJS2:

If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system

jpqExecLog_agtmon{1|2|3|4|5|6|7|8}.log

#8

In a cluster system, the file names vary depending on how JP1/AJS3 has been installed.

If JP1/AJS3 09-00 or later has been installed as a new installation:

jpqcliexec{1|2}.log

If JP1/AJS3 has been installed as an upgrade installation from JP1/AJS2:

If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system

jpqExecLog_cli{1|2}.log

#9

You can change the Agt_Path part differs depending on the value specified in the WaitInfFileOutDir environment setting parameter for the [{JP1_DEFAULT|logical-host-name}\JP1AOMAGENT] definition key.

#10

The file name is different in a cluster system:

Agt_Path\log\ajsqlexeclog-[logical-host-name]

If the full path name is 256 bytes or more, [logical-host-name] becomes the first 30 bytes of the logical host name.

#11

The latest execution result is output to the log file numbered 01. When the command is executed, log files are renamed by incrementing their numbers by 1, and a new log file with 01 is created. If the command is executed when a log file with the largest allowed number already exists, the log information in that log file is discarded.

#12

Information is also output to a folder on the physical host in a cluster system. Therefore, you can change the value of Agt_Path even in a cluster system by specifying the value in the WaitInfFileOutDir environment setting parameter for the [JP1_DEFAULT\JP1AOMAGENT] definition key.

#13

If a relay agent exists, log data is output to the relay agent. If a relay agent does not exist, log data is output to the manager host.

#14

This log file is used exclusively by JP1/AJS3 - Agent Minimal Edition. JP1/AJS3 - Agent does not output log data to this file.

Table 1‒10: Log files and folders in JP1/AJS3 - View (for Windows)

Log name

Log file and folder names

Logged information

Default disk space#1

Maximum disk space#1

Timing for switching files

Details on changing settings

JP1/AJS3 - View log

View_Path\log\ajs.log

--#2

--

1,024

When JP1/AJS3 - View terminates

N

JP1/AJS3 - View information log#3

View_Path\log\ajs2view[#nnnn_]#3{1|2}#4log#5

--#2

2,048

1,048,576

Maximum log file size specified in the Preferences dialog box

1.2.6(12)

License management log

View_Path\log\hliclibtrc{1|2|3|4|5}.log

License management log file#2

5,120

5,120

1,024

N

View_Path\log\hlicliberr{1|2|3|4|5}.log

5,120

5,120

1,024

View_Path\log\hliclibmgrtrc{1|2|3|4|5}.log

5,120

5,120

1,024

View_Path\log\hliclibmgrerr{1|2|3|4|5}.log

5,120

5,120

1,024

View_Path\log\hliclibtrc.conf

Management file for the license management log file#2

256 bytes

256 bytes

Wraparound

View_Path\log\hlicliberr.conf

256 bytes

256 bytes

Wraparound

View_Path\log\hliclibmgrtrc.conf

256 bytes

256 bytes

Wraparound

View_Path\log\hliclibmgrerr.conf

256 bytes

256 bytes

Wraparound

Custom job registration program log

View_Path\log\ajscjobregm.log

--#2

--

1,024

When Register Custom Job dialog box closes

N

View_Path\log\cjobregm[#nnnn_]#3{1|2}#4log#5

Log data output when a custom job is registered#2

2,048

2,048

1,024

Legend:

N : The log file settings cannot be changed.

#1

The unit is kilobytes unless otherwise specified.

#2

The format of the logged information is not publicly available outside the company.

#3

When multiple units are started, a value in the range from 0001 to 9999 is assigned to nnnn of #nnnn_. When only one unit is started, #nnnn_ is omitted.

The Default disk space and Maximum disk space columns indicate the disk space that is allocated to a log file if only one unit is started.

#4

The value in {1|2} indicates the log file number, which is fixed at 2.

If the size of the file specified with 1 reaches the upper limit, data continues to be output to the file specified by 2. If the size of the file specified by 2 also reaches the upper limit, the information in the file specified by 1 is deleted and data continues to be output to the file specified by 1.

#5

If the multiuser remote desktop connection function is enabled, the output destination changes to the folder below. Note that OS-user-name does not include domain information.

View_Path\log\OS-user-name

For details about the multiuser remote desktop connection function, see 11.2.7 Allowing multiple users to concurrently use JP1/AJS3 - View via remote desktop connections in the JP1/Automatic Job Management System 3 Operator's Guide.

Table 1‒11: Log files and folders in JP1/AJS3 - Web Console (for Windows)

Log name

Log file and folder names

Logged information

Default disk space#1

Maximum disk space#1

Timing for switching files

Details on changing settings

Command log

Web_Path\log\ajswebsetup{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16}.log

Log data about setup command operations

128

16,384

Wraparound

1.2.6(13)

Web_Path\log\jajs_web_service{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16}.log

Log data about start and stop of service

128

16,384

Wraparound

Application server log#2

Web_Path\log\appserver{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16}.log

Log data about operations and API requests

8,192

16,384

Wraparound

1.2.6(13)

Application server common log#2

Web_Path\log\appserversys{1|2}.log

Log data about start and stop of web applications

8,192

8,192

Wraparound

N

Legend:

N : The log file settings cannot be changed.

#1

The unit is kilobytes unless otherwise specified.

#2

The log is output as a log file in UTF-8 format.

(2) Log files and directories in UNIX

Table 1-13 and Table 1-15 describe the log file names and the directory names of the scheduler logs and the trace logs for each function in JP1/AJS3 for UNIX.

The Log name column lists the names of the logs created by JP1/AJS3.

The Log file and directory names column lists the names of the JP1/AJS3 log files in full-path-name form.

In a cluster system, consider the path names indicate the directories in the Log output directory in a cluster system column in the following table unless otherwise specified.

Table 1‒12: Log output directories in a cluster system

Value in Table 1-13 and Table 1-15

Log output directory in a cluster system

/var/opt/jp1ajs2/

shared-disk-name/jp1ajs2

/var/opt/jp1ajs3web/

shared-disk-name/jp1ajs3web

The Default disk space column indicates the disk space allocated to a log file when the default environment setting is used for operation, and is the total disk space size when there are multiple log files. If the user has not changed the size of a log file, the disk space indicated in the table is the disk space allocated to that log file.

The Maximum disk space column indicates the maximum disk space that a log file uses. This value includes changes to definitions, and is the total disk size when there are multiple log files. The values in this column are the maximum values for log files whose size varies according to the definitions.

The Timing for switching files change column indicates either a limit or the point at which JP1/AJS3 switches the log file (output file for the log) to another file. A value in this column indicates that there are multiple log files and that the file with the oldest update date is overwritten when the maximum disk space is reached. A value in parentheses indicates the default timing for switching log files.

The Details on changing settings column shows sections in 1.2.6 Whether log file settings can be changed that describe in detail whether log file settings can be changed and how to change them. An N indicates a log file whose settings cannot be changed.

Table 1‒13: Log files and directories of JP1/AJS3 - Manager (for UNIX)

Log name

Log file and directory names

Logged information

Default disk space#1

Maximum disk space#1

Timing for switching files#2

Details on changing settings

System management log

/var/opt/jp1ajs2/log/JAJS_SPMD{1|2|3}.log

Trace log related to starting, stopping, and checking the status of the JP1/AJS3 service#3

384

33,554,432

(32 gigabytes)

Log size specified during log setup

(128)

1.2.6(1)

/var/opt/jp1ajs2/log/JAJS_SPMD_COMMAND{1|2|3}.log

384

33,554,432

(32 gigabytes)

Log size specified during log setup

(128)

/var/opt/jp1ajs2/log/JAJS_DBMD_[embedded-database-setup-ID]{1|2|3}.log

384

33,554,432

(32 gigabytes)

Log size specified during log setup

(128)

/var/opt/jp1ajs2/log/JAJS_HSTD{1|2|3}.log

384

33,554,432

(32 gigabytes)

Log size specified during log setup

(128)

/var/opt/jp1ajs2/log/JAJS_AGTD{1|2|3}.log

384

33,554,432

(32 gigabytes)

Log size specified during log setup

(128)

/var/opt/jp1ajs2/log/JAJS_SCHD_[scheduler-service-name]{1|2|3}.log

384

33,554,432

(32 gigabytes)

Log size specified during log setup

(128)

Scheduler log

/var/opt/jp1ajs2/log/schedule/scheduler-service-name/ajs-log{1|2}.log

Operating information related to jobnets, jobs, and scheduler services (when scheduler log is logged separately for each scheduler service)

81,920

4,000,000

Size of the scheduler log specified in environment settings

(40,960)

1.2.6(2)

/var/opt/jp1ajs2/log/ajs-host-log{1|2}.log

Operating information related to jobnets, jobs, and scheduler services (when scheduler log is logged for the entire host)

20,480

4,000,000

Size of the scheduler log for the host specified in the environment settings

(10,240)

1.2.6(2)

ajsinetd internal log#4

/var/opt/jp1ajs2/log/ajsinetd{1|2}.log

Internal information related to the network control process#3

256

4,000,000

Size of the ajsinetd internal log

(128)

1.2.6(2)

ajscdinetd internal log

/var/opt/jp1ajs2/log/ajscdinetd{1|2}.log

Internal log for the network control process of JP1/AJS3 - Web Console#3

256

4,000,000

Size of the ajscdinetd internal log

(128)

1.2.6(2)

ajsmonsvr internal log

/var/opt/jp1ajs2/log/ajscdmonsvr_scheduler-service-name_{1|2}.log

Internal log for the ajsmonsvr process that JP1/AJS3 - Web Console connects to#3

8,192

32,768

Size of the ajsmonsvr internal log

(4,096)

1.2.6(2)

Common scheduler trace log#4

/var/opt/jp1ajs2/log/tracelog

Trace log and information about operations related to scheduler services and jobnets#3, #5

102,400

2,097,151

Wraparound

1.2.6(2)

Scheduler trace log of each scheduler service#4

/var/opt/jp1ajs2/log/tracelog_scheduler-service-name

Trace log and information about operations related to scheduler services and jobnets#3, #5

102,400

2,097,151

Wraparound

1.2.6(2)

Job execution manager log

/var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpqmanexec{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log

Trace log related to the job execution control manager process when a job is executed#3

15,360

524,288

Log size specified during log setup

(1,024)

1.2.6(3)

/var/opt/jp1ajs2/log/jpqmanexec{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log

Job execution agent log

/var/opt/jp1ajs2/log/jpqagtexec{1|2|3|4|5|6|7|8}.log

Trace log related to the job execution control agent process when a job is executed#3

4,096

524,288

Log size specified during log setup

(512)

1.2.6(3)

/var/opt/jp1ajs2/log/jpqagtexeccld{1|2|3|4|5|6|7|8}.log

4,096

524,288

Log size specified during log setup

(512)

/var/opt/jp1ajs2/log/jpqagtexecdmn{1|2|3|4|5|6|7|8}.log

4,096

524,288

Log size specified during log setup

(512)

/var/opt/jp1ajs2/log/jpqagtexecmon{1|2|3|4|5|6|7|8}.log

4,096

524,288

Log size specified during log setup

(512)

Job execution client log

/var/opt/jp1ajs2/log/jpqcliexec{1|2}.log

Execution trace log related to jpqxxxx commands and JpqxxxxAPI functions#3

1,024

524,288

Log size specified during log setup

(512)

1.2.6(3)

Job execution status report log

/var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpqnfyexec{1|2}.log

Trace log related to job execution control communication when a job is executed#3

1,024

524,288

Log size specified during log setup

(512)

1.2.6(3)

Event/action control manager log

/var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpomanager{1|2|3|4|5|6|7|8|9|10|11|12|13}.log

Trace log related to the event/action control manager when an event job is executed#3

53,248

16,777,216

(16 gigabytes)

Log size specified during log setup

(4,096)

1.2.6(4)

/var/opt/jp1ajs2/log/jpomanager{1|2|3|4|5|6}.log

12,288

16,777,216

(16 gigabytes)

Log size specified during log setup

(2,048)

/var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpomgrsub{1|2|3|4|5|6|7|8}.log

24,576

16,777,216

(16 gigabytes)

Log size specified during log setup

(3,072)

/var/opt/jp1ajs2/log/ jpomgrsub{1|2|3|4|5|6|7|8}.log

Event/action control agent log

/var/opt/jp1ajs2/log/jpoagent{1|2|3|4|5|6|7|8}.log

Trace log related to the event/action control agent when an event job is executed#3

24,576

16,777,216

(16 gigabytes)

Log size specified during log setup

(3,072)

1.2.6(4)

/var/opt/jp1ajs2/log/jpoagtsub{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16}.log

32,768

16,777,216

(16 gigabytes)

Log size specified during log setup

(2,048)

Event monitoring log

/var/opt/jp1ajs2/log/jpoeventwatch{1|2|3|4|5|6|7|8}.log

Execution trace log related to the JP1 event reception monitoring job and log file monitoring job#3

73,728

16,777,216

(16 gigabytes)

Log size specified during log setup

(9,216)

1.2.6(4)

Event search log

/var/opt/jp1ajs2/log/jpoevsearch{1|2}.log

Trace log related to event searching before the JP1 event reception monitoring job is executed#3

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

1.2.6(4)

File monitoring log

/var/opt/jp1ajs2/log/jpocwtflMain{1|2|3|4|5|6|7|8|9|10|11|12|13}.log

Execution trace log related to the file monitoring job#3

26,624

16,777,216

(16 gigabytes)

Log size specified during log setup

(2,048)

1.2.6(4)

Execution interval control log

/var/opt/jp1ajs2/log/jpocwttmMain{1|2|3|4|5|6}.log

Execution trace log related to the execution interval control job#3

1,536

16,777,216

(16 gigabytes)

Log size specified during log setup

(256)

1.2.6(4)

Mail monitoring log

/var/opt/jp1ajs2/log/jpocwtmlmain{1|2}.log

Execution trace log related to the mail reception monitoring job when the mail linkage function is used#3

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

1.2.6(4)

Mail delivery log

/var/opt/jp1ajs2/log/jpomailrecv{1|2}.log

Execution trace log related to the mail reception monitoring job when the mail delivery function of mail linkage is used#3

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

1.2.6(4)

NNM linkage log

/var/opt/jp1ajs2/log/jpoovlink{1|2}.log#4

Trace log related to monitoring when HP NNM is used#3

512

512

256

N

Job execution internal log

/var/opt/jp1ajs2/log/jpqagent/jpqagt_{00|01|02|03|04|05|06|07}.log

--#3, #5

12,288

1,048,576

Log size specified during log setup

(1,536)

1.2.6(3)

/var/opt/jp1ajs2/log/jpqagent/jpqmon_{00|01|02|03|04|05|06|07}.log

--#3, #5

12,288

1,048,576

Log size specified during log setup

(1,536)

/var/opt/jp1ajs2/log/jpqagent/jpqnjpagt_{00|01|02|03|04|05|06|07}.log

--#3, #5

12,288

1,048,576

Log size specified during log setup

(1,536)

/var/opt/jp1ajs2/log/jpqagent/jpqnjpdata_{00|01}.log

--#3, #5

1,024

1,048,576

Log size specified during log setup

(512)

Job execution internal log

/var/opt/jp1ajs2/log/jpqclient/jpqclient_{00|01|02|03|04|05|06|07|08|09}.log

--#3, #5

30,720

1,048,576

Log size specified during log setup

(3,072)

1.2.6(3)

/var/opt/jp1ajs2/log/jpqclient/jpqclientnjp_{00|01|02|03|04|05|06|07|08|09}.log

--#3, #5

30,720

1,048,576

Log size specified during log setup

(3,072)

/var/opt/jp1ajs2/log/jpqclient/jpqnjpdata_{00|01}.log

--#3, #5

1,024

1,048,576

Log size specified during log setup

(512)

Job execution internal log

/var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpqmanager/jpqman_{00|01|02|03}.log

--#3, #5

6,144

1,048,576

Log size specified during log setup

(1,536)

1.2.6(3)

/var/opt/jp1ajs2/log/jpqmanager/jpqman_{00|01|02|03}.log

/var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpqmanager/jpqmandb_{00|01|02|03}.log

--#3, #5

6,144

1,048,576

Log size specified during log setup

(1,536)

/var/opt/jp1ajs2/log/jpqmanager/jpqmandb_{00|01|02|03}.log

/var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpqmanager/jpqmannjp_{00|01|02|03}.log

--#3, #5

6,144

1,048,576

Log size specified during log setup

(1,536)

/var/opt/jp1ajs2/log/jpqmanager/jpqmannjp_{00|01|02|03}.log

/var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpqmanager/jpqnjpdata_{00|01}.log

--#3, #5

1,024

1,048,576

Log size specified during log setup

(512)

/var/opt/jp1ajs2/log/jpqmanager/jpqnjpdata_{00|01}.log

Job execution internal log

/var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpqnotify/jpqnotify_{00|01}.log

--#3, #5

3,072

1,048,576

Log size specified during log setup

(1,536)

1.2.6(3)

/var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpqnotify/jpqnotifynjp_{00|01}.log

--#3, #5

3,072

1,048,576

Log size specified during log setup

(1,536)

/var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpqnotify/jpqnjpdata_{00|01}.log

--#3, #5

1,024

1,048,576

Log size specified during log setup

(512)

Flow control subprocess internal log

/var/opt/jp1ajs2/log/schedule/scheduler-service-name/ajsflbd{1|2}.log

Trace log related to units with wait conditions#3

20,480

4,000,000

Size of the flow control subprocess internal log (10,240)

1.2.6(2)

Job execution environment database reorganization log

/var/opt/jp1ajs2/database/queue/CONDENSE{1|2}.log

--

1,024

1,024

512

N

Event/action common log#4

/var/opt/jp1ajs2/log/jpocommonerr{1|2}.log

--#3

16,384

4,194,304

(4 gigabytes)

Log size specified during log setup

(8,192)

1.2.6(4)

Event/action common error log#4

/var/opt/jp1ajs2/log/jpoproccomerr{1|2}.log

--#3

256

256

128

N

jajs_migrate command trace log

/var/opt/jp1ajs2/log/jajs_migrate_logical-host-name_{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20}.log#13

Trace log related to the command that changes the system environment from JP1/AJS2 to JP1/AJS3#3

10

200

When the jajs_migrate command is executed

N

jajs_setup command trace log#4

/var/opt/jp1ajs2/log/jajs_setup_{01|02|03|04|05|06|07|08|09|10|11|12|13|14|15|16|17|18|19|20}.log#11

Trace log related to the command that specifies environment settings#3

200

200

When the jajs_setup command is executed

N

jajs_config command trace log

/var/opt/jp1ajs2/log/jajs_config_{1|2}.log

Trace log related to the command that specifies an environment setting parameter#3

1

256

128

N

jajs_setup_cluster command trace log#4

/var/opt/jp1ajs2/log/jajs_setup_cluster_{01|02|03|04|05|06|07|08|09|10|11|12|13|14|15|16|17|18|19|20}.log#11

Trace log related to the command that configures a cluster environment#3

200

200

When the jajs_setup_cluster command is executed

N

jp1ajs2_setup_cluster command trace log#6

/var/opt/jp1ajs2/log/JAJS_SETUP/logical-host-name/jajs_setup.log#7

Trace log related to the command that sets up a logical host#3

10

100

None

N

jajs_killall.cluster command trace log

shared-dircetory/jp1ajs2/log/jajs_killall.cluster_logical-host-name.{1|2|3|4|5}.log

Trace log related to the command that kills a process associated with a logical host#3

50

50

When the jajs_killall.cluster command is executed

1.2.6(11)

jajsshowadminusr command trace log

/var/opt/jp1ajs2/log/jajsadminusr_{1|2}.log

Setting and reference log for AJS administrators#3

1

256

128

N

jajs_pmtcon command trace log

/var/opt/jp1ajs2/log/jajs_pmtcon_{1|2}.log

Log data output when restricting of connection sources is set#3

1

256

128

N

Queueless log

/var/opt/jp1ajs2/log/ajsql-log{1|2}.log

Information related to jobs executed by the queueless agent service

16,384

4,000,000

Queueless log file size specified in the environment settings (8,192)

1.2.6(5)

Queueless trace log#4

/var/opt/jp1ajs2/log/tracelog.ql

Execution trace log related to queueless jobs and commands related to execution control of queueless jobs#3, #5

15,360

2,097,151

Wraparound

1.2.6(5)

Queueless job execution internal log

/var/opt/jp1ajs2/log/ajsqlexeclog#4, #10

Execution trace log related to queueless jobs#3, #5

24,576

2,097,151

Wraparound

1.2.6(5)

/var/opt/jp1ajs2/log/ajsqlexeclog_ftpd#4

10,240

2,097,151

Wraparound

The status file used to store information about running queueless jobs

/var/opt/jp1ajs2/log/ajsqlstat.dat

Information about running queueless jobs#3, #5

2,048

2,000,000

Wraparound

1.2.6(5)

Maintenance log#4

/var/opt/jp1ajs2/log/jajs_maintain_manager{1|2|3|4}.log#8

Information related to database reorganization that is executed during maintenance#3

1,484

1,484

When maintenance is performed

N

/var/opt/jp1ajs2/log/jajs_maintain_[scheduler-service-name]{1|2|3|4}.log#8

1,484

1,484

When maintenance is performed

Automatic reorganization log#4

/var/opt/jp1ajs2/log/jpqautocond{1|2|3|4}.log#9

Information related to database reorganization that is executed during automatic reorganization#3

764

764

When automatic reorganization is performed

N

/var/opt/jp1ajs2/log/ajsautocond{1|2|3|4}.log#9

764

764

When automatic reorganization is performed

Definition check log#4

/var/opt/jp1ajs2/log/ajscheck{1|2}.log

Information related to definition pre-checks

8,192

4,000,000

Definition check log file size specified in the environment settings

1.2.6(6)

Definition check trace log#4

/var/opt/jp1ajs2/log/tracelog.ch

Trace log related to definition pre-checks#3, #5

3,072

2,097,151

Wraparound

1.2.6(6)

Execution log for embedded database operation commands#4

/var/opt/jp1ajs2/log/ajsembdbbackup.log

Information related to the execution of commands for manipulating the embedded database#3

--

--

--#12

N

/var/opt/jp1ajs2/log/ajsembdbrstr.log

--

--

--#12

/var/opt/jp1ajs2/log/embdb/ajsembdboplog[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

/var/opt/jp1ajs2/log/embdb/ajsembdbrorg[host-name][scheduler-service-name]{1|2|3|4}.log

4,096

4,096

1,024

/var/opt/jp1ajs2/log/embdb/ajsembdbreclaim[host-name][scheduler-service-name]{1|2|3|4}.log

4,096

4,096

1,024

/var/opt/jp1ajs2/log/embdb/ajsembdbreclaim_nv_[host-name][scheduler-service-name]{1|2|3|4}.log

4,096

4,096

1,024

/var/opt/jp1ajs2/log/embdb/ajsembdbaddarea[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

/var/opt/jp1ajs2/log/embdb/ajsembdbaddlog[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

/var/opt/jp1ajs2/log/embdb/ajsembdbstop[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

/var/opt/jp1ajs2/log/embdb/ajsembdbstop_nv[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

/var/opt/jp1ajs2/log/embdb/ajsembdbstart[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

/var/opt/jp1ajs2/log/embdb/ajsembdbstart_nv[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

/var/opt/jp1ajs2/log/embdb/ajsembdbcancel[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

/var/opt/jp1ajs2/log/embdb/ajsembdbunset[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

/var/opt/jp1ajs2/log/embdb/ajsembdbbuild[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

/var/opt/jp1ajs2/log/embdb/ajsembdbsetup[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

/var/opt/jp1ajs2/log/embdb/ajsembdbstatus[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

/var/opt/jp1ajs2/log/embdb/ajsembdbinstl{1|2|3|4}.log

4,096

4,096

1,024

/var/opt/jp1ajs2/log/embdb/ajsembdbuninstl{1|2|3|4}.log

4,096

4,096

1,024

/var/opt/jp1ajs2/log/embdb/ajsembdbmaintain{1|2|3|4}.log

4,096

4,096

1,024

/var/opt/jp1ajs2/log/embdb/ajsembdbmgrctl[embedded-database-setup-ID]{1|2|3|4}.log

4,096

4,096

1,024

Embedded database maintenance log#4

/var/opt/jp1ajs2/log/embdb/dbautomaintenance[host-name].{log|old}

Log data that is output during the automatic maintenance of an embedded database

4,096

4,096

When automatic maintenance is performed

N

Execution log for jajs_dbbackup command#4

/var/opt/jp1ajs2/log/jajs_dbbackup_[embedded-database-setup-ID]_{1|2}.log

Log data that is output when the embedded DB is backed up

8,192

8,192

4,096

N

Execution log for jajs_dbrestore command#4

/var/opt/jp1ajs2/log/jajs_dbrestore_[embedded-database-setup-ID]_{1|2}.log

Log data that is output when the embedded DB is restored

8,192

8,192

4,096

N

/var/opt/jp1ajs2/log/embdb/ajsembdb_ebrstr[embedded-database-setup-ID].log

1,024

1,024

When the jajs_dbrestore command is executed

Agent management trace log#4

/var/opt/jp1ajs2/log/ajsagttrace

--#3, #5

20,480

20,480

Wraparound

N

Agent management log

/var/opt/jp1ajs2/log/ajsagtmd{1|2}.log

Agent information for agent management control#3

8,192

8,192

4,096

1.2.6(7)

Communication control trace log

/var/opt/jp1ajs2/log/tracelog-nw

--#3, #5

40,960

40,960

Wraparound

1.2.6(8)

Communication control log

/var/opt/jp1ajs2/log/ajsnetwd{1|2|3|4|5}.log

--#3

51,200

51,200

10,240

1.2.6(8)

Export command trace log #4

/var/opt/jp1ajs2/log/jajs_rpenvexport_[logical-host-name]_{1|2|3|4}.log

--#3

256

256

32

N

/var/opt/jp1ajs2/log/ajsdbenvexport_[logical-host-name]_{1|2|3|4}.log

--#3

256

256

32

Import command trace log#4

/var/opt/jp1ajs2/log/jajs_rpenvimport_[logical-host-name]_{1|2|3|4}.log

--#3

256

256

32

N

/var/opt/jp1ajs2/log/ajsdbenvimport_[logical-host-name]_{1|2|3|4}.log

--#3

256

256

32

Migration command execution log#4

/var/opt/jp1ajs2/log/JP1AJS3_DBCnvExport_{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20}.log#13

Log information related to execution of a migration command#3

10

200

When the ajscnvdbexport command is executed

N

/var/opt/jp1ajs2/log/JP1AJS3_DBCnvImport_{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20}.log#13

10

200

When the ajscnvdbimport command is executed

ajsdbmgrd internal log

/var/opt/jp1ajs2/log/ajsdbmgrd_[embedded-database-setup-ID]{1|2}.log

Internal log for the database operation control process#3

8,192

8,192

4,096

1.2.6(9)

ajsshmdel command trace log

/var/opt/jp1ajs2/log/ajsshmdel{1|2}.log

Log output when shared memory information is deleted#3

1

256

128

N

Flexible job execution requester log file#4

/var/opt/jp1ajs2/log/ajsfxreq{1|2}.log

Log storing log data output by the flexible job execution requester (manager host#14)

20,480

4,000,000

Log file size specified in environment settings (10,240)

1.2.6(10)

Flexible job execution host log file#4

/var/opt/jp1ajs2/log/ajsfxexec{1|2}.log

Log storing log data output by the flexible job execution host (destination agent)

20,480

4,000,000

Log file size specified in environment settings (10,240)

1.2.6(10)

Flexible job trace log#4

/var/opt/jp1ajs2/log/ajsfxtrace

--#3, #5

20,480

20,480

Wraparound

N

Log file for the broadcast agent and broadcast-execution destination agents#4

/var/opt/jp1ajs2/log/ajsfxbcctl{1|2}.log

--#3

20,480

4,000,000

Log file size specified in environment settings (10,240)

1.2.6(10)

Broadcast agent log file#4

/var/opt/jp1ajs2/log/ajsfxdstr{1|2}.log

Log storing log data output by the broadcast agent

40,960

4,000,000

Log file size specified in environment settings (20,480)

1.2.6(10)

Internal trace log file for HTTP connection job execution#4

/var/opt/jp1ajs2/log/ajshttptrace

--#3, #5

20,480

20,480

Wraparound

N

Agent monitoring trace log#4

/var/opt/jp1ajs2/log/tracelog.agm

--#3, #5

20,480

20,480

Wraparound

N

performance log file

Files under /var/opt/jp1ajs2/log/schedule/scheduler-service-name/ajsreport

Log storing the operating status of each process#3, #5

604,800

1,814,400

Wraparound

1.2.6(2)

jajs_extdb command trace log

Mgr_Path\log\jajs_extdb_{1|2}.log

--#3

256

256

128

N

ODBC internal error log

/var/opt/jp1ajs2/log/ajsodbc{1|2}.log

--#3

4,096

4,096

2,048

N

Internal trace log file for JP1/IM2 linkage command

/var/opt/jp1ajs2/log/IMDDAdapter_HITACHI_JP1_AJS3_{00|01}.log

--#3

2,048

2,048

1,024

N

/var/opt/jp1ajs2/log/ajsimlinktrend_{1|2}.log

--#3

4,096

4,096

Size of the internal trace log file for JP1/IM2 linkage command (2,048)

/var/opt/jp1ajs2/log/ajsimlinkunitshow_{1|2}.log

--#3

4,096

4,096

Size of the internal trace log file for JP1/IM2 linkage command (2,048)

Internal information log file for JP1/IM2 linkage command

If a linkage function is run for a logical host:

/var/opt/jp1ajs2/log/IMAC_[logical-host-name]_{00|01}.log

If a linkage function is run for a physical host:

/var/opt/jp1ajs2/log/IMAC_{00|01}.log

--#3

--#15

--#15

When a linkage function with JP1/IM2 is run

N

Internal error log file for JP1/IM2 linkage command

If a linkage function is run for a logical host:

/var/opt/jp1ajs2/log/IMACE_[logical-host-name]_{00|01}.log

If a linkage function is run for a physical host:

/var/opt/jp1ajs2/log/IMACE_{00|01}.log

--#3

20

20

When a linkage function with JP1/IM2 is run

N

Temporary output file for JP1/IM2 linkage command

If a linkage function is run for a logical host:

/var/opt/jp1ajs2/tmp/IMAgps_[logical-host-name]

If a linkage function is run for a physical host:

/var/opt/jp1ajs2/tmp/IMAgps

--#3

--#15

--#15

When a linkage function with JP1/IM2 is run

N

Job execution result log file

/var/opt/jp1ajs2/log/jobexecresult/ajsjobexecresult{1|2|3|4|5|6|7|8|9|10|11|12}.log

Information about job executions on an agent host

196,608

1,048,576

Log file size specified in environment settings (16,384)

1.2.6(3)

Event job execution result log file

/var/opt/jp1ajs2/log/evjobexecresult/ajsevjobexecresult{1|2|3|4}.log

Information about event job executions on an agent host

65,536

1,048,576

Log file size specified in environment settings (16,384)

1.2.6(4)

Execution log for jajs_cnvdb command#4

/var/opt/jp1ajs2/log/jajs_cnvdb[_logical-host-name]{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20}.log

--#3

10

10

When the jajs_cnvdb command is executed

N

Management portal execution environment internal log

/var/opt/jp1ajs2/log/jajs_sysshow_{1|2}.log

--#3

8,192

8,192

4,096

N

ajssysctlmd internal log

/var/opt/jp1ajs2/log/ajssysctlmd{1|2}.log

Internal log of the management portal execution environment (for manager processes)

Stores information about process start and stop, information about process acceptance begin and end, and results of API function executions by JP1/Base.

8,192

4,000,000

Size of the ajssysctlmd internal log

(4,096)

1.2.6(14)

ajssysctlad internal log

/var/opt/jp1ajs2/log/ajssysctlad{1|2}.log

Internal log of the management portal execution environment (for agent processes)

Stores information about process start and stop, information about process acceptance begin and end, and results of API function executions by JP1/Base.

8,192

4,000,000

Size of the ajssysctlad internal log

(4,096)

1.2.6(14)

ajssysctl trace log

/var/opt/jp1ajs2/log/tracelog.sc

Process trace log

20,480

20,480

Wraparound

N

ajssysctlmd log

/var/opt/jp1ajs2/log/ajsscm-log{1|2}.log

Log storing information about connections and operations performed by clients.

20,480

4,000,000

Log file size specified in environment settings (10,240)

1.2.6(14)

ajssysctlad log

/var/opt/jp1ajs2/log/ajssca-log{1|2}.log

Log storing information about the operations performed by the manager host.

20,480

4,000,000

Log file size specified in environment settings (10,240)

1.2.6(14)

Legend:

N : The log file settings cannot be changed.

#1

The unit is kilobytes. The value in parentheses is the kilobytes value expressed in gigabytes.

#2

The unit is kilobytes. The value in parentheses in this column indicates the default timing for switching log files.

#3

The format of the logged information is not publicly available outside the company.

#4

Information is also output to the default directory in a cluster system.

#5

The information is in binary format and cannot be read.

#6

The jp1ajs2_setup_cluster command trace log contains information that is logged when a logical host is set up. The log size does not increase during operation.

#7

If a logical host already exists and you create another logical host, a log directory is created under the name of the new logical host.

#8

The file names are different in a cluster system:

jajs_maintain_manager_[logical-host-name]{1|2|3|4}.log

jajs_maintain_[scheduler-service-name]_[logical-host-name]{1|2|3|4}.log

#9

The file names are different in a cluster system:

jpqautocond_[logical-host-name]{1|2|3|4}.log

ajsautocond_[logical-host-name]{1|2|3|4}.log

#10

The file name is different in a cluster system:

/var/opt/jp1ajs2/log/ajsqlexeclog-[logical-host-name]

If the full path name is 256 bytes or more, [logical-host-name] becomes the first 30 bytes of the logical host name.

#11

The latest execution result is output to the log file numbered 01. When the command is executed, log files are renamed by incrementing their numbers by 1, and a new log file with 01 is created. If the command is executed when a log file with the largest allowed number already exists, the log information in that log file is discarded.

#12

The size of the file increases without limit. Save or delete information in the file as necessary.

#13

The latest execution result is output to the log file with the largest number. If the command is executed when a log file with the largest allowed number already exists, the information in the log file numbered 01 is discarded.

#14

If a relay agent exists, log data is output to the relay agent. If a relay agent does not exist, log data is output to the manager host.

#15

The file size increases in proportion to the number of defined units and execution agents.

Table 1‒14: Log files and directories in JP1/AJS3 - Agent (for UNIX)

Log name

Log file and directory names

Logged information

Default disk space#1

Maximum disk space#1

Timing for switching files#2

Details on changing settings

System management log

/var/opt/jp1ajs2/log/JAJS_SPMD{1|2|3}.log

Trace log related to starting, stopping, and checking the status of the JP1/AJS3 service#3

384

33,554,432

(32 gigabytes)

Log size specified during log setup

(128)

1.2.6(1)

/var/opt/jp1ajs2/log/JAJS_SPMD_COMMAND{1|2|3}.log

384

33,554,432

(32 gigabytes)

Log size specified during log setup

(128)

Job execution agent log

/var/opt/jp1ajs2/log/jpqagtexec{1|2|3|4|5|6|7|8}.log

Trace log related to the job execution control agent process when a job is executed#3

4,096

524,288

Log size specified during log setup

(512)

1.2.6(3)

/var/opt/jp1ajs2/log/jpqagtexeccld{1|2|3|4|5|6|7|8}.log

4,096

524,288

Log size specified during log setup

(512)

/var/opt/jp1ajs2/log/jpqagtexecdmn{1|2|3|4|5|6|7|8}.log

4,096

524,288

Log size specified during log setup

(512)

/var/opt/jp1ajs2/log/jpqagtexecmon{1|2|3|4|5|6|7|8}.log

4,096

524,288

Log size specified during log setup

(512)

Job execution client log

/var/opt/jp1ajs2/log/jpqcliexec{1|2}.log

Execution trace log related to jpqxxxx commands and JpqxxxxAPI functions#3

1,024

524,288

Log size specified during log setup

(512)

1.2.6(3)

Event/action control agent log

/var/opt/jp1ajs2/log/jpoagent{1|2|3|4|5|6|7|8}.log

Trace log related to the event/action control agent when an event job is executed#3

24,576

16,777,216

(16 gigabytes)

Log size specified during log setup

(3,072)

1.2.6(4)

/var/opt/jp1ajs2/log/jpoagtsub{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16}.log

32,768

16,777,216

(16 gigabytes)

Log size specified during log setup

(2,048)

Event monitoring log

/var/opt/jp1ajs2/log/jpoeventwatch{1|2|3|4|5|6|7|8}.log

Execution trace log related to the JP1 event reception monitoring job and log file monitoring job#3

73,728

16,777,216

(16 gigabytes)

Log size specified during log setup

(9,216)

1.2.6(4)

Event search log

/var/opt/jp1ajs2/log/jpoevsearch{1|2}.log

Trace log related to event searching before the JP1 event reception monitoring job is executed#3

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

1.2.6(4)

File monitoring log

/var/opt/jp1ajs2/log/jpocwtflMain{1|2|3|4|5|6|7|8|9|10|11|12|13}.log

Execution trace log related to the file monitoring job#3

26,624

16,777,216

(16 gigabytes)

Log size specified during log setup

(2,048)

1.2.6(4)

Execution interval control log

/var/opt/jp1ajs2/log/jpocwttmMain{1|2|3|4|5|6}.log

Execution trace log related to the execution interval control job#3

1,536

16,777,216

(16 gigabytes)

Log size specified during log setup

(256)

1.2.6(4)

Mail monitoring log

/var/opt/jp1ajs2/log/jpocwtmlmain{1|2}.log

Execution trace log related to the mail reception monitoring job when the mail linkage function is used#3

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

1.2.6(4)

Mail delivery log

/var/opt/jp1ajs2/log/jpomailrecv{1|2}.log

Execution trace log related to the mail reception monitoring job when the mail delivery function of mail linkage is used#3

256

16,777,216

(16 gigabytes)

Log size specified during log setup

(128)

1.2.6(4)

NNM linkage log

/var/opt/jp1ajs2/log/jpoovlink{1|2}.log#5

Trace log related to monitoring when HP NNM is used#3

512

512

256

N

Job execution internal log

/var/opt/jp1ajs2/log/jpqagent/jpqagt_{00|01|02|03|04|05|06|07}.log

--#3, #4

12,288

1,048,576

Log size specified during log setup

(1,536)

1.2.6(3)

/var/opt/jp1ajs2/log/jpqagent/jpqmon_{00|01|02|03|04|05|06|07}.log

--#3, #4

12,288

1,048,576

Log size specified during log setup

(1,536)

/var/opt/jp1ajs2/log/jpqagent/jpqnjpagt_{00|01|02|03|04|05|06|07}.log

--#3, #4

12,288

1,048,576

Log size specified during log setup

(1,536)

/var/opt/jp1ajs2/log/jpqagent/jpqnjpdata_{00|01}.log

--#3, #4

1,024

1,048,576

Log size specified during log setup

(512)

Job execution internal log

/var/opt/jp1ajs2/log/jpqclient/jpqclient_{00|01|02|03|04|05|06|07|08|09}.log

--#3, #4

30,720

1,048,576

Log size specified during log setup

(3,072)

1.2.6(3)

/var/opt/jp1ajs2/log/jpqclient/jpqclientnjp_{00|01|02|03|04|05|06|07|08|09}.log

--#3, #4

30,720

1,048,576

Log size specified during log setup

(3,072)

/var/opt/jp1ajs2/log/jpqclient/jpqnjpdata_{00|01}.log

--#3, #4

1,024

1,048,576

Log size specified during log setup

(512)

Event/action common log#5

/var/opt/jp1ajs2/log/jpocommonerr{1|2}.log

--#3

16,384

4,194,304

(4 gigabytes)

Log size specified during log setup

(8,192)

1.2.6(4)

jajs_config command trace log

/var/opt/jp1ajs2/log/jajs_config_{1|2}.log

Trace log related to the command that specifies an environment setting parameter#3

1

256

128

N

jajs_setup_cluster command trace log#5

/var/opt/jp1ajs2/log/jajs_setup_cluster_{01|02|03|04|05|06|07|08|09|10|11|12|13|14|15|16|17|18|19|20}.log#9

Trace log related to the command that configures a cluster environment#3

200

200

When the jajs_setup_cluster command is executed

N

jp1ajs2_setup_cluster command trace log#6

/var/opt/jp1ajs2/log/JAJS_SETUP/logical-host-name/jajs_setup.log#7

Trace log related to the command that sets up a logical host#3

10

100

None

N

jajs_killall.cluster command trace log

shared-directory/jp1ajs2/log/jajs_killall.cluster_logical-host-name.{1|2|3|4|5}.log

Trace log related to the command that kills a process associated with a logical host#3

50

50

When jajs_killall.cluster is executed

1.2.6(11)

jajsshowadminusr command trace log

/var/opt/jp1ajs2/log/jajsadminusr_{1|2}.log

Setting and reference log for AJS administrators#3

1

256

128

N

jajs_pmtcon command trace log

/var/opt/jp1ajs2/log/jajs_pmtcon_{1|2}.log

Log data output when restricting of connection sources is set#3

1

256

128

N

Queueless log

/var/opt/jp1ajs2/log/ajsql-log{1|2}.log

Information related to the jobs executed by the queueless agent service

16,384

4,000,000

Queueless log file size specified in the environment settings (8,192)

1.2.6(5)

Queueless trace log#5

/var/opt/jp1ajs2/log/tracelog.ql

Execution trace log related to queueless jobs and commands related to execution control of queueless jobs#3, #4

15,360

2,097,151

Wraparound

1.2.6(5)

Queueless job execution internal log

/var/opt/jp1ajs2/log/ajsqlexeclog #5, #8

Execution trace log related to queueless jobs#3, #4

24,576

2,097,151

Wraparound

1.2.6(5)

The status file used to store information about running queueless jobs

/var/opt/jp1ajs2/log/ajsqlstat.dat

Information about running queueless jobs#3, #4

2,048

2,000,000

Wraparound

1.2.6(5)

Definition check log#5

/var/opt/jp1ajs2/log/ajscheck{1|2}.log

Information related to definition pre-checks

8,192

4,000,000

Definition check log file size specified in the environment settings

1.2.6(6)

Definition check trace log#5

/var/opt/jp1ajs2/log/tracelog.ch

Trace log related to definition pre-checks#3, #4

3,072

2,097,151

Wraparound

1.2.6(6)

ajsshmdel command trace log

/var/opt/jp1ajs2/log/ajsshmdel{1|2}.log

Log output when shared memory information is deleted#3

1

256

128

N

Flexible job execution requester log file#5

/var/opt/jp1ajs2/log/ajsfxreq{1|2}.log

Log storing log data output by the flexible job execution requester (manager host#10)

20,480

4,000,000

Log file size specified in environment settings (10,240)

1.2.6(10)

Flexible job execution host log file#5

/var/opt/jp1ajs2/log/ajsfxexec{1|2}.log

Log storing log data output by the flexible job execution host (destination agent)

20,480

4,000,000

Log file size specified in environment settings (10,240)

1.2.6(10)

Flexible job trace log#5

/var/opt/jp1ajs2/log/ajsfxtrace

--#3, #4

20,480

20,480

Wraparound

N

Log file for the broadcast agent and broadcast-execution destination agents#5

/var/opt/jp1ajs2/log/ajsfxbcctl{1|2}.log

--#3

20,480

4,000,000

Log file size specified in environment settings (10,240)

1.2.6(10)

Broadcast agent log file#5

/var/opt/jp1ajs2/log/ajsfxdstr{1|2}.log

Log storing log data output by the broadcast agent

40,960

4,000,000

Log file size specified in environment settings (20,480)

1.2.6(10)

Internal trace log file for HTTP connection job execution #5

/var/opt/jp1ajs2/log/ajshttptrace

--#3, #4

20,480

20,480

Wraparound

N

Job execution history log file#11

/var/opt/jp1ajs2/log/jpqjobhistory{0|1}.log

Job execution history log output by JP1/AJS3 - Agent Minimal Edition

1,024

65,536

Log file size specified in environment settings (512)

1.2.6(3)

Job execution result log file

/var/opt/jp1ajs2/log/jobexecresult/ajsjobexecresult{1|2|3|4|5|6|7|8|9|10|11|12}.log

Information about job executions on an agent host

196,608

1,048,576

Log file size specified in environment settings (16,384)

1.2.6(3)

Event job execution result log file

/var/opt/jp1ajs2/log/evjobexecresult/ajsevjobexecresult{1|2|3|4}.log

Information about event job executions on an agent host

65,536

1,048,576

Log file size specified in environment settings (16,384)

1.2.6(4)

Management portal execution environment internal log

/var/opt/jp1ajs2/log/jajs_sysshow_{1|2}.log

--#3

8,192

8,192

4,096

N

ajssysctlad internal log

/var/opt/jp1ajs2/log/ajssysctlad{1|2}.log

Internal log of the management portal execution environment (for agent processes)

Stores information about process start and stop, information about process acceptance begin and end, and results of API function executions by JP1/Base.

8,192

4,000,000

Size of the ajssysctlad internal log

(4,096)

1.2.6(14)

ajssysctl trace log

/var/opt/jp1ajs2/log/tracelog.sc

Process trace log

20,480

20,480

Wraparound

N

ajssysctlad log

/var/opt/jp1ajs2/log/ajssca-log{1|2}.log

Log storing information about the operations performed by the manager host.

20,480

4,000,000

Log file size specified in environment settings (10,240)

1.2.6(14)

Legend:

N: The log file settings cannot be changed.

#1

The unit is kilobytes. The value in parentheses is the kilobytes value expressed in gigabytes.

#2

The unit is kilobytes. The value in parentheses in this column indicates the default timing for switching log files.

#3

The format of the logged information is not publicly available outside the company.

#4

The information is in binary format and cannot be read.

#5

Information is also output to the default directory in a cluster system.

#6

The jp1ajs2_setup_cluster command trace log contains information that is logged when a logical host is set up. The log size does not increase during operation.

#7

If a logical host already exists and you create another logical host, a log directory is created under the name of the new logical host.

#8

The file name is different in a cluster system:

/var/opt/jp1ajs2/log/ajsqlexeclog-[logical-host-name]

If the full path name is 256 bytes or more, [logical-host-name] becomes the first 30 bytes of the logical host name.

#9

The latest execution result is output to the log file numbered 01. When the command is executed, log files are renamed by incrementing their numbers by 1, and a new log file with 01 is created. If the command is executed when a log file with the largest allowed number already exists, the log information in that log file is discarded.

#10

If a relay agent exists, log data is output to the relay agent. If a relay agent does not exist, log data is output to the manager host.

#11

This log file is used exclusively by JP1/AJS3 - Agent Minimal Edition. JP1/AJS3 - Agent does not output log data to this file.

Table 1‒15: Log files and folders in JP1/AJS3 - Web Console (for UNIX)

Log name

Log file and folder names

Logged information

Default disk space#1

Maximum disk space#1

Timing for switching files

Details on changing settings

Command log

/var/opt/jp1ajs3web/log/ajswebsetup{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16}.log

Log data about setup command operations

128

16,384

Wraparound

1.2.6(13)

/var/opt/jp1ajs3web/log/jajs_web{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16}.log

Log data about service startup command operations

128

16,384

Wraparound

/var/opt/jp1ajs3web/log/jajs_web_stop{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16}.log

Log data about service stop command operations

128

16,384

Wraparound

Application server log#2

/var/opt/jp1ajs3web/log/appserver{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16}.log

Log data about operations and API requests

8,192

16,384

Wraparound

1.2.6(13)

Application server common log#2

/var/opt/jp1ajs3web/log/appserversys{1|2}.log

Log data about start and stop of web applications

8,192

8,192

Wraparound

N

Legend:

N : The log file settings cannot be changed.

#1

The unit is kilobytes unless otherwise specified.

#2

The log is output as a log file in UTF-8 format.

1.2.6 Whether log file settings can be changed

This section explains whether log file settings can be changed.

In the following tables, the meanings of symbols used in the Whether log settings can be changed, Applicable OS, and Applicable product columns are as follows:

Whether log settings can be changed

Y: This setting can be changed.

N: This setting cannot be changed.

Applicable OS

W: Windows

U: UNIX

Applicable product

M: JP1/AJS3 - Manager

A: JP1/AJS3 - Agent

V: JP1/AJS3 - View

W: JP1/AJS3 - Web Console

(1) System management log files

The following table shows whether the settings can be changed for system management log files.

Table 1‒16: Whether the settings can be changed for system management log files

Log name

Whether log settings can be changed

Description of log setting items

Applicable OS

Applicable product

Disk space

Output destination

Log file number

System management log

Y

N

Y

Disk space

This setting can be changed by using the LOGSIZE environment setting parameter (for system management logs).

For details, see 20.3.2 Details of the environment setting parameters for the system management in the JP1/Automatic Job Management System 3 Configuration Guide.

Log file number

This setting can be changed by using the LOGFILENUM environment setting parameter.

For details, see 20.3.2 Details of the environment setting parameters for the system management in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M, A

(2) Scheduler service log files

The following table shows whether the settings can be changed for scheduler service log files.

Table 1‒17: Whether the settings can be changed for scheduler service log files

Log name

Whether log settings can be changed

Description of log setting items

Applicable OS

Applicable product

Disk space

Output destination

Log file number

Scheduler log (existing per scheduler service)

Y

Y

N

Disk space

To change this setting, use the jajs_config command to set the LOGSIZE environment setting parameter.

For details about how to estimate the required disk space, see 3.4.1 Estimating the size of scheduler log files in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Output destination

This setting can be changed by using the AJSLOGFILE1 and AJSLOGFILE2 environment setting parameter.

For details, see 20.4.2 Details of the environment setting parameters for scheduler services in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M

Scheduler log (existing per host)

Y

Y

N

Disk space

To change this setting, use the jajs_config command to set the HOSTLOGSIZE environment setting parameter.

For details about how to estimate the required disk space, see 3.4.1 Estimating the size of scheduler log files in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Output destination

This setting can be changed by using the HOSTLOGFILE1 and HOSTLOGFILE2 environment setting parameter.

For details, see 20.3.2 Details of the environment setting parameters for the system management in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M

ajsinetd internal log

Y

N

N

Disk space

To change this setting, use the jajs_config command to set the AJSINETDLOGSIZE environment setting parameter.

For details, see 20.4.2 Details of the environment setting parameters for scheduler services in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M

ajscdinetd internal log

Y

N

N

Disk space

To change this setting, use the jajs_config command to set the AJSCDINETDLOGSIZE environment setting parameter.

For details, see 20.4.2 Details of the environment setting parameters for scheduler services in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M

ajsmonsvr internal log

Y

N

N

Disk space

To change this setting, use the jajs_config command to set the CDMONSVRLOGSIZE environment setting parameter.

For details, see 20.4.2 Details of the environment setting parameters for scheduler services in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M

Common scheduler trace log

Y

Y

N

Disk space

To change this setting, use the ajstrsetsz command.

Output destination

The default output destination folder or directory is used even in a cluster configuration.

This setting can be changed by using the TRACELOGFILE environment setting parameter.

For details, see 20.4.2 Details of the environment setting parameters for scheduler services in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M

Scheduler trace log of each scheduler service

Y

Y

N

Disk space

To change this setting, use the ajstrsetsz command.

Output destination

The default output destination folder or directory is used even in a cluster configuration.

This setting can be changed by using the TRACELOGDIVDIR environment setting parameter.

For details, see 20.4.2 Details of the environment setting parameters for scheduler services in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M

Flow control subprocess internal log

Y

Y

N

Disk space

To change this setting, see 3.4.6 Estimating the size of log files output by a flow control subprocess in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Output destination

This setting can be changed by using the AJSLOGDIR environment setting parameter (for scheduler service).

For details, see 20.4.2 Details of the environment setting parameters for scheduler services in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M

performance log file

Y

Y

N

Disk space

To change this setting, use the jajs_config command to set the AJSREPORTSTOREDAYPERIOD environment setting parameter.

For details about how to estimate the required disk space, see 3.4.8 Estimating the size of performance log files in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Output destination

This setting can be changed by using the AJSREPORTDIR environment setting parameter.

For details, see 20.4.2 Details of the environment setting parameters for scheduler services in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M

(3) Job execution control log files

The following table shows whether the settings can be changed for job execution control log files.

Table 1‒18: Whether the settings can be changed for job execution control log files

Log name

Whether log settings can be changed

Description of log setting items

Applicable OS

Applicable product

Disk space

Output destination

Log file number

Job execution manager log

In Windows:

Mgr_Path\log\schedule\scheduler-service-name\jpqmanexec{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log

In UNIX:

/var/opt/jp1ajs2/log/schedule\scheduler-service-name\jpqmanexec{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log

Y

Y

Y

Disk space

To change this setting, see 3.4.5 Estimating the size of the logs output by execution in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Output destination

This setting can be changed by using the AJSLOGDIR environment setting parameter (for scheduler service).

For details, see 20.4.2 Details of the environment setting parameters for scheduler services in the JP1/Automatic Job Management System 3 Configuration Guide.

Log file number

For details about how to change this setting, see 3.4.5 Estimating the size of the logs output by execution in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

W, U

M

Job execution manager log

In Windows:

Mgr_Path\log\jpqmanexec{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log

In UNIX:

/var/opt/jp1ajs2/log/jpqmanexec{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log

Y

N

Y

Disk space

To change this setting, see 3.4.5 Estimating the size of the logs output by execution in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Log file number

For details about how to change this setting, see 3.4.5 Estimating the size of the logs output by execution in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

W, U

M

Job execution status report log

Y

Y

Y

Disk space

To change this setting, see 3.4.5 Estimating the size of the logs output by execution in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Output destination

This setting can be changed by using the AJSLOGDIR environment setting parameter (for scheduler service).

For details, see 20.4.2 Details of the environment setting parameters for scheduler services in the JP1/Automatic Job Management System 3 Configuration Guide.

Log file number

For details about how to change this setting, see 3.4.5 Estimating the size of the logs output by execution in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

W, U

M

Job execution agent log

Y

N

Y

Disk space

To change this setting, see 3.4.5 Estimating the size of the logs output by execution in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Log file number

For details about how to change this setting, see 3.4.5 Estimating the size of the logs output by execution in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

W, U

M, A

Job execution client log

Job execution internal log

In Windows:

Mgr_Path\log\schedule\scheduler-service-name\jpqmanager\jpqman_{00|01|02|03}.log

Mgr_Path\log\schedule\scheduler-service-name\jpqmanager\jpqmandb_{00|01|02|03}.log

Mgr_Path\log\schedule\scheduler-service-name\jpqmanager\jpqmannjp_{00|01|02|03}.log

Mgr_Path\log\schedule\scheduler-service-name\jpqmanager\jpqnjpdata_{00|01}.log

Mgr_Path\log\schedule\scheduler-service-name\jpqnotify\jpqnotify_{00|01}.log

Mgr_Path\log\schedule\scheduler-service-name\jpqnotify\jpqnotifynjp_{00|01}.log

Mgr_Path\log\schedule\scheduler-service-name\jpqnotify\jpqnjpdata_{00|01}.log

In UNIX:

/var/opt/jp1ajs2/log/schedule\scheduler-service-name\jpqmanager/jpqman_{00|01|02|03}.log

/var/opt/jp1ajs2/log/schedule\scheduler-service-name\jpqmanager/jpqmandb_{00|01|02|03}.log

/var/opt/jp1ajs2/log/schedule\scheduler-service-name\jpqmanager/jpqmannjp_{00|01|02|03}.log

/var/opt/jp1ajs2/log/schedule\scheduler-service-name\jpqmanager/jpqnjpdata_{00|01}.log

/var/opt/jp1ajs2/log/schedule\scheduler-service-name\jpqnotify/jpqnotify_{00|01}.log

/var/opt/jp1ajs2/log/schedule\scheduler-service-name\jpqnotify/jpqnotifynjp_{00|01}.log

/var/opt/jp1ajs2/log/schedule\scheduler-service-name\jpqnotify/jpqnjpdata_{00|01}.log

Y

Y

Y

Disk space

To change this setting, see 3.4.5 Estimating the size of the logs output by execution in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Output destination

This setting can be changed by using the AJSLOGDIR environment setting parameter (for scheduler service).

For details, see 20.4.2 Details of the environment setting parameters for scheduler services in the JP1/Automatic Job Management System 3 Configuration Guide.

Log file number

For details about how to change this setting, see 3.4.5 Estimating the size of the logs output by execution in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

W, U

M

Job execution internal log

(A job execution internal log that stores the data that is not recorded in the preceding logs.)

Y

N

Y

Disk space

To change this setting, see 3.4.5 Estimating the size of the logs output by execution in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Log file number

For details about how to change this setting, see 3.4.5 Estimating the size of the logs output by execution in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

W, U

M, A

Job execution result log file

Y

Y

Y

Disk space, output destination, and log file number

For details about how to change these settings see 3.4.9 Estimating the size of job execution result log files and event job execution result log files in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

W, U

M, A

Job execution history log file

Y

N

Y

Disk space

To change this setting, see G.2(3) Estimating the job execution history log file in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Log file number

This setting can be changed by using the JobHistoryLogFileCount environment setting parameter.

For details, see 20.5.2 Details of the environment setting parameters for the job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

A

(4) Event/action control log files

The following table shows whether the settings can be changed for event/action control log files.

Table 1‒19: Whether the settings can be changed for event/action control log files

Log name

Whether log settings can be changed

Description of log setting items

Applicable OS

Applicable product

Disk space

Output destination

Log file number

Event/action control manager log

Y

Y

Y

Disk space

To change this setting, see 3.4.3 Estimating the size of the log information output by event jobs in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Output destination

The method for changing this setting depends on the log type.#1

Log file number

For details about how to change this setting, see 3.4.3 Estimating the size of the log information output by event jobs in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

W, U

M

Event/action control agent log

Y

Y

Y

Disk space

To change this setting, see 3.4.3 Estimating the size of the log information output by event jobs in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Output destination

This setting can be changed by using the WaitInfFileOutDir environment setting parameter (for agent processes).

For details, see 20.6.2 Details of the environment setting parameters for event/action control in the JP1/Automatic Job Management System 3 Configuration Guide.

Log file number

For details about how to change this setting, see 3.4.3 Estimating the size of the log information output by event jobs in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

W, U

M, A

Event monitoring log

Y

Y

Y

Disk space

To change this setting, see 3.4.3 Estimating the size of the log information output by event jobs in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Output destination

This setting can be changed by using the WaitInfFileOutDir environment setting parameter (for agent processes).

For details, see 20.6.2 Details of the environment setting parameters for event/action control in the JP1/Automatic Job Management System 3 Configuration Guide.

Log file number

For details about how to change this setting, see 3.4.3 Estimating the size of the log information output by event jobs in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

W, U

M, A

Event search log

File monitoring log

Execution interval control log

Email sending job log (when Outlook not used)

Y

Y

N

Disk space

To change this setting, see 3.4.3 Estimating the size of the log information output by event jobs in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Output destination

This setting can be changed by using the WaitInfFileOutDir environment setting parameter (for agent processes).

For details, see 20.6.2 Details of the environment setting parameters for event/action control in the JP1/Automatic Job Management System 3 Configuration Guide.

W

M, A

Mail monitoring log (common)

Y

Y

Y

Disk space

To change this setting, see 3.4.3 Estimating the size of the log information output by event jobs in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Output destination

The method for changing this setting depends on the log type.#2

Log file number

For details about how to change this setting, see 3.4.3 Estimating the size of the log information output by event jobs in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

W

M, A

Mail monitoring log

U

Mail monitoring log (when mail linkage is performed on the desktop)

Y

Y

Y

Disk space

To change this setting, see 3.4.3 Estimating the size of the log information output by event jobs in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Output destination

Information is also output to a folder on the physical host in a cluster system. This setting can be changed by using the WaitInfFileOutDir environment setting parameter (for agent processes).

For details, see 20.6.2 Details of the environment setting parameters for event/action control in the JP1/Automatic Job Management System 3 Configuration Guide.

Log file number

For details about how to change this setting, see 3.4.3 Estimating the size of the log information output by event jobs in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

W

M, A

Mail monitoring log (when mail linkage is performed in the service)

Mail delivery log

Y

N

Y

Disk space

To change this setting, see 3.4.3 Estimating the size of the log information output by event jobs in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Log file number

For details about how to change this setting, see 3.4.3 Estimating the size of the log information output by event jobs in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

U

M, A

Event/action common log

Y

N

N

Disk space

The default output destination folder or directory is used even in a cluster configuration.

To change this setting, see 3.4.3 Estimating the size of the log information output by event jobs in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

W, U

M, A

Event job execution result log file

Y

Y

Y

Disk space, output destination, and log file number

For details about how to change these settings, see 3.4.9 Estimating the size of job execution result log files and event job execution result log files in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

W, U

M, A

#1

The method for changing the log file output destination of the event/action control manager log depends on the log type.

Mgr_Path\log\schedule\scheduler-service-name\jpomanager{1|2|3|4|5|6|7|8|9|10|11|12|13}.log (in Windows), /var/opt/jp1ajs2/log/schedule\scheduler-service-name\jpomanager{1|2|3|4|5|6|7|8|9|10|11|12|13}.log (in UNIX), Mgr_Path\log\schedule\scheduler-service-name\jpomgrsub{1|2|3|4|5|6|7|8}.log (in Windows), and /var/opt/jp1ajs2/log/schedule\scheduler-service-name\jpomgrsub{1|2|3|4|5|6|7|8}.log (in UNIX)

This setting can be changed by using the AJSLOGDIR environment setting parameter (for scheduler service).

For details, see 20.4.2 Details of the environment setting parameters for scheduler services in the JP1/Automatic Job Management System 3 Configuration Guide.

Event/action control manager logs other than the preceding ones:

This setting can be changed by using the WaitInfFileOutDir environment setting parameter (for manager process).

For details, see 20.6.2 Details of the environment setting parameters for event/action control in the JP1/Automatic Job Management System 3 Configuration Guide.

#2

The method for changing the log file output destinations of the mail monitoring log (common, Windows) and mail monitoring log (UNIX) depends on the log type.

Mgr_Path\log\jpocwtmlmain{1|2}.log (in Windows), Agt_Path\log\jpocwtmlmain{1|2}.log (in Windows), and /var/opt/jp1ajs2/log/jpocwtmlmain{1|2}.log (in UNIX)

This setting can be changed by using the WaitInfFileOutDir environment setting parameter (for agent processes).

For details, see 20.6.2 Details of the environment setting parameters for event/action control in the JP1/Automatic Job Management System 3 Configuration Guide.

Logs other than the preceding ones:

Log data is output to the folder or directory on the physical host even in a cluster configuration. This setting can be changed by using the WaitInfFileOutDir environment setting parameter (for agent processes).

For details, see 20.6.2 Details of the environment setting parameters for event/action control in the JP1/Automatic Job Management System 3 Configuration Guide.

(5) Queueless jobs log files

The following table shows whether the settings can be changed for queueless jobs log files.

Table 1‒20: Whether the settings can be changed for queueless jobs log files

Log name

Whether log settings can be changed

Description of log setting items

Applicable OS

Applicable product

Disk space

Output destination

Log file number

Queueless log

Y

Y

N

Disk space

To change this setting, use the jajs_config command to set the AJSQL_LOGSIZE environment setting parameter.

For details about how to estimate the required disk space, see 7.2.1(1) Estimating the size of the queueless log file in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Output destination

This setting can be changed by using the AJSQL_LOGFILE environment setting parameter.

For details, see 20.10.2 Details of the environment setting parameters for the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M, A

Queueless trace log

Y

Y

N

Disk space

The default output destination folder or directory is used even in a cluster configuration.

To change this setting, use the ajsqltrsetsz command.

Output destination

This setting can be changed by using the AJSQL_TRACELOGFILE environment setting parameter.

For details, see 20.10.2 Details of the environment setting parameters for the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M, A

Queueless job execution internal log

Y

Y

N

Disk space

To change this setting, use the ajsqlexecsetsz command.

For details about this command, see ajsqlexecsetsz in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

For details about how to estimate the required disk space, see 7.2.1(3) Estimating the size of the internal execution logs for queueless jobs in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Output destination

The method for changing this setting depends on the log type.#

W, U

M, A

The status file used to store information about running queueless jobs

Y

Y

N

Disk space

To change this setting, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

Output destination

This setting can be changed by using the AJSQL_STATFILE environment setting parameter.

For details, see 20.10.2 Details of the environment setting parameters for the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M, A

#

The method for changing the log file output destination of the internal logs for queueless job executions depends on the log type.

Mgr_Path\log\ajsqlexeclog (in Windows), Agt_Path\log\ajsqlexeclog (in Windows), and /var/opt/jp1ajs2/log/ajsqlexeclog (in UNIX)

This setting can be changed by using the AJSQL_EXECLOG_AGTPATH environment setting parameter. For details, see 20.10.2 Details of the environment setting parameters for the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

Mgr_Path\log\ajsqlexeclog_ftpd (in Windows) and /var/opt/jp1ajs2/log/ajsqlexeclog_ftpd (in UNIX)

This setting can be changed by using the AJSQL_EXECLOG_FTPPATH environment setting parameter. For details, see 20.10.2 Details of the environment setting parameters for the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

(6) JP1/AJS3 definition pre-check function log files

The following table shows whether the settings can be changed for JP1/AJS3 definition pre-check function log files.

Table 1‒21: Whether the settings can be changed for JP1/AJS3 definition pre-check function log files

Log name

Whether log settings can be changed

Description of log setting items

Applicable OS

Applicable product

Disk space

Output destination

Log file number

Definition check log

Y

Y

N

Disk space

The default output destination folder or directory is used even in a cluster configuration.

To change this setting, see 6.5.1 Setting up the JP1/AJS3 definition pre-check function in the JP1/Automatic Job Management System 3 Configuration Guide.

Output destination

For details about how to change this setting, see 6.5.1 Setting up the JP1/AJS3 definition pre-check function in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M, A

Definition check trace log

Y

Y

N

Disk space

The default output destination folder or directory is used even in a cluster configuration.

To change this setting, use the ajschktrsetsz command.

If you do not use the JP1/AJS3 Check Manager function or the JP1/AJS3 Check Agent function, no trace log file is created.

Output destination

For details about how to change this setting, see 6.5.1 Setting up the JP1/AJS3 definition pre-check function in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M, A

(7) Agent management control log files

The following table shows whether the settings can be changed for agent management control log files.

Table 1‒22: Whether the settings can be changed for agent management control log files

Log name

Whether log settings can be changed

Description of log setting items

Applicable OS

Applicable product

Disk space

Output destination

Log file number

Agent management log

N

Y

N

Output destination

This setting can be changed by using the AJSLOGDIR environment setting parameter (for system management).

For details, see 20.3.2 Details of the environment setting parameters for the system management in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M

(8) Communication control log files

The following table shows whether the settings can be changed for communication control log files.

Table 1‒23: Whether the settings can be changed for communication control log files

Log name

Whether log settings can be changed

Description of log setting items

Applicable OS

Applicable product

Disk space

Output destination

Log file number

Communication control trace log

N

Y

N

Output destination

This setting can be changed by using the AJSLOGDIR environment setting parameter (for system management).

For details, see 20.3.2 Details of the environment setting parameters for the system management in the JP1/Automatic Job Management System 3 Configuration Guide.

U

M

Communication control log

(9) Embedded database log files

The following table shows whether the settings can be changed for embedded database log files.

Table 1‒24: Whether the settings can be changed for embedded database log files

Log name

Whether log settings can be changed

Description of log setting items

Applicable OS

Applicable product

Disk space

Output destination

Log file number

ajsdbmgrd internal log

N

Y

N

Output destination

This setting can be changed by using the AJSLOGDIR environment setting parameter (for system management).

For details, see 20.3.2 Details of the environment setting parameters for the system management in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M

(10) Flexible job log files

The following table shows whether the settings can be changed for flexible job log files.

Table 1‒25: Whether the settings can be changed for flexible job log files

Log name

Whether log settings can be changed

Description of log setting items

Applicable OS

Applicable product

Disk space

Output destination

Log file number

Flexible job execution requester log file

Y

N

N

Disk space

This setting can be changed by using the FXREQ_LOGSIZE environment setting parameter.

For details, see 20.9.2 Details of the environment setting parameters for the flexible-job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M, A

Flexible job execution host log file

Y

N

N

Disk space

This setting can be changed by using the FXEXEC_LOGSIZE environment setting parameter.

For details, see 20.9.2 Details of the environment setting parameters for the flexible-job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M, A

Broadcast agent

Y

N

N

Disk space

This setting can be changed by using the FXBCCTL_LOGSIZE environment setting parameter.

For details, see 20.9.2 Details of the environment setting parameters for the flexible-job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M, A

Broadcast-execution destination agent log file

Broadcast agent log file

Y

N

N

Disk space

This setting can be changed by using the FXDSTR_LOGSIZE environment setting parameter.

For details, see 20.9.2 Details of the environment setting parameters for the flexible-job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M, A

(11) Command log files

The following table shows whether the settings can be changed for command log files.

Table 1‒26: Whether the settings can be changed for command log files

Log name

Whether log settings can be changed

Description of log setting items

Applicable OS

Applicable product

Disk space

Output destination

Log file number

jajs_killall.cluster command trace log

N

Y

N

Output destination

For details about how to change this setting, see 10.4.1 Script for forcibly stopping JP1/AJS3 (jajs_killall.cluster) in the JP1/Automatic Job Management System 3 Administration Guide.

U

M

(12) JP1/AJS3 - View log files

The following table shows whether the settings can be changed for JP1/AJS3 - View log files.

Table 1‒27: Whether the settings can be changed for JP1/AJS3 - View log files

Log name

Whether log settings can be changed

Description of log setting items

Applicable OS

Applicable product

Disk space

Output destination

Log file number

JP1/AJS3 - View information log

Y

N

N

Disk space

To change this setting, change the Max. log file size setting in the Other tab of the Preferences dialog box in JP1/AJS3 - View.

W

V

(13) JP1/AJS3 - Web Console log files

The following table shows whether the settings can be changed for JP1/AJS3 - Web Console log files.

Table 1‒28: Whether the settings can be changed for JP1/AJS3 - Web Console log files

Log name

Whether log settings can be changed

Description of log setting items

Applicable OS

Applicable product

Disk space

Output destination

Log file number

Command log

Y

N

Y

Disk space

To change this setting, see 4.6.1(1) Log sizes and the number of log files output by the Web Console server in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide, and 3.4.3(5)(e) COM_LOG_SIZE in the JP1/Automatic Job Management System 3 Configuration Guide.

Log file number

For details about how to change this setting, see 4.6.1(1) Log sizes and the number of log files output by the Web Console server in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide, and 3.4.3(5)(g) COM_LOG_NUM in the JP1/Automatic Job Management System 3 Configuration Guide.

W

W

Y

N

Y

Disk space

To change this setting, see 4.6.1(1) Log sizes and the number of log files output by the Web Console server in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide, and 13.3.3(5)(d) COM_LOG_SIZE in the JP1/Automatic Job Management System 3 Configuration Guide.

Log file number

For details about how to change this setting, see 4.6.1(1) Log sizes and the number of log files output by the Web Console server in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide, and 13.3.3(5)(f) COM_LOG_NUM in the JP1/Automatic Job Management System 3 Configuration Guide.

U

W

Application server log

Y

N

Y

Disk space

To change this setting, see 4.6.1(1) Log sizes and the number of log files output by the Web Console server in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide, and 3.4.3(5)(i) SERVER_LOG_SIZE in the JP1/Automatic Job Management System 3 Configuration Guide.

Log file number

For details about how to change this setting, see 4.6.1(1) Log sizes and the number of log files output by the Web Console server in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide, and 3.4.3(5)(k) SERVER_LOG_NUM in the JP1/Automatic Job Management System 3 Configuration Guide.

W

W

Y

N

Y

Disk space

To change this setting, see 4.6.1(1) Log sizes and the number of log files output by the Web Console server in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide, and 13.3.3(5)(h) SERVER_LOG_SIZE in the JP1/Automatic Job Management System 3 Configuration Guide.

Log file number

For details about how to change this setting, see 4.6.1(1) Log sizes and the number of log files output by the Web Console server in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide, and 13.3.3(5)(j) SERVER_LOG_NUM in the JP1/Automatic Job Management System 3 Configuration Guide.

U

W

(14) Management portal log files

The following table shows whether the settings can be changed for management portal log files.

Table 1‒29: Whether the settings can be changed for management portal log files

Log name

Whether log settings can be changed

Description of log setting items

Applicable OS

Applicable product

Disk space

Output destination

Log file number

ajssysctlmd internal log

Y

N

N

Disk space

This setting can be changed by using the AJSSYSCTLDLOGSIZE environment setting parameter (for manager process).

For details, see 20.15.2(4) AJSSYSCTLDLOGSIZE (for manager process) in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M

ajssysctlad internal log

Y

N

N

Disk space

This setting can be changed by using the AJSSYSCTLDLOGSIZE environment setting parameter (for agent processes).

For details, see 20.15.2(7) AJSSYSCTLDLOGSIZE (for agent process) in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M, A

ajssysctlmd log

Y

N

N

Disk space

This setting can be changed by using the LOGSIZE environment setting parameter (for manager process).

For details, see 20.15.2(5) LOGSIZE (for manager process) in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M

ajssysctlad log

Y

N

N

Disk space

This setting can be changed by using the LOGSIZE environment setting parameter (for agent processes).

For details, see 20.15.2(8) LOGSIZE (for agent process) in the JP1/Automatic Job Management System 3 Configuration Guide.

W, U

M, A

1.3 Data to be collected when a problem occurs

This section describes the data you need to collect when a problem occurs.

A problem might be caused by JP1/AJS3, the OS, a user program, or an operator error. For these reasons, you might need to collect the data discussed in this section in addition to the JP1/AJS3 logs.

JP1 provides data collection tools for batch collection of required data. Data that can be collected using the initial settings of the data collection tools are indicated with symbols in the tables above.

1.3.1 Data to collect in Windows

(1) Log information about the OS

You need to collect the following log information about the OS.

Table 1‒30: OS log information that must be collected when a problem occurs

Type of information

Default storage location for files

Collection by the tool

Windows event log

--

Y

Windows registry information

--

Y

hosts file

services file

system-folder\system32\drivers\etc\hosts

system-folder\system32\drivers\etc\services

Y

Machine configuration#1

--

Y

List of program products with running services#1

--

Y

Network configuration#1

--

Y

Memory dump

--

N#2

Crash dump

--

N#2

Problem report

--

N#2

Legend:

Y: The data collection tools can collect data.

N: The data collection tools cannot collect data.

--: There is no default file name or default storage location.

#1

Various kinds of computer information that include this information, such as the hardware environment, software environment, and Internet environment, can be obtained.

Obtaining this information might take several minutes. While the information is being obtained, the System Information window is displayed. However, because the window closes automatically, you do not need to close it manually.

#2

For details about how to collect these dumps, see 1.4.1(2) Obtain a dump file.

(2) Information about JP1

You need to collect the following information about JP1. If the problem occurs while your system is connected to a network, you also need to obtain the files on the host to which the system is connected.

Table 1‒31: JP1 information to be collected for a problem occurring in JP1/AJS3

Type of information

Default storage location for files

Collection by the tool

Log files

Work files

Definition files

JP1/Base-installation-folder\log

JP1/Base-installation-folder\conf\user_acl

Mgr_Data_Path#1\log

JP1/AJS3 - Manager-installation-folder\conf

Mgr_Data_Path#1\sys

Mgr_Data_Path#1\database

Mgr_Data_Path#1\jobinf#2

Mgr_Data_Path#1\tmp\schedule#2

JP1/AJS3 - Manager-installation-folder\PATCHLOG.txt

JP1/AJS3 - View-installation-folder\PATCHLOG.txt

JP1/AJS3 - View-installation-folder\resource

%ALLUSERSPROFILE%#1

\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\log

%ALLUSERSPROFILE%#1

\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\conf

JP1/AJS3 - Web Console-installation-folder\PATCHLOG.TXT

JP1/AJS3 - Web Console-installation-folder\conf

JP1/AJS3 - Web Console-installation-folder\sys

JP1/AJS3 - Web Console-installation-folder\uCPSB\CC\server\usrconf

JP1/AJS3 - Web Console-installation-folder\uCPSB\CC\web\redirector

JP1/AJS3 - Web Console-installation-folder\uCPSB\httpsd\conf

Web_Data_Path#4\conf

Web_Data_Path#4\log

In a cluster system, you also need to obtain the following folders:

shared-folder\JP1BASE\log

shared-folder\JP1BASE\conf

shared-folder\JP1AJS2

shared-folder\jp1ajs3web

Y

Integrated trace log folder

system-drive\Program files (x86)#2,#3\HITACHI\HNTRLib2\spool

Y

Folder containing product information files

system-drive\Program Files (x86)#2,#3\HITACHI\jp1common\JP1AJS2

Y

List of files in the database directory

--

Y

List of JP1/Base files

--

Y

Information on shared memory used while JP1/AJS3 is running

--

Y

Legend:

Y: The data collection tools can collect data.

--: There is no default file name or default storage location.

#1

Mgr_Data_Path indicates the following path:

If the installation folder is the default installation folder or is in a folder protected by the system:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2

The default value 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)

If the installation folder is other than the above:

JP1/AJS3 - Manager-installation-folder

The default installation folder is system-drive\Program Files\HITACHI\jp1ajs2.

#2

For 32-bit versions of Windows, replace Program Files (x86) with Program Files.

#3

For JP1/AJS3 - Web Console, replace Program Files (x86) with Program Files.

#4

One of the following paths is indicated in Web_Data_Path:

If the installation folder is the default installation folder or is in a folder protected by the system:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS3WEB

The default value 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

If the installation folder is other than the above:

JP1/AJS3 - Web Console-installation-folder

The default installation folder is system-drive\Program Files\HITACHI\jp1ajs3WEB.

(3) JP1/AJS3 processes

Check the operating status of processes on the Processes page of the Task Manager window of Windows.

For details about JP1/AJS3 processes, see B.2 Processes (for Windows).

(4) Operation data

Collect the following information about the operation that was being performed when the problem occurred:

Details about the operation

Time that the problem occurred

Machine configuration (the version of each OS, host name, JP1/AJS3 - Manager and JP1/AJS3 - Agent configuration)

Whether the problem is reproducible

Name of the user who logged in from JP1/AJS3 - View (if there is one)

Name of the user who logged in if JP1/AJS3 - Web Console is used and login is performed from the Web GUI or a user application

(5) Error information displayed on the screen

Make hard copies of the following:

Windows on the screen when an application error has occurred

Error message dialog box (and display the displayed information when a details button (if there is one) is clicked)

Information in the Command Prompt window if the problem occurred during the execution of a command

(6) Information about the embedded database

You need to collect the following information about the embedded database.

Table 1‒32: JP1 information to be collected for a problem occurring in JP1/AJS3

Type of information

Default storage location for files

Collection by the tool

Definition file

embedded-database-practical-directory\conf

Y

Failure information

embedded-database-practical-directory\spool

Y

Database information

Unload file that is obtained by specifying the -k unld option in the ajsembdbrorg command

Y

Legend:

Y: The data collection tools can collect data.

(7) Information about the external database

If JP1/AJS3 is operated by using an external database, the following information about the external database must be collected.

Table 1‒33: JP1 information to be collected for a problem occurring in JP1/AJS3

Type of information

Default storage location for files

Collection by the tool

Database information

--

Y

Legend:

Y: The data collection tools can collect data.

--: There is no default file name or default storage location.

(8) Other information

In addition to the above information, you need to collect the following information:

Contents of System Log and Application Log of the Windows Event Viewer window

Arguments specified in a command when the problem occurs during the execution of a command

1.3.2 Data to collect in UNIX

(1) Log information about the OS

You need to collect the following log information about the OS.

Table 1‒34: OS log information that must be collected when a problem occurs in JP1/AJS3

Type of information

Default file name or default storage location for files

Collection by the tool

syslog#1, #2

/var/adm/syslog/syslog.log

(for HP-UX)

/var/adm/messages

(for Solaris)

/var/adm/syslog/

or /var/adm/syslog/*

(for AIX)

/var/log/messages*

(for Linux)

Y

hosts file

services file

passwd file

environment file#3

inittab file

/etc/hosts

/etc/services

/etc/passwd

/etc/environment

/etc/inittab

Y

Patch information for each OS

--

Y

Shared library file for each OS

--

Y

List of processes

--

Y

core file#4

core under /opt/jp1ajs2

core under /var/opt/jp1ajs2

core in the home directory of the OS user that is mapped to a JP1/AJS3 - View login user (this information cannot be collected by the tool)

core under /opt/jp1base

core under /var/opt/jp1base/log

You also need to collect the following file in a cluster system:

/shared-directory/jp1ajs2/database/core

Y#5

Error log information#3

--

Y

Network configuration

--

Y

Information about installed Hitachi products

/etc/.hitachi/pplistd/pplistd

Y

Legend:

Y: The data collection tools can collect data.

--: There is no default file name or default storage location.

#1

Depending on the system settings, the past syslog information might be required for investigation. If syslog is set to be changed frequently in the system settings, manually collect past syslog files.

#2

If the OS of the host on which JP1/AJS3 operates is AIX, depending on the OS function, incomplete messages might result when many messages are output to syslog. Note, however, that messages output to syslog are also output to the integrated trace log (HNTRLib2), so the complete text of any incomplete messages can be viewed there.

#3

This information is collected only for AIX.

#4

Do not limit the core file output setting of the JP1/AJS3 processes when not the setting violates the security policies of the host you are using.

If the output of core file is incomplete, you might not be able to identify the cause of the error. For details about the setting, see the documentation for your OS.

#5

You need to manually obtain the core file in the current directory if information is output to the core file by executing a command. In addition, if the problem occurred in the network control process while JP1/AJS3 - View was being used, you need to manually obtain the core file in the home directory of the OS user mapped to the JP1 user who was logged in.

(2) Information about JP1

You need to collect the following information about JP1. If the problem occurred while your system was connected to a network, you also need to obtain files on the host to which the system is connected.

Table 1‒35: JP1 information to be collected for a problem occurring in JP1/AJS3

Type of information

Default storage location for files

Collection by the tool

Log files

Work files

Definition files

/var/opt/jp1ajs2/log

/var/opt/jp1base/log

/etc/opt/jp1base/conf/user_acl

/etc/opt/jp1ajs2/conf

/var/opt/jp1ajs2/database

/var/opt/jp1ajs2/sys

/var/opt/jp1ajs2/jobinf

/var/opt/jp1ajs2/tmp/schedule

/opt/jp1ajs2/PatchHistory

/opt/jp1ajs2/PatchLog

/var/opt/jp1ajs3web/log

/var/opt/jp1ajs3web/sys

/etc/opt/jp1ajs3web/conf

/opt/jp1ajs3web/PatchLog

/opt/jp1ajs3web/sys

/opt/jp1ajs3web/uCPSB/CC/server/usrconf

/opt/jp1ajs3web/uCPSB/CC/web/redirector

/opt/jp1ajs3web/uCPSB/httpsd/conf

In a cluster system, you also need to obtain the following directories:

/shared-directory/jp1ajs2

/shared-directory/jp1base/log

/shared-directory/jp1base/conf

/shared-directory/jp1ajs3web

Y

Integrated trace log directory

/var/opt/hitachi/HNTRLib2/spool

Y

List of files in the database directory

--

Y

List of JP1/Base files

--

Y

Information required for analysis of the core file

--

Y

Legend:

Y: The data collection tools can collect data.

--: There is no default file name or default storage location.

Important

When you collect information, use the tar command instead of the cp command. Because the directory from which files are obtained also contains system files, using the cp command might lead to unexpected results.

(3) JP1/AJS3 processes

Use the ps command to check the operation status of processes.

For details about JP1/AJS3 processes, see B.3 Processes (for UNIX).

(4) Operation data

Collect the following information about the operation that was being performed when the problem occurred:

Details about the operation

Time that the problem occurred

Machine configuration (the version of each OS, host name, JP1/AJS3 - Manager and JP1/AJS3 - Agent configuration)

Whether the problem is reproducible

Name of the user who logged in from JP1/AJS3 - View (if there is one)

Name of the user who logged in if JP1/AJS3 - Web Console is used and login is performed from the Web GUI or a user application

(5) Information about the embedded database

You need to collect the following information about the embedded database.

Table 1‒36: JP1 information to be collected for a problem occurring in JP1/AJS3

Type of information

Default storage location for files

Collection by the tool

Definition file

embedded-database-practical-directory/conf

Y

Failure information

embedded-database-practical-directory/spool

Y

Database information

Unload file that is obtained by specifying the -k unld option in the ajsembdbrorg command

Y

Legend:

Y: The data collection tools can collect data.

(6) Information about the external database

If JP1/AJS3 is operated by using an external database, the following information about the external database must be collected.

Table 1‒37: JP1 information to be collected for a problem occurring in JP1/AJS3

Type of information

Default strage location for files

Collection by the tool

Database information

--

Y

Legend:

Y: The data collection tools can collect data.

--: There is no default file name or default storage location.

(7) Other information

When trouble occurred at the time of command execution, collecting of the argument specified in the command is needed.

1.4 Collecting data for troubleshooting

By collecting data, you can investigate and identify the causes of a problem, and then take the necessary measures. This section describes how to collect data when a problem occurs.

1.4.1 Collecting data for troubleshooting in Windows

(1) Execute the data collection tool

JP1/AJS3 provides the data collection tools listed in the following table. Use one of these tools according to the operational requirements.

Table 1‒38: Data collection tools provided by JP1/AJS3 (for Windows)

Data collection tool

Description

jajs_log.bat

Use this tool if you have not changed the output destinations of log files and other data from the defaults, or if you do not need to collect data other than the data collected by default.

_04.bat

Use this tool if you have changed the output destinations of log files and other data from the defaults, or if you need to collect data other than the data collected by default. You can customize this tool according to the output destinations or the data to be collected.

For details about how to set up the data collection tool (_04.bat), see 7.1 Collecting log data in the JP1/Automatic Job Management System 3 Configuration Guide.

The following shows examples of executing the data collection tool:

When executing jajs_log.bat:

C:\>C:\Program Files\HITACHI\JP1AJS2\tools\jajs_log.bat

When executing the file trouble.bat that is created by customizing _04.bat:

C:\>C:\usertools\trouble.bat

By default, the results of executing the data collection tool are output under %TEMP%\jp1ajs2\backlog. Back up these folders.

When you use the data collection tools in a cluster system, you can collect data by specifying a logical host name. The data collection tools also provide options for limiting the amount of data that is collected. For details on the data collection tools used in Windows, see jajs_log.bat or _04.bat (Windows only) in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

Cautionary note

When you execute the data collection tool, you must open the Command Prompt window as an administrator. If you are not an administrator, UAC will frequently open a confirmation dialog box.

(2) Obtain a dump file

If a STOP error occurs in Windows or if an application crashes, you might have to obtain dump files (a memory dump and a crash dump) and a problem report.

The following describes how to obtain a dump file and a problem report.

(a) How to obtain a dump file

You need to manually obtain a dump file that is output when a problem occurs.

Cautionary note

To output a dump file when a problem occurs, you must specify the settings in advance. For details about how to set the output of dump files, see 7.1.2 Procedure for setting the outputting of a dump file in the JP1/Automatic Job Management System 3 Configuration Guide.

(b) How to obtain a problem report

You can detect problems on a target host and find solutions for each problem. If a JP1/AJS3 process terminates because of an application error, use the following procedure to obtain a problem report.

To obtain a problem report:

In Control Panel, click Action Center.

The Action Center dialog box opens.

Click Maintenance.

The Maintenance menu appears.

Under Check for solutions to problem reports, click View reliability history.

The Reliability Monitor dialog box opens.

Click View all problem reports.

The Problem Reporting dialog box opens.

Double-click the applicable problem.

Details about the problem report appear.

Click Copy to clipboard.

Copy the text into a text editor, and save the file.

Use the problem report text file as data for investigating the failure.

(3) Check the status of processes

In Windows, start Task Manager and open the Processes page. Check the operating status of processes.

For details about JP1/AJS3 processes, see B.2 Processes (for Windows).

(4) Check the operation data

For the problem that has occurred, check the operation data and record it. You need to check the following information:

Details about the operation

Time that the problem occurred

Machine configuration (the version of each OS, host name, JP1/AJS3 - Manager and JP1/AJS3 - Agent configuration)

Whether the problem is reproducible

Name of the user, if any, who logged in from JP1/AJS3 - View

Name of the user who logged in if JP1/AJS3 - Web Console is used and login is performed from the Web GUI or a user application

(5) Collect error information displayed on the screen

Make hard copies of the following:

Windows on the screen when an application error has occurred

Error message dialog box

Displayed information when a details button, if any, is clicked

Information in the Command Prompt window if the problem occurred during the execution of a command

Before making a hard copy of the Command Prompt window, make the following preparations by using Console in Control Panel:

Options page

Select QuickEdit Mode.

Layout page

Enter 500 in Height of Screen Buffer Size.

(6) Collect information about the embedded database

You need the following information if an error occurs while you are using the embedded database:

Data needed to investigate the cause

Information needed to re-create the embedded database environment

The following describes how to collect the above information.

(a) Information needed to investigate the cause

To investigate the cause of an error, you mainly need to collect information about the OS and information about the embedded database. Use OS commands to collect information about the OS. Use embedded database commands to collect information about the embedded database.

If you use the support service to solve problems, you must submit the information listed in the table below. This table describes the type of information needed to investigate the cause of problems and how to collect information for each type of problem. Problems are classified into seven levels, of which level 1 has the highest priority.

Problems are grouped by type as follows:

Performance

The following processing or operation takes too much time:

Startup of the embedded database system (including normal startup, restart, and startup after action has been taken for a failure)

Stopping of the embedded database system (including normal stopping and forced stopping)

Execution of an operation command for the embedded database

No response

A response is not returned when the following processing or operation is performed:

Startup of the embedded database system (including normal startup, restart, and startup after action has been taken for a failure)

Stopping of the embedded database system (including normal stopping and forced stopping)

Execution of an operation command for the embedded database

Abnormal end

One of the following has occurred:

Abnormal termination of the embedded database system

Abnormal termination of an embedded database process

Abnormal termination of an operation command for the embedded database

Table 1‒39: Information needed to investigate the cause of failures and how to collect that information

No.

Component

Information to be collected

Collection method

Performance

No response

Abnormal end

1

OS

Windows event log

Use an OS function (command).

1

1

1

2

CPU usage rate and device status

Use the performance monitor.

3

4

3

3

Embedded database

Information about embedded database failures

Obtain the files under the following folders and store them on a DAT or another storage device:

embedded-database-practical-directory\spool

embedded-database-practical-directory\tmp

An error log file, a command log file, remote command information files, and node switching function information files are output to the above folders.

2

2

2

4

Error log file

The error log is output to a file under embedded-database-practical-directory\spool\errlog.

2

2

2

5

Command log file

The command log is output to a file under embedded-database-practical-directory\spool\cmdlog.

2

2

2

6

Remote command information files

The information about remote commands is output to embedded-database-practical-directory\spool\pdrshs1 and pdrshs2.

2

2

2

7

Node switching function information files

Information about the node switching function is output to embedded-database-practical-directory\spool\pdshs1 and pdshs2.

2

2

2

8

Specification difference absorption library error information files

The error information about the specification difference absorption library is output to embedded-database-practical-directory\UXPLDIR\SPOOL\uxpllog1 and uxpllog2.

2

2

2

9

Embedded database system definitions

Obtain the files under embedded-database-practical-directory\conf and store them on a DAT or another storage device.

4

5

4

10

SQL trace file and error log file

Obtain the output files and store them on a DAT or another storage device. A file name begins with pderr or pdsql.

--

6

5

11

System log file

Use the ajsembdboplog command to unload the system log. Obtain the unload log file and store it on a DAT or another storage device.

6

7

6

Legend:

--: The information need not be collected.

Note

The size of a file increases at a fixed rate if additional data continues to be stored in the file as a result of redirection. Because such a file takes up disk space, instead use bat files, which can be switched and reused after several generations.

(b) Information needed to re-create the embedded database environment

If a problem occurs during operation of the embedded database, you might need to re-create the environment that produced the problem to test whether the problem is reproducible or to investigate the cause of the problem. To enable this procedure, collect the following information needed to re-create the embedded database environment.

conf under the embedded database practical directory (if the user has changed the definition files)

Environment variables related to the embedded database

Data in the embedded database

Use the ajsembdbrorg command to collect the data in the embedded database.

To collect the information needed to re-create the embedded database environment:

Start the embedded database.

Execute the ajsembdbrorg command with the -k unld option specified.

Save conf under the embedded database practical directory in a folder of your choice.

Record the environment variables related to the embedded database.

For details about how to use the ajsembdbrorg command and a description of the command, see 9.2.3 Reorganizing a database in the JP1/Automatic Job Management System 3 Administration Guide.

1.4.2 Collecting data for troubleshooting in UNIX

(1) Execute the data collection tool

JP1/AJS3 provides the data collection tools listed in the following table. Use one of these tools according to the operational requirements.

Table 1‒40: Data collection tools provided by JP1/AJS3 (for UNIX)

Data collection tool

Description

jajs_log

Use this tool if you have not changed the output destinations of log files and other data from the defaults, or if you do not need to collect data other than the data collected by default.

_04

Use this tool if you have changed the output destinations of log files and other data from the defaults, or if you need to collect data other than the data collected by default. You can customize this tool according to the output destinations or the data to be collected.

For details about how to set up the data collection tool (_04), see 16.1 Collecting log data in the JP1/Automatic Job Management System 3 Configuration Guide.

The following shows examples of executing the data collection tool:

When executing jajs_log:

# /opt/jp1ajs2/tools/jajs_log

When executing the file trouble.sh that is created by customizing _04:

# /home/jp1ajs2/trouble.sh

By default, the results of executing the data collection tool are output under /tmp/jp1ajs2/trouble/. Back up these files.

When you use the data collection tools in a cluster system, you can collect data by specifying a logical host name. The data collection tools also provide options for limiting the amount of data that is collected. For details on the data collection tools used in UNIX, see jajs_log or _04 (UNIX only) in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

(2) Obtain the contents of the core file

Obtain the contents of the core file if the file has been output.

The core file is output to one of the following directories:

/opt/jp1ajs2/bin#1

/var/opt/jp1ajs2/database#1

/opt/jp1ajs3web/bin#1

User home directory#2

Current directory in which the command was executed

#1

The data collection tools can be used to collect data.

#2

If the core file was output after connection from JP1/AJS3 - View, this directory is the home directory of the mapped OS user.

If you want to collect only the information needed for analysis of the core file, use the ajs2collectcore command. For details about this command, see ajs2collectcore (UNIX only) in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

Do not limit the core file output setting of the JP1/AJS3 processes when not the setting violates the security policies of the host you are using. If the output of core file is incomplete, you might not be able to identify the cause of the error. For details about the setting, see the documentation for your OS.

(3) Check the status of processes

Use the ps command to check the operating status of processes.

For details about JP1/AJS3 processes, see B.3 Processes (for UNIX).

(4) Check the operation data

For the problem that has occurred, check the operation data and record it. You need to check the following information:

Details about the operation

Time that the problem occurred

Machine configuration (the version of each OS, host name, JP1/AJS3 - Manager and JP1/AJS3 - Agent configuration)

You can check the machine configuration by executing a command. The following table lists the commands you can use to check the machine configuration for each OS.

Table 1‒41: UNIX commands that can be used to check the machine configuration

OS

Command for checking the OS version

Command for checking the size of physical memory on the host

Command for checking the process information and required memory size

HP-UX

/usr/bin/uname -a

/usr/sbin/dmesg

/usr/bin/ps -elf

Solaris

/usr/bin/uname -a

/usr/sbin/prtconf

/usr/bin/ps -elf

AIX

/usr/bin/uname -a

/usr/sbin/bootinfo -r

/usr/bin/ps -elf

Linux

/bin/uname -a

/usr/bin/free

(or

/bin/cat/proc/meminfo)

/bin/ps -elf

Note

The options used in each command in the above table are typical options of the respective OSs. How the options are specified might vary depending on the environment being used. For details, see the documentation for the applicable OS.

Whether the problem is reproducible

Name of the users, if any, who logged in from JP1/AJS3 - View.

Name of the user who logged in if JP1/AJS3 - Web Console is used and login is performed from the Web GUI or a user application

(5) Collect information about the embedded database

You need the following information if an error occurs while you are using the embedded database:

Data needed to investigate the cause

Information needed to re-create the environment of the embedded database

The following describes how to collect the above information.

(a) Information required to investigate the cause

To investigate the cause of an error, you mainly need to collect information about the OS and information about the embedded database. Use OS commands to collect information about the OS. Use the embedded database commands to collect information about the embedded database.

If you use the support service to solve problems, you must submit the information listed in the table below. This table describes the type of information needed to investigate the cause of problems and how to collect information for each type of problem. Problems are classified into seven levels, of which level 1 has the highest priority.

Problems are grouped by type as follows:

Performance

The following processing or operation takes too much time:

Startup of the embedded database system (including normal startup, restart, and startup after action has been taken for a failure)

Stopping of the embedded database system (including normal stopping and forced stopping)

Execution of an operation command for the embedded database

No response

A response is not returned when the following processing or operation is performed:

Startup of the embedded database system (including normal startup, restart, and startup after action has been taken for a failure)

Stopping of the embedded database system (including normal stopping and forced stopping)

Execution of an operation command for the embedded database

Abnormal end

One of the following has occurred:

Abnormal termination of the embedded database system

Abnormal termination of an embedded database process

Abnormal termination of an operation command for the embedded database

Table 1‒42: Information needed to investigate the cause of failures and how to collect that information

No.

Component

Information to be collected

Collection method

Performance

No response

Abnormal end

1

OS

syslog

Use an OS function (command).

1

1

1

2

CPU usage rate and device status

Use an OS command, such as the sar command, to collect the information. For details about the commands, see the documentation for the OS.

3

4

3

3

CPU running status and memory status for processes

Use an OS command, such as the top command, to collect the information. For details about the commands, see the documentation for the OS.

3

4

3

4

Virtual memory

Use an OS command, such as the vmstat command, to collect the information. For details about the commands, see the documentation for the OS.

3

4

3

5

Network status

Use an OS command, such as the netstat command, to collect the information. For details about the commands, see the documentation for the OS.

3

4

3

6

Embedded database

Information about embedded database failures

Obtain the files under the following directories and store them on a DAT or another storage device:

embedded-database-practical-directory/spool

embedded-database-practical-directory/tmp

An error log file and a command log file are output to the above directories.

2

2

2

7

Error log file

The error log is output to a file under embedded-database-practical-directory/spool/errlog.

2

2

2

8

Command log file

The command log is output to a file under embedded-database-practical-directory/spool/cmdlog.

2

2

2

9

Embedded database system definitions

Obtain the files under embedded-database-practical-directory/conf and store them on a DAT or another storage device.

4

5

4

10

SQL trace file and error log file

Obtain the output files and store them on a DAT or another storage device. A file name begins with pderr or pdsql.

--

6

5

11

System log file

Use the ajsembdboplog command to unload the system log. Obtain the unload log file and store it on a DAT or another storage device.

6

7

6

Legend:

--: Information need not be collected.

Note

The size of a file increases at a fixed rate if additional data continues to be stored in the file as a result of redirection. Because such a file takes up disk space, instead create general-purpose shell scripts, which allow files to be switched and reused after several generations.

(b) Information needed to re-create the embedded database environment

If a problem occurs during operation of the embedded database, you might need to re-create the environment that produced the problem to test whether the problem is reproducible or to investigate the cause of the problem. To enable this procedure, collect the following information needed to re-create the embedded database environment.

conf under the embedded database practical directory (if the user has changed the definition files)

Environment variables related to the embedded database

Data in the embedded database

Use the ajsembdbrorg command to collect the data in the embedded database.

To collect the information needed to re-create the embedded database environment:

Start the embedded database.

Execute the ajsembdbrorg command with the -k unld option specified.

Save conf under the embedded database practical directory in a folder of your choice.

Record the environment variables related to the embedded database.

For details about how to use the ajsembdbrorg command and a description of the command, see 9.2.3 Reorganizing a database in the JP1/Automatic Job Management System 3 Administration Guide.

2 Troubleshooting Typical Problems

This chapter describes how to troubleshoot typical problems that might occur while JP1/AJS3 is being used.

2.1 Troubleshooting problems related to setup, service startup, and JP1/AJS3 operation

This section describes how to troubleshoot the problems related to setup, service startup, and JP1/AJS3 operation.

2.1.1 Troubleshooting problems related to setup

(1) JP1/AJS3 setup does not terminate normally

Possible causes are as follows:

If the KAVU5921-E message (Environment settings or the logical host name is invalid.) is output:

JP1/Base might not have been set up, or a logical host name specified during setup for cluster operation might be invalid.

Check the setup procedure and perform it again. During setup for cluster operation, make sure that you specify both the -mh option and a logical host name in the jpqimport command.

If the KAVU5950-E message (The same identifier or object name is already specified. (line:line-number)) is output:

An agent definition ($agent), queue definition ($queue), or exclusive execution resource definition ($res) in the configuration definition file for the execution environment (jpqsetup.conf) for QUEUE jobs and submit jobs might be invalid.

Check the definitions in the configuration definition file for the execution environment for QUEUE jobs and submit jobs. Correct any definitions that need to be corrected, and set up JP1/AJS3 again.

The storage location of the configuration definition file for the execution environment for QUEUE jobs and submit jobs is as follows:

In Windows:

JP1/AJS3-installation-folder\conf\jpqsetup.conf

In UNIX:

/etc/opt/jp1ajs2/conf/jpqsetup.conf

Make sure that the definitions in the configuration definition file for the execution environment for QUEUE jobs and submit jobs meet the following conditions:

A duplicate ID is not defined in $agent $an (n is an agent ID).

The same ID is not shared by def_queue $qn (n is a default queue ID) and $queue $qn (n is a queue ID).

A duplicate ID is not defined in $queue $qn (n is a queue ID).

A duplicate ID is not defined in $res $rn (n is an exclusive execution resource ID).

A duplicate agent name is not defined.

A duplicate queue name is not defined.

A duplicate exclusive execution resource name is not defined.

For details about the definitions in the configuration definition file for the execution environment for QUEUE jobs and submit jobs (jpqsetup.conf), see jpqimport in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

2.1.2 Troubleshooting problems related to service startup

(1) A JP1/AJS3 service has not started

Possible causes are as follows:

If the KAVU5285-E message (There is no the database table, or it is short of the system resources. (reason-location)) is output to the integrated trace log:

If you are using QUEUE jobs or submit jobs, the job execution environment database for QUEUE jobs and submit jobs might not have been created correctly. Use the jpqimport command to create or re-create the job execution environment database for QUEUE jobs and submit jobs. For details about how to create or re-create the database, see 2.11.2 Procedure for re-creating the execution environment database for QUEUE jobs and submit jobs.

If the KAVU5284-E message (It is short of the system resources. (reason-location)) is output to the integrated trace log:

System resources, such as semaphores, required for JP1/AJS3 operation might not be sufficient.

Check the estimate for system resources, make sure that system resources are sufficient, and then restart JP1/AJS3.

If you start a JP1/AJS3 service when memory is insufficient, the KAVU1203-E message (The agent process could not be started. (Reason code: 12)) or the KAVU1204-E message (The manager process could not be started. (Reason code: 12)) might be output to the integrated trace log. If either message is output, reconsider the memory estimate. If any unnecessary applications are running, stop them and restart the JP1/AJS3 service.

When you start a JP1/AJS3 service, the KAVU1203-E message (The agent process could not be started. (Reason code: 0xffffffff)) or the KAVU1204-E message (The manager process could not be started. (Reason code: 0xffffffff)) might be output to the integrated trace log. If either message is output, initialization of the JP1/AJS3 service might have failed. Check the message that is output immediately before this message in the integrated trace log, eliminate the cause of the error, and then restart the JP1/AJS3 service.

When the JP1/AJS3 service is started, the following messages might be output to the integrated trace log:

KAVU1103-I Process monitor (logical-host-name) is already running on the same host.

KAVU4111-E Job queuing control (logical-host-name) or jpqimport command is already running on the same host.

KAVS0500-E Scheduler service has already started.

If any of the messages above are output, the JP1/AJS3 service might have terminated abnormally without stopping JP1/AJS3 processes. In this case, forcibly terminate the remaining JP1/AJS3 processes, and then restart the JP1/AJS3 service as described below.

In Windows:

On both the physical and logical hosts, stop the JP1/AJS3 service, and then use the task manager to check whether JP1/AJS3 processes remain. If JP1/AJS3 processes remain, use the task manager to terminate them forcibly or restart the system.

In UNIX:

If the JP1/AJS3 service on the physical host cannot be started, stop the JP1/AJS3 service on both the physical and logical hosts, and then execute the ps command to check whether JP1/AJS3 processes remain. If JP1/AJS3 processes remain, use the kill command to terminate them forcibly.

If the JP1/AJS3 service on the logical host cannot be started, execute the jajs_killall.cluster command on that logical host to terminate the remaining processes forcibly.

If the KAVS8033-E message (An error occurred during the processing of the connection source restriction function. (code: cause-code, host: host-name) maintenance-information) is output to the integrated trace log:

Reading of the connection permission configuration file might have failed. Confirm the following:

The connection permission configuration file is in the environment settings storage folder.

You have access permission for the connection permission configuration file.

If you try to start the JP1/AJS3 service without entering the IP address of the local host in the manager connection permission configuration file, the KAVU4335-E message (The request sent from the host (connection-source-IP-address) was ignored. (reason, host-name)) is output to the integrated trace log, and the JP1/AJS3 service stops. If this message is output, enter all IP addresses, including the loopback and logical host IP addresses, that might be used as the connection source IP address in the manager connection permission configuration file, and then try to start the JP1/AJS3 service.

(2) A JP1/AJS3 service takes too much time to start

When JP1/AJS3 starts, it requests the authentication server to perform initialization. Even if the authentication server is not running, JP1/AJS3 can still start, but startup takes time.

To prevent a slow startup, before you start JP1/AJS3, start the authentication server.

(3) An error dialog box appears when a JP1/AJS3 service starts

When the cold start of JP1/AJS3 is performed in the mode that initializes a job execution environment database, the error dialog box reporting the failure in starting of the service may be displayed.

The starting of the service has not failed, but rather is taking time for initialization. When the initialization processing is completed, the service will be in the starting state.

2.1.3 Troubleshooting problems related to JP1/AJS3 operation

(1) JP1/AJS3 does not function normally

Check for the following:

JP1/AJS3 is not in a status in which programs can stop, such as the standby, resume, and suspended status.

If you have changed the system time, make sure that you did so by using the procedure described in 7.9.3 Changing the date and time of the system in the JP1/Automatic Job Management System 3 Administration Guide.

(2) An error occurs during communication using IPv6 addresses

Check the items listed below. For details about IPv6 addresses, see 2.3.5 Communication using IPv6 addresses in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

If the JP1/AJS3 service does not start on the manager host, make sure that the manager host is an IPv4/IPv6 host.

The JP1/AJS3 service does not start unless the manager host supports the IPv4 protocol.

If communication using IPv6 addresses is impossible, execute the jp1ping command to check the connection with the destination host. For details, see the JP1/Base User's Guide.

2.2 Troubleshooting problems related to the job execution environment

This section describes how to troubleshoot problems related to the job execution environment.

If an error has occurred on the existing agent host or if an agent host whose configuration definition can be changed is a remote host, take the following action:

Create an execution agent by using the ajsagtadd command. If you are using QUEUE jobs and submit jobs, use the jpqimport command to define the configuration of the execution environment for QUEUE jobs and submit jobs. Then use the jpqagtadd command or the jpqqueopen command to enable the new agent to be used.

If you specify 1 for the AutoCreate environment setting parameter at setup, an alternate execution agent or agent is automatically added when a job is submitted. You also can use the added alternate execution agent or agent to execute the job.

System administrators must specify the automatic definition of agents at setup to be ready for potential emergencies such as an agent host failure. If jobs are to be executed with the automatic definition of agents enabled, the user executing the jobs must be a JP1 user with JP1_JPQ_User permission and JP1_JPQ_Admin permission. Because an error could occur if any of the following conditions exists, make sure beforehand that they will not arise:

Memory becomes insufficient.

Disk space becomes insufficient.

Access to the database fails.

An existing queue is already using the same name.

The number of agents reaches the maximum number that has been defined.

A communication error that disables connection to the manager host occurs.

The event/action control manager process is no longer running.

Access permission for adding an execution agent or an agent has not been granted.

Use the following procedure to set the automatic definition of agents and to execute a job.

To set the automatic definition of agents:

Configure the AutoCreate environment setting parameter.

Specify the value for the AutoCreate environment setting parameter as follows:

"AutoCreate"=dword:1

If a failure occurs on the agent host, perform the following step:

Execute a job.

For JP1/AJS3 - View (for Windows):

Specify the name of the agent host to be automatically defined in Exec-agent in the Define Details dialog box for the job, and register the job for execution.

For the jpqjobsub command:

Specify the name of the agent host to be automatically defined in the -ah option and execute the command.

Cautionary notes

An execution agent is added when a job is registered for execution. If the job fails, the execution agent will remain. If you want to delete the execution agent, use the ajsagtdel command.

An agent is added when a job is submitted. If the job fails, the agent will remain. If you want to delete the agent, use the jpqagtdel command.

If you want to enable the automatic definition of agents while JP1/AJS3 is running, you need to restart JP1/AJS3.

Supplementary note

The setting values for an automatically added execution agent and the setting values for the default queue for an agent are the same as the default setting values specified at setup. The following table lists the default setting values.

Table 2‒1: Setting items and default values for an added execution agent

Setting item for the execution agent

Default value

Execution host name

Same as the execution agent name

Maximum number of concurrently executable jobs

00:00-00:00=5 (maximum of five concurrent jobs, 24 hours a day)

Job transfer restriction status

Enabled

Explanation

None

Use the ajsagtalt command to change the setting values of execution agents. For details about this command, see ajsagtalt in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

Table 2‒2: Setting items and default values for an added agent and the default queue of the agent

Setting item for the default queue

Default value

Period for changing the concurrently executable job limit and the value of the limit

00:00-00:00=5 (maximum of five concurrent jobs, 24 hours a day)

Maximum number of jobs

100

Warning level for the number of jobs

80

Status of the job entrance

open

Status of the job exit

open

Agent to be connected

Local agent host

Priority level of the agent

1

You can use the following commands to change the setting values for an added agent and the default queue of the agent:

jpqagtalt

jpqquealt

jpqqueopen

jpqqueclose

jpqagtlink

jpqagtunlink

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

2.3 Troubleshooting problems related to login to JP1/AJS3 - View

This section describes how to troubleshoot problems that might occur when you attempt to log in to JP1/AJS3 - View.

2.3.1 Troubleshooting problems if you are unable to log in to JP1/AJS3

Possible causes are as follows:

If the KAVV400-E message (Cannot connect to the host (host-name). Detailed information: port-number, IP-address) is output:

Check the following and take appropriate actions.

Check whether the following command can be executed normally:

ping IP-address-or-host-name-of-destination-host

If the destination host does not send a response, the destination host is not running or is unable to connect to the network.

Check whether the JP1/AJS3 service is running on the destination host.

To check the service status:

In Windows:

In the Services dialog box or the Services window, check whether the status of the JP1/AJS3 service is Start. Alternatively, open the Task Manager window, and on the Processes page, check whether the ajsinetd process is running.

In UNIX:

Execute the ps command to check whether the ajsinetd process is running.

Check whether there is a firewall between the source and destination hosts. If there is, check whether packet filtering is configured correctly. To do so, read the explanation in A. List of Port Numbers in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Check whether the port number in the message matches the port number defined in the services file of the destination host.

If the KAVV412-E message (The host name is specified incorrectly.) is output:

Specify settings so that the host name can be resolved.

If the KAVV452-E message (Cannot connect because the number of connections exceeded the maximum.) is output:

Check the following environment setting parameters to determine if the settings for the maximum number of JP1/AJS3 - View connections for logical hosts or for scheduler services are correct:

MAXSESSION environment setting parameter (maximum number of JP1/AJS3 - View connections for logical hosts)

SERVICEMAXSESSION environment setting parameter (maximum number of JP1/AJS3 - View connections for scheduler services)

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

If the KAVV457-E message (The user name or password is invalid.) is output:

Check whether the JP1 user name and password you entered for login are correct.

Check whether the JP1 user name and password you entered for login are registered correctly on the authentication server for the connection destination.

If the primary authentication server is blocked in an environment where a secondary authentication server is installed, check whether the user settings on the primary authentication server are identical with those on the secondary authentication server. It is possible that if you changed your password, the new password might not have been registered on the secondary authentication server and is registered only on the primary authentication server.

If the KAVV458-E message (User mapping failed. The user was not associated with an OS user at the connection destination.) is output:

Execute the jbsgetumap command on the destination host, check the standard output data, and check the points discussed below. For details about the jbsgetumap command, see the JP1/Base User's Guide.

If the JP1 user name that you entered when you logged in to JP1/AJS3 - Manager from JP1/AJS3 - View is not directed to the standard output, the user mapping settings on the destination host are invalid (no mapping is completed between JP1 users and OS users).

If anything other than * is output as the server host name for the JP1 user name, check whether the server host name matches the name of the local host.

Also see the explanation of user mapping in the JP1/Base User's Guide, and make sure that the name of the local host is specified correctly.

Make sure that the OS user name output to the standard output is the name of an existing OS user.

Also check the following if the destination host runs on Windows:

- Make sure that the OS user name to be mapped to the JP1 user name has not been changed in the JP1/Base password management settings.

- Make sure that the password of any mapped OS user has not been changed in the OS.

- Make sure that the accounts of mapped OS users have not been locked out.

- Make sure that the accounts of mapped OS users have permissions that allow local logon.

If the KAVV459-E message (An error occurred in JP1/Base at the connection destination.) is output:

Check the following:

Make sure that the authentication server host name specified on the destination host is correct.

If the authentication server host name is correct, make sure that an authentication server is running on that host.

Note that if the local host is specified as the authentication server in a UNIX environment, you must set up JP1/Base so that JP1/Base starts as the authentication server. For details, see the explanation of the authentication server settings in the JP1/Base User's Guide.

If the KAVV3102-E message (Connection denied.) is output:

Check the KAVS8040-E message that is output to the integrated trace log on the connection destination manager host. If necessary, add any required IP addresses in the manager connection permission configuration file, and then execute the jajs_pmtcon command.

If the KAVV3103-E message (An error occurred while processing was being performed for SSL communication.) is output:

This message is output if communication with the connection destination manager host is encrypted. Make sure that the route certificate for verifying the server certificate on the connection destination manager host has been deployed correctly on the JP1/AJS3 - View host. Also make sure that the communication encryption settings (whether to enable or disable encryption) specified in JP1/AJS3 - View and JP1/AJS3 - Manager are the same.

2.3.2 Troubleshooting problems if the destination host is disconnected immediately after login to JP1/AJS3

Immediately after you log in from JP1/AJS3 - View to JP1/AJS3 - Manager, one of the following messages might be output, and then the connection might be closed: KAVV401-E (The data to the connection destination could not be sent or received.) or KAVV3103-E (An error occurred while processing was being performed for SSL communication. (maintenance-information)). In such a case, take the appropriate action according to the message that is output. For details about the KAVV401-E and KAVV3103-E messages, see 6. Messages beginning with KAVV (Messages about JP1/AJS3 - View) in the manual JP1/Automatic Job Management System 3 Messages.

2.4 Troubleshooting problems related to the Web GUI

This section describes how to troubleshoot problems related to the Web GUI.

2.4.1 If a screen is not displayed or is corrupted

Possible causes are as follows:

The OS or web browser might not be supported. Check the version of the OS or web browser.

If the zoom rate of the web browser is not 100%, the displayed information might be corrupted. Make sure that the zoom rate is 100%.

If the text size of the OS is not 100%, the displayed information might be corrupted. Make sure that the text size is 100%.

If the pop-up blocker is enabled in your web browser, the display of some Web GUI screens and dialog boxes might be blocked. In the pop-up block settings in your web browser, add the address of the Web Console server to the allowed sites, to release the server from the pop-up block.

2.4.2 If the login window does not appear when SSL communication is used

HTTPS connections use SSL communication and HTTP connections do not use SSL communication. If the login window does not appear when an HTTPS connection is used although the login window appears when an HTTP connection is used, possible causes are as follows:

SSL communication might be disabled in the web browser. Make sure that SSL communication is enabled in the web browser.

The private keys for the server and server certificate might not match. Re-create a server private key and certificate signing request (CSR) to obtain the server certificate again, and then restart the JP1/AJS3 HTTP Server service.

2.4.3 If an error occurs when a window is opened or an operation is performed immediately after upgrade installation

The data stored in the cache for the web browser before the upgrade installation might still exist. Use the web browser to delete the cached temporary files.

2.5 Troubleshooting problems if processing of a jobnet with a start condition is delayed

In some cases, when a large number of events occur unexpectedly for a specific jobnet with a start condition, processing is delayed because large quantities of unprocessed data are stored on the event/action control manager. For example, an operation for an event job is delayed or an event job does not end quickly even if an event that matches the specified condition occurs.

The following shows the sequence from when a problem occurs in the system until the operator recognizes the problem:

A large number of events occur unexpectedly for a specific jobnet with a start condition.

The manager host slows down because there is too much data to be processed, causing other event jobs to be held in queues or other problems to occur.

The event/action control manager outputs the KAVT0333-W message to the integrated trace log.

You receive the message output in step 3, and notice that a problem has occurred on the event/action control manager.

In such cases, you can end the delay by deleting the information contained in the event/action control manager.

When restoring the operating status, you can check information by using the Web GUI (Management Portal) or commands. The following sections describe these two methods.

2.5.1 Troubleshooting starting by checking information by using the Web GUI (Management Portal)

The following shows the troubleshooting procedure when the Web GUI (Management Portal) is used to check the information:

In the Event Job Retention Details dialog box of the Web GUI (Management Portal), check the following information:

Name of a jobnet with start conditions in which a large number of events occurred

Execution host name

For details about the Event Job Retention Details dialog box, see 16.2.7 Event Job Retention Details dialog box in the JP1/Automatic Job Management System 3 Operator's Guide.

Forcibly terminate the jobnet with a start condition identified in step 1.

If the termination is successful, troubleshooting ends here.

For details about how to forcibly terminate a jobnet with start conditions, see 8.1.1 Stopping a jobnet that is monitoring start conditions in the JP1/Automatic Job Management System 3 Administration Guide.

If you could not stop the jobnet in step 2 or could not identify the jobnet name in step 1 assume that it will be difficult to restore operational status while JP1/AJS3 is running, and stop the scheduler service.

For details on how to stop a scheduler service, see 7.5.2 Stopping the scheduler service in the JP1/Automatic Job Management System 3 Administration Guide.

On the agent with the problem, execute the jpomanevreset command for the scheduler service you stopped in step 3, and restore the status of the event/action control manager.

For details about jpomanevreset command, see jpomanevreset in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

When you executed the jpomanevreset command, if you specified an option that retains event job executions and start conditions as is, correct the problem that caused a large number of unexpected events to occur in a specific jobnet with start conditions on the agent host.

Start the scheduler service you stopped in step 3.

For details about how to start a scheduler service, see 7.5.1 Starting the scheduler service in the JP1/Automatic Job Management System 3 Administration Guide.

2.5.2 Troubleshooting starting by checking information by using commands

The following shows the troubleshooting procedure when commands are used to check the information:

Execute the jpomanevshow command to obtain information about the agents that frequently send data, and the jobnet with a start condition.

Use the information you obtain in step 1 (unit ID) and either of the following commands to identify the name of the jobnet related to the problem.

ajsname command

This command outputs the unit name to the standard output file.

jpomanjobshow command

This command outputs a list of event jobs being executed on the manager to the standard output file.

Forcibly terminate the jobnet with a start condition identified in step 2.

If the termination is successful, troubleshooting ends here.

For details about how to forcibly terminate a jobnet with start conditions, see 8.1.1 Stopping a jobnet that is monitoring start conditions in the JP1/Automatic Job Management System 3 Administration Guide.

If you could not stop the jobnet in step 3 or could not identify the jobnet name in step 2, assume that it will be difficult to restore operational status while JP1/AJS3 is running, and stop the scheduler service.

For details on how to stop a scheduler service, see 7.5.2 Stopping the scheduler service in the JP1/Automatic Job Management System 3 Administration Guide.

On the agent with the problem, execute the jpomanevreset command for the scheduler service you stopped in step 4, and restore the status of the event/action control manager.

When you executed the jpomanevreset command, if you specified an option that retains event job executions and start conditions as is, correct the problem that caused a large number of unexpected events to occur in a specific jobnet with start conditions on the agent host.

Start the scheduler service you stopped in step 4.

For details about how to start a scheduler service, see 7.5.1 Starting the scheduler service in the JP1/Automatic Job Management System 3 Administration Guide.

For details about the commands, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

2.6 Troubleshooting problems related to jobs and jobnets

This section describes how to troubleshoot problems related to jobs and jobnets.

2.6.1 Troubleshooting problems related to the registration of jobs and jobnets for execution

If an error occurs during registration for execution, the following schedule rules might be specified for the root jobnet. Do not specify these schedule rules.

A past date is specified as a start date, and no processing cycle is set in the schedule rule.

An invalid date (for example, 2/30) is specified as a start date in the schedule rule.

A closed day is specified as a start date in the schedule rule, but no closed day is specified in the calendar definition to be used.

A closed day is specified as a start date in the schedule rule, but Do not execute is specified as the substitute schedule method for closed day jobs.

Do not execute is specified as the substitute schedule method for closed day jobs in the schedule rule, but closed days are specified in all the calendar definitions to be used.

The same schedule rule as that for a jobnet specified in the exclusive schedule is set. (All planned executions must be in the exclusive schedule.)

A definition that disables calculation of the same execution date from the schedule rule number that corresponds to a schedule rule number of an upper level jobnet is created.

If an invalid unit, such as one that does not exist, is specified in a job group or exclusive schedule that references the calendar, the status of the jobnet becomes shutdown status.

For a schedule that is planned to be executed soon, the schedule is changed dynamically according to the status and time so that the planned execution might not be carried out as scheduled.

If any of the above schedules is set in a nested jobnet, the jobnet is handled as Not sched. to exe., and execution does not occur until the status is temporarily changed.

2.6.2 Troubleshooting problems related to standard jobs, HTTP connection jobs, action jobs, and custom jobs

This subsection describes how to troubleshoot problems that might occur when you execute standard jobs, HTTP connection jobs, action jobs, and custom jobs.

(1) Executing a standard job, action job, or custom job results in a startup failure

Possible causes are as follows:

If a file or directory on a disk mounted on a file system that is distributed over a network (such as an NFS) is used in the definition parameters:

Do not use disks mounted on file systems that are distributed over a network (such as an NFS) to store the files and directories to be created or referenced by JP1/AJS3. If you do use such disks, JP1/AJS3 might not work properly. However, files and directories that are used only for the definition parameters of the following jobs can be stored on disks mounted on file systems that are distributed over a network (such as an NFS):

Execution file name for the job

Standard output file name for the job

Standard error output file name for the job

Environment file name for the job

File to transfer name for the job

Destination file name for the job

Work path for the job

Work directory for job environment settings

Home directory of the execution OS user

If the network cannot be accessed while you are using the above definition parameters, job execution might fail or be delayed.

For queueless jobs (PC jobs, Unix jobs, and actions jobs for which Queueless Agent is specified in Exec. Service), host names specified in Exec-agent are case sensitive. Make sure that the host names specified on the hosts that execute queueless jobs are correctly specified in Exec-agent.

If the KAVU4571-W message (The user mapping (JP1-user-name) at the agent (agent-host-name) failed.) is output to the integrated trace log:

User mapping might not be specified correctly. For example, user mapping might not be specified on the host that executes a job, or the specified JP1 user or execution user might not be registered.

Check the user mapping settings, and re-execute (re-register) the job.

If the KAVU4580-W message (The user (user-name) does not have administrator permission at the agent (agent-host-name).) is output to the integrated trace log (for UNIX only):

An execution user without superuser privilege might have attempted to execute a job with job execution priority 4 or 5.

To execute a job with job execution priority 4 of 5 in UNIX, the execution user must have superuser privilege (root user).

In Windows, however, the execution user does not need to have administrator privileges to execute a job with job execution priority 4 or 5.

If the KAVU4512-W message (The specified queue (queue-name) does not exist.) or the KAVU4511-W message (The specified agent (agent-host-name) does not exist.) is output to the integrated trace log:

The name of the specified execution host or queue for the QUEUE job or submit job might be invalid.

Check whether the execution environment has been created correctly for the QUEUE job or submit job.

To check, execute the jpqexport command and output the agent name (job execution host name) or queue name that is currently defined to a file. Agent names are not case sensitive. Queue names are case sensitive.

After checking the agent name and the queue name, re-execute (re-register) the QUEUE job or submit job.

If the KAVU4514-W message (The job cannot be registered because the entrance to queue (queue-name) is closed.) is output to the integrated trace log:

The queue might not be ready to accept the QUEUE job or submit job.

Execute the jpqqueshow command to check the status (ENTRYSTATUS) of the job entrance of the queue. To check the status of the job entrance of the default queue for an agent, specify the agent host name with the -ah option specified. To check the status of the job entrance of other queues, specify the queue name with the -q option specified.

If the job entrance is closed (when ENTRYSTATUS:CLOSE is specified), execute the jpqqueopen command to open the job entrance.

If the KAVU4515-W message (The job cannot be registered because the queue (queue-name) reached the maximum number of jobs (maximum-number).) is output to the integrated trace log:

The number of QUEUE jobs or submit jobs might have reached the maximum number of queuing jobs and running jobs.

Execute the jpqqueshow command to check the maximum number (MAXQUEUE) for QUEUE jobs or submit jobs. During operation, make sure that the number of QUEUE jobs or submit jobs stays below the maximum number.

To change the maximum value for QUEUE jobs and submit jobs, use either the jpqquealt command to change the maximum number of jobs in a queue, or the jpqimport command to re-create the job execution environment database for QUEUE jobs and submit jobs. For details about how to re-create the database, see 2.11.2 Procedure for re-creating the execution environment database for QUEUE jobs and submit jobs.

If the KAVU4520-W message (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).) is output to the integrated trace log:

The number of QUEUE jobs or submit jobs might have reached the maximum number of queuing jobs and running jobs in the system.

The maximum number of jobs allowed in the system is specified in the MaximumContentJob environment setting parameter.

During operation, make sure that the number of QUEUE jobs and submit jobs stays below the maximum number of jobs allowed in the system.

If you want to change the maximum number of jobs allowed in the system, see the Release Notes, and specify an appropriate value.

If the KAVU3586-W message (The privilege for service account was not set.) or the KAVU3571-W message (User mapping (JP1-user-name) failed.) is output to the integrated trace log (for Windows only):

The JP1/AJS3 service account might not be set up as a user account. In addition, the user account might not have the necessary permissions.

Set up the JP1/AJS3 service account as a user account and grant the necessary permissions. For details about setting up accounts for JP1/AJS3 services, see 4.2 JP1/AJS3 service settings in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide. If you change the JP1/AJS3 service account, restart the JP1/AJS3 services.

If the KAVU4581-W message (The execution file (file-name) at the agent (agent-host-name) is not an executable file.) is output to the integrated trace log:

The application file name associated with the file type might contain a space character.

In Windows Explorer, click View and then Options to display the Options dialog box. On the File Types page of the dialog box, check the associated application. If the application name contains a space character, enclose the file name in double quotation marks (").

If the KAVU4531-W message (The agent (agent-host-name) host name might be invalid.) is output to the integrated trace log:

The agent host name might be invalid, or resolution of the agent host name to an IP address might not be possible.

Check whether the agent host name is valid. Also check the hosts file to make sure that the host name can be resolved to an IP address.

If the KAVU4530-W message (The agent (agent-host-name) might have stopped, or an obstacle might have occurred.) is output to the integrated trace log:

The JP1/AJS3 service on the agent (job execution host) or the computer itself might have stopped, or a network error might have occurred.

Check the status of the agent, JP1/AJS3 service, and network.

If the KAVU3521-W message (The job (job-number) process could not be generated. (reason code:reason-code)) is output to the integrated trace log:

An attempt to start the job might have failed because of insufficient memory.

Check the memory size estimate.

If the KAVU4597-W message (A missed job at the agent (agent-host-name) was forcibly terminated.) or the KAVU4538-W message (The status of job (job-number) missed at the agent (agent-host-name) was changed to recovered (status).) is output to the integrated trace log:

The above messages are output in the following cases:

When a job is being executed on JP1/AJS3 - Manager, the JP1/AJS3 - Manager host or a JP1/AJS3 process goes down, after which JP1/AJS3 - Manager is restarted.

When a job is being executed on a remote execution host (agent), the execution host or a JP1/AJS3 process goes down, after which JP1/AJS3 on the execution host is restarted.

When a job is being executed on a remote execution host (agent), the JP1/AJS3 - Manager host and then the execution host go down, after which the JP1/AJS3 - Manager host and the execution host are restarted.

For QUEUE jobs and submit jobs, if a job is forcibly ended without its end status being reflected in the job execution environment database, the end status of the job becomes unknown, and a KAVU4597-W message or a KAVU4538-W message is output.

Register the applicable jobnet or job for re-execution as needed.

If the KAVU4546-W message (The PATH variable could not be acquired at the agent (agent-host-name).) is output to the integrated trace log (for UNIX only):

Check the login script of the execution OS user for any condition that causes processing to end prematurely.

If the login script contains any entries unnecessary for job execution by JP1/AJS3, either delete them, or skip them by appropriately specifying the JP1JobID environment variable.

If the KAVU5282-W message (A system call error occurred during a database process. (module:reason-location[reason-code],reason code:reason-code)) is output to the integrated trace log:

The number of job information items regarding QUEUE jobs and submit jobs might have exceeded 200,000.

Use the following procedure to change the number of days for retaining job information, and re-create the job execution environment database for QUEUE jobs and submit jobs.

To re-create the job execution environment database:

Change the number of days for retaining job information.

Specify a number of days so that the number of job information items will not exceed 200,000.

Use the jajs_config command to specify the PreserveTerm environment setting parameter.

Use the jpqimport command to re-create the job execution environment database for QUEUE jobs and submit jobs.

If the KAVU3577-W message (A system call (function-name) error occurred in a job execution process. (reason code:reason-code)) is output to the integrated trace log (for UNIX only):

The directory specified in the work path for job execution might not be treated as the current directory. The directory specified in the work path is the directory that operates as the current directory.

If the KAVU4548-W message (The temporary file at the agent (agent-host-name) cannot be accessed.) or the KAVU4583-W message (The execution shell is missing at the agent (agent-host-name).) is output to the integrated trace log, the OS user mapped to the JP1 user might not be able to log in to the OS. If a message is output, check the following:

If the KAVU4548-W message is output

Check whether the home directory specified in /etc/passwd exists.

If the KAVU4583-W message is output

Check whether the login shell specified in /etc/passwd exists.

If the KAVU7533-E message (The execution user (user-name) mapped from JP1 user (host name = host-name,JP1 user = user-name) is invalid. (Reason code: 1326)) is output to the integrated trace log, in Windows, the access token of the OS user who executed the job might not have been obtained. Possible causes are as follows:

The access token could not be obtained because of a temporary error in the Win32API functions.

If the user who executed the job is a domain user, the domain user could not log on temporarily because the domain controller was not running or for another reason. During JP1/AJS3 operation, an access token is obtained when a job is executed. However, JP1/AJS3 is not aware of the number and status of domain controllers at that point. You must therefore be careful when you restart a domain controller while a job is being executed.

To avoid the above situations that temporarily prevent an access token from being obtained, you can specify settings to enable the reuse of access tokens. Doing so reduces the number of times required to obtain access tokens to a minimum and the number of such errors. For details, see 6.2.17 Reusing access tokens for job execution in the JP1/Automatic Job Management System 3 Configuration Guide.

Also note that when you reuse access tokens, the method of using the desktop heap changes.

Thoroughly verify operation of the entire system to avoid any problems. For details, see 6.2.17(3) Notes in the JP1/Automatic Job Management System 3 Configuration Guide. For details about access tokens, see 5.4.1 User account for job execution in the manual JP1/Automatic Job Management System 3 Overview as well.

If the KAVU4721-E message (The request was rejected. (job-number)) is output to the integrated trace log:

Check the KAVU3296-E message that is output to the integrated trace log on the host where the job was to be executed. If necessary, add any required IP addresses in the agent connection permission configuration file, and then execute the jajs_pmtcon command.

If the KAVS8029-E message (The request was rejected. (unit-name)) is output to the integrated trace log:

Check the KAVS8039-E message that is output to the integrated trace log on the host where the job was to be executed. If necessary, add any required IP addresses in the agent connection permission configuration file, and then execute the jajs_pmtcon command.

(2) Executing an HTTP connection job results in a startup failure

Possible causes are as follows:

A directory mounted on NFS or a similar file system connected to a network is used in the following definition parameters:

Standard output file name for the job

Standard error output file name for the job

Home directory of the execution OS user

A job might be unable to start or execution of a job might be delayed if the job cannot access a network.

If the KAVU4571-W message (The user mapping (JP1-user-name) at the agent (agent-host-name) failed.) is output to the integrated trace log:

User mapping might not be specified correctly. For example, user mapping might not be specified on the host that executes a job, or the specified JP1 user or execution user might not be registered.

Check the user mapping settings, and re-execute (re-register) the job.

If the KAVU4580-W message (The user (user-name) does not have administrator permission at the agent (agent-host-name).) is output to the integrated trace log (for Linux only):

An execution user without superuser privilege might have attempted to execute a job with job execution priority 4 or 5.

To execute a job with job execution priority 4 of 5 in Linux, the execution user must have superuser privilege (root user).

In Windows, however, the execution user does not need to have administrator privileges to execute a job with job execution priority 4 or 5.

If the KAVU3586-W message (The privilege for service account was not set.) or the KAVU3571-W message (User mapping (JP1-user-name) failed.) is output to the integrated trace log (for Windows only):

The JP1/AJS3 service account might not be set up as a user account. In addition, the user account might not have the necessary permissions.

Set up the JP1/AJS3 service account as a user account and grant the necessary permissions. For details about setting up accounts for JP1/AJS3 services, see 4.2 JP1/AJS3 service settings in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide. If you change the JP1/AJS3 service account, restart the JP1/AJS3 services.

If the KAVU4531-W message (The agent (agent-host-name) host name might be invalid.) is output to the integrated trace log:

The agent host name might be invalid, or resolution of the agent host name to an IP address might not be possible.

Check whether the agent host name is valid. Also check the hosts file to make sure that the host name can be resolved to an IP address.

If the KAVU4530-W message (The agent (agent-host-name) might have stopped, or an obstacle might have occurred.) is output to the integrated trace log:

The JP1/AJS3 service on the agent (job execution host) or the computer itself might have stopped, or a network error might have occurred.

Check the status of the agent, JP1/AJS3 service, and network.

If the KAVU3521-W message (The job (job-number) process could not be generated. (reason code:reason-code)) is output to the integrated trace log:

An attempt to start the job might have failed because of insufficient memory.

Check the memory size estimate.

If the KAVU4597-W message (A missed job at the agent (agent-host-name) was forcibly terminated.) or the KAVU4538-W message (The status of job (job-number) missed at the agent (agent-host-name) was changed to recovered (status).) is output to the integrated trace log:

The above messages are output in the following cases:

When a job is being executed on JP1/AJS3 - Manager, the JP1/AJS3 - Manager host or a JP1/AJS3 process goes down, after which JP1/AJS3 - Manager is restarted.

When a job is being executed on a remote execution host (agent), the execution host or a JP1/AJS3 process goes down, after which JP1/AJS3 on the execution host is restarted.

When a job is being executed on a remote execution host (agent), the JP1/AJS3 - Manager host and then the execution host go down, after which the JP1/AJS3 - Manager host and the execution host are restarted.

Register the applicable jobnet or job for re-execution as needed.

If the KAVU4546-W message (The PATH variable could not be acquired at the agent (agent-host-name).) is output to the integrated trace log (for Linux only):

Check the login script of the execution OS user for any condition that causes processing to end prematurely.

If the login script contains any entries unnecessary for job execution by JP1/AJS3, either delete them, or skip them by appropriately specifying the JP1JobID environment variable.

If the KAVU4548-W message (The temporary file at the agent (agent-host-name) cannot be accessed.) or the KAVU4583-W message (The execution shell is missing at the agent (agent-host-name).) is output to the integrated trace log, the OS user mapped to the JP1 user might not be able to log in to the OS. If a message is output, check the following:

If the KAVU4548-W message is output

Check whether the home directory specified in /etc/passwd exists.

If the KAVU4583-W message is output

Check whether the login shell specified in /etc/passwd exists.

If the KAVU7533-E message (The execution user (user-name) mapped from JP1 user (host name = host-name,JP1 user = user-name) is invalid. (Reason code: 1326)) is output to the integrated trace log, in Windows, the access token of the OS user who executed the job might not have been obtained. Possible causes are as follows:

The access token could not be obtained because of a temporary error in the Win32API functions.

If the user who executed the job is a domain user, the domain user could not log on temporarily because the domain controller was not running or for another reason. During JP1/AJS3 operation, an access token is obtained when a job is executed. However, JP1/AJS3 is not aware of the number and status of domain controllers at that point. You must therefore be careful when you restart a domain controller while a job is being executed.

To avoid the above situations that temporarily prevent an access token from being obtained, you can specify settings to enable the reuse of access tokens. Doing so reduces the number of times required to obtain access tokens to a minimum and the number of such errors. For details, see 6.2.17 Reusing access tokens for job execution in the JP1/Automatic Job Management System 3 Configuration Guide.

Also note that when you reuse access tokens, the method of using the desktop heap changes.

Thoroughly verify operation of the entire system to avoid any problems. For details, see 6.2.17(3) Notes in the JP1/Automatic Job Management System 3 Configuration Guide. For details about access tokens, see 5.4.1 User account for job execution in the manual JP1/Automatic Job Management System 3 Overview as well.

If the KAVU4721-E message (The request was rejected. (job-number)) is output to the integrated trace log:

Check the KAVU3296-E message that is output to the integrated trace log on the host where the job was to be executed. If necessary, add any required IP addresses in the agent connection permission configuration file, and then execute the jajs_pmtcon command.

If the KAVS8029-E message (The request was rejected. (unit-name)) is output to the integrated trace log:

Check the KAVS8039-E message that is output to the integrated trace log on the host where the job was to be executed. If necessary, add any required IP addresses in the agent connection permission configuration file, and then execute the jajs_pmtcon command.

(3) Executing a standard job, action job, or custom job results in an abnormal end

Possible causes are as follows:

An environment variable used in executing the job might be invalid. There are two types of environment variables: those that are defined directly in a job and those that are specified in an environment variable file.

To check whether inappropriate environment variables are being used, see 1.4 Environment variables in the manual JP1/Automatic Job Management System 3 Command Reference.

A file name specified in a job might be invalid.

Check the following regarding file names:

Each job execution file name (execution file name for Windows and script file name for UNIX), environment variable file name, standard input file name, standard output file name, and standard error output file name must be unique. (An exception is that the standard output file name and the standard error output file name can have the same name).

The standard output file name and the standard error output file name must be different for jobs that are executed concurrently.

The standard output or the standard error output might have been competing for use of the redirect destination during processing of the executable file specified in a job. Check the following:

Make sure the standard output file or the standard error output file specified in the job is different from the redirect destination file for the standard output or the standard error output specified in the executable file.

If you concurrently execute multiple jobs with executable files specified, make sure different file names are specified as the redirect destinations for the standard output and the standard error output in the executable file.

The settings in /etc/logingroup might be invalid (when the execution host is HP-UX).

If an OS user who executes a job belongs to multiple groups and needs to access multiple groups, login groups must be specified in /etc/logingroup. If login groups are not specified in /etc/logingroup, only those group IDs defined in /etc/passwd are valid. Any group IDs not defined in /etc/passwd are invalid. For example, if an OS user named jp1user belongs to groups A and B (group A is defined in /etc/passwd and group B is not defined in /etc/passwd), the OS user cannot reference the files of group B. To enable access to multiple groups, copy the group definition in /etc/group to /etc/logingroup, or create a symbolic link between /etc/group and /etc/logingroup. For details, see the documentation for the OS.

The following commands might not operate correctly, as described below (when the execution host is Windows):

When a job containing the net use command is executed, an attempt to disconnect a network folder fails.

Two measures are available for handling this problem.

The first is to specify the net use command in a single batch file that is used to connect and disconnect network folders.

The second is to change the account for the applicable JP1/AJS3 service to a user account and execute the job containing the net use command with the new account for the JP1/AJS3 service (user account). For details about how to change the account for a JP1/AJS3 service to a user account, also see 4.2.3 Changing the JP1/AJS3 service settings (Windows only) in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

When a job containing the ftp command is executed, standard output data is not output.

Two measures are available for handling this problem.

The first is to specify the -v option in the ftp command.

The second is to specify CON as the standard input file name, standard output file name, and standard error output file name when you define the job. If you specify CON for these file names, data is output to the standard output file and standard error output file. However, the standard error output messages related to the job are not output to JP1/AJS3 - View when you use JP1/AJS3 - View to display the detailed execution results. In addition, you cannot use the jpqjobget command to obtain information from the standard output file and the standard error output file.

Cautionary note

If the same problem occurs when you use a command other than the ftp command, specify CON as described above.

When a job containing a command other than those described above is executed, the job does not run correctly.

JP1/AJS3 jobs are executed as services that are independent of the logon session of OS users so that JP1/AJS3 jobs can be executed even if an OS user has not logged on to Windows. Accordingly, the execution results of jobs might not be the same when JP1/AJS3 is used to execute the jobs and when the Command Prompt window is used to execute the jobs.

You can use the AT command or Task Scheduler provided by Windows to check whether jobs are executed correctly from a Windows service (at this time, the Task Scheduler service of Windows starts the jobs). If a job does not run correctly from a Windows service, it will not run correctly from a JP1/AJS3 service, either. In such cases, you must check the commands and programs used in the job, and correct them if necessary.

Note that the Task Scheduler service, and the JP1/AJS3 service generate job processes in slightly different ways. Therefore, even if a job does not run correctly when JP1/AJS3 is used, it might run correctly when a Windows service is used. For example, JP1/AJS3 might not be able to reference the information about the printers and applications specified in the logon session of an OS user if the information is stored in the registry. This is so even if the account of the OS user is specified for the execution user of the job, (sometimes with result the printing to a printer from the job, or application startup is not done correctly). In such cases, the OS user who executes the job must log on to Windows (execution host of JP1/AJS3) and execute the job.

Alternatively, specify the necessary settings as described in 6.2.16 Executing a job that requires a user profile in the JP1/Automatic Job Management System 3 Configuration Guide.

If you want to grant only users of the local server the access permissions for execution users, specify OS users in server-name\user-name format.

Job startup might fail because memory is insufficient.

Check the memory size estimate.

If the following messages are output to the integrated trace log (for Windows only):

KAVU4254-E message (It cannot access the database (logical-host-name). (reason code:reason-code))

KAVU5287-E message (The database table is locked. (reason-location))

These messages appear if the ISAM files for the job execution environment cannot be accessed when a QUEUE job or a submit job is executed. Make sure that the following are not executed simultaneously:

Data collection tool of JP1/AJS3

A command that operates on the ISAM database, such as a command that verifies or condenses the ISAM database for JP1/Base or JP1/AJS3 (except for the jpqdbcond -L command)

A backup program

Additionally to the above, the same problem might occur if a program is executed to open the database file for the job execution environment for QUEUE jobs and submit jobs in exclusive mode or in share mode in which only reading of files is shared. When you schedule this type of task, schedule it so that it will not be executed while jobs are being run.

If the following messages are output to the integrated trace log (for UNIX only):

KAVU4547-W message (You are not authorized to access the temporary file at the agent (agent-host-name).)

KAVU4560-W message (You lack access permission for the standard output file (file-name) at the agent (agent-host-name).)

KAVU4563-W message (You lack access permission for the standard error output file (file-name) at the agent (agent-host-name).)

If the KAVU4547-W message is output, the owner group of the work directory might be the secondary group of the job execution user, and the permission for the work directory might be 770 (the work directory is specified in the WorkPath environment setting parameter in the [JP1_DEFAULT\JP1NBQAGENT\Process] definition key).

If the KAVU4560-W or KAVU4563-W message is output, the owner group of the directory containing the specified file (file-name in the messages) might be the secondary group of the job execution user, and the permission for the directory might be 770.

Take one of the following actions:

If the KAVU4547-W message is output, change the access permission for the work directory so that the secondary group can access the directory.

Change the permission for the directory containing the specified file to one that allows the secondary group to access the directory. Also, change the permission for the specified file to one that allows the secondary group to read and write to the file.

Change the owner group of the directory and the specified file from the secondary group to the primary group of the job execution user.

Enable the necessary options as specified 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.

If the KAVU4551-W message (You are not authorized to access the execution file (file-name) at the agent (agent-host-name).) is output to the integrated trace log (for UNIX only):

The owner group of the directory containing the specified execution file (file-name in the message) might be the secondary group of the job execution user and the permission might be 770.

Take one of the following actions:

Change the permission for the directory containing the specified file to 771, and change the permission for the specified file to 774.

Change the owner group of the directory and the specified file from the secondary group to the primary group of the job execution user.

Enable the necessary options as 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.

Sometimes, the execution file name of a job cannot be correctly determined.

In UNIX:

When $0 (script file name) is referenced in a script file, $0 might be replaced by a script file name beginning with JPQ_EXEC_ instead of the script file name specified in the job definition.

This file name is the name of a script file that is temporarily created by JP1/AJS3 in the following cases (the script file is created in the work path that is used when the job is executed):

You execute a job containing the command that is specified in Command statement on the Definition page in the Define Details - [UNIX Job] dialog box of JP1/AJS3 - View.

You execute a script file whose name does not begin with #! shell-name in Script file name on the Definition page in the Define Details - [UNIX Job] dialog box of JP1/AJS3 - View#.

You execute a script file whose name does not begin with #! shell-name in the -sc option of the jpqjobsub command.

#

If the name of the execution shell is not written on the first line of the script file specified in Script file name, JP1/AJS3 creates a temporary script file with the execution shell name added to the first line, and executes the file as a job.

If you specify a command in Command statement and a script file name in Script file name at the same time, the specified command and script file name are merged into a temporary file in the sequence command and then script file name. Therefore, when a command is specified in Command statement, a temporary file is created regardless of whether an execution shell name is written in a script file (a temporary file is also created if a tab or space character is specified in Command statement).

To avoid creating temporary script files, define jobs so that none of the above conditions arise.

In Windows:

When the first argument (%0 in a batch file) in an execution file for Windows is referenced, the first argument might not be replaced by the execution file name specified in the job definition. This is because execution file names are converted to short file names in 8.3 format when JP1/AJS3 starts jobs.

To start a job without converting the execution file name in 8.3 format, see 6.2.15 Executing a job by using a long file name in the JP1/Automatic Job Management System 3 Configuration Guide.

If the following message is output to the integrated trace log (for Windows only):

KAVU7533-E message (The execution user (user-name) mapped from JP1 user (host name = host-name, JP1 user name = user-name) is invalid. (reason code: 1792).)

If you execute a job with a user account that is different from the account for the JP1/AJS3 service and the Net Logon service is not running, this message might be output and the job might end abnormally. If this message appears, check whether the Net Logon service is running.

If either of the following error messages is displayed when a job ends abnormally (for Windows only):

The job ends abnormally with return code 259 or -1, and the following message is output:

KAVU3284-W message (A system call error occurred in the internal process (logical-host-name). (module:reason-location[reason-location], reason code = 0x2013000a))

The job ends abnormally, and the following message output to the standard error output for the job:

The process cannot access the file. The file is being used by another process.

The above might occur when both of the following conditions exist:

When you register a job, a standard output file or standard error output file is explicitly specified by using either of the following methods:

- The file is specified in the detailed definition of the job.

- The file is specified in the job execution control command when you register the job.

Either of the following occurs for the file specified in step 1:

- In the program to be executed as a job, the file is opened with a function when the object-sharing method is either read-protected or write-protected.

- In the batch file to be executed as a job, the file is opened by using redirection.

As the standard output file or standard error output file when you register a job, do not specify a file opened from within a program executed as a job or opened by redirection from a batch fie. However, if the file is opened from within the program by using a function call, you can get around the problem by opening the file with a setting that permits shared reading or shared writing.

If either of the following messages is output to the integrated trace log:

KAVU5501-E message (message-from-database-system)

KAVU5290-E message (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))

An ISAM file might be invalid.

These errors might occur if you perform one of the following operations:

You forcibly shut down the system or turn off the power while the JP1/AJS3 service is still running.

You attempt to write to an ISAM file when there is insufficient disk space.

Check the status of the ISAM files. If an ISAM file is invalid, create the file again. For details about how to check the status of ISAM files and re-create them, see 2.11 Troubleshooting problems related to invalid ISAM files.

When you execute a job on an execution host running AIX or Linux, the resource limits defined for the user executing the job might not take effect. This could cause the job to end abnormally due to insufficient resources.

In AIX and Linux, when you define resource limits in /etc/security/limits (In Linux, /etc/security/limits.conf) for the user executing a job, the values will not take effect when the job is executed. Therefore, define the resource limits for the user (root) who starts JP1/AJS3.

For details, see Resource limits when Unix jobs are executed in 7.4 Notes on using Unix jobs in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

If the following message is output to the integrated trace log:

KAVU2251-E message (An error occurred in SSL communication processing.(logical-host-name, connection-destination-host-name, maintenance-information))

The communication encryption settings (whether to enable or disable encryption) on the manager and agent hosts do not match. Stop the JP1/AJS3 service, match the settings on both hosts, and then restart the JP1/AJS3 service.

If a child process is additionally executed in the background from the executed job process, the following phenomena might occur. (when the execution host is Windows)

It takes time for the executed job process to end.

If the process that was executed in the background continues to run and does not end, resources become insufficient.

To handle this, specify CON as the standard input file name, standard output file name, and standard error output file name when you define the job. If you specify CON for these file names, data is output to the standard output file and standard error output file. However, the standard error output messages related to the job are not output to JP1/AJS3 - View when you use JP1/AJS3 - View to display the detailed execution results. In addition, you cannot use the jpqjobget command to obtain information from the standard output file and the standard error output file.

(4) Executing an HTTP connection job results in an abnormal end

Possible causes are as follows:

A file name specified in a job might be invalid.

Check the following regarding file names:

The standard output file name and the standard error output file name must be different for jobs that are executed concurrently.

Job startup might fail because memory is insufficient.

Check the memory size estimate.

If the following messages are output to the integrated trace log (for Linux only):

KAVU4547-W message (You are not authorized to access the temporary file at the agent (agent-host-name).)

KAVU4560-W message (You lack access permission for the standard output file (file-name) at the agent (agent-host-name).)

KAVU4563-W message (You lack access permission for the standard error output file (file-name) at the agent (agent-host-name).)

If the KAVU4547-W message is output, the owner group of the work directory might be the secondary group of the job execution user, and the permission for the work directory might be 770 (the work directory is specified in the WorkPath environment setting parameter in the [JP1_DEFAULT\JP1NBQAGENT\Process] definition key).

If the KAVU4560-W or KAVU4563-W message is output, the owner group of the directory containing the specified file (file-name in the messages) might be the secondary group of the job execution user, and the permission for the directory might be 770.

Take one of the following actions:

If the KAVU4547-W message is output, change the access permission for the work directory so that the secondary group can access the directory.

Change the permission for the directory containing the specified file to one that allows the secondary group to access the directory. Also, change the permission for the specified file to one that allows the secondary group to read and write to the file.

Change the owner group of the directory and the specified file from the secondary group to the primary group of the job execution user.

Enable the necessary options as specified 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.

If the following message is output to the integrated trace log (for Windows only):

KAVU7533-E message (The execution user (user-name) mapped from JP1 user (host name = host-name, JP1 user name = user-name) is invalid. (reason code: 1792).)

If you execute a job with a user account that is different from the account for the JP1/AJS3 service and the Net Logon service is not running, this message might be output and the job might end abnormally. If this message appears, check whether the Net Logon service is running.

When you execute a job on an execution host running Linux, the resource limits defined for the user executing the job might not take effect. This could cause the job to end abnormally due to insufficient resources.

In Linux, when you define resource limits in /etc/security/limits.conf for the user executing a job, the values will not take effect when the job is executed. Therefore, define the resource limits for the user (root) who starts JP1/AJS3.

For details, see Resource limits when jobs are executed in 7.9 Notes on using HTTP connection jobs in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

If the following message is output to the integrated trace log:

KAVU2251-E message (An error occurred in SSL communication processing.(logical-host-name, connection-destination-host-name, maintenance-information))

The communication encryption settings (whether to enable or disable encryption) on the manager and agent hosts do not match. Stop the JP1/AJS3 service, match the settings on both hosts, and then restart the JP1/AJS3 service.

(5) The status of a standard job, HTTP connection job, action job, or custom job does not change

Possible causes are as follows:

If the KAVU3531-W message (The manager (logical-host-name) host name might be invalid.) is output to the integrated trace log:

The host name of the manager might be invalid, or the host name might not be resolved to an IP address.

Check whether the host name of the manager is valid. Also check the hosts file to make sure that the host name can be resolved to an IP address. If a DNS server is used, specify settings so that FQDN-format host names will be resolved to IP addresses.

The number of currently running jobs might have reached the maximum number of concurrently executable jobs.

Execute the ajsagtshow command to check the number of currently running jobs (JOB) and the maximum number of concurrently executable jobs (CON-EXE).

Specify the maximum number of concurrently executable jobs taking into considering the execution time of jobs and the number of jobs to be executed per unit time. To change the maximum number of concurrently executable jobs, use the ajsagtalt command.

For details about this command, see ajsagtshow in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

To determine whether the maximum number of concurrently executable jobs has been reached when job execution takes too much time or you cannot register a job, you can specify settings beforehand that output an appropriate message to the integrated trace log. For details about how to specify these settings, 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 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 UNIX).

If the backup enhancement function is enabled, job statuses will not change while the jajs_dbbackup command is creating a backup. Do not execute the jajs_dbbackup command while jobs are being executed. For details about backup enhancement function, see 5.2.5 Backing up and recovering an embedded database by using the backup enhancement function in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

While JP1/AJS3 was running, a backup program might have been executed to make backup copies of files and directories used by JP1/AJS3.

Do not execute a backup program while JP1/AJS3 is running.

If the KAVS1922-W message is output to the Windows event log or syslog while a queueless job is waiting for execution, the communication encryption settings (whether to enable encryption) on the manager and agent hosts might not match. Queueless jobs are PC jobs, Unix jobs, and action jobs for which Queueless Agent is specified in Exec. Service. Stop the JP1/AJS3 service, queueless agent service, and queueless file transfer service, make sure that the encryption settings on both hosts match, and then restart the service that you stopped.

(6) Registering a standard job, action job or custom job, or manipulating a queue results in an access permission error

An invalid access permission has been set for the JP1/Base authentication server.

Specify the correct access permission for the JP1_Queue resource group. Registering jobs and manipulating queues require one of the following permissions: JP1_JPQ_Admin, JP1_JPQ_Operator, and JP1_JPQ_User.

(7) The shell does not read environment variables (AIX only)

In AIX, the information in /etc/environment is not inherited.

See the explanation in 13.4.2 Changing the login scripts in the JP1/Automatic Job Management System 3 Configuration Guide, and change the login script. The following example shows how to change the login script:

if [ "$JP1JobID" != "" ] ; then
 . /etc/environment
 export environment-variable-to-be-specified
fi

After /etc/environment has been read, execute the export command for the environment variable to be specified.

Cautionary notes

The above setting is valid only for sh and ksh (.profile). It is invalid for other shell scripts such as csh.

When you specify the above setting, /etc/environment is read into the login script, possibly causing and the setting sequence of the information to change. Therefore, when you add processing that reads /etc/environment into the login script, check whether the environment variables set in /etc/environment are also specified in the login script. In addition, be careful about where you add /etc/environment. We recommend that you set the login script to read /etc/environment at the beginning of the login script.

(8) A job ends normally without executing the job process

In UNIX, JP1/AJS3 executes the login script when it executes a job. When the login script contains a command that ends the login script, such as the exit command shown below, the job ends normally before the job process is executed.

 /usr/bin/sh ; exit

To avoid premature ending of the job, change the login script so that the exit command is not executed.

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.

(9) Automatic retry is not performed when the retry interval has elapsed

Automatic retry might be delayed if there are a large number of jobs. Temporarily change the jobnet schedule or forcibly terminate the executing units to reduce the number of jobs that are executed simultaneously.

To set up automatic retry, you need to estimate the number of jobs, which also includes the number of retry executions. For details, see 1.3 Design considerations in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

(10) A task is delayed because automatic retry is performed concurrently for jobs

If jobs being executed on an agent host have ended concurrently due to, for example, an error on the agent host, automatic retry is performed for these jobs concurrently, increasing the number of jobs.

If you detect that the task is delayed because automatic retry has caused the number of jobs to increase, execute the ajsagtalt command to restrict jobs from being accepted on the execution agent where the error occurred. After agent host recovery, execute the ajsagtalt command again to cancel the restriction on job acceptance.

If automatic retry occurs when an error that requires some time for recovery has occurred, the increasing number of jobs might affect job execution performance. Therefore, when setting up automatic retry, specify the smallest necessary range of return codes. For details about automatic retry, see 2.4.13 Automatic retry for abnormally ending jobs in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

2.6.3 Troubleshooting problems related to action jobs

This subsection describes how to troubleshoot problems that are specific to action jobs.

(1) Execution of an action job fails at startup

Check whether the platform defined for the action job is the same as that defined for the agent that executes the action job. If the agent platform is different, change it to the platform defined for the action job.

(2) Execution of an action job results in display of an error message (for example, "DLL not found") on the execution host

A program needed to run an action job for message queue linkage or MSMQ linkage might not be installed on the host that executes the job.

Check whether the environment for the execution host is correct.

2.6.4 Troubleshooting problems related to event jobs

This subsection describes how to troubleshoot problems that are specific to event jobs.

(1) Condition not satisfied, although the specified host name is correct for JP1 event reception monitoring

An event server name has been specified as the host name in a JP1 event.

Check whether the event server name is the same as the name specified in the event service definition. Note that the host name in a JP1 event is case sensitive.

(2) When an event reception job is used, a condition match occurs on an unexpected event

When a JP1 event reception monitoring job, a log file monitoring job, and a Windows event log monitoring job are defined, character strings are specified for the following items:

JP1 event reception monitoring job:

Event issuer user name

Event issuer group name

Event issuer host name

Message

Event details

Extended attribute (if required)

Log file monitoring job:

Trap data

Data other than log information

Windows event log monitoring job:

Description

Partial matching is used for the character strings specified for the above items. Check whether a partial match has occurred for the specified character string.

If you want to find an exact match, use a regular expression. For example, if you want to find an exact match of spring as the event issuing host name, specify ^spring$ in Windows.

For details about regular expressions in Windows, see the JP1/Base User's Guide. For details about regular expressions in UNIX, see the UNIX documentation.

(3) An event job fails to execute at startup

If the KAVT0414-E message (The request was rejected. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)) is output to the integrated trace log:

Check the KAVT0992-E message that is output to the integrated trace log on the host where the job was to be executed. If necessary, add any required IP addresses in the agent connection permission configuration file, and then execute the jajs_pmtcon command.

(4) A warning message appears while an event job is in use

Possible causes are as follows:

The event action control performs delivery confirmation of communication data. The messages shown below might be output at the time JP1/AJS3 starts or stops, and mean socket data delivery confirmation failed and socket data delivery confirmation time expired. However, there will be no negative effects in such cases and you can continue the operation.

Therefore, when JP1/AJS3 starts or stops, messages with the following message IDs (for example, the system failed to check the arrival of socket data or the socket data arrival check exceeded the time limit) may be output. These messages do not affect the operation. Continue the operation.

KAVT0268-W

KAVT0612-W

KAVT0613-W

The event/action control of JP1/AJS3 - Manager retains event data that is detected by an event job that has been registered for execution, even when the JP1/AJS3 service is not running. However, when the number of event data retained exceeds a certain value, the detected event data information will be discarded. In that case, the following messages indicating event data disposal will be output.

KAVT0980-W

KAVT0981-W

For details about the above messages, see 4. Messages beginning with KAVT (Messages about the event/action control) in the manual JP1/Automatic Job Management System 3 Messages.

2.6.5 Troubleshooting problems related to jobnet connectors

This subsection describes how to troubleshoot problems related to jobnet connectors.

(1) A Jobnet connector does not terminate

Use the jobnet monitor or another method to check the execution status of the connection destination jobnet. If the status of that jobnet is Ended normally, Ended abnormally, or Ended with warning, a failure might have occurred. If the status is different from the above, the jobnet connector is waiting for a jobnet to end at the connection destination (the normal status).

If you want to advance the execution without waiting for the jobnet to end at the connection destination, change the status of the jobnet connector to Ended normally. Note, however, that the status of the jobnet connector and the status of the connection destination jobnet no longer match.

When the connection destination jobnet ends, use the messages output to the integrated trace log, and to the Windows event log or to syslog, to eliminate the cause of the failure. Next, re-execute the connection destination jobnet. When you re-execute the connection destination jobnet, generations are connected between the jobnet containing the jobnet connector and the connection destination jobnet, resulting in normal operation of the jobnet connector. For details about connecting generations, see 2.2.4(2) Rules governing connections between jobnet connectors and connection-destination jobnets in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

If you want to advance the execution of the jobnet connector without re-executing the connection destination jobnet, change the status of the jobnet connector to Ended normally. Note, however, that the status of the jobnet connector and the status of the jobnet on the connection destination will no longer match.

(2) A connection destination jobnet does not start after the scheduled start time is reached

Use the jobnet monitor or another method to check the execution status of the jobnet containing the jobnet connector. When the execution order control method is set to synchronous and the jobnet connector is waiting, the jobnet status is normal. If the jobnet connector is executing, a failure might have occurred.

When the execution order control method is set to synchronous and you want to start executing the connection destination jobnet without waiting for the jobnet connector to start, temporarily change the execution order control method to asynchronous.

2.6.6 Troubleshooting problems related to units with wait conditions

This subsection describes how to troubleshoot problems related to units with wait conditions.

(1) A unit with a wait condition remains in the Wait for prev. to end, Wait for start time, or Not sched. to exe. status and is not executed

In the Wait Conditions Statuses window, check the execution status of the unit whose end is being waited for, and then take appropriate action based on this status as described below.

If the unit whose end is being waited for is running:

The unit with a wait condition is still waiting for the termination of the unit whose end is being waited for. Wait until the unit whose end is being waited for terminates.

If the unit whose end is being waited for has ended abnormally:

An error might have occurred in the unit whose end is being waited for. Eliminate the cause of the error according to the messages output to the integrated trace log and to the Windows event log or to syslog. Next, either re-execute the unit whose end is being waited for or change the status of this unit to Ended normally.

If the unit whose end is being waited for is not registered:

Register for execution the unit whose end is being waited for.

If the unit whose end is being waited for is suspended:

Release the unit whose end is being waited for from the suspend status.

If the unit whose end is being waited for has no scheduled generations:

If Do not execute is selected for If not waiting for any generations in the Waiting Condition Settings window, the unit with a wait condition waits for a scheduled generation to be created for the unit whose end is being waited for, and for execution of the generation to end. If you want to execute the unit with a wait condition, create an execution schedule for the unit whose end is being waited for.

If you want to execute the unit with a wait condition without waiting for the unit whose end is being waited for to end, temporarily disable the wait for the unit whose end is being waited for. For details about how to temporarily change the wait condition, see 4.5.15 Temporarily changing the wait condition settings for a jobnet or job in the manual JP1/Automatic Job Management System 3 Overview.

Cautionary note

A unit with wait conditions can wait in the Not sched. to exe. status for the conditions to be met only if yes is specified for the PREWAITNOSCHUNITS environment setting parameter. For the PREWAITNOSCHUNITS environment setting parameter, see 20.4.2(122) PREWAITNOSCHUNITS in the JP1/Automatic Job Management System 3 Configuration Guide.

(2) A unit with a wait condition ends abnormally without being executed

In the Wait Conditions Statuses window, check the unit with a wait condition and the unit whose end is being waited for.

If the unit whose end is being waited for ends, but the unit with a wait condition ends abnormally, the definition of the unit whose end is being waited for might be invalid. For details about invalid definitions for units whose end is being waited for, see 2.2.5(8) Checking units whose ends are being waited for in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

If the definition of the unit whose end is being waited for is invalid, perform the procedure listed below.

To correct the problem, perform the following:

Correct the invalid definition for the unit whose end is being waited for.

Re-execute the unit whose end is being waited for.

Make sure that the status of the unit whose end is being waited for is Now running, and re-execute the unit with a wait condition.

If you want to re-execute only the unit with a wait condition, temporarily disable the wait for the unit whose end is being waited for, and then re-execute the unit with a wait condition. For details about how to temporarily change wait conditions, see 4.5.15 Temporarily changing the wait condition settings for a jobnet or job in the manual JP1/Automatic Job Management System 3 Overview.

2.6.7 Troubleshooting problems related to a flexible job distributed by a load balancer

This subsection describes how to troubleshoot problems that are related to a flexible job distributed by a load balancer.

(1) The status of a flexible job changes from "Now running" to "Ended abnormally" when monitoring ends

Possible causes are as follows:

The execution result of a job might not be returned from the destination agent due to a communication error or one of the following network setting errors:

Error in the security settings for the load balancer

Error in the firewall settings

Failure in name resolution

The load balancer might fail while a job is being executed on the destination agent.

While a job is being executed on the destination agent, the destination agent might be deleted by a scale-in operation.

While a job is being executed on the destination agent, the destination agent might fail.

While a job is being executed on the destination agent, the manager host might fail over and the execution result might be reported from the destination agent before the JP1/AJS3 Autonomous Agent Messenger service starts.

Correct the problem as follows:

If a load balancer is used, make sure that the load balancer is running and the network settings are correct.

Take action by referring to the execution result of the user program.

(2) The status of a flexible job changes to "Killed"

Possible causes are as follows:

While a job is being executed on the destination agent, the relay agent might fail.

While a job is being executed on the destination agent, the relay agent might fail over.

While a job is being executed on the destination agent, the manager host might fail.

Correct the problem as follows:

Make sure that the necessary services are running on the relay agent and manager host.

Take action by referring to the execution result of the user program.

(3) A user program terminates abnormally

Check the return value and the message sent to the standard error output and, if necessary, re-execute the flexible job.

(4) The status of a flexible job changes to "Failed to start"

Possible causes are as follows:

The specification of relay agents might be incorrect.

A connection attempt might have been refused by the connection source restriction function enabled on a relay agent.

Remove the cause of the problem according to the message that is output.

2.6.8 Troubleshooting problems related to a flexible job executed by broadcast execution

This subsection describes how to troubleshoot problems that are related to a flexible job executed by broadcast execution.

(1) A flexible job executed by broadcast execution terminates abnormally

Possible causes and their remedial actions vary depending on whether broadcast execution is in Sync mode or Async mode. Take action as appropriate.

Sync mode:

The action to be taken varies depending on whether the job execution results include the contents of the standard error output for each destination agent.

If the job execution results include the contents of the standard error output for each destination agent: A problem might have occurred on one or more of the destination agents. If a problem occurs on at least one destination agent during broadcast execution of a flexible job, the job status is judged to be Ended abnormally. Check the information output for each destination agent, and then take action as appropriate.

If the job execution results do not include the contents of the standard error output for each destination agent: A problem might have occurred on the relay agent (or the manager if no relay agent is used) or on the broadcast agent. Based on the output message, take action as appropriate on the relay agent (or the manager) or broadcast agent.

Async mode:

The action to be taken varies depending on whether maintenance-information-4 in the KAVS8100-E message is the host name of a destination agent. Take action as appropriate.

If maintenance-information-4 in the KAVS8100-E message is the host name of a destination agent: The broadcast agent might not be able to send an execution request to the indicated destination agent. Take measures so that the broadcast agent can communicate with the destination agent indicated by maintenance-information-4.

If maintenance-information-4 in the KAVS8100-E message is not the host name of a destination agent: The relay agent (or the manager if no relay manager is used) might not be able to communicate with the broadcast agent. Take measures so that the relay agent or manager is able to communicate with the broadcast agent.

(2) Jobs are not executed on a broadcast-execution destination agent

The following shows possible causes and actions to be taken in a case where jobs are not executed on a broadcast-execution destination agent:

The agent is not set up as a destination agent.

On a destination agent where jobs are not executed, use the ajsfxbcstatus command to check whether the broadcast agent has been set up correctly. If not, use the ajsatsetup command to set up the broadcast agent correctly.

The JP1/AJS3 Autonomous Agent service is not running.

On a destination agent where jobs are not executed, check whether the JP1/AJS3 Autonomous Agent service is running. If the service is not running, start it.

The destination agent cannot communicate with the broadcast agent.

On a destination agent where jobs are not executed, check whether the KAVS8146-E message has been output to the integrated trace log. If the message has been output, communication with the broadcast agent did not succeed. In this case, revise the communication environment settings, such as the firewall settings.

(3) A non-existent destination agent is requested to execute a flexible job by broadcast execution

The KAVS8100-E message might be output if an attempt is made to execute a flexible job by broadcast execution on a destination agent that has been deleted, for example, as a result of scaling-in. For broadcast execution of a flexible job, if the heartbeat of a destination agent stops, a destination agent is removed from broadcast agent management 60 minutes (default value) after its heartbeat stops. Therefore, if destination agents are deleted, for example, as a result of scaling-in, execute a flexible job after 60 minutes have passed.

The time before destination agents are removed from management can be changed by using the FXBC_MANAGEDAGT_REMOVEDTIME environment setting parameter. For the FXBC_MANAGEDAGT_REMOVEDTIME environment setting parameter, see 20.9.2(7) FXBC_MANAGEDAGT_REMOVEDTIME in the JP1/Automatic Job Management System 3 Configuration Guide.

2.6.9 Troubleshooting problems related to jobs that have an unknown end status

An unknown end status means that the job status cannot be correctly managed because one of the following situations occurred.

An attempt to acquire the job status fails.

When the JP1/AJS3 service is restarted, the job status cannot be acquired due to insufficient memory or a communication error.

The job information for a QUEUE job has already been deleted because the number of days for saving job information expired.

Example:

This problem might occur if the number of days for saving job information is set to 0, and the job information retention period (default: 10 minutes) expired before the JP1/AJS3 service was restarted. In such a case, the job information necessary for managing the job status might have been deleted already.

This subsection describes how to troubleshoot problems that are related to a job having an unknown end status.

(1) A PC job, UNIX job, QUEUE job, submit job, or queue-less job has an unknown end status

If a user program is started from a job that has an unknown end status, the execution results might be that the program ends normally (and not abnormally).If the job status is an unknown end status, check the execution results (for example, in the execution logs of the user program), and decide whether any of the following actions are applicable:

Re-execute the jobs, starting with the job that has the unknown end status.

Re-execute the jobs, starting with the next job after the job that has the unknown end status.

Re-execute only the job that has the unknown end status.

If a warning message or an error message was output to the integrated trace log at the time when the job status became an unknown end status, take action according to the individual output messages. For details, see the manual JP1/Automatic Job Management System 3 Messages.

If the defined jobnet uses a recovery unit, whether the recovery unit can be executed depends on the status of the preceding unit. For details on whether a recovery unit can be executed, see 7.5 Notes on using a recovery unit in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

2.6.10 Troubleshooting a situation in which the statuses of jobs become unknown on the manager host

The statuses of jobs that were run on an agent host might become unknown on the manager host, for example, in the following cases: when the JP1/AJS3 service is started by warm start or disaster recovery start, or when a communication failure occurs between the manager host and agent host.

In such cases, you can perform job recovery measures by checking the following files that have been output on the agent host:

Job execution result log file

Event job execution result log file

Note

For JP1/AJS3 for which an upgrade installation was performed from an earlier version and that is used under the default settings, the job execution result log file and event job execution result log file are not output. If you want these files to be output, set 1 or 2 for the JOBEXECRESULTLOG and EVJOBEXECRESULTLOG environment setting parameters. For details, see 3.4.9 Estimating the size of job execution result log files and event job execution result log files in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

The following table shows the correspondence between job types and the log files to which log data is to be output.

Table 2‒3: Job types and the log files to which log data is to be output

No.

Job type (unit)

Log file to which log data is to be output

1

PC Job#

Job execution result log file

2

Unix Job#

3

Action job#

4

Submit job

5

QUEUE Job

6

Custom Job

7

HTTP connection job

8

Passing information setting job

9

Flexible Job

10

Event job

Event job execution result log file

11

OR Job

No log data is output.

12

Judgment Job

13

Jobnet Connector

14

Remote Jobnet

#

No log data is output if the job is run by a queueless service.

(1) Recovery procedures for jobs other than event jobs

For jobs other than event jobs, you can perform recovery measures by following one of two procedures: a procedure using the ajsshow command, or a procedure using the scheduler log. Select the appropriate procedure according to the status of the manager host. The following table shows the statuses of the manager host and the corresponding recovery procedures.

Table 2‒4: Statuses of the manager host and the corresponding recovery procedures (for jobs other than event jobs)

Status of the manager host

Recovery procedure

The embedded database can be used (job execution information remains)

Perform recovery by using the ajsshow command.

Only the scheduler log can be used

Perform recovery by using the scheduler log.

The manager host has been set up again (neither the embedded database nor the scheduler log can be used).

Recovery is not possible.

(a) Recovery procedure using the ajsshow command

Run the ajsshow command, and then check the execution ID, job number, and agent host name of the target job.

Example:

ajsshow -f "%#,%I %H" /JOBNETNAME/JOBNAME

Search the job execution result log file by using as search conditions the full unit name of the target job in combination with the execution ID and job number that you checked in step 1.

Example:

Find the following: AJSROOT1:/JOBNETNAME/JOBNAME:@111,200001

Check whether messages KAVU3613-I, KAVU3614-I (in Windows only), KAVU3615-I (in UNIX only), and KAVU3616-I have been output to determine the status of the job on the agent host.

For details about the relationship between the messages that were output and the job status, see (3) Relationship between the messages that were output and the job status.

Perform recovery for the job according to the job status on the agent host.

Rerun the job or change the status of the job.

(b) Recovery procedure using the scheduler log

Search the scheduler log file, and then check the execution ID, job number, and agent host name of the target job.

Search the job execution result log file by using as search conditions the full unit name of the target job in combination with the execution ID and job number that you checked in step 1.

Example:

Find the following: AJSROOT1:/JOBNETNAME/JOBNAME:@111,200001

Check whether messages KAVU3613-I, KAVU3614-I (in Windows only), KAVU3615-I (in UNIX only), and KAVU3616-I have been output to determine the status of the job on the agent host.

For details about the relationship between the messages that were output and the job status, see (3) Relationship between the messages that were output and the job status.

Perform recovery for the job according to the job status on the agent host.

Rerun the job or change the status of the job.

(2) Recovery procedures for event jobs

Recovery for an event job can be performed only if the embedded database on the manager host can be used and the execution information of the job remains. In other cases, recovery is not possible.

The recovery procedure for an event job is as follows:

On the agent host, check the occurrence status (occurrence time) of the event you want to monitor.

For example, in the case of the JP1 event reception monitoring job, check the event database.

In the event job execution result log file, search for a start-event log record for which the KAVT0966-I message was output around the time that the monitoring-target event in step 1 occurred. Then, check the time at which the message was output and the unit ID.

On the manager host, run the ajsname command, and then obtain the full unit name from the unit ID.

Confirm that the full unit name that you obtained is the job in step 1.

Compare the time that the event in step 1 occurred and the time that the message in step 2 was output.

If the time that the event in step 1 occurred is earlier than the time that the message in step 2 was output, the event occurred before the monitoring of the event started. Manually run the succeeding job, if necessary.

(3) Relationship between the messages that were output and the job status

You can determine the status of a job from the messages that have been output to the job execution result log file. The status determined differs depending on whether the job is a flexible job.

(a) For jobs that are not flexible jobs

The following table shows the relationship between the messages that were output and the job status for a job that is not a flexible job.

Table 2‒5: Relationship between the messages that were output and the job status (for a job that is not a flexible job)

No.

KAVU3613-I

(at reception)

KAVU3614-I

or

KAVU3615-I

(at the start)#

KAVU3616-I

(at the end)

Status of the job

Status of the executable file or script file

Explanation

1

Not output

Not output

Not output

Not run yet

Not started yet

This is the status before the job is accepted from the manager host.

2

Output

Not output

Not output

Not run yet

Not started yet

This is the status in which the job has been accepted from the manager but has not been run yet.

3

Output

Output

Not output

Now running

Now running

This is the status in which the job is running.

4

Output

Not output

Output

Failed to start

Not started yet

In Windows:

This is the status in which the start of the executable file failed (for example, the executable file did not exist).

Determine the cause of the failure from the error messages that have been output to the integrated trace log file on the agent host.

In UNIX:

This is the status in which the start of the script file failed.

Determine the cause of the failure from the error messages that have been output to the integrated trace log file on the agent host.

5

Output

Output

Output

Execution ended

Ended

This is the status in which the job ran successfully and then ended.

#

In Windows, the KAVU3614-I message is output. In UNIX, the KAVU3615-I message is output.

(b) For flexible jobs

For a flexible job, the processing status on the relay agent is output to the job execution result log file. To check the status of the executable file or script file, you need to check the job-destination log file (ajsfxexec{1|2}.log) on the destination agent.

In a configuration that does not use relay agents, the manager host acts as a relay agent. In this configuration, messages are output to the job execution result log file on the manager host.

The following table shows the relationship between the messages that were output and the job status for a flexible job.

Table 2‒6: Relationship between the messages that were output and the job status (for a flexible job)

No.

KAVU3613-I

(at reception)

KAVU3614-I

or

KAVU3615-I

(at the start)#1

KAVU3616-I

(at the end)

Status of the flexible job

Status of the executable file or script file

Explanation

1

Not output

Not output

Not output

Not run yet

Not started yet

This is the status before the flexible job is accepted from the manager host.

2

Output

Not output

Not output

Not run yet

--#2

This is the status in which the flexible job has been accepted from the manager but has not been run yet.

3

Output

Output

Not output

Now running

--#2

This is the status in which the flexible job was started on a relay agent. To check whether the executable file was run, check the log file (ajsfxexec{1|2}.log) on the destination agent.

4

Output

Not output

Output

Failed to start

Not started yet

This is the status in which start of the flexible job failed. Determine the cause of the failure from the error messages that have been output to the integrated trace log file on the agent host.

5

Output

Output

Output

Execution ended

--#2

This is the status in which the flexible job ended on a relay agent. To check whether the executable file was run, check the log file (ajsfxexec{1|2}.log) on the destination agent.

#1

In Windows, the KAVU3614-I message is output. In Linux, the KAVU3615-I message is output.

#2

For details about how to check the status of an executable file or script file, see (4) How to check the status on the destination agent.

(4) How to check the status on the destination agent

The following describes how to check the status of an executable file or script file on the destination agent when a flexible job is used.

(a) If broadcast execution is not used

Check the full unit name and execution ID of the target flexible job from a message that has been output to the job execution result log file on the host that requested the flexible job (relay agent).

In the flexible-job-requester log file (ajsfxreq{1|2}.log) on the host that requested the flexible job (relay agent), check whether a message that meets the following condition has been output:

The full unit name and execution ID that are output in the KAVS8115-I message are the same as the full unit name and execution ID that you checked in step 1.

If a message that meets this condition has been output, check the host name of the destination agent and the maintenance information (uuid) that are output in that message.

In the flexible-job-destination log file (ajsfxexec{1|2}.log) that is on the host on which the flexible job was run (destination agent) and that you checked in step 2, check whether a message that meets the following conditions has been output:

The maintenance information that is output in the KAVS8139-I message is the same as the maintenance information (uuid) that you checked in step 2.

The maintenance information that is output in the KAVS8140-I message is the same as the maintenance information (uuid) that you checked in step 2.

Determine the status based on whether the KAVS8139-I and KAVS8140-I messages that meet these conditions have been output:

If both messages exist, the user program has ended.

If only the KAVS8139-I message exists, the user program is currently running.

If neither of the messages exists, the user program has not started.

(b) If broadcast execution is used

Check the full unit name and execution ID of the target flexible job from a message that has been output to the job execution result log file on the host that requested the flexible job (relay agent).

In the flexible-job-requester log file (ajsfxreq{1|2}.log) on the host that requested the flexible job (relay agent), check whether a message that meets the following condition has been output:

The full unit name and execution ID that are output in the KAVS8137-I message are the same as the full unit name and execution ID that you checked in step 1.

If a message that meets this condition has been output, check the maintenance information (uuid) that is output in that message.

In the log file (ajsfxdstr{1|2}.log) on the broadcast agent, check whether a message that meets the following condition has been output:

The full unit name and execution ID that are output in the KAVS8148-I message are the same as the full unit name and execution ID that you checked in step 1.

If a message that meets this condition has been output, run the ajsfxbcstatus command on the broadcast agent, and then check the destination agent.

Perform this step for each destination agent. Check whether a message that meets the following condition has been output in the flexible-job-destination log file (ajsfxexec{1|2}.log) on the destination agent:

The maintenance information that is output in the KAVS8139-I message is the same as the maintenance information (uuid) that you checked in step 2.

The maintenance information that is output in the KAVS8140-I message is the same as the maintenance information (uuid) that you checked in step 2.

Determine the status based on whether the KAVS8139-I and KAVS8140-I messages that meet these conditions have been output:

If both messages exist, the user program has ended.

If only the KAVS8139-I message exists, the user program is currently running.

If neither of the messages exists, the user program has not started.

2.7 Troubleshooting problems related to the embedded database

This section describes how to troubleshoot problems that might occur when the embedded database is being used.

2.7.1 Embedded database processing when a problem occurs and the action to be taken by the embedded database system administrator

This subsection describes the following items related to the processing of the embedded database when a problem occurs, and the action to be taken by the embedded database system administrator.

(1) The responsibilities of the embedded database system administrator when a problem occurs

When a problem occurs, the embedded database system administrator collects the troubleshooting information output to the following locations:

In Windows:

Files under embedded-database-practical-directory\spool

Files under embedded-database-practical- directory\tmp

Files under embedded-database-practical- directory\uxpldir

Windows event log

In UNIX:

Files under embedded-database-practical-directory/spool

Files under embedded-database-practical-directory/tmp

syslog

Remarks

The information required to troubleshoot a problem is described in 2.7.7 Information to be collected. The embedded database system administrator must refer to this information when troubleshooting.

(2) The information obtained by the embedded database when a problem occurs

The following table describes the troubleshooting information obtained by the embedded database when a problem occurs.

Table 2‒7: Troubleshooting information obtained by the embedded database when a problem occurs

Information

Description

Message log files

In Windows:

embedded-database-practical-directory\spool\pdlog1,pdlog2

In UNIX:

embedded-database-practical-directory/spool/pdlog1,pdlog2

Messages output by the embedded database. Back up this information when a problem occurs.

Standard output and standard error output for command execution

Information and error messages output by commands. This information appears on the screen from which the commands were entered. To save the information to a file, redirect the standard output and standard error output as needed.

In Windows:

Windows event log (Windows)

In UNIX:

syslog

Messages output by the embedded database.

In UNIX, use an OS editor to view this information. Note that messages might not be output when too many processes are attempting to access syslog.

Core save files#

(in UNIX)

embedded-database-practical-directory/spool/save/file-name

Data and stack information obtained in UNIX systems from processes related to the embedded database. Because only three such files can be saved at any one time, back up the core save files that you want to keep.

The file name format is ajs2n, where n is the sequence number of the core save file (1 to 3). Note that in some cases, sequence numbers might not be assigned.

Abort information file#

In Windows:

embedded-database-practical-directory\spool\save\file-name

In UNIX:

embedded-database-practical-directory/spool/save/file-name

Abort information. Back up this information if it is output. If the abort information consists of abort codes only, you can view them by using any text editor. The file name format is abcode.process-ID-of-server-process.

Snap information captured at the time the problem occurred#

In Windows:

embedded-database-practical-directory\spool\save\file-name

In UNIX:

embedded-database-practical-directory/spool/save/file-name

Snap information captured at the time the problem occurred. Back up this information if it is output. The file name format is ajs2n.deb, where n is the sequence number of the file (1 to 3). Note that in some cases, sequence numbers might not be assigned.

Shared memory dump file#

In Windows:

embedded-database-practical-directory\spool\pdshmdump\file-name

In UNIX:

embedded-database-practical-directory/spool/pdshmdump/file-name

Data collected from shared memory by the embedded database. Back up this information if it is output. The file name format is ajs2.rmb.process-ID-of-server-process.

Simple dump file#

In Windows:

embedded-database-practial-directory\spool\directory-for-each-server\file-name

In UNIX:

embedded-database-practial-directory/spool/directory-for-each-server/file-name

Data collected from shared memory and process-specific memory by the embedded database. Back up this information if it is output. The file name is the combination of the date and the process ID.

Command trace files

In Windows:

embedded-database-practical-directory\spool\cmdlog1,cmdlog2

In UNIX:

embedded-database-practical-directory/spool/cmdlog1,cmdlog2

The history information of executed commands, including commands that the embedded database generates internally. Back up the files before viewing this information in any text editor.

Error log files

In Windows:

embedded-database-practical-directory\spool\errlog\errlog1,errlog2

In UNIX:

embedded-database-practial-directory/spool/errlog/errlog1,errlog2

Internal information output by the embedded database. Back up this information if it is output.

Connected-user information file

In Windows:

embedded-database-practical-directory\spool\cnctusrinf

In UNIX:

embedded-database-practical-directory/spool/cnctusrinf

Information about users who were connected when the embedded database terminated. Use any text editor to view this information.

Connected-user details file

In Windows:

embedded-database-practical-directory\spool\cnctusrdtl

In UNIX:

embedded-database-practical-directory/spool/cnctusrdtl

Locked resource management table information file

In Windows:

embedded-database-practical-directory\spool\pdlckinf\output-date.mem

In UNIX:

embedded-database-practial-directory/spool/pdlckinf/output-date.mem

User information when a deadlock, lock-wait timeout, or insufficient locked-resource management table error occurs due to exclusive control by the embedded database. Use any text editor to view this information. Back up this information if it is output.

#

This troubleshooting information is output whenever the server process of the embedded database terminates abnormally. You can tell whether this process has terminated abnormally by checking for output of the KFPS01820-E message. If the message has been output, you can check the server name, process ID, and end state. Note that the following circumstances under which troubleshooting information might not be output.

If the end state begins with the letter c or d, no troubleshooting information will be output.

If the end state is 007f in Windows or 0009 in UNIX, the abort information file, core save files, and shared memory dump file will not be output.

(3) Embedded database processing when a problem occurs

The following describes the processing performed by the embedded database performs when a problem occurs.

(a) System recovery when the embedded database terminates abnormally

If, after the embedded database has terminated abnormally, the cause of the problem is eliminated and the embedded database is restarted, the embedded database restores the system to the status existing before the problem occurred.

(b) Processing when the embedded database repeatedly terminates abnormally

If the embedded database terminates abnormally, restart processing is executed. However, if the restart processing terminates abnormally three times in succession within 30 minutes, no more attempts to restart will be made. At this point, the embedded database system administrator must eliminate the cause of the problem, and then use the ajsembdbstart command to restart the embedded database.

(4) Action to be taken when a problem occurs in an embedded database process

When a problem occurs in an embedded database process, the process terminates abnormally. The embedded database then starts the recovery process and executes the rollback procedure. Because the process in question restarts automatically, the embedded database system administrator is not required to take any action. However, depending on the extent of the problem, the embedded database might terminate abnormally. If it does terminate abnormally, the embedded database restarts automatically. The embedded database system administrator must then eliminate the cause of the problem, and re-execute the operation.

2.7.2 The action to be taken if the embedded database is unable to start

This subsection describes the action to be taken if the embedded database is unable to start.

(1) Action to be taken if the embedded database is unable to start normally

The following table describes the possible causes of a failure of the embedded database to start normally and the actions to be taken.

Table 2‒8: Possible causes and actions to be taken if the embedded database is unable to start normally

Possible cause

Action to be taken

The embedded database is not installed or set up correctly.

Install or set up the embedded database again.

The system definition contains an error.

A message reporting that the system definition contains an error is output. Correct the error in the system definition based on the information in the message.

Memory or file capacity is insufficient.

A message reporting that system memory or file capacity is insufficient is output. Either stop unnecessary processes, or delete unnecessary files. If the message is related to shared memory, review the system definition. If the message is related to process-specific memory, stop all unnecessary processes.

In UNIX, if necessary, check the settings of the operating system parameters related to shared memory of the OS. For details about the operating system parameters, see the Release Notes.

Files required to start the embedded database are missing.

A message reporting that a file or files required to start the embedded database are missing. Create the required file or files based on the information in that message.

A problem has occurred in a file required to start the embedded database.

Refer to the messages, and check the file where the problem occurred. Eliminate the cause of the problem, and then restart the embedded database.

The OS is not properly configured to act as the execution environment for the embedded database.

Reconfigure the OS.

The current system log file cannot be allocated.

Use the ajsembdbaddlog command to add a system log file.

(2) Action to be taken if the embedded database is unable to restart

When the embedded database cannot be restarted, review the messages that are output during the restart processing. The following table lists the possible causes of a failure of the embedded database to restart and the actions to be taken.

Table 2‒9: Possible causes and actions to be taken if the embedded database is unable to restart

Possible cause

Action to be taken

The embedded database is unable to restart because a problem occurred in the RD area used by the master directory.

See (3) Action to be taken if a problem occurs in the system area.

The embedded database failed to restart after a log was added and the single server definition was edited (the KFPS00715-E message is output).

Execute the ajsembdbstart command with the -R option specified.

The embedded database cannot be restarted in UNIX due to a problem other than the above.

See (4) Action to be taken if another type of problem occurs (in UNIX).

(3) Action to be taken if a problem occurs in the system area

The embedded database cannot be restarted if a problem has occurred in the system area. In this case, you must restore the system area by using the procedure below. The system area contains internal information about the embedded database system. For details about the commands, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

To restore the system area:

Use the ajsembdbstart command with the -r option specified to start the embedded database.

Use the ajsembdbrstr command to restore the system area.

Use the ajsembdbstop command to terminate the embedded database.

Use the ajsembdbstart command to start the embedded database.

Use the ajsembdbrstr command to restore the RD area where the problem occurred.

We recommend that you check the execution results after each command is executed to ensure that the command was executed successfully.

(4) Action to be taken if another type of problem occurs (in UNIX)

The following describes the action to be taken if a problem other than those described above occurs in UNIX. For details about the commands used for this purpose, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference or 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.

(a) If the embedded database process registered in the OS has not started

Sometimes, an embedded database process registered in the OS might not start due to a fault of some kind. The OS will make several attempts to start the process before giving up, after which you will be unable to start the embedded database by using the ajsembdbstart command. At this point, take action by using the following procedure.

To correct the problem:

Execute the ajsembdbinstl command.

Note that if power is shut off and the server that hosts the embedded database stops while the database is running, the same problem might occur immediately after you turn the power back on and start the OS. This is because the status of the disk that contains the embedded database practical directory is the failed status. Take the same recovery action as described above.

(b) If the embedded database process registered in the OS has started

If the embedded database process registered in the OS has started, take action by using to the following procedure.

To correct the problem:

When you execute the ajsembdbstart command, a message is output. Use the information in the message to resolve the problem.

2.7.3 Action to be taken if the embedded database is unable to terminate

This subsection describes the action to be taken if the embedded database is unable to terminate.

(1) Action to be taken if the embedded database is unable to terminate because processes are connected

The following describes the action to be taken if the embedded database is unable to terminate because processes are still connected.

The embedded database will not terminate until all JP1/AJS3 processes have terminated. Make sure that all JP1/AJS3 services have stopped on the JP1/AJS3 - Manager host and any logical hosts. If a command is being executed, wait for the command to finish before terminating the embedded database. You can use the ajsembdbcancel command to forcibly terminate an executing command.

2.7.4 Action to be taken if the OS terminates abnormally

This subsection describes embedded database processing if the OS terminates abnormally, and the action to be taken by the embedded database system administrator.

(1) Embedded database processing

If the OS terminates abnormally due to a problem, the embedded database also terminates abnormally.

(2) Action to be taken by the embedded database system administrator

Perform the following step after you restart the OS.

Back up the troubleshooting information output to embedded-database-practical-directory\spool and embedded-database-practical-directory\tmp (embedded-database-practical-directory/spool and embedded-database-practical-directory/tmp in UNIX).

For details about the troubleshooting information that is output by the embedded database, see 2.7.1(2) The information obtained by the embedded database when a problem occurs.

2.7.5 Action to be taken if a communication error or power failure occurs

This subsection describes the action to be taken if the Communication error or Power failure occur.

(1) Action to be taken if a communication error occurs

An error message reporting that a communication error has occurred in the transaction will be displayed.

Investigate the cause of the error, and then terminate the embedded database and take action to resolve the problem. If the communication error prevents you from terminating the embedded database normally, then forcibly terminate the embedded database.

(2) Action to be taken if a power failure occurs

When the OS and the embedded database are restarted following recovery from a power failure, the power backup mechanism in the hardware restores the system to the point immediately before the power failure occurred.

Cautionary note (for Windows)

If the KFPO00107-E message ("aa....aa(bb....bb)" failed. errno = 999: dd....dd) is output when a command is executed or the embedded database starts, an embedded database work file might have become corrupted. If so, make sure that the embedded database has stopped, and then delete and restore all of the files listed below. Note that the files from number 4 and up might not exist in your system.

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

After you delete these files, make sure that embedded-database-practical-directory\tmp is not being accessed by any other applications, such as Windows Explorer, when you restart the embedded database.

2.7.6 Action to be taken if a disk failure occurs

This subsection describes the action to be taken if a disk failure occurs.

To correct a disk failure:

Initialize the hard disk.

Replace the hard disk and initialize it.

Set up partitions.

Set up partitions on the initialized hard disk in the same manner that they existed on the previous hard disk.

Initialize the UNIX file system.

Initialize, as a UNIX file system, the partition that you configured. However, this operation is not necessary if the partitions have already been initialized. For details about how to initialize the UNIX file system, see the documentation for the OS.

Re-create the embedded database environment.

If embedded database files had been created on the disk with the problem, execute ajsembdbunset to delete the environment and then use ajsembdbbuild to re-create the environment. Next, use ajsembdbrstr to restore the backup you created by using ajsembdbbackup.

2.7.7 Information to be collected

For details about the information that needs to be collected when a problem occurs while the embedded database is being used, see 1.3.1(6) Information about the embedded database (for Windows) or 1.3.2(5) Information about the embedded database (for UNIX).

For details about how to collect data, see 1.4.1(6) Collect information about the embedded database (for Windows) or 1.4.2(5) Collect information about the embedded database (for UNIX).

2.7.8 Action to be taken if an embedded database operation command error is detected

This subsection describes the action to be taken if an embedded database operation command error is detected.

(1) Action to be taken if an error occurs during embedded database maintenance

The following table describes the causes of errors that might occur during embedded database maintenance when the jajs_setup or jajs_setup_cluster command is executed, and the actions to be taken.

Table 2‒10: Causes of errors that might occur during embedded database maintenance and actions to be taken

Return value

Error cause

Action to be taken

1

An option was specified incorrectly.

Specify the correct option, and re-execute the command.

2

Creation of a temporary directory failed.

Back up the directories under the JP1/AJS3 installation directory, and contact the system administrator.

3

The setup identifier specified in the -id option is invalid.

Specify the correct setup identifier, and re-execute the command.

4

The embedded database corresponding to the setup identifier specified in the -id option is already installed.

Specify the setup identifier of an embedded database that is not installed, and re-execute the command.

5

There is no available setup identifier that JP1/AJS3 can allocate.

Back up the directories under the JP1/AJS3 installation directory, and contact the system administrator.

6

Acquisition of the embedded-database port number failed.

7

The port number specified in the -p option is invalid.

Specify the correct port number, and re-execute the command.

8

An unexpected error occurred.

Back up the directories under the JP1/AJS3 installation directory, and contact the system administrator.

9

The port number specified in the -p option is already being used.

Specify a port number that is not being used, and re-execute the command.

10

There is no available port number that JP1/AJS3 can allocate.

Back up the directories under the JP1/AJS3 installation directory, and contact the system administrator.

11

There is no available table prefix that JP1/AJS3 can allocate.

12

The specified embedded database configuration file was incorrectly edited by a user or is damaged.

Specify the correct embedded DB configuration file, and execute a command again.

24

The user who performed installation doesn't have administrator privileges.

A user who has administrator privileges must re-execute the command.

(2) Action to be taken if an error occurs during installation of the embedded database

The following table describes the causes of errors that might occur during installation of the embedded database and the actions to be taken.

Table 2‒11: Causes of errors that might occur during installation of the embedded database and actions to be taken

Return value

Error cause

Action to be taken

-66

Because the embedded DB file is being used by some process (such as Event Viewer, a virus scan program, or backup software), certain files cannot be updated.

Restart the OS, and then re-execute the command while the following processes are not running:

Event Viewer

Virus scan programs

Backup software

1

An option was specified incorrectly.

Specify the correct option, and re-execute the command.

2

Creation of a temporary directory failed.

Back up the directories under the JP1/AJS3 installation directory, and contact the system administrator.

3

The host name specified in the -mh option is invalid.

Specify the correct host name, and re-execute the command.

4

The setup identifier specified in the -id option is invalid.

Specify the correct setup identifier, and re-execute the command.

5

The embedded database corresponding to the setup identifier specified in the -id option is already installed.

Specify the setup identifier of an embedded database that is not installed, and re-execute the command.

6

The installation execution log of the embedded database was not found.

Back up the directories under the JP1/AJS3 installation directory, and contact the system administrator.

7

There is no installation image of the embedded database, or you do not have permission for the path specified in the -s option.

Either store an installation image of the embedded database in the directory pointed to by the path specified in the -s option, or change the permission for the specified path, and then re-execute the command. If you are performing the operation as an AJS administrator, make sure that the AJS administrators have the appropriate permission for the specified path.

8

Registration of the configuration definition failed.

Check the execution permissions for the command, and re-execute the command.

9

The combination of the setup identifier of the embedded database to be installed and the installation directory is invalid.

When you specify the setup identifier of an embedded database that is already installed, specify the installation directory that corresponds to the setup identifier, and then re-execute the command. When you specify the setup identifier of an embedded database that is not installed, specify the installation directory of an embedded database that is not installed, and then re-execute the command.

12

Some of the files to be copied during installation are missing.

The probable causes are as follows:

Because multiple ajsembdbinstl commands were executed simultaneously for the same setup identifier, the files to be copied during installation are in the invalid status.

Re-execute the ajsembdbinstl command.

For any other case:

Save the directories under the JP1/AJS3 installation directory, and then contact the system administrator.

24

The user who attempted installation doesn't have administrator privileges.

A user who has administrator privileges must re-execute the command.

61

Files required for installation are missing.

Store the installation image of the embedded database in the directory specified in the -s option, and then re-execute the command.

63

An error occurred during registration in the OS.

See the Release Notes, and make sure that all required OS patches and packages have been installed.

Also check whether the installation directory specified in the -i option meets the following conditions:

The installation directory name consists of the following characters:

In Windows:

- Alphanumeric characters

- Space character

- The path separator \

- Period (.)

- Underscore (_)

- Left parenthesis (()

- Right parenthesis ())

In UNIX:

- Alphanumeric characters

- Underscore (_)

- Slash (/)

The length of the path for the installation directory is 118 bytes or less.

Make sure that the above conditions are satisfied, and then re-execute the command. If this error reoccurs, back up the directories under the JP1/AJS3 installation directory, and contact the system administrator.

65

A disk access error occurred.

Make sure that the disk on which the embedded database is to be installed has sufficient free space, and then re-execute the command. If the error occurs again even when the disk has sufficient free space, back up the directories under the JP1/AJS3 installation directory, and contact the system administrator.

66

There is not enough free space on the installation disk for the embedded database.

Make sure that the installation disk for the embedded database has sufficient free space, and then re-execute the command.

68

A startup option (parameter) is invalid.

Back up the directories under the JP1/AJS3 installation directory, and contact the system administrator.

72

The user who attempted installation does not have the superuser privilege.

A user who has the superuser privilege must re-execute the command.

78

The OS is not a supported OS for JP1/AJS3.

Check whether the OS is supported for JP1/AJS3. If the OS is supported, back up the directories under the JP1/AJS3 installation directory, and contact the system administrator.

80

In Windows:

The status of the embedded database service with the specified setup identifier is not the stopped status.

In UNIX:

The embedded database specified for the installation directory is currently running.

Stop the embedded database, and re-execute the command.

82

In Windows:

An embedded database that has the same setup identifier is already installed.

In UNIX:

A database other than the embedded database is already installed in the installation directory.

Check the specified installation directory, and if necessary, change it.

83

An error occurred during registration in the exception list of the Windows firewall.

Back up the directories under the JP1/AJS3 installation directory, and contact the system administrator.

85

The contents of the patch information file are invalid.

86

Deletion of the patch information failed.

87

Deletion of the patch information failed. You need to restart the OS.

88

The pdservice.exe process is being executed.

89

The display name for the embedded database service duplicates an existing name.

90

The display name for the node switching service duplicates an existing name.

91

The source name for the Windows event log duplicates an existing name.

92

An abnormal condition occurred during registration of the display name for the embedded database service.

93

An abnormal condition occurred during registration of the display name for the node switching service.

94

An abnormal condition occurred during registration of the source name for the Windows event log.

95

The status of the embedded database is not the stopped status.

Stop the embedded database, and then re-execute the command.

96

The file to be used to install the version upgrade is being used.

Back up the directories under the JP1/AJS3 installation directory, and contact the system administrator.

60

An error other than above occurred.

(3) Action to be taken if an error occurs during uninstallation of the embedded database

The following table describes the causes of errors that might occur during uninstallation of the embedded database and the actions to be taken.

Table 2‒12: Causes of errors that might occur during uninstallation of the embedded database and actions to be taken

Return value

Error cause

Action to be taken

1

An option was specified incorrectly.

Specify the correct option, and re-execute the command.

2

Creation of a temporary directory failed.

Back up the directories under the JP1/AJS3 installation directory, and contact the system administrator.

3

JP1_DEFAULT cannot be specified in the -mh option.

Specify a correct host name, and re-execute the command.

4

The host name specified in the -mh option is invalid.

5

There is no installation information directory for the embedded database.

Back up the directories under the JP1/AJS3 installation directory, and contact the system administrator.

6

There is no uninstallation information directory for the embedded database.

7

The name of the installation directory for the embedded database cannot be resolved.

8

An unexpected error occurred.

9

Output of the environment creation information file for the embedded database failed.

10

The unsetup operation for the embedded database failed.

Take action based on the error message output before this message, and then re-execute the command.

11

Deletion of the configuration definition failed.

Back up the directories under the JP1/AJS3 installation directory, and contact the system administrator.

24

The user who attempted uninstallation doesn't have administrator privileges.

A user has administrator privileges must re-execute the command.

63

An error occurred during cancellation of registration in the OS.

Back up the directories under the JP1/AJS3 installation directory, and contact the system administrator.

65

A disk access error occurred.

72

The user who attempted uninstallation does not have the superuser privilege.

A user who has the superuser privilege must re-execute the command.

81

In Windows:

The embedded database that has the specified setup identifier is not installed.

In UNIX:

The embedded database is not installed in the installation directory.

Back up the directories under the JP1/AJS3 installation directory, and contact the system administrator.

88

Some files cannot be deleted because an executing embedded-database process remains.

Restart the OS, and then re-execute the command.

60

An error other than above occurred.

Back up the directories under the JP1/AJS3 installation directory, and contact the system administrator.

(4) Action to be taken if an error occurs during embedded database setup

The following table describes the causes of errors that might occur during embedded database setup and the actions to be taken. If an identifier other than "_JF0" is used as the embedded database identifier, replace the "_JF0" portion in command names or folder paths with the embedded database identifier that is used.

Table 2‒13: Causes of errors that might occur during embedded database setup and actions to be taken

Code

Message ID

Error cause

Action to be taken

7

KFPX29607

There are no files.

Back up the following information, and contact the system administrator:

In Windows:

Folders and files under JP1/AJS3-installation-folder\embdb\_JF0

Files under JP1/AJS3-installation-folder#\log\embdb

In UNIX:

Directories and files under /opt/jp1ajs2/embdb/_JF0

Files under /var/opt/jp1ajs2/log/embdb

8

KFPX29608

An attempt to open a file failed.

9

KFPX29609

An attempt to read a file failed.

10

KFPX29610

Generation of a file failed.

11

KFPX29611

Creation of a directory failed.

12

KFPX29612

The table and system areas are insufficient.

Make sure that the disk has sufficient free space.

13

KFPX29613

The table and system areas are insufficient.

14

KFPX29614

The table and system areas are insufficient.

15

KFPX29615

The table and system areas are insufficient.

16

KFPX29616

An error occurred during creation of the table and system areas.

If the maximum file size is set to 2 gigabytes or less in the OS file system settings, change it to a value greater than 2 gigabytes or to unlimited.

17

KFPX29617

An error occurred during initialization of the system area.

Back up the following information, and contact the system administrator:

In Windows:

Folders and files under JP1/AJS3-installation-folder\embdb\_JF0

Files under JP1/AJS3-installation-folder#\log\embdb

In UNIX:

Directories and files under /opt/jp1ajs2/embdb/_JF0

Files under /var/opt/jp1ajs2/log/embdb

18

KFPX29618

An error occurred during startup of the embedded database or initialization of the table area.

Make sure that the name of the host on which the embedded database is built can be resolved, and that communication is possible with the resulting IP address.

The system resources required by the embedded database are insufficient. See 3.2.5 Estimating the values for kernel parameters in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide, and check the required resources.

19

KFPX29619

An internal error occurred in the embedded database.

Back up the following information, and contact the system administrator:

In Windows:

Folders and files under JP1/AJS3-installation-folder\embdb\_JF0

Files under JP1/AJS3-installation-folder#\log\embdb

In UNIX:

Directories and files under /opt/jp1ajs2/embdb/_JF0

Files under /var/opt/jp1ajs2/log/embdb

20

KFPX29620

An error occurred during the creation of a temporary file.

23

KFPX29623

An internal error occurred in the embedded database.

24

KFPX29624

KFPS00031

The embedded database environment has already been created.

Uninstall JP1/AJS3 and then re-install JP1/AJS3.

25

KFPX29625

Memory is insufficient.

Secure sufficient memory.

26

KFPX29626

An internal error occurred in the embedded database.

Back up the following information, and contact the system administrator:

In Windows:

Folders and files under JP1/AJS3-installation-folder\embdb\_JF0

Files under JP1/AJS3-installation-folder#\log\embdb

In UNIX:

Directories and files under /opt/jp1ajs2/embdb/_JF0

Files under /var/opt/jp1ajs2/log/embdb

27

KFPX29627

An internal error occurred in the embedded database.

#

One of the following folders will be used:

If the installation destination folder is the default folder or a folder under a folder protected by the system

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2

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

A "folder protected by the system" refers to the following paths:

- Paths under system-drive\Windows

- Paths under system-drive\Program Files

- Paths under system-drive\Program Files (x86) (for 64-bit Windows)

If the installation target folder is none of the above

JP1/AJS3 - Manager-installation-folder

2.7.9 Action to be taken if a JP1/AJS3 - Manager installation or uninstallation error is detected

This subsection describes the action to be taken if a JP1/AJS3 - Manager installation or uninstallation error is detected. The following situations are covered:

Action to be taken if a JP1/AJS3 - Manager installation error occurs

Action to be taken if a JP1/AJS3 - Manager uninstallation error occurs

(1) Action to be taken if a JP1/AJS3 - Manager installation error occurs

The following table describes the causes of errors that might occur during installation of JP1/AJS3 - Manager and the actions to be taken.

Table 2‒14: Causes of errors that might occur during installation of JP1/AJS3 - Manager and actions to be taken

Error code

Error cause

Action to be taken

63

OS patches and packages required for JP1/AJS3 operation have not been installed.

See the Release Notes, install all required OS patches and packages, and then uninstall JP1/AJS3 and install it again.

66

There is not enough free space on the installation disk for the embedded database.

Check the environment being used to install JP1/AJS3. Check whether there is sufficient free space on the disk.

80

The previously installed embedded database has not been uninstalled.

Perform the following procedure:

In Windows:

Execute the following command:

ajsembdbstop -f -id _JF0

Execute the following command:

JP1/AJS3-installation-folder#\sys\install\embdbuninstl_JF0.cmd

Delete all of the following folders and files:

Folders and files under JP1/AJS3-installation-folder\embdb\_JF0

In UNIX:

Execute the following command:

ajsembdbstop -f -id _JF0

In edit mode, delete the pdprcd process for _JF0 registered in /etc/inittab.

Use the kill command to terminate the pdprcd process for _JF0 displayed by using the ps command.

Delete all of the following directories and files:

Directories and files under /opt/jp1ajs2/embdb/_JF0

82

95

#

One of the following folders will be used:

If the installation destination folder is the default folder or a folder under a folder protected by the system

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2

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

A "folder protected by the system" refers to the following paths:

- Paths under system-drive\Windows

- Paths under system-drive\Program Files

- Paths under system-drive\Program Files (x86) (for 64-bit Windows)

If the installation target folder is none of the above

JP1/AJS3 - Manager-installation-folder

(2) Action to be taken if a JP1/AJS3 - Manager uninstallation error occurs

The following table describes the causes of errors that might occur during uninstallation of JP1/AJS3 and the actions to be taken.

Table 2‒15: Causes of errors that might occur during uninstallation of JP1/AJS3 - Manager and actions to be taken

Error code

Error cause

Action to be taken

5

There is no installation directory for the embedded database.

The information about an embedded database that has already been uninstalled might still remain in the common definition of JP1/AJS3.

Perform the following procedure:

Execute the ajsembdbuninstl command for the setup identifiers of all the embedded databases installed in JP1/AJS3.

For details about this command, see ajsembdbuninstl in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.

Execute all of the following commands to delete the common definition:

jbsunsetcnf -i -h JP1_DEFAULT or logical-host-name -c JP1AJS2 -n EMBDBINSTALL

jbsunsetcnf -i -h JP1_DEFAULT -c JP1AJS2 -n EMBDB

jbsunsetcnf -i -h JP1_DEFAULT -c JP1AJS2 -n EMBDBPORT

For details about the jbsunsetcnf command, see the JP1/Base User's Guide.

6

Information required for uninstalling the embedded database does not exist.

81

The embedded database has not been installed.

10

The unsetup operation for the embedded database failed.

Possible causes are as follows:

Information about an embedded database that has already been uninstalled still remains in the common definition of JP1/AJS3.

Memory is insufficient.

Check the environment being used to uninstall JP1/AJS3. Also check whether there is sufficient free memory.

If this error reoccurs, perform the following procedure:

Execute the ajsembdbuninstl command for the setup identifiers of all the embedded databases installed in JP1/AJS3.

For details about this command, see ajsembdbuninstl in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.

Execute all of the following commands to delete the common definition:

jbsunsetcnf -i -h JP1_DEFAULT or logical-host-name -c JP1AJS2 -n EMBDBINSTALL

jbsunsetcnf -i -h JP1_DEFAULT -c JP1AJS2 -n EMBDB

jbsunsetcnf -i -h JP1_DEFAULT -c JP1AJS2 -n EMBDBPORT

For details about the jbsunsetcnf command, see the JP1/Base User's Guide.

2.8 Troubleshooting problems related to the execution of commands

This section describes how to troubleshoot problems related to the execution of commands.

If executed commands end normally but the execution results are inappropriate, JP1/AJS version 5 or earlier might be installed.

Make sure that the command path is specified in the PATH environment variable and is enabled, and then re-execute the command.

2.9 Troubleshooting problems related to mail system linkage (for Windows only)

This section describes how to troubleshoot problems related to mail system linkage performed in Windows.

2.9.1 Troubleshooting problems related to email sending jobs that do not use Outlook

(1) How to create a profile

To create a profile, execute the jpomailprof command with the -add option specified.

For details about how to create a profile, see 2.2.2(2) Creating profiles in the JP1/Automatic Job Management System 3 Linkage Guide. For details about the jpomailprof command, see jpomailprof (Windows only) in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

(2) Communication with the SMTP server fails

In the Execution Result Details dialog box of JP1/AJS3 - View, check whether any messages from KAVT3828-E to KAVT3833-E were output. If any were output, the profile settings might be wrong. Review the profile according to the instructions provided in the message.

(3) The email sending job ends abnormally

Check the following and take appropriate action.

In the Execution Result Details dialog box of JP1/AJS3 - View, check whether the KAVT3825-E message was output. If it was output, access to the profile might have failed. Review the access permissions for the execution user according to the instructions provided in the message.

(4) An email cannot be sent or received while the email sending job is running

Check the following and take appropriate action.

Make sure that the following two profiles have the same name. Note that the profile names are case sensitive and that single-byte characters and multi-byte characters are distinguished.

Profile that was actually created

Profile specified in the email sending job

Make sure that the mail server you are trying to connect to is running.

(5) The email sending job ended normally, but the email has not arrived

If the email sending job has ended normally, the email has been sent to the SMTP server. Check the following:

Use JP1/AJS3 - View to check whether the correct email destination is specified in the definition of the job. If the email destination is not correct, correct the definition of the email sending job.

Check the SMTP server log to see if the email was sent correctly. If the email was sent correctly, an error has occurred on either the communication path or the receiving-side host. Take appropriate action.

(6) The email sending job is forcibly terminated, but the telsmail.exe process still remains

If the email sending job is forcibly terminated, the telsmail.exe process might have been disconnected from JP1/AJS3, but might still remain for a certain time until the processing being performed is completed.

Check the following and take appropriate action.

After forcibly terminating the email sending job, use the task manager or task list to check whether the telsmail.exe process remains. If the process remains, terminate it manually.

2.9.2 Troubleshooting problems related to the email sending job and email reception monitoring job that use Outlook

(1) How to create a profile

In Windows, click the Mail icon in Control Panel. When a dialog box# for creating a profile for Outlook appears, specify the necessary settings.

#

The dialog box that is displayed differs depending on whether a profile has been created.

When a profile has been created:

The default-profile-name Properties dialog box appears.

On the Services page, click the Show Profiles button. The Mail dialog box appears. On the General page, click the Add button. You can start creating a profile.

When no profile has been created:

The Mail dialog box appears.

On the General page, click the Add button. You can start creating a profile.

Note that you cannot correctly create a profile in the Internet Accounts dialog box. For details, see (2) A profile cannot be created correctly below.

In addition, when you create a profile, specify a unique profile name. 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.

(2) A profile cannot be created correctly

The profile might have been created in the Internet Accounts dialog box. Therefore, make sure that the 32-bit version of Outlook 2021, 32-bit version of Outlook 2019, or the 32-bit version of Outlook 2016, is installed.

(3) Email sending and email reception monitoring jobs do not operate as intended

Mail system linkage operates on the premise that Outlook can independently send and receive emails in the system. If email sending and email reception monitoring jobs do not operate as intended, first use the procedure below to check whether emails can be sent and received normally.

Note that when operation profiles have been created or changed, mail system linkage might be disabled if Outlook starts without using the new profiles.

Make sure that Outlook can start.

Make sure the Outlook email program is set as the default email program for the system.

For details about how to specify this setting, see Help in Outlook.

If email sending and email reception monitoring jobs are executed without the Outlook email program set as the default program, Outlook opens a dialog box that displays the message Please run Microsoft Outlook and set it as the default mail client. Email sending and email reception monitoring are disabled.

Make sure that Outlook can send and receive emails normally.

Without starting JP1/AJS3, check whether Outlook can independently send and receive emails normally. To do so, adjust the following items to match the mail system linkage that will be used with JP1/AJS3:

Machine

Profile

Destination for emails to be sent

Sender, subject, and text of emails to be received

Account used to log on to the mail system from Outlook

Even if you plan to execute only email sending jobs or only email reception monitoring jobs, make sure that both email sending and email reception for operate normally, as described above.

If Outlook is used offline, open the File menu of Outlook and switch the Outlook mode from offline to online. When in offline mode, Outlook is not connected to any mail server.

Make sure that neither of the following types of dialog boxes requesting a response appears when Outlook starts, sends an email, or receives an email:

A dialog box that prompts you to enter the server name, user name, and password

A dialog box that prompts you to perform an operation, such as clicking a button, after which Outlook waits for you to perform the operation

Automatic operations that use mail system linkage are disabled in environments where either type of dialog box appears. If either type of dialog box appears, correct the profile so that it does not appear.

If you have determined that Outlook operation is normal, check the following and take appropriate action:

Make sure that the following three profiles have the same name. Also make sure that the use of single-byte and multi-byte characters and of upper-case and lower-case is identical for all the names.

Name of the profile created in the system

Profile name specified for the environment setting parameters ProfileName1 to ProfileName4

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.

Profile specified in the mail sending job and mail reception monitoring job

If you are using mail system linkage on a desktop, make sure that the JP1/AJS3 mail monitoring process is already running. If you are using mail system linkage in a service, make sure that the JP1/AJS3 Mail service is already running.

If you intend to use mail system linkage in a service, make sure that the account of the user who logged in to Windows when the profile was created, rather than a system account, has been set up as an account for the JP1/AJS3 Mail service. The JP1/AJS3 Mail service does not work with a system account.

If you have changed the values of the environment setting parameters for mail system linkage, restart the JP1/AJS3 service. Also, if mail system linkage is being used on a desktop, restart the JP1/AJS3 mail monitoring process. If mail system linkage is being used in a service, restart the JP1/AJS3 Mail service.

(4) Mail sending job and mail reception monitoring job ends abnormally

If an error message is followed by a mail system error code in the format MAPI CODE=xxxxxxxx, find the cause of the error in the following table and take appropriate action.

Table 2‒16: Mail system error codes and their meaning

MAPI code

Meaning

8004010D

Disk space is insufficient.

8004010E

Resources are insufficient.

80040111

Logon failed.

80040115

A network failure occurred.

80040116

A disk I/O error occurred.

80040124

The mail account is invalid.

8004010F

The destination address does not exist.

80040607

The destination address does not exist.

80040700

The destination address is ambiguous.

(5) A sent email is not placed in the Sent Items tray (it remains in the Outbox tray), or an email that is supposed to have arrived on the mail server is not placed in the Inbox tray

An email sending job executes the processing up to the point where new emails are sent to the Outbox of Outlook. The processing for sending emails from the Outbox of Outlook to the mail server, however, is executed by Outlook. Therefore, if emails remain in the Outbox of Outlook, see (3) Email sending and email reception monitoring jobs do not operate as intended, and check whether Outlook can independently send and receive emails.

If Outlook cannot normally send or receive emails independently, check and correct the profile settings and the connection to the mail server.

(6) If "Y" is specified for the environment setting parameter "ImmediateSendRecv", or when the environment setting parameter "ImmediateSendRecv" is not specified,a Send mail job takes a long time before ending successfully

Check whether emails are accumulated in the Outlook outbox.

If emails are accumulated in the outbox, either eliminate the cause of the problem and send the emails, or delete the accumulated emails so that they no longer remain in the outbox.

(7) Troubleshooting of any other problem

Check the following:

Make sure that you are using the prerequisite version of Outlook. For details, see 2.3.1(1) Mail systems that support linkage in the JP1/Automatic Job Management System 3 Linkage Guide. Also make a hard copy of the Outlook version information and make sure that the correct version is being used.

If you are using Outlook 2021, Outlook 2019, or Outlook2016, make sure that you are not using the 64-bit version of Outlook.

If an email reception monitoring job takes a long time to find applicable received emails, check the Inbox of Outlook to see whether it contains many unread emails. The email reception monitoring job references all unread emails in the Inbox of Outlook, and continues processing until it finds the emails that meet the conditions defined for the job. As a result, if the Inbox contains many unread emails that do not meet the job conditions, the processing takes a long time.

If you use mail system linkage for a service, see 2.3.8(15) Notes on using mail system linkage in a service in the JP1/Automatic Job Management System 3 Linkage Guide.

2.10 Troubleshooting agent failures that might affect manager processing

When you use submit jobs, you can use emergency commands to restore the system if an agent failure affects manager processing.

Using the emergency commands, you can check the job execution status if a failure occurs on an agent and take appropriate action. Because the emergency commands request job execution control over a communication path that is not used for normal commands, you can execute the commands immediately.

Important

Use the emergency commands only to restore the system if an agent failure affects the processing of the manager. If you use the emergency commands frequently, JP1/AJS3 might not be able to respond to failures.

The following table describes the commands executable as emergency commands. When using a command as an emergency command, add the -em option.

Table 2‒17: Commands that can be used as emergency commands

Purpose

Command

Description

Closing the queue entrance and exit

jpqqueclose

Use this command to close a queue's entrance and exit to prevent additional jobs from being queued, thereby preventing the failure from affecting other areas.

Opening the queue entrance and exit

jpqqueopen

Use this command to open a queue's entrance and exit when linkage with the failed agent becomes available.

Displaying information about a queue

jpqqueshow

Use this command to check the number of jobs in the queue and the number of jobs being executed when you change queue attributes.

Changing the number of jobs in a queue, the maximum value, and the warning value

jpqquealt

Use this command to increase the maximum number of jobs that can be temporarily held in a queue after you change queue attributes so that operation can continue after restoration.

Changing the maximum number of concurrently executable jobs on an agent

jpqagtalt

Use this command to execute priority jobs by using the maximum number of concurrently executable jobs to control alias agents.

Displaying information about an agent

jpqagtshow

Use this command to check the number of jobs being executed on an agent when you change an agent's attribute.

Changing the priority levels when multiple agents are connected

jpqagtlink

Use this command to change the priority levels for distributed startup of agents when a single queue is connected to multiple agents.

Canceling a job

jpqjobcan

Use this command to cancel the execution of a job waiting to be executed, placed on hold, or waiting for the specified time.

2.11 Troubleshooting problems related to invalid ISAM files

This section describes how to check the status of invalid ISAM files and how to re-create ISAM files.

If the ISAM files for the execution environment database for JP1/AJS3 QUEUE jobs and submit jobs become invalid, problems such as failure to start a job that uses a queue might occur. In such cases, perform the procedure described in 2.11.2 Procedure for re-creating the execution environment database for QUEUE jobs and submit jobs.

2.11.1 Procedure for checking the status of ISAM files

The following describes the procedure for checking the status of ISAM files.

If ISAM files are invalid, re-create them.

To check the status of ISAM files:

Stop the JP1/AJS3 service.

Execute the Jischk command to check whether the ISAM files are valid.

For Windows hosts:

Jischk -l 3 job-execution-environment-database-storage-directory-name#\JPQ*

For UNIX hosts:

/opt/jp1base/bin/Jischk -l 3 job-execution-environment-database-storage-directory-name#/JPQ*

#

For job-execution-environment-database-storage-directory-name, specify the directory name set in the DatabasePath environment setting parameter. For details about the DatabasePath environment setting parameter, see 20.5.2(3) DatabasePath in the JP1/Automatic Job Management System 3 Configuration Guide.

Check the output messages.

If one of the following messages is output, the corresponding ISAM file is invalid:

KAIU013-E Invalid key definition file detected.

KAIU014-E Invalid key file detected.

KAIU015-E Invalid data file detected.

For details about the Jischk command and the messages it outputs, see the JP1/Base User's Guide.

2.11.2 Procedure for re-creating the execution environment database for QUEUE jobs and submit jobs

To re-create the database used by the execution environment for QUEUE jobs and submit jobs:

Make sure that the JP1/AJS3 service is not running.

Use the jpqexport command to back up the definition of the execution environment for QUEUE jobs and submit jobs.

In Windows:

jpqexport [-mh logical-host-name] -dt isam -co jpqsetup.conf#

In UNIX:

/opt/jp1ajs2/bin/jpqexport [-mh logical-host-name] -dt isam -co jpqsetup.conf#

Although you can use any file name, for management purposes, we recommend that you use jpqsetup.conf.

#

Specify -mh logical-host-name to match the operating environment.

Depending on how an ISAM file is corrupted, attempts by the jpqexport command to access the file might result in an error. If you created a backup of the configuration definition file for the execution environment for QUEUE jobs and submit jobs (jpqsetup.conf), use it. If you do not have a backup, see jpqimport in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference, and create the configuration definition file for the execution environment for QUEUE jobs and submit jobs.

Delete the files and temporary files in the database storage directory for the execution environment for QUEUE jobs and submit jobs.

In Windows:

del execution-environment-database-storage-directory-for-QUEUE-jobs-and-submit-jobs\*#1

del work-directory-when-execution-environment-manager-process-for-QUEUE-jobs-and-submit-jobs-is-executing\M_JPQ*#2

In UNIX:

rm execution-environment-database-storage-directory-for-QUEUE-jobs-and-submit-jobs/*#1

rm work-directory-when-execution-environment-manager-process-for-QUEUE-jobs-and-submit-jobs-is-executing/M_JPQ*#2

#1

For execution-environment-database-storage-directory-for-QUEUE-jobs-and-submit-jobs, specify the folder specified in the DatabasePath environment setting parameter for the [{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Database] definition key. For details about the DatabasePath environment setting parameter, see 20.5.2(3) DatabasePath in the JP1/Automatic Job Management System 3 Configuration Guide.

#2

For work-directory-when-execution-environment-manager-process-for-QUEUE-jobs-and-submit-jobs-is-executing, specify the folder specified in the WorkPath environment setting parameter for the [{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Process] definition key. For details about the WorkPath environment setting parameter, see 20.5.2(1) WorkPath (for manager process) in the JP1/Automatic Job Management System 3 Configuration Guide.

Use the jpqimport command to re-create the ISAM files by using the file you backed up in step 2 as the execution environment definition for QUEUE jobs and submit jobs.

In Windows:

jpqimport [-mh logical-host-name] -dt isam -ci jpqsetup.conf#

In UNIX:

/opt/jp1ajs2/bin/jpqimport [-mh logical-host-name] -dt isam -ci jpqsetup.conf#

#

Specify -mh logical-host-name to match the operating environment.

Check the messages that are output when you execute the jpqimport command, and check whether the ISAM files are created successfully.

If the jpqimport command did not terminate normally, you will not be able to start the JP1/AJS3 service. If you are unsure as to whether the command was executed successfully, use the jpqexport command as described in step 2 to output the definition again. Then check whether the agent definition and queue definition in the definition output before re-creation of the ISAM files matches those in the definition after re-creation.

Restart the JP1/AJS3 service.

For details about the jpqexport and jpqimport commands, see 2. Commands Used during Setup 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 jbsgetcnf command, see the JP1/Base User's Guide.

2.12 Troubleshooting problems if JP1/AJS3 - View does not display scheduler services

This section describes how to troubleshoot problems if JP1/AJS3 - View does not display scheduler services.

If a scheduler service is not displayed as intended in an environment where scheduler service access restrictions are enabled, some settings in JP1/AJS3 - Manager might be incorrect. Check the following in JP1/AJS3 - Manager:

Make sure that a JP1 resource group is set as the root job group. If a JP1 resource is not set, set an appropriate JP1 resource group as the root job group by using the ajschange command.

Make sure that the logged-in JP1 user has permission to access the JP1 resource group set as the root job group.

Make sure that the OS user mapped to the logged-in JP1 user can access the following directories that constitute the scheduler service:

Database directory

Temporary directory

Job information directory

Backup information directory

2.13 Troubleshooting during the replication of a virtual machine after installing and setting up JP1/AJS3

This section describes troubleshooting during the replication of a virtual machine after installing and setting up JP1/AJS3.

2.13.1 Troubleshooting in the event that a job, jobnet, process, or embedded database terminates abnormally during the startup of the JP1/AJS3 service

This subsection describes troubleshooting in the event that a job, jobnet, process, or embedded database terminates abnormally during the startup of the JP1/AJS3 service.

(1) If the ajsinetd process terminates abnormally during the startup of the JP1/AJS3 service on a replicated virtual machine

If the ajsinetd process terminates abnormally and the KAVS1007-E message is output, a possible cause is that the replicated virtual machine failed to resolve the IP address of the local host. In this case, perform the following procedure:

Check the error message in the integrated trace log.

Make sure that the host name of the replicated virtual machine is correctly set. If the host name has already been set correctly, make sure that the IP address of the local host can be resolved from the host name on the replicated virtual machine.

(2) If a job or jobnet terminates abnormally during the startup of the JP1/AJS3 service on a replicated virtual machine

If a job or jobnet terminates abnormally and the KAVS0265-E or KAVS0262-E message is output, a possible cause is that the JP1/AJS3 service that was terminated during a job execution on the replicated virtual machine was not cold-started. In this case, perform the following procedure:

Check the error message in the integrated trace log.

Stop the JP1/AJS3 service on the replicated virtual machine.

Restart the JP1/AJS3 service in cold-start mode.

(3) If the embedded database terminates abnormally during the startup of the JP1/AJS3 service on a replicated virtual machine

If the embedded database terminates abnormally and the KFPU00219-E message is output, a possible cause is that the system common definition file for the embedded database contains incorrect settings. In this case, perform the following procedure:

Identify the incorrect settings according to the KFPU00219-E message.

Correct the system common definition file for the embedded database.

Restart the JP1/AJS3 service.

2.13.2 Troubleshooting in the event that an error message or warning message is output during the startup of the JP1/AJS3 service on a replicated virtual machine

This subsection describes troubleshooting in the event that an error message or warning message is output during the startup of the JP1/AJS3 service.

(1) If the event/action control agent process outputs an error message on a replicated virtual machine during the startup of the JP1/AJS3 service

If the KAVT0512-E message is output during the startup of the JP1/AJS3 service, a possible cause is that the agent process did not delete the manager host name on the replicated virtual machine. In this case, perform the following procedure:

Stop the JP1/AJS3 services.

On the replicated virtual machine, execute the jpoagoec command to delete the manager host name from the agent process.

Restart the JP1/AJS3 service.

(2) If a warning message is output to syslog or the event log on a replicated virtual machine during the startup of the JP1/AJS3 service

If the KFPS00615-W message is output during the startup of the JP1/AJS3 service, a possible cause is that the settings in the system common definition file for the embedded database are not correct. In this case, perform the following procedure:

Check the message in syslog or the event log.

Stop the JP1/AJS3 services.

Check and correct the settings in the system common definition file for the embedded database.

Restart the JP1/AJS3 service.

2.14 Troubleshooting problems related to the SSL communication

This section describes how to troubleshoot problems related to the SSL communication.

2.14.1 Troubleshooting in the event that the JP1/AJS3 service fails to start when SSL communication is enabled

The SSL communication settings might be incorrectly specified or the server certificate, private key, or route certificate might be incorrectly deployed.

If the KAVS8204-E message is output, the JP1/Base common definition information contains errors. Check and, if necessary, revise the JP1/Base common definition information, and then start the JP1/AJS3 service.

For details about the JP1/Base common definition information, see the JP1/Base User's Guide.

If one of the KAVS8201-E to KAVS8203-E messages is output, the server certificate, private key, or route certificate is incorrectly deployed. Check and, if necessary, revise the deployment of the server certificate, private key, and route certificate, and then start the JP1/AJS3 service.

For details about how to set the SSL communication, see 21.4 Setting up the communication using SSL in the JP1/Automatic Job Management System 3 Configuration Guide.

2.14.2 The KNAC0610-W, KAVU2252-W, KAVT0417-W, or KAVT0995-W message is output to the integrated trace log

The validity period of the server certificate used by the connection destination host has expired. Re-obtain the server certificate, and then replace the currently deployed server certificate with the new one.

2.15 Troubleshooting problems related to the external database

This section describes how to troubleshoot problems that occur during operation using the external database.

2.15.1 Troubleshooting in the event that a database access error occurs when the JP1/AJS3 service or a scheduler service is started or when a command is run

Possible causes are as follows:

The connection-destination database is not running.

No ODBC file data sources exist or can be accessed.

There are no ODBC drivers listed in an ODBC file data source.

The connection-destination address specified in the ODBC file data source is incorrect.

The user name and password specified in the ODBC file data source are incorrect.

The users specified in the ODBC file data source do not have access permissions for the database.

Check the status of the connection-destination database and the settings in the ODBC file data source.

2.15.2 Troubleshooting in the event that a scheduler service is automatically restarted due to a database access error occurring during operation

If the scheduler service can restart and job execution can continue, you do not need to take action.

If there are jobs that ended abnormally, check the statuses of those jobs, and then manually execute those jobs again.

If the scheduler service fails to restart, check whether a network failure has occurred or whether the network is unstable.

2.15.3 Troubleshooting in the event that the operability of jobnets and jobs or performance of job execution is degraded although the system settings or the number of job executions is not changed

Make sure that the manager host and database server in a cloud environment can communicate with each other at low latency.

Appendixes

A. List of Files and Directories

This appendix lists the files and directories for each JP1/AJS3-series program.

A.1 JP1/AJS3 - Manager files and directories

The following table lists the JP1/AJS3 - Manager files and directories for each OS.

(1) In Windows

The following table lists the files and folders for the Windows version of JP1/AJS3 - Manager according to their uses.

Supplementary note

For the tables listing log files and directories, see 1.2.5 List of log files and directories.

How to read the tables

The tables listing files and directories use the following abbreviations:

Abbreviation

Folder indicated by the abbreviation

Mgr_Path

JP1/AJS3 - Manager installation folder

Mgr_Data_Path

The value is different depending on the installation folder.

If the installation folder is the default installation folder or is in a folder protected by the system:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2

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)

If the installation folder is other than the above:

JP1/AJS3 - Manager installation folder

Embdb_Path

Embedded database practical directory

For details about the embedded database practical directory, see 2.6.5 Database settings that are set up in JP1/AJS3 in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

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

By default, Mgr_Path is SystemDrive\Program files (x86)\HITACHI\jp1ajs2.

By default, Base_Path is SystemDrive\Program files (x86)\HITACHI\jp1base.

An asterisk (*) indicates a string of one or more characters.

(a) Common files and folders

Table A‒1: Files that the user can modify (JP1/AJS3 - Manager for Windows)

Item

File name

JP1/AJS3 startup process definition file

Mgr_Path\conf\jp1ajs_spmd.conf

Mgr_Path\conf\jp1ajs_dbmd.conf

Mgr_Path\conf\jp1ajs_hstd.conf

Mgr_Path\conf\jp1ajs_agtd.conf

Mgr_Path\conf\jp1ajs_schd.conf

JP1/AJS3 extended startup process definition file

Mgr_Path\conf\jp1ajs_service_0700.conf

Mgr_Path\conf\jp1ajs_dbmd_0700.conf

Mgr_Path\conf\jp1ajs_hstd_0700.conf

Mgr_Path\conf\jp1ajs_agtd_0700.conf

Mgr_Path\conf\jp1ajs_schd_0700.conf

JP1/AJS3 system management event definition file

Mgr_Path\conf\jp1ajs_param.conf

JP1/AJS3 pre-start process definition file

Mgr_Path\conf\jp1ajs_spmd_pre.conf

Configuration definition file for the execution environment for QUEUE jobs and submit jobs

Mgr_Path\conf\jpqsetup.conf

Customization file that disables the menu commands available in the JP1/AJS3 - View window#1

Mgr_Data_Path\conf\profiles\JP1-user-name\jajsDisableMenu#5

Executable command settings file#2

Mgr_Data_Path\conf\profiles\(jajsExecutableCommand)\jajsExecutableCommand

Mgr_Data_Path\conf\profiles\(jajsExecutableCommand)\JP1-user-name\jajsExecutableCommand

System common definition for the embedded database#3

Embdb_Path\conf\pdsys

Single server definition for the embedded database#3

Embdb_Path\conf\ajs2

View customization settings file#4

Mgr_Data_Path\conf\profiles\(jajsCustomizeView)\jajsCustomizeView

Mgr_Data_Path\conf\profiles\(jajsCustomizeView)\JP1-user-name\jajsCustomizeView

Note

On the logical host, replace Mgr_Path and Mgr_Data_Path with the following folder:

shared-folder\jp1ajs2

#1

This file is created by the user in order to disable menu commands in JP1/AJS3 - View. For details, see 11.3.9 Disabling menus in the JP1/Automatic Job Management System 3 Operator's Guide.

#2

This file is created by the user to enable the execution of JP1/AJS3 commands in JP1/AJS3 - View. For details, see 11.3.18 Allowing execution of JP1/AJS3 commands in the JP1/Automatic Job Management System 3 Operator's Guide.

#3

For details, see 23.1 Preparation for using an embedded database in the JP1/Automatic Job Management System 3 Configuration Guide.

#4

This file is created by the user to display the information about the connection-destination manager host in a window of JP1/AJS3 - View. For details, see 11.3.19 Displaying the information about the connection-destination manager host in the JP1/Automatic Job Management System 3 Operator's Guide.

#5

This file take effect for all of physical and logical hosts.

Even in the case of a logical host, there is no need to replace Mgr_Data_Path with the shared folder name.

Table A‒2: Files and folders that the user can reference (JP1/AJS3 - Manager for Windows)

Item

File or folder name

Executable file storage folder

Mgr_Path\bin\

Library file storage folder

Mgr_Path\lib\

Environment-settings file storage folder

Mgr_Path\conf\#

Readme file

Mgr_Path\Readme_ja.txt

Mgr_Path\Readme_en.txt

Version information file

Mgr_Path\Version.txt

Tool file storage folder

Mgr_Path\tools\

Header file storage folder

Mgr_Path\include

#

On the logical host, replace Mgr_Path with the following folder:

shared-folder\jp1ajs2

Table A‒3: Files and folders that the user does not need to modify or reference (JP1/AJS3 - Manager for Windows)

Item

File or folder name

Job information storage folder

Mgr_Data_Path\jobinf\

Database storage folder for JP1/AJS3

Mgr_Data_Path\database\

Job/jobnet information storage folder

Mgr_Data_Path\database\schedule\

Queue information database storage folder

Mgr_Data_Path\database\queue\

Job/jobnet information backup folder

Mgr_Data_Path\backup\schedule\

JP1/AJS3 file system folder

Mgr_Data_Path\sys\

System file folder for an event/action control agent

Mgr_Data_Path\sys\infoagt

Information folder for an event/action control manager

Mgr_Data_Path\sys\schedule\scheduler-service-name\infodir\

Work file storage folder for JP1/AJS3

Mgr_Data_Path\tmp\

Product information file storage folder

system-drive\Program Files (x86)\HITACHI\jp1common\JP1AJS2

Profile storage folder for sending emails without using Outlook

profile-storage-folder#1\sys\prf

Folder storing the files used by the JP1/AJS3 Autonomous Agent service and JP1/AJS3 Autonomous Agent Messenger service

Mgr_Path\embsch\

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\embsch\

Embedded database files and folders#2

See Table A-4.

Note

On the logical host, replace Mgr_Data_Path with the following folder:

shared-folder\jp1ajs2

#1

For profile-storage-folder, substitute the value set for the WaitInfFileOutDir environment setting parameter of the [{JP1_DEFAULT|logical-host-name}\JP1AOMAGENT] definition key. For details about the WaitInfFileOutDir environment setting parameter, see 20.6.2(16) WaitInfFileOutDir (for agent processes) in the JP1/Automatic Job Management System 3 Configuration Guide.

#2

The system common definition and single server definition for the embedded database are exceptions.

Table A‒4: Embedded database files and folders (for Windows)

Item

File or folder name

Executable file storage folder

Embdb_Path\bin

Library file storage folder

Embdb_Path\lib

Executable file library storage folder

Embdb_Path\client

Troubleshooting information storage folder

Embdb_Path\spool

Embedded database work folder

Embdb_Path\tmp

System definition file storage folder

Embdb_Path\conf

Client environment definition file storage folder

Embdb_Path\conf\emb

Embedded database settings file storage folder

Embdb_Path\conf\ajsdbst

Folder for files used by the embedded database

Embdb_Path\.dbenv

Embdb_Path\UXPLDIR

Data area directory

Embdb_Path\dbarea#

System file area directory

Embdb_Path\dbarea#

Work area directory

Embdb_Path\dbarea#

#

These folders are automatically created when setup is performed during installation or the setup command is executed. The paths of the created folders differ depending on the options specified in the setup command. For details, see 2.6.5 Database settings that are set up in JP1/AJS3 in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

(b) Files when HP NNM linkage is used

Table A‒5: Files that the user can modify or reference (when JP1/AJS3 - Manager for Windows and HP NNM linkage are used)

Item

File name

Definition file for linkage with HP NNM

Mgr_Path\conf\jpoov.conf

(Environment definition)

Note

On the logical host, replace Mgr_Path with the following folder:

shared-folder

Table A‒6: Files that the user does not need to modify or reference (when JP1/AJS3 - Manager for Windows and HP NNM linkage are used)

Item

File name

Definition file for linkage with HP NNM

Mgr_Path\bin\jp1ajs2_f

(Field definition)

Mgr_Path\bin\snmpd.extend

(MIB object definition)

Mgr_Path\bin\jp1ajs2_j

(Menu definition for Japanese)

Mgr_Path\bin\jp1ajs2_e

(Menu definition for English)

Mgr_Path\bin\trpcajs2j

(Event definition for Japanese)

Mgr_Path\bin\trpcajs2e

(Event definition for English)

Mgr_Path\bin\trustajs2

(Trusted command definition)

Supplementary note

Logs are output to the default folders even in a cluster configuration.

(c) Files and folders when mail linkage is used

Table A‒7: Files and folders that the user references, and for which deletion must be managed during operation (when JP1/AJS3 - Manager for Windows and mail linkage are used)

Item

File or folder name

Default passing-information file#1

Mgr_Data_Path\tmp\infodir\mail\JPO*.tmp

Storage folder for a file attached to mail for inherited information of an email reception monitoring job#2

Mgr_Data_Path\tmp\infodir\mail\*_*\

Note

On the logical host, replace Mgr_Data_Path with the following folder:

shared-folder

#1

This file is used if you do not specify the EvjobInfFile environment setting parameter.

If you specify the EvjobInfFile environment setting parameter, the system creates the mail folder under the specified folder and uses it.

For details about the list of files attached to the received email to be stored in the directory for storing passed event or job information, see 2.6.3 List file for email reception monitoring job (Windows only) in the JP1/Automatic Job Management System 3 Linkage Guide.

#2

In this folder, the files attached to the mail are stored with the file name they had when attached.

Table A‒8: Folders that the user can reference (when JP1/AJS3 - Manager for Windows and mail linkage are used)

Item

Folder name

Default passing-information file folder#

Mgr_Data_Path\tmp\infodir\mail\

Note

On the logical host, replace Mgr_Data_Path with the following folder:

shared-folder

#

This folder is used if you do not specify the EvjobInfFile environment setting parameter.

If you specify the EvjobInfFile environment setting parameter, the system creates the mail folder under the specified folder and uses it.

(d) Files and folders when PC jobs are used

Table A‒9: Files that the user references, and for which deletion must be managed during operation (when JP1/AJS3 - Manager for Windows and PC jobs are used)

Item

File name

Standard output file#1

Defined by the user

Standard error output file#2

Defined by the user

#1

This file is used when you open the Define Details - [PC Job] dialog box, choose the Definition page, and specify a desired file name in Standard output. The data increases uniformly when you select Append in Standard output.

#2

This file is used when you open the Define Details - [PC Job] dialog box, choose the Definition page, and specify a desired file name in Standard error. The data increases uniformly when you select Append in Standard error.

(e) Files and folders when HTTP connection jobs are used

Table A‒10: Files that the user references, and for which deletion must be managed during operation (when JP1/AJS3 - Manager for Windows and HTTP connection jobs are used)

Item

File name

Standard output file#1

Defined by the user

Standard error output file#2

Defined by the user

#1

This file is used when you open the Define Details - [HTTP Connection Job] dialog box, choose the Definition page, and specify a desired file name in Standard output.

#2

This file is used when you open the Define Details - [HTTP Connection Job] dialog box, choose the Definition page, and specify a desired file name in Standard error.

(f) Files and folders when JP1/AJS3 Console Manager is used

The tables listing files and folders that are used by JP1/AJS3 Console Manager use the following abbreviations:

CM_Path: JP1/AJS3 - Manager installation folder\cm

CM_Data_Path: The value is different depending on the installation folder.

If the installation folder is the default installation folder or is in a folder protected by the system:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2CM

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)

If the installation folder is other than the above:

JP1/AJS3 - Manager installation folder\cm

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

Table A‒11: Files that the user can create and modify (when JP1/AJS3 - Manager for Windows and JP1/AJS3 Console Manager are used)

Item

File or folder name

Environment settings file for JP1/AJS3 Console Manager

CM_Path\conf\ajs2cm.conf

Table A‒12: Files and folders that the user can reference (when JP1/AJS3 - Manager for Windows and JP1/AJS3 Console Manager are used)

Item

File or folder name

Execution file storage folder

CM_Path\bin\

Environment-settings file storage folder

CM_Path\conf\

Environment settings model file for JP1/AJS3 Console Manager

CM_Path\conf\ajs2cm.conf.model

Table A‒13: Files and folders that the user does not need to modify or reference (when JP1/AJS3 - Manager for Windows and JP1/AJS3 Console Manager are used)

Item

File or folder name

Data directory

CM_Data_Path#\database

File for the creation of JP1/AJS3 Console Manager environment settings model file

CM_Path\conf\ajs2cm.conf.model.model

#

On the logical host, replace CM_Data_Path with the following folder:

shared-folder\jp1ajs2cm

Table A‒14: Log file storage folders (when JP1/AJS3 - Manager for Windows and JP1/AJS3 Console Manager is used)

Item

File or folder name

Trace log

CM_Data_Path\log

(g) Files and folders when JP1/AJS3 Console Agent is used

Table A‒15: Files and folders for JP1/AJS3 Console Agent (JP1/AJS3 Console Agent for Windows)

Item

File or folder name

Temporary file storage folder for JP1/AJS3 Console Agent

Mgr_Data_Path\tmp\console_agent

Execution file

Mgr_Path\bin\ajsca*.exe#1

Mgr_Path\bin\ajsca*.dll#1

Mgr_Path\bin\jp1ajs2camsg*.dll#1

Environment settings model file for JP1/AJS3 Console Agent

Mgr_Path\conf\ajs2ca.conf.model

Environment settings file for JP1/AJS3 Console Agent

Mgr_Path\conf\ajs2ca.conf

Log file storage folder

Mgr_Data_Path\log

File for creation of JP1/AJS3 Console Agent environment settings model file

Mgr_Path\conf\ajs2ca.conf.model.model#2

#1

An asterisk (*) indicates a string of one or more characters.

#2

Do not modify this file.

Cautionary note

The system creates files in the EVERYONE full-control mode.

(h) Files and folders when an external database is used

Table A‒16: Files that the user references, and for which deletion must be managed during operation (when JP1/AJS3 - Manager for Windows and when an external database is used)

Item

Folder name

Standard output file#1

In the folder#3 that contains the standard output file and the standard error output file

Standard error output file#2

#1

This is created if the ajsshow command is executed with -i %so specified.

#2

This is created if the ajsshow command is executed with -f %r or -r specified.

#3

Replace the specification of the folder that contains the standard output file and the standard error output file, with the value specified for the STDFILEOUTDIR environment setting parameter in the [JP1_DEFAULT\JP1AJSMANAGER\scheduler-service-name] definition key. For details about the STDFILEOUTDIR environment setting parameter, see 20.4.2(126) STDFILEOUTDIR in the JP1/Automatic Job Management System 3 Configuration Guide.

(2) In UNIX

The following table lists the files and directories for the UNIX version of JP1/AJS3 - Manager according to their uses.

Supplementary note

For the tables listing log files and directories, see 1.2.5 List of log files and directories.

How to read the tables

An asterisk (*) indicates a string of one or more characters.

Embdb_Path indicates the embedded database practical directory. For details about the embedded database practical directory, see 2.6.5 Database settings that are set up in JP1/AJS3 in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

(a) Common files and directories

Table A‒17: Files that the user can modify (JP1/AJS3 - Manager for UNIX)

Item

File name

JP1/AJS3 startup process definition file

/etc/opt/jp1ajs2/conf/jp1ajs_spmd.conf

/etc/opt/jp1ajs2/conf/jp1ajs_dbmd.conf

/etc/opt/jp1ajs2/conf/jp1ajs_hstd.conf

/etc/opt/jp1ajs2/conf/jp1ajs_agtd.conf

/etc/opt/jp1ajs2/conf/jp1ajs_schd.conf

JP1/AJS3 extended startup process definition file

/etc/opt/jp1ajs2/conf/jp1ajs_service_0700.conf

/etc/opt/jp1ajs2/conf/jp1ajs_dbmd_0700.conf

/etc/opt/jp1ajs2/conf/jp1ajs_hstd_0700.conf

/etc/opt/jp1ajs2/conf/jp1ajs_agtd_0700.conf

/etc/opt/jp1ajs2/conf/jp1ajs_schd_0700.conf

JP1/AJS3 system management event definition file

/etc/opt/jp1ajs2/conf/jp1ajs_param.conf

JP1/AJS3 pre-start process definition file

/etc/opt/jp1ajs2/conf/jp1ajs_spmd_pre.conf

Environment settings file for the scheduler service

/etc/opt/jp1ajs2/conf/AJS3_Schedule.conf

Execution environment settings file for jobs

/etc/opt/jp1ajs2/conf/AJS3_Queue.conf

the event/action execution environment settings file

/etc/opt/jp1ajs2/conf/AJS3_EVAction.conf

Environment settings file for the scheduler service (for compatibility with JP1/AJS2 - Manager)#1

/etc/opt/jp1ajs2/conf/Schedule.conf

Execution environment settings file for jobs (for compatibility with JP1/AJS2 - Manager)#1

/etc/opt/jp1ajs2/conf/Queue.conf

Configuration definition file for the execution environment for QUEUE jobs and submit jobs

/etc/opt/jp1ajs2/conf/jpqsetup.conf

the event/action execution environment settings file (for compatibility with JP1/AJS2 - Manager)#1

/etc/opt/jp1ajs2/conf/EVAction.conf

Queueless-job execution environment settings file

/etc/opt/jp1ajs2/conf/Queueless.conf

Customization file that disables the menu commands available in the JP1/AJS3 - View window#2

/etc/opt/jp1ajs2/conf/profiles/JP1-user-name/jajsDisableMenu#6

Executable command settings file#3

/etc/opt/jp1ajs2/conf/profiles/(jajsExecutableCommand)/jajsExecutableCommand

/etc/opt/jp1ajs2/conf/profiles/(jajsExecutableCommand)/JP1-user-name/jajsExecutableCommand

System common definition for the embedded database#4

Embdb_Path/conf/pdsys

Single server definition for the embedded database#4

Embdb_Path/conf/ajs2

View customization settings file#5

/etc/opt/jp1ajs2/conf/profiles/(jajsCustomizeView)/jajsCustomizeView

/etc/opt/jp1ajs2/conf/profiles/(jajsCustomizeView)/JP1-user-name/jajsCustomizeView

Note

On the logical host, replace /etc/opt/jp1ajs2 with the following directory:

shared-directory/jp1ajs2

#1

The environment does not include this file if the JP1/AJS3 - Manager installation is a new installation. This file is the environment file for compatibility with JP1/AJS2 - Manager. This file can not be used in a standard configuration of JP1/AJS3 - Manager.

#2

This file is created by the user in order to disable menu commands in JP1/AJS3 - View. For details, see 11.3.9 Disabling menus in the JP1/Automatic Job Management System 3 Operator's Guide.

#3

This file is created by the user to enable the execution of JP1/AJS3 commands in JP1/AJS3 - View. For details, see 11.3.18 Allowing execution of JP1/AJS3 commands in the JP1/Automatic Job Management System 3 Operator's Guide.

#4

For details, see 23.1 Preparation for using an embedded database in the JP1/Automatic Job Management System 3 Configuration Guide.

#5

This file is created by the user to display the information about the connection-destination manager host in a window of JP1/AJS3 - View. For details, see 11.3.19 Displaying the information about the connection-destination manager host in the JP1/Automatic Job Management System 3 Operator's Guide.

#6

This file take effect for all of physical and logical hosts.

Even in the case of a logical host, there is no need to replace /etc/opt/jp1ajs2 with the shared directory name.

Table A‒18: Files and directories that the user can reference (JP1/AJS3 - Manager for UNIX)

Item

File or directory name

Execution file storage directory

/opt/jp1ajs2/bin/

Library file storage directory

/opt/jp1ajs2/lib/

Message catalog

/opt/jp1ajs2/lib/nls/$LANG

Environment settings file storage directory

/etc/opt/jp1ajs2/conf/#

Help file storage directory

/opt/jp1ajs2/doc/

Tool file storage directory

/opt/jp1ajs2/tools/

#

On the logical host, replace /etc/opt/jp1ajs2 with the following directory:

shared-directory/jp1ajs2

Table A‒19: Files and directories that the user does not need to modify or reference (JP1/AJS3 - Manager for UNIX)

Item

File or directory name

Job information storage directory

/var/opt/jp1ajs2/jobinf/

Database storage directory for JP1/AJS3

/var/opt/jp1ajs2/database/

Job/jobnet information storage directory

/var/opt/jp1ajs2/database/schedule/

Queue information database storage directory

/var/opt/jp1ajs2/database/Queue/

Job/jobnet information backup directory

/var/opt/jp1ajs2/backup/schedule/

System file directory for JP1/AJS3

/var/opt/jp1ajs2/sys/

System file directory for an event/action control agent

/var/opt/jp1ajs2/sys/infoagt

Information folder for an event/action control manager

/var/opt/jp1ajs2/sys/schedule/scheduler-service-name/infodir/

Work file storage directory for JP1/AJS3

/var/opt/jp1ajs2/tmp/

Folder storing the files used by the JP1/AJS3 Autonomous Agent service and JP1/AJS3 Autonomous Agent Messenger service

/opt/jp1ajs2/embsch/

/var/opt/jp1ajs2/embsch/

Embedded database files and directories#

See Table A-20.

Note

On the logical host, replace /var/opt/jp1ajs2 with the following directory:

shared-directory/jp1ajs2

#

The system common definition and single server definition for the embedded database are exceptions.

Table A‒20: Embedded database files and directories (for UNIX)

Item

File or directory name

Executable file storage directory

Embdb_Path/bin

Library file storage directory

Embdb_Path/lib

Executable file library storage directory

Embdb_Path/client

Troubleshooting information storage directory

Embdb_Path/spool

Embedded database work directory

Embdb_Path/tmp

System definition file storage directory

Embdb_Path/conf

Client environment definition file storage directory

Embdb_Path/conf/emb

Embedded database settings file storage directory

Embdb_Path/conf/ajsdbst

Directory for files used by the embedded database

Embdb_Path/conf/Inittab

Embdb_Path/.dbenv

/dev/HiRDB/pth

Data area directory

Embdb_Path/dbarea#

System file area directory

Embdb_Path/dbarea#

Work area directory

Embdb_Path/dbarea#

#

These folders are automatically created when setup is performed during installation or the setup command is executed. The paths of the created folders differ depending on the options specified in the setup command. For details, see 2.6.5 Database settings that are set up in JP1/AJS3 in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

(b) Files and directories when HP NNM linkage is used

Table A‒21: Files and directories that the user can modify or reference (when JP1/AJS3 - Manager for UNIX and HP NNM linkage are used)

Item

File or directory name

Definition file for linkage with HP NNM

/etc/opt/jp1ajs2/conf/jpoov.conf

(Environment definition)

Note

On the logical host, replace /etc/opt/jp1ajs2 with the following directory:

shared-directory/jp1ajs2

Table A‒22: Files and directories that the user does not need to modify or reference (when JP1/AJS3 - Manager for UNIX and HP NNM linkage are used)

Item

File or directory name

Definition directory for linkage with HP NNM

/etc/opt/jp1ajs2/OV/

Definition file for linkage with HP NNM

/etc/opt/jp1ajs2/OV/jp1ajs2_f

(Field definition)

/etc/opt/jp1ajs2/OV/snmpd.extend

(MIB object definition)

/etc/opt/jp1ajs2/OV/trustajs2

(Trusted command definition)

/etc/opt/jp1ajs2/OV/$LANG/jp1ajs2

(Menu definition)

/etc/opt/jp1ajs2/OV/$LANG/trpcajs2

(Event definition )

/etc/opt/jp1ajs2/OV/$LANG/jajsovm.cat

(Message catalog)

(c) Files and directories when mail linkage is used

Table A‒23: Files that the user references, and must manage deleting during operation (when JP1/AJS3 - Manager for UNIX and mail linkage are used)

Item

File name

Default passing-information file#1

/var/opt/jp1ajs2/sys/infoagt/tmp/infodir/mail/MLDT*

Failed mail file for mail linkage#2

/var/opt/jp1ajs2/sys/infoagt/tmp/mail/errmail

Temporary mail file for mail linkage#2

/var/opt/jp1ajs2/tmp/mailbox/monitored-user-name

Note

On the logical host, replace /var/opt/jp1ajs2 with the following directory:

shared-directory/jp1ajs2

#1

This file is used if you do not specify the EvjobInfFile environment setting parameter.

If you specify the EvjobInfFile environment setting parameter, the system creates the mail directory under the specified directory and uses it.

#2

The data in the file increases uniformly when mail linkage is used.

Table A‒24: Directories that the user can reference (when JP1/AJS3 - Manager for UNIX and mail linkage are used)

Item

Directory name

Default passing-information file directory#

/var/opt/jp1ajs2/sys/infoagt/tmp/infodir/mail/

Temporary mail file directory for mail linkage

/var/opt/jp1ajs2/tmp/mailbox/

Note

On the logical host, replace /var/opt/jp1ajs2 with the following directory:

shared-director/jp1ajs2

#

This directory is used if you do not specify the EvjobInfFile environment setting parameter.

If you specify the EvjobInfFile environment setting parameter, the system creates the mail directory under the specified directory and uses it.

(d) Files and directories when Unix jobs are used

Table A‒25: Files that the user references, and for which deletion must be managed during operation (when JP1/AJS3 - Manager for UNIX and Unix jobs are used)

Item

File name

Standard output file#1

Defined by the user

Standard error output file#2

Defined by the user

#1

This file is used when you open the Define Details - [UNIX Job] dialog box, choose the Definition page, and specify a desired file name in Standard output. The data increases uniformly when you select Append in Standard output.

#2

This file is used when you open the Define Details - [UNIX Job] dialog box, choose the Definition page, and specify a desired file name in Standard error. The data increases uniformly when you select Append in Standard error.

(e) Files and directories when HTTP connection jobs are used

Table A‒26: Files that the user references and files whose deletion must be managed during operation (when JP1/AJS3 - Manager for UNIX and an HTTP connection job are used)

Item

File name

Standard output file#1

Defined by the user

Standard error output file#2

Defined by the user

#1

This file is used when you open the Define Details - [HTTP Connection Job] dialog box, choose the Definition page, and specify a desired file name in Standard output.

#2

This file is used when you open the Define Details - [HTTP Connection Job] dialog box, choose the Definition page, and specify a desired file name in Standard error.

(f) Files and directories when JP1/AJS3 Console Manager is used

Table A‒27: Files that the user can create and modify (when JP1/AJS3 - Manager for UNIX and JP1/AJS3 Console Manager is used)

Item

File or directory name

Environment settings file for JP1/AJS3 Console Manager

/etc/opt/jp1ajs2cm/conf/ajs2cm.conf

Table A‒28: Files and directories that the user can reference (when JP1/AJS3 - Manager for UNIX and JP1/AJS3 Console Manager are used)

Item

File or directory name

Execution file storage directory

/opt/jp1ajs2cm/bin/

/opt/jp1ajs2cm/lib/

Message catalog

/opt/jp1ajs2cm/lib/nls/$LANG

Environment settings file storage directory

/etc/opt/jp1ajs2cm/conf/

Environment settings model file for JP1/AJS3 Console Manager

/etc/opt/jp1ajs2cm/conf/ajs2cm.conf.model

Table A‒29: Files and directories that the user does not need to modify or reference (when JP1/AJS3 - Manager for UNIX and JP1/AJS3 Console Manager are used)

Item

File or directory name

Data directory

/var/opt/jp1ajs2cm/database

Note

On the logical host, replace /var/opt/jp1ajs2cm with the following directory:

shared-directory/jp1ajs2cm

Table A‒30: Log file storage directories(when JP1/AJS3 - Manager for UNIX and JP1/AJS3 Console Manager are used)

Item

File or directory name

Log file storage directory

/var/opt/jp1ajs2cm/log

(g) Files and directories when JP1/AJS3 Console Agent is used

Table A‒31: Files and directories for JP1/AJS3 Console Agent (JP1/AJS3 Console Agent for UNIX)

Item

File or directory name

Temporary file storage directory for JP1/AJS3 Console Agent

/var/opt/jp1ajs2/tmp/console_agent

Execution file

/opt/jp1ajs2/bin/ajsca*#

/opt/jp1ajs2/bin/jp1ajs2casetup

/opt/jp1ajs2/lib/libAjsca*#

Message catalog

/opt/jp1ajs2cm/lib/nls/$LANG

Automatic start/termination script

/etc/opt/jp1ajs2/jajsca_start.model

/etc/opt/jp1ajs2/jajsca_start

/etc/opt/jp1ajs2/jajsca_stop.model

/etc/opt/jp1ajs2/jajsca_stop

Start/termination script for JP1/AJS3 Console Agent service

/etc/opt/jp1ajs2/ajscainetd_startstop

Environment settings model file for JP1/AJS3 Console Agent

/etc/opt/jp1ajs2/conf/ajs2ca.conf.model

Environment settings file for JP1/AJS3 Console Agent

/etc/opt/jp1ajs2/conf/ajs2ca.conf

Log file storage directory

/var/opt/jp1ajs2/log

#

An asterisk (*) indicates a string of one or more characters.

(h) Files and directories when an external database is used

Table A‒32: Files that the user references, and for which deletion must be managed during operation (when JP1/AJS3 - Manager for UNIX and when an external database is used)

Item

Directory name

Standard output file#1

In the directory#3 that contains the standard output file and the standard error output file

Standard error output file#2

#1

This is created if the ajsshow command is executed with -i %so specified.

#2

This is created if the ajsshow command is executed with -f %r or -r specified.

#3

Replace the specification of the directory that contains the standard output file and the standard error output file, with the value specified for the STDFILEOUTDIR environment setting parameter in the [JP1_DEFAULT\JP1AJSMANAGER\scheduler-service-name] definition key. For details about the STDFILEOUTDIR environment setting parameter, see 20.4.2(126) STDFILEOUTDIR in the JP1/Automatic Job Management System 3 Configuration Guide.

A.2 JP1/AJS3 - Agent files and directories

The following table lists the JP1/AJS3 - Agent files and directories for each OS.

(1) In Windows

The following table lists the files and folders for the Windows version of JP1/AJS3 - Agent according to their uses.

Supplementary note

For the tables listing log files and directories, see 1.2.5 List of log files and directories.

How to read the tables

The tables listing files and directories use the following abbreviations:

- Agt_Path: JP1/AJS3 - Agent installation folder

- Agt_Data_Path: The value is different depending on the installation folder.

If the installation folder is the default installation folder or is in a folder protected by the system:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2

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)

If the installation folder is other than the above:

JP1/AJS3 - Agent installation folder

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

By default, Agt_Path is SystemDrive\Program files (x86)\HITACHI\jp1ajs2.

By default, Base_Path is SystemDrive\Program files (x86)\HITACHI\jp1base.

An asterisk (*) indicates a string of one or more characters.

(a) Common files and folders

Table A‒33: Files that the user can modify (JP1/AJS3 - Agent for Windows)

Item

File name

JP1/AJS3 startup process definition file

Agt_Path\conf\jp1ajs_spmd.conf

JP1/AJS3 extended startup process definition file

Agt_Path\conf\jp1ajs_service_0700.conf

JP1/AJS3 system management event definition file

Agt_Path\conf\jp1ajs_param.conf

Note

On the logical host, replace Agt_Path with the following folder:

shared-folder/jp1ajs2

Table A‒34: Files and folders that the user can reference (JP1/AJS3 - Agent for Windows)

Item

File or folder name

Execution file storage folder

Agt_Path\bin\

Library file storage folder

Agt_Path\lib\

Environment-settings file storage folder

Agt_Path\conf\

Readme file

Agt_Path\Readme_ja.txt

Agt_Path\Readme_en.txt

Version information file

Agt_Path\Version.txt

Note

On the logical host, replace Agt_Path with the following folder:

shared-folder/jp1ajs2

Table A‒35: Files and folders that the user does not need to modify or reference (JP1/AJS3 - Agent for Windows)

Item

File or folder name

System file folder for JP1/AJS3

Agt_Data_Path\sys\

System file folder for an event/action control agent

Agt_Data_Path\sys\infoagt

Work file storage folder for JP1/AJS3

Agt_Data_Path\tmp\

Product information file storage folder

system-drive\Program Files (x86)\HITACHI\jp1common\JP1AJS2

Profile storage folder for sending emails without using Outlook

profile-storage-folder#\sys\prf

Folder storing the files used by the JP1/AJS3 Autonomous Agent service and JP1/AJS3 Autonomous Agent Messenger service

Agt_Path\embsch\

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\embsch\

Note

On the logical host, replace Agt_Data_Path with the following folder:

shared-folder/jp1ajs2

#

For profile-storage-folder, substitute the value set for the WaitInfFileOutDir environment setting parameter of the [{JP1_DEFAULT|logical-host-name}\JP1AOMAGENT] definition key. For details about the WaitInfFileOutDir environment setting parameter, see 20.6.2(16) WaitInfFileOutDir (for agent processes) in the JP1/Automatic Job Management System 3 Configuration Guide.

(b) Files when HP NNM linkage is used

Table A‒36: Files that the user can modify or reference (when JP1/AJS3 - Agent for Windows and HP NNM linkage are used)

Item

File name

Definition file for linkage with HP NNM

Agt_Path\conf\jpoov.conf

(Environment definition)

Note

On the logical host, replace Agt_Path with the following folder:

shared-folder/jp1ajs2

Table A‒37: Files that the user does not need to modify or reference (when JP1/AJS3 - Agent for Windows and HP NNM linkage are used)

Item

File name

Definition file for linkage with HP NNM

Agt_Path\bin\jp1ajs2_f

(Field definition)

Agt_Path\bin\snmpd.extend

(MIB object definition)

Agt_Path\bin\jp1ajs2_j

(Menu definition for Japanese)

Agt_Path\bin\jp1ajs2_e

(Menu definition for English)

Agt_Path\bin\trpcajs2j

(Event definition for Japanese)

Agt_Path\bin\trpcajs2e

(Event definition for English)

Agt_Path\bin\trustajs2

(Trusted command definition)

(c) Files and folders when mail linkage is used

Table A‒38: Files and folders that the user references, and for which deletion must be managed during operation (when JP1/AJS3 - Agent for Windows and mail linkage are used)

Item

File or folder name

Default passing-information file#1

Agt_Data_Path\tmp\infodir\mail\JPO*.tmp

Storage folder for a file attached to mail for inherited information of an email reception monitoring job#2

Agt_Data_Path\tmp\infodir\mail\*_*\

Note

On the logical host, replace Agt_Data_Path with the following folder:

shared-folder/jp1ajs2

#1

This file is used if you do not specify the EvjobInfFile environment setting parameter.

If you specify the EvjobInfFile environment setting parameter, the system creates the mail folder under the specified folder and uses it.

For details about the list of files attached to received email to be stored in the directory for storing passed event or job information, see 2.6.3 List file for email reception monitoring job (Windows only) in the JP1/Automatic Job Management System 3 Linkage Guide.

#2

In this folder, the files attached to the mail are stored with the file names they had when attached.

Table A‒39: Folders that the user can reference (when JP1/AJS3 - Agent for Windows and mail linkage are used)

Item

Folder name

Default passing-information file folder#

Agt_Data_Path\tmp\infodir\mail\

Note

On the logical host, replace Agt_Data_Path with the following folder:

shared-folder/jp1ajs2

#

This folder is used if you do not specify the EvjobInfFile environment setting parameter.

If you specify the EvjobInfFile environment setting parameter, the system creates the mail folder under the specified folder and uses it.

(d) Files and folders when PC jobs are used

Table A‒40: Files that the user references, and for which deletion must be managed during operation (when JP1/AJS3 - Agent for Windows and PC jobs are used)

Item

File name

Standard output file#1

Defined by the user

Standard error output file#2

Defined by the user

#1

This file is used when you open the Define Details - [PC Job] dialog box, choose the Definition page, and specify a desired file name in Standard output. The data increases uniformly when you select Append in Standard output.

#2

This file is used when you open the Define Details - [PC Job] dialog box, choose the Definition page, and specify a desired file name in Standard error. The data increases uniformly when you select Append in Standard error.

(e) Files and folders when HTTP connection jobs are used

Table A‒41: Files that the user references, and for which deletion must be managed during operation (when JP1/AJS3 - Agent for Windows and HTTP connection jobs are used)

Item

File name

Standard output file#1

Defined by the user

Standard error output file#2

Defined by the user

#1

This file is used when you open the Define Details - [HTTP Connection Job] dialog box, choose the Definition page, and specify a desired file name in Standard output.

#2

This file is used when you open the Define Details - [HTTP Connection Job] dialog box, choose the Definition page, and specify a desired file name in Standard error.

(2) In UNIX

The following table lists the files and directories for the UNIX version of JP1/AJS3 - Agent according to their uses.

Supplementary note

For the tables listing log files and directories, see 1.2.5 List of log files and directories.

Note

An asterisk (*) indicates a string of one or more characters.

(a) Common files and directories

Table A‒42: Files that the user can modify (JP1/AJS3 - Agent for UNIX)

Item

File name

JP1/AJS3 startup process definition file

/etc/opt/jp1ajs2/conf/jp1ajs_spmd.conf

JP1/AJS3 extended startup process definition file

/etc/opt/jp1ajs2/conf/jp1ajs_service_0700.conf

JP1/AJS3 system management event definition file

/etc/opt/jp1ajs2/conf/jp1ajs_param.conf

Environment settings file for job execution

/etc/opt/jp1ajs2/conf/AJS3_Queue.conf

the event/action execution environment settings file

/etc/opt/jp1ajs2/conf/AJS3_EVAction.conf

Environment settings file for job execution (for compatibility with JP1/AJS2 - Agent)#

/etc/opt/jp1ajs2/conf/Queue.conf

the event/action execution environment settings file (for compatibility with JP1/AJS2 - Agent)#

/etc/opt/jp1ajs2/conf/EVAction.conf

Queueless-job execution environment settings file

/etc/opt/jp1ajs2/conf/Queueless.conf

Note

On the logical host, replace /etc/opt/jp1ajs2 with the following directory:

shared-directory/jp1ajs2

#

The environment does not include this file if the JP1/AJS3 - Agent installation is a new installation. This file is the environment file for compatibility with JP1/AJS2 - Agent, and can be used only in JP1/AJS3 - Agent after an upgrade from JP1/AJS2 - Agent.

Table A‒43: Files and directories that the user can reference (JP1/AJS3 - Agent for UNIX)

Item

File or directory name

Execution file storage directory

/opt/jp1ajs2/bin/

Library file storage directory

/opt/jp1ajs2/lib/

Message catalog

/opt/jp1ajs2/lib/nls/$LANG

Environment settings file storage directory

/etc/opt/jp1ajs2/conf/#

#

On the logical host, replace /etc/opt/jp1ajs2 with the following directory:

Shared-directory/jp1ajs2

Table A‒44: Files and directories that the user does not need to modify or reference (JP1/AJS3 - Agent for UNIX)

Item

File or directory name

System file directory for JP1/AJS3

/var/opt/jp1ajs2/sys/

System file directory for an event/action control agent

/var/opt/jp1ajs2/sys/infoagt

Work file storage directory for JP1/AJS3

/var/opt/jp1ajs2/tmp/

Folder storing the files used by the JP1/AJS3 Autonomous Agent service and JP1/AJS3 Autonomous Agent Messenger service

/opt/jp1ajs2/embsch/

/var/opt/jp1ajs2/embsch/

Note

On the logical host, replace /var/opt/jp1ajs2 with the following directory:

shared-directory/jp1ajs2

(b) Files and directories when HP NNM linkage is used

Table A‒45: Files and directories that the user can modify or reference (when JP1/AJS3 - Agent for UNIX and HP NNM linkage are used)

Item

File or directory name

Definition file for linkage with HP NNM

/etc/opt/jp1ajs2/conf/jpoov.conf

(Environment definition)

Note

On the logical host, replace /etc/opt/jp1ajs2 with the following directory:

shared-directory/jp1ajs2

Table A‒46: Files and directories that the user does not need to modify or reference (when JP1/AJS3 - Agent for UNIX and HP NNM linkage are used)

Item

File or directory name

Definition directory for linkage with HP NNM

/etc/opt/jp1ajs2/OV/

Definition file for linkage with HP NNM

/etc/opt/jp1ajs2/OV/jp1ajs2_f

(Field definition)

/etc/opt/jp1ajs2/OV/snmpd.extend

(MIB object definition)

/etc/opt/jp1ajs2/OV/trustajs2

(Trusted command definition)

/etc/opt/jp1ajs2/OV/$LANG/jp1ajs2

(Menu definition)

/etc/opt/jp1ajs2/OV/$LANG/trpcajs2

(Event definition)

/etc/opt/jp1ajs2/OV/$LANG/jajsovm.cat

(Message catalog)

(c) Files and directories when mail linkage is used

Table A‒47: Files that the user references, and for which deletion must be managed during operation (when JP1/AJS3 - Agent for UNIX and mail linkage are used)

Item

File name

Default passing-information file#1

/var/opt/jp1ajs2/sys/infoagt/tmp/infodir/mail/MLDT*

Failed mail file for mail linkage#2

/var/opt/jp1ajs2/sys/infoagt/tmp/mail/errmail

Temporary mail file for mail linkage#2

/var/opt/jp1ajs2/tmp/mailbox/monitored-user-name

Note

On the logical host, replace /var/opt/jp1ajs2 with the following directory:

shared-folder/jp1ajs2

#1

This file is used if you do not specify the EvjobInfFile environment setting parameter.

If you specify the EvjobInfFile environment setting parameter, the system creates the mail directory under the specified directory and uses it.

#2

The data in the file increases uniformly when mail linkage is used.

Table A‒48: Directories that the user can reference (when JP1/AJS3 - Agent for UNIX and mail linkage are used)

Item

Directory name

Default passing-information file directory#

/var/opt/jp1ajs2/sys/infoagt/tmp/infodir/mail/

Temporary mail file directory for mail linkage

/var/opt/jp1ajs2/tmp/mailbox/

Note

On the logical host, replace /var/opt/jp1ajs2 with the following directory:

shared-folder/jp1ajs2

#

This directory is used if you do not specify the EvjobInfFile environment setting parameter.

If you specify the EvjobInfFile environment setting parameter, the system creates the mail directory under the specified directory and uses it.

(d) Files and directories when Unix jobs are used

Table A‒49: Files that the user references, and for which deletion must be managed during operation (when JP1/AJS3 - Agent for UNIX and Unix jobs are used)

Item

File name

Standard output file#1

Defined by the user

Standard error output file#2

Defined by the user

#1

This file is used when you open the Define Details - [UNIX Job] dialog box, choose the Definition page, and specify a desired file name in Standard output. The data increases uniformly when you select Append in Standard output.

#2

This file is used when you open the Define Details - [UNIX Job] dialog box, choose the Definition page, and specify a desired file name in Standard error. The data increases uniformly when you select Append in Standard error.

(e) Files and directories when HTTP connection jobs are used

Table A‒50: Files that the user references and files whose deletion must be managed during operation (when JP1/AJS3 - Agent for UNIX and an HTTP connection job are used)

Item

File name

Standard output file#1

Defined by the user

Standard error output file#2

Defined by the user

#1

This file is used when you open the Define Details - [HTTP Connection Job] dialog box, choose the Definition page, and specify a desired file name in Standard output.

#2

This file is used when you open the Define Details - [HTTP Connection Job] dialog box, choose the Definition page, and specify a desired file name in Standard error.

A.3 JP1/AJS3 - View files and directories

The following table lists the JP1/AJS3 - View files and folders according to their purpose.

Note that the access control settings of these files and folders must not be changed. If these files and folders become inaccessible, the following problems occur:

JP1/AJS3 - View cannot be started.

An I/O error occurs during operation of JP1/AJS3 - View.

JP1/AJS3 - View assumes that the settings files do not exist, and continues processing by using the default settings.

How to read the tables

The tables listing files and directories use the following abbreviations:

- View_Path: JP1/AJS3 - View installation folder

By default, View_Path is SystemDrive\Program files (x86)\HITACHI\JP1AJS2V.

nnnn indicates any value from 0001 to 9999.

#

For 32-bit versions of Windows, replace Program Files (x86) with Program Files.

Table A‒51: Files that the user can create and modify (JP1/AJS3 - View)

Item

File name

User-specified option file

%ALLUSERSPROFILE%#\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\conf\JP1-user-name\ajs2view_opt.conf

System common settings file

%ALLUSERSPROFILE%#\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\conf\ajs2view_common.conf

Custom job extended settings file

%ALLUSERSPROFILE%#\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir\custom-job-name.cjx

File for specifying the names of the hosts that use non-encrypted communication

View_Path\conf\ssl\nosslhost.conf

#

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

Table A‒52: Files and folders that the user can reference (JP1/AJS3 - View)

Item

File or folder name

Environment-settings file storage folder

View_Path\conf\

%ALLUSERSPROFILE%#\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\conf

Model file for the user-specified option file

View_Path\conf\ajs2view_opt_en.conf.model

Model file for the user-specified option file (for version 10-50 or earlier)

View_Path\conf\ssl\ajs2view_opt_en.conf.V10.model

Model file for the system common settings file

View_Path\conf\ajs2view_common.conf.model

JP1/AJS3 command information settings file

%ALLUSERSPROFILE%#\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\conf\JP1-user-name\ajs2view_command.conf

Wallpaper setting file

%ALLUSERSPROFILE%#\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\conf\JP1-user-name\MapBackGround\wallpaper.conf

%ALLUSERSPROFILE%#\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\conf\JP1-user-name\MapBackGround\wallpaper#nnnn.conf

Default value setting file

%ALLUSERSPROFILE%#\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\conf\JP1-user-name\ajs2view_def.conf

Custom job registration information folder

%ALLUSERSPROFILE%#\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir\

Model file for the custom job extended settings file

%ALLUSERSPROFILE%#\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\custom.dir\CJNAME.cjx.model

Log file storage folder

%ALLUSERSPROFILE%#\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\log

Readme file

View_Path\Readme_ja.txt

View_Path\Readme_en.txt

Version information file

View_Path\Version.txt

Help file storage folder

View_Path\doc\

Help index file

View_Path\doc\ja\ajsmn.htm

View_Path\doc\en\ajsmn.htm

Tool file storage folder

View_Path\tools\

File for specifying the names of the hosts that use non-encrypted communication

View_Path\conf\ssl\nosslhost.conf.model

Model file of the View customization settings file

View_Path\conf\jajsCustomizeView.model

#

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

Table A‒53: Folders that the user does not need to modify or reference (JP1/AJS3 - View)

Item

Folder name

Execution file storage folder

View_Path\bin\

Java class file storage folder

View_Path\classes\

Library file storage folder

View_Path\lib\

Image file storage folder

View_Path\image\

Add-in information folder

View_Path\addin.dir\

Resource file storage folder

View_Path\resource\

View_Path\sys\

Custom job definition work folder

system-drive\Temp

Product information file storage folder

system-drive\Program Files\HITACHI\jp1common\JP1AJS2

(In the 32-bit version of Windows)

system-drive\Program Files (x86)\HITACHI\jp1common\JP1AJS2

(In the 64-bit version of Windows)

Java GUI process information storage folder

%TEMP%#\hsperfdata_OS-user-name

#

The default value for %TEMP% is one of the following folders:

system-drive\Users\OS-user-name\AppData\Local\Temp

Table A‒54: Log files (JP1/AJS3 - View)

Item

File name

JP1/AJS3 - View log

%ALLUSERSPROFILE%#1\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\log\ajs.log

JP1/AJS3 - View information log

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

#1

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

#2

If a single instance of JP1/AJS3 - View is started, the system omits #nnnn_. If multiple instances of JP1/AJS3 - View are started concurrently, the system assigns a value from 0001 to 9999 to each instance of JP1/AJS3 - View.

When multiple instances of JP1/AJS3 - View are started concurrently, the log files are output as follows:

ajs2view1.log

ajs2view#0001_1.log

ajs2view#0002_1.log

#3

The value in{1|2} indicates the log file number, which is fixed at 2.

If the size of the file specified as 1 reaches the upper limit, log data is continuously output to the file specified as 2. If the size of the file specified as 2 also reaches the upper limit, the information in the file specified as 1 is deleted, after which log data is continuously output to this file.

(1) Files when HP NNM linkage is used

Table A‒55: Files that the user does can modify or reference (when JP1/AJS3 - View and HP NNM linkage are used)

Item

File name

Definition file for linkage with HP NNM

View_Path\conf\jpoov.conf

(Environment definition)

Table A‒56: Files that the user does not need to modify or reference (when JP1/AJS3 - View and HP NNM linkage are used)

Item

File name

Definition file for linkage with HP NNM

View_Path\bin\jp1ajs2_f

(Field definition)

View_Path\bin\snmpd.extend

(MIB object definition)

View_Path\bin\jp1ajs2_j

(Menu definition for Japanese)

View_Path\bin\jp1ajs2_e

(Menu definition for English)

View_Path\bin\trpcajs2j

(Event definition for Japanese)

View_Path\bin\trpcajs2e

(Event definition for English)

View_Path\bin\trustajs2

(Trusted command definition)

Log for linkage with HP NNM

View_Path\log\jpoovlink{1|2}.conf

Supplementary note

Logs are output to the default folder even when a cluster is used.

(2) Files and folders when JP1/AJS3 Console View is used

Table A‒57: Folders for JP1/AJS3 Console View (when JP1/AJS3 - View and JP1/AJS3 Console View are used)

Item

File or folder name#

Folder storing Java class files for JP1/AJS3 Console View

View_Path\classes

Folder storing images for JP1/AJS3 Console View

View_Path\image\console

Folder storing background images for JP1/AJS3 Console View

View_Path\image\console\background

Folder storing icon images for JP1/AJS3 Console View

View_Path\image\console\icon

#

Folders are created in EVERYONE full control mode.

Table A‒58: Files for JP1/AJS3 Console View (when JP1/AJS3 - View and JP1/AJS3 Console View are used)

Item

File or folder name#1

Executable file for starting JP1/AJS3 Console View

View_Path\bin\ajscon.exe

Executable file for setting up JP1/AJS3 Console View

View_Path\bin\ajscvsetup.exe

JP1/AJS3 Console View common settings file

View_Path\conf\ajscon.conf

Model file for the JP1/AJS3 Console View common settings file

View_Path\conf\ajscon.conf.model

Model file for the JP1/AJS3 Console View user settings file

View_Path\conf\ajs2coview_opt.conf.model

System common settings file

%ALLUSERSPROFILE%#2\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\conf\ajs2coview_common.conf

Model file for the system common settings file

View_Path\conf\ajs2coview_common.conf.model

JP1/AJS3 Console View log file

%ALLUSERSPROFILE%#2\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\log\ajscon.log

JP1/AJS3 Console View execution log file

%ALLUSERSPROFILE%#2\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\log\ajs2coview[#nnnn_]#3{1|2}#4.log

#1

Files are created in EVERYONE full control mode.

#2

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

#3

If a single instance of JP1/AJS3 Console View is started, the system omits #nnnn_. If multiple instances of JP1/AJS3 Console View are started concurrently, the system assigns a value from 0001 to 9999 to each instance of JP1/AJS3 Console View.

When multiple instances of JP1/AJS3 Console View are started concurrently, the log files are output as follows:

ajs2coview1.log

ajs2coview#0001_1.log

ajs2coview#0002_1.log

#4

The value in{1|2} indicates the log file number, which is fixed at 2.

If the size of the file specified as 1 reaches the upper limit, log data is continuously output to the file specified as 2. If the size of the file specified as 2 also reaches the upper limit, the information in the file specified as 1 is deleted, after which log data is continuously output to this file.

A.4 JP1/AJS3 - Web Console files and directories

The following table lists the JP1/AJS3 - Web Console files and directories for each OS.

(1) In Windows

The following table lists the files and folders for the Windows version of JP1/AJS3 - Web Console according to their uses.

Supplementary note

For the tables listing log files and directories, see 1.2.5 List of log files and directories.

How to read the tables

The tables listing files and directories use the following abbreviations:

- Web_Path: JP1/AJS3 - Web Console installation folder

- Web_Data_Path: The value is different depending on the installation folder.

If the installation folder is the default installation folder or is in a folder protected by the system:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS3web

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

If the installation folder is other than the above:

JP1/AJS3 - Web Console installation folder

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

By default, Web_Path is SystemDrive\Program files\HITACHI\JP1AJS3WEB.

An asterisk (*) indicates a string of one or more characters.

Table A‒59: Files that the user can modify (JP1/AJS3 - Web Console for Windows)

Item

File name

Environment-settings file

Web_Path\conf\ajs3web.conf

Communication -settings file

Web_Data_Path\conf\ajscd_ajs3web.properties

File for specifying the names of the hosts that use non-encrypted communication#

Web_Data_Path\conf\nosslhost.conf

HTTP server definition file

Web_Path\uCPSB\httpsd\conf\httpsd.conf

User properties file for J2EE server

Web_Path\uCPSB\CC\server\usrconf\ejb\ajs3web\usrconf.properties

Display color settings file

Web_Path\conf\ajs3web_color.conf

Option definition file for J2EE server

Web_Path\uCPSB\CC\server\usrconf\ejb\ajs3web\usrconf.cfg

#

This file is created by a user if encryption of communication is to be used. For details about this file, see 21.4.6 Details on the settings in the unencrypted-communication host settings file (nosslhost.conf) in the JP1/Automatic Job Management System 3 Configuration Guide.

Table A‒60: Files and folders that the user can reference (JP1/AJS3 - Web Console for Windows)

Item

File or folder name

Executable file storage folder

Web_Path\bin\

Library file storage folder

Web_Path\lib\

Environment-settings file storage folder

Web_Path\conf\

Web_Data_Path\conf\

Readme file

Web_Path\Readme_ja.txt

Web_Path\Readme_en.txt

Version information file

Web_Path\Version.txt

HTTP and Application server folder

Web_Path\uCPSB\

Tool folder

Web_Path\tools\

Table A‒61: Files and folders that the user does not need to modify or reference (JP1/AJS3 - Web Console for Windows)

Item

File or folder name

System folder for Web Console server

Web_Path\sys\

Application folder

Web_Path\webapps\

Working folder for Web Console server

Web_Data_Path\tmp\

(2) In Linux

The following table lists the files and directories for the Linux version of JP1/AJS3 - Web Console according to their uses.

Supplementary note

For the tables listing log files and directories, see 1.2.5 List of log files and directories.

How to read the tables

An asterisk (*) indicates a string of one or more characters.

Table A‒62: Files that the user can modify (JP1/AJS3 - Web Console for Linux)

Item

File name

Environment-settings file

/etc/opt/jp1ajs3web/conf/ajs3web.conf

Communication -settings file

/etc/opt/jp1ajs3web/conf/ajscd_ajs3web.properties

File for specifying the names of the hosts that use non-encrypted communication#

/etc/opt/jp1ajs3web/conf/nosslhost.conf

HTTP server definition file

/opt/jp1ajs3web/uCPSB/httpsd/conf/httpsd.conf

User properties file for J2EE server

/opt/jp1ajs3web/uCPSB/CC/server/usrconf/ejb/ajs3web/usrconf.properties

Display color settings file

/etc/opt/jp1ajs3web/conf/ajs3web_color.conf

Option definition file for J2EE server

/opt/jp1ajs3web/uCPSB/CC/server/usrconf/ejb/ajs3web/usrconf.cfg

#

This file is created by a user if encryption of communication is to be used. For details about this file, see 21.4.6 Details on the settings in the unencrypted-communication host settings file (nosslhost.conf) in the JP1/Automatic Job Management System 3 Configuration Guide.

Table A‒63: Files and directories that the user can reference (JP1/AJS3 - Web Console for Linux)

Item

File or directory name

Executable file storage directory

/opt/jp1ajs3web/bin/

Library file storage directory

/opt/jp1ajs3web/lib/

Message catalog

/opt/jp1ajs3web/lib/nls/$LANG/

Environment settings file storage directory

/etc/opt/jp1ajs3web/conf/

HTTP and Application server folder

/opt/jp1ajs3web/uCPSB/

Tool folder

/opt/jp1ajs3web/tools/

Table A‒64: Files and directories that the user does not need to modify or reference (JP1/AJS3 - Web Console for Linux)

Item

File or directory name

System directory for Web Console server

/var/opt/jp1ajs3web/sys/

Application directory

/opt/jp1ajs3web/webapps/

Installation results storage directory

/opt/jp1ajs3web/sys

Working directory for Web Console server

/var/opt/jp1ajs3web/tmp/

Environment settings file storage directory

/var/opt/jp1ajs3web/conf

B. List of Processes

This appendix lists the JP1/AJS3 processes.

B.1 Configuration of processes

The figure below shows the configuration of JP1/AJS3 processes (UNIX). The figure illustrating the overall relationship between parent and child processes should be helpful in monitoring processes.

(1) Processes in the JP1/AJS3 (UNIX)

Figure B‒1: JP1/AJS3 processes (UNIX) (parent and child processes)

Figure B‒2: JP1/AJS3 processes (child and detail processes) (1/3)

Figure B‒3: JP1/AJS3 processes (child and detail processes) (2/3)

Figure B‒4: JP1/AJS3 processes (child and detail processes) (3/3)

B.2 Processes (for Windows)

The following table lists the processes of JP1/AJS3 programs and components for Windows.

(1) Processes of JP1/AJS3 - Manager for Windows

There are three kinds of processes of JP1/AJS3 - Manager for Windows:

Parent process

A parent process consists of several child processes.

Child process

A child process consists of several detail processes.

Detail process

You can use the jajs_spmd_status command to check the status of the child processes of jajs_spmd. For details, see the description of jajs_spmd_status in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

You can check the status of parent, child, and detail processes on the Processes page in the Task Manager window.

Table B-1 lists the parent and child processes. Table B-2 lists the child and detail processes. The number following a parent or child process name indicates the maximum number of processes you can activate concurrently.

Table B‒1: Parent and child processes of JP1/AJS3 - Manager for Windows

Parent process

(number of processes)

Description

Child process

(number of processes)

Description

jajs_spmd.exe(1)#1

JP1/AJS3 service

jajs_dbmd.exe(number-of-embedded-databases)

Database management

This process manages embedded databases.

jajs_hstd.exe(1)

Host service management

jajs_schd.exe(number-of-scheduler-services)

Scheduler service management

jajs_agtd.exe(1)

Agent service management

ajsqlagtd.exe(1)#2

JP1/AJS3 Queueless Agent service (queueless agent process)

This process accepts queueless job execution requests from JP1/AJS3 - Manager (scheduler service).

This process is necessary when queueless jobs are executed on the local host.

- (number-of-jobs-to-be-executed)#3

Queueless job management thread.

This thread executes queueless jobs.

The threads are generated respectively for jobs to be executed.

The threads are removed on completion of queueless job execution.

ajsqlftpd.exe(1)#4

JP1/AJS3 Queueless File Transfer service (queueless file transfer process)

This process accepts file transfer requests from the queueless job management process.

- (number-of-file-transfer-requests) #3

Queueless file transfer thread.

This thread transfers transfer files, standard output files, and standard error output files.

The threads are generated respectively for file transfer requests.

The threads are removed on completion of file transfer.

jpomlsrv.exe

JP1/AJS3 Mail service

Mail monitoring process when the mail system linkage function is used within the service

jpomlapisend.exe

Process for email transmission by linkage to a mail system.

This process places new emails in the Outlook Outbox.

The process starts each time a mail sending job is executed.

jpomlapirec.exe

Process for email reception monitoring by linkage to a mail system.

This process determines whether the received email matches the conditions defined in the email reception monitoring job by referencing the Outlook Inbox.

The process starts at the specified monitoring interval when a mail reception monitoring job is executed.

jpomldsk.exe

JP1/AJS3 email monitoring process

Mail monitoring process when the mail system linkage function is used on the desktop

jpomlapisend2.exe

Process for email transmission by linkage to a mail system.

This process places new emails in the Outlook Outbox.

The process starts each time a mail sending job is executed.

jpomlapirec2.exe

Process for email reception monitoring by linkage to a mail system.

This process determines whether the received email matches the conditions defined in the email reception monitoring job by referencing the Outlook Inbox.

The process starts at the specified monitoring interval when a mail reception monitoring job is executed.

ajschkmansvc.exe (1)

JP1/AJS3 Check Manager service

ajschkmand.exe (1)

This process controls the definition pre-check (manager process).

ajschkagtsvc.exe (1)

JP1/AJS3 Check Agent service

ajschkagtd.exe (1)

This process controls the definition pre-check (agent process).

as_service.exe (1)

Flexible job execution process

as_manager.exe (1)

JP1/AJS3 Autonomous Agent service process

as_iescscm.exe (1)

Flexible job execution process

as_iescsvr.exe (1)

JP1/AJS3 Autonomous Agent Messenger service process

ajssysctlmd.exe(1)#5

Management portal execution environment (manager process)

ajssysctlmrc.exe

Process started when JP1/AJS3 - Web Console performs an operation for management portal

ajssysctlad.exe(1)#6

Management portal execution environment (agent process)

ajssysctlarc.exe

Process started when JP1/AJS3 - Web Console performs an operation for management portal

#1

jajs_service.exe is available as the management process.

#2

ajsqlasvc.exe is available as the management process.

#3

Threads are spawned instead of child processes. The number of threads is indicated in parentheses.

#4

ajsqlfsvc.exe is available as the management process.

#5

ajssysctlmsvc.exe is available as the management process.

#6

ajssysctlasvc.exe is available as the management process.

Table B‒2: Child and detail processes of JP1/AJS3 - Manager for Windows

Child process name

Detail process name

(number of processes)

Description

jajs_dbmd.exe

ajsdbmgrd.exe

Database operation control

This process starts, stops, and monitors embedded databases.

jajs_hstd.exe

ajshlogd.exe

Host service-specific log management

ajsinetd.exe

Network control process that controls access from other servers such as JP1/AJS3 - View

ajscdinetd.exe#1

Network control process that controls access from JP1/AJS3 - Web Console

ajsnetwd.exe

Communication control and management

ajsagtmd.exe

Agent management

ajsovstatd.exe

This process monitors JP1/AJS3 from HP NNM when HP NNM is linked.

The process has no detail process.

ajsgwmasterd.exe

This process manages the scheduler service inter-communication control process when jobnet connectors are used to control the execution order of root jobnets between different scheduler services. The scheduler service inter-communication control process enables communication between jobnet connectors and the jobnets to which they connect.

ajsagtmond.exe

Agent monitoring process

This process conducts a communication status check and communication recovery check on execution agents.

This process is generated only if the job distribution delay reduction function is enabled.

jpqman.exe

Manager process for job execution control

Main process for processing specific to job execution control, such as the reception of submit jobs

jpomanager.exe

Event/action control manager process.

This process manages event jobs.

ajsqlcltd.exe(1)#2

This process automatically attaches a logical host to or detaches a logical host from the queueless cluster process when nodes are switched.

The process has no detailed process.

jajs_schd.exe

ajslogd.exe

Scheduler log output process

jpqman.exe

Job execution control manager process.

Main process for the processing that is specific to job execution control, such as the reception of submit jobs.

jpomanager.exe

Event/action control manager process.

This process manages event jobs.

ajsmasterd.exe

Scheduler.

This process monitors all the processes of the scheduler service.

jajs_agtd.exe

jpqmon.exe(1)

Job execution control.

This process monitors all the processes of job execution control.

jpoagent.exe(1)

Event/action control agent process.

This process monitors and controls the monitoring processes other than jpomanager.exe. jpoagent.exe also controls monitoring processes on JP1/AJS3 - Manager.

ajsinetd.exe

ajsmonsvr.exe#3

Process to be activated when connected to JP1/AJS3 - View

ajsrcmdsvr.exe

Process to be activated when a remote jobnet is executed, when a command is executed remotely, or when a JP1/AJS3 command is executed from JP1/AJS3 - View.

ajscdinetd.exe#1

ajsmonsvr.exe#1,#4

Process that processes requests from JP1/AJS3 - Web Console

ajsrcmdsvr.exe

Process that starts when an operation is performed on an execution agent from JP1/AJS3 - Web Console

ajsgwmasterd.exe

ajsgwd.exe

This process manages the scheduler service inter-communication control process when jobnet connectors are used to control the execution order of root jobnets between different scheduler services. The scheduler service inter-communication control process enables communication between jobnet connectors and the jobnets to which they connect.

jpomanager.exe

jpomgrsub.exe

Event/action control submanager process

ajsmasterd.exe

ajsschd.exe

Schedule control process

ajsschbd.exe#5

Generation management subprocess

ajsflowd.exe

Flow control process

ajssubd.exe

Job submit process

ajssubwd.exe

Job completion wait process

jpqnfyfd.exe

Status reporting process for job execution control

ajsremnetcl.exe

Process for requesting the registration of remote jobnets and the cancellation of the registration of remote jobnets

ajsreqd.exe

Queueless job request process.

A maximum of eight processes are started from ajsflowd.exe.

ajsflbd.exe#6

Flow control subprocess

jpqmon.exe

jpqagt.exe

Agent process for job execution control

This process activates jobs.

jpoagent.exe

jpoagtsub.exe

Event/action control subagent process.

This process mainly notifies the manager of information from the monitoring process.

jpocwtflMain.exe

File monitoring process

jpocwtflSub.exe

File monitoring subprocess

This process starts only if the NetworkFilewatch environment setting parameter is set to Y.

jpocwttmMain.exe

Execution interval control process

jpoeventwatch.exe

Event (such as JP1 event or log trap) monitoring process

jpoevsearch.exe

Event search process

This process starts to search for the specified event when a JP1 event reception monitoring job specified with a pre-execution event search is executed.

jpocwtmlmain.exe #7

Process for mail monitoring communication by linkage to a mail system

jpomlapisend.exe #8

Process for mail transmission by linkage to a mail system (when the mail system linkage function is used within the service)

jpomlapisend2.exe #8

Process for mail transmission by linkage to a mail system (when the mail system linkage function is used on the desktop)

jpomlapirec.exe #9

Process for mail reception by linkage to a mail system (when the mail system linkage function is used within the service)

jpomlapirec2.exe #9

Process for mail reception by linkage to a mail system (when the mail system linkage function is used on the desktop)

as_manager.exe (1)

as_player.exe (number of jobs to be executed + 2)

Flexible job execution process

as_player.exe

ajsfxexec.exe

Flexible job execution process

ajsfxdstr.exe

Process for broadcast execution of flexible jobs

ajsfxbcctl.exe

Process that manages the destination agents for broadcast execution of flexible jobs

Note

When you execute a command, a process with the same name as the command is activated.

#1

If you perform an upgrade installation from JP1/AJS3 - Manager version 10 or earlier, this process is not started automatically by using the initial settings. If you want the process to be started automatically, you must edit the JP1/AJS3 startup process definition file (jp1ajs_hstd.conf).

For details, see 3.4.1 Setting up JP1/AJS3 - Manager in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows) or 13.3.1 Setting up JP1/AJS3 - Manager in the JP1/Automatic Job Management System 3 Configuration Guide (for UNIX).

#2

Indicated as qlcltd by the jajs_spmd_status command.

When queueless jobs are used, the ajsqlcltd.exe process is created only if the jp1ajs_hstd.conf file is edited to automatically attach and detach the logical host. For details, see 8.2.7 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

#3

One process starts for the selected scheduler service when you select a scheduler service in the tree area in a JP1/AJS3 - View window.

The maximum number of processes that can start is number-of-scheduler-services x number-of-connected-instances-of-JP1/AJS3 - View.

#4

One process starts for the scheduler service that is referenced by JP1/AJS3 - Web Console.

The maximum number of processes that can start is number-of-scheduler-services x number-of-connected-instances-of-JP1/AJS3 - Web Console.

#5

This process starts only when you specify the environment settings as described in 6.1.7 Changing the mode in which unregistration or generation management deletes the generations of a jobnet in the JP1/Automatic Job Management System 3 Configuration Guide.

#6

This process starts only when you specify the environment settings as described in 6.1.8 Settings for using wait conditions in the JP1/Automatic Job Management System 3 Configuration Guide.

#7

This process does not start if the mail system linkage function is disabled. For details about how to set up the mail system linkage function, see 2.3.4 Setting up the environment for the mail system linkage in the JP1/Automatic Job Management System 3 Linkage Guide.

Note that you cannot start multiple instances of this process on the same PC.

#8

This process determines whether the received email matches the conditions defined in the email reception monitoring job by referencing the Outlook Inbox. The process starts each time a mail sending job is executed.

#9

This process checks the Outlook Inbox, and detects the reception of emails. The process starts at the specified monitoring interval when a mail reception monitoring job is executed.

(2) Processes of JP1/AJS3 - Agent for Windows

There are three kinds of processes of JP1/AJS3 - Agent for Windows:

Parent process

A parent process consists of several child processes.

Child process

A child process consists of several detail processes.

Detail process

You can use the jajs_spmd_status command to check the status of the child processes of jajs_spmd. For details, see the description of jajs_spmd_status in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

You can check the status of parent, child, and detail processes on the Processes page in the Task Manager window.

Table B-3 lists the parent and child processes. Table B-4 lists the child and detail processes. The number following a parent or child process name indicates the maximum number of processes you can activate concurrently.

Table B‒3: Parent and child processes of JP1/AJS3 - Agent for Windows

Parent process

(number of processes)

Description

Child process

(number of processes)

Description

jajs_spmd.exe

(1) #1

JP1/AJS3 service

jpoagent.exe

(1) #2

Even/action control agent process

jpqmon.exe

(1) #3

Job execution control

This process monitors all processes for job execution control.

ajsqlcltd.exe

(1) #4

This process automatically attaches a logical host to or detaches a logical host from the queueless cluster process when nodes are switched.

The process has no detail process.

ajsqlagtd.exe(1)#5

JP1/AJS3 Queueless Agent service (queueless agent process)

This process accepts queueless job execution requests from JP1/AJS3 - Manager (scheduler service).

- (number-of-jobs-to-be-executed) #6

Queueless job management thread

This thread executes queueless jobs.

The threads are generated respectively for jobs to be executed.

The threads are removed on completion of queueless job execution.

jpomlsrv.exe

JP1/AJS3 Mail service

Mail monitoring process when the mail system linkage function is used within the service

jpomlapisend.exe

Process for email transmission by linkage to a mail system.

This process places new emails in the Outlook Outbox.

The process starts each time a mail sending job is executed.

jpomlapirec.exe

Process for email reception monitoring by linkage to a mail system.

This process determines whether the received email matches the conditions defined in the email reception monitoring job by referencing the Outlook Inbox.

The process starts at the specified monitoring interval when a mail reception monitoring job is executed.

jpomldsk.exe

JP1/AJS3 email monitoring process

Mail monitoring process when the mail system linkage function is used on the desktop

jpomlapisend2.exe

Process for email transmission by linkage to a mail system.

This process places new emails in the Outlook Outbox.

The process starts each time a mail sending job is executed.

jpomlapirec2.exe

Process for email reception monitoring by linkage to a mail system.

This process determines whether the received email matches the conditions defined in the email reception monitoring job by referencing the Outlook Inbox.

The process starts at the specified monitoring interval when a mail reception monitoring job is executed.

ajschkagtsvc.exe (1)

JP1/AJS3 Check Agent service

ajschkagtd.exe (1)

This process controls the definition pre-check (agent process).

as_service.exe (1)

Flexible job execution process

as_manager.exe (1)

JP1/AJS3 Autonomous Agent service process

as_iescscm.exe (1)

Flexible job execution process

as_iescsvr.exe (1)

JP1/AJS3 Autonomous Agent Messenger service process

ajssysctlad.exe(1)#7

Management portal execution environment (agent process)

ajssysctlarc.exe

Process started when JP1/AJS3 - Web Console performs an operation for management portal

#1

jajs_service.exe is available as the management process.

#2

Indicated as evactiona by the jajs_spmd_status command.

#3

Indicated as queue by the jajs_spmd_status command.

#4

Indicated as qlcltd by the jajs_spmd_status command.

When queueless jobs are used, the ajsqlcltd.exe process is created only if the jp1ajs_hstd.conf file is edited to automatically attach and detach the logical host. For details, see 8.2.7 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

#5

ajsqlasvc.exe is available as the management process.

#6

Threads are spawned instead of child processes. The number of threads is indicated in parentheses.

#7

ajssysctlasvc.exe is available as the management process.

Table B‒4: Child and detail processes of JP1/AJS3 - Agent for Windows

Child process name

Detail process name

Description

jpoagent.exe

jpoagtsub.exe

Event/action control subagent process.

This process mainly notifies the manager of information from the monitoring process.

jpocwtflMain.exe

File monitoring process

jpocwtflSub.exe

File monitoring subprocess

This process starts only if the NetworkFilewatch environment setting parameter is set to Y.

jpocwttmMain.exe

Execution interval control process

jpocwtmlmain.exe #1

Process for mail monitoring communication by linkage to a mail system

jpoeventwatch.exe

Event (such as JP1 event or log trap) monitoring process

jpomlapisend.exe #2

Process for mail transmission by linkage to a mail system (when the mail system linkage function is used within the service)

jpomlapisend2.exe #2

Process for mail transmission by linkage to a mail system (when the mail system linkage function is used on the desktop)

jpomlapirec.exe #3

Process for mail reception by linkage to a mail system (when the mail system linkage function is used within the service)

jpomlapirec2.exe #3

Process for mail reception by linkage to a mail system (when the mail system linkage function is used on the desktop)

jpoevsearch.exe

Event search process.

This process starts to search for the specified event when a JP1 event reception monitoring job specified with a pre-execution event search is executed.

jpqmon.exe

jpqagt.exe

Agent process for job execution control

This process activates jobs.

as_manager.exe (1)

as_player.exe

Flexible job execution process

as_player.exe

ajsfxexec.exe

Flexible job execution process

ajsfxdstr.exe

Process for broadcast execution of flexible jobs

ajsfxbcctl.exe

Process that manages the destination agents for broadcast execution of flexible jobs

Note

When you execute a command, a process with the same name as the command is activated.

#1

This process does not start if the mail system linkage function is disabled. For details about how to set up the mail system linkage function, see 2.3.4 Setting up the environment for the mail system linkage in the JP1/Automatic Job Management System 3 Linkage Guide.

Only one process can start on one machine.

#2

The process places new emails in the Outlook Outbox. The process starts each time a mail sending job is executed.

#3

This process determines whether the received email matches the conditions defined in the email reception monitoring job by referencing the Outlook Inbox. The process starts at the specified monitoring interval when a mail reception monitoring job is executed.

(3) Processes of JP1/AJS3 - View for Windows

You can check the processes of JP1/AJS3 - View for Windows, on the Processes page in the Task Manager window.

The following table lists the Processes of JP1/AJS3 - View for Windows.

Table B‒5: Processes of JP1/AJS3 - View for Windows

Process name

Description

ajs.exe

Main process for JP1/AJS3 - View

java.exe

Java GUI process for JP1/AJS3 - View

ajs2java.exe

java.exe monitoring process

(4) Processes of JP1/AJS3 - Web Console for Windows

There are three kinds of processes of JP1/AJS3 - Web Console for Windows:

Parent process

A parent process consists of several child processes.

Child process

A child process consists of several detail processes.

Detail process

You can check the status of parent, and child, and detail processes on the Processes page in the Task Manager window.

Table B-6 lists the parent and child processes. Table B-7 lists the child and detail processes. The number following a parent or child process name indicates the maximum number of processes you can activate concurrently.

Table B‒6: Parent and child processes of JP1/AJS3 Web Console for Windows

Parent process (number of processes)

Description

Child process

(number of processes)

Description

httpsd.exe(1)

JP1/AJS3 HTTP Server service

httpsd.exe(1)

Web service process

rotatelogs2.exe(3)#

Log splitting utility for web services

jajs_web_service.exe(1)

JP1/AJS3 Web Application Server service

cjstartsv.exe(1)

J2EE Server process

#

When JP1/AJS3 Web Console communicates with the client host in SSL, the number of processes is 4.

Table B‒7: Child and detail processes of JP1/AJS3 Web Console for Windows

Child process

Detail process

(number of processes)

Description

httpsd.exe

rotatelogs2.exe(3)#

Log splitting utility for web services

Note

When you execute a command, a process with the same name as the command is activated.

#

When JP1/AJS3 Web Console communicates with the client host in SSL, the number of processes is 4.

B.3 Processes (for UNIX)

The following table lists the processes of JP1/AJS3 programs and components for UNIX.

(1) Processes of JP1/AJS3 - Manager for UNIX

There are three kinds of processes of JP1/AJS3 - Manager for UNIX:

Parent process

A parent process consists of several child processes.

Child process

A child process consists of several detail processes.

Detail process

You can use the jajs_spmd_status command to check the status of the child processes of jajs_spmd. For details, see the description of jajs_spmd_status in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

To check the status of parent, child and detail processes, use the ps command.

Table B-8 lists the parent and child processes. Table B-9 lists the child and detail processes. The number following a parent or child process name indicates the maximum number of processes you can activate concurrently.

Table B‒8: Parent and child processes of JP1/AJS3 - Manager for UNIX

Parent process

(number of processes)

Description

Child process

(number of processes)

Description

jajs_spmd

(1)#1

JP1/AJS3 service

jajs_dbmd_embedded-database-setup-ID(1)#2

Database management

This process manages embedded databases.

jajs_hstd(1)

Host service management

jajs_schd_scheduler-service-name(1)#3

Scheduler service management

jajs_agtd(1)

Agent service management

ajsqlagtd(1)

JP1/AJS3 Queueless Agent service (queueless agent process)

This process accepts queueless job execution requests from JP1/AJS3 - Manager (scheduler service).

ajsqlagtd (number-of-jobs-to-be-executed)

Queueless job management process

This process executes queueless jobs.

The same process names are generated from the JP1/AJS3 Queueless Agent service (queueless agent process) respectively for jobs to be executed.

The process is removed on completion of queueless job execution.

The process has no detail process.

The process is necessary when the local host executes queueless jobs.

ajsqlftpd(1)

JP1/AJS3 Queueless File Transfer service (queueless file transfer process)

This process accepts file transfer requests from the queueless job management process.

ajsqlftpd (number-of-file-transfer-requests)

Queueless file transfer worker process

This process transfers transfer files, standard output files and standard error output files.

The same process names are generated from the JP1/AJS3 Queueless File Transfer service (queueless file transfer process) respectively for file transfer requests.

The process is removed on completion of file transfer.

The process has no detail process.

ajschkmand(1)

JP1/AJS3 Check Manager service

The process controls the definition pre-check (manager process).

--

--

ajschkagtd(1)

JP1/AJS3 Check Agent service

ajschkagtd(5)

The process controls the definition pre-check (agent process).

as_manager (1)

JP1/AJS3 Autonomous Agent service process

as_player (number of jobs to be executed + 1)

Flexible job execution process

as_iescsvr (1)

JP1/AJS3 Autonomous Agent Messenger service process

--

--

ajssysctlmd(1)

Management portal execution environment (manager process)

ajssysctlmrc

Process started when JP1/AJS3 - Web Console performs an operation for management portal

ajssysctlad(1)

Management portal execution environment (agent process)

ajssysctlarc

Process started when JP1/AJS3 - Web Console performs an operation for management portal

Legend:

--: Not applicable.

#1

By specifying logical host names on the command line, you can differentiate between processes for physical hosts and for logical hosts.

A process for a logical host is represented as process-name -h logical-host-name.

For example, when a logical host name is hostA, the jajs_spmd process for hostA is represented as jajs_spmd -h hostA.

#2

The process name is indicated as jajs_dbmd_embedded-database-setup-ID.

For example, if the embedded database setup ID is_JF0, the process name is jajs_dbmd__JF0. If multiple embedded databases are used, the number of processes that start equals the number of embedded databases.

#3

The process name is indicated as jajs_schd_scheduler-service-name.

For example, if the scheduler service name is AJSROOT1, the process name is jajs_schd_AJSROOT1. If multiple scheduler services are running, the number of processes that start equals the number of scheduler services.

Table B‒9: Child and detail processes of JP1/AJS3 - Manager for UNIX

Child process name

Detail process name

Description

jajs_dbmd_embedded-database-setup-identifier

ajsdbmgrd

Database operation control

This process starts, stops, and monitors embedded databases.

jajs_hstd

ajshlogd

Host-service-specific log management

ajsinetd

Network control process that controls access from other servers

ajscdinetd#1

Network control process that controls access from JP1/AJS3 - Web Console

ajsnetwd

Communication control and management

ajsagtmd

Agent management

ajsovstatd

This process monitors JP1/AJS3 from HP NNM when HP NNM is linked.

The process has no detail process.

ajsgwmasterd

This process manages the scheduler service inter-communication control process when jobnet connectors are used to control the execution order of root jobnets between different scheduler services. The scheduler service inter-communication control process enables communication between jobnet connectors and the jobnets to which they connect.

ajsagtmond

Agent monitoring process

This process conducts a communication status check and communication recovery check on execution agents.

This process is generated only if the job distribution delay reduction function is enabled.

jpqman#2, #3

Job execution control manager process.

Main process for the processing that is specific to job execution control, such as the reception of submit jobs.

jpomanager

Event/action control manager process.

This process manages event jobs.

jajs_schd

ajslogd

Process for recording scheduler information

jpqman#2

Job execution control manager process.

Main process for the processing that is specific to job execution control, such as the reception of submit jobs.

jpomanager

Event/action control manager process.

This process manages event jobs.

ajsmasterd

Scheduler.

This process monitors all the processes of the scheduler service.

jajs_agtd

jpqmon

Job execution control.

This process monitors all the processes of job execution control.

jpoagent

Event/action control agent process.

This process monitors and controls the monitoring processes other than jpomanager. jpoagent also controls monitoring processes on JP1/AJS3 - Manager.

ajsinetd

ajsmonsvr#4

Process activated when JP1/AJS3 - View is connected. This process has no detail process.

ajsrcmdsvr

Process to be activated when a remote jobnet is executed, when a command is executed remotely, or when a JP1/AJS3 command is executed from JP1/AJS3 - View.

ajscdinetd#1

ajsmonsvr#1,#5

Process that processes requests from JP1/AJS3 - Web Console

ajsrcmdsvr

Process that starts when an operation is performed on an execution agent from JP1/AJS3 - Web Console

ajsgwmasterd#2

ajsgwd#6

Scheduler service inter-communication control process.

This process enables communication between jobnet connectors and their connection target jobnets when jobnet connectors are used to control the execution order of root jobnets between different scheduler services.

jpomanager#2

jpomgrsub#2

Event/action control submanager process

ajsmasterd

ajsschd#6

Schedule control process

ajsschbd#6, #7

Generation management subprocess

ajsflowd#6

Flow control process

ajssubd#6

Job submit process

ajssubwd#6

Job completion wait process

jpqnfyfd#2

Process for reporting the job execution control status

ajsremnetcl#6

Process for requesting the registration and the cancellation of registration of remote jobnets

ajsreqd#6

Queueless job request process.

A maximum of eight process instances start from ajsflowd.

ajsflbd#6, #8

Flow control subprocess

jpqmon#2

jpqagt#2

Agent process for job execution control

This process activates jobs.

jpqagtdmn#2

Job monitoring process activating process for job execution control

Process for activating the job monitoring process

Five processes are always activated. In a cluster system, five processes are activated for each logical host.

jpqagtchild#2

Job monitoring process for job execution control

Process for monitoring job process execution

Five processes are activated in the initial status. Also, one process is activated for each execution job. In a cluster system, five processes are activated for each logical host.

jpoagent#2

jpoagtsub#2

Event/action control subagent process.

This process mainly notifies the manager of information from the monitoring process.

jpocwtflMain#2

File monitoring process

jpocwtflSub

File monitoring subprocess

This process starts only if the NetworkFilewatch environment setting parameter is set to Y.

jpocwttmMain#2

Execution interval control process

jpoeventwatch#2

Event (such as JP1 event or log trap) monitoring process

jpoevsearch#2

Event search process

This process starts to search for the specified event when a JP1 event reception monitoring job specified with a pre-execution event search is executed.

jpocwtmlmain#2

Mail monitoring communication process

as_player

ajsfxexec

Flexible job execution process

ajsfxdst

Process for broadcast execution of flexible jobs

ajsfxbcctl

Process that manages the destination agents for broadcast execution of flexible jobs

Note

When you execute a command, a process with the same name as the command is activated.

#1

If you perform an upgrade installation from JP1/AJS3 - Manager version 10 or earlier, this process is not started automatically by using the initial settings. If you want the process to be started automatically, you must edit the JP1/AJS3 startup process definition file (jp1ajs_hstd.conf).

For details, see 3.4.1 Setting up JP1/AJS3 - Manager in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows) or 13.3.1 Setting up JP1/AJS3 - Manager in the JP1/Automatic Job Management System 3 Configuration Guide (for UNIX).

#2

A process name for a logical host is indicated as process-name logical-host-name. For example, when the logical host name is hostA, the ajsmasterd process for hostA is ajsmasterd hostA.

#3

In the case of HP-UX, AIX, and Linux, the detailed process name is jpqman32.

#4

One process starts for the selected scheduler service when you select a scheduler service in the tree area in a JP1/AJS3 - View window.

The maximum number of processes that can start is number-of-scheduler-services x number-of-connected-instances-of-JP1/AJS3 - View.

#5

One process starts for the scheduler service that is referenced by JP1/AJS3 - Web Console.

The maximum number of processes that can start is number-of-scheduler-services x number-of-connected-instances-of-JP1/AJS3 - Web Console.

#6

You can differentiate between a process for a physical host and a process for a logical host. A process name for a logical host is indicated as process-name_logical-host-name.

For example, when the logical host name is hostA, the ajsschd process for hostA is indicated as ajsschd_hostA.

#7

This process starts only when you specify the environment settings as described in 15.1.7 Changing the mode in which unregistration or generation management deletes the generations of a jobnet in the JP1/Automatic Job Management System 3 Configuration Guide.

#8

This process starts only when you specify the environment settings as described in 15.1.8 Settings for using wait conditions in the JP1/Automatic Job Management System 3 Configuration Guide.

(2) Processes of JP1/AJS3 - Agent for UNIX

There are three kinds of processes of JP1/AJS3 - Agent for UNIX:

Parent process

A parent process consists of several child processes.

Child process

A child process consists of several detail processes.

Detail process

You can use the jajs_spmd_status command to check the status of the child processes of jajs_spmd. For details, see the description of jajs_spmd_status in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

To check the status of parent, child and detail processes, use the ps command.

Table B-10 lists the parent and child processes. Table B-11 lists the child and detail processes. The number following a parent or child process name indicates the maximum number of processes you can activate concurrently.

Table B‒10: Parent and child processes of JP1/AJS3 - Agent for UNIX

Parent process

(number of processes)

Description

Child process

(number of processes)

Description

jajs_spmd (1)#

JP1/AJS3 service

jpoagent (1)

Event/action control agent process

jpqmon (1)

Job execution control

This process monitors all processes for job execution control.

ajsqlagtd (1)

JP1/AJS3 Queueless Agent service (queueless agent process)

JP1/AJS3 - Manager

This process accepts queueless job execution requests from JP1/AJS3 - Manager (scheduler service).

ajsqlagtd

(number-of-jobs-to-be-executed)

Queueless job management process

This process executes queueless jobs.

The same process names are generated from the JP1/AJS3 Queueless Agent service (queueless agent process) respectively for jobs to be executed.

The process is removed on completion of queueless job execution.

The process has no detail process.

ajschkagtd (1)

JP1/AJS3 Check Agent service

ajschkagtd (5)

This process controls the definition pre-check (agent process).

as_manager (1)

JP1/AJS3 Autonomous Agent service process

as_player (number of jobs to be executed + 1)

Flexible job execution process

as_iescsvr (1)

JP1/AJS3 Autonomous Agent Messenger service process

--

--

ajssysctlad(1)

Management portal execution environment (agent process)

ajssysctlarc

Process started when JP1/AJS3 - Web Console performs an operation for management portal

#

By specifying logical host names on the command line, you can differentiate between processes for physical hosts and for logical hosts.

A process for a logical host is represented as process-name -h logical-host-name. For example, when a logical host name is hostA, the jajs_spmd process for hostA is represented as jajs_spmd -h hostA.

Table B‒11: Child and detail processes of JP1/AJS3 - Agent for UNIX

Child process name

Detail process name

Description

jpoagent#

jpoagtsub#

Event/action control subagent process

This process mainly notifies the manager of information from the monitoring process.

jpocwtflMain#

File monitoring process

jpocwtflSub

File monitoring subprocess

This process starts only if the NetworkFilewatch environment setting parameter is set to Y.

jpocwttmMain#

Execution interval control process

jpocwtmlmain#

Mail monitoring communication process

jpoeventwatch#

Event (such as JP1 event or log trap) monitoring process

jpoevseach#

Event search process.

This process starts to search for the specified event when a JP1 event reception monitoring job specified with a pre-execution event search is executed.

jpqmon#

jpqagt#

Agent process for job execution control

This process activates jobs.

jpqagtdmn#

Job monitoring process activating process for job execution control

Process for activating the job monitoring process

Five processes are always activated. In a cluster system, five processes are activated for each logical host.

jpqagtchild#

Job monitoring process for job execution control

Process for monitoring job process execution

Five processes are activated in the initial status. Also, one process is activated for each execution job. In a cluster system, five processes are activated for each logical host.

as_player

ajsfxexec

Flexible job execution process

ajsfxdstr

Process for broadcast execution of flexible jobs

ajsfxbcctl

Process that manages the destination agents for broadcast execution of flexible jobs

Note

When you execute a command, a process with the same name as the command is activated.

#

You can differentiate between processes for physical hosts and for logical hosts.

A process for a logical host is represented as process-name logical-host-name.

For example, when a logical host name is hostA, the jpoagent process for hostA is represented as jpoagent hostA.

(3) Processes of JP1/AJS3 - Web Console for Linux

There are two kinds of processes of JP1/AJS3 - Web Console for Linux:

Parent process

A parent process consists of several child processes.

Child process

A child process consists of several detail processes.

Detail processes

To check the status of parent, child and detail processes, use the ps command.

Table B-12 lists the parent and child processes. The number following a parent or child process name indicates the maximum number of processes you can activate concurrently.

Table B‒12: Parent and child processes of JP1/AJS3 Web Console for Linux

Parent process

(number of processes)

Description

Child process

(number of processes)

Description

httpsd(1)

JP1/AJS3 HTTP Server service

httpsd(5 to 150)

Web service process

The number of processes varies according to the number processed of HTTP requests to JP1/AJS3 - Web Console.

rotatelogs2(3)#

Log splitting utility for web services

cjstartsv

(1)

JP1/AJS3 Web Application Server service

--

--

Note

When you execute a command, a process with the same name as the command is activated.

#

When JP1/AJS3 Web Console communicates with the client host in SSL, the number of processes is 4.

B.4 Embedded database processes

This appendix explains the embedded database processes generated when the embedded database is used as the scheduler database of JP1/AJS3 - Manager.

(1) Process configuration

The following figure shows the configuration of the embedded database processes generated when the embedded database is used as the scheduler database of JP1/AJS3 - Manager in UNIX. This figure is useful for monitoring processes because it shows the parent-child relationship of the processes of the entire embedded database.

Figure B‒5: Configuration of embedded database processes in UNIX

(2) Processes in Windows

The following explains the embedded database processes in Windows.

The Windows version of the embedded database consists of the following two types of processes:

Parent process

A parent process consists of at least one child process.

Child process

The status of parent and child processes can be checked on the Processes page in the Task Manager window.

The following table lists the parent and child processes. In the table, the number in parentheses following a process name indicates the number of instances that are activated concurrently.

Table B‒13: List of parent and child processes for the Windows version of the embedded database

Parent process

(instances)

Explanation

Child process

(instances)

Explanation

pdservice.exe (1)

JP1/AJS3 Database service process

pdprcd.exe (1)

Windows service control

pdprcd.exe (1)

Process server process, which manages the processes related to the embedded database

pdrsvre.exe (3)#1

Cleanup process, which performs cleanup processing after an embedded database process has terminated abnormally

pdmlgd.exe (1)

Message log server process, which controls message output

pdrdmd.exe (1)

System manager process, which controls the starting and stopping of units and manages users who want to connect

pdstsd.exe (1)

Status server process, which controls input and output for the status file for units

pdscdd.exe (1)

Scheduler process, which assigns a transaction to the single server process

pdtrnd.exe (1)

Transaction server process, which controls transactions

pdtrnrvd.exe (1 to 128)#2, #3

Transaction restoration process, which controls committing and restoration of transactions

pdlogd.exe (1)

Log server process, which controls the acquisition of system log data and log-related processes

pd_buf_dfw.exe (1)

Deferred write process, which controls background writing to the database storage disk

pdlogswd.exe (1)

Log swapper process, which allocates and de-allocates files related to the system log, manages input and output, and acquires synchronization point dumps

pdsds.exe (16 to 128)#3, #4

Single server process, which processes the SQL

pdsha.exe (1)#5

JP1/AJS3 Database ClusterService service process

--

Embedded database service for clusters

#1

When the version of the embedded database is 07-03 or earlier, two instances of this process are activated.

#2

Initially, only one instance is activated. Thereafter, each time a pdsds.exe process terminates abnormally, the number of instances temporarily increases.

#3

If the value of the pd_max_users operand in the system common definition file (pdsys) is changed, the new value becomes the maximum number of instances that can be activated.

#4

Initially, 16 instances are activated. Thereafter, the number of activated instances can increase to a maximum of 128 in response to the number of access requests for the embedded database.

#5

This process is activated if the version of the embedded database is earlier than 10-00.

(3) Processes in UNIX

The following explains the embedded database processes in UNIX.

The UNIX version of the embedded database consists of the following two types of processes:

Parent process

A parent process consists of at least one child process.

Child process

The status of parent and child processes can be checked by using the ps command.

The following table lists the parent and child processes. In the table, the number in parentheses following a process name indicates the number of instances that are activated concurrently.

Table B‒14: List of parent and child processes for the UNIX version of the embedded database

Parent process

(instances)

Explanation

Child process

(instances)

Explanation

pdmgrd (1)

Process server management process

pdprcd (1)

This process manages starting and stopping of the process server process.

pdprcd (1)

Process server process, which manages the processes related to the embedded database

pdrsvre (3)#1

Cleanup process, which performs cleanup processing after an embedded database process has terminated abnormally

pdmlgd (1)

Message log server process, which controls message output

pdrdmd (1)

System manager process, which controls the starting and stopping of units and manages users who want to connect

pdstsd (1)

Status server process, which controls input and output for the status file for units

pdscdd (1)

Scheduler process, which assigns a transaction to the single server process

pdtrnd (1)

Transaction server process, which controls transactions

pdtrnrvd (1 to 128)#2, #3

Transaction restoration process, which controls the committing and restoration of transactions

pdlogd (1)

Log server process, which controls the acquisition of system log data and log-related processes

pd_buf_dfw (1)

Deferred write process, which controls background writing to the database storage disk

pdlogswd (1)

Log swapper process, which allocates and deallocates files related to the system log, manages input and output, and acquires synchronization point dumps

pdsds (16 to 128)#3, #4

Single server process, which processes the SQL

#1

When the version of the embedded database is 07-03 or earlier, two instances of this process are activated.

#2

Initially, only one instance is activated. Thereafter, each time a pdsds process terminates abnormally, the number of instances temporarily increases.

#3

If the value of the pd_max_users operand in the system common definition file (pdsys) is changed, the new value becomes the maximum number of instances that can be activated.

#4

Initially, 16 instances are activated. The number of activated instances can increase to a maximum of 128 in response to the number of access requests for the embedded database.

C. Log Information

This appendix describes the log information output by JP1/AJS3 and how that information is formatted.

C.1 Log entries output by the scheduler services

The following table lists the types of logs output to the scheduler information log files of JP1/AJS3.

Table C‒1: Scheduler information log entries

Log entry type

Log entry name

Associated

message ID

Associated

JP1 event

Command name

Operation from JP1/AJS3 - View

Operation from JP1/AJS3 - Web Console (or API executed)

A001

Scheduler service started

KAVS0200-I

00004100

ajsstart

jajs_spmd

--

--

A002

Scheduler service terminated

KAVS0201-I

00004101

ajsstop

jajs_spmd_stop

--

--

A003

Scheduler service process terminated abnormally

KAVS0204-E

00004130

--

--

--

A007

JP1/AJS3 - View connection

KAVS0534-I

None

--

Connecting to a scheduler service

--

A008

JP1/AJS3 - View disconnection ended

KAVS0535-I

None

--

Disconnecting from a scheduler service

--

A011

Scheduler information logging started

KAVS0220-I

None

jajs_spmd

--

--

A012

Scheduler information logging terminated

KAVS0221-I

None

jajs_spmd_stop

--

--

A013

Authentication denied

KAVS1009-W

None

--

Connecting to a scheduler service

login

A016

Connection rejected by manager connection source restriction

KAVS8040-E

None

--

--

--

A017

JP1/AJS3 - Web Console connection

KAVS0570-I

None

--

--

Connecting to a scheduler service

A018

JP1/AJS3 - Web Console disconnection ended

KAVS0571-I

None

--

--

Disconnecting from a scheduler service

N001

Jobnet started

KAVS0260-I

00004102

--

--

--

N002

Jobnet ended normally

KAVS0261-I

00004103

--

--

--

N003

Jobnet ended abnormally

KAVS0262-E

00004104

--

--

--

N004

Jobnet ended with warning

KAVS0268-W

00004108

--

--

--

N005

Jobnet on hold

KAVS0270-I

00004120

--

--

--

N006

Jobnet shut down

KAVS0272-E

00004131

--

--

--

N007

KAVS0273-E

N008

Jobnet start delayed

KAVS0275-I

00004122

--

--

--

N009

Jobnet end delayed

KAVS0276-I

00004123

--

--

--

N010

Next schedule queuing

KAVS0277-I

00004124

--

--

--

N011

Jobnet start condition monitoring started

KAVS0240-I

00004140

--

--

--

N012

Jobnet start condition monitoring terminated

KAVS0241-I

00004141

--

--

--

N013

Jobnet skipped so not executed

KAVS0279-E

00004142

--

--

--

N014

All jobnet registrations canceled

KAVS0267-I

None

ajsstart -c

jajs_spmd -cold

--

--

N015

Start condition monitoring waiting to terminate

KAVS1420-I

00004145

--

--

--

N016

Waiting in accordance with the jobnet wait condition started

KAVS4950-I

00004146

--

--

--

N017

Jobnet wait condition in effect

KAVS4955-I

00004147

--

--

--

N018

Waiting in accordance with the jobnet wait condition endless

KAVS4957-E

00004148

--

--

--

J001

Job started

KAVS0263-I

00004105

--

--

--

J002

Job ended normally

KAVS0264-I

00004106

--

--

--

J003

Job ended abnormally

KAVS0265-E

00004107

--

--

--

J004

Job ended with warning

KAVS0269-W

00004109

--

--

--

J005

Job on hold

KAVS0271-I

00004121

--

--

--

J006

Job submission started

KAVS0278-I

00004125

--

--

--

J007

Event job execution request started

KAVS0242-I

00004126

--

--

--

J008

Job end delayed

KAVS0248-I

00004127

--

--

--

J009

Job queuing canceled

KAVS0266-I

0000410A

--

--

--

J010

Waiting in accordance with the job wait condition started

KAVS4951-I

0000414A

--

--

--

J011

Job wait condition in effect

KAVS4956-I

0000414B

--

--

--

J012

Waiting in accordance with the job wait condition endless

KAVS4971-E

0000414C

--

--

--

J013

Waiting for the automatic retry interval started

KAVS4675-I

00004155

--

--

--

J014

Automatic retry execution started

KAVS4676-I

00004156

--

--

--

J015

Error that disables retry execution occurred during automatic retry

KAVS4677-E

00004157

--

--

--

J016

Job submission by automatic retry started

KAVS4678-I

00004158

--

--

--

C001

Scheduler service operation environment temporarily changed

None

None

ajsalter

--

--

C002

Scheduler service stopped

None

None

ajsstop

--

--

C003

Scheduler service started

None

None

ajsstart

--

--

C101

Jobnet registered

None

None

ajsent

ry

Register for Execution, or

in the Daily Schedule or Monthly Schedule window, specifying a root jobnet and adding a jobnet by clicking Add

Register for execution

Register an execution schedule for a specified root jobnet

C102

Registered jobnet canceled

None

None

ajsleave

Cancel Registration used

Cancel registration

C103

Jobnet temporarily changed

None

None

ajsplan

Change Plan,

Change Hold Attribute,

Change Delay Monitor,

Change Priority, or

in the Daily Schedule or Monthly Schedule window, specifying a nested jobnet and adding a jobnet by clicking Add

Change plan,

Change hold attribute,

Change delay monitor

Change the execution schedule for a specified jobnet

C104

Jobnet execution interrupted

None

None

ajsintrpt

Interrupt

Interrupt

C105

Jobnet rerun

None

None

ajsrerun

Rerun

Rerun

C106

Jobnet suspended/released from suspension

None

None

ajssuspend

Suspension

--

C107

Jobnet registration for execution information imported

None

None

ajsrgimport

--

--

C108

Jobnet registered by import of jobnet registration for execution information

None

None

ajsrgimport

--

--

C201

Jobnet/job forcibly ended

None

None

ajskill

Kill

Kill

C202

Job status changed

None

None

ajschgstat

Change Job Status

Change job status

C301

Unit definitions changed

None

None

ajschange

ajschgjob

ajschgnet

Changing a definition

Changing a definition

C302

Unit deleted

None

None

ajsdelete

Delete

--

C303

Unit restored

None

None

ajsrestore

Restore

--

C304

Unit created

None

None

ajsdefine

New

--

C305

Unit copied or moved

None

None

ajscopy

Paste

--

C306

Unit imported

None

None

ajsimport

--

--

C307

Jobnet released

None

None

ajsrelease -a

or

ajsrelease -c

Release Entry,

Release Cancel

--

C401

Calendar changed

None

None

ajscalendar

Changing a calendar

--

C502

Unit status displayed

None

None

ajsshow

--

--

C503

Unit definitions output

None

None

ajsprint

--

--

C504

Unit definitions backed up

None

None

ajsbackup

Backup

--

C506

Root jobnet schedule information output

None

None

ajsschedule

--

--

C507

Unit name output

None

None

ajsname

--

Display the Event Job Retention Details dialog box

C508

Unit definitions exported

None

None

ajsexport

Package

--

C509

Unit status displayed (abnormal end)

None

None

ajsshow

--

--

C510

Unit definitions output (abnormal end)

None

None

ajsprint

--

--

C511

Unit definitions backed up (abnormal end)

None

None

ajsbackup

Backup

--

C512

Unit name output (abnormal end)

None

None

ajsname

--

Display the Event Job Retention Details dialog box

C513

Jobnet registration for execution information exported

None

None

ajsrgexport

--

--

C514

Jobnet information output by export of jobnet registration for execution information

None

None

ajsrgexport

--

--

C515

Jobnet release information referenced

None

None

ajsrelease -i

--

--

C516

Calendar calculation

None

None

ajscalutil

--

--

I001

Command processing started

None

None

ajsalter

ajscalutil

ajsimport

ajsprint

ajsschedule

ajsshow

ajsstart

ajsstop

--

--

ajsname

--

Display the Event Job Retention Details dialog box

ajscalendar

Changing a calendar

--

ajschange

ajschgjob

ajschgnet

Changing a definition

Changing a definition

ajschgstat

Change Job Status

Change job status

ajscopy

Paste

--

ajsdefine

New

--

ajsdelete

Delete

--

ajsentry

Register for Execution, or

in the Daily Schedule or Monthly Schedule window, specifying a root jobnet and adding a jobnet by clicking Add

Register for execution

Register an execution schedule for a specified root jobnet

ajsexport

Package

--

ajsintrpt

Interrupt

Interrupt

ajskill

Kill

Kill

ajsleave

Cancel Registration

Cancel registration

ajsplan

Change Plan,

Change Hold Attribute,

Change Delay Monitor, or

Change Priority, or

in the Daily Schedule or Monthly Schedule window, specifying a nested jobnet and adding a jobnet by clicking Add

Change plan,

Change hold attribute,

Change delay monitor

Change the execution schedul for a specified jobnet

ajsrelease

Release Entry,

Release Cancel, or

viewing release information (by selecting the jobnet related to the release in the list area)

--

ajsrerun

Rerun

Rerun

ajsrestore

Restore

--

ajsrgexport

--

--

ajsrgimport

--

--

ajssuspend

Suspension

--

I002

Command-to-scheduler service processing request started

None

None

ajschgstat

Change Job Status

Change job status

ajsentry

Register for Execution, or

in the Daily Schedule or Monthly Schedule window, specifying a root jobnet and adding a jobnet by clicking Add

Register for execution

Register an execution schedule for a specified root jobnet

ajsintrpt

Interrupt

Interrupt

ajskill

Kill

Kill

ajsleave

Cancel Registration

Cancel registration

ajsplan

Change Plan,

Change Hold Attribute,

Change Delay Monitor, or

Change Priority, or

in the Daily Schedule or Monthly Schedule window, specifying a nested jobnet and adding a jobnet by clicking Add

Change plan,

Change hold attribute,

Change delay monitor

Change the execution schedule for a specified jobnet

ajsrerun

Rerun

Rerun

ajssuspend

Suspension

--

Legend:

--: Not applicable.

The formats and the items output are described below for each log entry. A Δ in the format of a log entry indicates a one-byte space.

(1) Formats common to all log entries

The formats described below are common to all entries in the scheduler service logs.

You can select whether to include a process ID in the log information as follows.

Make the selection by using the jajs_config command to set the LOGHEADER or HOSTLOGHEADER environment setting parameter. If you do not want to include a process ID, specify none. If you want to include a process ID, specify PID.

For details about these environment setting parameters, see 20.4.2(67) LOGHEADER and 20.3.2(13) HOSTLOGHEADER in the JP1/Automatic Job Management System 3 Configuration Guide.

Table C‒2: Log entry formats with and without a process ID

Process ID setting

Log entry format

If you do not want to include a process ID, specify none in the LOGHEADER or HOSTLOGHEADER environment setting parameter.

log-numberΔdateΔtimeΔadditional-informationΔ

To include a process ID, specify PID in the LOGHEADER or HOSTLOGHEADER environment setting parameter.

log-numberΔdateΔtimeΔ[process-ID]Δadditional-informationΔ

The following table provides the details about each item in the formats.

Table C‒3: Format items common to the entries in the scheduler information logs

Item

Description

Length (bytes)

log-type

A log type (for example, A001) is output.

4

date

The date that the entry was output to the log.

The month and the day are delimited by either one or two one-byte space characters.

Examples:

- December 1: DecΔ Δ1 or DecΔ01#

- December 10: DecΔ10

If yes is specified in the AJSLOGOUTPUTYEAR or HOSTLOGOUTPUTYEAR environment setting parameter, the date is expressed in YYYY/MM/DD format.

Example:

December 7, 2009: 2009/12/07

6 or 11

time

The time that the entry was output to the log.

Hours, minutes, and seconds are delimited by one-byte colons (:). A single-digit is prefixed with 0.

Example:

Five minutes and 0 seconds after 11 p.m.: 23:05:00

8

[process-ID]

The process ID of a command or a scheduler service.

A process ID is included if PID is specified in the LOGHEADER or HOSTLOGHEADER environment setting parameter.

A process ID is not included if none is specified in the LOGHEADER or HOSTLOGHEADER environment setting parameter.

The value enclosed in square brackets is the process ID.

0 or 3 to 12

additional-information

Detailed log information.

The limit on length varies according to the log entry.

#

Whether the month and the day are separated by one space or two spaces depends on the character string generated by the ctime() function of the OS.

Cautionary notes

Each entry in the scheduler information log consists of one record and the length of one record is 2,048 bytes (includes two bytes for a linefeed). Therefore, if the length of the log information exceeds 2,048 bytes, only 2,048 bytes are output. The 2,049th subsequent bytes are not output.

When you perform an operation in JP1/AJS3 - View, multiple entries in the scheduler information log might be created for that one operation. For example, if you create a unit, the DEFINE (C304) and CHANGE (C301) log entries are output.

If you perform the operations described below in JP1/AJS3 - View, the CHANGE (C301) log entry is output.

In this case, the difference between the previous definition and the new definition is not output to the log, and only spaces (Δ) are output.

- You define a job by using a program other than JP1/AJS3 - View, you open the job in the Define Details dialog box, but change no settings, and then you click the OK button.

- You open the Schedule Settings dialog box for a jobnet, but change no settings, and then you click the OK button.

If you perform the operations described below in JP1/AJS3 - Web Console, the CHANGE (C301) log entry is output.

In this case, the difference between the previous definition and the new definition is not output to the log, and only spaces (Δ) are output.

- You define a job by using a program other than JP1/AJS3 - Web Console, you open the job in the Define Details dialog box, but change no settings, and then you click the OK button.

(2) Formats of the Scheduler Service Started log entry

The following are the formats of the Scheduler Service Started log entry.

When no process ID is to be included in the log information:

A001ΔdateΔtimeΔKAVS0200-IΔscheduler-service-name

When a process ID is to be included in the log information:

A001ΔdateΔtimeΔ[process-ID]ΔKAVS0200-IΔscheduler-service-name

Example of a log entry:

A001 Dec 15 10:40:43 KAVS0200-I AJSROOT1

The following table describes the item that is specific to these formats.

Table C‒4: Item specific to the Scheduler Service Started log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

(3) Formats of the Scheduler Service Terminated log entry

The following are the formats of the Scheduler Service Terminated log entry.

When no process ID is to be included in the log information:

A002ΔdateΔtimeΔKAVS0201-IΔscheduler-service-name

When a process ID is to be included in the log information:

A002ΔdateΔtimeΔ[process-ID]ΔKAVS0201-IΔscheduler-service-name

Example of a log entry:

A002 Dec 12 09:14:22 KAVS0201-I AJSROOT1

The following table describes the item that is specific to these formats.

Table C‒5: Item specific to the Scheduler Service Terminated log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

(4) Formats of the Scheduler Service Process Terminated Abnormally log entry

The following are the formats of the Scheduler Service Process Terminated Abnormally log entry.

When no process ID is to be included in the log information:

A003ΔdateΔtimeΔKAVS0204-EΔscheduler-service-nameΔprocess-nameΔreturn-code

When a process ID is to be included in the log information:

A003ΔdateΔtimeΔ[process-ID]ΔKAVS0204-EΔscheduler-service-nameΔprocess-nameΔreturn-code

Example of a log entry:

A003 Dec 12 09:14:22 KAVS0204-E AJSROOT1 ajsschd 4

The following table describes the items that are specific to these formats.

Table C‒6: Items specific to the Scheduler Service Process Terminated Abnormally log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

process-name

One of the following is output:

- ajsflowd

- ajsschd

- ajslogd

1 to 30

return-code

A return code is recorded.

1 to 10

(5) Formats of the JP1/AJS3 - View Connection log entry

The following are the formats of a JP1/AJS3 - View Connection log entry.

When no process ID is to be included in the log information:

A007ΔdateΔtimeΔKAVS0534-IΔhost-nameΔ;CONNECTΔuser-nameΔ[user-type]Δ[requesting-host-IP-address,requesting-source-identification]Δscheduler-service-name

When a process ID is to be included in the log information:

A007ΔdateΔtimeΔ[process-ID]ΔKAVS0534-IΔhost-nameΔ;CONNECTΔuser-nameΔ[user-type]Δ[requesting-host-IP-address,requesting-source-identification]Δscheduler-service-name

Logging conditions:

A log entry is output only if all is specified in the MONLOG environment setting parameter. Logging begins when:

You log in to JP1/AJS3 - Manager from JP1/AJS3 - View.

You select a scheduler service in the tree area in a JP1/AJS3 - View window.

JP1/AJS3 - View is automatically reconnected to JP1/AJS3 - Manager.

Example of a log entry:

A007 Aug 05 17:14:01 KAVS0534-I hostA ;CONNECT jp1admin [ADMIN] [10.210.38.11,JP1/AJS2-View] AJSROOT1

The following table describes the items that are specific to these formats.

Table C‒7: Items specific to the JP1/AJS3 - View Connection log entry (scheduler information log)

Item

Description

Length (bytes)

host-name

The host name of the host that was connected is output.

1 to 255

user-name

The name of the JP1 user who performed the operation is output.

0 to 20

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host requested to perform the operation is output.

7 to 15

requesting-source-identification

The information for identifying the source requesting the operation is output. (JP1/AJS2-View)

13

scheduler-service-name

The name of the scheduler service connected from JP1/AJS3 - View is output.

1 to 30

(6) Formats of the JP1/AJS3 - View Disconnection log entry

The following are the formats of the JP1/AJS3 - View Disconnection log entry.

When no process ID is to be included in the log information:

A008ΔdateΔtimeΔKAVS0535-IΔhost-nameΔ;DISCONNECTΔuser-nameΔ[user-type]Δ[requesting-host-IP-address,requesting-source-identification]Δscheduler-service-name

When a process ID is to be included in the log information:

A008ΔdateΔtimeΔ[process-ID]ΔKAVS0535-IΔhost-nameΔ;DISCONNECTΔuser-nameΔ[user-type]Δ[requesting-host-IP-address,requesting-source-identification]Δscheduler-service-name

Logging conditions:

A log entry is output only if all is specified in the MONLOG environment setting parameter. Logging begins when:

You exit JP1/AJS3 - View (log out from JP1/AJS3 - Manager).

You are unable to connect from JP1/AJS3 - View and the ajsmonsvr process terminates.

The length of time specified in the SESSIONTIMEOUT environment setting parameter has passed since communication with JP1/AJS3 - View was disconnected.

Example of a log entry:

A008 Dec 15 17:14:01 KAVS0535-I hostA ;DISCONNECT jp1admin [ADMIN] [10.210.38.11,JP1/AJS2-View] AJSROOT1

The following table describes the items that are specific to these formats.

Table C‒8: Items specific to the JP1/AJS3 - View Disconnection log entry (scheduler information log)

Item

Description

Length (bytes)

host-name

The host name of the host that was disconnected is output.

1 to 255

user-name

The name of the JP1 user who performed the operation is output.

0 to 20

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The information for identifying the source requesting the operation is output.

7 to 15

requesting-source-identification

The name of the product used to perform the operation is output (JP1/AJS2-View).

13

scheduler-service-name

The name of the scheduler service that was disconnected is output.

1 to 30

(7) Formats of the Scheduler Information Logging Started log entry

The following are the formats of the Scheduler Information Logging Started log entry.

When no process ID is to be included in the log information:

A011ΔdateΔtimeΔKAVS0220-I

When a process ID is to be included in the log information:

A011ΔdateΔtimeΔ[process-ID]ΔKAVS0220-I

Logging conditions:

An entry is output to the log only if all is specified in the LOGDLOG and HLOGDLOG environment setting parameter.

Example of a log entry:

A011 Dec 15 10:51:18 KAVS0220-I

(8) Formats of the Scheduler Information Logging Terminated log entry

The following are the formats of the Scheduler Information Logging Terminated log entry.

When no process ID is to be included in the log information:

A012ΔdateΔtimeΔKAVS0221-I

When a process ID is to be included in the log information:

A012ΔdateΔtimeΔ[process-ID]ΔKAVS0221-I

Logging conditions:

An entry is output to the log only if all is specified in the LOGDLOG and HLOGDLOG environment setting parameter.

Example of a log entry:

A012 Dec 15 10:51:18 KAVS0221-I

(9) Formats of the Authentication (Login or User Mapping) Denied log entry

The following are the formats of the Authentication (Login or User Mapping) Denied log entry.

When no process ID is to be included in the log information:

A013ΔdateΔtimeΔKAVS1009-WΔrequesting-host-IP-addressΔuser-nameΔhost-name

When a process ID is to be included in the log information:

A013ΔdateΔtimeΔ[process-ID]ΔKAVS1009-WΔrequesting-host-IP-addressΔuser-nameΔhost-name

Logging conditions:

An entry is output to the log only if all is specified in the AUTHLOG environment setting parameter.

Logging for each host is output to the scheduler information log, and begins when user authentication or user mapping on JP1/Base fails during a connection with one of the following clients:

JP1/AJS3 - View

JP1/AJS3 - Web Console

JP1/AJS3 - Definition Assistant

JP1/AJS3 - Manager (when a command is executed remotely or a remote jobnet is executed)

Example of a log entry:

A013 Dec 15 17:14:01 KAVS1009-W 10.210.38.11 jp1admin hostA

The following table describes the items that are specific to these formats.

Table C‒9: Items specific to an Authentication (Login or User Mapping) Denied log entry (scheduler information log)

Item

Description

Length (bytes)

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

7 to 15

user-name

The name of the JP1 user who performed the operation is output.

0 to 20

host-name

The host name of the host that accepted the request is output.

1 to 255

(10) Formats of the Connection Rejected by Manager Connection Source Restriction log entry

The following are the formats of the Connection Rejected by Manager Connection Source Restriction log entry:

When no process ID is to be included in the log information:

A016ΔdateΔtimeΔKAVS8040-EΔrequesting-host-IP-addressΔuser-nameΔhost-name

When a process ID is to be included in the log information:

A016ΔdateΔtimeΔ[process-ID]ΔKAVS8040-EΔrequesting-host-IP-addressΔuser-nameΔhost-name

Logging conditions:

A log entry is output only if all is specified in the CONRESTRICTLOG environment setting parameter.

This log entry is output to the scheduler log for each host when a connection is rejected because restricting of connection sources is in effect for the manager.

Example of a log entry:

A016 Feb 28 17:14:01 KAVS8040-E 10.210.38.11 jp1admin hostA

The following table describes the items that are specific to these formats.

Table C‒10: Items specific to the Connection Rejected by Manager Connection Source Restriction log entry (scheduler information log)

Item

Description

Length (bytes)

requesting-host-IP-address

The IP address of the host that requested the operation is output.

3 to 39

user-name

The name of the JP1 user who performed the operation is output.

0 to 20

host-name

The name of the host that received the request is output.

1 to 255

(11) Formats of the JP1/AJS3 - Web Console Connection log entry

The following are the formats of a JP1/AJS3 - Web Console Connection log entry.

When no process ID is to be included in the log information:

A017ΔdateΔtimeΔKAVS0570-IΔhost-nameΔ;CONNECTΔuser-nameΔ[user-type]Δ[requesting-host-IP-address,requesting-source-identification]Δscheduler-service-name

When a process ID is to be included in the log information:

A017ΔdateΔtimeΔ[process-ID]ΔKAVS0570-IΔhost-nameΔ;CONNECTΔuser-nameΔ[user-type]Δ[requesting-host-IP-address,requesting-source-identification]Δscheduler-service-name

Logging conditions:

A log entry is output only if all is specified in the MONLOG environment setting parameter. Logging begins when:

You log in to JP1/AJS3 - Manager from the Web GUI (Job Portal) of JP1/AJS3 - Web Console.

You select a scheduler service in the tree area in the Web GUI (Job Portal) of JP1/AJS3 - Web Console.

JP1/AJS3 - Web Console is automatically reconnected to JP1/AJS3 - Manager.

You execute an API of the JP1/AJS3 - Web Console.

Example of a log entry:

A017 Aug 05 17:14:01 KAVS0570-I hostA ;CONNECT jp1admin [ADMIN] [10.210.38.11,JP1/AJS3-WEB] AJSROOT1

The following table describes the items that are specific to these formats.

Table C‒11: Items specific to the JP1/AJS3 - Web Console Connection log entry (scheduler information log)

Item

Description

Length (bytes)

host-name

The host name of the host that was connected is output.

1 to 255

user-name

The name of the JP1 user who performed the operation is output.

0 to 20

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host requested to perform the operation is output.

3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. (JP1/AJS3-WEB)

11

scheduler-service-name

The name of the scheduler service connected from JP1/AJS3 - View is output.

1 to 30

(12) Formats of the JP1/AJS3 - Web Console Disconnection log entry

The following are the formats of the JP1/AJS3 - Web Console Disconnection log entry.

When no process ID is to be included in the log information:

A018ΔdateΔtimeΔKAVS0571-IΔhost-nameΔ;DISCONNECTΔuser-nameΔ[user-type]Δ[requesting-host-IP-address,requesting-source-identification]Δscheduler-service-name

When a process ID is to be included in the log information:

A018ΔdateΔtimeΔ[process-ID]ΔKAVS0571-IΔhost-nameΔ;DISCONNECTΔuser-nameΔ[user-type]Δ[requesting-host-IP-address,requesting-source-identification]Δscheduler-service-name

Logging conditions:

A log entry is output only if all is specified in the MONLOG environment setting parameter. Logging begins when:

You exit JP1/AJS3 - Web Console (log out from JP1/AJS3 - Manager).

You are unable to connect from JP1/AJS3 - Web Console and the ajsmonsvr process terminates.

The length of time specified in the CDSESSIONTIMEOUT environment setting parameter has passed since communication with JP1/AJS3 - Web Console was disconnected.

A log entry is output if the ajscdinetd process stops during connection to JP1/AJS3 - Web Console.

Example of a log entry:

A018 Dec 15 17:14:01 KAVS0571-I hostA ;DISCONNECT jp1admin [ADMIN] [10.210.38.11,JP1/AJS3-WEB] AJSROOT1

The following table describes the items that are specific to these formats.

Table C‒12: Items specific to the JP1/AJS3 - Web Console Disconnection log entry (scheduler information log)

Item

Description

Length (bytes)

host-name

The host name of the host that was disconnected is output.

1 to 255

user-name

The name of the JP1 user who performed the operation is output.

0 to 20

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

a user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The information for identifying the source requesting the operation is output.

3 to 39

requesting-source-identification

The name of the product used to perform the operation is output (JP1/AJS3-WEB).

11

scheduler-service-name

The name of the scheduler service that was disconnected is output.

1 to 30

(13) Formats of the Jobnet Started log entry

The following are the formats of the Jobnet Started log entry.

When no process ID is to be included in the log information:

N001ΔdateΔtimeΔKAVS0260-IΔscheduler-service-name:jobnet-name:execution-ID#

When a process ID is to be included in the log information:

N001ΔdateΔtimeΔ[process-ID]ΔKAVS0260-IΔscheduler-service-name:jobnet-name:execution-ID #

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

N001 Dec 15 17:14:01 KAVS0260-I AJSROOT1:/group/net1:@A100

The following table describes the items that are specific to these formats.

Table C‒13: Items specific to a Jobnet Started log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

jobnet-name

The name of the jobnet or jobnet connector that started is output.

1 to 930

execution-ID

The execution ID of the jobnet or jobnet connector that started is output in @alphanumeric-character format.

1 to 10

(14) Formats of the Jobnet Ended Normally log entry

The following are the formats of the Jobnet Ended Normally log entry.

When no process ID is to be included in the log information:

N002ΔdateΔtimeΔKAVS0261-IΔscheduler-service-name:jobnet-name:execution-ID#

When a process ID is to be included in the log information:

N002ΔdateΔtimeΔ[process-ID]ΔKAVS0261-IΔscheduler-service-name:jobnet-name:execution-ID#

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

N002 Dec 15 17:14:44 KAVS0261-I AJSROOT1:/group/net1:@A100

The following table describes the items that are specific to these formats.

Table C‒14: Items specific to the Jobnet Ended Normally log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

jobnet-name

The name of the jobnet or jobnet connector that ended is output.

1 to 930

execution-ID

The execution ID of the jobnet or jobnet connector that ended is output in @alphanumeric-character format.

1 to 10

(15) Formats of the Jobnet Ended Abnormally log entry

The following are the formats of the Jobnet Ended Abnormally log entry.

When no process ID is to be included in the log information:

N003ΔdateΔtimeΔKAVS0262-EΔscheduler-service-name:jobnet-name:execution-ID#

When a process ID is to be included in the log information:

N003ΔdateΔtimeΔ[process-ID]ΔKAVS0262-EΔscheduler-service-name:jobnet-name:execution-ID #

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

N003 Dec 01 14:05:46 KAVS0262-E AJSROOT1:/net1/nestnet1:@A111

The following table describes the items that are specific to these formats.

Table C‒15: Items specific to the Jobnet Ended Abnormally log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

jobnet-name

The name of the jobnet or jobnet connector that ended abnormally is output.

1 to 930

execution-ID

The execution ID of the jobnet or jobnet connector that ended abnormally is output in @alphanumeric-character format.

1 to 10

(16) Formats of the Jobnet Ended with Warning log entry

The following are the formats of the Jobnet Ended with Warning log entry.

When no process ID is to be included in the log information:

N004ΔdateΔtimeΔKAVS0268-WΔscheduler-service-name:jobnet-name:execution-ID#

When a process ID is to be included in the log information:

N004ΔdateΔtimeΔ[process-ID]ΔKAVS0268-WΔscheduler-service-name:jobnet-name:execution-ID#

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

N004 Dec 01 14:05:46 KAVS0268-W AJSROOT1:/net1/nestnet1:@A111

The following table describes the items that are specific to these formats.

Table C‒16: Items specific to the Jobnet Ended with Warning log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

jobnet-name

The name of the jobnet or jobnet connector that ended with a warning is output.

1 to 930

execution-ID

The execution ID of the jobnet or jobnet connector that ended with a warning is output in @alphanumeric-character format.

1 to 10

(17) Formats of the Jobnet on Hold log entry

The following are the formats of the Jobnet on Hold log entry.

When no process ID is to be included in the log information:

N005ΔdateΔtimeΔKAVS0270-IΔscheduler-service-name:jobnet-name:execution-ID#

When a process ID is to be included in the log information:

N005ΔdateΔtimeΔ[process-ID]ΔKAVS0270-IΔscheduler-service-name:jobnet-name:execution-ID#

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

N005 Dec 01 14:05:46 KAVS0270-I AJSROOT1:/net1/nestnet1:@A111

The following table describes the items that are specific to these formats.

Table C‒17: Items specific to the Jobnet on Hold log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

jobnet-name

The name of the jobnet on hold is output.

1 to 930

execution-ID

The execution ID of the jobnet on hold is output in @alphanumeric-character format.

1 to 10

(18) Formats of the Jobnet Shut Down log entry (N006)

The following are the formats of the Jobnet Shut Down log entry (N006).

When no process ID is to be included in the log information:

N006ΔdateΔtimeΔKAVS0272-EΔscheduler-service-name:jobnet-name:execution-ID#Δmaintenance-information

When a process ID is to be included in the log information:

N006ΔdateΔtimeΔ[process-ID]ΔKAVS0272-EΔscheduler-service-name:jobnet-name:execution-ID#Δmaintenance-information

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

N006 Dec 15 09:31:39 KAVS0272-E AJSROOT1:/net1:@A100 082b4be5

The following table describes the items that are specific to these formats.

Table C‒18: Items specific to the Jobnet Shut Down log entry (N006) (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

jobnet-name

The name of the shut-down jobnet is output.

1 to 930

execution-ID

The execution ID of the shut-down jobnet is output in @alphanumeric-character format.

1 to 10

maintenance-information

Maintenance information is output.

8

(19) Formats of the Jobnet Shut Down log entry (N007)

The following are the formats of the Jobnet Shut Down log entry (N007).

When no process ID is to be included in the log information:

N007ΔdateΔtimeΔKAVS0273-EΔscheduler-service-name:jobnet-name:execution-ID#Δmaintenance-information

When a process ID is to be included in the log information:

N007ΔdateΔtimeΔ[process-ID]ΔKAVS0273-EΔscheduler-service-name:jobnet-name:execution-ID#Δmaintenance-information

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

N007 Dec 15 09:31:39 KAVS0273-E AJSROOT1:/net1:@A100 082b4be5

The following table describes the items that are specific to these formats.

Table C‒19: Items specific to the Jobnet Shut Down log entry (N007) (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

jobnet-name

The name of the shut-down jobnet is output.

1 to 930

execution-ID

The execution ID of the shut-down jobnet is output in @alphanumeric-character format.

1 to 10

maintenance-information

Maintenance information is output.

8

(20) Formats of the Jobnet Start Delayed log entry

The following are the formats of the Jobnet Start Delayed log entry.

When no process ID is to be included in the log information:

N008ΔdateΔtimeΔKAVS0275-IΔscheduler-service-name:jobnet-name:execution-ID#

When a process ID is to be included in the log information:

N008ΔdateΔtimeΔ[process-ID]ΔKAVS0275-IΔscheduler-service-name:jobnet-name:execution-ID#

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

N008 Dec 01 16:36:37 KAVS0275-I AJSROOT1:/group/net1:@A106

The following table describes the items that are specific to these formats.

Table C‒20: Items specific to the Jobnet Start Delayed log entry(scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

jobnet-name

The name of the jobnet whose startup was delayed is output.

1 to 930

execution-ID

The execution ID of the jobnet whose startup was delayed is output in @alphanumeric-character format.

1 to 10

(21) Formats of the Jobnet End Delayed log entry

The following are the formats of the Jobnet End Delayed log entry.

When no process ID is to be included in the log information:

N009ΔdateΔtimeΔKAVS0276-IΔscheduler-service-name:jobnet-name:execution-ID#

When a process ID is to be included in the log information:

N009ΔdateΔtimeΔ[process-ID]ΔKAVS0276-IΔscheduler-service-name:jobnet-name:execution-ID#

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

N009 Dec 01 16:36:37 KAVS0276-I AJSROOT1:/group/net1:@A106

The following table describes the items that are specific to these formats.

Table C‒21: Items specific to the Jobnet End Delayed log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

jobnet-name

The name of the jobnet whose end was delayed is output.

1 to 930

execution-ID

The execution ID of the jobnet whose end was delayed is output in @alphanumeric-character format.

1 to 10

(22) Formats of the Next Schedule Queuing log entry

The following are the formats of the Next Schedule Queuing log entry.

When no process ID is to be included in the log information:

N010ΔdateΔtimeΔKAVS0277-IΔscheduler-service-name:jobnet-name:execution-ID#

When a process ID is to be included in the log information:

N010ΔdateΔtimeΔ[process-ID]ΔKAVS0277-IΔscheduler-service-name:jobnet-name:execution-ID#

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

N010 Dec 01 16:39:37 KAVS0277-I AJSROOT1:/group/net1:@A108

The following table describes the items that are specific to these formats.

Table C‒22: Items specific to the Next Schedule Queuing log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

jobnet-name

The applicable jobnet name is output.

1 to 930

execution-ID

The applicable execution ID is output in @alphanumeric-character format.

1 to 10

(23) Formats of the Jobnet Start Condition Monitoring Started log entry

The following are the formats of the Jobnet Start Condition Monitoring Started log entry.

When no process ID is to be included in the log information:

N011ΔdateΔtimeΔKAVS0240-IΔscheduler-service-name:jobnet-name:execution-ID#

When a process ID is to be included in the log information:

N011ΔdateΔtimeΔ[process-ID]ΔKAVS0240-IΔscheduler-service-name:jobnet-name:execution-ID#

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

N011 Dec 15 10:43:09 KAVS0240-I AJSROOT1:/group/net1:@A101

The following table describes the items that are specific to these formats.

Table C‒23: Items specific to the Jobnet Start Condition Monitoring Started log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

jobnet-name

The name of the jobnet for which start condition monitoring started is output.

1 to 930

execution-ID

The execution ID of the jobnet for which start condition monitoring started is output in @alphanumeric-character format.

1 to 10

(24) Formats of the Jobnet Start Condition Monitoring Terminated log entry

The following are the formats of the Jobnet Start Condition Monitoring Terminated log entry.

When no process ID is to be included in the log information:

N012ΔdateΔtimeΔKAVS0241-IΔscheduler-service-name:jobnet-name:execution-ID#Δend-status

When a process ID is to be included in the log information:

N012ΔdateΔtimeΔ[process-ID]ΔKAVS0241-IΔscheduler-service-name:jobnet-name:execution-ID#Δend-status

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

N012 Dec 01 16:36:38 KAVS0241-I AJSROOT1:/group/net1:@A101 u

The following table describes the items that are specific to these formats.

Table C‒24: Items specific to the Jobnet Start Condition Monitoring Terminated log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

jobnet-name

The name of the jobnet for which start condition monitoring terminated is output.

1 to 930

execution-ID

The execution ID of the jobnet for which start condition monitoring terminated is output in @alphanumeric-character format.

1 to 10

end-status

One of the following is output:

u: Unmonitored + Ended

c: Monitor terminated

i: Interrupted monitoring

n: Monitor-end normal

1

(25) Formats of the Jobnet Skipped So Not Executed log entry

The following are the formats of the Jobnet Skipped So Not Executed log entry.

When no process ID is to be included in the log information:

N013ΔdateΔtimeΔKAVS0279-EΔscheduler-service-name:jobnet-name:execution-ID#

When a process ID is to be included in the log information:

N013ΔdateΔtimeΔ[process-ID]ΔKAVS0279-EΔscheduler-service-name:jobnet-name:execution-ID#

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

N013 Dec 01 16:36:38 KAVS0279-E AJSROOT1:/group/net1:@A101

The following table describes the items that are specific to these formats.

Table C‒25: Items specific to the Jobnet Skipped So Not Executed log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

jobnet-name

The name of root jobnet name of the jobnet whose status became Skipped so not exe. is output.

1 to 930

execution-ID

The execution ID of the jobnet whose status became Skipped so not exe. is output in @alphanumeric-character format.

1 to 10

(26) Formats of the All Jobnet Registrations Canceled log entry

The following are the formats of the All Jobnet Registrations Canceled log entry.

When no process ID is to be included in the log information:

N014ΔdateΔtimeΔKAVS0267-IΔscheduler-service-name

When a process ID is to be included in the log information:

N014ΔdateΔtimeΔ[process-ID]ΔKAVS0267-IΔscheduler-service-name

Example of a log entry:

N014 Dec 01 16:36:38 KAVS0267-I AJSROOT1

The following table describes the item that is specific to these formats.

Table C‒26: Item specific to the All Jobnet Registrations Canceled log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

(27) Formats of the Start Condition Monitoring Waiting to Terminate log entry

The following are the formats of the Start Condition Monitoring Waiting to Terminate log entry.

When no process ID is to be included in the log information:

N015ΔdateΔtimeΔKAVS1420-IΔscheduler-service-name:jobnet-name:execution-ID-of-new-generationΔexecution-ID-of-previous-generation

When a process ID is to be included in the log information:

N015ΔdateΔtimeΔ[process-ID]ΔKAVS1420-IΔscheduler-service-name:jobnet-name:execution-ID-of-new-generationΔexecution-ID-of-previous-generation

Example of a log entry:

N015 Dec 15 14:48:54 KAVS1420-I AJSROOT1:/group/net1:@A109 @A108

The following table describes the items that are specific to these formats.

Table C‒27: Items specific to the Start Condition Monitoring Waiting to Terminate log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

jobnet-name

The applicable jobnet name is output.

1 to 930

execution-ID-of-new-generation

The execution ID of the new generation is output in @alphanumeric-character format.

1 to 10

execution-ID-of-previous-generation

The execution ID of the previous generation is output in @alphanumeric-character format.

1 to 10

(28) Formats of the Waiting in Accordance with the Jobnet Wait Condition Started log entry

The following are the formats of the Waiting in Accordance with the Jobnet Wait Condition Started log entry.

When no process ID is to be included in the log information:

N016ΔdateΔtimeΔKAVS4950-IΔscheduler-service-name:jobnet-name:execution-ID#

When a process ID is to be included in the log information:

N016ΔdateΔtimeΔ[process-ID]ΔKAVS4950-IΔscheduler-service-name:jobnet-name:execution-ID#

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

N016 Feb 28 17:48:54 KAVS4950-I AJSROOT1:/group/net1:@A100

The following table describes the items that are specific to these formats.

Table C‒28: Items specific to the Waiting in Accordance with the Jobnet Wait Condition Started log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

jobnet-name

The name of the jobnet or jobnet connector with the wait condition that started waiting is output.

1 to 930

execution-ID

The execution ID of the jobnet or jobnet connector with the wait condition that started waiting is output in @alphanumeric-character format.

1 to 10

(29) Formats of the Jobnet Wait Condition in Effect log entry

The following are the formats of the Jobnet Wait Condition in Effect log entry.

When no process ID is to be included in the log information:

N017ΔdateΔtimeΔKAVS4955-IΔscheduler-service-name:jobnet-name:execution-ID#Δfactor-establishing-wait-condition

When a process ID is to be included in the log information:

N017ΔdateΔtimeΔ[process-ID]ΔKAVS4955-IΔscheduler-service-name:jobnet-name:execution-ID#Δfactor-establishing-wait-condition

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

N017 Feb 26 18:48:54 KAVS4955-I AJSROOT1:/group/net1:@A101 2

The following table describes the items that are specific to these formats.

Table C‒29: Items specific to the Jobnet Wait Condition in Effect log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

jobnet-name

The name of the jobnet or jobnet connector with a wait condition that took effect is output.

1 to 930

execution-ID

The execution ID of the jobnet or jobnet connector with a wait condition that took effect is output in @alphanumeric-character format.

1 to 10

factor-establishing-wait-condition

The value of the factor establishing the wait condition is output.

1 to 4

(30) Formats of the Waiting in Accordance with the Jobnet Wait Condition Endless log entry

The following are the formats of the Waiting in Accordance with the Jobnet Wait Condition Endless log entry.

When no process ID is to be included in the log information:

N018ΔdateΔtimeΔKAVS4957-EΔname-of-unit-whose-end-is-being-waited-for:execution-IDΔscheduler-service-name:jobnet-nameexecution-ID#Δwait-retention-reason

When a process ID is to be included in the log information:

N018ΔdateΔtimeΔ[process-ID]ΔKAVS4957-EΔname-of-unit-whose-end-is-being-waited-for:execution-IDΔscheduler-service-name:jobnet-name:execution-ID#Δwait-retention-reason

#

:execution-ID for scheduler-service-name:jobnet-name is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

N018 Feb 26 18:48:54 KAVS4957-E /a:@A200 AJSROOT1:/group/net1:@A101 1

The following table describes the items that are specific to these formats.

Table C‒30: Items specific to the Waiting in Accordance with the Jobnet Wait Condition Endless log entry (scheduler information log)

Item

Description

Length (bytes)

name-of-unit-whose-end-is-being-waited-for

The name of the unit whose end is being waited for, specified in the wait condition, is output.

If the wait method is set to OR, three asterisks (***) are output.

1 to 930

execution-ID-of-unit-whose-end-is-being-waited-for

The execution ID of the unit whose end is being waited for is output in @alphanumeric-character format.

If the execution ID of the unit whose end is being waited for cannot be obtained, three asterisks (***) are output.

1 to 10

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

jobnet-name

The name of the jobnet or jobnet connector with a wait condition that took effect is output.

1 to 930

execution-ID

The execution ID of the jobnet or jobnet connector with a wait condition that took effect is output in @alphanumeric-character format.

1 to 10

wait-retention-reason

The value for the factor indicating why waiting in accordance with the wait condition could not end is output.

1 to 4

(31) Formats of the Job Started log entry

The following are the formats of the Job Started log entry.

When no process ID is to be included in the log information:

J001ΔdateΔtimeΔKAVS0263-IΔscheduler-service-name:job-name:execution-ID#Δexecution-host-name#Δjob-number#

When a process ID is to be included in the log information:

J001ΔdateΔtimeΔ[process-ID]ΔKAVS0263-IΔscheduler-service-name:job-name:execution-ID#Δexecution-host-name #Δjob-number #

#

:execution-IDΔexecution-host-name Δjob-number is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

J001 Dec 15 17:14:07 KAVS0263-I AJSROOT1:/group/net1/job1:@A100 hostA 1

The following table describes the items that are specific to these formats.

Table C‒31: Items specific to the Job Started log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

job-name

The name of the job that started is output.

1 to 930

execution-ID

The execution ID of the job that started is output in @alphanumeric-character format.

1 to 10

execution-host-name

The name of the execution host of the job that started is output.

1 to 255

job-number

The job number of the job that started is output as a decimal number.

1 to 10

(32) Formats of the Job Ended Normally log entry

The following are the formats of the Job Ended Normally log entry.

When no process ID is to be included in the log information:

J002ΔdateΔtimeΔKAVS0264-IΔscheduler-service-name:job-name:execution-ID#Δexecution-host-name#Δreturn-value #Δjob-number#

When a process ID is to be included in the log information:

J002ΔdateΔtimeΔ[process-ID]ΔKAVS0264-IΔscheduler-service-name:job-name:execution-ID#Δexecution-host-name #Δreturn-value#Δjob-number #

#

:execution-IDΔexecution-host-name Δreturn-valueΔjob-number is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

J002 Dec 15 17:14:44 KAVS0264-I AJSROOT1:/group/net1/job1:@A100 hostA 0 1

The following table describes the items that are specific to these formats.

Table C‒32: Items specific to the Job Ended Normally log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

job-name

The name of the job that ended is output.

1 to 930

execution-ID

The execution ID of the job that ended is output in @alphanumeric-character format.

1 to 10

execution-host-name

The name of the execution host of the job that ended is output.

If it ends before the job starts on the execution host, for example, because the job status changed, it might become blank.

1 to 255

return-value

The return value of the job that ended is output as a decimal number.

1 to 10

job-number

The job number of the job that ended is output as a decimal number.

1 to 10

(33) Formats of the Job Ended Abnormally log entry

The following are the formats of the Job Ended Abnormally log entry.

When no process ID is to be included in the log information:

J003ΔdateΔtimeΔKAVS0265-EΔscheduler-service-name:job-name:execution-ID#Δend-statusΔreturn-valueΔexecution-host-name#Δjob-number#

When a process ID is to be included in the log information:

J003ΔdateΔtimeΔ[process-ID]ΔKAVS0265-EΔscheduler-service-name:job-name:execution-ID#Δend-statusΔreturn-valueΔexecution-host-name #Δjob-number #

#

:execution-ID and Δexecution-host-name Δjob-number are output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

J003 Dec 01 14:05:45 KAVS0265-E AJSROOT1:/net1/nestnet1/job1:@A111 a 99 hostA 5

The following table describes the items that are specific to these formats.

Table C‒33: Items specific to the Job Ended Abnormally log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

job-name

The name of the job that ended abnormally is output.

1 to 930

execution-ID

The execution ID of the job that ended abnormally is output in @alphanumeric-character format.

1 to 10

end-status

One of the following is output:

- a: Ended abnormally

- f: Failed to start

- c: Killed

- ?: Unknown end status

1

return-value

The return value of the job that ended abnormally is output as a decimal number.

1 to 10

execution-host-name

The name of the execution host of the job that ended abnormally is output.

If it ends before the job starts on the execution host, for example, because the agent stopped or the job status changed, it might become blank.

1 to 255

job-number

The job number of the job that ended abnormally is output as a decimal number.

If the job could not be started because submission of the job failed, the job number is blank.

1 to 10

(34) Formats of the Job Ended with Warning log entry

The following are the formats of the Job Ended with Warning log entry.

When no process ID is to be included in the log information:

J004ΔdateΔtimeΔKAVS0269-WΔscheduler-service-name:job-name:execution-ID#Δreturn-valueΔexecution-host-name#Δjob-number#

When a process ID is to be included in the log information:

J004ΔdateΔtimeΔ[process-ID]ΔKAVS0269-WΔscheduler-service-name:job-name:execution-ID#Δreturn-valueΔexecution-host-name #Δjob-number #

#

:execution-ID and Δexecution-host-name Δjob-number are output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

J004 Dec 01 14:05:45 KAVS0269-W AJSROOT1:/net1/nestnet1/job1:@A111 99 hostA 5

The following table describes the items that are specific to these formats.

Table C‒34: Items specific to the Job Ended with Warning log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

job-name

The name of the job that ended with a warning is output.

1 to 930

execution-ID

The execution ID of the job that ended with a warning is output in @alphanumeric-character format.

1 to 10

return-value

The return value of the job that ended with a warning is output as a decimal number.

1 to 10

execution-host-name

The name of the execution host of the job that ended with a warning is output.

If it ends before the job starts on the execution host, for example, because the job status changed, it might become blank.

1 to 255

job-number

The job number of the job that ended with a warning is output as a decimal number.

1 to 10

(35) Formats of the Job on Hold log entry

The following are the formats of the Job on Hold log entry.

When no process ID is to be included in the log information:

J005ΔdateΔtimeΔKAVS0271-IΔscheduler-service-name:job-name:execution-ID#

When a process ID is to be included in the log information:

J005ΔdateΔtimeΔ[process-ID]ΔKAVS0271-IΔscheduler-service-name:job-name:execution-ID#

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

J005 Dec 01 14:05:45 KAVS0271-I AJSROOT1:/net1/nestnet1/job1:@A111

The following table describes the items that are specific to these formats.

Table C‒35: Items specific to the Job on Hold log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

job-name

The name of the job on hold is output.

1 to 930

execution-ID

The execution ID of the job on hold is output in @alphanumeric-character format.

1 to 10

(36) Formats of the Job Submission Started log entry

The following are the formats of the Job Submission Started log entry.

When no process ID is to be included in the log information:

J006ΔdateΔtimeΔKAVS0278-IΔscheduler-service-name:job-name:execution-ID#

When a process ID is to be included in the log information:

J006ΔdateΔtimeΔ[process-ID]ΔKAVS0278-IΔscheduler-service-name:job-name:execution-ID#

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

J006 Dec 15 17:14:01 KAVS0278-I AJSROOT1:/group/net1/job1:@A100

The following table describes the items that are specific to these formats.

Table C‒36: Items specific to the Job Submission Started log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

job-name

The name of the submitted job is output.

1 to 930

execution-ID

The execution ID of the submitted job is output in @alphanumeric-character format.

1 to 10

(37) Formats of the Event Job Execution Request Started log entry

The following are the formats of the Event Job Execution Request Started log entry.

When no process ID is to be included in the log information:

J007ΔdateΔtimeΔKAVS0242-IΔscheduler-service-name:event-job-name:execution-ID#

When a process ID is to be included in the log information:

J007ΔdateΔtimeΔ[process-ID]ΔKAVS0242-IΔscheduler-service-name: event-job-name:execution-ID#

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

J007 Dec 15 17:14:01 KAVS0242-I AJSROOT1:/group/net1/evjob1:@A100

The following table describes the items that are specific to these formats.

Table C‒37: Items specific to the Event Job Execution Request Started log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

event-job-name

The applicable event job name is output.

1 to 930

execution-ID

The execution ID of the event job is output in @alphanumeric-character format.

1 to 10

(38) Formats of the Job End Delayed log entry

The following are the formats of the Job End Delayed log entry.

When no process ID is to be included in the log information:

J008ΔdateΔtimeΔKAVS0248-IΔscheduler-service-name:job-name:execution-ID#

When a process ID is to be included in the log information:

J008ΔdateΔtimeΔ[process-ID]ΔKAVS0248-IΔscheduler-service-name: job-name:execution-ID#

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

J008 Dec 01 16:36:37 KAVS0248-I AJSROOT1:/group/net1/job1:@A106

The following table describes the items that are specific to these formats.

Table C‒38: Items specific to the Job End Delayed log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

job-name

The name of the job whose end was delayed is output.

1 to 930

execution-ID

The execution ID of the job whose end was delayed is output in @alphanumeric-character format.

1 to 10

(39) Formats of the Job Queuing Canceled log entry

The following are the formats of the Job Queuing Canceled log entry.

When no process ID is to be included in the log information:

J009ΔdateΔtimeΔKAVS0266-IΔscheduler-service-name:job-name:execution-ID#Δjob-number#

When a process ID is to be included in the log information:

J009ΔdateΔtimeΔ[process-ID]ΔKAVS0266-IΔscheduler-service-name:job-name:execution-ID#Δjob-number #

#

:execution-IDΔjob-number is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

J009 Dec 01 16:36:37 KAVS0266-I AJSROOT1:/group/net1/job1:@A100 1

The following table describes the items that are specific to these formats.

Table C‒39: Items specific to the Job Queuing Canceled log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

job-name

The name of the job that ended is output.

1 to 930

execution-ID

The execution ID of the job that ended is output in @alphanumeric-character format.

1 to 10

job-number

The job number of the job that ended is output as a decimal number.

1 to 10

(40) Formats of the Waiting in Accordance with the Job Wait Condition Started log entry

The following are the formats of the Waiting in Accordance with the Job Wait Condition Started log entry.

When no process ID is to be included in the log information:

J010ΔdateΔtimeΔKAVS4951-IΔscheduler-service-name:job-name:execution-ID#

When a process ID is to be included in the log information:

J010ΔdateΔtimeΔ[process-ID]ΔKAVS4951-IΔscheduler-service-name:job-name:execution-ID#

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

J010 Mar 28 14:48:54 KAVS4951-I AJSROOT1:/group/net1/job1:@A111

The following table describes the items that are specific to these formats.

Table C‒40: Items specific to the Waiting in Accordance with the Job Wait Condition Started log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

job-name

The name of the job with a wait condition that started waiting is output.

1 to 930

execution-ID

The execution ID of the job with a wait condition that started waiting is output in @alphanumeric-character format.

1 to 10

(41) Formats of the Job Wait Condition in Effect log entry

The following are the formats of the Job Wait Condition in Effect leg entry.

When no process ID is to be included in the log information:

ΔdateΔtimeΔKAVS4956-IΔscheduler-service-name:job-name:execution-ID#Δfactor-establishing-wait-condition

When a process ID is to be included in the log information:

J011ΔdateΔtimeΔ[process-ID]ΔKAVS4956-IΔscheduler-service-name:job-name:execution-ID#Δfactor-establishing-wait-condition

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

J011 Mar 26 18:48:54 KAVS4956-I AJSROOT1:/group/net1/job1:@A111 2

The following table describes the items that are specific to these formats.

Table C‒41: Items specific to the Job Wait Condition in Effect log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

job-name

The name of the job with a wait condition that took effect is output.

1 to 930

execution-ID

The execution ID of the job with a wait condition that took effect is output in @alphanumeric-character format.

1 to 10

factor-establishing-wait-condition

The value of the factor establishing the wait condition is output.

1 to 4

(42) Formats of the Waiting in Accordance with the Job Wait Condition Endless log entry

The following are the formats of the Waiting in Accordance with the Job Wait Condition Endless log entry.

When no process ID is to be included in the log information:

J012ΔdateΔtimeΔKAVS4971-EΔname-of-unit-whose-end-is-being-waited-for:execution-IDΔscheduler-service-name:job-name:execution-ID#Δwait-retention-reason

When a process ID is to be included in the log information:

J012ΔdateΔtimeΔ[process-ID]ΔKAVS4971-EΔname-of-unit-whose-end-is-being-waited-for:execution-IDΔscheduler-service-name:job-name:execution-ID#Δwait-retention-reason

#

:execution-ID for scheduler-service-name:job-name is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

J012 Mar 26 18:48:54 KAVS4971-E /a:@A200 AJSROOT1:/group/net1/job1:@A111 2

The following table describes the items that are specific to these formats.

Table C‒42: Items specific to the Waiting in Accordance with the Job Wait Condition Endless log entry (scheduler information log)

Item

Description

Length (bytes)

name-of-unit-whose-end-is-being-waited-for

The name of the unit whose end is being waited for specified in the wait condition is output.

If the wait method is set to OR, three asterisks (***) are output.

1 to 930

execution-ID-of-unit-whose-end-is-being-waited-for

The execution ID of the unit whose end is being waited for is output in @alphanumeric-character format.

If the execution ID of the unit whose end is being waited for cannot be obtained, three asterisks (***) are output.

1 to 10

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

job-name

The name of the job with a wait condition that took effect is output.

1 to 930

execution-ID

The execution ID of the job with a wait condition that took effect is output in @alphanumeric-character format.

1 to 10

wait-retention-reason

The value for the factor indicating why waiting in accordance with the wait condition could not end is output.

1 to 4

(43) Formats of the Waiting for Automatic Retry Interval Started log entry

The following are the formats of the Waiting for the Automatic Retry Interval Started log entry.

When no process ID is to be included in the log information:

J013ΔdateΔtimeΔKAVS4675-IΔscheduler-service-name:job-name:execution-ID#Δreturn-valueΔexecution-host-name#Δjob-number#Δnumber-of-retry-executions

When a process ID is to be included in the log information:

J013ΔdateΔtimeΔ[process-ID]ΔKAVS4675-IΔscheduler-service-name:job-name:execution-ID#Δreturn-valueΔexecution-host-name#Δjob-number#Δnumber-of-retry-executions

#

:execution-ID and Δexecution-host-name Δjob-number are output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

J013 Mar 03 14:05:45 KAVS4675-I AJSROOT1:/net1/nestnet1/job1:@A111 99 hostA 5 3

The following table describes the items that are specific to these formats.

Table C‒43: Items specific to the Waiting for the Automatic Retry Interval Started log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

job-name

The name of the job that starts waiting for the retry interval is output.

1 to 930

execution-ID

The execution ID of the job that starts waiting for the retry interval is output in @alphanumeric-character format.

1 to 10

return-value

The return value of the job that starts waiting for the retry interval is output as a decimal number.

1 to 10

execution-host-name

The name of the execution host of the job that starts waiting for the retry interval is output.

1 to 255

job-number

The job number of the job that starts waiting for the retry interval is output as a decimal number.

If the job could not be started because submission of the job failed, the job number is blank.

1 to 10

number-of-retry-executions

The number of retry executions for the job that starts waiting for the retry interval is output as a decimal number.

1 to 2

(44) Formats of the Automatic Retry Execution Started log entry

The following are the formats of the Automatic Retry Execution Started log entry.

When no process ID is to be included in the log information:

J014ΔdateΔtimeΔKAVS4676-IΔscheduler-service-name:job-name:execution-ID#Δexecution-host-name#Δjob-number#Δnumber-of-retry-executions

When a process ID is to be included in the log information:

J014ΔdateΔtimeΔ[process-ID]ΔKAVS4676-IΔscheduler-service-name:job-name:execution-ID#Δexecution-host-name#Δjob-number#Δnumber-of-retry-executions

#

:execution-IDΔexecution-host-name Δjob-number is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

J014 Feb 28 17:14:07 KAVS4676-I AJSROOT1:/group/net1/job1:@A100 hostA 1 3

The following table describes the items that are specific to these formats.

Table C‒44: Items specific to the Automatic Retry Execution Started log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

job-name

The name of the job whose execution is started by automatic retry is output.

1 to 930

execution-ID

The execution ID of the job whose execution is started by automatic retry is output in @alphanumeric-character format.

1 to 10

execution-host-name

The name of the execution host of the job whose execution is started by automatic retry is output.

1 to 255

job-number

The job number of the job whose execution is started by automatic retry is output as a decimal number.

1 to 10

number-of-retry-executions

The number of retry executions for the job whose execution is started by automatic retry is output as a decimal number.

1 to 2

(45) Formats of the Error That Disables Retry Execution Occurring During Automatic Retry log entry

The following are the formats of the Error That Disables Retry Execution Occurring During Automatic Retry log entry.

When no process ID is to be included in the log information:

J015ΔdateΔtimeΔKAVS4677-EΔscheduler-service-name:job-name:execution-ID#Δreturn-valueΔexecution-host-name#Δjob-number#Δnumber-of-retry-executionsΔreason-code

When a process ID is to be included in the log information:

J015ΔdateΔtimeΔ[process-ID]ΔKAVS4677-EΔscheduler-service-name:job-name:execution-ID#Δreturn-valueΔexecution-host-name#Δjob-number#Δnumber-of-retry-executionsΔreason-code

#

:execution-ID and Δexecution-host-name Δjob-number are output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

J015 Mar 03 14:05:45 KAVS4677-E AJSROOT1:/net1/nestnet1/job1:@A111 99 hostA 5 3 FATALERR

The following table describes the items that are specific to these formats.

Table C‒45: Items specific to the Error That Disables Retry Execution Occurring During Automatic Retry log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

job-name

The name of the job for which automatic retry ended due to an error that disables retry execution is output.

1 to 930

execution-ID

The execution ID of the job for which automatic retry ended due to an error that disables retry execution is output in @alphanumeric-character format.

1 to 10

return-value

The return value of the job for which automatic retry ended due to an error that disables retry execution is output as a decimal number.

1 to 10

execution-host-name

The name of the execution host of the job for which automatic retry ended due to an error that disables retry execution is output.

If it ends before the job starts on the execution host, for example, because the agent stopped, it might become blank.

1 to 255

job-number

The job number of the job for which automatic retry ended due to an error that disables retry execution is output as a decimal number.

If the job could not be started because submission of the job failed, the job number is blank.

1 to 10

number-of-retry-executions

The number of retry executions for the job for which automatic retry ended due to an error that disables retry execution is output as a decimal number.

1 to 2

reason-code

The reason for ending automatic retry is output.

FATALERR

The job ended in an end status that does not allow a retry.

ERRCODE

The executable file or script file ended with a return code that is outside the scope of automatic retry.

RETRYNUM

The number of retry executions reached the maximum number of retry executions.

7 or 8

(46) Formats of the Job Submission by Automatic Retry Started log entry

The following are the formats of the Job Submission by Automatic Retry Started log entry.

When no process ID is to be included in the log information:

J016ΔdateΔtimeΔKAVS4678-IΔscheduler-service-name:job-name:execution-ID#Δnumber-of-retry-executions

When a process ID is to be included in the log information:

J016ΔdateΔtimeΔ[process-ID]ΔKAVS4678-IΔscheduler-service-name:job-name:execution-ID#Δnumber-of-retry-executions

#

:execution-ID is output if yes is specified in the LOGINFOALL environment setting parameter.

Example of a log entry:

J016 Feb 28 17:14:01 KAVS4678-I AJSROOT1:/group/net1/job1:@A100 3

The following table describes the items that are specific to these formats.

Table C‒46: Items specific to the Job Submission by Automatic Retry Started log entry (scheduler information log)

Item

Description

Length (bytes)

scheduler-service-name

The applicable scheduler service name is output.

1 to 30

job-name

The name of the job submitted by automatic retry is output.

1 to 930

execution-ID

The execution ID of the job submitted by automatic retry is output in @alphanumeric-character format.

1 to 10

number-of-retry-executions

The number of retry executions for the job submitted by automatic retry is output as a decimal number.

1 to 2

(47) Formats of the Scheduler Service Operation Environment Temporarily Changed log entry

The following are the formats of the Scheduler Service Operation Environment Temporarily Changed log entry.

When no process ID is to be included in the log information:

C001ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;ALTERΔoption

When a process ID is to be included in the log information:

C001ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;ALTERΔoption

Logging conditions:

An entry is output to the log only if all or alter is specified in the OPELOG environment setting parameter.

Example of a log entry:

C001 Dec 15 09:51:41 jp1admin 0 JP1_DEFAULT ;ALTER -F AJSROOT1 -c COPY

The following table describes the items that are specific to these formats.

Table C‒47: Items specific to the Scheduler Service Operation Environment Temporarily Changed log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsalter command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

option

The options specified in the executed ajsalter command are output.

1 or more

(48) Formats of the Scheduler Service Stopped log entry

The following are the formats of the Scheduler Service Stopped log entry.

When no process ID is to be included in the log information:

C002ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;STOPΔoption

When a process ID is to be included in the log information:

C002ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;STOPΔoption

Logging conditions:

An entry is output to the log only if all or stop is specified in the OPELOG environment setting parameter.

Example of a log entry:

C002 Dec 15 09:53:08 jp1admin 0 JP1_DEFAULT ;STOP -F AJSROOT1 -w -c

The following table describes the items that are specific to these formats.

Table C‒48: Items specific to the Scheduler Service Stopped log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsstop command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

option

The options specified in the executed ajsstop command are output.

1 or more

(49) Formats of the Scheduler Service Started log entry

The following are the formats of the Scheduler Service Started log entry.

When no process ID is to be included in the log information:

C003ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;STARTΔoption

When a process ID is to be included in the log information:

C003ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;STARTΔoption

Logging conditions:

An entry is output to the log only if all or start is specified in the OPELOG environment setting parameter.

Example of a log entry:

C003 Dec 07 19:26:59 jp1admin 0 JP1_DEFAULT ;START -F AJSROOT1 -w -o

The following table describes the items that are specific to these formats.

Table C‒49: Items specific to the Scheduler Service Started log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsstart command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

option

The options specified in the executed ajsstart command are output.

1 to 500

(50) Formats of the Jobnet Registered log entry

The following are the formats of the Jobnet Registered log entry.

When no process ID is to be included in the log information:

C101ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;ENTRYΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

When a process ID is to be included in the log information:

C101ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;ENTRYΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or entry is specified in the OPELOG environment setting parameter.

Example of a log entry:

C101 Dec 15 10:51:18 jp1admin KAVS0681-E JP1_DEFAULT ;ENTRY -F AJSROOT1 -s /group/net1

The following table describes the items that are specific to these formats.

Table C‒50: Items specific to the Jobnet Registered log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsentry command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Web Console

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View, JP1/AJS3 - Web Console or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS3-WEB

Indicates that the operation was performed from JP1/AJS3 - Web Console.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the executed ajsentry command are output.

If the yes is specified for the AJSLOGOUTPUTEXTEND environment setting parameter, the value of the -c option is output.

1 to 500

unit-name

The unit name specified in the executed ajsentry command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(51) Formats of the Registered Jobnet Canceled log entry

The following are the formats of the Registered Jobnet Canceled log entry.

When no process ID is to be included in the log information:

C102ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;LEAVEΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

When a process ID is to be included in the log information:

C102ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;LEAVEΔ[user-type] #Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or leave is specified in the OPELOG environment setting parameter.

Example of a log entry:

C102 Dec 01 14:03:14 jp1admin 0 JP1_DEFAULT ;LEAVE -F AJSROOT1 -B all /net1

The following table describes the items that are specific to these formats.

Table C‒51: Items specific to the Registered Jobnet Canceled log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsleave command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Web Console

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View, JP1/AJS3 - Web Console or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS3-WEB

Indicates that the operation was performed from JP1/AJS3 - Web Console.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the executed ajsleave command are output.

1 to 500

unit-name

The unit name specified in the executed ajsleave command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(52) Formats of the Jobnet Temporarily Changed log entry

The following are the formats of the Jobnet Temporarily Changed log entry.

When no process ID is to be included in the log information:

C103ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;PLANΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

When a process ID is to be included in the log information:

C103ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;PLANΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or plan is specified in the OPELOG environment setting parameter.

Example of a log entry:

C103 Dec 15 09:55:10 jp1admin 0 JP1_DEFAULT ;PLAN -F AJSROOT1 -r -X auto /net1

The following table describes the items that are specific to these formats.

Table C‒52: Items specific to the Jobnet Temporarily Changed log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsplan command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Web Console

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View, JP1/AJS3 - Web Console or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS3-WEB

Indicates that the operation was performed from JP1/AJS3 - Web Console.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the executed ajsplan command are output.

1 to 500

unit-name

The unit name specified in the executed ajsplan command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(53) Formats of the Jobnet Execution Interrupted log entry

The following are the formats of the Jobnet Execution Interrupted log entry.

When no process ID is to be included in the log information:

C104ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;INTRPTΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

When a process ID is to be included in the log information:

C104ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;INTRPTΔ[user-type] #Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or intrpt is specified in the OPELOG environment setting parameter.

Example of a log entry:

C104 Dec 15 09:56:36 jp1admin 0 JP1_DEFAULT ;INTRPT -F AJSROOT1 -X auto /net1

The following table describes the items that are specific to these formats.

Table C‒53: Items specific to the Jobnet Execution Interrupted log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsintrpt command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Web Console

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View, JP1/AJS3 - Web Console or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS3-WEB

Indicates that the operation was performed from JP1/AJS3 - Web Console.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the executed ajsintrpt command are output.

1 to 500

unit-name

The unit name specified in the executed ajsintrpt command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(54) Formats of the Jobnet Rerun log entry

The following are the formats of the Jobnet Rerun log entry.

When no process ID is to be included in the log information:

C105ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;RERUNΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

When a process ID is to be included in the log information:

C105ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;RERUNΔ[user-type] #Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or rerun is specified in the OPELOG environment setting parameter.

Example of a log entry:

C105 Dec 07 16:36:47 jp1admin KAVS0141-E JP1_DEFAULT ;RERUN -F AJSROOT1 -t -X no /group/net1:@A118

The following table describes the items that are specific to these formats.

Table C‒54: Items specific to the Jobnet Rerun log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsrerun command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Web Console

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View, JP1/AJS3 - Web Console or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS3-WEB

Indicates that the operation was performed from JP1/AJS3 - Web Console.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the executed ajsrerun command are output.

1 to 500

unit-name

The unit name specified in the executed ajsrerun command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(55) Formats of the Jobnet Suspended/Released from Suspension log entry

The following are the formats of the Jobnet Suspended/Released from Suspension log entry.

When no process ID is to be included in the log information:

C106ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;SUSPENDΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

When a process ID is to be included in the log information:

C106ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;SUSPENDΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or suspend is specified in the OPELOG environment setting parameter.

Example of a log entry:

C106 Dec 07 16:36:14 jp1admin 0 JP1_DEFAULT ;SUSPEND -F AJSROOT1 -C -r /group/net1

The following table describes the items that are specific to these formats.

Table C‒55: Items specific to the Jobnet Suspended/Released from Suspension log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajssuspend command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the executed ajssuspend command are output.

1 to 500

unit-name

The unit name specified in the executed ajssuspend command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(56) Formats of the Jobnet Registration for Execution Information Imported log entry

The following are the formats of the Jobnet Registration for Execution Information Imported log entry.

When no process ID is to be included in the log information:

C107ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;RGIMPΔ[user-type]#Δoption

When a process ID is to be included in the log information:

C107ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;RGIMPΔ[user-type]#Δoption

#

Δ[user-type] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or rgimport is specified in the OPELOG environment setting parameter.

Example of a log entry:

C107 Dec 07 19:14:15 jp1admin KAVS0681-E JP1_DEFAULT ;RGIMP -F AJSROOT1 -i c:\temp\entry_info.txt

The following table describes the items that are specific to these formats.

Table C‒56: Items specific to the Jobnet Registration for Execution Information Imported log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsrgimport command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

option#

The options specified in the executed ajsrgimport command are output.

1 to 500

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(57) Formats of the Jobnet Registered by Import of Jobnet Registration for Execution Information log entry

The following are the formats of the Jobnet Registered by Import of Jobnet Registration for Execution Information log entry.

When no process ID is to be included in the log information:

C108ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;RGIMPΔ[user-type]#ΔoptionΔunit-name

When a process ID is to be included in the log information:

C108ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;RGIMPΔ[user-type]#ΔoptionΔunit-name

#

Δ[user-type] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or rgimport is specified in the OPELOG environment setting parameter.

Example of a log entry:

C108 Dec 07 19:14:15 jp1admin KAVS4832-E JP1_DEFAULT ;RGIMP -F AJSROOT1 /group/net1

The following table describes the items that are specific to these formats.

Table C‒57: Items specific to the Jobnet Registered by Import of Jobnet Registration for Execution Information log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsrgimport command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

option#

The options that are output are the ones specified in the ajsrgimport command when the command was used to register the jobnet.

1 to 500

unit-name

The root jobnet name that is output is name actually registered by using the ajsrgimport command.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(58) Formats of the Jobnet/Job Forcibly Ended log entry

The following are the formats of the Jobnet/Job Forcibly Ended log entry.

When no process ID is to be included in the log information:

C201ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;KILLΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

When a process ID is to be included in the log information:

C201ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;KILLΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or kill is specified in the OPELOG environment setting parameter.

Example of a log entry:

C201 Dec 07 19:14:15 jp1admin KAVS0129-E JP1_DEFAULT ;KILL -F AJSROOT1 -X no /group/net1:@A137

The following table describes the items that are specific to these formats.

Table C‒58: Items specific to the Jobnet/Job Forcibly Ended log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajskill command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Web Console

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View, JP1/AJS3 - Web Console or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS3-WEB

Indicates that the operation was performed from JP1/AJS3 - Web Console.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the executed ajskill command are output.

1 to 500

unit-name

The unit name specified in the executed ajskill command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(59) Formats of the Job Status Changed log entry

The following are the formats of the Job Status Changed log entry.

When no process ID is to be included in the log information:

C202ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;CHGSTATΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

When a process ID is to be included in the log information:

C202ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;CHGSTATΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or chgst is specified in the OPELOG environment setting parameter.

Example of a log entry:

C202 Dec 15 09:58:13 jp1admin 0 JP1_DEFAULT ;CHGSTAT -F AJSROOT1 -t normal -X auto /net1/job

The following table describes the items that are specific to these formats.

Table C‒59: Items specific to the Job Status Changed log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajschgstat command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Web Console

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View, JP1/AJS3 - Web Console or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS3-WEB

Indicates that the operation was performed from JP1/AJS3 - Web Console.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the executed ajschgstat command are output.

1 to 500

unit-name

The unit name specified in the executed ajschgstat command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(60) Formats of the Unit Definitions Changed log entry

The following are the formats of the Unit Definitions Changed log entry.

When no process ID is to be included in the log information:

C301ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;CHANGEΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification]#ΔoptionΔunit-name

When a process ID is to be included in the log information:

C301ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;CHANGEΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification]#ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification]Δoption is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or change is specified in the OPELOG environment setting parameter.

Logging example for commands:

When Monthly Jobnet is specified as the comment and 10 is specified as the number of saved generations:

C301 Dec 07 13:59:30 jp1admin 0 JP1_DEFAULT ;CHANGE [ADMIN] [CHANGE] -F AJSROOT1 -C "Monthly Jobnet" -l "10" /net

Logging examples for JP1/AJS3 - View:

When c:\user\pgm.exe is specified as the execution file name and 1 is specified as the execution priority:

C301 Mar 05 13:59:30 jp1admin 0 JP1_DEFAULT ;CHANGE [ADMIN] [127.0.0.1, JP1/AJS2-View] [VIEW] pr=1; sc="c:\user\pgm.exe"; AJSROOT1:/net/job

When the execution file name is blank and None (default) is specified as the execution priority:

C301 Mar 05 13:59:30 jp1admin 0 JP1_DEFAULT ;CHANGE [ADMIN] [127.0.0.1, JP1/AJS2-View] [VIEW] pr=; sc=; AJSROOT1:/net/job

When schedule rule 1 is copied to create schedule rule 2:

C301 Dec 07 13:59:30 jp1admin 0 JP1_DEFAULT ; CHANGE [ADMIN] [127.0.0.1, JP1/AJS2-View] [VIEW] sd; st; cy; sh; shd; AJSROOT1:/net

For the parameters listed below, the difference between the new and previous definitions cannot be extracted because the number of parameters that can be specified and parameter lengths are variable. Accordingly, only the names of the applicable parameters are recorded in the log entry.

sd, st, sy, ey, ln, cy, sh, shd, wt, wc, cftd, el, ar, env, evwfr, jpoif, mladr, mlsbj, mltxt, mlatf, lftpd, lffnm, lfmks, hlsh, hleh

Note that if only the sequence of the parameters is changed (the definitions of the parameters do not change), the difference in the sequence is not output, although the Unit Definitions Changed log entry is still output to the file.

Logging examples for JP1/AJS3 - Web Console:

When c:\user\pgm.exe is specified as the execution file name and 1 is specified as the execution priority:

C301 Mar 05 13:59:30 jp1admin 0 JP1_DEFAULT ;CHANGE [ADMIN] [127.0.0.1, JP1/AJS3-WEB] [WEB] pr=1; sc="c:\user\pgm.exe"; AJSROOT1:/net/job

When the execution file name is blank and None (default) is specified as the execution priority:

C301 Mar 05 13:59:30 jp1admin 0 JP1_DEFAULT ;CHANGE [ADMIN] [127.0.0.1, JP1/AJS3-WEB] [WEB] pr=; sc=; AJSROOT1:/net/job

For the parameter listed below, the difference between the new and previous definitions cannot be extracted because the number of parameters that can be specified and parameter lengths are variable. Accordingly, only the names of the applicable a parameter are recorded in the log entry.

env

Note that if only the sequence of the parameters is changed (the definitions of the parameters do not change), the difference in the sequence is not output, although the Unit Definitions Changed log entry is still output to the file.

The following table describes the items that are specific to these formats.

Table C‒60: Items specific to the Unit Definitions Changed log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajschange, ajschgjob, or ajschgnet command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Web Console

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View, JP1/AJS3 - Web Console or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS3-WEB

Indicates that the operation was performed from JP1/AJS3 - Web Console.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the executed ajschange, ajschgnet, or ajschgjob command, or the changes made by a user from JP1/AJS3 - View or JP1/AJS3 - Web Console are output.

For 08-00 or earlier, command options are not output.

For 08-10 or later, command options or the changes made by the user from JP1/AJS3 - View are output if yes is specified in AJSLOGOUTPUTEXTEND.

In option, the type of the definition change operation and then the options of the applicable command or the changes made by the user from JP1/AJS3 - View are output.

The definition change operation types are as follows:

For ajschange: CHANGE

For ajschgnet: CHGNET

For ajschgjob: CHGJOB

For JP1/AJS3 - View: VIEW

For JP1/AJS3 - Web Console: WEB

1 to 510

unit-name

The unit name specified in the executed ajschange, ajschgnet, or ajschgjob command, or the name of the unit for which operations were performed from JP1/AJS3 - View or JP1/AJS3 - Web Console is output.

For the ajschange, ajschgnet, and ajschgjob commands, unit names do not include scheduler service names. However, if the target is a scheduler service, the indication in option is -f scheduler-service-name. For JP1/AJS3 - View or JP1/AJS3 - Web Console, unit names include scheduler service names.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) or the value of the parameter to be changed (the part that is not the parameter name and the subsequent one-byte equal sign (=)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options or parameters exceeds 500 bytes, only 500 bytes are output. Note that the 500-byte limit is exceeded before an option name or a parameter name is complete, that option or parameter is not output.

(61) Formats of the Unit Deleted log entry

The following are the formats of the Unit Deleted log entry.

When no process ID is to be included in the log information:

C302ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;DELETEΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

When a process ID is to be included in the log information:

C302ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;DELETEΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or delete is specified in the OPELOG environment setting parameter.

Example of a log entry:

C302 Dec 07 12:25:43 jp1admin 0 JP1_DEFAULT ;DELETE -F AJSROOT1 -S /group/net1

The following table describes the items that are specific to these formats.

Table C‒61: Items specific to the Unit Deleted log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsdelete command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the executed ajsdelete command are output.

1 to 500

unit-name

The unit name specified in the executed ajsdelete command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(62) Formats of the Unit Restored log entry

The following are the formats of the Unit Restored log entry.

When no process ID is to be included in the log information:

C303ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;RESTOREΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

When a process ID is to be included in the log information:

C303ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;RESTOREΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or restore is specified in the OPELOG environment setting parameter.

Example of a log entry:

C303 Dec 07 10:00:22 jp1admin 0 JP1_DEFAULT ;RESTORE -F AJSROOT1 -e -n box

The following table describes the items that are specific to these formats.

Table C‒62: Items specific to the Unit Restored log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsrestore command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the executed ajsrestore command are output.

1 to 500

unit-name

The unit name specified in the executed ajsrestore command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(63) Formats of the Unit Created log entry

The following are the formats of the Unit Created log entry.

When no process ID is to be included in the log information:

C304ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;DEFINEΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

When a process ID is to be included in the log information:

C304ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;DEFINEΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or define is specified in the OPELOG environment setting parameter.

Example of a log entry:

C304 Dec 07 14:00:46 jp1admin 0 JP1_DEFAULT ;DEFINE -F AJSROOT1 /net1

The following table describes the items that are specific to these formats.

Table C‒63: Items specific to the Unit Created log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsdefine command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the executed ajsdefine command are output only for an abnormal termination.

1 to 500

unit-name or definition file name

The unit name or the definition file name specified in the executed ajsdefine command is output.

The unit name is output for a normal termination.

The definition file name is output for an abnormal termination.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(64) Formats of the Unit Copied or Moved log entry

The following are the formats of the Unit Copied or Moved log entry.

When no process ID is to be included in the log information:

C305ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;COPYΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

When a process ID is to be included in the log information:

C305ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;COPYΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or copy is specified in the OPELOG environment setting parameter.

Example of a log entry:

C305 Dec 15 11:21:57 jp1admin 0 JP1_DEFAULT ;COPY -F AJSROOT1 -c -o /group/net1/job11 /group/net1/job1

The following table describes the items that are specific to these formats.

Table C‒64: Items specific to the Unit Copied or Moved log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajscopy command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the executed ajscopy command are output.

1 to 500

unit-name

The unit name specified in the executed ajscopy command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(65) Formats of the Unit Imported log entry

The following are the formats of the Unit Imported log entry.

When no process ID is to be included in the log information:

C306ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;IMPORTΔ[user-type]#Δoption

When a process ID is to be included in the log information:

C306ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;IMPORTΔ[user-type]#Δoption

#

Δ[user-type] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or import is specified in the OPELOG environment setting parameter.

Example of a log entry:

C306 Dec 15 09:14:22 jp1admin 0 JP1_DEFAULT ;IMPORT -i c:\temp\file AJSROOT1:/group/net

The following table describes the items that are specific to these formats.

Table C‒65: Items specific to the Unit Imported log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsimport command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

option#

The options specified in the executed ajsimport command are output.

1 to 500

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(66) Formats of the Jobnet Released log entry

The following are the formats of the Jobnet Released log entry.

When no process ID is to be included in the log information:

C307ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;RELEASEOPEΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #Δoption

When a process ID is to be included in the log information:

C307ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;RELEASEOPEΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #Δoption

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or release is specified in the OPELOG environment setting parameter.

Example of a log entry:

C307 Dec 15 13:28:49 jp1admin 0 JP1_DEFAULT ;RELEASEOPE -F AJSROOT1 -a /Production Environment/unit001 -rid 001 -rcm 2009/12/07 Release Definition -rdy 2009/12/07 -rti 20:00 -ru /Test Environment/Rel001

The following table describes the items that are specific to these formats.

Table C‒66: Items specific to the Jobnet Released log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsrelease command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from JP1/AJS3 - View.

7 to 15

requesting-source-identification

The information for identifying the source requesting the operation is output. JP1/AJS2-View is displayed only when the operation was performed from JP1/AJS3 - View.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the executed ajsrelease command are output.

1 to 500

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(67) Formats of the Calendar Changed log entry

The following are the formats of the Calendar Changed log entry.

When no process ID is to be included in the log information:

C401ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;CALENDARΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

When a process ID is to be included in the log information:

C401ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;CALENDARΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or calendar is specified in the OPELOG environment setting parameter.

If you used JP1/AJS3 - View to change a calendar when yes was specified in the AJSLOGOUTPUTEXTEND environment setting parameter, the changes are not output in the Command Processing Started log entry corresponding to the Calendar Changed log entry.

Example of a log entry:

C401 Dec 15 10:49:45 jp1admin 0 JP1_DEFAULT ;CALENDAR -F AJSROOT1 mo we /

The following table describes the items that are specific to these formats.

Table C‒67: Items specific to the Calendar Changed log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajscalendar command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the executed ajscalendar command or the changes made by the user from JP1/AJS3 - View are output.

If no is specified in the AJSLOGOUTPUTEXTEND environment setting parameter, one of the following values is output for option to indicate the type of change:

When a calendar is changed: mo

When a standard week value is changed: we

When a base date is changed: sd

When a base time is changed: st

If yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter, the options specified in the executed ajscalendar command or the name of the definition parameter changed by the user from JP1/AJS3 - View is output for option.

The name of the definition parameter to be output is as follows when JP1/AJS3 - View is used to change the parameter:

When an open day is added or deleted: op

When a closed day is added or deleted: cl

When a base date is changed: sdd

When a base month for the calendar is changed: md

When a base time is changed: stt

1 to 500

unit-name

The unit name specified in the executed ajscalendar command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(68) Formats of the Unit Status Displayed log entry

The following are the formats of the Unit Status Displayed log entry.

When no process ID is to be included in the log information:

C502ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;SHOWΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

When a process ID is to be included in the log information:

C502ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;SHOWΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or show is specified in the REFLOG environment setting parameter.

Example of a log entry:

C502 Dec 07 09:14:22 jp1admin 0 JP1_DEFAULT ;SHOW -F AJSROOT1 -l -g 1 -X auto /group/*

The following table describes the items that are specific to these formats.

Table C‒68: Items specific to the Unit Status Displayed log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsshow command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

Always 0.

1

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the executed ajsshow command are output. Note that the value specified for the -f, -t, or -i option is always enclosed in double quotation marks ("").

1 to 500

unit-name

The unit name specified in the executed ajsshow command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(69) Formats of the Unit Definitions Output log entry

The following are the formats of the Unit Definitions Output log entry.

When no process ID is to be included in the log information:

C503ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;PRINTΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

When a process ID is to be included in the log information:

C503ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;PRINTΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or print is specified in the REFLOG environment setting parameter.

Example of a log entry:

C503 Dec 07 09:14:22 jp1admin 0 JP1_DEFAULT ;PRINT -F AJSROOT1 -a /group/*

The following table describes the items that are specific to these formats.

Table C‒69: Items specific to the Unit Definitions Output log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsprint command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

Always 0.

1

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the executed ajsprint command are output. Note that the value specified for the -f or -t option is always enclosed in double quotation marks ("").

1 to 500

unit-name

The unit name specified in the executed ajsprint command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(70) Formats of the Unit Definitions Backed Up log entry

The following are the formats of the Unit Definitions Backed Up log entry.

When no process ID is to be included in the log information:

C504ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;BACKUPΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

When a process ID is to be included in the log information:

C504ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;BACKUPΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or backup is specified in the REFLOG environment setting parameter.

Example of a log entry:

C504 Dec 07 09:14:22 jp1admin 0 JP1_DEFAULT ;BACKUP -F AJSROOT1 -b c:\tmp\backup -e -a -n BOX /group

The following table describes the items that are specific to these formats.

Table C‒70: Items specific to the Unit Definitions Backed Up log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsbackup command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

Always 0.

1

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the executed ajsbackup command are output.

1 to 500

unit-name

The unit name specified in the executed ajsbackup command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(71) Formats of the Root Jobnet Schedule Information Output log entry

The following are the formats of the Root Jobnet Schedule Information Output log entry.

When no process ID is to be included in the log information:

C506ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;SCHEDULEΔ[user-type]#ΔoptionΔunit-name

When a process ID is to be included in the log information:

C506ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;SCHEDULEΔ[user-type]#ΔoptionΔunit-name

#

Δ[user-type] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or schedule is specified in the REFLOG environment setting parameter.

Example of a log entry:

C506 Dec 07 09:14:22 jp1admin 0 JP1_DEFAULT ;SCHEDULE -F AJSROOT1 -b 2009/12/8 -e 2009/12/8 /group/net

The following table describes the items that are specific to these formats.

Table C‒71: Items specific to the Root Jobnet Schedule Information Output log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsschedule command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 to 5

option#

The options specified in the executed ajsschedule command are output.

1 to 500

unit-name

The root jobnet name specified in the executed ajsschedule command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(72) Formats of the Unit Name Output log entry

The following are the formats of the Unit Name Output log entry.

When no process ID is to be included in the log information:

C507ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;NAMEΔ[user-type]#ΔoptionΔunit-name

When a process ID is to be included in the log information:

C507ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;NAMEΔ[user-type]#ΔoptionΔunit-name

#

Δ[user-type] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or name is specified in the REFLOG environment setting parameter.

Example of a log entry:

C507 Dec 15 09:14:22 jp1admin 0 JP1_DEFAULT ;NAME -F AJSROOT1 /group/*

The following table describes the items that are specific to these formats.

Table C‒72: Items specific to the Unit Name Output log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsname command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

Always 0.

1

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

option#

The options specified in the executed ajsname command are output.

1 to 500

unit-name

The unit name specified in the executed ajsname command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(73) Formats of the Unit Definitions Exported log entry

The following are the formats of the Unit Definitions Exported log entry.

When no process ID is to be included in the log information:

C508ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;EXPORTΔ[user-type]#Δoption

When a process ID is to be included in the log information:

C508ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;EXPORTΔ[user-type]#Δoption

#

Δ[user-type] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or export is specified in the REFLOG environment setting parameter.

Example of a log entry:

C508 Dec 15 09:14:22 jp1admin 0 JP1_DEFAULT ;EXPORT -o c:\temp\file AJSROOT1:/group/net

The following table describes the items that are specific to these formats.

Table C‒73: Items specific to the Unit Definitions Exported log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsexport command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

option#

The options specified in the executed ajsexport command are output.

1 to 500

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(74) Formats of the Unit Status Displayed (Abnormal End) log entry

The following are the formats of the Unit Status Displayed (Abnormal End) log entry.

When no process ID is to be included in the log information:

C509ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;SHOWΔ[user-type]Δ[requesting-host-IP-address,requesting-source-identification]ΔoptionΔunit-name

When a process ID is to be included in the log information:

C509ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;SHOWΔ[user-type]Δ[requesting-host-IP-address,requesting-source-identification]ΔoptionΔunit-name

Logging conditions:

An entry is output to the log only if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter, and all or show is specified in the REFLOG environment setting parameter.

Example of a log entry:

C509 Mar 05 12:18:06 [2688] jp1admin KAVS0161-I JP1_DEFAULT ;SHOW [ADMIN] -F AJSROOT1 -l -g 1 -X auto /net

The following table describes the items that are specific to these formats.

Table C‒74: Items specific to the Unit Status Displayed (Abnormal End) log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsshow command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output.

10

host-name

The name of the logical host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the ajsshow command are output. Note that the value specified for the -f, -t, or -i option is always enclosed in double quotation marks ("").

1 to 500

unit-name

The unit name specified in the ajsshow command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(75) Formats of the Unit Definitions Output (Abnormal End) log entry

The following are the formats of the Unit Definitions Output (Abnormal End) log entry.

When no process ID is to be included in the log information:

C510ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;PRINTΔ[user-type]Δ[requesting-host-IP-address,requesting-source-identification]ΔoptionΔunit-name

When a process ID is to be included in the log information:

C510ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;PRINTΔ[user-type]Δ[requesting-host-IP-address,requesting-source-identification]ΔoptionΔunit-name

Logging conditions:

An entry is output to the log only if yes is specified in the AJSLOGOUTPUTEXTEND environment parameter, and all or print is specified in the REFLOG environment setting parameter.

Example of a log entry:

C510 Mar 05 12:20:56 [2552] jp1admin KAVS0161-I JP1_DEFAULT ;PRINT [ADMIN] -F AJSROOT1 -a /net

The following table describes the items that are specific to these formats.

Table C‒75: Items specific to the Unit Definitions Output (Abnormal End) log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsprint command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output.

10

host-name

The name of the logical host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the ajsprint command are output. Note that the value specified for the -f or -t option is always enclosed in double quotation marks ("").

1 to 500

unit-name

The unit name specified in the ajsprint command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(76) Formats of the Unit Definitions Backed Up (Abnormal End) log entry

The following are the formats of the Unit Definitions Backed Up (Abnormal End) log entry.

When no process ID is to be included in the log information:

C511ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;BACKUPΔ[user-type]Δ[requesting-host-IP-address,requesting-source-identification]ΔoptionΔunit-name

When a process ID is to be included in the log information:

C511ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;BACKUPΔ[user-type]Δ[requesting-host-IP-address,requesting-source-identification]ΔoptionΔunit-name

Logging conditions:

An entry is output to the log if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter, and all or backup is specified in the REFLOG environment setting parameter.

Example of a log entry:

C511 Mar 05 12:21:49 [1196] jp1admin KAVS0161-I JP1_DEFAULT ;BACKUP [ADMIN] -F AJSROOT1 -e -m -n box1 /net

The following table describes the items that are specific to these formats.

Table C‒76: Items specific to the Unit Definitions Backed Up (Abnormal End) log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsbackup command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output.

10

host-name

The name of the logical host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option#

The options specified in the ajsbackup command are output.

1 to 500

unit-name

The unit name specified in the ajsbackup command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(77) Formats of the Unit Name Output (Abnormal End) log entry

The following are the formats of the Unit Name Output (Abnormal End) log entry.

When no process ID is to be included in the log information:

C512ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;NAMEΔ[user-type]ΔoptionΔunit-name

When a process ID is to be included in the log information:

C512ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;NAMEΔ[user-type]ΔoptionΔunit-name

Logging conditions:

An entry is output to the log only if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter, and all or name is specified in the REFLOG environment setting parameter.

Example of a log entry:

C512 Mar 05 12:22:13 [2540] jp1admin KAVS0161-I JP1_DEFAULT ;NAME [ADMIN] -F AJSROOT1 /net

The following table describes the items that are specific to these formats.

Table C‒77: Items specific to the Unit Name Output (Abnormal End) log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsname command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output.

10

host-name

The name of the logical host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

option#

The options specified in the ajsname command are output.

1 to 500

unit-name

The unit name specified in the ajsname command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(78) Formats of the Jobnet Registration for Execution Information Exported log entry

The following are the formats of the Jobnet Registration for Execution Information Exported log entry.

When no process ID is to be included in the log information:

C513ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;RGEXPΔ[user-type]#ΔoptionΔunit-name

When a process ID is to be included in the log information:

C513ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;RGEXPΔ[user-type]#ΔoptionΔunit-name

#

Δ[user-type] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or rgexport is specified in the REFLOG environment setting parameter.

Example of a log entry:

C513 Dec 07 19:14:15 jp1admin 0 JP1_DEFAULT ;RGEXP -F AJSROOT1 -e f /group/*

The following table describes the items that are specific to these formats.

Table C‒78: Items specific to the Jobnet Registration for Execution Information Exported log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsrgexport command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

option#

The options specified in the executed ajsrgexport command are output.

1 to 500

unit-name

The unit name specified in the executed ajsrgexport command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(79) Formats of the Jobnet Information Output by Export of Jobnet Registration for Execution Information log entry

The following are the formats of the Jobnet Information Output by Export of Jobnet Registration for Execution Information log entry.

When no process ID is to be included in the log information:

C514ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;RGEXPΔ[user-type]#ΔoptionΔunit-name

When a process ID is to be included in the log information:

C514ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;RGEXPΔ[user-type]#ΔoptionΔunit-name

#

Δ[user-type] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or rgexport is specified in the REFLOG environment setting parameter.

Example of a log entry:

C514 Dec 07 19:14:15 jp1admin 0 JP1_DEFAULT ;RGEXP -F AJSROOT1 -e f /group/rootnet1

The following table describes the items that are specific to these formats.

Table C‒79: Items specific to the Jobnet Information Output by Export of Jobnet Registration for Execution Information log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsrgexport command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

option#

The options specified in the executed ajsrgexport command are output.

1 to 500

unit-name

The jobnet name specified in the ajsrgexport command is output. The command exported the information about the jobnet registration for execution for the specified jobnet.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(80) Formats of the Jobnet Release Information Referenced log entry

The following are the formats of the Jobnet Release Information Referenced log entry.

When no process ID is to be included in the log information:

C515ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;RELEASEREFΔ[user-type]#ΔoptionΔunit-name

When a process ID is to be included in the log information:

C515ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;RELEASEREFΔ[user-type]#ΔoptionΔunit-name

#

Δ[user-type] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or release is specified in the REFLOG environment setting parameter.

Example of a log entry:

C515 Dec 07 19:14:15 jp1admin 0 JP1_DEFAULT ;RELEASEREF -F AJSROOT1 -i /group/releasenet

The following table describes the items that are specific to these formats.

Table C‒80: Items specific to the Jobnet Release Information Referenced log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajsrelease command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

option#

The options specified in the ajsrelease command are output. These options were specified when the command was used to output release information.

1 to 500

unit-name

The unit name specified in the executed ajsrelease command is output.

1 to 930

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 64 bytes, only 64 bytes are output.

If the size of all options exceeds 500 bytes, only 500 bytes are output. Note that if the 500-byte limit is exceeded before an option name is complete, that option is not output.

(81) Formats of the Calendar Calculation log entry

The following are the formats of the Calendar Calculation log entry.

When no process ID is to be included in the log information:

C516ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;CALUTILΔ[user-type]#Δoption

When a process ID is to be included in the log information:

C516ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;CALUTILΔ[user-type]#Δoption

#

Δ[user-type] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Logging conditions:

An entry is output to the log only if all or calutil is specified in the REFLOG environment setting parameter.

Example of a log entry:

C516 Apr 15 15:32:49 jp1admin 0 JP1_DEFAULT ;CALUTIL -F AJSROOT1 -b 2016/5/1 -e 2016/5/31 -o -g /CAL/CAL1 -g /CAL/CAL2

The following table describes the items that are specific to these formats.

Table C‒81: Items specific to the Calendar Calculation log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the ajscalutil command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

The ID of the message reporting the result of the operation is output. If the operation was performed successfully, 0 is output.

1 or 10

host-name

The name of the host requested to perform the operation is output.

1 to 255

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

option#

The options specified in the executed ajscalutil command are output.

1 to 1110

#

If the value of an option (the part that is not the option name and the subsequent space (Δ)) exceeds 128 bytes, only 128 bytes are output.

(82) Formats of the Command Processing Started log entry

The following are the formats of the Command Processing Started log entry.

When no process ID is to be included in the log information:

I001ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;STARTΔcommand-nameΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

When a process ID is to be included in the log information:

I001ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;STARTΔcommand-nameΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Example of a log entry:

I001 Dec 15 09:14:22 jp1admin - JP1_DEFAULT ;START ENTRY -F AJSROOT1 -n /group/net

The following table describes the items that are specific to these formats.

Table C‒82: Items specific to the Command Processing Started log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the applicable command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

Always a hyphen (-).

1

host-name

The name of the host requested to perform the operation is output.

1 to 255

command-name

The applicable command name is output in upper-case alphabetic characters.

Example:

For the ajsentry command, the prefix (ajs) is removed and the remainder of the name is output in upper case (ENTRY).

7 to 11

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Web Console

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View, JP1/AJS3 - Web Console or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS3-WEB

Indicates that the operation was performed from JP1/AJS3 - Web Console.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option

The options specified in the executed command are output.

1 to 500

unit-name

The unit name specified in the executed command is output.

1 to 930

Note

The Command Processing Started log entry might not be output if an incorrectly specified option value results in an error or a non-existing unit name is specified. The log entry also might not be output if, while JP1/AJS3 - View is being used, an error occurs before definitions are updated or the existing definitions are not changed.

(83) Formats of the Command-to-Scheduler Service Processing Request Started log entry

The following are the formats of the Command-to-Scheduler Service Processing Request Started log entry.

When no process ID is to be included in the log information:

I002ΔdateΔtimeΔuser-nameΔmessage-IDΔhost-nameΔ;REQUESTΔcommand-nameΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

When a process ID is to be included in the log information:

I002ΔdateΔtimeΔ[process-ID]Δuser-nameΔmessage-IDΔhost-nameΔ;REQUESTΔcommand-nameΔ[user-type]#Δ[requesting-host-IP-address,requesting-source-identification] #ΔoptionΔunit-name

#

Δ[user-type]Δ[requesting-host-IP-address,requesting-source-identification] is output if yes is specified in the AJSLOGOUTPUTEXTEND environment setting parameter.

Example of a log entry:

I002 Dec 15 09:14:22 jp1admin - JP1_DEFAULT ;REQUEST ENTRY -F AJSROOT1 -n /group/net

The following table describes the items that are specific to these formats.

Table C‒83: Items specific to the Command-to-Scheduler Service Processing Request Started log entry (scheduler information log)

Item

Description

Length (bytes)

user-name

The name of the JP1 user who executed the applicable command is output. If a JP1 user without the execution permission for the command attempted to execute the command, a NULL character string is output.

0 to 20

message-ID

Always a hyphen (-).

1

host-name

The name of the host requested to perform the operation is output.

1 to 255

command-name

The applicable command name is output in upper-case alphabetic characters.

Example:

For the ajsentry command, the prefix (ajs) is removed and the remainder of the name is recorded in upper case (ENTRY).

7 to 11

user-type

The type of the user (ADMIN or USER) who performed the operation is output.

ADMIN

A user with administrator privileges or superuser privileges

USER

A general user

4 or 5

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

This item is output only when the operation was performed from one of the following programs or when the command was remotely executed.

JP1/AJS3 - View

JP1/AJS3 - Web Console

JP1/AJS3 - Definition Assistant

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

The information for identifying the source requesting the operation is output. This item is output only when the operation was performed from JP1/AJS3 - View, JP1/AJS3 - Web Console or JP1/AJS3 - Definition Assistant, or when the command was remotely executed.

JP1/AJS2-View

Indicates that the operation was performed from JP1/AJS3 - View.

JP1/AJS3-WEB

Indicates that the operation was performed from JP1/AJS3 - Web Console.

JP1/AJS2-DA (IN = export-source-file-name, OUT = export-execution-result-file-name)

Indicates that the operation was performed from JP1/AJS3 - Definition Assistant.

REMOTE

Indicates that the user remotely executed the command or that a remote jobnet executed the command.

If the length of the information exceeds 100 bytes, only 100 bytes are output.

1 to 100

option

The options specified in the executed command are output.

1 to 500

unit-name

The unit name specified in the executed command is output.

1 to 930

Note

The Command-to-Scheduler Service Processing Request Started log entry is not output if an error occurs before a processing request is issued to the scheduler service (for example, an incorrectly specified option value results in an error or a non-existing unit name is specified).

In the following cases, the log entry is output twice for a single execution of the command:

The -C option is specified in the ajssuspend command.

The -a or -c option is specified in the ajsrelease command.

C.2 Log entries output by the queueless agent service

The following table lists the types of log entries output to the queueless log files of JP1/AJS3.

Table C‒84: Queueless agent service log entries

Log entry type

Log entry name

Associated message ID

Associated JP1 event

Command name

Operation from JP1/AJS3 - View

API

A101

Queueless agent service started

KAVS1801-I

None

--

--

--

A102

Queueless agent service stopped

KAVS1802-I

None

--

--

--

C901

Command request received

None

None

--

--

--

J101

Queueless job started

KAVS0251-I

None

--

--

--

J102

Queueless job ended normally

KAVS0252-I

None

--

--

--

J103

Queueless job ended abnormally

KAVS0253-E

None

--

--

--

J104

Queueless job ended with warning

KAVS0254-W

None

--

--

--

J106

Submission request accepted

KAVS1984-I

None

--

--

--

Legend:

--: Not applicable.

The log format and the items output are described below for each log entry. For details about the formats for the items common to all logs, see C.1(1) Formats common to all log entries.

A Δ in a log format indicated a one-byte space.

(1) Format of the Queueless Agent Service Started log

The following is the format of the Queueless Agent Service Started log.

A101ΔdateΔtimeΔKAVS1801-IΔhost-name

Example of a log entry:

A101 Dec 15 12:30:59 KAVS1801-I hostA

The following table describes the item that is specific to this format.

Table C‒85: Item specific to the Queueless Agent Service Started log entry (queueless log)

Item

Description

Length (bytes)

host-name

The name of the host on which the queueless agent service started is output.

1 to 255

(2) Format of the Queueless Agent Service Stopped log entry

The following is the format of the Queueless Agent Service Stopped log entry.

A102ΔdateΔtimeΔKAVS1802-IΔhost-name

Example of a log entry:

A102 Dec 15 12:30:06 KAVS1802-I hostA

The following table describes the item that is specific to this format.

Table C‒86: Item specific to the Queueless Agent Service Stopped log entry (queueless log)

Item

Description

Length (bytes)

host-name

The name of the host on which the queueless agent service started is output.

1 to 255

(3) Formats of the Command Request Received log entry

The following are the formats of the Command Request Received log entry.

(a) ajsqlalter

C901ΔdateΔtimeΔajsqlalterΔmaximum-number-of-concurrently-executable-jobsΔmaximum-number-of-waiting-jobsΔuser-mapping-cache-clear-optionΔclass-nameΔlogical-host-name

(b) ajsqlattach

C901ΔdateΔtimeΔajsqlattachΔlogical-host-name

(c) ajsqldetach

C901ΔdateΔtimeΔajsqldetachΔlogical-host-nameΔforced-termination-specification

(d) ajsqlstop

C901ΔdateΔtimeΔajsqlstopΔend-mode

Logging examples:

ajsqlalter

C901 Dec 15 12:07:41 ajsqlalter -1 -1 0

ajsqlattach

C901 Dec 15 18:08:46 ajsqlattach

ajsqldetach

C901 Dec 15 18:08:08 ajsqldetach 0

ajsqlstop

C901 Dec 15 18:06:14 ajsqlstop 0

The following table describes the items that are specific to these formats.

Table C‒87: Items specific to the Command Request Received log entry (queueless log)

Item

Description

Length (bytes)

logical-host-name

The logical host name specified in the -h option is output. If the -h option is not specified in the command, a logical host name is not output.

0 to 255

maximum-number-of-concurrently-executable-jobs

The new maximum number of concurrently executable jobs is output as a decimal number. If no value is specified in the command, -1 is output.

1 to 4

maximum-number-of-waiting-jobs

The new maximum number of waiting jobs is output as a decimal number. If no value is specified in the command, -1 is recorded.

1 to 6

user-mapping-cache-clear-option

0 or 1 is output.

0: Clearing the cache is not specified.

1: Clearing the cache is specified.

1

class-name

The target class name is output. If no class name is specified in the command, a name is not output.

0 to 63

forced-termination-specification

0 or 1 is output.

0: Forced termination is not specified.

1: Forced termination is specified.

1

end-mode

0 or 1 is output.

0: There is a wait for the job to end.

1: There is no wait for the job to end.

1

(4) Format of the Queueless Job Started log entry

The following is the format of the Queueless Job Started log entry.

J101ΔdateΔtimeΔKAVS0251-IΔmanager-host-nameΔscheduler-service-name:job-name:execution-IDΔagent-host-name

Example of a log entry:

J101 Dec 15 17:14:01 KAVS0251-I hostA AJSROOT1:/group/net1/job1:@A100 hostB

The following table describes the items that are specific to this format.

Table C‒88: Items specific to the Queueless Job Started log entry (queueless log)

Item

Description

Length (bytes)

manager-host-name

The name of the manager host that requested execution of the queueless job is output.

1 to 255

job-name

The name of the queueless job that started is output in scheduler-service-name:job-name:execution-ID format.

1 to 969

agent-host-name

The name of the agent host on which the queueless job was executed is output.

1 to 255

(5) Format of the Queueless Job Ended Normally log entry

The following is the format of the Queueless Job Ended Normally log entry.

J102ΔdateΔtimeΔKAVS0252-IΔmanager-host-nameΔscheduler-service-name:job-name:execution-IDΔagent-host-nameΔreturn-value

Example of a log entry:

J102 Dec 15 17:14:01 KAVS0252-I hostA AJSROOT1:/group/net1/job1:@A100 hostB 0

The following table describes the items that are specific to this format.

Table C‒89: Items specific to the Queueless Job Ended Normally log entry (queueless log)

Item

Description

Length (bytes)

manager-host-name

The name of the manager host that requested execution of the queueless job is output.

1 to 255

job-name

The name of the queueless job that ended normally is output in scheduler-service-name:job-name:execution-ID format.

1 to 969

agent-host-name

The name of the agent host on which the queueless job ended normally is output.

1 to 255

return-value

The return value of the queueless job that ended normally is output as a decimal number.

1 to 10

(6) Format of the Queueless Job Ended Abnormally log entry

The following is the format of the Queueless Job Ended Abnormally log entry.

J103ΔdateΔtimeΔKAVS0253-EΔmanager-host-nameΔscheduler-service-name: job-name:execution-IDΔagent-host-nameΔend-statusΔreturn-value

Example of a log entry:

J103 Dec 15 17:14:01 KAVS0253-E hostA AJSROOT1:/group/net1/job1:@A100 hostB a 0

The following table describes the items that are specific to this format.

Table C‒90: Items specific to the Queueless Job Ended Abnormally log entry (queueless log)

Item

Description

Length (bytes)

manager-host-name

The name of the manager host that requested execution of the queueless job is output.

1 to 255

job-name

The name of the queueless job that ended abnormally is output in scheduler-service-name:job-name:execution-ID format.

1 to 969

agent-host-name

The name of the agent host on which the queueless job ended abnormally is output.

1 to 255

end-status

One of the following is output:

a: Ended abnormally

f: Failed to start

c: Killed

?: Unknown end status

1

return-value

The return value of the queueless job that ended abnormally is output as a decimal number.

1 to 10

(7) Format of the Queueless Job Ended with Warning log entry

The following is the format of the Queueless Job Ended with Warning log entry.

J104ΔdateΔtimeΔKAVS0254-WΔmanager-host-nameΔscheduler-service-name: job-name:execution-IDΔagent-host-nameΔreturn-value

Example of a log entry:

J104 Dec 15 17:14:01 KAVS0254-W hostA AJSROOT1:/group/net1/job1:@A100 hostB 0

The following table describes the items that are specific to this format.

Table C‒91: Items specific to the Queueless Job Ended with Warning log entry (queueless log)

Item

Description

Length (bytes)

manager-host-name

The name of the manager host that requested execution of the queueless job is output.

1 to 255

job-name

The name of the queueless job that ended with a warning is output in scheduler-service-name:job-name:execution-ID format.

1 to 969

agent-host-name

The name of the agent host on which the queueless job ended with a warning is output.

1 to 255

return-value

The return value of the queueless job that ended with a warning is output as a decimal number.

1 to 10

(8) Format of the Submission Request Accepted log entry

The following is the format of the Submission Request Accepted log entry.

J106ΔdateΔtimeΔKAVS1984-IΔmanager-host-nameΔscheduler-service-name:job-name:execution-IDΔagent-host-name

Example of a log entry:

J106 Dec 15 12:21:03 KAVS1984-I hostA AJSROOT1:/group/net1/job1:@A100 hostB

The following table describes the items that are specific to this format.

Table C‒92: Items specific to the Submission Request Accepted log entry (queueless log)

Item

Description

Length (bytes)

manager-host-name

The name of the manager host that requested execution of the queueless job is output.

1 to 255

job-name

The name of the queueless job for which a submission request was accepted is output in scheduler-service-name:job-name:execution-ID format.

1 to 969

agent-host-name

The host name specified as the execution agent host name is output.

1 to 255

C.3 Log entries recorded when definition pre-checks are performed

The following table lists the log entries that are output to the definition check log files when definition pre-checks are performed.

Table C‒93: Log entries output when definition pre-checks are performed

Log entry type

Log entry name

Associated message ID

Associated JP1 event

Command name

Operation from JP1/AJS3 - View

API

A201

JP1/AJS3 Check Manager service started

KAVS3402-I

None

ajschkstart

--

--

A202

JP1/AJS3 Check Manager service stopped

KAVS3403-I

None

ajschkstop

--

--

C901

Command request received

--

None

ajschkdef

--

--

A203

JP1/AJS3 Check Agent service started

KAVS3406-I

None

ajschkstart

--

--

A204

JP1/AJS3 Check Agent service stopped

KAVS3407-I

None

ajschkstop

--

--

Legend:

--: Not applicable.

The format and the items output are described below for each log entry. For details about the formats common to all logs, see C.1(1) Formats common to all log entries.

(1) Format of the JP1/AJS3 Check Manager Service Started log entry

The following is the format of the JP1/AJS3 Check Manager Service Started log entry.

A201ΔdateΔtimeΔKAVS3402-IΔname-of-host-on-which-service-started

Example of a log entry:

A201 Dec 15 09:14:22 KAVS3402-I host1

The following table describes the item that is specific to this format.

Table C‒94: Item specific to the JP1/AJS3 Check Manager Service Started log entry

Item

Description

Length (bytes)

name-of-host-on-which-service-started

The name of the host on which the service started is output.

1 to 255

(2) Format of the JP1/AJS3 Check Manager Service Stopped log entry

The following is the format of the JP1/AJS3 Check Manager Service Stopped log entry.

A202ΔdateΔtimeΔKAVS3403-IΔname-of-host-on-which-service-stopped

Example of a log entry:

A202 Dec 15 17:15:20 KAVS3403-I host1

The following table describes the item that is specific to this format.

Table C‒95: Item specific to the JP1/AJS3 Check Manager Service Stopped log entry

Item

Description

Length (bytes)

name-of-host-on-which-service-stopped

The name of the host on which the service stopped is output.

1 to 255

(3) Format of the Command Request Received log entry

The following is the format of the Command Request Received log entry.

C901ΔdateΔtimeΔcommand-execution-typeΔcheck-itemΔexecution-agent-profile-name#1Δregistered-user-nameΔunit-attribute-profile-name#2Δoutput-file-nameΔfull-unit-name

#1

ItemΔexecution-agent-profile-name is output only if the -p option is specified in the ajschkdef command. This item is not output if the -p option is omitted.

#2

ItemΔunit-attribute-profile-name is output only if the -e option is specified in the ajschkdef command. This item is not output if the -e option is omitted.

Example of a log entry:

C901 Dec 15 13:30:18 START O jp1admin C:\Program Files\HITACHI\JP1AJS2\log\ajscheckfile.txt net1

The following table describes the items that are specific to this format.

Table C‒96: Items specific to the Command Request Received log entry

Item

Description

Length (bytes)

command-execution-type

The execution type of the command is output.

START: A definition pre-check was started.

STATUS: The execution status of a definition pre-check was displayed.

1 to 6

check-item

The check item options specified in the command are output (the options are O, M, C, P, H, U, D, and A).

1 to 7

execution-agent-profile-name

The execution agent profile name specified in the -p option is output.

1 to 255

registered-user-name

The registered user name specified in the -u option is output.

1 to 31

unit-attribute-profile-name

The unit attribute profile name specified in the -e option is output.

1 to 255

output-file-name

The output file name specified in the -o option is output.

1 to 255

full-unit-name

The full unit name specified in the command is output.

1 to 961

(4) Format of the JP1/AJS3 Check Agent Service Started log entry

The following is the format of the JP1/AJS3 Check Agent Service Started log entry.

A203ΔdateΔtimeΔKAVS3406-IΔname-of-host-on-which-service-started

Example of a log entry:

A203 Dec 15 09:14:22 KAVS3406-I host1

The following table describes the item that is specific to this format.

Table C‒97: Item specific to the JP1/AJS3 Check Agent Service Started log entry

Item

Description

Length (bytes)

name-of-host-on-which-service-started

The name of the host on which the service started is output.

1 to 255

(5) Format of the JP1/AJS3 Check Agent Service Stopped log entry

The following is the format of the JP1/AJS3 Check Agent Service Stopped log entry.

A204ΔdateΔtimeΔKAVS3407-IΔname-of-host-on-which-service-stopped

Example of a log entry:

A204 Dec 15 17:15:20 KAVS3407-I host1

The following table describes the item that is specific to this format.

Table C‒98: Item specific to the JP1/AJS3 Check Agent Service Stopped log entry

Item

Description

Length (bytes)

name-of-host-on-which-service-stopped

The name of the host on which the service stopped is output.

1 to 255

C.4 Log entries output when flexible jobs are executed

The following table lists the messages that are output to the log files on the host requesting a flexible job and the host executing a flexible job.

Table C‒99: Log entries output when flexible jobs are executed

Message ID

Log file on the host requesting a flexible job

Log file on the host executing a flexible job

Broadcast agent log file

Log file for the broadcast agent and broadcast-execution destination agents

KAVS8100

Y

Y

Y

--

KAVS8101

Y

--

Y

--

KAVS8102

--

Y

--

--

KAVS8106

Y

Y

Y

--

KAVS8108

--

Y

--

--

KAVS8109

--

Y

--

--

KAVS8110

Y

Y

Y

--

KAVS8115

Y

--

Y

--

KAVS8116

Y

--

Y

--

KAVS8130

--

Y

--

--

KAVS8133 to

KAVS8136

--

Y

--

--

KAVS8137

Y

--

Y

--

KAVS8138

Y

--

Y

--

KAVS8139 to

KAVS8141

--

Y

--

--

KAVS8142

Y

--

--

--

KAVS8143

--

Y

--

--

KAVS8144

--

--

--

Y

KAVS8145

--

--

Y

--

KAVS8146

--

--

--

Y

KAVS8147

--

--

--

Y

KAVS8148

--

--

Y

--

KAVS8149

--

--

Y

--

KAVS8158

--

--

Y

--

KAVS8159

--

--

Y

--

KAVS8160

--

--

--

Y

KAVS8162

--

--

Y

--

KAVS8163

--

--

--

Y

KAVS8164

--

--

--

Y

Legend:

Y: Is output.

--: Is not output.

C.5 Log entries output by the JP1/AJS3 System Control Manager service and JP1/AJS3 System Control Agent service

The following table lists entries that are output to the ajssysctlmd and ajssysctlad logs. The entries for the JP1/AJS3 System Control Manager service are output to the ajssysctlmd log and the entries for the JP1/AJS3 System Control Agent service are output to the ajssysctlad log via the Web GUI (Management Portal).

Table C‒100: Log entries output by the JP1/AJS3 System Control Manager service and JP1/AJS3 System Control Agent service

Log entry type

Log entry name

Associated message ID

Associated JP1 event

Command name

Operation from JP1/AJS3 - View

Operation from JP1/AJS3 - Web Console

A301

JP1/AJS3 System Control Manager service started

KAVS8500-I

None

--

--

--

A302

JP1/AJS3 System Control Agent service started

KAVS8501-I

None

--

--

--

A303

JP1/AJS3 System Control Manager service terminated

KAVS8502-I

None

--

--

--

A304

JP1/AJS3 System Control Agent service terminated

KAVS8503-I

None

--

--

--

A313

Authentication denied

KAVS1009-W

None

--

--

Login to the management portal screen

A316

Connection rejected by manager connection source restriction

KAVS8040-E

None

--

--

--

A319

Connection rejected by agent connection source restriction

KAVS8039-E

None

--

--

--

C801

Request from client started

KAVS8506-I

None

--

--

Start of an operation from the management portal screen

C802

Request from manager host started

KAVS8507-I

None

--

--

Start of an operation from the management portal screen

C803

Request from client ended

KAVS8508-I

None

--

--

End of an operation from the management portal screen

C804

Request from manager host ended

KAVS8509-I

None

--

--

End of an operation from the management portal screen

Legend:

--: Not applicable.

The log format and the items output are described below for each log entry. For details about the formats for the items common to all logs, see C.1(1) Formats common to all log entries.

A Δ in a log format indicated a one-byte space.

(1) Format of the JP1/AJS3 System Control Manager Service Started log entry

The following is the format of the JP1/AJS3 System Control Manager Service Started log entry.

A301ΔdateΔtimeΔKAVS8500-IΔhost-name

Example of a log entry:

A301 Jul 28 12:30:59 KAVS8500-I hostA

The following table describes the item that is specific to this format.

Table C‒101: Item specific to the JP1/AJS3 System Control Manager Service Started log entry

Item

Description

Length (bytes)

host-name

The name of the host on which the JP1/AJS3 System Control Manager service started is output.

1 to 255

(2) Format of the JP1/AJS3 System Control Agent Service Started log entry

The following is the format of the JP1/AJS3 System Control Agent Service Started log entry.

A302ΔdateΔtimeΔKAVS8501-IΔhost-name

Example of a log entry:

A302 Jul 28 12:30:59 KAVS8501-I hostA

The following table describes the item that is specific to this format.

Table C‒102: Item specific to the JP1/AJS3 System Control Agent Service Started log entry

Item

Description

Length (bytes)

host-name

The name of the host on which the JP1/AJS3 System Control Agent service started is output.

1 to 255

(3) Format of the JP1/AJS3 System Control Manager Service Terminated log entry

The following is the format of the JP1/AJS3 System Control Manager Service Terminated log entry.

A303ΔdateΔtimeΔKAVS8502-IΔhost-name

Example of a log entry:

A303 Jul 28 12:30:06 KAVS8502-I hostA

The following table describes the item that is specific to this format.

Table C‒103: Item specific to the JP1/AJS3 System Control Manager Service Terminated log entry

Item

Description

Length (bytes)

host-name

The name of the host on which the JP1/AJS3 System Control Manager service terminated is output.

1 to 255

(4) Format of the JP1/AJS3 System Control Agent Service Terminated log entry

The following is the format of the JP1/AJS3 System Control Agent Service Terminated log entry.

A304ΔdateΔtimeΔKAVS8503-IΔhost-name

Example of a log entry:

A304 Jul 28 12:30:06 KAVS8503-I hostA

The following table describes the item that is specific to this format.

Table C‒104: Item specific to the JP1/AJS3 System Control Agent Service Terminated log entry

Item

Description

Length (bytes)

host-name

The name of the host on which the JP1/AJS3 System Control Agent service terminated is output.

1 to 255

(5) Format of the Authentication (Login or User Mapping) Denied log entry

The following is the format of the Authentication (Login or User Mapping) Denied log entry.

A313ΔdateΔtimeΔKAVS1009-WΔrequesting-host-IP-addressΔuser-nameΔhost-name

Logging conditions:

This log entry is output when user authentication or user mapping by JP1/Base fails for a connection from the following client:

JP1/AJS3 - Web Console (Management portal screen)

Example of a log entry:

A313 Feb 28 17:14:01 KAVS1009-W 10.210.38.11 jp1admin hostA

The following table describes the items that are specific to this format.

Table C‒105: Items specific to the Authentication (Login or User Mapping) Denied log entry

Item

Description

Length (bytes)

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

IPv4: 7 to 15

IPv6: 3 to 39

user-name

The name of the JP1 user who performed the operation is output.

0 to 20

host-name

The host name of the host that accepted the request is output.

1 to 255

(6) Formats of the Connection Rejected by Manager Connection Source Restriction log entry

The following is the format of the Connection Rejected by Manager Connection Source Restriction log entry.

A316ΔdateΔtimeΔKAVS8040-EΔrequesting-host-IP-addressΔuser-nameΔhost-name

Logging conditions:

This log entry is output when a connection is denied due to a connection source restriction for the manager.

Example of a log entry:

A316 Feb 28 17:14:01 KAVS8040-E 10.210.38.11 jp1admin hostA

The following table describes the items that are specific to this format.

Table C‒106: Items specific to the Connection Rejected by Manager Connection Source Restriction log entry

Item

Description

Length (bytes)

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

IPv4: 7 to 15

IPv6: 3 to 39

user-name

The name of the JP1 user who performed the operation is output.

0 to 20

host-name

The host name of the host that accepted the request is output.

1 to 255

(7) Formats of the Connection Rejected by Agent Connection Source Restriction log entry

The following is the format of the Connection Rejected by Agent Connection Source Restriction log entry.

A319ΔdateΔtimeΔKAVS8039-EΔrequesting-host-IP-addressΔuser-nameΔhost-name

Logging conditions:

This log entry is output when a connection is denied due to a connection source restriction for the agent.

Example of a log entry:

A319 Feb 28 17:14:01 KAVS8039-E 10.210.38.11 jp1admin hostA

The following table describes the items that are specific to this format.

Table C‒107: Items specific to the Connection Rejected by Agent Connection Source Restriction log entry

Item

Description

Length (bytes)

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

IPv4: 7 to 15

IPv6: 3 to 39

user-name

The name of the JP1 user who performed the operation is output.

0 to 20

host-name

The host name of the host that accepted the request is output.

1 to 255

(8) Format of the Request from Client Started log entry

The following is the format of the Request from Client Started log entry.

C801ΔdateΔtimeΔKAVS8506-IΔuser-nameΔhost-nameΔSTARTΔrequest-typeΔrequesting-host-IP-addressΔrequesting-source-identification

Example of a log entry:

C801 Aug 05 17:14:01 KAVS8506-I jp1admin hostA START GETSTATUS 10.210.38.11 JP1/AJS3-WEB

The following table describes the items that are specific to this format.

Table C‒108: Items specific to the Request from Client Started log entry

Item

Description

Length (bytes)

user-name

The name of the JP1 user who performed the operation is output.

0 to 20

host-name

The host name of the host that accepted the request is output.

1 to 255

request-type

One of the following strings is output as the request type:

LOGIN

Request to log in

LOGOUT

Request to log out

GETCHARCODE

Request to obtain the character encoding

GET_SCTLSTATUS

Request to confirm the status of the JP1/AJS3 System Control Manager service

STOP_SCTLSRV

Request to stop the JP1/AJS3 System Control Manager service

GETSTATUS

Request to obtain the statuses of the JP1/AJS3 services and processes

5 to 14

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

One of the following strings is output to identify the requesting source:

JP1/AJS3-WEB

Indicates that the operation was performed from JP1/AJS3 - Web Console.

SCTLSTATUS

Indicates that the operation was performed from ajssctlstatus command.

SCTLSTOP

Indicates that the operation was performed from ajssctlstop command.

8 to 12

(9) Format of the Request from Manager Host Started log entry

The following is the format of the Request from Manager Host Started log entry.

C802ΔdateΔtimeΔKAVS8507-IΔuser-nameΔhost-nameΔSTARTΔrequest-typeΔrequesting-host-IP-addressΔrequesting-source-identification

Example of a log entry:

C802 Aug 05 17:14:01 KAVS8507-I jp1admin hostA START GETSTATUS 10.210.38.11 GETSTATUS_COM

The following table describes the items that are specific to this format.

Table C‒109: Items specific to the Request from Manager Host Started log entry

Item

Description

Length (bytes)

user-name

The name of the JP1 user who performed the operation is output.

0 to 20

host-name

The host name of the host that accepted the request is output.

1 to 255

request-type

One of the following strings is output as the request type:

GETCHARCODE

Request to obtain the character encoding

GET_SCTLSTATUS

Request to confirm the status of the JP1/AJS3 System Control Agent service

STOP_SCTLSRV

Request to stop the JP1/AJS3 System Control Agent service

GETSTATUS

Request to obtain the statuses of the JP1/AJS3 services and processes

9 to 14

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

One of the following strings is output to identify the requesting source:

GETSTATUS_COM

Indicates that an operation to obtain the statuses of JP1/AJS3 services and processes was requested.

SCTLSTATUS

Indicates that the operation was performed from ajssctlstatus command.

SCTLSTOP

Indicates that the operation was performed from ajssctlstop command.

8 to 13

(10) Format of the Request from Client Ended log entry

The following is the format of the Request from Client Ended log entry.

C803ΔdateΔtimeΔKAVS8508-IΔuser-nameΔhost-nameΔENDΔrequest-typeΔrequesting-host-IP-addressΔrequesting-source-identification

Example of a log entry:

C803 Aug 05 17:14:01 KAVS8508-I jp1admin hostA END GETSTATUS 10.210.38.11 JP1/AJS3-WEB

The following table describes the items that are specific to this format.

Table C‒110: Items specific to the Request from Client Ended log entry

Item

Description

Length (bytes)

user-name

The name of the JP1 user who performed the operation is output.

0 to 20

host-name

The host name of the host that accepted the request is output.

1 to 255

request-type

One of the following strings is output as the request type:

LOGIN

Request to log in

LOGOUT

Request to log out

GETCHARCODE

Request to obtain the character encoding

GET_SCTLSTATUS

Request to confirm the status of the JP1/AJS3 System Control Manager service

STOP_SCTLSRV

Request to stop the JP1/AJS3 System Control Manager service

GETSTATUS

Request to obtain the statuses of the JP1/AJS3 services and processes

5 to 14

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

One of the following strings is output to identify the requesting source:

JP1/AJS3-WEB

Indicates that the operation was performed from JP1/AJS3 - Web Console.

SCTLSTATUS

Indicates that the operation was performed from ajssctlstatus command.

SCTLSTOP

Indicates that the operation was performed from ajssctlstop command.

8 to 12

(11) Format of the Request from Manager Host Ended log entry

The following is the format of the Request from Manager Host Ended log entry.

C804ΔdateΔtimeΔKAVS8509-IΔuser-nameΔhost-nameΔENDΔrequest-typeΔrequesting-host-IP-addressΔrequesting-source-identification

Example of a log entry:

C804 Aug 05 17:14:01 KAVS8509-I jp1admin hostA END GETSTATUS 10.210.38.11, GETSTATUS_COM

The following table describes the items that are specific to this format.

Table C‒111: Items specific to the Request from Manager Host Ended log entry

Item

Description

Length (bytes)

user-name

The name of the JP1 user who performed the operation is output.

0 to 20

host-name

The host name of the host that accepted the request is output.

1 to 255

request-type

One of the following strings is output as the request type:

GETCHARCODE

Request to obtain the character encoding

GET_SCTLSTATUS

Request to confirm the status of the JP1/AJS3 System Control Agent service

STOP_SCTLSRV

Request to stop the JP1/AJS3 System Control Agent service

GETSTATUS

Request to obtain the statuses of the JP1/AJS3 services and processes

9 to 14

requesting-host-IP-address

The IP address of the host used to perform the operation is output.

IPv4: 7 to 15

IPv6: 3 to 39

requesting-source-identification

One of the following strings is output to identify the requesting source:

GETSTATUS_COM

Indicates that an operation to obtain the statuses of JP1/AJS3 services and processes was requested.

SCTLSTATUS

Indicates that the operation was performed from ajssctlstatus command.

SCTLSTOP

Indicates that the operation was performed from ajssctlstop command.

8 to 13

D. How the Embedded Database Operates

This section explains what designers and operators of the embedded database need to know about embedded database operation.

D.1 The embedded database system and processes

Multiple processes run collaboratively on the OS to manage access to the embedded database. This management framework is called the embedded database system, and each process in the framework is called an embedded database process.

As shown in the figure below, the embedded database system uses several embedded database processes. In the embedded database system, some embedded database processes operate together with other embedded database processes, and some embedded database processes operate independently. For details about the process configuration for the embedded database and the number of processes, see B.4 Embedded database processes.

Figure D‒1: Embedded database system and processes

In this manual, the embedded database system might also be called embedded database server or, simply, embedded database. When a single embedded database process is explained, the term embedded database process is used to clarify that a process is meant.

D.2 Embedded database processes

(1) Types of embedded database processes

The following explains the types of embedded database processes.

(a) Process that manages embedded database processes (pdprcd process)

In Windows, the pdprcd process is generated when the embedded database service is started, and disappears when the service is stopped. If the ajsembdbstop command is used to stop the embedded database system, the pdprcd process remains resident on the OS. It does not disappear.

In UNIX, the pdprcd process is generated when the embedded database is started by the ajsembdbstart command, and disappears when the embedded database system is stopped by the ajsembdbstop command.

(b) Processes existing on the OS while the embedded database system is operating

When the embedded database system is started, the pdprcd process generates child processes. These processes reside on the OS to control database access while the embedded database system is operating. When the embedded database is stopped, these processes disappear from the OS.

(c) Processes for the embedded database operation commands

Every time an embedded database operation command is executed, processes for executing necessary processing are generated. These processes disappear immediately after the processing terminates.

Some embedded database operation commands can only be executed while the embedded database system is operating, and the other embedded database operation commands can be executed anytime, regardless of the operating status of the embedded database system.

(2) Status transitions of the embedded database processes

The following figure shows how the status of an embedded database process changes according to the operating status of the embedded database system.

Figure D‒2: Operating status of the embedded database system and the operating status of each embedded database process

The following explains the operating statuses of embedded database processes.

(a) Generation

In UNIX, the pdprcd process is generated by the ajsembdbstart command.

In Windows, the pdprcd process is generated by the embedded database service.

Processes other than the pdprcd process are generated by the pdprcd process or embedded database operation commands that are executed.

(b) Normal termination

When an embedded database process no longer has a reason to exist, it performs cleanup processing such as releasing or deleting resources (such as memory, or files), and then disappears from the OS. The status that results is called normal termination.

Normal termination is sometimes called normal stop in this manual.

(c) Forced termination

Before an embedded database process can terminate normally, it might have to be terminated immediately in order to fulfill a request. In this case, the pdprcd process sends an immediate termination request to the embedded database process. Upon receiving the request, the embedded database process terminates immediately without performing any cleanup processing. The resulting status in this case is called forced termination.

When an embedded database process is forcibly terminated, an embedded database process that performs cleanup processing in place of the forcibly terminated process is started.

Forced termination occurs in the following cases:

When the embedded database system is forcibly terminated (ajsembdbstop command -f option)

When execution of an embedded database operation command is canceled (ajsembdbcancel command)

Forced termination is sometimes called forced stop in this manual.

(d) Abnormal termination

If an error prevents an embedded database process from continuing operation, the process disappears from the OS without performing any cleanup processing. The resulting status in this case is called abnormal termination.

When an embedded database process is abnormally terminated, an embedded database process that performs cleanup processing in place of the abnormally terminated process is started. If the situation in which abnormal termination occurred is judged too serious for operation of the entire embedded database system to continue, the cleanup process abnormally terminates the embedded database system.

Abnormal termination occurs in the following cases:

When a system log file that can be overwritten does not exist

When the system cannot continue operation due to insufficient memory or disk space

When a contradiction resulting from damage to memory or a similar cause is detected

D.3 Embedded database system

The following figure shows the status transitions of the embedded database system.

Figure D‒3: Status transitions of the embedded database system

For details about the permanent and transitional statuses of the embedded database system in the figure, see (1) Embedded database system statuses. For details about the events that occur in the embedded database system in the figure, see (2) Events that occur in the embedded database system.

(1) Embedded database system statuses

The following describes the permanent and transitional statuses shown in Figure D-3.

To check the status of the embedded database system, execute the ajsembdbstatus command with the -s option specified. Character strings enclosed in parentheses in a permanent or transitional status in Figure D-3 correspond to the values in the UNIT-STAT column that appear when you execute the ajsembdbstatus command with the -s option specified.

(a) STOP status

STOP status refers to the status in which the only running embedded database process is the pdprcd process. Note that, in Windows, even the pdprcd process does not exist if the embedded database service has not been started.

When the embedded database system is in the STOP status, the scheduler database cannot be accessed.

(b) STARTING status

STARTING status refers to the status that occurs between the STOP and ONLINE statuses. In this status, the embedded database processes are in the midst of starting and preparing for operation. Because the STARTING status is a transitional status, the embedded database system never remains in this status.

When the embedded database system is in the STARTING status, the scheduler database cannot be accessed.

(c) ONLINE status

ONLINE status refers to the status in which all child processes of the pdprcd process have been started and initialized, and the embedded database can be accessed.

The scheduler database can be accessed only when the embedded database system is in the ONLINE status.

(d) STOPPING status

STOPPING status refers to the status that occurs between the ONLINE and STOP statuses when the embedded database system terminates normally. In this status, embedded database processes are in the midst of being sequentially stopped and preparation for termination is performed. Because the STOPPING status is a transitional status, the embedded database system never remains in this status. Note that the embedded database system does not enter this status if the system terminates abnormally or is forcibly stopped.

When the embedded database system is in the STOPPING status, the scheduler database cannot be accessed.

(e) PAUSE status

The embedded database system is placed in the PAUSE status only when an error has occurred.

In UNIX, if an error occurs frequently (three times# in succession within 30 minutes#) in the embedded database system, the system is placed in the PAUSE status. If this same situation occurs in Windows, the embedded database system is placed in the STOP status.

When the embedded database system is in the PAUSE status, as in the STOP status, the only embedded database process residing on the OS is the pdprcd process.

The embedded database system in the PAUSE status cannot be started until the embedded database system administrator corrects the error and executes the ajsembdbstart command with the -R option. The -R option explicitly indicates that the system has been recovered.

When the embedded database system in the PAUSE status, the scheduler database cannot be accessed.

#

The number of times and the number of minutes are fixed and cannot be changed.

(2) Events that occur in the embedded database system

The status transitions of the embedded database system are triggered by events that occur when embedded database operation commands are executed by the embedded database system administrator and events that the embedded database system automatically generates.

The following explains the events shown in Figure D-3.

(a) Normal start/restart

When an attempt is made to start the embedded database system that is in the STOP status, the system first enters the STARTING status, and then enters the ONLINE status.

Startup of the embedded database system immediately after the environment is set up or after the system has terminated normally is called a normal start.

Startup of the embedded database system after it has been forcibly stopped or after it has abnormally terminated is called a restart.

(b) Normal stop

When a normal stop operation is performed for the embedded database system that is in the ONLINE status, the system first enters the STOPPING status, and then enters the STOP status.

Normal stop is sometimes called normal termination in this manual.

(c) Forced stop

When a forced stop operation is performed for the embedded database system that is in ONLINE status, the system bypasses the STOPPING status and directly enters the STOP status.

Forced stop is sometimes called forced termination in this manual.

(d) Abnormal termination

If an error occurs in the embedded database system in the ONLINE status, the system enters the STOP or PAUSE status to limit any effects from the error. This event is called an abnormal termination.

Specifically, the pdprcd process forcibly terminates all other embedded database processes. Usually, a database process that is terminated abnormally enters the STOP status. However, if an error occurs three times# in succession within 30 minutes#, the process enters the PAUSE status.

#

The number of times and the number of minutes are fixed and cannot be changed.

Generally, the abnormal termination event occurs in the following cases:

When no system log file can be overwritten

When the system cannot continue operation due to insufficient memory or disk space

When damage to a system area on the disk is detected

(e) Restart after recovery

After the error in the embedded database system that has been placed in the PAUSE status has been corrected, execute the ajsembdbstart command with the -R option specified so that the embedded database system first enters the STARTING status, and then enters the ONLINE status. This operation is available in UNIX only.

E. Version Revisions

For details on the version revisions, see B. Version Revisions in the manual JP1/Automatic Job Management System 3 Overview.

F. Reference Material for This Manual

For details on reference information that would be helpful in reading this manual, see C. Reference Material for This Manual in the manual JP1/Automatic Job Management System 3 Overview.

G. Glossary

For the glossary, see D. Glossary in the manual JP1/Automatic Job Management System 3 Overview.

Index

A

agent management log[1], [2]

agent management trace log[1], [2]

agent monitoring trace log (UNIX)[1]

Agent monitoring trace log (Windows)[1]

agents

troubleshooting agent failures[1]

ajs.exe[1]

ajs2java.exe[1]

ajsagtmd[1]

ajsagtmd.exe[1]

ajsagtmond[1]

ajsagtmond.exe[1]

ajscdinetd[1], [2]

ajscdinetd.exe[1], [2]

ajscdinetd internal log (UNIX)[1]

ajscdinetd internal log (Windows)[1]

ajschkagtd[1], [2]

ajschkagtd.exe[1], [2]

ajschkagtsvc.exe[1], [2]

ajschkmand[1]

ajschkmand.exe[1]

ajschkmansvc.exe[1]

ajsdbmgrd[1]

ajsdbmgrd.exe[1]

ajsdbmgrd internal log (UNIX)[1]

ajsdbmgrd internal log (Windows)[1]

ajsflbd[1]

ajsflbd.exe[1]

ajsflowd[1]

ajsflowd.exe[1]

ajsfxbcctl[1], [2]

ajsfxbcctl.exe[1], [2]

ajsfxdst[1]

ajsfxdstr[1]

ajsfxdstr.exe[1], [2]

ajsfxexec[1], [2]

ajsfxexec.exe[1], [2]

ajsgwd[1]

ajsgwd.exe[1]

ajsgwmasterd[1], [2]

ajsgwmasterd.exe[1], [2]

ajshlogd[1]

ajshlogd.exe[1]

ajsinetd[1], [2]

ajsinetd.exe[1], [2]

ajsinetd internal log (UNIX)[1]

ajsinetd internal log (Windows)[1]

ajslogd[1]

ajslogd.exe[1]

ajsmasterd[1], [2]

ajsmasterd.exe[1], [2]

ajsmonsvr[1], [2]

ajsmonsvr.exe[1], [2]

ajsmonsvr internal log (UNIX)[1]

ajsmonsvr internal log (Windows)[1]

ajsnetwd[1]

ajsnetwd.exe[1]

ajsovstatd[1]

ajsovstatd.exe[1]

ajsqlagtd[1], [2]

ajsqlagtd.exe[1], [2]

ajsqlasvc.exe[1], [2]

ajsqlcltd.exe[1], [2]

ajsqlfsvc.exe[1]

ajsqlftpd[1]

ajsqlftpd.exe[1]

ajsrcmdsvr[1], [2]

ajsrcmdsvr.exe[1], [2]

ajsremnetcl[1]

ajsremnetcl.exe[1]

ajsreqd[1]

ajsreqd.exe[1]

ajsschbd.exe[1], [2]

ajsschd[1]

ajsschd.exe[1]

ajsshmdel command trace log (UNIX)[1]

ajssubd[1]

ajssubd.exe[1]

ajssubwd[1]

ajssubwd.exe[1]

ajssysctlad[1], [2]

ajssysctlad.exe[1], [2]

ajssysctlad internal log (UNIX)[1]

ajssysctlad internal log (Windows)[1]

ajssysctlad log (UNIX)[1]

ajssysctlad log (Windows)[1]

ajssysctlarc[1], [2]

ajssysctlarc.exe[1], [2]

ajssysctlasvc.exe[1], [2]

ajssysctlmd[1]

ajssysctlmd.exe[1]

ajssysctlmd internal log (UNIX)[1]

ajssysctlmd internal log (Windows)[1]

ajssysctlmd log (UNIX)[1]

ajssysctlmd log (Windows)[1]

ajssysctlmrc[1]

ajssysctlmrc.exe[1]

ajssysctlmsvc.exe[1]

ajssysctl trace log (UNIX)[1]

ajssysctl trace log (Windows)[1]

as_iescscm[1], [2]

as_iescscm.exe[1], [2], [3], [4]

as_manager.exe[1], [2]

as_player[1], [2]

as_player.exe[1], [2], [3], [4]

as_service[1], [2]

as_service.exe[1], [2], [3], [4]

automatic reorganization log (UNIX)[1]

automatic reorganization log (Windows)[1]

B

broadcast agent log file (UNIX)[1]

broadcast agent log file (Windows)[1]

C

cjstartsv[1]

cjstartsv.exe[1]

collecting data

how to if problem occurs[1]

commands

to check machine configuration (UNIX)[1]

troubleshooting[1]

common message log[1]

common scheduler trace log (UNIX)[1]

common scheduler trace log (Windows)[1]

communication control log (UNIX)[1]

communication control log (Windows)[1]

communication control trace log[1], [2]

D

default disk space (UNIX)[1]

default disk space (Windows)[1], [2]

definition check log (UNIX)[1]

definition check log (Windows)[1]

definition check trace log (UNIX)[1]

definition check trace log (Windows)[1]

details on changing settings (in UNIX)[1]

details on changing settings (in Windows)[1]

directories

list for JP1/AJS3 programs[1]

E

email sending job log (when Outlook is not used) (Windows)[1]

embedded database

action to be taken if unable to terminate[1]

action to be taken if unable to terminate because processes are connected[1]

explanation of operation[1]

files and folders (UNIX)[1]

parent and child processes (UNIX)[1]

parent and child processes (Windows)[1]

processes[1], [2]

troubleshooting[1]

embedded database maintenance log (UNIX)[1]

embedded database maintenance log (Windows)[1]

event/action common error log (UNIX)[1]

event/action common error log (Windows)[1]

event/action common log (UNIX)[1]

event/action common log (Windows)[1]

event/action control agent log (UNIX)[1]

event/action control agent log (Windows)[1]

event/action control manager log (UNIX)[1]

event/action control manager log (Windows)[1]

Event job execution result log file (UNIX)[1]

Event job execution result log file (Windows)[1]

event monitoring log (UNIX)[1]

event monitoring log (Windows)[1]

event search log (UNIX)[1]

event search log (Windows)[1]

executing action job results in abnormal end[1]

executing custom job results in abnormal end[1]

executing HTTP connection job results in abnormal end[1]

executing standard job results in abnormal end[1]

execution interval control log (UNIX)[1]

execution interval control log (Windows)[1]

execution log for embedded database operation commands (UNIX)[1]

execution log for embedded database operation commands (Windows)[1]

Execution log for jajs_cnvdb command (UNIX)[1]

Execution log for jajs_cnvdb command (Windows)[1]

Execution log for jajs_dbbackup command (UNIX)[1]

Execution log for jajs_dbbackup command (Windows)[1]

Execution log for jajs_dbrestore command (UNIX)[1]

Execution log for jajs_dbrestore command (Windows)[1]

export command trace log (UNIX)[1]

export command trace log (Windows)[1]

F

file monitoring log (UNIX)[1]

file monitoring log (Windows)[1]

files

list for JP1/AJS3 programs[1]

files and directories for JP1/AJS3 Console Agent (JP1/AJS3 Console Agent for UNIX)[1]

files and directories that user can reference (when JP1/AJS3 - Manager for UNIX and JP1/AJS3 Console Manager are used)[1]

files and directories that user does not need to modify or reference (when JP1/AJS3 - Manager for UNIX and JP1/AJS3 Console Manager are used)[1]

files and folders for JP1/AJS3 Console Agent (JP1/AJS3 Console Agent for Windows)[1]

files and folders for JP1/AJS3 Console View (when JP1/AJS3 - View and JP1/AJS3 Console View are used)[1], [2]

files and folders that user can reference (when JP1/AJS3 - Manager for Windows and JP1/AJS3 Console Manager are used)[1]

files and folders that user does not need to modify or reference (when JP1/AJS3 - Manager for Windows and JP1/AJS3 Console Manager are used)[1]

files and folders when HTTP connection jobs are used[1]

Files that the user can modify (JP1/AJS3 - Agent for Windows)[1]

files that user can create and modify (when JP1/AJS3 - Manager for Windows and JP1/AJS3 Console Manager are used)[1]

files that user references, and for which deletion must be managed during operation (when JP1/AJS3 - Agent for Windows and HTTP connection jobs are used)[1]

files that user references, and for which deletion must be managed during operation (when JP1/AJS3 - Manager for Windows and HTTP connection jobs are used)[1]

files that user references and files whose deletion must be managed during operation (when JP1/AJS3 - Agent for UNIX and HTTP connection job are used)[1]

files that user references and files whose deletion must be managed during operation (when JP1/AJS3 - Manager for UNIX and HTTP connection job are used)[1]

flexible job execution host log file (UNIX)[1]

flexible job execution host log file (Windows)[1], [2]

flexible job execution process[1]

flexible job execution requester log file (UNIX)[1]

flexible job execution requester log file (Windows)[1], [2]

flexible job trace log (UNIX)[1]

flexible job trace log (Windows)[1]

flow control subprocess internal log (UNIX)[1]

flow control subprocess internal log (Windows)[1]

format

common to all logs[1]

H

httpsd[1], [2]

httpsd.exe[1], [2], [3]

I

import command trace log (UNIX)[1]

import command trace log (Windows)[1]

integrated trace log[1]

Internal error log file for JP1/IM2 linkage command (UNIX)[1]

Internal error log file for JP1/IM2 linkage command (Windows)[1]

Internal information log file for JP1/IM2 linkage command (UNIX)[1]

Internal information log file for JP1/IM2 linkage command (Windows)[1]

internal trace log file for HTTP connection job execution (UNIX)[1]

internal trace log file for HTTP connection job execution (Windows)[1], [2]

Internal trace log file for JP1/IM2 linkage command (UNIX)[1]

Internal trace log file for JP1/IM2 linkage command (Windows)[1]

ISAM

checking file status[1]

troubleshooting files[1]

J

jajs_agtd[1], [2]

jajs_agtd.exe[1], [2]

jajs_config command trace log (UNIX)[1]

jajs_config command trace log (Windows)[1]

jajs_dbmd[1]

jajs_dbmd_embedded-database-setup-identifier[1]

jajs_dbmd.exe[1], [2]

jajs_extdb command trace log (UNIX)[1], [2]

jajs_hstd[1], [2]

jajs_hstd.exe[1], [2]

jajs_killall.cluster command trace log (UNIX)[1]

jajs_migrate command trace log (UNIX)[1]

jajs_migrate command trace log (Windows)[1]

jajs_pmtcon command trace log (UNIX)[1], [2]

jajs_pmtcon command trace log (Windows)[1]

jajs_schd[1], [2]

jajs_schd.exe[1], [2]

jajs_service.exe[1], [2]

jajs_setup_cluster command trace log (UNIX)[1]

jajs_setup_cluster command trace log (Windows)[1]

jajs_setup command trace log (UNIX)[1]

jajs_setup command trace log (Windows)[1]

jajs_spmd[1], [2]

jajs_spmd.exe[1], [2]

jajs_web_service.exe[1]

jajsshowadminusr command trace log (UNIX)[1], [2]

java.exe[1]

job execution agent log (UNIX)[1]

job execution agent log (Windows)[1]

job execution client log (UNIX)[1]

job execution client log (Windows)[1]

job execution environment

troubleshooting[1]

job execution environment database reorganization log (UNIX)[1]

job execution environment database reorganization log (Windows)[1]

job execution internal log (UNIX)[1], [2], [3], [4]

job execution internal log (Windows)[1], [2], [3], [4]

job execution manager log (UNIX)[1]

job execution manager log (Windows)[1]

Job execution result log file (UNIX)[1]

Job execution result log file (Windows)[1]

Job execution status report log (UNIX)[1]

job execution status report log (Windows)[1]

jobnets

troubleshooting[1]

troubleshooting delay[1]

jobs

troubleshooting[1]

JP1/AJS3

list of files and directories[1]

JP1/AJS3 - Agent

child and detail processes (UNIX)[1]

child and detail processes (Windows)[1]

list of files and directories[1]

parent and child processes (UNIX)[1]

parent and child processes (Windows)[1]

processes (UNIX)[1]

processes (Windows)[1]

JP1/AJS3 Check Agent service[1], [2]

JP1/AJS3 Check Manager service[1], [2]

JP1/AJS3 HTTP Server service[1], [2]

JP1/AJS3 - Manager

child and detail processes (UNIX)[1]

child and detail processes (Windows)[1]

list of files and directories[1]

parent and child processes (UNIX)[1]

parent and child processes (Windows)[1]

processes (UNIX)[1]

processes (Windows)[1]

JP1/AJS3 operation

troubleshooting[1]

JP1/AJS3 Queueless Agent service[1], [2]

JP1/AJS3 Queueless File Transfer service[1], [2]

JP1/AJS3 - View

login troubleshooting[1]

processes (Windows)[1]

JP1/AJS3 Web Application Server service[1]

jp1ajs2_setup_cluster command trace log (UNIX)[1]

jpoagent[1], [2], [3], [4]

jpoagent.exe[1], [2], [3], [4]

jpoagtsub[1], [2]

jpoagtsub.exe[1], [2]

jpocwtflMain[1], [2]

jpocwtflMain.exe[1], [2]

jpocwtflSub[1], [2]

jpocwtflSub.exe[1], [2]

jpocwtmlmain[1], [2]

jpocwtmlmain.exe[1], [2]

jpocwttmMain[1], [2]

jpocwttmMain.exe[1], [2]

jpoeventwatch[1], [2]

jpoeventwatch.exe[1], [2]

jpoevsearch[1], [2]

jpoevsearch.exe[1], [2]

jpomanager[1], [2], [3]

jpomanager.exe[1], [2], [3]

jpomgrsub[1]

jpomgrsub.exe[1]

jpomlapirec.exe[1], [2], [3], [4]

jpomlapirec2.exe[1], [2], [3], [4]

jpomlapisend.exe[1], [2], [3], [4]

jpomlapisend2.exe[1], [2], [3], [4]

jpomldsk.exe[1], [2]

jpomlsrv.exe[1], [2]

jpqagt[1], [2]

jpqagt.exe[1], [2]

jpqagtchild[1], [2]

jpqagtdmn[1], [2]

jpqman[1], [2]

jpqman.exe[1], [2]

jpqmon[1], [2], [3], [4]

jpqmon.exe[1], [2], [3], [4]

jpqnfyfd[1]

jpqnfyfd.exe[1]

K

KAVS8029-E (troubleshooting typical problems)[1], [2]

KAVS8033-E (troubleshooting typical problems)[1]

KAVU1203-E (troubleshooting typical problems)[1], [2]

KAVU1204-E (troubleshooting typical problems)[1], [2]

KAVU2251-E (troubleshooting typical problems)[1], [2]

KAVU3284-W (troubleshooting typical problems)[1]

KAVU3521-W (troubleshooting typical problems)[1], [2]

KAVU3531-W (troubleshooting typical problems)[1]

KAVU3571-W (troubleshooting typical problems)[1], [2]

KAVU3577-W (troubleshooting typical problems)[1]

KAVU3586-W (troubleshooting typical problems)[1], [2]

KAVU4254-E (troubleshooting typical problems)[1]

KAVU4511-W (troubleshooting typical problems)[1]

KAVU4512-W (troubleshooting typical problems)[1]

KAVU4514-W (troubleshooting typical problems)[1]

KAVU4515-W (troubleshooting typical problems)[1]

KAVU4520-W (troubleshooting typical problems)[1]

KAVU4530-W (troubleshooting typical problems)[1], [2]

KAVU4531-W (troubleshooting typical problems)[1], [2]

KAVU4538-W (troubleshooting typical problems)[1], [2]

KAVU4546-W (troubleshooting typical problems)[1], [2]

KAVU4547-W (troubleshooting typical problems)[1], [2]

KAVU4548-W (troubleshooting typical problems)[1], [2]

KAVU4551-W (troubleshooting typical problems)[1]

KAVU4560-W (troubleshooting typical problems)[1], [2]

KAVU4563-W (troubleshooting typical problems)[1], [2]

KAVU4571-W (troubleshooting typical problems)[1], [2]

KAVU4580-W (troubleshooting typical problems)[1], [2]

KAVU4581-W (troubleshooting typical problems)[1]

KAVU4583-W (troubleshooting typical problems)[1], [2]

KAVU4597-W (troubleshooting typical problems)[1], [2]

KAVU4721-E (troubleshooting typical problems)[1], [2]

KAVU5282-W (troubleshooting typical problems)[1]

KAVU5284-E (troubleshooting typical problems)[1]

KAVU5285-E (troubleshooting typical problems)[1]

KAVU5287-E (troubleshooting typical problems)[1]

KAVU5501-E (troubleshooting typical problems)[1]

KAVU5921-E (troubleshooting typical problems)[1]

KAVU5950-E (troubleshooting typical problems)[1]

KAVU7533-E (troubleshooting typical problems)[1], [2], [3], [4]

KAVV3102-E (troubleshooting typical problems)[1]

KAVV3103-E (troubleshooting typical problems)[1], [2]

KAVV400-E (troubleshooting typical problems)[1]

KAVV401-E (troubleshooting typical problems)[1]

KAVV452-E (troubleshooting typical problems)[1]

KAVV457-E (troubleshooting typical problems)[1]

KAVV458-E (troubleshooting typical problems)[1]

KAVV459-E (troubleshooting typical problems)[1]

L

license management log (Windows)[1]

log (UNIX)

agent management[1]

log (Windows)

agent management[1]

log file and directory names (UNIX)[1]

log file and folder names (Windows)[1]

log file for broadcast agent and broadcast-execution destination agents (UNIX)[1]

log file for broadcast agent and broadcast-execution destination agents (Windows)[1]

log files and directories in JP1/AJS3 - Agent (UNIX)[1]

log files and directories of JP1/AJS3 - Manager (UNIX)[1]

log files and folders in JP1/AJS3 - Agent (Windows)[1]

log files and folders in JP1/AJS3 - Manager (Windows)[1]

log files and folders in JP1/AJS3 - View (Windows)[1]

log files and folders in JP1/AJS3 - Web Console (UNIX)[1]

log files and folders in JP1/AJS3 - Web Console (Windows)[1]

log file storage directories (when JP1/AJS3 - Manager for UNIX and JP1/AJS3 Console Manager is used)[1]

log file storage folders (when JP1/AJS3 - Manager for Windows and JP1/AJS3 Console Manager is used)[1]

log information and logging formats[1]

log name (UNIX)[1]

log name (Windows)[1]

log output destination folder in cluster system (Windows)[1]

log output directory in cluster system (UNIX)[1]

logs

common message log[1]

entries output by scheduler services[1]

entries output by the queueless agent service[1]

entries recorded when definitions are pre-checked[1]

information[1]

integrated trace log[1]

list of log files and directories[1]

scheduler log[1]

system failure log[1]

trace log[1]

types and storage location[1]

M

mail delivery log (UNIX)[1]

mail monitoring log (common, for Windows)[1]

mail monitoring log (UNIX)[1]

mail monitoring log (when mail linkage is performed in service, for Windows)[1]

mail monitoring log (when mail linkage is performed on desktop, for Windows)[1]

mail system linkage

troubleshooting (Windows)[1]

maintenance log (UNIX)[1]

maintenance log (Windows)[1]

Management portal execution environment internal log (UNIX)[1]

Management portal execution environment internal log (Windows)[1]

maximum disk space (UNIX)[1]

maximum disk space (Windows)[1], [2]

migration command execution log (Windows)[1]

N

NNM linkage log (UNIX)[1]

NNM linkage log (Windows)[1]

O

ODBC internal error log (UNIX)[1]

ODBC internal error log (Windows)[1]

OS

action to be taken if terminates abnormally[1]

P

pd_buf_dfw[1]

pd_buf_dfw.exe[1]

pdlogd[1]

pdlogd.exe[1]

pdlogswd[1]

pdlogswd.exe[1]

pdmgrd[1]

pdmlgd[1]

pdmlgd.exe[1]

pdprcd[1], [2]

pdprcd.exe[1], [2]

pdrdmd[1]

pdrdmd.exe[1]

pdrsvre[1]

pdrsvre.exe[1]

pdscdd[1]

pdscdd.exe[1]

pdsds[1]

pdsds.exe[1]

pdservice.exe[1]

pdsha.exe[1]

pdstsd[1]

pdstsd.exe[1]

pdtrnd[1]

pdtrnd.exe[1]

pdtrnrvd[1]

pdtrnrvd.exe[1]

performance log file (UNIX)[1]

performance log file (Windows)[1]

processes

child and detail of JP1/AJS3 - Agent (UNIX)[1]

child and detail of JP1/AJS3 - Agent (Windows)[1]

child and detail of JP1/AJS3 - Manager (UNIX)[1]

child and detail of JP1/AJS3 - Manager (Windows)[1]

configuration[1]

for embedded database[1]

for UNIX[1]

for Windows[1]

JP1/AJS3 - View (Windows)[1]

list of[1]

parent and child of JP1/AJS3 - Agent (UNIX)[1]

parent and child of JP1/AJS3 - Agent (Windows)[1]

parent and child of JP1/AJS3 - Manager (UNIX)[1]

parent and child of JP1/AJS3 - Manager (Windows)[1]

Q

queueless agent process[1], [2]

queueless file transfer process[1], [2]

queueless job execution internal log (UNIX)[1]

queueless job execution internal log (Windows)[1]

queueless log[1]

queueless log (UNIX)[1], [2]

queueless log (Windows)[1]

queueless trace log (UNIX)[1]

queueless trace log (Windows)[1]

R

rotatelogs2[1]

rotatelogs2.exe[1], [2]

S

scheduler information log

entries[1]

scheduler log (UNIX)[1]

scheduler log (Windows)[1]

scheduler trace log of each scheduler service (UNIX)[1]

scheduler trace log of each scheduler service (Windows)[1]

service startup

troubleshooting[1]

setup

troubleshooting[1]

storage

location of logs[1]

system management log (UNIX)[1]

system management log (Windows)[1]

T

Temporary output file for JP1/IM2 linkage command (UNIX)[1]

Temporary output file for JP1/IM2 linkage command (Windows)[1]

the status file used to store information about running queueless jobs (UNIX)[1]

the status file used to store information about running queueless jobs (Windows)[1]

timing for switching file (Windows)[1]

Timing for switching files[1]

trace log (UNIX)

agent management[1]

communication control[1]

trace log (Windows)

agent management[1]

communication control[1]

troubleshooting

agent failures[1]

commands[1]

data to collect[1]

data to collect when problem occurs[1]

delayed jobnet with start condition[1]

embedded database[1]

general procedure[1]

ISAM files[1]

job execution environment[1]

jobs and jobnets[1]

JP1/AJS3 - View login[1]

mail system linkage (Windows)[1]

registration of jobs and jobnets for execution[1]

setup, service startup, and JP1/AJS3 operation[1]

standard, HTTP connection, action, and custom jobs[1]

typical problems[1]

U

UNIX

collecting data for troubleshooting[1]

data to collect when problem occurs[1]

JP1/AJS3 - Manager files and directories[1]

list of processes[1]

logs[1]

W

Windows

collecting data for troubleshooting[1]

data to collect when problem occurs[1]

JP1/AJS3 - Agent files and directories[1]

JP1/AJS3 - Manager files and directories[1]

list of processes[1]

logs[1]