7.3.1 Reporting events to JP1/Base

Events, such as the start and termination of HiRDB, can be reported to the JP1/Base 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.3.2 Managing events by JP1/IM. For details about automatic job execution using JP1/AJS3 linkage, see 7.3.3 Automatic job execution using JP1/AJS3 linkage.

For details about JP1/Base, see the manual Job Management Partner 1/Base User's Guide.

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.

(2) HiRDB events that can be sent

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

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

EventEvent ID#1MessageDetail information#2Registration timingValue of pd_jp1_event_levelExtended attribute class
12
Start0x00010C00KFPS05210-I or KFPS05219-I#3"start"After the system start completion message (KFPS05210-I or KFPS05219-I) is outputYYInformation
0x00010C80
Normal termination0x00010C01KFPS01850-I#3"end_normal"After HiRDB system shutdown (immediately before completion of HiRDB termination or immediately after output of the KFPS01850-I message)YYInformation
0x00010C81
Planned termination0x00010C01KFPS01850-I#3"end_plan"YYInformation
0x00010C81
Forced termination0x00010C01KFPS01850-I#3"end_force"YYInformation
0x00010C81
Message log output0x00010C03HiRDB messageNULLAfter message log is outputY#4Y#4Information
0x00010C83
Abnormal termination0x00010C02KFPS01821-ENULL
  • Upon HiRDB error termination
  • After error termination is reported to the cluster software when system switchover is used in server mode
NYError
0x00010C82
Definition change0x00010C04KFPS04666-INULLAt completion of HiRDB system normal startNYNotice
0x00010C84
RDAREA full0x00010C05KFPH00213-WNULLAt output of RDAREA-full error message (KFPH00213-W)NYWarning
0x00010C85
RDAREA expansion error0x00010C06KFPX14229-ENULLUpon pdmod (with expand specified) execution errorNYError
0x00010C86
Log file free space warning0x00010C07KFPS01160-E or KFPS01162-WNULLAt output of a system log file free-space warning messageNYWarning
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; the bottom code is for a HiRDB/Parallel Server.
#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.