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
Action
Points to check
Has the local server IP address or host name (logical host name for the cluster server) been specified in Default host name in the Standard information tab of the Job Net Properties window, or in Request host in the Standard information tab of the Add/Change - Job window?
Cause
If the local server IP address or host name (logical host name for the cluster server) has been specified in Default host name in the Standard information tab of the Job Net Properties window, or in Request host in the Standard information tab of the Add/Change - Job window, the network job runs assuming the request has been made to the local server.
When a network job is submitted, the job is started on the schedule server and the execution server. By starting a single job twice on the local server, the concurrency limit may have been reached and the job may have Waiting status. Additionally, because of the concurrency restriction, the start of the new job may be delayed.
Action method
When executing the job on a local server, there is no need to specify Default host name in the Standard information tab of the Job Net Properties window, or Request host in the Standard information tab of the Add/Change - Job window. Do not specify anything.
