Job Management Partner 1/Automatic Job Management System 3 Operator's Guide
When jobnets are nested, you can copy the schedule rules from the upper-level jobnet to the lower-level jobnet. The following shows how to copy the schedule rules to a jobnet from its upper-level jobnet.
To copy the schedule rules to the jobnet from the upper-level jobnet:
- In the JP1/AJS3 - View window, in Function Menu, click Schedule Definition.
Schedule Definition is now selected.
- In the list area, click the root jobnet of the jobnet for which a schedule needs to be defined.
The root jobnet you clicked is now selected.
- Choose Edit and then Edit, or double-click the root jobnet.
The Jobnet Editor window appears.
- In the tree area of the Jobnet Editor window, click a nested jobnet and choose Edit and then Schedule.
The Schedule Settings dialog box appears.
- Click the Copy Upper button.
A message dialog box appears for confirming that the schedule rules of the upper-level jobnet will be copied.
- Click the Yes button.
The schedule rules of the upper-level jobnet are copied.
- Click the OK button.
The Schedule Settings dialog box is closed.
- Cautionary notes
- If schedule rules have already been set in the jobnet to which you want to copy the schedule rules from the upper-level jobnet, the existing schedule rules are lost.
- You cannot copy the following items from the upper-level jobnet:
- Linked rule number in the Schedule rules list
- Exclusive jobnet specified in the Options group with Exclusive schedule check box selected
- Supplementary notes
- You can click Copy Upper button only when all the following conditions are satisfied:
- The Schedule Settings dialog box was displayed with a lower-level jobnet specified
- Depends on upper-level jobnet is not selected
- If Depends on upper-level jobnet is selected in the upper-level jobnet, the schedule rules of the jobnet one level upper are referenced. The upper-level jobnets can be referenced and referenced up to the root jobnet.
Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.