Job Management Partner 1/Base User's Guide

15.2 List of JP1 events output by JP1/Base

The following table lists the events output by JP1/Base.

Table 15-3 JP1 events output by JP1/Base

Event ID Occurrence Message

00003D00 When the event database is switched Event DB was switched from old-database-number to new-database-number.

00003D04 When the event service restart function restarts an abnormally stopped process The event service was recovered by restarting an internal function.

00003A10^#4 When a log file trap successfully connects to the event service at retry Event issuance was delayed because the system retried the log file trap.

00003A20^#4 When a log file trap cannot start log file monitoring Monitoring of the relevant log file cannot start.

00003A21^#4 When the retry count for reading application log files reaches the threshold and monitoring of the affected log file stops Monitoring will now stop because the specified number of retries was performed, but the relevant log file cannot be read.

00003A22^#4 When an application log file is in error status Monitoring of the relevant log file cannot continue.

00003A71 When a log message for a Windows event is detected Windows event-log message

00003A73 When a Windows event log failed to be acquired Acquisition of event log data failed.

00003A74 When it is possible to monitor a Windows event log An event log can now be monitored.

Event ID set in the ACTDEF parameter in the action definition file^#4 When a record of an AP log file is detected Contents of one line of log file data

00003A80 When an SNMP trap is detected NNM messages (For details, see I.5 JP1 events for SNMP trap conversion).

00003FA0^#1 When the command execution control receives an command execution request from the Execute Command window [host-name:JP1-user-name] Command execution started.

00003FA1^#1 When the command execution requested from the Execute Command window completes [host-name:JP1-user-name] Command execution ended normally.

00003FA2^#1 When command execution from the Execute Command window is not performed for some reason [host-name:JP1-user-name] Command execution ended abnormally.

00003FA3^#1 When the interval for issuing elapsed time events has been specified by the jcocmddef command. When the command execution requested from the Execute Command window or automated action is performed after the issuance interval of the elapse time event has been exceeded. [host-name] The execution time of command execution exceeded the regulation value (number sec)

00003FA5^#1 When a threshold of queued commands is specified in the jcocmddef command. When the number of queued commands has reached the threshold of the automated action In target-host-name, the number of queued commands requested from source-host-name has exceeded the threshold (xx).

00003FA6^#1 When a threshold of queued commands is specified in the jcocmddef command. When the threshold of queued commands for the automated action is specified as 0 In target-host-name, the number of queued commands requested from source-host-name has become 0.

00004700^#2 When an authentication server is blocked connection-sequence: authentication-server-name was successfully blocked.

00004701^#2 When an authentication server is unblocked connection-sequence: authentication-server-name was successfully unblocked.

00004702^#2 When all authentication servers are blocked All authentication servers are blocked.

00004720^#2 When the process ends abnormally component-name management-target-process-name has ended abnormally.

00004721^#2 When an attempt to start a process results in a timeout A component-name timeout occurred in management-target-process-name Processing continues.

00004722^#2 When an abnormally ended process is restarted Restart of the component-name management-target-process-name has finished.

00004740 When a monitored process ends abnormally function-name ended abnormally.

00004741 When a monitored process has been unable to access (update) shared memory for a set time (SEVERITY:Error) function-name has been processing for nn seconds.

00004742 When a monitored process has been unable to access (update) shared memory for a set time (SEVERITY:Warning) function-name has been processing for nn seconds. After passes of mm seconds, becomes error condition.

00004743 When a monitored process that was unable to access (update) shared memory for a set time has recovered function-name has a normal status.

00004747 When the health check function ends abnormally The health check function stopped because an error occurred.

00004748 When an error (service inactivity) is detected during monitoring of a remote host Monitoring notification cannot be performed at host-name because service-name is not functioning.

00004749 When an error (host unreachable) is detected during monitoring of a remote host Monitoring cannot be performed because a connection with host-name cannot be established.

