Hitachi

JP1 Version 12 JP1/Automatic Job Management System 3 Troubleshooting


2.5 Troubleshooting problems if processing of a jobnet with a start condition is delayed

In some cases, when a large number of events occur unexpectedly for a specific jobnet with a start condition, processing is delayed because large quantities of unprocessed data are stored on the event/action control manager. For example, an operation for an event job is delayed or an event job does not end quickly even if an event that matches the specified condition occurs.

In such cases, you can end the delay by deleting the information contained in the event/action control manager.

The following example shows how you can restore operational status if a system problem occurs:

  1. A large number of events occur unexpectedly for a specific jobnet with a start condition.

  2. The manager host slows down because there is too much data to be processed, causing other event jobs to be held in queues or other problems to occur.

  3. The event/action control manager outputs the KAVT0333-W message to the integrated trace log.

  4. You receive the message output in step 3, and notice that a problem has occurred on the event/action control manager.

  5. Execute the jpomanevshow command to obtain information about the agents that frequently send data, and the jobnet with a start condition.

  6. Use the information you obtain in step 5 (unit ID) and either of the following commands to identify the name of the jobnet related to the problem.

    • ajsname command

      This command outputs the unit name to the standard output file.

    • jpomanjobshow command

      This command outputs a list of event jobs being executed on the manager to the standard output file.

  7. Forcibly terminate the jobnet with a start condition identified in step 6.

    If the termination is successful, troubleshooting ends here.

  8. If you could not stop the jobnet in step 7 or could not identify the jobnet name in step 6, assume that it will be difficult to restore operational status while JP1/AJS3 is running, and stop the scheduler service.

  9. On the agent with the problem, execute the jpomanevreset command for the scheduler service you stopped in step 8, and restore the status of the event/action control manager.

  10. If you use the jpomanevreset command to continue the event job or the start condition, eliminate the cause of the problem in step 1 on the applicable agent host.

  11. Start the scheduler service you stopped in step 8.

For details about the commands, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference. For details about how to stop the scheduler service, see 7.5.2 Stopping the scheduler service in the JP1/Automatic Job Management System 3 Administration Guide.