12.7.7 Detailed Schedule dialog box

The Detailed Schedule dialog box displays detailed schedule information on a jobnet or job. The following figure shows the Detailed Schedule dialog box.

Figure 12‒204: Detailed Schedule dialog box

The following explains the displayed items.

Name

Displays the name of a jobnet or job.

Execution schedule for the selected item

Displays detailed schedule information on the selected jobnet or jobnet.

Status

Displays the status of detailed schedule information on the execution schedule selected in Execution schedule for the selected item.

Some of the statuses shown in the items need special attention as mentioned below.

Scheduled start time

Displays the date and time at which execution requested by the schedule rules takes place, only in the case of jobnets.

Start time

Displays the date and time at which execution is scheduled to start. If the execution has already started, it displays the date and time at which execution started. For a flexible job, the date and time that the relay agent or JP1/AJS3 - Manager sent an execution request to the destination is displayed.

Rerun start time

Displays the date and time at which re-execution took place last, only in the case of jobnets.

When the unit is re-executed, the rerun start time is set for the upper-level jobnet at the rerun start point.

However, the rerun start time is not set for the root jobnet if the root jobnet is being executed. If the root jobnet has terminated and the root jobnet has been specified for the rerun start point, the rerun start time is exclusively set for the root jobnet.

End time

Displays the date and time at which execution is scheduled to end. Otherwise, displays the date and time at which execution ended.

Delay status

If there are a number of delays, the following priority is given to them:

End delay
Nest end delay
Start delay
Nest start delay

Time when start delayed

Displays the date and time at which a start delay is to be monitored.

Time when end delayed

Displays the date and time from which to start monitoring of delayed end.

For jobnets

When an end delay is monitored based on the end time in the schedule, the system assumes the following to be the time from which to start monitoring an end delay: time after the specified number of days and hours from the scheduled start time or absolute time of the scheduled end.

When an end delay is monitored based on the time required for execution, the system assumes the number of days and hours from the start date and time. Therefore, the date and time from which to start detecting an end delay is determined when a jobnet starts to be executed.

If you have specified monitoring of an end delay based on both the scheduled end time and the time required for execution, the earlier time is shown here.
For jobs

When an end delay is monitored based on the time required for execution, the system assumes the number of days and hours from the start date and time. Therefore, the date and time from which to start detecting an end delay is determined when a job starts to be executed.

Execution ID

Displays the execution ID.

Exec. ID (Destination)

Displays the execution ID of the connection-destination jobnet for a jobnet connector.

For the following cases, the Status column displays None.

When no jobnet is connected.
When you do not have reference permission for the connection-destination jobnet.
When an error occurs during referencing of the connection-destination jobnet.

The Status column displays a hyphen (-) for units other than jobnet connectors.

This line appears only for nested jobnets, nested remote jobnets, and jobnet connectors.

Cautionary note

When the jobnet connector is connected to a jobnet under a scheduler service on a different host, you need to start the JP1/AJS3 service on the host with the connection-destination jobnet beforehand.

Supplementary notes

The following table describes whether this item displays the execution ID of the connection-destination jobnet based on the status of the jobnet.

Table 12‒52: Status of a connection-destination jobnet and whether its execution ID is displayed
Result/schedule	Generation of jobnet connector	Status of connection-destination jobnet		Execution ID
Result	Result	The connection-destination jobnet is not connected.		N
		The connection-destination jobnet is connected.	The connection-destination jobnet exists.	Y
		The connection-destination jobnet is connected.	The connection-destination jobnet does not exist (deleted when registration is canceled).	Y
Schedule	Fixed	A fixed execution schedule exists for the connection-destination jobnet on the execution day of the jobnet connector.	The unit type of the connection-destination jobnet is correct.	Y
			The unit type of the connection-destination jobnet is invalid.	Y^#
		A dummy schedule exists for the connection-destination jobnet on the execution day of the jobnet connector.		N
		A dummy schedule does not exist for the connection-destination jobnet on the execution day of the jobnet connector.		N
	Dummy schedule	--		N

Legend:

--: Not applicable.

Y: Displayed.

N: None is displayed.

#

When a normal root jobnet or nested jobnet is specified as the connection-destination jobnet (invalid definition), Exec. ID (Destination) displays the execution ID of the connection-destination jobnet for a scheduled generation of the jobnet connector. However, the jobnet enters the Ended abnormally status when it is executed because the definition is invalid. To check whether there are any definition errors, perform a definition pre-check.

