Preface
This manual describes the GUI operations of Job Management Partner 1/Automatic Job Management System 3 (abbreviated hereafter to JP1/AJS3).
- Organization of this preface
■ 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 is organized into the following parts. The manual is a common reference for all supported operating systems. Any platform-dependent differences in functionality are noted in the manual.
- PART 1: Overview
-
Part 1 provides an overview of JP1/AJS3 - View and JP1/AJS3 Console.
- PART 2: JP1/AJS3 - View
-
Part 2 describes, with the use of examples, how to use JP1/AJS3 - View in all system stages from design through operation, and the relevant commands.
- PART 3: JP1/AJS3 Console
-
Part 3 describes, with the use of examples, how to use JP1/AJS3 Console in all system stages from design through operation, and the relevant commands.
- PART 4: Windows
-
Part 4 describes the items displayed in the JP1/AJS3 - View and JP1/AJS3 Console windows and dialog boxes.
■ 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:
|
Italic |
Italic characters indicate a placeholder for some actual text to be provided by the user or system. For example:
Italic characters are also used for emphasis. For example:
|
Monospace |
Monospace characters indicate text that the user enters without change, or text (such as messages) output by the system. For example:
|
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.
|
(( )) (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)) |
|
2 |
System Design (Configuration) Guide (3021-3-319(E)) |
|
3 |
System Design (Work Tasks) Guide (3021-3-320(E)) |
|
4 |
Configuration Guide 1 (3021-3-321(E)) |
|
5 |
Configuration Guide 2 (3021-3-322(E)) |
|
6 |
Administration Guide (3021-3-323(E)) |
|
7 |
Troubleshooting (3021-3-324(E)) |
|
8 |
Operator's Guide (3021-3-325(E)) |
|
9 |
Command Reference 1 (3021-3-326(E)) |
|
10 |
Command Reference 2 (3021-3-327(E)) |
|
11 |
Linkage Guide (3021-3-328(E)) |
|
12 |
Messages 1 (3021-3-329(E)) |
|
13 |
Messages 2 (3021-3-330(E)) |
|
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 |
|
|
To configure a system (including installation and setup) that automatically runs jobs |
|
|
To design work tasks that will be automated (including job definitions and schedule definitions) |
|
|
To learn about monitoring and maintaining a running system |
|
|
To learn about what action you need to take for problems that occur during operation |
|
|
To learn about operating JP1/AJS3 |
|
|