Unicenter CA-Scheduler Job Management for VSE User Guide

3.9 Defining Jobs
3.9.3.9 How Do You Phase Unicenter CA-Scheduler into Production?
Fields on both the schedule and job base records allow you to implement
Unicenter CA-Scheduler in stages:
■
■
AUTO SELECT on the schedule base record
LIBRARY TYPE
AUTO SELECT on the schedule base record controls whether Unicenter
CA-Scheduler evaluates this schedule automatically during autoscan. When
AUTO SELECT = NO, this schedule is skipped and these jobs are not included
in the daily workload. That is exactly what you want to happen while you are
developing definitions for a schedule's jobs. Once you have verified those
definitions using the Analyze and simulation reports, set AUTO SELECT =
YES to include this schedule in the evaluation process that occurs at every
autoscan. Although this schedule may already include production work, you
can let Unicenter CA-Scheduler take control of the selection of this work by
specifying AUTO SELECT = YES.
The next implementation phase permits you to monitor Unicenter
CA-Scheduler's operation while it submits dummy JCL for each of your jobs.
This gives you three important capabilities:
■
■
■
When you are first implementing Unicenter CA-Scheduler, you can run the
product in parallel with your normal production. Without affecting your
regular operation, you can verify that Unicenter CA-Scheduler is
processing your workload as planned.
Even experienced Unicenter CA-Scheduler sites use this technique to
prepare for implementing new applications. TESTLIB enables you to define
and test definitions for applications that are not yet ready to go into
production. You can check your selection criteria and verify the order in
which jobs will run before they have even been handed over to
production.
You can also test the effect of abended and failed jobs by using TESTLIB to
cause those conditions for specific jobs.
To initiate this phase, change AUTO SELECT to YES on the schedule base
record and set LIBRARY TYPE to TESTLIB. Remember that if LIBRARY TYPE
is defined at the job level, it overrides the value you specify on that job's
schedule base record. You can quickly verify what library type applies to your
jobs by checking that value on the Job Directory panel.
When Unicenter CA-Scheduler sees that LIBRARY TYPE = TESTLIB, it
constructs the JCL to run a simple Computer Associates utility program:
CAJUTSTA.
You can use TESTPARM=testparm on individual jobs to cause the test
program to abend, to pass a nonzero completion code, and to have it wait for
a number of seconds. Thus, you can test the effect of abending and failing jobs
on the rest of the schedule.
3-70 Unicenter CA-Scheduler User Guide