Nonstop Database, HiRDB Version 9 Installation and Design Guide

[Contents][Index][Back][Next]

7.4.1 Reporting events to JP1/Base

Events, such as the start and termination of HiRDB, can be reported to the JP1/Base (JP1/System Event Service for JP1 Version 6 or earlier) that manages JP1 events. JP1/Base manages the reported HiRDB events as JP1 events. This makes it possible to use JP1/IM to manage events and to execute jobs automatically using JP1/AJS3 linkage. For details about event monitoring using JP1/IM, see 7.4.2 Managing events by JP1/IM. For details about automatic job execution using JP1/AJS3 linkage, see 7.4.3 Automatic job execution using JP1/AJS3 linkage.

For details about JP1/Base, see the JP1 manual. Because the manual name depends on the JP1 version, see the correct manual for the version you are using:

Organization of this subsection
(1) Sending event notice
(2) HiRDB events that can be sent

(1) Sending event notice

To send HiRDB events to JP1/Base, specify the following operands:

When 1 is specified in the pd_jp1_event_level operand, only the basic attributes are sent. When 2 is specified in this operand, extended attributes are also sent.

Note
In the following cases, only 1 can be specified in the pd_jp1_event_level operand; if 2 is specified, events cannot be sent:
  • Events are to be sent to JP1/System Event Service.
  • HiRDB in use is a 64-bit mode version for HP-UX.

(2) HiRDB events that can be sent

The following table shows HiRDB events that can be sent to JP1/Base.

Table 7-6 HiRDB events that can be sent to JP1/Base

Event Event ID#1 Message Detail information#2 Registration timing Value of pd_jp1_event_level Extended attribute class
1 2
Start 0x00010C00 KFPS05210-I, KFPS05219-I#3, or KFPS05260-I#5 "start" After the system start completion message (KFPS05210-I, KFPS05219-I, or KFPS05260-I) is output Y Y Information
0x00010C80
Normal termination 0x00010C01 KFPS01850-I#3 "end_normal" After HiRDB system shutdown (immediately before completion of HiRDB termination or immediately after output of the KFPS01850-I message) Y Y Information
0x00010C81
Planned termination 0x00010C01 KFPS01850-I#3 "end_plan" Y Y Information
0x00010C81
Forced termination 0x00010C01 KFPS01850-I#3 "end_force" Y Y Information
0x00010C81
Message log output 0x00010C03 HiRDB message NULL After message log is output Y#4 Y#4 Information
0x00010C83
Abnormal termination 0x00010C02 KFPS01821-E NULL
  • Upon HiRDB error termination
  • After error termination is reported to the cluster software when system switchover is used in server mode
 N Y Error
0x00010C82
Definition change 0x00010C04 KFPS04666-I NULL At completion of HiRDB system normal start N Y Notice
0x00010C84
RDAREA full 0x00010C05 KFPH00213-W NULL At output of RDAREA-full error message (KFPH00213-W) N Y Warning
0x00010C85
RDAREA expansion error 0x00010C06 KFPX14229-E NULL Upon pdmod (with expand specified) execution error N Y Error
0x00010C86
Log file free space warning 0x00010C07 KFPS01160-E or KFPS01162-W NULL At output of a system log file free-space warning message N Y Warning
0x00010C87

Legend:
NULL: Null; nothing is sent.
Y: This event is sent.
N: This event is not sent.

#1: The top code is for a HiRDB single server configuration; the bottom code is for a HiRDB parallel server configuration.

#2: The detail information is provided in text format. Following is the data format:
ssss mm...mm \0
ssss: System identifier (0-4 bytes)
mm...mm: Character string indicated in the Detail information column

#3: When pd_jp1_event_level=1 is specified, the message is null.

#4: When pd_jp1_event_msg_out=N is specified, the event is not sent.

#5: This message is displayed only when a log applicable site is started using the pdstart -1 command in cases in which the log-only synchronous method is used for Real Time SAN Replication processing.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2012, 2015, Hitachi, Ltd.