Work Scheduling:
CA-7 uses both date/time-driven and event-driven facilities to cause work to be scheduled and initiated. In CA-7, work is defined as CPU jobs, preprocessing and postprocessing workstation networks.
Event-driven scheduling, known as trigger scheduling, is a far more efficient technique than date/time oriented schedules.
For CPU jobs and preprocessing networks, date/time-driven schedules are generated through definition of base calendars and definition of schedules relative to base calendars. Once defined, work is automatically scheduled based on defined schedules and current date and time values within the CA-7 system. For postprocessing networks, output workstations are scheduled based on the scheduling of the CPU job to which the networks are connected.
Event-driven scheduling causes jobs to be scheduled or initiated based on completion of a previous activity or event. Event mechanisms are the creation of required data sets, completion of predecessor jobs, or completion of a preprocessing network.
Time-driven and event-driven facilities can be used in combination when scheduling and initiating work. For example, a CPU job can have a timed schedule for processing but can also have dependencies on data sets created by another job. When combined, time and event requirements must be satisfied before work is initiated.
The user should be aware that the schedule ID offers a powerful scheduling tool. Requirements, networks, JCL overrides, job triggers, etc can all be varied through the use of different schedule IDs.
For example, if a given job is to run on Monday through Friday but the requirements vary on Fridays, this same job could have a different schedule ID defined for its Friday run. Multiple schedule options can be chosen for a single schedule ID (daily and monthly). However, a job that is scheduled automatically on a defined date/time basis is not scheduled more than once per day for a given schedule ID.
CA-7 uses both date/time-driven and event-driven facilities to cause work to be scheduled and initiated. In CA-7, work is defined as CPU jobs, preprocessing and postprocessing workstation networks.
Event-driven scheduling, known as trigger scheduling, is a far more efficient technique than date/time oriented schedules.
For CPU jobs and preprocessing networks, date/time-driven schedules are generated through definition of base calendars and definition of schedules relative to base calendars. Once defined, work is automatically scheduled based on defined schedules and current date and time values within the CA-7 system. For postprocessing networks, output workstations are scheduled based on the scheduling of the CPU job to which the networks are connected.
Event-driven scheduling causes jobs to be scheduled or initiated based on completion of a previous activity or event. Event mechanisms are the creation of required data sets, completion of predecessor jobs, or completion of a preprocessing network.
Time-driven and event-driven facilities can be used in combination when scheduling and initiating work. For example, a CPU job can have a timed schedule for processing but can also have dependencies on data sets created by another job. When combined, time and event requirements must be satisfied before work is initiated.
The user should be aware that the schedule ID offers a powerful scheduling tool. Requirements, networks, JCL overrides, job triggers, etc can all be varied through the use of different schedule IDs.
For example, if a given job is to run on Monday through Friday but the requirements vary on Fridays, this same job could have a different schedule ID defined for its Friday run. Multiple schedule options can be chosen for a single schedule ID (daily and monthly). However, a job that is scheduled automatically on a defined date/time basis is not scheduled more than once per day for a given schedule ID.
Posts
No comments:
Post a Comment