ESP Workload Manager

Version 5.5

Getting Started

ESP-5.5-GS-01
First Edition (June 2007)
This documentation and any related computer software help programs (hereinafter referred to
as the “Documentation”) is for the end user’s 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 user’s 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 user’s
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 © 2007 CA. All rights reserved.
 Contents

1 ESP Workload Manager Basics 1

An ESP Workload Manager enterprise ............................................................... 2
ESP Workload Manager............................................................................... 2
ESP Agents .................................................................................................. 2
ESP Workstation.......................................................................................... 2
A brief introduction to ESP Workload Manager ................................................ 3
Using ESP Workload Manager calendars ........................................................... 4
How ESP Workload Manager uses calendars ............................................... 5
Defining what will run ....................................................................................... 5
ESP Applications and Procedures ................................................................. 5
A sample scenario......................................................................................... 6
Creating an Application in Workload Editor................................................ 7
Scheduling your jobs ........................................................................................ 10
ESP Events................................................................................................. 10
Simulating what will run.................................................................................. 12
Running your jobs ........................................................................................... 14
Monitoring your jobs ....................................................................................... 15
Workload Director—graphical views and custom views ............................. 15
Run criteria—a closer look............................................................................... 17
Defining run requirements......................................................................... 17
Inherited job relationships.......................................................................... 18
Summary ......................................................................................................... 21

ESP-5.5-GS-01 iii
 2 Using ESP Workstation 23
Our sample scenario......................................................................................... 24
Using ESP Workstation ................................................................................... 25
Starting ESP Workstation .......................................................................... 25
Connecting to ESP Workload Manager ..................................................... 25
Using online help....................................................................................... 26
Using this tutorial—a quick note ............................................................... 26
Defining a custom calendar.............................................................................. 27
Creating your Application................................................................................ 31
Opening the Workload Editor ................................................................... 31
Setting default values.................................................................................. 31
Creating a workflow diagram ..................................................................... 33
Setting job details....................................................................................... 36
Saving your Application locally .................................................................. 39
Uploading your Application....................................................................... 40
Running your Application................................................................................ 41
Creating an Event ...................................................................................... 41
Simulating your Event ............................................................................... 45
Testing schedule criteria............................................................................. 48
Triggering your Event ................................................................................ 50
Monitoring your jobs ....................................................................................... 51
Graphical view ........................................................................................... 51
Custom views............................................................................................. 52
3 Using ESP Workload Manager’s ISPF Interface 59
Our sample scenario......................................................................................... 60
Using menus and panels................................................................................... 61
Quick navigation........................................................................................ 61
Accessing help ............................................................................................ 61
Accessing the Main Menu ................................................................................ 61
Defining a custom calendar.............................................................................. 62
Creating your Application................................................................................ 64
Running your Application................................................................................ 66
Creating an Event ...................................................................................... 66
Copying an existing Event.......................................................................... 68
Simulating your Event ............................................................................... 68
Testing schedule criteria............................................................................. 71
Triggering your Event ................................................................................ 72
Monitoring your jobs ....................................................................................... 73
Consolidated Status Facility ....................................................................... 73
Application Monitor .................................................................................. 75
A Service Level Management 79
Anticipated end times and due-out times ......................................................... 80
Critical path analysis ........................................................................................ 81

iv ESP-5.5-GS-01
 Contents

Index 83

ESP-5.5-GS-01 v
vi ESP-5.5-GS-01
 ESP Workload Manager Basics

This chapter introduces the basic ESP Workload Manager concepts you’ll need to
define, schedule, and manage your workload.
To gain hands-on practice using the ESP Workstation interface, complete the tutorial
in the next chapter. To learn more about the ISPF interface, see Chapter 3, “Using
ESP Workload Manager’s ISPF Interface.”
For an introduction to ESP Workload Manager’s powerful service level management
features, see Appendix A, “Service Level Management.”

ESP-5.5-GS-01 1
 Section–An ESP Workload Manager enterprise

An ESP Workload Manager enterprise

ESP Workload Manager

ESP Workload Manager is the core of the ESP Workload Manager enterprise. ESP
Workload Manager acts as the central point of control for your workload—handling
and directing all incoming messages from ESP Workstation and ESP Agents. Through
ESP Agents, ESP Workload Manager manages distributed workload. ESP Workload
Manager is aware of the entire environment, sends commands to ESP Agents, receives
messages from them, and makes decisions based on information you define.

ESP Agents
ESP Agents—programs that reside on distributed servers—are key components of an
ESP Workload Manager enterprise. They enable you to automate and manage
workload running on operating systems such as Windows, Linux, and UNIX as well
as ERPs such as SAP, PeopleSoft, and Oracle E-Business Suite. ESP Agents are aware
of their local environments. They respond to commands sent from, send messages to,
and take direction from ESP Workload Manager.

ESP Workstation
ESP Workstation is the graphical interface that you use to define, monitor, and
control your workload. ESP Workstation runs on Microsoft Windows and
communicates with ESP Workload Manager.
Note: Although an ISPF interface is also provided with ESP Workload Manager, we
primarily discuss ESP Workstation in the first two chapters of this book. Chapter 3
provides a brief introduction to and tutorial for the ISPF interface.

2 ESP-5.5-GS-01
 Chapter 1–ESP Workload Manager Basics

A brief introduction to ESP Workload Manager

ESP Workload Manager schedules workload differently than other products. It is
helpful to think of ESP Workload Manager as a business application scheduler rather
than a job scheduler. You can group jobs that are part of a particular business process,
regardless of the days and times they run or what platforms they run on. This ability
to group related workload from, for example, daily, weekly, and monthly flows into
one business flow simplifies maintenance.
You use ESP Applications to group jobs into workflows. Inside an Application, each
job has a run frequency. But simply defining an Application does not make it run; you
use an ESP Event to run your Application. You schedule an Event to run, perhaps at a
particular date and time or in response to something that happens in the system, like
the arrival of a file.
You use free-format, everyday English to schedule both your jobs and your Events.
You can use uppercase and lowercase characters, abbreviations, and different date and
time formats. You can also add custom scheduling terms and create your own
calendars.
After you’ve grouped your jobs into an Application and created an Event that runs
your Application, you can use the simulation feature to test it. This unique testing
method is a strength of ESP Workload Manager that allows you to eliminate
production-scheduling errors.
When your Application is error-free, you’re ready to run it. ESP Workstation’s
Workload Director provides a flexible mechanism for monitoring and controlling
your workflow while it runs.
To recap, you’ll follow several steps to get your workload running:
1. Create a custom calendar and define your own organization-specific scheduling
terms.
2. Group jobs into an Application.
3. Create an Event to run your Application.
4. Test your Application by simulating it.
5. Run your Application.
6. Monitor and control your Application.
In the following sections we’ll look more closely at each of these steps. Let’s get started!

ESP-5.5-GS-01 3
 Section–Using ESP Workload Manager calendars

Using ESP Workload Manager calendars

ESP Workload Manager’s default calendar (named SYSTEM) defines the first day of
the week, workdays, and global holidays. You can create custom calendars that define
scheduling terms unique to your needs. Think of a custom calendar as a dictionary
that defines scheduling terms that mean something to you in the context of your
organization.
Other products require you use multiple calendars and cumbersome scheduling
terminology. With ESP Workload Manager's calendar feature, you can use one single
calendar to define your own terms, specifying your organization’s important days
and periods.

Your administrator configures the SYSTEM calendar during installation and sets up
authorization for users to create other calendars. If you have permission, you can
create one or more calendars to define your unique scheduling terms.
You might create a calendar that defines special processing periods, holidays, and
other special days. For example, suppose you want jobs to run at specific times within
pay periods. You might define a new term called PAY_PERIOD in your calendar.
Then, to run your jobs you can use an expression such as last workday of
pay_period.
The following example displays the definition for a calendar named PAYCAL.
Workdays are Monday through Friday and the week starts on Sunday.

4 ESP-5.5-GS-01
 Chapter 1–ESP Workload Manager Basics

The Special Days tab displays the definition of the PAY_PERIOD special period. In
the following example, the boundaries of a pay period have been defined as the first
and the 16th day of each month.

How ESP Workload Manager uses calendars

By default, ESP Workload Manager uses the SYSTEM calendar. Other calendars
you’ve defined are available for you to include when you define Events. When you
specify that your Event should use the PAYCAL calender, ESP Workload Manager
refers to the scheduling terms on the PAYCAL and SYSTEM calendars. It merges the
definitions of holidays, special days, and special periods in both calendars. If there are
special days or periods with the same name in both calendars, it uses the definitions
from PAYCAL.

Defining what will run

ESP Applications and Procedures

An Application groups related jobs and their processing requirements. When you
define an Application, you give it a name that reflects the business application it
handles, for example payroll or billing. An Application is a type of Procedure. A
Procedure is a data set containing ESP statements.

ESP-5.5-GS-01 5
 Section–Defining what will run

Note: Although an Application is the type of Procedure you will use most often, there
are Procedures that are not Applications. For example, you might use a Procedure to
store variables or issue commands.

Unlike other job-scheduling products, ESP Workload Manager doesn’t require a

database to hold its processing requirements. Because ESP Workload Manager
doesn’t need to scan a database to identify a job’s successors, customers often
experience less delay between one job completing and the submission of its successor
jobs. If you are a large-volume shop, you could see your batch cycle decrease.

A sample scenario
Consider a scenario where you want to schedule four jobs named A, B, C, and D that
all do payroll processing.
The jobs run on different systems: A and B run on the mainframe; C runs on Linux;
and D runs on Windows.
The jobs have dependencies: A must complete before B and C can start; B and C must
complete before D can start. All of the jobs run daily.
Here’s a flowchart showing the relationships between the four jobs in the payroll
Application.