For generations without fixed connection, the connection-destination jobnet determines the generation to be connected and Exec. ID (Destination) displays the execution ID for this generation.

At this time, if the connection-destination jobnet exists on a different host, the host with the jobnet connector communicates with the host with the jobnet. If the two hosts are managed by different authentication servers, login is required.

When you click Refresh or perform automatic update while the Detailed Schedule dialog box is displayed, login might be required because the host obtains a connection target execution ID or connection source execution ID.

Exec. ID (Destination) displays Unknown when you click Cancel in the Login screen. When Unknown is displayed, redisplay or automatic update of the Detailed Schedule dialog box will not allow the host with the jobnet connector to communicate with the other host where the connection-destination jobnet exists. Therefore, Unknown remains displayed.

If you want to display the execution ID of a connection-destination jobnet in Exec. ID (Destination), click View and then Refresh to update the display.

When the connection between the jobnet connector and the connection-destination jobnet is fixed, this item displays the execution ID of the jobnet without communicating with the host where the connection-destination jobnet exists.

Exec. ID (Source)

Displays the execution ID of the connected jobnet connector for root jobnets only.

A hyphen (-) is displayed for root jobnets for which execution order control is not performed or for remote jobnets.

This item displays None when execution order control is performed but no jobnet connector is connected. This item also displays None when you do not have reference permission for the connected jobnet connector.

This line appears only for root jobnets and root remote jobnets.

Cautionary note

When the connected jobnet connector is under a scheduler service on a different host, you need to start the JP1/AJS3 service on the host with the jobnet connector beforehand.

Supplementary notes

The following table describes whether this item displays the execution ID of a jobnet connector based on the status of the jobnet connector.

Table 12‒53: Status of a jobnet connector and whether its execution ID is displayed
Result/schedule	Generation of connection-destination jobnet	Status of jobnet connector		Execution ID	Execution order control method
Result	Result	No jobnet connector is connected.		N	Y
		A jobnet connector is connected.	The jobnet connector exists.	Y	Y
		A jobnet connector is connected.	The jobnet connector does not exist (deleted when registration is canceled).	Y	Y
Schedule	Fixed	A fixed execution schedule exists for a jobnet connector on the execution day of the connection-destination jobnet.	The unit type of the jobnet connector is correct.	Y	Y
			The unit type of the jobnet connector is invalid.	Y^#	Y
		A dummy schedule exists for a jobnet connector on the execution day of the connection-destination jobnet.		N	Y
		A dummy schedule does not exist for a jobnet connector on the execution day of the connection-destination jobnet.		N	Y
	Dummy schedule	--		N	Y

Legend:

--: Not applicable.

Y: Displayed.

N: None is displayed.

#

When a jobnet connector is defined in a normal nested jobnet (invalid definition), Exec. ID (Source) displays the execution ID of the jobnet connector for a scheduled generation of the connection-destination jobnet. However, the jobnet enters the Ended abnormally status when it is executed because the definition is invalid. To check whether there are any definition errors, perform a definition pre-check.

For jobnet generations without fixed connection, the jobnet connector determines the generation to be connected and Exec. ID (Source) displays the execution ID for this generation.

At this time, if the jobnet connector exists on a different host, the host with the jobnet communicates with the host with the jobnet connector. If the two hosts are managed by different authentication servers, login is required.

When you click Refresh or perform automatic update while the Detailed Schedule dialog box is displayed, login might be required because the host obtains a connection target execution ID or connection source execution ID.

The Status column displays Unknown when you click Cancel in the Login screen. When Unknown is displayed, redisplay or automatic update of the Detailed Schedule dialog box will not allow the host with the jobnet to communicate with the other host where the jobnet connector exists. Therefore, Unknown remains displayed.

If you want to display the execution ID of a jobnet connector in Exec. ID (Source), click View and then Refresh to update the display.

When the connection between the jobnet and the jobnet connector is fixed, the Status column displays the execution ID of the jobnet connector without communicating with the host where the jobnet connector exists.

Exec. order method

Displays an execution order control method for root jobnets only.

You can temporarily change the execution order control method for each generation. This item displays a method as follows.

When the method is not changed:

Follow the definition. (execution order control method) appears.
When the method is changed from Asynchro to Synchro:

Synchro appears.
When the method is changed from Synchro to Asynchro:

Asynchro appears.

A hyphen (-) is displayed for root jobnets for which execution order control is not performed and for remote jobnets.

