| Previous | TContents | YIndex |
F The basic idea is to modify the STEP number as a job proceeds. At the G beginning of the job a check is made for the RESTARTING flag, if it is set then a GOTO is done to D the correct step. A typical command sequence that uses this process would appear as follows:
|
" 8 $ IF SCHEDULE_RESTARTING THEN GOTO STEP_'SCHEDULE_STEP' $! $STEP_1: 6 $ SCHEDULE MODIFY/QUEUE/ENTRY='SCHEDULE_ENTRY'/STEP=1 $ RUN PROGRAM1 $! $STEP_2: 6 $ SCHEDULE MODIFY/QUEUE/ENTRY='SCHEDULE_ENTRY'/STEP=2 $ RUN PROGRAM2 $! |
; The above method is excellent for handling certain types of H failures. Another method that also can be used to handle failures is to H assign an initiate list to the job. On that initiate list provide a job G with a condition level of FATAL and/or ERROR. This error job will then G be started whenever the job fails (or still fails after exhausting all allowed restarts). V 2.2 Other scheduling features
B Several other features of SCHEDULE are explained in more ! detail in the following sections. X 2.3 EnterpriseSCHEDULE Workgroups
A EnterpriseSCHEDULE features the concept of workgroups. Workgroup a commands are detailed in Chapter 12. The basic functions of Workgroups are to:
A It is recomended that Workgroup configuration and maintenance be H performed in the EnterpriseSCHEDULE Windows Client. The client E features a Wizard that makes the setup of a Workgroup a simple task. C This section is included to explain the concepts behind Workgroups H only. See Windows Client documentation for instructions on working with Workgroups. |
= Workgroups feature the capability to apply load balancing to F EnterpriseSCHEDULE job flow by determining the best way to distribute @ workload. For instance you can apply more job runs to your more E powerful servers and allow the jobs to run across multiple machines, F alleviating the load on a single server. This can all be automated by G establishing several simple parameters to the Workgroup which the jobs are running in.
? A workgroup is considered to be 2 or more nodes in a networked G environment that can have duplicate versions of the EnterpriseSCHEDULE @ database (through automated replication) and/or facilitates the $ execution of jobs on multiple nodes. 7 2.3.1 Creating a Workgroup
H All Workgroups are created in the [SYSCONTROL.WORKGROUPS] folder in the H EnterpriseSCHEDULE database. You must have All Access rights to create, H modify, delete or copy and paste a workgroup. To create a new Workgroup:
A The workgroup can now be configured to replicate job data and/or distribute job activity.
| Previous | VNext | TContents | YIndex |