All of the jobs in this simple scenario run daily, but ESP Workload Manager allows
you to define Applications that include jobs that run on different days and at different
times. We’ll look at some examples of more complex schedules a little later on.

6 ESP-5.5-GS-01
 Chapter 1–ESP Workload Manager Basics

Creating an Application in Workload Editor

You use ESP Workstation’s Workload Editor to define your Application. As you
graphically build and edit schedules in Workload Editor, it automatically generates
ESP statements and displays them in the right pane. Here’s how the sample payroll
Application appears in Workload Editor.

Note: You can type statements directly into a data set using the ISPF editor if you
prefer. For more information, see Chapter 3, “Using ESP Workload Manager’s ISPF
Interface.”
When you define an Application, you give it a name. It’s a good idea to choose a name
that represents the purpose of the jobs in the Application, such as PAYROLL. You also
have to specify the JCL library that contains the JCL for your mainframe jobs.
You build your Application by placing graphical icons in the left pane to represent
your jobs. You draw arrows between jobs to define job dependencies. You also specify
details, such as a job’s name and run frequency. You specify other details for your
distributed jobs, such as the ESP Agent that runs the job and the location of the
program or script. For example, LNX_AGNT handles the Linux job as defined in the
preceding diagram. The script that will run is /export/home/khanna/
deduct.sh.

ESP-5.5-GS-01 7
 Section–Defining what will run

ESP Workload Manager can manage workload running on many different operating
systems—it doesn’t care whether the jobs run on the mainframe, a Windows server, a
UNIX server, a PeopleSoft system or any combination of systems. The icons at the
bottom of the Workload Editor screen represent the wide variety of job types that
ESP Workload Manager can manage. When ESP Workload Manager finds a job that
needs to run on a system other than the mainframe, it takes the information in the
job’s details, such as the program name or script name, and creates a message that it
sends to the specified ESP Agent over TCP/IP. ESP Agent interprets the message and
tells the operating system or ERP to execute the job. ESP Agent informs ESP
Workload Manager about the status of the work. In this way, ESP Workload
Manager manages work running on different systems, regardless of the type or
number of systems.

ESP statements
Workload Editor generates ESP statements and displays them in the right pane. These
statements are stored in a data set as an ESP Procedure and constitute the Application
definition.
Let’s examine some of these statements from our payroll Application.

The first two statements, APPL and JCLLIB, appear in every Application. The APPL
statement names the Application. It is generated using the name you specify when you
create your Application in Workload Editor. In this example, the following statement
identifies the PAYROLL Application:
APPL PAYROLL
The next statement, the JCLLIB statement, identifies the data set that contains the
JCL for the mainframe jobs in the Application, for example:
JCLLIB ’CYBKH01.TEST.JCL’
Following these statements are job definitions that Workload Editor generates when
you place job icons in the left pane. The JOB statement begins each job definition
and the ENDJOB statement ends it. Statements outside a JOB and ENDJOB pair
generally apply to more than one of the jobs in the Application—often the entire

8 ESP-5.5-GS-01
 Chapter 1–ESP Workload Manager Basics

Application. Statements between the JOB and ENDJOB pair apply to that specific
job only. The JOB statement identifies the job type. For example, the NT_JOB
statement tells ESP Workload Manager that D is a Windows job.

By default, the JOB statement indicates that the job is a mainframe job. When ESP
Workload Manager encounters the JOB statement, it searches the JCL library
specified in the JCLLIB statement for a member matching the name in the JOB
statement.
The LINUX_JOB statement indicates that the job runs on a Linux server. To run, the
Linux job definition requires two additional statements: AGENT and
SCRIPTNAME. Workload Editor generates these statements when you specify the
job’s details. The AGENT statement identifies the ESP Agent that runs the job on the
distributed server, in this case, LNX_AGNT. The SCRIPTNAME statement
identifies the name and location of the script to run. The statements necessary to run
the Windows job are equivalent.
Statement What it identifies
NT_JOB a Windows job
AGENT the ESP Agent that runs the job
CMDNAME the name and location of the Windows command to run

When you specify a job’s run frequency, a RUN statement is generated. In the
PAYROLL Application, all of our jobs contain the following RUN statement:
RUN DAILY
When you create dependencies in Workload Editor by drawing arrows between jobs,
RELEASE statements are generated. A RELEASE statement defines a job’s successors.

ESP-5.5-GS-01 9
 Section–Scheduling your jobs

For example, RELEASE(B, C) inside A’s definition specifies that B and C depend on
A’s successful completion.

Scheduling your jobs

Now that you’ve defined your Application, you need to schedule it. To generate active
workload on your system, you use an ESP Event to tell ESP Workload Manager when
it should run your Application.

ESP Events
An Event tells ESP Workload Manager when to read an Application and when it
should begin submitting jobs. In other words, Events tell ESP Workload Manager
what to do and when to do it. You create Events using the Event wizard in ESP
Workstation’s Event Manager.
When you create an Event, you begin by naming it. The name has two parts: a group
prefix and a descriptive name. The group prefix, CYB1 in the following example,
enables the segregation of workload by controlling which users are permitted to run
the Event. Your administrator sets up groups and their access permissions. The
descriptive name, PAYROLL, is the name you give to the Event. To easily identify
your Events, we recommend you use the name of the Application the Event runs as
your Event name.

10 ESP-5.5-GS-01
 Chapter 1–ESP Workload Manager Basics

When you create an Event, you must also specify which Application you want it to
run. In the following example, the PAYROLL member of the CYB1.KH.PROCS data
set stores the payroll Application.

You can specify scheduling criteria to automatically schedule your Event. In our
example, ESP Workload Manager will schedule the PAYROLL Application to run at
4pm daily. You can also use other methods for triggering Events, such as manual
triggers, data set triggers, job monitors, and ESP Workload Manager Alerts. To learn
more about those trigger methods, see the ESP Workload Manager User’s Guide.

ESP-5.5-GS-01 11
 Section–Simulating what will run

Most scheduling products require that you load a schedule once a day, bringing all
the workload for that day into the system at one time. Although that method may
suit your needs, you may also find it easier to schedule different workload at different
times. Using Events, you can stagger your workload into the system closer to its
actual run time. ESP Workload Manager enables you to choose the method you
prefer—you schedule whatever you want, anytime you want.

Now you have the workload you want to run and a method for scheduling it. Before
you move your Application into your production environment, use ESP Workload
Manager’s simulation feature to test it.

Simulating what will run

Simulation allows you to check the syntax of the statements in your Application and
preview what will run under different conditions, such as different times and different
dates. ESP Workload Manager’s simulation feature shows you which jobs will run,
what the dependencies are between jobs, and how many predecessors each job has.
Simulation also allows you to view your JCL, show syntax errors, identify missing
JCL, and verify that ESP Workload Manager is aware of any Agents you’re using. You
can simulate an Event to run in the past, present or future.

12 ESP-5.5-GS-01
 Chapter 1–ESP Workload Manager Basics

You use ESP Workstation’s Event Manager to run a simulation. You can specify a date
and time or allow Event Manager to use the next scheduled date and time. For
example, if you were to simulate the PAYROLL Application, you’d see these results in
Event Manager.

The simulation output shows you the job names and the number of jobs ESP
Workload Manager has selected for submission. For each job, it also shows you the job
type, job name, hold count (HC), and the successor job names (RELEASES).
A job’s hold count tells you the number of predecessor jobs on which it depends. For
example, B depends on one predecessor, A, so it has a hold count of one. By default,
ESP Workload Manager doesn’t submit a job with a hold count greater than zero.
When A completes, ESP Workload Manager decrements B’s hold count by one,
reducing it to zero so B can run. Because jobs that show a hold count of zero could
run immediately (unless they have a specific submission time), you’ll want to pay close
attention to those jobs during simulation.
The RELEASES column lists the successor jobs. B has one successor job that is
dependent on its completion, D.
When you are satisfied that your Application is correct, you are ready to put it into
production.

ESP-5.5-GS-01 13
 Section–Running your jobs

Running your jobs

Jobs run in response to the triggering of an Event that runs your Application. Usually,
you will want to schedule your Events so that ESP Workload Manager triggers them
automatically. Other times, you might need to trigger Events manually or use other
ESP Workload Manager triggering mechanisms. Whenever ESP Workload Manager
triggers an Event that runs an Application, it generates a unique occurrence of that
Application called a generation. During this generation phase, ESP Workload
Manager selects the jobs that will run. To keep track of Application generations, ESP
Workload Manager assigns each generation a unique number. The number following
the Application name indicates the generation number. Here’s how the first three
generations of the PAYROLL Application are identified.
PAYROLL.1
PAYROLL.2
PAYROLL.3
When an Application is generated, you can monitor the jobs using ESP Workstation’s
Workload Director.

14 ESP-5.5-GS-01
 Chapter 1–ESP Workload Manager Basics

Monitoring your jobs

Workload Director—graphical views and custom views

Using Workload Director, you can view real-time, graphical representations of your
Applications. The following example shows generation 36 of a slightly more complex
version of our PAYROLL Application.

In the left pane, you see a tree view of the Applications you told ESP Workload
Manager you wanted to monitor. In the right pane, you see the icons representing the
six jobs in the selected Application. The job state appears below each icon. The color
surrounding the job icon represents the job’s state. For example, blue indicates a
complete state and red indicates a troubled state. You can customize these colors to
suit your needs. The states in the preceding Application indicate the following:
• COMPLETE (blue) indicates that the job has finished processing successfully.
• EXEC (green) indicates that the job is executing.
• PREDWAIT (grey) indicates that the job is waiting for one or more predecessors
to complete.

