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.
Action 1
Cause
The limit for the number of jobs that can be executed simultaneously has been reached. The job waits until the number falls below the limit (this can be specified for the entire system, or per individual queue) before being executed.
Action method
Review the limit set for the number of jobs that can be executed simultaneously.
Check the limit set for the entire system in the following window:
Max Execution Jobs in the Operating control tab of the Define Operating Information window
Check the limit set per individual queue in the following window:
Max Execution Jobs in the View Queue Status/Operate window
Additionally, consider the following operations:
Submit the job to a queue that has not reached the limit.
Reduce the number of jobs executed at the same time.
Action 2
Cause
The queue has stopped.
Action method
The job can be executed by starting the job execution queue.
Check the queue status by displaying the View Queue Status/Operate window or by submitting the qstat command. Then, to start the queue that has stopped, use the start operation on the window, or use the qstart command.
Action 3
Cause
If the version level is V5.0L20/5.1 or earlier, or Disable simultaneous execution of jobs with an identical name is selected in a version level of V5.0L30/5.2 or later, multiple jobs with the same name are not executed at the same time. The execution of a job requested later does not start until the execution of the job that was requested first completes, therefore a delay occurs. (However, in a subsystem environment, there is a control per individual subsystem, therefore multiple jobs with the same job name that is used across subsystems are executed at the same time.)
Action method
Change the job name so that multiple jobs do not have the same job name.
To execute jobs with the same job name at the same time, take one of the following actions (V5.0L20/5.1 or earlier version levels cannot be used for this):
V11.0L10/11.1 or later
Clear Disable simultaneous execution of jobs with an identical name in the Backward compatibility tab of the Define Operating Information window, which will be displayed when Operation information is clicked in the Systemwalker Operation Manager Environment Setup window.
V5.0L30/5.2 or later, V10.0L21/10.1 or earlier
Select Disable simultaneous execution of jobs with an identical name in the Options tab of the Define Operating Information window, which will be displayed when Operation information is clicked in the Systemwalker Operation Manager Environment Setup window.
To enable the definition, restart the Job Execution Control service/daemon.
Information
If the "Job Name (J)" field is not entered, the directory path name from the path name specified in "Command Name (C)" and the name except for the extension part form the job name.
Action 4
Cause
This job is trying to allocate the resource already allocated to the job that is currently being executed. The job in the queue will not be executed until the job that is currently being executed and is using the same resource completes.
Action method
Display the View Job Status/Operate window or submit the qjstat command to check jobs with an executing status, and jobs that have not been executed. Then, for each job, compare the resource definitions in Resource name in the Standard information tab of the Monitor - Job window.
