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 1
Points to check
Is the message queue depleted?
Refer to "Action 16" in "4.2.2 A Job Net or Job does not Start at the Intended Time" for information on the cause and action method.
Action 2
Points to check
Is jobschprint command output stopped by the more command?
Refer to "Action 9" in "4.2.2 A Job Net or Job does not Start at the Intended Time" for information on the cause and action method.
Action 3
Points to check
Did you add time-consuming processing to the exit at completion of job nets/jobs?
Refer to "Action 12" in "4.2.2 A Job Net or Job does not Start at the Intended Time" for information on the cause and action method.
Action 4
Points to check
Are the starting and ending of job nets or jobs concentrated within a short period of time?
Cause
Jobscheduler executes the job net or job start or end processing one at a time. If the job net or job start or end processing is concentrated within a short period of time, the processing may take a while.
Action method
Examine if it is possible to distribute the scheduled start times of job nets so that processing is not concentrated.
In the Gantt Chart window or the jobschprint -n command result, the concentration of start time, end time, starts, and ends for job nets can be checked.
