CA Workload Automation CA 7® Edition

Chapter 1: Introduction
The Primer teaches new CA WA CA 7 Edition users how to use CA WA CA 7 Edition to
perform basic scheduling functions. The Primer is designed to be used either offline or online.

This section contains the following topics:

 Logging On
 Accessing the Database
 Displaying Command Output
 Logging Off

Logging On:

 In TPX menu, we need to give CA7 and you will get below panel. Use this logon screen
to log on to CA WA CA 7 Edition:

 When it is displayed, enter your USERID and a PASSWORD, when one is required. Press
Enter.
 The CA WA CA 7 Edition logon screen appears. Notice MENU in the upper-left corner of the
screen. MENU is the top line command that takes you to the CA-7 Function Menu.
  Press Enter to get to the next screen, which displays the CA WA CA 7 Edition function menu.
At any time, you can enter the top line command MENU to transfer to this screen.

Aliases for Formatted Panel Functions:

Functions Service Level Alias

ADD ADD A,ADDT,AELETE,AIST,APD
APPEND READ AP,APP
APPENDP READ N/A
CLEAR CLEAR CL,CLR
DD DELETE N/A
DELETE DELETE D,DEL,DELT
DELPRRN UPDATE N/A
EDIT EDIT E,EDITH
EXIT EXIT N/A
FE READ FEIT,FEPL,FEVE
FETCH READ F
FETCHP READ FP
FORMAT FORMAT FMT,FOR,FORM
FPE READ N/A
FREE DELETE N/A
LIST READ L,LDD,LDIT,LISTA,LISTP,LISTR,LPD
PURGE DELETE N/A
QUIT QUIT Q
REFRESH UPDATE REF
RENAME UPDATE REN
REPL UPDATE R,REP,REPLH
REQ UPDATE N/A
RESOLV SUBMIT RES
RET SUBMIT N/A
RUN SUBMIT N/A
RUNH SUBMIT N/A
SAVE ADD S
SR UPDATE N/A
SS ADD N/A
STATUS READ ST
SUBMIT SUBMIT SUB
UPD UPDATE U,UDD,UIST,UPDATE,UPDT
XPOST UPDATE N/A
XPRE UPDATE N/A
XQ UPDATE N/A
XQJ UPDATE N/A
XQM UPDATE N/A
XQN UPDATE N/A
XRQ UPDATE N/A
XRST UPDATE N/A
XSPOST UPDATE N/A
XSPRE UPDATE N/A
XUPD UPDATE N/A
XWLP UPDATE N/A
Accessing the Database:

All of the screens you use to add information to the CA WA CA 7 Edition database can be
accessed from the Data Base Maintenance Menu. Display this menu now by typing this command on
the top line of your screen (above the message telling you that your logon was accepted):

DB

When you press Enter, this screen is displayed:

 The menu lets you select nine different functions. Four of the functions take you directly to
formatted screens which you use for various database maintenance tasks, like defining jobs
or networks. Display the screen that defines jobs now by typing 1 in the FUNCTION field.

When you press Enter, this screen is displayed:

This panel contains the following fields:

FUNCTION:

Specifies the function to be performed. Value must be the name of some other panel or one
of the following:

ADD: Adds a job to the database.

DELETE: Deletes a job and its associated data from the database (documentation, schedules, and so
forth).

DD: Same as DELETE, but deletes any data sets that this job references if the data sets have no users
and no documentation, and do not cause job triggering. This includes all virtual resources connected
to the job.

PURGE: Same as DD, but also deletes job trigger definitions that trigger the job being deleted, job
requirement definitions that require the job being deleted; and, if the CA WA Restart Option
interface is active, deletes the CA WA Restart Option CMT member for the job being deleted.

DELPRRN: Deletes the JCL saved in the trailer queue from the job's prior run.

FORMAT: Clears the panel of all input data.

LIST: Lists a job and job-related information. In batch, a formatted panel is not listed. Only a found or
not found message is returned.

UPD: Updates database information about a job.

This screen contains the following information:

 Line contains the FUNCTION field. This field is where you tell CA WA CA 7 Edition what you
want to do with the information in the rest of the screen. For example, you would enter ADD
to add a new job to the database.
 The body of the screen contains information that is stored in the CA WA CA 7 Edition
database.
 The third line from the bottom of the screen contains CA WA CA 7 Edition program data, the
