Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1

[Contents][Glossary][Index][Back][Next]

14.3.16 Environment setting parameters related to communication for event/action control

When an event job or a jobnet with start conditions is executed, the event/action control manager and the event/action control agent communicate with each other. If a communication error occurs, communication is retried.

A retry interval and a maximum number of retries can be set by using the environment setting parameters for event/action control. Note that these parameters must be specified in a combination appropriate for the case.

This subsection provides examples of setting environment setting parameters that must be used in appropriate combinations.

For details about a specific environment setting parameter, see the description of that parameter.

Organization of this subsection
(1) Changing the retry interval for retries caused by a connection timeout
(2) Changing the retry interval for retries that are not caused by connection timeouts

(1) Changing the retry interval for retries caused by a connection timeout

If a connection from the manager to the agent times out when an event job or a jobnet with start conditions is executed, you can use the ClientConnectTimeout environment setting parameter to change the timeout value. Note, however, that increasing the timeout value might delay the start of other processing. In such cases, using a gradually increasing retry interval, instead of a regular retry interval, which might reduce the delay frequency.

For details about this retry process and interval, see Table 2-3 in 2.2.2(5) Notes on manager/agent system configurations in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

However, if a connection timeout is due to a temporary cause, the retry process described above takes more time, delaying the execution of an event job or jobnet with start conditions on the execution agent. If the gradually increasing retry interval is not convenient, you can also use the regular interval for retries that are caused by connection timeouts for retries that are not caused by connection timeouts.

For details about the interval for retries that are not caused by connection timeouts, see (2) Changing the retry interval for retries that are not caused by connection timeouts.

If you want retries to occur at regular, shorter intervals, set the NotificationConstantRetry environment setting parameter. If you do so, however, and the connection timeout value is large and the connection timeout status continues for a long time, the system might wait on connections more frequently, increasing the number of processing delays. For these cases, in addition to the NotificationConstantRetry environment setting parameter, use the ClientConnectTimeout environment setting parameter to adjust the connection timeout value for communication related to event jobs and jobnets with start conditions.

Table 14-43 Changing the retry interval for retries caused by a connection timeout

Definition key Environment setting parameter Explanation

  • For all scheduler services
    [{JP1_DEFAULT|logical-host}\JP1AJS2\SCHEDULER\EV\MANAGER]#
  • For a specific scheduler service
    [{JP1_DEFAULT|logical-host}\JP1AJSMANAGER\scheduler-service\EV\MANAGER]#
  • For a compatible ISAM configuration
    [{JP1_DEFAULT|logical-host}\JP1AOMMANAGER]#
 "NotificationConstantRetry"= Option ensuring that the sending of unreported information is retried at regular intervals

  • For all scheduler services
    [{JP1_DEFAULT|logical-host}\JP1AJS2\HOST\NETWORK\EVMANAGER]#
  • For a specific scheduler service
    [{JP1_DEFAULT|logical-host}\JP1AJSMANAGER\scheduler-service\NETWORK\EVMANAGER]#
 "ClientConnectTimeout"= Connection timeout value

#:
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 defining environment setting parameters, see the following:

(2) Changing the retry interval for retries that are not caused by connection timeouts

For communication between the event/action control manager and agent during execution of an event job or a jobnet with start conditions, the interval for retries not caused by connection timeouts is set by the NotificationRetryInterval environment setting parameter. Similarly, the maximum number of retries not caused by connection timeouts is set by the NotificationRetryCount environment setting parameter.

Note that if you change only the retry interval or only the number of retries, the retry period (the period during which retries can be performed) also changes. If you want to retain the retry period, you need to adjust the values of both environment parameters.

For example, if you change the retry interval to 15 seconds, which is half the default value, the number of retries to preserve the retry period is 5,760, which is twice the default value.

For a network error that is caused by a connection timeout, adjust the settings described in (1) Changing the retry interval for retries caused by a connection timeout.

Table 14-44 Environment setting parameters for changing the interval and number of retries that are not caused by connection timeouts for communication

Definition key Environment setting parameter Explanation

Communication from the manager host to the agent host:
  • For all scheduler services
    [{JP1_DEFAULT|logical-host}\JP1AJS2\SCHEDULER\EV\MANAGER]#
  • For a specific scheduler service
    [{JP1_DEFAULT|logical-host}\JP1AJSMANAGER\scheduler-service\EV\MANAGER]#
  • For a compatible ISAM configuration
    [{JP1_DEFAULT|logical-host}\JP1AOMMANAGER]#

Communication from the agent host to the manager host:
[{JP1_DEFAULT|logical-host}\JP1AOMAGENT]#
 "NotificationRetryInterval"= Interval for retrying the sending of unreported information
"NotificationRetryCount"= Maximum number of retries for sending unreported information

#:
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 defining the environment setting parameters for communication from the manager host to the agent host, see the following:

For details about defining the environment setting parameters for communication from the agent host to the manager host, see the following:

[Contents][Back][Next]

[Trademarks]

Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.