Top
Systemwalker Operation Manager Troubleshooting Guide

5.4.16 The Job is Delayed and not Started, or the Start is Delayed

Applicable versions and levels

Action

Points to check

Is a character string specified that does not fall under any of the following conditions 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 any of the following is set for Default host name in the Job Net Properties window - Basic Information sheet or Request host name in the Add/Change - Job window - Standard information sheet, the job is a network job 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.