cDSCHEDULE Automated Job Submission System Guide and Reference �ManualD

SCHEDULE
Automated Job Submission System
Guide and Reference Manual



 o T Y  
PreviousContentsIndex



@The third group consists of two jobs which together control the Einitiation of three sequential jobs to do the final reporting on the kresults of the database update, as shown in Figure 5-4 Third Group of Jobs.

/Figure 5-4 Third Group of Jobs




EThe normal initiation of jobs in the third group occurs when job B24 Efrom the second group of jobs succeeds, at which time both job F and Ejob G are initiated. Job F prepares a report on the database status. GJob G updates the snapshot of the database at remote nodes. When job G Asuccessfully completes, job H is initiated, but since job F is a Aprerequisite for job H, job H must wait until job F successfully completes.

EThe abnormal initiation of jobs in the third group occurs when job C Gfrom the second group successfully completes, at which time both job F <and job H are initiated. Again, job H must wait until job F ?successfully completes since job F is a prerequisite for job H.

FJob H prints out a report on the snapshot status at the remote nodes. EWhen job H successfully completes, job I is initiated. Job I updates Fthe weekly summarization data report. If job I succeeds, the complete Btask has finished. If job I fails, job J is initiated to log this failure.W

5.2 Create and configure jobs



CIn this section, DCL commands are used to illustrate how the daily 8database update job sequence was created and configured.@

5.2.1 Create directory and jobs



CAs the first step, directory [DEMO.D] and each of the jobs must be created.

?To create the [DEMO.D] directory for the job sequence, use the following DCL command:

 

"
 %$ SCHEDULE CREATE/DIRECTORY [DEMO.D]    




HTo create the jobs for the daily database update, use the following DCL commands:

 

"
 $ SCHEDULE CREATE [DEMO.D]A1- 3_$/GENERAL=COMMENT:"Startup check before database" $ SCHEDULE CREATE [DEMO.D]A2- )_$/GENERAL=COMMENT:"Backup the database"     .   .   . $ SCHEDULE CREATE [DEMO.D]I- =_$/GENERAL=COMMENT:"Update weekly summarization report data" $ SCHEDULE CREATE [DEMO.D]J- @_$/GENERAL=COMMENT:"Log failure of weekly summarization update"    




HTo confirm which jobs have been created, use the following DCL commands:

 

"
 $ SCHEDULE DIRECTORY [DEMO.D]*  Job directory [DEMO.D]      A1 A2 A3 B1 B21 B22 B23 B24 C D E F G H I J  Total of 16 jobs  /$ SCHEDULE DIRECTORY [DEMO.D]*/GENERAL=COMMENT  Job directory [DEMO.D]     (A1 Startup check before database update A2 Backup the database .A3 Place holder for after backup the database "B1 Initial update of the database  B21 Main update to the database 'B22 Sort the output of database update (B23 Final processing of database update 4B24 Print out results of successful database update -C Restore some of database from backup files 4D Purge files to make room for database sort output  E Restore backup to allow retry $F Prepare report on database status .G Update snapshot of database at remote nodes &H Print out report of snapshot update *I Update weekly summarization report data -J Log failure of weekly summarization update  Total of 16 jobs  









 o V T Y  
PreviousNextContentsIndex