screen ID, and the date and time. Each screen has a unique ID. The ID is DB.1 on this screen.
You can enter this ID on any other screen to transfer directly to this screen. This process is
illustrated when we copy job records.
 The last two lines can contain messages. Be sure to read them. They tell you if there is some
action you have to take next or if there was an error in the action you took. Messages are
described in the Message Reference Guide. The message number consists of the contents of
the PROGRAM field in the preceding line, followed by the contents of the MSG-INDX field.
For example, the number of the message that is shown on this screen is SM20-00.

To return to the menu now, enter DB in the FUNCTION field and press Enter. Instead of typing
DB, you can press PF3 to return to the menu. You cannot press PF3 when you are using CA WA
CA 7 Edition under ISPF and you have defined PF3 for another function.
 You are returned to the menu:

 Continuing down the menu, functions 2, 3, and 4 take you to submenus. You can use
submenus to select formatted scheduling, predecessor/successor, or workload
documentation screens. Display the scheduling submenu now by typing 2 in the
FUNCTION field.

When you press Enter, this screen is displayed:

This screen contains the following information:

 Line contains the FUNCTION field. This field is where you select the scheduling screen
that you want to display.
 The body of the screen lists the scheduling screens and the function codes that select
them.
  The three lines at the bottom contain program data and messages, the same as the CPU
Job Definition screen. The ID of this screen is DB.2.
 Now select the first formatted scheduling screen by typing 1 in the FUNCTION field.

When you press Enter, the CPU Job Scheduling screen is displayed:

 This screen is the screen you use to schedule CPU jobs after you add them to the database.
Enter DB in the FUNCTION field and press Enter to return to the main menu (or press PF3
twice):

 This time, enter 7 to display the JCL screen.

 When you press Enter, this screen is displayed:
  You can use this screen to display the JCL for any of your jobs. Provide is the member name
of the JCL (usually the same as the job name) and the number of the library (if other than 0)
where the JCL is stored. When you press Enter, the JCL is displayed and you can edit it.

Displaying Command Output:

Type the following command:

/DISPLAY,ST=KEY

Press Enter. You see a screen that lists the PF and PA keys. The screen also tells you the commands
that are executed by pressing those keys. The screen that you see can vary, depending on the way PF
and PA keys were defined in your shop. If the output from this command cannot all fit on one
screen, press Enter to scroll to the next screen.

Chapter 2: Defining Jobs

This section tells you how to define computer jobs to CA WA CA 7 Edition. This section contains the
following topics:

 Displaying the CPU Job Definition Screen

 Adding a Job
 Adding Another Job
 Displaying Job Records
 Copying Job Records

Adding a Job:

We start by defining a job with the following characteristics:

 The job name is your name followed by the letter A.

 The job is assigned to a system named PRIMER.
  The job is not submitted or executed on the CPU.
 The job does not send prompting messages to the operator when it is going to be late.

FUNCTION: Enter ADD.

JOB: Give the name of the job. Use the first seven letters of your name followed by the letter A. We
use the job name NAMEA in the rest of this book, but it is important to use your own name instead
of the letters NAME. This method lets everyone who performs the exercises in this book have a
unique set of jobs. If two people in your shop have the same name, add an initial so that each name
is unique.

SYSTEM: Enter PRIMER.

EXEC: Enter N to indicate that this job must not execute. If you leave this field blank, it defaults to Y.

PROMPTS: Enter N to indicate that prompting messages are not sent if the job is late. If you leave
this field blank, it defaults to Y.

Leave the rest of the fields blank. When you have entered this information in your screen, press
Enter. Your screen now looks like the following example, with the ADD SUCCESSFUL message at the
bottom of the screen.

Adding Another Job:

With NAMEA still displayed on your terminal, we can easily add another job with similar
characteristics. Type the following values on your screen, right over the values that are there:

FUNCTION: Enter the A in ADD again.

JOB: Change the job name to NAMEB. Assume that you want to leave all the other values the same
and press Enter:
The ADD SUCCESSFUL message is displayed at the bottom of the screen again. The message indicates
that NAMEB has been added to the database with the same values as NAMEA. The only exception is
MEMBER, which automatically changes to match the job name.

Displaying Job Records:

To ensure that NAMEA and NAMEB are both added to the database, move the cursor to the top line
of your screen and enter this command:

LJOB,JOB=NAME*

When you press Enter, this output screen is displayed:

