6.3.16 Settings for ensuring that a fixed manager host name is used when event jobs are executed

When an event job is executed, the event/action control manager communicates with the agent on which the job is executed. In the communication, the manager sends its own name to the agent so that the agent can distinguish the manager from other agents. The manager host name is acquired when the JP1/AJS3 service on the manager is started.

Normally, unless the host name is changed intentionally, the acquired host name never changes when the JP1/AJS3 service on the manager is restarted. However, case for alphabetic characters (upper or lower case) used in the acquired host name might change for some reason when the JP1/AJS3 service is restarted. For example, a change in the case might occur if the OS settings related to DNS name resolution are changed.

Because event job execution agents treat manager host names as being case-sensitive, a change in the case, which is equivalent to a change in the manager host name, might cause the following problems:

If the JP1/AJS3 service on the manager is restarted while a jobnet with start conditions is being executed, a duplication of monitored events might be detected after the restart.
When the option for continuing execution of active event jobs is enabled, if the JP1/AJS3 service is restarted in hot-start mode on the manager while an event job is being executed, multiple occurrences of the same event are detected.

For details about the option for continuing the execution of active event jobs, see 6.3.6 Resuming event jobs that stopped when the JP1/AJS3 service stopped.

To avoid these problems, enable the option for using a fixed manager host name (the FixedHostnameForAgent environment setting parameter). If this option is enabled, the event/action control manager always sends the host name in all lower case.

Cautionary note:

Be careful when you change the settings of the option for using a fixed manager host name while executing jobnets with start conditions or executing event jobs with the option for continuing the execution of active event jobs enabled. If you make a change, the case of the alphabetic characters of the manager host name might change.

Making such a change might cause inconsistencies in the management status of jobnets with start conditions or event jobs that have already been executed. For example, multiple jobnets might be incorrectly started for one event.

To avoid these types of problems, make sure you use the following procedure when enabling the option for using a fixed manager host name or changing the option settings:

Stop the JP1/AJS service on the agent host on which jobnets with start conditions or event jobs are being executed.
On the agent host in step 1, execute the jpoagoec command to delete the manager host name for which the option for using a fixed manager host name is to be enabled.

For details about the jpoagoec command, see jpoagoec in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.
On the manager host, enable the option for using a fixed manager host name.

For details about how to enable the option, see (1) below.
Cold-start the JP1/AJS service on the agent host in step 2.

The following describes the procedure for enabling the option.

Organization of this subsection

(1) Definition procedure
(2) Environment setting parameter

(1) Definition procedure

(a) For a standard configuration

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.

(b) For a compatible ISAM configuration

In Windows Control Panel, open the Services administrative tool, and stop the following service:
- JP1/AJS3 service
In a text editor such as Notepad, create a configuration file that defines the environment setting parameter described in (2) below.
Save the file and then execute the following command:
```
jbssetcnf configuration-file-name
```
The path of the jbssetcnf command is JP1/Base-installation-folder\bin\jbssetcnf. For details on this command, see the Job Management Partner 1/Base User's Guide.
Restart JP1/AJS3 in cold-start mode.

The contents of the configuration file are applied to the system.

To Page Top

(2) Environment setting parameter

Table 6‒57: Environment parameter for the option for using a fixed manager host name
Definition key	Environment setting parameter	Explanation
For all scheduler services `[{JP1_DEFAULT\|logical-host}\JP1AJS2\SCHEDULER\EV\MANAGER]`^# For a compatible ISAM configuration `[{JP1_DEFAULT\|logical-host}\JP1AOMMANAGER]`^#	`"FixedHostnameForAgent"=`	Option for using a fixed manager host name

#:: 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 parameters, see 2.4.2(6) FixedHostnameForAgent in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

To Page Top