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/AJS2 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/AJS2 linkage, see 7.4.3 Automatic job execution using JP1/AJS2 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

Table 7-5 lists and describes the HiRDB events that can be sent to JP1/Base.

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

Event	Event ID¹	Message	Detail information²	Registration timing	Value of pd_jp1_event_level
Event	Event ID¹	Message	Detail information²	Registration timing	1	2
Start	0x00010C00	KFPS05210-I or KFPS05219-I³	"start"	After the system start completion message (KFPS05210-I or KFPS05219-I) is output	Y	Y
Start	0x00010C80	KFPS05210-I or KFPS05219-I³	"start"		Y	Y
Normal termination	0x00010C01	KFPS01850-I³	"end_normal"	After termination of system service (immediately before completion of HiRDB termination or immediately after output of the KFPS01850-I message)	Y	Y
Normal termination	0x00010C81	KFPS01850-I³	"end_normal"		Y	Y
Planned termination	0x00010C01	KFPS01850-I³	"end_plan"		Y	Y
Planned termination	0x00010C81	KFPS01850-I³	"end_plan"		Y	Y
Forced termination	0x00010C01	KFPS01850-I³	"end_force"		Y	Y
Forced termination	0x00010C81	KFPS01850-I³	"end_force"		Y	Y
Message log output	0x00010C03	HiRDB message	NULL	After message log is output	Y⁴	Y⁴
Message log output	0x00010C83	HiRDB message	NULL	After message log is output	Y⁴	Y⁴
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
Abnormal termination	0x00010C82	KFPS01821-E	NULL		N	Y
Definition change	0x00010C04	KFPS04666-I	NULL	At completion of HiRDB system normal start	N	Y
Definition change	0x00010C84	KFPS04666-I	NULL	At completion of HiRDB system normal start	N	Y
RDAREA full	0x00010C05	KFPH00213-W	NULL	At output of RDAREA-full error message (KFPH00213-W)	N	Y
RDAREA full	0x00010C85	KFPH00213-W	NULL	At output of RDAREA-full error message (KFPH00213-W)	N	Y
RDAREA expansion error	0x00010C06	KFPX14229-E	NULL	Upon pdmod (with expand specified) execution error	N	Y
RDAREA expansion error	0x00010C86	KFPX14229-E	NULL	Upon pdmod (with expand specified) execution error	N	Y
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
Log file free space warning	0x00010C87	KFPS01160-E or KFPS01162-W	NULL	At output of a system log file free-space warning message	N	Y

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

¹ The top code is for a HiRDB/Single Server; the bottom code is for a HiRDB/Parallel Server.

² 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

³ When pd_jp1_event_level=1 is specified, the message is null.

⁴ When pd_jp1_event_msg_out=N is specified, the event is not sent.

7.4.1 Reporting events to JP1/Base

(1) Sending event notice

(2) HiRDB events that can be sent