6.3.7 Retrying startup notification of the event/action control agent
When an event job or a jobnet with start conditions is registered for execution from a manager host, the name of the manager host is set in JP1/AJS3 on the execution host (target host). When JP1/AJS3 starts, it notifies the event/action control manager that it has started. This notification is called the startup notification of the event/action control agent (abbreviated here to startup notification).
When the manager receives the notification, the manager communicates with the agent to synchronize the execution status of the event job (or jobnet with start conditions) running on the agent between the manager and agent.
If startup notification from the agent to the manager fails, the execution status of the event job (or jobnet with start conditions) might become inconsistent between the manager and agent. If an inconsistency occurs, the jobnet with start conditions might be displayed as a jobnet being monitored (Now monitoring status) in JP1/AJS3 - View even if the agent is no longer actually monitoring the jobnet. If a monitored event then occurs, the event will not be detected, preventing the event job from ending on the manager or the jobnet with start conditions from starting.
If the JP1/AJS3 service on the agent host will be restarted under either of the following conditions while an event job or a jobnet with start conditions is running, set an environment parameter as described in (1) below:
-
The agent restarts the JP1/AJS3 service on the agent host when the load on the overall system from programs other than JP1/AJS3 is excessive.
-
The JP1/AJS3 service on the agent host is restarted when a temporary communication error occurs on the network.
To check the manager host names set, you can use the jpoagoec command. If there are unnecessary manager hosts, use the command to delete them, and then set the environment setting parameter. For details about the jpoagoec command, see jpoagoec in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.
- Cautionary note:
-
If you set the environment setting parameter and then start the JP1/AJS3 service on the agent when unnecessary manager hosts are set on the agent, startup notification will fail for those hosts, resulting in retries. These unnecessary retries could delay the starting of an event job or a jobnet with start conditions executed from another manager as well as the detection of events.
- Organization of this subsection
(1) Definition procedure
-
In Windows Control Panel, open the Services administrative tool, and stop the following service:
-
JP1/AJS3 service
-
-
Execute the following command to set the environment setting parameter described in (2) below:
jajs_config -k definition-key "parameter-name"=value
-
Restart JP1/AJS3.
The new settings are applied.
(2) Environment setting parameter
|
Definition key |
Environment setting parameter |
Explanation |
|---|---|---|
|
[{JP1_DEFAULT|logical-host}\JP1AOMAGENT]# |
"RetryAgtStartNotification"= |
Specifies whether to enable retrying of startup notification of the event/action control agent after a notification failure. |
- #:
-
The specification of the {JP1_DEFAULT|logical-host} part depends on whether the host is a physical host or a logical host. For a physical host, specify JP1_DEFAULT. For a logical host, specify the logical host name.
For details about the definition of this environment setting parameter, see 20.6.2(24) RetryAgtStartNotification.