ESP-5.5-GS-01 15
 Section–Monitoring your jobs

With Workload Director you can also view this information in table-format using
custom views. You can use pre-packaged custom views or create your own custom
views that display the information you want in the format you want. You can tile
multiple custom views so you can monitor various execution criteria simultaneously.

You can control jobs in either a graphical view or custom view by right-clicking a job
and choosing a command from the menu that appears. You can view more details
about a job by double-clicking the job in either view. Here are the details of a
Windows job.

16 ESP-5.5-GS-01
 Chapter 1–ESP Workload Manager Basics

Run criteria—a closer look

Defining run requirements

As discussed on page 7, you define a run frequency for each of your jobs. In our first
PAYROLL Application, we defined four jobs that run daily. With ESP Workload
Manager, even though the jobs may have different run criteria, you can define them
within one Application. For example, you’ll group the jobs corresponding to a
business process into an Application even though the jobs run on different days and at
different times.
Suppose you want to change your PAYROLL Application so that job D only runs on
Friday. You also want to add two new jobs to the Application: E and F. Both E and F
run on the mainframe but on different days. E runs on the last workday of the month
and F runs daily. D must complete before E can start, and E must complete before F
can start.
Here’s a flowchart to show the relationships between the jobs in this scenario.

ESP-5.5-GS-01 17
 Section–Run criteria—a closer look

To change D’s run requirement, you edit its job details. To schedule the two new jobs,
you add two new job icons to your workflow diagram. Since E depends on D’s
completion and F depends on E’s, you also add two new arrows to create these
dependencies. Finally, you specify names and run criteria for E and F.
We now have jobs in our Application with three different run frequencies: daily,
Friday, and last workday of the month. Depending on which day of the week it is,
ESP Workload Manager will submit different jobs. When choosing which jobs are to
be run, ESP Workload Manager considers the inherited job relationships that exist.

Inherited job relationships

When ESP Workload Manager scans an Application and selects which jobs should
run, it checks for inherited job relationships. By default, when a job isn’t selected, the
dependency chain flows through that job.
To illustrate the effect of this inheritance feature, let’s look at jobs B, C, D, and E in
the PAYROLL Application and consider what happens when the last workday of the
month is any day other than Friday.

If the last workday of the month is a Tuesday, for example, ESP Workload Manager
selects B, C, and E. It doesn’t select D since D only runs on Friday. Because of
inherited job relationships, E runs after both B and C complete; the dependency
chain passes through the unselected job D. Without this inheritance feature, E would
run prematurely because its direct predecessor, D, is not present.
If the last workday of the month is Friday, ESP Workload Manager selects all four jobs
and the specified set of dependencies must be met for each job to run.

18 ESP-5.5-GS-01
 Chapter 1–ESP Workload Manager Basics

Other scheduling products require multiple job definitions and calendars for each
different run requirement. With ESP Workload Manager, you can handle various
scenarios in a single Application using schedule criteria and the inherited job
relationships feature. ESP Applications further simplify your work definitions
reducing the number of definitions you must maintain.

To see which jobs will run and which relationships are inherited, you can use the
simulation feature. Earlier in this chapter, we simulated the PAYROLL Event for 5pm
today and saw that ESP Workload Manager would submit all four jobs because each
job runs daily. Now our jobs have different run requirements. If we simulate for the
last workday of the month, our simulation will have two different results depending
on which day of the week the last workday of the month falls on.
If the last workday of the month is not a Friday, five jobs will appear in the
simulation. ESP Workload Manager automatically inherits job relationships, as shown
in the following example. E will wait for both B and C to complete before it runs.

Last workday of month is not a Friday

ESP-5.5-GS-01 19
 Section–Run criteria—a closer look

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

Last workday of month is a Friday

20 ESP-5.5-GS-01
 Chapter 1–ESP Workload Manager Basics

Summary
This chapter introduced the following key points about ESP Workload Manager:
• You can define your own schedule terms, such as special processing periods,
holidays, and other special days, using an ESP Workload Manager calendar.
• You define what you want to run by grouping jobs into an Application, which is a
type of Procedure—a data set that consists of ESP statements.
• Applications can group all jobs from a business process, regardless of when or
where they run.
• To schedule your jobs, you use an ESP Event, which tells ESP Workload Manager
what to do and when to do it.
• You can use free-format, everyday English schedule criteria, for example, “5pm
daily” or “last Tue of month”.
• You preview what will run under different conditions and check for errors using
ESP Workload Manager’s simulation feature.
• To run your jobs, you can schedule an Event, trigger an Event manually or use
other Event-triggering mechanisms.
• You can monitor and control your jobs using Workload Director.

ESP-5.5-GS-01 21
 Section–Summary

22 ESP-5.5-GS-01
 Using ESP Workstation

This chapter provides a hands-on tutorial to get you started using ESP Workstation.
Follow the steps provided to learn how to complete the following tasks:
1. Create a custom calendar.
2. Create an Application.
3. Create an Event to run your Application.
4. Simulate your Event.
5. Trigger your Event.
6. View your Application running.

ESP-5.5-GS-01 23
 Section–Our sample scenario

Our sample scenario

In this section you will create an Application containing six jobs. Five of the jobs run
on z/OS and one of the jobs runs on Windows. The Application will be named
PAYROLL. The following flowchart shows the relationships between the jobs.

Note: Ifyou don’t have access to ESP Agent on a Windows server, substitute another
z/OS job for B.

24 ESP-5.5-GS-01
 Chapter 2–Using ESP Workstation

Using ESP Workstation

Starting ESP Workstation

When you launch ESP Workstation from the Windows Start menu or by
double-clicking the ESP Workstation icon on your desktop, the ESP Workstation
toolkit appears.

The icons on the toolkit provide shortcuts to ESP Workstation’s components. Most of
the components are available only when you are connected to ESP Workload
Manager. The exception to this is Workload Editor; you can create and edit
Applications and workflow diagrams offline in Workload Editor and upload them
later.

Connecting to ESP Workload Manager

The first time you connect to ESP Workload Manager, you’ll have to provide the IP
address (or DNS name) and port number for your installation, as well as your user ID.
If you don’t have this information, speak to your administrator. You’ll need your
password every time you connect.

Connecting to ESP Workload Manager for the first time

1. On the toolkit menu bar, click Connection Manager > Connection Manager.
The Connection Manager dialog appears.
2. Click Connection > Add.
The Add a new connection dialog appears.
3. In the Address field, type the IP address or DNS name for your ESP Workload
Manager installation.
4. In the Port field, type the port number.
5. In the User Name field, type your TSO user ID.
6. Click OK.
A server connection appears.
7. To connect, right-click the server connection and click Connect.
The Connect dialog appears.
8. In the Password field, enter your password and click Connect.
A dialog appears indicating that you are connected.

ESP-5.5-GS-01 25
 Section–Using ESP Workstation

Connecting subsequently
1. On the toolkit menu bar, click Connection Manager > Connection Manager.
The Connection Manager dialog appears showing a list of servers.
2. Right-click the icon for the server you want to connect to and click Connect.
The Connect dialog appears with the Address, Port, and User Name fields populated.
3. Type your password in the Password field and click Connect.
A dialog appears indicating that you are connected.

Using online help

There are three types of online help available in ESP Workstation: field-specific help,
component-specific help, and general help. Some help screens provide links to related
topics; general help and component-specific help enable you to search the help topics.
We’ll look at an example of field-specific help when we create a custom calendar.

Accessing field-specific help

• Move the cursor to a field and press F1.

Accessing component-specific help

• On any ESP Workstation component’s Help menu, click ESP Workstation Help.

Accessing general help

• On the toolkit menu bar, click Help > ESP Workstation Help.

Using this tutorial—a quick note

ESP Workstation often provides several ways to accomplish the same thing. For
example, you can use either of the following methods to open the Calendar Manager:
• On the toolkit, click the Calendar button.
• On the toolkit menu bar, click ESP Tools > Calendar Manager.
There are also keyboard shortcuts for many tasks. Throughout this tutorial, we
present a single simple method for completing each task, usually clicking a button or
icon. But be sure to explore the component menus to find the method that works best
for you.

26 ESP-5.5-GS-01
 Chapter 2–Using ESP Workstation

Defining a custom calendar

For this tutorial, you’ll create a new custom calendar named PAYCAL, define the
special period PAY_PERIOD, and then use PAY_PERIOD to schedule a job. To
complete the entire tutorial, ask your administrator to authorize you to create and edit
this calendar. If creating calendars won’t be part of your job, you might want to ask
your administrator to do it for you. If you don’t want to use custom calendars at all,
skip to the next section: Creating your Application; look for tips throughout the
tutorial that tell you what to substitute for PAY_PERIOD.

Defining a new calendar

1. Connect to ESP Workload Manager.
2. On the toolkit, click the Calendar button.
The Calendar Manager dialog appears and loads available calendars.
3. On the Calendar Manager toolbar, click the Create icon.

The Calendar tab appears.

4. In the Name field, type PAYCAL.
5. In the Owner field, type your mainframe user ID.
6. In the Select Workdays for Calendar area, select Mon, Tue, Wed, Thu, and Fri.

ESP-5.5-GS-01 27
 Section–Defining a custom calendar

7. From the First day of week drop-down menu, select Sunday.

