CA-7 Job Scheduling

Scheduling jobs by Time

To access the CA-7 CPU JOB SCHEDULING screen you can type in DB.2.1 or use the top line command SCHD,JOB.

If this is the first time a job is being scheduled use EDIT for the function. If the job schedule exists and needs to be changed use the FE (Fetch Edit) function. For JOB use the job to be scheduled or updated. For new jobs fill in the SCAL with the default calendar you want your job to be scheduled on. For a list of the current calendars available see the CA-7 Standards page on the DPS website. For existing jobs the SCAL can be left blank. Once all the fields are filled in press enter to CA-7 CPU JOB SCHEDULING PARAMETER EDIT screen. Fields that need to be filled in on this screen are: Function: SCHID: ADD for new jobs, REPL to replace an existing schedule Always 001 for the first schedule of a job, 002 for second and so on.

SCAL: ROLL: INDEX: DOTM: LDTM: SBTM:

Can be left blank to default to the calendar on the previous screen. Set to N. Leave blank Time the job is expected to complete. Difference in time from DOTM to SBTM. Time you want the job to submit.

DAILY is used to schedule a job to run on all calendar days. WEEKLY is used to make jobs run on specific days. To make a job run Monday-Friday you would put an X beside weekly and then an X beside MON, TUE, WED, THU, FRI. If weekly is selected and all days are selected it acts the same as if the DAILY were selected. MONTHLY is used for monthly and quarterly jobs. Select Monthly and then the specific months that job needs to run. Under monthly you can specify the Week the job is to run, the day of the week, or the RDAY. A complete list of all fields can be found in the CA-7 Data Base Maintenance guide. Once all desired fields are filled in press enter and you should see a successful message on the bottom of the screen. If this is a new add type SS in the function area and press enter. This will take you to the previous screen. Type RESOLV in the function area and it will resolve the job on the specified calendar.

Scheduling Jobs to Job Triggers

To enter the CA-7 JOB TRIGGERING screen you can use the menu DB.2.4 or the top line command SCHD.JTRG. For Function type LIST and then tab to the JOB and type in the job name. This will list any jobs that are already being trigger by the listed job. To add a new job trigger: FUNCTION; UPD JOB: job name that will trigger job OPT A to add (A list of different options is displayed at the bottom of the screen). SCHID Schid to be used for trigger (000 indicates all schids) TRGD-JOB Job to be triggered. TRGID Not used at DPS DOTM Indicates the due out time of the TRGD-JOB normally left blank
2

QTM Elapsed queue time normally 0000 LDTM Elapsed lead time normally left blank SBTM Submit time Not normally used

Fill in the desired fields and press enter. At the bottom of the screen you should receive a message that the UPD function was successful. If you then list the job again you should see the trigger in place.

Data Set Triggers

There are 2 ways to access the Data Set Triggering screen: DB.2.6 or the top line command SCHD,DTRG. Once in the Data Set Triggering screen, list the DSN to be used as a trigger as in the below example.

This example shows no triggers are defined. To add a data set trigger enter UPD for the function. Tab to the OPT field and enter A to add. Under SCHID enter the schid that the jobs should run (Normally 001 for the first schedule of a job). Under TRGD-JOB enter the job name to be triggered by this Data Set. Tab to QTM and enter 0000 and press enter. Check the MESSAGE section at the bottom of the screen to ensure that the desired function was successful. You can then LIST the screen and see the job being triggered by the data set.

Job Dependencies
There are 2 ways to access the CA-7 CPU JOB PREDECESSORS screen, from the main menu you can enter DB.3.2 or the top line command JOBCONN,JDEP.

List the job that you want to add the Job predecessor for.

To add a new job: Function: Pred for Job OPT SCHID LEADTM ADD Job that is receiving the dependency These are listed at the bottom of the page. A to add. Schid of the predecessor job (000 is for any schid) This is the amount of time that CA-7 will look back for the desired job. 0000 looks back to the previous run of the listed job. 0001 0098 look back that number of hours. 0099 says that the predecessor job should complete after this job enters the CA-7 request queue. Name of the job that is a prerequisite of the listed job. There are 3 options for this. If you leave it blank it will default to YES to indicate that it is for all runs. If you tab to this field and type ONLY it is a one time dependency and then CA-7 will automatically remove it. SKIP indicates that this dependency will be skipped on the next run. After running it automatically resets back to YES.

PRED-JOB NEXT-RUN

After pressing enter you can again LIST the job and you should now see your updates listed.

Data Set Predecessors

There are 2 ways to access the CA-7 Data Set Predecessors screen, DB.3.1 or the top line command JOBCONN,DSN.

Once in the screen list the job that needs the dataset dependency. To update the list: Function: Pred for Job OPT SCHID LEADTM UPD Job that is receiving the dataset dependency These are listed at the bottom of the page. A to add. Schid of the predecessor job (000 is for any schid) This is the amount of time that CA-7 will look back for the desired job. 0000 looks back to the previous run of the listed job. 0001 0098 look back that number of hours. 0099 says that the predecessor job should complete after this job enters the CA-7 request queue. DATASET NAME Name of the dataset that is a prerequisite of the listed job. DSNBR DSN number (can be left blank) PERM This indicates if the dataset should be considered perm to this job. Options are Y and N. N is the default.

NEXT-RUN

There are 3 options for this. If you leave it blank it will default to YES to indicate that it is for all runs. If you tab to this field and type ONLY it is a one time dependency and then CA-7 will automatically remove it. SKIP indicates that this dependency will be skipped on the next run. After running it automatically resets back to YES.

Adding User Holds

When asked to put a CA-7 job on hold the standard is to use a USER hold with information as to why the jobs was held, who had it held and who will call to have the job released. There are 2 ways to access the CA-7 USER MEMO-FORM PREDECESSORS screen. DB.3.6 and the top line command JOBCONN,USR.

You can then LIST the job that you want to add the user hold to. To ADD the user hold: FUNCTION PRED FOR JOB UPD Job to have user hold added to.

OPT SCHID MEMO-FORM NEXT-RUN

A to add, other options are listed at the bottom of the screen. Normally set to 000 for all schids. This is a free form field that explains why the job is held, who had it held and who will call to have it release. This can be set to ONLY indicating a 1 time hold (after the job is run successfully CA-7 will remove the hold) or YES for a permanent hold.

Below is an example of what the hold should look like.