Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Administration Guide


11.2.2 Node switching caused by an error in JP1/AJS3 - Agent

The following figure shows the processing if node switching occurs in JP1/AJS3 - Agent during operation.

Figure 11‒5: Processing if node switching occurs in JP1/AJS3 - Agent

[Figure]

The flow of events in system processing is as follows:

  1. Now Running remains the status of the jobnet and the job being executed when node switching occurs.

    This status is managed by JP1/AJS3 - Manager.

    Note that only event jobs are able to maintain their status.

  2. The JP1/AJS3 - Agent service starts in the secondary node system agent.

  3. JP1/AJS3 - Manager is notified that the secondary node system agent is activated.

  4. The job status is reported from JP1/AJS3 - Manager to JP1/AJS3 - Agent in the secondary node.

    The job that is reported at this point is the one being executed when the error occurred (the status of this job was not reported to JP1/AJS3 - Manager previously). Note that the status of jobs being executed when failure occurs will be changed to Killed or Unknown end status, and the jobnet containing the job will be placed in an abnormal status.

For details about the job status inherited when a failover occurs, see 7.2.1(4) Job statuses on the manager host when an agent host is restarted.

This concludes the processing by the system. After this procedure, re-execute the Killed jobs and the jobnet containing such jobs and continue operation.