8. Click Upload.
A dialog appears telling you that the calendar is being uploaded.
Tip: You can select a field and press F1 to get more information about that field. In
the following example, help about the Owner field is displayed.

28 ESP-5.5-GS-01
 Chapter 2–Using ESP Workstation

Defining a special period

A special period is a period between two special days of the same name. In this
example you’ll define two special days named PAY_PERIOD: the special days occur
on the first of the month and the 16th of the month. These definitions create pay
periods that run from the first of the month until the 15th and the 16th until the last
day of the month. You’ll define this period to repeat until 2016.
1. Click the Special Days tab.
The Special Days pane appears.
2. In the Name field, type PAY_PERIOD.
Note: The name of a special day can’t contain spaces.
3. Select Repeat.
4. In the text box, type first day of the month until 2016.

5. Click Upload.
The date of the first day of each month until the current month in 2016 appears
in the List of Special Days.
6. Repeat steps 2 and 3.

ESP-5.5-GS-01 29
 Section–Defining a custom calendar

7. Type 16th day of the month until 2016 in the text box and click Upload.
The 16th of each month until the current month in 2016 appears in the List of
Special Days.

You have now created and uploaded the PAY_PERIOD special period, and it’s
available for you to use in your schedule criteria.

30 ESP-5.5-GS-01
 Chapter 2–Using ESP Workstation

Creating your Application

Opening the Workload Editor

• On the toolkit, click the Editor button.
The Workload Editor appears. The left pane is the workspace where you create
workflow diagrams—graphical representations of your Applications. The right
pane is where the generated statements that form your Applications are displayed.

Setting default values

Before creating an Application, you can specify some common defaults at the
Application level, referred to as workload definition defaults. These defaults apply to
all of the jobs in your Application.
For this example, you’ll name your Application and identify the JCL library that
contains the z/OS jobs your Application uses.

Opening the Workload Definition Defaults dialog

• On the Workload Editor menu bar, click Options > Workload Definition Defaults.
The Workload Definition Defaults dialog appears.

ESP-5.5-GS-01 31
 Section–Creating your Application

Naming your Application

• In the Application name field, type PAYROLL.
An Application name can be up to eight alphanumeric or national characters. The
first character must be alphabetic.

Specifying the JCL library for the entire Application

Five of the jobs in this example are z/OS jobs. You need to identify the JCL library
that contains the JCL for these jobs. You can specify the default JCL library you want
to use throughout an Application. If all or most of the jobs are in the default library,
you won’t have to specify a library in each job’s details. If a job isn’t in the default
library, you’ll have to specify its library at the job level.
1. On the Workload Definition Defaults dialog, click the Libraries tab.
2. In the Library name field, enter the name of your JCL library.
Note: Quotation marks are not required.

32 ESP-5.5-GS-01
 Chapter 2–Using ESP Workstation

3. Click OK.

Creating a workflow diagram

Workload Editor includes a menu of icons across the bottom of the workspace, one
for each type of job you can define in an Application. This menu is the job palette.
You use it to create a graphical representation of your workload—a workflow diagram.

Placing icons in the workspace

1. Ensure you’re in dialog editing mode by checking that your job palette is active.
If your job palette is grayed out, from the Actions menu, click Switch Editing Mode.
2. Click the z/OS icon on the job palette.
Your cursor changes to a box.
3. Move the box onto the workspace and click.
The box changes to the z/OS icon and drops into position.
Tip: When you want to use the same icon multiple times, you don’t need to select
the icon on the job palette repeatedly. Just click the icon once then click in the
workspace as many times as you want. Workload Editor uses the same icon until
you choose a different one.
4. Place four more z/OS icons on the workspace in the configuration shown in the
following example.
5. Click the NT icon on the job palette.

ESP-5.5-GS-01 33
 Section–Creating your Application

6. Move the box onto the workspace to the position shown in the following example
and click.
The box changes to the NT icon and drops into position.
Don’t worry about making your diagram neat; we’ll clean it up later.

Notice that ESP statements appear in the right pane as you place your icons on
the workspace. These are the statements that ESP Workload Manager needs to
run your Application.

Creating job dependencies

When your job icons are on the workspace, you can graphically illustrate the
dependencies between them.
1. On the Workload Editor toolbar, click the Create Dependencies icon.

Your cursor becomes a wand.

2. Drag your cursor between the first job and one of its successors.
An arrow from the first job to the second job appears, indicating the dependency.

34 ESP-5.5-GS-01
 Chapter 2–Using ESP Workstation

3. Drag your cursor to draw arrows from the jobs to their successors until you’ve
drawn all of the dependencies.
The last dependency you create is in red.

Notice that RELEASE statements have been added to the text in the right pane.

ESP-5.5-GS-01 35
 Section–Creating your Application

Organizing the layout of your workflow diagram

Now that you have created your workflow diagram, you can clean up your layout.
• On the toolbar, click the Layout icon.

Your workflow diagram is displayed in an organized fashion.

Setting job details

Changing a job name
By default, the jobs on the workspace are labeled with the job type and a sequential
number. You can specify a more meaningful name in the job details.
1. Right-click the icon for the first job in your workflow diagram and click Job
Details.

The Job Details dialog appears.

36 ESP-5.5-GS-01
 Chapter 2–Using ESP Workstation

2. On the General tab, in the Name field, enter A as the job’s name.

This example uses A, B, C, D, E, and F for the six jobs.

Note: The JCL library you specified when you created this Application must contain
JCL for five jobs: A, C, D, E, and F. You can use your own job names if you prefer.

Specifying when a job should run

You must specify a run frequency for each of your jobs. You can define a single
condition or you can create a list of conditions under which a job should run or not
run. In this example, you’ll use a single condition for each job.
1. On the Job Details dialog, click the Run Frequency tab.
2. In the Specify Run Frequency text field, type daily.

ESP-5.5-GS-01 37
 Section–Creating your Application

3. Click Add.
The run frequency condition appears in the List of Run Frequency Conditions box.

4. Click OK.

Specifying details for your Windows job

1. Open the Job Details dialog for the NT job. Change the job name to B and set a
run frequency of daily.
2. Click the Agent Specifications tab.
3. In the Name field of the Specify Agent section, type the name of the ESP Agent on
your Windows machine.
If you don’t know the name of the ESP Agent on your Windows machine, ask
your administrator.

38 ESP-5.5-GS-01
 Chapter 2–Using ESP Workstation

4. In the Name field of the Specify Command File to Run section, type the name of a
command file or program on your Windows machine.
You can use any command file or program on the Windows machine.

Specifying the details for the rest of your jobs

• Right-click the third icon and so on until you’ve specified a name and a run
frequency for each of the remaining z/OS jobs. Use the following run frequencies:
C – daily
D – Friday
E – last workday of pay_period
F – daily
Tip: If you aren’t using custom calendars, make job E’s run frequency last
workday of month instead.

Saving your Application locally

When you’ve finished specifying your job details, save your Application. You don’t
have to be connected to ESP Workload Manager to define and save Applications
locally.
1. On the Workload Editor menu bar, click File > Save As.
The Save As dialog appears.
2. In the File name field, enter PAYROLL as your Application name and click Save.

ESP-5.5-GS-01 39
 Section–Creating your Application

Uploading your Application

After you save your Application locally, upload it to the mainframe. You have to be
connected to ESP Workload Manager to upload your Application. For more
information on how to connect to ESP Workload Manager, see “Connecting to ESP
Workload Manager” on page 25.
1. On the Workload Editor menu bar, click File > Upload Workload Definition.
The Upload to Procedure Library dialog appears.
Note: As discussed in Chapter 1, an Application is a type of Procedure.

2. In the Name field, enter the name of the data set where you want to store your
Applications.
Note: This data set must have already been allocated on the mainframe.
3. In the Member field, enter PAYROLL as the name of your Application.
Your Application will be stored in the specified data set as member PAYROLL.
4. If you don’t want to replace an existing member that has the same name, check the
Do not override if member exists box.

5. In the ESP Workload Manager field, choose the mainframe you want to upload your
Application to.
6. Click OK.
A confirmation message appears.
7. Click OK.
Your Application is uploaded.

40 ESP-5.5-GS-01
 Chapter 2–Using ESP Workstation

Running your Application

After you create an Application, you have to tell ESP Workload Manager when to run
it and where its definition is stored. To do this, you create an Event.

Creating an Event
Opening and loading the Event Manager
1. On the toolkit, click the Event button.
The Event Manager dialog appears.
2. Click the server name.

3. In the Prefix field, enter your mainframe user or group ID.

4. Click List of Events.
The Event Manager loads the available Events.

Creating an Event
1. On the Event Manager toolbar, click New.
The Event Properties tab appears.
2. Name the Event. An Event name has two parts: a prefix and a descriptive name.
The prefix can contain up to eight alphanumeric characters, including national
characters. The prefix corresponds to a mainframe user or group ID.
a. In the Prefix field, enter a prefix.
Event names can contain up to 16 characters, including national characters
and the underscore; the first character must be alphabetic. Event names must

ESP-5.5-GS-01 41
 Section–Running your Application

be unique. It’s a good idea to name your Event the same name as the
Application it runs.
b. In the Name field, enter a name for your Event. For this example, enter
PAYROLL.

3. Click Next.
The Additional Options tab appears.

Specifying an additional calendar to use

Tip: If you aren’t using a custom calendar, skip to step 2.
1. From the Calendar 1 drop-down menu, select PAYCAL.
2. Click Next.
The Run ESP Procedure(s) tab appears.

42 ESP-5.5-GS-01
 Chapter 2–Using ESP Workstation

Specifying the Application to run

