CA Workload Automation

Getting Started
r11.1
This documentation and any related computer software help programs (hereinafter referred to as the
Documentation) is for the end users informational purposes only and is subject to change or withdrawal by CA at
any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in
part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA
and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the Documentation for
their own internal use, and may make one copy of the related software as reasonably required for back-up and
disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy.
Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for
the Product are permitted to have access to such copies.

The right to print copies of the Documentation and to make a copy of the related software is limited to the period
during which the applicable license for the Product remains in full force and effect. Should the license terminate for
any reason, it shall be the users responsibility to certify in writing to CA that all copies and partial copies of the
Documentation have been returned to CA or destroyed.

EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY
APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING
WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE
OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY
LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT
LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY
ADVISED OF SUCH LOSS OR DAMAGE.

The use of any product referenced in the Documentation is governed by the end users applicable license
agreement.

The manufacturer of this Documentation is CA.

Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the
restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-
7014(b)(3), as applicable, or their successors.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Copyright 2008 CA. All rights reserved.

CA Product References
This document references the following CA products:

CA Workload Automation (CA WA)

CA Workload Automation High Availability (CA WA High Availability)

CA Workload Automation High Security (CA WA High Security)

CA Workload Automation Desktop Client (CA WA Desktop Client)

CA Workload Automation Web Client (CA WA Web Client)

CA Workload Automation System Agent (CA WA System Agent)

CA Workload Automation System Agent for z/OS (CA WA System Agent
for z/OS)
CA Workload Automation System Agent for i5/OS (CA WA System Agent
for i5/OS)
CA Workload Automation Application Services Agent (CA WA Application
Services Agent)
CA Workload Automation Web Services Agent (CA WA Web Services
Agent)
CA Workload Automation for Micro Focus Enterprise Server (CA WA for
Micro Focus Enterprise Server)

CA Workload Automation Database Agent (CA WA Database Agent)

CA Workload Automation Business Agent for SAP Solutions (CA WA
Business Agent for SAP Solutions)
CA Workload Automation Business Agent for PeopleSoft Solutions (CA
WA Business Agent for PeopleSoft Solutions)
CA Workload Automation Business Agent for Oracle E-Business Suite (CA
WA Business Agent for Oracle E-Business Suite)

CA Alchemist

Contact Technical Support

For online technical assistance and a complete list of locations, primary service
hours, and telephone numbers, contact Technical Support at
http://ca.com/support.
Contents

Chapter 1: Introduction 7
About CA WA .................................................................................. 7
CA WA Server ............................................................................. 7
CA WA Desktop Client ...................................................................... 8
Agents .................................................................................... 8
What you are going to do ...................................................................... 8
Scheduling Scenario ....................................................................... 9
Scheduling steps .......................................................................... 10
Information you need to work through this tutorial .......................................... 10
Using the examples in this tutorial ......................................................... 10

Chapter 2: Define Your Workload 13

Define steps .................................................................................. 14
Step 1: Connect to the server using CA WA Desktop Client ...................................... 15
Using the default connection set at installation time ......................................... 15
Step 2: Define an Application .................................................................. 16
Step 3: Schedule your Application using an Event............................................... 17
Understanding the relationship between Events and Applications ............................. 17
Defining the default Date-Time/Manual Event ............................................... 18
Step 4: Define jobs in your Application ......................................................... 20
Adding jobs to the workspace .............................................................. 20
Defining the relationships between jobs .................................................... 21
Defining job details for each job ........................................................... 22
Step 5: Save the Application and upload it to the server ........................................ 27
Step 6: Test what will run using Event simulation ............................................... 28
Simulate the Events next execution ....................................................... 28
Simulate for Friday........................................................................ 29
Simulate for the last workday of the month ................................................. 29
Step 7: Test schedule criteria ................................................................. 30

Chapter 3: Run Your Workload 31

Triggering your Event manually................................................................ 32

Chapter 4: Monitor Your Workload 33

Viewing your workload using subscription filters ................................................ 34

Contents 5
Controlling your Application ................................................................... 35
Releasing your Application ................................................................. 35
Monitoring your Application ................................................................... 36
Controlling your jobs .......................................................................... 37
Displaying job details ..................................................................... 37
Handling submission errors ................................................................ 38
Displaying job output ..................................................................... 39
Using a custom view to monitor and control workload ........................................... 39
Creating a custom view ................................................................... 40
Controlling jobs from a custom view ....................................................... 41
Controlling Applications from a custom view ................................................ 42

Chapter 5: CA WA Desktop Client Tips 43

Using online help ............................................................................. 43
Adding a new server connection ............................................................... 44
Setting Application and job properties .......................................................... 45
Moving perspective icons ...................................................................... 46
Removing types of workload objects ........................................................... 46
Moving views around ......................................................................... 47
Resetting your workspace ..................................................................... 47

Index 49

6 Getting Started
Chapter 1: Introduction
CA WA provides distributed job scheduling and workload management across
the enterprise. It is a simple, flexible, and powerful solution for enterprise
application integration (EAI) and systems operations. Platform-independent as
a result of its next-generation XML and JAVA architecture, CA WA functions
across various server and Enterprise Resource Planning (ERP) platforms,
including the following:
UNIX
Windows NT/2000/2003
z/OS
IBM OS/400
OpenVMS
Compaq NSK
SAP R/3
PeopleSoft
Oracle

This guide is a tutorial for new users. It walks you through the process of
defining, running, and monitoring your workload. Along the way, you will learn
about key CA WA concepts.

About CA WA
Before you start this tutorial, ensure you have the following components.

CA WA Server

The CA WA server is installed on a Windows or UNIX server by your server

administrator.

The server is the core of the CA WA system. It handles and directs all
incoming communication from CA WA Desktop Client, agents, a Relational
Database Management System (RDBMS), and a peer server in a high
availability configuration.

Chapter 1: Introduction 7
What you are going to do

CA WA Desktop Client

CA WA Desktop Client is installed on your personal computer.

CA WA Desktop Client is a graphical interface for defining, monitoring, and

controlling enterprise workload. The interface lets you quickly drag-and-drop
your way through workload definitions, manage calendars, and monitor and
control batch workload, regardless of the operating system. A CA WA system
can have many CA WA Desktop Clients.

