AD database
The basic unit of information
in the AD database is an application description (AD), containing
all the
information about one application. An AD can contain:
- General information
- This section contains information, such as the application name, status, and owner, which uniquely identifies the application and must appear only once in each AD. You build this section with an ADSTART control statement.
- Run cycle definitions
- These definitions describe when the application should run, such as daily or weekly. The IBM® Z Workload Scheduler planning functions convert this information into calendar run dates. There can be more than one run cycle in each AD; for example, if a particular application must be run daily with an additional run at the end of each week. You specify a run cycle with an ADRUN control statement.
- Operations
- An application usually consists of a series of related operations,
such as:
- JCL setup
- Execution of a job or started task
- Printing and dispatch of reports
Each operation is described by its own section, which contains a unique operation number and the name of the workstation. There are normally multiple operation sections in each AD. You build an operation section with an ADOP control statement.
An operation section can have one or more of these subsections:
- Dependencies
- Each operation in an application can have one or more dependencies, or predecessor operations, which must be completed before it can start. A predecessor operation can be part of the same occurrence of the application (internal dependency), part of another application (external dependency), or part of another occurrence of the same application (external dependency). Within each operation section in the AD, there can be one or more dependency subsections, one for each dependency. You create a dependency subsection with an ADDEP control statement. You can also add application or operation dependencies with the ADAPD control statement.
- Special resources
- Each operation can use one or more special resources. A special resource subsection contains details of how the operation uses the resource. There can be one or more resource subsections within each operation section. You create a resource subsection with an ADSR control statement. For information about special resources, see Creating special resources.
- Operation Extended Info
- Within an application every operation can have its own
extended
information area, so that there can be one operation extended name
subsection per operation. You create or delete an operation extended
information subsection with an ADOPEXTN control statement. The extended
information area contains two types of information:
- Extended job name
- Scheduling Environment name
- System Automation Info
- Within
an application every operation can have its own System
Automation information area, so that there can be one operation system
automation subsection per operation. The subsection is present only
for operations running on automation workstations. The System Automation
information area contains the following data:
- Command text
- Automated function
- Security element
- Completion information
- User Fields
- Each operation can use one or more user fields. A user field subsection contains details about user field name and value. There can be one or more user fields subsections within each operation section. You create a user field subsection with an ADUSF control statement.
- Remote Job Info
- Within an
application, every operation can have their own Remote
Job information area. The subsection is present only for operations
running on remote workstations. The Remote Job information area contains
the following data:
- ADID or job stream name
- Operation number (IBM Z Workload Scheduler only)
- Job stream workstation (IBM Workload Scheduler only)
- Job name (IBM Workload Scheduler only)
- Complete on failed bind (Y | N)