cDSCHEDULE Automated Job Submission System Guide and Reference �ManualD

SCHEDULE
Automated Job Submission System
Guide and Reference Manual

o T Y

2.1.16 Job sets

HA job in the SCHEDULE database is essentially a self-contained Fprocessing unit. All the information needed to perform the processing is defined for eachCjob in the control file. A group of jobs can be grouped into a set.

FA set of jobs is just a collection of jobs that are connected to each 7other using either prerequisites or initiates. They canDbe in the same or different directories. They can be on the same or different nodes in a network.

BThree bits of information are passed between members of a job set Gduring execution to control and coordinate the processing. This allows Gfor multiple invocations of the same job set processing different data 0without any interference between them. They are:

Set id. - The set id. is just a number that is assigned . to the first job that starts up the job set.FThis number can be manually specified or the system can automatically Hassign one. ⁶
This value is available to the job through the DCL symbol SCHEDULE_SET_ID.H
Set parameter - The set parameter is just text data (up ' to 56 characters) that is passed intoHeach job as it starts to execute. It is available to the job as the DCL Fsymbol SCHEDULE_SET_PARAMETER. This value is established by the first Gjob in the job set that is initiated. Later jobs can modify this value.G
Set tag - The set tag is also just text data (up to 32 J characters) that is passed into each job as it starts to execute. It is : available to the job as the DCL symbol SCHEDULE_SET_TAG.FThe only difference between the tag and the parameter is that the tag Dpicks up its initial value from the control file. When a job set is .first initiated and no tag value is explicitlyDprovided then this value is picked up from the job tag field of the control data.

2.1.16.1 Using set parameters

@The set parameter is used to pass information between jobs. For Dexample, we have set up a series of three jobs (JOB1, JOB2 and JOB3 Ceach initiates the next job) that process a given data file into a Breport. To start up the series and send along the file name use a command of the following format:

"
?$ SCHEDULE SUBMIT JOB1/SET_PARAMETER="DATAFILE1.DAT"/INITIATES

FThe /INITIATES qualifier is present so that all initiate jobs will be <triggered on completion. (The default behavior of the submit8command is to just run the one job independently of all interconnections.)

AThe first job (JOB1) reads and processes the input data file and Cgenerates an output file which is then processed by the second job G(JOB2). The DCL commands for the first job (JOB1) would look something like the following.

"
-$ DEFINE INPUT_FILE 'SCHEDULE_SET_PARAMETER' $ RUN PROCESS_DATA_PROGRAM $! $! PASS THE DATA TO JOB2 $! 0$ SCHEDULE MODIFY/QUEUE/ENTRY='SCHEDULE_ENTRY'- # /SET_PARAMETER="OUTPUT.DAT"

N Note

⁶ The automatically assigned numbers + are in the range 1 to 99,999.

o V T Y

Contents

Index

SCHEDULE Automated Job Submission System Guide and Reference Manual

2.1.16 Job sets

2.1.16.1 Using set parameters

6 The automatically assigned numbers + are in the range 1 to 99,999.

SCHEDULE
Automated Job Submission System
Guide and Reference Manual

⁶ The automatically assigned numbers + are in the range 1 to 99,999.