The screen gives the basic information for NAMEA followed by the basic information for NAMEB. If
any other jobs in your database start with the letters NAME, they are listed too.

Copying Job Records:

You can decide to add similar jobs later. To do so, copy a job like NAMEA that has already
been defined. To copy a job, list the NAMEA record on your screen, make your changes, and then
add the new job to the database. To illustrate this process, enter DB.1 on the top line of your screen
and press Enter. A blank CPU Job Definition screen is displayed:

To display NAMEA, enter values in two fields:

FUNCTION: Enter LIST.

JOB: Enter the name of a job you have already defined, in this case NAMEA.

When you press Enter, the screen displays the NAMEA record:

To add a similar job to the database, fill in these fields:

FUNCTION: Change LIST to ADD.

JOB: Enter the name of the new job. In this case, call it NAMEC.
Then press Enter and wait for the ADD SUCCESSFUL message at the bottom of the screen. Now add
NAMED to the database by retyping the A in the FUNCTION field and changing the JOB field to
NAMED. Repeat these steps for NAMEE. Now we can use these jobs to learn how to schedule jobs to
run automatically

Chapter 3: Scheduling Jobs

This section contains the following topics:

 Selecting a Calendar
 Scheduling a Job To Run On Certain Days
 Scheduling a Job To Run After Another Job
 Scheduling a Job Differently
 Triggering Other Jobs
 Other Scheduling Methods

Selecting a Calendar:

To see the calendars in your shop, enter this command on the top line of any CA WA CA 7 Edition
screen:

/DISPLAY, FM=SCAL

When you press Enter, the screen lists all of your calendars:

To complete the exercises in this book, use a calendar that defines weekdays as normal processing
days and has at least one holiday. To see the processing days and holidays that are defined on each
of your calendars, enter this command on the top line of any screen:

PRINT,YEAR=yy,SCAL=xx

yy: Indicates the year that the fifth and sixth characters identify.
xx: Indicates the last two characters in the calendar name.

For example, we are going to use SCAL145D to schedule the jobs in this book. To see the way that
this calendar is defined, enter this command on your screen:

PRINT,YEAR=14,SCAL=5D

When you press Enter, you see the first month of the calendar you specified. For example, here is
January on the SCAL145D calendar:

Only the processing days (workdays) are displayed. In this case, they are every weekday except
January 1 which was defined as a holiday on SCAL145D. In addition, the first and last days of January
are identified:

 The characters B01 in place of 01 identify the first day of the first month. Because this day is
a nonprocessing day, the characters are enclosed in parentheses.
 The characters E01 in place of 31 identify the last day of the first month. Because this day is
a processing day, the characters are enclosed in periods.

To scroll forward to the next month, press Enter. The February SCAL145D calendar looks like the
following example:

Because February 17 is a holiday on this calendar, it is not displayed. Keep scrolling through as many
months as you want to see. You can stop at any point and can go on to the next exercise.
Scheduling a Job To Run On Certain Days:

You can schedule a job to run on certain days. Now we learn how to schedule a job to run. The job
runs Tuesdays and Thursdays by 9 p.m. or the next available processing day when Tuesday or
Thursday is a holiday.

Return to the Data Base Maintenance Menu by typing DB on the top line of your current screen.
When you press Enter, the menu is displayed again:

Now, we want to go to the scheduling screens. Enter 2 in the FUNCTION field, and press Enter. The
Scheduling Menu is displayed:

To select scheduling for the CPU jobs, enter 1 in the FUNCTION field. When you press Enter, the CPU
Job Scheduling screen is displayed:
What job we are scheduling and what calendar it is based on. To provide this information, fill in the
following fields on this screen:

FUNCTION: Enter EDIT to define scheduling information.

JOB: Enter NAMEA to identify the job.

SCAL: Give the two-character name of a calendar that has been defined in your shop. The rest of the
illustrations in this book are based on calendar 5D. If 5D is not defined in your shop for the current
year, you can use another calendar. (You can get this information from the calendars you listed
when you selected a calendar.)

When you press Enter, this edit screen is automatically displayed:

Fill in the fields on this screen as follows:

FUNCTION: Enter ADD.

SCHID: Enter 1 to indicate that this schedule is the first schedule we have defined for NAMEA. (We
learn more about this field when we schedule a job differently.)

ROLL: Enter F. This value rolls the scheduling of NAMEA forward to the next day when Tuesday or
Thursday happens to be a holiday on calendar 5D.

