Escolar Documentos
Profissional Documentos
Cultura Documentos
© Copyright IBM Corporation 1990, 2001. All rights reserved. May only be used pursuant to a Tivoli Systems Software License
Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No
part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer
language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior
written permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of
any machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporation
copyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. The document is
not intended for production and is furnished “as is” without warranty of any kind. All warranties on this document are hereby
disclaimed, including the warranties of merchantability and fitness for a particular purpose.
U.S. Government Users Restricted Rights—Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM
Corporation.
Trademarks
IBM, Tivoli, the Tivoli logo, AIX, BookManager, Hiperbatch, OS/390, RACF, and z/OS are trademarks or registered trademarks of
International Business Machines Corporation or Tivoli Systems Inc. in the United States, other countries, or both.
Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or
both.
Other company, product, and service names may be trademarks or service marks of others.
Notices
References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in
all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to
imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or other
legally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead of
the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except
those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or
pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license
to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive,
Armonk, New York 10504-1785, U.S.A.
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
Who Should Read This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
What This Guide Contains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix
Tivoli Workload Scheduler for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix
Tivoli Workload Scheduler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx
Accessing Publications Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx
Workload Scheduler for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi
Ordering Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi
Providing Feedback about Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi
LookAt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi
Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxii
Conventions Used in This Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxii
Typeface Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxii
Operating System-dependent Variables and Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxiii
Other Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxiii
iv Version 8.1
Updating Workload Scheduler Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Useful Framework Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Part II. Using the Job Scheduling Console with Tivoli Workload
Scheduler for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
vi Version 8.1
Modifying Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Modifying Job Stream Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Adding and Modifying Jobs and Dependencies in the Graph View . . . . . . . . . . . . . . . . . . . . . 113
Adding and Modifying Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Viewing and Modifying Time Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Deleting Job Streams from the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Using Copy to Add an External Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Using Existing Definitions to Create Other Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Part III. Using the Job Scheduling Console with Tivoli Workload
Scheduler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
x Version 8.1
Deleting an External Job Stream in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Modifying an External Job in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Deleting an External Job in a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Deleting Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
xx Version 8.1
206. Properties - Job Instance General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
207. Properties - Job Instance Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
208. Properties - Job Instance Time Restrictions Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
209. Properties - Job Instance Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
210. Properties - Job Instance Prompts Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
211. Properties - Job Instance Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
212. Properties - Job Instance Predecessors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
213. Workstation Status List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
214. Properties - Workstation in Plan Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
215. Change Limit - Workstation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
216. Change Fence - Workstation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
217. Switch Manager - Domain Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
218. Status of All Files List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
219. Set Alternate Plan Files Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
220. Properties - Job Instance Common List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
221. Properties - Job Stream Instance Common List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
The Tivoli Job Scheduling Console User’s Guide provides an introduction to and an
explanation of the Tivoli Job Scheduling Console Feature Level 1.2. It explains how to
install the console and provides instructions for performing scheduling tasks using Tivoli
Workload Scheduler for z/OS and Tivoli Workload Scheduler.
Part II. Using the Job Scheduling Console with Tivoli Workload Scheduler for z/OS
Part III. Using the Job Scheduling Console with Tivoli Workload Scheduler
Publications
This section lists publications in the Tivoli Workload Scheduler suite. It also describes how
to access Tivoli publications online, how to order Tivoli publications, and how to make
comments on Tivoli publications.
http://www.tivoli.com/support/documents/
These publications are available in PDF or HTML format, or both. Translated documents are
also available for some products.
You can read the softcopy books on CD-ROMs using these IBM licensed programs:
¶ BookManager® READ/2
¶ BookManager READ/DOS
¶ BookManager READ/6000
All the BookManager programs need a personal computer equipped with a CD-ROM disk
drive (capable of reading disks formatted in the ISO 9660 standard) and a matching adapter
and cable. For additional hardware and software information, refer to the documentation for
the specific BookManager product you are using.
http://www.tivoli.com/support/Prodman/html/pub_order.html
LookAt
LookAt is an online facility that allows you to look up explanations for z/OS messages and
system abends. Using LookAt to find information is faster than a conventional search
because LookAt goes directly to the explanation. LookAt can be accessed from the internet
or from a Time Sharing Option (TSO) command line.
http://www.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/lookat.html
To find a message explanation from a TSO command line, type the message ID, as in the
following example:
lookat iec192i
This results in direct access to the message explanation for message IEC192I.
To find a message explanation from the LookAt Web site, type the message ID. You can
select the release if needed.
Some messages have information in more than one book. For example, IEC192I has routing
and descriptor codes listed in OS/390 MVS Routing and Descriptor Codes, GC28-1778. For
such messages, LookAt prompts you to choose which book to open.
http://www.tivoli.com/support/handbook/
The handbook provides information about how to contact Customer Support, depending on
the severity of your problem, as well as the following information:
¶ Registration and eligibility
¶ Telephone numbers and e-mail addresses, depending on the country you are in
¶ What information you should gather before contacting support
When using the Microsoft Windows command line, replace $variable with %variable% for
environment variables and replace each forward slash (/) with a backslash (\) in directory
paths.
Note: If you are using the bash shell on a Windows system, you can use the UNIX
conventions.
Other Conventions
Wildcards, as used in this book, are defined as:
* (asterisk) Used to represent a character string.
? (question mark) Used to represent a single character.
2 Version 8.1
Working with Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Default Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Default Database Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Default Plan Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Creating a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Specifying Defaults for Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Creating a Group of Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Displaying a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Detaching a List Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Modifying a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Deleting a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Finding Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Example: Finding a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
The Job Scheduling Console allows you to work with Tivoli Workload Scheduler for z/OS
and Tivoli Workload Scheduler. You can work with these products simultaneously from the
same graphical console.
Extensions, built into the Job Scheduling Console, extend its base scheduling functions to
specific scheduling functions of Tivoli Workload Scheduler for z/OS and of Tivoli Workload
Scheduler.
Connectors manage the traffic between the Job Scheduling Console and the job schedulers.
Connectors are installed separately on a Tivoli management server and on managed nodes
that have access to the scheduler.
Note: To use the Job Scheduling Console with Tivoli Workload Scheduler for z/OS, you
must install the Workload Scheduler for z/OS Connector. To use the Job Scheduling
Console with Workload Scheduler, you must install the Workload Scheduler
Connector.
To use the Job Scheduling Console with both schedulers, you must install both types
of Connector, one for each type of scheduler.
For each of these functions, you can use a list creation mechanism that enables you to list
database or plan objects that you select according to filtering criteria. Filtering criteria
narrow a list down to selected objects that you want to work with. You can list objects
without using filtering criteria. In this case, the list displays all the existing objects of a kind.
You can use both predefined lists that are packaged with the Job Scheduling Console, and
lists that you create.
Modifying a job stream involves adding, deleting, or modifying any of the jobs that
comprise it, along with the dependencies and run cycles. You can also delete an entire job
stream.
Job stream definitions are stored in the job scheduler databases. To browse or update job
streams you have created, you must make and run a list of job streams in the database.
Jobs are stored in the job scheduler database as parts of job streams. To browse, update, or
delete a job definition, you must list the parent job stream in the database.
6 Version 8.1
1. Introduction
Working with Run Cycles
A run cycle provides the scheduling information of a job stream. Like jobs, you can create
run cycles only after you have defined the job streams to which they apply. A job stream can
have more than one run cycle. Creating a run cycle involves:
¶ Defining run cycle properties
¶ Specifying when the run cycle starts and how long it lasts
¶ Specifying the rules that define the run days for the job stream
Run cycle definitions are stored in the job scheduler database as parts of job streams. To
browse, update, or delete a run cycle definition, you must list the parent job stream in the
database.
Resource definitions are stored in the job scheduler database. To browse, update, or delete a
resource definition, you must make and run a list of resources in the database.
Operator Tasks
From the Job Scheduling Console, you can monitor and control the following objects in the
scheduler plan:
¶ Job stream instances
¶ Job instances
¶ Resource instances
¶ Workstations
To monitor and control these objects, you must first display them in a list in the Job
Scheduling Console.
You can list workstations defined in the scheduler database, selected according to filtering
criteria, and browse or modify their properties. You can also delete workstations from the
database.
You can list workstations defined in the scheduler database, selected according to filtering
criteria, and browse or modify their properties. You can also delete workstations from the
database.
8 Version 8.1
1. Introduction
Working with Job Streams
You can use the Job Scheduling Console to work with job streams and job stream templates.
Job stream templates contain only scheduling information. When you define a job stream as
belonging to a template, you imply that it must share the template calendar and run cycles.
You can:
¶ Create, update, or delete job stream templates
¶ Add or remove a job stream from a job stream template
¶ List job stream templates in the scheduler database
You can list resources defined in the scheduler database, selected according to filtering
criteria, and browse or modify their properties. You can also delete resources from the
database.
Operator Tasks
All the tasks that involve working with objects in the plan, are referred to as operator tasks
in this book. You must first list the objects in the plan in order to work with any of them.
You can also view the job instances scheduled to run on a given workstation at any time
during the plan.
After you complete the definition of a job stream in terms of jobs, dependencies, and run
cycles, and you mark it active in the Job Stream Properties window, you have to go to the
scheduler to schedule the job stream into the current plan. You cannot add a job stream to
the plan from the Job Scheduling Console.
10 Version 8.1
1. Introduction
Table 3. Job Scheduling Console Terminology (continued)
Tivoli Workload Tivoli Workload Explanation
Scheduler for z/OS Scheduler
In-effect date for run Valid from The first date that a run cycle is valid.
cycles
Input arrival time (Earliest) start time The time before when a job or job stream is
planned to be ready for processing.
Negative run cycle Exclusionary run cycle Specifies when a job stream must not run.
Occurrence Job stream instance A job stream that is scheduled for a specific run
date in the plan.
Controller Engine The component that runs on the controlling
system, and that contains the tasks that manage
the plans and databases.
Operation Job A unit of work that is part of a job stream and
that is processed at a workstation.
Operation number Job identifier The number that identifies a job.
Operations in the current Job instances A job scheduled for a specific run date in the
plan plan.
Out-of-effect date for run Valid to The last date that a run cycle is valid.
cycles
Run cycle with offsets Offset-based run cycle Includes a user-defined period and an offset, such
as the 3rd day in a 90-day period.
Run cycle with rules Rule-based run cycle Includes a rule, such as the first Friday of March
or the second workday of the week.
Special resources Logical resources Any type of limited resource, such as tape drives,
communication lines, databases, or printers, that
is needed to run a job.
Status: Complete Successful The job or job stream has been completed.
Status: Delete Canceled The job or job stream has been deleted from the
plan.
Status: Started Running The job has started (jobs only).
Task Job A job performed at a computer workstation.
You can install Job Scheduling Services either from the Tivoli desktop or from the command
line.
Note: You must install Job Scheduling Services on the Tivoli server and on each managed
node where the Connector is to be installed.
Before Installing
Read this information before you install Job Scheduling Services.
System Requirements
The Connector has the following system requirements:
Software
¶ Tivoli Management Framework:
Version 3.7.1 for Microsoft Windows, AIX, HP-UX, and Sun Solaris
Version 3.7B for Linux
Hardware
¶ CD-ROM drive for installation.
¶ Approximately 4 MB of free disk space.
Note: You must install Job Scheduling Services on at least the Tivoli management
server. You can install the Connector only on managed nodes where Job
Scheduling Services is installed.
8. Click Install. The Product Install window is displayed, which shows you the progress
of the installation.
9. Click Continue Install to continue the installation or click Cancel to cancel the
installation.
10. The installation program copies the files and configures the Tivoli database with the
new classes. When the installation is complete, the message Finished product
installation appears. Click Close.
14 Version 8.1
Installing from the Command Line
To install the Connector from the command line, ensure you have set the Tivoli environment
(see “Setting the Tivoli Environment” on page 13), then enter one of the following
commands:
¶ To install on all managed nodes:
winstall -c install_dir -i TMF_JSS
¶ To install on only one managed node:
winstall -c install_dir -i TMF_JSS node
You must install Job Scheduling Services on at least the Tivoli management server. You can
only install the Connector on managed nodes where Job Scheduling Services is installed.
To uninstall Job Scheduling Services, ensure you have set the Tivoli environment (see
“Setting the Tivoli Environment” on page 13), then enter one of the following commands:
¶ On AIX, Solaris, HP-UX, and Linux, enter:
wuninst TMF_JSS node -rmfiles
¶ On Microsoft Windows, first enter:
bash
then enter:
where:
node
is the name of the system from which you want to remove Job Scheduling Services.
This removes the Job Scheduling Services classes and installation files.
Installing Patches
To install patches, ensure you have set the Tivoli environment (see “Setting the Tivoli
Environment” on page 13), then:
1. Open the Tivoli Desktop.
2. From the Desktop menu select Install, then Install Patch. The Install Patch window is
displayed.
3. Follow the instructions presented online.
16 Version 8.1
3
Installing the Tivoli Workload Scheduler
for z/OS Connector
This chapter describes how to install the Tivoli Workload Scheduler for z/OS Connector. The
Job Scheduling Console communicates with the Workload Scheduler for z/OS system
through the Connector, a protocol converter that translates the instructions entered through
the console into scheduler commands. Although the Connector must be running to use the
console, you can install them in the order you prefer.
You must install the Connector on a Tivoli server or managed node, while the Job
Scheduling Console can be installed on any workstation that has a TCP/IP connection with
z/OS Connector
Framework Release Notes.
This chapter explains how to install the Workload Scheduler for z/OS Connector. “Installing
the Tivoli Workload Scheduler Connector” on page 25 explains how to install the Workload
Scheduler Connector. “Installing the Tivoli Job Scheduling Console” on page 33 explains
how to install the Job Scheduling Console.
Before Installing
Read this information before you install the Connector.
System Requirements
The Connector has the following system requirements:
Software
¶ Tivoli Management Framework:
Version 3.7.1 for Microsoft Windows, AIX, HP-UX, and Sun Solaris
Version 3.7B for Linux
¶ Tivoli Workload Scheduler for z/OS 8.1, or Tivoli OPC 2.1 or later
¶ Tivoli Job Scheduling Services 1.2
¶ TCP/IP network communications.
¶ A Workload Scheduler for z/OS user account is required for proper installation. You can
create the account beforehand, or have the Setup program create it for you.
Hardware
¶ CD-ROM drive for installation.
You can install the Connector either from the Tivoli desktop or from the command line.
Note: Ensure that you have already installed Job Scheduling Services. If you have not yet
done so, see “Installing Tivoli Job Scheduling Services” on page 13.
If you want to re-install the Connector, you must uninstall the existing one before you do.
See “Uninstalling the Connector” on page 22.
Setting the Tivoli Environment
To install the Connector, you must first set the Tivoli environment. To do this, log in as root
or administrator, then enter one of the following commands:
Table 5. Setting the Tivoli Environment
For this operating system ... Enter this command ...
AIX, Solaris, HP-UX, Linux ./etc/Tivoli/setup_env.sh
Microsoft Windows, UNIX shell .c:/windir/system32/drivers/etc/Tivoli/setup_env.sh
Microsoft Windows, DOS shell c:\windir\system32\drivers\etc\Tivoli\setup_env.cmd
18 Version 8.1
where windir is the name of the Microsoft Windows installation directory.
Installing from the Tivoli Desktop
To install the Connector from the Tivoli Desktop, ensure you have set the Tivoli
environment (see “Setting the Tivoli Environment” on page 18), then:
1. Open the Tivoli Desktop.
2. From the Desktop menu, select Install, then Install Product. The Install Product
window is displayed.
3. Click Select Media to select the installation directory. The File Browser window is
displayed.
4. Type or select the installation path. The path includes the directory containing the
CONTENTS.LST file.
5. Click Set Media & Close. You return to the Install Product window.
6. Select Tivoli OPC Connector.
7. In the Available Clients list, select the managed nodes to install on and move them to
the Clients to Install On list.
z/OS Connector
can create instances only on managed nodes where the Connector is installed.
8. Click Install. The Product Install window is displayed, which shows you the progress
of the installation.
9. Click Continue Install to continue the installation or click Cancel to cancel the
installation.
10. The installation program copies the files and configures the Tivoli database with the
new classes. When the installation is complete, the message Finished product
installation appears. Click Close.
Installing from the Command Line
To install the Connector from the command line, ensure you have set the Tivoli environment
(see “Setting the Tivoli Environment” on page 18), then enter one of the following
commands:
¶ To install on all managed nodes:
winstall -c install_dir -i opc
¶ To install on only one managed node:
winstall -c install_dir -i opc node
where:
install_dir
is the path containing the Connector installation program.
node
is the name of the destination managed node.
You must install the Connector on at least the Tivoli management server. You can create
instances only on managed nodes where the Connector is installed.
Note: You must be a Tivoli administrator with admin, senior, or super authorization roles.
For more information refer to “Authorization Roles Required for Instances”.
Enter the following command on the Tivoli server or managed node where you installed the
Connector that you need to access through the Job Scheduling Console:
where:
node
is the name or the ID of the managed node on which you are creating the instance. The
name of the Tivoli server is the default.
engine_name
is the name of the new instance.
address
is the IP address of the z/OS system where the scheduler subsystem that you want to
connect to is installed.
port
is the port number of the TCP/IP server to which the Connector will connect.
You can also run the wopcconn utility in interactive mode. To do this:
1. On the command line, enter wopcconn with no arguments.
2. Select choice number 1 in the first menu.
Authorization Roles Required for Instances
To manage Connector instances from a Tivoli server or managed node, you must be a Tivoli
administrator with one or more of the following roles:
Table 6. Authorization Roles
These roles ... Can perform these tasks ...
user Use the instances
View instance settings
admin, senior, super Perform all actions available to the user role
Create and remove instances
Change instance settings
Start and stop instances
Note: To control access to the scheduler, the TCP/IP server associates each Tivoli
administrator to a Remote Access Control Facility (RACF®) user. For this reason, a
20 Version 8.1
Tivoli administrator should be defined for every RACF user. For additional
information, refer to the Tivoli Workload Scheduler for z/OS Customization and
Tuning book.
Managing Connector Instances
Use the wopcconn utility to create, remove, and manage Connector instances. This program
is downloaded when you install the Connector.
Note: Before you use wopcconn, you must set the Tivoli environment. See “Setting the
Tivoli Environment” on page 18.
The following table describes how to use wopcconn on the command line to manage
Connector instances:
z/OS Connector
information, such as product
version and the object ID of
the instance.
Change the settings of an wopcconn -view -e engine_name | -o object_id -n new_name -a
instance address -p port -t trace_level -l trace_length
where:
node
is the name or the object ID (OID) of the managed node on which you are creating the
instance. The name of the Tivoli server is the default.
engine_name
is the name of the new or existing instance.
object_id
is the object ID of the instance.
new_name
is the new name for the instance.
address
is the IP address of the z/OS system where the Workload Scheduler for z/OS subsystem
that you want to connect to is installed.
port
is the port number of the Workload Scheduler for z/OS TCP/IP server to which the
Connector must connect.
trace_level
is the trace detail level, from 0 to 5.
trace_length
is the maximum length of the trace file.
then enter:
where:
node
is the name of the system from which you want to remove the Connector. To uninstall
the Connector from all the managed nodes on which it is installed, replace node with the
name of the Tivoli server.
Installing Patches
To install patches, ensure you have set the Tivoli environment (see “Setting the Tivoli
Environment” on page 18), then:
1. Open the Tivoli Desktop.
2. From the Desktop menu select Install, then Install Patch. The Install Patch window is
displayed.
3. Follow the instructions presented online.
22 Version 8.1
Table 7. Useful Framework Commands (continued)
This command ... Performs this function ...
wlookup -ar MaestroEngine Lists the instances of this class type (same for the other classes).
For example::
barb 1318267480.2.19#Maestro::Engine#
The number before the first period (.) is the region number and the
second number is the managed node ID (1 is the Tivoli server). In
a multi-Tivoli environment, you can determine where a particular
instance is installed by looking at this number because all Tivoli
regions have a unique ID.
wuninst -list Lists all the products that can be uninstalled.
wuninst {ProductName} -list Lists the managed nodes where a product is installed.
You must install the Connector on a Tivoli server or managed node, while the Job
Scheduling Console can be installed on any workstation that has a TCP/IP connection with
the machine running the Connector. For information about how to install a Tivoli server or
managed node, refer to the Tivoli Framework Planning and Installation Guide and the Tivoli
Framework Release Notes.
Before Installing
Read this information before you install the Connector.
System Requirements
The Connector has the following system requirements:
Software
¶ Tivoli Management Framework:
Version 3.7.1 for Microsoft Windows, AIX, HP-UX, and Sun Solaris
Version 3.7B for Linux
¶ Tivoli Workload Scheduler 8.1
¶ Tivoli Job Scheduling Services 1.2
¶ TCP/IP network communications.
¶ A Workload Scheduler user account is required for proper installation. You can create
the account beforehand, or have the Setup program create it for you.
Hardware
¶ CD-ROM drive for installation
¶ Approximately 100 MB of free disk space for domain managers, and fault-tolerant
agents. Approximately 40 MB for standard agents. In addition, the Workload Scheduler
produces log files and temporary files, which are placed on the local hard drive. The
amount of space required depends on the number of jobs managed by Workload
Scheduler, and the amount of time you choose to retain log files.
Note: Each Connector instance name must be unique within the Workload Scheduler
network, so you must create each instance separately. Preferably, use the name of
the scheduler agent as the instance name.
Fault-tolerant Agents
Workload Scheduler fault-tolerant agents that are accessed through the Job Scheduling
Console to check local data, must have Job Scheduling Services and a Connector installed.
In addition, there must be a unique Connector instance for each installation you need to
access through the Job Scheduling Console.
26 Version 8.1
4. Installing Scheduler
Note: Each Connector instance name must be unique within your scheduler network.
Connector
Installing the Connector
Installation comprises the following:
1. Installing Job Scheduling Services (see “Installing Tivoli Job Scheduling Services” on
page 13). Skip this step if you have already done this.
Note: Job Scheduling Services must be installed before the Connector, and must be
installed on the Tivoli server.
2. Installing the Connector on the Tivoli server.
3. Creating the Connector instance. There must be one instance for every Workload
Scheduler engine you want to access through the Job Scheduling Console. The
Connector instance name must be unique within the scheduler network.
You can install the Connector either from the Tivoli desktop or from the command line.
Note: Ensure that you have already installed Job Scheduling Services. If you have not yet
done so, see “Installing Tivoli Job Scheduling Services” on page 13.
If you want to re-install the Connector, you must uninstall the existing one before you do.
See “Uninstalling the Connector” on page 31.
Where to Install
Install the Connector on the Tivoli server and on the managed node where the scheduler
master is installed.
You can also install the connector on a fault-tolerant agent, if you want to access local data
on the fault-tolerant agent from the Job Scheduling Console.
Setting the Tivoli Environment
To install the Connector, you must first set the Tivoli environment. To do this, log in as root
or administrator, then enter one of the following commands:
Table 8. Setting the Tivoli Environment
For this operating system ... Enter this command ...
AIX, Solaris, HP-UX, Linux ./etc/Tivoli/setup_env.sh
Microsoft Windows, UNIX shell .c:/windir/system32/drivers/etc/Tivoli/setup_env.sh
Microsoft Windows, DOS shell c:\windir\system32\drivers\etc\Tivoli\setup_env.cmd
Note: If you decide not to create the instance at this time, you can create it later by
using the wtwsconn utility from the command line (see “Creating Connector
Instances” on page 29). Creating the Connector instance later is
recommended when installing the Connector on multiple nodes, because you
can perform the installation simultaneously on all the nodes while creating
the instance locally using wtwsconn.
8. To install the Connector without creating a Connector instance, leave the Create
Instance checkbox clear and leave the General Installation Options fields blank.
These fields are used only during the creation of the Connector Instance.
9. To install the Connector and create a Connector Instance:
a. Select the Create Instance checkbox.
b. In the TWS directory field, specify the directory where Workload Scheduler is
installed.
c. In the TWS instance name field, specify a name for the Workload Scheduler
instance on the managed node. This name must be unique in the network.
10. Click Set to close the Install Options window and return to the Install Product window.
11. In the Available Clients list, select the nodes to install on and move them to the
Clients to Install On list.
You must install the Connector on at least the Tivoli management server. You can install
the Connector only on managed nodes on which Job Scheduling Services is installed.
Note: If you choose to create a Connector instance during the installation, you must
select only one node from the list, because the instance name must be unique
within the Workload Scheduler Network.
12. In the Install Product window, click Install. The Product Install window is displayed,
which shows you the progress of the installation.
13. Click Continue Install to continue the installation or click Cancel to cancel the
installation.
14. The installation program copies the files and configures the Tivoli database with the
new classes. When the installation is complete, the message Finished product
installation appears. Click Close.
Installing from the Command Line
To install the Connector from the command line, ensure you have set the Tivoli environment
(see “Setting the Tivoli Environment” on page 27), then enter one of the following
commands:
¶ To install on all managed nodes:
28 Version 8.1
4. Installing Scheduler
winstall -c install_dir -i TWS_CONN twsdir=/users/maestro iname= instance_name
Connector
owner=maestro
¶ To install on only one managed node:
winstall -c install_dir -i twsdir=/users/maestro iname=instance_name
owner=maestro createinst=1 node
where:
install_dir
is the path containing the Job Scheduling Services installation program.
instance_name
is the name of the instance that appears in the Job Scheduling view.
maestro
is the owner name.
node
is the name of the destination managed node.
You must install the Connector on at least the Tivoli management server. You can create
instances only on managed nodes where the Connector is installed.
Enter the following command on the Tivoli server or managed node where you installed the
Connector that you need to access through the Job Scheduling Console:
where:
node
specifies the node where the instance is created. If not specified, it defaults to the node
where the script file is run.
instance_name
is the name of the new instance. This name identifies the engine node in the Job
Scheduling tree of the Job Scheduling Console. The name must be unique within the
scheduler network.
TWS_directory
specifies the value for the TWSdir attribute. This is the Workload Scheduler installation
directory on the specified node.
Authorization Roles Required for Instances
To manage Connector instances from a Tivoli server or managed node, you must be a Tivoli
administrator with one or more of the following roles:
Note: To control access to the scheduler, the TCP/IP server associates each Tivoli
administrator to a Remote Access Control Facility (RACF) user. For this reason, a
Tivoli administrator should be defined for every RACF user. For additional
information, refer to the Tivoli Workload Scheduler for z/OS: Customization and
Tuning book.
Managing Connector Instances
Use the wtwsconn utility to create, remove, and manage connector instances. This program
is downloaded when you install the Connector.
Note: Before you use wtwsconn, you must set the Tivoli environment. See “Setting the
Tivoli Environment” on page 27.
The following table describes how to use wtwsconn in the command line to manage
Connector instances.
where:
node
specifies the node where instance is created. If not specified, it defaults to the node
where the script is run from.
instance
is the name of the new instance. This name identifies the engine node in the Job
Scheduling tree of the Job Scheduling Console. The name must be unique within the
scheduler network.
30 Version 8.1
4. Installing Scheduler
twsdir
Connector
specifies the value for the scheduler dir attribute. This is the Workload Scheduler
installation directory in node.
then enter:
where:
node
is the name of the system from which you want to remove the Connector.
This stops all Connector processes, then removes Connector classes and installation files.
Installing Patches
To install patches, ensure you have set the Tivoli environment (see “Setting the Tivoli
Environment” on page 27), then:
1. Open the Tivoli Desktop.
2. From the Desktop menu select Install, then Install Patch. The Install Patch window is
displayed.
3. Follow the instructions presented online.
The number before the first period (.) is the region number and the
second number is the managed node ID (1 is the Tivoli server). In
a multi-Tivoli environment, you can determine where a particular
instance is installed by looking at this number because all Tivoli
regions have a unique ID.
wuninst -list Lists all the products that can be uninstalled.
wuninst {ProductName} -list Lists the managed nodes where a product is installed.
wmaeutil Maestro -Version * Lists the versions of the installed engine, database, and plan.
wmaeutil Maestro -dbinfo * Lists information about the database and the plan.
wmaeutil Maestro -gethome Lists the installation directory of the Connector.
32 Version 8.1
5
Installing the Tivoli Job Scheduling
Scheduling Console
This chapter describes how to install the Tivoli Job Scheduling Console on each of the
following operating systems:
Table 11. Job Scheduling Console Supported Platforms
To install on this operating system ... Go to page ...
Microsoft Windows (see “Supported Platforms” on page 34) 35
AIX, HP-UX 36
Sun Solaris, Linux 38
Before Installing
Read this information before you install the Job Scheduling Console.
System Requirements
The Job Scheduling Console has the following system requirements:
Software
¶ Tivoli Workload Scheduler for z/OS Connector Version 1.2
¶ Tivoli Workload Scheduler for z/OS Version 8.1 or OPC 2.1 or later
¶ Tivoli Job Scheduling Services 1.2
¶ TCP/IP network communication
¶ Java Runtime Environment Version 1.3
Hardware
¶ CD-ROM drive for installation
¶ 70 MB disk space for full installation, or 34 MB for customized (English base) installation
plus approximately 4 MB for each additional language
Software
¶ Tivoli Workload Scheduler Connector
¶ Tivoli Workload Scheduler Version 7.0 or 8.1
¶ Tivoli Job Scheduling Services 1.2
¶ TCP/IP network communication
¶ Java Runtime Environment Version 1.3
Hardware
¶ CD-ROM drive for installation
¶ 70 MB disk space for full installation, or 34 MB for customized (English base) installation
plus approximately 4 MB for each additional language
Supported Platforms
The Job Scheduling Console is supported on the following platforms:
¶ Microsoft Windows:
NT 4.0 with Service Pack 5 or Service Pack 6a
Professional, Server, and Advanced Server 2000 with Service Pack 1 and Service
Pack 2
98
Millennium Edition
¶ IBM AIX 4.3.3, 4.3.3s, 5.1
¶ HP-UX PA-RISC 11.0, 11i
¶ Sun Solaris 2.7, 2.8
¶ Linux Red Hat 7.1
34 Version 8.1
Installing on Microsoft Windows
To install the Job Scheduling Console on Microsoft Windows:
1. Insert the Tivoli Job Scheduling Console CD-ROM into the CD-ROM drive.
2. Click Start and select Run.
3. In the Open field, enter:
drv:\Install
where:
Scheduling Console
is the name of the CD-ROM drive.
The Job Scheduling Console splash window is displayed.
4. Click the down arrow in the language field. This displays a drop-down list containing
all the available languages in which you can perform installation.
5. Select your language and click OK. The Introduction window is displayed.
This window leads you through the installation process, displaying a series of option
windows that enable you to provide the necessary information. You can use the
Previous, Next, or Exit buttons, when enabled, to move through these windows.
6. Click Next. The Choose Install Folder window is displayed.
7. Enter the path where you want to install the Job Scheduling Console. If you need to,
edit the default location provided in the field, or select Choose to open the Select a
folder window where you can specify another location.
8. Click Next. The Choose Shortcut Location window is displayed.
9. Click one of the available radio buttons to specify where the Job Scheduling Console
buttons are to be placed.
10. Click Next. The Choose Install Set window is displayed.
11. If you want to install the Job Scheduling Console in all available languages (Full
Package), click Install. A progress information window is displayed. Go to Step 13.
If you want to select the languages installed with the Job Scheduling Console
(Customized Install), click Customize. The Customize Install window is displayed.
Continue with Step 12.
12. Select in which languages, besides English, you want to install the Job Scheduling
Console. Click Install.
Notes:
a. The Job Scheduling Console displays in your selected language only if the language
matches the regional settings of your computer. If it does not, English is the default.
b. The Job Scheduling Console automatically adjusts to the country, language and time
zone settings of your system.
36 Version 8.1
To do this:
1. Go to the /bin/java subdirectory of the directory where you installed the Job
Scheduling Console.
2. Open AIXconsole.sh in editing mode.
3. Find the following statement:
JAVAPATH=%ENTRY%
Scheduling Console
38 Version 8.1
Starting the Job Scheduling Console
1. Depending on your platform, start the Job Scheduling Console in one of the following
ways:
Table 12. Starting the Job Scheduling Console
On this platform ... In the ..\bin\java subdirectory of the installation path ...
Microsoft Windows NT, 2000 Enter NTconsole
Microsoft Windows 98, ME Enter console
Scheduling Console
Console button on the Windows Desktop or by selecting the corresponding item from the Start
menu.
AIX Enter ./AIXconsole.sh
SUN Solaris Enter ./SUNconsole.sh
HP-UX Enter ./HPconsole.sh
Linux Enter ./LINUXconsole.sh
40 Version 8.1
6
Working with the Job Scheduling Console
The Job Scheduling View
The Job Scheduling view is the main window of the Job Scheduling Console.
The view consists of two panes. The left pane is a tree view that displays your scheduler
engines (Workload Scheduler, Workload Scheduler for z/OS, or other). If you expand any of
the objects that represent the scheduler engines, you see the lists and groups of lists
available for that particular engine.
The right-hand pane displays a detailed view of the object selected in the tree. This can be
either a number of list objects or the contents of a list in the shape of a table or a Gantt
chart.
The upper part of the Job Scheduling view contains the menu bar and a number of buttons.
You can use the buttons to:
¶ Size the panes
¶ Browse scheduler general properties and set defaults for refreshing list contents
¶ Remove an object from the tree
¶ Create objects in the sheduler database
¶ Create lists of objects in the database and in the plan
¶ Create groups of lists
As an alternative to using the buttons, you can right-click your intended engine to open a
pop-up menu displaying the same options for creating lists, groups of lists, and objects in
the database.
Stop loading a list. This button is active while the results of a list are
being uploaded.
Refresh the results of a list. This button becomes available only after you
have opened a list. Click the button to reload the results of the list on
display in the right-hand pane of the Job Scheduling view.
Create a job stream in the database. Displays the Job Stream Editor
window, where you define job stream properties and create jobs, job
dependencies, and run cycles.
Create a job in the database. Opens the Properties - Job Definition
window.
Lists jobs defined in the database. Displays the Properties - Job List
window, where you create a filtered list of selected jobs.
42 Version 8.1
Table 13. Job Scheduling View Buttons (continued)
Use this button ... To do this ...
List job instances in the plan. Displays the Properties - Job Instance List
window, where you create a filtered list of selected jobs scheduled in the
plan.
List workstations in the plan. Displays the Properties - Plan Workstation
List window, where you create a filtered list of selected workstations
allocated to the plan.
List resources in the plan. Displays the Properties - Plan Resource List
window, where you create a filtered list of selected resources allocated to
the plan.
Create a group of lists. Displays the Properties - Group of Lists window,
where you enter a name for the new group. The group is added to the
tree of your selected scheduler and you can thereafter create lists as part
of it.
Note: Remember to select your intended engine in the tree before you use an button to
create or to list an object. By default, the Job Scheduling Console selects the first
engine in the list.
Lists and list groups are displayed both in the tree view and in the right-hand pane of the
Job Scheduling view. The right-hand pane displays all lists and list groups available for the
selected engine. In the right-hand pane, you can only double-click a list to display its results.
In the tree view, double-click an engine to display the lists available for the engine.
Right-click one of the lists to open a pop-up menu that displays the following options:
Table 14. Object List Properties
Select this option ... To do this ...
Properties Open the list properties window. Choose this option to change the
list name, refresh options, or filter criteria.
Delete Delete the list from the tree.
Open Run the list and display the results in the right-hand pane of the
Job Scheduling view.
Detach View Take the results of a list from the Job Scheduling view and places
them in a separate window.
Default Lists
The console provides default lists for every scheduler engine in your installation. There is a
default list for each type of scheduler object. Default lists are general; that is, no selection
You can edit the properties of each default list to add more restrictive selection criteria or to
change its name or refresh options.
You can edit the properties of each default list to add more restrictive selection criteria or to
change its name or refresh options.
Creating a List
To create a list:
1. Select an engine in the tree.
2. Click one of the buttons displayed in the Job Scheduling view. The Properties - Database
Resource List window is displayed.
44 Version 8.1
Figure 2. Properties - Database Resource List Window
3. In the Name field, enter a name for the list. You can use the same name for more than
one list. Different lists maintain their individual properties even if they have the same
Scheduling Console
4. Specify refresh options for the list. This is optional. If a default periodic refresh period is
already specified in the Properties - Scheduler window, this value is automatically
displayed for each new list. You can change or deselect the default. See “Specifying
Defaults for Lists”.
5. Enter or select filtering criteria from those displayed in the window. You can use
combinations of more parameters. The more filters you use, the more restricted is the
search. To generalize your search, use wildcard characters. If you leave all fields blank,
all objects are displayed when you open the list.
For lists of resources only, you can specify if you want the special characters in the
search items to be treated as wildcards, real letters, prefixes, or suffixes.
First you must create a group, then you can create the lists that comprise it. To create a
group of lists:
1. Select an engine in the tree.
2. Click the Create a Group of Lists button or right-click on the engine button and select
Create Group from the pop-up menu.
To create a group in an existing group, select the group and click Create a Group of
Lists on the toolbar or right-click the existing group button and select Create Group
from the pop-up menu.
3. Enter a name for the group. You can use the same name for more than one group.
Different groups maintain their individual properties even if they have the same name.
After creating a group, you can create its member lists and subgroups. Right-click the group
to display a pop-up menu with the following options:
Table 17. Properties List Options
Select this option ... To do this ...
Properties Change the group name.
Delete Delete the group and all its contents.
Create Database List Create a new list of job stream, resource, or workstation
definitions in the database.
46 Version 8.1
Table 17. Properties List Options (continued)
Select this option ... To do this ...
Create Plan List Create a new list of job streams, jobs, resources, or
workstations in the plan.
Create Group Create a subgroup of more lists.
Displaying a List
To display a list:
1. In the tree of the Job Scheduling view, double-click an engine.
2. Right-click the list you want to run and select Load List from the pop-up menu. The list
tool searches the database or plan and displays the objects it finds in the right-hand pane
of the Job Scheduling view.
Note: Alternatively, you can select an engine in the tree and, in the right-hand pane,
double-click the list you want to run.
You can display several lists in sequence. The newest list is displayed above the preceding
ones. However, as long as a list is kept open, it is maintained and refreshed according to the
refresh options specified. To view the list, click the corresponding object in the Job
Scheduling view.
Detaching a List Display
Detaching a list frees the right-pane of the Job Scheduling Console to display other objects.
You can detach multiple lists to view several objects simultaneously.
Finding Objects
A contextual find tool in the Job Scheduling Console helps you to find the name of a
resource, workstation, job, or job stream when you need to provide one. The find tool is
available when you can see an ellipsis (...) next to the field where you are asked to enter the
name. An example is shown in the Properties - Workstation in Database window, shown in
the next figure, in which the Find tool ellipsis is identified by the cursor arrow.
48 Version 8.1
6. Working with the Job
Scheduling Console
Figure 5. Properties - Workstation in Database Window
2. Enter your search criteria. You can do one or more of the following:
¶ Enter a name in the Find field. You can generalize your search by using wildcards
or leave the field blank to use no filters.
¶ Select one or more check boxes when available.
50 Version 8.1
II — Using the Job Scheduling Console
with Tivoli Workload Scheduler for
z/OS
Chapter 7. Managing Workstations in the Database . . . . . . . . . . . . . . . . . . . . . 55
Creating a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
General Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Defining Open Time Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Managing Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Default Workstation Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Creating a List of Workstations in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Using Workstation Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Displaying a List of Workstations in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Modifying Workstation Properties in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Deleting a Workstation from the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Creating Workstations from Existing Ones in the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
52 Version 8.1
Rescheduling the Deadline Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Deleting a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Setting a Job Stream Instance to Complete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Setting a Job Stream Instance to Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Rerunning a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Additional Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
54 Version 8.1
7. Managing Workstations
in the Database
7
Managing Workstations in the Database
The Tivoli Workload Scheduler for z/OS environment is defined in terms of resources and
workstations. A workstation describes how jobs have to be run. A workstation is not
necessarily hardware. It is a stage in the processing that is controlled by the scheduler.
To schedule a job instance, you must define a workstation beforehand. Before the scheduler
can start a job instance, the workstation on which the job instance is defined must be
available. So, by controlling workstation availability, you control the running of job
instances that are defined on the workstation.
The scheduler establishes the availability of a workstation by using the open intervals in the
list of available workstations in the database. These are the times when workstation
resources and parallel servers are available to process work. Parallel servers and resources
are usually necessary to run work at the workstation.
Workstations are usually created to represent specific elements in your system configuration.
The availability of these workstations should reflect the availability of those elements in the
real world. For instance, a computer workstation might be created for each z/OS system in a
scheduler complex. So, the availability of the computer workstation should reflect the
availability of the z/OS system it represents. This prevents the scheduler from submitting
work to a z/OS system that is not physically available. Also, the accuracy of any planning
predictions that the scheduler produces for you depends on how accurately you have
described the installation to the scheduler.
This chapter describes how to use the Job Scheduling Console to define and administer the
availability of workstations. For a full description of workstations, refer to the Tivoli
Workload Scheduler for z/OS Planning and Scheduling the Workload book.
In the Job Scheduling view, select the engine in whose database you want to work, then
click the New Workstation button in the toolbar. The new workstation will be defined in
the database of that engine.
General Page
When you click the New Workstation button, the Properties - Workstation in Database
General page is displayed. This is where you enter general information for the workstation.
56 Version 8.1
7. Managing Workstations
in the Database
Use the information in Table 18 to enter all the information required to create the
workstation.
Table 18. Properties - Workstation in Database General Information
In this area ... Enter this information ...
Name Required. Specify a name for the new workstation.
Description Enter a description of the workstation.
Workstation type Select one of the following:
General for preparation of jobs and for control of
operations that are normally not controlled
automatically.
Computer for running of jobs and started tasks.
Printer for printing.
Reporting attribute Select one of the following mechanisms for reporting status
updates on the jobs defined on the workstation:
Automatic if the status change of jobs is reported
automatically, in response to event records
created by Tivoli Workload Scheduler for z/OS.
Typically, you should use this reporting
attribute for computer and print workstations, or
for workstations that specify a user-defined
destination.
Manual start and completion
if the status change of jobs is reported either
from the Ready List ISPF panes on the host or
from the results of a workstation status list (see
“Using Workstation Lists” on page 67 for
details). Typically, you should use this reporting
attribute for general workstations that are used
for job preparation, or for other general
workstations if the duration of the task needs to
be tracked.
Completion only
if the status change of jobs is reported either
from the Ready List ISPF panes on the host or
from the results of a workstation status list (see
“Using Workstation Lists” on page 67 for
details). Typically, you should use this reporting
attribute for general workstations that are not
used for job preparation.
Non reporting if jobs on this workstation are set to complete
as soon as they become eligible to be started.
Typically, you should use this reporting
attribute for dummy jobs created to simplify the
sequencing of other jobs.
Printout routing Enter the ddname of the daily printout data set where reports for
this workstation are to be written.
58 Version 8.1
7. Managing Workstations
in the Database
Table 18. Properties - Workstation in Database General Information (continued)
In this area ... Enter this information ...
Fault Tolerant Select this to define the workstation as fault-tolerant. Use
fault-tolerant workstations to run Tivoli Workload Scheduler jobs
in a Tivoli Workload Scheduler for z/OS plan. Fault-tolerant
workstations are automatically defined as computer workstation
types with an automatic reporting attribute. When you select this
box, all the properties for this workstation are disabled and set to
their default value.
Destination Enter a destination that corresponds to the destination specified
on a ROUTOPTS initialization statement. For computer
workstations and WTO general workstations this is the name of
the Tivoli Workload Scheduler for z/OS tracker. The default
destination is the system where the Tivoli Workload Scheduler
for z/OS engine is started.
Defaults
Transport time Enter the time, in hours:minutes (HH:MM)
format, that the system should allow between
the end of a predecessor job and the beginning
of the present job. The transport time of the
workstation is the default transport time for all
the jobs defined on the workstation and is used
for planning purposes only.
Duration Enter the default estimated processing time, in
HH:MM:SS format, for all jobs on that
workstation. Tivoli Workload Scheduler for
z/OS uses the estimated processing time, when
creating the plan, to work out a timetable for
all jobs. You do not need to give an exact
figure, because Tivoli Workload Scheduler for
z/OS can adjust this figure dynamically from its
experience of the actual durations, however you
should attempt to estimate as close as possible.
You can override this value by specifying a
duration when you create a new job.
Access Methods Enter details of any optional access methods that enable the
workstation to submit and track jobs that are run by an external
product.
Note: This option applies only to workstations running on OPC
2.2 or later.
Name Enter the name of the access method that
handles the external product.
Node address Write the optional TCP/IP address or hostname
of the tracker agent that is hosting the access
method.
Port number Enter the optional TCP/IP port number of the
tracker agent that is hosting the access method.
You can define a maximum of two workstations, or fixed resources, called Resource 1 (R1)
and Resource 2 (R2), to schedule or run jobs on this workstation.
When defined, the two resources are associated to the workstation and are recognized
automatically when you schedule and run jobs on the workstation. However, they are subject
to the following limitations, that in some instances could make it more practical to use
logical resources in their place:
¶ You can have a quantity of no more than 99 of each resource.
¶ They cannot be shared by other workstations.
¶ Their name is limited to two characters.
R1 and R2 can represent any physical resource in your system that is significant for
scheduling purposes. When you create a new job, you can specify how many of the
workstation resources (R1, R2, or both) the job will use. Unless the specified quantity of
resources is available, the job will not start.
60 Version 8.1
7. Managing Workstations
in the Database
To define the use of each resource:
1. Enter a 2-character name in Name if you want to change its name from the R1 or R2
default.
2. Select the Used for planning check box, if you want this resource to be considered
when a plan involving this workstation is built.
3. Select the Used for control check box, if you want this resource to be used when a job
runs on this workstation.
The plan contains the best estimation of when operations will start. If something
unexpected happens (for example, a job exceeds its expected run time), Tivoli Workload
Scheduler for z/OS may need to reassess the start time of some of its operations. At this
point, the Control option becomes important. If you selected it, Tivoli Workload
Scheduler for z/OS considers the workstation resource when rescheduling its operations.
Otherwise, the workstation resource is ignored.
Select Open Time Intervals in the left pane. The Open Time Intervals page is displayed.
62 Version 8.1
7. Managing Workstations
in the Database
Use the information in Table 19 to complete all the necessary fields in the window.
Table 19. Properties - Workstation in Database Open Time Intervals Information
In this column ... Do this ...
Day menu Choose: a day of the week, Standard, or Specific Date (where a
calendar pops up from which you select a date). The Standard
interval defines the values that are true at all times, with the exception
of the additional intervals that you also specify on this page. When
you define a new workstation, you find a default Standard row where
you enter the name of an alternate workstation and the quantities of
parallel servers and of workstation resources that you want to be
available on a general basis. Select a day or Specific Date to specify
the time intervals where the quantities, name, or both are different
from Standard.
Status menu Specify the availability status of the workstation in the given interval.
Select one of the following:
Defined
To specify that during the interval the workstation is available in
the quantities and with the properties defined in the current row.
Closed
To specify that the workstation is not available during the
interval. If you select this value, the remaining cells in the row
are disabled.
From Time and To Time A time range, with times in the 12-hour format.
Parallel Servers The quantity, to a maximum of 99, of parallel servers available to the
workstation during the time interval. Leave this field blank if you did
not specify usage of parallel servers in the General page.
R1 Capacity and R2 The available quantities, to a maximum of 99 each for every interval,
Capacity of resources R1 and R2 if you specified their use for this workstation
in the Resources page.
Alternate Workstation The name of another workstation of the same type that can be used
during the interval if this workstation becomes unavailable. This
option is possible only for computer workstations and for WTO
general workstations.
Note: For best results, make the configurations of the two
workstations symmetrical, so that the two workstations can be
alternates for each other.
The following sections explain how to create database and plan workstation lists. They also
explain how to use database workstation lists to update definitions in the Workload
Scheduler for z/OS database. “Managing Workstations in the Plan” on page 161 provides
information on how to use plan workstation lists to modify the allocation of workstations in
the plan.
Default Workstation Lists
The Job Scheduling Console provides two workstation lists. You can find them in the default
lists groups in the tree of each Workload Scheduler for z/OS engine shown in the Job
Scheduling view.
Table 21. Default Workstation Lists
Use this list ... To do this ...
All Workstations Display a list of all the workstations defined in the workstation
definition database. Resides in the Default Database Lists group.
Status of All Workstations Display a list of all the workstations currently allocated to the plan.
Resides in the Default Plan Lists group.
The default workstation lists have the same behavior as the user lists. You can display their
properties and see from the empty fields that no selection criteria are specified. You can
modify their properties and make them less general by adding the filters of your choice.
64 Version 8.1
7. Managing Workstations
in the Database
Creating a List of Workstations in the Database
A workstation list produces a filtered list of workstations defined in the Workload Scheduler
for z/OS workstation description database.
To create a database workstation list, in the Job Scheduling view, select an engine and click
the List Workstations in Database button.
66 Version 8.1
7. Managing Workstations
in the Database
Using Workstation Lists
When you open a database workstation list object, all the workstations defined in the
database that respond to the filter criteria are displayed in the right-hand pane of the Job
Scheduling Console.
To work with workstations allocated to the plan, you must use a plan workstation list. For
further information, see “Browsing and Modifying Workstation Properties” on page 164. To
work with workstations defined in the database, continue with “Displaying a List of
Workstations in the Database”
68 Version 8.1
8
Managing Resources in the Database
8. Managing Resources in
In Workload Scheduler for z/OS, resources represent the physical or logical objects that are
the Database
used by jobs. You can use resources to prioritize access to a data set or to limit the number
of simultaneous file transfers on a particular network link.
You specify how a job uses resources when you create the job. But first you must:
¶ Create the resource and its attributes
¶ Specify the associated workstations
¶ Specify the number of resources available in each interval
The Properties - Resource in Database window is displayed. This window contains the
Resource, Default Workstations, and Availability Intervals pages. On the first two pages, you
enter the default information for the new resource. These values are valid at all times, except
for the periods that you optionally define on the Availability Intervals page.
Resource Page
In this Properties - Resource in Database Resource page, you enter information that
describes the resource you are creating.
70 Version 8.1
Use the information in Table 23 to enter all the information needed to create the resource.
Table 23. Create a Resource Information
In this area ... Do this ...
Name Specify a name identifying the resource. The name is converted to
uppercase.
Description Provide a description of the resource.
Default The quantity of the resource (from 1 to 999999) in Quantity. Specify
the number of the resource that is available (when you select the Is
8. Managing Resources in
Available box) for the availability intervals associated with the
resource. This information is used as the default unless otherwise
specified for a given interval on the Availability Intervals page.
the Database
Group ID A name of up to eight characters that identifies a group to which the
resource belongs. The group ID can be used as a list filter for selecting
subsets of resources.
Hiperbatch Select to specify whether the resource is a data set eligible for
Hiperbatch™. Hiperbatch is a host performance enhancement that
works with the Data Lookaside Facility (DLF) to enable batch jobs and
started tasks to share access to data sets.
Used for Select from the drop-down list how the resource is to be used, for:
¶ Planning
¶ Control
¶ Planning and control
¶ Neither planning nor control
On error Select from the drop-down list box what action to take on the resource
when a job that allocates this resource ends in error (and does not have
an overriding keep-on-error specification in the job definition):
Free
Free the full allocation of this resource, both exclusive and shared.
Keep
Keep the full allocation of this resource. You may want critical
jobs to keep their resources even when they fail, to avoid having
to wait for resources when the job is restarted.
Free if exclusive
Free the full exclusive allocation of this resource.
Free if shared
Free the full shared allocation of this resource.
Assume System Default
Use the default specified in the ONERROR keyword of the
RESOPTS statement. Refer to the Customization and Tuning
manual.
Select Default Workstations in the left pane. The Properties - Resource in Database Default
Workstations page is displayed.
1. To add all the workstations defined in Workload Scheduler for z/OS, click the Add All
Workstations button in the toolbar. An asterisk (*) is added to the list of connected
workstations.
Note: By default, all workstations are already added when the Resource Editor window
for a new resource opens.
2. To remove a workstation from the list, select it, then click the Remove Row button.
3. The Find tool allows you to pick from a list of available workstations. Click the Find
Workstation button. The Find Workstation window is displayed.
4. Several filtering items are available to search for connected workstations. Either enter a
name directly in the Workstation field or select one or more boxes in the Reporting
Attributes and Types groups.
5. Click Start.
6. When the search results are displayed, select a workstation and click Add to add it to the
Default Workstations list.
Select Availability Intervals in the left pane. The Properties - Resource in Database
Availability Intervals page is displayed.
72 Version 8.1
Availability Intervals Page
On this page, you define the time intervals when the resource can be used with either the
Quantity, Availability, and Connected Workstations values in the Resource and Default
Workstations pages, or with other values that you specify for each different interval.
8. Managing Resources in
the Database
Figure 13. Properties - Resource in Database Availability Intervals Window
To add or delete an availability interval, click the Add Row or Remove Row buttons, then
select the specific interval. After you have added a row, you can define the new interval.
Use the information in Table 24 to enter the information to define the availability interval.
Table 24. Define an Availability Interval Information
In this column ... Do this ...
Day menu Choose: a day of the week, Standard, or Specific Date.
The Standard interval represents the norm where the resource is used
with the values you entered in the other two pages. When you define a
new resource, you find a default Standard row where you need not add
any values except, optionally, for a time range.
Managing Resources
Once you have created resources, create one or more resource lists to manage them. From a
resource list you can:
¶ View the characteristics and status of resources
¶ Modify resource properties
¶ Delete resources
The following sections explain how to create database and plan resource lists. They also
explain how to use database resource lists to update definitions in the database. “Managing
Resources in the Plan” on page 173 provides information on how to use plan resource lists
to modify resource allocation in the plan.
Default Resource Lists
The Job Scheduling Console provides two resource lists. You can find them in the default
lists groups in the tree of each engine displayed in the Job Scheduling view.
Table 26. Default Resource Lists
Use this type of list ... To do this ...
All Resources Display a list of all the resources defined in the resource definition
database. Resides in the Default Database Lists group.
Status of all Resources Display a list of all the resources currently allocated to the plan.
Resides in the Plan Lists group.
Default resource lists have the same behavior as user-defined lists. You can display their
properties and see from the empty fields that no selection criteria are specified. You can
modify their properties and make them less general by adding the filters of your choice.
Listing Resources in the Database
A database resource list shows a filtered list of resources defined in the Workload Scheduler
for z/OS resource description database.
To make a database resource list, select an engine in the Job Scheduling view, then click the
List Resources in Database button. The Properties - Database Resource List window is
displayed.
74 Version 8.1
8. Managing Resources in
the Database
Figure 14. The Properties - Database Resource List Window
Use the information in Table 27 to enter all the information needed to create the list.
Table 27. Database Resource List Information
In this area ... Do this ...
Name Enter a name to identify the query.
Periodic Refresh Options To refresh the list results automatically, select the Periodic Refresh
check box and specify a refresh interval in seconds. Alternatively,
click Apply Defaults to use the defaults specified in the scheduler
Properties window available in the Job Scheduling view.
Filter Criteria Specify search parameters or combinations of parameters.
The following sections explain how to use database resource lists to work with resources
defined in the resource description database. From the display produced by opening a
database resource list, you can:
¶ Browse and modify the properties of resources defined in the database
¶ Delete resource definitions from the database
¶ Define new resources starting from existing definitions
To work with resources allocated to the plan, you must use a plan resource list. For
information about how to work with plan resources, see “Browsing and Modifying
Resources” on page 176.
76 Version 8.1
Modifying Resource Properties in the Database
To modify the properties of a resource displayed in a list:
1. In the Job Scheduling view, right-click the resource and select Properties from the
pop-up menu.
The Properties - Resource in Database window is displayed.
8. Managing Resources in
the Database
Figure 16. The Properties - Resource in Database Window
2. Make your changes to the resource properties. For a description of the fields in this
window, see “Creating Resources” on page 70.
3. Click OK to save your changes to the resource definition.
You determine the type when you specify the job stream properties.
Use the information in Table 29 to enter all the information needed for this window.
Table 29. Properties - Job Stream Window Information
In this area ... Do this ...
Name Enter a name for the job stream or template.
Note: The name, valid date, and status uniquely identify each job stream
or template. You can define up to four job streams and job stream
templates that share the same name but have different valid dates.
Description Enter a description for the job stream or template.
Is a template Select this check box to define a new job stream template. A job stream
template contains run cycles but no jobs. All job streams defined as
belonging to a template inherit the run cycles defined for the template.
Inherits from template Enter the name of the template if you are defining a job stream that
belongs to a job stream template. The job stream is scheduled using the
template run cycle information.
Active Select this check box to schedule the job stream. If you are creating a
complex job stream that requires time to define, do not select this check
box until you have added all jobs, specified dependencies, and created a
run cycle. This avoids the risk that the incomplete job stream will be
included in any plans. You can make the job stream active after you have
completed it.
Valid Date Specify the time period covered by the job stream. You can specify only
the From date. A To date of 12/31/2071 is automatically assigned by
Workload Scheduler for z/OS. To change the From value, click the small
calendar button to select a valid From date. You can create several job
streams with the same name but with different dates in the From field.
The scheduler picks the correct version for the day it is planning.
80 Version 8.1
Table 29. Properties - Job Stream Window Information (continued)
In this area ... Do this ...
Priority Specify how the job stream ranks in importance compared to other jobs
streams. The lowest priority is 1 and the highest priority is 9. This means
that, when job streams are competing for resources, a job stream with a
priority of 3 will run before a job stream with a priority of 1. This value
is not definitive. Other factors, such as resource and workstation
dependency, are considered in determining priority. This field does not
apply to job stream templates.
Authority group name Enter a name to be used to generate a RACF resource name for authority
checking. This information is optional.
Calendar Specify the name of the calendar of workdays and freedays, including
holidays, that you associate to the job stream. If you need to, click the
ellipsis (...) to open a Find window (see “Finding Objects” on page 48).
If you leave this field blank, the scheduler uses the calendar specified in
the initialization parameter CALENDAR during startup of the TCP/IP
server.
Note: The calendar that you specify here is used to display the run days
of the job stream in the Run Cycle view of the Job Stream Editor. It is
not necessarily the calendar that is used to determine the actual run days
of the job stream instances that are generated.
Note: The Workload Scheduler for z/OS ISPF main panel, option 1.8, allows you to create a
job stream containing a single job by specifying only the name of the JCL associated
with the operation. This option is not available in the Job Scheduling Console. To
create job streams with a single job, you must follow the steps in this chapter.
The Graph view displays an button for each possible type of job that you can define in
Workload Scheduler for z/OS. Table 31 describes these job buttons:
Table 31. Graph View Job Buttons
This button ... Denotes this job type ...
Add JCL JobA job that consists of JCL statements. Runs on computer
workstations.
Add Started Task JobA job to start or stop a task that has already
started. Runs on computer workstations.
Add Printer JobA job to print the output of a predecessor job. Runs on
printer workstations.
Add General JobA job to include activities other than printing and
processing, such as manual activities. Runs on general workstations.
Add Setup JobA job containing a set of JCL statements for a JCL or
started task job. Runs on general workstations.
The property windows for the different job types are identical. However, when you save the
job stream, Workload Scheduler for z/OS applies different validation policies, based on the
job type, to the properties that you specified. Moreover, when you use the Find tool to
search for a target workstation, the tool lists only workstations that are compatible with the
specific job type.
82 Version 8.1
Creating a Job Using Buttons
To create a job in the job stream, click one of the job buttons in the Graph view of the Job
Stream Editor, depending on the type of job that you want to define. For example, the Add
JCL Job button. The Properties - JCL Job window is displayed.
General Page
Use the information in Table 32 to enter all the information needed to define the job details.
Table 32. Properties - JCL Job General Information
In this area ... Do this ...
Identifier Enter the job number. This information is required and must be unique
within the job stream.
Target workstation The name of the workstation on which the job is run. This information
is required. If you do not know the name:
1. Click the ellipsis (...) button. The Find Workstation window is
displayed.
2. In the Find field, enter the name of the workstation or you can use
wildcard characters. You can also run your search by selecting boxes
in the Reporting attributes group box.
3. Click Start. A list of workstations is displayed.
4. Double-click the name of a workstation, or click it once then click
on OK. The name of the workstation is displayed in the Target
workstation field in the Properties - JCL Job General page.
Description A brief description of the job.
Auto submit Select this to start the job automatically or to issue a WTO message
(when all dependencies have been satisfied and all required resources
are available). Auto submit is selected by default.
84 Version 8.1
Table 32. Properties - JCL Job General Information (continued)
In this area ... Do this ...
Restartable Specify whether to restart the job if its workstation becomes inactive:
Yes Restarts the job from the beginning on the alternate workstation (if
one was defined), or on this workstation when it becomes active
again.
No Restarts the job, even if it overrules the installation default in the
WSFAILURE or WSOFFLINE parameters of the JTOPTS
initialization statement.
Default
Uses the installation default action specified in the
OPRESTARTDEFAULT keyword of the JTOPTS statement. This is
selected by default.
Reroutable Specify whether to make the job eligible to be rerouted if its
workstation becomes inactive. This option applies to the job only when
it is in ready (R) or waiting (W) status.
Yes Makes the job reroutable.
No Makes the job not reroutable
Default
Takes the installation default action specified in the
OPRESTARTDEFAULT keyword of the JTOPTS statement. This is
Task Page
In the Task page, enter information about the program associated with the job.
86 Version 8.1
Use the information in Table 33 to enter all the information needed to define the task.
Table 33. Properties - JCL Job Task Information
In this area ... Enter this information ...
Task name The name of the JCL associated with the job, when applicable. Together
with the identifier you specified in the previous page, the task name
labels the job in the Graph view of the Job Stream Editor.
Form number The printer form number that appears on the daily plan and ready lists.
For printer workstations with automatic reporting, it enables the engine
to identify the different print operations that belong to a specific job.
Job class click the drop-down list and select a letter that matches the host job
class from the JCL.
Select Time Restrictions in the left pane. The Time Restrictions page is displayed.
Use the information in Table 34 on page 88 to enter all the information required to define the
time restrictions.
88 Version 8.1
Resources Page
In the Resources page, describe the parallel servers, and the logical and workstation
resources that the job uses.
In the following procedure, you perform the following actions on target resources and
logical resources, which you access from the drop-down list:
Target resources
Where you specify the workstation (or fixed) resources, and the parallel servers, that
the job needs to run.
Logical resources
Where you specify the logical and physical resources that the job needs to run
1. Click the arrow next to Target resources. Columns are displayed where you can specify
the target resoruces.
2. Double-click each cell in the Quantity column to edit the amount of resources Resource
1 and Resource 2 are required by the job. Do the same for parallel servers.
3. Click the arrow again and select Logical resources. Columns are displayed where you
can specify the logical resoruces.
4. Click the Add row button for each resource you need to assign to the job.
5. Type the name of the resource. If you do not know it, use the Find tool (...).
When you have finished, click OK to save your changes and close the window. The new job
is displayed as an button in the Graph view of the Job Stream Editor.
The name of the button is made up of the name of the task with which the job is associated
and by the job identifier. You can drag and drop the button to position it.
Repeat the steps in this section to create as many jobs as you need.
Note: You can use the slider, positioned on the left margin of the Graph view, to zoom in
and zoom out the jobs displayed. When you move the slider downwards to zoom out
of the Graph view, the job buttons change their appearance, changing color depending
on the job type.
Creating a Job Using Copy and Paste
To create a job using the copy and paste functions on an existing job:
1. In the Job Stream Editor, right-click the job you want to copy and select Copy from the
pop-up menu.
2. Right-click the mouse somewhere in the window and select Paste from the pop-up
menu. The Properties - JCL Job window for the copied job is displayed.
3. Change the identifier and edit the properties as required.
4. Click OK to save your changes and close the window. The new job is added in the
Graph view.
90 Version 8.1
Creating Dependencies between Jobs
When you create dependencies, you link jobs in a sequence. A successor job cannot begin
until the predecessor job is complete. Dependencies determine when the successor job runs,
even if the successor job has time restrictions.
For example, to print bank account statements, you must first subtract withdrawals from an
account (Job A) before you calculate the account balance (Job B). Here, Job A is the
predecessor and Job B the successor.
Creating Dependencies within a Job Stream
To create a dependency between jobs within the same job stream:
1. In the Graph view of the Job Stream Editor, click the Add Link button.
2. Click the predecessor job and drag the link to the successor job. A line is displayed
between the two jobs, with an arrow pointing to the successor job.
Figure 24 shows that jobs 04 and 05 can start only when job 03 has finished, and that
job 03 can start only when job 02 has finished.
This section describes one way to add an external job to a job stream. Another method,
based on the use of job stream lists, is described in “Using Copy to Add an External Job” on
page 115.
2. In the Job Stream field, enter the name of the job stream containing the external job. If
you do not know the name of the job stream, see “Finding a Job Stream” on page 94.
3. Click Show Jobs. The jobs in the job stream are displayed.
4. Select a job and click OK. An button for the external job is displayed in the Graph view.
92 Version 8.1
Figure 27. Job Stream Editor — External Job Button
94 Version 8.1
period of 15 days is the third day from the beginning of the period. It is more practical
to use offset-based run cycles when the cycle is based on cyclic periods.
You can specify multiple run cycles when you create a job stream, and you can add new
ones afterwards. You can also mix rule-based and offset-based run cycles.
Both types of run cycles can be either inclusionary or exclusionary. Inclusionary run cycles
specify the days that the job stream must run. Exclusionary run cycles specify the days that
the job stream must not run. You can add run cycles to generate more days, or to have
multiple instances on the same day. You can add exclusionary run cycles to exclude some of
the days already generated.
Creating a Run Cycle
To create a run cycle, in the Job Stream Editor, click the Run Cycle button. The Run Cycle
view is displayed.
Depending on which choice you make, either the Properties - Rule-based Run Cycle window
or the Properties - Offset-based Run Cycle window is displayed.
General Page
The Properties - Rule-based Run Cycle General page is similar to the Properties -
Offset-based Run Cycle General page.
Use the information in Table 37 to specify whether the run cycle is exclusionary, the period
that the run cycle is valid, and how to handle freedays in the schedule.
Table 37. Run Cycle General Information
In this area ... Do this ...
Name Type a name for the run cycle.
Note: Offset-based run cycles take the name of the
period specified in the Offsets page. See “Creating
Offset-based Run Cycles” on page 102.
Description Type a description of the run cycle.
Exclusionary run cycle Select this if the run cycle keeps the job stream from
running.
Valid Date Use the From and To drop-down lists to specify an
interval of time for which the run cycle applies. Click the
calendar buttons next to each field to select dates using
pop-up calendars. The intersection between this valid date
and the valid date you defined in the Job Stream
Properties window is the interval during which the job
stream is actually scheduled.
96 Version 8.1
Table 37. Run Cycle General Information (continued)
In this area ... Do this ...
Rule for freedays Specify how you want Workload Scheduler for z/OS to
treat freedays when calculating the rundays of the job
stream, by selecting one of the following:
Count workdays only
Excludes freedays when calculating on which days
the job stream runs. This is the default for
offset-based run cycles.
Schedule on last workday before freeday
Counts both workdays and freedays. If the runday
falls on a freeday, it is shifted to the closest workday
before the freeday.
Schedule on next workday after freeday
Counts both workdays and freedays. If the runday
falls on a freeday, it is shifted to the closest workday
after the freeday.
Count workdays and freedays alike
Counts both workdays and freedays. The job stream
is scheduled on the runday, regardless whether it is a
freeday or a workday. This is the default for
Select Time Restrictions in the left pane. The Time Restrictions page is displayed.
If you are creating a rule-based run cycle, select Rules in the left pane. The Properties -
Rule-based Run Cycle Rules page is displayed. Continue with “Creating Rule-based Run
Cycles”.
If you are creating an offset-based run cycle, select Offsets in the left pane. Properties -
Offset-based Run Cycle Rules page is displayed. Continue with “Creating Offset-based Run
Cycles” on page 102.
Creating Rule-based Run Cycles
Use the information in Table 39 on page 99 to specify the elements that make up the rules
on which the run cycle is based.
98 Version 8.1
Table 39. Rule-based Run Cycle Rules Information
In this area ... Do this ...
Periods Select Week, Month, Year, or User-defined (a period that you
have defined in the scheduler). You can check more than one
period at a time for complex rules specifying more cycles. For
example, you can check Week and Month, and then choose the
days that apply to both rules. You do not need to select the same
days twice, since they are fitted automatically to all cycles.
Ensure that the period you select is also highlighted so that the
other options in the page are enabled. The period that you select
affects the number of days listed in the Available days
scroll-list. Also, the In the following group changes depending
on the period you select.
Frequency Only
Select this if the rule applies to only one day in the
specified period. The rule does not repeat within the period.
For example, Only last Monday in Month schedules the job
stream to run on the last Monday of the month.
Every
Select this if the rule is used to calculate more than one day
The rundays of an exclusionary run cycle are marked with a red bar in the graphic calendar.
WPREXCEP annuls the WEEKLYPR run cycle in the week marked in red.
Use the information in Table 40 to specify the combination of period and offsets on which
the run cycle is based.
Table 40. Offset-based Run Cycle Rules Information
In this area ... Do this ...
In the following period Type the name of a user-defined period. If you do not know the
name, click the ellipsis to use the Find Period window to find
all the available user-defined periods. For further information,
see “Finding Objects” on page 48.
Note: The name of the period is also used as the run cycle
name.
To open the Timeline view of a job stream, click the Timeline button from the toolbar of
any of the other views of the Job Stream Editor.
The inside of the window has four panes. You can size the panes by dragging the horizontal
and vertical lines that divide the window. The left half of the window, lists the job stream
run cycles in the top pane, and the job stream jobs in the lower pane.
Activity Bars
The right half of the window contains activity bars that represent, on a daily and hourly
scale, the time restrictions defined for every run cycle and job. You can customize the
timescale in the following way:
1. Right-click anywhere along the lower scale. A pop-up menu is displayed.
2. Move your pointer to Timescale to display available choices.
3. Select the radio button that matches your preference.
Table Frame
The table frame is the left half of the window and contains columns that display the
following information:
Note: The run cycle time restrictions inherited from a template are displayed in read-only
Time restrictions for a job are shown by a thick blue bar that represents the time interval
from the start to the deadline of the job, and by a thinner, light blue line that represents the
expected duration. Where the duration of the job exceeds the deadline, the blue bar becomes
red. You can move the interval of time between the start and the deadline times of the job
by dragging either end of the thicker bar (or the whole bar). You can only move the right
end of the thinner bar because the start position is calculated automatically based on the job
dependencies. The job deadline is indicated by a black vertical line. If a job has no specified
deadline, the thick bar is replaced by a vertical stripe indicating the start. You can only move
it forward or backward. To specify a deadline for the job, you have to double-click the job
in the upper left pane and open a Time Restrictions page.
Other Tasks
In the Timeline view you can also:
¶ Detect inconsistencies in time restrictions. Specifically, if the time restrictions of any job
are such that it is not within the time restrictions of a run cycle, a warning icon marks
the run cycle that does not include the job. If you point your mouse on the triangle, a
hover help on the triangle lists the jobs that are not included.
¶ View the earliest start time of the first job and latest deadline time for the last job to see
the total run time of the job stream.
¶ Click a run cycle to see how it affects the jobs that start with the job stream. The
activity bars for jobs that start with the job stream change position when you select
different run cycles.
¶ See which jobs have a specified start time, which jobs follow job stream rules, and
which jobs have no restrictions on start time, by looking at the button at the beginning
of the job activity bar.
The Job Stream Editor checks for any missing or invalid information, then saves the job
stream in the application description database.
Note: You can save a job stream from any of the three views available in the Job Stream
Editor. You can define parts of a job stream, for instance the jobs that are in it, then
save it and open it again later, as explained in the next chapter, to define its run
cycles. Just remember to wait to mark it active when it is ready to be scheduled.
Use Table 41 to complete the information needed to submit the job stream.
Table 41. Submit Job Stream Window
In this area ... Enter this information ...
Job Stream Name The name of the job stream. If you do not remember the name of the
job stream, click the ellipsis (...) to open a Find Job Stream window.
This chapter explains how to list job streams from the Workload Scheduler for z/OS
database and how to use job stream lists. To learn how to list job stream instances, see
“Listing Job Stream and Job Instances” on page 119. To learn how to use job stream instance
lists, see “Managing Job Streams” on page 127.
This list works like any other user list. You can display its properties and see from the
empty fields that no selection criteria are specified. You can modify properties and make
them less general by adding the filters of your choice.
To create a job stream list, select an engine in the Job Scheduling view and click the List
Job Streams button. The Properties - Job Stream List window is displayed.
Use the information in Table 42 to enter the requested information to create the job stream
list.
Table 42. Properties - Job Stream List Information
In this area ... Do this ...
Name Type a name for the job stream list.
Periodic Refresh Options Periodic Refresh
Select this if you want the list results refreshed automatically, then
specify a refresh interval in seconds.
Note: Do not specify frequent refreshes of many detached views
open at the same time in order to prevent from overloading your
system.
—OR—
Apply Defaults
Click this to use the defaults specified in the Scheduler Properties
window available in the Job Scheduling view.
Job Streams
In this area ... Do this ...
Filter Criteria Specify any of the following search parameters, or combinations of two
or more parameters. Use wildcards to help your search.
Job stream
Lists all the job streams with this name or namestring.
Task name
Lists all the job streams where this task or JCL is used.
Job stream template
Lists all the job streams that are part of this template.
Owner
Lists all the job streams that belong to this owner.
Authority group
Lists all the job streams that use this authority group for RACF
authority checking.
Calendar
Lists all the job streams that use this calendar.
Workstation
Lists all job streams containing jobs that run on this workstation.
Is a template
Lists only job streams that are templates.
Exclude template
Lists only job streams that are not templates.
Priority
Lists all the jobs streams that have the priority level you select in
From and To.
Dates
Lists all the job streams valid within the interval you specify in
From and To.
Status of Job Stream
Lists all the currently active or inactive job streams, depending on
which button you select. The default is to ignore this criteria.
Contains Monitored Job
Yes
lists only job streams that contain jobs selected for monitoring
by Tivoli Business Systems Manager.
No
lists only job streams that contain jobs that are not selected for
monitoring by Tivoli Business Systems Manager.
Ignore criteria
lists job streams, regardless of whether they contained jobs
that are monitored by Tivoli Business Systems Manager.
Click OK to save the list. A list object with the name you specified is added to the tree
under the engine you selected at the beginning. Optionally, before saving it, you can run the
list by clicking Apply.
Job Streams
determines which views you can access in the Job Stream Editor:
¶ For job stream templates, you can open the Timeline and Run Cycle views.
¶ For normal job streams you can open the Graph, Timeline, and Run Cycle views.
¶ For job streams that inherit their scheduling information from a template, you can open
the Graph view only. Open the template to see the scheduling information for the job
stream.
Modifying Job Stream Properties
To modify the properties of a job stream in the database:
1. Run a job stream list.
2. Right-click the job stream and select Properties from the pop-up menu.
3. Make the changes you want in the window (see “Specifying Properties for the Job
Stream” on page 80 for details about the Job Stream Properties window).
Modifying a Job
1. In the Graph view of the Job Stream Editor, right-click the job and select Properties
from the pop-up menu.
Note: If any of the job buttons in the Graph view display a superimposed question
mark, this is an indication that the definition of the workstation associated with
the particular job cannot be found in the database. Likewise, if an button label
displays a (Not Found) string, it means that an external job is missing because
the job or the job stream to which it belongs were deleted in the meantime.
2. Apply your changes (for information about how to do this, see “Creating a Job” on
page 82).
3. Click on Save.
Note: If you change your mind, you can use the Undo Delete option in the same pop-up
menu or in the toolbar of the Graph view to put the job back in the job stream.
This option is valid until you save the job stream.
3. Click Save to save the job stream.
Job Streams
click this option ... To do this ...
Copy Create an additional run cycle with the same properties as the
selected one. A Rule-based Run Cycle Properties window or an
Offset-based Run Cycle Properties window opens with the same
definitions as the model run cycle. Modify any definitions you need
to, and enter a new name before saving.
Delete Delete the run cycle from the job stream.
In addition, you can view and modify time restrictions for more than one run cycle and
more than one job in the Timeline view. For a full description of the Timeline view of a job
stream, see “Checking Time Restrictions in the Timeline View” on page 104.
To do this:
1. Run a job stream list.
2. When the list is opened, right-click the job stream you want to delete and select Delete
from the pop-up menu.
3. Click OK in the confirmation window. The job stream is deleted.
For example:
1. Run a job stream list.
2. Right-click a job stream and select Open. The job stream opens in the Graph view of the
Job Stream Editor.
3. Right-click another job stream in the list and this time select Copy from the pop-up
menu.
4. Go to the Job Stream Editor where the first job stream is open..
5. Right-click anywhere in the window and select Paste from the pop-up menu.
6. In the Properties - External Job window, select Show jobs. All the jobs that comprise the
second job stream are displayed.
7. Select the job or jobs that you want to add as external jobs of the first job stream.
8. Click OK to close the Properties - External Job window. Icons for the added jobs are
displayed in the Graph view of the first job stream.
Job Streams
You can select a job stream from a list and use its definition to create other job streams with
equal or similar properties. To do this:
1. Display a list of job streams.
2. Right-click the job stream that you want to use as a model for creating another job
stream and select Create Another from the pop-up menu. The Job Stream Editor and the
job stream properties windows for the job stream that you selected are displayed.
3. In the Name field of the job stream properties window, change the default name to the
name of your choice. If you do not change the name, the new job stream is saved as
CopyOfname, where name is the name of the model job stream.
4. In the job stream properties and Job Stream Editor windows make any other changes that
you need to customize the new job stream for your requirements.
5. Save the new job stream and close the Job Stream Editor window.
6. In the Job Scheduling Console window, either click the Refresh List Results button or
run another list to view the new job stream.
Job Instances
that has been scheduled in the plan. The plan contains past, present, and future scheduled
job streams. It also contains the workstations and resources that support this workload.
To monitor and modify job and job stream instances, you create and display lists for each.
This chapter describes how to list job stream and job instances. “Managing Job Streams” on
page 127 describes how to work with instances from the lists you create.
Table 45 shows some examples of how to use job and job stream instance lists:
Table 45. Examples of How to Use Job and Job Stream Instance Lists
To do this ... Perform this task ...
List jobs that have ended in error in the Create a list of jobs with a status of Error and a time
last 24 hours interval between yesterday’s and today’s dates.
Discover all the scheduled jobs that List the job in error and look at all its successors.
depend on a job that you know will end
in error
Search for all job streams that include a Create a job instance list and specify the identifier in the
specific job 3 filter criteria. The resulting list displays all instances of job
3 and the job stream instance to which it belongs.
See all job stream instances scheduled Create a job stream instance list and specify the dates in the
for the month of December 2001 filter criteria.
To list job stream instances, in the Job Scheduling view, select an engine and click the List
Job Stream Instances button in the toolbar. The Properties - Job Stream Instance List
window is displayed.
Use the information in Table 46 to specify the selection criteria for the list.
Table 46. Properties - Job Stream Instance List Information
In this area ... Do this ...
Name Type a name for the job stream instance list.
Periodic Refresh Options Periodic refresh
Select this to specify a refresh interval in seconds, if you
want the list results refreshed automatically.
Apply defaults
Click this to use the default specified in the Settings page of
the Scheduler Properties window.
Filter Criteria
Specify any of the following search parameters, or combinations of two or more parameters. Use
wildcards to help your search.
Job Instances
Dates Lists all job stream instances scheduled to run in an interval
period starting on the day and time specified in the From Date
and Time fields and ending in the day and time specified in the
To Date and Time fields. Pop-up calendars are provided to help
you select the days.
Priority Lists all the job stream instances that have the priority level you
select in From and To.
Manually Added Lists all those job stream instances that were added manually to
the plan (and not automatically through a plan extension), if you
select the Yes radio button. Select No to exclude manually added
job streams from the list. Select Ignore criteria to omit this filter.
Rerun requested Lists all those job stream instances for which a rerun was
requested, if you select the Yes radio button. Select No to exclude
these job stream instances from the list. Select Ignore criteria to
omit this filter.
Contains Monitored Job Yes
lists only job streams that contain jobs selected for monitoring
by Tivoli Business Systems Manager.
No
lists only job streams that contain jobs that are not selected for
monitoring by Tivoli Business Systems Manager.
Ignore criteria
lists job streams, regardless of whether they contained jobs
that are monitored by Tivoli Business Systems Manager.
Most Critical Job The start time of the most critical job. If the job stream has no
critical job, the field is blank.
Status Lists all the job stream instances with any of the following Job
Scheduling Console status codes that you specify in the
drop-down list:
¶ Waiting
¶ Running
¶ Successful
¶ Error
¶ Canceled
Note: Status and internal status exclude each other as filter criteria. However, they are both
displayed among the properties of job stream instances. Internal status refers to the
status code assigned by the specific job scheduling engine. It generally provides more
detail than the broader status code assigned by the Job Scheduling Console.
Click OK. An button of the new list is displayed in the tree under the engine you selected
when creating it. To display the list, right-click it and select Open. List results are displayed
in the right hand pane. Optionally, before saving the list, you can click Apply to display the
list results immediately.
Use the information in Table 47 to specify the selection criteria for the list.
Table 47. Properties - Job Instance List Information
In this area ... Do this ...
Name Type a name for the list.
Periodic Refresh Options Periodic refresh
Select this to specify a refresh interval in seconds, if you want
the list results refreshed automatically.
Apply defaults
Click this to use the default specified in the Settings page of
the Scheduler Properties window.
Filter Criteria
Specify any of the following search parameters, or combinations of two or more parameters. Use
wildcards to help your search.
Job stream Lists all the job instances that are in the job stream with this name
or namestring.
Job identifier Lists all the job instances that have this identifier. You cannot use
wildcard characters with this filter.
Task name Lists all the job instances that are associated with this task or JCL.
Workstation Lists all the job instances run on this workstation.
Owner Lists all the job instances that belong to this owner.
Job Instances
¶ Waiting
¶ Undecided
Critical job Lists all the job instances defined as critical jobs. Available for OPC
2.3 or later.
WLM policy Lists all the job instances defined as critical jobs and for which the
WLM policy you indicate here was defined. click the arrow and
select one of the available policies. Available for OPC 2.3 or later.
Note: Status and internal status exclude each other as filter criteria. However, they are both
displayed among the properties of job instances. Internal status refers to the status
code assigned by the specific job scheduling engine. It generally provides more detail
than the broader status code assigned by the Job Scheduling Console.
Click OK. An button of the new list is displayed in the tree under the engine you selected
when creating it. To display the list, right-click it and select Open. List results are displayed
in the right-hand pane. Optionally, before saving the list, you can click Apply to display the
list results immediately.
Timeline View
The Timeline View displays graphic information about time restrictions.
In the Timeline View, job stream instances with the same names are listed in groups. A
group contains two or more job stream instances that have the same job stream name but
The only possible action on a group of job stream instances is Delete all, which you can
select when you right-click the group. To perform the actions listed above and to display
activity bars on the individual instances, you must first expand the group by clicking on the
arrow.
The right-hand pane has activity bars that show the actual run time if the instances have
begun, as well as the specified time restrictions for the instances.
By moving components of the activity bars, you can change the time restrictions of each
instance and view the results of your changes, as you would by following the steps
described in “Browsing and Modifying Job Stream Instances” on page 128 and going
directly to the Time Restrictions page of the Properties - Job Stream Instance window.
The activity bar shows the runtime of a job stream instance in terms of the start and
deadline times that were specified as time restrictions for the job stream. The deadline is
indicated by a vertical black stripe at the end of the blue activity bar. As the instance starts,
a horizontal black line unfolds inside the activity bar to show the actual runtime.
You can change the time restrictions of an instance that has yet to run or that is running by:
¶ Rescheduling the instance
¶ Rescheduling the start time
¶ Rescheduling the deadline time
As you move the bar, a tooltip tells you the new deadline time at every position of the
right end of the bar.
2. When you find the position you want, release the mouse button. The Properties - Job
Stream Instance Time Restrictions window is displayed, showing the new start and
deadline times.
As you move your mouse, a tooltip tells you the corresponding start time at every new
position of the left end of the bar.
2. When you find the position you want, release the mouse button. The Properties - Job
Stream Instance Time Restrictions window is displayed, showing the new start time.
3. ClickOK to save the new settings. The left end of the activity bar is set on the new
position.
Rescheduling the Deadline Time
To reschedule the deadline time:
1. Position the mouse pointer on the right end of the bar. When the pointer becomes a
double arrow, hold down the left mouse button while moving the end of the bar.
As you move your mouse, a tooltip tells you the corresponding deadline time at every
new position of the right end of the bar.
2. When you find the position you want, release the mouse button. The Properties - Job
Stream Instance Time Restrictions window is displayed, showing the new deadline time.
3. Click OK to save the new settings. The right end of the activity bar is set on the new
position.
Note: To be able to rerun a job stream instance, restart cleanup must be enabled in the job
properties. This can only be done on the host.
Timeline View
The Timeline View displays graphic information about time restrictions.
In the Timeline View, job instances that share the same job stream instance and runtime are
listed in groups. A group contains two or more job instances that have the same runtime but
different identifiers. Groups are indicated by a small arrow on their left side. Click the arrow
and the individual instances are displayed.
To perform the actions available to individual job instances and to display activity bars on
the job instances arranged in a group, you must first expand the group by clicking on the
arrow.
This section describes the following pages of the the properties window:
¶ General
¶ Task
¶ Time Restrictions
¶ Details
¶ Options
¶ Resources
Click the pull-down arrow and select the type of resources you want to see.
Target Resources
The Target resources list, shown in the next figure, displays the quantities of workstation
resources 1 and 2, and of the parallel server. You can modify quantities by double-clicking
the field and entering a new value.
To add or remove resources in the list, click the Add Row or Remove Row buttons. When
adding a resource, click the ellipsis (...) under the Resource field to locate resources with
theFind tool. When removing a resource, select the resource before clicking on Remove
Row.
Note: You can only add or remove logical resources, not target resources.
List the job instance that you want to work on, then right-click it and select Dependencies
from the pop-up menu. The Dependencies - JCL Job Instance Predecessors window is
displayed.
Predecessors Window
The Predecessors window displays information about the job instances that must complete
before this instance can start running:
Note: If you cannot read the headings completely, widen the column heading cells with
your mouse.
Note: If you cannot read the headings completely, widen the column heading cells with
your mouse.
The right-hand pane, see Figure 71, has activity bars that show the runtime of a job instance
in terms of start, duration, and deadline times.
By moving components of the activity bars, you can change the time restrictions of each
instance and view the results of your changes, as you would by following the steps
described in “Browsing and Modifying Job Instances” on page 139 and going directly to the
Time Restrictions page of the job instance properties window.
As you move the bar, a tooltip tells you the new deadline time at every position of the
right end of the bar.
2. When you find the position you want, release the mouse button. The Properties - Job
Instance Properties Time Restrictions page is displayed, showing the new times.
3. Click OK in the Time Restrictions page to save the new settings. The activity bar is set
on the new position.
As you move your mouse, a tooltip tells you the corresponding start time for every new
position of the left end of the bar.
2. When you find the position you want, release the mouse button. The Properties - Job
Instance Properties Time Restrictions page is displayed, showing the new start time.
3. Click OK to save the new settings. The left end of the activity bar is set in the new
position.
You can change the way the view is displayed by using the following buttons in the toolbar.
Table 59. Impact View Options
Select this button ... To display this type of view ...
Radial
Left
Right
Up
Down
Displaying Dependencies
To display a dependency of a job instance, right-click the job instance and select
Dependencies from the pop-up menu. Any dependent job instances are displayed.
Only the first level of dependenct job instances is displayed. If you want to display more
than one level of dependency, you must right-click each dependent job instance in turn,
selecting Dependencies from the pop-up menu each time.
Note: If you display dependencies for more than one job, then refresh the display, only the
first level of dependent job instances is displayed.
To reset the display in a separate window, right-click the job instance you want to use as as
the root job instance and select Set As Root In New Frame from the pop-up menu.
To use the NOP option, right-click the name of a job instance and select NOP from the
pop-up menu.
To do this, right-click the name of a job instance and select UN-NOP from the pop-up
menu. The job instance is restored to the plan.
To force the running of a job instance, right-click the name of a job instance and select
Execute from the pop-up menu. If all conditions are met, the job instance is run
immediately.
Note: If you are changing to an Error status, a field becomes available for entering any
code you want to show in the properties window.
3. Click the Import button to open a JCL file and copy JCL into the edit window.
4. Click the Export button to save any JCL from the job you are editing.
Note: The Browse Operator Instruction option is only available if an operator instruction
has been defined for the job instance.
Note: You can only change the variable value. A default value is displayed, if it has been
set beforehand.
When you have made your changes, click OK. A second Job Setup window is displayed for
each successor job instance. Each window shows the JCL for the instance, reflecting the
change made to the promptable variables.
When you have finished, for each Job Setup JCL window:
¶ Click OK to save the changes and close the window.
¶ Click Cancel to close the window without saving any changes.
You can restart a job instance and perform cleanup operations. To do this:
1. Right-click a job instance and select Restart and Cleanup from the pop-up menu. The
Restart and Cleanup window is displayed.
2. Select one of the following:
Step Restart Choose at what step of the JCL the job is to restart.
Job Restart Completely restart the job.
Start Clean Up Only clean up the environment.
Display Clean Up Result View the results of the clean up.
Use Expanded JCL Select this to use expanded JCL.
in the Plan
¶ Monitor the status of a workstation in the plan and of the job instances scheduled to run
on it
¶ Modify the settings and availability of the workstation
¶ Reroute the job instances that are scheduled to run on a workstation
¶ Modify the status of the job instances running on the workstation
To perform these tasks, you use a filtered list of workstations in the plan.
To create a list of workstations in the plan, in the Job Scheduling view, select an engine and
click the List Workstations in Plan button. The Properties - Plan Workstation List window
is displayed.
in the Plan
Filter Criteria In the group, specify any of the following search parameters or
combinations of two or more parameters. To generalize your
search, use wildcard characters, such as an asterisk (*) to represent
strings of characters, or a question mark (?) to represent a single
character. If you leave all fields blank, all the workstations defined
in the database are displayed when you open the list.
Workstation
Lists all the workstations with this name or namestring.
Reporting Attributes
Lists all the workstations characterized by the reporting
attributes you select with the following check boxes:
¶ Automatic
¶ Completion only
¶ Manual start at completion
¶ Non reporting
Types
Lists all the workstations of the type you select with the
following check boxes:
¶ General
¶ Computer
¶ Printer
Is Fault Tolerant
Lists fault-tolerant workstations. These workstations are
used to run the Workload Scheduler jobs in the Workload
Scheduler for z/OS plan. Select:
Yes To list fault-tolerant workstations
No To list workstations that are not fault-tolerant
Ignore criteria
To list workstations regardless of whether they are
fault-tolerant or not
Plan workstation lists are displayed in windows composed of two horizontal panes. In
addition to the workstation list, there is a lower pane that contains details about the jobs
scheduled on the workstations. To see the lower pane, drag the horizontal dividing bar
located at the bottom of the window.
For more information, see “Displaying by Status the Job Instances Scheduled on a
Workstation” on page 171.
The changes you make from a workstation status list update the current workstation plan
information. This information is stored in the current plan data set.
Right-click a workstation in the list and select Properties from the pop-up menu. The
Properties - Workstation in Plan General page is displayed. Several fields are read-only.
Select Resource in the left pane. The Properties - Workstation in Plan Resource page is
displayed
This page displays details about the two workstation resources. For each of the two
resources the window displays the name, the amount in use, and the type of use.
To change the type of use of each resource, select Used for control. This means that, if an
unexpected event happens while job instances are running, the system considers the resource
when it reschedules them.
Job Summary Page
Select Job Summary in the left pane. The Job Summary page is displayed.
This page displays the number, estimated duration, and actual duration (where applicable) of
all the job instances scheduled to run on the workstation. The information is provided for
instances in the following status:
Select Open Time Intervals in the left pane. The Open Time Intervals page is displayed.
in the Plan
Figure 83. Properties - Workstation in Plan Open Time Intervals Page
This page shows a list of time slots when the workstation is available to run jobs with
resource quantities different from the default. The list shows the boundaries of each time slot
and, for every slot, the planned quantities of workstation resources and of parallel servers
available, together with the name of the alternate workstation.
You cannot edit the resource quantities and the alternate workstation names in the Planned
fields. They correspond to the workstation Open Time Intervals definitions in the system
database and can only be modified there (from a list of workstations in the database, for
example). You can change the time boundaries and the values in the Modified fields. These
values override the Planned values for the duration of the plan.
3. To change the initial time, double-click in the Start Time column and enter the new
time.
4. To change the last day, double-click the date field in the End Date column.
5. Click the pop-up calendar button and select the new day in the calendar. The new day
is automatically entered in the field.
6. To change the final time, double-click the time field in the End Time column header.
7. Enter the new time.
8. To adjust the quantity of available parallel servers, double-click the field in the
Modified PS column.
9. Enter a new quantity.
To do this:
1. Right-click a workstation in the list and select Set Status from the pop-up menu. The
Change Status - Workstation window is displayed.
To display the job instances, right-click a workstation from the list and select List Jobs, then
Complete (for example) from the pop-up menu.
All the job instances scheduled to run on the workstation and currently in Complete status
in the Plan
Figure 88. List of Jobs Scheduled on the Workstation and in Complete Status
Table 62 shows the list of options that you can select from the pop-up menu.
Table 62. Workstation List Jobs Options
Select this option ... To display jobs that ...
Arriving Are scheduled to run on the workstation
Complete Have completed without errors
Deleted Have been canceled on the workstation
Error Have ended in error on the selected workstation
Interrupted Have been interrupted on the workstation
Ready Are ready to run on the workstation
Ready List Are ready to run, including jobs that have a predecessor on a
nonreporting workstation, but are ready to run on the selected
workstation
Ready - Non Reporting Have a predecessor on a non-reporting workstation, but are ready
Workstation to run on the selected workstation
Started Are running on the workstation
Undecided Have an unknown status
For an explanation about how to use these options, see “Managing Jobs” on page 137.
To perform these tasks, you use a filtered list of resources in the plan.
To make a plan resource list object, select an engine in the Job Scheduling view and click
the List Resources in Plan button.
the Plan
Treat special characters as wildcards and character
substitutes.
Exact match
Treat special characters as part of the resource name.
Prefix
Treat the string as a name prefix.
Suffix
Treat the string as a name suffix.
¶ Specify a resource group name in Group.
¶
¶ Specify whether the resources are data sets with the DLF
attribute or not, or if this is to be ignored, in Hiperbatch.
¶ In Allocation Options, specify whether or not the resources
have been allocated for shared or exclusive use, or whether this
is to be ignored.
¶ In Waiting, specify whether or not there are job instances
waiting to allocate the resources, or whether this is to be
ignored.
¶ In Available, specify whether or not the resources are
available, or whether this is to be ignored.
A list of resources allocated to the plan is displayed in the right pane of the Job Scheduling
view. The entries displayed are read-only. To modify details of resources already allocated to
the plan, you must use the Properties - Resource in Plan window as explained in “General
Page” on page 177.
Plan resource lists are displayed in windows composed of two horizontal panes. In addition
to the resource list, there is a lower pane that contains details about the jobs associated with
the resources. To view the lower pane, drag the horizontal dividing bar located at the bottom
of the window, as shown in the next figure.
See“Displaying the Job Instances Associated with a Resource” on page 181 for details.
The changes you make from a plan resource list update the current resource plan
information, which is stored in the plan.
Right-click a resource from the list and select Properties from the pop-up menu.The page of
the Properties - Resource in Plan Resource page is displayed.
Table 65 describes the contents of this window. Some of the information displayed is
read-only. Other information you can edit.
the Plan
Table 65. Properties - Resource in Plan Resource Information
This area ... Contains this information ...
Name Name of the resource. Read-only.
Description Description of the resource. Read-only.
Default Is Available
Changes the availability status of the resource.
Quantity
Adjusts the default resource quantity that must be available while
the plan is running by entering a new quantity in the Quantity
field.
Group ID Resource group ID. Read-only.
Hiperbatch Whether the resource is enabled to Hiperbatch. It can be Yes or No.
Read-only.
Used for Modifies the type of use of the resource. Choices are
Planning
Control
Planning And Control
Neither Planning Nor Control
On Error What to do with the resource if a job instance that allocates the
resource ends in error (and does not have an overriding keep-on-error
specification in the job definition). Select one of:
Free
Keep
Free if Exclusive
Free if Shared
Assume System Default
Note: While the updates you make to most of these details are replaced by the database
values at the end of the plan, the updates in Quantity and Deviation are retained also
through plan extensions, unless they are changed manually.
Click Default Workstations in the left pane. The Properties - Resource in Plan Default
Workstations page is displayed.
This page displays the workstations that can use the resource. Table 66 shows how to add or
remove workstations in this list by using the buttons in the upper-right side of the page.
the Plan
Table 66. Properties - Resource in Plan Default Workstations Information
To perform this task ... Do this ...
Remove a workstation Select the workstation and click on the Remove Row button.
Add all available workstations click the Add All Workstations button. A new row is added.
It contains an asterisk, meaning that all available workstations
are connected to the resource
Add specific workstations click the Find Workstations button. A Find dialog is
displayed.
Click Availability Intervals in the left pane. The Properties - Resource in Plan Availability
Intervals page is displayed.
This page shows a list of time intervals when the resource is available with properties
different from the defaults. You can use this list to change the resource availability values in
the defined intervals, or to add or remove availability intervals. Blank fields in an
availability interval mean that the default values, as specified in the database or in the other
pages of this window, are the valid ones during the interval.
Table 67 shows how to add or remove workstations in this list by using the buttons in the
upper-right side of the page.
Table 67. Properties - Resource in Plan Availability Intervals Information
To perform this task ... Do this ...
Change the day in which the interval Double-click the Date field and select the pop-up calendar
occurs button. In the pop-up calendar, choose a date and click it to
enter it in the field.
Change the starting time Double-click the From Time field and enter the new time.
Change the finishing time Double-click the To Time field and enter the new time.
Change the resource quantity that is Double-click the Quantity field and enter a number.
made available or unavailable for the
workstations defined in the
availability interval
Change the availability status of the Double-click the Is available field and select one of:
quantity defined in the previous field Available
Not available
Default
Default uses the value specified in the database.
the Plan
To display the job instances, right-click a resource from the list display and select List Jobs
from the pop-up menu, then select either Waiting for Resource or Using Resource.
All the job instances scheduled to use the resource and currently in this status are displayed
in the bottom pane of the window.
Obtain a list of jobs associated with a resource, then right-click a selected job and select one
of the follwing options:
Table 68. Modifying Job Instance Options
Select this option ... To do this ...
Properties Browse and modify the properties of the job instance.
Dependencies Browse and modify the dependencies of the job instance.
Delete Delete the job instance from the plan.
Hold Hold the job instance.
Release Release the job instance.
NOP / UN-NOP NOP or UN-NOP the job instance.
Execute Run the job instance immediately.
Set status Change the status of the job instance.
For an explanation on how to use these options, see “Managing Jobs” on page 137.
Lists
Managing Database Lists
Database lists are used to display objects in the scheduler database. When you create a list,
you give it a name and specify filtering criteria. When you run a list, it displays a filtered
table of objects in the database. Each list you create is represented by an button in the tree
view of the Job Scheduling Console.
You can create lists in the Workload Scheduler branch or you can create groups below the
branch to organize your lists. Tivoli supplies a basic set of lists in a group called Default
Database Lists.
3. Enter a name for the group. You can use the same name for more than one group, if you
want. Different groups maintain their individual properties even if they have the same
name.
After creating a group, you can create its member lists and subgroups. Right-click the group
to display a pop-up menu with the following options:
Creating Lists
To create a database list, right-click an engine and select one of the following options:
To create the list in the scheduler branch, expand the branch and select a group button.
2. Click the List Job Streams button on the toolbar. Alternatively, right-click the engine or
group button and select Create Database List then Job Stream from the pop-up menu.
Lists
Figure 96. Properties - Job Stream List Window
To create the list in the scheduler branch, expand the branch and select a group button.
2. Click the List Job Definitions button on the toolbar. Alternatively, right-click the engine
or group button and select Create Database List then Job from the pop-up menu.
The Properties - Job List window is displayed.
To create the list in the scheduler branch, expand the branch and select a group button.
2. Click the List Workstations in Database button on the toolbar. Alternatively, right-click
the scheduler engine button or group button and select Create Database List then
Workstations from the pop-up menu.
The Properties - Database Workstation List window is displayed.
Lists
To create a list of resources:
1. Select an engine in the tree.
To create the list in the scheduler branch, expand the branch and select a group button.
2. Click the List Resources in Database button on the toolbar. Alternatively, right-click the
scheduler engine button or group button and select Create Database List then Resource
from the pop-up menu.
The Properties - Database Resource List window is displayed.
Lists
When you have finished:
¶ Click Apply to run the list without closing the window. The list results are displayed in
the right pane of the Job Scheduling Console.
¶ Click OK to save the list and close the window. A new button is created for the list in
the tree view of the Job Scheduling Console.
¶ Click Cancel buttonto close the window without running or saving the list.
Creating a List of Parameters
To create a list of parameters:
1. Select an engine in the tree.
To create the list in the scheduler branch, expand the branch and select a group button.
2. Right-click the scheduler engine button or group button and select Create Database List
then Parameter from the pop-up menu.
The Properties - Parameter List window is displayed.
Note: Alternatively, you can select an engine in the tree and double-click the list you
want to run in the right-hand pane of the Job Scheduling view.
You can display several lists in sequence. The newest list is displayed above the preceding
ones. However, as long as a list is kept open, it is maintained and refreshed according to the
refresh options specified. To view the list, click the corresponding object in the Job
Scheduling view.
Detaching a List Display
Detaching a list frees the right-pane of the Job Scheduling Console to display other objects.
You can detach multiple lists to view several objects simultaneously.
Lists
3. To place the list back in the right-hand pane, either close the detached window or
right-click the list in the tree view and select Attach View from the pop-up menu.
Notes:
1. The right-hand pane of the console is not disabled. This is so that you can run other lists
or perform other tasks.
2. You can have a maximum number of seven detached views open at the same time.
3. To prevent your system from overloading, do not have frequent refreshes of many
detached views open at the same time.
Modifying a Database List
To modify the properties of a list:
1. In the tree of the Job Scheduling view, double-click an engine.
2. Right-click the list you want to modify and select Properties from the pop-up menu.
3. The properties window of the list is displayed.
4. Make your changes.
Finding Objects
Search tools are provided in the Job Scheduling Console to help you find objects in the
database. The availability of a search tool is indicated by an ellipsis located next to the field
where you enter an object name. In the following example of the Properties - Resource in
Database window, the Workstation field provides a search tool.
When you click the ellipsis, the Find Workstation window is displayed.
3. In the Select a task type window, select a task type from the drop-down list. Once a task
type is defined for a job it cannot be changed. Table 71 describes the task types:
Table 71. New Job Definition Task Types
This task type ... Specifies that ...
UNIX Script The job is an executable file on a UNIX computer.
UNIX Command The job is a UNIX command.
NT Script The job is an executable file on a Windows NT computer.
NT Command The job is a Windows NT command.
Workstation Class Script The job is an executable file that runs on a workstation class.
Workstation Class Command The job is a command that runs on a workstation class.
Extended Agent The job is associated with an Extended Agent workstation.
MPE Job File The job is an executable file on an MPE computer.
Use the information in Table 72 to complete the text boxes and select options.
Table 72. Properties - Job Definition General Information
In this area ... Enter this information ...
Name The name of the job. The name must start with a letter, and can
contain alphanumeric characters, dashes, and underscores. For
non-expanded databases, it can contain up to eight characters. For
expanded databases, it can contain up to 40 characters.
Workstation The name of the workstation or workstation class on which the job
runs. You can type a name directly or you can click Find and select a
workstation or workstation class from a list. If you specify a
workstation class, it must match the workstation class of any job
stream in which the job will be included. For information about using
the Find button, refer to “Finding Objects” on page 199.
Description A description of the job. The description can contain up to 64
characters.
Table 73 on page 204 summarizes all possible combinations of recovery options and actions.
The table is based on the following criteria from a job stream called sked1:
¶ Job stream sked1 has two jobs, job1 and job2.
¶ If selected for job1, the recovery job is jobr.
¶ job2 is dependent on job1 and will not start until job1 is complete.
Table 73. Job Stream Recovery Options
Prompt / Job Stop Continue Rerun
Recovery prompt: No Intervention is Run job2. Rerun job1. If job1 abends,
Recovery job: No required. issue scheduler prompt. If
reply is yes, repeat above.
If job1 is successful, run
job2.
Notes:
1. ″Intervention is required″ means that job2 is not released from its dependency on job1,
and therefore must be released by the operator.
2. The continue recovery option overrides the abend state, which may cause the schedule
containing the abended job to be marked as successful. This will prevent the schedule
from being carried forward to the next day.
3. If you select the Rerun option without supplying a recovery prompt, Workload Scheduler
generates its own prompt.
4. To reference a recovery job in Conman, you must use the name of the original job (job1
in the scenario above, not jobr). Recovery jobs are run only one per abend.
Select Task in the left pane of the Properties - Job Definition window. This displays the
Task page.
The Task page is different for each task type. To complete the fields and select options on
this page:
Table 74. Task Types
For this task type ... Go to page ...
UNIX Script, NT Script, or Workstation Class Script 206
UNIX Command, NT Command, or Workstation Class Command 207
MPE Job File 207
MPE User Job 207
Extended Agent 207
SAP Job 208
Specify the name of the file the job runs. Enter the file name and any options and
arguments. For non-expanded databases, the field can contain up to 255 characters. For
expanded databases, it can contain up to 4095 characters.
For Windows NT jobs, include the file extensions. Universal Naming Convention (UNC)
names are permitted. Do not specify files on mapped drives.
If the file name contains spaces, enter the name in another file that does not have spaces in
its name and use the second file’s name in this field.
A parameter can be used for all or part of the field and multiple parameters are permitted.
Commands are run directly and the jobmanrc standard configuration script is not run.
A parameter can be used for all or part of the field and multiple parameters are permitted.
Extended Agent
Refer to the specific user guide for the Extended Agent you are working with for more
information.
3. Make your changes. For information about the window, see “Creating a Job Definition”
on page 201.
Add Job Definition Adds a job to the job stream. An button is added to
represent the job.
Timeline View
The Timeline view provides a tabular and timeline display of the time restriction properties
of the job stream and its jobs. Use this view to display and adjust time restriction properties.
The window is divided into four panes. The job stream is displayed in the upper pane and
its jobs are displayed in the lower pane. Use the borders and the arrows on the borders to
adjust the sizes of the panes. Use the arrows at the top of the timeline pane to move the
view in one hour and one day increments.
Dragging a line, or the end of a line, adjusts the start and deadline times of the job stream
or a job. Double-clicking the job or job stream name opens time properties windows. You
can edit the time properties of the job or job stream from these windows.
Table 78 describes the toolbar in the Timeline view of the Job Stream Editor.
Table 78. Job Stream Editor Timeline View Toolbar
This button ... Has this name ... And does this ...
Properties Displays the Job Stream Properties window.
Move Job Up Move the job up one step in the job stream.
Move Job down Move the job down one step in the job stream.
The window is divided into two panes. The left pane lists the types of run cycles defined for
the job stream and the associated freeday rule. The right pane displays a calendar showing
included or excluded days as defined in the selected run cycle. Use the border and the
arrows on the border to adjust the pane size.
Use the tabs above the calendar to select the Monthly or Yearly view and use the arrows
above and below the calendar to change the month or year of the calendar.
Table 79 describes the toolbar in the Run Cycle view of the Job Stream Editor.
Table 79. Job Stream Editor Run Cycles View Toolbar
This button ... Has this name ... And does this ...
Properties Displays the Job Stream Properties window.
Save Saves the job stream in the database.
Select a Run Cycle Changes the mouse pointer to a selection arrow.
Delete Deletes the selected run cycle.
Simple Run-Cycle Adds a run cycle of days marked on a monthly or
yearly basis.
Weekly Run-Cycle Adds a run cycle of days selected on a weekly
basis.
Calendar Run-Cycle Adds a run cycle of days based on a previously
defined calendar.
Graph Displays the Graph view.
The Job Stream Properties window opens automatically when you create a new job stream.
If the window is not displayed, select Properties from the File menu of the Job Stream
Editor.
To specify job stream properties, click Generalin the left pane of the Job Stream Properties
window. The General page is displayed.
Use the information in Table 81 to complete the text boxes and select options.
Table 81. Job Stream Properties General Information
In this area ... Enter this information ...
Name The name of the job stream. The name must start with a letter, and
can contain alphanumeric characters and dashes. For non-expanded
databases, it can contain up to eight characters. For expanded
databases, it can contain up to 16 characters. The name of a job
stream cannot be changed once is has been saved. However, you can
use the create another command to save the job stream with another
name.
Workstation The name of the workstation or workstation class on which the job
stream is launched. You can type a name directly or you can click
the Find button and select a workstation or workstation class from a
list. If you specify a workstation class, it must match the workstation
class of any jobs or resources used in the job stream. For information
about using the Find button, refer to “Finding Objects” on page 199.
Description A description of the job stream.
When you have finished, click Time Restrictions in the left pane of the Job Stream
Properties window. The Time Restrictions page is displayed.
Note: Time Restrictions can also be set in the Timeline view of the Job Stream Editor. See
“Specifying Time Restrictions in the Timeline View” on page 244 for more
information.
When you have finished, click Resources in the left pane of the Job Stream Properties
window. The Resources page is displayed.
To remove a resource dependency for the job stream, select the resource row in the list and
click Delete from Table.
When you have finished, click Files in the left pane of the Job Stream Properties window.
The Files page is displayed.
To remove a file dependency for the job stream, select the file row in the list and click the
Delete from Table button.
When you have finished, click Prompts in the left pane of the Job Stream Properties
window. The Prompts page is displayed.
Prompts Page
For an ad hoc prompt dependency, select Ad Hoc Prompt from the drop-down list. For a
predefined prompt dependency, select Predefined Prompt from the drop-down list.
To add external dependencies for a job stream, open the job stream in the Job Stream Editor
and select External Dependencies from the File menu. The Job Stream External
Dependencies window is displayed.
There are five pages of job properties in the Properties - Job window:
¶ General
¶ Time Restrictions
¶ Resources
¶ Files
¶ Prompts
Use the information in Table 83 to complete the text boxes and select options.
Table 83. Properties - Job General Information
In this area ... Enter this information ...
Name The name of the job. Click the Find button to choose the job. See
“Finding Objects” on page 199 for more information.
Workstation Name The workstation this job is defined to run on. If this workstation is
deleted, the task type for the job is unknown and must be specified before
you can save the job again.
Priority The priority of the job. Select a priority value from the drop-down list or
click of the following buttons:
Hold Sets the priority to zero.
High Sets the priority to 100.
Go Sets the priority to 101.
Possible priority values are 0 through 101, where 101 is the highest
priority. A priority value of zero prevents the job from launching.
Description A description of the job.
Requires Confirmation Select this box to indicate that job completion must be confirmed by the
operator. When a job with requires confirmation enabled completes, it
remains in the internal status PEND until confirmation is received. If
confirmation is received before the job completes, its internal status is
either SUCCP or ABENDP and other job and job stream successors are
not released.
Is Monitored Job Mark this check box to specify that the running of this job must be
monitored by Tivoli Business Systems Manager.
Select Time Restrictions in the left pane of the Properties - Job window. The Restrictions page
is displayed.
Use the information in Table 84 to complete the text boxes and select options.
Table 84. Properties - Job Time Restrictions Information
Note: Time Restrictions can also be set in the Job Stream Editor Timeline view. For more
information, see “Timeline View” on page 214.
Select Resources in the left pane of the Properties - Job window. The Resources page is
displayed.
Resources Page
Select Files in the left pane of the Properties - Job window. The Files page is displayed.
Files Page
On both UNIX and Windows NT, the expression %p inserts the file name.
Entering notempty is the same as entering -s %p. If no qualifier is specified, the default is
-f %p.
Select Prompts in the left pane of the Properties - Job window. The Prompts page is displayed.
Prompts Page
For an ad hoc prompt dependency, select Ad Hoc Prompt from the drop-down list. For a
predefined prompt dependency, select Predefined Prompt from the drop-down list.
To remove a prompt dependency for the job, select the prompt row in the list and click the
Delete from Table button.
Add internetwork dependencies to a job stream to create predecessors for the jobs in the job
stream you are editing. A predecessor must complete successfully before the successor job is
launched.
You add internetwork dependencies in a job stream using the Graph view of the Job Stream
Editor. See “Graph View” on page 213 for more information.
You add external job streams in a job stream using the Graph view of the Job Stream Editor.
For more information, see “Graph View” on page 213.
4. Click the Find (...) button next to the Workstation field to locate and insert the name of
the workstation on which the job stream runs.
5. Click Show Job Streams to list the job streams that run on the workstation.
6. Select a job stream in the list.
For information about using an external job stream as a predecessor, see “Creating
Dependencies Between Jobs in a Job Stream” on page 236.
Adding an External Job to a Job Stream
An external job is a job that runs in a job stream other than the one you are editing. Add
external jobs to a job stream to create predecessors for the jobs in the job stream you are
editing. A predecessor must complete successfully before the successor job is launched.
You add external jobs in a job stream using the Graph view of the Job Stream Editor. For
more information, see “Graph View” on page 213.
4. Click the Find (...) button next to the Job Stream Name field to locate and insert the
name of the job stream in which the job runs. For information about using the Find
window, see “Finding Objects” on page 199.
5. Click Show Jobs to list the jobs in the selected job stream that run on the selected
workstation.
6. Select a job in the list.
For information about using an external job as a predecessor, see “Creating Dependencies
Between Jobs in a Job Stream”.
Creating Dependencies Between Jobs in a Job Stream
You can add dependencies between jobs to specify the order in which they run. A job that
depends on the successful completion of another job is called a successor and the job or job
stream that it depends on is called a predecessor.
You add dependencies between jobs in the Graph view of the Job Stream Editor. For more
information, see “Graph View” on page 213. The dependencies are represented by arrows.
Notes:
1. Internetwork dependencies, external jobs, and external job streams cannot be successors.
2. Internetwork dependencies, external jobs, and external job streams that are not linked are
To remove a dependency between jobs, select the arrow between the predecessor and the
successor , then right-click the arrow and select Delete from the pop-up menu.
When you are finished in the Job Stream Editor, refer to “Saving a Job Stream in the
Database” on page 247.
You specify run cycles for a job stream using the Run Cycle view of the Job Stream Editor.
To display the Run Cycle view, select Run Cycle from the View menu in the Job Stream
Editor or click the Run Cycle button in the toolbar. For more information, see “Run Cycle
View” on page 216.
Inclusionary or Exclusionary Run Cycles
When you define a run cycle, you must specify if it designates the days when the job stream
is to run (inclusionary) or when the job stream is not to run (exclusionary).
The days you mark in an inclusive run cycle are displayed as Days Included in the list
of run cycles applied to the job stream.
For each job stream, you can define as many inclusive and exclusive run cycles as you
want.
Rule for Freedays
This rule is based on the definition of freedays. Freedays are non-workdays, such as
holidays or closing days, and can be defined in one or more specific calendars. Freedays
calendars can in other terms be considered the list of non-workdays when there is no activity
in your enterprise. For details, see “Freedays Calendars” on page 267.
Based on a freedays calendar, you can specify a rule when you define the run cycle of a job
stream. The rule determines what action Workload Scheduler must take when the schedule of
a job stream falls on a freeday. If the schedule date falls on a freeday, the scheduler can do
one of the following:
¶ Run the job stream
¶ Not run the job stream
¶ Run the job stream on the closest workday before the freeday
¶ Run the job stream on the closest workday after the freeday
If no freeday rule is specified, the scheduler proceeds by default and runs the job stream
even if the selected run date is a freeday.
Workload Scheduler does not reschedule the same job stream more than once on a given
production day if its run date was moved because of a freeday rule application.
Colored Bars on Dates
As you include and exclude dates, colored bars are displayed across the dates. The bars have
the following meanings:
Table 85. Colored Bars on Dates
This bar ... Specifies ...
Blue An included date.
Red An excluded date.
White A non-workday.
White/Blue An included non-workday.
White/Red An excluded non-workday.
Note: Dates defined in the Holidays calendar are shown as non-workdays. For more
information, see “The Holidays Calendar” on page 266.
7. Select the Monthly or Yearly tab to display the corresponding view. Use the arrow
buttons in the upper and lower bars of the selected view to move to the desired month
and year.
8. Click the dates in the calendar to add them to the run cycle. Click on the same date a
second time to remove it from the run cycle.
7. Enter the name of the calendar in the Name field or click the Find (...) button to find a
calendar. For more information, see “Finding Objects” on page 199.
8. In the Offset group, you can specify an offset from the dates defined in the calendar. For
example, if a calendar date is 3/13/2001, an offset of +2 Days results in an effective date
of 3/15/2001.
To specify an offset:
a. Select + for a positive offset or - for a negative offset from the drop-down menu.
b. In the Offset field, enter the number of days (between 0 and 9999).
c. From the drop-down menu, select one of:
Days Specifies calendar days with no exceptions.
Workdays
Specifies calendar days except Saturday, Sunday, and the days defined either
in the freedays calendar or in the Holidays calendar, depending on which one
you specified in the properties window of the job stream.
Weekdays
Specifies calendar days except Saturday and Sunday.
Using a Window
To adjust the time restrictions using a window, either double-click the job stream row in the
tabular pane or right-click the row and select Properties from the pop-up menu. A properties
window is displayed.
Use the information in Table 86 to complete the text boxes and select options.
Table 86. Properties Information
In this area ... Enter this information ...
Start The earliest time the job stream will be launched. The job stream will
not be launched before this time.
Specify time
Select this option to enable the entry of a start time.
Note: Time Restrictions can also be set in the Time Restrictions view of the Properties - Job
window. For more information, see “Specifying Job Stream Properties” on page 217.
Specifying Time Restrictions for a Job
To specify time restrictions for a job in the Timeline view of the Job Stream Editor, either
select Timeline from the View menu in the Job Stream Editor or click the Timeline button
in the toolbar.
Using a Window
To adjust the time restrictions using a window, double-click the job row in the tabular pane
or right-click the row and select Properties from the pop-up menu. A properties window is
displayed
Use the information in Table 87 to complete the text boxes and select options.
Table 87. Properties Information
In this area ... Enter this information ...
Start The earliest time the job will be launched. The job will not be
launched before this time.
Specify time
Select this option to enable the entry of a start time.
At Enter a start time in the following format:
hh:mm am|pm
For example, 11:30 am or 4:25 pm.
Delay for
Enter the number of days to offset the start time from the day the
job is selected for inclusion in the production plan.
Deadline The latest time the job will be launched. The job will not be launched
after this time.
Specify time
Select this option to enable the entry of a deadline time.
At Enter a deadline time in the following format:
hh:mm am|pm
For example, 11:30 am or 4:25 pm.
Note: The deadline time must be later than the Start Time.
Delay for
Enter the number of days to offset the deadline time from the day
the job is selected for inclusion in the production plan.
Time Zone The time zone for this job. For information about the time zone
feature, see “Enabling Time Zones in the Workload Scheduler” on
page 385.
Repeat Range The repetition rate of the job. The job is launched multiple times at
this rate.
Hours
Specify the hours that a job repeats.
Minutes
Specify the minutes that the job repeats.
Note: Time restrictions can also be set in the Time Restrictions view of the Properties - Job
window. See “Specifying Job Properties” on page 227 for more information.
If you have not saved your job stream changes, a warning messages is displayed. Do one of
the following:
¶ Click Yes to save the job stream in the database before closing the Job Stream Editor.
¶ Click No to close the Job Stream Editor without saving the job stream in the database.
When you right-click a job stream instance in the list, a pop-up menu is displayed. This is
described in “Managing Job Stream Instances in the Plan” on page 316.
When you are finished modifying the job stream, save the job stream in the database and
close the Job Stream Editor. For more information, see “Saving a Job Stream in the
Database” on page 247 and “Closing the Job Stream Editor” on page 247.
Modifying a Job in a Job Stream
To modify a job in a job stream, right-click the job button in the Graph view and select
Properties from the pop-up menu. For information about job properties, see “Specifying Job
Properties” on page 227.
Deleting a Job in a Job Stream
To delete a job in a job stream, right-click the job button in the Graph view and select
Delete from the pop-up menu.
Modifying an Internetwork Dependency in a Job Stream
To modify an internetwork dependency in a job stream, right-click its button in the Graph
view and select Properties from the pop-up menu. For information about internetwork
dependency properties, see “Adding an Internetwork Dependency to a Job Stream” on
page 233.
Click OK to delete the job stream in the database or click Cancel to cancel the delete
operation.
In the tree view of the Job Scheduling Console, right-click the scheduler engine button and
select New Workstation from the pop-up menu. The Properties - Workstation in Database
window is displayed.
Use the information in Table 90 to complete the text boxes and select options.
Table 90. Properties - Workstation in Database Information
In this area ... Enter this information ...
Workstation name The name of the workstation. The name must start with a letter and can
contain alphanumeric characters, dashes, and underscores. For
non-expanded databases, it can contain up to eight characters. For
expanded databases, it can contain up to 16 characters.
Note: Workstation names must be unique, and cannot be the same as
workstation class and domain names.
Node The host name or the IP address of the workstation. Fully-qualified
domain names are accepted.
TCP Port The Netman TCP port number that Workload Scheduler uses for
communications on the workstation. The default is 31111. The port
number of Netman on a workstation is defined by the localopts file in the
parameter nm port.
Operating System The operating system of the workstation. Select one of:
UNIX
Windows NT
MPE/V
MPE/IX
Other
Domain The name of the Workload Scheduler domain of the workstation. The
name must start with a letter and can contain alphanumeric characters,
dashes, and underscores. For non-expanded databases, it can contain up to
eight characters. For expanded databases, it can contain up to 16
characters.
Note: Domain names must be unique, and cannot be the same as
workstation and workstation class names. The default for fault-tolerant and
standard agents is the master domain, usually named MASTERDM. The
default for a domain manager is the domain in which it is defined as the
manager. The default for an extended agent is the domain of its host.
If Full Status is not selected, the agent is informed only about the status
of jobs and job streams on other workstations that affect its own jobs and
job streams. This can improve performance by reducing network activity.
To specify a server, select a letter or a number (A-Z and 0-9) from the
drop-down list. The IDs are unique to each domain manager, so you can
use the same IDs in other domains without conflict. If more than 36
server IDs are required in a domain, consider dividing it into two or more
domains.
When a domain manager starts up, it creates a separate server for each
unique server ID. If the same ID is used for multiple agents, a single
server is created to handle their communications. As a guide, extra servers
should be defined to prevent a single server from handling more than
eight agents.
Access Method An access method for extended agents and network agents. This must be
the name of a method file that resides in the TWShome/methods directory
on the agent’s host workstation. For a local UNIX extended agent, the
method name is unixlocl. For a remote UNIX extended agent the method
name is unixrsh. For Network agents, the method name is netmth. For
more information about extended agents, refer to the individual extended
agent user’s guides. For more information about network agents, refer to
the Tivoli Workload Scheduler Reference Guide.
Host The name of the agent’s host workstation. This is required for extended
agents. The host is the workstation with which the extended agent
communicates and where its access method resides. The host for an
extended agent must be a Master, Domain Manager, or FTA. The host for
an extended agent can be specified as $MASTER. This assigns the host as
the Master Domain Manager, and is useful if you need to switch masters
in the domain. The extended agent will automatically connect to the new
manager.
Note: The host option is no longer required for Standard agents. The host workstation for
standard agents is now defaulted to the domain manager.
19. Managing
Workstations
following:
¶ Click the OK button to save the workstation in the database and close the window.
¶ Click the Cancel button to close window without saving the workstation in the database.
Displaying a List of Workstations
To display a list of workstations in the database:
1. In the tree view of the Job Scheduling Console, expand the scheduler engine button.
2. Expand the branches below the scheduler until you see the button for the workstation list
you want to run. For information about creating workstation lists, see “Creating a List of
Workstations” on page 192.
3. Select the workstation list button.
4. Right-click the workstation list button and select Load List from the pop-up menu. The
list results are displayed in the right pane of the Job Scheduling view.
Displaying a Workstation
To display a workstation in the database:
1. Run a list of workstations that contains the workstation you want to display. See
“Displaying a List of Workstations” on page 255 for more information.
2. In the list results, double-click the workstation you want to display or right-click the
workstation and select Properties from the pop-up menu.
This opens the workstation in the Properties - Workstation in Database window. For
information about this window, see “Creating a Workstation” on page 251.
3. Click OK or on Cancel to close the window.
Modifying a Workstation
To modify a workstation in the database:
1. Run a list of workstations that contains the workstation you want to display. See
“Displaying a List of Workstations” on page 255 for more information.
2. In the list results, double-click the workstation you want to modify or right-click the
workstation and select Properties from the pop-up menu.
The Properties - Workstation in Database window is displayed.
3. Make your changes in the Properties - Workstation in Database window. For information
about this window, see “Creating a Workstation” on page 251.
4. When you have finished:
¶ Click OK to save the workstation in the database and close the window.
¶ Click Cancel button to close the Properties - Workstation in Database window
without saving the workstation in the database.
Deleting Workstations
To delete workstations in the database:
1. Run a list of workstations that contains the workstation you want to delete. See
“Creating a Workstation” on page 251 for more information.
2. In the list results, do one of the following:
¶ To delete one workstation, right-click the workstation.
¶ To delete multiple workstations in a range, hold down the Shift key, click the first
and last workstations in the range, then right-click one of the selected workstations.
¶ To delete multiple workstations that are not in a range, hold down the Ctrl key, click
each workstation, then right-click one of the selected workstations.
3. Choose Delete from the pop-up menu. A confirmation message is displayed for each
workstation.
19. Managing
Workstations
operation.
Creating a Workstation by Copying Another Workstation
To create a new workstation in the database using a copy of another workstation:
1. Run a list of workstations that contains the workstation you want to copy. See
“Displaying a List of Workstations” on page 255 for more information.
2. In the list results, right-click the workstation you want to copy and select Create
another from the pop-up menu.
This displays a copy of the workstation in the Properties - Workstation in Database
window.
3. Change the name in the Workstation name text box to the name of the new
workstation.
4. Make other changes as needed to define the new workstation. For information about the
Properties - Workstation in Database window, see “Creating a Workstation” on page 251.
5. When you have finished:
¶ Click OK to save the workstation in the database and close the window.
¶ Click Cancel to close the window without saving the workstation in the database.
If a job stream is defined on a workstation class, each job added to the job stream must be
defined either on a single workstation or on the exact same workstation class that the job
stream was defined on.
Creating a Workstation Class
To create workstation classes in the database, you use the Properties - Workstation Class
window.
1. In the Name text box, enter the name of the workstation class. The name must start with
a letter and can contain alphanumeric characters, dashes, and underscores. For
non-expanded databases, it can contain up to eight characters. For expanded databases, it
can contain up to 16 characters.
Note: Workstation class names must be unique and cannot be the same as workstation
and domain names.
2. Select Workstations in the left pane of the Properties - Workstation Class window. The
Workstations page is displayed.
Workstations Page
19. Managing
Workstations
¶ click Cancel to close the window without saving the workstation class in the database.
Displaying a List of Workstation Classes
To display a list of workstation classes in the database:
1. In the tree view of the Job Scheduling Console, expand the scheduler button.
2. Expand the branches below the scheduler until you see the button for the workstation
class list you want to run. See “Creating a List of Workstation Classes” on page 193 for
information about creating workstation class lists.
3. Select the workstation class list button.
4. Right-click the workstation class list button and select Load List from the pop-up menu.
The list results are displayed in the right pane of the Job Scheduling Console.
To do this, in the tree view of the Job Scheduling Console, right-click the scheduler engine
button and select New Domain from the pop-up menu. The Properties - Domain window is
displayed.
Displaying a Domain
To display a domain in the databases:
1. Run a list of domains that contains the domain you want to display. See “Displaying a
List of Domains” for more information.
2. In the list results, double-click the domain you want to display or right-click the domain
and select Properties from the pop-up menu.
This opens the domain in the Properties - Domain window. For information about this
window, see “Creating a Domain” on page 261.
3. Click OK or on Cancel to close the window.
Managing Users
The users for whom Workload Scheduler will launch jobs must be defined in the database.
This is required for Windows NT users only.
Creating a User
To create users in the database, you use the Properties - NT User window. To do this, in the
tree view of the Job Scheduling Console, right-click the scheduler engine button and select
New User from the pop-up menu. The Properties - NT User window is displayed
Displaying a User
To display a user in the database:
1. Run a list of users that contains the user you want to display. See “Displaying a List of
Users” on page 264 for more information.
2. In the list results, double-click the user you want to display or right-click on the user and
select Open from the pop-up menu.
This opens the user in the Properties - NT User window. For information about the
Properties - NT User window, see “Creating a User” on page 263.
3. Click OK or on Cancel to close the window.
Modifying a User
To modify a user in the database:
1. Run a list of users that contains the user you want to modify. See “Displaying a List of
Users” on page 264 for more information.
2. In the list results, double-click the user you want to modify or right-click on the user and
select Open from the pop-up menu.
This opens the user in the Properties - NT User window.
3. Make your changes. For information about the Properties - NT User window, see
“Creating a User” on page 263.
4. When you have finished:
¶ Click OK to save the user in the database and close the window.
¶ Click Cancel to close the window without saving the user in the database.
Managing Calendars
A calendar is a list of scheduling dates defined in the scheduler database. Assigning a
calendar run cycle to a job stream causes that job stream to be run on the days specified in
the calendar. Since a calendar is defined to the scheduler database, it can be assigned to
multiple job streams.
You can create as many calendars as required to meet your scheduling needs. For example:
Table 98. Example Calendars
This calendar ... Could contain ...
PAYDAYS A list of pay dates
MONTHEND A list of month ending dates
HOLIDAYS A list of your company’s holidays
If you decide to use your own freedays calendar for a particular job stream, the redefined
When you do not specify a freedays calendar for the job stream, then HOLIDAYS is used,
if available.
Creating a Calendar in the Database
To create calendars in the database, you use the Properties - Calendar window. To do this, :
1. In the tree view of the Job Scheduling Console, right-click the scheduler button and
select New Calendar from the pop-up menu. The Properties - Calendar window is
displayed.
2. In the Name field, specify the name of the calendar. The name must start with a letter
and can contain alphanumeric characters, dashes, and underscores. The name can
contain up to eight characters.
Note: You cannot use Workload Scheduler keywords (for example, freedays and
schedule).
3. In the Description field, enter a description of the calendar.
4. Click Define Calendar to add dates to the calendar. The Monthly Yearly Calendar
window is displayed, as shown in the next figure.
5. Select Monthly or Yearly in the left pane of the window to view a monthly or yearly
calendar. Use the arrow buttons above and below the calendar to change the month and
year.
6. To add a specific date to the calendar, click the date in the calendar view.
7. To add a specific day of the month, select Day of Month from the Select menu. The
Day of Month window is displayed.
8. To add a day of the month by number, select the day number in the Day drop-down
list. To add the last day of the month, select the Last Day of Month option.
9. Select start and end dates for the calendar by selecting the month and year from the
Start and End drop-down lists. The days you specified are selected for every month in
this range.
10. Click OK to close the Day of Month window and select the dates. Click Cancel to
close the window without selecting the dates.
11. Click OK to close the Monthly Yearly Calendar window and add the dates to the
calendar. Click Cancel to close the window without adding the dates to the calendar.
12. When you have finished:
¶ Click OK to close the Properties - Calendar window and save the new calendar in
the database.
¶ Click Cancel to close the window without saving the calendar in the database.
4. In the Workstation field, enter the name of the workstation or workstation class on
which the resource is used.
5. In the Resource field, enter the name of the resource.
6. In the Quantity field, enter the number of available resource units.
Displaying a Resource
To display a resource in the database:
2. In the Name field, enter the name of the prompt. The name must start with a letter and
can contain alphanumeric characters, dashes, and underscores. The name can contain up
to eight characters.
3. In the Text field, enter the text of a prompt.
The default behavior of a prompt is to display a message and wait for a reply. If the
string begins with a colon (:), the message is displayed but no reply is necessary. If the
string begins with an exclamation mark (!), the message is not displayed but it requires a
reply. You can include backslash n (\n) within the text to create a new line.
4. When you have finished:
¶ Click OK to close the window and save the new prompt in the database.
¶ Click Cancel to close the window without saving the prompt in the database.
The Name and Text columns specify the name and text content of the prompts.
Displaying a Prompt
To display a prompt in the database:
1. Run a list of prompts that contains the prompt you want to display. See “Displaying a
List of Prompts” for more information.
2. In the list results, double-click the prompt you want to display or right-click the prompt
and select Open from the pop-up menu.
This opens the prompt in the Properties - Prompt window. For information about this
window, see “Creating a Prompt” on page 274.
3. Click OK or on Cancel to close the window.
Modifying a Prompt in the Database
To modify a prompt in the database:
1. Run a list of prompts that contains the prompt you want to modify. See “Displaying a
List of Prompts” for more information.
2. In the list results, double-click the prompt you want to modify or right-click the prompt
and select Open from the pop-up menu.
This opens the prompt in the Properties - Prompt window.
3. Make your changes. For information about this window, see “Creating a Prompt” on
page 274.
4. When you have finished:
¶ Click OK to save the prompt in the database and close the window.
¶ Click Cancel to close the window without saving the prompt in the database.
Managing Parameters
Parameters are useful to substitute values into your jobs and job streams. Since parameters
are stored in the Workload Scheduler database, all jobs and job streams that use the
particular parameter are updated automatically when the value changes. For scheduling, a
parameter can be used as a substitute for all or part of:
¶ File dependency path names
¶ Text for prompts
¶ Logon, command, and script file names
When using a parameter in a job script, the value is substituted at run time. In this case, the
parameter must be defined on the workstation where it will be used. Parameters cannot be
used when scripting Extended Agent jobs.
Note: Be careful when renaming a parameter because it might be part of a dependency for a
job scheduler object in the database. If this is the case, and you rename it, any action
you perform that refers to the old name will return an error.
Creating a Parameter
To create parameters in the database , you use the Properties - Parameter window.
3. In the Name field, enter the name of the parameter. The name must start with a letter
and can contain alphanumeric characters, dashes, and underscores. The name can contain
up to eight characters.
4. In the Value field, enter the value assigned to the parameter. Do not include the names
of other parameters.
5.
The Name and Value columns show the names and values of the parameters.
Displaying a Parameter
To display a parameter in the database, follow these steps:
1. Run a list of parameters that contains the parameter you want to display. See “Displaying
a List of Parameters” for more information.
2. In the list results, double-click the parameter you want to display or right-click the
parameter and select Open from the pop-up menu.
You can create groups to organize your lists. After installation there are a default set of basic
plan lists in a group named Default Plan Lists.
Creating a Group for Plan Lists
To create a group for plan lists:
1. In the Job Scheduling view, expand the scheduler engine button.
2. From the scheduler branch, highlight the group you want to contain this list.
3. Click Create a Group of Lists in the toolbar or right-click the scheduler engine button
and select Create Group from the pop-up menu.
To create a group in an existing group, select the group and click Create a Group of
Lists in the toolbar or right-click the existing group button and select Create Group
from the pop-up menu.
The Properties - Group of Lists window is displayed.
4. In the Name field, enter the name of the list group. The name can contain up to 40
characters, starting with a letter.
5. Click OK to close the window and save the new group.
Creating a Plan List of Workstations
To create a plan list that displays workstations:
1. In the Job Scheduling view, expand the scheduler engine button.
2. From the scheduler branch, highlight the group you want to contain this list.
General Page
Use the information in Table 100 to create the list and filter the results.
Table 100. Properties - Job Stream Instance List General Information
In this area ... Enter this information ...
Name A name for the list.
Select Time Restrictions in the left pane. The Time Restrictions page is displayed.
Figure 161. Properties - Job Stream Instance List Time Restrictions Page
Dependencies Page
For example, to display all job streams with a file dependency, enter an asterisk (*) in the
File Dependency / File Name field.
To display all job streams with both a file and a prompt dependency, enter an asterisk (*) in
the File Dependency / File Name field and in the Prompt Dependency / Prompt Name
field.
Note: In this case, only job streams with both a file and a prompt dependency are
displayed. Job Streams with only prompt dependencies or only file dependencies are
not displayed.
Use the information in Table 102 to define the list of jobs from the plan.
Table 102. Properties - Job Stream Instance List Dependency Information
In this area ... Enter this information ...
Job/Job Stream Dependency The name of a job or job stream dependency.
In the Workstation field, specify the name of a workstation.
In the Job Stream field, specify the name of a job stream.
In the Job field, specify the name of a job.
Resource Dependency The name of a resource dependency.
In the Workstation field, specify the name of a workstation.
In the Resource field, specify the name of a resource.
File Dependency The name of a file dependency.
In the Workstation field, specify the name of a workstation.
In the File Name field, specify the name of a file.
Prompt Dependency The name of a prompt dependency.
In the Name field, specify the name of a prompt.
In the Prompt Number field, specify the number of a prompt.
Use the information in Table 103 to create the list and filter the results.
Table 103. Properties - Job Instance List General Information
In this area ... Enter this information ...
Name A name for the list.
Period Refresh Options Select the Periodic Refresh check box if you want the list results
refreshed automatically and specify a refresh interval in seconds in the
Period (secs) text box.
Select Time Restrictions in the left pane. The Restrictions page is displayed.
Use this window to define a list of jobs from the plan based on dependency types. Only job
instances with the specified dependencies are displayed. Note that all the fields in this
window act as filters, so that all fields specified must be valid for a job stream to be chosen
for display.
For example, to display all jobs with a file dependency, enter an asterisk (*) in the File
Dependency / File Name field.
To display all jobs with both a file and a prompt dependency, enter an asterisk (*) in the
File Dependency / File Name field and in the Prompt Dependency / Prompt Name field.
Note: In this case, only jobs with both a file and a prompt dependency are displayed. Job
instances with only prompt dependencies or only file dependencies are not displayed.
Use the information in Table 105 to define the list of jobs from the plan.
Table 105. Properties - Job Instance List Dependency Information
In this area ... Enter this information ...
Job/Job Stream Dependency The name of a job or job stream dependency.
In the Workstation field, specify the name of a workstation.
In the Job Stream field, specify the name of a job stream.
In the Job field, specify the name of a job.
Resource Dependency The name of a resource dependency.
In the Workstation field, specify the name of a workstation.
In the Resource field, specify the name of a resource.
Table 108 shows the commands that you can issue against a job instance in the plan.
Table 108. Job Instance Commands
Use this command ... To do this ...
Properties View or modify the properties of a job instance. This includes viewing,
adding, modifying, or deleting the dependencies and time restrictions
on the job instance.
Dependencies View, add, modify, or delete the predecessors of a job instance.
Hold Set a job instance priority to 0, the internal status to HOLD, and the
Job Schedule Console status to HELD.
Release Counteracts the Hold command. The Release command reverts a job
instance priority to what it was before the Hold command ran.
Browse Job Log Opens a read-only view of the job instance log.
Rerun Rerun a job instance.
Cancel Job Cancels the planned running of a job instance.
Kill Stops a job instance.
Confirm Forces the status of a job instance to SUCC or ABEND.
Release All Dependencies Releases all dependencies to this job instance.
Get Job Output View the STDLIST of a job instance that has completed running.
The toolbar in the job instance view contains two special buttons.
Table 109 describes the column headings in the table part of the List view.
Table 109. Job Instance List View Columns
This column ... Specifies ...
Job Name The name of the job instance.
Job Number For UNIX and MPE, this displays the process identification number
(PAID) of the job instance. For Windows NT, the job number is an
incremental number from the value found in the file nxtjobno in
TWShome.
Workstation (Job) The name of the workstation on which the job instance runs.
Job Stream The name of the job stream instance that owns this job instance.
Workstation (Job Stream) The name of the workstation on which the job stream instance runs.
Status The Job Scheduling Console status of the job instance. For more
information on job or job stream status refer to “Status Description and
Mapping” on page 387.
Internal Status The Workload Scheduler internal status of the job instance. For more
information on job or job stream status refer to “Status Description and
Mapping” on page 387.
Information Additional information about the job instance.
Run Options The run options of the job instance.
Priority The priority of the job instance. The priority can be from 0 to 101. A
priority of 0 stops the job instance from running.
Every Frequency The repeat rate for this job instance, in hours and minutes.
Start Time The date, time and time zone when this job instance is scheduled to
start running.
Est. Duration The estimated run time of the job instance.
Actual Time The actual start time of the job instance.
Elapse Time The actual duration of the job instance.
Deadline Time The date, time and time zone after which the job instance cannot begin
running.
Job Stream Dep. The number of job stream dependencies for each job instance.
Job Dep. The number of job dependencies for each job instance.
In the timeline window, the dark blue line represents the window of time a job instance can
start. A black bar at the end of the blue line represents the deadline time (UNTIL keyword).
The actual start time of the job instance is displayed by a black dot. A light blue bar within
the dark blue line represents the actual duration of the job instance. The start time, deadline
time, and duration time are also listed in the tabular window.
Table 110 describes the column headings in the table part of the Timeline view.
Table 110. Job Instance Timeline View Columns
This column ... Specifies ...
Name The name of the job instance.
Status The status of the job instance. For more information on job or job
stream status refer to “Status Description and Mapping” on page 387.
Started The actual start date and time of the job instance.
Runtime The actual duration of the job instance.
Start at The date and time of the planned start time for the job instance.
Duration The estimated duration time of the job instance.
Deadline The date and time of the deadline for the job instance.
General Page
Select Task in the left pane of the Properties - NT Script Instance window. The Task page is
displayed.
Note: The fields in this window change according to the type of job instance displayed.
Table 112. Properties - NT Script Instance Task Information
This area ... Specifies ...
Task Type The task type of the job instance.
UNIX Script Information about the UNIX script file:
Script Displays the path and filename of the UNIX script.
UNIX Command Information about the UNIX command:
Command Displays the path and filename of the UNIX
command.
NT Script Information about the Windows NT script file:
Script Displays the path and filename of the Windows NT
script.
NT Command Information about the Windows NT command:
Command Displays the path and filename of the Windows NT
command.
MPE Job File Displays information about the MPE Job File:
Job File Displays the filename, group, and account for this
MPE job file.
MPE User Job Displays information about the MPE User Job:
User Job Displays the filename, group, and account for this
MPE User Job.
Extended Agent Task Displays information about the extended agent task:
Task Displays the filename or command for this extended
agent task.
Select Time Restrictions in the left pane of the Properties - Job Instance window. The Time
Restrictions page is displayed.
Select Files in the left pane of the Properties - Job Instance window. The Files page is
displayed.
On both UNIX and Windows NT, the expression %p inserts the file name.
Entering notempty is the same as entering -s %p. If no qualifier is specified, the default
is -f %p.
To remove a file dependency for the job instance, select the file row in the list and click the
Delete from Table (X) button.
Select Prompts in the left pane of the Properties - NT Script Instance window. The Prompts
page is displayed.
To display ad hoc prompt dependencies, select Ad Hoc Prompt from the drop-down list in
the toolbar.
To display predefined prompt dependencies, select Predefined Prompt from the drop-down
list in the toolbar.
To remove a prompt dependency for the job instance, select the prompt row in the list and
click the Delete from Table (X) button.
Select Resources in the left pane of the Properties - NT Script Instance window. The
Resources page is displayed.
Predecessors Page
Table 117 describes the columns in the Predecessors page.
Table 117. Predecessors Page
This column ... Specifies ...
Job Stream The name of a predecessor job stream instance or the job stream that
owns the predecessor job.
Job The name of a predecessor job instance.
Workstation The workstation of the predecessor job or job stream.
Successors Page
Table 119 describes the columns in the Successors page.
Table 119. Successors Page
This column ... Specifies ...
Workstation The workstation to which the successor belongs.
Job Stream The job stream to which the successor belongs.
Job The name of the successor job.
Release Status The release status of the Internetwork predecessors. The possible states
are Released or Not Released.
Internal Status The Workload Scheduler internal status of the successor job.
You can change the way the view is displayed by using the following buttons in the toolbar.
Table 120. Impact View Options
Select this button ... To display this type of view ...
Radial
Left
Right
Up
Down
Displaying Dependencies
To display a dependency of a job instance, right-click the job instance and select
Dependencies from the pop-up menu. Any dependent job instances are displayed.
Only the first level of dependent job instances is displayed. If you want to display more than
one level of dependency, you must right-click each dependent job instance in turn, selecting
Dependencies from the pop-up menu each time.
Note: If you display dependencies for more than one job, then refresh the display, only the
first level of dependent job instances is displayed.
To reset the display in a separate window, right-click the job instance you want to use as the
root job instance and select Set As Root In New Frame from the pop-up menu.
Browsing the Job Log
A job instance log file is created for each job instance launched by Workload Scheduler. Log
files contain header and trailer banners, echoed commands, and errors and warnings. These
files can be used to troubleshoot problems when jobs run.
4. To rerun the job directly, click OK. Otherwise, add any additional options.
Table 122describes the commands that you can use on a job stream instance in the plan.
Table 122. Job Stream Instance Commands
Use this command ... To do this ...
Open Opens the job stream instance in the Job Stream Instance Editor.
Properties View or modify the properties of a job stream instance. This includes
viewing, adding, modifying, or deleting the dependencies and time
restrictions on the job stream instance.
Dependencies View, add, modify, or delete the predecessors of a job stream instance.
Hold Sets a job stream instance priority to 0, the internal status to hold, and
the Job Schedule Console status to held.
Release Counteracts the Hold command. The Release command reverts a job
stream instance priority to what it was before the Hold command ran.
Impact View View the predecessors and successors of job stream instance.
Cancel Cancels the planned running of a job stream instance.
Limit View or modify the job limit of a job stream instance. This is the
number of jobs that can run concurrently in the job stream instance.
Priority View or modify the priority of a job stream instance.
Release All Dependencies Releases all dependencies to this job stream instance.
Re-submit Re-submits the job stream instance under an alias name.
Submit Submits a predefined or ad hoc job into the plan as part of the selected
job stream instance. See “Submitting Jobs and Job Streams into the
Plan” on page 335.
Select for Monitoring Specify that the running of this job is to monitored by Tivoli Business
Systems Manager.
Deselect for Monitoring Specify that the running of this job is no longer to be monitored by
Tivoli Business Systems Manager.
In the timeline window, the dark blue line represents the window of time a job stream
instance can start. A black bar at the end of the blue line represents the deadline time
(UNTIL keyword). The actual start time of the job stream instance is displayed by a black
dot. A light blue bar within the dark blue line represents the actual duration of the job
stream. The start time, deadline time, and duration time are also listed in the tabular window.
The toolbar in the job stream instance Timeline view contains two special buttons:
Go to First Moves the timeline display to the start time and day offset
of the earliest job stream instance.
General Page
Select Time Restrictions in the left pane. The Time Restrictions page is displayed.
Files Page
On both UNIX and Windows NT, the expression %p, inserts the file name.
Entering notempty is the same as entering -s %p. If no qualifier is specified, the default
is -f %p.
You can change the way the view is displayed by using the following buttons in the toolbar.
Table 131. Impact View Options
Select this button ... To display this type of view ...
Radial
Left
Right
Up
Down
4. Select a new priority value from the drop-down list or click of the following buttons:
Table 132. Job Stream Instance Priorities
This button ... Sets the priority to ...
Hold 0
High 100
Go 101
Default Original value (see note)
Note: If a single job stream instance is selected, Default sets the priority to the original
value of the job stream instance at the start of the processing day. If multiple job
stream instances are selected, the priority of each job stream instance is set back
to what it was at start of the processing day.
This permits the job stream to run unless there are other prerequisites. For more information,
see:
¶ “Displaying and Changing the Properties of a Job Stream Instance” on page 319.
¶ “Changing the Job Limit of a Job Stream Instance” on page 331.
¶ “Changing the Priority of a Job Stream Instance” on page 331.
Re-submitting a Job Stream Instance
When you re-submit a job stream instance, a new job stream instance is created in the plan.
The new job stream instance is given an alias name.
4. Specify an alias name for the re-submitted job stream instance in the Alias field. If you
do not specify an alias, a name is generated by Workload Scheduler. For unexpanded
mode, Workload Scheduler starts with the first two characters of the original job stream
instance name followed by six random numbers. For expanded mode, the scheduler starts
with the first six characters of the original job stream instance name followed by ten
random numbers.
5. When you are finished:
¶ Click OK to re-submit the job stream instance and close the window.
¶ Click Cancel to close the window without re-submitting the job stream instance.
6. To change the properties of the re-submitted job stream, click Properties.... For
information about job stream instance properties, see “Displaying and Changing the
Properties of a Job Stream Instance” on page 319.
To deselect a job a job stream instance from monitoring by Tivoli Business Systems
Manager, right-click the job stream instance and select Deselect for Monitoring.
You can also submit ad hoc jobs to the plan. These are jobs that have not been defined in
the database. These jobs are created and submitted into the plan, but are never saved in the
database.
Submitting a Job Stream into the Plan
To submit a job stream that already exists in the database into the plan:
1. In the Job Scheduling view, expand the scheduler engine button.
2. Right-click the scheduler engine button and select Submit then Job Stream from the
pop-up menu.
The Submit Job Stream into Plan window is displayed.
3. Use the information in Table 133 to complete the fields in this window.
Table 133. Submit Job Stream into Plan Window
In this field ... Do this ...
Job Stream click the ellipsis to open a Find Job Stream window. This field is
completed automatically when you select a job stream using the
Find Job Stream window.
Workstation name This field is completed automatically when you select a job stream
using the Find Job Stream window.
Alias Specify an alias name for the submitted job stream instance. An
alias name is needed only if the plan contains a job stream instance
of the same name. If an alias name is necessary, and you do not
specify an alias, a name is generated by Workload Scheduler that
starts with the first two characters of the original job stream name
followed by six random characters.
4. To modify the properties of the submitted job stream, click Properties. For information
about job stream properties, see “Displaying and Changing the Properties of a Job
Stream Instance” on page 319.
If you submit the job from the scheduler engine pop-up menu, the job is submitted through a
default job stream instance named JOBS (see “Using a Default Job Stream”).
If you submit the job from the pop-up menu of a specific job stream instance, the job is
submitted through that specific job stream instance (see “Using a Specific Job Stream” on
page 337).
Figure 196. Submit Job into Plan Window - Default Job Stream
General Page
Requires Confirmation Select this option to indicate that job completion must be confirmed by
the operator.
Select Task in the left pane of the window. The Task page is displayed.
The Task page is different for each type of job and operating system. These fields display
the task type, path, and the command or script file referenced by the job. These fields are
read only.
Select Time Restrictions in the left pane of the window. The Time Restrictions page.
Select Files in the left pane of the window. The Files page is displayed
Select Prompts in the left pane of the window. The Prompts page is displayed.
Select Resources in the left pane of the window. The Resources page is displayed.
Select Predecessors in the left pane of the window. The Predecessors page is displayed.
Predecessors Page
Adding a Predecessor
To add a predecessor for the job instance:
1. Click the Add Row button. This creates a new row in the list of predecessors.
2. To specify a predecessor job stream, double-click in the text box in the Job Stream
column and click Find to locate and insert the name of a job stream.
3. To specify a predecessor job, double-click in the text box in the Job column and click
Find to locate and insert a resource name.
To submit a job that is defined in the database into a job stream instance, you use the job
stream instance popup menu or the scheduler engine popup menu.
2. In the Task Type field, select the task type of the ad hoc job.
3. Click OK to specify the properties of this submitted ad hoc job.
The Properties - Job Instance General page is displayed.
Requires Confirmation Select this option to indicate that ad hoc job completion must be
confirmed by the operator.
Select Task in the left pane of the window. The Task page is displayed.
The Task view is different for each task type. To complete the fields and select options on
this page:
Table 144. Task Types
For this task type ... Go to page ...
UNIX Script and NT Script 352
UNIX Command and NT Command 353
MPE Job File 353
MPE User Job 353
Extended Agent 353
SAP Job 353
Specify the name of the file the ad hoc job runs. Enter the file name and any options and
arguments. For non-expanded databases, the field can contain up to 255 characters. For
expanded databases, it can contain up to 4095 characters.
For Windows NT ad hoc jobs, include the file extensions. Universal Naming Convention
(UNC) names are permitted. Do not specify files on mapped drives.
If spaces or special characters are included, other than slashes (/) and backslashes (\), the
entire string must be enclosed in quotes (″).
If the file name contains spaces, specify the name in another file that does not have spaces
in its name and use the second file’s name in this field.
A parameter can be used for all or part of the field and multiple parameters are permitted.
A parameter can be used for all or part of the field and multiple parameters are permitted.
Extended Agent
In the Task field, enter the XAgent script path or file name or the XAgent command for this
job.
SAP Job
For task type SAP Job, refer to the Tivoli Workload Scheduler Extended Agent for SAP/R3
User’s Guide for information about defining the task.
Select Time Restrictions in the left pane of the window. The Time Restrictions page is
displayed.
Select Files in the left pane of the window. The Files page is displayed.
Files Page
Select Prompts in the left pane of the window. The Prompts page is displayed.
Select Resources in the left pane of the window. The Resources page is displayed
Select Predecessors in the left pane of the window. The Predecessors page is displayed.
Predecessors Page
Adding a Predecessor
To add a predecessor for the ad hoc job instance:
1. Click the Add Row button. This creates a new row in the list of predecessors.
2. To specify a predecessor job stream, double-click in the text box in the Job Stream
column and click Find to locate and insert the name of a job stream.
3. To specify a predecessor job, double-click in the text box in the Job column and click
Find to locate and insert a resource name.
os_wkstat
For descriptions of the field values, see “Displaying a List of Workstations in the Plan”
on page 361.
3. You can change the Limit and Fence values by entering new values in the fields. For
more information, see “Changing the Job Limit of a Workstation in the Plan” and
“Changing the Job Fence of a Workstation in the Plan” on page 364.
Note: To start all the workstations in a domain, refer to “Starting the Workstations in a
Domain” on page 366.
Note: To stop all of the workstations in a domain, refer to “Stopping the Workstations in a
Domain” on page 366.
Linking a Workstation Instance
To link a workstation instance, right-click the workstation you want to stop and select Link
from the pop-up menu.
Unlinking a Workstation Instance
To unlink a workstation instance, right-click the workstation you want to stop and select
Unlink from the pop-up menu.
Note: To unlink all of the workstations in a domain, refer to “Unlinking the Workstations in
a Domain” on page 366.
Note: To start individual workstations, see “Starting a Workstation Instance” on page 364.
Stopping the Workstations in a Domain
To stop Workload Scheduler running on all of the workstations in a domain:
1. Run a list of domains that contains the domain you want to stop. See “Displaying a List
of Domains in the Plan” on page 365 for more information.
2. In the list results, right-click the domain you want to stop.
3. Select Stop Workstations from the pop-up menu.
Note: To stop individual workstations, see “Stopping a Workstation Instance” on page 365.
Linking the Workstations in a Domain
To link all of the workstations in a domain:
1. Run a list of domains that contains the domain you want to link. See “Displaying a List
of Domains in the Plan” on page 365 for more information.
2. In the list results, right-click the domain you want to link.
3. Select Link Workstations from the pop-up menu.
Note: To link individual workstations, see “Linking a Workstation Instance” on page 365.
Unlinking the Workstations in a Domain
To unlink all of the workstations in a domain:
1. Run a list of domains that contains the domain you want to unlink. See “Displaying a
List of Domains in the Plan” on page 365 for more information.
2. In the list results, right-click the domain you want to unlink.
3. Select Unlink Workstations from the pop-up menu.
3. Click Find and use the Find window to select the name of the new domain manager
workstation. The new domain manager must be a member of the domain and it must be
a fault-tolerant agent with Full Status and Resolve Dependencies selected.
Table 155 describes the contents of the columns in the resource display.
Table 155. Resource Dependencies Status
This column ... Specifies ...
Name The name of the resource.
Workstation The name of the workstation.
Status The status of the resource. This is one of:
Available The resource has units available.
Not Available The resource has no units available.
Unknown The status of the resource is unknown.
Quantity Defined The total number of units defined for the resource.
Quantity Available The number resource units that are not in use.
In Use The number of resource units that are currently in use.
Holders The names of job and job stream instances that require units of the
resource and the number of units required.
In the Job Scheduling view, the Common Default Plan Lists group appears at the bottom of
the job scheduling tree. The group provides two predefined lists, one for job instances and
one for job stream instances. Unlike similar lists for specific engines, these lists display all
the job and job stream instances that exist in all the engines to which the Job Scheduling
Console is connected. The group always appears in the Job Scheduling tree, regardless of the
number of connections that you might have.
Like all default lists, the two common plan lists are defined with no filters. If you want to,
you can create additional common plan lists that use particular filters, such as a particular
status or a subset of all the engines. However, common plan lists are limited to job and job
stream instances. Common plan lists provide fewer details about the job and job stream
instances than engine-specific plan lists. If you are connected to a single engine, or if you
want to see more information about the instances of a specific engine, you should use the
plan lists for that engine.
—EITHER—
Click Apply to display the list results immediately, then click OK to close the window.
—OR—
Click OK to close the window. The new list definition is added to the Common Default
Plan Lists group in the Job Scheduling view. Right-click the list in the Job Scheduling
view and select Open. The list results are displayed in the right hand pane.
Note: To display the list at a later date, double-click it in the scheduling tree.
—EITHER—
Click Apply to display the list results immediately, then click OK to close the window.
—OR—
Click OK to close the window. The new list definition is added to the Common Default
Plan Lists group in the Job Scheduling view. Right-click the list in the Job Scheduling
view and select Open. The list results are displayed in the right hand pane.
Note: To display the list at a later date, double-click it in the scheduling tree.
—EITHER—
Click Apply to display the list results immediately, then click OK to close the window.
—OR—
Click OK to close the window. The new list definition is added to the Common Default
Plan Lists group in the Job Scheduling view. Right-click the list in the Job Scheduling
view and select Open. The list results are displayed in the right hand pane.
You can set the tracing facility by customizing the TRACELEVEL and TRACEDATA
variables. These variables are located in the following files:
Table 159. Trace Variable Location by Operating System
For this operating system ... The file is ...
Microsoft Windows NT, 2000 ..\bin\java\NTconsole.bat
Microsoft Windows 98, ME ..\bin\java\console.bat
AIX ../bin/java/AIXconsole.sh
HP-UX ../bin/java/HPconsole.sh
SUN Solaris ../bin/java/SUNconsole.sh
Linux ../bin/java/LINUXconsole.sh
To customize either variable, open the file in editing mode and set the variable to a value
ranging from 0 to 3. Values enable you to tune the tracing facilities to report the type and
detail of data that best fits your needs.
TRACEDATA enables you to choose what type of data flow the tracing facility must record.
You can set it to record the contents of the Job Scheduling Console beans or the data
structures exchanged between the Job Scheduling Console and the Workload Scheduler for
z/OS Connector. The following table displays what each values does:
The various combinations of values for TRACELEVEL and TRACEDATA give you the
maximum flexibility in terms of information provided by the log file. However, it is
important to point out that the combination of values of 2 or greater for TRACELEVEL and
of 1 or greater for TRACEDATA can be quite heavy for system performance: they can slow
program operation and generate very big log files.
Tracking of error conditions is active by default (TRACELEVEL is already set to 0). You
can also set TRACELEVEL to -1 to force the tracing facility not to create a log file at all.
The log file is named JSCONSOLE.LOG and is placed in the DAT subdirectory of the
directory hosting the Job Scheduling Console files.
By default, the maximum size of JSCONSOLE.LOG can be 3 MB. When this limit is
reached, the tracing facility creates an additional log file. The tracing facility can create up
to ten log files for a total of 30 MB. You can, however, change this by using the advanced
customization options described in the next section.
where:
traceFileMaxLen
Defines the maximum size, in bytes, that the log file can be. When the file reaches this
size, it is renamed and a new log file is created. The value is an integer of your choice.
traceFileMaxNum
Defines the maximum number of log files that can be present on disk during each
instance of the Job Scheduling Console. When this number is exceeded, the older files
are replaced first. This includes only the files created during the current session of the
Job Scheduling Console. You have to manually delete the files stored during previous
sessions. The value is an integer of your choice.
printTimeDate
Specifies if the trace calls write date and time information in the log file. The value can
be True or False.
Use the other options to determine what type of information you want included in the trace
file.
Job stream PST_SCHEDULE1 is not time zone enabled. To get this job stream to run every
weekday morning, you must schedule it to run Sunday through Thursday, and you must
specify ″carryforward″. Without carryforward, the jobs would never run, since the
fault-tolerant agent would be initialized at 0300 every morning (assuming an EST master
with a Workload Scheduler start of day of 0600). Job stream PST_SCHEDULE2 is time
zone enabled. When the EST master initializes the PST fault-tolerant agent at 0300, it starts
the job stream the same day at 0330.
Time zone enabling also has an effect on eastern fault-tolerant agents when scheduling from
western masters. For example, consider the following two job streams for an EST
fault-tolerant agent and a PST master with an 0600 start of day.
Job stream EST_SCHEDULE1 is not time zone enabled. For this job stream to run every
weekday morning, you must schedule it to run Sunday through Thursday. Specify
carryforward and +1DAY for the AT time. Carryforward is needed for the +1DAY
specification. Without the +1DAY specification, the job stream would launch immediately
after initialization from the western master at 0900. Job stream EST_SCHEDULE2 is time
zone enabled. When the eastern fault-tolerant agent is initialized at 0900, it runs the job
stream at 0800 the next day.
Once enabled, time zones can be specified in the Job Scheduling Console or composer for
start and deadline times within jobs and job streams. For conman, the following commands
now accept time zone parameters where AT or UNTIL times are used:
¶ submit job
¶ submit docommand
¶ submit file
¶ submit schedule
¶ addep schedule
¶ addep job
¶ addep schedule
¶ addep job
¶ ″rurun job; from″ option
Time zones are disabled by default on installation or update of the product. If the timezone
enable entry is missing from the globalopts file, time zones are disabled.
For information about job and job stream status for Workload Scheduler for z/OS, refer to
Tivoli Workload Scheduler for z/OS Controlling and Monitoring the Workload.
Status Overview
There are two types of status:
Job Scheduling Console status
This is a subset of internal status and is common for both Workload Scheduler and
Workload Scheduler for z/OS.
Internal Status
This refers to the Workload Scheduler internal or engine status for the job or job
stream. The internal status messages are unique to the scheduler.
Job Status
This section describes the job status for both Job Scheduling Console and Workload
Scheduler internal status.
Mapping
Table 160. Job Scheduling Console Job States
This job status ... Means that ...
WAITING The job stream instance is waiting for its dependencies to be resolved.
READY The dependencies of the job stream instance have been resolved and
the job stream instance is ready to run.
RUNNING The job stream instance is running.
SUCCESSFUL The job stream instance completed successfully.
ERROR The job stream instance has stopped running with an error.
CANCELED The job stream instance was canceled.
HELD The job stream instance was interrupted.
UNDECIDED The job stream status is currently being checked.
BLOCKED The job stream instance was blocked due to unfulfilled dependencies.
Mapping
Status Mapping
This section provides a table of how Job Scheduling Console status maps to Workload
Scheduler internal status for jobs and job streams.
Job Status Mapping
Table 164 describes how Job Scheduling Console status correlates to Workload Scheduler
internal status for jobs.
Table 164. Job Status Mapping
This console status ... Maps to this Workload Scheduler internal status ...
WAITING ADD, PEND, WAIT, WAITD, INTRO, HOLD
READY READY
RUNNING EXEC, SUCCP, ABENP
SUCCESSFUL SUCC
ERROR ABEND, FAIL
The list below includes all the messages displayed by the base Job Scheduling console.
GJS0000E There was an unidentified problem when connecting
GJS0001E Cannot load job stream list
GJS0002E Cannot load plan view
GJS0003E Cannot load resource list
GJS0004E Cannot load resource plan view
GJS0005E Cannot load workstation list
GJS0006E Cannot open job stream instance
GJS0007E Cannot update job stream
Messages
GJS0010E Cannot open the Resource Editor
GJS0012E Cannot load the job stream
GJS0013E Cannot load the definition of resource availability
GJS0014E Cannot load the job stream instance
GJS0015E Cannot save the job stream
GJS0016E Cannot save the resource
GJS0017E Cannot add this dependency
GJS0027E Cannot save the workstation
GJS0028E Class Cast Exception
GJS0029E There is a problem with your job scheduling engine
GJS0030E Cannot close the window
GJS0031E Cannot add Job Dependency
Messages
All Job Scheduling Console messages that contain the GJSQ prefix refer to Workload
Scheduler for z/OS error conditions. The explanation of each message displays a specific
Workload Scheduler for z/OS message. These messages are identified by the EQQ prefix.
For information about these messages, refer to the Tivoli Workload Scheduler for z/OS
Messages and Codes book.
C
Calendar
A definition of workdays, free days, and holidays. The scheduler uses the calendar combined with run cycles to
determine on which days to run the job stream. In the GUI, you can assign a calendar to a job stream; however,
you must use the ISPF panes to create or modify calendars in the database.
D
Database
A collection of data that is fundamental to a system. The database for each engine contains calendars, JCL
variable tables, job streams, operator instructions, periods, resources, and workstations. In the Job Scheduling
Console, you can define and modify job streams, resources, and workstations. This information is stored in the
database of the engine and is used to generate instances for the plan.
Deadline
The time by which the job or job stream must be completed. The deadline is your estimate, based on your
experience in running the job or job stream. In the timeline, the deadline is represented by the black border at the
right end of the navy blue activity bar.
Dependency
A relationship between two jobs in which the first job must be completed before the second can begin. When you
create a job stream in the database, you define the dependencies between jobs
DLF
Data Lookaside Facility. The z/OS component that manages Hiperbatch objects.
Duration
The time you expect the job to take to complete. In the Timeline view of jobs in the database, the duration is
represented by a light blue bar at the center of the activity bar or by a light blue diamond.
Glossary
E
Earliest start time
The time before which the job or job stream cannot start. The earliest start time is your estimate, based on your
experience in running the job or job stream. The job or job stream can, however, start after the time you specify
as long as all other dependencies are satisfied. In the timeline, the start time is represented by the beginning (left
edge) of the navy blue activity bar. For job instances, the start time that the scheduler calculates is represented by
a light blue bar. See also actual start time and planned start time.
External job
A job from one job stream that is a predecessor for a job in another job stream. An external job is represented by
a place holder button in the Graph view of the job stream. When you delete an external job either from the
database or the plan, the job stream that includes it as a predecessor skips it as if it did not exist, and the
scheduler logs the error.
H
Hiperbatch
The z/OS facility that stores VSAM and QSAM data in Hiperspace for access by multiple jobs. The facility can
significantly reduce the run time of certain batch streams that access VSAM and QSAM.
J
Job
A unit of work in a job stream that is processed at a workstation. It usually includes all necessary computer
programs, linkages, files, and instructions to the operating system. When you create a job in the database, you
also define its dependencies on predecessor jobs and its time restrictions, such as the estimated start time and
deadline. The type of job determines the type of target workstation on which it can run: JCL jobs consist of JCL
statements and run on computer workstations. Started task jobs start or stop started tasks and run on computer
workstations. Printer jobs print the output of a predecessor job and run on printer workstations. General jobs
include activities other than printing and processing, such as manual activities and run on general workstations.
Setup jobs require preparation of a set of JCL statements for a JCL or started task job and run on general
workstations. Write-to-operator (WTO) jobs consist of an operator instruction displayed on the system console
and run on general workstations. Fault tolerant workstation jobs are used to run jobs from Tivoli Workload
Scheduler. They require fault tolerant workstations. Fault tolerant workstation jobs can have neither a general job
as a predecessor nor a printer job as a successor. See also job instance.
Job instance
A job scheduled for a specific run date in the plan. See also job.
Job status
See status
Job stream
A sequence of jobs, including the resources and workstations that support them, and scheduling information. The
dependency of one job on the completion of another determines the sequence of the jobs. The scheduling
information, such as run cycles and a calendar, determines when and how often the job stream is run. See also
job stream instance.
Logical resource
See resource.
P
Plan
A detailed plan of system activity that covers a period of at least one minute and not more than 21 days. It
typically covers one or two days. The plan encompasses all job and job stream instances and the resources and
workstations involved in running them. All job streams for which you have created run cycles are automatically
scheduled and included in the plan. Contrast with database.
Predecessor
A job that must be completed before jobs that are dependent on it can begin. Contrast with successor.
R
Resource
Any type of limited resource, such as tape drives, communication lines, databases, or printers, that is needed to
run a job. You designate when a resource is available, in what quantities, and by which logical workstations the
resource can be used. This information helps determine when job stream instances are scheduled to run. In the
Job Scheduling Console, resources are also called logical resources.
Resource availability
Fixed times when the job can use a resource. You define conditions, similar to run cycles, that generate the
calendar days when a resource is available. You can also define conditions for when a resource is not available.
Run cycle
A specification of the days that a job stream is scheduled to run. It can be either rule-based or offset-based:
Rule-based: Includes a rule, such as, the first Friday of March or the second workday of the week Offset-based:
Includes a user-defined period and an offset, such as, the 3rd day in a 90-day period. See also exclusionary run
Glossary
cycle.
S
Status
The state of a job or job stream instance. It can be one of the following:
Arriving The instance is waiting for input to arrive (jobs only).
Canceled The instance has been deleted from the plan.
Error The instance has ended in error.
Interrupted The instance has been interrupted (jobs only).
Pending predecessor
The job stream instance is waiting for a predecessor to be completed (job streams only).
Ready The instance is ready to start. All predecessors are complete (jobs only).
Ready-nonreporting workstation
The job instance is ready to start. All predecessors, except a predecessor at a nonreporting
workstation, are complete (jobs only).
Running The job has started.
Successful The instance has been completed successfully.
Undecided The status of the instance is not known.
Waiting The instance is waiting for a predecessor job to end.
V
Valid from, to dates
The interval for which a job stream is available for scheduling and can be run. The first and last date that a run
cycle is in effect.
W
Workstation
The logical machine on which a job runs. When you create a job, you identify at least one workstation on which
it will run. There are three types of workstations: Computer, Printer, General.
WTO
Write-to-operator. See also job.
Index
online xxix deleting a run cycle 244
ordering xxix deleting a user 266
deleting predecessors
job instance 309
job stream instance 328
dependency filter window
job stream instance 284, 288
C directory names, notation xxxiii
calendar 63, 73, 81, 111
displaying predecessors
creating 267
job instance 307
database list 269
job stream instance 327
deleting 269
displaying successors
modify 269
job instance 309
view properties 269
job stream instance 328
calendar run cycle 242
DLF attribute 75, 76, 175
cancelling a job instance 314
domain
cancelling a job stream instance 330
creating 261
changing number of resource units 370
database list 262
changing the job fence, workstation 364
deleting 263
E J
e-mail contact xxxi JCL 58, 111
earliest start time 88 job definition
enabling the time zone feature 386 adding to a job stream 227
environment variables, notation xxxiii properties 227
exclusive 71, 175 job fence, changing 364
external dependencies job instance
deleting 227 adding predecessors 308
external job 92 cancelling 314
adding to a job stream 226, 235 confirm 315
external job stream deleting predecessors 309
adding to a job stream 226, 234 displaying successors 309
holding 309
killing 314
modifying 297
predecessors 307
F release all dependencies 315
feedback about publications xxxi releasing 310
file dependency rerun 313
adding to a job 231 submitting into the plan 336
status 367 job instance properties
find calendar window 81 files 302
find workstations 63 prompts 304
finding objects in the plan 293 resources 306
follows dependency 236 time restrictions 300
freedays 81 job instances 55, 119, 123, 137, 175
from time 63, 73 job limit, changing for a workstation 363
job properties
files 231
prompts 232
resource 230
G time restrictions 229
globalopts file Job Scheduling view 75, 110, 175
time zone feature 386 job stream
graph view 113 adding run cycles 237
saving 247
submit into plan 335
job stream editor 113
job stream instance
H cancelling 330
hiperbatch 71, 75, 175 commands 316
holding a job instance 309 hold 316
holding a job stream instance 329 holding 329
holidays calendar 266 job limit 331
list view 318
modifying 319
plan list 316
priority 331
release 316
release all dependencies 316, 332
K
killing a job instance 314
O
occurrence 119
online publications xxx
operations 57, 58
L ordering publications xxxi
linking a workstation 365
linking workstations, domain 366
list view 138
job instance 294
job stream instance 318 P
listing domains in the plan 280 parallel server 58
listing file dependencies in the plan 291 parameter
listing job instances in the plan 284, 294 creating 276
listing job streams in the plan 281 database list 277
listing parameters in the database 277 deleting 278
listing prompts in the database 275 modifying 278
listing prompts in the plan 290 properties 277
listing resources in the database 272 path names, notation xxxiii
listing resources in the plan 289 plan 59, 119
listing workstations in the plan 279, 361 plan list
deleting 292
detaching 292
Index
modifying 292
plan lists 279
M planning on servers 58
manuals predecessor job 59
feedback xxix priority 81
online xxix prompt
ordering xxix creating 274
modifying a domain 263 deleting 276
modifying a job instance 297 listing 275
modifying a parameter 278 modifying 275
modifying a prompt 275 properties 275
modifying a resource 273 replying 369
modifying a run cycle 244 status 368
modifying a user 265 publications
modifying file dependencies feedback xxix
job instance 302 online xxix
job stream instance 322 ordering xxix
modifying prompt dependencies
job instance 304
job stream instance 324
R
ready 57, 58
release all dependencies
job instance 315 T
job stream instance 332 target workstation 83
releasing a job instance 310 task name 111
releasing a job stream instance 329 TCP/IP 59
replying to a prompt 369 tempsec 31
reporting attributes 66, 83, 163 time restrictions 88
rerunning a job instance 313 job 245
resource job stream 244
adding to a job 230 timeline view
changing units 370 job instance 296
creating 271 job stream instance 317
database list 272 Timeline view 104, 138
deleting 273 Tivoli Customer Support xxxii
modifying 273 to time 63, 73
properties 272 transport time 59
status 369 treat input as 75, 175
viewing plan properties 370
Resource Description database 175
resubmit a job stream instance 333
run cycle
adding to a job stream 237 U
calendar 242 unlinking a workstation 365
deleting 244 unlinking workstations, domain 366
modifying 244 user
simple 239 creating 263
weekly 240 deleting 266
listing 264
modifying 265
using plan lists 279
S
saving a job stream 247
scheduling 55, 58, 75, 175
search tool 73 V
security 31 variables, notation for xxxiii
setting priority viewing calendars in the database 269
job instance 297 viewing domain status 365
job stream instance 316 viewing domains in the database 262
shared 71, 175 viewing parameter properties 277
simple run cycle 239 viewing prompt properties 275
special resources 69 viewing prompt status 368
specifying job properties 227 viewing resource properties 272
start time 88, 144 viewing resource properties in the plan 370
started 57, 58, 59, 71 viewing resource status 369
starting a workstation 364 viewing the properties of a domain 262
starting workstations, domain 366 viewing the status of a workstation 362
status viewing users in the database 264
workstation 362
status of job stream 111
stopping a workstation 365
stopping workstations, domain 366
Index
SH19-4552-00