JP1 Version 12 JP1/Base Messages


This manual explains the messages output with a message ID by JP1/Base. 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:

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



JP1/Base User's Guide

  • Overview and functionality of JP1/Base

  • Setup of each function

  • Commands, definition files, and JP1 events

  • Troubleshooting

  • Processes, port numbers, and operation logs

JP1/Base Messages


JP1/Base Function Reference

  • Procedures for issuing and acquiring JP1 events by using a JP1 program or user application

  • Functions

■ 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: "syslog" as used in this manual

This manual assumes that messages are output to syslog. However, in SUSE Linux 15 or later, by default, log information is not output to syslog. Therefore, to output to syslog the messages for which the output destination

should be syslog, syslog output must be enabled.

For details about how to enable syslog output, see the manual JP1/Base User's Guide.

■ 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

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

Text formatting



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 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 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:




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.


Parentheses indicate the range of items to which the vertical bar (|) or ellipsis (...) is applicable.


This symbol is used to explicitly indicate a space. For example, AAA[Figure]BBB means that you must place a space between AAA and BBB.


When a syntax character shown above is used as an ordinary character, a backslash is prefixed to the character. For example, \| means | as an ordinary character, not as a syntax character.

■ Conventions: Installation folder for JP1/Base

This manual uses the following to indicate the installation folder for JP1/Base:


Indication of an installation folder

Installation folder#



In an x86 environment:

system-drive:\Program Files\HITACHI\JP1Base

In an x64 environment:

system-drive:\Program Files (x86)\HITACHI\JP1Base

#: 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 might 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:

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 JP1/Base User's Guide.