10.1.2 Monitoring JP1/AJS3 by using JP1/IM2

(1) Monitoring the statuses of root jobnets managed by multiple instances of JP1/AJS3 - Manager

You can obtain jobnet information from multiple instances of JP1/AJS3 - Manager that are managed by JP1/IM2 to monitor their statuses on one screen. The status of a jobnet that was started by a manager host is updated by a JP1 event issued when the jobnet terminates.

The following figure shows an overview of the processing to update a jobnet status.

Figure 10‒2: Overview of the processing to update a jobnet status

To Page Top

(2) Supporting determination of business impact

The Job flow tab of JP1/IM2 allows you to check links between jobnets. You can also check links between jobnets that are managed by multiple JP1/AJS3 - Manager instances. If an error is detected in a root jobnet, you can use this function to quickly check the impact, such as the scheduled start time of the succeeding job and whether the succeeding job is affected. This allows you to cope with failures in appropriate priority.

The following figure shows an overview of monitoring the status and links between jobnets managed by multiple JP1/AJS3 - Manager instances.

Figure 10‒3: Monitoring the status and links between jobnets managed by multiple JP1/AJS3 - Manager instances

You can monitor units that have the following links:

• Links with JP1 events

• Links with wait conditions

• Links with jobnet connectors

In addition, clicking an icon in the Job flow tab opens the Linked unit dialog box. If a failure occurs in the preceding unit, you can use this dialog box to check the affected succeeding unit and understand the urgency of corrective actions for each unit job based on the scheduled time. You can also display the Monitor screen of Web GUI by clicking the preceding or succeeding unit name. This allows you to check details about jobnets in each unit. The Monitor screen also allows you to change the wait statuses of units.

The following figure shows an overview of monitoring jobnet details by using the Linked unit dialog box.

Figure 10‒4: Monitoring jobnet details by using the Linked unit dialog box

Cautionary note

To monitor wait-related links as described in Supporting determination of business impact, operate the system so that, for one root jobnet, the number of generations for a day does not exceed 1,000. The schedule dates and times related to the succeeding units of the 1,000th or later generations will not be displayed.

To Page Top

(3) Proactive monitoring

JP1/AJS3 issues a JP1 event to report that a factor that might stop job execution occurred. Early detection of such factors is possible by checking JP1 events from JP1/IM2. In addition, all performance data collected by JP1/AJS3 in performance reports is displayed as trend information in graphics format in JP1/IM2. This allows you to use trend information to check the operation status of the scheduler service and isolate the cause of any failure. This function is called proactive monitoring.

The following figure shows an overview of proactive monitoring.

Figure 10‒5: Overview of proactive monitoring

To perform proactive monitoring, the following settings are required:

• Settings for detecting factors that might stop job execution

• Settings for the performance report output function

For details about how to specify the settings for detecting factors that might stop job execution, see 21.7 Settings for detecting factors that might stop job execution in the JP1/Automatic Job Management System 3 Configuration Guide.

For details about how to set the performance report output function, see 6.6 Settings related to the output of performance reports in the JP1/Automatic Job Management System 3 Configuration Guide (in Windows) or 15.7 Settings related to the output of performance reports in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

To Page Top

(4) Other features supported by JP1/IM2

The following describes other features supported by JP1/IM2.

To Page Top