6.2.1 Monitoring via the JP1/AJS3 - View windows

(a) Monitoring root jobnets in the list area

To monitor job groups in the list area, select an upper-level job group in tree area. The root jobnets defined directly under the selected job group appear in the list area.

To monitor root jobnets in the list area, select the upper-level job group in the tree area. The root jobnets defined directly under the selected job group appear in the list area.

Which generation is shown in the Status field depends on the value set in the VIEWSTATUSRANGE environment setting parameter in the JP1/AJS3 - Manager that the user is logged in to. The parameter settings, and the priorities on which the generation determination is based, are as follows:

• VIEWSTATUSRANGE=all (default)

  1. The execution generation^# whose start time or rerun time is closest to the current time

  2. A scheduled generation^# that has been re-executed and is in wait state

  3. A scheduled generation^# due to execute in the next run, or a generation in Shutdown status

• VIEWSTATUSRANGE=today

  1. The execution generation^# whose start time or rerun time is closest to the current time

  2. A scheduled generation^# that has been re-executed and is in wait state

  3. A scheduled generation^# set for today and due to execute in the next run, or a generation in Shutdown status

  4. Of the result generations^# that completed execution today, the result generation whose end time is closest to the current time

If there is no generation that meets the above criteria, Not sched. to exe. appears in the Status field.

#

The listed statuses are categorized as being for an execution generation, scheduled generation, or result generation. The following table lists execution statuses for each generation category.

Table 6‒2: Execution statuses and generation categories

No.	Category	Displayed status levels
1	Execution generation	Now running Running + Warning Running + Abend Now monitoring Wait for start cond.
2	Scheduled generation	Wait for start time Being held
3	Result generation	Ended normally Ended with warning Ended abnormally Interrupted Killed Invalid exe. seq. Skipped so not exe. Monitor-end normal Unmonitored + Ended Monitor terminated Interrupted monitoring

Supplementary note

The color of an icon displayed in the Name column indicates information in either the Status or Result column. In the Status and Result columns, you can also display color images that represent the status. For details about these settings, see the description of the Main page in 12.3.42 Preferences dialog box in the JP1/Automatic Job Management System 3 Operator's Guide. For details about the display colors used to represent statuses, see the description of the General page in 12.3.42 Preferences dialog box in the JP1/Automatic Job Management System 3 Operator's Guide.

(b) Monitoring a root jobnet in the detailed information area

To monitor a root jobnet in the detailed information area, select the root jobnet in the list area and then click the Show button. Information about the generations of the selected root jobnet appears.

Information about the following generations is displayed in the detailed information area:

• Today's generations^#1

  • Execution generation^#2

  • Scheduled generation whose start time falls within today^#2

  • Result generation whose end time falls within today^#2

• Generation of the previous day or earlier

  Of previous generations not included in today's generations, the generation with the most recent end time.

• Generation of the next day or later

  Of next generations not included in today's generations, the generation with the earliest start time.

• Generation in Shutdown status

#1

Today means the current day in the local time of the connected scheduler service.

#2

The execution generation, scheduled generation, and result generation for today are categorized into separate sets of execution statuses. For execution statuses and generation categories, see Table 6-2.

The following figure shows the generations displayed in the detailed information area.

Figure 6‒2: Jobnet generations displayed in the detailed information area

The following figure shows the generations displayed for a jobnet that has a start condition.

Figure 6‒3: Jobnet generations displayed in the detailed information area (jobnet with a start condition)

Supplementary notes

• Generations in Not registered and Not sched. to exe. statuses are not displayed.

• A rerun generation placed in Wait for start time and Being held status is categorized as being in Now running status.

• An execution generation of a jobnet with a start condition that has been placed in Being held status is categorized as being in Now running status.

(c) Checking a root jobnet in the Monitor Details - [Jobnet] dialog box

In the Monitor Details - [Jobnet] dialog box, in addition to the jobnet status, you can check information such as the unit's start time, end time, and delay status, and execution result details.

