KAVU2232-E

A timeout occurred when the system was waiting for a response after sending protocol data during TCP/IP communication for job execution control. The probable causes are:

1. When the agent host sends a result file to the manager host at the end of a job, analysis takes a long time because the result file is too large.

2. When an attempt is made to execute a job with a transfer file specified, analysis takes a long time because the transfer file is too large.

3. The CPU on the manager host or agent host at the communication destination is heavily loaded. Alternatively, the system resources are insufficient.

4. Job information is being deleted on the manager host.

(S)

Cancels the requested processing.

(O)

Take one of the following actions according to the cause of the error, and then reissue the request:

1. Make sure that the result file for the job is not too large. Also, make sure that too much data will not be output even if additional writes are specified for the standard output file or standard error output file.

2. When you define the job, do not specify too large a transfer file.

3. Check the CPU load. Also see the kernel parameter settings to check the limit values of system resources.

4. Adjust the schedule to execute the job at a different time from that when job information was deleted. You must also prevent a lot of jobs from being deleted at the same time. For example, to reduce the number of jobs to be deleted, reduce the number of days for which job information is saved.

For 1 and 2 above, you can also limit the size of a file to be received in advance to prevent processing on some jobs from affecting the entire system. For details, see 6.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (for hosts under Windows), or 15.2.7 Placing restrictions on file reception in the JP1/Automatic Job Management System 3 Configuration Guide (for hosts under UNIX).