Preface
This manual explains the messages output with a message ID by Job Management Partner 1/Base. In this manual, Job Management Partner 1 is abbreviated to JP1. This manual is for all supported operating systems. Any differences between operating systems in regard to the operation of this program are mentioned at the appropriate place in the manual.
- Organization of this preface
■ Intended readers
This manual is intended for:
-
System administrators who are responsible for introducing and operating JP1/Base.
-
System administrators and system operators who are responsible for introducing, configuring, and operating a system that incorporates JP1 products (such as JP1/IM, JP1/AJS, and JP1/Power Monitor) for which JP1/Base is a prerequisite.
■ Organization of this manual
This manual is organized as follows:
- 1. Overview of Messages
-
Chapter 1 provides an overview of JP1/Base messages, including the output destinations and the message format.
- 2. List of Messages
-
Chapter 2 explains the contents of JP1/Base messages.
■ JP1/Base manual organization
The JP1/Base documentation is divided into three manuals. Read the manual appropriate to your purpose, referring to the content of each manual shown in the following table.
|
Manual |
Content |
|---|---|
|
Job Management Partner 1/Base User's Guide |
|
|
Job Management Partner 1/Base Messages |
Messages |
|
Job Management Partner 1/Base Function Reference |
|
■ Conventions: "Administrator permissions" as used in this manual
In this manual, Administrator permissions refers to Administrator permissions for the local PC. The local user, domain user, or user of the Active Directory environment can perform tasks requiring Administrator permissions if granted Administrator permissions for the local PC.
■ Conventions: Directory names
HP-UX directory names are used in this manual as a general rule. The directory names have symbolic links, so that users of UNIX OSs other than HP-UX can use the same directory names.
When HP-UX uses a different directory name from another flavor of UNIX, both directory names are given.
■ Conventions: Fonts and symbols
Font and symbol conventions are classified as:
-
General font conventions
-
Conventions in syntax explanations
These conventions are described below.
General font conventions
The following table lists the general font conventions:
|
Font |
Convention |
|---|---|
|
Bold |
Bold type indicates text on a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example, bold is used in sentences such as the following:
|
|
Italics |
Italics are used to indicate a placeholder for some actual text provided by the user or system. Italics are also used for emphasis. For example:
|
|
Code font |
A code font indicates text that the user enters without change, or text (such as messages) output by the system. For example:
|
Examples of coding and messages appear as follows (although there may be some exceptions, such as when coding is included in a diagram):
MakeDatabase ... StoreDatabase temp DB32
In examples of coding, an ellipsis (...) indicates that one or more lines of coding are not shown for purposes of brevity.
Conventions in syntax explanations
Syntax definitions appear as follows:
StoreDatabase [temp|perm] (database-name ...)
The following table lists the conventions used in syntax explanations:
|
Example font or 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. |
|
perm |
Underlined characters indicate a default value. |
|
|
This symbol is used to explicitly indicate a space.
|
|
StoreDatabase |
Code-font characters must be entered exactly as shown. |
|
database-name |
This font style marks a placeholder that indicates where appropriate characters are to be entered in an actual command. |
|
SD |
Bold code-font characters indicate an abbreviation for a command. |
![[Figure]](GRAPHICS/TRIANGLE.GIF)
■ Conventions: Installation folder for JP1/Base
This manual uses the following to indicate the installation folder for JP1/Base:
|
Product |
Indication of an installation folder |
Installation folder# |
|---|---|---|
|
JP1/Base |
installation-folder |
|
#: The installation folders in this column are the default installation folders.
For Windows Vista or later, the manual uses the expression system-drive:\ProgramData. The actual value is determined by the OS environment variable when the program is installed. The installation destination may differ depending on the environment.
■ 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.
■ Other reference information
For other reference information, see Reference Material for this Manual in the Job Management Partner 1/Base User's Guide.