To check a root jobnet in the Monitor Details - [Jobnet] dialog box, select the root jobnet in the list area and choose View, Detailed Information, and then choose Status, Result, or Next Schedule. The generations displayed in the Monitor Details - [Jobnet] dialog box differ depending on the menu item you choose as described below.

• When Status is chosen:

  The generations with the status displayed in the Status column in the list area are displayed.

• When Result is chosen:

  The generations with the status displayed in the Result column in the list area are displayed.

• When Next Schedule is chosen:

  The next generations due to run.

The Monitor Details - [Jobnet] dialog box is shown below.

Figure 6‒4: Monitor Details - [Jobnet] dialog box

(d) Monitoring the delay status of a unit in the delay list area and detailed information area

You can also check the delay status of a unit in the list area and the detailed information area. The delay status appears in parentheses after the character string indicating the status name (for example, Ended normally (delayed)).

The delay status displayed for a job group or root jobnet in the list area or detailed information area of the JP1/AJS3 - View window (Main window) is determined by the status priority, as listed in the following table.

Table 6‒3: Priority of delay status levels

Priority	Delay status	Delay display for root jobnets and job groups
1	Root jobnet end delay	(delayed)
2	Nested jobnet or job end delay	(nested jobnet delayed)
3	Root jobnet start delay	(delayed)
4	Nested jobnet start delay	(nested jobnet delayed)
5	Not delayed	Not displayed

From the Jobnet Monitor window you can monitor and check the execution status and execution results of the jobs and nested jobnets defined in the root jobnet.

Supplementary note

In the list area and detailed information area, the icons for delayed units are displayed in a color that represents its delay status. However, if an abend or warning status exists, by default, the abend or warning display has precedence. To give the delay status color higher priority than the abend and warning colors, you need to set the priority of delay display color. For details about delay color priority, see the description of the General page in 12.3.42 Preferences dialog box in the JP1/Automatic Job Management System 3 Operator's Guide.

(e) Monitoring job groups in the list area

To monitor job groups in the list area, select a scheduler service (default AJSROOT1) or an upper-level job group in tree area. The job groups defined directly under the selected unit appear in the list area.

In the list area, you can display the status of a job group that corresponds to the status of a jobnet defined in the job group. To display the status of a job group in the list area, you need to specify the setting. For details, see the description of the Main page in 12.3.42 Preferences dialog box in the JP1/Automatic Job Management System 3 Operator's Guide.

The status displayed for a job group or root jobnet in the list area or detailed information area is that of the job or jobnet with the highest priority among those defined under the job group or root jobnet. The different priorities of status levels that the job group or root jobnet can acquire from lower-level units are shown in the following table.

Table 6‒4: Priority of status levels acquired by job groups and root jobnets

Priority	Job group status	Route jobnet status
1	Shutdown	Shutdown
2	Running + Abend	Running + Abend
3	Ended abnormally	Ended abnormally Interrupted Killed Invalid exe. seq.
4	Running + Warning	Running + Warning
5	Ended with warning	Ended with warning
6	Now running	Wait for start time Being held Wait for start cond. Now running Now monitoring
7	Ended normally	Ended normally Skipped so not exe. Unmonitored + Ended Monitor-end normal Monitor terminated Interrupted monitoring
8	Not sched. to exe.	Not sched. to exe.
9	None	Not registered

(a) Monitor days and monitored generations

As the period to be monitored, you can specify the date on any one day. The span of one day is from the base time on that day to the next base time. When jobnets have different base times, their monitor days will cover different periods. The range of a monitor day is illustrated below.

Figure 6‒6: Range of a monitor day

In this example, 7/5 is specified as the monitor day.

Because the base time of jobnet A is 00:00, the monitor day extends from 00:00 to 23:59 on 7/5 in absolute time.

Because the base time of jobnet B is 08:00, the monitor day extends from 08:00 on 7/5 to 07:59 on 7/6 in absolute time.

Because the base time of jobnet C is 16:00, the monitor day extends from 16:00 on 7/5 to 15:59 on 7/6 in absolute time.

A generation is monitored only if it meets one of the following conditions:

