| Previous | TContents | YIndex |
m To configure the job flow as shown in Figure 5-1 Complete Job Flow, A the initiate and prerequisite relationships between jobs must be established.
B To edit the initiate list for each job, use the following command:
|
" ' $ SCHEDULE EDIT [DEMO.D]B21 /INITIATES |
> Within the editor, enter the jobs to be initiated by this job:
|
" B22,SUCCESS C,FAILURE |
D To edit the prerequisite list for job H, which is the only job that requires G a prerequisite, follow the same procedure using prerequisites 2 in place of initiates within the command.
H To view the initiate and prerequisite lists, use the following commands:
|
" % $ SCHEDULE TYPE [DEMO.D]* /INITIATES [DEMO.D]A1.initiates A2,SUCCESS [DEMO.D]A2.initiates A3,SUCCESS [DEMO.D]A3.initiates B1,SUCCESS [DEMO.D]B1.initiates B21,SUCCESS [DEMO.D]B21.initiates C,FATAL B22,SUCCESS [DEMO.D]B22.initiates D,CODE=7389215 B23,SUCCESS [DEMO.D]B23.initiates E,FATAL B24,SUCCESS [DEMO.D]B24.initiates G,SUCCESS F,SUCCESS [DEMO.D]C.initiates H,SUCCESS F,SUCCESS [DEMO.D]D.initiates B22,SUCCESS [DEMO.D]E.initiates A3,SUCCESS [DEMO.D]F.initiates [DEMO.D]G.initiates H,SUCCESS [DEMO.D]H.initiates I,SUCCESS [DEMO.D]I.initiates J,FATAL [DEMO.D]J.initiates ) $ SCHEDULE TYPE [DEMO.D]H /PREREQUISITES [DEMO.D]H.prerequisites F |
B The same information about the initiates and prerequisites can be 1 viewed within the MOTIF Editor/Monitor, as below.
G See the chapter on the MOTIF Editor/Monitor for a complete description ( of the editing and viewing capabilities. 9 5.2.3 Specify job actions
F Each job has a DCL command list that can be edited to specify the DCL * commands to be executed when the job runs.
E To edit the command list for each job, use the following DCL command:
|
" % $ SCHEDULE EDIT [DEMO.D]A1 /COMMANDS |
D Since this job sequence is only simulating the task of updating the D database, within the editor only the DCL command to wait is entered:
|
" $ WAIT 'P1' |
? The 'P1' part of the wait command is the standard command file E variable. This variable is supplied as a submit parameter for all of 2 the jobs in [DEMO.D] by the following DCL command:
|
" 9 $ SCHEDULE MODIFY [DEMO.D]* /SUBMIT=PARAMETER:"00:00:30" |
G Up to eight submit parameters can be entered in this way. This sets up E each job to simply wait for 30 seconds before initiating the jobs in H the initiate list of that job. The only exception is that job A3, which D just serves as a return point in the job flow, has an empty command ! list and therefore will not wait.
G To view the command lists and submit parameters, use the following DCL commands:
|
" # $ SCHEDULE TYPE [DEMO.D]*/COMMANDS [DEMO.D]A1.commands $ WAIT 'P1' [DEMO.D]A2.commands $ WAIT 'P1' [DEMO.D]A3.commands [DEMO.D]B1.commands $ WAIT 'P1' [DEMO.D]B21.commands $ WAIT 'P1' [DEMO.D]B22.commands $ WAIT 'P1' [DEMO.D]B23.commands $ WAIT 'P1' [DEMO.D]B24.commands $ WAIT 'P1' [DEMO.D]C.commands $ WAIT 'P1' [DEMO.D]D.commands $ WAIT 'P1' [DEMO.D]E.commands $ WAIT 'P1' [DEMO.D]F.commands $ WAIT 'P1' [DEMO.D]G.commands $ WAIT 'P1' [DEMO.D]H.commands $ WAIT 'P1' [DEMO.D]I.commands $ WAIT 'P1' [DEMO.D]J.commands $ WAIT 'P1' 0 $ SCHEDULE DIRECTORY [DEMO.D]*/SUBMIT=PARAMETER Job directory [DEMO.D] A1 "30","","","","","","","" A2 "30","","","","","","","" A3 "30","","","","","","","" B1 "30","","","","","","","" B21 "30","","","","","","","" B22 "30","","","","","","","" B23 "30","","","","","","","" B24 "30","","","","","","","" C "30","","","","","","","" D "30","","","","","","","" E "30","","","","","","","" F "30","","","","","","","" G "30","","","","","","","" H "30","","","","","","","" I "30","","","","","","","" J "30","","","","","","","" Total of 16 jobs |
| Previous | VNext | TContents | YIndex |