| Previous | TContents | YIndex |
E SCHEDULE allows you to specify which jobs must be completed C before another job is initiated, as well as to define which are to H start when a current job ends. This allows conditional branching within C a job set without recourse to complex application programming, and F provides the ability to handle `interdependencies'. A wide variety of E `if-then-else' scenarios can be specified between jobs, enabling the E system manager to build in automatic error correction when a program fails.
H Applications can be developed into highly reliable `fault tolerant' job F sets, which are ideally suited to the emerging trend for `lights out' @ operations and `hands off' solutions. By taking remedial action E automatically when a fault occurs and re-running the jobs through to E their termination, SCHEDULE eliminates the need for regular H operator attendance, and makes applications effectively self-correcting. 2 1.5.1 Initiate jobs
G A job can have any number of initiate jobs. On the completion > of a job all initiate jobs are readied for execution.
/ Figure 1-1 Initate Job example
= For example in Figure 1-1 H when Job A completes, Job B is readied and is immediately submitted for ? execution. When Job B completes Jobs C and D are ready and are $ submitted immediately for execution.
D Each initiate branch can be conditioned only to occur under certain F circumstances. The conditions are based on the completion code of the C job. The severity level (success, warning, error and fatal) or the + numeric value of the code can be specified. 6 1.5.2 Prerequisite jobs
F A job can have any number of prerequisite jobs. A job cannot # be submitted into a queue until all . prerequisite jobs have completed successfully.
4 Figure 1-2 Prerequisite job example
k For example in Figure 1-2 Job D cannot be submitted until Jobs B and E C have completed successfully. Job B cannot be submitted until Job A has completed successfully. S 1.5.3 Combinations of initiates and prerequisites
F A combination of prerequisite and initiate jobs can ! be used to control a set of jobs.
F Figure 1-3 Combination of Initiates and Prerequisites
2 In Figure 1-3 A Job A is used to trigger the entire set of jobs. Job B and C are D immediately submitted on the completion of Job A. Job D even though H readied for execution by the completion of Job A will wait until Jobs B G and C are completed before it is submitted into a queue. On completion + of Job D, Job E is submitted for execution. P 1.6 Rescheduling methods
A SCHEDULE allows you to select which jobs are to be run, E specify their start times and to schedule them at regular intervals, H define a specific day of the week or month to initiate the job. You can D also create schedule calendars that recognize national holidays and ? weekends when jobs are not to run, as well as fiscal calendars.
H The flexibility of SCHEDULE is ideal for customizing jobs to a F company's specific requirements and for multi-national companies with H distributed processing who need to allow for varying national holidays. H You can also instruct SCHEDULE not to run jobs until a minimum H amount of disk space is available or until required files are available & ensuring fast and reliable processing.
| Previous | VNext | TContents | YIndex |