7.3.2 Status acquired by JP1/AJS3 Console

The status levels that JP1/AJS3 Console acquires for AJS3 unit monitored objects and business scopes are explained below.

Organization of this subsection

(1) Statuses for AJS3 unit monitored objects
(2) Statuses for business scopes

(1) Statuses for AJS3 unit monitored objects

JP1/AJS3 Console can display the statuses shown in the list below for AJS3 unit monitored objects.

(a) List of acquired statuses

The following table shows the statuses for monitored jobnets that can be reported by JP1/AJS3 Console Manager and JP1/AJS3 Console View, and the corresponding default icon colors.

Table 7‒9: Statuses of AJS3 unit monitored objects and corresponding colors
No.	Status	Color (default)
1	Not registered	None
2	Waiting for start time	Sky blue
3	Hold plan^#1	Yellow
4	Being held	Yellow
5	Not sched. to exe.	Gray
6	Now running	Green
7	Running + Warning	Red
8	Running + Abend	Red
9	Ended normally	Light green
10	Ended with warning	Light red
11	Ended abnormally	Light red
12	Interrupted	Light red
13	Killed	Light red
14	Invalid exe. seq.	Light red
15	Skipped so not exe.	Gray
16	Shutdown	Brown
17	Now monitoring	Green
18	Wait for start cond.	Sky blue
19	Unmonitored + Ended	Gray
20	Monitor-end normal	Light green
21	Monitor terminated	Light red
22	Interrupted monitoring	Light green
23	No status^#2	None
24	Unrecognizable^#3	Gray
25	Unknown^#4	Red

#1

A hold plan is only displayed when the function for displaying hold plans is enabled in the monitoring properties. Although color is used to indicate the hold plan, the hold plan is not displayed as a status name.

#2

This status indicates than no status has yet been received from JP1/AJS3 Console Agent.

#3

This status indicates that JP1/AJS3 Console Manager and JP1/AJS3 Console View are unable to recognize the status of a monitored jobnet.

#4

This status is displayed when any of the following is true:

A jobnet specified in an AJS3 unit monitored objects is not a root jobnet.
JP1/AJS3 Console could not connect to the host because the host name was invalid.
A jobnet specified in an AJS3 unit monitored objects does not exist.
You do not have permission to reference a jobnet specified in an AJS3 unit monitored objects.
You do not have permission to access an upper-level unit for a jobnet specified in an AJS3 unit monitored objects.
JP1/AJS3 Console cannot obtain the status of a jobnet since the scheduler service where the monitored jobnet is defined is undergoing maintenance.
JP1/AJS3 Console cannot connect to the authentication server.
JP1/AJS3 Console cannot obtain the status levels because JP1/AJS3 Console Agent is not running.
JP1/AJS3 Console cannot connect to JP1/AJS3 Console Agent.
A problem occurred that prevents JP1/AJS3 Console Agent from acquiring statuses.

If a status is displayed as Unknown, you can obtain more details in the Detailed Information - [AJS3 Unit Monitored Objects] dialog box.

(b) Delay status

With JP1/AJS3 Console, you can also monitor the delay status of a jobnet. The jobnet delay status is shown in parentheses after a status name listed in Table 7-9 (for example, Now running (Delayed start)).

There are four delay status levels that apply to AJS3 unit monitored objects.

Delayed end
Delayed start
Nested jobnet delayed end
Nested jobnet delayed start

To Page Top

(2) Statuses for business scopes

Business scopes can take the same status as AJS3 unit monitored objects. The only difference is that hold plans do not affect the display color for a business scope. The status displayed for a business scope is that of the lower-level business scope or AJS3 unit monitored object whose status has the highest priority.

(a) Acquired statuses and their priority

The order of the different statuses that can be displayed for a business scope are shown in the following table.

Table 7‒10: Order of priority of statuses for business scopes
Priority	Status
1	Unknown
2	Shutdown
3	Running + Abend
4	Ended abnormally
5	Killed
6	Interrupted
7	Invalid exe. seq.
8	Running + Warning
9	Ended with warning
10	Being held
11	Now running
12	Wait for start cond.
13	Now monitoring
14	Waiting for start time
15	Skipped so not exe.
16	Unmonitored + Ended
17	Monitor terminated
18	Interrupted monitoring
19	Ended normally
20	Monitor-end normal
21	Not sched. to exe.
22	Not registered
23	Unrecognizable
24	No status

(b) Order of priority of delay statuses

The delay status displayed for a business scope is that of the lower-level business scope or AJS3 unit monitored object whose delay status has the highest priority. The order of priority of the delay statuses is shown in the following table.

Table 7‒11: Order of priority of delay statuses for business scopes
Priority	Delay status
1	Delayed end
2	Nested jobnet delayed end
3	Delayed start
4	Nested jobnet delayed start
5	Not delayed

(c) Status display example for a business scope

The following figure shows an example of the status display for a business scope.

Figure 7‒19: Status display example for a business scope

In the case of a business scope, the statuses of all lower-level business scopes and AJS3 unit monitored objects are merged, and the upper-level business scope displays the status with the highest priority.

To Page Top