7.9.5 Changing to FQDN host names for event jobs in a DNS environment

The following describes the settings you need to change to use host names in Fully Qualified Domain Name (FQDN) format as the execution agent names for event jobs being used in a DNS environment.

There is no need to perform these settings if there is no duplication of host names within the network or within different domains, or if event jobs are not used in your system.

For details about operation in a DNS environment and whether settings need to be changed, see 2.3.8 Operation in a DNS environment in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

The following figure shows the work flow for changing to operation with FQDN host names in a DNS environment.

Figure 7‒23: Work flow for changing to FQDN host names

To convert the manager host name sent from the manager to the agents into FQDN format in a DNS environment, follow the steps below.

Kill all active event jobs and jobnets with start conditions.
Stop the JP1/AJS3 service on the manager host.

In Windows:

From the Windows Control Panel, select Administrative Tools and then Services, and stop the following service:

JP1/AJS3 service

In UNIX:

Execute the following commands to check that all processes have stopped.

Before you execute the /etc/opt/jp1ajs2/jajs_stop command, make sure that the command script is edited to stop JP1/AJS3 processes automatically.

# /etc/opt/jp1ajs2/jajs_stop

# /opt/jp1ajs2/bin/jajs_spmd_status
On the manager host, execute the following command to set the environment setting parameter:
```
jajs_config -k "[{JP1_DEFAULT|logical-host-name}\JP1AJS2\SCHEDULER\EV\MANAGER]" "DNSEstablish"="Y"
```
Specify Y to use FQDN host names in a DNS environment. If you replace Y with N, FQDN host names will not be used. Instead of the FQDN host name, the manager host name^#1 will be sent to the agents. The default is N.
Enable all agent hosts to resolve manager host names in FQDN format.
Enable the manager host to resolve all agent host names in FQDN format.
Restart JP1/AJS3 on the manager host.

The settings you performed in step 3 take effect.
Stop the JP1/AJS3 service on each agent host.
Execute the jpoagoec command on each agent host.

An agent host stores the name of a manager host with which the agent host communicated in the past. By running the jpoagoec -p command on the agent host, check the manager host name stored by the agent host. If the manager host name^#1 output in the results of the jpoagoec -p command is the name from before the settings were changed to the FQDN format, run the jpoagoec -d command to delete the stored manager host name^#2.

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.
Restart JP1/AJS3 on the agent host.

#1

Manager host name refers to a name that you can check as follows:

Physical host

The name that is output at execution of the hostname command on the manager host.

Logical host

In Windows:

The host name indicated by the xxxxx portion of the JP1/AJS3_xxxxx service name, which is displayed by selecting Services, or Administrative Tools and then Services, from the Control Panel on the manager host
In UNIX:

The host name that appears with the jajs_spmd process, which is displayed by executing the ps command

#2

If you start the JP1/AJS3 service on an agent host and execute an event job without first clearing the manager host name used previously, the agent host will record two host names (FQDN and non-FQDN host name) for the same manager host. If an event job is executed while JP1/AJS3 - Manager is in this state, the following problems might occur:

If the JP1/AJS3 service is restarted on the manager host while a jobnet with start conditions is being executed, monitored events that occur after the restart will be detected twice.
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 host while an event job is being executed, the same event will be incorrectly detected multiple times.

To avoid these problems, before you start the JP1/AJS3 service on an agent host, execute the jpoagoec command to clear recorded manager host names.

To Page Top