2.6.8 Troubleshooting problems related to a flexible job executed by broadcast execution
This subsection describes how to troubleshoot problems that are related to a flexible job executed by broadcast execution.
- Organization of this subsection
(1) A flexible job executed by broadcast execution terminates abnormally
Possible causes and their remedial actions vary depending on whether broadcast execution is in Sync mode or Async mode. Take action as appropriate.
- Sync mode:
-
The action to be taken varies depending on whether the job execution results include the contents of the standard error output for each destination agent.
-
If the job execution results include the contents of the standard error output for each destination agent: A problem might have occurred on one or more of the destination agents. If a problem occurs on at least one destination agent during broadcast execution of a flexible job, the job status is judged to be Ended abnormally. Check the information output for each destination agent, and then take action as appropriate.
-
If the job execution results do not include the contents of the standard error output for each destination agent: A problem might have occurred on the relay agent (or the manager if no relay agent is used) or on the broadcast agent. Based on the output message, take action as appropriate on the relay agent (or the manager) or broadcast agent.
-
- Async mode:
-
The action to be taken varies depending on whether maintenance-information-4 in the KAVS8100-E message is the host name of a destination agent. Take action as appropriate.
-
If maintenance-information-4 in the KAVS8100-E message is the host name of a destination agent: The broadcast agent might not be able to send an execution request to the indicated destination agent. Take measures so that the broadcast agent can communicate with the destination agent indicated by maintenance-information-4.
-
If maintenance-information-4 in the KAVS8100-E message is not the host name of a destination agent: The relay agent (or the manager if no relay manager is used) might not be able to communicate with the broadcast agent. Take measures so that the relay agent or manager is able to communicate with the broadcast agent.
-
(2) Jobs are not executed on a broadcast-execution destination agent
The following shows possible causes and actions to be taken in a case where jobs are not executed on a broadcast-execution destination agent:
-
The agent is not set up as a destination agent.
On a destination agent where jobs are not executed, use the ajsfxbcstatus command to check whether the broadcast agent has been set up correctly. If not, use the ajsatsetup command to set up the broadcast agent correctly.
-
The JP1/AJS3 Autonomous Agent service is not running.
On a destination agent where jobs are not executed, check whether the JP1/AJS3 Autonomous Agent service is running. If the service is not running, start it.
-
The destination agent cannot communicate with the broadcast agent.
On a destination agent where jobs are not executed, check whether the KAVS8146-E message has been output to the integrated trace log. If the message has been output, communication with the broadcast agent did not succeed. In this case, revise the communication environment settings, such as the firewall settings.
(3) A non-existent destination agent is requested to execute a flexible job by broadcast execution
The KAVS8100-E message might be output if an attempt is made to execute a flexible job by broadcast execution on a destination agent that has been deleted, for example, as a result of scaling-in. For broadcast execution of a flexible job, if the heartbeat of a destination agent stops, a destination agent is removed from broadcast agent management 60 minutes (default value) after its heartbeat stops. Therefore, if destination agents are deleted, for example, as a result of scaling-in, execute a flexible job after 60 minutes have passed.
The time before destination agents are removed from management can be changed by using the FXBC_MANAGEDAGT_REMOVEDTIME environment setting parameter. For the FXBC_MANAGEDAGT_REMOVEDTIME environment setting parameter, see 20.9.2(7) FXBC_MANAGEDAGT_REMOVEDTIME in the JP1/Automatic Job Management System 3 Configuration Guide.