This manual explains messages in the following format:

---

KFPX₁ n₁ n₂ n₃ n₄ n₅ -I Y TYPEx

message-text

Explanation of the message:
S: Action taken by HiRDB once the message has been issued.
P: Action that should be taken by the programmer.
O: Action that should be taken by the operator.

Action

Action that should be taken by the HiRDB administrator.

Note

"Contact the customer engineer" in a message explanation means that the user should contact a Hitachi employee or customer service representative.

The following explains the codes used in the message ID:

KFP: Code indicating that the message was issued by the HiRDB system.

X₁: Code identifying the message management source:

A: Message concerning an SQL statement (this message is also output following the execution of a utility or command)

B: Distributed database message

C: Windows-specific message

D: Dictionary manager message

H: Database-related message

I: HiRDB file system message

J: JDBC drive message

K: Utility-related message (statistics analysis utility or database condition analysis utility)

L: Utility-related message (database load utility or database reorganization utility)

M: MIB-related message

N: Utility-related message (optimizing information collection utility)

O: OS library message

R: Utility-related message (database recovery utility)

S: System manager message

T: Updatable online reorganization messages

U: Utility-related message (any utility)

W: HiRDB External Data Access-related messages

X: Utility-related message (environment definition)

Y: Plug-in related message

Z: Client message

n₁ to n₅: Message number

i: Message severity code:

E: Error message (indicates that the error disabled a function)

W: Warning message (indicates a warning concerning resource utilization status, etc., or indicates that a command specification error was detected but processing continued using the default value)

I: Information message (indicates an operating status that does not apply to E or W)

Q: Response request message (indicates that the system is waiting for the user's response to the displayed message)

Y: Message output destination

If a message has multiple output destinations, all the destinations to which output may be directed are shown, separated by the plus sign (+). "L" denotes output to the standard output device when the pdcat command or the real-time output function is used.

KFPJ messages are collected into getMessage( ), which is an SQLException object of JDBC driver.

A: SQLCA (SQL communication area)

D: Message dialog

E: Standard error output

J: JP1 event database^#1

L: Message log file and event log (in UNIX, syslogfile)^#2

R: Error log file

S: Standard output

#1

This is output when the system is linked to JP1.

#2

In the following situations, either no message is output or a message is output to the event log in the host where the message output source unit is located (in UNIX, to syslogfile).

• When an error occurs on a single server or on a unit with a system manager
• After abnormal termination and before restart of the message log server
• When a standby system is used
  

  Note

  Message KFPA, which is output when any of the utilities listed below is executed, is not output to the destination listed in the message. In these cases, the destination for message KFPA will be (E+L).

  • Database load utility
  • Database reorganization utility
  • Rebalancing utility

TYPEx:

Message KFPJ can include two types of messages sharing the same message ID: Type2 JDBC driver messages and Type4 JDBC driver messages. If a message contains both Type2 and Type4 messages, both messages are listed. When two types of messages exist, and only when two types exist, the messages are represented as follows so that they can be distinguished:

TYPE2: Indicates a Type2 JDBC driver message.

TYPE4: Indicates a Type4 JDBC driver message.

In a Type4 JDBC driver message, the message text can be followed by the name of the class that generated the message, and the name of the method by which the message was generated, in the following format:

 
KFPxn1n2n3n4n5-i message-text [aa....aa.bb....bb]
 

• aa....aa: Name of the class that generated the message
• bb....bb: Name of the method by which the message was output

The message text explains the message or event, as well as embedded characters.

The following notations are used in message text:

{ }: Only one of the text items enclosed in braces is displayed; the text items are delimited by the vertical bar (|).

Example: {authorization-identifier |password}

[ ]: A text item enclosed in square brackets may not be displayed.

The following shows the relationships between message IDs and the SQLCODE contents in the SQL Communications Area (SQLCA):

Message ID	SQLCODE
KFPA11nnn	-nnn
KFPA19nnn	-1nnn
KFPA12nnn	+nnn

• Notes on the UNIX version

For the following return code, the HiRDB system does not output a message; only the error code is returned to SQLCODE:

• SQLCODE=-849

The SQLCODE description is set at the message ID location.