KAVS8116-E

Monitoring of the execution status terminates because the start of the flexible job could not be confirmed within the time specified for the environment setting parameter FXJOB_START_TIMEOUT.

The probable causes are as follows:

1. The start of the flexible job is delayed on the destination agent due to a heavy processing load on the destination agent.

2. The destination agent failed to report the flexible job execution result to the manager due to one of the following causes.

   • The IP address of the host that requested the execution of the flexible job cannot be resolved on the destination agent.

   • The JP1/AJS3 Autonomous Agent service on the destination agent stopped.

   • JP1/AJS3 Autonomous Agent Messenger service on the destination agent or relay agent stopped.

   • Network error

   • Routing error

   • The auto scale function stopped the server on which the flexible job was running.

   • An IPC error occurred because of insufficient resource.

3. Broadcast execution was performed for a host that was not set up as a broadcast agent in an environment in which the version of JP1/AJS3 - Agent on a relay agent or JP1/AJS3 - Manager was 11-10 or later.

4. In a broadcast execution environment in which the version of JP1/AJS3 - Manager or JP1/AJS3 - Agent on the relay agent is 11-10 or later, the broadcast agent distributed a job to hosts other than destination hosts.

5. After setup of a broadcast-execution destination agent was canceled, the ajsatsetup command was used to perform setup again by specifying an option other than -a -p. Then, broadcast execution was performed before the time set for the FXBC_MANAGEDAGT_REMOVEDTIME environment setting parameter passes.

6. In an environment in which broadcast execution is disabled, the execution host of the flexible job is not set up as a destination agent.

(S)

Terminates monitoring of the flexible job execution status, and then sets the status to Ended abnormally.

(O)

Take action appropriate for the cause of the error as follows:

1. The flexible job is still running on the destination agent even after monitoring terminated. Check the job execution status based on the log and execution result file for the destination agent. Next, if necessary, change the job status.

   In addition, check and, if necessary, revise the value specified for the environment setting parameter FXJOB_START_TIMEOUT.

2. Check the cause of the error, and then, if necessary, re-execute the flexible job.

   If you are using the auto scale function, revise the scale-in setting so that a scale-in does not occur during job execution.

3. Check the version of JP1/AJS3 - Manager or JP1/AJS3 - Agent on the destination host specified for Destination / Broadcast agent in the Define Details dialog box, and take action according to the version:

   If the version is 11-00 or earlier:

   Update the version to 11-10 or later.

   If the version is 11-10 or later:

   Use the ajsfxbcstatus command to check whether the destination host specified for Destination / Broadcast agent is set up as a broadcast agent. If the destination host is not set up as a broadcast agent, execute the ajsatsetup command with the -g option.

4. Check the version of JP1/AJS3 - Manager or JP1/AJS3 - Agent on the host on which the problem occurred, and take action according to the version:

   If the version is 11-00 or earlier:

   Update the version to 11-10 or later.

   If the version is 11-10 or later:

   Use the ajsfxbcstatus command to check whether the host on which the problem occurred is set up as a broadcast-execution destination agent. If the host is not set up as a broadcast-execution destination agent, execute the ajsatsetup command with the -a -p option.

5. After the time specified for the FXBC_MANAGEDAGT_REMOVEDTIME environment setting parameter passes, perform broadcast execution.

6. On the execution hosts of the flexible job, execute the ajsatsetup command with the -a option.