cDSCHEDULE Automated Job Submission System Guide and Reference �ManualD

SCHEDULE
Automated Job Submission System
Guide and Reference Manual

o T Y

GFor example to establish 15 minutes as the startup window for your job !MYJOB use the following commands.

"
5$ SCHEDULE MODIFY MYJOB/GENERAL=STARTUP_WINDOW:00:15

9

2.1.14 Execution window

FThe execution window is the interval in which a job must be initiated Hand completed. If a job goes beyond this window then any initiates that (it might have started are not activated.HIf you look at the scheduling queues this is the time it takes a job to ,travel from the C or D queue to the M queue.

FAs an example, a series of linked batch jobs A, B, and C were started Gon Monday morning. Normally A initiates B and B initiates C. The A job His submitted and then it activates the B job. Due to an error the B job Bis placed in the PENDING state and forgotten. On Thursday someone Fnotices that the B job is still on the system and PENDING. They start Hthe job. Unknown to him this job is no longer needed. The B job has now Fbeen in the system for 3 days. If the execution window is set to less Hthen 3 days the C job will NOT be started when the B job terminates. If Bit had been set to 3 days or greater the C job would be activated.

DThe objective of the execution window interval is to allow a system that hasHbeen down or work that has been postponed for a lengthy time a graceful 9method for catching up without creating extra batch jobs.

GFor example to establish 12 hours as the execution window for your job (MYJOB use the following type of command.

"
2$ SCHEDULE MODIFY MYJOB/GENERAL=EXECUTE_WINDOW:12

2.1.15 Pre/Post COM files

HFor each job two command files can be defined. The pre-job command file 9is a file that contains a series of DCL commands that areGto be executed before the job's own DCL commands. The post-job command Hfile is executed afterwards. This is a useful place for operations that 9are common to all jobs (or a family of jobs)⁵.

FBy modifying your local default job you can have a common pre-job and Fpost-job command added automatically to each new job that you create. HFor example, to have the file START_JOB.COM execute at the beginning of ;each new job that you create use the following the command.

"
C$ SCHEDULE CREATE DEFAULT/GENERAL=PRE_COM_FILE:SYS$LOGIN:START_JOB $ SCHEDULE CREATE NEW_JOB

@When the NEW_JOB is initiated and enters an execution queue the ?temporary command file contains the following type of commands.

"
$ @SYS$LOGIN:START_JOB ... job commands ...

FBoth the pre and the post command file should be set up in such a way Gas to always complete with a success status code. In this way the main 2procedure will always get a chance to do its work.

BTo include the actual contents of a PreCom or PostCom file in the 9temporary command, use a command of the following format:

"
>$ SCHEDULE CREATE DEFAULT/GENERAL=PRE_COM_FILE:"I myfile.COM"

GThe "I" indicates that the contents of "myfile.COM" are to be included .into the temporary COM file that is submitted.

N Note

⁵ In a Satellite-Central network M configuration be sure that these pre/post command files exist on all O systems. Only the commands that are contained in the SCHEDULE 0 Database are copied across the net.

o V T Y

Contents

Index

SCHEDULE Automated Job Submission System Guide and Reference Manual

2.1.14 Execution window

2.1.15 Pre/Post COM files

5 In a Satellite-Central network M configuration be sure that these pre/post command files exist on all O systems. Only the commands that are contained in the SCHEDULE 0 Database are copied across the net.

SCHEDULE
Automated Job Submission System
Guide and Reference Manual

⁵ In a Satellite-Central network M configuration be sure that these pre/post command files exist on all O systems. Only the commands that are contained in the SCHEDULE 0 Database are copied across the net.