When you select an individual
application you want to add to the
current plan, HCL Workload Automation for Z displays
the following panel:
Note: If you are using the advanced panels, you can also add occurrences by selecting Add
in the Action menu of the OPERATIONS IN THE CURRENT PLAN panel. For more information, see List of administrative tasks available from
the Action menu.
Any
values specified on the ADDING APPLICATIONS TO THE CURRENT PLAN panel
(see EQQMADDP - Adding
Applications to the Current Plan panel) are
carried forward to this panel. The priority is extracted from the
application description. The panel indicates the number of operations
in the occurrence and the number of external predecessors.
The scheduler does
not accept any command, except CANCEL, until the input arrival and
deadline dates and times are specified. If you want the input arrival
time to be the current time, you can either specify the necessary
time or press Enter. The scheduler uses
the current time as default for the input arrival time. If you press
Enter again, HCL Workload Automation for Z uses
the current date as default for the deadline date.
You can use
the ISPF command delimiter to set up a chain command
to do this quickly. For example, if you type ;;; and
press Enter, the panel is re-displayed with the cursor at the deadline
time field. All other date and time fields are set by HCL Workload Automation for Z.
Note: If the added application has a run cycle defined, the input arrival and deadline time is taken
from the first run cycle description. If you try to add an application with the same date and
time as another occurrence of the same application already in the plan (even if deleted or
completed), HCL Workload Automation for Z rejects
it. If you mean to do this, change the time by one minute until the added occurrence is unique.
But be careful if you want HCL Workload Automation for Z to resolve external
dependencies: external dependencies can depend on the input arrival time of the added occurrence.
For example, if application B depends on application A, what happens if you add an extra
occurrence of A and B? When you add A, you must give its occurrence a different input arrival
time to the regular occurrence. When you add B, you give its occurrence the same or later input
arrival time, and it should become dependent on the added occurrence of A, because that is the
closest occurrence with an equal or earlier input arrival time. See Including dependencies defined in the database for a description of how dependencies are resolved when
there are several candidates. But you can have problems if the operations in A and B have
explicit input arrival times: these are not affected by the occurrence input arrival time that
you specify on the ADDING AN APPLICATION TO THE CURRENT PLAN panel, and you should alter these
dependencies manually. For details, see Changing external dependencies to an occurrence.
You can use the DEP and OPER commands to alter dependencies
and
operation details for this occurrence. When you have specified all
the occurrence information, add it to the current plan by issuing
the END command.
Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.