Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2

3021-3-322-20(E)

Notices

Relevant program products

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

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

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

The above product includes the following:

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

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

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

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

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

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

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

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

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

The above product includes the following:

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

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

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

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

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

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

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

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

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

The above product includes the following:

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

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

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

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

The above product includes the following:

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

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

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

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

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

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

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

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

Trademarks

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Microsoft product name abbreviations

This manual uses the following abbreviations for Microsoft product names.

Abbreviation

Full name or meaning

Excel

Microsoft(R) Excel

Microsoft(R) Office Excel

Exchange Server

Microsoft(R) Exchange 2000 Enterprise Server

Microsoft(R) Exchange 2000 Server

Microsoft(R) Exchange Server

IE

Internet Explorer

Microsoft(R) Internet Explorer(R)

Windows(R) Internet Explorer(R)

Microsoft Mail

Microsoft(R) Mail

Microsoft SQL Server

Microsoft(R) SQL Server

Microsoft(R) SQL Server Enterprise Edition

MSCS

Microsoft(R) Cluster Server

MSMQ

Microsoft(R) Message Queue Server

Outlook

Outlook 2003

Microsoft(R) Outlook(R) 2003

Outlook 2007

Microsoft(R) Outlook(R) 2007

Outlook 2010

Microsoft(R) Outlook(R) 2010

Outlook Express

Microsoft(R) Outlook(R) Express

Windows 7

Microsoft(R) Windows(R) 7 Enterprise

Microsoft(R) Windows(R) 7 Professional

Microsoft(R) Windows(R) 7 Ultimate

Windows 8

Windows(R) 8 Enterprise

Windows(R) 8 Pro

Windows 8.1

Windows(R) 8.1 Enterprise

Windows(R) 8.1 Pro

Windows Server 2003

Windows Server 2003

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

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

Windows Server 2003 R2

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

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

Windows Server 2003 (x64)

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

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

Windows Server 2003 R2 (x64)

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

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

Windows Server 2008

Windows Server 2008

Microsoft(R) Windows Server(R) 2008 Datacenter

Microsoft(R) Windows Server(R) 2008 Enterprise

Microsoft(R) Windows Server(R) 2008 Standard

Windows Server 2008 R2

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

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

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

Windows Server 2012

Windows Server 2012

Microsoft(R) Windows Server(R) 2012 Datacenter

Microsoft(R) Windows Server(R) 2012 Standard

Windows Server 2012 R2

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

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

Windows Vista

Microsoft(R) Windows Vista(R) Business

Microsoft(R) Windows Vista(R) Enterprise

Microsoft(R) Windows Vista(R) Ultimate

Windows XP Professional

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

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

Restrictions

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

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

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

Issued

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

Copyright

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

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

Summary of amendments

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

Changes

Location

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

System Design (Configuration) Guide:

F

Configuration Guide 1:

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

Troubleshooting:

2.14

Messages 2:

KFPS00615-W, KFPU00219-E

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

Configuration Guide 1:

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

Administration Guide:

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

Command Reference 2:

2. jajs_rpenvexport, 2. jajs_rpenvimport, 2. jajs_rpsite

Messages 1:

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

Messages 2:

KNAD3994-E

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

Overview:

3.3.2

System Design (Work Tasks) Guide:

3.5.5

Operator's Guide:

15.3.17

Command Reference 1:

2. ajschgnet, 2. ajsprint

Command Reference 2:

4.2.4

Messages 1:

KAVS0188-E

Messages 2:

KAVV455-E

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

Overview:

3.4.2, 4.1.1

System Design (Work Tasks) Guide:

2.2.3

Operator's Guide:

15.3.1, 15.3.22, 15.3.38, 15.3.47, 15.10.1

Command Reference 1:

2. ajsentry

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

System Design (Configuration) Guide:

4.5.4

Configuration Guide 1:

C.1

Administration Guide:

2.2.2, 2.2.4, 2.3.5, 13.1, 13.1.8

Troubleshooting:

A.1, A.3

Operator's Guide:

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

Command Reference 1:

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

Command Reference 2:

2. jajs_setup_cluster

Messages 1:

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

Messages 2:

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

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

System Design (Configuration) Guide:

5.1.1, 9.4

Configuration Guide 1:

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

Administration Guide:

2.2.5, 2.3.6

Troubleshooting:

1.4.1, 1.4.2, 2.7.2

Command Reference 1:

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

Command Reference 2:

1.5.8, 1.6

Messages 2:

KAVU5287-E, KAVU5501-E

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

Configuration Guide 2:

2.2.1, 2.2.2

Administration Guide:

13.1, 13.1.8

Command Reference 1:

2. ajsprint

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

Configuration Guide 1:

6.3.19, 15.3.19

Configuration Guide 2:

2.4.1, 2.4.2

Administration Guide:

8.9.2

Messages 1:

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

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

Overview:

10.1.1

System Design (Configuration) Guide:

2.4.3, 7.2.2, 8.2.2

Configuration Guide 1:

13.4.1, 15.1.9, C.2, D.2

Configuration Guide 2:

2.2.2, 2.7.1, 2.8.2

Administration Guide:

4.4.2

Operator's Guide:

15.3.6

Command Reference 1:

1.4.1

Command Reference 2:

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

Messages 2:

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

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

Administration Guide:

11.6.1

Command Reference 1:

2. jajs_killall.cluster

Legend:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Preface

This manual describes the environment setting parameters and operation profiles in Job Management Partner 1/Automatic Job Management System 3 (abbreviated hereafter to JP1/AJS3).

Intended readers

This manual is intended for:

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

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

Organization of this manual

This manual 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. Overview of the Environment Setting Parameters

Chapter 1 describes the environment setting parameters in JP1/AJS3.

2. Environment Setting Parameters

Chapter 2 lists the environment setting parameters, and describes how they are defined.

3. Operation Profiles

Chapter 3 provides an overview of operation profiles and describes them in detail.

Conventions: Fonts and symbols

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

Text formatting

Convention

Bold

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

From the File menu, choose Open.

Click the Cancel button.

In the Enter name entry box, type your name.

Italic

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

Write the command as follows:

copy source-file target-file

The following message appears:

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

Italic characters are also used for emphasis. For example:

Do not delete the configuration file.

Monospace

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

At the prompt, enter dir.

Use the send command to send mail.

The following message is displayed:

The password is incorrect.

The following table explains the symbols used in this manual:

Symbol

Convention

|

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

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

{ }

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

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

[ ]

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

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

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

...

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

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

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

x

Multiplication sign

/

Division sign

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

Example:

The result of 34 / 3 is 12.

(tilde)

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

< >

(angle brackets)

Indicates the characters and lexical elements that can be specified.

<characters>

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

<numeric>

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

<alphabetic character>

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

<alphanumeric character>

Alphabetic or numeric character

<symbolic name>

No more than eight alphanumeric characters beginning with an alphabetic character

<unsigned integer>

One or more numeric characters

<hexadecimal character>

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

<file name>

A system-determined name assigned to a file

<path>

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

(( ))

(double parentheses)

Indicates the range of specifiable values.

<< >>

(double angle brackets)

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

Example:

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

MAX

Choose the largest of the calculation results.

Example:

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

Conventions: Version numbers

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

Version 1.00 (or 1.0) is written as 01-00.

Version 2.05 is written as 02-05.

Version 2.50 (or 2.5) is written as 02-50.

Version 12.25 is written as 12-25.

The version number might be shown on the spine of a manual as Ver. 2.00, but the same version number would be written in the program as 02-00.

JP1 program reorganization in version 8

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

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

JP1/AJS2 - Client Toolkit was eliminated.

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

Organization of JP1/AJS3 manuals and choosing the right manuals

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

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

No.

Manual

Contents

1

Overview

(3021-3-318(E))

JP1/AJS3 features

Description of functions

2

System Design (Configuration) Guide

(3021-3-319(E))

Information that must be considered when designing a system

Cautionary notes on designing a system

3

System Design (Work Tasks) Guide

(3021-3-320(E))

Information that must be considered when constructing jobs and jobnets

Cautionary notes on designing jobs and jobnets

4

Configuration Guide 1

(3021-3-321(E))

Installation and setup procedures

Environment setup procedure by operation type

5

Configuration Guide 2

(3021-3-322(E))

Description of environment setting parameters

Description of operation profiles

6

Administration Guide

(3021-3-323(E))

Information required to operate a system

Know-how useful for JP1/AJS3 operation

7

Troubleshooting

(3021-3-324(E))

How to troubleshoot errors

Data required when an error occurs

8

Operator's Guide

(3021-3-325(E))

How to operate JP1/AJS3 - View

How to operate JP1/AJS3 Console View

Description of windows and dialog boxes

9

Command Reference 1

(3021-3-326(E))

Command syntax

10

Command Reference 2

(3021-3-327(E))

Syntax of commands used for setup and special operations

Syntax and coding examples of information definition files

11

Linkage Guide

(3021-3-328(E))

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

12

Messages 1

(3021-3-329(E))

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

13

Messages 2

(3021-3-330(E))

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

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

Purpose

Required reading

Read as necessary

To learn about JP1/AJS3's functionalities

Overview

(3021-3-318(E))

Linkage Guide

(3021-3-328(E))

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

System Design (Configuration) Guide

(3021-3-319(E))

Configuration Guide 1

(3021-3-321(E))

Configuration Guide 2

(3021-3-322(E))

Linkage Guide

(3021-3-328(E))

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

System Design (Work Tasks) Guide

(3021-3-320(E))

Operator's Guide

(3021-3-325(E))

To learn about monitoring and maintaining a running system

Administration Guide

(3021-3-323(E))

Troubleshooting

(3021-3-324(E))

Messages 1

(3021-3-329(E))

Messages 2

(3021-3-330(E))

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

Troubleshooting

(3021-3-324(E))

Messages 1

(3021-3-329(E))

Messages 2

(3021-3-330(E))

To learn about operating JP1/AJS3

Operator's Guide

(3021-3-325(E))

Command Reference 1

(3021-3-326(E))

Command Reference 2

(3021-3-327(E))

1 Overview of the Environment Setting Parameters

This chapter describes the environment setting parameters in JP1/AJS3.

1.1 Format of the environment setting parameters

This section describes the format of the definition keys and environment setting parameters used in this manual.

1.1.1 Format of the definition keys

Definition keys are written in the following format:

[name-of-definition-key]

The name of each definition key name is enclosed in square brackets ([ ]).

In the {JP1_DEFAULT|logical-host-name} part, enter JP1_DEFAULT for the physical host, and enter the name of a logical host for logical-host-name.

1.1.2 Format of the environment setting parameters

Environment setting parameters are written in the following format:

"name-of-environment-setting-parameter"=definition

The name of an environment setting parameter is enclosed in double quotation marks (").

If a string is specified for a definition, the definition is enclosed in double quotation marks. If a numeric value is specified for a definition, dword: precedes the value.

If multiple values are allowed for the definition of an environment setting parameter, the values are separated by a colon (:). Note that you must specify at least one value.

Example:

If the definition key is {backup:export:name:print:schedule:show:rgexport:release}, you can specify more than one of the following values:

backup, export, name, print, schedule, show, rgexport, and release

2 Environment Setting Parameters

This chapter lists the environment setting parameters, and describes how they are defined.

2.1 Setting up the system management environment

This section describes the environment setting parameters for the system management.

2.1.1 List of environment setting parameters for the system management

The system management environment requires different settings in the manager environment (JP1/AJS3 - Manager) and the agent environment (JP1/AJS3 - Agent).

The table below describes the environment setting parameters to be used to set the system management in the manager environment (JP1/AJS3 - Manager) and the agent environment (JP1/AJS3 - Agent).

To determine whether an environment setting parameter is to be set in Windows or UNIX, see the Applicable OS column. To determine whether an environment setting parameter is to be set in the manager environment (JP1/AJS3 - Manager) or the agent environment (JP1/AJS3 - Agent), see the Applicable product column.

Table 2‒1: Environment setting parameters (system management)

No.

Definition key

Environment setting parameter

Definition

Applicable OS

Applicable product

1

[{JP1_DEFAULT|logical-host-name}\JP1AJS2]#

"SEND_PROCESS_TERMINATED_ABNORMALLY_EVENT"=

Whether a JP1 event is issued when a process terminates abnormally or times out at startup (Used to ensure compatibility when an upgrade is performed)

Windows

UNIX

M, A

2

"SEND_PROCESS_RESTART_EVENT"=

Whether a JP1 event is issued when a process is restarted (Used to ensure compatibility when an upgrade is performed)

Windows

UNIX

M, A

3

"SEND_SYSTEM_STARTSTOP_EVENT"=

Whether a JP1 event is issued when JP1/AJS3 starts or stops

Windows

UNIX

M, A

4

"SEND_SYSTEM_CHILD_STARTSTOP_EVENT"=

Whether a JP1 event is issued when a process starts or stops

Windows

UNIX

M

5

"SEND_SYSTEM_TERMINATED_ABNORMALLY_EVENT"=

Whether a JP1 event is issued when a process terminates abnormally or times out at startup

Windows

UNIX

M, A

6

"SEND_SYSTEM_RESTART_EVENT"=

Whether a JP1 event is issued when a process is restarted

Windows

UNIX

M, A

7

[{JP1_DEFAULT|logical-host-name}\JP1AJS2\HOST]#

"AJSSYSDIR"=

The system folder of a host

Windows

UNIX

M

8

"AJSLOGDIR"=

The log folder of a host

Windows

UNIX

M

9

"HOSTLOGSIZE"=

The size of the scheduler log file of a host

Windows

UNIX

M

10

"HOSTLOGFILE1"=

The name of the scheduler log file 1 of a host

Windows

UNIX

M

11

"HOSTLOGFILE2"=

The name of the scheduler log file 2 of a host

Windows

UNIX

M

12

"HOSTLOGOUTPUTYEAR"=

Setting for whether the year in the date of a host's scheduler log is to be output

Windows

UNIX

M

13

"HOSTLOGHEADER"=

Whether a host's scheduler log history information is to be output with the process ID added

Windows

UNIX

M

14

"HLOGDLOG"=

Setting for whether to output the start and stop history of the scheduler-log output process (ajshlogd.exe in Windows, or ajshlogd in UNIX) to the scheduler log for hosts

Windows

UNIX

M

15

"HLOGDSYSLOG"=

In Windows:

Setting for whether to output the start and stop history of the scheduler-log output process ajshlogd.exe to the Windows event log and the integrated trace log for hosts

In UNIX:

Setting for whether to output the start and stop history of the scheduler-log output process ajshlogd to the syslog file and the integrated trace log for hosts

Windows

UNIX

M

16

[{JP1_DEFAULT|logical-host-name}\JP1AJS2\LOG_CONTROL\JAJS_SPM]

"LOGSIZE"=

The size of the system management log

Windows

UNIX

M, A

17

"LOGFILENUM"=

The number of system management log files

Windows

UNIX

M, A

Legend:

M: JP1/AJS3 - Manager

A: JP1/AJS3 - Agent

#

Specify JP1_DEFAULT for the physical host. For logical-host-name, specify the name of a logical host.

The following describes each of the environment setting parameters:

Parameters that are not described here are used for maintenance purposes. Do not change the values of those parameters.

The default value is used whenever a value is not specified for an environment setting parameter.

2.1.2 Details of the environment setting parameters for the system management

(1) "SEND_PROCESS_TERMINATED_ABNORMALLY_EVENT" = dword:Whether-to-issue-a-JP1-event-when-a-process-terminates-abnormally-or-times-out-at-startup

Use this parameter to specify whether to issue a JP1 event when a process terminates abnormally or times out at startup.

This parameter ensures compatibility when you upgrade from an old version. In an upgrade, the parameter setting is inherited.

Specifiable values

0

A JP1 event is not issued.

1

A JP1 event is issued.

Default value

dword:00000000 (0 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service starts

(2) "SEND_PROCESS_RESTART_EVENT" = dword:whether-to-issue-a-JP1-event-when-a-process-is-restarted

Use this parameter to specify whether to issue a JP1 event when the process is restarted.

This parameter ensures compatibility when you upgrade from an old version. In an upgrade, the parameter setting is inherited.

Specifiable values

0

A JP1 event is not issued.

1

A JP1 event is issued.

Default value

dword:00000000 (0 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service starts

(3) "SEND_SYSTEM_STARTSTOP_EVENT" = dword:whether-to-issue-a-JP1-event-when-JP1/AJS3-is-started-or-stops

Use this parameter to specify whether to issue a JP1 event when the JP1/AJS3 service starts or stops.

Specifiable values

0

A JP1 event is not issued.

1

A JP1 event is issued.

Default value

dword:00000000 (0 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service starts

(4) "SEND_SYSTEM_CHILD_STARTSTOP_EVENT" = dword:Whether-to-issue-a-JP1-event-when-a-process-is-started-or-stops

Use this parameter to specify whether to issue a JP1 event when a process starts or stops.

The applicable processes are as follows:

In Windows:

Child process of jajs_spmd.exe

Child process of jajs_dbmd.exe, jajs_hstd.exe, jajs_agtd.exe, and jajs_schd.exe

In UNIX:

Child process of jajs_spmd

Child process of jajs_dbmd, jajs_hstd, jajs_agtd, and jajs_schd

For details about processes, see the B.2 Processes (for Windows) in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting or B.3 Processes (for UNIX) in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

Specifiable values

0

A JP1 event is not issued.

1

A JP1 event is issued.

Default value

dword:00000000 (0 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service starts

(5) "SEND_SYSTEM_TERMINATED_ABNORMALLY_EVENT" = dword:Whether-to-issue-a-JP1-event-when-a-process-terminates-abnormally-or-times-out-at-startup

Use this parameter to specify whether to issue a JP1 event when a process terminates abnormally or times out at startup.

The applicable processes are as follows:

In Windows:

Child process of jajs_spmd.exe

Child process of jajs_dbmd.exe, jajs_hstd.exe, jajs_agtd.exe, and jajs_schd.exe

In UNIX:

Child process of jajs_spmd

Child process of jajs_dbmd, jajs_hstd, jajs_agtd, and jajs_schd

For details about the processes, see B.2 Processes (for Windows) in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting or B.3 Processes (for UNIX) in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

This environment setting parameter has the same functionality as the SEND_PROCESS_TERMINATED_ABNORMALLY_EVENT environment setting parameter. In an environment configured by a new installation, specify the SEND_SYSTEM_TERMINATED_ABNORMALLY_EVENT environment setting parameter.

Do not specify this parameter together with the SEND_PROCESS_TERMINATED_ABNORMALLY_EVENT environment setting parameter. If you specify these parameters concurrently with 1 specified for either parameter, a JP1 event will be issued.

Specifiable values

0

A JP1 event is not issued.

1

A JP1 event is issued.

Default value

dword:00000000 (0 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service starts

(6) "SEND_SYSTEM_RESTART_EVENT" = dword:Whether-to-issue-a-JP1-event-when-a-process-is-restarted

Use this parameter to specify whether to issue a JP1 event when a process is restarted.

This environment setting parameter has the same functionality as the SEND_PROCESS_RESTART_EVENT environment setting parameter. In an environment configured by a new installation, specify the SEND_SYSTEM_RESTART_EVENT environment setting parameter.

Do not specify this parameter together with the SEND_PROCESS_RESTART_EVENT environment setting parameter. If you specify these parameters concurrently with 1 specified for either parameter, a JP1 event will be issued.

Specifiable values

0

A JP1 event is not issued.

1

A JP1 event is issued.

Default value

dword:00000000 (0 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service starts

(7) "AJSSYSDIR" = "name-of-system-directory"

Use this parameter to specify the name of the directory in which the JP1/AJS3 system files are to be created. Specify a full path name.

Determine the name based on operating requirements and an estimate of required disk space.

For users with administrator permissions or superuser permissions, set the update permission (rwx for UNIX) for this directory. For all users, set the operation permission (rx for UNIX).

Specifiable values

In Windows:

A character string of no more than 180 bytes

In UNIX:

A character string of no more than 191 bytes

Do not use either semicolons (;) or spaces.

Default value

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\sys

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-Manager-installation-folder\sys

For Windows Server 2003:

JP1/AJS3-Manager-installation-folder\sys

In UNIX:

/var/opt/jp1ajs2/sys/

Recommended value

For a physical host:

Default value

For a logical host:

The value set at the time of setup.

When the setting takes effect

The next time the JP1/AJS3 service starts

Cautionary notes

The default folders and directories also have uses that are not related to this environment setting parameter. Do not delete the default folders or directories even if you have changed the environment setting parameter.

Specify different paths for the physical and logical hosts.

Specify a path on the shared disk for logical hosts in a cluster configuration.

(8) "AJSLOGDIR" = "directory-name-for-log"

Use this parameter to specify the name of the directory in which JP1/AJS3 log files are to be created. Specify a full path name.

Determine the name based on operating requirements and an estimate of the required disk space.

For all users, set the update permission (rwx for UNIX) for this directory.

Specifiable values

In Windows:

A character string of no more than 180 bytes

In UNIX:

A character string of no more than 191 bytes

Do not use either semicolons (;) or spaces.

Default value

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

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

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-Manager-installation-folder\log

For Windows Server 2003:

JP1/AJS3-Manager-installation-folder\log

In UNIX:

/var/opt/jp1ajs2/log

Recommended value

For a physical host:

Default value

For a logical host:

The value set at the time of setup.

When the setting takes effect

The next time the JP1/AJS3 service starts

Cautionary notes

The default folders and directories also have uses that are not related to this environment setting parameter. Do not delete the default folders or directories even if you have changed the environment setting parameter.

Specify different paths for the physical and logical hosts.

Specify a path on the shared disk for logical hosts in a cluster configuration.

(9) "HOSTLOGSIZE" = dword:size-of-scheduler-log-file-for-a-host

Use this parameter to specify the size of log files.

The ajsinetd authentication error log (KAVS1009-W) and the log data when ajshlogd starts (KAVS0220-I) and when it stops (KAVS0221-I), are output to log files. However, if host is output to AJSLOGOUTPUTDEST, which is an environment setting parameter in scheduler service environment settings, the scheduler log of the appropriate scheduler service is output. Accordingly, specify a size sufficient for storing the data of at least one day so that you can check the execution status of a job or jobnet.

For details about how to estimate the log file size when specifying the settings for outputting the scheduler log of a scheduler service, see 3.4.1 Estimating the size of scheduler log files in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

Specifiable values

A hexadecimal value (in kilobytes) from 0 to 1E8480 (0 to 2,000,000 in decimal).

If you specify dword:00000000, the system does not create a log file.

Default value

dword:00000000 (0 in decimal)

During a new installation of JP1/AJS3 or upgrade installation from version 8 or earlier, and during setup of cluster operation, dword:00002800 (10,240 in decimal) is set.

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service starts

(10) "HOSTLOGFILE1" = "name-of-scheduler-log-file-1-for-a-host"

Use this parameter to specify a log file name. Specify a full path name.

Specify a file name that is different from the name of the scheduler log file 2 on any other host.

When the amount of information written to this log file equals or is greater than the specified size, the system writes subsequent information to log file 2.

Specify different paths for the physical and logical hosts.

In UNIX, you cannot omit this parameter if you use a scheduler log file for a host.

Specifiable values

A character string of no more than 255 bytes

Default value

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

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

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

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

For Windows Server 2003:

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

In UNIX:

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

Recommended value

For a physical host:

Default value

For a logical host:

The value set at the time of setup.

When the setting takes effect

The next time the JP1/AJS3 service starts

(11) "HOSTLOGFILE2" = "name-of-scheduler-log-file-2-for-a-host"

Use this parameter to specify a log file name. Specify a full path name.

Specify different paths for the physical and logical hosts.

In UNIX, you cannot omit this parameter when you use a scheduler log file for a host.

Specifiable values

A character string of no more than 255 bytes

Default value

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

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

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

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

For Windows Server 2003:

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

In UNIX:

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

Recommended value

For a physical host:

Default value

For a logical host:

The value set at the time of setup.

When the setting takes effect

The next time the JP1/AJS3 service starts

(12) "HOSTLOGOUTPUTYEAR" = "{yes|no}"

Use this parameter to specify whether to output the year as part of the date of a host's scheduler log. The scheduler log is specified when you specify the HOSTLOGFILE1 and HOSTLOGFILE2 environment setting parameters.

Change the parameter value if you use the year to manage scheduler log information.

Specifiable values

yes

The year is output. The system outputs the year, month, and day in the date section.

no

The year is not output. The system outputs only the month and day in the date section.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service starts

(13) "HOSTLOGHEADER" = "{none|PID}"

Use this parameter value to specify whether to output the history information with the process ID added in a host's scheduler log file.

Change the parameter value to output history information without adding process ID information.

Specifiable values

none

A process ID is not added to the history information to be output.

PID

A process ID is added to the history information to be output.

Default value

none

During a new installation of JP1/AJS3 or upgrade installation from version 8 or earlier, and during setup of cluster operation, PID is set.

Recommended value

PID

When the setting takes effect

The next time the JP1/AJS3 service starts

(14) "HLOGDLOG" = "{none|all}"

Use this parameter value to specify whether to output the start and stop messages related to the scheduler-log output process (ajshlogd.exe in Windows, or ajshlogd in UNIX) to the scheduler log for hosts.

Specifiable values

none

Does not output messages related to starting and stopping the scheduler-log output process for hosts.

all

Outputs messages KAVS0220-I and KAVS0221-I, which are the messages related to starting and stopping the scheduler-log output process for hosts.

Default value

none

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service starts or stops

(15) "HLOGDSYSLOG" = "{none|all}"

In Windows:

Use this parameter value to specify whether to output the start and stop messages related to the scheduler-log output process ajshlogd.exe to the Windows event log and the integrated trace log for hosts.

In UNIX:

Use this parameter value to specify whether to output the start and stop messages related to the scheduler-log output process ajshlogd to the syslog and the integrated trace log for hosts.

Specifiable values

none

Does not output messages related to starting and stopping the scheduler-log output process for hosts.

all

Outputs messages KAVS0220-I and KAVS0221-I, which are the messages related to starting and stopping the scheduler-log output process for hosts.

Default value

none

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service starts or stops

(16) "LOGSIZE" = dword:size-of-the-system-management-log

Use this parameter to specify the size of the system management log.

For details about the log files, see 1.2.4 List of log files and directories in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

Specifiable values

A hexadecimal value (in bytes) from 1000 to 7FFFFFFF (4,096 to 2,147,483,647 in decimal)

Default value

dword:1F400 (128,000 in decimal)

Recommended value

Default value

When the setting takes effect

The next time the JP1/AJS3 service starts

Cautionary note

If the value specified for the log file size and the number of log files are too small, you might not be able to identify the cause of an error. When you change the log file size, do not specify a log file size smaller than the default value.

(17) "LOGFILENUM" = dword:Number-of-system-management-log-files

Use this parameter to specify the number of system management log files.

For details about the log files, see 1.2.4 List of log files and directories in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

Specifiable values

A hexadecimal value from 1 to 10 (1 to 16 in decimal)

Default value

dword:00000003 (3 in decimal)

Recommended value

Default value

When the setting takes effect

The next time the JP1/AJS3 service starts

Cautionary note

If the value specified for the log file size and the number of log files are too small, you might not be able to identify the cause of an error. When you change the number of log files, do not specify a value smaller than the default value.

2.2 Setting up the scheduler service environment

This section describes the environment setting parameters for the scheduler service environment.

2.2.1 List of environment setting parameters for the scheduler service environment

To set up the scheduler service environment, perform the necessary setup operations in the manager environment (JP1/AJS3 - Manager). Nothing is required in the agent environment (JP1/AJS3 - Agent).

The table below describes the environment setting parameters to be used to set the scheduler service environment in the manager environment (JP1/AJS3 - Manager).

To determine whether an environment setting parameter is to be set in Windows or UNIX, see the Applicable OS column.

Table 2‒2: Environment setting parameters (scheduler service environment setup)

No.

Definition key

Environment setting parameter

Definition

Applicable OS

Applicable product

1

[JP1_DEFAULT\JP1AJSMANAGER]

"DEFAULTSERVICENAME"=#1

The name of the default scheduler service

Windows

UNIX

M

2

"REMNETSERVICENAME"=#1

The name of the scheduler service that executes a remote jobnet

Windows

UNIX

M

3

"TRACELOGFILE"=#1

The name of the scheduler trace log file

Windows

UNIX

M

4

"VRSHIFT_IMMINT"=#1

Whether a jobnet stops immediately when it is interrupted or killed

Windows

UNIX

M

5

"VRSHIFT_INTRERUN"=#1

Whether succeeding units are rerun when a jobnet is interrupted

Windows

UNIX

M

6

"IPC_TIMEOUT"=#1

Remote communication timeout

Windows

UNIX

M

7

"IPC_LOCALTIMEOUT"=#1

Local communication timeout

Windows

UNIX

M

8

"IPCRETRYINTERVAL"=#1

Retry interval

Windows

UNIX

M

9

"IPCRETRYCOUNT"=#1

Retry count

Windows

UNIX

M

10

"EVENTRETRY"=#1

The action to be taken for an event service connection failure

Windows

UNIX

M

11

"REUSELOGON"=#1

The method used to start the logon-session process

Windows

M

12

"LOGONSHMAX"=#1

The number of sessions that can share logon resources

Windows

M

13

[{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER]#2

"MAXSESSION"=

The maximum number of simultaneous sessions

Windows

UNIX

M

14

"AJSINETDLOGSIZE"=

The size of the ajsinetd internal log

Windows

UNIX

M

15

"MONLOG"=#1

Whether messages related to connections of JP1/AJS3 - View to and disconnections from the scheduler service are to be output to the scheduler log

Windows

UNIX

M

16

"MONSYSLOG"=

In Windows:

Whether messages related to starting and terminating the ajsinetd processes, and connecting and disconnecting JP1/AJS3 - View are to be output to the Windows event log and integrated trace log

In UNIX:

Whether messages related to starting and terminating the ajsinetd processes, and connecting and disconnecting JP1/AJS3 - View are to be output to the syslog and integrated trace log

Windows

UNIX

M

17

"AUTHLOG"=

Whether messages related to user authentication are to be output to the scheduler log

Windows

UNIX

M

18

"AUTHSYSLOG"=

In Windows:

Whether messages related to user authentication are to be output to the Windows event log and integrated trace log

In UNIX:

Whether messages related to user authentication are to be output to the syslog and integrated trace log

Windows

UNIX

M

19

"HIDEOTHERLHOST"=

The scheduler services to be displayed for a login to JP1/AJS3 - View

Windows

UNIX

M

20

"CONRESTRICTLOG"=

Whether messages related to restricting connection sources are to be output to the scheduler log

Windows

UNIX

M

21

"CONRESTRICTSYSLOG"=

In Windows:

Whether messages related to restricting connection sources are to be output to the Windows event log

In UNIX:

Whether messages related to restricting connection sources are to be output to the syslog

Windows

UNIX

M

22

"HIDEOTHERSERVICE"=

Whether to prevent the display of a scheduler service without access permissions in JP1/AJS3 - View

Windows

UNIX

M

23

"CHANGEPASSWORD"=

Whether changing of the JP1 user password is to be permitted in JP1/AJS3 - View

Windows

UNIX

M

24

"CHANGEPWDLOG"=

Whether messages related to changing of the password are to be output if the JP1 user password change function is enabled in JP1/AJS3 - View

Windows

UNIX

M

25

[{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name]#2

"AUTORESTARTCOUNT"=

The number of attempts to be made to restart the scheduler service

Windows

UNIX

M

26

"RESTARTCLRTIME"=

The period of time until the restart count is cleared

Windows

UNIX

M

27

"MASTERDABEND"=

The action to be taken for a scheduler service error

Windows

UNIX

M

28

"AJSLOGOUTPUTDEST"=

The output-destination setting for the scheduler log file

Windows

UNIX

M

29

"LOGSIZE"=

The size of the scheduler log file (when the file is output by a scheduler service)

Windows

UNIX

M

30

"AJSLOGFILE1"=

The name of scheduler log file 1

Windows

UNIX

M

31

"AJSLOGFILE2"=

The name of scheduler log file 2

Windows

UNIX

M

32

"LOGDLOG"=

Whether log data about starting and terminating the scheduler log output process (ajslogd.exe for Windows and ajslogd for UNIX) is to be output to the scheduler log

Windows

UNIX

M

33

"LOGDSYSLOG"=

In Windows:

Whether log data about starting and terminating the scheduler log output process (ajslogd.exe) is to be output to the Windows event log and the integrated trace log

In UNIX:

Whether log data about starting and terminating the scheduler log output process (ajslogd) is to be output to syslog and the integrated trace log

Windows

UNIX

M

34

"AJSLOGOUTPUTYEAR"=

Whether the year in a scheduler log date is to be output

Windows

UNIX

M

35

"AJSLOGOUTPUTEXTEND"=

The setting for extended output of a scheduler log

Windows

UNIX

M

36

"AUTOSTART"=

Whether a scheduler service is to be started automatically

Windows

UNIX

M

37

"SESSIONTIMEOUT"=

The connection timeout period

Windows

UNIX

M

38

"AJSSERVICEID"=

The scheduler service identification number

Windows

UNIX

M

39

"ISAMWRITEMODE"=

The write mode for updating an ISAM file

Windows

UNIX

M

40

"TABLENAMEPREFIX"=

The table name prefix

Windows

UNIX

M

41

"TABLENAMEPOSTFIX"=

The table ID

Windows

UNIX

M

42

"RDBAUTHID"=

The RDB permission identifier

Windows

UNIX

M

43

"RDBUSER"=

The RDB access user name

Windows

UNIX

M

44

"RDBPASSWORD"=

The RDB user password

Windows

UNIX

M

45

"RDBCHECKINTERVAL"=

The RDB server disconnection detection interval

Windows

UNIX

M

46

"RDBHOST"=

The name of the host at the RDB connection destination

Windows

UNIX

M

47

"RDBPORT"=

RDB port number

Windows

UNIX

M

48

"RDBIPC"=

The method used to communicate with the RDB server

Windows

UNIX

M

49

"RDBSENDMEMSIZE"=

The size of send-data memory for RDB interprocess memory communication

Windows

UNIX

M

50

"RDBRECVMEMSIZE"=

The size of receive-data memory for RDB interprocess memory communication

Windows

UNIX

M

51

"RDBCONNECTWAITTIME"=

The maximum wait time for connection to RDB

Windows

UNIX

M

52

"AJSCHARCODE"=

Character set

Windows

UNIX

M

53

"AJSTMPDIR"=

The name of the directory for temporary files

Windows

UNIX

M

54

"JOBINFDIR"=

The name of the directory for job error information

Windows

UNIX

M

55

"AJSBKUROOT"=

The name of the directory for backup information

Windows

UNIX

M

56

"HNTRLOGLEVEL"=

The level of the messages to be output to the integrated trace log file

Windows

UNIX

M

57

"SYSLOGCODE"=

The character set for outputting a log file

UNIX

M

58

"AJSSYSLOG"=

In Windows:

Whether messages about starting and terminating a scheduler service are to be output to the Windows event log

In UNIX:

Whether messages about starting and terminating a scheduler service are to be output to the syslog file

Windows

UNIX

M

59

"NETSYSLOG"=

In Windows:

Whether messages about starting and ending a jobnet are to be output to the Windows event log

In UNIX:

Whether messages about starting and ending a jobnet are to be output to the syslog file

Windows

UNIX

M

60

"JOBSYSLOG"=

In Windows:

Whether messages about starting and ending a job in a jobnet are to be output to the Windows event log

In UNIX:

Whether messages about starting and ending a job in a jobnet to be output to be output to the syslog file

Windows

UNIX

M

61

"AJSLOG"=

Whether messages about starting and terminating a scheduler service are to be output to the scheduler log file

Windows

UNIX

M

62

"NETLOG"=

Whether messages about starting and ending a jobnet are to be output to the scheduler log file

Windows

UNIX

M

63

"JOBLOG"=

Whether messages about starting and ending a job in a jobnet are to be output to the scheduler log file

Windows

UNIX

M

64

"OPELOG"=

Whether the operation log is to be output

Windows

UNIX

M

65

"LOGINFOALL"=

The output format of logs

Windows

UNIX

M

66

"REFLOG"=

Whether the reference log is to be output

Windows

UNIX

M

67

"LOGHEADER"=

Whether log information is to be output with the process ID added

Windows

UNIX

M

68

"INFOLOG"=

Whether the information log is to be output

Windows

UNIX

M

69

"ROOTJOBNETSCHEDULERANGE"=

The valid range for a root jobnet schedule

Windows

UNIX

M

70

"VIEWSTATUSRANGE"=

The range of the generation information to be used as the basis for acquiring the status via JP1/AJS3 - View

Windows

UNIX

M

71

"STARTMODE"=

The startup mode of a scheduler service

Windows

UNIX

M

72

"OVERSCHEDULE"=

The mode for skipping a jobnet

Windows

UNIX

M

73

"SUPPRESS"=

Whether the execution of a job in the jobnet and a jobnet is suppressed

Windows

UNIX

M

74

"EXECDEFER"=

The repeat method of a jobnet

Windows

UNIX

M

75

"JOBSTATUSPORT"=

The service name of the port used to acquire the job status

Windows

UNIX

M

76

"QUEUELESSMULTIREQ"=

The maximum number of queueless job requests

Windows

UNIX

M

77

"UNITDEFINERELOAD"=

Whether the jobnet definition is updated as soon as it is changed

Windows

UNIX

M

78

"MAXSAVEGEN"=

The maximum number of saved generations

Windows

UNIX

M

79

"AJSPRINTNETSCHPRF"=

The method for handling the schedule rules of nested jobnets

Windows

UNIX

M

80

"SUBMITRETRYINTERVAL"=

The retry interval for submit processing

Windows

UNIX

M

81

"JOBEXECIPCBUFSIZE"=

The size of the job execution information communication buffer for a scheduler service

Windows

UNIX

M

82

"BACKGROUNDLEAVE"=

The method used to delete generations due to cancellation of registration or management of the number of saved generations

Windows

UNIX

M

83

"REQDAGTREQCONNECTTIMEOUT"=

The timeout period for communication with the queueless agent service

Windows

UNIX

M

84

"REQDAGTRECONNECTTIMEOUT"=

The timeout period for recovery processing for communication with a queueless agent service

Windows

UNIX

M

85

"COMMANDEVENT"=

Whether a JP1 event is issued when a command is executed or when an operation is performed from JP1/AJS3 - View

Windows

UNIX

M

86

"NONRELOADHOLDING"=

Whether the definition of a unit on hold is reloaded

Windows

UNIX

M

87

"RJCUSE"=

Whether the execution order of root jobnets spread among different scheduler services is to be controlled by using a jobnet connector

Windows

UNIX

M

88

"JOBDELAYWARNMSG"=

Whether a start message is to be output to the integrated trace log when a scheduler service is started. The start message is generated when the scheduler service is stopped, if a job whose termination delay is monitored in accordance with a period of time required for the execution restarts its operation in the agent.

Windows

UNIX

M

89

"FGRECONLMT"=

The number of reconnection attempts when the flow control process cannot communicate with the scheduler service inter-communication control process

Windows

UNIX

M

90

"SAVEGENTYPE"=

The method for managing the number of logs to keep resulting from the execution of a jobnet for which start conditions are defined

Windows

UNIX

M

91

"AJSDBTYPE"=

The database type

Windows

UNIX

M

92

"AJSDBDIRECTORY"=

The name of the database directory

Windows

UNIX

M

93

"AJSSYSDIR"=

The system folder of each scheduler service

Windows

UNIX

M

94

"AJSLOGDIR"=

The log folder of each scheduler service

Windows

UNIX

M

95

"PREWAITUSE"=

Whether wait conditions are used

Windows

UNIX

M

96

"PREWAITEXTEND"=

Extension of the wait condition function

Windows

UNIX

M

97

"FLBDLOGSIZE"=

The size of an internal log file for a flow control subprocess

Windows

UNIX

M

98

"AGENTPROFMEMSIZE"=

The size of memory that can be used by an execution agent profile

Windows

UNIX

M

99

"UNITPROFMEMSIZE"=

The size of memory that can be used by a unit-attribute profile

Windows

UNIX

M

100

"UNITDEFDIVIDEUPDATE"=

Whether writing to a database during unit operations is to be divided

Windows

UNIX

M

101

"EXECREGISTRATIONNUMBER"=

Whether an execution registration number is treated as a calendar date or an execution date

Windows

UNIX

M

102

"SAVEPLANINFO"=

Whether the temporary-change operation and management functionality are used

Windows

UNIX

M

103

"DEFLENTYPE"=

The number of characters that can be used in a UTF-8 environment

UNIX

M

104

"RERUNSUBORDINATE"=

Whether dependent units are to be re-executed

Windows

UNIX

M

105

"SERVICEMAXSESSION"=

The maximum allowable number of simultaneous sessions for a scheduler service

Windows

UNIX

M

106

"DEFAULTPRIORITY"=

Default execution priority of a job

Windows

UNIX

M

107

"AJSPRINTSORTUNITINF"

The order of relation line information entries to be output when the ajsprint command is executed

Windows

UNIX

M

108

[{JP1_DEFAULT|logical-host-name}\JP1AJS2\GATEWAY]#2

"GWMAXCONNECTION"=

The maximum number of concurrent connections for the scheduler service inter-communication control process (ajsgwd.exe for Windows and ajsgwd for UNIX)

Windows

UNIX

M

109

"GWPROCESSHA"=

Whether the process that manages the scheduler service inter-communication control process (ajsgwmasterd.exe for Windows and ajsgwmasterd for UNIX) terminates when the scheduler service inter-communication control process (ajsgwd.exe in Windows and ajsgwd in UNIX) terminates abnormally

Windows

UNIX

M

110

"GWRESTARTCOUNT"=

The number of times automatic restart is to be attempted when the scheduler service inter-communication control process terminates abnormally

Windows

UNIX

M

Legend:

M: JP1/AJS3 - Manager

#1

Specify this item directly under the [JP1_DEFAULT\JP1AJSMANAGER] key.

#2

Specify JP1_DEFAULT for the physical host. For logical-host-name, specify the name of a logical host.

Important note

You can specify a maximum of 20 scheduler services for the physical and logical hosts on a machine. Specify a service name that is unique among all physical hosts of the local host and all logical hosts. For the service name, specify a character string of no more than 30 bytes. You can use alphanumeric characters and the following symbols:

!, #, $, %, +, - (hyphen), . (period), _ (underscore)

Do not use multi-byte characters, single-byte kana characters, or any symbols other than those above.

If you use an invalid character, the command interpreter will not correctly recognize the scheduler service name when it analyzes the command line, and a failure might occur.

The following describes each of the environment setting parameters.

Parameters that are not described here are used for maintenance purposes. Do not change the values of those parameters.

The default value is used whenever a value is not specified for an environment setting parameter.

2.2.2 Details of the environment setting parameters for scheduler services

(1) "DEFAULTSERVICENAME" = "name-of-default-scheduler-service"

Use this parameter to specify the name of the default scheduler service.

If you have not specified the target scheduler service name (for example, when you execute a command), the system executes processing by using the scheduler service specified in this parameter.

If you execute a command that performs an operation on a unit in an environment in which there are multiple scheduler services, you can omit the -F schedule-service-name option.

Specifiable values

A character string of no more than 30 bytes

Default value

AJSROOT1

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When a process starts

(2) "REMNETSERVICENAME = "name-of-scheduler-service-executing-a-remote-jobnet"

Use this parameter to specify the name of the scheduler service that executes a remote jobnet. If you omit this parameter, the scheduler service cannot execute the remote jobnet even if requested to by another host.

Specifiable values

A character string of no more than 30 bytes

Default value

None

Recommended value

Hitachi does not recommend that remote jobnet operation be used.

When the setting takes effect

Immediately (when a remote jobnet process is running)

(3) "TRACELOGFILE" = "name-of-scheduler-trace-log-file"

Use this parameter to specify the name of the file to which the trace information of the scheduler service is output. Specify a full path name.

If you omit this parameter, trace information is not output.

The system records the scheduler trace information for the physical host and all logical hosts in the file specified in this parameter. Specify the name of a file on the local disk so that trace information will be reliably recorded.

Because the system creates a new file whenever trace information is output, do not specify the name of an existing file.

Specifiable values

A character string of no more than 255 bytes

Default value

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

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

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-Manager-installation-folder\log\tracelog

For Windows Server 2003:

JP1/AJS3-Manager-installation-folder\log\tracelog

In UNIX:

/var/opt/jp1ajs2/log/tracelog

Recommended value

Default value

When the setting takes effect

When a process starts

(4) "VRSHIFT_IMMINT" = "{V5|V6}"

Use this parameter to specify whether to immediately change the jobnet status (that is, whether to immediately stop a jobnet) when you interrupt or kill the root jobnet while a scheduler service is suppressing job execution.

Specifiable values

V5

The jobnet status is changed immediately.

V6

The jobnet status is changed when the suppression of job execution is canceled.

Default value

V5

Recommended value

Default value

When the setting takes effect

When the scheduler service starts

(5) "VRSHIFT_INTRERUN" = "{V5|V6}"

Use this parameter to specify whether to rerun the succeeding units of a nested jobnet that has been interrupted.

Change the parameter value if you do not want to rerun the succeeding units.

In an interrupted nested jobnet, there are some units whose execution has not terminated. Specify V5 to give priority to rerunning the units that follow the interrupted nested jobnet without also executing the units that have not terminated.

This parameter is effective when there is an interrupted nested jobnet before a unit that is to be rerun.

When there is no interrupted nested job ahead of the units to be rerun, but there is a nested job that has ended abnormally, you can rerun the units regardless of the setting of this parameter.

Specifiable values

V5

The units following an interrupted nested jobnet are rerun.

V6

The units following an interrupted nested jobnet are not rerun.

Default value

V6

During a new installation and setup of JP1/AJS3, V5 is set.

Recommended value

V5

When the setting takes effect

When the scheduler service starts

(6) "IPC_TIMEOUT" = dword:remote-communication-timeout-period

Use this parameter to specify the time to wait (timeout) for the originator to start communication with another host.

Customize this parameter if you want to quickly detect, on a fast network connecting hosts, a host that has failed to be activated.

Specify a value other than 0 when you want to set an explicit timeout period rather than depend on the OS timeout period.

For this parameter, the originator's settings are used for execution of the following operations:

When execution of a remote jobnet starts or ends

(Between the originator's JP1/AJS3 - Manager and the destination JP1/AJS3 - Manager)

When you execute operation commands remotely for a job or jobnet

(From the originator's JP1/AJS3 - Manager to the destination JP1/AJS3 - Manager)

When you execute a command from a menu by choosing Management, JP1AJS3 management, and JP1AJS3 status from HP NNM

(From JP1/AJS3 - Manager at the NNM end to the monitored JP1/AJS3 - Manager)

If the originator is unable to start communication when the timeout period specified in this parameter expires, an error occurs.

Specifiable values

A hexadecimal value (in seconds) from 0 to 258 (0 to 600 in decimal)

When dword:00000000 is specified, control is determined by the OS timeout period.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

When a process starts

(7) "IPC_LOCALTIMEOUT" = dword:local-communication-timeout

Use this parameter to specify the time that the system will wait (timeout) for the originator to start communication for interprocess communication related to a JP1/AJS3 scheduler service. Because this parameter is used for internal processing, use only the standard setting.

Specify a value other than 0 when you want to use an explicit timeout period rather than depend on the timeout period of the OS.

If the originator cannot start communication when the timeout period specified for this parameter expires, an error occurs.

Specifiable values

A hexadecimal value (in seconds) from 0 to 3C (0 to 60 in decimal)

When dword:00000000 is specified, control is determined by the OS timeout period.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

When a process starts

(8) "IPCRETRYINTERVAL" = dword:retry-interval

Use this parameter to specify the retry interval when a communication error occurs.

Change this parameter to a value appropriate for the communication error status. If you change the parameter value, you also have to change the IPCRETRYCOUNT environment setting parameter value (retry count).

Each time a retry occurs, the specified value is incremented.

Specifiable values

A hexadecimal value (in seconds) from 0 to A (0 to 10 in decimal)

Default value

dword:00000001 (1 in decimal)

Recommended value

Default value

When the setting takes effect

When a process starts

(9) "IPCRETRYCOUNT" = dword:retry-count

Use this parameter to specify the number of retries attempted when a communication error occurs.

Change this parameter to a value appropriate for the communication error status. If you change this parameter value, you also have to change the IPCRETRYINTERVAL environment setting parameter value (retry interval).

When there is a heavy concentration of scheduler service interprocess communication, a temporary communication error might occur. Specify a value larger than the default value if you will simultaneously start multiple scheduler services or execute many JP1/AJS3 commands at one time.

Specifiable values

A hexadecimal value from 0 to 64 (0 to 100 in decimal)

Default value

dword:00000003 (3 in decimal)

Recommended value

Default value or a value larger than the default value, depending on operating requirements

When the setting takes effect

When a process starts

(10) "EVENTRETRY" = "{yes|no}"

Use this parameter to specify whether to reconnect to an event service for which a connection error has occurred.

Change this parameter to enable reconnection each time the system outputs a JP1 event.

Use the default value (no) if the system does not reference JP1 events (from 4100 to 4142) output from the scheduler service.

Specifiable values

yes

An attempt to reconnect to the event service is made the next time an event is output.

If reconnection to the event service is successful, the JP1 event is output. However, note that, because the event service is not reconnected, the JP1 event for the error that occurs is not output (the failed event is not registered as a JP1 event).

If you specify yes, this function tries to connect to the event service for each event output until reconnection to the event service is successful. Therefore, the job performance might be adversely affected compared to when no is specified. Specify yes if reconnection to the event service has greater priority than performance.

If you specify yes, the system outputs an error message (KAVS0863-E Interprocess communication failed.:maintenance-information-1, maintenance-information-2, maintenance-information-3) each time an error occurs on the connection with an event service. If the connection to the event service is not restored quickly, a large number of log messages will be output.

no

JP1 events are not output after an event service connection error occurs.

The event service will be connected again when the JP1/AJS3 service is restarted.

Default value

no

Recommended value

yes

When the setting takes effect

Immediately

(11) "REUSELOGON" = {yes|no}"

Use this parameter to select the method that will be used to start the logon session process that is executed after a logon using the OS user account.

Specify yes when multiple simultaneous sessions are to be mapped to the same OS user and then run, and a lack of desktop heap area prevents the process from starting.

Reuse the logon resources for starting the following processes:

Connection of JP1/AJS3 - View

Running a command remotely

Running a remote jobnet

Operations from JP1/AJS3 - Definition Assistant

Specifiable values

yes

Logon information is saved and reused for the sessions to be mapped to the same OS user.

Specifying yes enables these sessions to share desktop heaps, and helps reduce the consumption of the desktop heap area.

If there are multiple simultaneous sessions to be mapped to the same OS user, and the processes cannot be started because desktop heap area is insufficient, specify yes. If you specify yes and change the OS user information, you must restart the ajsinetd process.

no

Logon information is not reused for the sessions to be mapped to the same OS user.

Default value

no

Recommended value

yes

When the setting takes effect

When the ajsinetd process starts.

For details about how to start and stop ajsinetd process individually, see jajs_hstd in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1 and jajs_hstd_stop in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

(12) "LOGONSHMAX" = dword:number-of-logon-sessions-sharing-logon-resources

When reusing a logon, you need to specify the number of sessions that are allowed to share the logon information.

A new desktop heap is assigned if the number of sessions for the same OS user exceeds the value specified in this parameter.

You can specify this parameter only if you specify yes for the REUSELOGON environment setting parameter.

Specifiable values

A hexadecimal value from 1 to 80 (1 to 128 in decimal)

Default value

dword:00000032 (50 in decimal)

Recommended value

Default value

When the setting takes effect

When the ajsinetd process starts.

For details about how to start and stop ajsinetd process individually, see jajs_hstd in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1 and jajs_hstd_stop in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

Supplementary note

How to estimate the number of logon sessions that share the logon resources:

If the desktop heap area is running low, change the number of logon sessions that can share the logon resources to a value in the range indicated below.

For the size of the desktop heap to be assigned to non-interactive processes, see the OS documentation.

Number-of-logon-sessions-sharing-the-logon-resources < size-of-the-desktop-heap-to-be-assigned-to-a-non-interactive-processes (in kilobytes)/10 (in kilobytes)

(13) "MAXSESSION" = dword:maximum-number-of-simultaneous-sessions

Use this parameter to specify the maximum allowable number of simultaneous sessions for JP1/AJS3 - View. If the specified number has been reached and you attempt to connect from JP1/AJS3 - View, the attempt will fail.

If you select scheduler services in the tree area of the JP1/AJS3 - View window, a connection is established for each scheduler service you select. Accordingly, in an environment in which there are multiple scheduler services, the maximum number of connections that will be established is number-of-scheduler-services x number-of-JP1/AJS3 - View-instances.

If the maximum number of JP1/AJS3 - View connections exceeds 50, specify a value based on the maximum number. Also, when you want to restrict JP1/AJS3 - View connections because of resource limitations on the machine, change the value of each host to a smaller one appropriate for operation of the physical host or logical host. You do not need to change the value in any other case.

Specify the environment setting parameter for restricting the number of connections on each host. To restrict the maximum allowable number of simultaneous sessions for JP1/AJS3 - View for each scheduler service rather than by host, use the SERVICEMAXSESSION environment setting parameter. If you use both the MAXSESSION environment setting parameter and the SERVICEMAXSESSION environment setting parameter, note the following:

Make sure that the setting value of the SERVICEMAXSESSION environment setting parameter does not exceed the setting value of the MAXSESSION environment setting parameter.

When there are multiple scheduler services, make sure that the total of the setting values of the SERVICEMAXSESSION environment setting parameter for all scheduler services does not exceed the setting value of the MAXSESSION environment setting parameter.

For example, if scheduler services AJSROOT1 and AJSROOT2 have been created, the setting value of the SERVICEMAXSESSION environment setting parameter for AJSROOT1 is 25, and the setting value of the SERVICEMAXSESSION environment setting parameter for AJSROOT2 is 25, you must specify a value of 50 or larger for the MAXSESSION environment setting parameter.

Specifiable values

A hexadecimal value from 0 to 80 (0 to 128 in decimal)

Default value

dword:00000032 (50 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When any scheduler service on an applicable host starts or stops

Cautionary note

If the maximum allowable number of simultaneous sessions has been exceeded, a message (KAVV452-E) is displayed in the JP1/AJS3 - View window (Summary Monitor window) for each monitored unit that is unable to establish a connection. This message is displayed whenever the window is updated.

(14) "AJSINETDLOGSIZE" = dword:size-of-ajsinetd-internal-log

Use this parameter to specify the size of the ajsinetd internal log.

Specifiable values

00000000 or a value in kilobytes from 00000004 to 001E8480 in hexadecimal (in decimal 0 or a value from 4 to 2,000,000)

If you specify dword:00000000, the system does not create a log file.

If you omit this parameter, dword:00000080 is assumed. If the specified value is invalid, dword:00000000 is assumed.

Default value

dword:00000080 (128 in decimal)

Recommended value

Default value

When the setting takes effect

When the ajsinetd process starts.

For details about how to start or stop ajsinetd processes individually, see jajs_hstd in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1 and jajs_hstd_stop in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

(15) "MONLOG" = "{none|all}"

Use this parameter to specify whether messages related to connections of the following program to the scheduler service and disconnections from it are to be output to the scheduler log:

JP1/AJS3 - View

Change the parameter value if you want to output to the scheduler log the status of the connections established by this program to the scheduler service.

Specifiable values

none

Messages about the connections of this program to and disconnections from the scheduler service are not output.

all

Messages related to the connections of this program to and disconnections from the scheduler service are output.

The following messages are output:

JP1/AJS3 - View connection message (KAVS0534-I)

JP1/AJS3 - View disconnection message (KAVS0535-I)

Default value

none

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts or terminates

(16) "MONSYSLOG" = "{none|all}"

Use this parameter to specify whether to output the following messages to the log:

Start and stop messages related to the ajsinetd process

Acceptance processing start and end messages related to the ajsinetd process

The messages are output to the following logs.

In Windows:

The Windows event log and integrated trace log

In UNIX:

The syslog and integrated trace log

Change the parameter value if you do not need to check the status of connections established by JP1/AJS3 - View in the Windows event log or syslog. If you change this parameter and an error occurs, you will not be able to check the status of connections for JP1/AJS3 - View.

Specifiable values

none

Messages related to starting and terminating the ajsinetd process or to connecting and disconnecting JP1/AJS3 - View are not output.

all

The following messages are output:

ajsinetd process start message (KAVS0530-I)

ajsinetd process stop message (KAVS0531-I)

Acceptance processing start message for the ajsinetd process (KAVS0532-I)

Acceptance processing end message for the ajsinetd process (KAVS0533-I)

JP1/AJS3 - View connection message (KAVS0534-I)

JP1/AJS3 - View disconnection message (KAVS0535-I)

Default value

none

During a new installation and setup of JP1/AJS3, all is set.

Recommended value

all

When the setting takes effect

Immediately (For messages related to connection and disconnection of JP1/AJS3 - View, the setting takes effect the next time you log in to JP1/AJS3 - View after the scheduler service starts.)

(17) "AUTHLOG" = "{none|all}"

Use this parameter to specify whether messages related to user authentication are to be output to the scheduler log for each host.

Specifiable values

none

Messages related to user authentication are not output.

all

Messages related to user authentication are output.

The log message (KAVS1009-W) generated when authentication of the ajsinetd process is rejected is output to the scheduler log for each host.

Default value

none

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

Immediately (the next time a user authentication request is received)

(18) "AUTHSYSLOG" = "{none|all}"

Use this parameter to specify whether to output messages related to user authentication to the following file or logs:

In Windows:

The Windows event log and the integrated trace log

In UNIX:

The syslog file and the integrated trace log

Specifiable values

none

Messages related to user authentication are not output.

all

Messages related to user authentication are output.

In Windows:

The log message (KAVS1009-W) generated when authentication of the ajsinetd process is rejected is output to the Windows event log and the integrated trace log.

In UNIX:

The log message (KAVS1009-W) generated when authentication of the ajsinetd process is rejected is output to the syslog file and the integrated trace log.

Default value

none

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

Immediately (the next time a user authentication request is received)

(19) "HIDEOTHERLHOST" = "{yes|no}"

Use this parameter to specify the range of the scheduler services to be displayed when you log on to a host from JP1/AJS3 - View in an environment in which JP1/AJS3 services has been established for logical hosts.

Specifiable values

yes

Only the scheduler service corresponding to the specified host name is displayed when you log on to a host from JP1/AJS3 - View.

no

All defined scheduler services established on the host are displayed if you log on as a JP1 user mapped to the OS user with superuser permission or the Administrators permission.

If you log on as any other type of user, all defined scheduler services established on hosts that belong to the same user authentication block as the logged-on host are displayed. If any scheduler service other than the one for the logged-on logical host is failed over and does not exist on the logged-on physical host, do not access that scheduler service.

Also, if the ajsinetd process is not running on the connection-destination host, you cannot access the scheduler service on that host.

Specify this value if you want to access the scheduler services on all logical hosts in the JP1/AJS3 - Manager to which you log on from JP1/AJS3 - View.

Default value

yes

Recommended value

Default value

When the setting takes effect

Immediately (at the next login to JP1/AJS3 - View)

(20) "CONRESTRICTLOG" = "{none|all}"

Use this parameter to specify whether messages related to restricting connection sources are to be output to the scheduler log of each host.

Specifiable values

none

Messages related to restricting connection sources are not output.

all

All messages related to restricting connection sources are output.

An entry (KAVS8040-E) reporting the rejection of a connection attempt due to the restriction on connection sources in the ajsinetd process and ajscdinetd process is output to the scheduler log of the applicable host.

Default value

none

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the JP1/AJS3 service starts

(21) "CONRESTRICTSYSLOG" = "{none|all}"

Use this parameter to specify whether messages related to restricting connection sources are to be output to the following log file.

In Windows:

Windows event log

In Unix:

syslog

Specifiable values

none

Messages related to restricting connection sources are not output.

all

Messages related to restricting connection sources are output.

An entry (KAVS8040-E) reporting the rejection of a connection attempt due to the restriction on connection sources in the ajsinetd process and ajscdinetd process is output to the Windows event log or syslog.

Default value

none

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the JP1/AJS3 service starts

(22) "HIDEOTHERSERVICE" = "{yes|no}"

Use this parameter to specify whether to prevent the display of a scheduler service without access permissions in JP1/AJS3 - View (that is, whether the scheduler service reference restriction function is enabled or disabled).

Specifiable values

yes

The scheduler service reference restriction function is enabled. Scheduler services without permissions are not displayed in JP1/AJS3 - View.

no

The scheduler service reference restriction function is disabled. Scheduler services without access permissions are displayed in JP1/AJS3 - View.

Default value

no

Recommended value

no

When the setting takes effect

Immediately (at the next login to JP1/AJS3 - View)

Supplementary note

If you change the access permissions of a scheduler service, restart JP1/AJS3 - View. The change is reflected in JP1/AJS3 - View.

(23) "CHANGEPASSWORD" = "{yes|no}"

Use this parameter to permit changing JP1 user passwords.

When this functionality is enabled, you can change JP1 user passwords by selecting Options and then Change Password in the connected JP1/AJS3 - View.

Because you must meet the conditions for using this functionality, see the cautionary notes in 6.6.4 Settings for permitting changing JP1 user passwords in JP1/AJS3 - View in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.7.3 Settings for permitting changing JP1 user passwords in JP1/AJS3 - View in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX), and then decide whether the functionality can be enabled beforehand.

Specifiable values

yes

Changing JP1 user passwords in JP1/AJS3 - View is permitted.

no

Changing JP1 user passwords in JP1/AJS3 - View is not permitted.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the JP1/AJS3 service starts

(24) "CHANGEPWDLOG" = "{none|all}"

Use this parameter to specify whether messages related to changing JP1 user passwords are to be output when the JP1 user password change function is enabled in JP1/AJS3 - View (when the CHANGEPASSWORD environment setting parameter is set to yes).

Specifiable values

none

Messages related to changing JP1 user passwords are not output.

all

The following messages related to changing JP1 user passwords are output:

KAVS1010-I (The password was changed successfully)

KAVS1011-E (The password could not be changed)

KAVS1015-I (Changing of the password is now starting)

Default value

all

Recommended value

all

When the setting takes effect

When the JP1/AJS3 service starts

(25) "AUTORESTARTCOUNT" = dword:scheduler-service-restart-count

Use this parameter to specify the number of times that a scheduler service process will be automatically restarted if it has terminated abnormally.

Specify 0 to immediately stop job execution in JP1/AJS3 when a scheduler service has terminated abnormally. In addition, if you monitor the scheduler service status by executing the jajs_spmd_status command or a process, specify 0 for this parameter and yes for the MASTERDABEND environment setting parameter.

Note that this parameter is valid only in compatible ISAM configuration.

Specifiable values

A hexadecimal value from 0 to 3 (0 to 3 in decimal)

If you specify dword:00000000, the scheduler service is not restarted.

If you specify dword:00000001, the scheduler service is restarted only once.

Default value

dword:00000003 (3 in decimal)

Recommended value

Default value

When the setting takes effect

When the scheduler service starts

(26) "RESTARTCLRTIME" = dword:time-to-clear-the-restart-count

When a process in a scheduler service terminates abnormally and is then restarted, the system assumes normal operation and clears the restart count if the specified time elapses before it stops again. Specify the length of time that the system must operate before the operation is regarded as normal.

When it takes more than three minutes for the scheduler service to start, increase the value if you do not want to restart the system after an abnormal termination.

Note that this parameter is valid only in compatible ISAM configuration.

Specifiable values

A hexadecimal value (in seconds) from B4 to 15180 (180 to 86,400 in decimal)

Default value

dword:000000B4 (180 in decimal)

Recommended value

Default value

When the setting takes effect

When the scheduler service starts

(27) "MASTERDABEND" = "{yes|no}"

Use this parameter to specify whether to stop all scheduler services and terminate the ajsmasterd process abnormally if a scheduler service terminates abnormally.

Note that this parameter is valid only in compatible ISAM configuration. In a standard configuration, this parameter is always no.

Specifiable values

yes

All scheduler services terminate, and the ajsmasterd process terminates abnormally.

Specify this value to monitor the operating status of JP1/AJS3 by executing the jajs_spmd_status command.

When you do this, you cannot restart the scheduler service by executing the jajs_spmd command with the -n jajs_schd option specified. To start the scheduler service, restart the JP1/AJS3 service.

no

Not all the scheduler services terminate.

If you specify this value, you can restart the scheduler service by executing the jajs_spmd command with the -n jajs_schd option specified.

Default value

no

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

- In Windows:

On a logical host in a cluster configuration, if a scheduler service on the logical host terminates abnormally, the system performs the following operation:

If yes is specified, the JP1/AJS3 service on the logical host on which the scheduler service terminated, terminates abnormally.

If no is specified, the JP1/AJS3 service on the logical host on which the scheduler service terminated abnormally, does not terminate.

- In UNIX:

If a scheduler service in the JP1/AJS3 service that was started by executing the jajs_spmd command with the -HA option specified terminates abnormally, the system performs the following operation:

If yes is specified, the JP1/AJS3 service started by the jajs_spmd command with the -HA option specified terminates.

If no is specified, the JP1/AJS3 service started by executing the jajs_spmd command with the -HA option specified does not terminate.

Note that even if yes is specified, the system restarts the scheduler service only the number of times specified for the AUTORESTARTCOUNT environment setting parameter. If the scheduler service terminates abnormally after being restarted the specified number of times, all scheduler services terminate.

(28) "AJSLOGOUTPUTDEST" = "{schedule|host}"

Use this parameter to specify whether to output the scheduler log by scheduler service or by host. Specify this parameter for each scheduler service.

Specifiable values

schedule

The scheduler log for a scheduler service is output to the files specified in the AJSLOGFILE1 and AJSLOGFILE2 environment setting parameters.

For each scheduler service, you can estimate and check the log size, and switch and back up logs.

host

The scheduler log for a host is output to the file specified in the HOSTLOGFILE1 and HOSTLOGFILE2 environment setting parameters.

Although it is necessary to estimate and check the file size, and to switch and back up logs for each host, the system can log the commands that are executed while the scheduler service is not running.

Default value

schedule

Recommended value

Default value

When the setting takes effect

When the scheduler service starts

(29) "LOGSIZE" = dword:size-of-the-scheduler-log-file (when outputting the scheduler log for a scheduler service)

Specify the size of the file to which the system outputs the scheduler log file for a scheduler service.

Because this log is used to check the execution status of a job or jobnet, specify a size that is sufficient for storing the log data for at least one day.

For details about how to estimate the size of a scheduler log file, see 3.4.1 Estimating the size of scheduler log files in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

Specifiable values

In Windows:

0 or a hexadecimal value (in kilobytes) from 4 to 1E8480 (0 or a value from 4 to 2,000,000 in decimal)

In UNIX:

A hexadecimal value (in kilobytes) from 0 to 1E8480 (0 to 2,000,000 in decimal)

If you specify dword:00000000, the system does not create a log file.

Default value

In Windows:

dword:00001400 (5,120 in decimal)

In UNIX:

dword:00000000 (0 in decimal)

During a new installation and setup of JP1/AJS3, dword:00002800 (10,240 in decimal) is set.

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts or terminates

(30) "AJSLOGFILE1" = "name-of-scheduler-log-file-1"

Use this parameter to specify the name of a log file. Specify a full path name.

Specify a file name different from the name of scheduler log file 2.

When the amount of information written to this file becomes equal to or greater than the specified size, the system writes subsequent information to log file 2.

When you use multiple scheduler services, specify a unique file name for each scheduler service.

In UNIX, when you use the scheduler log file, you cannot omit this parameter.

Specifiable values

A character string of no more than 255 bytes

Default value

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\schedule\schedule-service-name\ajs-log1.log

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-Manager-installation-folder\log\schedule\scheduler-service-name\ajs-log1.log

For Windows Server 2003:

JP1/AJS3-Manager-installation-folder\log\schedule\scheduler-service-name\ajs-log1.log

In UNIX:

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

Recommended value

The value set at the time of installation or setup.

When the setting takes effect

When the scheduler service starts or terminates

(31) "AJSLOGFILE2" = "name-of-scheduler-log-file-2"

Use this parameter to specify the name of a log file. Specify a full path name.

When you use multiple scheduler services, specify a unique file name for each scheduler service.

In UNIX, when you use the scheduler log file, you cannot omit this parameter.

Specifiable values

A character string of no more than 255 bytes

Default value

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\schedule\scheduler-service-name\ajs-log2.log

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-Manager-installation-folder\log\schedule\scheduler-service-name\ajs-log2.log

For Windows Server 2003:

JP1/AJS3-Manager-installation-folder\log\schedule\scheduler-service-name\ajs-log2.log

In UNIX:

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

Recommended value

The value set at the time of installation or setup.

When the setting takes effect

When the scheduler service starts or terminates

(32) "LOGDLOG" = "{none|all}"

Use this parameter to specify whether to output the messages related to starting and terminating the scheduler log output process (ajslogd.exe for Windows and ajslogd for UNIX) to the scheduler log.

Specifiable values

none

The messages related to starting and terminating the scheduler log output process is not output.

all

The messages related to starting (KAVS0220-I) and terminating (KAVS0221-I) the scheduler log output process, are output.

Default value

none

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts or terminates

(33) "LOGDSYSLOG" = "{none|all}"

In Windows:

Use this parameter to specify whether to output the messages related to starting and terminating the scheduler log output process (ajslogd.exe) to the Windows event log and integrated trace log.

In UNIX:

Use this parameter to specify whether to output the messages related to starting and terminating the scheduler log output process (ajslogd) to syslog and integrated trace log.

Specifiable values

none

The messages related to starting and terminating the scheduler log output process is not output.

all

The messages related to starting (KAVS0220-I) and terminating (KAVS0221-I) the scheduler log output process, are output.

Default value

none

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts or terminates

(34) "AJSLOGOUTPUTYEAR" = "{yes|no}"

Use this parameter to specify whether to output the year as part of the scheduler log date.

Change the parameter value if you use the year to manage scheduler log information.

Specifiable values

yes

The year is output. The system outputs the year, month, and day in the date section.

no

The year is not output. The system outputs only the month and day in the date section.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts or terminates

(35) "AJSLOGOUTPUTEXTEND" = "{yes|no}"

Use this parameter to specify the output format when the system outputs the execution log or operation log of units to the scheduler log.

Change the parameter value if you want to output the operation user type, requester information, and detailed options for command operation to the scheduler log.

If you specify yes for this parameter, the system outputs the detailed information to the scheduler log when you execute or manipulate a unit. By using this log, you can verify the validity of an operation. For details about this function and information that can be added, see C.1 Functions for verifying the legitimacy of JP1/AJS3 operations in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

Specifying yes for this parameter increases the amount of information that will be output to the scheduler log. See 3.4.1 Estimating the size of scheduler log files in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide and take into consideration all the factors in changing the value of the LOGSIZE environment setting parameter that specifies the size of a scheduler log. For details about the LOGSIZE environment setting parameter, see (29) LOGSIZE.

The conditions governing when a log is output and the information to be added when a log is output vary according to the type of log. For details, see C.1 Log entries output by the scheduler services in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

Specifiable values

yes

In addition to the information that is output when no is selected, detailed information, including operation user type, is also output.

The following information is added to the message:

Operation user type

Requester host IP address

Requester identification information

Options for command operations

Unit name

no

No additional detailed information, such as operation user information, is output.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts or terminates

(36) "AUTOSTART" = "{yes|no}"

Use this parameter to specify whether to automatically start a scheduler service when JP1/AJS3 - Manager is started.

Specifiable values

yes

A scheduler service is automatically started when JP1/AJS3 - Manager starts.

no

Scheduler services are not automatically started when JP1/AJS3 - Manager starts.

Specify no when there are scheduler services that do not need to be started.

If you specify no, some processes do not start because scheduler services do not start when JP1/AJS3 - Manager starts. Accordingly, the execution result of the jajs_spmd_status command differs from when yes is specified.

Standard configuration:

The jajs_schd process and its subprocesses do not start. If you want to start a specific scheduler service, use the jajs_spmd command with the -n option specified or the ajsstart command.

Compatible ISAM configuration:

The execution result of the jajs_spmd_status command is the same as when yes is specified. If you want to start a specific scheduler service, use the ajsstart command.

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

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

Default value

yes

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After JP1/AJS3 is restarted

(37) "SESSIONTIMEOUT" = dword:connection-timeout-period

Specify how many minutes it is necessary to wait after the last communication for disconnection from JP1/AJS3 - View.

If the system is unable to communicate with JP1/AJS3 - View for the specified period of time since the last communication, the system assumes that JP1/AJS3 - View has failed and disconnects from JP1/AJS3 - View.

Specifiable values

A hexadecimal value (in minutes) from 1 to 78 (1 to 120 in decimal)

Default value

dword:00000078 (120 in decimal)

Recommended value

Default value

When the setting takes effect

On connection to JP1/AJS3 - View after a scheduler service has started or terminated

(38) "AJSSERVICEID" = dword:scheduler-service-id-number

Use this parameter to specify a scheduler service ID number.

Specify an ID number that is unique among all the physical hosts of the local host and all the logical hosts.

Because the system uses this ID number internally to identify a scheduler service when, for example, a temporary file name or key for interprocess communication is used, do not change the ID number after it has been specified. If you change the ID number, you will need to cold-start the scheduler service.

Specifiable values

A hexadecimal value from 1 to 14 (1 to 20 in decimal)

Default value

None

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

(39) "ISAMWRITEMODE" = "{flush|noflush|sync}"

Use this parameter to specify whether to permit synchronous writing when an ISAM file is updated.

Select the writing method appropriate for performance, reliability, and method of operation when an ISAM file is used.

Specifiable values

flush

Data in the buffer in memory is written to a disk each time a write operation finishes.

noflush

Data is written to a disk in response to OS buffering. There is no synchronization with JP1/AJS3 processing.

sync

Synchronous writing is always performed when a file is updated. This writing mode improves reliability, but degrades performance. Note that synchronous writing is performed only for the status management files of jobs and jobnets. The system uses flush mode to write data to files that store unit definition information.

Default value

flush

Recommended value

For a physical host:

flush (flush)

For a cluster configuration:

sync (synchronization)

When the setting takes effect

When the scheduler service starts or terminates

(40) "TABLENAMEPREFIX" = "table-name-prefix"

Use this parameter to specify a character string that will be prefixed to the name of a table that is stored in the scheduler service schema.

This environment setting parameter is set automatically during installation and setup. You do not need to change the value of this parameter.

Specifiable values

An alphanumeric character string of no more than 4 bytes

This value is not case sensitive, and all characters are treated as upper-case characters.

Default value

AJS

Recommended value

A value set in JP1/AJS3 - Manager

When the setting takes effect

When the scheduler service starts or terminates

If you change this parameter, you must re-create the scheduler database.

(41) "TABLENAMEPOSTFIX" = "table-ID"

Use this parameter to specify a character string that will be suffixed to the name of a table that is stored in the scheduler service schema.

Usually, you do not need to change this value.

Specifiable values

An alphanumeric character string of no more than 4 bytes

This value is not case sensitive, and all the characters are treated as upper-case characters.

Default value

None

Recommended value

Set the value appropriate for the operating environment.

A value set in JP1/AJS3 - Manager

When the setting takes effect

When the scheduler service starts or terminates

If you change this parameter, you must re-create the scheduler database.

(42) "RDBAUTHID" = "RDB-permission-identifier"

Use this parameter to specify a permission identifier to be used for setting up and operating the database.

Usually, you do not need to change this value.

Specifiable values

A value of no more than 8 bytes must be specified if an embedded database is used (when EmbedDB is specified for the AJSDBTYPE environment setting parameter).

Default value

None

Recommended value

A value set in JP1/AJS3 - Manager

When the setting takes effect

When the scheduler service starts or terminates

(43) "RDBUSER" = "RDB-access-user-name"

Use this value to define the name of the user who accesses the database.

Usually, you do not need to change this value.

Specifiable values

A value of no more than 8 bytes must be specified when you use an embedded database (when EmbedDB is specified for the AJSDBTYPE environment setting parameter).

Default value

None

Recommended value

A value set in JP1/AJS3 - Manager

When the setting takes effect

When the scheduler service starts or terminates

(44) "RDBPASSWORD" = "RDB-user-password"

Use this parameter to define a password for enabling access to the database.

Usually, you do not need to change this value.

Specifiable values

A value of no more than 30 bytes must be specified if an embedded database is used (when EmbedDB is specified for the AJSDBTYPE environment setting parameter).

The passwords for an embedded database are not case sensitive. To distinguish between upper-case and lower-case characters, enclose the password character string in exclamation marks (!).

Example:

"RDBPASSWORD"="!password!"

Default value

Not specified

Recommended value

Default value

When the setting takes effect

When the scheduler service starts or terminates

(45) "RDBCHECKINTERVAL" = dword:whether-to-use-the-RDB-server-connection-check-function

Use this parameter when you use the function for automatically stopping the scheduler service when the scheduler service is no longer able to continue processing for a reason such as a database server stoppage. You use this function to check the connection of the scheduler service to the database server and to automatically stop the scheduler service if it has been disconnected from the database server.

Usually, you do not need to change this parameter.

Specifiable values

A hexadecimal value from 1 to 15180 (1 to 86,400 in decimal)

If you specify a value outside this range, the function is disabled. If the function is disabled, the connection to the database server is not checked, and the scheduler service does not terminate automatically.

Default value

dword:00000000 (0 in decimal)

During a new installation and setup of JP1/AJS3, dword:0000012C (300 in decimal) is set.

Recommended value

dword:0000012C (300 in decimal)

When the setting takes effect

When the scheduler service starts

(46) "RDBHOST" = "RDB-connection-destination-host-name"

Use this parameter to specify the name of the host on which the database is set up.

Usually, you do not need to change this value.

Specifiable values

A character string of no more than 511 bytes

Default value

None

Recommended value

The value set in JP1/AJS3 - Manager

When the setting takes effect

When the scheduler service starts or terminates

(47) "RDBPORT" = dword:RDB-connection-port-number

Use this parameter to specify the port number for the RDB connection.

Usually, you do not need to change this value.

Specifiable values

A hexadecimal value from 1389 to FFFF (5,001 to 65,535 in decimal) if an embedded database is used (when EmbedDB is specified for the AJSDBTYPE environment setting parameter).

Default value

None

Recommended value

The value set in JP1/AJS3 - Manager

When the setting takes effect

When the scheduler service starts or terminates

(48) "RDBIPC" = "{MEMORY|DEFAULT}"

Use this parameter to specify the method for connecting to the RDB server.

Usually, you do not need to change this value.

Specifiable values

MEMORY

Interprocess memory communication is used for communication with the RDB server.

DEFAULT

TCP/IP communication is used for communication with the RDB server.

Default value

DEFAULT

Recommended value

The value set in JP1/AJS3 - Manager

When the setting takes effect

When the scheduler service starts or terminates

(49) "RDBSENDMEMSIZE" = dword:size-of-data-send-memory-for-RDB-interprocess-memory-communication

Use this parameter to specify the amount of memory used to store send data in interprocess memory communication with the RDB server.

This parameter is valid only if interprocess memory communication is specified as the method of communication with the RDB server (when MEMORY is specified for the RDBIPC environment setting parameter).

Usually, you do not need to change this value.

Specifiable values

Any hexadecimal value (in kilobytes).

However, to use RDB interprocess memory communication with JP1/AJS3, specify a value of dword:00000008 (8 in decimal) or greater.

If you specify 0, the default RDB value is used.

Default value

Default RDB value

Recommended value

The value set in JP1/AJS3 - Manager

When the setting takes effect

When the scheduler service starts or terminates

(50) "RDBRECVMEMSIZE" = dword:size-of-data-receive-memory-for-RDB-interprocess-memory-communication

Use this parameter to specify the amount of memory used to store receive data in interprocess memory communication with RDB.

This parameter is valid only if you specify interprocess memory communication as the method of communication with the RDB server (when MEMORY is specified for the RDBIPC environment setting parameter).

Usually, you do not need to change this value.

Specifiable values

Any hexadecimal value (in kilobytes).

However, to use the RDB interprocess memory communication with JP1/AJS3, specify a value of dword:00000040 (64 in decimal) or greater.

If you specify 0, the default RDB value is used.

Default value

Default RDB value

Recommended value

The value set in JP1/AJS3 - Manager

When the setting takes effect

When the scheduler service starts or terminates

(51) "RDBCONNECTWAITTIME" = dword:maximum-wait-time-for-connection-to-RDB

Use this parameter to specify the maximum wait time to wait for connection to the RDB server.

Usually, you do not need to change this value.

Specifiable values

A hexadecimal value (in minutes) from 0 to 3C (0 to 60 in decimal)

If you specify 0, the RDB connection wait function is disabled.

Default value

dword:00000001 (1 in decimal)

Recommended value

The value set in JP1/AJS3 - Manager

When the setting takes effect

When the scheduler service starts

(52) "AJSCHARCODE" = "{C|SJIS|EUC|UTF-8}"

Use this parameter to specify the character set for job definition information recorded in the scheduler service database.

You must specify one of the listed specifiable values.

If the character set does not match the actual data type, the information will not be displayed correctly in JP1/AJS3 - View.

Do not change the character set while a job is being defined or executed in JP1/AJS3. If you want to change the character set during JP1/AJS3 operation, you must first cancel registration of all the jobnets and back up the unit. After changing the character set, restart the JP1/AJS3 - Manager host, restore the unit, and then register the jobnets for execution.

Specifiable values

C

ASCII character set

SJIS

Shift JIS character set

EUC

EUC character set

UTF-8

UTF-8 character set

Note: UTF-8 is enabled for UNIX only.

Default value

None

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts or terminates

(53) "AJSTMPDIR" = "name-of-directory-for-temporary-files"

Use this parameter to specify the name of a directory in which temporary JP1/AJS3 files are created. Specify a full path name.

Determine the name based on the operating environment after estimating the amount of required disk space.

For those users who will be executing and referencing jobnets, set the update permission (rwx for UNIX) for this directory. For those users who will only be referencing jobnets, set the operation permission (rx for UNIX).

If an error occurs during operations, a work file might remain under the specified directory.

For this reason, when no JP1/AJS3 services are running (for example, when the system is started), delete files and maintain the directory regularly. Note, however, if an embedded database is used, do not delete any files with names beginning with pd (such as pderr1.trc and pderr2.trc).

Specifiable values

In Windows:

A character string of no more than 180 bytes

In UNIX:

A character string of no more than 191 bytes

Do not use a semicolon (;) or spaces.

Default value

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

For a physical host:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\tmp\schedule

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For a logical host:

shared-folder\jp1ajs2\tmp\schedule

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

For a physical host:

JP1/AJS3-Manager-installation-folder\tmp\schedule

For a logical host:

shared-folder\jp1ajs2\tmp\schedule

For Windows Server 2003:

For a physical host:

JP1/AJS3-Manager-installation-folder\tmp\schedule

For a logical host:

shared-folder\jp1ajs2\tmp\schedule

In UNIX:

For a physical host:

/var/opt/jp1ajs2/tmp/schedule

For a logical host:

shared-directory/jp1ajs2/tmp/schedule

When you add a scheduler service, create this directory. Make sure that this directory is neither a directory used by another scheduler service set on the local hosts (the physical host and all the logical hosts) nor a subdirectory of that directory.

Recommended value

The value set at the time of installation or setup.

When the setting takes effect

When the scheduler service starts or terminates

(54) "JOBINFDIR" = "job-error-information-directory-name"

Use this parameter to specify the name of the directory to be used to store the standard error output when a job is executed. Specify a full path name.

Determine the name based on the operating environment after estimating the amount of required disk space.

For those users who will be executing and referencing jobnets, set the update permission (rwx for UNIX) for this directory. For those users who will only be referencing jobnets, set the operation permission (rx for UNIX).

Specifiable values

In Windows:

A character string of no more than 180 bytes

In UNIX:

A character string of no more than 191 bytes

Do not use a semicolon (;) or spaces.

Default value

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\jobinf

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-Manager-installation-folder\jobinf

For Windows Server 2003:

JP1/AJS3-Manager-installation-folder\jobinf

In UNIX:

/var/opt/jp1ajs2/jobinf

When you add a scheduler service, create this directory. Make sure that this directory is neither a directory used by another scheduler service set on the local hosts (the physical host and all the logical hosts) nor a subdirectory of that directory.

Recommended value

The value set at the time of installation or setup.

When the setting takes effect

When the scheduler service starts or terminates

(55) "AJSBKUROOT" = "backup-information-directory-name"

Use this parameter to specify the name of the directory to be used to back up units. Specify a full path name.

Determine the name based on the operating environment after estimating the amount of required disk space.

For those users who will be backing up jobnets, set the update permission (rwx for UNIX) for this directory. For those users who will only be restoring jobnets, set the operation permission (rx for UNIX).

Specifiable values

In Windows:

A character string of no more than 180 bytes

In UNIX:

A character string of no more than 191 bytes

Do not use a semicolon (;) or spaces.

Default value

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\backup\schedule

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-Manager-installation-folder\backup\schedule

For Windows Server 2003:

JP1/AJS3-Manager-installation-folder\backup\schedule

In UNIX:

/var/opt/jp1ajs2/backup/schedule

When you add a scheduler service, create this directory.

Recommended value

The value set at the time of installation or setup.

When the setting takes effect

When the scheduler service starts or terminates

(56) "HNTRLOGLEVEL" = "{none|error|warn|info}"

Use this parameter to specify the level of messages that the scheduler service outputs to the integrated trace log.

Specifiable values

none

No messages are output.

error

Error messages are output.

warn

Error and warning messages are output.

info

Error, warning, and information messages are output.

Default value

none

During a new installation and setup of JP1/AJS3, error is set.

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

(57) "SYSLOGCODE" = "{C|LANG-environment-variable-value}"

Use this parameter to specify the language type of the messages that are output by the scheduler service to the syslog file.

Specifiable values

C

The messages are output encoded with the English ASCII character set.

LANG-environment-variable-value (character string other than C)

Operation depends on the settings of the LANG environment variable at the time the scheduler service starts. However, in some systems, a message in the language type corresponding to the LANG environment variable at the time the scheduler service starts might not be output to syslog. In such a system, make sure that this parameter is set to C. Check whether Japanese can be output in the system you are using by executing the logger command to output a message in Japanese and then confirming that the message is correctly output to syslog.

The LANG environment variable value differs depending on the OS.

The following table describes the values that can be specified for the LANG environment variable.

Table 2‒3: Specifiable values of the LANG environment variable

OS

Environment variable value for setting Shift JIS

Environment variable value for setting EUC

Environment variable value for setting UTF-8#1

HP-UX

ja_JP.SJIS

japanese

ja_JP.eucJP

japanese.euc

ja_JP.utf8

Solaris

ja_JP.PCK

ja#2

ja_JP.eucJP#2

ja_JP.UTF-8

AIX

Ja_JP

Ja_JP.IBM-932

ja_JP

ja_JP.IBM-eucJP

JA_JP

JA_JP.UTF-8

Linux

Not available

Not available

ja_JP.UTF-8

ja_JP.utf8

#1

In compatible ISAM configuration, UTF-8 can be used in Linux only.

#2

In Solaris 11, ja and ja_JP.eucJP can be used.

In Solaris 10, only ja can be used.

Default value

C

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(58) "AJSSYSLOG" = "{none|all}"

Use this parameter to specify whether to output messages related to starting and terminating the scheduler service to the Windows event log or syslog file.

Specifiable values

none

The messages related to starting and terminating the scheduler service is not output.

all

The messages related to starting (KAVS0200-I) and terminating (KAVS0201-I) the scheduler service, are output.

Default value

none

Recommended value

Default value

When the setting takes effect

When the scheduler service starts

(59) "NETSYSLOG" = "{none|{abend:warning:hold:startdelay:enddelay:condition:execdeffer:connector:prewait}|all}"

Use this parameter to specify whether to output messages related to starting and ending jobnets to the Windows event log or syslog file.

Specifiable values

none

The messages related to starting and ending jobnet are not output.

abend

The abnormal end message for jobnets (KAVS0262-E) is output.

warning

The end with warning message for jobnets (KAVS0268-W) is output.

hold

The on-hold notification message for jobnets (KAVS0270-I) is output.

startdelay

The delayed-start notification message for jobnets (KAVS0275-I) is output.

enddelay

The delayed-end notification message for jobnets (KAVS0276-I) is output.

condition

The notification messages for jobnets reporting the start of start-condition monitoring (KAVS0240-I) and the end of start-condition monitoring (KAVS0241-I) are output.

execdeffer

The deferred-execution message for jobnets (KAVS0279-E) is output.

connector

Error messages related to the connection between the jobnet connector and the connection destination jobnet (KAVS0243-E, KAVS0244-E, KAVS4700-E to KAVS4708-E, KAVS4711-E to KAVS4716-E, and KAVS4730-E to KAVS4733-E) are output.

prewait

Messages related to the start and end of waiting in accordance with a jobnet wait condition and the messages related to endless waiting (KAVS4950-I, KAVS4955-I, and KAVS4957-E) are output.

all

The following messages related to starting and ending jobnets are output:

Start (KAVS0260-I)

Normal end (KAVS0261-I)

Abnormal end (KAVS0262-E)

End with warning (KAVS0268-W)

On-hold notification (KAVS0270-I)

Delayed start (KAVS0275-I)

Delayed end (KAVS0276-I)

Start/end of start-condition monitoring (KAVS0240-I and KAVS0241-I)

Deferred execution (KAVS0279-E)

All registrations canceled (KAVS0267-I)

Jobnet connector connection error (KAVS0243-E, KAVS0244-E, KAVS4700-E to KAVS4708-E, KAVS4711-E to KAVS4716-E, and KAVS4730-E to KAVS4733-E)

Start or end of waiting in accordance with a wait condition, and endless waiting (KAVS4950-I, KAVS4955-I, and KAVS4957-E)

The KAVS0260-I message (jobnet start) and the KAVS0261-I message (normal end) are output only when all is specified.

Default value

none

Recommended value

Default value

When the setting takes effect

When the scheduler service starts

(60) "JOBSYSLOG" = "{none|{abend:warning:hold:enddelay:prewait:retry}|all}"

Use this parameter to specify whether to output messages related to starting and ending the jobs in a jobnet to the Windows event log or syslog file.

Specifiable values

none

The messages related to starting and ending jobs are not output.

abend

The abnormal end message for jobs (KAVS0265-E) is output.

warning

The end with warning message for jobs (KAVS0269-W) is output.

hold

The on-hold notification message for jobs (KAVS0271-I) is output.

enddelay

The delayed-end message for jobs (KAVS0248-I) is output.

prewait

Messages related to the start and end of waiting in accordance with a job wait condition and the messages related to endless waiting (KAVS4951-I, KAVS4956-I, and KAVS4971-E) are output.

retry

The automatic retry notification messages generated when a job ends abnormally (KAVS4675-I, KAVS4676-I, KAVS4677-E, and KAVS4678-I) are output.

all

The following messages related to starting and ending jobs are output:

Start (KAVS0263-I)

Normal end (KAVS0264-I)

Abnormal end (KAVS0265-E)

Queuing cancellation (KAVS0266-I)

End with warning (KAVS0269-W)

On-hold notification (KAVS0271-I)

Delayed end (KAVS0248-I)

Start or end of waiting in accordance with a wait condition, and endless waiting (KAVS4951-I, KAVS4956-I, and KAVS4971-E)

Automatic retry of a job that ends abnormally (KAVS4675-I, KAVS4676-I, KAVS4677-E, and KAVS4678-I)

If you specify a value other than all, the start (KAVS0263-I), normal-end (KAVS0264-I), and queuing cancellation (KAVS0266-I) messages will not be output for jobs.

Default value

none

Recommended value

Default value

When the setting takes effect

When the scheduler service starts

(61) "AJSLOG" = "{none|all}"

Use this parameter to specify whether to output messages related to starting and terminating the scheduler services to the scheduler log file.

Specifiable values

none

The messages related to starting and terminating the scheduler service, are not output.

all

Messages related to starting (KAVS0200-I) and terminating (KAVS0201-I) the scheduler service and to the abnormal end message for processes (KAVS0204-E) are output.

Default value

all

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

(62) "NETLOG" = "{none|{abend:warning:hold:startdelay:enddelay:condition:execdeffer:prewait}|all}"

Use this parameter to specify whether to output messages related to starting and ending jobnets to the scheduler log file.

Specifiable values

none

The messages related to starting and ending jobnets are not output.

abend

The abnormal end message for jobnets (KAVS0262-E) and the block notification messages (KAVS0272-E and KAVS0273-E) are output.

warning

The end with warning message for jobnets (KAVS0268-W) is output.

hold

The on-hold notification message for jobnets (KAVS0270-I) is output.

startdelay

The delayed-start notification message for jobnets (KAVS0275-I) is output.

enddelay

The delayed-end notification message for jobnets (KAVS0276-I) is output.

condition

The notification messages for jobnets reporting the start of start-condition monitoring (KAVS0240-I) and the end of start-condition monitoring (KAVS0241-I) are output.

execdeffer

The deferred execution message for jobnets (KAVS0279-E) is output.

prewait

Messages related to the start and end of waiting in accordance with a jobnet wait condition and those related to endless waiting (KAVS4950-I, KAVS4955-I, and KAVS4957-E) are output.

all

The following messages related to starting and ending jobnets are output:

Start (KAVS0260-I)

Normal end (KAVS0261-I)

Abnormal end (KAVS0262-E)

End with warning (KAVS0268-W)

On-hold notification (KAVS0270-I)

Block notification (KAVS0272-E and KAVS0273-E)

Delayed start (KAVS0275-I)

Delayed end (KAVS0276-I)

Notification of the next queued execution schedule (KAVS0277-I)

Start of start-condition monitoring notification (KAVS0240-I)

End of start-condition monitoring notification (KAVS0241-I)

Deferred execution (KAVS0279-E)

All registrations canceled (KAVS0267-I)

Notification of the wait for the end of start-condition monitoring (KAVS1420-I)

Start or end of waiting in accordance with a wait condition, and endless waiting (KAVS4950-I, KAVS4955-I, and KAVS4957-E)

If you specify a value other than all, the following messages are not output:

Start (KAVS0260-I)

Normal end (KAVS0261-I)

Notification of the next queued execution schedule (KAVS0277-I)

All registrations canceled (KAVS0267-I)

Notification of the wait for the end of start-condition monitoring (KAVS1420-I)

Default value

all

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

Cautionary note

Note that the default behavior of JP1/AJS3 and JP1/AJS2 version 06-71 and later is to output the start/end of start-condition monitoring notification, deferred execution, and all registration canceled messages for jobnets.

(63) "JOBLOG" = "{none|{abend:warning:hold:enddelay:prewait:retry}|all}"

Use this parameter to specify whether to output messages related to starting and ending jobs in a jobnet to the scheduler log file.

Specifiable values

none

The messages related to starting and ending jobs are not output.

abend

The abnormal end message for jobs (KAVS0265-E) is output.

warning

The end with warning message for jobs (KAVS0269-W) is output.

hold

The on-hold notification message for jobs (KAVS0271-I) is output.

enddelay

The delayed-end notification message for jobs (KAVS0248-I) is output.

prewait

Messages related to the start and end of waiting in accordance with a job wait condition and messages related to endless waiting (KAVS4951-I, KAVS4956-I, and KAVS4971-E) are output.

retry

The automatic retry notification messages generated when a job ends abnormally (KAVS4675-I, KAVS4676-I, KAVS4677-E, and KAVS4678-I) are output.

all

The following messages related to starting and ending jobs are output:

Request for event job execution started (KAVS0242-I)

Start (KAVS0263-I)

Normal end (KAVS0264-I)

Abnormal end (KAVS0265-E)

Queuing cancellation (KAVS0266-I)

End with warning (KAVS0269-W)

On-hold notification (KAVS0271-I)

Submit started (KAVS0278-I)

Delayed end (KAVS0248-I)

Start or end of waiting in accordance with a wait condition, and endless waiting (KAVS4951-I, KAVS4956-I, and KAVS4971-E)

Automatic retry of a job that ends abnormally (KAVS4675-I, KAVS4676-I, KAVS4677-E, and KAVS4678-I)

If you specify a value other than all, the start (KAVS0242-I, KAVS0263-I, KAVS0278-I), normal-end (KAVS0264-I), and queuing cancellation (KAVS0266-I) messages will not be output for jobs.

Default value

all

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

(64) "OPELOG" = "{none|{alter:stop:entry:leave:plan:intrpt:rerun:kill:change:calendar:delete:restore:define:copy:chgst:suspend:import:start:rgimport:release}|all}"

Use this parameter to specify whether to output operation logs to the scheduler log file.

Specifiable values

none

Operation logs are not output.

alter

The execution log for the ajsalter command (log type: C001) is output.

stop

The execution log for the ajsstop command (log type: C002) is output.

entry

The operation log recording the registration of jobnets (log type: C101) is output.

leave

The operation log recording the cancellation of jobnet registration (log type: C102) is output.

plan

The operation log recording changes to jobnet plans (log type: C103) is output.

intrpt

The operation log recording the interruption of jobnets (log type: C104) is output.

rerun

The operation log recording the rerunning of jobnets (log type: C105) is output.

kill

The operation log recording killed jobs (log type: C201) is output.

change

The operation log recording changes to units (log type: C301) is output.

calendar

The operation log recording changes to the calendar information (log type: C401) is output.

delete

The operation log recording the deletion of units (log type: C302) is output.

restore

The operation log recording the restoration of units (log type: C303) is output.

define

The operation log recording the definition of units (log type: C304) is output.

copy

The operation log recording the copying and moving of units (log type: C305) is output.

chgst

The operation log recording changes to the job status (log type: C202) is output.

suspend

The operation log recording suspension or the cancellation of the suspended status (log type: C106) is output.

import

The operation log recording the import of units (log type: C306) is output.

start

The execution log for the ajsstart command (log type: C003) is output.

rgimport

The operation log recording the import of the registered execution-schedule information (log type: C107, C108) is output.

release

The execution log for the ajsrelease command (log type: C307) is output.

all

All operation logs are output.

Default value

all

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts or terminates

(65) "LOGINFOALL" = "{yes|no}"

Use this parameter to specify the format of messages output to the scheduler log file, Windows event log, or syslog file.

Change the parameter value if you do not want to output messages that contain additional information such as the execution ID or the job number.

For details about the logs that can be output to the scheduler log file, see C.1 Log entries output by the scheduler services in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

Specifiable values

yes

In addition to the message output when no is specified, messages are output in a format that includes detailed information such as the execution ID or the job number.

The following information is added to messages:

Execution ID is added to the log data related to starting and ending jobnets and jobs.

Job number is added to the log data related to starting and ending jobs.

Host name is added to log data related to the starting of jobs in the Windows event log or syslog. Host name is output to log data related to the ending of jobs, regardless of the setting.

Return value is added to the normal-end log data for jobs.

no

No additional detailed information, such as the execution ID or job number, is output.

Default value

no

During a new installation and setup of JP1/AJS3, yes is set.

Recommended value

yes

When the setting takes effect

When the scheduler service starts or terminates

(66) "REFLOG" = "{none|{backup:export:name:print:schedule:show:rgexport:release}|all}"

Use this parameter to specify whether to output reference logs to the scheduler log file.

Specify this parameter when you want to keep logs that will be used by the reference commands, such as ajsprint.

Specifiable values

none

No reference logs are output.

backup

The reference log for backed-up units (log type: C504 and C511) is output.

export

The reference log for exported units (log type: C508) is output.

name

The reference log for output of unit names (log type: C507 and C512) is output.

print

The reference log for unit definitions (log type: C503 and C510) is output.

schedule

The reference log for output of jobnet schedule information (log type: C506) is output.

show

The reference log for output of the unit status (log type: C502 and C509) is output.

rgexport

The reference log for exporting the registered execution-schedule information (log type: C513 and C514) is output.

release

The execution log for the ajsrelease command (log type: C515) is output.

all

All reference logs are output:

Backed-up units (log type: C504 and C511)

Exported units (log type: C508)

Output of unit names (log type: C507 and C512)

Output of unit definitions (log type: C503 and C510)

Output of jobnet schedule information (log type: C506)

Output of the unit status (log type: C502 and C509)

Exported registered execution-schedule information (log type: C513 and C514)

ajsrelease command (log type: C515)

Default value

all

Recommended value

Default value

When the setting takes effect

When the scheduler service starts or terminates

Cautionary note

The default log file size (LOGSIZE) in version 07-00 and later differs from that in version 06-71 and earlier because some commands for which logs were not output in version 06-71 or earlier have been changed so that operation logs can now be output in version 07-00 and later.

Supplementary note

Reference logs related to abnormal end will be output if you specify one or more of all, backup, export, name, print, schedule, show, rgexport, and release, and specify yes for the AJSLOGOUTPUTEXTEND environment setting parameter.

(67) "LOGHEADER" = "{none|PID}"

Use this parameter to specify whether to output the log information with the process ID added.

Change the parameter value if you do not want to output log information with the process ID added.

Specifiable values

none

The process ID is not output as part of the log information (the specification in version 06-71 and earlier).

PID

The process ID is output as part of the log information.

Default value

none

During a new installation and setup of JP1/AJS3, PID is set.

Recommended value

PID

When the setting takes effect

When the scheduler service starts or terminates

(68) "INFOLOG" = "{none|{START:REQUEST}|all}"

Use this parameter to specify whether to output information logs.

Change the parameter value if you do not want to perform any performance evaluations, such as evaluations of the command processing time and the maximum number of concurrently executable commands.

Specifiable values

none

The command execution start log (log type: I001) and the scheduler service request log (log type: I002) are not output.

START

The log recording the applicable command processing started (log type: I001) is output.

REQUEST

The log recording when processing requests from a command to the scheduler service started (log type: I002) is output.

all

The command execution start log (log type: I001) and scheduler service request log (log type: I002) are output.

Default value

none

During a new installation and setup of JP1/AJS3, all is set.

Recommended value

all

When the setting takes effect

When the scheduler service starts or terminates

(69) "ROOTJOBNETSCHEDULERANGE" = dword:{00000018|00000030}

Use this parameter to specify the valid range for the schedule of a root jobnet.

Change the parameter value if you want to set the valid range for the schedule of a root jobnet to 48 hours.

If you change the specified value, the execution schedules of the root jobnet before and after the change will be different, in which case you must review the cold-start and jobnet schedules.

Specifiable values

00000018

The valid range for the schedule of the root jobnet is set to 24 hours.

00000030

The valid range for the schedule of the root jobnet is set to 48 hours.

You can specify dword:00000030 only if you specify all for the VIEWSTATUSRANGE environment setting parameter as the range of generation information used as the basis for acquiring the status via JP1/AJS3 - View.

Default value

dword:00000018 (24 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

(70) "VIEWSTATUSRANGE" = "{today|all}"

Use this parameter to specify the range of generation information to be used as the basis for acquiring the status via JP1/AJS3 - View.

Change the parameter value if you want to determine the status to be displayed from the generation information for the current date between the base times.

Specifiable values

today

The status to be displayed is determined from the generation information for the current date between the base times.

You can specify today only if you specify 24 hours as the valid range for the schedule of the root jobnet (dword:00000018 is specified for the ROOTJOBNETSCHEDULERANGE environment setting parameter).

If you specify 48 hours (dword:00000030 is specified for the ROOTJOBNETSCHEDULERANGE environment setting parameter), you cannot specify today.

all

The status to be displayed is determined from the information for the generation or scheduled generation within the range of all days, including today.

Default value

all

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

(71) "STARTMODE" = "{cold|warm|hot}"

Use this parameter to specify the start mode of the scheduler service that starts when the JP1/AJS3 service is started.

When a scheduler service starts, the start mode determines whether the registration status existing when the scheduler service terminated previously, is preserved or canceled.

For details about the statuses of the jobnets and jobs in each start mode, see 7.2.1(3) Jobnet and job statuses for each start mode in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

Specifiable values

cold

The registration status existing when the scheduler service was terminated previously, is canceled, and the scheduler service starts.

warm

The registration status existing when the scheduler service terminated previously, is preserved, and the scheduler service starts. However, the jobnet that was being executed the previous time the service terminates is treated as having terminated and is executed according to the schedule for the day on which the scheduler service is currently started.

hot

The registration status existing when the scheduler service terminated previously, is preserved, and the scheduler service starts. When you restart a service in which an error has occurred, specify this value if you want the restarted service to inherit the status existing when the scheduler service terminated abnormally.

Default value

warm

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

(72) "OVERSCHEDULE" = "{exec|skip|plan}"

When a scheduler service starts, if the scheduled execution start time of a jobnet, which is scheduled for execution that day has already passed, use this parameter to specify how to handle execution of the jobnet. If hot is specified for the STARTMODE environment setting parameter as the scheduler service start mode, all the jobnets are executed regardless of this parameter and the jobnet execution registration options.

If you start the scheduler service by executing the ajsstart command, the value of the OVERSCHEDULE environment setting parameter is not valid, and operation is determined by the ajsstart command. For details about the ajsstart command, see ajsstart in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

Specifiable values

exec

The jobnets scheduled for execution that day are executed, except in the following cases:

The scheduled execution time of a jobnet for which you select the Execute from next time option in the Planned time passed when daemon starts column in the Register for Execution dialog box of JP1/AJS3 - View have already passed when you register the job for execution.

The scheduled execution time of a jobnet for which you specify the -o option in the ajsentry command has already passed when you register the job for execution.

skip

All jobnets scheduled for execution that day are executed except those jobs that are scheduled for execution before the scheduler service starts. These jobs are not executed because their status is skipped so not executed. In addition, jobnets are not executed in the following cases:

The scheduled execution time of a jobnet for which you select the Execute immediately option in the Planned time passed when daemon starts column in the Register for Execution dialog box of JP1/AJS3 - View has already passed when you register the job for execution.

The scheduled execution time of a jobnet for which you did not specify the -o option in the ajsentry command has already passed when you register the jobnet for execution.

plan

The jobnets scheduled for execution that day are not executed because their status will be skipped so not executed. Regardless of the option set when execution was registered, the jobnets scheduled for execution on the day that the scheduler service starts are not executed.

Default value

exec

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

(73) "SUPPRESS" = "{none|exec}"

Use this parameter to specify whether to suppress the execution of jobnets and the jobs in jobnets.

Specifiable values

none

The execution of jobs and jobnets is not suppressed.

exec

The execution of jobs and jobnets is suppressed.

Default value

none

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

(74) "EXECDEFER" = "{oneday|twoday|unlimit}"

Use this parameter to specify how long to wait before the status of a root jobnet registered for execution changes to skipped so not executed when the jobnet has not been executed and the scheduled start date and time have passed.

This parameter remains in effect regardless of the mode set at execution registration.

If you register a jobnet for immediate execution, the date and time that the jobnet is registered are regarded as the scheduled start date and time.

Specifiable values

oneday

The jobnet status changes to skipped so not executed one day after the scheduled date.

twoday

The jobnet status changes to skipped so not executed two days after the scheduled date.

unlimit

Although the scheduled date has passed, the jobnet status remains waiting for start time or on hold.

Default value

oneday

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

(75) "JOBSTATUSPORT" = "service-name-of-the-port-for-acquiring-job-status"

Use this parameter to specify the port number of the communication port to be used to acquire job status information.

To execute multiple scheduler services, you must specify a different service name for each scheduler service and set a unique port number in the services file.

Specifiable values

A service name defined in the services file

Default value

jp1ajs2report

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

(76) "QUEUELESSMULTIREQ" = dword:maximum-number-of-queueless-job-requests

The number of concurrently requested queueless jobs equals the number of processes communicating with the queueless agent when a queueless job is executed. Use this parameter to specify the number of queueless job request processes (ajsreqd.exe for Windows and ajsreqd for UNIX) started for each scheduler service.

If distributing queueless jobs will affect job execution performance, specify this parameter only if you increase the number of processes that communicate with the queueless agent services.

Specifiable values

A hexadecimal value from 00000001 to 00000008 (1 to 8 in decimal)

Default value

dword:00000001 (1 in decimal)

In a queueless job system, distributing queueless jobs does not result in lower-execution performance, so you can use the default value.

Recommended value

Default value

When the setting takes effect

When the scheduler service starts

(77) "UNITDEFINERELOAD" = "{yes|no}"

If you change the definition of a job or jobnet after registering execution, use this parameter to specify whether to reload the changed definition just before execution so that the changes take effect immediately.

Change the value of the parameter if you do not want to immediately apply changes made to the already defined unit information.

Specifiable values

yes

The definition is reloaded immediately before a job or jobnet is executed.

If this value is set, the most recent changes to the definition will take effect for the generation that was being processed when the definition was changed.

no

The definition is not reloaded immediately before a job or jobnet is executed (This is the behavior in JP1/AJS2 06-51 and earlier versions).

If this value is set, the most recent changes to the definition will not take effect for the generation that was being processed when the definition was changed.

Default value

no

During a new installation and setup of JP1/AJS3, yes is set.

Recommended value

yes

When the setting takes effect

When the scheduler service starts

Cautionary note

JP1/AJS3 allows you to change the unit definition information that affects the execution of the unit, such as the file name, target host, and hold attribute, during registration for execution. However, some items in the changed unit information will not take effect for the generation that is being processed when you change the definition. For details, see 8.4 Changing the unit definition information during registration for execution in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

(78) "MAXSAVEGEN" = dword:maximum-number-of-saved-generations

Use this parameter to specify the maximum number of saved generations.

The value specified here is the maximum value that you can define for the number of logs to keep.

Change this value when you want to increase the number of logs to keep to 100 or more.

When you specify LEGACY for the SAVEGENTYPE environment setting parameter, the same number of execution results as the number of logs to keep is stored for each of the monitoring generations and execution generations.

When you specify TOTAL for the SAVEGENTYPE environment setting parameter, the same number of execution results as the number of logs to keep is stored, but in this case, the number of logs to keep is the sum of the number of monitoring generations and execution generations.

Specifiable values

A hexadecimal value from 63 to 3E7 (99 to 999 in decimal)

Default value

dword:63 (99 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

Cautionary notes

When you specify LEGACY for the SAVEGENTYPE environment setting parameter and increase the maximum number of specifiable generations, the number of records obtained by multiplying the number of logs to keep by the number of registered units also increases. This greatly affects operations that access the database. Before you increase the maximum number of saved generations, you must divide the jobnets by, for example, reducing the number of records obtained as described above to reduce the size of each root jobnet. For details about the relationship between the number of logs to keep and performance, see 7.2 Relationship between number of logs to keep and performance in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

If you increase the number of logs to keep to 100 or more, the versions of all instances of JP1/AJS3 - View must be version 07-00 or later. If you do this in JP1/AJS3 - View version 07-00 or later, and then update the detailed definitions in version of JP1/AJS3 - View earlier than 07-00, only the first two digits of the number of logs to keep appear. As a result, the number of logs to keep could be changed to an undesirable two-digit-number.

A system for which a smaller value is specified for the maximum number of saved generations might not be able to restore the jobnet definition information defined in a system in which the maximum number of saved generations is increased. For example, suppose you specify 200 as the number of logs to keep for a jobnet in a system in which the maximum number of saved generations is set to 200. If you output this definition information by using the ajsprint command and then try to define this output information by executing the ajsdefine command in a system in which the maximum number of saved generations is set to 150, an error occurs. The reason for the error is that the definition parameters contain a value larger than 150 (200 in this case).

An error dialog box asking you to change the maximum number of saved generations to a smaller value is displayed if the following sequence of operations is performed. First, you increase the maximum number of saved generations and define a jobnet with many saved generations, and then you reduce the maximum number of saved generations. Next, you open the Define Details dialog box of the jobnet in JP1/AJS3 - View, in which the large value you originally specified for the number of logs to keep is displayed. Finally, you click the OK button to close the dialog box.

If you register a jobnet defined with many saved generations, after increasing the maximum number of saved generations, and then you reduce the maximum number of saved generations, the system saves generations according to the registered maximum number of saved generations.

If you specify a decimal number exceeding 320 as the maximum number of saved generations, and then set the number of logs to keep to the maximum, the specified number of generations might not be saved, depending on how many future generations there will be. To increase the number of logs to keep, you must accurately estimate the number of future generations to be registered, and then use this estimate to determine the number of logs to keep. For details about the relationship between the numbers of logs to keep and the number of future generations, see B. List of Limits in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

(79) "AJSPRINTNETSCHPRF" = "{yes|no}"

Specify whether to enable the scheduler rule, thereby freeing operation from the schedule of the upper-level jobnet, or to delete the scheduler rule, thereby making operation dependent on the schedule of the upper-level jobnet.

This option takes effect when you execute the ajsprint, ajsbackup, or ajsexport command, or choose Backup from JP1/AJS3 - View to back up a jobnet created by copying a root jobnet with a schedule rule to a nested jobnet.

Specifiable values

yes

The scheduler rule is enabled. Operation does not depend on the schedule of the upper-level jobnet.

no

The schedule rule is deleted. Operation depends on the schedule of the upper-level jobnet.

Default value

yes

During a new installation and setup of JP1/AJS3, no is set.

Recommended value

no

When the setting takes effect

When the scheduler service starts

(80) "SUBMITRETRYINTERVAL" = dword:retry-interval

If many jobs are executed simultaneously, although they may seem to have been submitted, they will be submitted in some cases they will not actually be queued (that is, their submission will be put on hold).

For such cases, you can use this parameter to specify a value in milliseconds for the period of time that needs to elapse before the submission will be retried.

However, be careful not to specify too small a value as the retry interval, because the system will attempt the job submission many times when there are jobs on hold, increasing the system load.

Specifiable values

A hexadecimal value (in milliseconds) from 00000000 to 00002710 (0 to 10,000 in decimal)

If you omit this parameter or specify an invalid value, the system assumes the default value.

Default value

dword:00000BB8 (3,000 in decimal)

Recommended value

Set a value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

(81) "JOBEXECIPCBUFSIZE" = dword:buffer-size-for-job-execution-information-communication

Use this parameter to specify the buffer size to be used for communicating the job execution information of a scheduler service.

Specifiable values

A hexadecimal value (in bytes) from 00001000 to 00100000 (4,096 to 1,048,576 in decimal)

If you omit this parameter or specify an invalid value, the system assumes the default value.

Default value

dword:00000000 (0 in decimal)

If you do not specify a buffer size for communicating job execution information, the default value is assumed. In this case, the OS socket buffer is used as the default value.

Recommended value

Default value

When the setting takes effect

When the scheduler service starts

(82) "BACKGROUNDLEAVE" = "{yes|no}"

Use this parameter to determine the method to be used to delete generations when canceling registration or managing saved generations.

Change the parameter value if you want to create the generation management subprocess (ajsschbd) in the processing that deletes jobnet registration information so that generations will be deleted in the background.

If you change the value, you must restart the JP1/AJS3 service. You also need to perform migration by using a migration tool or by a cold-start.

For details about how to set the environment setting parameters, see 6.1.6 Changing the mode in which unregistration or generation management deletes the generations of a jobnet in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.1.6 Changing the mode in which unregistration or generation management deletes the generations of a jobnet in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

yes

The generation management subprocess (ajsschbd) is used to delete the registration information of a jobnet.

If you specify yes, the generation management subprocess deletes registration information in the background, reducing the turnaround time for registration cancellation. Be careful when you specify yes, because doing so causes the system to use more resources for the generation management subprocess.

no

The schedule control process (ajsschd) is used to delete the registration information of a jobnet.

If you specify no, the schedule control process (ajsschd) deletes all the information of the generations to be deleted, increasing the turnaround time for registration cancellation in proportion to the number of generations or units to be deleted.

Default value

no

During a new installation and setup of JP1/AJS3, yes is set.

Recommended value

yes

When the setting takes effect

When the scheduler service starts

(83) "REQDAGTREQCONNECTTIMEOUT" = dword:timeout-period-for-communication

Use this parameter to specify how long to wait (the timeout period) for the requesting queueless-job request process to establish communication when connection processing is performed for a processing request (job execution, forced termination, or status confirmation) to a queueless agent service.

For a high-speed network between the manager host and an agent host, specify a smaller value when you want to quickly detect non-starting of an agent host. For a low-speed network and system, or for an environment in which the agent host is likely to be busy, specify a larger value. However, please note when specifying a larger value because a processing request will not be sent to another agent host until connection has been completed or the timeout period expires. If there are no special circumstances, we recommend that you use the default value of 15 seconds.

If communication is not established within the period specified by this parameter, the queueless job request process outputs the KAVS1930-W message and starts the reconnection processing. After the reconnection processing has started, processing requests to other agents that can communicate normally are executed as usual. However, processing requests to other relevant agents accumulate on the manager host as requests to a failed agent, and the reconnection processing is attempted one request at a time in the order they were executed. The timeout period for the reconnection processing differs according to the OS, and the reconnection processing will stop when the maximum communication-recovery-processing timeout period specified in the REQDAGTRECONNECTTIMEOUT environment settings parameter expires. Two reconnection attempts are performed at 60 second intervals, but if recovery is not possible, one of the following error messages is output:

For a job execution request: KAVS1931-E

For a request to force the termination of a job: KAVS1932-E

For a request to confirm the status of a job: KAVS1933-E

If the reconnection is successful, the KAVS1929-I message is output, the accumulated requests are resent in order, and the system recovers from a failure status.

Specifiable values

A hexadecimal value (in seconds) from 00000000 to 00000258 (0 to 600 in decimal)

If you specify dword:00000000, the operation is controlled by the OS timeout period.

Default value

dword:0000000F (15 in decimal)

Recommended value

Default value

When the setting takes effect

When the scheduler service starts

(84) "REQDAGTRECONNECTTIMEOUT" = dword:timeout-period-for-communication

Specify how long to wait (the timeout period) for the requesting queueless-job request process to establish communication when reconnection processing is performed in either of the following cases:

When a communication failure occurs for a processing request (job execution, forced termination, of status confirmation) to a queueless agent (the KAVS1930-W message is output)

When disconnection of the communication line between the manager host and agent host was detected during execution of a job on a queueless agent (the KAVS1922-W message is output) and the system attempts to re-establish communication

Unless there are special circumstances, we recommend that you use the default value of 90 seconds.

This reconnection processing is performed in parallel with a processing request to another agent host. Therefore, requests to other agent hosts able to perform communication normally do not have until connection is completed or until the timeout period expires.

Specifiable values

A hexadecimal value (in seconds) from 00000000 to 00000258 (0 to 600 in decimal)

If you specify dword:00000000, operation is controlled by the OS timeout period. For details about reconnection processing, see the explanation for the REQDAGTREQCONNECTTIMEOUT environment setting parameter that specifies the timeout period for connection processing.

Default value

dword:0000005A (90 in decimal)

Recommended value

Default value

When the setting takes effect

When the scheduler service starts

(85) "COMMANDEVENT" = "{yes|no}"

Specify whether to issue a JP1 event when a command is executed or when an operation is performed from JP1/AJS3 - View.

If you set in the OPELOG, REFLOG, and INFOLOG environment setting parameters that the command operation logs are to be output to the scheduler log, the same information is issued as a JP1 event. However, for the log reporting processing start requests to a scheduler service (log type: I002), no JP1 event is issued.

Specifiable values

yes

A JP1 event is issued when a command is executed or when an operation is performed from JP1/AJS3 - View.

no

A JP1 event is not issued when a command is executed or when an operation is performed from JP1/AJS3 - View.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts or terminates

(86) "NONRELOADHOLDING" = "{yes|no}"

Use this parameter if a unit definition on hold is not to be reloaded when the function for immediately applying jobnet definition changes (UNITDEFINERELOAD) is used. If you reload the unit definition on hold and change the specification for holding the unit definition from yes to no, a unit on hold is executed immediately.

Specifiable values

yes

A unit definition on hold is not reloaded when the function for immediately applying jobnet definition changes (UNITDEFINERELOAD) is used.

no

A unit definition on hold is reloaded when the function for immediately applying jobnet definition changes (UNITDEFINERELOAD) is used.

Default value

no

During a new installation and setup of JP1/AJS3, yes is set.

Recommended value

yes

When the setting takes effect

When the scheduler service starts

Cautionary note

If you specify no for this parameter, and change the hold specification for the unit definition from yes to no, the unit on hold is executed when:

Execution of a unit in the same scheduler service starts or ends.

One of the following operations is executed for a unit in the same scheduler service: rerun, hold, release hold, suspend, release suspension, or change schedule.

The scheduler service is restarted.

The ajsstop command is executed with the -r option specified.

Also note that if many units are on hold (200 units is the recommended maximum, although this limit might vary depending on the environment), more unit definitions must be reloaded than when yes is specified, resulting in increased I/O processing.

Specify no only if an operation procedure that releases a unit on hold by specifying no for the hold specification of the unit definition has been set up and modifying the operation procedure would be difficult.

(87) "RJCUSE" = "{yes|no}"

Use this parameter to specify whether to control the execution order of root jobnets that have been distributed among different scheduler services by using a jobnet connector.

Specifiable values

yes

Specify this value to control the execution order of root jobnets distributed among different scheduler services.

no

Specify this value if you do not want to control the execution order of root jobnets distributed among different scheduler services.

Default value

no

During a new installation and setup of JP1/AJS3, yes is set.

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After JP1/AJS3 service is restarted

(88) "JOBDELAYWARNMSG" = "{yes|no}"

Use this parameter to specify whether to output a warning message to the integrated trace log when the scheduler service starts. The message that is output is generated if a job for which termination delay is monitored according to the required time for execution is executed on the job execution control agent when a scheduler service has been stopped.

Specifiable values

yes

The KAVS0249-W message is output.

Note, however, that the scheduler service is started in disaster recovery mode, the termination status will be unknown regardless of the job status on the job execution control agent. In this case, the message will not be output.

no

The message is not output.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

(89) "FGRECONLMT" = dword:number-of-reconnection-attempts

Use this parameter to specify the number of reconnection attempts if the flow control process cannot communicate with the scheduler service inter-communication control process.

Specifiable values

A hexadecimal value from 0 to 64 (0 to 100 in decimal)

Default value

dword:00000003 (3 in decimal)

Recommended value

Default value

When the setting takes effect

When the scheduler service starts

(90) "SAVEGENTYPE" = "{TOTAL|LEGACY}"

Use this parameter to specify the method used to manage the number of logs to keep of the execution results for a jobnet for which start conditions are defined.

For details about how to manage the number of logs to keep, see 4.2.3 Jobnet generation management in the manual Job Management Partner 1/Automatic Job Management System 3 Overview.

Specifiable values

TOTAL

A new method used from version 9 (the total management method). The number of logs to keep can be specified as the sum of the number of monitoring generations and execution generations.

LEGACY

The legacy management method used through version 8 (the individual management method). The number of execution results specified as the number of logs to keep is saved separately for the monitoring generation and the execution generation. Therefore, the number of execution results to be saved is the square of the number specified as the maximum number of saved generations.

Default value

LEGACY

During a new installation and setup of JP1/AJS3, TOTAL is set.

Recommended value

TOTAL

When the setting takes effect

When the scheduler service starts

(91) "AJSDBTYPE" = "{ISAM|EmbedDB}"

Use this parameter to specify the type of database to be used.

Usually, you do not need to change this value.

Specifiable values

ISAM

The ISAM database is provided as a standard component of JP1/AJS3 - Manager.

EmbedDB

The embedded database can be used as the standard JP1/AJS3 - Manager database.

Default value

ISAM

During a new installation and setup of JP1/AJS3, EmbedDB is set.

Recommended value

The value set in JP1/AJS3 - Manager

When the setting takes effect

When the scheduler service starts or terminates

If you change this parameter, you must re-create the scheduler database.

(92) "AJSDBDIRECTORY" = "database-directory-name"

Use this parameter to specify the name of the directory used to store the JP1/AJS3 unit information. Specify a full path name.

Change the parameter value if there is no more available disk space in the default directory or when you need to change the directory to a directory under a shared directory in a cluster configuration.

If you use multiple scheduler services, specify a directory that does not conflict with the directories of other scheduler services.

Specifiable values

In Windows:

A character string of no more than 180 bytes

In UNIX:

A character string of no more than 191 bytes

Do not use a semicolon (;) or spaces.

Default value

During a new installation and setup of JP1/AJS3, the following path is set:

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\database\schedule\AJSROOT1

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-Manager-installation-folder\database\schedule\AJSROOT1

For Windows Server 2003:

JP1/AJS3-Manager-installation-folder\database\schedule\AJSROOT1

In UNIX:

/var/opt/jp1ajs2/database/schedule/AJSROOT1

Recommended value

The value set at the time of installation or setup.

When the setting takes effect

When the scheduler service starts or terminates

If you change this parameter, you must re-create the scheduler database.

Cautionary notes

For those users who define, execute, and reference jobnets, define the following permissions for the directory specified here and the files under the directory:

- In Windows:

Read and write permissions

- In UNIX:

Update permission (rwx)

The directory specified here will contain the files needed to perform exclusive editing of the unit, ISAM data files, and key files (if you specify ISAM as the JP1/AJS3 database). Do not delete these files.

This directory must be created when you add a scheduler service.

In UNIX, do not create a symbolic link for a file created in the directory specified in this parameter. If you do so, reorganization will break the link because the file is re-created. Use the directory specified in this parameter if you want to create a symbolic link.

For this parameter, you cannot specify a directory mounted on an NFS file system or a similar file system connected to a network or a network drive.

(93) "AJSSYSDIR" = "name-of-system-directory"

Use this parameter to specify the name of the directory in which you create the JP1/AJS3 system files. Specify a full path name.

Determine a name appropriate for the operating environment after estimating the amount of the required disk space.

If you use multiple scheduler services, specify a directory that does not conflict with the directories of other scheduler services.

For users with administrator permissions or superuser permissions, set the update permission (rwx for UNIX) for this directory. For all users, set the operation permission (rx for UNIX).

Specifiable values

In Windows:

A character string of no more than 180 bytes

In UNIX:

A character string of no more than 191 bytes

Do not use a semicolon (;) or spaces.

Default value

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\sys\schedule\scheduler-service-name

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-Manager-installation-folder\sys\schedule\scheduler-service-name

For Windows Server 2003:

JP1/AJS3-Manager-installation-folder\sys\schedule\scheduler-service-name

In UNIX:

/var/opt/jp1ajs2/sys/schedule/scheduler-service-name

If you have added a scheduler service, create this directory newly.

Recommended value

The value set at the time of installation or setup.

When the setting takes effect

When the scheduler service starts or terminates

(94) "AJSLOGDIR" = "name-of-direcotry-for-log-files"

Use this parameter to specify the name of the directory in which JP1/AJS3 log files are created. Specify a full path name.

Determine a name appropriate for the operating environment after estimating the amount of the required disk space.

If you use multiple scheduler services, specify a directory that does not conflict with the directories of other scheduler services

For all users, set the update permission (rwx for UNIX) for this directory.

Specifiable values

In Windows:

A character string of no more than 180 bytes

In UNIX:

A character string of no more than 191 bytes

Do not use a semicolon (;) or spaces.

Default value

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\schedule\scheduler-service-name

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-Manager-installation-folder\log\schedule\scheduler-service-name

For Windows Server 2003:

JP1/AJS3-Manager-installation-folder\log\schedule\scheduler-service-name

In UNIX:

/var/opt/jp1ajs2/log/schedule/scheduler-service-name

If you have added a scheduler service, create this directory newly.

Recommended value

The value set at the time of installation or setup.

When the setting takes effect

When the scheduler service starts or terminates

(95) "PREWAITUSE" = "{yes|no}"

Use this parameter to specify whether to use wait conditions.

Specifiable values

yes

Wait conditions are used.

no

Wait conditions are not used.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

Supplementary notes

If you want to change the setting from yes to no, cancel the registration of all units with wait conditions before you change the setting to no. Alternatively, cold-start the scheduler service after changing the setting to no.

Even if the setting is no, you can still define wait conditions. Note, however, that if you execute a unit with a wait condition, it will terminate abnormally.

If the database configuration of JP1/AJS3 is a compatible ISAM configuration, wait conditions cannot be used even if the setting is yes.

If the database configuration of JP1/AJS3 is a standard configuration or a standard configuration without ISAM, changing the setting to yes starts the flow control subprocess (ajsflbd).

(96) "PREWAITEXTEND" = "{none|condition}"

Use this parameter to extend the wait condition function. When the PREWAITUSE environment setting parameter is set to yes, specify for this parameter a value appropriate for the operating environment.

The setting of this parameter is ignored in the following cases:

The PREWAITUSE environment setting parameter is set to no.

The database configuration of JP1/AJS3 is a compatible ISAM configuration.

Specifiable values

none

You can apply wait conditions to the following units:

Units capable of accepting wait conditions:

A root jobnet without start conditions and its lower-level units

Nested jobnet

A root jobnet directly under a planning group and its lower-level units

Standard job

Jobnet connector

Event job in a jobnet

Action job

Custom job

Passing information setting job

Units specifiable as a unit whose end is being waited for:

A root jobnet without start conditions and its lower-level units

Nested jobnet

Planning group

Lower-level units in root jobnet directly under planning group

Standard job

Jobnet connector

Event job in a jobnet

Action job

Custom job

Passing information setting job

For details, see Table 2-9 in 2.2.5(1)(a) Units with wait conditions and units whose ends are being waited for in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

condition

In addition to the case in which none is set, you can apply wait conditions to the following units.

Units capable of accepting wait conditions:

Root jobnet with a start condition

Units specifiable as a unit whose end is being waited for:

Root jobnet with a start condition

For details, see Table 2-9 in 2.2.5(1)(a) Units with wait conditions and units whose ends are being waited for in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

Default value

none

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

(97) "FLBDLOGSIZE" = dword:size-of-flow-control-subprocess-internal-log-file

Use this parameter to specify the size of an internal log file for a flow control subprocess.

You do not need to specify this parameter if wait conditions will not be used (the PREWAITUSE environment setting parameter is set to no).

Because this log file is used to check the execution status of units with wait conditions, specify a size large enough for storing the log data of at least one day. For details about how to estimate the file size, see 3.4.7 Estimating the size of log files output by a flow control subprocess in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

The two files whose size you specify here will be used as log files.

Specifiable values

A hexadecimal value (in kilobytes) from 0 to 1E8480 (0 to 2,000,000 in decimal)

If you specify a value from 0 to 3, a log file is not created.

Default value

dword:00002800 (10,240 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

(98) "AGENTPROFMEMSIZE" = dword:memory-size-used-by-execution-agent-profile

Use this parameter to specify the size of memory that can be used by an execution agent profile.

If many units are specified in an execution agent profile, allocate only the amount of memory required for the execution agent profile. For details about how to estimate the size of memory used by an execution agent profile, see 3.2.1(2)(a) @SYS_RESTRICT_START.

The specified value needs to be added to the estimate for required memory.

If an attempt to allocate memory fails, an error message is output and the execution agent profile is not enabled.

Specifiable values

A hexadecimal value (in kilobytes) from 200 to 1400 (512 to 5,120 in decimal)

Default value

dword:00000200 (512 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the JP1/AJS3 service starts

(99) "UNITPROFMEMSIZE" = dword: memory-size-used-by-unit-attribute-profile

Use this parameter to specify the size of memory that can be used by a unit-attribute profile.

If many units are specified in a unit-attribute profile, allocate only the amount of memory required for the unit-attribute profile. For details about how to estimate the size of memory used by a unit-attribute profile, see 3.2.2(2)(a) @SYS_PROFILE_START.

The specified value needs to be added to the estimate for required memory.

If an attempt to allocate memory fails, an error message is output and the unit-attribute profile is not enabled.

Specifiable values

A hexadecimal value (in kilobytes) from 80 to 500 (128 to 1,280 in decimal)

Default value

dword:00000080 (128 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the JP1/AJS3 service starts

(100) "UNITDEFDIVIDEUPDATE" = "{yes|no}"

Use this parameter to specify whether writing to a database during the following unit operations is to be divided into parts.

ajsdefine command

ajscopy command or copying of a unit in JP1/AJS3 - View

ajsrestore command or restoration in JP1/AJS3 - View

ajsimport command

ajssuspend command or a suspension release in JP1/AJS3 - View

ajsdetele command or deletion in JP1/AJS3 - View

ajsrelease command or either a release entry or a release cancel in JP1/AJS3 - View

Specifiable values

yes

Writing to a database during unit operations is divided.

Division limits the consumption of an embedded database's exclusive resources to prevent a resource insufficiency.

no

Writing to a database during unit operations is not divided.

If a large number of units are operating at the same time, an embedded database's exclusive resources might become insufficient.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

Cautionary notes

If you have specified yes for this parameter, and an error occurs after unit information has been divided and written to the database, a unit whose unit information has been written up to the point of the error might be created or deleted. If an error occurs, restore the unit as described in the output message.

If the total number of units subject to operations by commands or from JP1/AJS3 - View or JP1/AJS2 - View satisfies the following expression, specify yes for the UNITDEFDIVIDEUPDATE environment setting parameter.

(a + b + c + d) / 4 x 1.2 > 4,000

a: (total-number-of-job-groups x 2) + total-number-of-the-calendar-definition-year-items-defined-in-job-groups

b: (total-number-of-jobnets x 2) + total-number-of-the-schedule-rules-defined-in-all-jobnets

c: total-number-of-jobs x 2

d: total-number-of-relation-line-connections-defined-in-jobs-and-jobnets

(101) "EXECREGISTRATIONNUMBER" = "{calendar|execution}"

Use this parameter to specify whether the execution registration number is treated as a calendar date or an execution date.

Specifiable values

calendar

The execution registration number is treated as a calendar date (this is the behavior in 09-10 and earlier versions).

execution

The execution registration number is treated as an execution date.

If a base time has been set or if the system operates on a 48-hour cycle, specify execution to ensure that a temporary-change operation is re-executed correctly.

Default value

calendar

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

Cautionary note

Do not change this parameter during operation. If you do so, the execution registration numbers in the temporary change information displayed in the JP1/AJS3 - View window or by using a command will no longer be consistent with the execution registration numbers held by JP1/AJS3. As a result, a temporary-change operation will not be re-executed correctly. If you change this parameter during operation, cold-start the scheduler service.

(102) "SAVEPLANINFO" = "{yes|no}"

Use this parameter to specify whether to use the temporary-change operation and management functionality. This functionality allows you to display temporary change information and re-execute temporary-change operations. For details about this functionality, see 4.5.16 Displaying and re-executing temporary change operations for a job or jobnet in the manual Job Management Partner 1/Automatic Job Management System 3 Overview.

Specifiable values

yes

The temporary-change operation and management functionality is used.

no

The temporary-change operation and management functionality is not used.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

Cautionary notes

If yes is specified for this parameter and the base time is not set to 0:00, or if dword:00000030 is set for the ROOTJOBNETSCHEDULERANGE environment setting parameter, change the value of the EXECREGISTRATIONNUMBER environment setting parameter to execution to ensure that temporary-change operations are re-executed correctly.

If you changed the parameter setting from yes to no during operation, cold-start the scheduler service. If you do not cold-start the scheduler service, the temporary change information file will not be deleted.

(103) "DEFLENTYPE" = "{byte|sjis}"

Use this parameter to specify whether the number of characters that can be specified for the following items in a UTF-8 environment should conform to the number of characters that can be specified in a Shift JIS environment.

Unit name of a unit detailed definition

Comment for a unit detailed definition

Exclusive jobnet name in the schedule settings

This environment setting parameter is automatically set by executing the ajsembdbsetup command and cannot be changed by the jajs_config command.

For details, see 15.1.9 Setting for changing the number of characters specifiable for a unit name in a UTF-8 environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

byte

The number of usable characters is the number of characters after conversion to the number of bytes in a UTF-8 environment.

sjis

The number of usable characters is the same as that in a Shift JIS environment.

Default value

byte

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

Supplementary note

If you specify the -e byte option for the ajsembdbsetup command, byte is set. If you specify the -e sjis option, sjis is set. If you specify the -del option, byte is set.

(104) "RERUNSUBORDINATE" = "{yes|no}"

Use this parameter to specify whether to re-execute dependent units. Specify yes to allow dependent units to be re-executed.

For details about this functionality, see 4.5.11 Rerunning a job or jobnet in the manual Job Management Partner 1/Automatic Job Management System 3 Overview.

Specifiable values

yes

A dependent unit can be re-executed.

no

A dependent unit cannot be re-executed.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

(105) "SERVICEMAXSESSION" = dword:maximum-allowable-number-of-simultaneous-sessions-for-each-scheduler-service

Use this parameter to specify the maximum allowable number of simultaneous sessions for JP1/AJS3 - View for each scheduler service. If you attempt to connect from JP1/AJS3 - View when the specified number has been reached, the attempt will fail.

Specify this environment setting parameter to restrict the number of connections for each scheduler service. To restrict the maximum allowable number of simultaneous sessions for JP1/AJS3 - View according to the host rather than according to the scheduler service, use the MAXSESSION environment setting parameter. When you use the SERVICEMAXSESSION environment setting parameter, note the following:

Make sure that the setting value of the SERVICEMAXSESSION environment setting parameter does not exceed the setting value of the MAXSESSION environment setting parameter.

When there are multiple scheduler services, make sure that the total of the setting values of the SERVICEMAXSESSION environment setting parameter for all scheduler services does not exceed the setting value of the MAXSESSION environment setting parameter.

For example, if scheduler services AJSROOT1 and AJSROOT2 have been created and the setting value of the MAXSESSION environment setting parameter is 50 (default value), and the setting value of the SERVICEMAXSESSION environment setting parameter for AJSROOT1 is 25, you must specify 25 or a smaller value for the SERVICEMAXSESSION environment setting parameter for AJSROOT2.

Specifiable values

A hexadecimal value from 00000000 to 00000080 (0 to 128 in decimal)

If you specify dword:00000000, JP1/AJS3 - View cannot be connected.

Default value

None.

If you do not set a value, no restrictions on the maximum allowable number of simultaneous sessions for a scheduler service are applied. Therefore, the maximum allowable number of simultaneous sessions for JP1/AJS3 - View will depend on the MAXSESSION environment setting parameter.

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

Cautionary notes

Specify the SERVICEMAXSESSION environment setting parameter for all scheduler services. If this environment setting parameter is set for only some scheduler services on the same logical host or same physical hosts, but not for others, a message (KAVS1014-W) is output at scheduler service startup.

If the maximum allowable number of simultaneous sessions has been exceeded, a message (KAVV452-E) is displayed in the JP1/AJS3 - View window (Summary Monitor window) for each monitored unit that is unable to establish a connection. This message is displayed whenever the window is updated.

To disable the SERVICEMAXSESSION environment setting parameter, delete the definition key by using the jbsunsetcnf command, and then reset the other environment setting parameters of the deleted definition key. Before performing this operation, back up the definition beforehand by using the jbsgetcnf command.

(106) "DEFAULTPRIORITY" = dword:default-execution-priority-of-a-job

Specify the default execution priority to be used if the execution priority of a job and of all upper-level jobnets is set to None.

For details about the job execution priority, see 2.1.4(2) Execution priority in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide. For details about the value specified for the execution priority of jobs, see 7.8.2 Notes on the execution priority of jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

Specifiable values

A hexadecimal value from 1 to 3 (1 to 3 in decimal)

Default value

dword:00000001 (1 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

This setting does not apply to jobs for which the execution start processing has begun and for which the job status is Waiting to execute, Now queuing, or Now running.

Supplementary note

If you specify an execution priority that is higher than that of other processes, a job process started from JP1/AJS3 might use a large portion of the CPU, thus affecting other processes. For this reason, you cannot specify 4 or 5 for the DEFAULTPRIORITY environment setting parameter. If it is necessary to specify an execution priority of 4 or 5 for a certain job, carefully consider the system environment and the manner in which operations are performed, and then specify the execution priority of the job in the job definition.

(107) "AJSPRINTSORTUNITINF" = "{yes|no}"

Use this parameter to determine whether to fix the order of relation line information entries that are output when the ajsprint command is executed with the -f or -a option specified. If the -f option is specified, each entry of relation line information is output as the value represented by the %ar format indicator. If the -a option is specified, each entry of relation line information is output as the ar parameter.

If the ajsprint command is executed without specifying the -s option, the command uses the AJSPRINTSORTUNITINF environment setting parameter instead of the -s option.

If the values of the -s option and the AJSPRINTSORTUNITINF environment setting parameter are different, the -s option takes precedence over the parameter.

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

Specifiable values

yes

Fixes the output order of relation line information entries for units. If yes is specified, the following rules apply when relation line information entries are output:

Entries are output in ascending order of the character codes of the preceding unit names.

Entries whose preceding units are the same are output in ascending order of character codes of the succeeding unit names.

no

Does not fix the output order of relation line information entries for units. If no is specified, the output order of relation line entries depends on the unit creation order.

Default value

no

Recommended value

yes

When the setting takes effect

When the scheduler service starts

(108) "GWMAXCONNECTION" = dword:maximum-concurrent-connections

Use this parameter to specify the maximum number of concurrent connections used for communication by the scheduler service inter-communication control process (ajsgwd.exe for Windows and ajsgwd for UNIX).

In the following cases, you do not need to estimate or change the value of this environment setting parameter:

No jobnet connectors and connection-destination jobnets are used in the system.

Jobnet connectors and connection-destination jobnets are used in the system, but execution sequence control for different scheduler services is not used.

If execution sequence control for different scheduler services is used, you must determine the value to be specified for GWMAXCONNECTION environment setting parameter by using the method for estimating the maximum number of concurrent connections for physical and logical hosts. If the maximum number of concurrent connections exceeds the specified value, the process that controls communication between scheduler services might fail to communicate.

Specifiable values

A hexadecimal value from A to 400 (10 to 1,024 in decimal)

Default value

dword:A (10 in decimal)

Recommended value

The value determined by using the method for estimating the maximum number of concurrent connections

When the setting takes effect

When the JP1/AJS3 service starts

Supplementary note

To estimate the maximum number of concurrent connections for physical and logical hosts, follow the procedure described below.

If the estimated value is less than 10, you do not need to change the default value.

For all scheduler services configured on the host, list the jobnet connectors and connection-destination jobnets for which Other service is specified for Connection range.

These jobnets are those for which the letter y is output when the ajsprint command with the format indicator %Ce specified for the -f option is executed. For the command syntax, see ajsprint in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

Count the number of connection destination hosts. Count jobnet connectors and connection-destination jobnets listed in 1. that have the same value for Host to connect as a single host.

To output the value of Host to connect, execute the ajsprint command with the format indicator %Ch specified for the -f option.

Calculate the maximum number of concurrent connections by using the following formula:

2 x number-of-connection-destination-hosts-counted-in-2.

(109) "GWPROCESSHA" = "{yes|no}"

Specify whether to terminate the process (ajsgwmasterd.exe for Windows and ajsgwmasterd for UNIX) that manages the scheduler service inter-communication control process if the scheduler service inter-communication control process (ajsgwd.exe for Windows and ajsgwd in UNIX) terminates abnormally.

Specifiable values

yes

The process that manages the scheduler service inter-communication control process (ajsgwmasterd.exe for Windows and ajsgwmasterd for UNIX) is terminated.

In UNIX, you start the JP1/AJS3 service by executing the jajs_spmd command with the -HA option specified, when using a logical host in a cluster configuration, all instances of the JP1/AJS3 service terminate.

no

The process (ajsgwmasterd.exe for Windows and ajsgwmasterd for UNIX) that manages the scheduler service inter-communication control process is not terminated.

In UNIX, if you start the JP1/AJS3 service by executing the jajs_spmd command with the -HA option specified when using a logical host in a cluster configuration, operation can continue. This is because you can use functions other than the execution order control function for root jobnets between scheduler services.

Default value

no

Recommended value

Default value

When the setting takes effect

When the JP1/AJS3 service starts

(110) "GWRESTARTCOUNT" = dword:number-of-restarting-scheduler-service-inter-communication-control-process

Use this parameter to specify the number of times automatic restart is to be attempted if the scheduler service inter-communication control process terminates abnormally.

Specifiable values

A hexadecimal value from 0 to 3 (0 to 3 in decimal)

Default value

dword:00000003 (3 in decimal)

Recommended value

Default value

When the setting takes effect

When the JP1/AJS3 service starts

2.3 Setting up the job execution environment

This section describes the environment setting parameters for the job execution environment.

2.3.1 List of the environment setting parameters for the job execution environment

The job execution environment requires different settings in the manager environment (JP1/AJS3 - Manager) and the agent environment (JP1/AJS3 - Agent).

The table below lists the environment setting parameters to be used to set the job execution environment in the manager environment (JP1/AJS3 - Manager) and the agent environment (JP1/AJS3 - Agent).

The job execution control manager that is started is determined by the database configuration of JP1/AJS3.

For the standard composition:

The job execution control manager for scheduler services, which executes PC jobs, Unix jobs, action jobs, and custom jobs and starts them for each scheduler service

The job execution control manager for submit jobs, which executes queue jobs and submit jobs

For the compatible ISAM configuration:

The job execution control manager for the compatible ISAM configuration, which executes PC jobs, Unix jobs, action jobs, custom jobs, queue jobs, and submit jobs

For which job execution manager type you need to specify an environment setting parameter, see the Applicable manager column.

Some environment setting parameters for scheduler services have two definition keys. One definition key is used to set a value common to all scheduler services (SCHEDULER is part of a key name). The other definition key is used to set a different value for each scheduler service (scheduler-service-name is part of a key name). If you specify both definition keys, the definition key for setting a different value for each scheduler service is valid.

For definition keys used to set a common value for the scheduler services, you will see the following text: For scheduler service (common). For definition keys used to set different values for the scheduler services, you will see the following text: For scheduler service (individual).

The job execution control managers for submit jobs and the compatible ISAM configuration reference the same environment setting parameters. In the Definition key column, you will see the following text: For submit jobs and the compatible ISAM configuration.

To determine whether an environment setting parameter is to be set in Windows or UNIX, see the Applicable OS column. To determine whether an environment setting parameter is to be set in the manager environment (JP1/AJS3 - Manager) or the agent environment (JP1/AJS3 - Agent), see the Applicable product column.

Cautionary note on limiting resources in the job execution environment for UNIX

If you limit the resources for jobs executed from job execution control, the system might not be able to execute the jobs correctly, depending on the values specified in the environment setting parameters. For example, if you set 0 for the upper limit of the stack segment size, the system might not be able to execute jobs.

Therefore, make sure that you specify either limit values that have sufficient margin or do not specify limits. If you want to set a limit, first execute the ps command to check the segment size and CPU time, and then determine the values to be specified based on the data. Note, however, that even if you do not set limits, it does not mean there are no limits on resources. It only means that JP1/AJS3 does not explicitly set limits, and the default limits of the system (the one in which JP1/AJS3 was started) are in effect.

There are some environment setting parameters that are not subject to the OS limits.

If a value larger than the default limit is specified, the job execution user must have the appropriate permission (superuser). If the job execution user does not have the appropriate permission, the resource limit is not set when a job is executed and a warning message (KAVU3587-W) is output to the integrated trace log. That message reports that the job is executed with the default limit.

Limits placed on resources also apply to any child processes created by the job process (unless specific limits are set on a child process).

For AIX and Linux, although you use /etc/security/limits (In Linux, /etc/security/limits.conf) to define resource limits for the user who executes the job, those values do not take effect when a job is executed. In this case, you need to define resource limits for the user when JP1/AJS3 (root) is started. For details, see 7.4 Notes on using Unix jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

Table 2‒4: Environment setting parameters (job execution environment setting)

No.

Definition key

Environment setting parameter

Definition

Applicable manager

Applicable OS

Applicable product

1

[{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Process]#

"WorkPath"=

Work directory name when a manager process is executed

C

Windows

UNIX

M

2

"IsHA"=

Definition for cluster environment setup for manager processes

C, S

Windows

UNIX

M

3

[{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Database]#

"DatabasePath"=

Name of the directory used to store the database

C

Windows

UNIX

M

4

"PreserveTerm"=

Number of days that job execution results are retained

C

Windows

UNIX

M

5

"StandardTime"=

Standard time for deleting job information

C

Windows

UNIX

M

6

"FlashOption"=

Data file update mode

C

Windows

UNIX

M

7

"DeleteFlashOption"=

Asynchronous option for job information deletion

C

Windows

UNIX

M

8

"PreserveMinute"=

Retention period for information when 0 is specified as the number of days for retaining job information

C

Windows

UNIX

M

9

"StartUpDelete"=

Option for suppressing job information deletion when the JP1/AJS3 service starts

C

Windows

UNIX

M

10

"ColdStartMode"=

Database initialization when the JP1/AJS3 service is cold-started

C

Windows

UNIX

M

11

[{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Queue]#

"MaximumQueue"=

Maximum number of definable queues

C

Windows

UNIX

M

12

For scheduler service (common):

[{JP1_DEFAULT|logical-host-name}\JP1AJS2\SCHEDULER\QUEUE\MANAGER\Job]#

For scheduler service (individual):

[{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name\QUEUE\MANAGER\Job]#

For submit jobs and the compatible ISAM configuration:

[{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Job]#

"MaximumContentJob"=

Maximum number of jobs in the system

C, S

Windows

UNIX

M

13

"AlartContentJob"=

Number of warning jobs in the system

C, S

Windows

UNIX

M

14

"ReceiveFileSizeStatus"=

Behavior when the size of the job result file or transfer file has reached the upper limit

C, S

Windows

UNIX

M

15

"LimitReceiveFileSize"=

Upper limit on the size of the job result file or transfer file

C, S

Windows

UNIX

M

16

"ReceiveFileOption"=

Definition for preventing duplicated reception of the job result file

C, S

Windows

UNIX

M

17

"QueuingJobRecoveryTime"=

Length of time an agent waits for recovery from a failure occurring in a queuing job

C, S

Windows

UNIX

M

18

"ExecutingJobRecoveryTime"=

Length of time an agent waits for recovery from a failure occurring in a running job

C, S

Windows

UNIX

M

19

"MaximumExecJobLogOption"=

Setting for whether to output a message confirming that the maximum number of concurrently executable jobs has been reached

C, S

Windows

UNIX

M

20

"MaximumExecJobLogInterval"=

Interval for outputting a message confirming that the maximum number of concurrently executable jobs has been reached

C, S

Windows

UNIX

M

21

"PreventChangeJobOrder"=

Setting for preventing changes to the execution order of submit jobs

C

Windows

UNIX

M

22

"EnumJobSaveMemory"=

Setting for reducing the memory consumed by the job execution control manager when job information is enumerated

C

Windows

UNIX

M

23

"ExecutingJobChangeStatus"=

Setting for placing all jobs that are being executed in an end status when a communication error occurs

C, S

Windows

UNIX

M

24

For scheduler service (common):

[{JP1_DEFAULT|logical-host-name}\JP1AJS2\SCHEDULER\QUEUE\MANAGER\Network]#

For scheduler service (individual):

[{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name\QUEUE\MANAGER\Network]#

For submit jobs and the compatible ISAM configuration:

[{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Network]#

"ConnectTimeout"=

Definition of the TCP/IP connection timeout value on the job execution control manager

C, S

Windows

UNIX

M

25

"CommunicateRetryCount"=

Definition of the number of TCP/IP connection error retries on the job execution control manager

C, S

Windows

UNIX

M

26

"CommunicateRetryInterval"=

Definition of the TCP/IP connection error retry interval on the job execution control manager

C, S

Windows

UNIX

M

27

For scheduler service (common):

[{JP1_DEFAULT|logical-host-name}\JP1AJS2\SCHEDULER\QUEUE\MANAGER\Agent]#

For scheduler service (individual):

[{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name\QUEUE\MANAGER\Agent]#

For submit jobs and the compatible ISAM configuration:

[{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Agent]#

"MaximumAgent"=

Maximum number of definable agents

C

Windows

UNIX

M

28

"ObserveInterval"=

Agent monitoring interval

C, S

Windows

UNIX

M

29

"AutoCreate"=

Control flag for automatic agent definition

C, S

Windows

UNIX

M

30

"AutoCreateExecJobs"=

Maximum number of concurrently executable jobs when an agent is defined automatically

C, S

Windows

UNIX

M

31

"AutoCreateMaxJobs"=

Maximum number of jobs when an agent is defined automatically

C

Windows

UNIX

M

32

"AutoCreateWarnJobs"=

Warning value for the number of jobs when an agent is defined automatically

C

Windows

UNIX

M

33

"AutoCreatePriority"=

Agent priority when an agent is defined automatically

C

Windows

UNIX

M

34

"LeastRecentlyUsed"=

Definition of the method for determining the agent host to which jobs are distributed

C, S

Windows

UNIX

M

35

[{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Resource]#

"MaximumResource"=

Maximum number of definable execution-locked resources

C

Windows

UNIX

M

36

[{JP1_DEFAULT|logical-host-name}\JP1NBQAGENT\Process]#

"WorkPath"=

Name of the work directory when an agent process is executed

--

Windows

UNIX

M, A

37

"IsHA"=

Definition for cluster environment step for agent processes

--

Windows

UNIX

M, A

38

[{JP1_DEFAULT|logical-host-name}\JP1NBQAGENT\Job]#

"IsExecFindExecutable"=

Definition for executing a job with a long file name

--

Windows

M, A

39

"LoadUserProfile"=

Definition for whether a user profile is loaded

--

Windows

M, A

40

"IsAccessTokenCache"=

Setting for reusing an access token when a job is executed

--

Windows

M, A

41

"DISABLE_FS_REDIRECTION"=

Setting for disabling file system redirection when jobs are executed in the WOW64 environment

--

Windows

M, A

42

"ENABLE_LONG_EXT"=

Setting for whether to execute a job specified for an executable file whose extension is 4 bytes or more in an application associated with the executable-file extension

--

Windows

M, A

43

"IsLimitCoreSize"=

Limit flag for the maximum core file size for each process

--

UNIX

M, A

44

"LimitCoreSize"=

Maximum core file size for each process

--

UNIX

M, A

45

"IsLimitDataSize"=

Limit flag for the maximum data segment size for each process

--

UNIX

M, A

46

"LimitDataSize"=

Maximum data segment size for each process

--

UNIX

M, A

47

"IsLimitFileSize"=

Limit flag for the maximum permanent file size for each process

--

UNIX

M, A

48

"LimitFileSize"=

Maximum permanent file size for each process

--

UNIX

M, A

49

"IsLimitMemorySize"=

Limit flag for the maximum memory size for each process

--

UNIX

M, A

50

"LimitMemorySize"=

Maximum memory size for each process

--

UNIX

M, A

51

"IsLimitStackSize"=

Limit flag for the maximum stack segment size for each process

--

UNIX

M, A

52

"LimitStackSize"=

Maximum stack segment size for each process

--

UNIX

M, A

53

"IsLimitCpuTime"=

Limit flag for the maximum CPU time for each process

--

UNIX

M, A

54

"LimitCpuTime"=

Maximum CPU time for each process

--

UNIX

M, A

55

"IsLimitWorkSize"=

Limit flag for the maximum working set size for each process

--

UNIX

M, A

56

"LimitWorkSize"=

Maximum working set size for each process

--

UNIX

M, A

57

"IsLimitNoFile"=

Limit flag for the maximum number of file descriptors for each process

--

UNIX

M, A

58

"LimitNoFile"=

Maximum number of file descriptors for each process

--

UNIX

M, A

59

"PipeComTimeout"=

Definition of the pipe communication timeout value for agents

--

UNIX

M, A

60

"AfterForkPipeTimeout"=

Definition of the timeout value for the job process execution ready notification

--

UNIX

M, A

61

"IsCacheCmdSearchPath"=

Flag for specifying whether to cache the value in the command search path

--

UNIX

M, A

62

"IsUseWorkPath"=

Flag for specifying whether to change the work (current) path when the job is executed

--

UNIX

M, A

63

"IsSigchldDefault"=

Definition for changing the setting of child processes started by JP1/AJS3 to the SIG_DFL setting whereby the SIGCHLD signal is received

--

UNIX

M, A

64

"FileAccessPermissionMode"=

Setting of the method for checking the file access permission when a Unix job is executed

--

UNIX

M, A

65

[{JP1_DEFAULT|logical-host-name}\JP1NBQAGENT\Network]#

"NotfyJobStateInterval"=

Interval for resending the job result file

--

Windows

UNIX

M, A

66

"NotfyJobStateCount"=

Number of times that the job result file is resent

--

Windows

UNIX

M, A

67

"ConnectTimeout"=

Definition of the TCP/IP connection timeout value on the job execution control agent

--

Windows

UNIX

M, A

68

"CommunicateRetryCount"=

Definition of the number of TCP/IP connection error retries on the job execution control agent

--

Windows

UNIX

M, A

69

"CommunicateRetryInterval"=

Definition of the TCP/IP connection error retry interval on the job execution control agent

--

Windows

UNIX

M, A

70

"LogonUserRetryCount"=

Number of retries for obtaining access tokens when Standard is specified for Exec. service

--

Windows

M, A

71

"LogonUserRetryInterval"=

Retry interval for obtaining access tokens when Standard is specified for Exec. service

--

Windows

M, A

72

[{JP1_DEFAULT|logical-host-name}\JP1NBQAGENT\Variable]#

"variable-name"=

Installation directory of an execution program indicated by the variable name on each applicable host

--

Windows

UNIX

M, A

73

[{JP1_DEFAULT|logical-host-name}\JP1NBQCLIENT\PathEnv]#

"All Users"=

Search path for a transfer file

--

Windows

UNIX

M, A

74

"JP1-user-name"=

Search path for a transfer file

--

Windows

UNIX

M, A

75

[{JP1_DEFAULT|logical-host-name}\JP1NBQCLIENT\Network]#

"ConnectTimeout"=

Definition of the TCP/IP connection timeout value for the commands and schedulers used to execute jobs

--

Windows

UNIX

M, A

76

"CommunicateRetryCount"=

Definition of the number TCP/IP connection error retries for the commands and schedulers used to execute jobs

--

Windows

UNIX

M, A

77

"CommunicateRetryInterval"=

Definition of the TCP/IP connection error retry interval for the commands and schedulers used to execute jobs

--

Windows

UNIX

M, A

78

"CommunicateTimeout"=

Connection timeout period for the manager process of job execution control

--

Windows

UNIX

M, A

79

[{JP1_DEFAULT|logical-host-name}\JP1NBQCLIENT\Process]#

"MacroOptionReplaceMode"=

Setting for whether to replace the passing information in a macro variable with the NULL character string

--

Windows

UNIX

M, A

80

"IsHA"=

Definition for cluster environment setup for the commands and schedulers used to execute jobs

--

Windows

UNIX

M, A

81

"PassingInfoUsePreRc"=

Settings for using the return value of the preceding job in the passing information setting jobs

--

Windows

UNIX

M

82

For scheduler service (common)

[{JP1_DEFAULT|logical-host-name}\JP1AJS2\SCHEDULER\QUEUE\NOTIFY\Network]#

For scheduler service (individual)

[{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name\QUEUE\NOTIFY\Network]#

For the compatible ISAM configuration:

[{JP1_DEFAULT|logical-host-name}\JP1NBQNOTIFY\Network]#

"ConnectTimeout"=

Definition of the TCP/IP connection timeout value in the status reporting process for job execution control

--

Windows

UNIX

M

83

"CommunicateRetryCount"=

Definition of the number TCP/IP connection error retries in the status reporting process for job execution control

--

Windows

UNIX

M

84

"CommunicateRetryInterval"=

Definition of the TCP/IP connection error retry interval in the status reporting process for job execution control

--

Windows

UNIX

M

85

[{JP1_DEFAULT|logical-host-name}\JP1NBQNOTIFY\Process]#

"IsHA"=

Definition for cluster environment setup for the status reporting process for job execution control

--

Windows

UNIX

M, A

86

[{JP1_DEFAULT|logical-host-name}\JP1NBQAGENT\Job]#

"MergeEnvMode"=

Definition for whether an environment variable in a job definition is enabled when the name is the same as a system environment variable name

--

Windows

M, A

87

"UACAdministratorsExec"=

Setting for executing jobs as a user with administrator permissions when UAC is enabled

--

Windows

M, A

88

"GetPasswd_RetryCount"=

Number of retry attempts when an attempt to acquire user information from the OS password file has failed

--

UNIX

M, A

89

"GetPasswd_RetryInterval"=

Retry interval when an attempt to acquire user information from the OS password file has failed

--

UNIX

M, A

90

"IgnoreResultFileError"=

Operation if an error occurs during transfer processing of a job result file and Standard is specified for Exec. Service

--

Windows

UNIX

M, A

91

"PreventResultFileLack"=

Setting for ensuring that data generated by jobs is output to result files

--

Windows

M, A

Legend:

C: Job execution control manager for submit jobs and the compatible ISAM configuration

S: Job execution control manager for scheduler services

M: JP1/AJS3 - Manager

A: JP1/AJS3 - Agent

--: Not applicable

#

Specify JP1_DEFAULT for the physical host. For logical-host-name, specify the name of a logical host.

The following explains each of the environment setting parameters.

Parameters that are not described here are used for maintenance purposes. Do not change their values.

The default value is used whenever a value is not specified for an environment setting parameter.

2.3.2 Details of the environment setting parameters for the job execution environment

(1) "WorkPath" = "name-of-work-directory-used-when-manager-process-is-running"

The name of the work directory used when the manager process is running. Use this parameter to specify the name of the work directory used to manage job execution. Specify a full path name.

If there is not enough space on the disk that contains the default directory, specify a directory on a disk that has enough space.

Specifiable values

A character string of no more than 180 bytes

Default value

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

For a physical host:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\tmp

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For a logical host:

shared-folder\jp1ajs2\tmp

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

For a physical host:

JP1/AJS3-Manager-installation-folder\tmp

For a logical host:

shared-folder\jp1ajs2\tmp

For Windows Server 2003:

For a physical host:

JP1/AJS3-Manager-installation-folder\tmp

For a logical host:

shared-folder\jp1ajs2\tmp

In UNIX:

For a physical host:

/var/opt/jp1ajs2/tmp

For a logical host:

shared-directory/jp1ajs2/tmp

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(2) "IsHA" = dword:definition-for-cluster-environment-setup-for-the-manager-process

Use this parameter to specify the definition for setting up a cluster environment for the job execution control manager process. Specify this parameter only to stop cluster use.

Specifiable values

0

Specifies to stop cluster use.

1

If you execute setup when operating a cluster system, this value is automatically set to the parameter for the physical and logical hosts.

Default value

dword:00000000 (0 in decimal)

Recommended value

None

When the setting takes effect

After JP1/AJS3 is restarted

(3) "DatabasePath" = "name-of-the-directory-used-to-store-the-database"

Use this parameter to specify the name of the directory used to store the ISAM file, which is the file to which job execution environment information or job information is written. Specify a full path name.

If there is not enough space on the disk that contains the default directory, specify a directory on a disk that has enough space.

Specifiable values

A character string of no more than 180 bytes

Default value

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

For a physical host:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\database\queue

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For a logical host:

shared-folder\jp1ajs2\database\queue

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

For a physical host:

JP1/AJS3-Manager-installation-folder\database\queue

For a logical host:

shared-folder\jp1ajs2\database\queue

For Windows Server 2003:

For a physical host:

JP1/AJS3-Manager-installation-folder\database\queue

For a logical host:

shared-folder\jp1ajs2\database\queue

In UNIX:

For a physical host:

/var/opt/jp1ajs2/database/queue

For a logical host:

shared-directory/jp1ajs2/database/queue

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

In UNIX:

Do not create a symbolic link for a file created in the directory specified in this parameter. Reorganization will break the link because the file is re-created. If you want to create a symbolic link, use the directory specified in this parameter instead.

Do not use NFS or a network drive as the directory to be specified here.

For this parameter, you cannot specify a directory mounted on an NFS file system or a similar file system connected to a network or a network drive.

(4) "PreserveTerm" = dword:number-of-days-job-information-retained

Use this parameter to specify the number of days that job execution results are retained.

Change this value as necessary if the number of executed jobs will exceed 20,000 before the specified number of retention days (recommended value) expires.

The settings for this parameter are not applied to event jobs.

Specifiable values

A hexadecimal value (in days) from 0 to 3E7 (0 to 999 in decimal)

If you specify dword:00000000 (zero days), the execution result information is deleted when execution of the job is complete.

For details about the setting of the retention period for job information when the specified value is 0, see 7.1.9 Setting the retention period for job information in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

Default value

dword:00000007 (7 days)

During a new installation and setup of JP1/AJS3, dword:00000001 is set.

Recommended value

dword:00000001 (one day)

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The number of days that job information is retained is the number of days that job information saved in the job execution environment database is retained. If you decrease the number of retention days, there is no effect on the number of saved generations of a jobnet that are managed by the scheduler database.

After you reduce the number of retention days, if a large amount of job information is to be deleted at the next standard time for deleting job information or at JP1/AJS3 service restart, this process might conflict with the job information deletion processing. In such a case, the job execution performance might degrade, or the system load might increase.

Be careful when changing this parameter, such as changing the value if fewer jobs are being executed or gradually reducing the number of retention days for job information.

In a standard configuration, the number of jobs that can be registered in the database for QUEUE jobs and submit jobs is less than 200,000.

The job execution result information that is registered in the database is the result information for the number of jobs executed for the number of retention days plus one more day. For example, if the number of jobs executed in one day is 10,000, and the number of retention days is 10 days, the information for 110,000 jobs is registered.

Specify the number of retention days for job information so that the number of job execution results that are to be registered in the database is less than 200,000.

(5) "StandardTime" = dword:standard-time-at-which-job-information-deleted

Use this parameter to specify the time at which job execution result information is to be deleted. Note, however, that the job execution result information is also deleted when the JP1/AJS3 service starts. In this case, the system uses the JP1/AJS3 service start time as the base time to delete all job execution result information that is older than the number of days specified for retaining the information. Thereafter, the system deletes the job execution result information at the time specified in this parameter.

If job execution performance degrades because many jobs are executed while job information is being deleted, change the base time to at time when fewer jobs are being executed.

You can also specify settings so that job information is not deleted when the JP1/AJS3 service is started. For details, see 7.1.10 Setting for disabling deletion of job information when JP1/AJS3 starts in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

The setting for this parameter is not applied to event jobs.

Specifiable values

Using 0:00 as the base time, specify a relative time in hexadecimal from 0:00 to 23:59 (in minutes).

For example, to set 1:00, specify dword:0000003c (1:00 = 60 minutes).

Default value

dword:00000000 (0:00)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(6) "FlashOption" = dword:data-file-update-mode

Use this parameter to specify whether to permit synchronous writing when an ISAM file is updated.

Specifiable values

0

Data is written to a disk in response to OS buffering. There is no synchronization with JP1/AJS3 processing.

Specify 0 when job execution performance is more important than the reliability of database access in the job execution environment provided by writing data to a disk with OS buffering. However, in a cluster configuration, specifying this value is not recommended because reliability degrades.

1

Synchronous writing is always performed when a file is updated. This writing mode improves reliability, but reduces performance.

Default value

dword:00000001 (synchronization mode)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(7) "DeleteFlashOption" = dword:asynchronous-option-for-job-information-deletion

Use this parameter to specify whether to delete job information in asynchronous mode.

For details about job information deletion processing, see 7.1.8 Option for deleting job information asynchronously in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

Specifiable values

0

Job information is deleted in asynchronous mode.

1

Job information is deleted in synchronous mode.

Default value

dword:00000001 (1 in decimal) (synchronous mode)

During a new installation and setup of JP1/AJS3, 0 is set.

Recommended value

dword:00000000 (0 in decimal) (asynchronous mode)

When the setting takes effect

After JP1/AJS3 is restarted

(8) "PreserveMinute" = dword:retention-period-for-job-information-when-the-number-of-days-for-retaining-job-information-is-0

Use this parameter to specify how long you want to retain job information after a job has been executed when 0 is specified as the number of days for retaining job information.

For details about job information deletion processing, see 7.1.9 Setting the retention period for job information in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide or 7.1.8 Option for deleting job information asynchronously in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

Specifiable values

A hexadecimal value (in minutes) from 0000000A to 000005A0 (10 to 1,440 in decimal)

Default value

dword:0000000A (10 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(9) "StartUpDelete" = dword:option-for-suppressing-job-information-deletion-at-JP1/AJS3-service-startup

Use this parameter to specify whether to suppress job information deletion at JP1/AJS3 service startup when 1 or more is specified as the number of days for retaining job information.

For details about job information deletion processing, see 7.1.10 Setting for disabling deletion of job information when JP1/AJS3 starts in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide or 7.1.8 Option for deleting job information asynchronously in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

Specifiable values

0

When the JP1/AJS3 service starts, the processing that deletes job information deletes job information whose retention period (number of days) has expired when the standard time for deleting job information arrives.

When the JP1/AJS3 service starts, job information whose retention period has expired in the period from the standard time for deleting job information to the time that the JP1/AJS3 service started is not deleted.

If job information was not deleted when the previous standard time for deleting job information arrived because the JP1/AJS3 service was not running, job information whose retention period had expired when the base time arrived might remain. If so, only the remaining job information is deleted when the JP1/AJS3 service starts.

1

When the JP1/AJS3 service starts, job information deletion processing deletes all job information whose retention period has expired at the time that the JP1/AJS3 service starts.

When the JP1/AJS3 service starts, job information is also deleted if the retention period of the job information has expired in the period from the standard time for deleting job information to the time that the JP1/AJS3 service started.

If job information was not deleted when the previous standard time for deleting job information arrived because the JP1/AJS3 service was not running, job information whose retention period had expired when the base time arrived might remain. If so, any remaining job information is also deleted when the JP1/AJS3 service starts.

2

Job information deletion processing that occurs when the JP1/AJS3 service starts is suppressed. However, if the JP1/AJS3 service is set to stop at the same time as the standard time for deleting job information, do not specify this value.

Note that if the JP1/AJS3 service is not running when the standard time for deleting job information arrived, job information whose retention period had expired when the base time arrived will never be deleted. As a result, the disk space required by the job execution environment database increases, and this increase might prevent the JP1/AJS3 service from starting, or prevent a job from being executed.

Default value

dword:00000001 (1 in decimal)

During a new installation and setup of JP1/AJS3, 0 is set.

Recommended value

dword:00000000 (0 in decimal)

When the setting takes effect

After JP1/AJS3 is restarted

(10) "ColdStartMode" = "{clear|noclear}"

Use this parameter to specify whether to initialize the job information of the job execution environment database when the JP1/AJS3 service is cold-started.

Specifiable values

clear

The job information of the job execution environment database is initialized when the JP1/AJS3 service is cold-started, unless there has been a scheduler service that has been set to not start automatically.

noclear

The job information of the job execution environment database is not initialized when the JP1/AJS3 service is cold-started. Specify this value when you want current operation to be consistent with that of 06-71 or earlier, which does not initialize the database.

Default value

clear

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(11) "MaximumQueue" = dword:maximum-number-of-definedable-queues

Use this parameter to specify the maximum number of queues that can be defined.

Change this parameter as necessary if the number of queues defined for the manager might exceed the recommended value.

Specifiable values

A hexadecimal value from 1 to 2000 (1 to 8,192 in decimal)

Default value

dword:00000096 (150 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The maximum number of queues that can be used on one manager includes the number of default queues used on the agent. The maximum number of agents specified in the MaximumAgent environment setting parameter equals the maximum number of default queues. Specify a larger value in the MaximumQueue environment setting parameter than the value specified in the MaximumAgent environment setting parameter.

The following shows the relationship between the maximum number of queue definitions you specify here and the maximum number of queues that can be used on one manager:

value-specified-for-the-MaximumQueue-environment-setting-parameter (a value greater than the value in the MaximumAgent environment setting parameter) = maximum-number-of-queues-that-can-be-used-on-one-manager

(12) "MaximumContentJob" = dword:maximum-number-of-jobs-in-the-system

Use this parameter to specify the maximum number of jobs that the system can hold in its work area.

Change this value as necessary if the system has to register and execute a large number of jobs in a short period.

When you start the JP1/AJS3 service, the system allocates a job information area in memory that can accommodate information for the number of jobs specified here. Specify a value that is sufficient to cover the peak number of queuing jobs during operation.

If all job information areas are being used (when the same number of jobs as the value specified for this parameter are queued), the submit processing fails. In addition, the value of this parameter is applied only to queuing jobs (including those whose status is waiting for time and on hold) and running jobs. The value is not applied to jobs that have ended, event jobs, and judgment jobs.

Specifiable values

A hexadecimal value from 1 to 14000 (1 to 81,920 in decimal)

Default value

For the job execution control manager of the scheduler service

dword:00001770 (6,000 in decimal)

For the job execution control manager of the submit job and the compatible ISAM configuration

dword:000007D0 (2,000 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(13) "AlartContentJob" = dword:number-of-warning-jobs-in-the-system

Use this parameter to specify the threshold at which a warning message will be output according to the use status of the job information area in the work area of the system.

Change this parameter as necessary if you have changed the MaximumContentJob environment setting parameter (maximum number of jobs in the system).

The value of this parameter is applied only to queuing jobs (including those whose status is waiting for time and on hold) and running jobs. The value is not applied to jobs that have ended, event jobs, and judgment jobs.

Specifiable values

A hexadecimal value from 1 to 14000 (1 to 81,920 in decimal)

Default value

For the job execution control manager of a scheduler service

dword:000012C0 (4,800 in decimal)

For the job execution control manager of a submit job and the compatible ISAM configuration

dword:00000640 (1,600 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(14) "ReceiveFileSizeStatus" = dword:behavior-when-the-received-file-size-reaches-the-upper-limit

Use this parameter to specify the behavior when the size of a file being received reaches the upper limit.

For details, see 6.2.7 Placing restrictions on file reception in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.7 Placing restrictions on file reception in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

0

The upper limit for received files size is checked. If the upper limit is reached, the following message is output, but all file data is received. Even if the file size exceeds the upper limit, the job status does not change, and the job end status on the agent host is inherited.

For a result file:

Message KAVU4294-I

For a transfer file:

Message KAVU2243-I

1

The upper limit for received files size is checked. If the upper limit is reached, receive processing is canceled and the job status changes.

A result file is received until the upper limit for file size (LimitReceiveFileSize environment setting parameter) is reached. Thereafter, data that exceeds the upper limit is discarded, and the end status changes to Ended abnormally. For a transfer file, no file data is received, and the end status changes to Failed to start. For details about the return code and end status, see 6.2.7(3) Operation performed if the size of received files exceeds the maximum in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.7(3) Operation performed if the size of received files exceeds the maximum in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

If the upper limit has been reached, the following message is output:

For a result file:

Message KAVU4296-E

For a transfer file:

Message KAVU2244-E

2

The upper limit for received file size is checked. If the upper limit is reached, receive processing is canceled, and the job status changes.

Result files are received until the upper limit for file size (LimitReceiveFileSize environment setting parameter) is reached. Thereafter, data that exceeds the upper limit is discarded, and the end status changes to Ended with warning. However, if the job status on the agent host is Ended abnormally, that status is inherited. For a transfer file, the end status changes to Failed to start, and no file data is received. For the return code and end status, see 6.2.7(3) Operation performed if the size of received files exceeds the maximum in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.7(3) Operation performed if the size of received files exceeds the maximum in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

If the upper limit has been reached, the following message is output:

For a result file:

Message KAVU4295-W

For a transfer file:

Message KAVU2244-E

3

The upper limit for received files size is checked. If the upper limit is reached, receive processing is canceled.

Result files are received until the upper limit for file size (LimitReceiveFileSize environment setting parameter) is reached. Thereafter, all file data that exceeds the upper limit is discarded. For a transfer file, all file data is discarded. The end status on the agent host is inherited as the end status for the job. For the return code and end status, see 6.2.7(3) Operation performed if the size of received files exceeds the maximum in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.7(3) Operation performed if the size of received files exceeds the maximum in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

If the upper limit is reached, the following message is output:

For a result file:

Message KAVU4294-I

For a transfer file:

Message KAVU2243-I

This specification allows a job to end normally even if the limit is exceeded. However, because the files that are created are not complete, you must make sure beforehand that the incomplete files will not cause any problems if they are referenced and used in a succeeding job.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(15) "LimitReceiveFileSize" = dword:limit-on-file-size

Use this parameter to specify the upper limit for the size of received files.

If the size of a transfer file or a result file used when a job is executed exceeds the value estimated for operation, limit the size of files received by the manager host. We recommend that you set a limit of approximately five megabytes, depending on operational requirements.

If multiple transfer files are to be sent at one time, this setting enables the total size of the files to be checked against the limit. The value used to check a result file is the total of the sizes of the standard output file and the standard error output file.

Note that the limit might be subject to an error in a range of plus or minus several hundred bytes.

The following shows how to estimate file size (in bytes):

File count

(file-name-length + file-size + (12 x file-line-count) + 100)

For details, see 6.2.7 Placing restrictions on file reception in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.7 Placing restrictions on file reception in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (in bytes) from 80000 to 40000000 (524,288 to 1,073,741,824 in decimal)

Default value

dword:00500000 (5,242,880 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary notes

This setting is rounded in increments of 8000 (32,768 in decimal). For example, if you specify 80001 (524,289 in decimal), the valid value is 88000 (557,056 in decimal).

For action jobs, if the size of the information to be output by JP1/AJS3 is less than the lowest value in the range that can be specified (524,288 bytes), no information is output. Note, however, that the size could be less if you run a job in UNIX and standard error output is output for a login script of a job execution OS user or the system.

(16) "ReceiveFileOption" = dword:definition-for-preventing-duplicated-reception-of-the-job-result-file

Use this parameter to specify whether to prevent duplicated reception of the job result file.

For details, see 6.2.6 Preventing duplicated reception of job result files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.6 Preventing duplicated reception of job result files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

0

Duplicated reception of the job result file is not prevented.

1

Duplicated reception of the job result file is prevented.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(17) "QueuingJobRecoveryTime" = dword:recovery-time-for-queuing-jobs-when-agent-has-failed

Use this parameter to specify the recovery time for queuing jobs when an agent has failed.

For details, see 6.2.12 Changing the wait time for recovery when an agent has failed in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.12 Changing the wait time for recovery when an agent has failed in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (in seconds) from 0000001E to 00000E10 (30 to 3,600 in decimal).

A period of no jobs being executed might occur. This is possible if the system detects a job error several tens of seconds after the error occurred because the system monitors job errors at intervals of several tens of seconds.

Default value

dword:00000258 (600 in decimal, which is 10 minutes)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(18) "ExecutingJobRecoveryTime" = dword:recovery-time-for-running-jobs-when-agent-has-failed

Use this parameter to specify the recovery time for running jobs when an agent has failed.

For details, see 6.2.12 Changing the wait time for recovery when an agent has failed in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.12 Changing the wait time for recovery when an agent has failed in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (in seconds) from 0000001E to 00000E10 (30 to 3,600 in decimal)

Default value

dword:00000258 (600 in decimal, which is 10 minutes)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

By default, the system checks the status of running jobs a maximum of three times before it detects a job abnormality. If you specify a value that is smaller than the agent monitoring interval for this parameter, the wait time for recovery elapses before the system checks the status of running jobs. In that case, the system checks the status of running jobs a maximum of two times. The detailed calculation of the total time required to detect a failure is as follows:

Total-time-elapsing-before-a-failure-is-detected

(agent-monitoring-interval x 1)

+ (communication-time x 2)

+ length-of-time-between-the-failure-occurrence-and-the-first-check-of-the-job-status

If you reduce the agent monitoring interval, the retry interval for TCP/IP connection errors, and the number of retries, the total time elapsing before a failure is detected decreases further.

For details about setting the agent monitoring interval, see (28) ObserveInterval.

For details about setting the retry interval and number of retries for TCP/IP connection errors, see 6.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Polling using the agent monitoring interval is executed for each agent host. If you shorten the agent monitoring interval and increase the number of pollings, the number of times communication occurs increases in proportion to the number of agent hosts. Keep this in mind when you change the agent monitoring interval. Similar care is also required when you change the retry interval and the number of retries for TCP/IP connection errors.

(19) "MaximumExecJobLogOption" = dword:setting-for-whether-to-output-a-message-confirming-that-the-maximum-number-of-concurrently-executable-jobs-has-been-reached

Use this parameter to specify whether to output a message confirming that the maximum number of concurrently executable jobs has been reached.

For details, see 6.2.13 Outputting a message that reports that the maximum number of concurrently executable jobs has been reached in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.13 Outputting a message that reports that the maximum number of concurrently executable jobs has been reached in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

0

A message confirming that the maximum number of concurrently executable jobs has been reached, is not output.

1

A message confirming that the maximum number of concurrently executable jobs has been reached, is output.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(20) "MaximumExecJobLogInterval" = dword:interval-for-outputting-a-message-confirming-that-the-maximum-number-of-concurrently-executable-jobs-has-been-reached

Use this parameter to specify the interval for outputting a message to confirming that the maximum number of concurrently executable jobs has been reached.

After the first KAVU4310-I message is output, the next KAVU4310-I message is not output for the period specified here (10 minutes by default) even though jobs remain queued. If jobs still remain queued when the specified interval has elapsed, another KAVU4310-I message is output as specified.

For details, see 6.2.13 Outputting a message that reports that the maximum number of concurrently executable jobs has been reached in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.13 Outputting a message that reports that the maximum number of concurrently executable jobs has been reached in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (in seconds) from 0000003C to 00015180 (60 to 86,400 in decimal)

Default value

dword:00000258 (600 in decimal, which 10 minutes)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(21) "PreventChangeJobOrder" = dword:setting-for-preventing-changes-to-the-execution-order-of-submit-jobs

Use this parameter to specify whether to prevent changes to the execution order of submit jobs.

For details, see 7.1.11 Setting for preventing changes in the submit job execution order in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

Specifiable values

0

Changes to the execution order of submit jobs are not prevented.

1

Changes to the execution order of submit jobs are prevented.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

Specifying 1 for the PreventChangeJobOrder environment setting parameter only changes the job distribution processing. In addition to this setting, you must perform the following steps to prevent changes from being made to the execution order of submit jobs:

Make sure that only one agent is connected to the queue to which jobs are submitted.

Specify 1 for the maximum number of concurrently executable jobs for the agent.

Note that, because this setting controls the job execution order, job performance might be reduced by several percent.

(22) "EnumJobSaveMemory" = dword:setting-for-reducing-memory-consumed-by-the-job-execution-control-manager-when-job-information-is-enumerated

Use this parameter to specify whether to reduce the memory consumed by the job execution control manager when job information is enumerated.

For details, see 7.1.12 Setting to reduce memory usage by the job execution control manager (jpqman) when enumerating job information in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

Specifiable values

0

The job execution control manager consumes memory as needed for the number of enumerated job information items when job information is enumerated.

1

The memory consumed by the job control manager is reduced when job information is enumerated.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The following are estimates of memory consumption when job information is enumerated:

When 0 is set

The maximum amount of memory consumed is about 100 KB per job.

When 1 is set

The maximum amount of memory consumed is about 60 MB, regardless of the number of jobs for which information is enumerated.

(23) "ExecutingJobChangeStatus" = dword:setting-for-placing-all-running-jobs-in-the-end-status-when-a-communication-error-occurs

Use this parameter to specify whether to place all running jobs in the end status when a communication error occurs. Specify a hexadecimal value.

For details about definitions, see 6.2.20 Placing all running jobs in an end status when a communication error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.19 Placing all running jobs in an end status when a communication error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

0

Specify this value to place the jobs in the end status one by one if a communication error occurs during system monitoring of running jobs by polling.

1

Specify this value to place only those jobs on the execution agent among the jobs that are being executed in the same queue in the end status if a communication error occurs during the system monitoring of running jobs by polling.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(24) "ConnectTimeout" = dword:definition-of-the-TCP/IP-connection-timeout-value-on-the-job-execution-control-manager

Use this parameter to specify the TCP/IP connection timeout value.

For details about the definition, see 6.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (in milliseconds) from 00002710 to 000927C0 (10,000 to 600,000 in decimal)

Default value

dword:00015F90 (90,000 in decimal, which is 90 seconds)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary notes

If you decrease the connection timeout value, a timeout might occur before the connection is completed, resulting in a TCP/IP communication connection error.

Depending on the connection timeout specifications and the settings for the OS, a connection timeout might occur before the value specified for this parameter is reached.

(25) "CommunicateRetryCount" = dword:definition-of-the-number-of-retries-for-a-TCP/IP-connection-error-for-the-job-execution-control-manager

Use this parameter to specify the number of retries for a TCP/IP connection error.

For details about the definition, see 6.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value from 00000000 to 00000064 (0 to 100 in decimal)

Default value

dword:00000002 (2 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you increase the value for number of retries too much, unavoidable communication errors might cause the number of TCP/IP connection errors to increase.

(26) "CommunicateRetryInterval" = dword:definition-of-the-TCP/IP-connection-error-retry-interval-on-the-job-execution-control-manager

Use this parameter to specify the TCP/IP connection error retry interval.

For details about the definition, see 6.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (in seconds) from 00000001 to 0000012C (1 to 300 in decimal)

Default value

dword:00000014 (20 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you decrease the retry interval to so that it is too small, the communication retry interval will be too short. As a result, unavoidable communication errors might cause the number of TCP/IP connection errors to increase.

(27) "MaximumAgent" = dword:maximum-number-of-definable-agents

Use this parameter to specify the maximum number of agents that execute jobs requested by the JP1/AJS3 - Manager used to define jobs.

Change this value as necessary if the number of agents defined for the manager could exceed the recommended value.

An attempt to connect to more job-execution agents than the number of agents specified here will be rejected by the system.

Specifiable values

A hexadecimal value from 1 to 400 (1 to 1,024 in decimal)

Default value

dword:00000032 (50 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(28) "ObserveInterval" = dword:agent-monitoring-interval

Use this parameter to specify the interval for monitoring the agent on which you want to execute a job.

Change this parameter as necessary if you have adjusted the period of time for monitoring agent errors.

Specifiable values

A hexadecimal value (in seconds) from 3C to 15180 (60 to 86,400 in decimal)

Default value

dword:0000012C (300 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(29) "AutoCreate" = dword:control-flag-for-automatic-definition-of-an-agent

Use this parameter to specify whether to enable the function that automatically defines an agent.

You can use this function only if you execute PC jobs, Unix jobs, and action jobs, other than queueless jobs, that have been defined in a jobnet, or execute submit jobs that have been defined by using the jpqjobsub command. This function cannot be used for queue jobs and event jobs.

Even if the execution of a job fails, the created execution agent or agent is not lost. Also, execution agents or agents are still available even after a JP1/AJS3 restart.

About a execution agents that is to be created

The following are attributes of an execution agent to be created:

Name of the execution host: Same as the execution agent name

Maximum number of concurrently executable jobs: 5 for a full 24 hours

Job transfer restriction status: Enabled

Description: None

You can change the attributes of an execution agent by using the ajsagtalt command. For details about the ajsagtalt command, see ajsagtalt in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

About an agent that is to be created

The following is the attribute of an agent to be created:

Maximum number of concurrently executable jobs: 5 for a full 24 hours

The following are the attributes of the default queue of an agent to be created:

Maximum number of jobs: 100

Maximum number of warnings: 80

Queue entrance status: open

Queue exit status: open

Connection agent: local agent host

Priority of the agent: 1

You can change the attributes of the agent and default queue by using the jpqagtalt, jpqquealt, jpqqueopen, jpqqueclose, jpqagtlink, and jpqagtunlink commands. For details about these commands, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

You can customize beforehand the attributes of an execution agent or agent that will be created by using the function that automatically defines an agent from the common definition information. For details, see 6.2.3 Customizing the execution agent or agent attribute values created by the automatic agent definition function in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.3 Customizing the execution agent or agent attribute values created by the automatic agent definition function in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

If you specify this parameter, the settings apply to all the execution agent or agent attributes that are created by using the automatic agent definition function.

Specifiable values

0

No execution agents or agents are automatically defined.

1

Execution agents or agents are automatically defined.

If you specify 1, the automatic agent definition function is enabled for all the jobs that the job execution control manager for which this parameter is specified handles.

Default value

dword:00000000 (0 in decimal)

Recommended value

None

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary notes

Use this function only if absolutely necessary, such as when an error occurs on an existing execution agent or agent (job execution environment) and you need to quickly create a substitute execution agent or agent so that a job can be executed. Under normal circumstances, you should create a execution agent or agent before executing a job. If you need to add execution agents during operation, use the ajsagtadd command. If you need to add agents, use the jpqimport or jpqagtadd command.

When the function that automatically defines an agent is enabled, you need to execute a job as a JP1 user with both JP1_JPQ_User and JP1_JPQ_Admin permissions.

(30) "AutoCreateExecJobs" = dword:maximum-number-of-concurrently-executable-jobs-when-an-agent-host-is-defined-automatically

Use this parameter to specify the maximum number of concurrently executable jobs that a execution agent or agent created when the agent host is defined automatically can execute.

The concurrency level specified in this parameter is valid for a full 24 hours. To specify the concurrency level for 30-minute intervals, use the ajsagtalt command to change the value. For details about the ajsagtalt command, see ajsagtalt in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1. If you want to specify the concurrency level for 30-minute intervals for agent, use the jpqagtalt command to change the value. For details about the jpqagtalt command, see jpqagtalt in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

Specifiable values

A hexadecimal value from 1 to 00000400 (1 to 1,024 in decimal)

Default value

dword:00000005 (5 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(31) "AutoCreateMaxJobs" = dword:maximum-number-of-jobs-when-the-agent-host-is-defined-automatically

Use this parameter to specify the maximum number of jobs in the default queue that is created when the agent host is defined automatically.

Specifiable values

A hexadecimal value from 1 to FFFFFFFF (1 to 4,294,967,295 in decimal)

Default value

dword:00000064 (100 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(32) "AutoCreateWarnJobs" = dword:warning-value-for-the-number-of-jobs-when-the-agent-host-is-defined-automatically

Use this parameter to specify a warning value for the number of jobs in the default queue that is created when the agent host is defined automatically.

Specifiable values

A hexadecimal value from 1 to FFFFFFFF (1 to 4,294,967,295 in decimal)

Default value

dword:00000050 (80 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(33) "AutoCreatePriority" = dword:agent-priority-when-the-agent-host-is-defined-automatically

Use this parameter to specify the agent priority for the default queue that is created when the agent host is defined automatically.

Specifiable values

A hexadecimal value from 1 to 00000010 (1 to 16 in decimal)

Default value

dword:00000001 (1 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(34) "LeastRecentlyUsed" = dword:definition-of-method-for-determining-the-agent-host-to-which-jobs-are-distributed

Use this parameter to specify the method for determining the agent host to which jobs are to be distributed.

For details, see 6.2.9 Setting the method for determining the agent host to which a job will be delivered in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.9 Setting the method for determining the agent host to which a job will be delivered in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX). If you specify a value for queuing jobs and for submit jobs, see 7.1.7 Method of determining the agent host to which a job is distributed in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

Specifiable values

0

If there are multiple agents that have the same priority and agent usage rate, the system determines the job distribution destination agent host regardless of the idle time since the job was last distributed.

1

If there are multiple agents that have the same priority and agent usage rate, the system distributes a job to the agent host that has been idle for the longest time since a job was last distributed.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(35) "MaximumResource" = dword:maximum-number-of-definable-execution-locked-resources

Use this parameter to specify the maximum number of execution-locked resources used to suppress the concurrent execution of jobs.

When the JP1/AJS3 service is started, an area for execution-locked resource information that is equivalent to the value specified in this parameter is reserved in memory.

The value of this parameter is not applied to event jobs.

You cannot use the execution-locked resources for the jobs defined in a jobnet. You can, however, use them for submit jobs that have been defined by using the jpqjobsub command.

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

Change this value as necessary if the maximum number of defined execution-locked resources that can be added by executing the jpqresadd command is insufficient.

Specifiable values

A hexadecimal value from 1 to 2000 (1 to 8,192 in decimal)

Default value

dword:00000032 (50 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(36) "WorkPath" = "name-of-the-work-directory-used-when-an-agent-process-is-running"

The name of the work directory used when an agent process is running. Use this parameter to specify the name of the work directory to be used to execute jobs on the host. Specify a full path name.

If there is not enough space on the disk that contains the default directory, specify a directory on a disk that has enough space.

Specifiable values

A character string of no more than 180 bytes

Default value

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

For a physical host:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\tmp

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For a logical host:

shared-folder\jp1ajs2\tmp

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

For a physical host:

JP1/AJS3 - Manager: JP1/AJS3-Manager-installation-folder\tmp

JP1/AJS3 - Agent: JP1/AJS3-Agent-installation-folder\tmp

For a logical host:

shared-folder\jp1ajs2\tmp

For Windows Server 2003:

For a physical host:

JP1/AJS3 - Manager: JP1/AJS3-Manager-installation-folder\tmp

JP1/AJS3 - Agent: JP1/AJS3-Agent-installation-folder\tmp

For a logical host:

shared-folder\jp1ajs2\tmp

In UNIX:

For a physical host:

/var/opt/jp1ajs2/tmp

For a logical host:

shared-directory/jp1ajs2/tmp

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(37) "IsHA" = dword:definition-for-cluster-environment-setup-for-agent-processes

Use this parameter to specify the definition for setting up a cluster environment for a job execution control agent process. Specify this parameter only to stop cluster use.

Specifiable values

0

Specifies to stop cluster use.

1

If you execute setup when operating a cluster system, this value is automatically set to the parameter for the physical and logical hosts.

Default value

dword:00000000 (0 in decimal)

Recommended value

None

When the setting takes effect

After JP1/AJS3 is restarted

(38) "IsExecFindExecutable" = dword:definition-for-executing-a-job-with-a-long-file-name

Use this parameter to specify whether to execute the execution file of a job using a long file name without conversion to a short file name.

For details, see 6.2.15 Executing a job by using a long file name in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

0

An execution file name is converted to a short file name.

1

An execution file name is not converted to a short file name. The job is executed with a long file name.

Default value

dword:00000000 (0 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

(39) "LoadUserProfile" = dword:definition-for-whether-to-load-the-user-profile

Use this parameter to specify whether to load the user profile information of the OS user who executes a job when a job is executed.

For details, see 6.2.16 Executing a job that requires a user profile in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

0

The user profile information is not loaded.

1

The user profile information is loaded.

If you set 1 for this parameter, set 1 or 2 for the IsAccessTokenCache environment setting parameter.

Default value

dword:00000000 (0 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

(40) "IsAccessTokenCache" = dword:setting-for-reusing-an-access-token-when-a-job-is-executed

Use this parameter to specify whether to reuse an access token when a job is executed.

Set 1 or 2 for this parameter when you set 1 for the LoadUserProfile environment setting parameter to load user profile information.

For details, see 6.2.17 Reusing access tokens for job execution in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

0

Specify this value to acquire an access token each time a job is executed and then to release the token after the job is executed.

With this setting, a desktop heap area is allocated each time a job is executed, and is then released after the job is executed.

1

Specify this value to reuse an access token to execute a job if an access token with the same user name, domain name, and password was saved when the previous job was executed.

With this setting, all OS users who execute jobs share the desktop heap area, and the desktop heap area is released when the JP1/AJS3 service stops.

2

Specify this value to reuse an access token to execute a job if an access token with the same user name, domain name, and password was saved when the previous job was executed.

With this setting, a desktop heap area is allocated for each OS user who executes the job, and is then released when the JP1/AJS3 service stops.

With any of these settings, if a job is executed by the OS user who started the JP1/AJS3 service, the desktop heap area that was allocated when the JP1/AJS3 service started is shared.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(41) "DISABLE_FS_REDIRECTION" = dword:setting-for-disabling-file-system-redirection-when-jobs-are-executed-in-the-WOW64-environment

Use this parameter to specify whether to disable file system redirection when jobs are executed in the WOW64 environment and Standard has been specified for Exec. service.

For details, see 6.6.2 Disabling file system redirection when jobs are executed in a WOW64 environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

0

File system redirection is enabled when jobs are executed in the WOW64 environment.

1

File system redirection is disabled when jobs are executed in the WOW64 environment.

Default value

dword:00000000 (0 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

(42) "ENABLE_LONG_EXT" = dword:setting-value

Use this parameter to specify whether to execute a job specified for an executable file whose extension is 4 bytes or more in the application associated with the executable-file extension when Standard has been specified for Exec. service.

For details, see 6.2.18 Executing a job whose executable file name has an extension longer than three bytes in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

0

Although the executable-file extension is 4 bytes or more, the job specified for the file is executed in the application that is associated with the first three digits of the executable-file extension.

If the system cannot find the application that is associated with the first three digits of the extension, the job does not start.

1

If the executable-file extension is 4 bytes or more, the job is executed in the application that is associated with the extension.

However, if Standard is specified for Exec. service, the job is executed with a long file name when the executable file is executed with an extension of 4 bytes or more.

Default value

dword:00000000 (0 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

(43) "IsLimitCoreSize" = dword:limit-flag-for-the-maximum-core-file-size-for-each-process

Use this parameter to specify whether to limit the core-file size for each process of a job that is executed from JP1/AJS3.

Specifiable values

0

The core file size for each process of a job is not limited.

1

The core file size for each process of a job is limited.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(44) "LimitCoreSize" = dword:maximum-core-file-size-for-each-process

Use this parameter to specify the maximum core-file size for each process of a job that is executed from JP1/AJS3.

The specified parameter value takes effect when 1 is specified for the IsLimitCoreSize environment setting parameter to limit the maximum core file size.

Specifiable values

A hexadecimal value from 0 to 7FFFFFFF (0 to 2,147,483,647 in decimal)

Default value

dword:7FFFFFFF (2,147,483,647 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The valid range of 0 to 7FFFFFFF is the range of values that are logically available. The actual valid range depends on the range set in the setrlimit() OS system call.

If you specify dword:7FFFFFFF, the upper limit set of the system is used.

If you specify a number smaller than dword:7FFFFFFF, but larger than the upper limit of the system, the upper limit of the system is used.

If the setting fails, the system outputs a message and does not change the limit.

(45) "IsLimitDataSize" = dword:limit-flag-for-maximum-data-segment-size-for-each-process

Use this parameter to specify whether to limit the data-segment size for each process of a job that is executed from JP1/AJS3.

Specifiable values

0

The data-segment size for each process of a job is not limited.

1

The data-segment size for each process of a job is limited.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(46) "LimitDataSize" = dword:maximum-data-segment-size-for-each-process

Use this parameter to specify the maximum data-segment size for each process of a job that is executed from JP1/AJS3.

The specified parameter value takes effect when 1 is specified for the IsLimitDataSize environment setting parameter to limit the maximum data-segment size.

Specifiable values

A hexadecimal value from 0 to 7FFFFFFF (0 to 2,147,483,647 in decimal)

Default value

dword:7FFFFFFF (2,147,483,647 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The valid range of 0 to 7FFFFFFF is the range of values that are logically available. The actual valid range depends on the range set in the setrlimit() OS system call.

If you specify dword:7FFFFFFF, the upper limit set for the system is used.

If you specify a number smaller than dword:7FFFFFFF, but larger than the upper limit of the system, the upper limit of the system is used.

If the setting fails, the system outputs a message and does not change the limit.

(47) "IsLimitFileSize" = dword:limit-flag-for-the-maximum-permanent-file-size-for-each-process

Use this parameter to specify whether to limit the permanent-file size for each process of a job that is executed from JP1/AJS3.

Specifiable values

0

The permanent-file size for each process of a job is not limited.

1

The permanent-file size for each process of a job is limited.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(48) "LimitFileSize" = dword:maximum-permanent-file-size-for-each-process

Use this parameter to specify the maximum permanent-file size for each process of a job that is executed from JP1/AJS3.

The specified parameter value takes effect when 1 is specified for the IsLimitFileSize environment setting parameter to limit the maximum permanent-file size.

Specifiable values

A hexadecimal value from 0 to 7FFFFFFF (0 to 2,147,483,647 in decimal)

Default value

dword:7FFFFFFF (2,147,483,647 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The valid range of 0 to 7FFFFFFF is the range of values that are logically available. The actual valid range depends on the range set in the setrlimit() OS system call.

If you specify dword:7FFFFFFF, the upper limit set for the system is used.

If you specify a number smaller than dword:7FFFFFFF, but larger than the upper limit of the system, the upper limit of the system is used.

If the setting fails, the system outputs a message and does not change the limit.

(49) "IsLimitMemorySize" = dword:limit-flag-for-the-maximum-memory-size-for-each-process

Use this parameter to specify whether to limit the memory size (total amount of physical memory and swap area) for each process of a job that is executed from JP1/AJS3.

Specifiable values

0

The memory size for each process of a job is not limited.

1

The memory size for each process of a job is limited.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(50) "LimitMemorySize" = dword:maximum-memory-size-for-each-process

Use this parameter to specify the maximum memory size (total amount of physical memory and swap area) for each process of a job that is executed from JP1/AJS3.

The specified parameter value takes effect when 1 is specified for the IsLimitMemorySize environment setting parameter to limit the maximum memory size.

Specifiable values

A hexadecimal value from 0 to 7FFFFFFF (0 to 2,147,483,647 in decimal)

Default value

dword:7FFFFFFF (2,147,483,647 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The valid range of 0 to 7FFFFFFF is the range of values that are logically available. The actual valid range depends on the range set in the setrlimit() OS system call.

If you specify dword:7FFFFFFF, the upper limit set for the system is used.

If you specify a number smaller than dword:7FFFFFFF, but larger than the upper limit of the system, the upper limit of the system is used.

If the setting fails, the system outputs a message and does not change the limit.

(51) "IsLimitStackSize" = dword:maximum-stack-segment-size-for-each-process

Use this parameter to specify whether to limit the stack segment size for each process of a job that is executed from JP1/AJS3.

Specifiable values

0

The stack segment size for each process of a job is not limited.

1

The stack segment size for each process of a job is limited.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(52) "LimitStackSize" = dword:maximum-stack-segment-size-for-each-process

Use this parameter to specify the maximum stack segment size for each process of a job that is executed from JP1/AJS3.

The specified parameter value takes effect when 1 is specified for the IsLimitStackSize environment setting parameter to limit the maximum stack segment size.

Specifiable values

A hexadecimal value from 0 to 7FFFFFFF (0 to 2,147,483,647 in decimal)

Default value

dword:7FFFFFFF (2,147,483,647 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The valid range of 0 to 7FFFFFFF is the range of values that are logically available. The actual valid range depends on the range set in the setrlimit() OS system call.

If you specify dword:7FFFFFFF, the upper limit set for the system is used.

If you specify a number smaller than dword:7FFFFFFF, but larger than the upper limit of the system, the upper limit of the system is used.

If the setting fails, the system outputs a message and does not change the limit.

(53) "IsLimitCpuTime" = dword:limit-flag-for-the-maximum-CPU-time-for-each-process

Use this parameter to specify whether to limit the CPU time for each process of a job that is executed from JP1/AJS3.

Specifiable values

0

The CPU time for each process of a job is not limited.

1

The CPU time for each process of a job is limited.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(54) "LimitCpuTime" = dword:maximum-CPU-time-for-each-process

Use this parameter to specify the maximum CPU time for each process of a job that is executed from JP1/AJS3.

The specified parameter value takes effect when 1 is specified for the IsLimitCpuTime environment setting parameter to limit the maximum CPU time.

Specifiable values

A hexadecimal value from 0 to 7FFFFFFF (0 to 2,147,483,647 in decimal)

Default value

dword:7FFFFFFF (2,147,483,647 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The valid range of 0 to 7FFFFFFF is the range of values that are logically available. The actual valid range depends on the range set in the setrlimit() OS system call.

If you specify dword:7FFFFFFF, the upper limit set for the system is used.

If you specify a number smaller than dword:7FFFFFFF, but larger than the upper limit of the system, the upper limit of the system is used.

If the setting fails, the system outputs a message and does not change the limit.

(55) "IsLimitWorkSize" = dword:limit-flag-for-the-maximum-working-set-size-for-each-process

Use this parameter to specify whether to limit the working-set size (amount of physical memory used by a process) for each process of a job that is executed from JP1/AJS3.

Specifiable values

0

The working-set size for each process of a job is not limited.

1

The working-set size for each process of a job is limited.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you use Solaris, do not specify this flag. If you specify this flag, JP1/AJS3 might not be able to start.

(56) "LimitWorkSize" = dword:maximum-working-set-size-for-each-process

Use this parameter to specify the maximum working-set size (amount of physical memory used by process) for each process of a job that is executed from JP1/AJS3.

The specified parameter value takes effect when 1 is specified for the IsLimitWorkSize environment setting parameter to limit the maximum working-set size.

Specifiable values

A hexadecimal value from 0 to 7FFFFFFF (0 to 2,147,483,647 in decimal)

Default value

dword:7FFFFFFF (2,147,483,647 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The valid range of 0 to 7FFFFFFF is the range of values that are logically available. The actual valid range depends on the range set in the setrlimit() OS system call.

If you specify dword:7FFFFFFF, the upper limit set for the system is used.

If you specify a number smaller than dword:7FFFFFFF, but larger than the upper limit of the system, the upper limit of the system is used.

If the setting fails, the system outputs a message and does not change the limit.

(57) "IsLimitNoFile" = dword:limit-flag-for-the-maximum-number-of-file-descriptors-for-each-process

Use this parameter to specify whether to limit the number of file descriptors for each process of a job that is executed from JP1/AJS3.

Specifiable values

0

The number of file descriptors for each file of a job is not limited.

1

The number of file descriptors for each file of a job is limited.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(58) "LimitNoFile" = dword:maximum-number-of-file-descriptors-for-each-process

Use this parameter to specify the maximum number of file descriptors for each process of a job that is executed from JP1/AJS3.

The specified parameter value takes effect when 1 is specified for the IsLimitNoFile environment setting parameter to limit the maximum number of file descriptors.

Specifiable values

A hexadecimal value from 0 to 7FFFFFFF (0 to 2,147,483,647 in decimal)

Default value

dword:7FFFFFFF (2,147,483,647 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The valid range of 0 to 7FFFFFFF is the range of values that are logically available. The actual valid range depends on the range set in the setrlimit() OS system call.

If you specify dword:7FFFFFFF, the upper limit set for the system is used.

If you specify a number smaller than dword:7FFFFFFF, but larger than the upper limit of the system, the upper limit of the system is used.

If the setting fails, the system outputs a message and does not change the limit.

(59) "PipeComTimeout" = dword:pipe-communication-timeout-value-for-agents

Use this parameter to specify the pipe communication timeout value.

For details, see 15.2.15 Changing the timeout value for pipe communication of the agent in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

A hexadecimal value (in seconds) from 0000012C to 7FFFFFFF (300 to 2,147,483,647 in decimal)

Default value

dword:0000012C (300 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you specify a large value for the pipe communication timeout period, a job failure might not be detected quickly enough.

You can specify one second as the minimum value for the pipe communication timeout period. If you specify a value less than 300 seconds, however, the possibility that pipe communication times out increases, and a job might fail to start. For this reason, the minimum specifiable value is defined as 300 seconds or more. Note, however that if you specify a value that is less than 300 seconds, no error occurs and operation will continue.

(60) "AfterForkPipeTimeout" = dword:timeout-value-for-job-process-execution-ready-notification

Use this parameter to specify the timeout value for job process execution ready notification.

For details, see 15.2.16 Setting the timeout value for receiving notification from the job process that execution is ready in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

A hexadecimal value (in seconds) from 00000384 to 00015180 (900 to 86,400 in decimal)

The maximum value, which is 00015180 (86,400 seconds in decimal), is the number of seconds in one day.

Default value

dword:00000384 (900 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you specify a large value as the timeout value for reporting that preparations for job process execution have been completed, a job failure might not be detected quickly enough.

You can specify zero seconds as the minimum timeout value for reporting that preparations for job process execution have been completed. If you specify a value less than 900 seconds, however, the possibility a timeout error occurs increases, and a job might fail to start. For this reason, the minimum specifiable value is defined as 900 seconds or more. Note, however, that if you specify a value that is less than 900 seconds, no error occurs, and operation will continue.

(61) "IsCacheCmdSearchPath" = dword:flag-for-specifying-whether-to-cache-the-command-search-path-value

Use this parameter to specify whether to cache the value of the command-search path that is to be used when a job starts.

Caching the value improves performance when a job starts because the search path is obtained quickly. Note, however, that if you change the path when the value is cached, the change does not immediately take effect. Therefore, if you change the command-search path with caching enabled, wait at least 5 minutes before starting the job.

Specifiable values

0

The value for the command-search path is not cached.

1

The value for the command-search path is cached.

If you specify any value other than 0 or 1, the specified value is changed to 1.

If you often change the value for the PATH environment variable of the execution OS user, and want the change applied immediately when a job is executed, change this parameter value to 0. Note, however, that specifying 0 degrades job execution performance.

If you want operation to be consistent with that of version 06-71 or earlier, specify dword:00000000.

Default value

dword:00000001 (1 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Supplementary note

The command-search path is a PATH environment variable set in the login script of the execution OS user.

(62) "IsUseWorkPath" = dword:flag-for-specifying-whether-to-change-the-work-path-for-job-execution

Use this parameter to specify whether to change the work path when a job is executed to the work directory of the JP1/AJS3 agent process.

Specifiable values

0

The work path when a job is executed is not changed to the work directory used when the process is executed (the setting is disabled).

1

The work path when a job is executed is changed to the work directory used when the agent process is executed.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Supplementary note

For jobs executed in UNIX, if you do not specify a work path name (-w option for the jpqjobsub command), the home directory of the executing user is assumed. If the home directory is not defined, root (/) is assumed.

For job execution, the system creates a file whose name starts with JPQ_EXEC in the work path as a temporary file. No other files are created. If you have omitted the work path specification and the job ends abnormally, this file remains in the home directory of the job executing user. To prevent this file from remaining in the home directory of the job executing user, you must change the work path to the work directory of the JP1/AJS3 agent process.

(63) "IsSigchldDefault" = dword:definition-for-changing-setting-of-child-processes-started-by-JP1/AJS3-to-the-SIG_DFL-setting-whereby-the-SIGCHLD-signal-is-received

Use this parameter to specify whether to execute jobs with the default setting (SIG_DFL), whereby the SIGCHLD signal is received.

For details, see 15.2.17 Applying SIG_DFL (setting for receiving the SIGCHLD signal) to a child process started from JP1/AJS3 in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

0

Specify this value to execute the job with the setting (SIG_IGN) whereby the SIGCHLD signal is ignored.

1

Specify this value to execute the job with the setting (SIG_DFL) whereby the SIGCHLD signal is received.

Default value

dword:00000000 (0 in decimal)

During a new installation and setup of JP1/AJS3, 1 is set.

Recommended value

dword:00000001 (1 in decimal)

When the setting takes effect

After JP1/AJS3 is restarted

(64) "FileAccessPermissionMode" = dword:setting-for-the-method-of-checking-the-file-access-permission-at-UNIX-job-execution

Use this parameter to specify the method used to check the access permission of the following files when Unix jobs are executed:

Script file

Environment variable file

Standard input file

Standard output file

Standard error output file

Destination file

For details, see 15.2.18 Enabling the file access permission check for the ACL and secondary group settings during job execution in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

0

The access permission of each file is checked according to the file permission setting. The check is not performed according to the access control list or the secondary group settings.

1

The access permission of the script file is checked according to the file permission, access control list, and secondary group settings.

For the access permissions of files other than the script file, only the check according to the file permission is performed.

2

The access permission of each file is checked according to the file permission, access control list, and secondary group settings.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you change the parameter value to 1 or 2, a job that can start by default even if the access control list or secondary group for this job is set might fail to start. Before you specify a setting, consider the difference between the setting that uses only the file permission and the settings that also use the access control list or secondary group settings to prevent any effect on the starting of a job.

(65) "NotfyJobStateInterval" = dword:interval-for-resending-the-job-result-file

Use this parameter to specify the interval for resending the job result file.

For details, see 6.2.5 Changing the interval and number of resend attempts for job result files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.5 Changing the interval and number of resend attempts for job result files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (in seconds) from 0 to 00015180 (0 to 86,400 in decimal).

The maximum value is 00015180 (86,400 seconds in decimal), which is the number of seconds in one day.

If you do not want to resend the result file, specify 0.

Default value

dword:0000012C (300 in decimal, which means 5 minutes)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you specify 0 for this parameter, the result file is not resent. Therefore, job completion will not be reported if transfer of the result file fails, and the state of job completion will be detected by job status monitoring on the manager host. Because monitoring of the job status is usually performed by polling at five-minutes intervals, detection of job end could be delayed.

In either of the following cases, the end information for a job on the agent host is deleted. As a result, the job will be killed, and the message KAVU4597-W (A missed job at the agent (agent-host-name) was forcibly terminated.) will be output to the integrated trace log on the manager host.

When the resend operation is repeated until the upper limit of NotfyJobStateCount is reached, at which time transfer of the result file fails

When the agent host's JP1/AJS3 service stops before the manager host starts checking the job status

(66) "NotfyJobStateCount" = dword:number-of-times-job-result-file-to-be-resent

Use this parameter to specify the number of times that the job result file is to be resent.

For details, see 6.2.5 Changing the interval and number of resend attempts for job result files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.5 Changing the interval and number of resend attempts for job result files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value from 1 to 00000800 (1 to 2,048 in decimal)

Default value

dword:00000120 (288 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Supplementary note

If you use the default values of this parameter and the NotfyJobStateInterval environment setting parameter, a resend operation is performed at five-minute intervals for 24 hours.

(67) "ConnectTimeout" = dword:definition-of-the-TCP/IP-connection-timeout-value-of-the-job-execution-control-agent

Use this parameter to specify the TCP/IP connection timeout value.

For details about the definition, see 6.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (in milliseconds) from 00002710 to 000927C0 (10,000 to 600,000 in decimal)

Default value

dword:00015F90 (90,000 in decimal, which is 90 seconds)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary notes

If you decrease the connection timeout value, a timeout might occur before the connection is completed, resulting in a TCP/IP communication connection error.

Depending on the connection timeout specifications and the settings for the OS, a connection timeout might occur before the value specified for this parameter is reached.

(68) "CommunicateRetryCount" = dword:definition-of-the-number-of-retries-for-a-TCP/IP-connection-error-on-the-job-execution-control-agent

Use this parameter to specify the number of retries for a TCP/IP connection error.

For details about the definition, see 6.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value from 00000000 to 00000064 (0 to 100 in decimal)

Default value

dword:00000002 (2 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you increase the value for number of retries too much, unavoidable communication errors might cause the number of TCP/IP connection errors to increase.

(69) "CommunicateRetryInterval" = dword:definition-of-the-TCP/IP-connection-error-retry-interval-on-the-job-execution-control-agent

Use this parameter to specify the TCP/IP connection error retry interval.

For details about the definition, see 6.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (in seconds) from 00000001 to 0000012C (1 to 300 in decimal)

Default value

dword:00000014 (20 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you decrease the value for the retry interval so that it is too small, the communication retry interval will be too short. As a result, unavoidable communication errors might cause the number of TCP/IP connection errors to increase.

(70) "LogonUserRetryCount" = dword:number-of-retries-for-obtaining-an-access-token-when-"Standard"-is-specified-for-"Exc.service"

Use this parameter to specify the number of retries for obtaining an access token when Standard is specified for Exec. service.

For details, see 6.2.19 Changing the settings for logon retries when a job is executed in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

A hexadecimal value from 00000000 to 00000064 (0 to 100 in decimal)

Default value

dword:00000003 (3 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you specify 0, no retry attempts are made.

(71) "LogonUserRetryInterval" = dword:retry-interval-for-obtaining-an-access-token-when-"Standard"-is-specified-for-"Exec.service"

Use this parameter to specify the retry interval for obtaining the access token when Standard is specified for Exec. service.

For details, see 6.2.19 Changing the settings for logon retries when a job is executed in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

A hexadecimal value (in seconds) from 00000001 to 0000012C (0 to 300 in decimal)

Default value

dword:00000001 (1 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(72) "variable-name" = "value"

variable-name

Specify the character string for the variable name in the format $variable-name$. The specified variable name here can be used in the file path names and parameters.

value

Specify the installation path for the execution program indicated by variable-name on each applicable host.

Cautionary note

If you define environment setting parameters incorrectly, you can perform the recovery procedure described in E. Recovery Procedure Used When an Incorrect Environment Settings Parameter is Set in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

For details, see 6.2.1 Defining variables for work paths used during job execution in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.1 Defining variables for work paths used during job execution in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

(73) "All Users" = search-path-for-a-transfer-file

Specify the search path name for all JP1 users.

Supplementary note

You can specify a search path name for each JP1 user separately, and a search path name for all JP1 users in any sequence.

When you write multiple search path names in Windows, use two colons (::) to delimit them. Also enclose the entire path name after the equal sign (=) in double quotation marks (").

If the specifications are duplicated, the priority is as follows:

The specification for a JP1 user has priority over the specification for all JP1 users. If a transfer file with a search path that was specified for a JP1 user is found, a search using the search path specified for all JP1 users is not performed.

If a JP1 user name is duplicated, the most recent specification has priority.

For details, see 6.2.2 Defining search paths for a file to be transferred in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.2 Defining search paths for a file to be transferred in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

(74) "JP1-user-name" = search-path-for-a-transfer-file

Specify the search path name for each JP1 user who executes a job.

Supplementary note

You can specify a search path name for each JP1 user separately, and a search path name for all JP1 users in any sequence.

When you write multiple search path names in Windows, use two colons (::) to delimit them. Also enclose the entire path name after the equal sign (=) in double quotation marks (").

If specifications are duplicated, the priority is as follows:

The specification for a JP1 user has priority over the specification for all JP1 users. If a transfer file with a search path that was specified for a JP1 user is found, a search using the search path specified for all JP1 users is not performed.

If a JP1 user name is duplicated, the most recent specification has priority.

For details, see 6.2.2 Defining search paths for a file to be transferred in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.2 Defining search paths for a file to be transferred in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

(75) "ConnectTimeout" = dword:definition-of-the-TCP/IP-connection-timeout-value-for-job-execution-and-schedulers-commands

Use this parameter to specify the TCP/IP connection timeout value.

For details about the definition, see 6.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (in milliseconds) from 00002710 to 000927C0 (10,000 to 600,000 in decimal)

Default value

dword:00015F90 (90,000 in decimal, which is 90 seconds)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary notes

If you decrease the connection timeout value, a timeout might occur before the connection is completed, resulting in a TCP/IP communication connection error.

Depending on the connection timeout specifications and the settings for the OS, a connection timeout might occur before the value specified for this parameter is reached.

(76) "CommunicateRetryCount" = dword:definition-of-number-of-retries-for-an-TCP/IP-connection-error-for-job-execution-and-scheduler-commands

Use this parameter to specify the number of retries for a TCP/IP connection error.

For details about the definition, see 6.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value from 00000000 to 00000064 (0 to 100 in decimal)

Default value

dword:00000002 (2 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you increase the value for number of retries too much, unavoidable communication errors might cause the number of TCP/IP connection errors to increase.

(77) "CommunicateRetryInterval" = dword:definition-of-the-TCP/IP-connection-error-retry-interval-for-job-execution-and-scheduler-commands

Use this parameter to specify the TCP/IP connection error retry interval.

For details about the definition, see 6.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (in seconds) from 00000001 to 0000012C (1 to 300 in decimal)

Default value

dword:00000014 (20 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you decrease the value for the retry interval to so that it is too small, the communication retry interval will be too short. As a result, unavoidable communication errors might cause the number of TCP/IP connection errors to increase.

(78) "CommunicateTimeout" = dword:setting-value

Use this parameter to specify the communication timeout period.

For details, see 6.2.14 Changing the timeout value for the job execution control manager process in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.14 Changing the timeout value for the job execution control manager process in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (in milliseconds) from 000927c0 to 0036EE80 (600,000 to 3,600,000 in decimal)

Default value

dword:000927c0 (600,000 in decimal, which is 10 minutes)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(79) "MacroOptionReplaceMode" = dword:whether-to-replace-the-passing-information-in-a-macro-variable-with-a-NULL-character-string

When the passing information in a macro variable that has no characters before and after it is a NULL character string, use this parameter to specify whether to replace the macro variable name with a NULL character string.

For details, see 6.2.11 Setting the handling of a macro variable when the value is a NULL string in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.11 Setting the handling of a macro variable when the value is a NULL string in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

0

The specified macro variable name is used as is as a character string. There is no replacement with a NULL string.

1

The macro variable name is replaced with a NULL string.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(80) "IsHA" = dword:definition-for-the-cluster-environment-setup-for-the-commands-and-schedulers-used-for-job-execution

Use this parameter to specify the definition for setting up a cluster environment for the commands and schedulers used for job execution. Specify this parameter only to stop cluster use.

Specifiable values

0

Specifies to stop cluster use.

1

If you execute setup when operating a cluster system, this value is automatically set to the parameter for the physical and logical hosts.

Default value

dword:00000000 (0 in decimal)

Recommended value

None

When the setting takes effect

After JP1/AJS3 is restarted

(81) "PassingInfoUsePreRc"=dword:settings-for-using-the-return-value-of-the-preceding-job-in-the-passing-information-setting-jobs

Specify whether to enable or disable the return value of the preceding job in a passing information setting job.

For details, see 6.2.25 Settings for using the return value of the preceding job in the passing information setting jobs in the Job Management Partner 1/ Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.23 Settings for using the return value of the preceding job in the passing information setting jobs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

0

Regardless of the return value of the preceding job, the return value of the passing information setting job itself is set.

1

If the return value of the preceding job is 0, the return value of the passing information setting job itself is set.

If the return value of the preceding job is a return value other than 0, the return value of the preceding job in set as the return value of the passing information setting job.

Default value

dword:00000001 (1 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

Immediately (the next time a passing information setting job is executed)

(82) "ConnectTimeout" = dword:definition-of-the-TCP/IP-connection-timeout-value-in-the-status-reporting-process-for-the-job-execution-control

Use this parameter to specify the TCP/IP connection timeout value.

For details about the definition, see 6.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (in milliseconds) from 00002710 to 000927C0 (10,000 to 600,000 in decimal)

Default value

dword:00015F90 (90,000 in decimal, which is 90 seconds)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary notes

If you decrease the connection timeout value, a timeout might occur before the connection is completed, resulting in a TCP/IP communication connection error.

Depending on the connection timeout specifications and the settings for the OS, a connection timeout might occur before the value specified for this parameter is reached.

(83) "CommunicateRetryCount" = dword:definition-of-the-number-of-retries-for-a-TCP/IP-connection-error-in-the-status-reporting-process-for-job-execution-control

Use this parameter to specify the number of retries for a TCP/IP connection error.

For details about the definition, see 6.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value from 00000000 to 00000064 (0 to 100 in decimal)

Default value

dword:00000002 (2 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you increase the value for number of retries too much, unavoidable communication errors might cause the number of TCP/IP connection errors to increase.

(84) "CommunicateRetryInterval" = dword:definition-of-the-TCP/IP-connection-error-retry-interval-in-the-status-reporting-process-for-job-execution-control

Use this parameter to specify the TCP/IP connection error retry interval.

For details about the definition, see 6.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (in seconds) from 00000001 to 0000012C (1 to 300 in decimal)

Default value

dword:00000014 (20 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you decrease the value for the retry interval so that it is too small, the communication retry interval will be too short. As a result, unavoidable communication errors might cause the number of TCP/IP connection errors to increase.

(85) "IsHA" = dword:definition-for-cluster-environment-setup-for-the-status-reporting-process-for-job-execution-control

Use this parameter to specify the definition for setting up a cluster environment for the status reporting process for job execution control. Specify this parameter only to stop cluster use.

Specifiable values

0

Specifies to stop cluster use.

1

If you execute setup when operating a cluster system, this value is automatically set to the parameter for the physical and logical hosts.

Default value

dword:00000000 (0 in decimal)

Recommended value

None

When the setting takes effect

After JP1/AJS3 is restarted

(86) "MergeEnvMode" = dword:definition-for-whether-an-environment-variable-in-a-job-definition-is-enabled-when-the-name-is-the-same-as-a-system-environment-variable-name

Use this parameter to specify whether an environment variable in a job definition is enabled when the name is the same as a system environment variable name.

For details, see 6.2.21 Settings for enabling an environment variable in a job definition when the name is the same as a system environment variable name in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

0

Specify this value to disable an environment variable in a job definition when the name is the same as a system environment variable name.

1

Specify this value to enable an environment variable in a job definition when the name is the same as a system environment variable name.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(87) "UACAdministratorsExec" = dword:setting-for-executing-jobs-as-a-user-with-administrator-permissions-when-UAC-is-enabled

Use this parameter to specify whether a user can execute jobs as a user with administrator permissions when Standard is specified for Exec. Service of the job and the UAC function is enabled.

Note that this parameter is disabled in Windows Server 2003.

For details, see 6.2.22 Settings for executing jobs as a user with administrator permissions when the UAC is enabled in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

0

When the UAC function is enabled, all OS users who belong to the Administrators group execute jobs with the administrator permissions disabled. However, the built-in Administrator and an OS user whose account is the same as the JP1/AJS3 service account are excluded.

1

When the UAC function is enabled, an OS user who belongs to the Administrators group executes jobs as a user with administrator permissions.

When you specify 1, the Log on as a batch job permission must be set for all OS users (including standard users) who execute jobs.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(88) "GetPasswd_RetryCount" = dword:number-of-retry-attempts-when-an-attempt-to-acquire-user-information-from-the-OS-password-file-has-failed

Use this parameter to specify the number of retry attempts when an attempt to acquire user information from the OS password file has failed.

Usually, you do not need to change this value.

For details, see 15.2.20 Changing the settings for retries when user information is acquired in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

A hexadecimal value from 00000000 to 0000000A (0 to 10 in decimal)

If you specify dword:00000000, a retry is not performed.

Default value

dword:00000002 (2 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(89) "GetPasswd_RetryInterval" = dword:retry-interval-when-an-attempt-to-acquire-user-information-from-the-OS-password-file-has-failed

Use this parameter to specify the retry interval when an attempt to acquire user information from the OS password file has failed.

Usually, you do not need to change this value.

For details, see 15.2.20 Changing the settings for retries when user information is acquired in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

A hexadecimal value (in milliseconds) from 00000000 to 00002710 (0 to 10,000 in decimal)

If you specify dword:00000000, a retry is performed immediately.

Default value

dword:000003E8 (1,000 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(90) "IgnoreResultFileError" = dword:operation-if-a-transfer-error-occurs-in-a-job-result-file

Use this parameter to specify the operation to be executed if an error occurs during the transfer processing of a job result file (standard output file or standard error output file) and if Standard is specified for Exec. Service.

For details, see 6.2.24 Operation settings when job result file transfer fails in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (Windows), or 15.2.22 Operation settings when job result file transfer fails in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (UNIX).

Specifiable values

0

If an error occurs during the transfer processing of a job result file, -1 is set as the job return code and the job status is set to Ended abnormally.

1

If an error occurs during the transfer processing of a job result file, the return code of the job process is set as the job return code and the job status is set to Ended normally, Ended with warning, or Ended abnormally according to how the end of processing is judged.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(91) "PreventResultFileLack" = dword:setting-for-ensuring-that-data-generated-by-jobs-is-output-to-result-files

Use this parameter to specify whether all data generated by jobs is output to result files.

For details, see 6.2.26 Setting for ensuring that data generated by jobs is output to result files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1..

Specifiable values

0

If 0 is specified, data generated by jobs might not be output to result files if disk access or restart of processing takes time. (For example, restart of processing takes time when the memory used by JP1/AJS3 is swapped out.)

1

If 1 is specified, data generated by jobs is output to result files even if disk access or restart of processing takes time. (For example, restart of processing takes time when the memory used by JP1/AJS3 is swapped out.)

Default value

dword:00000000 (0 in decimal)

Recommended value

Depends on the user environment.

Note that 1 is recommended if you use the passing information setting job.

When the setting takes effect

After JP1/AJS3 is restarted

2.4 Setting up the event/action control environment

This section describes the environment setting parameters for event/action control.

2.4.1 List of environment setting parameters for event/action control

The environment for starting event jobs requires different settings in the manager environment (JP1/AJS3 - Manager) and the agent environment (JP1/AJS3 - Agent).

The table below lists the environment setting parameters to be used to set event/action control in the manager environment (JP1/AJS3 - Manager) and the agent environment (JP1/AJS3 - Agent).

To determine whether an environment setting parameter is to be set in Windows or UNIX, see the Applicable OS column. To determine whether an environment setting parameter is to be set in the manager environment (JP1/AJS3 - Manager) or the agent environment (JP1/AJS3 - Agent), see the Applicable product column.

Table 2‒5: Environment setting parameters (event action control)

No.

Definition key

Environment setting parameter

Definition

Applicable OS

Applicable product

1

[{JP1_DEFAULT|logical-host-name}\JP1AOMMANAGER]#1

"WaitInfFileOutDir"=

Name of the directory to which the wait information file (settings for the manager process) is output

Windows

UNIX

M

2

[JP1_DEFAULT\JP1AOMMANAGER]#2

"_AgentStartStopResolveMode"=

Name resolution option for an agent host

Windows

UNIX

M

3

For scheduler service (common):

[{JP1_DEFAULT|logical-host-name}\JP1AJS2\SCHEDULER\EV\MANAGER]#1

For the compatible ISAM configuration:

[{JP1_DEFAULT|logical-host-name}\JP1AOMMANAGER]#1

"FileWriteMode"=

File update mode

Windows

UNIX

M

4

"MacVarDQuotation"=

Option for enabling double quotation marks (") in passing information

Windows

UNIX

M

5

"DNSEstablish"=

Definition for running JP1/AJS3 in FQDN format for DNS operation that uses event jobs

Windows

UNIX

M

6

"FixedHostnameForAgent"=

Option for ensuring that a fixed manager host name is used

Windows

UNIX

M

7

For scheduler service (common):

[{JP1_DEFAULT|logical-host-name}\JP1AJS2\SCHEDULER\EV\MANAGER]#1

For scheduler service (individual):

[{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name\EV\MANAGER]#1

For the compatible ISAM configuration:

[{JP1_DEFAULT|logical-host-name}\JP1AOMMANAGER]#1

"EvJobExecContinue"=

Option to continue execution of active event jobs

Windows

UNIX

M

8

"BlockadeTimeoutInterval"=

Period of time for monitoring an event job in the blocked status

Windows

UNIX

M

9

"NotificationConstantRetry"=

Option for ensuring that the sending of unreported information is retried at regular intervals

Windows

UNIX

M

10

"NotificationRetryInterval"=

Interval for sending unreported information

Windows

UNIX

M

11

"NotificationRetryCount"=

Maximum number of retries for sending unreported information

Windows

UNIX

M

12

For scheduler service (common):

[{JP1_DEFAULT|logical-host-name}\JP1AJS2\SCHEDULER\EV\MANAGER]#1

For the event/action control agent:

[{JP1_DEFAULT|logical-host-name}\JP1AOMAGENT]#1

For the compatible ISAM configuration:

[{JP1_DEFAULT|logical-host-name}\JP1AOMMANAGER]#1

"ClientBindFlag"=

Behavior of the send binding method

Windows

UNIX

M, A

13

For manager host:

[{JP1_DEFAULT|logical-host-name}\JP1AOMMANAGER]#1

[{JP1_DEFAULT|logical-host-name}\JP1AJS2\SCHEDULER\EV\MANAGER]#1

For agent host:

[{JP1_DEFAULT|logical-host-name}\JP1AOMAGENT]#1

"ResolveAgentInfo"=

Option for changing the agent host information to be used for name resolutions

Windows

UNIX

M, A

14

[{JP1_DEFAULT|logical-host-name}\JP1AOMAGENT]#1

"WaitInfFileOutDir"=

Name of the directory to which the wait information file (settings for the agent process) is output

Windows

UNIX

M, A

15

"EvjobInfFile"=

Name of directory in which inherited event job information is saved

Windows

UNIX

M, A

16

"HowUseInfWhenHA"=

Information inheritance when a failover occurs

Windows

UNIX

M, A

17

"InformationWhenShutDown"=

How information is inherited at system shutdown

Windows

UNIX

M, A

18

"FilewatchinfContinue"=

How information of the file monitoring job is in inherited

Windows

UNIX

M, A

19

"FileWriteMode"=

File update mode

Windows

UNIX

M, A

20

"EVProcessHA"=

Option used when a detail process terminates

Windows

UNIX

M, A

21

"EventSequential"=

Event order option

Windows

UNIX

M, A

22

"RetryAgtStartNotification"=

Definition for resending the startup notification if sending of a startup notification has failed

Windows

UNIX

M, A

23

"ClientConnectTimeout"=

Time out value for the connection between the event/action control manager and the event/action control agent for communication

Windows

UNIX

M, A

24

"NotificationRetryInterval"=

Interval for sending unreported information

Windows

UNIX

M, A

25

"NotificationRetryCount"=

Maximum number of retries for sending unreported information

Windows

UNIX

M, A

26

"EventServerName"=

FQDN event server name

Windows

UNIX

M, A

27

"GetFQDNForShortNameOnly"=

Whether to use an FQDN local host name for interprocess communication for event/action control

Windows

UNIX

M, A

28

[JP1_DEFAULT\JP1AOMAGENT]#2

"RecvTimeout"=

Whether to set a timeout for receiving data in event job socket communication

Windows

UNIX

M, A

Legend:

M: JP1/AJS3 - Manager

A: JP1/AJS3 - Agent

#1

Specify JP1_DEFAULT for the physical host. For logical-host-name, specify the name of a logical host.

#2

The setting of this parameter is valid for the physical and all logical hosts.

The following describes each of the environment setting parameters.

Parameters that are not described here are used for maintenance purposes. Do not change their values.

The default value is used whenever a value is not specified for an environment setting parameter.

2.4.2 Details of the environment setting parameters for event/action control

(1) "WaitInfFileOutDir" = "name-of-directory-to-which-the-wait-information-file-is-output" (setting for the manager process)

Use this parameter to specify the name of the directory to which detailed information about event jobs and information about the receive status of events monitored by the start condition (wait information) is output. Specify a full path name. Note that you need to specify this directory only if you want to change the default directory.

Specify this parameter if you want to output the wait information to a folder that is not specified by default or to support a cluster configuration.

The wait information is output to the directory you specify in this parameter or to the following folder in the assumed directory.

In Windows:

sys\infodir

In UNIX:

sys/infodir

This parameter is valid only for a manager process in an ISAM configuration, which ensures compatibility, or for a manager process started from host-service management in a standard configuration.

Specifiable values

A character string of no more than 180 bytes

Default value

In Windows:

JP1/AJS3-Manager-installation-folder

During a new installation and setup of JP1/AJS3, one of the following values is set.

In Windows Server 2012 or Windows Server 2008 in which the installation folder is in the default folder or 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 is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

In Windows Server 2012 or Windows Server 2008 in which an installation folder other than above is used:

JP1/AJS3-Manager-installation-folder

In Windows Server 2003:

Blank

In UNIX:

/var/opt/jp1ajs2

During a new installation and setup of JP1/AJS3, the value is blank.

Recommended value

For a physical host:

In Windows Server 2012 or Windows Server 2008 in which the installation folder is in the default folder or 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 is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

In Windows Server 2012 or Windows Server 2008 in which an installation folder other than above is used:

JP1/AJS3-Manager-installation-folder

In Windows Server 2003:

Blank

In UNIX:

Blank

For a logical host:

directory-name-of-a-common-disk

When the setting takes effect

The next time the JP1/AJS3 service is started

Cautionary note

For the name of the directory to which the wait information file is output, do not specify characters that the OS does not permit to be used for a directory name. For example, in Windows, double quotation marks (") and asterisks (*) cannot be used.

Also, do not specify a backslash (\) at the end of the directory name.

(2) "_AgentStartStopResolveMode" = "{optimized|normal}"

Use this parameter to specify whether to optimize the name resolution processing of an agent host.

This parameter is valid only for the compatible ISAM configuration.

Specifiable values

optimized

Specify this value to optimize the name resolution processing of an agent host name.

Only the name of the agent host that runs event jobs or jobnets with start conditions is resolved.

normal

Specify this value if you do not want to optimize name resolution processing of the agent host name.

Default value

normal

Recommended value

Default value

When the setting takes effect

The next time the JP1/AJS3 service is started

(3) "FileWriteMode" = "{sync|nosync}" (setting for the manager process)

Use this parameter to specify whether to perform synchronous writing when the wait information file is updated.

Select the writing method appropriate for performance, reliability, and method of operation.

Specifiable values

sync

Synchronous writing is always performed when a file is updated. This writing mode improves reliability, but reduces performance.

Select this method when reliability is more important, as in a cluster environment.

nosync

Data is written to a disk in response to OS buffering. There is no synchronization with JP1/AJS3 processing. This mode provides better performance than sync, but a system failure will lead to inconsistent information, sometimes causing an event to disappear.

Default value

nosync

Recommended value

sync

When the setting takes effect

The next time the JP1/AJS3 service is started

Cautionary note

Specify the same parameter value in the manager process (definition key JP1AJSMANAGER\SCHEDULER\EV\MANAGER) and the agent process (definition key JP1AOMAGENT). If you specify nosync for the manager process and sync for agent process, JP1/AJS3 slows down dramatically. This could happen if a jobnet using an event job or a jobnet with a start condition is registered for execution or is killed, or if an OR job preceded by many event jobs is executed. For the same reason, specify the same setting for the manager and the agents in the manager-agent system.

(4) "MacVarDQuotation" = "{Y|N}"

Use this parameter to specify whether to use the option for enabling double quotation marks (") in passing information.

Specifiable values

Y

The option is used.

N

The option is not used.

Default value

N

During a new installation and setup of JP1/AJS3, Y is set.

Recommended value

Y

When the setting takes effect

The next time the JP1/AJS3 service is started

(5) "DNSEstablish" = "{Y|N}"

Use this parameter to specify whether to use an FQDN host name when DNS is used.

For details, see 6.3.5 Using fully qualified domain names (FQDN) when using event jobs during DNS operation in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.3.5 Using fully qualified domain names (FQDN) when using event jobs during DNS operation in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

Y

An FQDN host name is used when DNS is used.

N

An FQDN host name is not used when DNS is used. The manager sends a host name to agents instead of an FQDN host name.

Default value

N

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service is started

(6) "FixedHostnameForAgent" = "{Y|N}"

Use this parameter to specify whether lower case is always used for alphabetic characters in the manager host name for communication between event/action control processes.

For details, in Windows, see 6.3.16 Settings for ensuring that a fixed manager host name is used when event jobs are executed in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1. In UNIX, see 15.3.17 Settings for ensuring that a fixed manager host name is used when event jobs are executed in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

Y

The host name obtained on the manager host is used for communication for event/action control after case conversion is performed so that all letters are lower case.

N

The host name obtained on the manager host is used for communication for event/action control without case conversion.

Default value

N

Recommended value

Y

When the setting takes effect

The next time the JP1/AJS3 service starts

(7) "EvJobExecContinue" = "{Y|N}"

Use this parameter to specify whether to continue execution of an event job when you restart the JP1/AJS3 service on an execution.

For details, see 6.3.6 Resuming event jobs that stopped when the JP1/AJS3 service stopped in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.3.6 Resuming event jobs that stopped when the JP1/AJS3 service stopped in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

Y

Execution of the event job is continued.

N

Execution of the event job ends.

Default value

N

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service is started

Cautionary note

Set the option to continue execution of active event jobs for each manager of a physical host and a logical host.

(8) "BlockadeTimeoutInterval" = dword:time-for-monitoring-event-jobs-in-blocked-status

Use this parameter to specify the period of time until an event job in blocked status or a jobnet with start conditions is killed.

For details, see 6.3.10 Setting the period of time for monitoring event jobs in the blocked status in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.3.10 Setting the period of time for monitoring event jobs in the blocked status in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (in hours) from 00000018 to 000002D0 (24 to 720 in decimal)

Default value

dword:000002D0 (720 in decimal)

Recommended value

Default value

When the setting takes effect

The next time the JP1/AJS3 service is started

(9) "NotificationConstantRetry" = "{Y|N}"

Use this parameter to specify whether to use the regular or gradually increasing retry interval if the connection for communication from the manager host to the agent host fails because of a network error caused by a timeout.

For details, see 6.3.12 Settings for ensuring that the sending of unreported information is retried at regular intervals in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.3.13 Settings for ensuring that the sending of unreported information is retried at regular intervals in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

Y

If a network error caused by a timeout occurs, sending is retried at regular intervals.

N

If a network error caused by a timeout occurs, sending is retried at gradually increasing intervals.

Default value

N

Recommended value

Default value

When the setting takes effect

The next time the JP1/AJS3 service starts

(10) "NotificationRetryInterval" = dword:retry-interval-for-sending-unreported-information-from-the-manager-host-to-the-agent-host

Use this parameter to specify the retry interval for sending unreported information from the manager host to the agent host.

For details, see 6.3.13 Changing the send retry interval and the number of retries for sending unreported information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.3.14 Changing the send retry interval and the number of retries for sending unreported information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (in seconds) from 00000001 to 00015180 (1 to 86,400 in decimal)

Default value

dword:0000001E (30 in decimal)

Recommended value

Default value

When the setting takes effect

The next time the JP1/AJS3 service starts

(11) "NotificationRetryCount" = dword:maximum-number-of-retries-for-sending-unreported-information-from-the-manager-host-to-the-agent-host

Use this parameter to specify the maximum number of retries for sending unreported information from the manager host to the agent host.

For details, see 6.3.13 Changing the send retry interval and the number of retries for sending unreported information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.3.14 Changing the send retry interval and the number of retries for sending unreported information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (number of times) from 00000001 to 00015180 (1 to 86,400 in decimal)

Default value

dword:00000B40 (2,880 in decimal)

Recommended value

Default value

When the setting takes effect

The next time the JP1/AJS3 service starts

(12) "ClientBindFlag" = dword:behavior-of-the-send-binding-method

Use this parameter to specify whether to match the send binding method used for communication when an event job is executed to the receive binding method.

For details, see 6.3.11 Setting the binding method applied to the outgoing communication used in the execution of event jobs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.3.11 Setting the binding method applied to the outgoing communication used in the execution of event jobs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

0

The setting for the send binding method used for communication when an event job is executed is canceled.

1

The send binding method used for communication when an event job is executed is matched to the receive binding method.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

The next time the JP1/AJS3 service is started

(13) "ResolveAgentInfo"="{exec|host}"

Use this parameter to set the option for changing the agent host information that is to be used for name resolutions. For details, see 6.3.19 How to set the option for changing the agent information to be used for name resolution in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.3.19 How to set the option for changing the agent information to be used for name resolution in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

exec

When the IP address of an agent host is changed, the tasks on the manager host can be omitted.

host

When the IP address of an agent host is changed, tasks on the manager host are required.

Default value

host

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service is started

Supplementary notes

If you set this parameter, make sure that you set the same parameter value on both the manager and agent hosts. If different values are specified, the system assumes that host is specified on both hosts.

If you set this parameter on the manager host, you must set this parameter in two locations: the host definition key [{JP1_DEFAULT|logical-host-name}\JP1AOMMANAGER] and the scheduler service definition key [{JP1_DEFAULT|logical-host-name}\JP1AJS2\SCHEDULER\EV\MANAGER]. If you specify different parameter values for these two locations, scheduler service processes output the KAVT0199-E message. This message is output for each scheduler service.

(14) "WaitInfFileOutDir" = "name-of-directory-to-which-the-wait-information-file-is-output" (setting for the agent process)

Use this parameter to specify the name of the directory to which information such as the event-generation status of the event job and receive status of events monitored by the start condition (wait information) is output. Specify a full path name. Note that you need to specify this directory only if you want to change the default directory.

Specify this parameter if you want to output the wait information to a folder that is not specified by default or to support a cluster configuration.

The wait information is output to the directory you specify here or to the following directory in the assumed directory.

In Windows:

sys\infoagt

In UNIX:

sys/infoagt

Specifiable values

A character string of no more than 180 bytes

Default value

In Windows:

JP1/AJS3 - Manager: JP1/AJS3-Manager-installation-folder

JP1/AJS3 - Agent: JP1/AJS3-Agent-installation-folder

During a new installation and setup of JP1/AJS3, one of the following values is set.

In Windows Server 2012 or Windows Server 2008 in which the installation folder is in the default folder or 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 is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

In Windows Server 2012 or Windows Server 2008 in which an installation folder other than above is used:

JP1/AJS3 - Manager: JP1/AJS3-Manager-installation-folder

JP1/AJS3 - Agent: JP1/AJS3-Agent-installation-folder

In Windows Server 2003:

Blank

In UNIX:

/var/opt/jp1ajs2

During a new installation and setup of JP1/AJS3, it is set as blank.

Recommended value

For a physical host:

In Windows Server 2012 or Windows Server 2008 in which the installation folder is in the default folder or 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 is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

In Windows Server 2012 or Windows Server 2008 in which an installation folder other than above is used:

JP1/AJS3 - Manager: JP1/AJS3-Manager-installation-folder

JP1/AJS3 - Agent: JP1/AJS3-Agent-installation-folder

In Windows Server 2003:

Blank

In UNIX:

Blank

For a logical host:

directory-name-of-a-shared-disk

When the setting takes effect

The next time the JP1/AJS3 service is started

Cautionary note

For the name of the directory to which the wait information file is output, do not specify characters that the OS does not permit to be used for a directory name. For example, in Windows, double quotation marks (") and asterisks (*) cannot be used.

Also, do not specify a backslash (\) at the end of the directory name.

(15) "EvjobInfFile" = "name-of-directory-for-inheriting-event-or-job-information"

Use this parameter to specify the name of the directory in which the file inheriting the information received in the email reception monitoring jobs is saved. Specify a full path name. Note that you need to specify this directory only if you want to change the default directory.

Specify this parameter if you want to output the information to a folder that is not specified by default or to support a cluster configuration.

For details about the behavior of email reception monitoring jobs, see 2.1.2 Behavior when receiving email in the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.

Specifiable values

A character string of no more than 180 bytes

Default value

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\tmp\infodir

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3 - Manager: JP1/AJS3-Manager-installation-folder\tmp\infodir

JP1/AJS3 - Agent: JP1/AJS3-Agent-installation-folder\tmp\infodir

For Windows Server 2003:

JP1/AJS3 - Manager: JP1/AJS3-Manager-installation-folder\tmp\infodir

JP1/AJS3 - Agent: JP1/AJS3-Agent-installation-folder\tmp\infodir

In UNIX:

/var/opt/jp1ajs2/sys/infoagt/tmp/infodir

If it has been set as blank, the default value is assumed. It is set as blank during a new installation and setup of JP1/AJS3.

Recommended value

Physical hosts

Blank

Logical hosts

directory-name-of-a-shared-disk

When the setting takes effect

The next time the JP1/AJS3 service is started

Cautionary note

JP1/AJS3 does not use the file saved in this directory. Also, because the file is not automatically deleted, delete it when it is no longer needed.

(16) "HowUseInfWhenHA" = "{Y|N}"

Use this parameter to specify whether information is to be passed if the JP1/AJS3 service in JP1/AJS3 - Manager or JP1/AJS3 - Agent stops unaccompanied by normal stop processing during failover or power-off processing. Specify whether information about the stoppage is to be passed to the failover destination or the restarted JP1/AJS3 - Manager or JP1/AJS3 - Agent.

Change this parameter if you want to discard an event occurring before the failover or JP1/AJS3 service stoppage when the JP1/AJS3 service stoppage unaccompanied by normal stop processing prevents the event from being reported to JP1/AJS3 - Manager.

Specifiable values

Y

The status when a stoppage without normal stop processing has occurred is passed to the failover destination or the restarted JP1/AJS3 - Manager or JP1/AJS3 - Agent. For example, after the switchover, an event that could not be reported to JP1/AJS3 - Manager before the failover occurred will be resent.

N

The status when a stoppage without normal stop processing has occurred is not passed to the failover destination or the restarted JP1/AJS3 - Manager or JP1/AJS3 - Agent. For example, an event that could not be reported to JP1/AJS3 - Manager before the failover occurred will be discarded.

Specify Y for normal operation.

Default value

Y

Recommended value

Default value

When the setting takes effect

The next time the JP1/AJS3 service is started

(17) "InformationWhenShutDown" = "{K|B}"

Use this parameter to specify whether to report events that could not be reported to JP1/AJS3 - Manager when either the JP1/AJS3 - Manager host or JP1/AJS3 - Agent host was shut down (end with stop processing).

Change the parameter value to discard any such unreported events at the next restart.

Specifiable values

K

When JP1/AJS3 - Manager or JP1/AJS3 - Agent is started after the previous shutdown, the system reports the events that could not be reported to JP1/AJS3 - Manager before the shutdown. For example, when you start the terminated host, events generated before shutdown are reported to JP1/AJS3 - Manager. Note, however, that this applies only when JP1/AJS3 - Manager is started within 24 hours.

B

When JP1/AJS3 - Manager or JP1/AJS3 - Agent is started after the previous shutdown, the system does not report the events that could not be reported to JP1/AJS3 - Manager before the shutdown. That is any such events are discarded. Specify this value if you want information to be inherited only when a power failure occurs.

Specify K for normal operation.

Default value

K

Recommended value

Default value

When the setting takes effect

The next time the JP1/AJS3 service is started

(18) "FilewatchinfContinue" = "{Y|N}"

Use this parameter to specify whether the information for a file-monitoring job existing at the last shutdown is inherited when JP1/AJS3 - Manager or JP1/AJS3 - Agent is shut down (end with stop processing) during execution of the file-monitoring job.

Change the parameter value in the following case: if the shut-down file-monitoring job is defined in the start conditions and is to be restarted, you do not want the monitoring status to be inherited.

Specifiable values

Y

The JP1/AJS3 - Manager or JP1/AJS3 - Agent started after the shutdown inherits the pre-shutdown monitoring status of a file-monitoring job.

N

The JP1/AJS3 - Manager or JP1/AJS3 - Agent started after shutdown doe not inherit the pre-shutdown monitoring status of a file-monitoring job.

Default value

N

During a new installation and setup of JP1/AJS3, Y is set.

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service is started

(19) "FileWriteMode" = "{sync|nosync}" (setting for agent processes)

Use this parameter to specify whether to permit synchronous writing when the event or job information and wait information file are updated.

Select the writing method appropriate for performance, reliability, and method of operation.

Specifiable values

sync

Synchronous writing is always performed when a file is updated. This writing mode improves reliability, but reduces the performance.

Select this method when reliability is more important, as in a cluster environment.

nosync

Data is written to a disk in response to OS buffering. There is no synchronization with the JP1/AJS3 processing. This mode provides better performance than sync, but a system failure will lead to inconsistent information, sometimes causing an event to disappear.

Default value

nosync

Recommended value

sync

When the setting takes effect

The next time the JP1/AJS3 service is started

Cautionary note

Specify the same parameter value in the manager process (definition key JP1AJS2\SCHEDULER\EV\MANAGER) and the agent process (definition key JP1AOMAGENT). If you specify nosync for the manager process and sync for the agent process, JP1/AJS3 operation slows down dramatically. This might happen if a jobnet using an event job or a jobnet with a start condition is registered for execution or is killed, or if an OR job preceded by many event jobs is executed. For the same reason, specify the same setting for the manager and the agents in the manager-agent system.

(20) "EVProcessHA" = "{Y|N}"

When event/action control detail processes are terminated with a signal, specify whether to operate at a reduced level without terminating the event/action control agent process, or whether to terminate the processing after stopping all detail processes.

Specifiable values

Y

All the detail processes are stopped, after which the event/action control agent process terminates.

N

Operation continues at a reduced level. The event/action control agent process is not terminated. If some of the detail processes are terminated for a reason such as a signal, you will be able to use only the remaining event jobs that are not affected by those detail processes that have been terminated.

Default value

N

During a new installation and setup of JP1/AJS3, Y is set.

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service is started

Cautionary notes

If you specify Y for the parameter value and then set restarting of the abnormally terminated JP1/AJS3 processes, the agent and detail processes are restarted when the JP1/AJS3 process is restarted. For details about how to restart the abnormally terminated JP1/AJS3 processes, see 7.3.1 Restarting an abnormally terminated JP1/AJS3 process in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

In UNIX, if you specify N for the parameter value and disable the detail process termination option, registering for execution a job related to an abnormally terminated detail process# causes the job to terminate abnormally.

#: For example, run the file-monitoring job when the jpocwtflMain process has terminated abnormally.

(21) "EventSequential" = "{Y|N}"

Use this parameter to specify whether to use the event order option.

Specifiable values

Y

Specify this value to use the event order option.

N

Specify this value if you do not use the event order option.

Default value

N

Recommended value

Default value

When the setting takes effect

The next time the JP1/AJS3 service is started

(22) "RetryAgtStartNotification" = "{Y|N}"

Use this parameter to specify whether to resend the startup notification if sending the startup notification has failed.

Specifiable values

Y

The startup notification is resent.

N

The startup notification is not resent.

Default value

N

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service is started

Cautionary note

For details about the operating environment in which Y must be specified, see 6.3.7 Retrying startup notification of the event/action control agent in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) , or 15.3.7 Retrying startup notification of the event/action control agent in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

(23) "ClientConnectTimeout" = dword:connection-timeout-for-communication-between-the-event/action-control-manager-and-the-event/action-control-agent

Use this parameter to specify how long to wait for a connection if a connection request for a TCP/IP socket does not immediately result in either success or failure.

If the connection request is not completed within the specified time, the request is canceled as a timeout.

For details about setting this environment setting parameter in the manager environment, see 2.6.2(1) ClientConnectTimeout.

Specifiable values

A hexadecimal value (in milliseconds) from 000003E8 to 000927C0 (1,000 to 600,000 in decimal)

Default value

In Windows:

dword:00007530 (30,000 in decimal)

In UNIX:

dword:000003E8 (1,000 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service starts

Cautionary notes

If the TCP/IP connection timeout value set in the OS is less than the value set in this environment setting parameter, the timeout value set in the OS overrides the value of the environment setting parameter.

If this environment setting parameter is omitted, the default value is used.

If a value that cannot be specified for event/action control is specified in this parameter, the default value is used.

(24) "NotificationRetryInterval" = dword:retry-interval-for-sending-unreported-information-from-the-agent-host-to-the-manager-host

Use this parameter to specify the retry interval for sending unreported information from the agent host to the manager host.

For details, see 6.3.13 Changing the send retry interval and the number of retries for sending unreported information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.3.14 Changing the send retry interval and the number of retries for sending unreported information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (in seconds) from 00000001 to 00015180 (1 to 86,400 in decimal)

Default value

dword:0000000A (10 in decimal)

Recommended value

Default value

When the setting takes effect

The next time the JP1/AJS3 service starts

(25) "NotificationRetryCount" = dword:maximum-number-of-retries-for-sending-unreported-information-from-the-agent-host-to-the-manager-host

Use this parameter to specify the maximum number of retries for sending unreported information from the agent host to the manager host.

For details, see 6.3.13 Changing the send retry interval and the number of retries for sending unreported information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.3.14 Changing the send retry interval and the number of retries for sending unreported information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value (number of times) from 00000001 to 00015180 (1 to 86,400 in decimal)

Default value

dword:000021C0 (8,640 in decimal)

Recommended value

Default value

When the setting takes effect

The next time the JP1/AJS3 service starts

(26) "EventServerName" = "event-server-name"

When you execute a log file monitoring job on a host on which an event server that has an FQDN event server name runs, use this parameter to specify the FQDN event server name specified in the JP1/Base event server index file (index).

Specifiable values

A character string of no more than 255 bytes

Default value

Specify the short name of the host on which JP1/AJS3 is running.

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service is started

Cautionary notes

The event server name specified in this option must be the name of an event server that is running on a host on which JP1/AJS3 is running.

Because the event server name specified in this option is case sensitive, use the uppercase and lowercase characters exactly the same way as the FQDN event server name specified in the JP1/Base event server index file (index).

(27) "GetFQDNForShortNameOnly" = "{Y|N}"

Use this parameter to specify whether to acquire the local host name used for interprocess communication for event/action control from DNS. To specify Y for this environment setting parameter, you need to specify Y for the DNSEstablish environment setting parameter.

Specifiable values

Y

An FQDN local host name acquired from DNS is used for interprocess communication for event/action control even if a short local host name is specified for jp1hosts or jp1hosts2.

N

The short local host name specified for jp1hosts or jp1hosts2 is used for interprocess communication for event/action control.

If a short local host name is not specified for jp1hosts or jp1hosts2, an FQDN local host name acquired from DNS is used.

Default value

N

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service is started

Supplementary note

To use the FQDN local host name acquired from DNS for all interprocess communication for event/action control, specify Y for this environment setting parameter for all the following hosts:

Manager host on which the DNSEstablish environment setting parameter is set to Y

Agent host that executes event jobs

(28) "RecvTimeout" = "{Y|N}"

In interprocess communication for event/action control, if data is not delivered to the receiver for some reason, use this parameter to specify whether to terminate the attempt to receive the data so that the system can proceed to other processing.

Specifiable values

Y

If data is not received within the specified period of time, the data receive processing times out.

N

The system waits for data to arrive.

Default value

Y

Recommended value

Default value

When the setting takes effect

The next time the JP1/AJS3 service is started

2.5 Setting for the JP1/AJS3 definition pre-check function

This section describes the environment setting parameters for the JP1/AJS3 definition pre-check function.

2.5.1 List of environment setting parameters for the JP1/AJS3 definition pre-check function

The JP1/AJS3 definition pre-check function requires different settings in the manager environment (JP1/AJS3 - Manager) and the agent environment (JP1/AJS3 - Agent).

For details about the JP1/AJS3 definition pre-check function, see 6.5.1 Setting up the JP1/AJS3 definition pre-check function in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.5.1 Setting up the JP1/AJS3 definition pre-check function in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

The table below lists the environment setting parameters to be used to set the definition pre-check function in the manager environment (JP1/AJS3 - Manager) and agent environment (JP1/AJS3 - Agent).

To determine whether an environment setting parameter is to be set in Windows or UNIX, see the Applicable OS column. To determine whether an environment setting parameter is to be set in the manager environment (JP1/AJS3 - Manager) or the agent environment (JP1/AJS3 - Agent), see the Applicable product column.

Table 2‒6: Environment setting parameters (settings for the JP1/AJS3 definition pre-check function)

No.

Definition key

Environment setting parameter

Definition

Applicable OS

Applicable product

1

[JP1_DEFAULT\JP1AJS2\CHECK]

"AJSCHK_CHECKFILE"=

Name of the file that contains the definition pre-check result

Windows

UNIX

M

2

"AJSCHK_LOGDIR"=

Name of the directory for the definition check log

Windows

UNIX

M, A

3

"AJSCHK_LOGSIZE"=

Size of the definition check log file

Windows

UNIX

M, A

4

"AJSCHK_TRACELOGFILE"=

Name of the trace log file for the definition pre-check function

Windows

UNIX

M, A

5

"AJSCHK_CHARCODE"=

Specifies the character set to be used for an agent in a definition pre-check and the character set to be output in the pre-check result.

Windows

UNIX

M, A

Legend:

M: JP1/AJS3 - Manager

A: JP1/AJS3 - Agent

The following describes each of the environment setting parameters.

Parameters that are not described here are used for maintenance purposes. Do not change their values.

The default value is used whenever a value is not specified for an environment setting parameter.

2.5.2 Details of the environment setting parameters for the JP1/AJS3 definition pre-check function

(1) "AJSCHK_CHECKFILE" = "name-of-the-file-used-to-store-the-definition-pre-check-result"

Use this parameter to specify the name of the file used to the definition pre-check result. Specify a full path name.

If the directory specified for name-of-file-used-to-store-definition-pre-check-result does not exist, the file used to store the definition pre-check result will not be output.

Specifiable values

A character string of no more than 255 bytes

Default value

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\ajscheckfile.txt

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-Manager-installation-folder\log\ajscheckfile.txt

For Windows Server 2003:

JP1/AJS3-Manager-installation-folder\log\ajscheckfile.txt

In UNIX:

/var/opt/jp1ajs2/log/ajscheckfile.txt

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After the JP1/AJS3 Check Manager service is restarted

(2) "AJSCHK_LOGDIR" = "name-of-the-directory-for-the-definition-check-log"

Use this parameter to specify the name of the directory to which the log for the definition pre-check process is output. Specify a full path name.

If the directory specified for name-of-directory-for-definition-check-log does not exist, the definition check log will not be output.

Log data is written to the ajscheck1.log file under the directory specified in this parameter. If the log data written to the ajscheck1.log reaches the size limit specified in the AJSCHK_LOGSIZE environment setting parameter, the writing of log data continues to the ajscheck2.log file.

Specifiable values

A character string of no more than 180 bytes

Default value

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

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

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-Manager-installation-folder\log or JP1/AJS3-Agent-installation-folder\log

For Windows Server 2003:

JP1/AJS3-Manager-installation-folder\log or JP1/AJS3-Agent-installation-folder\log

In UNIX:

/var/opt/jp1ajs2/log

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After the JP1/AJS3 Check Manager service or the JP1/AJS3 Check Agent service is restarted

(3) "AJSCHK_LOGSIZE" = dword:log-file-size

Use this parameter to specify the size of the log file to which log data is output by the definition pre-check process.

The specified size is to the size definition check log file 1 (ajscheck1.log) and of definition check log file 2 (ajscheck2.log).

Specifiable values

0, or a value (in kilobytes) from 4 to 1E8480 in hexadecimal (0, or a value from 4 to 2,000,000 in decimal)

Default value

dword:00001000 (4,096 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After the JP1/AJS3 Check Manager service or the JP1/AJS3 Check Agent service is restarted

Cautionary note

When the information written to file 1 reaches the limit specified in this parameter, the writing of information switches to file 2. When the information written to file 2 reaches the limit, the writing of information switches back to file 1 and existing information is overwritten. Because the repeated switching between files 1 and 2 continually overwrites older information, you must be especially careful when specifying the file size.

(4) "AJSCHK_TRACELOGFILE" = "name-of-the-trace-log-file"

Use this parameter to specify the name of the trace log file for the definition pre-check function. Specify a full path name.

If the directory specified for name-of-trace-log-file does not exist, the trace log will not be output.

Specifiable values

A character string of no more than 255 bytes

Default value

The setup processing assumes the following file name:

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\tracelog.ch

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-Manager-installation-folder\log\tracelog.ch or JP1/AJS3-Agent-installation-folder\log\tracelog.ch

For Windows Server 2003:

JP1/AJS3-Manager-installation-folder\log\tracelog.ch or JP1/AJS3-Agent-installation-folder\log\tracelog.ch

In UNIX:

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

If you do not specify a file name, a trace log is not output.

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After the JP1/AJS3 Check Manager service or the JP1/AJS3 Check Agent service is restarted

(5) "AJSCHK_CHARCODE" = "{none|C|SJIS|EUC|UTF-8}"

Use this parameter to specify the character set to be used for an agent in the definition pre-check and the character set to be output in the pre-check result.

Specifiable values

none

The 7-bit ASCII character set is used.

none cannot be specified by using the jajs_config command. To specify this value, use the jbssetcnf command. For details on the jbssetcnf command, see the Job Management Partner 1/Base User's Guide.

C

The 7-bit ASCII character set is used.

SJIS

The Shift JIS character set is used.

EUC

The EUC character set is used.

UTF-8

The UTF-8 character set is specified.

Default value

none

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After the JP1/AJS3 Check Manager service or the JP1/AJS3 Check Agent service is restarted

Cautionary notes

For agents, the character set specified in this parameter must match the character set specified in the LANG environment variable used when the JP1/AJS3 Check Agent service starts.

In the following cases, the definition pre-check results are displayed by using the character set specified in the AJSCHARCODE environment setting parameter.

- SJIS, EUC, or UTF-8 is specified for the AJSCHARCODE environment setting parameter, and none or C is specified for AJSCHK_CHARCODE.

- C is specified for the AJSCHARCODE environment setting parameter.

2.6 Setting up the communication control environment

This section describes the environment setting parameters for communication control.

2.6.1 List of environment setting parameters for communication control

To set up the communication control environment, perform the necessary setup operations in the manager environment (JP1/AJS3 - Manager). Nothing is required in the agent environment (JP1/AJS3 - Agent).

The table below lists the environment setting parameters to be used to set the communication control environment in the manager environment (JP1/AJS3 - Manager).

To determine whether an environment setting parameter is to be set in Windows or UNIX, see the Applicable OS column.

Table 2‒7: Environment setting parameters (communication control)

No.

Definition key#1

Environment setting parameter

Definition

Applicable OS

Applicable product

1

[{JP1_DEFAULT|logical-host-name}\JP1AJS2\HOST\NETWORK],

[{JP1_DEFAULT|logical-host-name}\JP1AJS2\HOST\NETWORK\subkey]#2, and

[{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name\NETWORK\subkey]#2

"ClientConnectTimeout"=

Connection timeout

Windows

UNIX

M

2

"ClientRetryInterval"=

Connection retry interval

Windows

UNIX

M

3

"ClientRetryCount"=

Number of connection retries

Windows

UNIX

M

Legend:

M: JP1/AJS3 - Manager

#1

Specify JP1_DEFAULT for the physical host. For logical-host-name, specify the name of a logical host.

#2

For subkey, specify QUEUEMANAGER for the job execution control manager, QUEUENOTIFY for the job execution control (Notify), and EVMANAGER for the event/action control manager.

The following explains each of the environment setting parameters.

Parameters that are not described here are used for maintenance purposes. Do not change their values.

The default value is used whenever a value is not specified for an environment setting parameter.

2.6.2 Details of the environment setting parameters for communication control

(1) "ClientConnectTimeout" = dword:connection-timeout-period

Use this parameter to specify the connection timeout value to be used when connecting to JP1/AJS3 - Agent.

Specifiable values

A hexadecimal value (in milliseconds) from 000003E8 to 05265C00 (1,000 to 86,400,000 in decimal)

Default value

dword:00015F90 (90,000 in decimal)

Recommended value

Default value

When the setting takes effect

The next time the JP1/AJS3 service is started

Cautionary notes

If you decrease the connection timeout value, a timeout might occur before connection is completed, resulting in a connection error in TCP/IP communication.

Depending on the connection timeout specifications and the settings for the OS, a connection timeout might occur before the value specified for this environment setting parameter is reached.

If you specify a decimal value larger than 86,400,000, the KAVS1518-E message is output to the integrated trace log, and the JP1/AJS3 service do not start.

If you want to set this parameter on the event/action control manager, see (a) To set the parameter for event/action control.

(a) To set the parameter for event/action control

The following describes the settings of the communication connection timeout value used if you want to set the parameter for the event/action control manager.

This environment setting parameter has no effect if it is specified for the [{JP1_DEFAULT|logical-host-name}\JP1AJS2\HOST\NETWORK]definition key.

Specifiable values

A hexadecimal value (in milliseconds) from 000003E8 to 000927C0 (1,000 to 600,000 in decimal)

Default value

In Windows:

dword:00007530 (30,000 in decimal)

In UNIX:

dword:000003E8 (1,000 in decimal)

During a new installation and setup of JP1/AJS3, dword:00002710 is set.

Recommended value

In Windows:

Set the value appropriate for the operating environment.

In UNIX:

dword:00002710 (10,000 in decimal)

When the setting takes effect

The next time the JP1/AJS3 service starts

Cautionary notes

If the environment setting parameter for event/action control is not specified, the default value is assumed.

If a value that is not within the allowable range of the connection timeout values is specified for event/action control, the default value (30,000 in decimal in Windows or 1,000 in decimal in UNIX) is assumed, and the JP1/AJS3 service start.

If you specify a value larger than 86,400,000 in decimal, the KAVS1518-E message is output to the integrated trace log, and the JP1/AJS3 service do not start.

If you want to set an environment setting parameter for event/action control described here in an agent environment, see 2.4.2(23) ClientConnectTimeout.

(2) "ClientRetryInterval" = dword:connection-retry-interval

Use this parameter to specify the retry interval for the remote connection timeout (includes connection to JP1/AJS3 - Agent). This environment setting parameter has no effect on event/action control.

Specifiable values

A hexadecimal value (in seconds) from 00000000 to 00015180 (0 to 86,400 in decimal)

Default value

dword:00000014 (20 in decimal)

Recommended value

Default value

When the setting takes effect

The next time the JP1/AJS3 service is started

Cautionary note

If you specify a decimal value larger than 86,400, the KAVS1518-E message is output to the integrated trace log, and the JP1/AJS3 service do not start.

(3) "ClientRetryCount" = dword:number-of-connetion-retries

Use this parameter to specify the number of retries for a remote-communication connection timeout occurring when trying to connect to JP1/AJS3 - Agent. This environment setting parameter has no effect on event/action control.

Specifiable values

A hexadecimal value (number of times) from 00000000 to 7FFFFFFF (0 to 2,147,483,647 in decimal)

Default value

dword:00000002 (2 in decimal)

Recommended value

Default value

When the setting takes effect

The next time the JP1/AJS3 service is started

Cautionary note

If you specify a decimal value larger than 2,147,483,647, the KAVS1518-E message is output to the integrated trace log, and the JP1/AJS3 service do not start.

2.7 Setting up the queueless job execution environment

This section describes the environment setting parameters for the queueless job execution environment.

2.7.1 List of environment setting parameters for the queueless job execution environment

As the initial step in setting up a new queueless job execution environment, you must first execute the ajsqlsetup command. For a manager-agent configuration, you must execute the ajsqlsetup command for both the manager and agent.

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

To set up the queueless job execution environment, use the queueless agent environment (queueless agent service).

The table below lists the environment setting parameters to be used to set up the queueless job execution environment in the manager environment (JP1/AJS3 - Manager) and the agent environment (JP1/AJS3 - Agent).

Note that the environment setting parameters to be used to set up a queueless job execution environment cannot be specified by using the jajs_config command. Use the jbssetcnf command. For details on the jbssetcnf command, see the Job Management Partner 1/Base User's Guide.

To determine whether an environment setting parameter is to be set in Windows or UNIX, see the Applicable OS column. To determine whether an environment setting parameter is to be set in the manager environment (JP1/AJS3 - Manager) or the agent environment (JP1/AJS3 - Agent), see the Applicable product column.

Table 2‒8: Environment setting parameters (queueless job execution environment setup)

No.

Definition key

Environment setting parameter

Definition

Applicable OS

Applicable product

1

[JP1_DEFAULT\JP1AJSMANAGER]#1

"QLMANCHARCODE"=

Settings for correctly executing a job on an agent that does not support UTF-8 when a manager in a UTF-8 environment is managing queueless jobs.

UNIX

M

2

[JP1_DEFAULT\JP1QLAGENT]

"AJSQL_JOBMAX"=

Maximum number of simultaneous jobs within a queueless agent service

Windows

UNIX

M, A

3

"AJSQL_CHARCODE"=

Language encoding used to display job information and job output results

Windows

UNIX

M, A

4

"AJSQL_JOBWAITMAX"=

Maximum number of waiting jobs within a queueless agent service

Windows

UNIX

M, A

5

"AJSQL_NOATTACHREQ"=

Processing when the execution on an unattached logical host is requested

Windows

UNIX

M, A

6

"AJSQL_EXECCURRENTSCRIPT"=

Whether to execute a script file in the current path

UNIX

M, A

7

"AJSQL_TRACELOGFILE"=

Trace-log file name

Windows

UNIX

M, A

8

"AJSQL_VARDQUOTEADD"=

Processing for converting a $JP1AJS2_JPQTEMPxx$ variable

Windows

UNIX

M, A

9

"AJSQL_CONNECTTIMEOUT"=

Length of time before an attempt to connect to the queueless file transfer service for communication times out

Windows

UNIX

M, A

10

"AJSQL_CONNECTCOUNT"=

Number of retries when attempting to connect to the queueless file transfer service

Windows

UNIX

M, A

11

"AJSQL_CONNECTINT"=

Retry interval when attempting to connect to the queueless file transfer service for communication

Windows

UNIX

M, A

12

"DISABLE_FS_REDIRECTION"=

Setting for disabling file system redirection when jobs are executed in the WOW64 environment

Windows

M, A

13

"ENABLE_LONG_EXT"=

Setting for whether to execute a job specified for an executable file whose extension is 4 bytes or more in an application associated with the executable-file extension

Windows

M, A

14

"AJSQL_CREATEWINDOWSTATION"=

Setting for preventing a problem whereby a queueless job ends abnormally with return value 128

Windows

M, A

15

"AJSQL_EXECLOG"=

Whether to enable the internal log output function for queueless job execution

Windows

UNIX

M, A

16

"AJSQL_EXECLOG_FTPPATH"=

Name of the folder used to store the queueless job execution internal log output by the queueless file transfer service

Windows

UNIX

M

17

"UACAdministratorsExec"=

Settings for executing jobs as a user with administrator permissions when UAC is enabled

Windows

M, A

18

"AJSQL_GETPASSWD_FTPRETRYCOUNT"=

Number of retry attempts when the queueless file transfer service has failed to acquire user information from the OS password file

UNIX

M

19

"AJSQL_GETPASSWD_FTPRETRYINTERVAL"=

Retry interval when the queueless file transfer service has failed to acquire user information from the OS password file

UNIX

M

20

"IgnoreResultFileError"=

Operation if an error occurs during the transfer processing of a queueless job result file

Windows

UNIX

M, A

21

[{JP1_DEFAULT|logical-host-name}\JP1QLAGENT]#2

"AJSQL_LOGFILE"=

Log folder name

Windows

UNIX

M, A

22

"AJSQL_LOGSIZE"=

Log file size

Windows

UNIX

M, A

23

"AJSQL_STATFILE"=

Status file name

Windows

UNIX

M, A

24

"AJSQL_STATSIZE"=

Status file size

Windows

UNIX

M, A

25

"AJSQL_ATTACH"=

Whether to attach the logical host set when the queueless agent service starts

Windows

UNIX

M, A

26

"AJSQL_EXECLOG_AGTPATH"=

Name of the folder used to store the internal log of the queueless job execution output by the queueless agent service

Windows

UNIX

M, A

27

"AJSQL_AGTWORKPATH"=

Workpath used in a queueless job and the name of a directory for temporary files

Windows

UNIX

M, A

28

"AJSQL_LOADUSERPROFILE"=

Definition of whether to load the user profile

Windows

M, A

29

"AJSQL_GETPASSWD_AGTRETRYCOUNT"=

Number of retry attempts when the queueless agent service has failed to acquire user information from the OS password file

UNIX

M, A

30

"AJSQL_GETPASSWD_AGTRETRYINTERVAL"=

Retry interval when the queueless agent service has failed to acquire user information from the OS password file

UNIX

M, A

31

[logical-host-name\JP1QLAGENT]

"AJSQL_CLUSTERREQ"=

Processing to be performed if a queueless cluster process is unable to attach a logical host

Windows

M, A

32

[{JP1_DEFAULT|logical-host-name}\JP1QLAGENT\AJSQL_CLASS\class-name]#2

"AJSQL_CJOBMAX"=

Maximum number of jobs that can be executed simultaneously within a class

Windows

UNIX

M, A

33

"AJSQL_CJOBWAITMAX"=

Maximum number of waiting jobs within a class

Windows

UNIX

M, A

Legend:

M: JP1/AJS3 - Manager

A: JP1/AJS3 - Agent

#1

This definition key can be specified in UNIX only.

#2

Specify JP1_DEFAULT for the physical host. For logical-host-name, specify the name of a logical host.

The following describes each of the environment setting parameters.

Parameters that are not described here are used for maintenance purposes. Do not change their values.

The default value is used whenever a value is not specified for an environment setting parameter.

2.7.2 Details of the environment setting parameters for the queueless job execution environment

(1) "QLMANCHARCODE" = "{none|UTF-8}"

Use this parameter to specify settings for correctly executing a job on an agent that does not support UTF-8 when a manager in a UTF-8 environment is managing queueless jobs.

Because an agent that does not support UTF-8 does not support UTF-8 character code conversion, you need to specify UTF-8 as the environment setting parameter to allow the manager to perform the character code conversion.

Specifiable values

none

The manager does not perform character code conversion. Specify this value only when all the applicable queueless agents operate in a UTF-8 environment.

UTF-8

The manager converts UTF-8 into character codes that the queueless agent supports and communicates with the queueless agent. Specify this value if one or more queueless agents do not operate in a UTF-8 environment.

Default value

none

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After restart of the JP1/AJS3 Queueless File Transfer service and restart of the scheduler service

Cautionary notes

In a Linux environment in which a queueless job has never been set up, UTF-8 is set when you execute the ajsqlsetup command.

Set this environment setting parameter only when the character set of the manager (the value of the AJSCHARCODE environment setting parameter) is UTF-8. If the character set of the manager is not UTF-8, do not set this environment setting parameter.

The character code conversion in this environment setting parameter applies only to data that is related to queueless jobs.

If you specify UTF-8 for this environment setting parameter, you must specify the agent character set for the AJSQL_CHARCODE environment setting parameter on all the agent hosts, including the local host.

Whereas the AJSCHARCODE environment setting parameter is set individually for scheduler services, the QLMANCHARCODE environment setting parameter is set for a single host. If you specify UTF-8 for the QLMANCHARCODE environment setting parameter, also specify UTF-8 for the AJSCHARCODE environment setting parameter for each of the scheduler services.

(2) "AJSQL_JOBMAX" = dword:maximum-number-of-concurrently-executable-jobs-within-a-queueless-agent-service

Use this parameter to specify the maximum number of concurrently executable jobs within a queueless agent service.

Specify this parameter if you want to limit the number of concurrently executable queueless jobs according to available machine resources.

If the number of jobs exceeds the specified value, the jobs exceeding the value enter the wait status (pooled in memory of the queueless agent). For details about how to specify the number of jobs that can wait, see the explanation of the AJSQL_JOBWAITMAX environment setting parameter.

Specifiable values

A hexadecimal value from 0 to 400 (0 to 1,024 in decimal)

Default value

In Windows:

dword:00000005 (5 in decimal)

In UNIX:

dword:00000400 (1,024 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted

(3) "AJSQL_CHARCODE" = "{none|C|SJIS|EUC|UTF-8}"

Character code conversion is required when you use a queueless job in either of the following environments. In these cases, specify the character set to be used when a queueless job is executed on the agent host.

Environment in which the character sets of the manager host and the agent host are different

Environment in UTF-8 is specified for the QLMANCHARCODE environment setting parameter on the manager host.

Specifiable values

none

The 7-bit ASCII character set is used. There is no character code conversion between the manager and the agent.

C

The 7-bit ASCII character set is used. There is no character code conversion between the manager and the agent.

SJIS

The Shift JIS character set is used.

EUC

The EUC character set is used.

UTF-8

The UTF-8 character set is specified.

Default value

none

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted

Cautionary notes

The character string used when a queueless job is executed is not encoded with the character set of the JP1/AJS3 service. Instead, the LANG environment variable value specified when the queueless agent service is started is used.

Specify this environment setting parameter on the host used as an agent.

(4) "AJSQL_JOBWAITMAX" = dword:maximum-number-of-waiting-jobs-within-the-queueless-agent-service

Use this parameter to specify the maximum number of jobs that are allowed to wait within a queueless agent service.

Specify this parameter if the peak number of queueless jobs that are being executed exceeds the maximum number of simultaneous jobs.

If the number of jobs exceeds the specified value, the queueless job fails to start.

Specifiable values

A hexadecimal value from 0 to 19000 (0 to 102,400 in decimal)

Default value

In Windows:

dword:00000800 (2,048 in decimal)

In UNIX:

dword:00000000

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted

(5) "AJSQL_NOATTACHREQ" = "{exec|error}"

Use this parameter to specify the processing for a request for execution on an unattached logical host.

Specifiable values

exec

The request is processed on the physical host.

error

The request results in an error.

Default value

exec

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted

(6) "AJSQL_EXECCURRENTSCRIPT" = "{yes|no}"

If you use a relative path to specify the script file, you need to specify whether a script file already in the current path is to be executed when a job is executed.

The current path is the path specified for Working path. If a path is not specified for Working path, the home directory of the OS user who executes the job is used as the current path.

Specifiable values

yes

The script file in the current path has priority.

no

When a job is executed, the path in the PATH environment variable is followed to find and execute the target script file.

Default value

no

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted

Cautionary note

If you specify yes for this parameter, the current path is searched to locate the script file. Therefore, the job will fail to start if a hard disk failure or another problem causes the search for the script file to fail.

(7) "AJSQL_TRACELOGFILE" = "trace-log-file-name"

Use this parameter to specify the full path name of the queueless trace log file.

If you do not specify this parameter, a trace log is not output.

Specifiable values

A character string of no more than 255 bytes

Default value

The following file name is assumed at setup.

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\tracelog.ql

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-installation-folder\log\tracelog.ql

For Windows Server 2003:

JP1/AJS3-installation-folder\log\tracelog.ql

In UNIX:

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

Recommended value

Default value

When the setting takes effect

For the JP1/AJS3 Queueless Agent service:

After the JP1/AJS3 Queueless Agent service is restarted

For the JP1/AJS3 Queueless File Transfer service:

After the JP1/AJS3 Queueless File Transfer service is restarted

For the JP1/AJS3 service:

After the JP1/AJS3 service is restarted

(8) "AJSQL_VARDQUOTEADD" = "{yes|no}"

When a $JP1AJS2_JPQTEMPxx$ variable is converted, use this parameter to select whether to enclose the variable value after conversion in double quotation marks (").

The setting of this parameter is valid for the physical host and all logical hosts.

Specifiable values

yes

The variable value after conversion is enclosed in double quotation marks (").

no

The variable value after conversion is not enclosed in double quotation marks (").

Default value

yes

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted

(9) "AJSQL_CONNECTTIMEOUT" = dword:connection-timeout-value

Use this parameter to specify the length of time before an attempt to the connect to the queueless file transfer service times out.

Specifiable values

A hexadecimal value (in seconds) from 00000000 to 00000258 (0 to 600 in decimal).

If you specify dword:00000000, the timeout value depends on the connection timeout value of the OS.

Default value

dword:0000000A (10 in decimal)

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted

(10) "AJSQL_CONNECTCOUNT" = dword:number-of-connection-retries

Use this parameter to specify the number of retries to be attempted if a communication error occurs during processing to connect to the queueless file transfer service.

Specifiable values

A hexadecimal value (in seconds) from 00000000 to 00000064 (0 to 100 in decimal)

Default value

dword:00000003 (3 in decimal)

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted

(11) "AJSQL_CONNECTINT" = dword:retry-interval-for-communication-connection

Use this parameter to specify the retry interval if a communication error occurs during processing to connect to the queueless file transfer service.

Specifiable values

A hexadecimal value (in seconds) from 00000000 to 0000003C (0 to 60 in decimal)

Default value

dword:00000001 (1 in decimal)

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted

(12) "DISABLE_FS_REDIRECTION" = dword:setting-value

Use this parameter to specify whether to disable file system redirection when jobs are executed in the WOW64 environment and Queueless Agent is specified for Exec. service.

For details, see 6.6.2 Disabling file system redirection when jobs are executed in a WOW64 environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

0

File system redirection is enabled when jobs are executed in the WOW64 environment.

1

File system redirection is disabled when jobs are executed in the WOW64 environment.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted

(13) "ENABLE_LONG_EXT" = dword:setting-value

Use this parameter to specify whether to execute a job specified for an executable file whose extension is 4 bytes or more in an application associated with the executable-file extension when Queueless Agent has been specified for Exec. service.

For details, see 6.2.18 Executing a job whose executable file name has an extension longer than three bytes in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

0

Although the executable-file extension is 4 bytes or more, the job specified for the file is executed in the application that is associated with the first three digits of the executable-file extension.

If the system cannot find the application that is associated with the first three digits of the extension, the job does not start.

1

If the executable-file extension is 4 bytes or more, the job is executed in the application that is associated with the extension.

If Standard is specified for Exec. service, the job is executed with a long file name when the executable file is executed with an extension of 4 bytes or more.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted

(14) "AJSQL_CREATEWINDOWSTATION" = "{yes|no}"

Use this parameter to specify whether to prevent a problem whereby a job ends abnormally with return value 128.

For details, see 6.4.3 Preventing a queueless job from ending abnormally with return value 128 in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

yes

A problem whereby a job ends abnormally with return value 128 is prevented.

no

A problem whereby a job ends abnormally with return value 128 is not prevented.

Default value

no

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted

(15) "AJSQL_EXECLOG" = "{yes|no}"

Use this parameter to specify whether to enable the internal log output function for queueless job execution.

Specifiable values

yes

The internal log output function for the queueless job execution is enabled.

no

The internal log output function for the queueless job execution is disabled.

Default value

yes

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless Agent service or the JP1/AJS3 Queueless File Transfer service is restarted

(16) "AJSQL_EXECLOG_FTPPATH" = "name-of-the-directory-used-to-store-the-internal-log-output-by-the-queueless-file-transfer-service"

Use this parameter to specify the name of the directory used to store the internal log data output by the queueless file transfer service. Specify a full path name.

Specifiable values

A character string of no more than 200 bytes

Default value

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

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

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-Manager-installation-folder\log

For Windows Server 2003:

JP1/AJS3-Manager-installation-folder\log

In UNIX:

/var/opt/jp1ajs2/log

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless File Transfer service is restarted

Cautionary note

Specify the name of a directory on the local disk.

(17) "UACAdministratorsExec" = dword:setting

Use this parameter to specify whether a user can execute queueless jobs as a user with administrator permissions when the UAC function is enabled.

Note that this parameter is disabled in Windows Server 2003.

For details, see 6.2.22 Settings for executing jobs as a user with administrator permissions when the UAC is enabled in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

0

When the UAC is enabled, all OS users who belong to the Administrators group execute jobs with the administrator permissions disabled. Excluded, however, is the built-in Administrator.

1

When the UAC is enabled, an OS user who belongs to the Administrators group executes jobs as a user with administrator permissions.

When you specify 1, the Log on as a batch job permission must be set for all OS users (including standard users) who execute jobs.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted

(18) "AJSQL_GETPASSWD_FTPRETRYCOUNT" = dword: number-of-retry-attempts-when-an-attempt-to-acquire-user-information-from-the-OS-password-file-has-failed

Use this parameter to specify the number of retry attempts when the queueless file transfer service has failed to acquire user information from the OS password file.

Usually, you do not need to change this value.

For details, see 15.2.20 Changing the settings for retries when user information is acquired in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

A hexadecimal value from 00000000 to 0000000A (0 to 10 in decimal)

If you specify dword:00000000, a retry is not performed.

Default value

dword:00000002 (2 in decimal)

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless File Transfer service is restarted

(19) "AJSQL_GETPASSWD_FTPRETRYINTERVAL" = dword: retry-interval-when-an-attempt-to-acquire-user-information-from-the-OS-password-file-has-failed

Use this parameter to specify the retry interval when the queueless file transfer service has failed to acquire user information from the OS password file.

Usually, you do not need to change this value.

For details, see 15.2.20 Changing the settings for retries when user information is acquired in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

A hexadecimal value (in milliseconds) from 00000000 to 00002710 (0 to 10,000 in decimal)

If you specify dword:00000000, a retry is performed immediately.

Default value

dword:000003E8 (1,000 in decimal)

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless File Transfer service is restarted

(20) "IgnoreResultFileError" = dword:operation-if-a-transfer-error-occurs-in-a-job-result-file

Use this parameter to specify the operation to be executed if, after a job process has finished, an error occurs during the transfer processing of a job result file (standard output file or standard error output file).

For details, see 6.2.24 Operation settings when job result file transfer fails in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (Windows), or 15.2.22 Operation settings when job result file transfer fails in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (UNIX).

Specifiable values

0

If an error occurs during the transfer processing of a job result file, -1 is set as the job return code and the job status is set to Ended abnormally.

1

If an error occurs during the transfer processing of a job result file, the return code of the job process is set as the job return code and the job status is set to Ended normally, Ended with warning, or Ended abnormally according to how the end of processing is judged.

Default value

dword:00000000(0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(21) "AJSQL_LOGFILE" = "log-folder-name"

Use this parameter to specify the name of the log folder to which the messages related to starting and ending executed jobs are output. Specify a full path name.

Specifiable values

A character string of no more than 180 bytes

Default value

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

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

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-installation-folder\log

For Windows Server 2003:

JP1/AJS3-installation-folder\log

In UNIX:

For a physical host: /var/opt/jp1ajs2/log

For a logical host: shared-directory-name/jp1ajs2/log

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted or the logical host is attached

(22) "AJSQL_LOGSIZE" = dword:log-file-size

Use this parameter to specify the size of the log file.

Because this log file used to check the job execution status, specify a size that is sufficient for storing the log data for at least one day.

As the log file, the system uses two files (file 1 and file 2), each of which has the size specified for this parameter.

Specifiable values

0 or a value (in kilobytes) from 4 to 1E8480 in hexadecimal (0 or a value from 4 to 2,000,000 in decimal)

Default value

dword:00002000 (8,192 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted or the logical host is attached

Cautionary note

When the information written to file 1 reaches the limit specified in this parameter, the writing of information switches to file 2. When the information written to file 2 reaches the limit, the writing of information switches back to file 1 and existing information is overwritten. Because the repeated switching between files 1 and 2 continually overwrites older information, you must be especially careful in specifying the file size.

(23) "AJSQL_STATFILE" = "status-file-name"

Use this parameter to specify the name of the status file used to store information about running jobs. Specify a full path name.

Specifiable values

A character string of no more than 255 bytes

Default value

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\ajsqlstat.dat

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-installation-folder\log\ajsqlstat.dat

For Windows Server 2003:

JP1/AJS3-installation-folder\log\ajsqlstat.dat

In UNIX:

For a physical host: /var/opt/jp1ajs2/log/ajsqlstat.dat

For a logical host: shared-directory-name/jp1ajs2/log/ajsqlstat.dat

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted or the logical host is attached

(24) "AJSQL_STATSIZE" = dword:status-file-size

Use this parameter to specify the size of the status file used to store information about running jobs.

When the a status file is used, although nodes are switched for the requesting scheduler service and executing queueless agent before job-end results are reported to the requesting manager, the job-end results can be reported after a restart.

The job status can be managed on the manager side even if the scheduler service requesting execution of a queueless job fails during job execution. If you want to improve the reliability, specify this parameter.

One kilobyte corresponds to the information for about 9 jobs.

Specifiable values

0 or a value (in kilobytes) from 4 to 1E8480 in hexadecimal (0 or 4 to 2,000,000 in decimal)

Default value

dword:00000800 (2,048 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted or the logical host is attached

Cautionary note

If you specify 0 for this parameter, the information about running jobs is not stored. If nodes are switched for the scheduler service requesting execution during job execution, the end status of a running job will be unknown.

If you specify a non-zero value, the job status might be displayed as Ended abnormally even if the job itself has terminated normally. This is because an attempt to transfer output (the information sent by the job to the standard error output) from the agent host to the manager host has failed. You can prevent this problem from occurring by only sending output to the standard error output when an error occurs.

(25) "AJSQL_ATTACH" = "{yes|no}"

Use this parameter to specify whether to attach the logical host that was set when the queueless agent service stared.

This item is effective only if you specify the logical host key.

Specifiable values

yes

The logical host is attached.

no

The logical host is not attached.

To enable the logical host to be used, use the ajsqlattach command to attach it after starting the queueless agent service.

Default value

no

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted

(26) "AJSQL_EXECLOG_AGTPATH" = "name-of-the-directory-used-to-store-the-internal-log-output-by-the-queueless-agent-service"

Use this parameter to specify the name of the directory used to store the internal log data output by the queueless agent service. Specify a full path name.

Specifiable values

A character string of no more than 200 bytes

Default value

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

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

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-installation-folder\log

For Windows Server 2003:

JP1/AJS3-installation-folder\log

In UNIX:

/var/opt/jp1ajs2/log

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted or the logical host is attached

Cautionary note

Specify the name of a directory on the local disk.

The directory name for cluster use is as follows:

name-of-the-directory-used-to-store-the-internal-log-output-by-the-queueless-agent-service/ajsqlexeclog-[logical-host-name]

If the full path name is 256 bytes or more, the first 30 bytes are used as the logical host name specified for logical-host-name.

If there are multiple logical hosts satisfying the above conditions and the first 30 bytes of their names are the same, the internal logs of these logical hosts are output to the same file. However, if the internal logs of multiple logical hosts are output to the same file, starting the queueless job might slow down and the output of internal logs might fail.

If the internal logs of multiple logical hosts will be output to the same file, specify a different directory path for the AJSQL_EXECLOG_AGTPATH environment setting parameter for each logical host, so that the internal logs will be output to different files. If you change the value of the AJSQL_EXECLOG_AGTPATH environment setting parameter to a non-default value, you also have to edit the contents of the data collection sample script. For details, see 7.1 Collecting log data in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

(27) "AJSQL_AGTWORKPATH" = "work-path-used-in-the-queueless-job-and-the-name-of-the-directory-for-temporary-files"

Use this parameter to specify the work path to be used for queueless jobs and the name of the directory to be used for temporary files. Specify a full path name.

Specifiable values

A character string of no more than 100 bytes

Default value

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\tmp

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-installation-folder\tmp

For Windows Server 2003:

JP1/AJS3-installation-folder\tmp

In UNIX:

/var/opt/jp1ajs2/tmp

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted or the logical host is attached

(28) "AJSQL_LOADUSERPROFILE" = "{yes|no}"

Use this parameter to specify whether to load user the profile information about the OS user who executes a job when a job is executed.

Specify this parameter value if the user information must be set in the logon session of the OS user when PC jobs are executed.

For details, see 6.4.2 Executing a job that requires a user profile in a queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

yes

Specify this value to load the user profile.

no

Specify this value if you do not want to load the user profile.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted

(29) "AJSQL_GETPASSWD_AGTRETRYCOUNT" = dword: number-of-retry-attempts-when-an-attempt-to-acquire-user-information-from-the-OS-password-file-has-failed

Use this parameter to specify the number of retry attempts when the queueless agent service has failed to acquire user information from the OS password file.

Usually, you do not need to change this value.

For details, see 15.2.20 Changing the settings for retries when user information is acquired in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

A hexadecimal value from 00000000 to 0000000A (0 to 10 in decimal)

If you specify dword:00000000, a retry is not performed.

Default value

dword:00000002 (2 in decimal)

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted or the logical host is attached

(30) "AJSQL_GETPASSWD_AGTRETRYINTERVAL" = dword: retry-interval-when-an-attempt-to-acquire-user-information-from-the-OS-password-file-has-failed

Use this parameter to specify the retry interval when the queueless agent service has failed to acquire user information from the OS password file.

Usually, you do not need to change this value.

For details, see 15.2.20 Changing the settings for retries when user information is acquired in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

A hexadecimal value (in milliseconds) from 00000000 to 00002710 (0 to 10,000 in decimal)

If you specify dword:00000000, a retry is performed immediately.

Default value

dword:000003E8 (1,000 in decimal)

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted or the logical host is attached

(31) "AJSQL_CLUSTERREQ" = "{exec|error}"

Use this parameter to specify whether to abnormally terminate a queueless cluster process if it fails to attach a logical host.

Specifiable values

exec

The startup of the process continues, and the queueless cluster process does not terminate abnormally. Startup of the JP1/AJS3 service also continues.

If you specify exec, startup of the process continues even if an attempt to attach a logical host fails. Accordingly, you need to execute the ajsqlstatus command after nodes are switched, to check whether the logical host has been attached successfully. If the attachment has failed, use the integrated trace log to determine the cause of the error and then correct the error. You can then use the ajsqlattach command to attach the logical host.

error

The queueless cluster process terminates abnormally. Startup of the JP1/AJS3 service also terminates abnormally.

Default value

exec

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 service is restarted

(32) "AJSQL_CJOBMAX" = dword:maximum-number-of-simultaneous-jobs-within-a-class

Use this parameter to specify the maximum number of jobs that can be executed simultaneously within a class.

For details, see 6.4.1 Executing jobs with a class specified in a queueless job environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.4.1 Executing jobs with a class specified in a queueless job environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value from 0 to 400 (0 to 1,024 in decimal)

Default value

In Windows:

dword:00000005 (5 in decimal)

In UNIX:

dword:00000400 (1,024 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted or the logical host is attached

(33) "AJSQL_CJOBWAITMAX" = dword:maximum-number-of-jobs-that-can-wait-in-a-class

Use this parameter to specify the maximum number of queueless jobs that can be stored in queueless agent service memory if the number of jobs exceeds the maximum number of simultaneous jobs in the class.

For details, see 6.4.1 Executing jobs with a class specified in a queueless job environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.4.1 Executing jobs with a class specified in a queueless job environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

A hexadecimal value from 0 to 19000 (0 to 102,400 in decimal)

Default value

In Windows:

dword:00000800 (2,048 in decimal)

In UNIX:

dword:00000000 (0 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After the JP1/AJS3 Queueless Agent service is restarted or the logical host is attached

2.8 Setting up the JP1/AJS3 Console environment

This section describes the environment setting parameters for JP1/AJS3 Console.

2.8.1 List of the environment setting parameters for JP1/AJS3 Console

Setup of the JP1/AJS3 Console environment that enables centralized monitoring of jobs during automatic operation, differs between the JP1/AJS3 Console Manager environment and the JP1/AJS3 Consol Agent environment.

For JP1/AJS3 Console Manager, set the definition key [JP1_DEFAULT\JP1AJS2CONSOLEMANAGER]. Even if you use a logical host still use the value of the JP1_DEFAULT host key for all environment setting parameters other than DATADIRECTORY.

For JP1/AJS3 Console Agent, set the definition key [JP1_DEFAULT\JP1AJS2CONSOLEAGENT]. If you plan to monitor logical host objects, set environment setting parameters under the JP1_DEFAULT host key.

The table below lists the JP1/AJS3 Console Manager environment setting parameters to be set in JP1/AJS3 Console Manager environment, and the JP1/AJS3 - Console Agent environment setting parameters to be set in the JP1/AJS3 - Agent environment.

To determine whether an environment setting parameter is to be set in Windows or UNIX, see the Applicable OS column. To determine whether an environment setting parameter is to be set in the manager environment (JP1/AJS3 Console Manager) or the agent environment (JP1/AJS3 Console Agent), see the Applicable product column.

Table 2‒9: Environment setting parameters (JP1/AJS3 Console environment setup)

No.

Environment setting parameter

Definition and default value

Applicable OS

Applicable product

1

"MAXSESSION"=

Maximum number of simultaneous sessions

Windows

UNIX

M, A

2

"IPC_TIMEOUT"=

Remote communication timeout period

Windows

UNIX

M

3

"IPCRETRYINTERVAL"=

Retry interval

Windows

UNIX

M

4

"IPCRETRYCOUNT"=

Number of retries

Windows

UNIX

M

5

"SESSIONTIMEOUT"=

Connection timeout period

Windows

UNIX

M

6

"CHARCODE"=

Character set used for information to be stored in user-defined data

Windows

UNIX

M

7

"SYSLOGCODE"=

Character set used to output a log file

UNIX

M, A

8

"HNTRLOGLEVEL"=

Level of messages to be output to the integrated trace log

Windows

UNIX

M, A

9

"DATADIRECTORY"=

Name of the data directory for root scope

Windows

UNIX

M

10

"RECONNECTINTERVAL"=

Interval at which reconnection to JP1/AJS3 Console Agent is attempted.

Windows

UNIX

M

11

"TRACELOGFILE"=

Name of the trace log file for JP1/AJS3 Console Manager

Windows

UNIX

M, A

12

"IPC_CONNECTTIMEOUT"=

Remote connection timeout value

Windows

UNIX

M

13

"ENABLEOPERATION"=

Permission for operation functions

Windows

UNIX

A

Legend:

M: JP1/AJS3 Console Manager

A: JP1/AJS3 Console Agent

Note

If there is an error in the specification of the DATADIRECTORY environment setting parameters, a login error occurs in JP1/AJS3 Console View. If there is an error in the specification of the environment setting parameters other than DATADIRECTORY, the system assumes the standard JP1/AJS3 Console Manager setting.

The following describes each of the environment setting parameters.

Parameters that are not described here are used for maintenance purposes. Do not change their values.

The default value is used whenever a value is not specified for an environment setting parameter.

2.8.2 Details of the environment setting parameters for JP1/AJS3 Console

(1) "MAXSESSION" = dword:maximum-number-of-simultaneous-sessions

Use this parameter to specify the maximum number of JP1/AJS3 Console View connections in JP1/AJS3 Console Manager, and the maximum number of JP1/AJS3 Console Manager connections in JP1/AJS3 Console Agent.

If the maximum number of JP1/AJS3 Console View or JP1/AJS3 Console Manager connections is more than 16, specify a suitable value for the number. If resources are limited, decrease the value to limit the number of JP1/AJS3 Console View or JP1/AJS3 Console Manager connections.

An error occurs if the number of JP1/AJS3 Console View or JP1/AJS3 Console Manager connections exceeds the specified value.

Specifiable values

A hexadecimal value from 0 to 40 (0 to 64 in decimal)

Default value

dword:00000010 (16 in decimal)

Recommended value

Default value

When the setting takes effect

For JP1/AJS3 Console Manager:

After the JP1/AJS3 Console Manager service is restarted

For JP1/AJS3 Console Agent:

After the JP1/AJS3 Console Agent service is restarted

(2) "IPC_TIMEOUT" = dword:connection-timeout

Use this value to specify the timeout period for establishing communication with JP1/AJS3 Console Agent.

If communication cannot be established within the specified time, an error occurs. In that case, control is determined by the OS timeout period.

Specify a value other than 0 if you want to set an explicit timeout period rather than depend on the OS timeout period.

Specifiable values

A hexadecimal value (in seconds) from 0 to 258 (0 to 600 in decimal)

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Console Manager service is restarted

(3) "IPCRETRYINTERVAL" = dword:retry-interval

Use this parameter to specify the retry interval when a communication error occurs.

Depending on the communication error status, change the parameter value and the value for the IPCRETRYCOUNT environment setting parameter (number of retries).

Each time a retry occurs, the specified value increases.

Specifiable values

A hexadecimal value (in seconds) from 0 to A (0 to 10 in decimal)

Default value

dword:00000001 (1 in decimal)

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Console Manager service is restarted

(4) "IPCRETRYCOUNT" = dword:number-of-retries

Use this parameter to specify the number of retries to be performed when a communication error occurs.

Depending on the communication error status, change the parameter value and the value for the IPCRETRYINTERVAL environment setting parameter (retry interval).

Specifiable values

A hexadecimal value from 0 to 64 (0 to 100 in decimal)

Default value

dword:00000003 (3 in decimal)

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Console Manager service is restarted

(5) "SESSIONTIMEOUT" = dword:connection-timeout-period

Use this parameter to specify how long the system waits after the last communication with JP1/AJS3 Console View before it severs the connection.

Specifiable values

In Windows:

A hexadecimal value (in minutes) from 0 to 78 (0 to 120 in decimal)

In UNIX:

A hexadecimal value (in minutes) from 1 to 78 (1 to 120 in decimal)

Default value

dword:00000078 (120 in decimal)

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Console Manager service is restarted

(6) "CHARCODE" = "{C|SJIS|EUC|UTF-8}"

Use this parameter to specify only one character set that is to be used for the name and definitions of the nested application scope or monitored objects.

Specifiable values

C

The ASCII character set

SJIS

The Shift JIS character set

EUC

The EUC character set

UTF-8

The UTF-8 character set

Note: UTF-8 is enabled for UNIX only.

Default value

C

When you execute setup, the following value is automatically set.

In Windows

SJIS

In UNIX

Solaris: EUC

Linux: UTF-8

Other OSs: SJIS

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Console Manager service is restarted

Cautionary note

If you change the CHARCODE environment setting parameter in the environment settings of JP1/AJS3 Console Manager, and the value you are changing is SJIS or EUC, make sure that the definition data does not contain any Japanese characters (characters other than ASCII characters).

If the definition data contains Japanese characters (characters other than ASCII characters), do not change the CHARCODE environment setting parameter.

(7) "SYSLOGCODE" = "{C|LANG-environment-variable-value}"

Use this parameter to specify the language type of the messages that are output to the syslog file.

Specifiable values

C

Messages are output in English ASCII character set.

LANG-environment-variable-value (character string other than C)

Operation depends on the settings of the LANG environment variable at the time the JP1/AJS3 Console Manager service for JP1/AJS3 Console Manager or the JP1/AJS3 Console Agent service for JP1/AJS3 Console Agent starts. However, in some systems, a message in the language type corresponding to the LANG environment variable for the JP1/AJS3 Console Manager service or the JP1/AJS3 Console Agent service might not be output to syslog. In such a system, make sure that this parameter is set to C. Check whether Japanese can be output in the system you are using by executing the logger command to output a message in Japanese and then confirming that the message is correctly output to syslog.

The LANG environment variable value differs depending on the OS.

The following table describes the values that can be specified for the LANG environment variable.

Table 2‒10: Specifiable values of the LANG environment variable

OS

Environment variable value for setting Shift JIS

Environment variable value for setting EUC

Environment variable value for setting UTF-8#1

HP-UX

ja_JP.SJIS

japanese

ja_JP.eucJP

japanese.euc

ja_JP.utf8

Solaris

ja_JP.PCK

ja#2

ja_JP.eucJP#2

ja_JP.UTF-8

AIX

Ja_JP

Ja_JP.IBM-932

ja_JP

ja_JP.IBM-eucJP

JA_JP

JA_JP.UTF-8

Linux

Not available

Not available

ja_JP.UTF-8

ja_JP.utf8

#1

In compatible ISAM configuration, UTF-8 can be used in Linux only.

#2

In Solaris 11, ja and ja_JP.eucJP can be used.

In Solaris 10, only ja can be used.

Default value

C

Recommended value

Default value

When the setting takes effect

For JP1/AJS3 Console Manager:

After the JP1/AJS3 Console Manager service is restarted

For JP1/AJS3 Console Agent:

After the JP1/AJS3 Console Agent service is restarted

(8) "HNTRLOGLEVEL" = "{none|error|warn|info}"

Use this parameter to specify the level of messages that are output to the integrated trace log.

Specify this parameter if you want to output detailed log information to the integrated trace log.

Specifiable values

none

No messages are output.

error

Error messages are output.

warn

Warning messages are output.

info

Information messages are output.

Default value

error

Recommended value

Default value

When the setting takes effect

For JP1/AJS3 Console Manager:

After the JP1/AJS3 Console Manager service is restarted

For JP1/AJS3 Console Agent:

After the JP1/AJS3 Console Agent service is restarted

(9) "DATADIRECTORY" = "data-directory-path"

Use this parameter to specify the name of the directory used to store the definition information of the root scope. Specify a full path name.

Specify this parameter if you want to change location where the definition data is saved to a location other than the default directory.

To change the location, specify an existing directory. If you want to specify a new data directory, create the directory first and then specify the name. Specifying a directory that does not exist results in an error when you log in to JP1/AJS3 Console View.

Do not delete the files in the directory specified in this parameter.

Specifiable values

A character string of no more than 191 bytes

Default value

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

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\database

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

JP1/AJS3-Console-installation-folder\database

For Windows Server 2003:

JP1/AJS3-Console-installation-folder\database

In UNIX:

/var/opt/jp1ajs2cm/database

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Console Manager service is restarted

(10) "RECONNECTINTERVAL" = dword:interval-for-reconnecting-to-JP1/AJS3-Console-Agent

Use this parameter to specify the interval at which connection to JP1/AJS3 Console Agent is retried when connection to the agent fails.

Specify this parameter if you want to change the interval until the next connection when you cannot connect to the JP1/AJS3 Console Agent to be monitored.

Specifiable values

A hexadecimal value (in seconds) from 1E to E10 (30 to 3,600 in decimal)

Default value

dword:0000012C (300 in decimal)

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Console Manager service is restarted

(11) "TRACELOGFILE" = "trace-log-file-name"

Use this parameter to specify the trace log file name. Specify a full path name.

Specify the name of a trace log file on the local disk so that trace information will be recorded reliably.

Because the system creates a new file whenever trace information is output, do not specify the name of an existing file.

Specifiable values

A character string of no more than 255 bytes

Default value

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

For JP1/AJS3 Console Manager:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2CM\log\tracelog.cm

For JP1/AJS3 Console Agent:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\tracelog.ca

The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86) (for 64-bit Windows)

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

For JP1/AJS3 Console Manager:

JP1/AJS3-Console-installation-folder\log\tracelog.cm

For JP1/AJS3 Console Agent:

JP1/AJS3-Manager-installation-folder\log\tracelog.ca

In Windows Server 2003:

For JP1/AJS3 Console Manager:

JP1/AJS3-Console-installation-folder\log\tracelog.cm

For JP1/AJS3 Console Agent:

JP1/AJS3-Manager-installation-folder\log\tracelog.ca

In UNIX:

For JP1/AJS3 Console Manager:

/var/opt/jp1ajs2cm/log/tracelog.cm

For JP1/AJS3 Console Agent:

/var/opt/jp1ajs2/log/tracelog.ca

Recommended value

Default value

When the setting takes effect

For JP1/AJS3 Console Manager

After the JP1/AJS3 Console Manager service is restarted

For JP1/AJS3 Console Agent

After the JP1/AJS3 Console Agent service is restarted

(12) "IPC_CONNECTTIMEOUT" = dword:remote-connection-timeout-value

Use this parameter to specify the connection timeout period for remote communication with JP1/AJS3 Console Agent.

If the timeout period for TCP/IP connection set in the OS is shorter than the value specified in this parameter, the OS setting is used.

Specifiable values

A hexadecimal value (in seconds) from 0 to 258 (0 to 600 in decimal)

Default value

dword:00000014 (20 in decimal)

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Console Manager service is restarted

(13) "ENABLEOPERATION" = "{yes|no}"

Use this parameter to specify whether to enable operation form of JP1/AJS3 Console View.

Specifiable values

yes

Operation from JP1/AJS3 Console View is enabled.

no

Operation from JP1/AJS3 Console View is disabled.

Specify this value if you do not want operations to be performed from JP1/AJS3 Console View for a jobnet on the target host.

Default value

yes

Recommended value

Default value

When the setting takes effect

After the JP1/AJS3 Console Agent service is restarted

2.9 Setting up JP1/AJS3 shared information

This section describes the environment setting parameters for JP1/AJS3 shared information.

2.9.1 List of the environment setting parameters for JP1/AJS3 shared information

The same settings for JP1/AJS3 shared information can be used for the manager environment (JP1/AJS3 - Manager) and for the agent environment (JP1/AJS3 - Agent).

The table below lists the environment setting parameters to be used to set JP1/AJS3 shared information in the manager environment (JP1/AJS3 - Manager) and in the agent environment (JP1/AJS3 - Agent).

To determine whether an environment setting parameter is to be set in Windows or UNIX, see the Applicable OS column.

Table 2‒11: Environment setting parameters (JP1/AJS3 shared information)

No.

Definition key

Environment setting parameter

Definition

Applicable OS

Applicable product

1

[{JP1_DEFAULT|logical-host-name}\JP1AJS2COMMON]#

"LARGEFILEUSE"=

Operation for large files

Windows

UNIX

M, A

2

"SYSLOGJOBMSG"=

Setting for whether the error messages for jobs are also to be output to syslog

UNIX

M, A

3

"MACROCHANGEFAIL"=

Operation if an attempt to expand a macro variable specified in an event job fails when the job is registered for execution registration

Windows

UNIX

M, A

4

"ADMACLIMIT"=

Setting of the operation permission for units for JP1 users mapped to the OS users with administrator permissions or superuser permissions

Windows

UNIX

M

5

"CONNECTIONRESTRICTION"=

Setting for whether the connection source restriction function is to be enabled or disabled.

Windows

UNIX

M, A

6

[JP1_DEFAULT\JP1AJS2]

"LOGIPV6INFOALL"=

Setting for whether IPv6 addresses are to be added to messages output to logs.

Windows

UNIX

M, A

Legend:

M: JP1/AJS3 - Manager

A: JP1/AJS3 - Agent

#

Specify JP1_DEFAULT for the physical host. For logical-host-name, specify the name of a logical host.

The following describes each of the environment setting parameters.

Parameters that are not described here are used for maintenance purposes. Do not change their values.

The default value is used whenever a value is not specified for an environment setting parameter.

2.9.2 Details of the environment setting parameters for JP1/AJS3 shared information

(1) "LARGEFILEUSE" = "{yes|no}"

Use this parameter to specify whether the file monitoring job monitors large files and the judgment job determines if there are any large files.

For details, see 6.3.17 Enabling monitoring of a large file in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.3.12 Enabling monitoring of a large file in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

yes

The file monitoring job monitors files larger than 2 GB and the judgment job determines if there are any files larger than 2 GB.

no

The file monitoring job cannot monitor files that are larger than 2 GB. If you specify no, but specify a file larger than 2 GB as a monitoring target, an error message is output to the integrated trace log when execution of the file monitoring job terminates abnormally. For this reason, do not specify a file larger than 2 GB as a monitoring target.

The judgment job cannot determine if there are any files larger than 2 GB. If you specify a file larger than 2 GB in a judgment condition when you have specified no, the judgment job determines that there are no large files.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After JP1/AJS3 is restarted

(2) "SYSLOGJOBMSG" = "{none|error}"

Use this parameter to specify whether to also output error messages appearing during the execution of jobs to syslog.

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

Specifiable values

none

Error messages appearing during the execution of jobs are not output to syslog. The status of JP1/AJS3 is monitored by the integrated trace log.

error

Error messages appearing during the execution of jobs are output to the syslog file, which is used to monitor the error status of JP1/AJS3. However. even if you specify this value, you must not stop the integrated trace log process.

If you specify error for this parameter, a message reporting abnormal job termination (KAVS0265-E) is output to syslog, regardless of whether the scheduler service setting contains JOBSYSLOG (outputs, to syslog, messages related to starting and ending a job).

The following table lists the messages that are output based on the values specified for the SYSLOGJOBMSG and JOBSYSLOG environment setting parameters.

Table 2‒12: Messages to be output based on the values specified for SYSLOGJOBMSG and JOBSYSLOG

Value specified for SYSLOGJOBMSG

Value specified for JOBSYSLOG

none

abend

warning

hold

enddelay

all

none

--

KAVS0265-E

KAVS0269-W

KAVS0271-I

KAVS0248-I

KAVS0263-I

KAVS0264-I

KAVS0265-E

KAVS0266-I

KAVS0269-W

KAVS0271-I

error

KAVS0265-E

KAVS0265-E

KAVS0265-E

KAVS0269-W

KAVS0265-E

KAVS0271-I

KAVS0265-E

KAVS0248-I

KAVS0263-I

KAVS0264-I

KAVS0265-E

KAVS0266-I

KAVS0269-W

KAVS0271-I

Legend:

--: Not applicable

Default value

none

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(3) "MACROCHANGEFAIL" = "{yes|no}"

Use this parameter to specify whether to set Failed to start as the status if expansion of the passing information in a macro variable fails when a job is executed.

For details, see 6.2.10 Setting the action to be taken if the value of a macro variable cannot be passed in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.10 Setting the action to be taken if the value of a macro variable cannot be passed in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

yes

If the expansion of the passing information in a macro variable fails when a job is executed, the status set is Failed to start, and an error message is output to the integrated trace log and as execution result details so that you can check the macro variable that could not be expanded.

no

Even if the expansion of the passing information in a macro variable fails when a job is executed, the system treats the information defined in the macro variable as a character string and continues processing.

Default value

no

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(4) "ADMACLIMIT" = "{yes|no}"

Use this parameter to set the operation permission for units for JP1 users mapped to OS users with administrator permissions or superuser permissions.

Specifiable values

yes

Access is controlled according to the permission level set for a JP1 user irrespective of the OS user to whom the JP1 user is mapped.

no

A JP1 user mapped to an OS user with administrator permissions or superuser permissions can perform all operations irrespective of the permission level.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After JP1/AJS3 is restarted

(5) "CONNECTIONRESTRICTION" = "{none|manager|agent|all}"

Use this parameter to specify whether the connection source restriction function for restricting connection to JP1/AJS3 is to be enabled or disabled.

If the database configuration of JP1/AJS3 is a compatible ISAM configuration, the setting of this environment setting parameter is ignored.

Specifiable values

none

The setting in the manager connection permission configuration file and the setting in the agent connection permission configuration file are disabled.

manager

The setting in the manager connection permission configuration file is enabled, and the setting in the agent connection permission configuration file is disabled.

This value cannot be specified in JP1/AJS3 - Agent.

agent

In JP1/AJS3 - Manager, the setting in the agent connection permission configuration file is enabled, and the setting in the manager connection permission configuration file is disabled.

In JP1/AJS3 - Agent, the setting in the agent connection permission configuration file is enabled.

all

In JP1/AJS3 - Manager, the setting in the manager connection permission configuration file and the setting in the agent connection permission configuration file are enabled.

In JP1/AJS3 - Agent, the setting in the agent connection permission configuration file is enabled.

Default value

none

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

If both the JP1/AJS3 service and the JP1/AJS3 Queueless Agent service have stopped, when either service restarts

Cautionary notes

Change this environment setting parameter if both the JP1/AJS3 service and the JP1/AJS3 Queueless Agent service have stopped, and then, after making the change, start the services.

If you changed this environment setting parameter while either the JP1/AJS3 service or the JP1/AJS3 Queueless Agent service was running, stop both services and then start them.

If you specify a value other than none for this environment setting parameter, and the environment settings file storage folder does not contain the connection permission configuration file corresponding to the specified value, or the connection permission configuration file cannot be read, the JP1/AJS3 service or the JP1/AJS3 Queueless Agent service terminates abnormally.

(6) "LOGIPV6INFOALL" = "{yes|no}"

Use this parameter to specify whether to add IPv6 addresses to the messages output to logs such as the integrated trace log, event log, and syslog and to messages detailing execution results.

The IPv6 addresses are added to the messages shown below. For details about messages, see the manual Job Management Partner 1/Automatic Job Management System 3 Messages 1.

KAVT0009-E, KAVT0145-E, KAVT0268-W, KAVT0293-W, KAVT0559-E, KAVT0606-W, KAVT0612-W, KAVT0613-W, KAVT8343-W

Specifiable values

yes

IPv6 addresses are added to the messages.

no

IPv6 addresses are not added to the messages.

Default value

no

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

3 Operation Profiles

This chapter provides an overview of operation profiles, and then describes them in detail.

3.1 Overview of operation profiles

This section provides an overview of operation profiles.

3.1.1 Location of operation profiles

Operation profiles are stored in the environment settings file storage folder, which is one of the following folders:

Windows

For a physical host:

JP1/AJS3-Manager-installation-folder\conf

For a logical host:

shared-folder\jp1ajs2\conf

UNIX

For a physical host:

/etc/opt/jp1ajs2/conf

For a logical host:

shared-directory/jp1ajs2/conf

3.1.2 List of operation profiles

The following table lists the operation profiles.

Table 3‒1: List of operation profiles

No.

Type

Related functions

File name

See:

1

Execution agent profile

Execution agent restriction

ajsprof_scheduler-service-name_agent.conf

3.2.1

2

Unit-attribute profile

Execution-user fixing function

Upper-level unit-attribute inheritance function

ajsprof_scheduler-service-name_unit.conf

3.2.2

3.1.3 Cautionary notes on operation profiles

The following are cautionary notes on operation profiles.

You must set the view permission for the following user or account in advance to prevent unintended users from editing or deleting the operation profiles.

In Windows:

An account that starts the JP1/AJS3 service

The default is SYSTEM.

In UNIX:

Root user

Use the character set that is used in JP1/AJS3.

The maximum size of an operation profile is 10 megabytes.

If the same unit path is specified multiple times, the path that is specified first takes effect.

The following lines are ignored:

0-byte line

A line that contains only spaces or tab characters

A line beginning with a hash mark (#) (the line is treated as a comment line)

If the second character of a line that begins with a space or tab character is #, the line is treated as a comment line.

The maximum length of a line in an operation profile is as follows:

A line containing a linefeed character (LF: 0x0a or CR: 0x0d)

2,047 bytes, not including linefeed characters

A line without a linefeed character (LF: 0x0a or CR: 0x0d)

2,048 bytes

An operation profile that contains a line longer than the maximum has no effect (syntax error).

If there is a space or tab character at the beginning or end of the line, the value without the space or tab character is used.

When you use the jajs_setup command to rename a scheduler service for which an operation profile is enabled, you also need to change the scheduler service name in the operation profile name.

If you start the renamed scheduler service without making the change, the operation profile does not take effect because the applicable operation profile no longer exists.

When you use the jajs_setup command to delete a scheduler service for which an operation profile is enabled, you also need to move or delete the operation profile that corresponds to the scheduler service from the environment settings file storage folder.

If you do not make either change and you add a new scheduler service that has the same name as the deleted scheduler service, the remaining operation profile takes effect with the result that unintended operations might occur.

When you execute the jajs_setup_cluster command, operation profiles on physical hosts are copied to the logical host. Delete the copied operation profiles as required.

3.2 Operation profile details

This section describes each operation profile in detail.

3.2.1 Execution agent profile

Specify the settings related to execution agent restriction in an execution agent profile. Next, create a file for each scheduler service, and then set the execution agents that will be permitted to execute the jobs of each unit.

For details about execution agent restriction, see 2.5.1(6) Execution agent restriction in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

For details about how to create an execution agent profile, see 4.3.1 Procedure for setting up an execution agent profile in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (in Windows) or 14.3.1 Procedure for setting up an execution agent profile in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (in UNIX).

(1) Format

Create an execution agent profile for each scheduler service.

The following shows the format of an execution agent profile.

@SYS_RESTRICT_START
unit_path=full-name-of-the-unit
View=restriction-check-when-a-unit-is-defined
ViewCheckLevel=operation-when-a-unit-is-defined
JobExec=restriction-check-at-job-execution
@SYS_AGENTLIST_START
entity-for-which-definition-or-execution-permitted
 :
 :
@SYS_AGENTLIST_END
@SYS_RESTRICT_END

(2) Setting items

The following describes the items that need to be set. Use a linefeed character to separate items.

(a) @SYS_RESTRICT_START

The setting on this line is the fixed value @SYS_RESTRICT_START, which indicates the start of the execution agent restriction settings.

The information enclosed by this line and the corresponding @SYS_RESTRICT_END constitutes the settings for one unit. To specify information for multiple units, repeatedly specify the information for each enclosed by a @SYS_RESTRICT_START and a @SYS_RESTRICT_END. You can specify information for a maximum of 128 units.

This item must be set.

Cautionary note

If a large amount of information is set in the execution agent profile, the memory used by the execution agent profile might be insufficient. Use the AGENTPROFMEMSIZE environment setting parameter to set the amount of memory that can be used for the execution agent profile. Use the formula below to estimate the required amount of memory, then round the result to the next whole number and set the resulting value in hexadecimal. Note, however, that if the resulting value is smaller than 512, set dword:00000200 (512 in decimal).

Amount of memory in kilobytes required for the execution agent profile = (a + 256) / 1,024

a

Result of the following calculation performed for each unit (the information enclosed by a @SYS_RESRTICT_START and a @SYS_RESTRICT_END):

b + 1,280

b

Result of the following calculation performed for the execution entities (the information between @SYS_AGENTLIST_START and @SYS_AGENTLIST_END):

length-of-target-name-permitted-for-definition-or-execution + 128

For example, the execution agent profile might contain the following settings:

@SYS_RESTRICT_START
unit_path=/net1
View=on
ViewCheckLevel=warning
JobExec=on
@SYS_AGENTLIST_START
@SYSTEM
AGT01
@SYS_AGENTLIST_END
@SYS_RESTRICT_END

@SYS_RESTRICT_START
unit_path=/net2
View=on
ViewCheckLevel=warning
JobExec=on
@SYS_AGENTLIST_START
AGT02
AGT03
@SYS_AGENTLIST_END
@SYS_RESTRICT_END

For unit /net1, @SYSTEM and AGT01 are specified as execution targets. Therefore, the value of b is as follows:

(7 + 128) + (5 + 128) = 268

For unit /net2, AGT02 and AGT03 are specified as execution targets. Therefore, the value of b is as follows:

(5 + 128) + (5 + 128) = 266

The value of a is as follows:

(268 + 1,280) + (266 + 1,280) = 3,094

The amount of memory in kilobytes required for the execution agent profile is as follows:

(3,094 + 256) / 1,024 = Approx. 3.27

Because the value obtained from the above calculation is smaller than 512, set the AGENTPROFMEMSIZE environment setting parameter to 512.

For details about the AGENTPROFMEMSIZE environment setting parameter, see 2.2.2(98) AGENTPROFMEMSIZE.

(b) unit_path=full-name-of-the-unit

Use a character string of no more than 930 bytes to specify the full name of the unit. unit_path= is fixed. Specify this setting after @SYS_RESTRICT_START.

You can specify one of the following types of unit:

Any unit contained in a scheduler service (a forward slash (/) is set in the unit name)

Job group

Root jobnet

Nested jobnet

UNIX job

PC job

Event job

Action job

Custom job

This item must be set.

(c) View=restriction-check-when-a-unit-is-defined

Specify whether you want to display the selected execution agents and check the restrictions for the specified execution agents when a unit is defined in the JP1/AJS3 - View Define Details dialog box. You can set either of the following values:

on

The selected execution agents are displayed and the restrictions are checked.

off

The selected execution agents are not displayed and the restrictions are not checked.

View= is fixed. Set this information on a line between unit_path= full-name-of-the-unit and @SYS_AGENTLIST_START.

This item is optional. If it is not specified, on is assumed.

(d) ViewCheckLevel=operation-when-a-unit-is-defined

Specify the operation to be performed if an execution entity that is not permitted is encountered during restriction checking when a unit is defined in the JP1/AJS3 - View Define Details dialog box. You can set either of the following values.

error

The dialog box cannot be closed by clicking the OK button if an execution entity that is not permitted is specified.

warning

If an execution target that is not permitted is specified, the KAVV1501-Q message is output. Depending on the response to the message, the unit definition is registered in JP1/AJS3 - Manager even when an execution entity that is not permitted is specified.

ViewCheckLevel= is fixed. Set this information on a line between unit_path=full-name-of-the-unit and @SYS_AGENTLIST_START. This setting is valid only when on is set for View=restriction-check-when-a-unit-is-defined.

This item is optional. If it is not specified, error is assumed.

(e) JobExec=restriction-check-at-job-execution

Set either of the following values to specify whether restriction checking is to be performed for execution agents when a job is executed.

on

Restrictions are checked.

off

Restrictions are not checked.

JobExec= is fixed. Set this information on a line between unit_path=full-name-of-the-unit and @SYS_AGENTLIST_START.

This item is optional. If it is not specified, on is assumed.

(f) @SYS_AGENTLIST_START

The setting on this line is the fixed value @SYS_AGENTLIST_START, which indicates the start of the specification of entities for which definition or execution is permitted. The information between this line and the corresponding @SYS_AGENTLIST_END holds the settings of the execution entities that are permitted to perform definition or execution.

This item must be set.

(g) entity-for-which-definition-or-execution-permitted

On one line, specify the execution agent, execution agent group, or execution host for which definition or execution is to be permitted. Use a character string of no more than 255 bytes for an execution entity. A maximum of 2,048 execution entities can be set on the lines enclosed by @SYS_AGENTLIST_START and @SYS_AGENTLIST_END.

Note that the specified values are not case sensitive.

If you specify more than 255 bytes for an execution entity or specify more than 2,048 execution entities between @SYS_AGENTLIST_START and @SYS_AGENTLIST_END, a syntax error occurs in the execution agent profile and the settings are not applied.

To specify an execution entity that begins with a hash mark (#) or a backslash (\), do the following:

If the execution entity begins with a hash mark (#):

Use a backslash (\) as an escape character. The escape character is not required if the hash mark (#) is the second or a subsequent character.

If the execution entity begins with a backslash (\):

Use a backslash (\) as an escape character. The escape character is not required if the backslash is the second or a subsequent character.

If the specified execution entity begins with a backslash (\) and the second character is neither a hash mark (#) nor a backslash (\), a syntax error occurs in the execution agent profile.

The following table contains concrete examples.

Table 3‒2: How to specify permitted execution entities

No.

Permitted execution entity

Specification in the execution agent profile

Remarks

1

AGT1

AGT1

--

2

#AGT1

\#AGT1

--

#AGT1

The line is treated as a comment line.

3

\AGT1

\\AGT1

--

\AGT1

A syntax error for the execution agent profile occurs.

4

##AGT1

\##AGT1

Only the first character requires an escape character. The second and subsequent characters do not need one.

5

\\AGT1

\\\AGT1

6

\#AGT1

\\#AGT1

7

#\AGT1

\#\AGT1

8

AGT#1

AGT#1

The second and subsequent characters do not require as escape character.

9

AGT\1

AGT\1

Legend:

--: None

When permitting execution on the local host

@SYSTEM must be specified. Note, however, that if you want to permit an execution agent that has the same name as the local host name, specify the execution agent name.

If you want to permit execution of queueless jobs on the local host, specify the local host name. Hereafter, local host name refers to names that can be checked by using the following methods.

Physical host:

The host name determined by executing the hostname command

Logical host (Windows):

On the host on which JP1/AJS3 is running, in Control Panel, either choose Services, or choose Administrative Tools and then Services. In the Services dialog box that opens, the host name is displayed as xxxxx in JP1/AJS3_xxxxx

Logical host (UNIX):

Execute the ps command. The host name is displayed after the jajs_spmd process.

When specifying an execution agent group as the execution agent for units:

To specify an execution agent group as the execution agent for units, set the name of the execution agent group.

When specifying a macro variable name as the execution agent for units

To specify a macro variable name as the execution agent for units, set an execution agent name or a macro variable name according to the settings of View=restriction-check-when-a-unit-is-defined and JobExec=restriction-check-at-job-execution. The following table describes the information that needs to be set for this item.

Table 3‒3: Settings when a macro variable is specified

No.

View=restriction-check-when-a-unit-is-defined setting

JobExec=restriction-check-at-job-execution setting

Setting required for entity-for-which-definition-or-execution-permitted

1

off

on

Execution agent name

2

on

off

Macro variable name

3

on

on

Macro variable name

Execution agent name

For queueless jobs

To use the execution agent restriction functionality for a queueless job, set the name of the host on which the queueless job will be executed.

If the target host with a class name is specified in Exec-agent in the Define Details dialog box, you do not need to set the !class-name portion in the execution agent profile.

If a logical host that has not been attached is specified as the execution host for the queueless job, the queueless job is executed on the physical host corresponding to the logical host when the following conditions exist:

The logical host specified for the queueless job has been set in the execution agent profile.

exec is set in the AJSQL_NOATTACHREQ environment setting parameter.

Whether the physical host is set in the execution agent profile does not matter. Even if the physical host is not defined in the execution agent profile, the queueless job can be executed on the physical host.

(h) @SYS_AGENTLIST_END

The setting on this line is the fixed value @SYS_AGENTLIST_END, which indicates the end of the specification of the execution entities permitted for definition or execution.

This item must be set.

(i) @SYS_RESTRICT_END

The setting on this line is the fixed value @SYS_RESTRICT_END, which indicates the end of the execution agent restriction settings.

This item must be set.

(3) Examples

The following are examples of specifying execution agent profiles.

(a) When setting an execution agent profile for all units in the scheduler service

Suppose that an execution agent will be permitted for all units in the scheduler service as described in the following table.

Table 3‒4: Example 1

Target unit

Restriction check when a unit is defined

Restriction check at job execution

Permitted execution entity

All units in the scheduler service

Restriction checked

Restriction not checked

@SYSTEM and AGT01

Specify the execution agent profile as follows.

@SYS_RESTRICT_START
unit_path=/
View=on
JobExec=off
@SYS_AGENTLIST_START
@SYSTEM
AGT01
@SYS_AGENTLIST_END
@SYS_RESTRICT_END

(b) When setting an execution agent profile for multiple unit paths

Suppose that an execution agent will be permitted for multiple unit paths as described in the following table.

Table 3‒5: Example 2

Target unit

Restriction check when a unit is defined

Restriction check at job execution

Permitted execution entity

All units in job group /Grp1

Restriction checked

Restriction not checked

AGT01 and AGT02

Jobnet /net1 and subordinate units

Restriction checked

Restriction checked

AGT03

Specify the execution agent profile as follows.

@SYS_RESTRICT_START
unit_path=/Grp1
View=on
JobExec=off
@SYS_AGENTLIST_START
AGT01
AGT02
@SYS_AGENTLIST_END
@SYS_RESTRICT_END

@SYS_RESTRICT_START
unit_path=/net1
View=on
ViewCheckLevel=warning
JobExec=on
@SYS_AGENTLIST_START
AGT03
@SYS_AGENTLIST_END
@SYS_RESTRICT_END

3.2.2 Unit-attribute profile

In a unit-attribute profile, set the upper-level unit-attribute inheritance function and execution-user fixing function. Create a file for each scheduler service, and set the functions for each unit.

For details about the upper-level unit-attribute inheritance function, see 6.4.1(4) Access permission for creating or copying a unit, or making a release entry in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide. For details about the execution-user fixing function, see 6.4.1(5) Job execution user in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

For details about how to create a unit-attribute profile, see 4.3.2 Procedure for setting up a unit-attribute profile in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (in Windows) or 14.3.2 Procedure for setting up a unit-attribute profile in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (in UNIX).

(1) Format

Create a unit-attribute profile for each scheduler service.

The following shows the format of a unit-attribute profile.

@SYS_PROFILE_START
unit_path=full-name-of-the-unit
InheritUnitAttr=upper-level-unit-attribute-inheritance-function-setting-method
FixedExecUser=execution-user-fixing-function-setting-method
@SYS_PROFILE_END

(2) Setting items

The following describes the items that need to be set. Use a linefeed character to separate items.

(a) @SYS_PROFILE_START

The setting on this line is the fixed value @SYS_PROFILE_START, which indicates the start of the unit-attribute profile settings.

The information enclosed by this line and the corresponding @SYS_PROFILE_END constitutes the settings for one unit. To specify information for multiple units, repeatedly specify the information for each enclosed by a @SYS_PROFILE_START and a @SYS_PROFILE_END. You can specify information for a maximum of 128 units.

This item must be set.

Cautionary note

If many units are set in the unit-attribute profile, the memory used by the unit-attribute profile might be insufficient. Use the UNITPROFMEMSIZE environment setting parameter to set the amount of memory that can be used by the unit-attribute profile. Use the following formula to estimate the required memory size.

Size of memory in kilobytes required for the unit-attribute profile = total-number-of-units-set-in-the-unit-attribute-profile x 2

For details about the UNITPROFMEMSIZE environment setting parameter, see 2.2.2(99) UNITPROFMEMSIZE.

(b) unit_path=full-name-of-the-unit

Use a character string of no more than 930 bytes to specify the full name of the unit for which you want to set the upper-level unit-attribute inheritance function and execution-user fixing function. unit_path= is fixed.

You can set any type of unit.

Set a forward slash (/) to enable the unit-attribute profile for all units in the specified scheduler service.

This item must be set.

Even if only this item is specified as shown below, a syntax error will not occur and the setting has the effect that the upper-level unit-attribute inheritance function and the execution-user fixing function are not used. Use the following specification when you want to temporarily suppress the functions.

@SYS_PROFILE_START
unit_path=/
@SYS_PROFILE_END

Because a line beginning with a hash mark (#) is treated as a comment line, the following specification also has the effect that the upper-level unit-attribute inheritance function and the execution-user fixing function are not used.

@SYS_PROFILE_START
unit_path=/
#InheritUnitAttr=all
#FixedExecUser=all
@SYS_PROFILE_END

(c) InheritUnitAttr=upper-level-unit-attribute-inheritance-function-setting-method

Set either of the following values as the method for setting the upper-level unit-attribute inheritance function.

entryuser

The units in the job group or jobnet specified for unit_path=full-name-of-the-unit inherit the owner and JP1 resource group from the upper-level unit. However, for a unit created by copying a job for which User who owns is set for Executed by, the setting of the copy-source unit is retained instead of the setting of the upper unit being inherited.

all

The units in the job group or jobnet specified for unit_path=full-name-of-the-unit inherit the owner and JP1 resource group from the upper-level unit. Even if a unit is created by copying a job for which User who owns is set for Executed by, the unit inherits the setting of the upper unit.

InheritUnitAttr= is fixed.

Specify this setting only if you want to use the upper-level unit-attribute inheritance function.

When you use the upper-level unit-attribute inheritance function, we recommend that you set the same value that is set for FixedExecUser=execution-user-fixing-function-setting-method.

(d) FixedExecUser=execution-user-fixing-function-setting-method

Set either of the following values as the method for setting the execution-user fixing function.

entryuser

The owner of the unit for which the execution-user fixing function has been set is fixed as the user that executes the jobs in the unit specified for unit_path=full-name-of-the-unit. However, for those jobs for which User who owns is set for Executed by, the owner of each job is the execution user.

all

The owner of the unit for which the execution-user fixing function has been set is fixed as the user that executes the jobs in the unit specified for unit_path=full-name-of-the-unit. This also holds true for jobs for which User who owns is set for Executed by.

FixedExecUser= is fixed.

Specify this setting only if you want to use the execution-user fixing function.

When you use the execution-user fixing function, we recommend that you set the same value that is set for InheritUnitAttr=upper-level-unit-attribute-inheritance-function-setting-method.

(e) @SYS_PROFILE_END

The setting on this line is the fixed value @SYS_PROFILE_END, which indicates the end of the unit-attribute profile settings.

This item must be set.

(3) Example

The following are examples of specifying unit-attribute profiles.

(a) When setting a unit-attribute profile for all units in a scheduler service

Suppose that you want to set a unit-attribute profile for all units in a scheduler service as described in the following table:

Table 3‒6: Example 1

Target unit

Upper-level unit-attribute inheritance function

Execution-user fixing function

All units in the scheduler service

Used (setting: all)

Used (setting: all)

Write the unit-attribute profile as follows.

@SYS_PROFILE_START
unit_path=/
InheritUnitAttr=all
FixedExecUser=all
@SYS_PROFILE_END

(b) When setting a unit-attribute profile for multiple unit paths

Suppose that you want to set a unit-attribute profile for multiple paths as described in the following table:

Table 3‒7: Example 2

Target unit

Upper-level unit-attribute inheritance function

Execution-user fixing function

Units in job group /Grp1

Used (setting: entryuser)

Used (setting: entryuser)

Units in jobnet /net1

Used (setting: all)

Not used

Write the unit-attribute profile as follows.

@SYS_PROFILE_START
unit_path=/Grp1
InheritUnitAttr=entryuser
FixedExecUser=entryuser
@SYS_PROFILE_END

@SYS_PROFILE_START
unit_path=/net1
InheritUnitAttr=all
@SYS_PROFILE_END

Appendixes

A. Access Permissions for Directories and Files Specified in Environment Setting Parameters Required for AJS Administrators to Perform Operations

An AJS administrator who operates JP1/AJS3 might require access permissions for the directories or files specified in the environment setting parameters. When the AJS administrator sets up an environment, appropriate access permissions must have already been set.

The following table lists the directories and files specified in the environment setting parameters, and the access permissions required for the AJS administrator.

Table A‒1: Access permissions required for the AJS administrator to operate JP1/AJS3

No.

Key

Parameter

Directory or file for which access permission is required

Permission required for the AJS administrator

1

[{JP1_DEFAULT|logical-host-name}\JP1AJS2\HOST]

AJSSYSDIR

System folder of a host

rwx

2

HOSTLOGFILE1

Scheduler log file 1 for a host

rwx

3

HOSTLOGFILE2

Scheduler log file 2 for a host

rwx

4

[{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name]

AJSLOGFILE1

Scheduler log file 1

rwx

5

AJSLOGFILE2

Scheduler log file 2

rwx

6

AJSSYSDIR

System folder of each scheduler service

rwx

7

[{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Process]

WorkPath

Work directory when a manager process is executed

rwx

8

[{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Database]

DatabasePath

Directory used to store the database

rwx

9

[{JP1_DEFAULT|logical-host-name}\JP1NBQAGENT\Process]

WorkPath

Work directory when an agent process is executed

rwx

10

[{JP1_DEFAULT|logical-host-name}\JP1AOMMANAGER]

WaitInfFileOutDir

Directory to which the wait information file (settings for the manager process) is output

rwx

11

[{JP1_DEFAULT|logical-host-name}\JP1AOMAGENT]

WaitInfFileOutDir

Directory to which the wait information file (settings for the agent process) is output

rwx

12

EvjobInfFile

Directory in which inherited event job information is saved

rwx

13

[JP1_DEFAULT\JP1AJS2\CHECK]

AJSCHK_CHECKFILE

File that contains the definition pre-check results

rwx

14

AJSCHK_LOGDIR

Definition check log directory

rwx

15

AJSCHK_TRACELOGFILE

Trace log file for the definition pre-check function

rwx

16

[JP1_DEFAULT\JP1QLAGENT]

AJSQL_TRACELOGFILE

Trace log file

rwx

17

AJSQL_EXECLOG_FTPPATH

Directory used to store the internal log of queueless job execution output by the queueless file transfer service

rwx

18

[{JP1_DEFAULT|logical-host-name}\JP1QLAGENT]

AJSQL_LOGFILE

Log folder

rwx

19

AJSQL_STATFILE

Status file

rwx

20

AJSQL_EXECLOG_AGTPATH

Directory used to store the internal log of queueless job execution output by the queueless agent service

rwx

21

AJSQL_AGTWORKPATH

Workpath used in a queueless job, and the directory for temporary files

rwx

22

[JP1_DEFAULT\JP1AJS2CONSOLEMANAGER]

DATADIRECTORY

Data directory for the root scope

rwx

B. Version Revisions

This appendix lists the changes in each version of the JP1/AJS series programs.

B.1 Revisions in 10-50

The following lists the revisions in 10-50 for each program.

(1) JP1/AJS3 - Manager

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

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

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

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

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

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

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

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

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

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

(2) JP1/AJS3 - Agent

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

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

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

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

(3) JP1/AJS3 - View

A setting for shifting the start day by a number of days (counting both open and closed days) was added to the Schedule by days from start settings in the Advanced tab of the Schedule Rule dialog box.

A setting for holding jobnet execution if the registration method is Immediate execution was added to the Register for Execution dialog box.

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

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

B.2 Revisions in 10-10

The following lists the revisions in 10-10 for each program.

(1) JP1/AJS3 - Manager

A function was added that uses IP addresses to restrict the hosts that are able to connect to a manager host.

A function was added for checking the execution schedule of unregistered units in the Monthly Schedule window of JP1/AJS3 - View.

A function was added for preventing scheduler services for which the JP1 user logged in to JP1/AJS3 - View has no access privileges from appearing in JP1/AJS3 - View.

A function was added for restricting the maximum number of allowed JP1/AJS3 - View concurrent sessions for a scheduler service.

A function was added for changing the passwords of JP1 users by using JP1/AJS3 - View.

The following OS is supported:

Linux 5.1 (x86) or later

Linux 5.1 (AMD/Intel 64) or later

Content related to Solaris 11 (SPARC) was added.

(2) JP1/AJS3 - Agent

A function was added that uses IP addresses to restrict the hosts that are able to connect to an agent host.

Content related to Solaris 11 (SPARC) was added.

(3) JP1/AJS3 - View

A function was added for checking the execution schedule of unregistered units in the Monthly Schedule window of JP1/AJS3 - View.

A function was added for preventing scheduler services for which the JP1 user logged in to JP1/AJS3 - View has no access privileges from appearing in JP1/AJS3 - View.

A function was added for restricting the maximum number of allowed JP1/AJS3 - View concurrent sessions for a scheduler service.

A function was added for changing the passwords of JP1 users by using JP1/AJS3 - View.

The way in which the Register Custom Job dialog box and the Set Properties of Custom Job dialog box are displayed was changed.

A change was made so that when Jobnet Definition is selected from Function Menu, jobnets for which execution has been registered are displayed in the list area of the JP1/AJS3 - View window (main window).

The function for hiding the icons of unused units in the Jobnet Editor window (a setting in the Set Default Values dialog box) was extended.

A function was added for preventing the history of previously-used login-user names and connection-destination host names from appearing on the Login screen.

B.3 Revisions in 10-00

The following lists the revisions in 10-00 for each program.

(1) JP1/AJS3 - Manager

IPv6 addresses are now supported for communication.

Mirroring by copying a disk is now supported to enable disaster recovery operations.

The AJS administrator, with JP1/AJS3 access permissions that are almost equivalent to superuser permissions, can now be designated when JP1/AJS3 is installed as a new installation.

Wait conditions can now be used as a means for controlling the execution order of units across jobnets.

The number of definition items for which macro variables can be specified has been increased, and the passing information setting job, which uses macro variables to pass information, has been added.

A function that assigns a created or copied unit the attributes inherited from the upper-level unit, and a function that can permanently assign (fix) an execution user to a job have been added.

A function that prevents jobs from being executed on unauthorized execution agents has been added.

A function that allows users to save information about temporary change operations and to re-execute temporary change operations has been added.

A function that automatically retries execution of a job when the executable file defined for the job terminates abnormally has been added.

The dependent job of a judgment job can now be re-executed when the judgment job terminates normally.

Mutually exclusive conditions and range conditions can now be specified as judgment conditions for judgment jobs.

The Monitoring Event Log Job now can monitor the types of log data and events that were added in Windows Server 2008.

An option that can be used when the Interval Control Job is defined as a start condition has been added to forcibly assume that the start condition is satisfied immediately after the monitoring of the start condition starts.

The email sending job now supports a function that sends emails without using Outlook.

SNMP traps can now be issued in Windows Server 2008.

Processes for managing the embedded database have been improved.

The startup type of the JP1/AJS3 Database service has been changed to Manual so that the JP1/AJS3 Database ClusterService service will not be created.

An option has been added that checks the permissions of JP1 users mapped to OS users that have administrator permissions based on the JP1 permission level.

A time period can now be specified when the ajsentry command is used to register a jobnet for fixed execution.

Options that can be specified when the jajs_setup or jajs_setup_cluster command is used to set up the embedded database have been added.

The ajsembdbidlist and ajsembdbstatus commands can now be used to display the status of the embedded database.

The embedded database settings file is now generated when an embedded database is set up. If this file is specified when the ajsembdbbuild command is used to build another embedded database, the other embedded database will be set up with the settings in the file.

Execution user name and Execution time have been added as extended attributes that can be output for JP1 events (specific information) so that JP1 events indicating job termination can be used as job operating information.

JP1/AJS3 - Manager can now link with JP1/DH - AJE, and DHAJEW has been added as a standard custom job.

The following OS is no longer supported:

Solaris 9(SPARC)

Linux 5 (x86)

Linux 5 (AMD/Intel 64)

Linux 5 (IPF)

The following OS is supported:

Windows Server 2012

Solaris 11(SPARC)

Linux 6 (x86)

Linux 6 (x64)

(2) JP1/AJS3 - Agent

IPv6 addresses are now supported for communication.

The AJS administrator, with JP1/AJS3 access permissions that are almost equivalent to superuser permissions, can now be designated when JP1/AJS3 is installed as a new installation.

An option that can be used when the Interval Control Job is defined as a start condition has been added to forcibly assume that the condition is satisfied when the monitoring of the start condition starts.

The email sending job now supports a function that sends emails without using Outlook.

SNMP traps can now be issued in Windows Server 2008.

The Monitoring Event Log Job now can monitor the types of log data and events that were added in Windows Server 2008.

The following OS is no longer supported:

Solaris 9(SPARC)

Linux 5 (x86)

Linux 5 (AMD/Intel 64)

Linux 5 (IPF)

The following OS is supported:

Windows Server 2012

Solaris 11(SPARC)

Linux 6 (x86)

Linux 6 (x64)

(3) JP1/AJS3 - View

The Wait Conditions Settings List window and the Wait Conditions Statuses window have been added as means for managing units with wait conditions and units whose end is being waited for.

A dialog box which lists temporary change operations that have already been performed and which allows users to re-execute (re-apply) specific temporary change operations has been added.

Retry information can now be displayed in the following windows:

Daily Schedule window

Monthly Schedule window

Jobnet Monitor window

Detailed Schedule dialog box

Monitor Details - [icon-name] dialog box

Whether retries are enabled is now displayed in the list area of the Jobnet Editor window.

The Jobnet Monitor window was provided with a function that grays out all relation lines and units other than the day's units (the units that were executed and are to be executed on the day).

Specify period, Reference calendar, Waiting-target, and Execution type have been added as search conditions that can be specified in the Search window.

In the Search window, Retry Settings and Retry execution can now be specified as search conditions. In addition, the search results displayed in the Search window now include items related to automatic retry.

The procedure for displaying the units found in the Search window in the Summary Monitor window has been simplified.

The Display Item Setup dialog box can now be used to set the items to be displayed in the list areas of the Jobnet Editor window and the Jobnet Monitor window.

A function that allows users to define all-at-one-time schedule rules that start execution at regular intervals, and a function that allows users to delete multiple schedule rules at one time have been added.

Definition items related to automatic retry have been added to the detailed definitions of Unix jobs, PC jobs, QUEUE jobs, and custom jobs.

Mutually exclusive conditions and range conditions can now be specified as judgment conditions for judgment jobs.

The types of log data and events that were added in Windows Server 2008 can now be specified as Log type and Event type in the detailed definition of the Monitoring Event Log Job.

The Expire right after starting option has been added in the detailed definition of the Interval Control Job. When the job has been defined as a start condition, this option can be used to forcibly assume that the condition is satisfied immediately after the monitoring of the start condition starts.

An option ensuring that the job groups and planning groups displayed in the list area are initially selected when the JP1/AJS3 - View window (Main window) opens has been added. In addition, an option ensuring that the nested jobnets and nested remote jobnets displayed in the map area are initially selected when the Jobnet Editor window or the Jobnet Monitor window opens has been added.

An option has been added that displays a nested jobnet as being selected at the location at which the jobnet existed before it was moved to the upper layer in the Jobnet Editor window or the Jobnet Monitor window.

When the Depends on upper-level jobnet check box is selected in the schedule settings of a nested jobnet, whether to display a confirmation message before defined schedule rules are deleted can now be selected by using an option.

The Start button, which allows users to launch arbitrary programs, has been added to the Monitor Details - [custom-job-name] dialog box.

Because of the user authentication function added in JP1/AJS3 - Definition Assistant 09-10, specifying the JP1 user name is now mandatory for starting JP1/AJS3 - Definition Assistant from JP1/AJS3 - View. With this specification change, User name has been added as an item that can be selected from the Replace drop-down list in the Tool Entry dialog box.

The following OS is supported:

Windows 8.1

Windows 8

Windows Server 2012

An option for preventing the opening of multiple Jobnet Editor windows and Jobnet Monitor windows has been added.

B.4 Revisions in 09-00

The following lists the revisions in 09-00 for each program.

(1) JP1/AJS3 - Manager

The standard database of JP1/AJS3 is now an embedded database.

Functions related to an embedded database have been changed as follows:

The sizes of the large-scale, medium-scale, and small-scale database models have been changed.

The database area auto-increment function and the system log auto-increment function have been added.

The system log is no longer used.

The functions of the commands used to control an embedded database have been enhanced.

The ISAM database is now used only for QUEUE jobs and submit jobs.

An agent management function has been added for specifying a logical execution agent name as the destination host for a job or jobnet. Previously, users could only specify execution hosts by their real names.

Jobs that are in the Now queuing status when the service is stopped are now returned to the Wait for prev. to end status when the service restarts (in hot-start mode), before being resubmitted.

A jobnet release function has been added for replacing the definition of a jobnet that is registered for execution with another definition.

The job execution control manager process (jpqman) and event/action control manager process (jpomanager) can now be started on a scheduler service basis.

A scheduler log file can now be output for an individual scheduler service or host.

The following functions have been enhanced:

The method by which the number of logs to keep is managed

The process by which monitored generations of jobnets with start conditions are established

The process by which execution generations when a start condition is established are held

A format specification has been added to the ajsshow command for outputting the standard output file name.

The Manager Environment Settings dialog box is no longer provided. Instead, you can use the jajs_config command to set up the manager environment.

The following environment setting parameters have been added:

FixedHostnameForAgent

NotificationConstantRetry

NotificationRetryInterval

NotificationRetryCount

ClientConnectTimeout

A function has been added to support end delay monitoring based on how long a job takes to execute.

The jobnet connector functionality has been enhanced to enable control of the execution order of root jobnets managed by different scheduler services.

The definition pre-check has been enhanced so that if an invalid execution order is found in the units of the jobnet being checked, the names of the units are output to the check results file.

The file permission check performed at execution of a Unix job has been enhanced to include checks of the access control list and secondary group settings as well as file permissions.

A function has been added that enables event jobs to continue executing even if the JP1/AJS3 service stops on the execution host.

A function has been added for exporting and importing the registration statuses of jobnets as registered execution-schedule information.

Linkage with message queues on UNIX hosts (TP1/LiNK, TP1/Message Queue, MQSeries) is no longer supported.

Windows Server 2008 has been added as platforms supported by JP1/AJS3 - Manager.

A unit called a jobnet connector which controls the execution order of root jobnets has been added.

An option has been added to output a detailed history of user operations, such as changes to jobnet definitions, to the scheduler log.

The ajslogprint command for extracting log entries from the scheduler log has been added.

(2) JP1/AJS3 - Agent

The Agent Environment Settings dialog box is no longer provided. Instead, you can use the jajs_config command to set up the agent environment.

Linkage with a message queue system is no longer supported.

The following environment setting parameters have been added:

FixedHostnameForAgent

NotificationConstantRetry

NotificationRetryInterval

NotificationRetryCount

ClientConnectTimeout

The file permission check performed at execution of a Unix job has been enhanced to include checks of the access control list and secondary group settings as well as file permissions.

Linkage with message queues on UNIX hosts (TP1/LiNK, TP1/Message Queue, MQSeries) is no longer supported.

Windows Server has been added as platforms supported by JP1/AJS3 - Agent.

(3) JP1/AJS3 - View

An agent management function has been added for specifying a logical execution agent name as the destination host for a job or jobnet. Previously, users could only specify execution hosts by their real names.

A jobnet release function has been added for replacing the definition of a jobnet that is registered for execution with another definition.

Function menus have been added to the JP1/AJS3 - View window to facilitate task-oriented operation.

The JP1/AJS3 - View window (Summary Monitor window) has been added. In this window, you can view the progress of jobnets and other information.

JP1/AJS3 - View can now be started in the following modes:

Normal mode

In this mode, the JP1/AJS3 - View window is equipped with function menus.

Monitoring mode

A mode dedicated to monitoring jobs and jobnets. Only the JP1/AJS3 - View window (Summary Monitor window) is displayed.

Compatible mode

JP1/AJS3 - View operates in the same way as JP1/AJS2 - View version 8 or earlier.

A Detailed Information area has been added to the JP1/AJS3 - View window (Main window), which displays detailed information about a unit.

The concurrent execution setting of monitored generations and the holding behavior of execution generations (produced when a start condition is satisfied) can now be selected in the detailed definition of a start condition.

A list filter function has been added for filtering the information in a list.

A function has been added for saving list information in CSV format.

You can now click a button in the Daily Schedule window and Monthly Schedule window to move between days and months.

A list area has been added to the Jobnet Editor window and Jobnet Monitor window. This area displays the jobs defined in the jobnet.

A Search window has been added, in which you can set detailed search conditions and perform operations on units listed in the search results.

You can now use a mouse wheel to scroll inside JP1/AJS3 - View.

A function has been added that allows you to select whether Type in list areas are grouped by type or displayed in detailed format.

A function has been added for prohibiting changes to specific definition items in the Define Details dialog box.

A function has been added for removing icons you no longer use from the icon list area in the Jobnet Editor window.

Windows 7 has been added as a supported OS (JP1/AJS3 - View 09-00-05 or later).

A function has been added to support end delay monitoring based on how long a job takes to execute.

The jobnet connector functionality has been enhanced to enable control of the execution order of root jobnets managed by different scheduler services.

An option has been added to the Filter Settings dialog box so that jobnets with hold plans can be treated as jobnets in Being held status for filtering purposes in the Daily Schedule window and Monthly Schedule window.

The ability to define, operate, and monitor jobnet connectors which control the execution order of root jobnets has been added.

A function that displays the preceding and succeeding jobs of a given job or jobnet in bold has been added.

Support for Windows Vista has been added.

B.5 Revisions in 08-00

The following lists the revisions in 08-00 for each program.

(1) JP1/AJS2 - Manager

The recommended values for the environment settings are now set during installation and setup.

A Monitoring Files job can now monitor files larger than 2 gigabytes (large files).

The ajsstatus command can now output the connection status of JP1/AJS2 - View.

The following commands used to control an embedded database have been added:

ajsembdbaddarea command (expands a database area in an embedded database)

ajsembdbaddlog command (expands a log area in an embedded database)

ajsembdbcancel command (cancels execution of a command manipulating an embedded database)

ajsembdboplog command (manipulates embedded database logs)

ajsembdbreclaim command (maintains an embedded database)

ajsembdbrorg command (unloads and reloads an embedded database)

ajsembdbrstr command (backs up and restores an embedded database)

ajsembdbstart command (starts an embedded database)

ajsembdbstatus command (monitors an embedded database)

ajsembdbstop command (stops an embedded database)

ajsembdbunset command (removes the setup of an embedded database)

With support of the ajsembdbreclaim command, the time required to reclaim free pages has been reduced.

JP1/Performance Management - Agent Option for JP1/AJS2 can now be linked with JP1/AJS2 to analyze the operating status.

The jajs_start command and the jajs_start.cluster command can now check whether a process has already been started when JP1/AJS2 is started. (UNIX only)

(2) JP1/AJS2 - Agent

The recommended values for the environment settings are now set during installation and setup.

A Monitoring Files job can now monitor files larger than 2 gigabytes (large files).

(3) JP1/AJS2 - View

Icons have been changed.

B.6 Revisions in 07-50

The following lists the revisions in 07-50 for each program.

(1) JP1/AJS2 - Manager

Macro variables can now be used during registration for execution to specify information to be passed.

Judgment jobs can now perform variable judgment.

A function has been added that suppresses jobnet executions that follow an abnormally terminated jobnet and that will be started when their start conditions are satisfied.

A definition pre-check function has been added for conducting a final check before starting production in the production environment after the unit definitions are migrated from the development environment.

The jpomanevreset command has been added for deleting data accumulated in the event action manager if a large amount of unprocessed data accumulated in the event action manager has caused delay. To identify the start conditions and agents that have caused this problem, the jpomanevshow command has also been added for displaying information about agents that frequently send data to the manager and the start conditions.

A function that alleviates consumption of the Desktop heap has been added. (Windows only)

A function has been added for specifying the maximum wait time for the scheduler service to connect to a database.

Messages that were output to only the integrated trace log can now be output to syslog also. (UNIX only)

The following functions have been added to the data collection tool:

Specifying a logical host name

Filtering the data to be collected

Adding types of data that can be collected

Descriptions of messages have been improved.

An urgent command has been added that can be executed if an error occurs.

A function has been added that places limits on, for example, the size of files that can be received, to prevent a part of job processing from affecting the entire system operation.

A function has been added that performs a synchronized write when updating event job information or the wait information file.

The monitoring interval for linkage with MQ Series can now be specified in seconds.

If a TCP/IP connection error occurs, the retry interval and count can now be changed.

The policy to determine the agent hosts to which a job will be dispatched can now be specified.

All the detailed processes of the event action function can now be stopped to terminate the agent process for the event action function if any of the detailed processes have terminated upon receiving a signal.

Microsoft(R) Visual C++ .NET Version 2003 is now supported as a compiler for the provided code functions.

The ajsshow command can now display the hold attribute of a jobnet or job even when the jobnet or job has already terminated.

(2) JP1/AJS2 - Agent

A definition pre-check function has been added for conducting a final check before starting production in the production environment after the unit definitions are migrated from the development environment.

The following functions have been added to the data collection tool:

Specifying a logical host name

Filtering the data to be collected

Adding types of data that can be collected

Descriptions of messages have been improved.

The monitoring interval for linkage with MQ Series can now be specified in seconds.

All the detailed processes of the event action function can now be stopped to terminate the agent process for the event action function if any of the detailed processes have terminated upon receiving a signal.

A function has been added that performs a synchronized write when updating event job information or the wait information file.

(3) JP1/AJS2 - View

Macro variables can now be used during registration for execution to specify information to be passed.

Judgment jobs can now perform variable judgment.

A function has been added that suppresses the jobnet executions that follow an abnormally terminated jobnet and that will be started when their start conditions are satisfied.

The Add, Change Time, Execute Immediately, and Release Change options have been added to the JP1/AJS2 - View window.

The Paste (Extension) menu command has been added for copying units and relationship lines at the same time.

Relationship lines can now be drawn from multiple units to a single job network element.

When opening the Jobnet Monitor window of JP1/AJS2 - View from JP1/AJS2 Console View, if there is already an activated JP1/AJS2 - View, the window can now be opened in JP1/AJS2 - View.

The following functions have been added to the data collection tool:

Specifying a logical host name

Filtering the data to be collected

Adding types of data that can be collected

Descriptions of messages have been improved.

The maximum log file size for JP1/AJS2 - View has been increased.

The maximum log file size for JP1/AJS2 Console View has been increased.

In JP1/AJS2 - View, log information that previously was output many times in small units can now be output at one time.

In JP1/AJS2 Console View, log information that previously was output many times in small units can now be output at one time.

In the Windows version of JP1/AJS2 - View, Help has been added to the Start menu.

B.7 Revisions in 07-00

The following lists the revisions in 07-00 for each program.

(1) About JP1/AJS2 - Manager

A function was provided to temporarily compress JP1/AJS2 and reconfigure the ISAM database (scheduler database and job execution environment database) without stopping active applications.

ISAM databases can now be reconfigured in parallel.

The number of scheduler services that can be added has been changed from 9 to 20.

An option was added for outputting the execution timings of reference commands, such as ajsshow and the history of service processing requests from operation commands, as the operation log to the scheduler log.

The number of logs to keep for a jobnet has been changed from 99 to 999.

For a cold start of JP1/AJS2, the job execution environment database is deleted so that the startup time of JP1/AJS2 becomes shorter.

A function is now supported for validating the user profile information in the environment setup for job execution control.

By setting the number of days that job information is held to 0 days, jobs that terminate abnormally can now be handled by changing the save time.

The JP1/AJS2 job information deletion can now be suppressed.

Any event job can now be used in a DNS environment (host name in the FQDN format).

Event job reception information can now be inherited as macro variables as the parameters of standard jobs and action jobs without having to pay attention to double quotation marks in the inherited information.

The extended regular expression supported by JP1/Base can now be used in Receive event job monitoring jobs, Monitoring log files jobs, and Monitoring event log jobs according to the JP1/Base settings.

A function to execute queueless jobs is now supported.

(2) About JP1/AJS2 - Agent

Event job reception information can now be inherited as macro variables of the parameters of standard jobs and action jobs without being aware of double quotation marks in the inherited information.

A function for executing queueless jobs was supported.

When JP1/AJS2 - Agent starts, it no longer accesses the authentication server (07-00-/C or later).

(3) About JP1/AJS2 - View

A user profile can now be used to set the JP1/AJS2 - View environment.

A line feed character can now be inserted at any point in a unit name displayed in the map area of the Jobnet Editor and Jobnet Monitor windows.

The default values in the dialog box can now be changed.

Display items (columns) in the following locations can now be selected.

List area in the JP1/AJS2 - View window

Execution result list in the Daily Schedule window

Execution result list in the Monthly Schedule window

C. Reference Material for This Manual

This appendix provides reference information, including various conventions, for this manual.

C.1 Related publications

This manual is part of a related set of manuals. The manuals in the set are listed below (with the manual numbers):

About JP1/AJS:

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Overview (3021-3-318(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide (3021-3-319(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide (3021-3-320(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (3021-3-321(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Administration Guide (3021-3-323(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Troubleshooting (3021-3-324(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Operator's Guide (3021-3-325(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Command Reference 1 (3021-3-326(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Command Reference 2 (3021-3-327(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Linkage Guide (3021-3-328(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Messages 1 (3021-3-329(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Messages 2 (3021-3-330(E))

Job Management Partner 1/Automatic Job Management System 2 Description (3020-3-K21(E))

Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide (3020-3-K22(E))

Job Management Partner 1/Automatic Job Management System 2 Setup Guide (3020-3-K23(E))

Job Management Partner 1/Automatic Job Management System 2 Operator's Guide (3020-3-K24(E))

Job Management Partner 1/Automatic Job Management System 2 Command Reference (3020-3-K25(E))

Job Management Partner 1/Automatic Job Management System 2 Linkage Guide (3020-3-K27(E))

Job Management Partner 1/Automatic Job Management System 2 Messages (3020-3-K28(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 - Print Option Description, User's Guide (3021-3-331(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 - Definition Assistant Description, Operator's Guide and Reference (3021-3-332(E))

Job Management Partner 1/Automatic Job Management System 3 - Web Operation Assistant Description, Operator's Guide and Reference (3020-3-S18(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 for Enterprise Applications Description, User's Guide and Reference (3021-3-333(E))

About JP1:

Job Management Partner 1 Version 10 Job Management Partner 1/Base User's Guide (3021-3-301(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Base Messages (3021-3-302(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Base Function Reference (3021-3-303(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Integrated Management - Manager Quick Reference (3021-3-304(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Integrated Management - Manager Overview and System Design Guide (3021-3-305(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Integrated Management - Manager Configuration Guide (3021-3-306(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Integrated Management - Manager Administration Guide (3021-3-307(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Integrated Management - Manager GUI Reference (3021-3-308(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference (3021-3-309(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Integrated Management - Manager Messages (3021-3-310(E))

Job Management Partner 1 Version 10 Job Management Partner 1/Script Description and Reference (3021-3-135(E)), for Windows Systems

Job Management Partner 1 Version 10 Job Management Partner 1/File Transmission Server/FTP Description, Reference, and Operator's Guide (3021-3-334(E)), for Windows systems

Job Management Partner 1 Version 10 Job Management Partner 1/File Transmission Server/FTP Description, Reference, and Operator's Guide (3021-3-335(E)), for UNIX systems

Job Management Partner 1 Version 10 Job Management Partner 1/Data Highway - Automatic Job Executor Operation manual (3021-3-336(E))

Job Management Partner 1/Software Distribution Description and Planning Guide (3020-3-S79(E)), for Windows systems

Job Management Partner 1/Software Distribution Setup Guide (3020-3-S80(E)), for Windows systems

Job Management Partner 1/Software Distribution System Administrator's Guide Volume 1 (3020-3-S81(E)), for Windows systems

Job Management Partner 1/Software Distribution System Administrator's Guide Volume 2 (3020-3-S82(E)), for Windows systems

Job Management Partner 1/Software Distribution Automatic Installation Tool Description and Reference (3020-3-S83(E)), for Windows systems

Job Management Partner 1/Software Distribution Administrator Kit Description and Operator's Guide (3020-3-S84(E))

Job Management Partner 1/Software Distribution Client Description and User's Guide (3020-3-S85(E)), for UNIX systems

Job Management Partner 1/Software Distribution SubManager Description and Administrator's Guide (3020-3-L42(E)), for UNIX systems

Job Management Partner 1/Software Distribution Manager Description and Administrator's Guide (3000-3-841(E))

Job Management Partner 1/Consolidated Management 2/Extensible SNMP Agent Description, Operator's Guide and Reference (3020-3-L04(E)), for UNIX systems

Job Management Partner 1/NQSEXEC System Administrator's Guide (3020-3-F30(E))

Job Management Partner 1/Open Job Entry Description, User's Guide and Reference (6190-3-365(E)), for VOS3 systems

Job Management Partner 1/Open Job Entry Description, User's Guide and Reference (9000-3-365(E)), for MVS systems

Job Management Partner 1/Open Job Entry Description, User's Guide and Reference (9000-3-366(E)), for OSIV/MSP systems

Job Management Partner 1/Open Job Entry for Midrange Computer Description and User's Guide (9000-3-367(E))

C.2 Conventions: Abbreviations for product names

This manual uses the following abbreviations for product names:

Abbreviation

Full name or meaning

JP1/AJS3

JP1/AJS3 - Manager

Job Management Partner 1/Automatic Job Management System 3 - Manager

JP1/AJS3 - Agent

Job Management Partner 1/Automatic Job Management System 3 - Agent

JP1/AJS3 - View

Job Management Partner 1/Automatic Job Management System 3 - View

JP1/AJS2

JP1/AJS2 - Manager

Job Management Partner 1/Automatic Job Management System 2 - Manager

JP1/AJS2 - Agent

Job Management Partner 1/Automatic Job Management System 2 - Agent

JP1/AJS2 - View

Job Management Partner 1/Automatic Job Management System 2 - View

JP1/AJS2 - Advanced Manager

Job Management Partner 1/Automatic Job Management System 2 - Advanced Manager#

JP1/AJS2 - Client Toolkit

Job Management Partner 1/Automatic Job Management System 2 - Client Toolkit#

JP1/AJS3 - Definition Assistant

Job Management Partner 1/Automatic Job Management System 3 - Definition Assistant

JP1/AJS3 for Enterprise Applications

Job Management Partner 1/Automatic Job Management System 3 for Enterprise Applications

JP1/AJS3 - Web Operation Assistant

Job Management Partner 1/Automatic Job Management System 3 - Web Operation Assistant

JP1/DH - AJE

Job Management Partner 1/Data Highway - Automatic Job Executor

JP1/DH - Server

Job Management Partner 1/Data Highway - Server

JP1/FTP

Job Management Partner 1/File Transmission Server/FTP

JP1/IM

JP1/IM - Manager

Job Management Partner 1/Integrated Management - Manager

JP1/IM - View

Job Management Partner 1/Integrated Management - View

JP1/IM - Central Console

Job Management Partner 1/Integrated Manager - Central Console#

JP1/IM - Central Scope

Job Management Partner 1/Integrated Manager - Central Scope#

JP1/OJE

Job Management Partner 1/Open Job Entry

JP1/OJE for Midrange Computer

Job Management Partner 1/Open Job Entry for Midrange Computer

JP1/OJE for VOS3

VOS3 Job Management Partner 1/Open Job Entry

JP1/SES

Job Management Partner 1/System Event Service

NNM

HP NNM

HP Network Node Manager Software version 7.5 or earlier

HP Network Node Manager Software Starter Edition version 7.5 or earlier

AIX

AIX 5L 5.3

AIX V6.1

AIX V7.1

HP-UX

HP-UX (IPF)

HP-UX 11i V2(IPF)

HP-UX 11i V3(IPF)

Linux

Linux 6.1 (x86)

Red Hat Enterprise Linux(R) Server 6.1 (32-bit x86)

Linux 6.1 (x64)

Red Hat Enterprise Linux(R) Server 6.1 (64-bit x86_64)

Linux 5.1 (x86)

Red Hat Enterprise Linux(R) 5.1 (x86)

Linux 5.1 (AMD/Intel 64)

Red Hat Enterprise Linux(R) 5.1 (AMD/Intel 64)

SAP BW

SAP Business Information Warehouse

SAP R/3

SAP R/3(R)

Solaris

Solaris 10(SPARC)

Solaris 11(SPARC)

# Version 7

In this manual, JP1/AJS is sometimes used generically, referring to JP1/AJS3 and JP1/AJS2.

UNIX is sometimes used generically, referring to HP-UX, Solaris, AIX and Linux.

C.3 Conventions: Acronyms

This manual also uses the following acronyms:

Acronym

Full name or meaning

ACL

Access Control List

DB

Database

DBMS

Database Management System

DNS

Domain Name System

EUC

Extended UNIX Code

FQDN

Fully Qualified Domain Name

FTP

File Transfer Protocol

GUI

Graphical User Interface

IME

Input Method Editor

IPF

Itanium(R) Processor Family

ISAM

Indexed Sequential Access Method

LAN

Local Area Network

MAPI

Messaging Application Programming Interface

MIB

Management Information Base

MIME

Multipurpose Internet Mail Extensions

NAT

Network Address Translator

NFS

Network File System

NIC

Network Interface Card

OS

Operating System

PDF

Portable Document Format

RDB

Relational Database

SMTP

Simple Mail Transfer Protocol

SNMP

Simple Network Management Protocol

SUP

Service Using Program

TCP/IP

Transmission Control Protocol/Internet Protocol

UAC

User Account Control

UNC

Universal Naming Convention

WAN

Wide Area Network

WOW64

Windows On Windows 64

WSDL

Web Services Description Language

C.4 Conventions: KB, MB, GB, and TB

This manual uses the following conventions:

1 KB (kilobyte) is 1,024 bytes.

1 MB (megabyte) is 1,024² bytes.

1 GB (gigabyte) is 1,024³ bytes.

1 TB (terabyte) is 1,024⁴ bytes.

C.5 Conventions: Meaning of "directory" and "folder"

As a general rule, Windows folder names are used in this manual if they are identical to UNIX directory names.

C.6 Conventions: Meaning of "member of the Administrators group"

The term member of the Administrators group in this manual refers to a user who is a member of the Administrators group on the local PC only. The privileges of local users, domain users, and Active Directory users are no different as long as these users are members of the Administrators group on the local PC.

C.7 Default installation folders of JP1/AJS3 for Windows

The default installation folders of JP1/AJS3 for Windows are as follows:

Default installation folders of JP1/AJS3 - Manager:

system-drive\Program Files#\HITACHI\JP1AJS2

and

system-drive\Program Files#\HITACHI\JP1AJS2CM

Default installation folder of JP1/AJS3 - Agent:

system-drive\Program Files#\HITACHI\JP1AJS2

Default installation folder of JP1/AJS3 - View:

system-drive\Program Files#\HITACHI\JP1AJS2V

#

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

C.8 About the Start menu in Windows

In Windows Server 2012 or later, instead of using the Start menu, perform the operation as described below.

In Windows 8 or Windows Server 2012 (except Windows Server 2012 R2):

Right-click on the Start screen to display the All Apps screen.

In Windows 8.1 or Windows Server 2012 R2:

Click the down-pointing arrow icon to display the Apps screen.

C.9 Online manual

JP1/AJS3 - View comes with an online manual that you can read in browsers.

The HTML manual contains the same content as the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

In JP1/AJS3 - View, you can view the manual by choosing Help and then Contents. You can also press the F1 key to view the manual contents. Your Web browser must be associated with a file that has the extension htm; otherwise, the online manual will not be displayed correctly. If this happens, associate the htm file with the Web browser.

Cautionary note

Depending on the OS settings, the online manual might appear in the active window of the browser when you launch the manual from the Start menu.

C.10 Regular expressions available in JP1/AJS3

Regular expressions can be used in some items in dialog boxes and commands. For details about regular expressions in Windows, see the Job Management Partner 1/Base User's Guide. For details about regular expressions in UNIX, see your UNIX documentation.

The regular expressions that you can use when executing an event job on a Windows host depend on the JP1/Base settings. For details on setting regular expressions for event job execution, see the explanation about extending the available regular expressions in the Job Management Partner 1/Base User's Guide.

Searching may take a long time if you often use the regular expression .* (which means match any character or characters). In long messages, use .* only where necessary. In UNIX, you can use [^ ]* (repeat characters other than space characters) instead of .* when you want to find a match other than space characters. Using [^ ]* reduces the search time.

C.11 About the 3rd level and 4th level Kanji characters added in JIS 2004 (JIS X 0213:2004)

JP1/AJS3 cannot use the 3rd level and 4th level Kanji characters added in JIS 2004. If these characters are used, operation might not be performed correctly.

C.12 About NNM linkage

JP1/AJS3 supports linkage with the following products:

HP Network Node Manager Software version 6 or earlier

HP Network Node Manager Starter Edition Software version 7.5 or earlier

In this manual, these products are indicated as HP NNM.

Note that linkage with the following products is not supported:

HP Network Node Manager i Software v8.10

D. Glossary

abnormal end

A jobnet ends abnormally if one of the processes defined in the jobnet fails to execute properly. The jobnet is interrupted at that point and subsequent processes are not executed.

A job ends abnormally if it fails to execute properly. The process is interrupted at that point.

The embedded database system ends abnormally when an error causes its status to change from active to stopped or paused, without any intervention by the user. For details, see D. How the Embedded Database Operates in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

abnormal threshold

A value that is compared with a job's return code to evaluate whether the job ended normally or abnormally.

action job

A job that sends email, or sends events reporting the system status to JP1/ IM or the HP NNM.

agent host

A host that executes jobs on request from a manager host. JP1/AJS3 - Agent must be installed on the agent host, or since JP1/AJS3 - Manager also provides JP1/AJS3 - Agent functionality, JP1/AJS3 - Manager might be installed on the agent host.

The agent host executes the job on receipt of a job request from the manager host. At completion of the job, the agent host receives the execution result (return value) of the executable file and forwards it to the manager host.

AJS3 unit monitored object

An object for monitoring the status of root jobnets in JP1/AJS3. By defining the monitoring conditions in this object, you can then switch to monitoring mode and monitor the root jobnets.

AJS administrator

A user that has access permissions almost equivalent to superuser permissions for JP1/AJS3. Only one of the JP1/Base administrators in the JP1 administrators group can be designated as the AJS administrator. An ordinary user designated as the AJS administrator can perform such JP1/AJS3 system management operations as specifying the environment settings and starting and stopping services.

AJSPATH

An environment variable for defining the paths used by JP1/AJS3. When this environment variable is defined, you do not need to specify the full path when specifying a jobnet name in a command.

automatic retry

A function that automatically retries execution of a job if the executable file defined for the job terminates abnormally. Because jobs that have terminated abnormally due to a temporary error might be able to run normally when automatically retried, this function can improve the system availability.

backup box

A directory or a folder for storing backup files.

backup file

A file containing the units defined in JP1/AJS3.

base day

A date specified as the starting day of the month in the calendar information.

base time

The time that marks when a day ends and the next day begins in a JP1/AJS3 system. For example, if 8:00 a.m. is set as the base time, the previous day is regarded as lasting until 7:59 a.m.

calendar information

Information about open days and closed days for jobnet execution. You can define calendar information separately for each job group. The calendar information specifies the days on which jobnets in the job group can and cannot be executed. (When the processing cycle falls on a closed day, the jobnet can be executed on another day if a substitute schedule is defined.) For open days, you can specify the base day, base month, and base time.

closed day

A day on which jobnets are not executed. However, if Execute without shift is specified, the jobnet will be executed on that closed day.

cluster system

A system configured as multiple linked server systems, designed to continue operation even if one system fails. If a failure occurs in the server currently executing applications (primary node), the other standby server (secondary node) takes over and continues processing the applications. Therefore, a cluster system is also referred to as a node switching system.

The term cluster system can also mean load balancing based on parallel processing. In this manual, however, cluster system refers only to node-switching functionality for preventing interruption of application processing.

common user profile

A file containing the environment settings for JP1/AJS3 - View, accessible to all JP1 users. The system administrator saves the common user profile in JP1/AJS3 - Manager. JP1 users can download this file, enabling the same JP1/AJS3 - View environment to be set for all JP1 users.

A common user profile is useful when a large number of JP1 users will be using JP1/AJS3 - View in the same environment.

compatible ISAM configuration

A system configuration in which JP1/AJS3 information is managed exclusively by the ISAM database.

This configuration is offered to help users migrate from JP1/AJS2 version 8 or earlier. It can restrict to the same degree as in previous versions, the use of resources such as hard disk and memory. However, from version 9 only a subset of the new features offered is provided.

correlation ID

Information for identifying sent and received messages. The correlation ID is received in the character code set specified by the sender.

custom job

A predefined job for executing a task with a specific purpose. JP1/AJS3 provides standard custom jobs such as file transfer and job requests to a mainframe. In addition, you can register your own frequently used jobs as custom jobs. When registering a custom job, you can represent it by creating an icon with a special shape and design, and you can create a dialog box for entering job information.

To use a custom job, the requisite program for the job must be installed.

Daily Schedule window

A window that displays each day's execution schedules, execution status, and execution results.

data collection tool

These tools are provided by JP1 for batch collection of log data and other information required to investigate problems. In addition to problems in JP1/AJS3, problems might occur in the OS or user programs or as the result of operational mistakes. The data collection tools collect JP1/AJS3 log data and other information, such as OS log data, at the same time.

default queue

A queue created in an agent host for executing jobs. You must always create a default queue.

When you submit a job for execution, if you specify an agent host name as the destination, the job will be submitted to the default queue of the specified agent host.

dependent job

A job executed when the judgment result of a judgment job is true.

dependent jobnet

A jobnet executed when the judgment result of a judgment job is true.

disaster recovery

Disaster recovery refers to measures that are taken when there are unexpected occurrences such as system shutdown due to a large-scale disaster.

JP1/AJS3 supports a disaster recovery operation that copies JP1/AJS3 data on the shared disk to a shared disk at a remote site. If the JP1/AJS3 system fails because of an event such as a disaster, the JP1/AJS3 system at the remote site can continue operation by using the copied data. The disk copy and mirroring functionality of hardware is used to copy data between shared disks.

embedded database

The standard database of JP1/AJS3. An embedded database offers high reliability, and is well suited to large-scale systems that handle large quantities of information.

embedded database administrator (database administrator)

A user authorized to assign and cancel various permissions for an embedded database (a user with DBA permissions).

Database administrators are managed within an embedded database.

embedded database operation commands

A generic term for commands whose name begins with ajsembdb.

embedded database service

A service that provides the environment for using the embedded database in Windows. This service must be started before you can use the embedded database. The name of the embedded database service is JP1/AJS3 Database setup-identifier.

embedded database system administrator

The owner of an embedded database practical directory and embedded database file system areas (data area and system area). The embedded database system administrator can execute commands for an embedded database.

The OS manages embedded database system administrators.

end with warning

A status indicating that a jobnet finished, but some of the processes defined in the jobnet were executed incorrectly. The jobnet continues to the end without interruption.

This ending method is used when an error is not so serious as to terminate the jobnet.

environment setting parameter

A parameter for defining the information required to operate JP1/AJS3, written in an environment settings file. With these parameters, you can specify the directory in which information about JP1/AJS3 units is stored, whether to output syslog messages, and other such preferences.

environment settings file

A file containing the settings required to operate JP1/AJS3, such as the scheduler service environment and job execution environment.

event

A specific event, such as email reception or file update, that occurred in the system. Events can be used to start a job or jobnet, and can be monitored using an event job.

event job

A job that monitors specific events occurring in the system. When an event job is initiated, it starts monitoring for file updates, incoming messages, or other specified events.

execution agent

The logical name of an agent host that executes jobs or jobnets. Based on the agent information defined in the manager host, the manager maps the execution agent specified in the job or jobnet to the physical host name of the agent host, and distributes the job or jobnet accordingly.

execution agent group

A group of execution agents configured to realize load distribution. The manager distributes jobs among the execution agents according to their assigned priorities.

execution agent restriction

A function that suppresses execution of jobs on an execution agent that the administrator has not permitted to execute the jobs. The execution agents permitted to execute jobs can be set for each unit.

When the execution agent profile is enabled, this function checks for whether the execution agent is permitted to execute jobs at the following times:

When a unit is defined in JP1/AJS3 - View

When the ajschkdef command is used to conduct a definition pre-check

When a job is executed

execution ID

A number assigned to an execution schedule of the uppermost jobnet.

execution-locked resource

A means of preventing multiple jobs from executing at the same time, by specifying the same resource name (execution-locked resource name) for each job.

fixed execution registration

A method of registering a jobnet so that it starts and runs at a predetermined date and time calculated by the system from schedule definitions.

fixed schedule

A schedule set by absolute times when a jobnet is registered for fixed execution.

HP NNM

A suite of integrated network management tools from Hewlett-Packard Co. for managing network configuration, performance, and failures.

immediate execution registration

A method for starting and processing a jobnet immediately after registering it for execution.

ISAM database

The database that manages the execution environment for QUEUE jobs and submit jobs. Data is indexed using the Indexed Sequential Access Method (ISAM) and is managed in the database. The ISAM database is provided as standard with JP1/Base.

job

A group of commands, shell scripts, or Windows executable files.

job execution environment

A job execution environment consists of a JP1/AJS3 manager and agents.

The job execution environment for the manager is used to manage the definition information for execution agents (such as the maximum number of concurrently executable jobs and job transfer restriction status), job distribution method, and job execution results.

The job execution environment for the agent is used mainly to manage how a job is executed.

These job execution environments are managed by using a database and environment setting parameters.

When QUEUE jobs and submit jobs are used, the ISAM database and environment setting parameters are used as the job execution environment for the QUEUE jobs and submit jobs.

Note that queueless jobs are managed in the queueless job execution environment.

job group

A folder for classifying and managing jobnets.

job network element

The generic term for these elements is unit.

jobnet

A set of jobs associated in execution order. When a jobnet is executed, the jobs in the jobnet are automatically executed in their predetermined order.

jobnet connector

A unit for controlling the execution order of root jobnets. A jobnet connector establishes connections between root jobnets and controls their execution order by having connected generations wait for their counterparts to start or finish.

Jobnet Editor window

A window in which you can create new jobnets or edit existing jobnets.

Jobnet Monitor window

A window that displays the execution status or detailed execution results of jobnets or jobs. You can manipulate jobnets or jobs in this window.

JP1 event

Event information that is reported to JP1/Base when an event occurs in the system. JP1 events are reported to other systems via JP1/Base.

JP1 permission level

A name that indicates the operations that a JP1 user is allowed to perform on management targets (resources) defined in JP1/AJS3, including applications and events. Use JP1/Base to define JP1 permission levels.

JP1 resource group

A name given to a specific JP1/AJS3 unit for controlling access by JP1 users to that unit.

JP1 user

A user designation for using JP1/AJS3 or JP1/IM - Manager. Each JP1 user is registered in the authentication server, which controls the user's access to management targets (resources).

JP1/AJS3 - Definition Assistant

This program allows you to register a large amount of JP1/AJS3 definition information edited using an Excel template into a manager host, or to retrieve JP1/AJS3 definition information from a manager host to an Excel template. The Excel templates provided by JP1/AJS3 - Definition Assistant are called definition management templates. With a definition management template in the spreadsheet format, you can enter or edit definition information efficiently by using automatic filling, automatic filtering, and other Excel functionalities.

JP1/AJS3 - Print Option

This program allows you to display or print jobnet or schedule information formatted as needed (for example, as jobnet definition information, an execution schedule table, or an execution result confirmation table).

You can also output jobnet or schedule information in CSV format so that you can edit the information.

JP1/AJS3 Console Agent

A JP1/AJS3 component that regularly monitors the status of objects (root jobnets) on the local host, specified in JP1/AJS3 Console Manager. Any change in status is notified to JP1/AJS3 Console Manager.

JP1/AJS3 Console Manager

A JP1/AJS3 component that stores definitions about monitored objects defined in JP1/AJS3 Console View, and gets status information about monitored objects by issuing requests to JP1/AJS3 Console Agent.

JP1/AJS3 Console View

A JP1/AJS3 component that allows you to define objects to be monitored, using a graphical user interface. The definitions are stored in JP1/AJS3 Console Manager. Using JP1/AJS3 Console View, you can view and monitor the status of target objects notified by JP1/AJS3 Console Agent to JP1/AJS3 Console Manager. You need to log in to JP1/AJS3 Console Manager before using JP1/AJS3 Console View.

JP1/AJS3 for Enterprise Applications

A program that allows you to control jobs in an R/3 system from another system. You can submit, delete, and monitor R/3 jobs.

R/3 jobs can be executed automatically from JP1/AJS3 if you register them as custom jobs for JP1/AJS3 for Enterprise Applications when you define a JP1/AJS3 jobnet.

JP1/AJS3 for Enterprise Applications is the successor to JP1/Application Manager for R/3.

JP1/Base

A program that provides the event service function. JP1/Base allows you to control the order in which services start, and it lets you send and receive JP1 events. JP1/Base is a prerequisite program for JP1/IM and JP1/AJS3. When JP1/IM is deployed in a system with JP1/AJS3, JP1/Base provides functionality for restricting operations by JP1 users.

JP1/DH - AJE

A program that automatically sends data to and receives data from JP1/DH - Server.

JP1/FTP

A program for performing file transfer tasks efficiently, including file transfer/reception linked to application execution, scheduled file transfer, and automated program execution following file reception. JP1/FTP supports monitoring of transfer status, enhancing file transfer reliability.

JP1/IM

A program for centrally monitoring a distributed system. Using the windows in JP1/IM - View, the system administrator can monitor JP1 events, which provide information about job execution status or problems in the distributed system.

JP1/NQSEXEC

A program for executing routine batch processing on a distributed system and for running batch jobs efficiently.

JP1/OJE for Midrange Computer

A program for submitting batch jobs to AS/400 from a Windows or UNIX host, or for submitting batch jobs from AS/400 to a Windows or UNIX host.

JP1/OJE for VOS3

A program that links with JP1/AJS3 for executing and monitoring batch jobs between a Windows or UNIX system and a mainframe (VOS3).

JP1/Script

A program for creating and executing scripts (batch files) that control jobs on Windows. Job operation can be automated by linking JP1/Script with JP1/AJS3.

JP1/Software Distribution

A general term for a system that distributes software and manages clients using batch operations over a network.

By linking with JP1/AJS3 using the JP1/Software Distribution command interface, the user can automate software distribution and other tasks.

judgment job

A job that executes a dependent unit if the judgment result of a specified condition is true.

judgment value

A value for evaluating whether a job ended normally or abnormally.

kill

To forcibly terminate a unit being executed.

When the root jobnet is killed, all the jobs being executed are killed and the jobnets are terminated.

list file

A file containing a list of extracts from sent and received mail.

logical host

A logical server that provides the JP1 execution environment for running a cluster system. If a failure occurs on the primary node, the logical host is switched to the secondary node.

Each logical host has a unique IP address. At failover, the secondary node inherits the IP address. Thus, if the physical server fails, clients can access the secondary node using the same IP address. To the clients, it appears that one server is operating continuously.

macro variable

A variable used to pass information from one job to another job during execution.

A macro variable name and passing information (or for an event job, a passing information name) are specified during unit definition. A macro variable can be used during job execution by specifying the name of the macro variable in the succeeding job.

macro variable name

A character string in ?AJS2xxxxx? format that indicates the name of a macro variable. If a macro variable name is specified during the definition of a unit, the macro variable set in the preceding job can be used during job execution.

mail filtering application

A program or a shell script that converts email formats.

A mail filtering application is required to convert the character set when exchanging email in formats other than RFC822.

mail receipt parameter file

A file containing the mail receipt monitoring parameters defined by the user. The file extension is .prm. This file is created automatically when the user defines a Receive Email Event job.

mail send parameter file

A file containing the mail send parameters defined by the user. The file extension is .prm. This file is created automatically when the user defines a Send Email Action job.

manager host

A host that manages jobnet definitions and schedule information in a database, and requests agent hosts to execute jobs. You must install JP1/AJS3 - Manager on the manager host.

The manager host creates jobnet execution schedules from the defined schedule information. At jobnet run time, the manager host starts the executable files defined as jobs, forwards the job definitions to an agent host, and requests the agent host to execute the jobs. When execution completes, the execution result is received by the agent host and the database is updated. Based on the updated information, the manager host executes a succeeding job or schedules the next execution of the jobnet.

manager job group

A job group for monitoring JP1/AJS3 - Manager applications from another JP1/AJS3 - Manager.

manager jobnet

A jobnet for monitoring JP1/AJS3 - Manager applications from another JP1/AJS3 - Manager.

MAPI (Messaging Application Programming Interface)

The standard messaging API for Windows.

max. shiftable days

A set number of days within which to shift the next scheduled execution date when the recalculated date falls on a closed day.

maximum number of concurrently executable jobs

The maximum number of jobs that can be executed concurrently.

message ID

One item in an MQSeries message descriptor. Message IDs are stored in the character set specified by the sender. They can be used as storage locations to help identify messages.

MIME (Multipurpose Internet Mail Extensions)

An extended SMTP function used for sending and receiving non-ASCII data.

MIME specifies various procedures, such as how data is to be transmitted between email systems, and the format of control messages for email transfer.

Monthly Schedule window

A window that displays each month's execution schedules and execution results.

nested jobnet

A jobnet defined within another jobnet.

node switching system

See cluster system.

normal end

A normal end of a jobnet occurs when all the processes defined in the jobnet have executed correctly and the jobnet has completed.

A normal end of a job occurs when the job has executed correctly.

open day

A day when jobnets run.

passing information

Values specified for macro variables during registration for execution, event IDs, event issuance dates, and other information (values) that is dynamically set in macro variables and passed to succeeding jobs.

passing information name

A variable name indicating the event information to be received by an event job.

Variable names that can be used for this purpose include EVID (event ID) and EVDATE (event issuance date). These variable names are specified during the definition of an event job.

physical host

An environment unique to each of the servers (nodes) in a cluster system. When a secondary node takes over from the primary node, the environment of the physical host remains unchanged and is not inherited by the other server.

planned execution registration

A method of registering a jobnet so that it starts and executes according to schedule definitions.

planning group

A unit for switching execution among multiple root jobnets in a planned manner. Directly under a planning group, you can create a number of root jobnets, each defined differently and with differing execution schedules. This enables the root jobnets to be executed automatically in turn, according to the set schedules.

preceding job

A job executed immediately before another job or jobnet.

preceding jobnet

A jobnet executed immediately before another job or jobnet.

processing cycle

The interval between one execution start date and the next execution start date of a jobnet. By defining a processing cycle, you can execute a jobnet at regular intervals.

queue

An area for temporarily keeping jobs registered for execution. Jobs are submitted to the queue in order of registration, and are sequentially transferred for execution to the agent connected to that queue.

The queue controls the number of jobs that the agent executes concurrently, thereby preventing any degradation in performance caused by a large number of jobs being executed at the same time.

queueless job

A job transferred directly from the manager to an agent host for execution, without using a queue. Queueless jobs simplify processing because they are not managed in a queue by the job execution control. As a result, they offer better performance than ordinary queued jobs, allowing more jobs to be executed within a given period of time. However, job execution control functions such as execution agent names and execution agent groups are not available with queueless jobs.

You can define PC jobs and Unix jobs in a jobnet as queueless jobs by specifying Queueless Agent as the execution service.

Unless otherwise indicated, the descriptions in this manual apply to jobs for which Standard is specified as the execution service.

queueless job execution environment

A queueless job execution environment consists of execution environments for the JP1/AJS3 manager (scheduler service and queueless file transfer service) and queueless agents (queueless agent services). The execution of queueless jobs is managed by using the environment setting parameters for the job execution environment.

Note that the job execution environment must be set up by using the ajsqlsetup command before environment setting parameters are set.

queuing job

A job submitted directly to a queue and waiting to be executed.

recovery job

A job to be executed when a job or jobnet ends abnormally.

recovery jobnet

A jobnet to be executed when a job or jobnet ends abnormally.

schedule by days from start

A schedule defined for recalculating the next scheduled execution date, using as the base day the next scheduled execution date determined from the execution start time, processing cycle, and substitute schedule for closed days.

schedule information file

A text file containing schedule information parameters, entered by command when setting fixed execution registration for a jobnet.

schedule rule

Jobnet information such as execution start time and processing cycle. Up to 144 schedule rules can be defined for a single jobnet.

scheduler service

A service that manages the schedules for jobnet execution, and executes processes according to those schedules. Each scheduler service manages all the units in the root job group whose name matches the scheduler service name.

Multiple scheduler services can be activated in a single manager. This allows root job groups to be managed individually. For example, if you start a separate scheduler service for each application, each scheduler service can run its specific application (jobnet and jobs) in parallel, independently of the other scheduler services.

shift days

A set number of days within which to determine a substitute date when the next execution date falls on a closed day.

shutdown status

A situation in which a jobnet fails to start or end due to an error, and the execution status or the next scheduled execution cannot be verified. If this happens, you must cancel and then re-register the jobnet for execution.

SMTP (Simple Mail Transfer Protocol)

A protocol, generally used in UNIX networks, for transferring ASCII data by TCP/IP between heterogeneous systems.

standard configuration

A system configuration in which JP1/AJS3 information is managed by the embedded database.

Unless otherwise indicated, the descriptions in this manual relate to a system in a standard configuration.

Note that the ISAM database is still used to store some information related to QUEUE jobs and submit jobs.

start condition

A definition of the conditions under which a jobnet starts when the jobnet is driven by a specific event.

subject

A character string written in the subject line of an email message. Non-ASCII characters are supported in JP1/AJS3, but might not be supported in connected email systems.

submit

To request the system to execute a job.

submit job

A standard job registered using the jpqjobsub command.

substitute schedule

A means of executing a jobnet on a different day when the next execution date, determined from the jobnet schedule, falls on a closed day.

succeeding job

A job executed immediately after another job or jobnet.

succeeding jobnet

A jobnet executed immediately after another job or jobnet.

suspend

To suppress the execution of the root jobnet and lower units.

When you change a definition under a root jobnet that has been registered for execution, you should suspend the root jobnet to prevent erroneous operation such as the execution control processing running with the old definition. By suspending the root jobnet, the redefinition processing can be synchronized with the execution control processing.

threshold

A value for evaluating the termination status of a job. You can define an abnormal threshold and a warning threshold for each job.

timeout period

A time interval after which an executed job is forcibly terminated if there was no response from the job or if it failed to complete during the specified period.

TP1/Server Base

Software for distributing transaction processing and server processing in an open system. JP1/AJS2 uses TP1/Server Base transaction processing.

unit

A generic term for any job network element.

unit definition parameter file

A text file containing unit definition parameters, entered by command when defining the units.

unit ID

A unique number allocated to a unit.

unit whose end is being waited for

A unit specified as a wait condition of another unit. The unit for which the unit whose end is being waited for is specified as a wait condition starts when the unit whose end is being waited for terminates.

unit with wait condition

A unit for which another unit (unit whose end is being waited for) is specified as a wait condition. The unit with the wait condition starts execution when the associated unit (unit whose end is being waited for) terminates.

virtual machine

A virtual computer system (host) created on a physical host to run an OS is called a virtual machine. Multiple virtual machines can operate on a single physical host to execute multiple processes simultaneously or to run different OSs concurrently.

By replicating a virtual machine that has already been set up, you can easily increase hosts that have the same environment.

wait condition

A condition set for a unit that allows the execution order of units across jobnets to be controlled. A unit with another unit specified as a wait condition starts execution when the associated unit terminates.

warning threshold

A value for evaluating whether a job ended with a warning.

Windows Messaging

A facility that provides an interface for sending and receiving email. Using Windows Messaging, you can manage, access, and share a variety of information such as data received from an online service.

Index

Symbols

_AgentStartStopResolveMode[1]

A

abbreviations for products[1]

abnormal end[1]

abnormal threshold[1]

About the 3rd level and 4th level Kanji characters added in JIS 2004 (JIS X 0213:2004)[1]

About the Start menu in Windows[1]

access permissions for directories and files specified in environment setting parameters required for AJS administrators to perform operations[1]

acronyms[1]

action control environment

setting up[1]

action job[1]

ADMACLIMIT[1]

AfterForkPipeTimeout[1]

agent host[1]

AGENTPROFMEMSIZE[1]

AJS3 unit monitored object[1]

AJS administrator[1]

AJSBKUROOT[1]

AJSCHARCODE[1]

AJSCHK_CHARCODE[1]

AJSCHK_CHECKFILE[1]

AJSCHK_LOGDIR[1]

AJSCHK_LOGSIZE[1]

AJSCHK_TRACELOGFILE[1]

AJSDBDIRECTORY[1]

AJSDBTYPE[1]

AJSINETDLOGSIZE[1]

AJSLOG[1]

AJSLOGDIR[1], [2]

AJSLOGFILE1[1]

AJSLOGFILE2[1]

AJSLOGOUTPUTDEST[1]

AJSLOGOUTPUTEXTEND[1]

AJSLOGOUTPUTYEAR[1]

AJSPATH[1]

AJSPRINTNETSCHPRF[1]

AJSPRINTSORTUNITINF[1]

AJSQL_AGTWORKPATH[1]

AJSQL_ATTACH[1]

AJSQL_CHARCODE[1]

AJSQL_CJOBMAX[1]

AJSQL_CJOBWAITMAX[1]

AJSQL_CLUSTERREQ[1]

AJSQL_CONNECTCOUNT[1]

AJSQL_CONNECTINT[1]

AJSQL_CONNECTTIMEOUT[1]

AJSQL_CREATEWINDOWSTATION[1]

AJSQL_EXECCURRENTSCRIPT[1]

AJSQL_EXECLOG[1]

AJSQL_EXECLOG_AGTPATH[1]

AJSQL_EXECLOG_FTPPATH[1]

AJSQL_GETPASSWD_AGTRETRYCOUNT[1]

AJSQL_GETPASSWD_AGTRETRYINTERVAL[1]

AJSQL_GETPASSWD_FTPRETRYCOUNT[1]

AJSQL_GETPASSWD_FTPRETRYINTERVAL[1]

AJSQL_JOBMAX[1]

AJSQL_JOBWAITMAX[1]

AJSQL_LOADUSERPROFILE[1]

AJSQL_LOGFILE[1]

AJSQL_LOGSIZE[1]

AJSQL_NOATTACHREQ[1]

AJSQL_STATFILE[1]

AJSQL_STATSIZE[1]

AJSQL_TRACELOGFILE[1]

AJSQL_VARDQUOTEADD[1]

AJSSERVICEID[1]

AJSSYSDIR[1], [2]

AJSSYSLOG[1]

AJSTMPDIR[1]

AlartContentJob[1]

All Users[1]

AUTHLOG[1]

AUTHSYSLOG[1]

AutoCreate[1]

AutoCreateExecJobs[1]

AutoCreateMaxJobs[1]

AutoCreatePriority[1]

AutoCreateWarnJobs[1]

automatic retry[1]

AUTORESTARTCOUNT[1]

AUTOSTART[1]

B

BACKGROUNDLEAVE[1]

backup box[1]

backup file[1]

base day[1]

base time[1]

BlockadeTimeoutInterval[1]

C

calendar information[1]

CHANGEPASSWORD[1]

CHANGEPWDLOG[1]

CHARCODE[1]

ClientBindFlag[1]

ClientConnectTimeout[1], [2]

ClientRetryCount[1]

ClientRetryInterval[1]

closed day[1]

cluster system[1]

ColdStartMode[1]

COMMANDEVENT[1]

common user profile[1]

CommunicateRetryCount[1], [2], [3], [4]

CommunicateRetryInterval[1], [2], [3], [4]

CommunicateTimeout[1]

communication control environment

setting up[1]

CONNECTIONRESTRICTION[1]

ConnectTimeout[1], [2], [3], [4]

CONRESTRICTLOG[1]

CONRESTRICTSYSLOG[1]

conventions

abbreviations for products[1]

acronyms[1]

fonts and symbols[1]

KB, MB, GB, and TB[1]

meaning of directory and folder[1]

meaning of member of Administrators group[1]

version numbers[1]

correlation ID[1]

custom job[1]

D

Daily Schedule window[1]

database administrator[1]

DatabasePath[1]

data collection tool[1]

DATADIRECTORY[1]

DEFAULTPRIORITY[1]

default queue[1]

defaults

installation folders of JP1/AJS3 for Windows[1]

DEFAULTSERVICENAME[1]

DEFLENTYPE[1]

DeleteFlashOption[1]

dependent job[1]

dependent jobnet[1]

directory

term defined[1]

DISABLE_FS_REDIRECTION[1], [2]

disaster recovery[1]

DNSEstablish[1]

E

embedded database

administrator, glossary definition[1]

glossary definition[1]

operation commands, glossary definition[1]

service, glossary definition[1]

system administrator, glossary definition[1]

ENABLE_LONG_EXT[1], [2]

ENABLEOPERATION[1]

end with warning[1]

EnumJobSaveMemory[1]

environment

environment setting parameters[1]

setting up system management environment[1]

environment setting parameters

for communication control[1]

for event action control[1]

for job execution environment setting[1]

for JP1/AJS3 Console environment setup[1]

format[1]

for scheduler service environment setup[1]

for system management[1]

glossary definition[1]

JP1/AJS3 shared information[1]

queueless job execution environment setup[1]

settings for JP1/AJ3 definition precheck function[1]

environment settings file[1]

event[1]

event control environment

setting up[1]

event job[1]

EVENTRETRY[1]

EventSequential[1]

EventServerName[1]

EvJobExecContinue[1]

EvjobInfFile[1]

EVProcessHA[1]

EXECDEFER[1]

EXECREGISTRATIONNUMBER[1]

ExecutingJobChangeStatus[1]

ExecutingJobRecoveryTime[1]

execution agent[1]

execution agent group[1]

execution agent profile[1]

execution agent restriction[1]

execution ID[1]

execution-locked resource[1]

F

FGRECONLMT[1]

FileAccessPermissionMode[1]

FilewatchinfContinue[1]

FileWriteMode[1], [2]

fixed execution registration[1]

FixedHostnameForAgent[1]

fixed schedule[1]

FlashOption[1]

FLBDLOGSIZE[1]

folder

term defined[1]

font conventions[1]

format

environment setting parameters[1]

G

GB meaning[1]

GetFQDNForShortNameOnly[1]

GetPasswd_RetryCount[1]

GetPasswd_RetryInterval[1]

Glossary[1]

GWMAXCONNECTION[1]

GWPROCESSHA[1]

GWRESTARTCOUNT[1]

H

HIDEOTHERLHOST[1]

HIDEOTHERSERVICE[1]

HLOGDLOG[1]

HLOGDSYSLOG[1]

HNTRLOGLEVEL[1], [2]

HOSTLOGFILE1[1]

HOSTLOGFILE2[1]

HOSTLOGHEADER[1]

HOSTLOGOUTPUTYEAR[1]

HOSTLOGSIZE[1]

HowUseInfWhenHA[1]

HP NNM[1]

term defined[1]

I

IgnoreResultFileError[1], [2]

immediate execution registration[1]

INFOLOG[1]

InformationWhenShutDown[1]

installation folders

default for JP1/AJS3 for Windows[1]

IPC_CONNECTTIMEOUT[1]

IPC_LOCALTIMEOUT[1]

IPC_TIMEOUT[1], [2]

IPCRETRYCOUNT[1], [2]

IPCRETRYINTERVAL[1], [2]

IsAccessTokenCache[1]

ISAM

compatible ISAM configuration, glossary definition[1]

database, glossary definition[1]

ISAMWRITEMODE[1]

IsCacheCmdSearchPath[1]

IsExecFindExecutable[1]

IsHA[1], [2], [3], [4]

IsLimitCoreSize[1]

IsLimitCpuTime[1]

IsLimitDataSize[1]

IsLimitFileSize[1]

IsLimitMemorySize[1]

IsLimitNoFile[1]

IsLimitStackSize[1]

IsLimitWorkSize[1]

IsSigchldDefault[1]

IsUseWorkPath[1]

J

job[1]

JOBDELAYWARNMSG[1]

JOBEXECIPCBUFSIZE[1]

job execution environment[1]

setting up[1]

job group[1]

JOBINFDIR[1]

JOBLOG[1]

jobnet connector[1]

Jobnet Editor window[1]

Jobnet Monitor window[1]

jobnets

glossary definition[1]

job network element[1]

JOBSTATUSPORT[1]

JOBSYSLOG[1]

output messages[1]

JP1/AJS3 Console Agent[1]

JP1/AJS3 Console environment

setting up[1]

JP1/AJS3 Console Manager[1]

JP1/AJS3 Console View[1]

JP1/AJS3 - Definition Assistant[1]

JP1/AJS3 definition pre-check function

setting up[1]

JP1/AJS3 for Enterprise Applications[1]

JP1/AJS3 - Print Option[1]

JP1/AJS3 shared information

setting up[1]

JP1/Base[1]

JP1/DH - AJE[1]

JP1/FTP[1]

JP1/IM[1]

JP1/NQSEXEC[1]

JP1/OJE for Midrange Computer[1]

JP1/OJE for VOS3[1]

JP1/Script[1]

JP1/Software Distribution[1]

JP1 event[1]

JP1 permission level[1]

JP1 resource group[1]

JP1 user[1]

JP1-user-name[1]

judgment job[1]

judgment value[1]

K

KB meaning[1]

kill[1]

L

LANG environment variable[1]

LARGEFILEUSE[1]

LeastRecentlyUsed[1]

LimitCoreSize[1]

LimitCpuTime[1]

LimitDataSize[1]

LimitFileSize[1]

LimitMemorySize[1]

LimitNoFile[1]

LimitReceiveFileSize[1]

LimitStackSize[1]

LimitWorkSize[1]

list file[1]

LoadUserProfile[1]

LOGDLOG[1]

LOGDSYSLOG[1]

LOGFILENUM[1]

LOGHEADER[1]

logical host[1]

LOGINFOALL[1]

LOGIPV6INFOALL[1]

LOGONSHMAX[1]

LogonUserRetryCount[1]

LogonUserRetryInterval[1]

LOGSIZE[1], [2]

M

MACROCHANGEFAIL[1]

MacroOptionReplaceMode[1]

macro variable[1]

macro variable name[1]

MacVarDQuotation[1]

mail filtering application[1]

mail receipt parameter file[1]

mail send parameter file[1]

manager host[1]

manager job group[1]

manager jobnet[1]

MAPI[1]

MASTERDABEND[1]

max. shiftable days[1]

MaximumAgent[1]

MaximumContentJob[1]

MaximumExecJobLogInterval[1]

MaximumExecJobLogOption[1]

maximum number of concurrently executable jobs[1]

MaximumQueue[1]

MaximumResource[1]

MAXSAVEGEN[1]

MAXSESSION[1], [2]

MB meaning[1]

member of the Administrators group

term defined[1]

MergeEnvMode[1]

message ID[1]

messages

output based on SYSLOGJOBMSG and JOBSYSLOG[1]

MIME[1]

MONLOG[1]

MONSYSLOG[1]

Monthly Schedule window[1]

N

nested jobnet[1]

NETLOG[1]

NETSYSLOG[1]

NNM linkage

supported products[1]

node switching system[1]

NONRELOADHOLDING[1]

normal end[1]

NotfyJobStateCount[1]

NotfyJobStateInterval[1]

NotificationConstantRetry[1]

NotificationRetryCount[1], [2]

NotificationRetryInterval[1], [2]

O

ObserveInterval[1]

online manual

contents[1]

OPELOG[1]

open day[1]

operation profile

overview[1]

OVERSCHEDULE[1]

P

passing information[1]

passing information name[1]

PassingInfoUsePreRc[1]

physical host[1]

PipeComTimeout[1]

planned execution registration[1]

planning group[1]

preceding job[1]

preceding jobnet[1]

PreserveMinute[1]

PreserveTerm[1]

PreventChangeJobOrder[1]

PreventResultFileLack[1]

PREWAITEXTEND[1]

PREWAITUSE[1]

processing cycle[1]

Q

QLMANCHARCODE[1]

queue[1]

queueless job[1]

queueless job execution environment[1]

setting up[1]

QUEUELESSMULTIREQ[1]

queuing job[1]

QueuingJobRecoveryTime[1]

R

RDBAUTHID[1]

RDBCHECKINTERVAL[1]

RDBCONNECTWAITTIME[1]

RDBHOST[1]

RDBIPC[1]

RDBPASSWORD[1]

RDBPORT[1]

RDBRECVMEMSIZE[1]

RDBSENDMEMSIZE[1]

RDBUSER[1]

ReceiveFileOption[1]

ReceiveFileSizeStatus[1]

RECONNECTINTERVAL[1]

recovery job[1]

recovery jobnet[1]

RecvTimeout[1]

Reference Material for This Manual[1]

REFLOG[1]

regular expressions available in JP1/AJS3[1]

Related publications[1]

REMNETSERVICENAME[1]

REQDAGTRECONNECTTIMEOUT[1]

REQDAGTREQCONNECTTIMEOUT[1]

RERUNSUBORDINATE[1]

ResolveAgentInfo[1]

RESTARTCLRTIME[1]

RetryAgtStartNotification[1]

REUSELOGON[1]

revisions

07-00[1]

07-50[1]

08-00[1]

09-00[1]

10-00[1]

10-10[1]

10-50[1]

RJCUSE[1]

ROOTJOBNETSCHEDULERANGE[1]

S

SAVEGENTYPE[1]

SAVEPLANINFO[1]

schedule by days from start[1]

schedule information file[1]

scheduler service[1]

scheduler service environment

setting up[1]

schedule rule[1]

SEND_PROCESS_RESTART_EVENT[1]

SEND_PROCESS_TERMINATED_ABNORMALLY_EVENT[1]

SEND_SYSTEM_CHILD_STARTSTOP_EVENT[1]

SEND_SYSTEM_RESTART_EVENT[1]

SEND_SYSTEM_STARTSTOP_EVENT[1]

SEND_SYSTEM_TERMINATED_ABNORMALLY_EVENT[1]

SERVICEMAXSESSION[1]

SESSIONTIMEOUT[1], [2]

shift days[1]

shutdown status[1]

SMTP[1]

standard configuration[1]

StandardTime[1]

start condition[1]

STARTMODE[1]

StartUpDelete[1]

subject[1]

submit[1]

submit job[1]

SUBMITRETRYINTERVAL[1]

substitute schedule[1]

succeeding job[1]

succeeding jobnet[1]

SUPPRESS[1]

suspend[1]

symbol conventions[1]

syntax

environment setting parameters[1]

SYSLOGCODE[1], [2]

SYSLOGJOBMSG[1]

output messages[1]

T

TABLENAMEPOSTFIX[1]

TABLENAMEPREFIX[1]

TB meaning[1]

threshold[1]

timeout period[1]

TP1/Server Base[1]

TRACELOGFILE[1], [2]

U

UACAdministratorsExec[1], [2]

unit[1]

unit-attribute profile[1]

UNITDEFDIVIDEUPDATE[1]

UNITDEFINERELOAD[1]

unit definition parameter file[1]

unit ID[1]

UNITPROFMEMSIZE[1]

unit whose end is being waited for[1]

unit with wait condition[1]

V

variable-name[1]

version number conventions[1]

version revisions[1]

VIEWSTATUSRANGE[1]

virtual machine[1]

VRSHIFT_IMMINT[1]

VRSHIFT_INTRERUN[1]

W

wait condition[1]

WaitInfFileOutDir[1], [2]

warning threshold[1]

Windows Messaging[1]

WorkPath[1], [2]