Applicable versions and levels
Windows versions: V5.0L10 or later
Solaris versions: 5.0 or later
Linux versions: 5.2, V10.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions: 5.1 or later
AIX versions: 5.1 or later
DS versions: V20L10
Check all applicable actions below to resolve the issue.
Action1
Points to check
Has the correct schedule server IP address been obtained by resolving the name from the schedule server host name on the execution server?
Could communication be made with the schedule server using the IP address obtained by resolving the name from the schedule server host name on the execution server?
Was NAT conversion performed between the schedule server and the execution server?
Cause
The mechanism is that, after the request to start the network job is made by the schedule server to the execution server, the job runs on the execution server, and when the job ends, a completion notification is sent from the execution server to the schedule server.
The completion notification of the network job cannot be sent by the execution server in the following cases:
When the correct schedule server IP address cannot be obtained by resolving the name from the schedule server host name on the execution server
When communication could not be made with the schedule server using the IP address obtained by resolving the name from the schedule server host name on the execution server
When the schedule server IP address value is converted using NAT conversion
However, schedule server checks the job status of the execution server at fixed intervals, therefore the schedule server is able to recognize that a job has ended.
For this reason, there may actually be a delay from the end of the job on the execution server until the schedule server recognizes this.
Action method
Using the IP address obtained by resolving the name from the schedule server host name on the execution server, take action so that the connection can be made with the schedule server.
If the schedule server is in a cluster configuration, and Systemwalker Operation Manager is one of the following version levels, the problem can be resolved by registering a logical IP address on the schedule server:
Windows versions: V11.0L10/V12.0L10
Solaris versions: 11.0/12.0
Linux versions: V11.0L10/V12.0L10
When registering a logical IP address, use the following procedure to set this IP address on all schedule servers configured in the cluster system, both active and standby.
Open the Cluster settings tab of the Define Operating Information window, which will be displayed when Operation information is clicked in the Systemwalker Operation Manager Environment Setup window.
Select Register the logical IP address, and register the logical IP address of the cluster.
Save the operating information definition, and then restart the Job Execution Control service/daemon.
Information
The logical IP address is used as the recipient of the job completion notification.
By registering the logical IP address of the cluster, even if the schedule server fails over while the network job is being executed and switches to the standby server, the execution server can send the job completion notification to the schedule server.
Action 2
Points to check
Does the Systemwalker Operation Manager startup account match on the schedule server and the execution server?
Cause
If it takes a while until the network job ends, the Systemwalker Operation Manager startup account may not match on the schedule server and the execution server. In this case, the network job completion notification cannot be sent, therefore the schedule server cannot recognize that the job has ended until it checks (at fixed intervals) the status of the job on the execution server.
Action method
Unify the Systemwalker Operation Manager startup account on the schedule server and the execution server.
Refer to the notes in the following manual for information on how to change the startup account.
"Notes on the Post-installation Procedure" in the Installation Guide
Refer to the following manual for information on how to change the startup account.
V10.0L20 or later
"Changing the Startup Account" in the Installation Guide
Action 3
Points to check
Has the jmnet port number (9352) communication between the execution server and the schedule server been blocked by a firewall?
Cause
The jmnet port number (9352) communication may have been blocked by a firewall.
Action method
Configure the firewall settings so that the jmnet port number (9352) communication is possible.
