cDSCHEDULE Automated Job Submission System Guide and Reference �ManualD

SCHEDULE
Automated Job Submission System
Guide and Reference Manual



 o T Y  
PreviousContentsIndex

/

2.1.11 Held up by



<The held-up-by list that is associated with each job in the FSCHEDULE database specifies all jobs that reference this job >on their prerequisite list. The held-up-by list is the inverseGof the prerequisite list. This list can be manually updated if needed. ?Normally only the prerequisite list is modified and the system *automatically updates the held-up-by list.

FThe SCHEDULE REBUILD command can be used to recreate the activated-by "and held-up-by lists for all jobs.3

2.1.12 Distrib list



?The distribution list is a list of PRINT commands to be issued.DThe idea is to provide a central mechanism for maintaining the `how 8many, where to and what printer' information in a common3location separate from the main DCL command stream.

BEach statement appears on a separate line in the notice list. The &format of each line is detailed below:

 

"
 General format:  %    $ DCL_command [/qualifiers] 'Pn'  where:       command  - a single command 1    qualifiers  - can be any group of qualifiers !    Pn   - any parameter P1...P8  




EThe command can be any command. The more common ones would be PRINT, EMAIL, or COPY. A typical distribution list can be displayed by using the command:

 

"
 .$ SCHEDULE TYPE/DISTRIBUTION [DEMO.A]REPORT_3  [DEMO.A]REPORT_3.distribution  *$ PRINT/QUEUE=SPECIAL/FORM=LANDSCAPE 'P1'  "$ PRINT/COPIES=2/PAGES=(1,3) 'P1'   $ MAIL 'P1' SYSTEM_MANAGER    




FThe distribution processing is invoked by using the following type of command.

 

"
 B$ SCHEDULE_DISTRIBUTE 'SCHEDULE_FULL_NAME' REPORT_1 [REPORT_2...]    




GThe above command is inserted into the main body of DCL commands after $the report files have been produced.

HOne useful variation on this is to set aside a special job that is then Fused by many other jobs to control how they distribute printouts. For Eexample, create a job called ACCOUNTING_DEPARTMENT. In this job just Fset up a distribution list. In all jobs that generate reports for the 7accounting department just enter the following command.

 

"
 8$ SCHEDULE_DISTRIBUTE ACCOUNTING_DEPARTMENT REPORT_FILE    




AIn this way if a change is made to the distribution list an edit -operation only needs to be done in one place.4

2.1.13 Startup window



GEach job can be assigned a startup window interval. The startup window 1is used by jobs that are waiting for a start timeEin the scheduling queue B. This interval represents the allowed time 5period during which a job must exit from the B queue.

GAs an example, a job is set to start at 12:00. The system goes down at D11:50 and comes back up at 12:30. When the system comes back up the Gscheduler decides whether or not to actually start the 12:00 job based Fon the window interval. The job is now 30 minutes behind schedule. If Gthe window interval is 30 minutes or greater the job is started. If it <is less then 30 minutes then it is NOT started. 4

GThe main objective of the startup window is to allow a system that has ?been down to gracefully catch up and not create unnecessary or undesired batch jobs.



/   
N
Note

 N

4 A value of `not set' is equivalent - to an infinite window interval.








 o V T Y  
PreviousNextContentsIndex