• The start time or scheduled start time falls within the specified day.

• The end time or scheduled end time falls within the specified day.

• The generation is in Now running status throughout the specified day.

If you specify today or a future date, dummy schedules are also monitored.

The following figure shows how JP1/AJS3 determines the generations to be monitored.

Figure 6‒7: Determination of monitored generations

In this example, 7/5 is specified as the monitor day.

Generations A and G are not monitored because their start and end times fall outside the specified day.

Generations B and C are monitored because their end times fall within the specified day.

Generation D is monitored because its start and end times fall within the specified day.

Generations E and F are monitored because their start times fall within the specified day.

Generation H is monitored because it is in Now running status throughout the monitor day.

When a generation is partially outside the monitor day, as in generations C and E, any lower-level units that fall completely outside the monitor day are not monitored.

This is illustrated below, taking the example of generation C in Figure 6-7.

Figure 6‒8: Determination of monitored units (where the end time falls within the monitor day)

Root jobnet (generation C) is monitored because its end time falls within the monitor day.

Job 1 is not monitored because its start and end times fall outside the monitor day.

Job 2 is monitored because its end time falls within the monitor day.

Job 3 is monitored because its start and end times fall within the monitor day.

This means that if there is a delay of some sort, and an execution schedule that was due to end on the previous day extends into the monitor day, its status can still be checked as a schedule belonging to the monitor day.

This is illustrated below, taking the example of generation E in Figure 6-7.

Figure 6‒9: Determination of monitored units (where the start time falls within the monitor day)

Job 1 is monitored because its start and end times fall within the monitor day.

Job 2 is monitored because its start time falls within the monitor day.

Job 3 is not monitored because its start and end times fall outside the monitor day.

This means that if there is a delay of some sort, and an execution schedule that was due to end on the monitor day extends into the next day, its status can still be checked from its scheduled end time.

Supplementary notes

• Whether a rerun jobnet is monitored is determined from its original start time, not from its rerun start time.

• The span of the monitor day is 24 hours from the base time, regardless of whether the 24-hour schedule or 48-hour schedule is set in JP1/AJS3 - Manager.

Monitoring a jobnet that has a start condition

For a jobnet that has a start condition, both the monitoring generations and execution generations are monitored.

The following figure shows how the monitored generations are determined in this case.

Figure 6‒10: Determination of monitored execution generations when the jobnet has a start condition

In this example, 7/5 is specified as the monitor day.

The monitoring generation is monitored because it is in Now monitoring status throughout the monitor day.

Execution generations 1 and 5 are not monitored because their start and end times fall outside the monitor day.

Execution generation 2 is monitored because its end time falls within the monitor day.

Execution generation 3 is monitored because its start and end times fall within the monitor day.

Execution generation 4 is monitored because its start time falls within the monitor day.

For an execution generation, whether a unit is monitored is determined in the same way as for a root jobnet, according to whether its start time or end time falls within the monitoring range. For a monitoring generation, however, whether a unit is monitored depends on the status of the monitoring generation, as follows:

Table 6‒5: Status of a monitoring generation and monitored units

No.	Monitoring generation status	Monitored units
1	Wait for start time Being held	The root jobnet and all lower-level units are monitored.
2	Now monitoring Monitor-end normal Monitor terminated Unmonitored + Ended Interrupted monitoring Skipped so not exe.	Only the root jobnet is monitored.
3	Not sched. to exe.	No units are monitored.

For a dummy schedule, the root jobnet and all lower-level units are monitored.

(b) Calculation of progress percentages

The progress percentage (%) is calculated using the following formula:

