Rules for creating applications
This section outlines the basic rules that govern standard applications and group definitions. The panels prevent you from breaking these rules.
A group
definition is the central member
in an application group. It groups related
applications as a unit, holding common run cycles and calendar information
for all applications in the group. The benefits are that you:
- Can perform modify actions on the group as a single unit within the plan instead of having to perform actions on many individual applications. This makes it simpler to add, delete, and complete many applications at once.
- Maintain only a single source for run cycle and calendar information. Maintaining your application description database is simpler and less prone to error.
| Specifications | Standard application | Group definition |
|---|---|---|
| How many operations can it have? | From 1 to 255, each with an operation number in the range 001 to 255, all directly or indirectly linked to each other, and in such a way that they do not form a loop. | None directly, but it has applications, each of which can have 255 operations |
| How do you get HCL Workload Automation for Z to schedule it? | Specify the calendar name (if you are not using the default calendar) and the run cycles | Specify the calendar name (if you are not using the default calendar) and the run cycles. The applications that belong to the group must not specify these. |
| What fields must you specify?
(Values for type, priority, valid-from date, and status are stored in your ISPF profile and are used as default values when you next use the panel.) |
|
|