CA WA Desktop Client also includes the administrator's tools for setting up

security, configuring CA WA server parameters and agent parameters,
monitoring messages sent from the server, and diagnosing problems with the
CA WA solution.

Note: If CA WA Desktop Client is not installed on your computer, ask your

server administrator for the CA WA DVD. You can also download the CA WA
Desktop Client setup file from the CA Support Online website
(http://ca.com/support).

Agents

Agents are installed on various servers by your CA WA administrator or agent

administrator.

Agents are applications that extend batch workload across multiple operating
systems. Agents run batch workload and monitor its progress. They
communicate with the CA WA server through TCP/IP.

When your administrator installs the server, a default CA WA System Agent

automatically gets installed on the same computer as the server. For example,
if your administrator installs the server on Windows 2000, a CA WA System
Agent automatically gets installed on the same computer. The default agent is
often used to verify the installation.

What you are going to do

In this tutorial, you will use CA WA to schedule and run six jobs on the same
computer. All jobs will run the same batch file or script.

8 Getting Started
 What you are going to do

Scheduling Scenario

The following flowchart represents the jobs you will set up:
The names of the jobs are A, B, C, D, E, and F.
Arrows indicate relationships between jobs. For example, A is the
predecessor for B and C. When A completes successfully, the CA WA
server releases B and C.

The run frequencies of each job are as follows: A, B, C, and D run daily; E
runs on Friday and F runs on the last workday of the month.

Chapter 1: Introduction 9
What you are going to do

Scheduling steps

This tutorial guides you through the three steps you will use to schedule
workload with CA WA.

Information you need to work through this tutorial

Before you connect to the CA WA server, obtain the following information from
your server administrator:
User Name Your server user name.
Password The password for your server user name.
The name of the default agent installed with the server. For this tutorial,
you will use the default agent to run your jobs. The name of the default
agent is AGENT. However, your server administrator may have changed
the default name when installing the server.
You can use another agent instead of the default agent. Ensure that you
have the name of the agent that is installed on the computer where you
will run your jobs.
The directory in which the server is installed. For this tutorial, you will use
the test command file or script installed with the server.

If you are using another agent to run your jobs, ensure that you have the
full path to the command file, script, or command your jobs will run.

Using the examples in this tutorial

In this guide, we use the default agent to run sample workload. Ensure you
know the directory in which the CA WA server is installed.

10 Getting Started
 What you are going to do

Windows examples

If the CA WA server and its default agent are running on a Windows computer,
follow the Windows examples in this guide.

You will need the path to the sample Windows command file installed with the
server. This command file displays the arguments entered for the echo
command. The default path to the file is

installDir\Resources\TestScripts\echo.bat

where installDir is the directory in which the server is installed.

The command file is also on the Documentation CD. If you do not have the
Documentation CD, using a text editor, create your own test file with

echo %*

and save the file in a directory you have access to on the agent computer.

UNIX examples

If the CA WA server and its default agent are running on a UNIX computer,
follow the UNIX examples in this guide.

You will need the path to the sample UNIX script installed with the server. This
script displays the arguments entered for the echo command. The default path
to the script is

installDir/Resources/TestScripts/echo.sh

where installDir is the directory in which the server is installed.

The script is also on the Documentation CD. If you do not have the
Documentation CD, using a text editor, create your own test script with

echo $*

and save the file in a directory you have access to on the agent computer.

Chapter 1: Introduction 11
Chapter 2: Define Your Workload
This section contains the following topics:

Define steps (see page 14)

Step 1: Connect to the server using CA WA Desktop Client (see page 15)
Step 2: Define an Application (see page 16)
Step 3: Schedule your Application using an Event (see page 17)
Step 4: Define jobs in your Application (see page 20)
Step 5: Save the Application and upload it to the server (see page 27)
Step 6: Test what will run using Event simulation (see page 28)
Step 7: Test schedule criteria (see page 30)

Chapter 2: Define Your Workload 13

Define steps

Define steps

14 Getting Started
 Step 1: Connect to the server using CA WA Desktop Client

Step 1: Connect to the server using CA WA Desktop Client

You define, monitor, and control workload using CA WA Desktop Client. CA WA
Desktop Client has four main components named perspectives: Define,
Monitor, Services, and Admin. Other perspectives are SAP Tools and CLI.
Depending on your account permissions, you may not have access to all of the
perspectives.

Use the Define perspective to define your workload. The Define perspective
lets you create graphical representations of jobs and their relationships and
define detailed scheduling requirements for jobs.

Using the default connection set at installation time

1. Open CA WA Desktop Client in one of the following ways:

Select Start, Programs, CA, WA Desktop Client, CA WA Desktop Client.

Double-click the CA Workload Automation Desktop Client icon on your

desktop.

2. In the Connect to Server dialog, enter your user name and password, and
then click Connect.

3. In the Welcome Screen, click the Define icon.

The Define perspective appears.

Chapter 2: Define Your Workload 15

Step 2: Define an Application

Step 2: Define an Application

To set up the scheduling scenario in this tutorial, you will first define an
Application. When you have defined this Application, you will schedule an
Event to run the Application at 4 p.m. daily. Then, you will define the six jobs
in the Application.

An Application consists of one or more jobs. A job can be an executable file, a

task representing a manual process, or a database query. Two examples of
executable files are command files and UNIX scripts.

Usually, jobs in an Application are related. For example, all of your payroll jobs
may be in one Application. An Application may contain jobs that run on the
same platform or it may have jobs that run on different platforms.

To define a new Application

1. Open the Define perspective.

2. In the Application Workspace view, right-click the CA WA server you want

to create the Application on, then select New.

The Application properties dialog opens.

3. In the Name field, enter a name for your Application. For this tutorial,
enter quick_name where name is your first name.

Usually, you will choose a name to reflect the line of business, such as
Payroll, Inventory, Housekeeping, or Order_Processing.

There are few limitations on Application names. For security reasons, your
server administrator can restrict the Application names you can use.

The name is not case sensitive; the name automatically enters in

uppercase letters.

Do not use special characters (such as punctuation marks, brackets,

and spaces). To enter a name with more than one word, you can use
an underscore to separate the words.

You can choose a name with up to 128 characters.

Note: Fields marked with an asterisk (*) are mandatory.

4. Select Wait for previous generation.

Each time an Application runs, the server creates a unique instance named
a generation and assigns the next sequential generation number for that
Application. In many cases, you may want one generation to complete
before the next one begins. For example, you may not want to process
Tuesdays payroll until Mondays payroll is complete.

In this tutorial, each time your Application is scheduled, it must wait for all
previous generations of the Application to complete before it starts
processing.

16 Getting Started
 Step 3: Schedule your Application using an Event

5. In the Agent field, select the agent that will run all jobs in the Application.

For this tutorial, if you are using the default agent installed with the
server, select AGENT. If your server administrator specified another name
for the default agent, select that name instead.

If you are using an agent other than the default, select that agent name.

6. Click OK.

The Application properties dialog closes and your Application workspace

appears.

More information:

Setting Application and job properties (see page 45)

Step 3: Schedule your Application using an Event

The CA WA server uses an Event to determine when and how often to run an
Application. Most Events are scheduled Events. An Application with a
scheduled Event runs according to a specified date and time. You can also run
an Application by triggering the Event manually or triggering the Event by a
particular condition (such as a file being created).

Understanding the relationship between Events and Applications

The following diagram shows the relationship between an Event, an Application
definition, and an active Application. An Event named CYBER.PAYROLL is
scheduled at 4 p.m. each day to run the Payroll Application. The Payroll
Application definition includes six Windows jobs. Some of these jobs run daily,
one job runs weekly, and one job runs monthly. When you schedule an Event,
the CA WA server determines which jobs should be selected to run that day.

Chapter 2: Define Your Workload 17

Step 3: Schedule your Application using an Event

This diagram shows the four jobs that run daily in the active Payroll
Application.

Defining the default Date-Time/Manual Event

When you define a new Application in the Define perspective, the CA WA

server defines a default Date-Time/Manual Event that lets you schedule the
Application or run the Application manually.

For this tutorial, you will schedule the Event to run the Application at 4 p.m.
daily.

1. In your Applications Event Triggers workspace, double-click the Event, or

right-click the Event and select Edit.

The Event Trigger Properties dialog opens.

For this tutorial, we will use the default Event properties:

Event Prefix (your server user ID)

An Event name has two parts: a prefix and a descriptive name.

The prefix lets you group Events. You can list Events based on their
prefix. For example, all of your production Events could have a PROD
(or PRODUCTION) prefix and all of your test Events could have a TEST
prefix.

You can choose a prefix with up to 32 characters. CA WA Desktop

Client converts the prefix to uppercase.

18 Getting Started
 Step 3: Schedule your Application using an Event

Event Name (your Application name)

The Event Name must be unique. Usually, this name will be the same
as your Application name.

You can choose a name with up to 128 characters. The server converts
this name to uppercase.

Specify Calendars

This Event does not require a special calendar definition. If you do not
specify a calendar, the server uses the SYSTEM calendar, which is the
default calendar for storing scheduling terms unique to your
installation.

Specify Application to run (your Application name)

The Event runs the Application it is defined for.

2. From the left pane, click Schedule.

The Schedule dialog opens.

3. Click Add Schedule.

A new schedule criteria entry appears.

4. In the When field, type 4pm daily.

Note: You can use uppercase or lowercase. Do not use periods (a.m. or
p.m.).

You can also use the Schedule event dialog to specify your scheduling
criteria.

a. In the When field, click the ellipses (...).

The Schedule event dialog opens.

b. If not already selected, select Use generated statement.

c. Select the appropriate phrase or term in the order you want it to

appear in your schedule statement.

d. In the Schedule event dialog, click OK.

The Schedule event dialog closes and your schedule criteria appears in
the Schedule dialog.

5. In the Schedule dialog, click OK.

Your Event is now defined to run the Application at 4 p.m. daily.

Note: For more information on scheduling criteria, see the Define Perspective
Help.

Chapter 2: Define Your Workload 19

Step 4: Define jobs in your Application

Step 4: Define jobs in your Application

The Application workspace in the Define perspective has a Workload Objects
palette containing an icon for each job type you can define in an Application.
Use the workspace to create a workload diagram, which is a graphical
representation of the jobs in your Application.

For this tutorial, use one of the following icons to create your workload
depending on the computer your agent is installed on.

Windows

UNIX

You can customize the Workload Objects palette to show only the workload
objects you need.

More information:

Removing types of workload objects (see page 46)

Adding jobs to the workspace

1. Drag and drop the Windows or UNIX icon from the Workload Objects
palette to the Application workspace.

An icon representing the job appears in the Application workspace. The job
is assigned a default job name (for example, UNIX_0).

2. Add another five Windows or UNIX jobs onto the workspace in positions
similar to the diagram shown below.

For example,

If a job must run after another job, place it below that job on the
workspace.

If a job can run at the same time as another job, place it beside that
job on the workspace.

Note: You dont need to click the icon on the job palette again. Simply
click the mouse as many times as necessary on the workspace and CA WA
Desktop Client will place the same icon there until you choose another
type. When you select an item from the Workload Objects palette, it
remains selected until you select another item.

Dont worry about the layout; you will use an icon later to tidy it.

20 Getting Started
 Step 4: Define jobs in your Application

Your diagram should look like one of the following diagrams:

Defining the relationships between jobs

The next step is to draw lines to represent the dependencies between the jobs
in your Application.

1. Click the Dependencies icon in the toolbar.

Your cursor displays as a single link chain. You will use it to create
relationships between jobs by connecting them with lines.

2. Click the Windows_0 or UNIX_0 job in your Application and hold the left
mouse button.

3. Drag the mouse from the selected job to the second job (its successor) in
your workload (for example, between Windows_0 and Windows_1).

A line appears indicating the jobs dependency.

4. Release the left mouse button.

5. Click and drag the mouse to draw lines from each of the jobs to their
successors. Repeat this step until you have drawn all the dependencies.

Chapter 2: Define Your Workload 21

Step 4: Define jobs in your Application

Your diagram should look like one of the following diagrams:

6. Click the Layout icon in the toolbar.

Your Application and its job dependencies are shown in an organized

layout.

Defining job details for each job

Now you will specify details for each of the jobs in your Application. For each
job, you will specify the following:
The job name
The jobs run frequency (when the job is to run)
The command file or script to run

Note: You do not have to specify the agent name in the job definition because
you set a default agent for all jobs in this Application when you defined the
Application properties.

Note: The defaults you define in the Application properties apply to all jobs in
the Application, regardless of job type. If you want to specify a default for a
particular job type, use job defaults instead.

For this tutorial, you will start by specifying the job details for the first job.

22 Getting Started
 Step 4: Define jobs in your Application

Open the job definition dialog

Double-click the first job (Windows_0 in this example) in your workload

diagram, or right-click the job and select Edit.

The job definition dialog opens.

Fields marked with an asterisk (*) are mandatory. An error message appears
at the top of the dialog until all required fields are filled in.

Name the job

In the Name field, type A as the name of the job you are defining. Job names
are not case sensitive.

The job icon takes the name you enter here.

Usually, the job name reflects the command file or script you are running. Job
names must be unique in an Application, although you can use a qualifier to
distinguish same-named jobs. Job names are limited to 128 characters and
qualifiers are limited to 64 characters.

Specify when a job is to run

In the Run frequency section, leave the default run statement.

By default, all jobs in the Application are set to run daily.

Later, you will specify different run frequencies for some of the jobs in the
Application.

Chapter 2: Define Your Workload 23

Step 4: Define jobs in your Application

Specify command file or script to run

To specify a command file for Windows workload

1. In the Command to run field, type

installDir\Resources\TestScripts\echo.bat

where installDir is the directory in which the CA WA server is installed.

If the command file is located in another directory, type that path instead.

Note: If your path has spaces, enclose the path with double quotes.

You can also browse for the file using the Command Browser.

2. Click OK.

To specify a script for UNIX workload

By default, Run a script is selected in the Specify action to take section.

1. In the Script/command name field, type

installDir/Resources/TestScripts/echo.sh

where installDir is the directory in which the server is installed.

If the file is located in another directory, type that path instead.

You can also browse for the file using the Script/Command Browser.

2. Click OK.

Repeat steps for other jobs

When you have finished defining job A, repeat the steps for B, C, D, E, and F.
Use the following chart as a guide when defining the job name and run
frequency for each of your jobs.

Job Name Run Frequency

B daily

C daily

D daily

E friday

F last workday of month

All of the jobs in this Application will run the same batch or script file as A.

24 Getting Started
 Step 4: Define jobs in your Application

Specifying different run frequencies for jobs E and F

By default, jobs are set to run daily. In this tutorial, you will specify different
run frequencies for jobs E and F.

To specify the run frequency for E

1. In the Run frequency section, clear Use Application-level defaults.

2. In the When field for the existing run frequency, type friday.

This information is not case sensitive. The CA WA server understands

many common scheduling terms. For terms that are unique to your
organization, you can create holiday and special-day definitions and add
them to the servers vocabulary.

Note: For more information on scheduling criteria, see the Define

Perspective Help.

3. Click OK.

To specify the run frequency for F

1. In the Run frequency section, clear Use Application-level defaults.

2. In the When field for the existing run frequency, click the ellipses (...).

The Run dialog opens.

3. Select the appropriate phrase or term in the order you want it to appear in
your Run statement.

To specify last workday of month in the Run dialog, do the following:

a. Select Use generated statement.

b. In the Occurrences section, clear Every, then select Last.

c. In the Type of Day section, select workday.

d. In the Period section, select month.

last workday of month appears in the Use generated statement

field.

e. Click OK.

Note: You can also type the run frequency for the job in the When field.
For example, if a job runs on the last workday of the month, type

last workday of month

Note: Click Show in calendar and select a month and year to view when
the job will run based on its run frequencies.

Chapter 2: Define Your Workload 25

Step 4: Define jobs in your Application

Later, you will learn how to test different criteria to see how the server
interprets them. You can define a single condition or you can create a list of
conditions under which a job should run or not run. Each run frequency
appears as a RUN statement followed by the conditions under which the job
runs.

Passing arguments to job D

The CA WA server gives you powerful substitution capabilities through

symbolic variables. When the server encounters a symbolic variable, it
substitutes the current value of that variable. For example, you can use
symbolic variables to define date parameters, specify job names, define job
dependencies, pass arguments to scripts, and so on. The server has several
built-in symbolic variables you can use in your Applications. You can also
define and use your own symbolic variables.

For this tutorial, you will pass three server built-in date variables as an
argument string of positional parameters to a command file or script. When
the command file or script runs, it simply echoes the resolved values of these
three variables. Later, you will learn how you can view the resolved variables
directly from CA WA Desktop Client.

To specify arguments for job D

1. Double-click D in your workload diagram, or right-click D and select Edit.

The job definition dialog opens.

2. In the Arguments to pass field, enter the following in uppercase:

%APPL._SMM%APPL._SDD%APPL._SYY

This string consists of three variables. It passes as a single argument to

the command file. Each variable begins with the percent sign (%). The
following table describes the variables:

Variable Description

%APPL._SMM Number of month (for example, 09 for

September)

%APPL._SDD Number of day of month (for example,

19)

%APPL._SYY Last two digits of the year (for example,

06)

3. Click OK.

26 Getting Started
 Step 5: Save the Application and upload it to the server

Step 5: Save the Application and upload it to the server

When you have finished specifying details for all of the jobs, you can save a
backup copy of your Application file locally.

To save the Application

1. In the Application Workspace view, right-click your Application name and

select Save As.

The Save As dialog opens.

2. Browse to the directory in which you want to save your Application.

By default, the CA WA server stores your Applications in

installDir\plugins\com.cybermation.workloadeditor_2.0.0\Resources\

where installDir is the directory in which the CA WA Desktop Client is

installed.

3. Ensure the File name field has QUICK_NAME where NAME is your first
name.

4. Click Save.

For the server to process your Application, you must upload the Application to
the server.

To upload your Application

1. Ensure all of your jobs are defined.

No job should have a red box around it. If a red box surrounds a job, you
may have omitted its command file name. Open the job definition dialog to
ensure all of the necessary information is there.

2. In the Application Workspace view, click the Upload icon, or right-click

your Application name and select Upload.

Note: If Upload is not accessible, you are not connected. Reconnect to the
server.

The Upload Application To Repository dialog opens.

3. Click OK.

A confirmation message appears in the Console View, which displays

messages sent from the server, indicating that the Application is defined.
The Event trigger icon in your Application workspace has a green box
around it indicating that the Event is uploaded to the server.

The Application is now uploaded and you have finished defining your
Application. Your Application is stored in the servers database.

Chapter 2: Define Your Workload 27

Step 6: Test what will run using Event simulation

More information:

Open the job definition dialog (see page 23)

Step 1: Connect to the server using CA WA Desktop Client (see page 15)

Step 6: Test what will run using Event simulation

Use the simulation feature to see a graphical representation of an Application
for particular schedule criteria. You can simulate an Events next execution,
future execution, or past execution. Simulation helps you identify problems
before an Application runs.

The schedule criteria you use for simulation are similar to those you use when
you define job schedule criteria. You can use absolute dates (Nov 6, 2006),
terms based on holiday or special-day definitions (Christmas less 1 workday),
or more general terms (last workday of May).

For this scenario, you will simulate the following criteria for the Event:
The Events next execution
Friday
Last workday of month

Simulate the Events next execution

The default criteria for simulation is the Events next scheduled execution or
now if the Event is not scheduled. To simulate the Events next execution, you
do not have to fill in any of the fields on the Simulate Event dialog.

1. In your Applications Event Triggers workspace, right-click the Event

trigger and select Simulate.

The Simulate Event dialog opens.

2. Leave the Schedule criteria field blank.

Your Event will simulate for the next scheduled execution.

3. Click OK.

A graphical representation and a text-based representation of the

Application appear. If the time is before 4 p.m., you will see which jobs are
selected today. Otherwise, you will see which jobs will be selected the next
day. E appears if it is Friday and F appears if it is the last workday of the
month.

4. Click OK to close the simulation.

28 Getting Started
 Step 6: Test what will run using Event simulation

Simulate for Friday

1. In your Applications Event Triggers workspace, right-click the Event
trigger and select Simulate.

The Simulate Event dialog opens.

2. In the Schedule criteria field, type friday.

Your Event will simulate for the next occurrence of Friday.

3. Click OK.

A graphical representation and a text-based representation of the

Application appear. If Friday is the last workday of the month, you will see
job F as well.

4. Click OK to close the simulation.

Simulate for the last workday of the month

Jobs in an Application may not require the same run frequency. When the CA
WA server selects jobs for submission, it automatically checks if the jobs
should inherit any relationships from other jobs.

The last workday of month schedule criteria could result in two different
graphical representations.

1. In your Applications Event Triggers workspace, right-click the Event

trigger and select Simulate.

The Simulate Event dialog opens.

2. In the Schedule criteria field, type last workday of month.

You can also click the ellipses (...) to use the Simulate dialog to specify the
jobs schedule criteria.

Your Event will simulate for the next occurrence of the last workday of the
month.

3. Click OK.

After a status message appears, you will see both a graphical

representation and a text-based representation of the Application.

If the last workday of the month is not a Friday, job F will wait for D to
complete before it runs. Five jobs will appear in the simulation. As you can
see, the server automatically inherits job relationships.

If the last workday of the month is a Friday, F will wait for E to complete
before it runs. Six jobs will appear in the simulation.

4. Click OK to close the simulation.

Chapter 2: Define Your Workload 29

Step 7: Test schedule criteria

Step 7: Test schedule criteria

Testing is useful when you want to see how the CA WA server interprets
different scheduling terms and phrases. When you simulated your Event for
the scheduling scenario, you might have wanted to determine a date when the
last workday of the month is a Friday and a date when the last workday of the
month is not a Friday.

You can determine such dates by testing schedule criteria.

To test schedule criteria

1. Click the Test icon in the toolbar.

The Test Schedule Criteria dialog opens.

2. In the Use free format statement field, type the schedule criteria you want
to test, such as last workday of month.

3. Click Test.

The dates for the next 10 times the job will run appear in the Test Results
text box.

Note: To change the number of results shown, enter the number of results
you want to see in the Display field.

4. Verify that the results are those you expected.

If they are not, change the criteria to achieve the desired results and test
again.
Note: If you want to simulate your Event for other criteria, you can
choose dates or terms from the Test results list. For example, you can see
which jobs are selected when the last workday of the month is not a Friday
by simulating your Event for October 31, 2006 (the last workday of
October, which occurs on a Tuesday). To see which jobs are selected when
the last workday of the month is a Friday, simulate your Event for
September 29, 2006 (the last workday of September, which occurs on a
Friday).

5. Click Close to close the Test Schedule Criteria dialog.

Next you will learn how to run your Application.

30 Getting Started
Chapter 3: Run Your Workload
When you have defined an Event in an Application and uploaded the
Application to the CA WA server, the Application runs automatically according
to the scheduling criteria or trigger specified in the Event.

In this tutorial, you defined a Date-Time/Manual Event to run your Application

at 4 p.m. each day.

You will now learn how to run the Event immediately by manually triggering
the Event. You will use the Define perspective to run your workload.

Chapter 3: Run Your Workload 31

Triggering your Event manually

Triggering your Event manually

When triggering an Event manually, you can add a new scheduled Event. In
this tutorial, instead of waiting until 4 p.m., you will learn how to add an Event
to run the Application now as well as at 4 p.m. today. You will manually trigger
the Event without affecting what is already scheduled.

To manually trigger an Event

1. Ensure that your Application is open in the Define perspective.

2. In your Application's Event Triggers workspace, right-click the Event

trigger and select Trigger.

The Trigger Event dialog opens.

3. Leave the Schedule criteria field blank.

The Event will be triggered immediately.

4. Leave Add new scheduled Event as selected.

The Event will run now in addition to its 4 p.m. schedule.

5. Select Submit Application on hold.

The Application will not run until it is manually released. In this tutorial,
you are holding the Application before its jobs start to run so that you can
view the different job states when you monitor the workload.

6. Click OK to trigger the Event.

Note: You can also list and control Events from the Events view in the
Services perspective. For more information on listing and controlling Events
from the Services perspective, see the Services Perspective Help.

Next, you will learn how to view your Application as it is running.

32 Getting Started
Chapter 4: Monitor Your Workload
When you have triggered the Event to run your Application, you can monitor
your Application's state, view its details and jobs, and issue commands against
your Application. You will monitor your workload in the Monitor perspective.

This section contains the following topics:

Viewing your workload using subscription filters (see page 34)

Controlling your Application (see page 35)
Monitoring your Application (see page 36)
Controlling your jobs (see page 37)
Using a custom view to monitor and control workload (see page 39)

Chapter 4: Monitor Your Workload 33

Viewing your workload using subscription filters

Viewing your workload using subscription filters

The Monitor perspective organizes and displays Applications and their
generations. To view Applications and their generations, you must subscribe to
the Applications to receive the data from the CA WA server.

For this tutorial, you will subscribe to all active Applications (Applications that
are not complete) on the server.

To view generations of an Application

1. In CA WA Desktop Client, click the Monitor icon.

The Monitor perspective appears.

2. In the Application Monitor view, right-click the server connection name

that contains your Application and click Subscribe Active to see all active
Applications you have access to.

A plus sign (+) appears beside the server connection name.

3. Click the + or double-click the server connection name.

A list of all active Applications you have access to appears. Each

Application displays as a folder labeled with the Application name and the
number of generations that Application has.

4. Click the + or double-click the QUICK_NAME folder (where NAME is your

name).

The Application folder expands and a folder for each generation of this
Application appears. Each generation is color-coded based on the
Application's state.

5. Double-click the Application generation you want to view.

A graphical view of your Application appears.

Next, you will learn how to manually release the Application to run the
workload.

34 Getting Started
 Controlling your Application

Controlling your Application

You can issue commands against an active Application (Applications that are
not complete). For example, you can do the following:
Hold an Application while it is running and stop further job submission in
that Application.
Release an Application that was triggered on hold.
Insert jobs into the Application.
Complete the Application. When you complete an Application, all jobs in
the Application are considered to have executed even if they have not
been submitted, have failed, or are still running.

To view a list of commands that you can issue against an active Application,
right-click the Application generation in the Monitor perspective.

In this tutorial, you will release your Application.

Releasing your Application

In this tutorial, you selected Submit Application on hold when you triggered
your Event. To run the Application, you must release it.

1. In the Monitor perspective's Application View, right-click the Application

generation and select Release.

The Release dialog opens.

2. Click OK to release the Application.

The Application is released.

Note: Applications can be defined with the Hold on submission option selected
in the Application properties. To run Applications that are defined on hold, you
must also release them.

Chapter 4: Monitor Your Workload 35

Monitoring your Application

Monitoring your Application

The following is an example of an Application that is processing, as it appears
in the Monitor perspective.

As the jobs in the Application pass through different states, the text below the
job name indicates the job's state and the border surrounding the job icon
changes color.

In the preceding example

A and B are in the COMPLETE state.

Note: If A remains in an AGENTDOWN state, it means the agent is not

running. Speak with your administrator.
C is in an EXEC state. This state means the job is executing.
D is in a PREDWAIT state. This state means it is waiting for the
predecessor jobs (both B and C) to complete.

Note: If a job goes into a SUBERROR state, it usually means the path to the
command file, script, or command is wrong.

36 Getting Started
 Controlling your jobs

More information:

Handling submission errors (see page 38)

Controlling your jobs

In addition to viewing and controlling your Applications, you can issue
commands against a job. For example, you may need to view comments about
a job, resubmit a failed job, reset a time dependency for a job, view a job's
details (such as its start and end times and the path to its command file) or
cancel (bypass) a job from the schedule.

To view a list of commands you can issue against a job, right-click the job in
the Monitor perspective.

Note: You require the appropriate security permissions to issue commands

against jobs. The commands you can issue depend on the workload object and
its state.

In this tutorial, you will learn how to display a job's details, handle submission
errors, and display a job's output.

Displaying job details

In the Monitor perspective's Application View, double-click job A, or right-click

A and select Details.

The Details dialog opens.

Chapter 4: Monitor Your Workload 37

Controlling your jobs

Handling submission errors

If a job goes into a SUBERROR state, this indicates a submission error. The
path to the command file, script, or command might be wrong. In the Monitor
perspective, double-click the job. The Details dialog opens. If the Status field
says File not found or Command file not found, the CA WA server could not
find the file to run.

To correct a submission error

1. Right-click the job and select Reset Definition.

The Reset Definition dialog opens.

2. In the Command to run field (Windows) or Script/command name field

(UNIX), type the correct location of the script or command file. You can
also click the browser icon to browse for the script or command file.

3. Click OK to save your changes.

These changes are temporary. You can make your changes permanent by
returning to the Define perspective, changing the job's details, and re-
uploading the Application.

4. Right-click the job and select Resubmit.

The Resubmit dialog opens.

5. Click OK to resubmit the job.

The job completes successfully.

38 Getting Started
 Using a custom view to monitor and control workload

Displaying job output

In this tutorial, job D echoes the CA WA server built-in variables that were
passed as arguments to the batch file or script. The job's output is stored in a
spool file. You can display the spool file in the Monitor perspective.

Depending on the type and version of the agent that runs the job, you can
view the entire spool file, selected lines, or a number of lines you specify.

To view the spool file for job D

1. Right-click D and select Retrieve Spool File.

The Retrieve Spool File dialog opens.

2. Since the file for D is very small, click Retrieve All to retrieve the entire
spool file.

The server displays the job's output in the dialog.

3. Review the output to see the resolved variables.

You should see three numbers, representing the two-digit month, day, and
year. For example, for a scheduled date of February 14, 2006, you should
see 021406.

4. Click Close to close the dialog.

Using a custom view to monitor and control workload

CA WA provides custom views for monitoring and controlling your workload.
You can also create your own text-based custom views to display only the
information you want, in the format you want.

A custom view looks like a table; it contains rows and columns of information.
While an Application's graphical view focuses on a particular generation of an
Application, a custom view can span many different Applications. For example,
CA WA provides a custom view named Failed, which displays all failed jobs
regardless of the Application they belong to.

Chapter 4: Monitor Your Workload 39

Using a custom view to monitor and control workload

Creating a custom view

This section walks you through the process of creating a custom view that
shows only the QUICK_NAME Application.

1. In the Monitor perspective, click the Custom Views tab.

A list of custom views appear.

2. Click the Create a New Custom View icon.

The Custom View Configuration dialog opens.

3. In the Custom view name field of the Presentation dialog, enter a name for
your custom view. For this tutorial, type My Quick Application.

4. Click the double right arrow (>>) to select all fields for your display.

All the fields in the Available fields list box moves into the Selected fields
list box.

Note: You can shorten a field name by entering an alias for the field name
in the Alias column. For example, you can type gen # for Generation
Number.

Sorting the information in your custom view

In this tutorial, you will sort the information in your custom view by generation
number, and then by job name.

1. In the Presentation dialog, for the Generation Number field name, click in
the Sort column and select Ascending.

The information in your custom view will be sorted from the lowest
Application generation number to the highest Application number.

2. For the Job Name field name, click in the Sort column and select
Ascending.

When the information in your custom view is sorted by Application

generation number, the information will be sorted by job name
alphabetically (from A to Z).

3. Click Apply.

Note: When you have created your custom view, you can also click the
column heading in your custom view to sort by that column. Sorting the
information this way temporarily overrides the sort defined in the Custom View
Configuration.

40 Getting Started
 Using a custom view to monitor and control workload

Filtering the information in your custom view

You will set up a filter to display only the QUICK_NAME Application. You build a
filter using different fields and operators.

1. From the left pane, click Filter to open the Filter dialog.

2. Click Add.

3. In the Field Name field, click the down arrow and select Application Name.

4. In the Relationship field, click the down arrow and select Is.

5. Click in the Value column and type quick_name, where name is your
name.

The Application name is not case sensitive.

6. Click Apply.

The completed filter criteria appear in the Result text box.

Note: You can also click any area in the Criteria table outside of the
selected row to apply your filter criteria.

7. Click OK.

The Custom View Configuration dialog closes and your custom view is
added to the Custom Views view.

Controlling jobs from a custom view

You can use the custom view to control jobs in Applications. Controlling jobs
using the custom view is similar to controlling jobs using the graphical view.
From a custom view, you can also locate a job in the graphical view.

1. Double-click My Quick Application in the Custom Views view to open the

custom view you created.

2. In the custom view, right-click the job you want to control and select a
command.

Chapter 4: Monitor Your Workload 41

Using a custom view to monitor and control workload

Controlling Applications from a custom view

You can also control Applications in a custom view.

1. Double-click My Quick Application in the Custom Views view to open the

custom view you created.

2. In the custom view, right-click a job in the Application generation you

want to control and select Application commands.

3. From the drop-down menu, select a command.

For example, select Details to see the Application details.

You have now completed the Getting Started tutorial.

Note: To learn more about scheduling and running workload, see the Define
Perspective Help and the Monitor Perspective Help.

The next chapter provides tips on using CA WA Desktop Client.

42 Getting Started
Chapter 5: CA WA Desktop Client Tips
This chapter describes tips you can use to customize CA WA Desktop Client.

This section contains the following topics:

Using online help (see page 43)

Adding a new server connection (see page 44)
Setting Application and job properties (see page 45)
Moving perspective icons (see page 46)
Removing types of workload objects (see page 46)
Moving views around (see page 47)
Resetting your workspace (see page 47)

Using online help

While you are using CA WA Desktop Client, you can access the following help:

Context-sensitive help

Click the help icon (?) or press F1 to get help about a dialog, view, or
page. A description appears along with links to related help topics.

Task-based help

From the Help menu, click Help Contents. You can access the following
help books:

Define Perspective Help

Monitor Perspective Help

Services Perspective Help

SAP Tools Perspective Help

CLI Perspective Help

Admin Perspective Help

To navigate the Help, expand the topics in the Contents pane on the left
side of the page, then click an entry to display its information.

Click the Index tab at the bottom of the left pane to display the Help
Index. Enter a term in the text box and click Display to display matching
index entries; click an index entry to display associated information.

To search the Help, enter a keyword or phrase in the Search field, then
click GO to locate the specified text in the Help and display search results
in context in the left pane. Click a result link in the left pane to open a
topic.

Chapter 5: CA WA Desktop Client Tips 43

Adding a new server connection

Adding a new server connection

If you are not using the default server connection and your server connection
is not listed in the Connection name field, you can add a new connection for
your server.

1. Open CA WA Desktop Client.

2. In the Connect to server dialog, click Work Offline.

3. In the Welcome Screen, click the Define icon.

The Define perspective opens.

4. Click the Connections icon.

The Connections view opens.

5. Click the new connection icon.

The New Connection dialog opens.

6. In the New Connection dialog, complete the following fields:

Connection name Name for the server connection

IP address Domain name or IP address of the server you want to

connect to

Port number Client port number for the server you want to connect
to. The default is 7500.

User name Your server user name. Your user name is automatically
converted to uppercase.

Password Your server password. This password is case sensitive.

Retry count Number of times you want to try connecting to the

server

Server type Type of server you are connecting to. For this tutorial,
select CA Workload Automation.
If you do not know the connection information, talk to your server
administrator.

Note: For servers in high availability installations, when the Primary fails
over, CA WA Desktop Client automatically connects to the Standby. CA WA
Desktop Client notifies you of the switch from the Primary to Standby
through a message in its Console View. To prevent automatic
reconnection, select Prevent auto-connection on failover. This feature is
useful if, for example, you are using manual failback and want to switch to
a specific server.

7. Click Save and Connect.

The new connection name appears in the Application Workspace view.

44 Getting Started
 Setting Application and job properties

Note: You can connect to multiple servers at one time. If you connect to
multiple servers, you can view all workload on the different servers that you
have access to.

Setting Application and job properties

You can set properties for the following:
All Applications you define (Application defaults)

For example, you can set up a global email notification that sends an email
to an operator when any job in any Application fails.
A specific Application and its jobs (Application properties)

For example, in this tutorial, you selected a default agent in the

Application properties. All jobs in the Application run on that agent's
computer, unless specified differently in the job details. Job details
override Application properties.
All jobs of a particular type in a specific Application that run on the same
platform (job defaults)

For example, you can set up an email notification that sends an email to
an operator whenever a UNIX job in a specific Application fails.
A specific job (job details)

For example, you can specify when a specific job runs (or does not run).

The property that applies to an Application or job depends on where you set
the property. Defaults set at certain levels can be overridden by properties set
at other levels.

Properties Description Overridden by

Application defaults Properties common to all Application properties

Applications you define.
Job defaults
Specify Application
defaults prior to creating a Job details
new Application.

Application properties Properties that apply to a Job defaults

particular Application.
Job details
Properties that apply to all
jobs in the Application.

Job defaults Properties that apply to all Job details

jobs of a particular type in
a specific Application that
run on the same platform.

Chapter 5: CA WA Desktop Client Tips 45

Moving perspective icons

Properties Description Overridden by

Job details Properties that apply to a None. Job details override

particular job. all other defaults.

More information:

Step 2: Define an Application (see page 16)

Moving perspective icons

You can move the perspective icons to other areas of your workspace.

1. Right-click the Open Perspective icon or one of the perspective icons.

2. Select Dock On > Top Right to display the perspective icons at the top-
right corner of CA WA Desktop Client.

You can also select Dock On > Left to display the perspective icons in a
vertical menu.

Removing types of workload objects

You may not need all of the workload objects in the Define perspective's
Workload Objects palette. You can choose which workload objects to show.

1. In an Application's Workload Objects palette, right-click anywhere in the

palette and select Filter.

The Workload objects palette filter dialog opens.

2. Clear the types of workload objects you do not want to show in the
Workload Objects palette. By default, all types of workload objects are
selected.

3. Click OK.

The Workload Objects palette is customized to your preferences.

46 Getting Started
 Moving views around

Moving views around

You can move views around in your workspace.

1. Click the view's title bar to select it.

For example, if you have multiple custom views open in the Monitor
perspective, select one of them. By default, custom views open as tabbed
views.

2. Drag the view to the area where you want it placed.

Depending on where you are moving your view, your cursor changes to a
folder icon or an arrow icon. A gray outline of the view appears, indicating
how your view will be placed.

3. Drop the view to the area where you want it placed.

The view is moved to the new location.

For example, you can move custom views around so that the views are
tiled in your workspace.

This setting is preserved. The next time you open the Monitor perspective,
the custom views you moved are tiled in your workspace.

Resetting your workspace

At times, you may find your workspace cluttered with too many open or tiled
views. To fix this, you can reset the perspective to its original settings.

1. Right-click the perspective icon and select Reset.

The Reset Perspective dialog opens.

2. Click OK to reset the perspective to its defaults.

Chapter 5: CA WA Desktop Client Tips 47

Index
commands
A Application 35
active Applications 34, 35 COMPLETE state 36
AGENTDOWN state 36 connection
agents adding 44
default 10, 16 default 15
defined 8 multiple servers 44
specify 16 Console View 27
Applications controlling
active 34, 35 Application from custom view 42
commands 35 Application from graphical view 35
controlling from custom view 42 job from custom view 41
default properties 45 job from graphical view 37
defined 16 creating
defining 16 custom view 40
details 42 dependencies 21
generations 16, 34 Event 18
monitoring 36 test file 11
naming 16 workload diagram 20
on hold 35 custom views
properties 16, 45 controlling Application 42
relationship to Event 17 controlling job 41
saving 27 creating 40
uploading 27 defined 39
using 16 fields 40
arguments, passing 26 filters 41
name 40
B sorting 40
customize CA WA Desktop Client 43
browsing, command file or script 24, 38
built-in variables 26 D
C Date-Time/Manual Event 18
Define perspective
CA WA
about 15
components of 7
opening 15
overview 7
defining
CA WA Desktop Client
Application 16
customize 43
Application on hold 35
defined 8
Event 18
perspectives 15
job 20
using 15
relationships between jobs 21
CA WA Server
workflow 13
connecting to 15
definition, job 22
defined 7
dependency lines 21
calendars
displaying
calendars 18, 25
Application details 42

Index 49
 job details 37 inheritance
job output 39 defined 29
docking perspective icons 46
J
E
jobs
Events controlling from custom view 41
creating 18 controlling from graphical view 37
default Date-Time/Manual 18 defaults 45
defined 17 defined 23
defining 18 defining 20
function 17 details 22, 37, 45
naming 18 inheriting relationships 29
prefix 18 naming 23
schedule criteria 18 output 39
simulating 28 properties 45
specifying Application to run 18 relationships 21
triggering manually 32 resubmitting 38
triggers 18 run frequency 23, 25
using 17 states 36, 38
using to schedule an Application 17
EXEC state 36 L
layout, organizing 21
F
fields M
fields, custom view 40 manual trigger 32
filter Monitor perspective
custom view 41 defined 34
subscription 34 opening 34
frequency monitoring
Event 18 Application 36
job 23, 25 workload 33
moving
G
perspective icons 46
generations views 47
Application 16, 34
graphical view N
controlling Application 35 naming
controlling job 37 Application 16
Event 18
H
job 23
help
help, using 43 O
online help 43
I
opening
icons Define perspective 15
for jobs 20 Monitor perspective 34
for perspectives 46 output for job 39
placing on workspace 20

50 Getting Started
P script 24
spool file
passing arguments 26 spool file, retrieving 39
perspectives state
defined 15 AGENTDOWN 36
moving icons 46 COMPLETE 36
PREDWAIT state 36 EXEC 36
prefix, Event 18 PREDWAIT 36
properties SUBERROR 36, 38
Application 16, 45 SUBERROR state 36, 38
Event Trigger 18 submission error 38
job 45 submitting Application on hold 32, 34, 35
subscribing to Applications 34
R
symbolic variables
releasing symbolic variables 26
Applications 35
removing types of workload objects 46 T
resetting testing
workspace 47 schedule criteria 30
resubmitting failed jobs 38 what will run 28
retrieving trigger Event
spool file 39 manually 32
run frequency
specifying 23, 25 U
running workload 31
uploading Applications 27
S V
saving Application 27
variables
schedule criteria
built-in 26
Event 18
symbolic 26
simulation 28
viewing
testing 30
Application details 42
triggering Event 32
job details 37
scheduling
job output 39
Event 18
spool file 39
job 23, 25
workload 34
steps 10
views, moving 47
setting
Application properties 45 W
job properties 45
simulating 28 wait for previous generation 16
sorting, custom view 40 workload
specifying defining 13
agent 16 diagram 20
Applications 18 monitoring 36
arguments 26 objects 20, 46
command file 24 running 31
job name 23 workspace, resetting 47
run frequency for job 23, 25

Index 51