DOTM: Use your tab key to place the cursor under this heading. The value tells what time the job has
to end (its due-out time). Specify 2100

LDTM: Use this field to tell how many minutes it typically takes to process the job (its lead time).
Specify 30 to let the job have a half hour to run. CA WA CA 7 Edition uses this number to figure out
when it has to start the job to complete on time. In this case, it has to start the job by 2030 so it
completes by 2100.

WEEKLY: Tab to this field and enter an X to the left of the word WEEKLY and more Xs to the right of
TUE and THU. Press Enter and watch for the ADD FUNCTION SUCCESSFUL message at the bottom of
the screen:

Now that you have defined the scheduling criteria for NAMEA, save it by typing SS after
FUNCTION and pressing Enter. This command automatically returns you to the CPU Job Scheduling
screen:
See the two messages at the bottom of the screen? They inform you that your schedule has been
saved and that it must now be resolved.

Seeing When the Job Will Run:

To compare it to the calendar you specified and determine the exact days to process the job. To
resolve the schedule, issue the RESOLV command. To issue the command, enter RESOLV in the
FUNCTION field and press Enter. The next screen that you see has the RESOLV command on the top
line. Move the cursor to the end of the RESOLV command and enter:

,YEAR=yy

where yy is the current year. Press Enter. When you press Enter, the screen looks something like the
following example:

The middle of the screen displays SCHEDULE DATA. You defined these values on the CPU Job
Scheduling Parameter Edit screen.

The dates that are listed under SCHEDULE DAYS ROLL STARTED are different from the dates that are
shown here unless you are also using SCAL135D with holidays defined on January 1 and July 4. These
dates show you what happens to NAMEA when Tuesday or Thursday is a holiday. NAMEA is
processed on the following day (because we specified F in the ROLL field).

This screen shows you when NAMEA is processed in January. NAMEA is processed every Tuesday
and Thursday except for January 1 which is a holiday. Press Enter to scroll forward again, to this
screen:

Scheduling a Job To Run After Another Job:

Some jobs must be scheduled after other jobs, regardless of what day those other jobs run. For
example, assume that NAMEB has to run after NAMEA, regardless of whether NAMEA runs on
Tuesday and Thursday or is rolled forward to Wednesday or Friday. CA WA CA 7 Edition lets you
schedule NAMEA to trigger NAMEB. This triggering means that NAMEB is automatically scheduled
whenever NAMEA ends successfully. Here is how to define this triggering:

 Enter DB.2 at the top of any screen to return to the Scheduling Menu. The Scheduling Menu
is displayed.
  Enter 4 in the FUNCTION field to select job triggering. When you press Enter, this screen is
displayed:

To trigger NAMEB from NAMEA, fill in the fields on this screen as follows:

FUNCTION: Enter UPD (because you are updating the NAMEA record).

JOB: Identify the job that runs first, in this case NAMEA.

OPT: Tab down to the line under the OPT heading and enter A to add the triggered job.

SCHID: Enter 1.

TRGD-JOB: Identify the job that is to run when NAMEA ends, in this case NAMEB. QTM Specify 30 to
indicate that NAMEB is late when it has to wait more than 30 minutes before it starts processing.
The due-out time of the job is calculated for you, based on this number.

LDTM: Assume that NAMEB also takes 30 minutes to process. When these fields are filled in, press
Enter and watch for the UPD FUNCTION SUCCESSFUL message at the bottom of the screen.
Displaying the Triggers:

To ensure that NAMEA triggers NAMEB, move the cursor to the top line of your screen and enter this
command:

LJOB,JOB=NAMEA,LIST=TRIG

When you press Enter, this output screen is displayed:

Scheduling a Job Differently:

Now assume that we receive instructions to schedule NAMEA on Mondays in addition to

Tuesdays and Thursdays, to run it every Monday even if Monday is a holiday, and to run NAMED
after NAMEA on Mondays only. How do we go about this scheduling?

To begin with, we do not need to change the way we defined NAMEA on the CPU Job
Definition screen in the last chapter. The definition of NAMEA stays the same, regardless of when it
runs and what jobs run after it. (In fact, we cannot add another definition for NAMEA, because there
is only one job by that name.)
 What we must do is to add another schedule for NAMEA. To keep this schedule separate
