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
Was the Delete job output file check box cleared on the Output file tab in the Define Jobscheduler Startup Parameters window?
Additionally, was the job output file deleted periodically?
Cause
If the Delete job output file check box is cleared, the file may remain on the disk, which may cause the security check to take a while during the startup. Accordingly, the Jobscheduler start time will become longer.
Action method
Depending on the operation, select the Delete job output file check box, or periodically delete the job output file in the following directory.
Windows
<Jobscheduler database directory>\work
UNIX
<Jobscheduler database directory>/work
Action 2
Points to check
Were there too many job net definitions?
Cause
In the initialization processing when the server starts, Jobscheduler reads all job net definition information, and schedules the scheduled start from the point when the server starts until the next day change time. If a large number of job nets are defined in one system, the job net schedule processing will take a while.
Action method
Collect linked multiple job nets that run as one job net, to reduce the number of job nets that are registered.
