3.2.1 List of JP1 events issued by JP1/IM - Manager
Event ID |
When issued |
Message |
Function that issues the event |
---|---|---|---|
00002010 |
When an action's execution time exceeds the action delay monitoring time. |
KAVB4400-E The run time of an action for an event exceeded the action delay monitoring time.(Event_ID=event-ID, SEQNO=serial-number-in-event-database, Execution Host=action-execution-host, Action Serial Number=action-serial-number) Delay monitoring notifications will not be sent until suppression of the function for sending notifications to the action delay monitor is canceled. |
Automatic Action Service |
00002011 |
When an action is placed in Fail or Error status while the action's status is being monitored. |
KAVB4402-E An event status is abnormal.(event ID = event-ID, event serial number = serial-number-in-event-database, execution host = action-execution-host, action serial number = action-serial-number) Status monitoring notifications will not be sent until suppression of the function for sending notifications to the action status monitor is canceled |
Automatic Action Service |
00002012 |
When the health check function detects an error. |
KAVB8060-E An abnormality was detected in function-name. (host name = host-name, process name = process-name, process ID = process-ID) : maintenance-information |
|
00002013#1 |
When the health check function detects an error. |
KAVB8062-E An abnormality was detected in function-name. (host name = host-name, process name = process-name) : maintenance-information |
Event Console Service |
00002014#2 |
When the health check function detects error recovery. |
KAVB8061-I function-name has been recovered. (host name = host-name, process name = process-name, process ID = process-ID) : maintenance-information |
|
00002015 |
When suppression of the function for sending notification to the action delay monitor is released. |
KAVB4401-I Suppression of the function for sending notifications to the action delay monitor was canceled. |
Automatic Action Service |
00002016 |
When suppression of the function for sending notification to the action status monitor is released. |
KAVB4403-I Suppression of the function for sending notifications to the action status monitor was canceled. |
Automatic Action Service |
00002020 |
When an action that has been placed in delayed status during action delay monitoring wraps around in the action information file. |
KAVB4404-E Although the run time of an action exceeded the action delay monitoring time, an action delay notification event could not be sent because no action information exists in the action information file.(action serial number = action-serial-number) Delay monitoring notifications will not be sent until suppression of the function for sending notifications to the action delay monitor is canceled. |
Automatic Action Service |
00002021 |
When an action that has been placed in error status during action status monitoring wraps around in the action information file. |
KAVB4405-E Although an action status is abnormal, an action state notification event could not be sent because no action information exists in the action information file. Status monitoring notifications will not be sent until suppression of the function for sending notifications to the action status monitor is canceled.: maintenance-information |
Automatic Action Service |
000020A0 |
When automated action processing terminates abnormally due to a problem that prevents processing from resuming. |
KAVB4054-E Automatic Action was terminated abnormally. (Hostname : host-name) |
Automatic Action Service |
000020A1 |
When an automated action is started by the jco_start (.model) command. The default is that this event is not issued. |
KAVB4050-I Automatic Action was started. : logical-host-name |
Automatic Action Service |
000020A2 |
When an automated action is terminated by the jco_stop (.model) command. The default is that this event is not issued. |
KAVB4051-I Automatic Action was terminated. : logical-host-name |
Automatic Action Service |
000020A3 |
When the automated action function is started by the jcachange command or by a window operation. |
KAVB4055-I The action definition file was read and the automatic action function status was changed to operating. The processing will be based on the definitions read from the subsequently received (arrival-time-of-most-recently-processed-event (YYYY/MM/DD hh:mm:ss)) events. (Definition=total-number-of-effective-definitions/total-number-of-definitions-in-file, SEQNO=serial-number-of-most-recently-processed-event) |
Event Base Service |
000020A4 |
When the status of the automated action function changes from running to standby. |
KAVB4056-I Automatic action was suspended. Automatic actions cannot be executed for the subsequently received (arrival-time-of-most-recently-processed-event (YYYY/MM/DD hh:mm:ss)) events. (SEQNO=serial-number-of-most-recently-processed-event) |
Event Base Service |
000020A5 |
When setting of locale information by Automatic Action Service fails. |
KAVB4909-E An attempt to set locale information has failed. |
Automatic Action Service |
000020A6 |
When setting of locale information by the Event Base Service process fails. |
KAVB4909-E An attempt to set locale information has failed. |
Event Base Service |
000020E0 |
When execution of an action starts. |
KAVB4430-I Execution of the action for an event was requested.(Event_ID=event-ID, SEQNO=serial-number-in-event-database) |
Automatic Action Service |
000020E1 |
When execution of an action is completed. |
KAVB4431-I Execution of the action for an event ended normally.(EVENT_ID=event-ID, SEQNO=serial-number-in-event-database, Return_code=termination-code) |
Automatic Action Service |
000020E2 |
When an automated action or an action under command control is placed in abnormal status. |
KAVB4432-E Automatic action or command control of the action for an event ended abnormally.(EVENT_ID=event-ID, SEQNO=serial-number-in-event-database) |
Automatic Action Service |
000020E3#3 |
When an action execution request for an action status notification event is registered. |
KAVB4433-I Execution of the action for an action state notification event was requested.(Event_ID=event-ID, SEQNO=serial-number-in-event-database) |
Automatic Action Service |
000020E4#3 |
When an action for an action status notification event terminates. |
KAVB4434-I Execution of the action for an action state notification event ended normally.(EVENT_ID=event-ID, SEQNO=serial-number-in-event-database, Return_code=termination-code) |
Automatic Action Service |
000020E5#3 |
When an automated action or an action under command control for an action status notification event is placed in abnormal status. |
KAVB4435-E Automatic action or command control of the action for an action state notification event ended abnormally.(EVENT_ID=event-ID, SEQNO=serial-number-in-event-database) |
Automatic Action Service |
000020E6#3 |
When the jcocmddef command has been set to provide notification of execution requests, but issuance of the action status notification event (000020E0 or 000020E3) for an execution request fails because the action information file has wrapped around. (Event level: Warning). |
KAVB4436-W Although Execution of the action for an event was requested, an action state notification event could not be sent because no action information exists in the action information file. : maintenance-information |
Automatic Action Service |
000020E7#3 |
When the jcocmddef command has been set to provide notification of command execution terminations, but issuance of the action status notification event (000020E1 or 000020E4) for an execution termination fails because the action information file has wrapped around. (Event level: Warning). |
KAVB4437-W Although Execution of the action for an event ended normally, an action state notification event could not be sent because no action information exists in the action information file. : maintenance-information |
Automatic Action Service |
000020E8#3 |
When the jcocmddef command has been set to provide notifications of abnormal command terminations, but issuance of the action status notification event (000020E2 or 000020E5) for an abnormal termination fails because the action information file has wrapped around. (Event level: Error). |
KAVB4438-E Although automatic action or command control of the action for an event ended abnormally, an action state notification event could not be sent because no action information exists in the action information file. : maintenance-information |
Automatic Action Service |
00003F01#1 |
When no more events can be displayed because there are no events to be acquired from the event buffer at the connected host. |
KAVB1513-W Cannot display some event(S). There were no events to obtain from the event buffer on the connecting host. All the events except the above will be displayed. To search for an event which was not displayed, specify the search conditions in the event search condition settings dialog as follows: (1) In "Search host", specify the name of the connecting host. (2) In "Registered timeframe", specify the times when the events before and after this event were registered. Check to see if the following conditions are met when this event appears frequently. (1) The "Interval" value that was set for "Automatic refresh" in the Preferences window is too long. (2) The "Num. of events to acquire at update" value that was set in the Preferences window is too small. (3) The "Event buffer" value for the Manager that was set in the System Environment Settings window is too small. |
Event Console Service |
00003F02#1 |
When the event is not found in the event buffer on the connected host, and the event cannot be displayed either on the Monitor Events page or the Severe Events page, displays the event you want to obtain on the applicable page. To display it on the Severe Events page, forcibly treat the event as a severe event. |
KAVB1540-W Cannot display some event(s). (page = page). There were no events to obtain from the event buffer on the connecting host. All the events except the above will be displayed. To search for an event which was not displayed, specify the search conditions in the event search condition settings dialog as follows: (1) In "Search host", specify the name of the connecting host. (2) In "Registered timeframe", specify the times when the events before and after this event were registered. Check to see if the following conditions are met when this event appears frequently. (1) The "Interval" value that was set for "Automatic refresh" in the Preferences window is too long. (2) The "Num. of events to acquire at update" value that was set in the Preferences window is too small. (3) The "Event buffer" value for the Manager that was set in the System Environment Settings window is too small. |
Event Console Service |
00003F03#1 |
When an error occurs while events are being acquired from Event Service. |
KAVB1516-W An error occurred in acquiring an event from the event service. Cannot recover the error after attempting the number of retries specified in the system profile. No more events will be displayed from now on due to this error. Please check if the event service is running or not. If not, recover the error by re-executing the manager after starting the event service. |
Event Console Service |
00003F04#1 |
When an attempt is made to search for events using a condition that is not supported for the Event Service of JP1/Base version 06-00 (such as Is contained, Is not contained, Regular expression, or specification of multiple action statuses) or JP1/Base version 06-51 (such as Regular expression). |
KAVB1527-E A condition that cannot be received by the search host is included. |
Event Console Service |
00003F05#1 |
When the filter length is found to exceed Event Service's maximum value during event search processing. |
KAVB0246-E The filter condition exceeds the maximum length. (Maximum length:maximum-length) |
Event Console Service |
00003F06#1 |
When a specified regular expression is found to be invalid during event search processing. |
KAVB0248-E The settings for a regular expression is incorrect. |
Event Console Service |
00003F07#1 |
When the connection between Event Base Service and Event Service is lost. |
KAVB4764-W An error occurred in acquiring an event from the event service. Please check if the event service is running or not. If not, recover the error by starting the event service. |
Event Base Service |
00003F08#1 |
When an attempt is made to execute an event search with an exclusion-condition specified, but the search host's JP1/Base version is 08-11 or earlier. |
KAVB0251-E The search cannot be performed for the specified condition because the search host's JP1/Base does not support the exclusion condition. |
Event Console Service |
00003F11 |
When the status of a JP1 event action is changed by an operation in one of the following windows or by entering the following command:
|
KAVB1577-I A status operation was performed. (user who performed the operation = JP1-user, event ID = event-ID, status before operation = status-before-operation, status after operation = status-after-operation) |
Event Console Service |
00003F13#4 |
When a message is issued that provides notification that an event acquisition filter condition of JP1/IM - Manager has been changed in the System Environment Settings window or the Event Acquisition Conditions List window, or by entry of the jcochfilter command. |
KAVB4014-I The event acquisition filter definition file was read. The read definitions will be used for processing from the next received event. (filter name = filter-name, last received event = arrival-time, serial number in event DB = serial-number-in-event-DB) |
Event Base Service |
Event ID specified in the SUCCESS_EVENT parameter in the correlation event generation definition file |
When a specified correlation event generation condition results in success during correlation event generation processing. |
Message specified in the FAIL_EVENT parameter in the correlation event generation definition file |
Correlation event generation function |
Event ID specified in the FAIL_EVENT parameter in the correlation event generation definition file |
When a specified correlation event generation condition results in failure during correlation event generation processing. |
Message specified in the SUCCESS_EVENT parameter in the correlation event generation definition file |
Correlation event generation function |
00003F15 |
When the integrated monitoring database is enabled and a message is sent providing notification that the severe event definition of JP1/IM - Manager (Central Console) has been changed from the Severe Event Definitions window. |
KAVB1669-I The severe event definition file has been read. Next, processing will be performed using the definition read from the acquired event. (Event acquired at the end:Arrival time = arrival-time-of-the-event-acquired-at-the-end, serial number in event DB = serial-number-in-event-database-of-the-event-acquired-at-the-end) |
Event Base Service |
00003F16#1 |
When an error occurs while events are being acquired from the integrated monitoring database. |
KAVB1671-W An error occurred in acquiring an event from the integrated monitoring database. Cannot recover the error after attempting the number of retries specified in the system profile. No more events will be displayed from now on due to this error. |
Event Console Service |
00003F17#4 |
When a message is issued providing notification that additional common exclusion-conditions have been registered from JP1/IM - View. |
KAVB1150-I An additional common exclusion conditions group was registered. (common exclusion conditions group ID = common-exclusion-conditions-group-ID, common exclude conditions group name = common-exclude-conditions-group-name, registering user = user-name) |
Event Base Service |
00003F20#4 |
When a message is issued providing notification that an event acquisition filter condition of JP1/IM - Manager (Event Generation Service) has been changed in the System Environment Settings window or the Event Acquisition Conditions List window, or by entry of the jcochfilter command. |
KAJV2179-I The event acquisition filter definition file was read. The read definitions will be used for processing from the next received event. (filter name = filter-name, last received event = arrival-time, serial number in event DB = serial-number-in-event-database) |
Event Generation Service |
00003F21 |
When a message is issued providing notification that a correlation event generation definition has been updated by the jcoegschange command. |
KAJV2242-I The correlation event generation definition file has been read, and the definitions for the correlation event generation function have been updated. (file name = file-name) |
Event Generation Service |
00003F22 |
When the setting for regular expressions used for JP1/Base at JP1/IM - Manager startup is not extended regular expressions, and the operating mode of the common exclusion-conditions group for JP1/IM - Manager is set to extended mode |
KAVB4712-W The event base service cannot use common exclusion condition groups (extended) because a regular expression used by JP1/Base is not extended. The event base service will start without any common exclusion condition groups (extended) being set. |
Event Console Service |
00003F23 |
When the setting for regular expressions used for JP1/Base at JP1/IM - Manager startup is not extended regular expressions, and the operating mode of the common exclusion-conditions group for JP1/IM - Manager is set to extended mode |
KAJV2502-W The correlation event issuing service cannot use common exclusion condition groups (extended) because the regular expressions used by JP1/Base are not extended. The correlation event issuing service will start without any common exclusion condition groups (extended) being set. |
Event Correlation Feature |
00003F25 |
When a message is issued providing notification that correlation event generation processing has been restarted by the jcoegsstart command. |
KAJV2243-I The correlation event generation function has been restarted. |
Event Generation Service |
00003F26 |
When a message is issued providing notification that correlation event generation processing has been terminated by the jcoegsstop command without stopping the Event Generation Service. |
KAJV2234-I The correlation event generation function has stopped. |
Event Generation Service |
00003F28 |
When the number of JP1 event sets issued by the Event Generation Service exceeds the maximum value (20,000 sets). |
KAJV2322-W A JP1 event (event ID = event-ID, serial number in the event database = serial-number-in-event-database) could not be correlated because the number of correlated JP1 event pairs has reached the upper limit (20,000). |
Event Generation Service |
00003F31#4 |
When a message is issued providing notification that additional common exclusion-conditions have been registered from JP1/IM - View |
KAJV2188-I An additional common exclusion conditions group was registered. (common exclusion conditions group ID = common-exclusion-conditions-group-ID, common exclude conditions group name = common-exclude-conditions-group-name, registering user = user-name) |
Event Generation Service |
00003F41 |
When more response-waiting events than the maximum that can be accumulated have been issued. |
KAVB0551-E The number of accumulated response-waiting events on the manager exceeded the maximum (2000). |
Event Console Service |
00003F42 |
When response-waiting data for the file for accumulated response-waiting events cannot be read. |
KAVB1816-W A response-waiting event could not be displayed. To search for the event, specify the search conditions in the dialog box for setting the event search conditions as follows: (1) As the host to be searched for, specify the name of the connected host. (2) As the response-waiting event, specify the target event. (3) As the arrival timeframe, specify the times when the events before and after this event arrived. |
Event Console Service |
00003F51 |
When events are deleted from the integrated monitoring database. |
KAVB1841-I The events from deletion-target-start-date-and-time to deletion-target-end-date-and-time were deleted from the integrated monitoring database. |
Integrated monitoring database |
00003F52 |
When the number of events on which an output-and-save operation has not been performed exceeds the deletion warning position. |
KAVB1842-W Events not output for preservation have exceeded the deletion warning level (deletion-warning-level%). |
Output-and-save function |
00003F53#1 |
When an error occurs while events are being registered into the integrated monitoring database. |
KAVB1832-E An error occur while attempting to register an event into the integrated monitoring database. The system will retry registering the event. (detailed information = detailed-information) |
Event Base Service |
00003F54 |
When an event registration error that occurred in the integrated monitoring database is recovered. |
KAVB1833-I An error occur while attempting to register an event into the integrated monitoring database. However, after several retries, the event was registered into the database. The event base service is restarting event acquisition. |
Event Base Service |
00003F56#4 |
When an additional repetition event condition has been registered (added). |
KAVB4673-I A repeated event condition was registered. (repeated event condition name = repeated-event-condition-name, registering user = user-name) |
Repeated event monitoring suppression function |
00003F57#4 |
When the Apply button in the List of Repeated Event Conditions is clicked. |
KAVB4674-I The definition file for the repeated event condition was updated. Next, processing will be performed using the definition read from the received event. (arrival time of the last received event = arrival-time-of-the-last-received-event, serial number in the event database = serial-number-in-the-event-database) |
Repeated event monitoring suppression function |
00003F58 |
When suppression of the repeated event monitoring suppression function starts. |
KAVB4676-I Suppression of repeated events that match the repeated event condition (repeated-event-condition-name) has started. (arrival time of the first suppressed event = arrival-time-of-the-first-suppressed-event, event database serial number of the first suppressed event = event-database-serial-number-of-the-first-suppressed-event) |
Repeated event monitoring suppression function |
00003F59 |
When suppression of the repeated event monitoring suppression function ends. |
KAVB4677-I Suppression of repeated events that match the repeated event condition (repeated-event-condition-name) has ended. (arrival time of the suppressed event = arrival-time-of-the-first-suppressed-event(YYYY/MM/DD HH:MM:SS) - arrival-time-of-the-last-suppressed-event(YYYY/MM/DD HH:MM:SS), event database serial number of the suppressed event = event-database-serial-number-of-the-first-suppressed-event - event-database-serial-number-of-the-last-suppressed-event) |
Repeated event monitoring suppression function |
00003F60 |
When suppression of monitoring repeated events has ended |
KAVB4678-I Suppression of repeated events that match the repeated event condition (repeated-event-condition-name) has terminated. (arrival time of the suppressed event = arrival-time-of-the-first-suppressed-event(YYYY/MM/DD HH:MM:SS) - arrival-time-of-the-last-suppressed-event(YYYY/MM/DD HH:MM:SS), event database serial number of the suppressed event = event-database-serial-number-of-the-first-suppressed-event - event-database-serial-number-of-the-last-suppressed-event) |
Repeated event monitoring suppression function |
00003F61 |
When a severity changing definition has been applied and jco_spmd_reload is executed. |
KAVB4600-I The severity change definition has been read. Next, processing will be performed using the definition read from the received event. (arrival time of the last received event = arrival-time, serial number in the event database = serial-number-in-event-database) |
Event Base Service |
00003F63 |
When the event source host mapping definition is applied. When jco_spmd_reload is executed. |
KAVB4650-I An event-source-host mapping definition was read. Processing will be performed by the definition read from the next received event. (last received event: reception time = reception-time, event database serial number = event-database-serial-number) |
Event source host mapping feature |
00003F64 |
When a business group is updated |
KAVB8453-I The business group was updated. Processing will be performed from the next-received event. (last received event: reception time = reception-time, event database serial number = event-database-serial-number) |
Restriction on referencing and operating business groups |
00003F65 |
When suppression of monitoring repeated events is regarded as continued |
KAVB4679-I Suppression of repeated events that match the repeated event condition (repeated-event-condition-name) will continue. (arrival time of the suppressed event = arrival-time-of-the-first-suppressed-event(YYYY/MM/DD HH:MM:SS) - arrival-time-of-the-last-suppressed-event(YYYY/MM/DD HH:MM:SS), event database serial number of the suppressed event = event-database-serial-number-of-the-first-suppressed-event - event-database-serial-number-of-the-last-suppressed-event) |
Repeated event monitoring suppression function |
00003F68 |
When a business group is updated |
KAVB8454-W The business group could not be updated. (cause = cause) |
Restriction on referencing and operating business groups |
00003F69 |
When a business group is updated |
KAVB8456-E The business group could not be updated. (cause = cause) |
Restriction on referencing and operating business groups |
00003F6A |
When a display message change definition is applied. When jco_spmd_reload is executed. |
KAVB4623-I The display message change definition has been read. Next, processing will be performed using the definition read from the received event. (arrival time of the last received event = arrival-time, serial number in the event database = event-database-serial-number) |
Display message change function |
00003F71 |
When the additional severity changing definition is registered |
KAVB4802-I A severity change definition was registered. (severity change definition name = severity-change-definition-name, registered user = user-name) |
Severity change function of events |
00003F76 |
When an additional display message change definition is registered |
KAVB4803-I A display message change definition was registered. (display message change definition name = display-message-change-definition-name, registering user = user-name) |
Display message change function |
00003F77 |
When a definition file for extended event attributes is reloaded |
KAVB5800-I The definition file for extended event attributes was read in to JP1/IM - Manager. |
Function for displaying and specifying program-specific extended attributes |
00003F78 |
When a definition file for extended event attributes is reloaded, but some of the definition file fails to reload |
KAVB5804-E An attempt to read the definition file for extended event attributes failed because part of the definition file for extended event attributes could not be read. |
Function for displaying and specifying program-specific extended attributes |
00003F7C |
When a definition file for opening monitor windows is reloaded |
KAVB1981-I The definition file for opening monitor windows was applied to JP1/IM - Manager. |
Monitor startup of linked products |
00003FA0#5 |
When command execution control receives a command execution request from the Execute Command window. |
KAVB2100-I [host-name:JP1-user-name] Command execution started. |
JP1/Base command execution |
00003FA1#5 |
When execution of a command requested from the Execute Command window is completed. |
KAVB2101-I [host-name:JP1-user-name] Command execution ended normally. |
JP1/Base command execution |
00003FA2#5 |
When it is detected that a command whose execution was requested from the Execute Command window cannot be executed for some reason. |
KAVB2102-E [host-name:JP1-user-name] Command execution ended abnormally. |
JP1/Base command execution |
00003FA3#5 |
When execution of a command was requested from the Execute Command window but the elapsed time event issuance interval for the automated action is exceeded. (The jcocmddef command is used to specify the elapsed time event issuance interval). |
KAVB2402-W [host-name]The execution time of command execution exceeded the regulation value (numeric-value sec) |
JP1/Base command execution |
00003FA5#5 |
When the number of pre-loaded automated actions reaches a threshold value (if a threshold for the number of pre-loaded commands has been set by the jcocmddef command). |
KAVB2071-W In target-host-name, the number of queued commands requested from source-host-name has exceeded the threshold (xx). |
JP1/Base command execution |
00003FA6#5 |
When the number of pre-loaded automated actions becomes 0 (if a threshold for the number of pre-loaded commands has been set by the jcocmddef command). |
KAVB2072-I In target-host-name, the number of queued commands requested from source-host-name has become 0. |
JP1/Base command execution |
00003FB0 |
When the status of a monitoring node changes. |
KAVB7900-I Status of monitoring-node-name is changed status from status. |
Central Scope Service |
00003FB1 |
When the number of monitoring node status change events reaches a maximum value. |
KAVB7901-W The number of status change event for the monitored node monitoring-node-ID has reached the threshold. |
Central Scope Service |
00003FC0 |
When a remote monitoring log-file trap is unable to start monitoring a log file. |
KNAN26102-E The remote log-file trap cannot start. (Code: code, Host name: host name, Monitoring-target-name: monitoring-target-name) |
Remote monitoring feature |
00003FC1 |
When the number of retries for reading a remote monitoring log-file trap exceeds the threshold, and monitoring of the applicable log file has stopped. |
KNAN26094-E The relevant log file could not be read after the specified number of retires, so monitoring will stop. (Code: code, Host name: host-name, Monitoring-target-name: monitoring-target-name, Log file name: Log file name) |
Remote monitoring feature |
00003FC2 |
When the status of a remote monitoring log-file trap changes to abnormal. |
KNAN26095-E The relevant log file can no longer be monitored. (Code: code, Host name: host-name, Monitoring-target-name: monitoring-target-name, Log file name: Log file name) |
Remote monitoring feature |
00003FC3 |
When a remote monitoring log-file trap terminates abnormally. |
KNAN26057-E The remote log-file trap will stop due to error. (Code: code, Host name: host name, Monitoring-target-name: monitoring-target-name) |
Remote monitoring feature |
00003FC5 |
When the amount of data for a log file collected by a remote monitoring log-file trap exceeds the allowed upper limit for logs. |
KNAN26140-W The amount of data that a remote log file trap collected from the log file exceeded the limit. The log entries output from the last collection time to this collection time will not be output as JP1 events. (host name: host name, monitoring-target name: monitoring-target-name, log file name: Log file name, previous collection time: Last collection time(yyyy/MM/dd hh:mm:ss), this collection time: This collection time(yyyy/MM/dd hh:mm:ss)) |
Remote monitoring feature |
00003FC6 |
When a remote monitoring log-file trap stops as a result of executing the collection of host information on the monitored host where remote monitoring is running |
KNAN26351-E All trapping of remote log files on monitored host "monitored-host-name" will now stop. (cause = cause) |
Remote monitoring feature |
00003FC7 |
When a renamed log file (backup file) cannot be found (only when the SEQ2 format is used and the monitored host is a UNIX host) |
KNAN26350-W The backup files for the monitored log files were not found. The log entries output to the backup files between the previous collection time and the current collection time will not be output as JP1 events. (host name = monitored-host-name, monitoring target = monitoring-target-name, log file name = monitored-log-file-name, previous collection time = yyyy/MM/dd hh:mm:ss, current collection time = yyyy/MM/dd hh:mm:ss, user = user, command line that was executed = command-line-executed) |
Remote monitoring feature |
00003FC8 |
When a renamed log file (backup file) cannot be found (only when the SEQ2 format is used and the monitored host is a Windows host) |
KNAN26352-W The backup files for the monitored log files were not found. The log entries output to the backup files between the previous collection time and the current collection time will not be output as JP1 events. (host name = monitored-host-name, monitoring target = monitoring-target-name, log file name = monitored-log-file-name, previous collection time = yyyy/MM/dd hh:mm:ss, current collection time = yyyy/MM/dd hh:mm:ss, user = user) |
Remote monitoring feature |
00003FC9 |
When a remote monitoring event log trap trap stops as a result of executing the collection of host information on the monitored host where remote monitoring is running |
KNAN26353-E Trapping of remote event log files on monitored host "monitored-host-name" will now stop. (cause = cause) |
Remote monitoring feature |
00003FD0 |
When a remote monitoring event log trap is unable to start monitoring Windows events. |
KNAN26107-E The remote event-log trap cannot start. (Code: code, Host name: host name) |
Remote monitoring feature |
00003FD1 |
When the number of retries for reading an event log trap for remote monitoring exceeds the threshold, and monitoring of the applicable Windows events stops. |
KNAN26028-E Monitoring will now stop because the event log could not be read after the specified number of retries. (Code: code, Host name: host name) |
Remote monitoring feature |
00003FD2 |
When reading of an event log file is retried. |
KNAN26027-I The system will now retry reading the event log. (Code: code, Host name: host name) |
Remote monitoring feature |
00003FD3 |
When a remote monitoring event log trap terminates abnormally. |
KNAN26002-E The remote event-log trap will now stop due to error. (Code: code, Host name: host name) |
Remote monitoring feature |
00003FD4 |
When reading of an event log is successful on a retry. |
KNAN26026-I An event log can now be monitored. (Host name: host name) |
Remote monitoring feature |
00003FD5 |
When the differing-components data for an event log collected by a remote monitoring event log trap exceeds the upper limit for logs. |
KNAN26142-W The amount of data collected from the host by a remote event-log trap exceeded the limit. The event log entries that were output during the period from the previous collection time to the current collection time will not be output as JP1 events. (host name = host-name, previous collection time = previous-collection-time, current collection time = current-collection-time) |
Remote monitoring feature |
00003FD6 |
When an operation to write to the remote monitoring status retention file by the remote-monitoring log file trap fails. |
KNAN26339-W Failed to save the state of the remote log file trap when the log was collected. (host name = monitored-host-name, monitoring target = monitoring-target-name) |
Remote monitoring feature |
00003FD7 |
When an operation to write to the remote monitoring status retention file by the remote-monitoring event log trap fails. |
KNAN26340-W Failed to save the state of the remote event log trap when the log was collected. (host name = monitored-host-name) |
Remote monitoring feature |
00003FD8 |
When an operation to read the remote monitoring status retention file by the remote-monitoring log file trap fails. |
KNAN26341-W Failed to restore the remote log file trap to its state when it was last terminated. (host name = monitored-host-name, monitoring target = monitoring-target-name) |
Remote monitoring feature |
00003FD9 |
When an operation to read the remote monitoring status retention file by the remote-monitoring event log trap fails. |
KNAN26342-W Failed to restore the remote log file trap to its state when it was last terminated. (host name = monitored-host-name) |
Remote monitoring feature |
00003FDA |
When the logs output while remote monitoring was stopped cannot be collected after remote monitoring resumes (warm start) because a monitored log was changed by a remote-monitoring log file trap. |
KNAN26343-W The remote log file trap was not restored to its state when it was last terminated, because the trap was in a state where it could not be monitored. (details = detailed-information, host name = monitored-host-name, monitoring target = monitoring-target-name, log file name = log-file-name) |
Remote monitoring feature |
00003FDB |
When the system recovers from an error in the operation to write to the remote monitoring status retention file by the remote-monitoring log file trap. |
KNAN26345-I An error in the processing to save the state of the remote log file trap that occurred during log collection was resolved. (host name = monitored-host-name, monitoring target = monitoring-target-name) |
Remote monitoring feature |
00003FDC |
When the system recovers from an error in the operation to write to the remote monitoring status retention file by the remote-monitoring event log trap. |
KNAN26346-I An error in the processing to save the state of the remote event log trap that occurred during log collection was resolved. (host name = monitored-host-name, monitoring target = monitoring-target-name) |
Remote monitoring feature |
Value specified for the ACTDEF parameter#6 |
When an AP log file record is detected. |
Data content of one line in a log file |
Remote monitoring feature |
Details of 00003A71, or the event ID specified in the filter block of the remote-monitoring event log trap action-definition file#7 |
When a log message reporting a Windows event is detected. |
Event log message |
Remote monitoring feature |
00003F90#8 |
When a process terminates abnormally. |
KAVB3737-E The component-name managed-process-name terminated abnormally. |
JP1/IM - Manager process management |
00003F91#8 |
When a timeout occurs during process startup. |
KAVB3613-W A component-name timeout occurred in managed-process-name. Processing continues. |
JP1/IM - Manager process management |
00003F92#8 |
When a process that terminated abnormally restarts. |
KAVB3616-I Restart of the component-name managed-process-name has finished. |
JP1/IM - Manager process management |
00006400#9 |
When a display message change event is issued |
If the message was changed by the display message change function, the changed message is set. If the message was not changed, the message text of the original event is set. |
Issuance of a display message change event |
00003FE0 |
When the response action starts |
KAJY22023-I The response action will now start. (suggestion ID : suggestion-ID, JP1 user name : JP1-user-name, IM management node : tree-SID, action information : action-information) |
Suggestion function provided by JP1/IM - Manager (Intelligent Integrated Management Base) |
00003FE1 |
When the response action ends |
KAJY22024-I The response action has finished. (suggestion ID : suggestion-ID, JP1 user name : JP1-user-name, IM management node : tree-SID, action information : action-information) |
Suggestion function provided by JP1/IM - Manager (Intelligent Integrated Management Base) |
00003FE2 |
When the execution of the response action failed |
KAJY22025-E Execution of the response action failed. (suggestion ID : suggestion-ID, JP1 user name : JP1-user-name, cause : cause, IM management node : tree-SID, action information : action-information) |
Suggestion function provided by JP1/IM - Manager (Intelligent Integrated Management Base) |
00003FF0 |
When Status of the auto Response Action is set to "Execute control sending" |
KAJY63025-I Response Action for event. (Serial number in integrated monitoring DB = Serial number in integrated monitoring DB) was sent to JP1/IM-Manager managing Response Action Execute destination. |
Auto execution of Response Action |
00003FF1 |
When Status of Auto Response Action is set to "Queuing" |
KAJY63026-I Response Action for event. (Serial number in the integrated monitoring DB = Serial number in the integrated monitoring DB) was requested to JP1/IM agent management base. |
Auto execution of Response Action |
00003FF2 |
When Status of Auto Response Action is set to "Exit" |
KAJY63027-I Execution of Response Action for event. (Serial number in the integrated monitoring DB = Serial number in the integrated monitoring DB) has terminated. (End code = End code) |
Auto execution of Response Action |
00003FF3 |
When Status of Auto Response Action is "Fail", "Communication Failed", or "error" |
KAJY63028-E Response Action for event. (Serial number in the integrated monitoring DB = Serial number in the integrated monitoring DB) terminated abnormally. |
Auto execution of Response Action |
00003FF4 |
When Status of the auto Response Action for Response Action notification event is set to "Execution control sending" |
KAJY63029-I Response Action for Response Action Status notification event (serial number in integrated monitoring DB = serial number in integrated monitoring DB) was sent to JP1/IM-Manager managing Response Action Execute destination. |
Auto execution of Response Action |
00003FF5 |
When Status of auto Response Action for Response Action notification event is set to "Queuing" |
KAJY63030-I Response Action for Response Action Status notification event (serial number in the integrated monitoring DB = serial number in the integrated monitoring DB) was requested to JP1/IM agent management base. |
Auto execution of Response Action |
00003FF6 |
When Status of the auto Response Action for Response Action notification events is set to "Exit" |
KAJY63031-I Execute of Response Action for Response Action Status notification event (serial number in the integrated monitoring DB = serial number in the integrated monitoring DB) has terminated. (End code = End code) |
Auto execution of Response Action |
00003FF7 |
When Status of the auto Response Action for Response Action notification event is "Fail", "Communication Failed", or "Execute Failed" |
KAJY63032-E Response Action for Response Action Status notification event (serial number in integrated monitoring DB = serial number in integrated monitoring DB) terminated abnormally. |
Auto execution of Response Action |
00003FF8 |
Failed to issue Response Action notification event (queuing) |
KAJY63033-W Execution of Response Action was requested, but Response Action Status notification event cannot be issued because Response Action does not exist in Response Action results-management database. (Detailed Information : Detailed Information) |
Auto execution of Response Action |
00003FF9 |
Response Action notification event issuance failure (Execute termination) |
KAJY63034-W Execution of Response Action has terminated, but Response Action Status notification event cannot be issued because Action does not exist in Response Action results-management database. (Detailed Information : Detailed Information) |
Auto execution of Response Action |
00003FFA |
Response Action notification event issue failure (Execute failure) |
KAJY63035-E Response Action terminated abnormally, but Action Status notification event cannot be issued because there is no Action in Response Action results-management database. (Detailed Information : Detailed Information) |
Auto execution of Response Action |
00003FFB |
When the auto Response Action defi nition is loaded and auto execution of Response Action goes to the operational Status |
KAJY63023-I read Auto Response Action Definitions and set auto execution of Response Action to Operational Status. The definition read from the next received event is processed. (Number of definitions: Enable number of definitions/total number of definitions in definition, last received event: arrival time = arrival time of last processed event (YYYY/MM/DD HH:MM:SS), serial number in integrated monitoring DB = serial number in integrated monitoring DB of last processed event) |
Auto execution of Response Action |
3F80 |
When you have finished generating IM management node related information |
KAJY02073-I Generation of the information related to IM management nodes ended normally. |
Generating IM Management Node Related Information |
3F81 |
Failure to generate IM management node-related information |
KAJY02074-E Failed to generate the information related to IM management nodes. (return value = return-value, details = details) |
Generating IM Management Node Related Information |
3F82 |
When you have finished reflecting IM management node-related information |
KAJY02075-I Processing to apply the information related to IM management nodes ended normally. |
Reflecting IM Management Node Related Information |
3F83 |
Failure to propagate IM management node-related information |
KAJY02076-E Failed to apply the information related to IM management nodes. (return value = return-value, details = details) |
Reflecting IM Management Node Related Information |