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

supportcontent.ca.com
from supportcontent.ca.com More from this publisher
03.03.2015 Views

3.1 Defining Schedules 3.1 Defining Schedules A schedule contains one or more jobs that are grouped together because they share similarities. Jobs in the same schedule might all: ■ ■ ■ ■ Belong to the same application Run on the same day Have the same operational dependencies or, most importantly, Belong together because that is how your site is organized Grouping jobs in schedules is easier because jobs can be selected whenever their schedules are selected, and many schedule options apply to all jobs within a schedule. That means you can define jobs faster if you specify their common characteristics on a schedule record. In this chapter, the examples we use do not store much information in schedule records. But as time goes on, you will find it is easy to implement special features such as ■ ■ Having Unicenter CA-Scheduler issue messages when work falls behind or Defining when to submit jobs by changing just schedule records instead of every job record. All users with write passwords can define schedule records. This topic shows you how by ■ ■ ■ ■ ■ Planning schedules Defining a schedule base record Checking which defaults apply to schedules Learning the basics about a schedule record Defining optional schedule records 3.1.1 Planning Schedules As you start using Unicenter CA-Scheduler, do not try to automate everything at once. If you do, you will be overwhelmed with details. Instead, start getting comfortable with Unicenter CA-Scheduler by defining just a few simple schedules first. You will start by outlining a schedule for your site's backup runs. This example shows how easy defining a schedule can be. Later examples will show optional features you can implement when defining schedules. When you are deciding what schedules to define for your site, keep these guidelines in mind: ■ Group jobs into schedules by application first. If that gives you an unmanageable number of jobs for one schedule, subdivide it based on when jobs run. 3-2 Unicenter CA-Scheduler User Guide

3.1 Defining Schedules ■ ■ ■ Do not create a schedule for each day of the week. That approach is difficult to implement and even harder to maintain. Instead, group jobs belonging to the same application together in one or two schedules. That makes it easier to verify predecessor relationships. Likewise, put jobs that run upon request with the rest of those applications' jobs. The goal here is to limit the number of cross-schedule dependencies, keeping schedule maintenance and verification as simple as possible. Try to limit the number of jobs you put in schedules to under 50. Again, the rationale is keeping things simple. Big schedules are more cumbersome. Now apply this advice to defining a schedule for backup jobs. 3.1.2 Defining a Schedule Base Record Since schedules define the characteristics shared by groups of jobs, schedule records primarily consist of optional fields. The simplest schedule definition is stored on a base record. This topic explains how to define a simple schedule. You begin defining schedules at Unicenter CA-Scheduler's main menu. Tab to SCHEDULE MAINTENANCE. SCHD-MM MAIN MENU CA-SCHEDULER ===> MASTER - WR CONNECT : 4 -------SELECT FUNCTION------- ==> ONLINE SCHEDULE STATUS ==> ONLINE MONITORING ==> REPORTING FACILITY ==> POWER INTERFACE _ ==> SCHEDULE MAINTENANCE ==> JOB MAINTENANCE ==> USER ID MAINTENANCE ==> STATION MAINTENANCE ==> RESOURCE MAINTENANCE ==> CALENDAR MAINTENANCE ==> DATETABLE MAINTENANCE ==> STAGED JCL MAINTENANCE ==> DOCUMENTATION MAINTENANCE ==> DRIVER PROC MAINTENANCE ==> AUTO-REPLY MAINTENANCE ==> GENERATION PARM DISPLAY PF1=HELP Defining schedules is one form of schedule maintenance. Therefore, tab down to the fifth selection and press Enter. That choice displays the Schedule Maintenance menu, which lists everything you can do with schedule records. Chapter 3. Maintaining the Database 3-3

3.1 Defining Schedules<br />

3.1 Defining Schedules<br />

A schedule contains one or more jobs that are grouped together because they<br />

share similarities. <strong>Job</strong>s in the same schedule might all:<br />

■<br />

■<br />

■<br />

■<br />

Belong to the same application<br />

Run on the same day<br />

Have the same operational dependencies or, most importantly,<br />

Belong together because that is how your site is organized<br />

Grouping jobs in schedules is easier because jobs can be selected whenever<br />

their schedules are selected, and many schedule options apply to all jobs<br />

within a schedule. That means you can define jobs faster if you specify their<br />

common characteristics on a schedule record.<br />

In this chapter, the examples we use do not store much in<strong>for</strong>mation in<br />

schedule records. But as time goes on, you will find it is easy to implement<br />

special features such as<br />

■<br />

■<br />

Having <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> issue messages when work falls behind or<br />

Defining when to submit jobs<br />

by changing just schedule records instead of every job record.<br />

All users with write passwords can define schedule records. This topic shows<br />

you how by<br />

■<br />

■<br />

■<br />

■<br />

■<br />

Planning schedules<br />

Defining a schedule base record<br />

Checking which defaults apply to schedules<br />

Learning the basics about a schedule record<br />

Defining optional schedule records<br />

3.1.1 Planning Schedules<br />

As you start using <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong>, do not try to automate everything<br />

at once. If you do, you will be overwhelmed with details. Instead, start getting<br />

com<strong>for</strong>table with <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> by defining just a few simple<br />

schedules first. You will start by outlining a schedule <strong>for</strong> your site's backup<br />

runs. This example shows how easy defining a schedule can be. Later<br />

examples will show optional features you can implement when defining<br />

schedules.<br />

When you are deciding what schedules to define <strong>for</strong> your site, keep these<br />

guidelines in mind:<br />

■<br />

Group jobs into schedules by application first. If that gives you an<br />

unmanageable number of jobs <strong>for</strong> one schedule, subdivide it based on<br />

when jobs run.<br />

3-2 <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!