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 there a large number of job nets per project?
Refer to "Action 6" 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
Was the execution of the Jobscheduler command concentrated in a short time?
Action method
The execution of a command should not be concentrated in a short time.
The number of Jobscheduler command processes during the time period when the problem occurred can be checked using Task Manager [Windows versions] or the ps command [UNIX versions].
Action 3
Points to check
Is the starting and closing of job nets or jobs concentrated within a short period of time?
Refer to "Action 4" in "4.2.18 Job Nets are Not Completed".
Action 4
Points to check
Was the jobschprint command result stopped using more?
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 5
Points to check
Is the IPC resource (message queue) depleted?
Check this using the IPC command, for example. 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 6
Points to check
Is a large number of Systemwalker Operation Manager clients connected? Alternatively, did you press the F5 (refresh window) key continuously on the Systemwalker Operation Manager client?
Cause
The Systemwalker Operation Manager client refreshes the window, and loads the schedule information file of the Systemwalker Operation Manager server, periodically. If the number of connected Systemwalker Operation Manager clients is increased, the number of window refreshes increases, and a schedule information file lock occurs on the server.
Action method
Keep the number of simultaneously connected Systemwalker Operation Manager clients to a minimum. Also, do not press F5 too many times in a row on Systemwalker Operation Manager clients. Consider carefully before deciding on the number of connected clients. Note that the number of connected Systemwalker Operation Manager clients can be checked using the jobschprint -u command.
