2.6.4 Troubleshooting problems related to event jobs
This subsection describes how to troubleshoot problems that are specific to event jobs.
- Organization of this subsection
(1) Condition not satisfied, although the specified host name is correct for JP1 event reception monitoring
An event server name has been specified as the host name in a JP1 event.
Check whether the event server name is the same as the name specified in the event service definition. Note that the host name in a JP1 event is case sensitive.
(2) When an event reception job is used, a condition match occurs on an unexpected event
When a JP1 event reception monitoring job, a log file monitoring job, and a Windows event log monitoring job are defined, character strings are specified for the following items:
- JP1 event reception monitoring job:
-
Event issuer user name
Event issuer group name
Event issuer host name
Message
Event details
Extended attribute (if required)
- Log file monitoring job:
-
Trap data
Data other than log information
- Windows event log monitoring job:
-
Description
Partial matching is used for the character strings specified for the above items. Check whether a partial match has occurred for the specified character string.
If you want to find an exact match, use a regular expression. For example, if you want to find an exact match of spring as the event issuing host name, specify ^spring$ in Windows.
For details about regular expressions in Windows, see the JP1/Base User's Guide. For details about regular expressions in UNIX, see the UNIX documentation.
(3) An event job fails to execute at startup
-
If the KAVT0414-E message (The request was rejected. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)) is output to the integrated trace log:
Check the KAVT0992-E message that is output to the integrated trace log on the host where the job was to be executed. If necessary, add any required IP addresses in the agent connection permission configuration file, and then execute the jajs_pmtcon command.
(4) A warning message appears while an event job is in use
Possible causes are as follows:
-
The event action control performs delivery confirmation of communication data. The messages shown below might be output at the time JP1/AJS3 starts or stops, and mean socket data delivery confirmation failed and socket data delivery confirmation time expired. However, there will be no negative effects in such cases and you can continue the operation.
Therefore, when JP1/AJS3 starts or stops, messages with the following message IDs (for example, the system failed to check the arrival of socket data or the socket data arrival check exceeded the time limit) may be output. These messages do not affect the operation. Continue the operation.
-
KAVT0268-W
-
KAVT0612-W
-
KAVT0613-W
-
-
The event/action control of JP1/AJS3 - Manager retains event data that is detected by an event job that has been registered for execution, even when the JP1/AJS3 service is not running. However, when the number of event data retained exceeds a certain value, the detected event data information will be discarded. In that case, the following messages indicating event data disposal will be output.
-
KAVT0980-W
-
KAVT0981-W
For details about the above messages, see 4. Messages beginning with KAVT (Messages about the event/action control) in the manual JP1/Automatic Job Management System 3 Messages.
-