03.03.2015 Views

Unicenter CA-Scheduler Job Management for VSE User Guide

Unicenter CA-Scheduler Job Management for VSE User Guide

Unicenter CA-Scheduler Job Management for VSE User Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

1.1 Beginning with the Basics<br />

when you define jobs to <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong>. Even if ARDAILY is a group<br />

of jobs, you can still retain your familiar names. Because <strong>VSE</strong> sites run so<br />

much production work, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> has you group related jobs<br />

together under one name, a schedule name.<br />

Think of a schedule as a timetable: it tells <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> when<br />

certain jobs run and which workstations they stop at. All jobs in the database<br />

belong to some schedule.<br />

Since you are allowed to have multiple schedules, you need to devise an<br />

organized way of grouping jobs into schedules. Many sites group jobs by<br />

application and frequency. If ARDAILY is one schedule, ARMNTHLY could be<br />

another. When grouping jobs into schedules, keep in mind one thing: options<br />

defined <strong>for</strong> a schedule apply to all jobs in that schedule which means you can<br />

save time by defining options <strong>for</strong> an entire schedule, but you will always find<br />

jobs that are exceptions. <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> allows you to override<br />

schedule options by defining different values <strong>for</strong> the exceptional jobs: most<br />

options defined at the job level override options set <strong>for</strong> a schedule.<br />

Schedule Name When <strong>Job</strong>s Run <strong>Job</strong> Names<br />

ARDAILY<br />

Most options defined <strong>for</strong> a<br />

schedule apply to all the<br />

jobs in that schedule.<br />

ARMNTHLY<br />

Override schedule options<br />

with job options.<br />

Every day<br />

Each weekend and<br />

each month end.<br />

AR001<br />

.<br />

.<br />

AR014<br />

ADDSTOCK<br />

ADDSALES<br />

AR030<br />

ARMNTHLY Only each weekend. ARPAID<br />

ARDUE<br />

Since <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> does not want to change how you name jobs, it<br />

organizes its database using a method that works <strong>for</strong> all sites.<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> uniquely identifies a task by knowing four values:<br />

■<br />

■<br />

■<br />

■<br />

<strong>Job</strong> name<br />

<strong>Job</strong> number<br />

Workstation number<br />

Schedule name<br />

Four values are needed. First, job name alone usually is not enough to single<br />

out every task per<strong>for</strong>med at your site: too many applications have a JOB1 or<br />

JOBA, but when job name is linked to schedule name, you come up with a<br />

unique job ID. If you omit telling <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> the other two<br />

values, workstation defaults to 40 and job number defaults to 01.<br />

Chapter 1. Introduction 1-3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!