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
Are there a large number of job nets registered in the project?
Cause
If the number of job nets registered in the project increases, this will affect the processing performance of the Systemwalker Operation Manager client.
Consider the following as a guide to the number of job nets to register in the project:
Limited to up to 255 job nets.
There is no limit, however use the following as a guide to the number of job nets that can be registered.
Windows versions: Up to 300
UNIX versions: Up to 500
Also, refer to the following manuals:
V10.0L20/10.1 or later
"Limit Values for Job Scheduling" in the Technical Guide.
"Notes When Registering a Large Number of Job Nets" in the User's Guide.
V10.0L10/10.0
"Limit Values for Job Scheduling" in the Technical Guide.
Action method
Set the access rights for the project, and limit the number of projects to display. By limiting the number of projects to display, the display target job nets are reduced, so the display time may be shortened.
Action 2
Points to check
Was a large number of job nets started at one time?
Cause
If a large number of job nets were started at one time, Jobscheduler will start them one at a time. For this reason, the schedule information file is locked, and the request from the Systemwalker Operation Manager client waits until the lock is released.
Action 3
Points to check
Is the 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 4
Points to check
Is a large number of Systemwalker Operation Manager clients connected?
Did you press F5 many times in a row on the Systemwalker Operation Manager client?
Cause
The Systemwalker Operation Manager client periodically obtains job net information and refreshes the window. At that time, the schedule information file on the Systemwalker Operation Manager server is read.
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.
Also, even if F5 is pressed many times in a row on a single Systemwalker Operation Manager client, the same issue as that for a large number of connected Systemwalker Operation Manager clients occurs.
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.
Ensure to verify sufficiently before deciding on the number of connections.
Action 5
Points to check
Was the Jobscheduler database directory placed on a disk with slow access speeds?
Cause
When the Jobscheduler database directory is placed on a disk with slow access speeds, file access performance drops and may prevent Jobscheduler from demonstrating the level of performance it was designed for.
The delays in starting job nets simultaneously are particularly significant when a large number of job nets are started.
Action method
It is recommended that you distribute the disk I/O load and place the job scheduler database directory on a high-performance (high access speeds) disk.
Action 6 [UNIX versions]
Points to check
Is the message queue on the server depleted? Check this using the ipcs command.
Cause
The Jobscheduler daemon comprises multiple daemon processes, and uses the message queue (IPC resources) to operate while mutually synchronizing. The Jobscheduler daemon performs retry processing because the communication between the processes failed, however as a result, communication with the Systemwalker Operation Manager client is not possible.
Action method
Tune the message queue. Alternatively, check if there is an application that is greatly consuming the message queue.
Refer to "4.13.4 The Jobscheduler Server Processing Hangs up [UNIX Versions]" for information on message queue tuning.
Action 7
Points to check
Was processing that takes a while added for the job net/job end exit?
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 8
Points to check
Was a client machine with slow performance used?
Cause
The Jobscheduler service or daemon communicates with each connected client separately and performs processing. If even one client machine with slow performance connects, the communication with the client machine with slow performance will cause a bottleneck, and the entire operation performance may deteriorate.
Action method
If at all possible, avoid using a client machine with slow performance.
Action 9
Points to check
Was a large amount of job information or previous log information collected?
Cause
The Jobscheduler service or daemon communicates with each connected client separately and performs processing.
To display the job properties, the client receives the output information for the job from the server. When the job is executed, if a large amount of information is output in standard output/standard error output, the client will receive that large amount of data via the network. The server will experience a bottleneck in the processing to send that, and delays in sending and receiving the data to/from other client machines will occur.
Action method
Review the output information of the job and, wherever possible, minimize the job information and previous log information to be obtained.
Action 10
Points to check
Did an error occur in the connection destination server?
Cause
If the server cannot return a response to the processing request from the client because of the server stopped responding, or because the server ended abnormally during processing, the client response may not return.
Action method
Check if a problem has occurred on the server. If it has, resolve the problem, shut down the unresponsive client, and then reconnect the client window.
Also, refer to the following manual.
User's Guide - "If the Jobscheduler Function does not Respond"