1. In the Specify ESP Procedure to Run section, in the Data set name field, enter the name
of the data set you have allocated on the mainframe for storing your Applications.
This is the same data set you specified in the Upload to Procedure Library dialog when
you uploaded the PAYROLL Application from Workload Editor to the
mainframe.

2. In the Member name field, enter the name of the data set member. In this example,
the member has the same name as the Application: PAYROLL.
Note: Do not type quotation marks.
3. Click Add.
The data set name and member name appear in the List of Procedures to Run box.
4. Click Next until the Schedule Definition tab appears.

ESP-5.5-GS-01 43
 Section–Running your Application

Specifying when to run the Application

1. In the Specify Schedule Criteria text field, type 4pm daily.
2. Click Add.
The schedule criteria appears in the Resulting Schedule Criteria box.

Uploading your Event

1. Click Next until the Comments tab appears.
2. Click Finish.
The Event Properties tab appears.

44 ESP-5.5-GS-01
 Chapter 2–Using ESP Workstation

3. On the Event Properties tab, click Upload to upload the current Event definition to
ESP Workload Manager.
A message appears telling you when the Event named PAYROLL will execute.

4. Click OK.
In the left pane, the tree view now includes the PAYROLL Event.

Simulating your Event

In the Event Manager, use the simulation feature to see a graphical representation of a
generation of your Application. You can simulate the next occurrence of the Event, a
future occurrence or a past occurrence.
1. In the tree view, select the PAYROLL Event.
2. On the Event Manager toolbar, click the Simulate icon.

The Simulate Event dialog appears.

ESP-5.5-GS-01 45
 Section–Running your Application

For this example, you’ll simulate the following schedule criteria:

• Next occurrence of the Event
• Friday
• Last workday of the pay period

Next occurrence of the Event

To simulate the next occurrence of the Event, leave all of the fields of the Simulate Event
dialog blank. The default is the next scheduled occurrence (or NOW if the Event is
not scheduled).
1. Click OK.
A message appears asking you to wait while the Event is simulated, and then a
graphical representation of the Application is displayed.
Jobs A, B, C, and F are included. If it happens to be Friday, D is also included. If
it happens to be the last workday of the pay period, E is also included. If it is prior
to 4pm, you’ll see which jobs are selected today. Otherwise, you’ll see which jobs
will be selected tomorrow.
2. Click the ViewLog icon to display the simulation’s text output.
The log identifies the jobs that will run that day. It also displays ESP Agent
information and the hold count and successor jobs for each selected job. In the
following example, the next occurrence is neither Friday nor the last workday of
the pay period.

3. On the toolbar, click CloseGraph.

46 ESP-5.5-GS-01
 Chapter 2–Using ESP Workstation

Friday
1. Open the Simulate Event dialog again.
2. In the Schedule Criteria field, enter friday.
3. Click OK.
A message appears asking you to wait while the Event is simulated, and then a
graphical representation of the Application is displayed.
In addition to jobs A, B, C, and F, which are scheduled to run daily, D is included
in the graph because it is scheduled to run on Friday. If this Friday happens to be
the last workday of the pay period, E is also included.
4. Click the ViewLog icon to display the simulation’s text output.
In the following example, this Friday is not the last workday of the pay period.

5. On the toolbar, click CloseGraph.

Last workday of the pay period

1. Open the Simulate Event dialog again.
2. In the Schedule Criteria field, enter last workday of pay_period.
Tip: If you aren’t using a custom calendar, type last workday of month
instead.

ESP-5.5-GS-01 47
 Section–Running your Application

3. Click OK.
A message appears asking you to wait while the Event is simulated, and then a
graphical representation of the Application is displayed.
Job E is included in the graph because it is scheduled to run on the last workday of
the pay period. By default, when ESP Workload Manager selects jobs for
submission, it automatically checks whether any relationships among jobs should
be inherited. For example, if the last workday of the pay period is a Friday, E must
wait for D to complete before it can run. If the last workday of the pay period is
not a Friday, E waits for B and C to complete.
4. Click the ViewLog icon to display the simulation’s text output.
In the following example, the last workday of the pay period is a Friday.

5. On the toolbar, click CloseGraph.

Testing schedule criteria

You can use the Event Manager to test schedule criteria to see how ESP Workload
Manager interprets different scheduling terms. When you simulated your Events in
our example, it might have been useful to determine a date when the last workday of a
pay period is also a Friday. You can find such a date by testing schedule criteria.
1. On the Event Manager toolbar, click Test.
The Test Schedule Criteria dialog appears.
2. In the Schedule criteria text box, type last workday of pay_period.

48 ESP-5.5-GS-01
 Chapter 2–Using ESP Workstation

Tip: If you aren’t using a custom calendar, type last workday of month
instead.
3. In the Number of cycles box, type a number or use the arrows to choose a number,
such as 6.
4. From the Calendar 1 drop-down menu, choose PAYCAL.
Tip: If you aren’t using a custom calendar, skip to step 5.
5. Click Test.
The next six dates that fit the criteria appear in the Results box.

ESP-5.5-GS-01 49
 Section–Running your Application

Triggering your Event

Your Event is scheduled to run at 4pm each day. If you want to run the Event
immediately, you can trigger it manually.
1. Select the Event.
2. On the Event Manager toolbar, click the Trigger icon.

The Trigger the Event dialog appears.

3. Leave the Schedule criteria field blank because you want to trigger the Event
immediately.
4. Leave Add new scheduled Event selected.
Choosing Add new scheduled Event triggers your Event now, as well as at its next
scheduled time. Choosing Replace next scheduled Event triggers your Event now
instead of at its next scheduled time.
5. Click OK.
A message appears confirming the Event has been triggered. The Event submits
the Application immediately as well as at 4pm.

50 ESP-5.5-GS-01
 Chapter 2–Using ESP Workstation

Monitoring your jobs

ESP Workstation’s Workload Director component is used to monitor and control
your Applications or jobs as they run. You can view workload that has recently
completed, is currently running or is scheduled to run. Workload Director provides a
graphical view and text-based custom views of the workload.

Opening the Workload Director

• On the toolkit, click the Director button.
The Workload Director appears. Tabs that control which view is active are located
at the bottom left of the Workload Director window.

Graphical view
The graphical view organizes and displays Applications and their generations. Each
Application is represented by a folder labelled with the Application name and the
number of generations of the Application.

Viewing generations of your Application

1. Click the Graphical View tab.
2. In the tree view, right-click the server that you uploaded your Application to.
Note: This may be the only server you see.
3. On the shortcut menu, click Subscribe No Filter.
A plus (+) sign appears next to the server name.
4. Click the plus (+) sign.
A folder appears for each Application.

ESP-5.5-GS-01 51
 Section–Monitoring your jobs

5. Double-click the PAYROLL folder.

The PAYROLL folder expands and a folder for each generation of the Application
is displayed.
6. Double-click the generation of the Application you want to view.
In the right pane of the Workload Director, a graphical view of your Application
generation appears.

The colored border around an icon, as well as the label below it, indicate a job’s
processing state. As a job passes through different states, these indicators change.
In addition to viewing your Application, you can take actions against a job.

Taking an action against a job

1. Right-click one of the jobs in the graphical view.
2. On the shortcut menu, click the required action.
You can also take an action against an Application by right-clicking the
Application folder and choosing an action from the shortcut list.

Custom views
A custom view is a table you use to monitor and control your workload. Workload
Director comes with several default custom views, but you can create your own. For
example, you might create a custom view to display all jobs in a particular Application

52 ESP-5.5-GS-01
 Chapter 2–Using ESP Workstation

that are waiting. You can create (and save) custom views to display only the
information you want, in the format you want. You can also control jobs from a
custom view the same way you control jobs using the graphical view.

Default custom views

The Custom View tab of the Workload Director provides a list of default custom views.
Double-click a custom view to display it. The following example shows the Failures
and Waiting custom views tiled horizontally.

ESP-5.5-GS-01 53
 Section–Monitoring your jobs

User-defined custom views

Creating a custom view

1. On the Workload Director menu bar, click Custom View > New.
The Presentation tab of the Custom View Configuration dialog appears.

2. Click the following fields while holding down the Shift key.
• Application Name
• Generation Number
• Job ID
• Job Name
• State
• Status
3. Click the right arrow (>).
You can move all of the fields to the Selected Fields list box by clicking the double
right arrow (>>). You can move a field back from the Selected Fields list box by
clicking the left arrow (<). You can move all of the fields back by clicking the
double left arrow (<<).
4. In the Custom View Name field, enter a name for your custom view. Choose a
meaningful name that is related to the information the custom view displays. For
this example, enter PAYROLL.
This name will appear in the custom view’s title bar.

54 ESP-5.5-GS-01
 Chapter 2–Using ESP Workstation

Sorting the information in your custom view

1. Click the Sort tab.

2. In the Sort By dialog, click the down arrow to select the field you want to sort by.
For this example, select Job Name.
3. Select Ascending.
Ascending sorts from A to Z, lowest to highest number or by earliest date.
The Then By fields are optional.

ESP-5.5-GS-01 55
 Section–Monitoring your jobs

Setting up the filter to display only the PAYROLL Application

1. Click the Filter tab.

2. Click in the first row of the Field Name column and select Application Name from the
resulting drop-down menu.
Application Name appears in the Resulting Filter Criteria box at the bottom of the
dialog.
3. Click in the first row of the Relationship column and select IS from the resulting
drop-down menu.
Is appears in the Resulting Filter Criteria box.
4. Click in the first row of the Value column and enter PAYROLL in the text field.
PAYROLL appears in the Resulting Criteria box.