from the original schedule, we are going to give it a different schedule ID. Previously, we used the
number 1 when we scheduled NAMEA for Tuesdays and Thursdays. Now we are going to use the
schedule ID 2 to schedule NAMEA on Mondays. To change the record, we must return to the CPU
Job Scheduling screen and must change the NAMEA scheduling record.

Return to the CPU Job Scheduling screen now by typing DB.2.1 on the top line of your
screen. When you press Enter, this screen is displayed:

What we must do now is fetch (get) the NAMEA scheduling record and add to it. To get the
record, fill in these two fields:

FUNCTION: Enter FE to fetch the scheduling record and go into edit mode.

JOB: Enter NAMEA to identify the job you want to edit.

When you press Enter, the CPU Job Scheduling edit screen is automatically displayed with
the scheduling criteria we defined the scheduling criteria.
 We change this screen to tell CA WA CA 7 Edition to run NAMEA on Mondays under
schedule ID 2. To do this adjustment, change the following fields:

FUNCTION: Change LIST to ADD.

SCHID: Change 1 to 2.

ROLL: Change F to N. This change tells CA WA CA 7 Edition to run NAMEA on Mondays even if
Monday is a holiday.

LDTM: Change 0030 to 0040 because NAMEA takes a little longer to run on Mondays.

WEEKLY: Leave the X in this field but add an X after Monday and erase the Xs after TUE and THU.

Press Enter and watch for the ADD FUNCTION SUCCESSFUL message at the bottom of the screen:
 Now the NAMEA scheduling record is expanded to include another scheduling variation. To
replace the original scheduling record with the expanded record, enter SR (for save/replace) after
FUNCTION and press Enter. This action returns you to the CPU Job Scheduling screen:

See how the schedule ID count is now set to 2? This count indicates that NAMEA has two scheduling
variations.

Resolving the Revised Schedule:

The next step is to resolve the schedule again to include the days that are defined under
schedule ID 2. To do this resolve, enter RESOLV in the FUNCTION field again and press Enter. This
time the output screens that you see describe schedule ID 2 after schedule ID 1. They look
something like the following screens.
 Keep scrolling until you get to the calendars. Our sample calendar shows you that Monday
has been added to Tuesday and Thursday as the regular processing days for NAMEA. These
calendars do not distinguish between schedule IDs; they show all the days that NAMEA is scheduled:

Checking Schedule IDs:

Before you go on, verify that two schedule IDs are defined for NAMEA. To list all defined
schedule IDs, enter this command on the top line of your screen:

LJOB,JOB=NAMEA,LIST=SCHD

When you press Enter, this screen is displayed:

 The middle of this screen shows all schedules that have been defined for NAMEA. In this
case there are two: schedule ID 1 and schedule ID 2.

Triggering Other Jobs:

We now use the schedule ID 2 to tell CA WA CA 7 Edition to run NAMED after NAMEA on
Mondays. We do this triggering by returning to the Job Triggering screen for NAMEA and adding
NAMED to it. Enter DB.2.4. When you press Enter, the Job Triggering screen is displayed again:

To display the jobs that NAMEA currently triggers, enter LIST in the FUNCTION field and
NAMEA in the JOB field. When you press Enter, the NAMEA triggering record is displayed:
To trigger NAMED from NAMEA on Mondays, fill in these fields:

FUNCTION: Change LIST to UPD.

OPT: Tab down to the line below NAMEB and enter A under OPT.

SCHID: Enter 2 because we want to trigger NAMED on Mondays when NAMEA runs under schedule
ID 2.

TRGD-JOB: Identify the job that is to run after NAMEA under schedule ID 2: NAMED.

QTM: Specify 15 to indicate that NAMED is late when it has to wait more than 15 minutes before it
starts processing.

LDTM: Assume that NAMED takes one hour to process (0100).

When these fields are filled in, press Enter and watch for the UPD FUNCTION SUCCESSFUL message
at the bottom of the screen:
The time entries for NAMED are displayed. The 15 minutes you specified for QTM is automatically
rounded down to 10 minutes. From now on, whenever NAMEA ends successfully on Monday (when
it runs under schedule ID 2) NAMED is scheduled.

Chapter 4: Adding Requirements to Jobs

This section shows you how to ensure that jobs run in order by adding predecessor requirements to
them. Also, it shows you how to prevent two jobs from running simultaneously. This section contains
the following topics:

 Defining a Predecessor.
 Preventing Jobs From Running Together.
 Defining a Manual Predecessor.
 Displaying Requirements.
 Connecting Resources to Jobs.