0000474A When remote host monitoring can be resumed host-name can now be monitored.

0000474B When the shared memory is inaccessible The shared memory is locked.

00002102^#3 In UNIX, a JP1 event is output in one of the following cases:

When the event service starts while the JP1/SES compatibility function is enabled

When connected from the JP1/SES or JP1/AJS event service on a remote host

None

00002103^#3 In UNIX, a JP1 event is output in one of the following cases:

When the event service starts while the JP1/SES compatibility function is enabled

When connected from the JP1/SES or JP1/AJS event service on a remote host

When connected to the JP1/SES or JP1/AJS event service on a remote host

In Windows, a JP1 event is output in one of the following cases:

When connected from the JP1/SES or JP1/AJS event service on a remote host

When connected to the JP1/SES or JP1/AJS event service on a remote host

None

00002104^#3 In UNIX, a JP1 event is output in one of the following cases:

When the event service stops while the JP1/SES compatibility function is enabled

When the JP1/SES or JP1/AJS event service stops on the remote host that is connected to

Function name of the process

00010B7F^#3 In Windows or UNIX, when connected from the JP1/SES or JP1/AJS event service on a remote host None

00004780 When a request to start execution of the action is accepted, or when the JP1 event (action start event) is registered An action execution start request was accepted. (action-execution-information)

00004781 When command execution completed and the JP1 event (action end event) is registered An action has completed. (action-execution-information)

