Job Management Partner 1/Automatic Job Management System 3 - Web Operation Assistant Description, Operator's Guide and Reference

2.2.1 List view for status acquisition

When you search for information about the job or jobnets that satisfy the conditions specified in the frame for setting status acquisition conditions, the results are displayed in a list view. Use unit names to specify the units whose statuses are to be acquired.

Organization of this subsection

(1) Specifying a monitoring target

(2) Filtering displayed information

(3) Selecting a display method

(4) Selecting a monitoring method

(5) Sorting of displayed items

(1) Specifying a monitoring target

(a) Specifying a unit

Specify a unit to be monitored by its host name, service name, and unit name.

A unit name can be specified not only by an absolute path name, but also by using wildcards. The following table describes the regular expressions that can be used as wildcards.

Table 2-1 Regular expressions that can be used as wildcards

Regular expression Description

* Any string of 0 or more characters

? Any character

Note that you cannot use backslashes (\), double quotation marks ("), back quotation marks (`), or square brackets ([ ]) when specifying a unit name.

(b) Selecting a unit type

When selecting a unit to be monitored, you can also choose whether to include the units under the specified unit, as well as the type of units to include.

Table 2-2 Unit types under the specified unit

Unit type Description

Specified Unit only Specifies that only the unit specified by the unit name is to be monitored

All Units under specified Unit Specifies that all units within the unit specified by the unit name are also to be monitored

Only Root Jobnets under specified Unit Specifies that only root jobnets within the unit specified by the unit name are also to be monitored

Only Jobnets under specified Unit Specifies that only jobnets within the unit specified by the unit name are also to be monitored

Only Jobs under specified Unit Specifies that only jobs within the unit specified by the unit name are also to be monitored

The following table describes the correspondence between the unit types specified in the search conditions and the unit types displayed.

Table 2-3 Correspondence between the unit types specified in the search conditions and the unit types displayed

Unit type Unit type specified in the search conditions

Specified Unit only All Units under specified Unit Only Root Jobnets under specified Unit Only Jobnets under specified Unit Only Jobs under specified Unit

Job groups No No No No No

Root jobnets (normal) Yes^# Yes Yes Yes No

Root remote jobnets (normal) Yes^# Yes Yes Yes No

Root jobnets (within planning groups) Yes^# Yes Yes Yes No

Remote root jobnets (within planning groups) Yes^# Yes Yes Yes No

Nested jobnets Yes^# Yes No Yes No

Nested remote jobnets Yes^# Yes No Yes No

Manager job groups No No No No No

Manager jobnets No No No No No

Planning groups No No No No No

Jobs Yes^# Yes No No Yes

Host link jobnets Yes^# Yes No Yes No

Legend:

Yes: Displayed

No: Not displayed (not monitored)

#

When a corresponding unit is specified

Regular expression	Description
*	Any string of 0 or more characters
?	Any character

Unit type	Description
Specified Unit only	Specifies that only the unit specified by the unit name is to be monitored
All Units under specified Unit	Specifies that all units within the unit specified by the unit name are also to be monitored
Only Root Jobnets under specified Unit	Specifies that only root jobnets within the unit specified by the unit name are also to be monitored
Only Jobnets under specified Unit	Specifies that only jobnets within the unit specified by the unit name are also to be monitored
Only Jobs under specified Unit	Specifies that only jobs within the unit specified by the unit name are also to be monitored

Unit type	Unit type specified in the search conditions
Specified Unit only	All Units under specified Unit	Only Root Jobnets under specified Unit	Only Jobnets under specified Unit	Only Jobs under specified Unit
Job groups	No	No	No	No	No
Root jobnets (normal)	Yes^#	Yes	Yes	Yes	No
Root remote jobnets (normal)	Yes^#	Yes	Yes	Yes	No
Root jobnets (within planning groups)	Yes^#	Yes	Yes	Yes	No
Remote root jobnets (within planning groups)	Yes^#	Yes	Yes	Yes	No
Nested jobnets	Yes^#	Yes	No	Yes	No
Nested remote jobnets	Yes^#	Yes	No	Yes	No
Manager job groups	No	No	No	No	No
Manager jobnets	No	No	No	No	No
Planning groups	No	No	No	No	No
Jobs	Yes^#	Yes	No	No	Yes
Host link jobnets	Yes^#	Yes	No	Yes	No

(2) Filtering displayed information

The list display can be filtered for the following conditions.

Specifiable conditions Description

Status Execution status

Now running

Being held

Shutdown

Result

Now monitoring

Schedule

Only units of the specified status are displayed.
If no status is specified, units of all statuses are displayed, except for those not yet registered.
For Now running and Result, you can specify one of the following detailed conditions: All, Normal, Warning, Abend, or Warning/Abend. Specify All to leave the detailed condition blank.

Delay status

Start delay

End delay

Units in the start delay or end delay status are displayed.

Hold plan status Units that are scheduled to be held are displayed.

Comment string Only units whose comment contains the specified string are displayed.

Target host name Only units whose execution destination is the specified host are displayed.

(a) How conditions are combined

When the status, comment string and target host name conditions are specified simultaneously, units that satisfy all of the conditions are selected.

When the execution status, delay status, and hold plan status conditions are specified simultaneously, units that satisfy all of the conditions are selected.

When each status within the execution status and delay status conditions are specified simultaneously, units that satisfy at least one of those conditions are selected.

(b) Correspondence between the specified status and the status in JP1/AJS3 - Manager or JP1/AJS2 - Manager

The following table describes the correspondence between the statuses specified in the search conditions and the statuses in JP1/AJS3 - Manager or JP1/AJS2 - Manager.

Table 2-4 Correspondence between the statuses specified in the search conditions and the statuses in JP1/AJS3 - Manager or JP1/AJS2 - Manager

JP1/AJS3 - Web Operation Assistant search condition Status in JP1/AJS3 - Manager or JP1/AJS2 - Manager Existence of status

Status Detailed status Jobnet Job

Root Nested

Now running Normal Now running Yes Yes Yes

Now queuing No No Yes

Warning Running + Warning Yes Yes No

Abend Running + Abend Yes Yes No

Being held -- Being held Yes Yes Yes

Shutdown -- Shutdown Yes Yes Yes

Result Normal Ended normally Yes Yes Yes

Normal end + false No No Yes

Bypassed No Yes Yes

Skipped so not exe. Yes Yes No

Monitor-end normal Yes Yes No

Unmonitored + Ended Yes Yes No

Interrupted monitoring Yes Yes Yes

Warning Ended with warning Yes Yes Yes

Abend Not executed + Ended No Yes Yes

Ended abnormally Yes Yes Yes

Invalid exe. seq. Yes Yes No

Interrupted Yes Yes No

Killed Yes Yes Yes

Failed to start No No Yes

Monitor terminated Yes Yes No

Unknown end status No No Yes

Now monitoring -- Now monitoring Yes Yes No

Schedule -- Waiting to execute No No Yes

Waiting for start time Yes Yes No

Waiting for prev. to end No Yes Yes

Legend:

Yes: The status exists.

No: The status does not exist.

Specifiable conditions	Description
Status	Execution status	Now running Being held Shutdown Result Now monitoring Schedule	Only units of the specified status are displayed. If no status is specified, units of all statuses are displayed, except for those not yet registered. For Now running and Result, you can specify one of the following detailed conditions: All, Normal, Warning, Abend, or Warning/Abend. Specify All to leave the detailed condition blank.
Delay status	Start delay End delay	Units in the start delay or end delay status are displayed.
Hold plan status	Units that are scheduled to be held are displayed.
Comment string	Only units whose comment contains the specified string are displayed.
Target host name	Only units whose execution destination is the specified host are displayed.

JP1/AJS3 - Web Operation Assistant search condition	Status in JP1/AJS3 - Manager or JP1/AJS2 - Manager	Existence of status
Status	Detailed status	Jobnet	Job
Root	Nested
Now running	Normal	Now running	Yes	Yes	Yes
Now queuing	No	No	Yes
Warning	Running + Warning	Yes	Yes	No
Abend	Running + Abend	Yes	Yes	No
Being held	--	Being held	Yes	Yes	Yes
Shutdown	--	Shutdown	Yes	Yes	Yes
Result	Normal	Ended normally	Yes	Yes	Yes
Normal end + false	No	No	Yes
Bypassed	No	Yes	Yes
Skipped so not exe.	Yes	Yes	No
Monitor-end normal	Yes	Yes	No
Unmonitored + Ended	Yes	Yes	No
Interrupted monitoring	Yes	Yes	Yes
Warning	Ended with warning	Yes	Yes	Yes
Abend	Not executed + Ended	No	Yes	Yes
Ended abnormally	Yes	Yes	Yes
Invalid exe. seq.	Yes	Yes	No
Interrupted	Yes	Yes	No
Killed	Yes	Yes	Yes
Failed to start	No	No	Yes
Monitor terminated	Yes	Yes	No
Unknown end status	No	No	Yes
Now monitoring	--	Now monitoring	Yes	Yes	No
Schedule	--	Waiting to execute	No	No	Yes
Waiting for start time	Yes	Yes	No
Waiting for prev. to end	No	Yes	Yes

(3) Selecting a display method

You can choose from the following display methods:

Display all
All information matching the search conditions is displayed in one page on the Web browser.

Display n records
Of the information matching the search conditions, the number of records specified in the numeric input field is displayed on one page in the Web browser. If the number of matching records exceeds this number, the records are displayed on the following pages, and the Next n records link is displayed. Click this link to navigate to the next page. On all pages but the first, the Prev. n records link is also displayed.
When you click these links to navigate forward and backward, the displayed information is not re-acquired. When the auto refresh option is used, information is automatically updated after the specified time has elapsed, but if the number of pages becomes smaller than that displayed before the update, the last page after collection is displayed.

(4) Selecting a monitoring method

You can select one of the following monitoring methods to specify which statuses are prioritized for display among the generations of jobnets monitored:

Prioritize all Unit times

Prioritize all Unit time schedules

The following explains the display priority for each monitoring method.

(a) Display priority

There are two ways to prioritize the display for monitoring targets: by result or by schedule.

Table 2-5 Display priority for monitoring method

Monitoring method Display priority

Prioritize all Unit times The display is prioritized by result.

Prioritize all Unit time schedules The display is prioritized by schedule.
  
The following describes the display priority for statuses in each case.

When results are prioritized (Prioritize all Unit times)
The following describes the status display priorities when results are prioritized.

Table 2-6 Status display priorities when results are prioritized

Priority Status of the target generation Priority criterion when multiple generations of the same status exist

1 (high) Now running Proximity of start time (of re-execution) to current time

2 Being held Proximity of scheduled start time to current time

3 Waiting for start time^#
(for re-execution) Proximity of start time for which the generation is waiting to current time

4 Shutdown --

5 Result Proximity of end time to current time (including re-execution)

6 Now monitoring Proximity of start time to current time

7 (low) Schedule Proximity of scheduled start time to current time

#

Generations to be rerun take priority over normal generations in the Waiting for start time status. Normal generations waiting for a start time are included in the Schedule status.

When schedules are prioritized (Prioritize all Unit times)
The following describes the status display priorities when schedules are prioritized.

Table 2-7 Status display priorities when schedules are prioritized

Priority Status of the target generation Priority criterion when multiple generations of the same status exist

1 (high) Now running Proximity of start time (of re-execution) to current time

2 Being held Proximity of scheduled start time to current time

3 Waiting for start time^#
(for re-execution) Proximity of start time for which the generation is waiting to current time

4 Shutdown --

5 Now monitoring Proximity of start time to current time

6 Schedule Proximity of scheduled start time to current time

7 (low) Result Proximity of end time to current time (including re-execution)

#

Generations to be rerun take priority over normal generations in the Waiting for start time status. Normal generations waiting for a start time are included in the Schedule status.

As you can see from Table 2-6 and Table 2-7, generations in the Now running status have the highest display priority. Also, if multiple generations of the same status exist, those with start times, scheduled start times, or end times closer to the current time take priority.

The following figure gives an example display in which multiple generations of the same status exist.

Figure 2-2 Example display in which multiple generations of the same status exist

(b) Example status display of result priority and schedule priority

The following gives example status displays for current day and total generation targets for cases of result priority and schedule priority.

n Predicted performance of jobnets and the status display in JP1/AJS3 - Web Operation Assistant

The following describes the statuses (predicted performance) of each generation within the monitoring range and the status display in JP1/AJS3 - Web Operation Assistant.

Table 2-8 Statuses (predicted performance) of each generation within the monitoring range and the status display in JP1/AJS3 - Web Operation Assistant

Status of each generation (plans and results) JP1/AJS3 - Web Operation Assistant status display

Previous day and earlier Current day Next day and later Result priority Schedule priority

-- -- -- -- -- (Nothing displayed) (Nothing displayed)

Result -- -- -- -- Result Result

-- Result -- -- -- Result Result

-- -- Now running -- -- Now running Now running

-- -- -- Schedule -- Schedule Schedule

-- -- -- -- Schedule Schedule Schedule

Result 1 Result 2 Now running Schedule 1 Schedule 2 Now running Now running

Result 1 Result 2 -- -- -- Result 2 Result 2

Result -- Now running -- -- Now running Now running

Result -- -- Schedule -- Result Schedule

Result -- -- -- Schedule Result Schedule

-- Result Now running -- -- Now running Now running

-- Result -- Schedule -- Result Schedule

-- Result -- -- Schedule Result Schedule

-- -- Now running Schedule -- Now running Now running

-- -- Now running -- Schedule Now running Now running

-- -- -- Schedule 1 Schedule 2 Schedule 1 Schedule 1

Result 1 Result 2 Now running -- -- Now running Now running

Result 1 Result 2 -- Schedule -- Result 2 Schedule

Result 1 Result 2 -- -- Schedule Result 2 Schedule

Result -- Now running Schedule -- Now running Now running

Result -- Now running -- Schedule Now running Now running

Result -- -- Schedule 1 Schedule 2 Result Schedule 1

-- Result Now running Schedule -- Now running Now running

-- Result Now running -- Schedule Now running Now running

-- Result -- Schedule 1 Schedule 2 Result Schedule 1

-- -- Now running Schedule 1 Schedule 2 Now running Now running

Result 1 Result 2 Now running Schedule -- Now running Now running

Result 1 Result 2 Now running -- Schedule Now running Now running

Result 1 Result 2 -- Schedule 1 Schedule 2 Result 2 Schedule 1

Result -- Now running Schedule 1 Schedule 2 Now running Now running

-- Result Now running Schedule 1 Schedule 2 Now running Now running

Legend:

--: No generations exist.

If there are no generations (plans and results) within the monitoring range or the generations are in the Wait for start cond. status, nothing will be displayed.

n Status display for jobnets with start conditions

The following describes the status display when jobnets to be monitored have start conditions.

Table 2-9 Status display for jobnets with start conditions

Start condition satisfaction Status JP1/AJS3 - Web Operation Assistant status display

Start condition Root jobnet Result priority Schedule priority

Not reached Now monitoring Waiting for start cond. Now monitoring Now monitoring

Unmonitored + Ended -- Unmonitored + Ended Unmonitored + Ended
or
Waiting for start time

Monitor terminated -- Monitor terminated Monitor terminated
or
Waiting for start time

Interrupted monitoring -- Interrupted monitoring Interrupted monitoring
or
Waiting for start time

Reached Now monitoring Now running
Waiting for start cond. Now running Now running

Result
Waiting for start cond. Result Now monitoring

Monitor terminated Now running Now running Now running

Result before monitor terminated Monitor terminated Monitor terminated
or
Waiting for start time

Result after monitor terminated Result Result
or
Waiting for start time

Interrupted monitoring Result Interrupted monitoring Interrupted monitoring
or
Waiting for start time

Monitor-end normal Now running Now running Now running

Result Result Result
or
Waiting for start time

Legend:

--: No generations exist.

n Status display for jobnets with skipped or multiple schedules

The following describes the status display when jobnets to be monitored have skipped or multiple schedules (without multiple starts).

Figure 2-3 Example status display for jobnets with skipped or multiple schedules (without multiple starts)

For jobnets with skipped schedules, the status of the skipped generation is Skipped so not exe., but since the result of the generation before the one skipped is closer to the current time, this status is not displayed.

Also, for jobnets with multiple schedules (without multiple starts), the status of a given generation is Waiting for start time. until the previous generation terminates, but since the priority of previous generations in the Now running status is higher, this status is not displayed.

n Status display for rerun jobnets

If a jobnet is rerun after being terminated, the generation to be displayed is determined by using the rerun start time. In the case below, since the execution start time for Now running 1 is closer to the current time than that of Now running 2, Now running 1 is displayed.

Figure 2-4 Operation when a root jobnet is rerun after being terminated

However, when a root jobnet is rerun while its status is Now running, it is displayed using the execution start time. In the case below, since the execution start time for Now running 2 is closer to the current time than that of Now running 1, Now running 2 is displayed.

Figure 2-5 Operation when a root jobnet is rerun while in the Now running status

Monitoring method	Display priority
Prioritize all Unit times	The display is prioritized by result.
Prioritize all Unit time schedules	The display is prioritized by schedule.

Priority	Status of the target generation	Priority criterion when multiple generations of the same status exist
1 (high)	Now running	Proximity of start time (of re-execution) to current time
2	Being held	Proximity of scheduled start time to current time
3	Waiting for start time^# (for re-execution)	Proximity of start time for which the generation is waiting to current time
4	Shutdown	--
5	Result	Proximity of end time to current time (including re-execution)
6	Now monitoring	Proximity of start time to current time
7 (low)	Schedule	Proximity of scheduled start time to current time

Priority	Status of the target generation	Priority criterion when multiple generations of the same status exist
1 (high)	Now running	Proximity of start time (of re-execution) to current time
2	Being held	Proximity of scheduled start time to current time
3	Waiting for start time^# (for re-execution)	Proximity of start time for which the generation is waiting to current time
4	Shutdown	--
5	Now monitoring	Proximity of start time to current time
6	Schedule	Proximity of scheduled start time to current time
7 (low)	Result	Proximity of end time to current time (including re-execution)

Status of each generation (plans and results)	JP1/AJS3 - Web Operation Assistant status display
Previous day and earlier	Current day	Next day and later	Result priority	Schedule priority
--	--	--	--	--	(Nothing displayed)	(Nothing displayed)
Result	--	--	--	--	Result	Result
--	Result	--	--	--	Result	Result
--	--	Now running	--	--	Now running	Now running
--	--	--	Schedule	--	Schedule	Schedule
--	--	--	--	Schedule	Schedule	Schedule
Result 1	Result 2	Now running	Schedule 1	Schedule 2	Now running	Now running
Result 1	Result 2	--	--	--	Result 2	Result 2
Result	--	Now running	--	--	Now running	Now running
Result	--	--	Schedule	--	Result	Schedule
Result	--	--	--	Schedule	Result	Schedule
--	Result	Now running	--	--	Now running	Now running
--	Result	--	Schedule	--	Result	Schedule
--	Result	--	--	Schedule	Result	Schedule
--	--	Now running	Schedule	--	Now running	Now running
--	--	Now running	--	Schedule	Now running	Now running
--	--	--	Schedule 1	Schedule 2	Schedule 1	Schedule 1
Result 1	Result 2	Now running	--	--	Now running	Now running
Result 1	Result 2	--	Schedule	--	Result 2	Schedule
Result 1	Result 2	--	--	Schedule	Result 2	Schedule
Result	--	Now running	Schedule	--	Now running	Now running
Result	--	Now running	--	Schedule	Now running	Now running
Result	--	--	Schedule 1	Schedule 2	Result	Schedule 1
--	Result	Now running	Schedule	--	Now running	Now running
--	Result	Now running	--	Schedule	Now running	Now running
--	Result	--	Schedule 1	Schedule 2	Result	Schedule 1
--	--	Now running	Schedule 1	Schedule 2	Now running	Now running
Result 1	Result 2	Now running	Schedule	--	Now running	Now running
Result 1	Result 2	Now running	--	Schedule	Now running	Now running
Result 1	Result 2	--	Schedule 1	Schedule 2	Result 2	Schedule 1
Result	--	Now running	Schedule 1	Schedule 2	Now running	Now running
--	Result	Now running	Schedule 1	Schedule 2	Now running	Now running

Start condition satisfaction	Status	JP1/AJS3 - Web Operation Assistant status display
Start condition	Root jobnet	Result priority	Schedule priority
Not reached	Now monitoring	Waiting for start cond.	Now monitoring	Now monitoring
Unmonitored + Ended	--	Unmonitored + Ended	Unmonitored + Ended or Waiting for start time
Monitor terminated	--	Monitor terminated	Monitor terminated or Waiting for start time
Interrupted monitoring	--	Interrupted monitoring	Interrupted monitoring or Waiting for start time
Reached	Now monitoring	Now running Waiting for start cond.	Now running	Now running
Result Waiting for start cond.	Result	Now monitoring
Monitor terminated	Now running	Now running	Now running
Result before monitor terminated	Monitor terminated	Monitor terminated or Waiting for start time
Result after monitor terminated	Result	Result or Waiting for start time
Interrupted monitoring	Result	Interrupted monitoring	Interrupted monitoring or Waiting for start time
Monitor-end normal	Now running	Now running	Now running
Result	Result	Result or Waiting for start time

(5) Sorting of displayed items

When you click the column item name of the list display, row data is sorted on the key of the specified item. Even if the displayed information spans multiple hosts, information from all hosts is displayed in aggregate. When a sort is performed, data from all pages is sorted to display information over several pages, after which the first page is displayed. The following describes how to specify ascending and descending orders.

To sort data in ascending order: click the column item name an odd number of times

To sort data in descending order: click the column item name an even number of times

[Contents][Back][Next]

[Trademarks]