Job Management Partner 1 Version 10, Job Management Partner 1/Automatic Job Management System 3 Operator's Guide
![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
15.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 15-191 Detailed Schedule dialog box
![[Figure]](FIGURE/ZV140770.GIF)
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.
- 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.
- The Status column displays None when no jobnet is connected. The Status column also displays None when you do not have reference permission for 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
- 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
- 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, 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, 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, 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, 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.
Copyright (C) 2012, Hitachi, Ltd.
Copyright (C) 2012, Hitachi Solutions, Ltd.