56 ESP-5.5-GS-01
 Chapter 2–Using ESP Workstation

Saving your custom view

1. Click OK. The custom view is now saved and appears in the list in the left pane.

Optionally, you can customize the font and display colors in your custom view by
selecting the Colors Fonts tab of the Custom View Configuration dialog.

Opening an Application in a graphical view

• Right-click a job and choose Locate this job in graph.
A graphical view of the job’s Application appears. The job is selected.

Changing your custom view

1. In the bottom of the left pane, click the Custom View tab.
The tree view appears in the left pane.
2. In the tree view, right-click the custom view you want to change.
3. Click Change Definition.
The Presentation tab of the Custom View Configuration dialog appears.
4. Use the preceding procedures to make the changes you want.

Displaying your custom view

• In the tree view, double-click the PAYROLL custom view.
Your PAYROLL custom view appears.

ESP-5.5-GS-01 57
 Section–Monitoring your jobs

58 ESP-5.5-GS-01
 Using ESP Workload Manager’s ISPF
Interface

This chapter provides a hands-on tutorial to get you started using ESP Workload
Manager’s ISPF interface. Follow the steps provided to learn how to complete the
following tasks:
1. Create a custom calendar.
2. Create an Application.
3. Create an Event to run your Application.
4. Simulate your Event.
5. Trigger your Event.
6. View your Application running.

ESP-5.5-GS-01 59
 Section–Our sample scenario

Our sample scenario

In this section, you will create an Application containing six jobs. Five of the jobs run
on z/OS and one of the jobs runs on Windows. The Application will be named
PAYROLL. The following flowchart shows the relationships between the jobs.

Note: If you don’t have access to an ESP Agent running on a Windows server,
substitute another z/OS job for job B.

60 ESP-5.5-GS-01
 Chapter 3–Using ESP Workload Manager’s ISPF Interface

Using menus and panels

The ISPF interface consists of menus and panels. You choose from lists of options by
typing a number or letter at a prompt and pressing Enter. You use the Tab key to
navigate within a panel.
ESP Workload Manager displays messages in the upper right corner of a menu or
panel. Messages are truncated at 24 characters; to display a complete message, press
the Help key (usually F1 or F13).

Quick navigation
If you know several of the selections you’ll make in sequence, you can join them with
a period to go directly to the panel you want. For example, if you know you’ll choose
E from one menu and then 3 from the next, you can type E.3 at the first prompt to
reach the panel you’re looking for.

Accessing help
You can get help about a menu, panel or available options by pressing the Help key.
This is usually F1 or F13; if neither of those keys work, ask your administrator which
key to use.

Accessing the Main Menu

1. Connect to the mainframe where ESP Workload Manager is installed.
2. Type ESP on the ISPF command line (not the TSO command line) and press
Enter.

ESP-5.5-GS-01 61
 Section–Defining a custom calendar

The Main Menu appears.

If this doesn’t work, contact your administrator to find out how to access your
ESP Workload Manager panels.

Defining a custom calendar

For this tutorial, you’ll create a new custom calendar named PAYCAL, define the
special period PAY_PERIOD, and then use PAY_PERIOD to schedule a job. To
complete the entire tutorial, ask your administrator to authorize you to create and edit
this calendar. If creating calendars won’t be part of your job, you might want to ask
your administrator to do it for you. If you don’t want to use custom calendars at all,
skip to the next section: Creating your Application; look for tips throughout the
tutorial that tell you what to substitute for PAY_PERIOD.

Creating your calendar

1. From the Main Menu, select M ESP Administration and press Enter.
The Administrator Subcommands menu appears.
2. Select 3 Calendar definitions and press Enter.
The Calendar Definitions panel appears.
3. At the Option prompt, type A.
4. In the Calendar field, type PAYCAL.
5. Press Enter.
The Define a Calendar panel appears.

62 ESP-5.5-GS-01
 Chapter 3–Using ESP Workload Manager’s ISPF Interface

6. Fill in the rest of the panel as shown in the following example, substituting your
user or group ID in the Owner field.
Note: Throughout
this tutorial we’ll use CYBKH01 as a sample user ID. When
you see CYBKH01, substitute your mainframe user ID or group ID.

7. Press Enter.
The Calendar Definitions panel appears.
8. Press F3 until you reach the Main Menu.

Defining a special period

A special period is a period between two special days of the same name. In this
example you’ll define two special days named PAY_PERIOD: the special days occur
on the first of the month and the 16th of the month. These definitions create pay
periods that run from the first of the month until the 15th and the 16th until the last
day of the month. You’ll define this period to repeat until 2016.
1. From the Main Menu, select L Calendars and press Enter.
The Calendar Control Menu appears.
2. Select 4 DEFSPEC and press Enter.
The Calendars panel appears.

ESP-5.5-GS-01 63
 Section–Creating your Application

3. Fill in the panel as shown in the following example and press Enter.

The Define a Special Day panel reappears with a message in the upper right corner
indicating the number of special days that have been created. Press the Help key
(usually F1 or F13) to see the entire message.
4. Press F3 until you reach the Main Menu.

Creating your Application

Five of the jobs in our example are z/OS jobs. When you create your Application,
you’ll need to identify the JCL library that contains the JCL for these jobs. You can
specify the default JCL library you want to use throughout an Application. If all or
most of the jobs are in the default library, you won’t have to specify a library as part of
each job’s details. If a job isn’t in the default library, you’ll have to specify its library at
the job level. Substitute the name of your default JCL library in the following JCLLIB
statement.
In job B, you’ll need to use the name of the ESP Agent running on your Windows
server instead of WIN_AGNT. Likewise, substitute the name of a command file on your
Windows server for C:\payroll\pay.cmd.
You can store an Application as a sequential data set, but usually you’ll store your
Applications as members of a partitioned data set.

Editing a member of a data set

1. From the Main Menu, press F3 until you reach the ISPF Primary Option Menu.
2. Allocate a partitioned data set to store your Applications.
3. Define the member PAYROLL.

64 ESP-5.5-GS-01
 Chapter 3–Using ESP Workload Manager’s ISPF Interface

4. Use the ISPF editor to enter the ESP statements shown in the following example
into member PAYROLL. Be sure to substitute your specific details for the text
shown in bold.
Indentation or other formatting is not required, but may make your Application
easier to read.
APPL PAYROLL
JCLLIB ‘CYBKH01.TEST.JCL’
JOB A
RUN DAILY
RELEASE (B, C)
ENDJOB
NT_JOB B
AGENT WIN_AGNT
CMDNAME C:\pay.cmd
RUN DAILY
RELEASE D
ENDJOB
JOB C
RUN DAILY
RELEASE D
ENDJOB
JOB D
RUN FRIDAY
RELEASE E
ENDJOB
JOB E
RUN LAST WORKDAY OF PAY_PERIOD
RELEASE F
ENDJOB
JOB F
RUN DAILY
ENDJOB
Tip: If you’re not using the PAYCAL calendar, make job E’s run statement RUN
LAST WORKDAY OF MONTH.
5. Save member PAYROLL.
6. Type F3 until you reach the ISPF Primary Option Menu
7. To return to the Main Menu, type ESP on the ISPF Primary Option Menu.

ESP-5.5-GS-01 65
 Section–Running your Application

Running your Application

After you create an Application, you have to tell ESP Workload Manager when to run
it and where its definition is stored. To do this, you create an Event.

Creating an Event

Event Names
Event names consist of two parts: a prefix and a descriptive name. The prefix can
contain up to eight alphanumeric characters, including national characters. The prefix
corresponds to a TSO user or group ID.
Event names can contain up to 16 characters, including national characters and the
underscore; the first character must be alphabetic. Event names must be unique. It’s a
good idea to name your Event the same name as the Application it runs.
In our example, the prefix is CYBKH01 and the descriptive name is PAYROLL; the
Event name is CYBKH01.PAYROLL.

Defining an Event
1. From the Main Menu, type E Events and press Enter.
The Event Management Menu appears.
2. Select 2 Define a new ESP Event and press Enter.
The Start Event Definition panel appears.
3. In the Prefix field, type your user or group ID. In the Descriptive Name field, type
PAYROLL. Press Enter.
The Specify Event Processing Options panel appears.

66 ESP-5.5-GS-01
 Chapter 3–Using ESP Workload Manager’s ISPF Interface

4. Fill in the fields as shown in the following example and press Enter.

The Invoke panel appears.

Tip: If you aren’t using a custom calendar, leave the Set Additional Calendars option
blank.
5. In the Data Set Name field, type the name of the data set you allocated for storing
your Applications. Type PAYROLL in the Member field and press Enter.
There may already be a data set name in the field. If that name isn’t correct, type
over it.
The Set Additional Calendars panel appears.
Tip: If you aren’t using a custom calendar, the Event Schedule panel appears instead.
Skip to step 7.
6. In the Calendar 1 field, type PAYCAL and press Enter.
The Event Schedule panel appears.
7. In the first Criteria field, type the schedule criteria for the Event and press Enter. In
this case we’ll use 4pm daily.
The Process Event Definition panel appears.
8. To review the Event you just created, type E and press Enter.
The Event Editing panel appears.
9. Press F3 to save the Event and return to the Event Management Menu.
A message appears in the upper right corner of the menu informing you of the
next time the Event is scheduled to run. Press the Help key (usually F1 or F13) to
see the entire message.

ESP-5.5-GS-01 67
 Section–Running your Application

Copying an existing Event

If you want to create a new Event that’s similar to one that exists, you might find it
efficient to save a copy of the existing Event as a new Event.

