| Previous | TContents | YIndex |
? Included with the SCHEDULE System are some predefined 7 calendars and a procedure to create some demonstration : jobs1. The demonstration jobs are grouped into ' subdirectories of the [DEMO] directory.
B The jobs grouped into the [DEMO.D] subdirectory are configured to @ simulate the task of the daily updating of a database. This job C sequence is divided into three groups of jobs. In brief, the first H group backs up the database, the second group updates the database, and H the third group does the final reporting on the results of the database update.
D The first part of this section describes the job flow for the daily E database update, identifying each job and describing the function of F that job. The next part of this section gives the complete set of DCL A commands to create and configure each job. The last part of this D section describes running the job sequence and reviewing the events that occurred during execution.
G In this section, DCL commands will be used to illustrate how the daily > database update job sequence was created, configured, and run.
| N L 1 To build the demonstration jobs, I issue the following command:@SCHEDULE_LIBRARY:SCHEDULE_DEMO. |
> The complete job flow of the three groups of jobs is shown in F Figure 5-1 Complete Job Flow.
- Figure 5-1 Complete Job Flow
A The first group consists of three sequential jobs to back up the Z database, as shown in Figure 5-2 First Group of Jobs.
/ Figure 5-2 First Group of Jobs
D Every day at a preset time, job A1 is scheduled to be submitted and E run. When run, job A1 checks to see if the database is available for G updating. If this check fails, the complete job sequence is exited. If F the check succeeds, job A2 is initiated. Job A2 backs up the database D to allow for recovery from errors in the subsequent updating of the G database. When job A2 successfully completes, job A3 is initiated. Job E A3 does no operation but just serves as a return point used in error A recovery. Since job A3 does no operation, it always succeeds and F initiates job B1, the first job of the second group. The second group G consists of five sequential jobs to update the database and three jobs i used in error recovery, as shown in Figure 5-3 Second Group of Jobs.
0 Figure 5-3 Second Group of Jobs
@ Job B1 does the initial update of the database. Upon successful H completion, job B21 is initiated to do the main update to the database. B If this job fails, job C is initiated. Job C restores some of the D database from the backup files and then initiates jobs in the third E group of jobs. If job B21 succeeds, job B22 is initiated to sort the F output of the database update. If job B22 fails due to the disk being H full, job D is initiated. Job D purges files and then initiates job B22 @ again. This loop continues until job B22 succeeds. Upon job B22 C succeeding, job B23 is initiated to do the final processing in the 3 database update. If this fails, job E is initiated.
F Job E completely restores the database from the backup files and then D initiates the last job of the first group, job A3, to start another ? pass at updating the database. If job B23 succeeds, job B24 is F initiated. Job B24 prints out the results for the successful database : update and then initiates jobs in the third group of jobs.
| Previous | VNext | TContents | YIndex |