00004782 When command execution is not completed and the JP1 event (action end event (not executable) is registered An action ended without being executed. (action-execution-information)

00004783 When command execution is canceled and the JP1 event (action end event (cancellation)) is registered An action ended because it was cancelled. (action-execution-information)

#1: This JP1 event is issued only when the jcocmddef command was used when specifying JP1/IM - Manager. For details on the settings, see jcocmddef in 13. Commands.

#2: Issued only when you have configured JP1 events to be issued upon a change in the blocked status of an authentication server or upon the abnormal end of a process. For details on how to issue a JP1 event indicating the blocked status of the authentication server or abnormal process status, see 2.4.2(2) Detecting process termination and authentication server switching.

#3: JP1 events for the JP1/SES compatibility function have no severity specified. However, you do not need to take action for these indications, because they are equivalent to the Information severity level.

#4: The log file trap or JP1/AJS log monitoring job issues the event.

Event ID	Occurrence	Message
00003D00	When the event database is switched	Event DB was switched from old-database-number to new-database-number.
00003D04	When the event service restart function restarts an abnormally stopped process	The event service was recovered by restarting an internal function.
00003A10^#4	When a log file trap successfully connects to the event service at retry	Event issuance was delayed because the system retried the log file trap.
00003A20^#4	When a log file trap cannot start log file monitoring	Monitoring of the relevant log file cannot start.
00003A21^#4	When the retry count for reading application log files reaches the threshold and monitoring of the affected log file stops	Monitoring will now stop because the specified number of retries was performed, but the relevant log file cannot be read.
00003A22^#4	When an application log file is in error status	Monitoring of the relevant log file cannot continue.
00003A71	When a log message for a Windows event is detected	Windows event-log message
00003A73	When a Windows event log failed to be acquired	Acquisition of event log data failed.
00003A74	When it is possible to monitor a Windows event log	An event log can now be monitored.
Event ID set in the ACTDEF parameter in the action definition file^#4	When a record of an AP log file is detected	Contents of one line of log file data
00003A80	When an SNMP trap is detected	NNM messages (For details, see I.5 JP1 events for SNMP trap conversion).
00003FA0^#1	When the command execution control receives an command execution request from the Execute Command window	[host-name:JP1-user-name] Command execution started.
00003FA1^#1	When the command execution requested from the Execute Command window completes	[host-name:JP1-user-name] Command execution ended normally.
00003FA2^#1	When command execution from the Execute Command window is not performed for some reason	[host-name:JP1-user-name] Command execution ended abnormally.
00003FA3^#1	When the interval for issuing elapsed time events has been specified by the jcocmddef command. When the command execution requested from the Execute Command window or automated action is performed after the issuance interval of the elapse time event has been exceeded.	[host-name] The execution time of command execution exceeded the regulation value (number sec)
00003FA5^#1	When a threshold of queued commands is specified in the jcocmddef command. When the number of queued commands has reached the threshold of the automated action	In target-host-name, the number of queued commands requested from source-host-name has exceeded the threshold (xx).
00003FA6^#1	When a threshold of queued commands is specified in the jcocmddef command. When the threshold of queued commands for the automated action is specified as 0	In target-host-name, the number of queued commands requested from source-host-name has become 0.
00004700^#2	When an authentication server is blocked	connection-sequence: authentication-server-name was successfully blocked.
00004701^#2	When an authentication server is unblocked	connection-sequence: authentication-server-name was successfully unblocked.
00004702^#2	When all authentication servers are blocked	All authentication servers are blocked.
00004720^#2	When the process ends abnormally	component-name management-target-process-name has ended abnormally.
00004721^#2	When an attempt to start a process results in a timeout	A component-name timeout occurred in management-target-process-name Processing continues.
00004722^#2	When an abnormally ended process is restarted	Restart of the component-name management-target-process-name has finished.
00004740	When a monitored process ends abnormally	function-name ended abnormally.
00004741	When a monitored process has been unable to access (update) shared memory for a set time (SEVERITY:Error)	function-name has been processing for nn seconds.
00004742	When a monitored process has been unable to access (update) shared memory for a set time (SEVERITY:Warning)	function-name has been processing for nn seconds. After passes of mm seconds, becomes error condition.
00004743	When a monitored process that was unable to access (update) shared memory for a set time has recovered	function-name has a normal status.
00004747	When the health check function ends abnormally	The health check function stopped because an error occurred.
00004748	When an error (service inactivity) is detected during monitoring of a remote host	Monitoring notification cannot be performed at host-name because service-name is not functioning.
00004749	When an error (host unreachable) is detected during monitoring of a remote host	Monitoring cannot be performed because a connection with host-name cannot be established.
0000474A	When remote host monitoring can be resumed	host-name can now be monitored.
0000474B	When the shared memory is inaccessible	The shared memory is locked.
00002102^#3	In UNIX, a JP1 event is output in one of the following cases: When the event service starts while the JP1/SES compatibility function is enabled When connected from the JP1/SES or JP1/AJS event service on a remote host	None
00002103^#3	In UNIX, a JP1 event is output in one of the following cases: When the event service starts while the JP1/SES compatibility function is enabled When connected from the JP1/SES or JP1/AJS event service on a remote host When connected to the JP1/SES or JP1/AJS event service on a remote host In Windows, a JP1 event is output in one of the following cases: When connected from the JP1/SES or JP1/AJS event service on a remote host When connected to the JP1/SES or JP1/AJS event service on a remote host	None
00002104^#3	In UNIX, a JP1 event is output in one of the following cases: When the event service stops while the JP1/SES compatibility function is enabled When the JP1/SES or JP1/AJS event service stops on the remote host that is connected to	Function name of the process
00010B7F^#3	In Windows or UNIX, when connected from the JP1/SES or JP1/AJS event service on a remote host	None
00004780	When a request to start execution of the action is accepted, or when the JP1 event (action start event) is registered	An action execution start request was accepted. (action-execution-information)
00004781	When command execution completed and the JP1 event (action end event) is registered	An action has completed. (action-execution-information)
00004782	When command execution is not completed and the JP1 event (action end event (not executable) is registered	An action ended without being executed. (action-execution-information)
00004783	When command execution is canceled and the JP1 event (action end event (cancellation)) is registered	An action ended because it was cancelled. (action-execution-information)

[Contents][Back][Next]

[Trademarks]