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.

6.1 Commonly Asked Questions<br />

6.1.1.3 Should I Use Datetables or Calendars?<br />

Datetables and calendars are two different methods used to select schedules<br />

and jobs <strong>for</strong> a specific day. Datetables provide significantly more flexibility<br />

than calendars and should be used if at all possible. They are a bit more<br />

complicated to understand, but entail less maintenance than calendars when<br />

going from year to year. Datetables also allow multiple accounting periods as<br />

well as different holidays.<br />

One area where you will want to use Calendars is when the schedule has to<br />

run according to a set of dates that follows no pattern. Define these individual<br />

days once in a calendar. Then when any schedule runs on those dates, you<br />

give it that calendar name <strong>for</strong> selection.<br />

For most of your application needs, however, use datetables. A detailed<br />

discussion on this matter appears in the chapter "Criteria Language."<br />

6.1.1.4 When Should I Define a New Datetable Versus a New Cycle in an<br />

Existing Datetable?<br />

Keep in mind that a cycle can be an accounting, production, or sales period.<br />

You can have up to twenty cycles defined with any one datetable, and any<br />

number of datetables. The datetable prefixed by the letter A is your default<br />

production datetable. The other prefixes are variations upon that datetable.<br />

Any time you want to schedule a job based on a combination of two or more<br />

cycles, you must use the datetable prefix; you cannot use different datetable<br />

names.<br />

6.1.2 Maintaining the Database<br />

Commonly asked questions concerning maintaining the database follow.<br />

6.1.2.1 How Should I Organize My Schedules?<br />

A schedule should consist of a group of logically related jobs. This group of<br />

jobs usually belongs to one application, but could also be run at the same<br />

frequency. For example, you could define a Payroll schedule containing all the<br />

payroll jobs and its selection criteria. If certain jobs in the schedule do not run<br />

every time the schedule is selected, define the selection criteria <strong>for</strong> the<br />

exceptional jobs. Or the daily Accounts Receivable jobs could be contained in<br />

one schedule and the weekly Accounts Receivable jobs could be in another.<br />

Possibly, the weekly schedule is dependent on the daily schedule to complete.<br />

Do not organize schedules just by frequency. For example, do not have a<br />

Monday schedule. There should not be one schedule just <strong>for</strong> requested jobs,<br />

either, unless it is easily manageable. Instead, try to keep application-related<br />

jobs together. This makes interdependencies within applications much clearer.<br />

6-4 <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> <strong>User</strong> <strong>Guide</strong>

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

Saved successfully!

Ooh no, something went wrong!