Copying your Event

1. From the Event Management Menu, select 3 Control an existing Event and press Enter.
The Event Control Menu appears.
2. Ensure the prefix in the Single Event area of the panel is correct and press Enter.
The List Events panel appears, showing a list of your Events.
3. Tab until your cursor is next to the PAYROLL Event, type E, and press Enter.
The PAYROLL Event opens for editing.
4. Move your cursor to the Event ID line so it’s over the P in PAYROLL and type
PAYROLL2).
5. Tab to the Command line, type save, and press Enter.
A new Event named PAYROLL2 is created. Because we only changed the name,
it’s a duplicate of the PAYROLL Event. You could have also changed other
attributes, such as schedule time or the Application to run.
6. Press F3 until you reach the Event Control Menu.

Simulating your Event

You use ESP Workload Manager’s simulation feature to test your Application. When
you simulate an Event, you can see which jobs are submitted to run and what their
predecessors and successors are. You can also check for missing JCL or other errors in
your Application. You can simulate the next occurrence of your Event, a future
occurrence or a past occurrence.
In this section you’ll simulate the following schedule criteria:
• Next occurrence of the Event
• Friday
• Last workday of the pay period

Next occurrence of the Event

1. Ensure the correct Event prefix appears in the Single Event section of the Event
Control Menu and that the option field is blank. Press Enter.

The List Events panel appears.

2. Tab until your cursor is next to your PAYROLL Event, type M, and press Enter.
The Simulate Event Execution panel appears.

68 ESP-5.5-GS-01
 Chapter 3–Using ESP Workload Manager’s ISPF Interface

3. Ensure all of the fields are blank and press Enter.

Note: As long as you remain in the Event panels, the parameters you enter in this
panel are saved for the most recent simulation you do. Then, if you trigger the
Event you last simulated, the parameters you specified in the simulation panel are
automatically filled in on the trigger panel. You can still change the parameters on
the trigger panel if you want.
The Event simulation begins and the results appear.
Jobs A, B, C, and F are included. If it happens to be Friday, D is also included. If
it happens to be the last workday of the pay period, E is also included. If it is prior
to 4pm, you’ll see which jobs are selected today. Otherwise, you’ll see which jobs
will be selected tomorrow.

4. Press F7 to scroll up in the results.

In addition to the jobs that are selected, the results include your Application,
Agent messages, and any errors that may have occurred.

ESP-5.5-GS-01 69
 Section–Running your Application

5. Press F3 twice to return to the Event Control Menu.

Friday
1. Ensure the option field is blank and press Enter.
The List Events panel appears.
2. Type M next to your PAYROLL Event and press Enter.
The Simulate Event Execution panel appears.
3. Type friday in the Schedule Time field and press Enter.
The Event simulation begins and the results appear.
In addition to jobs A, B, C, and F, which are scheduled to run daily, D is included
in the simulation output because it’s scheduled to run on Friday. If this Friday
happens to be the last workday of the pay period, E is also included.

4. Press F3 twice to return to the Event Control Menu.

Last workday of the pay period

1. Ensure the option field is blank and press Enter.
The List Events panel appears.
2. Type M next to your PAYROLL Event and press Enter.
The Simulate Event Execution panel appears.
3. Type last workday of pay_period in the Schedule Time field and press Enter.

70 ESP-5.5-GS-01
 Chapter 3–Using ESP Workload Manager’s ISPF Interface

Tip: If you aren’t using a custom calendar, type last workday of month
instead.
The Event simulation begins and the results appear.
Job E is included because it is scheduled to run on the last workday of the pay
period. By default, when ESP Workload Manager selects jobs for submission, it
checks to see if any relationships among jobs should be inherited. For example, if
the last workday of the pay period is a Friday, E must wait for D to complete
before it can run. If the last workday of the pay period is not a Friday, E waits for
B and C to complete.

Testing schedule criteria

You can test schedule criteria to see how ESP Workload Manager interprets different
scheduling terms. When you simulated your Events in our example, it might have
been useful to determine a date when the last workday of a pay period is also a Friday.
You can find such a date by testing schedule criteria.
1. From the Main Menu, type E and press Enter.
The Event Management Menu appears.
2. Select 4 Test and press Enter.
The Test schedule criteria panel appears.
3. In the Number of Cycles field, type the number of test results you’d like to generate.
For this example, type 6.
4. In the Schedule Criteria field, type last workday of pay_period.
Tip: If you aren’t using a custom calendar, type last workday of month
instead.

ESP-5.5-GS-01 71
 Section–Running your Application

5. In the Calendar field, type PAYCAL and press Enter.

Tip: If you aren’t using a custom calendar, skip this step.
Results similar to those shown in the following example appear.

6. Press F3 until you return to the Main Menu.

Triggering your Event

Your Event is scheduled to run at 4pm each day, and ESP Workload Manager will
trigger the Event at that time. If you want to run the Event immediately, you can
manually trigger it.

To manually trigger an Event

1. From the ESP Main Menu, type E Events and press Enter.
The Event Management Menu appears.
2. Select 3 Control an existing Event and press Enter.
The Event Control Menu appears.
3. Leave the option field blank, but ensure the correct Event prefix appears in the
Single Event section of the panel. Press Enter.

The List Events panel appears.

4. Type T next to your PAYROLL Event and press Enter.
The Trigger an Event panel appears.

72 ESP-5.5-GS-01
 Chapter 3–Using ESP Workload Manager’s ISPF Interface

5. Type add in the Replace/Add field, ensure all other fields are blank, and press Enter.
This adds an execution of the Event in addition to the scheduled execution.
The List Events panel appears. Note the ESP Workload Manager message ‘Event
Triggered’ in the upper right corner of the panel. This means that the Event has
been triggered and will run your Application.
6. Press F3 until you return to the Main Menu.

Monitoring your jobs

Consolidated Status Facility

ESP Workload Manager’s Consolidated Status Facility (CSF) provides a real-time view
of your system’s workload. CSF shows you which jobs have recently executed, which
are currently executing, and which are waiting to execute. You can customize CSF to
display the information you want in the format you want.
When you start CSF, you see the general view. The information displayed in the
general view depends on how CSF is set up, but you will probably see something like
the following.

You’ll create a view that only includes select information. To do this, you’ll first create
a new view by replicating the general view, and then you’ll specify what information
your new view displays, and finally you’ll specify how CSF displays it.

ESP-5.5-GS-01 73
 Section–Monitoring your jobs

Creating a new view

1. From the Main Menu, enter C.
2. On the CSF panel command line, type V and press Enter.
The View Definitions panel appears. This panel shows a list of views and their
descriptions.
3. Next to the General View view, type R and press Enter.
The Replicate a View panel appears.
4. In the New View Name field, type PAYROLL.
5. In the Description field, type payroll view.
6. In the No Items to Display field, type No PAYROLL items.
This is the message that appears if there are no items that fit your view’s criteria.
7. Press Enter.
The View Definitions panel appears with your new view added to the list.
8. Next to the PAYROLL view, type S and press Enter.
The Consolidated Status panel displays the PAYROLL view.

Defining filters for your view

1. On the Consolidated Status panel command line, type FI and press Enter.
The Filter Specifications panel appears.
2. In the Appl field, type PAYROLL and press Enter.
The Consolidated Status panel appears, showing only the jobs in the PAYROLL
Application.

Customizing the layout of your view

You’ll customize your view so that it shows only the following:
• The job name
Note: The job name is always included in the first column of a view.
• The job number
• The Application name
• The Application generation number
• The job state
• The job status
1. On the Consolidated Status panel command line, type PR and press Enter.
The Presentation Fields panel appears, listing all of the fields that CSF can display.
2. On the Application row, in the Pres Order column, type 3.

74 ESP-5.5-GS-01
 Chapter 3–Using ESP Workload Manager’s ISPF Interface

3. Fill in the following presentation orders for the following rows. Be sure to scroll
down to view all rows.
Appl Generation -4
Processing Node -5
System Status -6
Job Number -2
Note: Processing node is another term for a job’s state.
4. Delete the other numbers on the panel.
5. Press Enter.
The Consolidated Status panel appears. It now contains only the information
specified. It should be similar to the following panel.

6. Press F3 to return to the ESP Main Menu.

Application Monitor
ESP Workload Manager’s Application Monitor provides a real-time view of your
system’s Applications. Application Monitor shows you which Applications have
recently run, which are currently running, and which are waiting to run. You can
customize Application Monitor to display the information you want in the format
you want.

ESP-5.5-GS-01 75
 Section–Monitoring your jobs

When you start Application Monitor, you see the default Application viewer. The
information displayed in the default Application viewer depends on how Application
Monitor is set up, but you will probably see something like this.

You’ll create a view that only includes select information. To do this, you’ll first create
a new view by replicating the default view, and then you’ll specify what information
your new view displays, and finally you’ll specify how Application Monitor displays it.

Creating a new view

1. From the Main Menu, enter A.
2. On the Application Status panel command line, type V and press Enter.
The Application View Summary panel appears. This panel shows a list of views and
their descriptions.
3. Next to the ESP-VIEW view, type R and press Enter.
4. In the Specify A View Name pop-up panel, type PAYROLL and press Enter.
The Application View Summary panel displays the PAYROLL view.
5. To mark the view as a favorite, type Y in the Fav column.
You can select favorite views by pressing the F5 (previous view) and F6 (next view)
keys.
6. In the Description column, type payroll view.
7. To update your view, type U next to the view and press Enter.
8. Next to the PAYROLL view, type S and press Enter.
The Application Status panel displays the PAYROLL view.

