CA WA CA 7 Edition uses date and time-driven and event-driven schedules and processes on-demand work. We recommend event-driven scheduling, known as triggering. Event-driven scheduling is a far more efficient technique than date and time-oriented schedules or on-demand processing. Try to have the following balance:
Scheduling is the heart of CA WA CA 7 Edition. The best time to schedule is always the closest to the event that causes the job to require processing. Most jobs rarely run at a specific time on a specific day because of waiting on other jobs, data sets, and so on. Usually jobs run because their data is ready for processing or data is required to be ready for processing because of file closures or updates. Use data set or job triggers and requirements to sequence the execution instead of date and time scheduling of these types of jobs.
Schedule IDs (SCHIDs) are used to denote variations in jobs’ schedules, processing, or both. Requirements, networks, JCL overrides, job triggers, and so on, can all be varied by using 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.
For flexibility, it is best not to assign a meaning to a particular SCHID.
Business Value:
Follow these guidelines for using scheduling techniques, which provide the greatest flexibility in scheduling your production workload.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|