13.5.2 Statuses acquired by objects

(a) List of acquired statuses

The following table shows the statuses of AJS3 unit monitored objects that JP1/AJS3 Console Manager and JP1/AJS3 Console Agent notify of and the default icon display colors.

Table 13‒3: Statuses of AJS3 unit monitored object and default display colors

No.	Status name	Default display color
1	Not registered	Not specified
2	Wait for starting 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	Blocked	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	Not specified
24	Unrecognizable#3	Gray
25	Unknown#4	Red

#1

The color for representing Hold plan is displayed only when the Display option is selected for Hold plan in the Monitoring Properties dialog box. For the status, only the color indicates the status while the status name is not displayed.

#2

Indicates that no status has been notified from JP1/AJS3 Console Agent.

#3

Indicates that JP1/AJS3 Console Manager and JP1/AJS3 Console View cannot determine the status of the monitored jobnet.

#4

Indicates one of the following statuses:

• The monitored jobnet is not a root jobnet.

• The monitored host cannot be connected because of an invalid host name.

• The monitored jobnet does not exist.

• No right to reference the monitored jobnet.

• No right to for access the upper-level unit of the monitored jobnet.

• No status can be acquired because the maintenance of the monitored scheduler service is in progress.

• The monitored host cannot connect to the authentication server.

• The status cannot be acquired because JP1/AJS3 Console Agent has not started.

• JP1/AJS3 Console Manager cannot connect to JP1/AJS3 Console Agent.

• Trouble occurred on JP1/AJS3 Console Agent that prevented acquiring the status.

When Unknown is displayed, you can check the cause in the Detail Information - [AJS3 Unit Monitored Objects] dialog box.

(b) Delay statuses

JP1/AJS3 Console can also monitor the delay status of AJS3 unit monitored object. The delay status of AJS3 unit monitored object is displayed in parentheses following the status name shown in the table above, Statuses of AJS3 unit monitored object and default display colors. (For example: Now running (Delayed start) )

The delay statuses of AJS3 unit monitored object are:

• Delayed end

• Delayed start

• Nested jobnet delayed end

• Nested jobnet delayed start

(a) Acquired statuses and priority

The status of business scope notified by JP1/AJS3 Console Manager and the default icon display colors are the same as those for AJS3 unit monitored objects. However, for the business scopes, Hold plan is not displayed in color. When no object exists under the business scope, the status of the business scope becomes No status status.

The status displayed has the highest priority among the lower-level business scopes and AJS3 unit monitored objects. The following table shows the priority of statuses.

Table 13‒4: Priority of statuses of business scope

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	Wait 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 shed. to exe.
22	Not registered
23	Unrecognizable
24	No status

(b) Priority of delay statuses

JP1/AJS3 Console can also monitor the delay status of a business scope. The delay statuses of a business scope are the same as those for AJS3 unit monitored objects.

The delay status displayed has the highest priority among the lower-level business scopes and the AJS3 unit monitored objects. The following table shows the priority of delay statuses. Without any unit under the business scope, Not delayed is displayed.

Table 13‒5: Priority of delay statuses of a business scope

Priority	Status
1	Delayed end
2	Nested jobnet delayed end
3	Delayed start
4	Nested jobnet delayed start
5	Not delayed

(c) Display example of status of a business scope

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

Figure 13‒12: Display example of status of a business scope

The status of the upper-level business scope is displayed based on the priority by merging the statuses of the lower-level business scopes and AJS3 unit monitored objects.

Cautionary notes

• On acquiring the status, if the connection to the authentication server failed, the status of a monitored object, which requires an authority check and whose status acquirement has not been completed, becomes Unknown status. Additionally the message "KAVS1005-E Cannot connect to Access Control Server" is displayed for Information in the Detail Information - [AJS3 Unit Monitored Objects] dialog box.

• When some monitored objects require the authority check, the connection to the authentication server is tried at the monitoring interval. When the connection to the authentication server fails because the server has stopped or for other causes, it takes time until the connection request to the authentication server is timed out. It may take time until the status acquirement is completed.