This line appears only for root jobnets and root remote jobnets.

Waiting

If the unit has wait conditions, this field shows whether the wait conditions are satisfied.

If there are any conditions waiting to be satisfied:

Displays Yes.
If there are no conditions waiting to be satisfied:

Displays No.

This field shows a hyphen if any of the following apply:

The unit has no wait conditions
The connection target is JP1/AJS2 - Manager or a version of JP1/AJS3 - Manager earlier than 09-50
The JP1/AJS3 - Manager database uses the compatible ISAM configuration

Retry status

The following is displayed for Unix jobs, PC jobs, Queue jobs, flexible jobs, HTTP connection jobs, standard custom jobs, custom PC jobs, and custom Unix jobs:

When automatic retry is enabled

Displays retry waiting, retry executing, or retry end. If the job has never been retried, None is displayed.
When automatic retry is disabled

Displays None.

For the following units, a hyphen (-) is displayed:

Units other than the above types
Units whose connection-target JP1/AJS3 - Manager version is earlier than 10-00
Units for which the JP1/AJS3 - Manager database is a compatible ISAM configuration

This item does not appear if either of the following applies:

The version of JP1/AJS3 - View is earlier than 10-00
The unit is a root jobnet, nested jobnet, root remote jobnet, nested remote jobnet, or jobnet connector

Retry execution times

The following is displayed for Unix jobs, PC jobs, Queue jobs, flexible jobs, HTTP connection jobs, standard custom jobs, custom PC jobs, and custom Unix jobs:

When automatic retry is enabled

Displays the number of times the job has been retried. If the job has never been retried, 0 is displayed.
When automatic retry is disabled

Displays 0.

For the following units, a hyphen (-) is displayed:

Units other than the above types
Units whose connection-target JP1/AJS3 - Manager version is earlier than 10-00
Units for which the JP1/AJS3 - Manager database is a compatible ISAM configuration

This item does not appear if either of the following applies:

The version of JP1/AJS3 - View is earlier than 10-00
The unit is a root jobnet, nested jobnet, root remote jobnet, nested remote jobnet, or jobnet connector

Retry start time

The following is displayed for Unix jobs, PC jobs, Queue jobs, flexible jobs, HTTP connection jobs, standard custom jobs, custom PC jobs, and custom Unix jobs:

When automatic retry is enabled

Displays the date and time when the job last entered Now running status as a result of an automatic retry, in the format YYYY/MM/DD hh:mm:ss. If the job has never been retried, None is displayed.
When automatic retry is disabled

Displays None.

For the following units, a hyphen (-) is displayed:

Units other than the above types
Units whose connection-target JP1/AJS3 - Manager version is earlier than 10-00
Units for which the JP1/AJS3 - Manager database is a compatible ISAM configuration

This item does not appear if either of the following applies:

The version of JP1/AJS3 - View is earlier than 10-00
The unit is a root jobnet, nested jobnet, root remote jobnet, nested remote jobnet, or jobnet connector

Retry registration time

The following is displayed for Unix jobs, PC jobs, Queue jobs, flexible jobs, HTTP connection jobs, standard custom jobs, custom PC jobs, and custom Unix jobs:

When automatic retry is enabled

Displays the date and time when the job last entered Waiting to execute status as a result of an automatic retry, in the format YYYY/MM/DD hh:mm:ss. If the job has never been retried, None is displayed.
When automatic retry is disabled

Displays None.

For the following units, a hyphen (-) is displayed:

Units other than the above types
Units whose connection-target JP1/AJS3 - Manager version is earlier than 10-00
Units for which the JP1/AJS3 - Manager database is a compatible ISAM configuration

This item does not appear if either of the following applies:

The version of JP1/AJS3 - View is earlier than 10-00
The unit is a root jobnet, nested jobnet, root remote jobnet, nested remote jobnet, or jobnet connector

Cautionary note

Note the following when you display the Detailed Schedule dialog box for a generation without fixed connection with a jobnet connector or connection-destination jobnet:

When you specify a jobnet connector or a connection-destination jobnet on the host in a different authentication bloc as the connection destination, you might need to log in to the host containing the destination item in order to obtain a connection source execution ID or connection target execution ID.
Because the local host might need to communicate with the host containing the connection destination unit, you need to start the JP1/AJS3 service on the host with the connection destination item beforehand. If the JP1/AJS3 service is not active, a communication error occurs. You cannot perform other operations before a communication error is detected.

To Page Top