Progress % = (number of ended units^#1) / (number of units in the execution schedules falling on the monitor day^{#1, #2}) x 100

#1

The total includes the root jobnet as well as the jobs in the jobnet.

#2

This number indicates the number of monitoring-target units. When monitoring a jobnet that is executed over two days, this number is the number of units whose execution start time (scheduled execution start time) or execution end time (scheduled end time) is included in the monitor day. Therefore, the number of monitoring-target units might be less than the total number of units under the root jobnet.

Cautionary note

If an unlimited number of executions and an unlimited period are set as the valid range of the start condition, the monitoring generation is always in Now monitoring status and its progress percentage never becomes 100%.

The following examples illustrate how a progress percentage is calculated.

Example 1: When a jobnet is executed three times on the monitor day

The jobnet in this example is executed three times on the monitor day.

Figure 6‒11: Example of a jobnet executed three times on the monitor day

In this example, nine jobs and three jobnets (generations 1 to 3), or a total of 12 units, are scheduled to execute on the monitor day. Currently, jobs up to job A in generation 2 have ended normally, and the succeeding job B is now running. Therefore, four jobs plus one jobnet (generation 1), or a total of five units, are in ended status. Putting these values in above formula, we get a progress percentage of 41%.

Example 2: When the progress percentage declines during the monitor day

The progress percentage calculation is dependent on the number of logs to keep. Depending on the values set for these items, the progress percentage of a jobnet executed multiple times on the monitor day might decline during the course of monitoring.

Figure 6‒12: Example of the progress percentage declining during the monitor day

In this example, a jobnet is executed three times on the monitor day and the number of logs to keep is set to 1. In the current time frame A-C, the monitored units include the past job in generation 1 and the scheduled generations 2 and 3, making a total of 12 scheduled units to monitor. However, when execution of generation 2 starts, because the number of logs to keep is set to 1, the job in generation 2 becomes the past job, and generation 1 is deleted. Accordingly, in the current time D-F, the monitored units include the scheduled generation 3 and the past job in generation 2, making a total of eight scheduled units to monitor. Similarly, in the current time frame G-I, because the past job in generation 3 is also monitored, there are four scheduled units to monitor. That is, the progress percentage declines between C and D, and between F and G.

Example 3: When a job linked by relation lines ends abnormally

When the jobnet being monitored contains jobs linked by relation lines, the progress percentage depends on the execution results of those jobs. Suppose, for example, we have a jobnet configuration like the following one.

Figure 6‒13: Example of a jobnet that contains jobs linked by relation lines

While the jobnet is waiting to execute, the ratio of ended units to scheduled units is 0:5, giving a progress percentage of 0%.

When the jobnet starts, job 2 ends abnormally and the succeeding jobs 3 and 4 enter Not executed + Ended status. Now the ratio of ended units to scheduled units is 1:3, giving a progress percentage of 33%.

In the Summary list, 2 appears in the Ended Abnormally field, indicating how many jobs failed.

Example 4: When the jobnet contains a recovery unit

When the jobnet being monitored contains a recovery unit, the progress percentage depends on the execution result of the recovery unit.

Suppose, for example, we have a jobnet configuration like the following one.

Figure 6‒14: Example of a jobnet that contains a recovery job

While the jobnet is waiting to execute, the ratio of ended units to scheduled units is 0:5, giving a progress percentage of 0%.

When the jobnet starts, job 2 ends normally and the jobnet completes execution. Recovery job 4, which follows job 2, is placed in Not executed + Ended status. In this case, the ratio of ended units to scheduled units is 4:4, giving a progress percentage of 100%.

As this example shows, recovery units, which are not executed unless there is an error, are excluded from the monitoring process, so the jobnet can be monitored in the usual manner.

Example 5: When monitoring a jobnet that is executed over two days

When monitoring a jobnet that is executed over two days, the progress depends on the number of units whose execution start time (scheduled execution start time) or execution end time (scheduled end time) is included in the monitor day. Therefore, the number of monitoring-target units might be less than the total number of units under the root jobnet.

Suppose, for example, we have a jobnet configuration like the following one.

Figure 6‒15: Example of a jobnet that is executed over two days

If 7/5 is specified as the monitor day, the generations of job 3 running on 7/6 are excluded from monitoring targets. Therefore, the number of units in the normal end status is 2 (job 1 and job 2), and the number of units scheduled to be executed on the monitor day is 3 (root jobnet, job 1, and job 2). If these values are substituted into the formula to calculate the progress percentage, the progress percentage is calculated to be 66%.

Also, if 7/6 is specified as the monitor day, the generations of job 1 ending normally are excluded from monitoring targets. Therefore, the number of units in the normal end status is 1 (job 2), and the number of units scheduled to be executed on the monitor day is 3 (root jobnet, job 2, and job 3). If these values are substituted into the formula to calculate the progress percentage, the progress percentage is calculated to be 33%.

(c) Status classes

Unit statuses are classified and displayed as follows:

• Ended Abnormally

• Ended with Warning

• Delay

• Being held

• Waiting to start

• Now running

• Ended Normally

The following table lists the statuses in each class.

Table 6‒6: Status classes

No.	Class	Statuses
1	Ended Abnormally	Ended abnormally Invalid exe. seq. Interrupted Killed Failed to start Unknown end status Skipped so not exe.#1 Monitor terminated
2	Ended with Warning	Ended with warning
3	Delay	Start delay#2 End delay#2
4	Being held	Being held
5	Waiting to start	Wait for start time Wait for prev. to end Waiting to execute Now queuing Wait for start cond.
6	Now running	Now running Running + Warning Running + Abend Now monitoring
7	Ended Normally	Ended normally Normal end + False Unmonitored + Ended Interrupted monitoring Monitor-end normal

Note

Units in the following statuses are excluded from the summary in the Summary Monitor window:

• Not registered

• Not sched. to exe.

• Bypassed

• Shutdown

• Not executed + Ended

• Nested jobnet delayed start

• Nested jobnet delayed end

#1

A unit that has no execution schedule, because execution was prohibited or it is a nested jobnet whose schedule does not match that of the upper-level jobnet, enters Not sched. to exe. status. If the root jobnet is skipped, the status of the unscheduled unit changes to Skipped so not exe. Units in Skipped so not exe. status are also excluded from the summary in the Summary Monitor window.

#2

When a start delay and end delay both occur in a unit, it is counted as a single delay. When a lower-level unit is delayed (Nested jobnet delayed start or Nested jobnet delayed end status), the upper-level unit being monitored is not counted as being in the Delay class.

The following table describes the relationship between delay statuses and the Delay count.

Table 6‒7: Unit delay statuses and the number of units counted as being delayed

Case	Unit delay status				Number added to the Delay count
	Start delay	End delay	Nested jobnet delayed start	Nested jobnet delayed end
1	N	N	N	N	0
2	N	N	N	Y	0
3	N	N	Y	N	0
4	N	N	Y	Y	0
5	N	Y	N	N	1
6	N	Y	N	Y	1
7	N	Y	Y	N	1
8	N	Y	Y	Y	1
9	Y	N	N	N	1
10	Y	N	N	Y	1
11	Y	N	Y	N	1
12	Y	N	Y	Y	1
13	Y	Y	N	N	1
14	Y	Y	N	Y	1
15	Y	Y	Y	N	1
16	Y	Y	Y	Y	1

Legend:

Y: Counted.

N: Not counted.

Note

When the unit being monitored is a job that started on time and has no lower-level units, it is counted as a delayed unit depending on whether an end delay occurred in the job itself (cases 1 and 5 in the above table).

For example, consider the following unit.

Figure 6‒16: Example of the unit configuration

Example 1: Only the nested jobnet is delayed (case 2)

Only job B is delayed. Root jobnet 1 and nested jobnet 1 are not delayed and are not counted as delayed units. Only job B is counted in the total, so 1 appears in the Delay field.

Example 2: Both the upper-level unit and nested unit are delayed (case 6)

Root jobnet 1, nested jobnet 1, and job B are all delayed. Root jobnet 1 and nested jobnet 1 are counted as delayed units, but the delay in the lower-level units is disregarded. Therefore, the Delay count is incremented by 1 for each of root jobnet 1, nested jobnet 1, and job B, adding up to three delayed units in total.

Example 3: Both a start delay and end delay occur (case 13)

Root jobnet 1 both starts and ends later than scheduled. It is counted as a delayed unit, but the Delay count is incremented by 1 only, giving a total of one delayed unit.