76 ESP-5.5-GS-01
 Chapter 3–Using ESP Workload Manager’s ISPF Interface

Defining filters for your view

1. On the Application Status panel command line, type FI and press Enter.
The Basic Application Filter panel appears.
2. In the Complete? field, type Y.
3. In the Appl Name -1 field, type PAYROLL.
4. Press F3.
The Application Status panel appears, showing only generations of the PAYROLL
Application.

Customizing the layout of your view

You’ll customize your view so that it shows only the following:
• The Application name
• The Application generation number
• The Application status
• The Application status details
• The Application elapsed run time
1. On the Application Status panel command line, type PR and press Enter.
The Application Presentation panel appears, listing all of the fields that Application
Monitor can display.
2. On the Appl NAME row, in the FIELD Ord column, type 1.
3. Fill in the following presentation orders for the following rows. Be sure to scroll
down to view all rows.
Appl ELAPSED run Time -5
Appl GENERATION Number -2
Appl STATUS -3
Appl Status DETAILS -4
4. In the FIELD Ord column, delete the other numbers on the panel.

ESP-5.5-GS-01 77
 Section–Monitoring your jobs

5. Press F3.
The Application Status panel appears. It now contains only the information
specified. It should be similar to the following panel.

Displaying the active jobs for a selected Application

From Application Monitor, you can access CSF to monitor and control the jobs for
your PAYROLL Application.
1. In Application Status panel, type CSF next to the PAYROLL Application and press
Enter.

The Consolidated Status panel appears, showing only the jobs in that generation of
the PAYROLL Application.
2. To return to Application Monitor, press F3.
3. Press F3 to return to the ESP Main Menu.

78 ESP-5.5-GS-01
 Service Level Management

ESP Workload Manager offers many features beyond the basic ones described earlier
in this book. This Appendix provides an overview of two of the features that enable
you to proactively manage your service level agreements: automated critical path
analysis and due-out notification. These features predict when a critical job is in
danger of being late, allowing corrective action to be taken before the job is actually
late.

ESP-5.5-GS-01 79
 Section–Anticipated end times and due-out times

Anticipated end times and due-out times

When ESP Workload Manager generates an Application, it uses historical average run
times to calculate an anticipated end time for each job. It adjusts the anticipated end
times as the Application progresses. If a job is not completed by its anticipated end
time, ESP Workload Manager continues to adjust this time so there is no indication
that the job has missed its original anticipated end time. However, if you want to keep
track of when certain jobs are late you can specify due-out times for these processing
stages:
• Submission time
• Start time
• End time
If a job has not completed the specified stage of processing by its due-out time, the
job’s status field changes to OVERDUE. You can specify that ESP Workload Manager
trigger an Event or send a message when a job is OVERDUE, or you can view
OVERDUE jobs in Workload Director’s graphical or custom views.
When you specify a due-out time for a job, ESP Workload Manager propagates due-
out times upstream to all of the job’s predecessors. It calculates these times based on
historical average run times for the predecessor jobs. If a calculated due-out time is not
met, ESP Workload Manager changes the job’s status to OVERDUE, just as it does
for specified due-out times. This enables early notification when a predecessor job
may endanger a mission-critical job downstream.
With other scheduling products, you have to calculate and code due-out times for
each job in a stream. ESP Workload Manager’s propagation feature does this
automatically, reducing code complexity and maintenance.

Suppose that D in the following Application should complete execution by 7pm.

ESP Workload Manager automatically calculates due-out times for jobs A, B, and C.
If any job in the Application is late, it is marked as OVERDUE, thus allowing
corrective action to be taken earlier in the Application.

80 ESP-5.5-GS-01
 Appendix A–Service Level Management

Critical path analysis

ESP Workload Manager allows you to identify any job as a critical point in an
Application. The longest path to that job, based on historical execution times, is the
critical path. If a job has been designated critical, ESP Workload Manager determines
the critical path when it generates the Application. The critical path may vary based
on which jobs are selected in a particular generation. Let’s look at how critical paths
vary in the following Application where job Z is critical.

If These Jobs Are Not The Critical Path Is

Selected
X, Y A, B, E, F, Z
X, Z A, B, E, F
X, Y, F A, B, C, D, Z and A, B, E, Z
Z A, B, X, Y (defaults to longest path)

You can enable the critical path feature for all Applications, for selected Applications
or for no Applications. Prior to using critical path, check with your administrator to
ensure that it is enabled in your installation. You can mark a job as critical when you
specify its job details in Workload Editor. If critical path is enabled and no job is
designated as critical, ESP Workload Manager calculates the longest path.

ESP-5.5-GS-01 81
 Section–Critical path analysis

The following is an example of an enterprise Application with two critical paths. In

Workload Director’s Graphical View, critical paths appear in green; in this diagram,
the critical paths are shown with thicker arrows.

82 ESP-5.5-GS-01
 Index

A Application Monitor
Agent, 2, 8 creating a new view, 76
anticipated end time, 80 displaying jobs in CSF, 78
Application fields, 77
defining filters, 77
with ESP Workstation, 7, 31
with ISPF, 64 C
generation, 14 calendar
JCL library, default, 7 about, 4–5
monitoring defining
with ESP Workstation, 15, 51 with ESP Workstation, 4, 27
with ISPF, 73 with ISPF, 62
naming holiday, 4
with ESP Workstation, 7, 32 scheduling terms, 4–5
with ISPF, 64, 65 SYSTEM, 4
properties, 8 using
relationship to Event, 10 in ESP Workstation, 42
relationship to Procedure, 5 in ISPF, 67
running Consolidated Status Facility
See also Event, triggering creating a new view, 74
with ESP Workstation, 41 displaying jobs from Application Monitor, 78
with ISPF, 66 fields, 74
saving with ESP Workstation, 39 filters, 74
uploading with ESP Workstation, 40 controlling a job, 16

ESP-5.5-GS-01 83
 critical job, 79 NT_JOB, 9
critical path RELEASE, 9
analysis, 81 RUN, 9
in Workload Director, 82 SCRIPTNAME, 9
CSF ESP Workload Manager
See Consolidated Status Facility connecting to, 25
custom calendar introduction, 2–3
See calendar ESP Workstation
custom view about, 2
about, 16 tutorial, 23
default, 53 Event
defining, 54 about, 10
filters, 56 copying in ISPF, 68
saving, 57 defining
sorting, 55 with ESP Workstation, 10, 41
with ISPF, 66
naming
D with ESP Workstation, 10, 41
defining with ISPF, 66
Application simulating
with ESP Workstation, 7, 31 with ESP Workstation, 12, 45
with ISPF, 64 with ISPF, 68
Application Monitor view, 76 triggering
calendar with ESP Workstation, 14, 50
with ESP Workstation, 4, 27 with ISPF, 72
with ISPF, 62
CSF view, 74
custom view, 54 F
Event F1 help
with ESP Workstation, 10, 41 with ESP Workstation, 26
with ISPF, 66 with ISPF, 61
special period
with ESP Workstation, 29
G
with ISPF, 63
due-out time, 80 generation number, 14
generation of an Application, 14
graphical view
E about, 15
ESP Agent, 2, 8 tutorial, 51
ESP statements
in Applications, 8
H
in ISPF, 65
in Procedures, 5 help
in Workload Editor, 8 with ESP Workstation, 26
AGENT, 9 with ISPF, 61
ENDJOB, 8 hold count, 13
JCLLIB, 8
JOB, 8 I
LINUX_JOB, 9 inherited job relationships, 18

84 ESP-5.5-GS-01
 Index

ISPF tutorial, 59 P
Procedure, 5
J
JCL library, default, 7 R
job run frequency
controlling, 16 and inherited job relationships, 18
dependencies, inherited, 18 and JOB statement, 9
details differing within Application, 17–18
in ESP Workstation, 16, 36 of job, 3, 7, 9, 17
in ISPF, 64 specifying with ESP Workstation, 37
monitoring running
with ESP Workstation, 15, 51 Application
with ISPF, 73 with ESP Workstation, 41
naming with ISPF, 66
with ESP Workstation, 36 running jobs
with ISPF, 65 See triggering an Event
running
with ESP Workstation, 41
with ISPF, 66 S
states, 15 schedule criteria
for Events
with ESP Workstation, 11, 44
L with ISPF, 67
layout of workflow diagram, 36 simulating
with ESP Workstation, 47
M with ISPF, 70
monitoring testing
with ESP Workstation, 15, 51 with ESP Workstation, 48
with ISPF, 73 with ISPF, 71
scheduling terms
in calendars, 4–5
N See also run frequency
naming See also schedule criteria
Application service level management, 79
with ESP Workstation, 7, 32 simulation
with ISPF, 64, 65 and inherited job relationships, 19
Event with ESP Workstation, 12, 45
with ESP Workstation, 10, 41 with ISPF, 68
with ISPF, 66 special day, 4–5
job special period
with ESP Workstation, 36 about, 4–5
with ISPF, 65 defining
with ESP Workstation, 29
O with ISPF, 63
statements, ESP
OVERDUE job status, 80
See ESP statements
states, job, 15

ESP-5.5-GS-01 85
 T with ESP Workstation, 38
testing by simulating, 12 with ISPF, 64
See also simulation workflow diagram, 33
testing schedule criteria workload
with ESP Workstation, 48 about, 3
with ISPF, 71 defining, 5
triggering an Event distributed, 8
with ESP Workstation, 14, 50 scheduling, 10, 12
with ISPF, 72
Z
W z/OS
Windows job, specifying details jobs, JCL for, 8

86 ESP-5.5-GS-01