Unicenter CA-Scheduler Job Management for VSE User Guide

3.9 Defining Jobs
SCHD-JRR RESOURCE DEFINITION Scheduler
===> MASTER - WR
CONNECT : 4
JOB NAME : IH7D2 PROTOTYPE JOB: JNO: STN:
JOB NUMBER : 1 PROTOTYPE JOB IN SCHEDULE :
STATION ID : 4
SCHEDULE NAME : BACKUP
MAX CPU TIME : ROUTE DELAY :
SEPARATE DSNAME:
SEPARATE JOBS
LIST:
DASD1 : 338,2 DASD2 :
DASD3 : DASD4 :
DASD VOLSERS :
DASD EXCPS :
TAPE1 : 348,1 TAPE2 :
TAPE3 : TAPE4 :
TAPE EXCPS:
UNIT1 : UNIT2 :
UNIT3 : UNIT4 :
UNIT EXCPS:
RECS= JBR: Y JCR: Y JRC: Y JIR: Y JMR: Y JRR: N JNR: N
PF1=HELP
First, let us focus on three fields that affect when jobs are actually processed:
SEPARATE DSNAME
Identifies a data set that can only be used by one
job at a time. That means while this job is
running, all other jobs are prevented from using
that data set. Unicenter CA-Scheduler accepts up
to 44 characters for a SEPARATE DSNAME. For
this option to be effective, you must also define
this data set as a SEPARATE DSNAME for every
job that uses this data set.
SEPARATE JOBS LIST
Accepts up to eight entries that identify jobs that
are submitted or started or that cannot run on this
CPU while this job is running. If JOBA cannot
run with JOBB, then JOBB cannot run with JOBA
which means every job mentioned here also needs
a JRR of its own that names this job in its
SEPARATE JOBS LIST. When specifying more
than one job name, use commas between them, or
use mask characters. Mask characters identify a
group of jobs by defining the characters that these
job names have in common. The chart following
gives several examples of how to use mask
characters.
To Separate All Jobs That
Specify
Start with PAY
PAY*
End with 0100 0100
3-86 Unicenter CA-Scheduler User Guide