Points to be noted when you connect from HULFT in clustering environments

This section explains the points to be noted on remote hosts when HULFT in clustering environments uses the following programs and APIs to connect to remote hosts:

Table 3.1 Relevant Programs and APIs

Program or API That is Run on HULFT in Clustering Environment

Remote Host Processing That Acknowledges Connections

Send File command (utlsend.exe)

Receive

Send Request command (utlrecv.exe)

Observe

Job Execution Result Notification command (hulsndrc.exe)

Observe

Remote Job Execution command (utlrjob.exe)

Observe

Send File API (utlsend)

Receive

Send File Extension API (utlsendex)

Receive

Instant Transfer Send File API (utlsendit)

Receive

Send Request API (utlrecv)

Observe

Send Request Extension API (utlrecvex)

Observe

Job Execution Result Notification API (hulsndrc)

Observe

 

In HULFT clustering systems, Local Host Name (myhostname) can be set to the host name that corresponds to the virtual IP address of the system. This allows operation of services using the virtual IP address without requiring attention to each node.

However, if a host (in the clustering system) cannot receive host identification information from a remote host due to a system failure or other causes, the actual IP address or the actual host name of the remote host may be displayed in various logs or in the console log on the host.

 

Example:

  • Console logs of the remote host

    The actual host name of the local host (in the clustering system) is output

  • Observe log of the remote host

    If the remote host acknowledges a service request that is not registered in the Observe Definition file (HULPATH\service.dat) and generates an error, the actual host name is output.

Figure 3.1 Points to be Noted When Connecting

Note that the appearance of an IP address or actual host name does not cause abnormal behaviors of the HULFT program.

If this behavior does not affect your business, you do not have to take any action.

You can deal with this exposure in the following way:

Workaround: Editing the 'hosts' file of the remote host

For the actual IP address of each node in the 'hosts' file of the remote host, add the virtual host name (Local Host Name (myhostname) for HULFT) that corresponds to the virtual IP address.

The following shows a setting example of the 'hosts' file.

172.16.52.235  CLUSTER 
172.16.52.236  CLUSTER