tivoli guide

Tivoli® Workload SchedulerJob Scheduling ConsoleUser’s GuideVersion 8.1 SH19-4552-00

Tivoli Workload Scheduler, Job Scheduling Console User’s Guide, Version 8.1

Copyright Notice

© Copyright IBM Corporation 1990, 2001. All rights reserved. May only be used pursuant to a Tivoli Systems Software LicenseAgreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. Nopart of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computerlanguage, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without priorwritten permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions ofany machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporationcopyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. The document isnot intended for production and is furnished “as is” without warranty of any kind. All warranties on this document are herebydisclaimed, 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 IBMCorporation.

Trademarks

IBM, Tivoli, the Tivoli logo, AIX, BookManager, Hiperbatch, OS/390, RACF, and z/OS are trademarks or registered trademarks ofInternational 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, orboth.

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 inall countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended toimply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or otherlegally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead ofthe referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, exceptthose expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents orpending patent applications covering subject matter in this document. The furnishing of this document does not give you any licenseto 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.

ISO 9001 CertificationThis product was developed using an ISO 9001 certified quality system. Certification has been awarded by BureauVeritas Quality International (BVQI) (Certification No. BVQI - 92086 / A).BVQI is a world leader in quality certification and is currently recognized by more than 20 accreditation bodies.

Contents

Figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviiWho 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

Part I. Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Tivoli Workload Scheduler for z/OS Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Planning Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Operator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Tivoli Workload Scheduler Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Planning Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Operator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Terminology Used in the Job Scheduling Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2. Installing Tivoli Job Scheduling Services . . . . . . . . . . . . . . . . . . . . 13Before Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Setting the Tivoli Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Installing from the Tivoli Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Installing from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

iiiTivoli Job Scheduling Console User’s Guide

Uninstalling Job Scheduling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Installing Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 3. Installing the Tivoli Workload Scheduler for z/OSConnector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Before Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17


Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Job Scheduling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Installing the Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Setting the Tivoli Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Installing from the Tivoli Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Installing from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Customizing the Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Creating Connector Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Authorization Roles Required for Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Managing Connector Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Uninstalling the Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22


Useful Framework Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 4. Installing the Tivoli Workload Scheduler Connector . . . . . . . . . 25Before Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25



Job Scheduling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Workload Scheduler Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Fault-tolerant Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Installing the Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Where to Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Setting the Tivoli Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Installing from the Tivoli Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Installing from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Customizing the Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Creating Connector Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Authorization Roles Required for Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Managing Connector Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Uninstalling the Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31


iv Version 8.1

Updating Workload Scheduler Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Useful Framework Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 5. Installing the Tivoli Job Scheduling Console. . . . . . . . . . . . . . . . . 33Before Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33



Installing on Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Installing on AIX and HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Updating AIXconsole.sh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Installing on Solaris and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Starting the Job Scheduling Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Uninstalling the Job Scheduling Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Uninstalling on Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Uninstalling on AIX, HP-UX, Solaris, and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 6. Working with the Job Scheduling Console . . . . . . . . . . . . . . . . . . . 41The Job Scheduling View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Using the Buttons of the Job Scheduling View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Working with Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Default Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

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

Part II. Using the Job Scheduling Console with Tivoli WorkloadScheduler for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 7. Managing Workstations in the Database . . . . . . . . . . . . . . . . . . . . . 55Creating a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

General Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Defining Open Time Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Managing Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

vTivoli Job Scheduling Console User’s Guide

Default Workstation Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Creating a List of Workstations in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Using Workstation Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 8. Managing Resources in the Database . . . . . . . . . . . . . . . . . . . . . . . . 69Creating Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Resource Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Default Workstations Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Availability Intervals Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Managing Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Default Resource Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Listing Resources in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Using Resource Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Chapter 9. Creating Job Streams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Specifying Properties for the Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Creating a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Creating a Job Using Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Creating a Job Using Copy and Paste . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Creating Dependencies between Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Creating Dependencies within a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Creating Dependencies between Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Scheduling Job Streams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Types of Run Cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Creating a Run Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Creating Rule-based Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Creating Offset-based Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Checking Time Restrictions in the Timeline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Activity Bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Table Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Time Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Other Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Saving a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Submit a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Chapter 10. Listing and Modifying Job Streams . . . . . . . . . . . . . . . . . . . . . . . . 109Default Job Stream List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Creating a Job Stream List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Displaying a Job Stream List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

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

Chapter 11. Listing Job Stream and Job Instances . . . . . . . . . . . . . . . . . . . . . 119Creating Lists of Job Stream and Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Default Instance Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Listing Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Listing Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Chapter 12. Managing Job Streams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Job Stream Instance Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Timeline View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Browsing and Modifying Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Using the General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Using the Time Restrictions Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Changing Time Restrictions in the Timeline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Rescheduling the Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Rescheduling the Start Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

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

Chapter 13. Managing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Job Instance Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Timeline View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Browsing and Modifying Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

viiTivoli Job Scheduling Console User’s Guide

Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Details Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Browsing and Modifying Job Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Changing Time Restrictions in the Timeline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Deleting Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Putting Job Instances on Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Releasing Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Showing Predecessors and Successors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Displaying Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Set as Root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Browsing the Job Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Removing a Job Instance from the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Restoring a Job Instance to the Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Running a Job Instance Immediately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Changing the Status of a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Editing JCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Viewing Operator Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Modifying Job Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Restart and Cleanup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Chapter 14. Managing Workstations in the Plan . . . . . . . . . . . . . . . . . . . . . . . . 161Creating a List of Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Displaying Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Browsing and Modifying Workstation Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Job Summary Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Open Time Intervals Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Linking Fault-Tolerant Workstations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Changing Workstation Status and Rerouting Scheduled Job Instances . . . . . . . . . . . . . . . . . . . . . . . 170

Displaying by Status the Job Instances Scheduled on a Workstation . . . . . . . . . . . . . . . . . . . . . . . . 171

Modifying the Job Instances Scheduled on a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Chapter 15. Managing Resources in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Creating a List of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Displaying Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

viii Version 8.1

Browsing and Modifying Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Default Workstations Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Availability Intervals Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Displaying the Job Instances Associated with a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Modifying Job Instances Associated with a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Part III. Using the Job Scheduling Console with Tivoli WorkloadScheduler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Chapter 16. Managing Database Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Creating a Group for Database Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Creating Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Creating a List of Job Streams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Creating a List of Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Creating a List of Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Creating a List of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Creating a List of Workstation Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Creating a List of Prompts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Creating a List of Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Creating a List of NT Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Creating a List of Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Creating a List of Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Working with Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Displaying a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Detaching a List Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Modifying a Database List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Deleting a List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Finding Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Chapter 17. Managing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Creating a Job Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Displaying a List of Job Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Displaying a Job Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Displaying Job Definition Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Modifying a Job Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Deleting Job Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

ixTivoli Job Scheduling Console User’s Guide

Chapter 18. Managing Job Streams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Using the Job Stream Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Graph View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Timeline View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Run Cycle View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Creating a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Specifying Job Stream Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Adding External Dependencies for a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Deleting External Dependencies from a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Adding a Job to a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Copying and Pasting Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Cloning the Job Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Adding an Internetwork Dependency to a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Adding an External Job Stream to a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Adding an External Job to a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Creating Dependencies Between Jobs in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Specifying Run Cycles for a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Inclusionary or Exclusionary Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Rule for Freedays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Colored Bars on Dates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Specifying Simple Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Specifying Weekly Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Specifying Calendar Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Modifying Run Cycles for a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Deleting Run Cycles from a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Specifying Time Restrictions in the Timeline View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Specifying Time Restrictions for a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Specifying Time Restrictions for a Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Saving a Job Stream in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Closing the Job Stream Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Displaying a List of Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Displaying a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Modifying a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Modifying a Job in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Deleting a Job in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Modifying an Internetwork Dependency in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Deleting an Internetwork Dependency in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Modifying an External Job Stream in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

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

Chapter 19. Managing Workstations and Workstation Classes . . . . . . . . 251Managing Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Creating a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Displaying a List of Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Displaying a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Modifying a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Deleting Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Creating a Workstation by Copying Another Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Managing Workstation Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Creating a Workstation Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Displaying a List of Workstation Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Displaying a Workstation Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Modifying a Workstation Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Deleting Workstation Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Chapter 20. Managing Domains, Users, and Calendars . . . . . . . . . . . . . . . . 261Managing Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Creating a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Displaying a List of Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Displaying a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Modifying a Domain in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Deleting Domains in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Creating a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Displaying a List of Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Displaying a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Modifying a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Deleting Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Changing User Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Managing Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

The Holidays Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Freedays Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Creating a Calendar in the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Displaying a List of Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Viewing Calendar Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

xiTivoli Job Scheduling Console User’s Guide

Modifying a Calendar in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Deleting Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Chapter 21. Managing Resources, Prompts, and Parameters . . . . . . . . . . 271Managing Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

Creating a Resource. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

Displaying a List of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

Displaying a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

Modifying a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Deleting Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Creating a Resource by Copying Another Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Managing Prompts in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Creating a Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Displaying a List of Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Displaying a Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Modifying a Prompt in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Deleting Prompts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Managing Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Creating a Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Displaying a List of Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Displaying a Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Modifying a Parameter in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

Deleting Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

Chapter 22. Plan Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279Using Plan Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Creating a Group for Plan Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Creating a Plan List of Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Creating a Plan List of Domain Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Creating a Plan List of Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Creating a Plan List of Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Creating a Plan List of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

Creating a Plan List of Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Creating a Plan List of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Modifying the Properties of a Plan List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

Deleting a Plan List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

Detaching a Plan List Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

Finding Objects in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Managing Job Instances in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Displaying a List of Jobs in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

xii Version 8.1

Modifying the Properties of a Job Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

Displaying Dependencies of a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

Adding Predecessors to a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Deleting Predecessors from a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Displaying Successors of a Job Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Holding a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Releasing a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

Showing Predecessors and Successors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

Browsing the Job Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

Rerunning a Job Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Canceling a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

Killing a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

Confirming a Job Instance SUCC or ABEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

Releasing a Job Instance from Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

Managing Job Stream Instances in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

Displaying a List of Job Streams in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

Displaying and Changing the Properties of a Job Stream Instance. . . . . . . . . . . . . . . . . . . . . . 319

Displaying Dependencies of a Job Stream Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

Adding Predecessors to a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Deleting Predecessors from a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Displaying Successors of a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Holding a Job Stream Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Releasing a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Showing Predecessors and Successors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Canceling a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Changing the Job Limit of a Job Stream Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Changing the Priority of a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Releasing a Job Stream Instance from Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

Re-submitting a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

Submitting Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Monitoring Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Submitting Jobs and Job Streams into the Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Submitting a Job Stream into the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Submitting a Job into the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

Viewing or Modifying the Properties of the Job to Submit . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

Submitting an Ad Hoc Job into the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

Managing Workstations in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

Displaying a List of Workstations in the Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

Displaying a Workstation Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

xiiiTivoli Job Scheduling Console User’s Guide

Changing the Job Limit of a Workstation in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

Changing the Job Fence of a Workstation in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

Starting a Workstation Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

Stopping a Workstation Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

Linking a Workstation Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

Unlinking a Workstation Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

Managing Domains in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

Displaying a List of Domains in the Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

Starting the Workstations in a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

Stopping the Workstations in a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

Linking the Workstations in a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

Unlinking the Workstations in a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

Switching the Domain Manager in a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Managing File Dependencies in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Displaying File Dependencies Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Managing Prompt Dependencies in the Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

Displaying Prompt Dependencies Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

Replying to a Prompt Dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Managing Resource Dependencies in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Displaying Resource Dependencies Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Displaying the Properties of a Resource Dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

Changing the Number of Units of a Resource Dependency. . . . . . . . . . . . . . . . . . . . . . . . . . . 370

Setting an Alternate Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

Part IV. Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

Appendix A. Using Common Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375Creating a Common List of Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

Listing All Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

Using Filter Criteria. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

Creating a Common List of Job Stream Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

Listing All Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

Using Filter Criteria. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

Displaying a Common List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380

Modifying a Common List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380

Deleting a Common List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380

Appendix B. Setting Traces for the Job Scheduling Console . . . . . . . . . . 381

Appendix C. Enabling Time Zones in the Workload Scheduler . . . . . . . . 385

xiv Version 8.1

Appendix D. Status Description and Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . 387

Appendix E. Job Scheduling Console Messages . . . . . . . . . . . . . . . . . . . . . . . 391

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

xvTivoli Job Scheduling Console User’s Guide

xvi Version 8.1

Figures

1. Job Scheduling View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412. Properties - Database Resource List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453. Properties - Group of Lists Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464. Displaying a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475. Properties - Workstation in Database Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496. Find Workstations Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497. Properties - Workstation in Database General Window General Page. . . . . . . . . . . . . . . . . . . . . . . . . 568. Properties - Workstation in Database Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609. Adding an Open Time Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

10. The Properties - Database Workstation List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6511. Properties - Resource in Database Window Resource Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7012. Properties - Resource in Database Default Workstations Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 7213. Properties - Resource in Database Availability Intervals Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7314. The Properties - Database Resource List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7515. List of Resources in the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7616. The Properties - Resource in Database Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7717. Properties - Job Stream Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8018. Properties - JCL Job General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8319. Properties - JCL Job Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8620. Properties - JCL Job Time Restrictions Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8721. Properties - JCL Job Resources Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8922. Job Stream Editor Graph View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9023. Job Stream Editor - Add Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9124. Job Stream Editor - Example Dependent Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9125. Properties - External Job Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9226. Selecting the External Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9227. Job Stream Editor — External Job Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9328. Job Stream Editor — Example External Job Dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9329. Job Stream Editor - Run Cycle View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9530. Properties - Rule-based Run Cycle General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9631. Properties - Rule-based Run Cycle Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9732. Properties - Rule-based Run Cycle Rules Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9833. Example Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10034. Example 1: Rule-based Run Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10035. Example 2: Exclusionary Run Cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10136. Example 3: Exclusionary Run Cycle Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10137. Properties - Offset-based Run Cycle Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10238. Example 1: Offset-based Run Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10339. Example 2: Offset-based Run Cycle Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10340. Job Stream Editor - Timeline View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10441. Submit Job Stream Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10642. The Properties - Job Stream List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11043. Displaying the Results of a Job Stream List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11244. Properties - External Job Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11645. Job Stream Editor - External Job Added . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11646. Properties - Job Stream Instance List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12047. The Properties - Job Instance List window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12348. Job Stream Instances List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12749. Job Stream Instances Timeline View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

xviiTivoli Job Scheduling Console User’s Guide

50. Properties - Job Stream Instance General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12951. Properties - Job Stream Instance Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13052. Timeline View - Left Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13153. Timeline View - Right Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13154. Rescheduling a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13255. Properties - Job Stream Instance Time Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13256. Rescheduling the Start time of a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13357. Rescheduling the Deadline Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13458. Job Instances List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13859. Job Instances Groups in the Timeline View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13860. Properties - JCL Job Instance Instance General Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14061. Properties - JCL Job Instance Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14162. Properties - JCL Job Instance Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14263. Properties - JCL Job Instance Details Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14364. Properties - JCL Job Instance Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14565. Properties - JCL Job Instance Resources Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14666. Target Resources for a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14667. Logical Resources for a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14768. Dependencies - JCL Job Instance Predecessors Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14869. Dependencies - JCL Job Instance Successors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15070. Timeline View of Job Instances - Left Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15271. Timeline View of Job Instances - Right Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15272. Rescheduling a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15373. Rescheduling the Start Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15474. Rescheduling the Deadline Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15475. Impact View Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15676. Change Status Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15877. Edit JCL Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15978. The Properties - Plan Workstation List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16279. Plan Workstation List Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16480. Properties - Workstation in Plan General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16581. Properties - Workstation in Plan Resource Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16682. Properties - Workstation in Plan Job Summary Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16683. Properties - Workstation in Plan Open Time Intervals Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16784. Changing the Start Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16885. Changing the Start Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16886. Changing the Quantity of Resource 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16987. Change Status - Workstation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17088. List of Jobs Scheduled on the Workstation and in Complete Status . . . . . . . . . . . . . . . . . . . . . . . . . 17189. The Properties - Plan Resource List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17490. A Plan Resource List Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17691. Properties - Resource in Plan Resource Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17792. Properties - Resource in Plan Default Workstations Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17993. Properties - Resource in Plan Availability Intervals Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18094. Properties - Group of Lists Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18995. Create Database List Pop-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19096. Properties - Job Stream List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19197. Properties - Job List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19198. Properties - Database Workstation List window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19299. Properties - Database Resource List window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

100. Properties - Workstation Class List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194101. Properties - Prompt List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

xviii Version 8.1

102. Properties - Parameter List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195103. Properties - NT User List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196104. Properties - Domain List Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197105. Properties - Calendar List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197106. Displaying a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198107. Properties - Resource in Database Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200108. Find Workstation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200109. Select a Task Type Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201110. Properties - Job Definition General Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202111. Properties - Job Definition: Task Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206112. Job Definition List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208113. Details for Job Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210114. Properties - Job Definition Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211115. Job Stream Editor Graph View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213116. Job Stream Editor Timeline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215117. Job Stream Editor Run Cycle View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216118. Properties - Job Stream Properties General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218119. Properties - Job Stream Time Restrictions Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220120. Properties - Job Stream Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222121. Properties - Job Stream Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223122. Properties - Job Stream Prompts Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224123. Job Stream External Dependencies Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225124. External Dependencies Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225125. Properties - Job General Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228126. Properties - Job Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229127. Properties - Job Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230128. Properties - Job Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231129. Properties - Job Prompts Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232130. External Job Stream Dependency Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235131. External Job Dependency Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236132. Job Stream Editor Window Graph View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237133. Simple Run Cycle General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239134. Simple Run Cycle Rule Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240135. Weekly Run Cycle General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241136. Weekly Run Cycle Rule Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241137. Calendar Run Cycle General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242138. Calendar Run Cycle Rule Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243139. Job Streams List Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247140. Properties - Workstation in Database Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252141. Workstation List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255142. Properties - Workstation Class General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258143. Properties - Workstation Class Workstations Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258144. Workstation Class List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259145. Properties - Domain Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261146. Properties - NT User Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264147. Users List Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265148. Properties - Calendar Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267149. Monthly Yearly Calendar Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268150. Day of Month Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268151. Properties - Resource in Database Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271152. Resource List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272153. Properties - Prompt Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

xixTivoli Job Scheduling Console User’s Guide

154. Prompts List Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275155. Properties - Parameter Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277156. Parameter List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277157. Properties - Group of Lists Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279158. Properties - Plan Workstation List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280159. Properties - Domains Status List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280160. Properties - Job Stream Instance List General Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281161. Properties - Job Stream Instance List Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282162. Properties - Job Stream Instance List Dependencies Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283163. Properties - Job Instance List General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285164. Properties - Job Instance List Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287165. Properties - Job Instance List Dependencies Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288166. Properties - Plan Resource List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289167. Properties - Prompt Status List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290168. Properties - File Status List window.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291169. Example of a Find Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293170. Example Find Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293171. Job Instance List View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295172. Job Instance List: Timeline View window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296173. Properties - NT Script Instance General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297174. Properties - NT Script Instance Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299175. Properties - NT Script Instance Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300176. Properties - NT Script Instance Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302177. Properties - NT Script Instance Prompts Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304178. Properties - NT Script Instance Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306179. Dependencies - NT Script Instance Successors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307180. Impact View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311181. Job instance Log File Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312182. Rerun Job Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313183. Job Stream Instances Timeline View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317184. Job Stream Instances List View Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318185. Properties - Job Stream Instance General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319186. Properties - Job Stream Instance Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321187. Properties - Job Stream Instance Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322188. Properties - Job Stream Instance Prompts Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324189. Properties - Job Stream Instance Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326190. Dependencies Predecessors Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327191. Impact View Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330192. Change Limit - Job Stream Instance Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331193. Change Priority - Job Stream Instance Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332194. Re-Submit Job Stream Instance Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333195. Submit Job Stream into Plan Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335196. Submit Job into Plan Window - Default Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336197. Submit Job into Plan Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337198. Properties - Job Instance General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338199. Properties - Job Instance Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341200. Properties - Job Instance Time Restrictions Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341201. Properties - Job Instance Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343202. Properties - Job Instance Prompts Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345203. Properties - Job Instance Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347204. Properties - Job Instance Predecessors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348205. Submit Ad Hoc Job into Plan Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

xx Version 8.1

206. Properties - Job Instance General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350207. Properties - Job Instance Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352208. Properties - Job Instance Time Restrictions Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354209. Properties - Job Instance Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355210. Properties - Job Instance Prompts Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357211. Properties - Job Instance Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359212. Properties - Job Instance Predecessors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360213. Workstation Status List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361214. Properties - Workstation in Plan Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363215. Change Limit - Workstation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364216. Change Fence - Workstation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364217. Switch Manager - Domain Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367218. Status of All Files List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368219. Set Alternate Plan Files Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371220. Properties - Job Instance Common List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376221. Properties - Job Stream Instance Common List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

xxiTivoli Job Scheduling Console User’s Guide

xxii Version 8.1

Tables

1. List of Publications for Tivoli Workload Scheduler for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix2. List of Publications for Tivoli Workload Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx3. Job Scheduling Console Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104. Setting the Tivoli Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135. Setting the Tivoli Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186. Authorization Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207. Useful Framework Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228. Setting the Tivoli Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279. Authorization Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

10. Useful Framework Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3211. Job Scheduling Console Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3312. Starting the Job Scheduling Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3913. Job Scheduling View Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4214. Object List Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4315. Default Database Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4416. Default Plan Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4417. Properties List Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4618. Properties - Workstation in Database General Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5719. Properties - Workstation in Database Open Time Intervals Information . . . . . . . . . . . . . . . . . . . . . . . 6320. User-defined Workstation Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6421. Default Workstation Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6422. Properties - Database Workstation List Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6623. Create a Resource Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7124. Define an Availability Interval Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7325. User-defined Resource Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7426. Default Resource Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7427. Database Resource List Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7528. Tasks in Creating a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7929. Properties - Job Stream Window Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8030. What Happens When You Define a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8131. Graph View Job Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8232. Properties - JCL Job General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8333. Properties - JCL Job Task Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8734. Properties - JCL Job Time Restrictions Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8735. Filter Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9436. Run Cycle Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9537. Run Cycle General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9638. Run Cycle Time Restrictions Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9839. Rule-based Run Cycle Rules Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9940. Offset-based Run Cycle Rules Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10241. Submit Job Stream Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10642. Properties - Job Stream List Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11043. Adding and Modifying Jobs and Dependencies in the Graph View . . . . . . . . . . . . . . . . . . . . . . . . . 11344. Adding and Modifying Run Cycles – Pop-up Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11445. Examples of How to Use Job and Job Stream Instance Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11946. Properties - Job Stream Instance List Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12047. Properties - Job Instance List Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12348. Job Instance Details Timeline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13049. Properties - JCL Job Instance General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

xxiiiTivoli Job Scheduling Console User’s Guide

50. Properties - JCL Job Instance Task Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14151. Properties - JCL Job Instance Details Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14352. Properties - Write-to-Operator Job Instance Options Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 14553. Logical Resources Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14754. Dependencies Predecessors Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14855. Dependencies Predecessors Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14956. Dependencies Successors Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15057. Dependencies Predecessors Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15158. Timeline View Job Instance Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15259. Impact View Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15660. Properties - Plan Workstation List Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16361. Properties - Workstation in Plan General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16562. Workstation List Jobs Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17163. Modifying Job Instance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17264. Plan Resource List Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17565. Properties - Resource in Plan Resource Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17766. Properties - Resource in Plan Default Workstations Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 17967. Properties - Resource in Plan Availability Intervals Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . 18068. Modifying Job Instance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18169. Properties List Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18970. Properties List Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19071. New Job Definition Task Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20172. Properties - Job Definition General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20273. Job Stream Recovery Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20474. Task Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20675. Job Definition List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20876. Details for Job Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21077. Job Stream Editor Graph View Toolbar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21478. Job Stream Editor Timeline View Toolbar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21579. Job Stream Editor Run Cycles View Toolbar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21680. Job Stream Properties Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21781. Job Stream Properties General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21882. Job Stream Time Restrictions Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22183. Properties - Job General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22884. Properties - Job Time Restrictions Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22985. Colored Bars on Dates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23886. Properties Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24587. Properties Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24688. Job Streams List Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24889. Modifying Objects in a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24990. Properties - Workstation in Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25291. Workstation List Window Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25592. Properties - Workstation Class Workstations Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25893. Workstation Class List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25994. Properties - Domain Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26195. Domain List Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26296. Properties - NT User Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26497. Users List Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26598. Example Calendars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26699. Properties - Resource in Database Window Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

100. Properties - Job Stream Instance List General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281101. Properties - Job Stream Instance List Time Restrictions Information . . . . . . . . . . . . . . . . . . . . . . . . 283

xxiv Version 8.1

102. Properties - Job Stream Instance List Dependency Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284103. Properties - Job Instance List General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285104. Properties - Job Instance List Time Restrictions Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287105. Properties - Job Instance List Dependency Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288106. Properties - Plan Resource List Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289107. Properties - Prompt Status List Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290108. Job Instance Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294109. Job Instance List View Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295110. Job Instance Timeline View Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296111. Properties - NT Script Instance General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297112. Properties - NT Script Instance Task Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299113. Properties - NT Script Instance Time Restrictions Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301114. Properties - NT Script Instance Files Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302115. Properties - NT Script Instance Prompts Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304116. Properties - NT Script Instance Resources Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306117. Predecessors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307118. Internetwork Predecessors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308119. Successors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308120. Impact View Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311121. Rerun Job Window Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313122. Job Stream Instance Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316123. Job Stream Instances Timeline View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317124. Job Stream Instances List View Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318125. Properties - Job Stream Instance General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319126. Properties - Job Stream Instance Time Restrictions Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . 321127. Properties - Job Stream Instance Files Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322128. Properties - Job Stream Instance Prompts Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324129. Properties - Job Stream Instance Resources Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326130. Dependencies - Job Stream Instance Predecessor Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327131. Impact View Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330132. Job Stream Instance Priorities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332133. Submit Job Stream into Plan Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335134. Submit Job into Plan Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336135. Submit Job into Plan Window - Specific Job stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337136. Properties - Job Instance General Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339137. Properties - Job Instance Time Restrictions Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342138. Properties - Job Instance Files Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343139. Ad Hoc Prompt Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345140. Predefined Prompt Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346141. Properties - Job Instance Resources Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347142. Properties - Job Instance Predecessors Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348143. Properties - Job Instance General Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350144. Task Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352145. Properties - Job Instance Time Restrictions Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354146. Properties - Job Instance Files Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355147. Ad Hoc Prompt Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357148. Predefined Prompt Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358149. Properties - Job Instance Resources Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359150. Properties - Job Instance Predecessors Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360151. Workstation Status List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361152. List of Domains in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366153. Status of All Files List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

xxvTivoli Job Scheduling Console User’s Guide

154. Prompt Dependencies Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369155. Resource Dependencies Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370156. Set Alternate Plan Files Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371157. Properties - Job Instance List Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377158. Properties - Job Stream Instance List Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379159. Trace Variable Location by Operating System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381160. Job Scheduling Console Job States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387161. Workload Scheduler Internal Job States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388162. Job Scheduling Console Job Stream States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388163. Workload Scheduler Internal Job Stream States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389164. Job Status Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389165. Job Stream Status Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

xxvi Version 8.1

Preface

This guide describes Tivoli Workload Scheduler for z/OS™, Tivoli Workload Scheduler, andthe Tivoli Job Scheduling Console, which make up the Tivoli Workload Scheduler suite ofapplications. The Tivoli Job Scheduling Console provides users with a Java™-based userinterface to Tivoli Workload Scheduler for z/OS and Tivoli Workload Scheduler. The JobScheduling Console supplements, but does not totally replace, the traditional z/OS ISPFpanes on the host. It allows you to work with scheduling objects in the following ways:

¶ Define job streams, jobs, workstations, and logical resources in the scheduling database.

¶ Monitor and modify job stream instances, job instances, workstation instances, andresource instances in the plan.

The Tivoli Job Scheduling Console User’s Guide provides an introduction to and anexplanation of the Tivoli Job Scheduling Console Feature Level 1.2. It explains how toinstall the console and provides instructions for performing scheduling tasks using TivoliWorkload Scheduler for z/OS and Tivoli Workload Scheduler.

Who Should Read This GuideThis guide is intended for use by:

¶ System administrators who have the task of installing the Tivoli Job SchedulingConsole. They should be familiar with one or more of the following operating systems:

Microsoft® Windows®

AIX®

HP-UXSun SolarisLinux

¶ Schedulers who have the responsibility of creating and updating definitions of objects inthe scheduler database and of creating lists of objects in the scheduler database and plan.They should be familiar with performing these specific tasks and with working in theIBM® z/OS and Microsoft Windows NT® environments:

¶ Operators who have the responsibility of controlling and monitoring the scheduler plan.They should be familiar with performing the tasks related to monitoring and modifyingobjects in the plan and with working in the IBM z/OS and Windows NT environment.

What This Guide ContainsThis book contains the following sections:

Part I. Getting started

Part I contains the following chapters:

¶ Chapter 1, “Introduction” on page 5provides an introduction to the Job Scheduling Console

¶ Chapter 2, “Installing Tivoli Job Scheduling Services” on page 13describes how to install Job Scheduling Services.

¶ Chapter 3, “Installing the Tivoli Workload Scheduler for z/OS Connector” on page 17describes how to install the Tivoli Workload Scheduler for z/OS Connector.

xxviiTivoli Job Scheduling Console User’s Guide

¶ Chapter 4, “Installing the Tivoli Workload Scheduler Connector” on page 25describes how to install the Tivoli Workload Scheduler Connector.

¶ Chapter 5, “Installing the Tivoli Job Scheduling Console” on page 33describes how to install the Tivoli Job Scheduling Console.

¶ Chapter 6, “Working with the Job Scheduling Console” on page 41describes the main features of the Job Scheduling Console.

Part II. Using the Job Scheduling Console with Tivoli Workload Scheduler for z/OS

Part II contains the following chapters:

¶ Chapter 7, “Managing Workstations in the Database” on page 55describes how to create workstations and workstation lists.

¶ Chapter 8, “Managing Resources in the Database” on page 69describes how to create and list resources.

¶ Chapter 9, “Creating Job Streams” on page 79describes how to create job streams, specify dependencies, schedule and submit jobstreams.

¶ Chapter 10, “Listing and Modifying Job Streams” on page 109describes how to create job stream lists and how to modify them.

¶ Chapter 11, “Listing Job Stream and Job Instances” on page 119describes how to create lists of jobs and job instances.

¶ Chapter 12, “Managing Job Streams” on page 127describes how to display and modify job stream instances.

¶ Chapter 13, “Managing Jobs” on page 137describes how to display and modify job instances.

¶ Chapter 14, “Managing Workstations in the Plan” on page 161describes how to display and modify workstations.

¶ Chapter 15, “Managing Resources in the Plan” on page 173describes how to display and modify resources in the plan.

Part III. Using the Job Scheduling Console with Tivoli Workload Scheduler

Part III contains the following chapters:

¶ Chapter 16, “Managing Database Lists” on page 189describes how to create all types of Workload Scheduler lists.

¶ Chapter 17, “Managing Jobs” on page 201describes how to create and manage job definitions.

¶ Chapter 18, “Managing Job Streams” on page 213describes how to use the Job Stream Editor to create, display, and modify job streams.

¶ Chapter 19, “Managing Workstations and Workstation Classes” on page 251describes how to create, display, and modify workstations and workstation classes.

¶ Chapter 20, “Managing Domains, Users, and Calendars” on page 261describes how to create, display, and modify domains, users, and calendars.

xxviii Version 8.1

¶ Chapter 21, “Managing Resources, Prompts, and Parameters” on page 271describes how to create, display, and modify resources, prompts, and parameters.

¶ Chapter 22, “Plan Tasks” on page 279 describes how to create and manage resources inthe plan.

Part IV. Appendixes

Part IV contains the following Appendixes:

¶ Appendix A, “Using Common Lists” on page 375describes how to create and modify common lists.

¶ Appendix B, “Setting Traces for the Job Scheduling Console” on page 381describes how to use the Job Scheduling Console tracing facility.

¶ Appendix C, “Enabling Time Zones in the Workload Scheduler” on page 385describes how to enable the time zone facility.

¶ Appendix D, “Status Description and Mapping” on page 387provides information about job and job stream status.

¶ Appendix E, “Job Scheduling Console Messages” on page 391lists the messages produced by the Job Scheduling Console.

PublicationsThis section lists publications in the Tivoli Workload Scheduler suite. It also describes howto access Tivoli publications online, how to order Tivoli publications, and how to makecomments on Tivoli publications.

The Tivoli Workload Scheduler libraries comprise:

¶ Publications for Tivoli Workload Scheduler for z/OS

¶ Publications for Tivoli Workload Scheduler

Tivoli Workload Scheduler for z/OS

PublicationsThe following table lists the publications in the Tivoli Workload Scheduler for z/OS library.

Table 1. List of Publications for Tivoli Workload Scheduler for z/OSTask Publication Order number

Planning Tivoli WorkloadScheduler for z/OS

Tivoli Workload Scheduler for z/OSLicensed Program Specifications

GH19-4540

Understanding the TivoliWorkload Scheduling Suite

Tivoli Workload Scheduler for z/OSGeneral Information

GH19-4539

Learning concepts andterminology

Tivoli Workload Scheduler for z/OSGetting Started

SH19-4542

Using the Java GUI Tivoli Workload Scheduler for z/OSTivoli Job Scheduling Console User’sGuide Release Notes

GI10-5781

Interpreting messages and codes Tivoli Workload Scheduler for z/OSMessages and Codes

SH19-4548

xxixTivoli Job Scheduling Console User’s Guide

Table 1. List of Publications for Tivoli Workload Scheduler for z/OS (continued)Task Publication Order number

Installing Tivoli WorkloadScheduler for z/OS

Tivoli Workload Scheduler for z/OSInstallation Guide

SH19-4543

Customizing and tuning TivoliWorkload Scheduler for z/OS

Tivoli Workload Scheduler for z/OSCustomization and Tuning

SH19-4544

Planning and scheduling theworkload

Tivoli Workload Scheduler for z/OSPlanning and Scheduling the Workload

SH19-4546

Controlling and monitoring thecurrent plan

Tivoli Workload Scheduler for z/OSControlling and Monitoring theWorkload

SH19-4547

Writing application programs Tivoli Workload Scheduler for z/OSProgramming Interfaces

SH19-4545

Quick reference Tivoli Workload Scheduler for z/OSQuick Reference

GH19-4541

Diagnosing failures Tivoli Workload Scheduler for z/OSDiagnosis Guide and Reference

LY19-6410

Tivoli Workload Scheduler

PublicationsThe following table lists the publications in the Tivoli Workload Scheduler library.

Table 2. List of Publications for Tivoli Workload SchedulerTask Publication Order number

Installing a Tivoli WorkloadScheduler network

Tivoli Workload Scheduler Planningand Installation

SH19-4555

Using the command line interface,scheduling language, and utilitycommands

Tivoli Workload Scheduler ReferenceGuide

SH19-4556

Installing and configuring limitedfault-tolerant agents on AS/400

Tivoli Workload Scheduler LimitedFault-Tolerant Agent for AS/400 User’sGuide

SH19-4558

Setting up and using the Plusmodule

Tivoli Workload Scheduler Plus ModuleUser’s Guide

SH19-4562

Interpreting messages Tivoli Workload Scheduler ErrorMessages

SH19-4557

Accessing Publications OnlineYou can access many Tivoli publications online at the Tivoli Customer Support Web site:

http://www.tivoli.com/support/documents/

These publications are available in PDF or HTML format, or both. Translated documents arealso available for some products.

xxx Version 8.1

http://www.tivoli.com/support/documents/

Workload Scheduler for z/OSAll the books in the Tivoli Workload Scheduler for z/OS library, except the licensedpublications, are available in displayable softcopy form on CD-ROM in the followingSoftcopy Collection Kit:¶ OS/390®, SK2T-6951

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 diskdrive (capable of reading disks formatted in the ISO 9660 standard) and a matching adapterand cable. For additional hardware and software information, refer to the documentation forthe specific BookManager product you are using.

Updates to books between releases are provided in softcopy only.

Ordering PublicationsYou can order many Tivoli publications online at:

http://www.tivoli.com/support/Prodman/html/pub_order.html

You can also order by telephone by calling one of these numbers:

¶ In the U.S.: 800-879-2755

¶ In Canada: 800-426-4968

¶ In other countries, for a list of telephone numbers, see the following Web site:

http://www.tivoli.com/inside/store/lit_order.html

Providing Feedback about PublicationsWe are very interested in hearing about your experience with Tivoli products anddocumentation, and we welcome your suggestions for improvements. If you have commentsor suggestions about our products and documentation, contact us in one of the followingways:

¶ Send an e-mail to [email protected].

¶ Complete our customer feedback survey at the following Web site:

http://www.tivoli.com/support/survey/

¶ Complete the Readers Comment Form provided at the back of the book.

LookAtLookAt is an online facility that allows you to look up explanations for z/OS messages andsystem abends. Using LookAt to find information is faster than a conventional searchbecause LookAt goes directly to the explanation. LookAt can be accessed from the internetor from a Time Sharing Option (TSO) command line.

You can use LookAt on the Internet at:

http://www.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/lookat.html

xxxiTivoli Job Scheduling Console User’s Guide

http://www.tivoli.com/support/Prodman/html/pub_order.html

http://www.tivoli.com/inside/store/lit_order.html

http://www.tivoli.com/support/survey/

http://www.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/lookat.html

To use LookAt as a TSO command, LookAt must be installed on your host system. You canobtain the LookAt code for TSO from the LookAt Web site by clicking on News and Help,or from the SK3T-4269.

To find a message explanation from a TSO command line, type the message ID, as in thefollowing 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 canselect the release if needed.

Some messages have information in more than one book. For example, IEC192I has routingand descriptor codes listed in OS/390 MVS Routing and Descriptor Codes, GC28-1778. Forsuch messages, LookAt prompts you to choose which book to open.

Contacting Customer SupportIf you have a problem with any Tivoli product, you can contact Tivoli Customer Support.See the Tivoli Customer Support Handbook at the following Web site:

http://www.tivoli.com/support/handbook/

The handbook provides information about how to contact Customer Support, depending onthe 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

Conventions Used in This BookThis book uses several conventions for special terms and actions, operatingsystem-dependent commands and paths, and margin graphics.

Typeface ConventionsThe following typeface conventions are used in this book:

Bold Lowercase and mixed-case commands, command options, and flags thatappear within text appear like this, in bold type.

Graphical user interface elements, except for titles of windows and dialogsand names of keys also appear like this, in bold type.

Italic Variables, values you must provide, new terms, and words and phrases thatare emphasized appear like this, in italic type.

Monospace Commands, command options, and flags that appear on a separate line, codeexamples, output, and message text appear like this, in monospace type.

Names of files and directories, text strings you must type, when they appearwithin text, names of Java methods and classes, and HTML and XML tagsalso appear like this, in monospace type.

xxxii Version 8.1

http://www.tivoli.com/support/handbook/

Operating System-dependent Variables and PathsThis book uses the UNIX® convention for specifying environment variables and fordirectory notation.

When using the Microsoft Windows command line, replace $variable with %variable% forenvironment variables and replace each forward slash (/) with a backslash (\) in directorypaths.

Note: If you are using the bash shell on a Windows system, you can use the UNIXconventions.

Other ConventionsWildcards, as used in this book, are defined as:

* (asterisk) Used to represent a character string.

? (question mark) Used to represent a single character.

xxxiiiTivoli Job Scheduling Console User’s Guide

xxxiv Version 8.1

I — Getting StartedChapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Tivoli Workload Scheduler for z/OS Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Planning Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Working with Job Streams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Working with Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Working with Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Working with Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Working with Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Operator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Working with Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Working with Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Working with Resource Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Working with Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Tivoli Workload Scheduler Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Planning Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Working with Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Working with Job Streams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Working with Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Working with Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Operator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Working with Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Working with Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Working with Workstations in the Current Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Working with Resources in the Current Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Scheduling Job Streams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Terminology Used in the Job Scheduling Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2. Installing Tivoli Job Scheduling Services . . . . . . . . . . . . . . . . . . . . 13Before Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Setting the Tivoli Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Installing from the Tivoli Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Installing from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Uninstalling Job Scheduling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Installing Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 3. Installing the Tivoli Workload Scheduler for z/OSConnector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Before Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17


Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Job Scheduling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Installing the Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Setting the Tivoli Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

1Tivoli Job Scheduling Console User’s Guide

Installing from the Tivoli Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Installing from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Customizing the Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Creating Connector Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Authorization Roles Required for Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Managing Connector Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Uninstalling the Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Installing Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Useful Framework Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 4. Installing the Tivoli Workload Scheduler Connector . . . . . . . . . 25Before Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25


Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Job Scheduling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Workload Scheduler Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Fault-tolerant Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Installing the Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Where to Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Setting the Tivoli Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Installing from the Tivoli Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Installing from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Customizing the Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Creating Connector Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Authorization Roles Required for Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Managing Connector Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Uninstalling the Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Installing Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Updating Workload Scheduler Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Useful Framework Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 5. Installing the Tivoli Job Scheduling Console. . . . . . . . . . . . . . . . . 33Before Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33For Use With Tivoli Workload Scheduler for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33For Use With Tivoli Workload Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Installing on Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Installing on AIX and HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Updating AIXconsole.sh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Installing on Solaris and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Starting the Job Scheduling Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Uninstalling the Job Scheduling Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Uninstalling on Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Uninstalling on AIX, HP-UX, Solaris, and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 6. Working with the Job Scheduling Console . . . . . . . . . . . . . . . . . . . 41The Job Scheduling View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Using the Buttons of the Job Scheduling View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

2 Version 8.1

Working with Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Default Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Default Database Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Default Plan Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Creating a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Specifying Defaults for Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Creating a Group of Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Displaying a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Detaching a List Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Modifying a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Deleting a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Finding Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Example: Finding a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49


4 Version 8.1

Introduction

The Tivoli Job Scheduling Console for Tivoli Workload Scheduler is an interactive interfacefor creating, modifying, and deleting objects in the product database. It also allows you tomonitor and control objects scheduled in the current plan.

The Job Scheduling Console allows you to work with Tivoli Workload Scheduler for z/OSand Tivoli Workload Scheduler. You can work with these products simultaneously from thesame graphical console.

Extensions, built into the Job Scheduling Console, extend its base scheduling functions tospecific scheduling functions of Tivoli Workload Scheduler for z/OS and of Tivoli WorkloadScheduler.

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 nodesthat have access to the scheduler.

Note: To use the Job Scheduling Console with Tivoli Workload Scheduler for z/OS, youmust install the Workload Scheduler for z/OS Connector. To use the Job SchedulingConsole with Workload Scheduler, you must install the Workload SchedulerConnector.

To use the Job Scheduling Console with both schedulers, you must install both typesof Connector, one for each type of scheduler.

The Job Scheduling Console provides two main functions:

SchedulingEnables you to define and list job streams, jobs, and resource availability in thescheduler database.

Monitoring and controlEnables you to monitor and control scheduled jobs and job streams in the schedulerplan. In the Job Scheduling Console, a scheduled job stream is called a job streaminstance whereas a scheduled job is called a job instance.

For each of these functions, you can use a list creation mechanism that enables you to listdatabase or plan objects that you select according to filtering criteria. Filtering criterianarrow a list down to selected objects that you want to work with. You can list objectswithout 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, andlists that you create.

1


1.In

trod

uctio

n

This chapter describes the features of the base Job Scheduling Console. The base JobScheduling Console provides a common set of functions on which the specific functions ofthe supported job scheduler extensions are implemented. The rest of this chapter provides afunctional overview of the Job Scheduling Console for Tivoli Workload Scheduler for z/OSand for Tivoli Workload Scheduler.

Tivoli Workload Scheduler for z/OS Tasks

Planning TasksFrom the Job Scheduling Console, you can define and manage the following objects in thescheduler database:

¶ Job streams

¶ Jobs

¶ Resources

¶ Workstations

Working with Job StreamsJob streams are a collection of jobs, scheduling information, and the resources they requireto run. The jobs that comprise a job stream usually follow a sequence where the running ofa job depends on the successful completion of another job. Creating a job stream involves:

¶ Defining job stream properties

¶ Creating jobs, which includes defining what resources each job requires to run and thestart time

¶ Defining the necessary dependencies, or sequencing, among the jobs of the job streamand with jobs that belong to other job streams

¶ Defining one or more run cycles, or the days on which the job stream must run andwhen it must start

Modifying a job stream involves adding, deleting, or modifying any of the jobs thatcomprise it, along with the dependencies and run cycles. You can also delete an entire jobstream.

Job stream definitions are stored in the job scheduler databases. To browse or update jobstreams you have created, you must make and run a list of job streams in the database.

Working with JobsJobs are the units of work in a job stream. You cannot create jobs outside of a job stream.You must first create a job stream and define its properties before you can start to create thejobs that comprise it. Creating a job involves:

¶ Defining job properties

¶ Specifying when the job must run (time restrictions) within its job stream run cycle

¶ Defining the properties of the task associated with the job, if applicable

¶ Specifying the resources that the job requires to run

Jobs are stored in the job scheduler database as parts of job streams. To browse, update, ordelete a job definition, you must list the parent job stream in the database.

6 Version 8.1

Working with Run CyclesA run cycle provides the scheduling information of a job stream. Like jobs, you can createrun cycles only after you have defined the job streams to which they apply. A job stream canhave 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. Tobrowse, update, or delete a run cycle definition, you must list the parent job stream in thedatabase.

Working with WorkstationsA workstation describes how and when jobs have to be run. A workstation is not necessarilyhardware—it is a stage in the processing that is controlled by the scheduler. Workstations areusually created to represent specific elements in your system configuration. Defining aworkstation involves:

¶ Defining workstation properties

¶ Defining resources and their capacity

¶ Defining the availability of servers

Working with ResourcesResources represent physical or logical devices that jobs use in order to run. Defining aresource involves:

¶ Defining the resource general properties

¶ Specifying availability intervals, periods during which the resource state and quantityavailable for running jobs differ from the values specified as general properties.

Resource definitions are stored in the job scheduler database. To browse, update, or delete aresource definition, you must make and run a list of resources in the database.

Operator TasksFrom the Job Scheduling Console, you can monitor and control the following objects in thescheduler 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 JobScheduling Console.

Working with Job Stream InstancesJob streams that are scheduled in the plan are job stream instances. You can browse, modify,and delete job stream instances, provided you display them in a job stream instance list.Modifying a job stream instance includes changing some of its general properties, the startand deadline times, the job instances it contains, and their dependencies.


1.In

trod

uctio

n

Working with Job InstancesJobs belonging to a job stream that is scheduled in the plan are job instances. You canbrowse, modify, and delete job instances after displaying them in a job instance list.Modifying a job instance involves:

¶ Changing its state, resource dependencies, and time restrictions

¶ Deleting predecessor and successor jobs in the job instance dependency chain

Working with Resource InstancesA resource instance is a resource allocated to the plan. The resource is reserved for theduration of the plan for use by the jobs that depend on it. The status and quantities of theresource are specified in the general properties and availability intervals definitions in thedatabase. You can, however, modify the resource availability intervals and quantity after theresource has been allocated to the plan.

Working with WorkstationsYou can create, update, and delete workstation definitions in the scheduler database. Youdefine the following workstation characteristics:

¶ General properties

¶ Availability status during specific periods of time

¶ Available quantities during specific periods of time

You can list workstations defined in the scheduler database, selected according to filteringcriteria, and browse or modify their properties. You can also delete workstations from thedatabase.

Tivoli Workload Scheduler TasksThe Tivoli Workload Scheduler extension supports all the tasks of the base Job SchedulingConsole. In addition, it supports specific functions and resources, such as schedulingresources and workstations. These are described in the following sections of this chapter.

Planning TasksAll the tasks that involve working with object definitions in the scheduling database arereferred to as scheduler tasks in this guide. Once you have saved an object in the database,you must first list it in the Job Scheduling Console if you want to browse, change, or deleteit.

Working with WorkstationsYou can create, update, and delete workstation definitions in the scheduler database. Youdefine the following workstation characteristics:


¶ Availability status during specific periods of time

¶ Available quantities during specific periods of time

You can list workstations defined in the scheduler database, selected according to filteringcriteria, and browse or modify their properties. You can also delete workstations from thedatabase.

8 Version 8.1

Working with Job StreamsYou 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 asbelonging 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

Working with JobsWhen you create or modify a job, the Tivoli Workload Scheduler extension adds thefollowing features to a basic job definition:

¶ Assigning the necessary special (logical) and workstation resources for the running ofthe job

¶ Defining the automatic and feedback options

Working with ResourcesYou can create, update, and delete resource definitions in the scheduler database. You definethe following resource characteristics:


¶ Availability status on a given workstation during specific periods of time

¶ Available quantities on a given workstation during specific periods of time

¶ Workstations connected to the resource

You can list resources defined in the scheduler database, selected according to filteringcriteria, and browse or modify their properties. You can also delete resources from thedatabase.

Operator TasksAll the tasks that involve working with objects in the plan, are referred to as operator tasksin this book. You must first list the objects in the plan in order to work with any of them.

Working with Job Stream InstancesIn addition to monitoring job stream instances, you can change the status of a job streaminstance to Waiting and Complete.

Working with Job InstancesYou can:

¶ Change the status of job instances to: Running, Ready, Interrupted, Error, or Successful

¶ Run, hold, or release the job instance

¶ Remove or restore (NOP or UN-NOP) the job instance in the plan

Working with Workstations in the Current PlanYou can create and update workstation instance definitions in the plan. This includes editing:

¶ Control properties

¶ Availability status to run jobs during specific intervals of time


1.In

trod

uctio

n

¶ Available quantities that jobs can use during specific intervals of time

You can also view the job instances scheduled to run on a given workstation at any timeduring the plan.

Working with Resources in the Current PlanYou can create and update resource instance definitions in the plan. This includes editing thefollowing:

¶ Control properties

¶ Availability status on a given workstation during specific intervals of time

¶ Available quantities on a given workstation during specific intervals of time

¶ Workstations connected to the resource

Scheduling Job StreamsWhen you create a job stream, the job stream run cycles are used to generate the dates andtimes at which the job stream will run. Each occurrence of a job stream is called a jobstream instance, and each job stream instance contains job instances.

After you complete the definition of a job stream in terms of jobs, dependencies, and runcycles, and you mark it active in the Job Stream Properties window, you have to go to thescheduler to schedule the job stream into the current plan. You cannot add a job stream tothe plan from the Job Scheduling Console.

Terminology Used in the Job Scheduling ConsoleThe terminology used in the Job Scheduling Console varies from that used in TivoliWorkload Scheduler for z/OS. Table 3 lists Tivoli Workload Scheduler for z/OS terms, theirJob Scheduling Console equivalents, and a brief explanation. For more information, see the“Glossary” on page 395.

Table 3. Job Scheduling Console TerminologyTivoli WorkloadScheduler for z/OS

Tivoli WorkloadScheduler

Explanation

Application description Job stream A sequence of jobs, including the resources andworkstations that support them, and schedulinginformation.

Application group Job stream template A grouping of job streams that providesscheduling information, such as a calendar, afree-day rule, and run cycles that can be inheritedby all the job streams that have been createdusing the template.

Current plan Plan A detailed plan of system activity that covers aperiod of at least one minute and not more than21 days, but typically one or two days. The planencompasses all job and job stream instances andthe resources and workstations involved inrunning them.

External dependency External job A job from one job stream that is a predecessorfor a job in another job stream.

10 Version 8.1

Table 3. Job Scheduling Console Terminology (continued)Tivoli WorkloadScheduler for z/OS

Tivoli WorkloadScheduler

Explanation

In-effect date for runcycles

Valid from The first date that a run cycle is valid.

Input arrival time (Earliest) start time The time before when a job or job stream isplanned 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 rundate in the plan.

Controller Engine The component that runs on the controllingsystem, and that contains the tasks that managethe plans and databases.

Operation Job A unit of work that is part of a job stream andthat is processed at a workstation.

Operation number Job identifier The number that identifies a job.

Operations in the currentplan

Job instances A job scheduled for a specific run date in theplan.

Out-of-effect date for runcycles

Valid to The last date that a run cycle is valid.

Run cycle with offsets Offset-based run cycle Includes a user-defined period and an offset, suchas 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 Marchor the second workday of the week.

Special resources Logical resources Any type of limited resource, such as tape drives,communication lines, databases, or printers, thatis 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 theplan.

Status: Started Running The job has started (jobs only).

Task Job A job performed at a computer workstation.


1.In

trod

uctio

n

12 Version 8.1

Installing Tivoli Job Scheduling Services

This chapter describes how to install Tivoli Job Scheduling Services. You must install JobScheduling Services before you install either the Workload Scheduler for z/OS Connector orthe Workload Scheduler Connector.

You can install Job Scheduling Services either from the Tivoli desktop or from the commandline.

Note: You must install Job Scheduling Services on the Tivoli server and on each managednode where the Connector is to be installed.

Before InstallingRead this information before you install Job Scheduling Services.

System RequirementsThe Connector has the following system requirements:

Software¶ Tivoli Management Framework:

Version 3.7.1 for Microsoft Windows, AIX, HP-UX, and Sun SolarisVersion 3.7B for Linux

Hardware¶ CD-ROM drive for installation.

¶ Approximately 4 MB of free disk space.

Setting the Tivoli EnvironmentTo install Job Scheduling Services, you must first set the Tivoli environment. To do this, login as root or administrator, then enter one of the following commands:

Table 4. Setting the Tivoli EnvironmentFor 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

where windir is the name of the Microsoft Windows installation directory.

2


2.In

stalling

Tivoli

Job

Sch

edu

ling

Services

Installing from the Tivoli DesktopTo install the Connector from the Tivoli Desktop, ensure you have set the Tivolienvironment (see “Setting the Tivoli Environment” on page 13), then:

1. Open the Tivoli Desktop.

2. From the Desktop menu select Install, then Install Product. The Install Productwindow is displayed.

3. Click Select Media to select the installation directory. The File Browser window isdisplayed.

4. Type or select the installation path. This path includes the directory containing theCONTENTS.LST file.

5. Click Set Media & Close. You return to the Install Product window.

6. In the Select Product to Install list, select Tivoli Job Scheduling Services.

7. In the Available Clients list, select the managed nodes to install on and move them tothe Clients to Install On list.

Note: You must install Job Scheduling Services on at least the Tivoli managementserver. You can install the Connector only on managed nodes where JobScheduling Services is installed.

8. Click Install. The Product Install window is displayed, which shows you the progressof the installation.

9. Click Continue Install to continue the installation or click Cancel to cancel theinstallation.

10. The installation program copies the files and configures the Tivoli database with thenew classes. When the installation is complete, the message Finished productinstallation appears. Click Close.

14 Version 8.1

Installing from the Command LineTo 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 followingcommands:

¶ 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

where:install_diris the path containing the Job Scheduling Services installation program.nodeis the name of the destination managed node.

You must install Job Scheduling Services on at least the Tivoli management server. You canonly install the Connector on managed nodes where Job Scheduling Services is installed.


2.In

stalling

Tivoli

Job

Sch

edu

ling

Services

Uninstalling Job Scheduling ServicesBefore you uninstall Job Scheduling Services, ensure you have uninstalled the WorkloadScheduler for z/OS Connector, the Workload Scheduler Connector, or both.

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:

wuninst TMF_JSS node -rmfiles

where:nodeis 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 PatchesTo install patches, ensure you have set the Tivoli environment (see “Setting the TivoliEnvironment” on page 13), then:


2. From the Desktop menu select Install, then Install Patch. The Install Patch window isdisplayed.

3. Follow the instructions presented online.

16 Version 8.1

Installing the Tivoli Workload Schedulerfor z/OS Connector

This chapter describes how to install the Tivoli Workload Scheduler for z/OS Connector. TheJob Scheduling Console communicates with the Workload Scheduler for z/OS systemthrough the Connector, a protocol converter that translates the instructions entered throughthe console into scheduler commands. Although the Connector must be running to use theconsole, you can install them in the order you prefer.

You must install the Connector on a Tivoli server or managed node, while the JobScheduling Console can be installed on any workstation that has a TCP/IP connection withthe machine running the Connector. For information about how to install a Tivoli server ormanaged node, refer to the Tivoli Framework Planning and Installation Guide and the TivoliFramework Release Notes.

This chapter explains how to install the Workload Scheduler for z/OS Connector. “Installingthe Tivoli Workload Scheduler Connector” on page 25 explains how to install the WorkloadScheduler Connector. “Installing the Tivoli Job Scheduling Console” on page 33 explainshow to install the Job Scheduling Console.

Before InstallingRead this information before you install the Connector.




¶ 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 cancreate the account beforehand, or have the Setup program create it for you.

Hardware¶ CD-ROM drive for installation.

3


3.In

stalling

Sch

edu

lerfo

rz/O

SC

on

necto

r

¶ Approximately 100 MB of free disk space for domain managers, and fault-tolerantagents. Approximately 40 MB for standard agents. In addition, the Workload Schedulerfor z/OS produces log files and temporary files, which are placed on the local harddrive. The amount of space required depends on the number of jobs managed byWorkload Scheduler for z/OS, and the amount of time you choose to retain log files.

¶ 128 MB RAM and 128 MB swap space for domain managers and fault-tolerant agents.Standard agents require less.

Supported PlatformsThe Tivoli Workload Scheduler for z/OS Connector is supported on the following platforms:

¶ Microsoft Windows:NT 4.0 with Service Pack 5 or Service Pack 6aProfessional, Server, and Advanced Server 2000 with Service Pack 1 and ServicePack 2

¶ 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

Job Scheduling ServicesJob Scheduling Services 1.2 must be installed in your Tivoli environment before you installthe Connector.

Installing the ConnectorInstallation comprises the following:

1. Installing the Connector on the Tivoli server.

2. Creating Connector instances. You must create one instance for each engine that youwant to access from the Job Scheduling Console. The Connector instance name must beunique 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 yetdone 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 EnvironmentTo install the Connector, you must first set the Tivoli environment. To do this, log in as rootor administrator, then enter one of the following commands:





18 Version 8.1


Installing from the Tivoli DesktopTo install the Connector from the Tivoli Desktop, ensure you have set the Tivolienvironment (see “Setting the Tivoli Environment” on page 18), then:


2. From the Desktop menu, select Install, then Install Product. The Install Productwindow is displayed.


4. Type or select the installation path. The path includes the directory containing theCONTENTS.LST file.


6. Select Tivoli OPC Connector.

7. In the Available Clients list, select the managed nodes to install on and move them tothe Clients to Install On list.

Note: You must install the Connector on at least the Tivoli management server. Youcan create instances only on managed nodes where the Connector is installed.

8. Click Install. The Product Install window is displayed, which shows you the progressof the installation.





winstall -c install_dir -i opc


winstall -c install_dir -i opc node

where:install_diris the path containing the Connector installation program.nodeis the name of the destination managed node.

You must install the Connector on at least the Tivoli management server. You can createinstances only on managed nodes where the Connector is installed.


3.In

stalling

Sch

edu

lerfo

rz/O

SC

on

necto

r

Customizing the ConnectorThis section describes how to customize the Connector.

Creating Connector InstancesCreate one Connector instance for each engine that you want to access with the Tivoli JobScheduling Console. To create an instance, provide the information that enables theConnector to connect to the TCP/IP server. For information about activating server supportfor TCP/IP, refer to the Tivoli Workload Scheduler for z/OS Installation Guide.

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 theConnector that you need to access through the Job Scheduling Console:

wopcconn -create [-h node] -e engine_name -a address -p port

where:nodeis the name or the ID of the managed node on which you are creating the instance. Thename of the Tivoli server is the default.engine_nameis the name of the new instance.addressis the IP address of the z/OS system where the scheduler subsystem that you want toconnect to is installed.portis 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 InstancesTo manage Connector instances from a Tivoli server or managed node, you must be a Tivoliadministrator with one or more of the following roles:

Table 6. Authorization RolesThese roles ... Can perform these tasks ...

user Use the instancesView instance settings

admin, senior, super Perform all actions available to the user roleCreate and remove instancesChange instance settingsStart and stop instances

Note: To control access to the scheduler, the TCP/IP server associates each Tivoliadministrator 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 additionalinformation, refer to the Tivoli Workload Scheduler for z/OS Customization andTuning book.

Managing Connector InstancesUse the wopcconn utility to create, remove, and manage Connector instances. This programis downloaded when you install the Connector.

Note: Before you use wopcconn, you must set the Tivoli environment. See “Setting theTivoli Environment” on page 18.

The following table describes how to use wopcconn on the command line to manageConnector instances:

To do this ... Use this command ...

Create an instance wopcconn -create -h node -e engine_name -a address -p port

Stop an instance wopcconn -stop -e engine_name | -o object_id

Start an instance wopcconn -start -e engine_name | -o object_id

Restart an instance wopcconn -restart -e engine_name | -o object_id

Remove an instance wopcconn -remove -e engine_name | -o object_id

View the settings of aninstance. Also view otherinformation, such as productversion and the object ID ofthe instance.

wopcconn -view -e engine_name | -o object_id

Change the settings of aninstance

wopcconn -view -e engine_name | -o object_id -n new_name -aaddress -p port -t trace_level -l trace_length

where:nodeis the name or the object ID (OID) of the managed node on which you are creating theinstance. The name of the Tivoli server is the default.engine_nameis the name of the new or existing instance.object_idis the object ID of the instance.new_nameis the new name for the instance.addressis the IP address of the z/OS system where the Workload Scheduler for z/OS subsystemthat you want to connect to is installed.portis the port number of the Workload Scheduler for z/OS TCP/IP server to which theConnector must connect.trace_levelis the trace detail level, from 0 to 5.trace_lengthis the maximum length of the trace file.


3.In

stalling

Sch

edu

lerfo

rz/O

SC

on

necto

r

You can also use wopcconn in interactive mode. To do this, simply enter the command,without arguments, in the command line.

Uninstalling the ConnectorTo uninstall the Connector, ensure you have set the Tivoli environment (see “Setting theTivoli Environment” on page 18), then enter one of the following commands:

¶ On AIX, HP-UX, Solaris, and Linux, enter:

wuninst OPCConnector node -rmfiles

¶ On Microsoft Windows, first enter:$bash

then enter:

wuninst OPCConnector node -rmfiles

where:nodeis the name of the system from which you want to remove the Connector. To uninstallthe Connector from all the managed nodes on which it is installed, replace node with thename of the Tivoli server.

This command removes:

¶ The Connector files

¶ All the defined Connector instances

¶ All the related class definitions





Useful Framework CommandsThese commands can be used to check your Framework environment. Refer to the TivoliFramework Reference Guide for more details.

Table 7. Useful Framework CommandsThis command ... Performs this function ...

wlookup -ar ProductInfo Lists the products installed on the Tivoli server.

wlookup -ar PatchInfo Lists the patches installed on the Tivoli server.

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 thesecond number is the managed node ID (1 is the Tivoli server). Ina multi-Tivoli environment, you can determine where a particularinstance is installed by looking at this number because all Tivoliregions 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.


3.In

stalling

Sch

edu

lerfo

rz/O

SC

on

necto

r

24 Version 8.1

Installing the Tivoli Workload SchedulerConnector

This chapter describes how to install the Tivoli Workload Scheduler Connector. The JobScheduling Console communicates with the Tivoli Workload Scheduler system through theConnector, a protocol converter that translates the instructions entered through the consoleinto scheduler commands. Although the Connector must be running to use the console, youcan install them in the order you prefer.

You must install the Connector on a Tivoli server or managed node, while the JobScheduling Console can be installed on any workstation that has a TCP/IP connection withthe machine running the Connector. For information about how to install a Tivoli server ormanaged node, refer to the Tivoli Framework Planning and Installation Guide and the TivoliFramework Release Notes.

Before InstallingRead this information before you install the Connector.




¶ Tivoli Workload Scheduler 8.1


¶ TCP/IP network communications.

¶ A Workload Scheduler user account is required for proper installation. You can createthe 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-tolerantagents. Approximately 40 MB for standard agents. In addition, the Workload Schedulerproduces log files and temporary files, which are placed on the local hard drive. Theamount of space required depends on the number of jobs managed by WorkloadScheduler, and the amount of time you choose to retain log files.

4


4.In

stalling

Sch

edu

lerC

on

necto

r

¶ 128 MB RAM and 128 MB swap space for domain managers and fault-tolerant agents.Standard agents require less.

Supported PlatformsThe Tivoli Workload Scheduler Connector is supported on the following platforms:

¶ Microsoft Windows:NT 4.0 with Service Pack 5 or Service Pack 6aProfessional, Server, and Advanced Server 2000 with Service Pack 1 and ServicePack 2

¶ IBM AIX 4.3.3, 4.3.3s, 5.1




Job Scheduling ServicesJob Scheduling Services 1.2 must be installed in your Tivoli environment before you installthe Connector.

Workload Scheduler MasterThe Connector installation and customization varies depending on whether your WorkloadScheduler master is on a Tivoli Server or on a managed node.

¶ When the Workload Scheduler master is on a Tivoli server, you must install both the JobScheduling Services and the Connector on the Tivoli server of your environment. Youmust also create a Connector instance for the Tivoli server. You can do this duringinstallation by using the Create Instance checkbox and completing the required fields.

¶ When the Workload Scheduler master is on a managed node, you must install JobScheduling Services on the Tivoli Server and on the managed node where the master islocated. You must then install the Connector on the Tivoli server and on the same nodeswhere you installed Job Scheduling Services. Ensure that you do not select the CreateInstance checkbox.

If you have more than one node where you want to install the Connector (for example,if you want to access the local data of a fault-tolerant agent through the Job SchedulingConsole), you can install the connector on multiple machines. However, in this case youshould deselect the Create Instance checkbox, because each instance must have aunique name in the Workload Scheduler network.

After you have installed the connector on the workstations in your network, you canproceed with the creation of Connector instances on the machines you need to access thescheduler through the Job Scheduling Console.

Note: Each Connector instance name must be unique within the Workload Schedulernetwork, so you must create each instance separately. Preferably, use the name ofthe scheduler agent as the instance name.

Fault-tolerant AgentsWorkload Scheduler fault-tolerant agents that are accessed through the Job SchedulingConsole 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 toaccess through the Job Scheduling Console.

26 Version 8.1

Note: Each Connector instance name must be unique within your scheduler network.

Installing the ConnectorInstallation comprises the following:

1. Installing Job Scheduling Services (see “Installing Tivoli Job Scheduling Services” onpage 13). Skip this step if you have already done this.

Note: Job Scheduling Services must be installed before the Connector, and must beinstalled on the Tivoli server.

2. Installing the Connector on the Tivoli server.

3. Creating the Connector instance. There must be one instance for every WorkloadScheduler engine you want to access through the Job Scheduling Console. TheConnector 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 yetdone 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 InstallInstall the Connector on the Tivoli server and on the managed node where the schedulermaster is installed.

You can also install the connector on a fault-tolerant agent, if you want to access local dataon the fault-tolerant agent from the Job Scheduling Console.

Setting the Tivoli EnvironmentTo install the Connector, you must first set the Tivoli environment. To do this, log in as rootor administrator, then enter one of the following commands:






Installing from the Tivoli DesktopTo install the Connector from the Tivoli Desktop, ensure you have set the Tivolienvironment (see “Setting the Tivoli Environment”), then:


2. From the Desktop menu choose Install, then Install Product. The Install Productwindow is displayed.



4.In

stalling

Sch

edu

lerC

on

necto

r

4. Type or select the installation path. This path includes the directory containing theCONTENTS.LST file.


6. In the Select Product to Install list, select Tivoli TWS Connector. The Install Optionswindow is displayed.

7. This window enables you to:¶ Install the Connector only.¶ Install the Connector and create a Connector instance.

Note: If you decide not to create the instance at this time, you can create it later byusing the wtwsconn utility from the command line (see “Creating ConnectorInstances” on page 29). Creating the Connector instance later isrecommended when installing the Connector on multiple nodes, because youcan perform the installation simultaneously on all the nodes while creatingthe instance locally using wtwsconn.

8. To install the Connector without creating a Connector instance, leave the CreateInstance 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 theClients to Install On list.

You must install the Connector on at least the Tivoli management server. You can installthe 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 mustselect only one node from the list, because the instance name must be uniquewithin 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.





28 Version 8.1

winstall -c install_dir -i TWS_CONN twsdir=/users/maestro iname= instance_nameowner=maestro


winstall -c install_dir -i twsdir=/users/maestro iname=instance_nameowner=maestro createinst=1 node

where:install_diris the path containing the Job Scheduling Services installation program.instance_nameis the name of the instance that appears in the Job Scheduling view.maestrois the owner name.nodeis the name of the destination managed node.

You must install the Connector on at least the Tivoli management server. You can createinstances only on managed nodes where the Connector is installed.

Customizing the ConnectorThis section describes how to customize the Connector.

Creating Connector InstancesCreate one Connector instance for each engine that you want to access with the JobScheduling Console. To create an instance, you must be a Tivoli administrator with admin,senior, or super authorization roles. For more information refer to “Authorization RolesRequired for Instances”.

Enter the following command on the Tivoli server or managed node where you installed theConnector that you need to access through the Job Scheduling Console:

wtwsconn -create -h node -n instance_name -t TWS_directory

where:nodespecifies the node where the instance is created. If not specified, it defaults to the nodewhere the script file is run.instance_nameis the name of the new instance. This name identifies the engine node in the JobScheduling tree of the Job Scheduling Console. The name must be unique within thescheduler network.TWS_directoryspecifies the value for the TWSdir attribute. This is the Workload Scheduler installationdirectory on the specified node.

Authorization Roles Required for InstancesTo manage Connector instances from a Tivoli server or managed node, you must be a Tivoliadministrator with one or more of the following roles:


4.In

stalling

Sch

edu

lerC

on

necto

r

Table 9. Authorization RolesThese roles ... Can perform these tasks ...

user Use the instancesView instance settings

admin, senior, super Perform all actions available to the user roleCreate and remove instancesChange instance settingsStart and stop instances

Note: To control access to the scheduler, the TCP/IP server associates each Tivoliadministrator to a Remote Access Control Facility (RACF) user. For this reason, aTivoli administrator should be defined for every RACF user. For additionalinformation, refer to the Tivoli Workload Scheduler for z/OS: Customization andTuning book.

Managing Connector InstancesUse the wtwsconn utility to create, remove, and manage connector instances. This programis downloaded when you install the Connector.

Note: Before you use wtwsconn, you must set the Tivoli environment. See “Setting theTivoli Environment” on page 27.

The following table describes how to use wtwsconn in the command line to manageConnector instances.

To do this ... Use this command ...

Create an instance wtwsconn.sh -create [-h node] -n instance -t twsdir

Stop an instance wtwsconn.sh -stop -n instance | -t twsdir

Two stop actions are supported:When -n instance is specified, the instance with that name is stopped.When -t twsdir is specified, all the instances on this node (the nodewhere the script is run) whose TWSdir attribute matches twsdir arestopped.

Remove an instance wtwsconn.sh -remove -n instance

View the settings of aninstance.

wtwsconn.sh -view -n instance

Change the settings ofan instance

wtwsconn.sh -set -n instance -t twsdir

where:nodespecifies the node where instance is created. If not specified, it defaults to the nodewhere the script is run from.instanceis the name of the new instance. This name identifies the engine node in the JobScheduling tree of the Job Scheduling Console. The name must be unique within thescheduler network.

30 Version 8.1

twsdirspecifies the value for the scheduler dir attribute. This is the Workload Schedulerinstallation directory in node.

Uninstalling the ConnectorTo uninstall the Connector, ensure you have set the Tivoli environment (see “Setting theTivoli Environment” on page 27), then enter one of the following commands:

¶ On AIX, Solaris, HP-UX, and Linux:

wuninst TWSConnector node -rmfiles

¶ On Microsoft Windows, first enter:$bash

then enter:

wuninst TWSConnector node -rmfiles

where:nodeis 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.





Updating Workload Scheduler SecurityBefore you update Workload Scheduler security, you must add the scheduler user as a Tivoliadministrator on the Tivoli desktop. To do this:

1. Open the Tivoli desktop.

2. Do one of the following:¶ Add the user login to the Edit Logins window for Tivoli Administrators.¶ Create a Tivoli administrator that has the login of the user.

To update the scheduler security file:

1. Login as the user (usually, TWSuser or maestro).

2. Change directory to TWS home.

3. Enter:dumpsec >tempsec

4. Edit the tempsec file so it contains the Admin name.


4.In

stalling

Sch

edu

lerC

on

necto

r

Note: To get the Admin name, open the Tivoli desktop and double-clickAdministrators. The Admin name is the Administrators group to which yourlogin belongs. Usually the name looks like Root_dallas-region. If the Adminname contains a blank, enclose it in double quotes.

5. Enter:wmaeutil ALL -stop

This stops the Connector.

6. Enter:makesec tempsec

Useful Framework CommandsThese commands can be used to check your Framework environment. Refer to the TivoliFramework Reference Guide for more details.

Table 10. Useful Framework CommandsThis command ... Performs this function ...

wlookup -ar ProductInfo Lists the products installed on the Tivoli server.

wlookup -ar PatchInfo Lists the patches installed on the Tivoli server.

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 thesecond number is the managed node ID (1 is the Tivoli server). Ina multi-Tivoli environment, you can determine where a particularinstance is installed by looking at this number because all Tivoliregions 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

Installing the Tivoli Job SchedulingConsole

This chapter describes how to install the Tivoli Job Scheduling Console on each of thefollowing operating systems:

Table 11. Job Scheduling Console Supported PlatformsTo 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 InstallingRead this information before you install the Job Scheduling Console.

System RequirementsThe Job Scheduling Console has the following system requirements:

For Use With Tivoli Workload Scheduler for z/OS

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


¶ 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) installationplus approximately 4 MB for each additional language

5


5.In

stalling

the

Tivoli

Job

Sch

edu

ling

Co

nso

le

For Use With Tivoli Workload Scheduler

Software

¶ Tivoli Workload Scheduler Connector

¶ Tivoli Workload Scheduler Version 7.0 or 8.1


¶ 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) installationplus approximately 4 MB for each additional language

Supported PlatformsThe Job Scheduling Console is supported on the following platforms:

¶ Microsoft Windows:NT 4.0 with Service Pack 5 or Service Pack 6aProfessional, Server, and Advanced Server 2000 with Service Pack 1 and ServicePack 298Millennium Edition

¶ IBM AIX 4.3.3, 4.3.3s, 5.1




34 Version 8.1

Installing on Microsoft WindowsTo 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:drv: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 containingall 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 optionwindows that enable you to provide the necessary information. You can use thePrevious, 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 afolder 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 Consolebuttons 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 (FullPackage), 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 SchedulingConsole. Click Install.

Notes:

a. The Job Scheduling Console displays in your selected language only if the languagematches 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 timezone settings of your system.

A progress information window is displayed.

13. When installation is finished, the Install Complete window is displayed.

14. Click Done to close the window. The Job Scheduling Console is now installed.


5.In

stalling

the

Tivoli

Job

Sch

edu

ling

Co

nso

le

Installing on AIX and HP-UXTo install the Job Scheduling Console on AIX:

1. Ensure that the Java Runtime Environment is installed. If in doubt, refer to your systemadministrator.

2. Add to your system path the ../jre/bin subdirectory of the directory where youinstalled the Job Scheduling Console.

3. Mount the CD-ROM drive.

4. Enter:sh install.bin



6. Select your language and click OK. The Introduction window is displayed.

The window leads you through the installation process, displaying a series of optionwindows that enable you to provide the necessary information. You can use thePrevious, Next, or Exit buttons, when enabled, to move through these windows.




10. If you want to install the Job scheduling Console in all available languages (FullPackage), click Install. A progress information window is displayed. Go to Step 12.




Notes:





13. Click Done. The Job Scheduling Console is installed.

Updating AIXconsole.shTo complete installation, you must update the AIXconsole.sh file with the path where youinstalled the Java Runtime Environment.

36 Version 8.1

To do this:

1. Go to the /bin/java subdirectory of the directory where you installed the JobScheduling Console.

2. Open AIXconsole.sh in editing mode.

3. Find the following statement:JAVAPATH=%ENTRY%

4. Change %ENTRY% with the path to the Java Runtime Environment.

5. Save your changes and exit the editor. You can now start the Job Scheduling Console.


5.In

stalling

the

Tivoli

Job

Sch

edu

ling

Co

nso

le

Installing on Solaris and LinuxTo install the Job Scheduling Console on Solaris:

1. Change to the directory where you downloaded the install.zip file before running theinstaller.

2. Enter:sh install.bin



4. Select your language and click OK.

The Introduction window is displayed.

This window leads you through the installation process, displaying a series of optionwindows that enable you to provide the necessary information. You can use thePrevious, Next, or Exit buttons, when enabled, to move through these windows.



7. Click Next. The Choose Shortcut Location window is displayed.

8. Select one of the available radio buttons to specify where the Job Scheduling Consolebuttons are to be placed.


10. If you want to install the Job Scheduling Console in all available languages (FullPackage), click Install. A progress information window is displayed. Go to Step 12.




Notes:





13. Click Done. The Job Scheduling Console is installed.

38 Version 8.1

Starting the Job Scheduling Console1. Depending on your platform, start the Job Scheduling Console in one of the following

ways:

Table 12. Starting the Job Scheduling ConsoleOn this platform ... In the ..\bin\java subdirectory of the installation path ...

Microsoft Windows NT, 2000 Enter NTconsole

Microsoft Windows 98, ME Enter console

Note: You can also start the Job Scheduling Console by double-clicking the Job SchedulingConsole button on the Windows Desktop or by selecting the corresponding item from the Startmenu.

AIX Enter ./AIXconsole.sh

SUN Solaris Enter ./SUNconsole.sh

HP-UX Enter ./HPconsole.sh

Linux Enter ./LINUXconsole.sh

The Tivoli Job Scheduling Console startup window is displayed.

2. In the Login As field, enter the user ID of the Tivoli administrator of the host machinerunning the scheduler engine.

3. In the Password field, enter the password to the host machine running the schedulerConnector

4. In the Host Machine field, enter the name of the Tivoli managed node that runs thescheduler Connector.

5. Click OK to continue.

6. If you are logging onto the managed node of Host Machine for the first time, aninformation pop-up is displayed, telling you how to specify a user preference file forinitialization, if it exists.

7. Click OK. The Open Location window is displayed.

8. Do one of the following:¶ Specify a URL where user preferences are defined. Enter the URL and click on

Load from URL.¶ Click Get from file to open a window from where you can select a file that contains

initialization data.¶ Click Cancel to use default user preferences.

The Welcome window is displayed.

9. Do one of the following:Select a radio button, then click OK to start working with the Job SchedulingConsole.Click Cancel to close the window and work with the Job Scheduling Consolewithout online assistance.


5.In

stalling

the

Tivoli

Job

Sch

edu

ling

Co

nso

le

Uninstalling the Job Scheduling Console

Uninstalling on Microsoft WindowsTo uninstall the Job Scheduling Console on Microsoft Windows:

1. Use the Start menu to go to the shortcut location that you specified during installation,and click Uninstall Tivoli Job Scheduling Console. The InstallAnywhere Uninstallerwindow is displayed.

2. Click Uninstall. A progress indicator is displayed. When the process completes, it listsany files that the program was not able to uninstall. You will need to delete those filesmanually.

3. Click Exit to close the window and end the uninstall process.

Uninstalling on AIX, HP-UX, Solaris, and LinuxTo uninstall the Job Scheduling Console on UNIX platforms, go to the /UninstallerDatasubdirectory of the installation path and enter:./Uninstall_JSconsole

40 Version 8.1

Working with the Job Scheduling Console

The Job Scheduling ViewThe 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 schedulerengines (Workload Scheduler, Workload Scheduler for z/OS, or other). If you expand any ofthe objects that represent the scheduler engines, you see the lists and groups of listsavailable for that particular engine.

The right-hand pane displays a detailed view of the object selected in the tree. This can beeither a number of list objects or the contents of a list in the shape of a table or a Ganttchart.

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 apop-up menu displaying the same options for creating lists, groups of lists, and objects inthe database.

Figure 1. Job Scheduling View

6


6.W

orkin

gw

ithth

eJo

bS

ched

ulin

gC

on

sole

Using the Buttons of the Job Scheduling ViewUse the following buttons, located in the toolbar of the Job Scheduling view, to create anobject in the scheduler database, or to create a list of objects defined in the database or inthe plan:

Table 13. Job Scheduling View ButtonsUse this button ... To do this ...

Browse or modify the properties of the selected object. Displays theproperties of the object selected in the tree view. If you have selected ascheduler, it opens the Properties - Scheduler window. If you haveselected a list, it opens the Properties window of that list. If you haveopened the Job Stream Editor, it displays the Properties window of thejob stream.

Delete the object selected in the tree view.

Open a resource list in a separate window (detached view), instead if thelist displaying in the right hand pane of the Job Scheduling view.

Stop loading a list. This button is active while the results of a list arebeing uploaded.

Refresh the results of a list. This button becomes available only after youhave opened a list. Click the button to reload the results of the list ondisplay in the right-hand pane of the Job Scheduling view.

Create a job stream in the database. Displays the Job Stream Editorwindow, where you define job stream properties and create jobs, jobdependencies, and run cycles.

Create a job in the database. Opens the Properties - Job Definitionwindow.

Create a workstation in the database. Displays the Properties -Workstation in Database window, where you define workstationproperties, resources, and availability intervals.

Create a resource in the database. Displays the Properties - Resourcewindow, where you define a resource properties, associated workstations,and availability intervals.

List job streams defined in the database.

Lists jobs defined in the database. Displays the Properties - Job Listwindow, where you create a filtered list of selected jobs.

List workstations defined in the database. Displays the Properties -Database Workstation List window, where you create a filtered list ofselected workstations.

List resources defined in the database. Displays the Properties - DatabaseResource List window, where you create a filtered list of selectedresources.

List job stream instances in the plan. Displays the Properties - JobStream Instance List window, where you create a filtered list of selectedjob streams scheduled in the plan.

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 Listwindow, where you create a filtered list of selected jobs scheduled in theplan.

List workstations in the plan. Displays the Properties - Plan WorkstationList window, where you create a filtered list of selected workstationsallocated to the plan.

List resources in the plan. Displays the Properties - Plan Resource Listwindow, where you create a filtered list of selected resources allocated tothe 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 thetree of your selected scheduler and you can thereafter create lists as partof it.

Note: Remember to select your intended engine in the tree before you use an button tocreate or to list an object. By default, the Job Scheduling Console selects the firstengine in the list.

Button availability in the Job Scheduling view follows the tasks you perform dynamically.For instance, if you open a list, many of the buttons described above disappear from the JobScheduling view. To display the initial layout, collapse the tree view to engine level.

Working with ListsTo browse, update, or delete objects already defined in the database and plan, you mustcreate and display a list of the objects.

Lists and list groups are displayed both in the tree view and in the right-hand pane of theJob Scheduling view. The right-hand pane displays all lists and list groups available for theselected 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 PropertiesSelect this option ... To do this ...

Properties Open the list properties window. Choose this option to change thelist 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 theJob Scheduling view.

Detach View Take the results of a list from the Job Scheduling view and placesthem in a separate window.

Default ListsThe console provides default lists for every scheduler engine in your installation. There is adefault list for each type of scheduler object. Default lists are general; that is, no selection


6.W

orkin

gw

ithth

eJo

bS

ched

ulin

gC

on

sole

criteria are specified. They therefore list all the existing objects. Default lists are grouped inlists that show objects defined in the database and lists that show objects defined in thecurrent plan.

You can edit the properties of each default list to add more restrictive selection criteria or tochange its name or refresh options.

Default Database ListsTable 15 describes the default database lists.

Table 15. Default Database ListsThis list ... Shows ...

All Job Streams All job stream definitions, including jobs,dependencies, and run cycles.

All Resources All resource definitions.

All Workstations All workstation definitions.

Default Plan ListsTable 16 describes the default plan lists.

Table 16. Default Plan ListsThis list ... Shows ...

All Scheduled Job Streams All job stream instances.

All Scheduled Jobs All job instances.

Status of all Resources The status of every resource instance.

Status of all Workstations Shows the status of every workstation instance.

You can edit the properties of each default list to add more restrictive selection criteria or tochange its name or refresh options.

Creating a ListTo create a list:

1. Select an engine in the tree.

2. Click one of the buttons displayed in the Job Scheduling view. The Properties - DatabaseResource List window is displayed.

44 Version 8.1

3. In the Name field, enter a name for the list. You can use the same name for more thanone list. Different lists maintain their individual properties even if they have the samename.

4. Specify refresh options for the list. This is optional. If a default periodic refresh period isalready specified in the Properties - Scheduler window, this value is automaticallydisplayed for each new list. You can change or deselect the default. See “SpecifyingDefaults for Lists”.

5. Enter or select filtering criteria from those displayed in the window. You can usecombinations of more parameters. The more filters you use, the more restricted is thesearch. 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 thesearch items to be treated as wildcards, real letters, prefixes, or suffixes.

When you have finished:

¶ Click Apply to display the list results immediately.

¶ Click OK to save the list. The new list is added in the tree under the engine youselected when creating the list.

Specifying Defaults for ListsYou can use the Properties - Scheduler window to set or change the following defaults forlists. To do this:

1. In the Job Scheduling view, select a scheduler engine and click the Properties button inthe toolbar. The Properties - Scheduler window is displayed.

2. Open the Settings page and make your adjustments.

Periodic refreshSelect the check box and type the number of seconds after which a list displaywill periodically refresh. After you do this, this information is used every timeyou click Apply defaults in the properties window of a list. This information is

Figure 2. Properties - Database Resource List Window


6.W

orkin

gw

ithth

eJo

bS

ched

ulin

gC

on

sole

also automatically displayed in editable form in the Periodic Refresh Optionsgroup of the properties window of each new list you create.

Buffer size for listsSelect a value from the drop-down list. The value determines at which rate theresults of a list are sent onto your screen. For example, if you select 100, theresults of a list are sent in blocks of 100 lines. The default is 50. If you select ahigher number, it takes more time to display the list initially, but less time todisplay the entire list when it is scrolled.

Creating a Group of ListsThe Job Scheduling Console allows you to organize your lists into groups. You can organizeyour groups of lists by any criterion that will help you to quickly display the objects thatyou want to work with. For example, you can create a group gathering lists that enable youto work with all the objects associated with a particular plan.

First you must create a group, then you can create the lists that comprise it. To create agroup of lists:


2. Click the Create a Group of Lists button or right-click on the engine button and selectCreate Group from the pop-up menu.

To create a group in an existing group, select the group and click Create a Group ofLists on the toolbar or right-click the existing group button and select Create Groupfrom the pop-up menu.

The Properties - Group of Lists window is displayed.

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.


¶ Click OK to close the window and save the new group. An button is created for the newgroup in the tree view of the Job Scheduling Console.

¶ Click Cancel to close the window without saving the new group.

After creating a group, you can create its member lists and subgroups. Right-click the groupto display a pop-up menu with the following options:

Table 17. Properties List OptionsSelect 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 workstationdefinitions in the database.

Figure 3. Properties - Group of Lists Window

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, orworkstations in the plan.

Create Group Create a subgroup of more lists.

Displaying a ListTo 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 listtool searches the database or plan and displays the objects it finds in the right-hand paneof 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 precedingones. However, as long as a list is kept open, it is maintained and refreshed according to therefresh options specified. To view the list, click the corresponding object in the JobScheduling view.

Detaching a List DisplayDetaching 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.

To detach a list display:

1. Open a list and wait for the results to be displayed.

2. Right-click the list in the tree view and select Detach View from the pop-up menu. Thelist window is displayed separately from the Job Scheduling view.

3. To place the list back in the right-hand pane, either close the detached window orright-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 listsor perform other tasks.

Figure 4. Displaying a List


6.W

orkin

gw

ithth

eJo

bS

ched

ulin

gC

on

sole

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 manydetached views open at the same time.

Modifying a List1. 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.


¶ Click Apply to run the list without closing the window. The list results are displayed inthe right pane of the Job Scheduling Console.

¶ Click OK to save the changes and to close the window.

¶ Click Cancel to close the window without running or saving the changes.

Deleting a List1. In the tree of the Job Scheduling view, double-click an engine.

2. Right-click the list you want to delete and select Delete from the pop-up menu. Aconfirmation message is displayed.

3. Click OK. The list is deleted from the tree.

Finding ObjectsA contextual find tool in the Job Scheduling Console helps you to find the name of aresource, workstation, job, or job stream when you need to provide one. The find tool isavailable when you can see an ellipsis (...) next to the field where you are asked to enter thename. An example is shown in the Properties - Workstation in Database window, shown inthe next figure, in which the Find tool ellipsis is identified by the cursor arrow.

48 Version 8.1

Example: Finding a WorkstationThe following example shows how you can use the Find tool to enter the name of analternate workstation when you are defining workstation open time intervals.

To use the Find tool:

1. Click the ellipsis. The Find Workstations window is displayed.

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.

Figure 5. Properties - Workstation in Database Window

Figure 6. Find Workstations Window


6.W

orkin

gw

ithth

eJo

bS

ched

ulin

gC

on

sole

¶ Add no input. This results in an unfiltered search that produces a list of all theobjects (workstations in this example) defined in Workload Scheduler for z/OS.

3. Click Start. The window expands, and the objects found are listed at the bottom of thewindow.

4. Select an object and click Apply. The Find window closes and the name of the object isautomatically entered in the required field.

5. Click OK to close the Properties - Workstation in Database window.

50 Version 8.1

II — Using the Job Scheduling Consolewith Tivoli Workload Scheduler forz/OSChapter 7. Managing Workstations in the Database . . . . . . . . . . . . . . . . . . . . . 55Creating a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

General Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Defining Open Time Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Managing Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Default Workstation Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Creating a List of Workstations in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Using Workstation Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Displaying a List of Workstations in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Modifying Workstation Properties in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Deleting a Workstation from the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Creating Workstations from Existing Ones in the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Chapter 8. Managing Resources in the Database . . . . . . . . . . . . . . . . . . . . . . . . 69Creating Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Resource Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Default Workstations Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Availability Intervals Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Managing Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Default Resource Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Listing Resources in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Using Resource Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Displaying a List of Resources in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Modifying Resource Properties in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Deleting Resources from the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Creating Resources from Existing Ones in the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Chapter 9. Creating Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Specifying Properties for the Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Creating a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Creating a Job Using Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83General Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Creating a Job Using Copy and Paste . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Creating Dependencies between Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Creating Dependencies within a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Creating Dependencies between Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Finding a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Scheduling Job Streams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Types of Run Cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Creating a Run Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95


General Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Creating Rule-based Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Example 1: Rule-based Run Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Example 2: Exclusionary Run Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Example 3: Exclusionary Run Cycle Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Creating Offset-based Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Example 1: Offset-based Run Cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Example 2: Offset-based Run Cycle Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Checking Time Restrictions in the Timeline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Activity Bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Table Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Time Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Other Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Saving a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Submit a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Chapter 10. Listing and Modifying Job Streams . . . . . . . . . . . . . . . . . . . . . . . . 109Default Job Stream List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Creating a Job Stream List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Displaying a Job Stream List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Modifying Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Modifying Job Stream Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Adding and Modifying Jobs and Dependencies in the Graph View . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Modifying a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Adding a New Job using Copy and Paste . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Deleting a Job or External Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Editing Another Job Stream from an External Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Removing a Dependency between Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Adding and Modifying Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Viewing and Modifying Time Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Deleting Job Streams from the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Using Copy to Add an External Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Using Existing Definitions to Create Other Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Chapter 11. Listing Job Stream and Job Instances . . . . . . . . . . . . . . . . . . . . . 119Creating Lists of Job Stream and Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Default Instance Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Listing Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Listing Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Chapter 12. Managing Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Job Stream Instance Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Timeline View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Browsing and Modifying Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Using the General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Using the Time Restrictions Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Changing Time Restrictions in the Timeline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Rescheduling the Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Rescheduling the Start Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

52 Version 8.1

Rescheduling the Deadline Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Deleting a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Setting a Job Stream Instance to Complete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Setting a Job Stream Instance to Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Rerunning a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Additional Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Chapter 13. Managing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Job Instance Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Timeline View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Browsing and Modifying Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Details Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Target Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Logical Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Browsing and Modifying Job Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Predecessors Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Successors Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Changing Time Restrictions in the Timeline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Rescheduling the Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Rescheduling the Start Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Rescheduling the Deadline Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Deleting Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Putting Job Instances on Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Releasing Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Showing Predecessors and Successors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Displaying Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Set as Root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Browsing the Job Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Removing a Job Instance from the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Restoring a Job Instance to the Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Running a Job Instance Immediately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Changing the Status of a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Editing JCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Viewing Operator Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Modifying Job Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Restart and Cleanup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Chapter 14. Managing Workstations in the Plan . . . . . . . . . . . . . . . . . . . . . . . . 161Creating a List of Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Displaying Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Browsing and Modifying Workstation Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Job Summary Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Open Time Intervals Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167


Linking Fault-Tolerant Workstations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Changing Workstation Status and Rerouting Scheduled Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Displaying by Status the Job Instances Scheduled on a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Modifying the Job Instances Scheduled on a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Chapter 15. Managing Resources in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Creating a List of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Displaying Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Browsing and Modifying Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Default Workstations Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Availability Intervals Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Displaying the Job Instances Associated with a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Modifying Job Instances Associated with a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

54 Version 8.1

Managing Workstations in the Database

The Tivoli Workload Scheduler for z/OS environment is defined in terms of resources andworkstations. A workstation describes how jobs have to be run. A workstation is notnecessarily 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 schedulercan start a job instance, the workstation on which the job instance is defined must beavailable. So, by controlling workstation availability, you control the running of jobinstances that are defined on the workstation.

The scheduler establishes the availability of a workstation by using the open intervals in thelist of available workstations in the database. These are the times when workstationresources and parallel servers are available to process work. Parallel servers and resourcesare 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 thereal world. For instance, a computer workstation might be created for each z/OS system in ascheduler complex. So, the availability of the computer workstation should reflect theavailability of the z/OS system it represents. This prevents the scheduler from submittingwork to a z/OS system that is not physically available. Also, the accuracy of any planningpredictions that the scheduler produces for you depends on how accurately you havedescribed the installation to the scheduler.

This chapter describes how to use the Job Scheduling Console to define and administer theavailability of workstations. For a full description of workstations, refer to the TivoliWorkload Scheduler for z/OS Planning and Scheduling the Workload book.

7


7.M

anag

ing

Wo

rkstation

sin

the

Datab

ase

Creating a WorkstationThis section describes how to create a workstation in the Workload Scheduler for z/OSdatabase.

In the Job Scheduling view, select the engine in whose database you want to work, thenclick the New Workstation button in the toolbar. The new workstation will be defined inthe database of that engine.

General PageWhen you click the New Workstation button, the Properties - Workstation in DatabaseGeneral page is displayed. This is where you enter general information for the workstation.

Figure 7. Properties - Workstation in Database General Window General Page

56 Version 8.1

Use the information in Table 18 to enter all the information required to create theworkstation.

Table 18. Properties - Workstation in Database General InformationIn 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 controlledautomatically.

Computer for running of jobs and started tasks.Printer for printing.

Reporting attribute Select one of the following mechanisms for reporting statusupdates on the jobs defined on the workstation:Automatic if the status change of jobs is reported

automatically, in response to event recordscreated by Tivoli Workload Scheduler for z/OS.Typically, you should use this reportingattribute for computer and print workstations, orfor workstations that specify a user-defineddestination.

Manual start and completionif the status change of jobs is reported eitherfrom the Ready List ISPF panes on the host orfrom the results of a workstation status list (see“Using Workstation Lists” on page 67 fordetails). Typically, you should use this reportingattribute for general workstations that are usedfor job preparation, or for other generalworkstations if the duration of the task needs tobe tracked.

Completion onlyif the status change of jobs is reported eitherfrom the Ready List ISPF panes on the host orfrom the results of a workstation status list (see“Using Workstation Lists” on page 67 fordetails). Typically, you should use this reportingattribute for general workstations that are notused for job preparation.

Non reporting if jobs on this workstation are set to completeas soon as they become eligible to be started.Typically, you should use this reportingattribute for dummy jobs created to simplify thesequencing of other jobs.

Printout routing Enter the ddname of the daily printout data set where reports forthis workstation are to be written.


7.M

anag

ing

Wo

rkstation

sin

the

Datab

ase

Table 18. Properties - Workstation in Database General Information (continued)In this area ... Enter this information ...

Control on serversPlanning on servers

Use the two check boxes, Control on servers and Planning onservers, to specify how the workstation uses parallel servers.When you create a Tivoli Workload Scheduler for z/OS job, youspecify how many parallel servers it requires. The workstationthat the job is using must have that number of parallel serversavailable before the job can run. You set this value when youcreate the workstation, but you can change it later.

We recommend that you select both the Control on servers andthe Planning on servers check boxes, so that Tivoli WorkloadScheduler for z/OS submits jobs only up to the limit of thenumber of servers specified. If you select the Planning onservers check box only, or no check box at all, then TivoliWorkload Scheduler for z/OS will not evaluate the number ofparallel servers when deciding when to start an operation. Inaddition, the number of parallel servers will be used only forplanning purposes, and the plans that Tivoli Workload Schedulerfor z/OS produces cannot accurately predict the behavior of realwork in your system, because Tivoli Workload Scheduler forz/OS will submit as many jobs as are ready, regardless of itscount of the number of servers in use.Note: At a non–STC computer workstation, a parallel server canrepresent a Job Entry Subsystem initiator. You must allocate atleast one parallel server when you define a job. If you selectboth check boxes, or the Control on servers box only, thenumber of parallel servers required by the job must also beavailable on the workstation before the job can be started.

Splittable Select this box to specify that jobs on the workstation can beinterrupted and then continued at a later time. Use this attributefor a job setup general workstation where you prepare JCL forsubmission. If the preparation of the JCL is interrupted by thepreparer issuing the TSAVE command, the operation is givenstatus I, interrupted. Preparation of the JCL can continue at alater time. Printer workstations can also be split, but operationson computer workstations cannot be split.

Started task, STCJob setupWTO

Select one of these three check boxes according to whichworkstation type you chose:Started task, STC

if this is a computer workstation that will runstarted tasks rather than jobs.

Job setup if this is a general workstation on which toprepare job JCLs or started task JCLs manuallybefore running. You do not need this attribute ifTivoli Workload Scheduler for z/OS can resolveall the JCL variables automatically.

WTO if this is a general workstation on which theTivoli Workload Scheduler for z/OS schedulingfacilities can issue a write-to-operator messageat the operator console designated inDestination.

58 Version 8.1

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. Usefault-tolerant workstations to run Tivoli Workload Scheduler jobsin a Tivoli Workload Scheduler for z/OS plan. Fault-tolerantworkstations are automatically defined as computer workstationtypes with an automatic reporting attribute. When you select thisbox, all the properties for this workstation are disabled and set totheir default value.

Destination Enter a destination that corresponds to the destination specifiedon a ROUTOPTS initialization statement. For computerworkstations and WTO general workstations this is the name ofthe Tivoli Workload Scheduler for z/OS tracker. The defaultdestination is the system where the Tivoli Workload Schedulerfor z/OS engine is started.

DefaultsTransport time Enter the time, in hours:minutes (HH:MM)

format, that the system should allow betweenthe end of a predecessor job and the beginningof the present job. The transport time of theworkstation is the default transport time for allthe jobs defined on the workstation and is usedfor planning purposes only.

Duration Enter the default estimated processing time, inHH:MM:SS format, for all jobs on thatworkstation. Tivoli Workload Scheduler forz/OS uses the estimated processing time, whencreating the plan, to work out a timetable forall jobs. You do not need to give an exactfigure, because Tivoli Workload Scheduler forz/OS can adjust this figure dynamically from itsexperience of the actual durations, however youshould attempt to estimate as close as possible.

You can override this value by specifying aduration when you create a new job.

Access Methods Enter details of any optional access methods that enable theworkstation to submit and track jobs that are run by an externalproduct.Note: This option applies only to workstations running on OPC2.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 accessmethod.

Port number Enter the optional TCP/IP port number of thetracker agent that is hosting the access method.

Select Resources in the left pane. The Resources page is displayed.


7.M

anag

ing

Wo

rkstation

sin

the

Datab

ase

Resources Page

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 recognizedautomatically when you schedule and run jobs on the workstation. However, they are subjectto the following limitations, that in some instances could make it more practical to uselogical 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 forscheduling purposes. When you create a new job, you can specify how many of theworkstation resources (R1, R2, or both) the job will use. Unless the specified quantity ofresources is available, the job will not start.

Figure 8. Properties - Workstation in Database Resources Page

60 Version 8.1

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 R2default.

2. Select the Used for planning check box, if you want this resource to be consideredwhen 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 jobruns on this workstation.

The plan contains the best estimation of when operations will start. If somethingunexpected happens (for example, a job exceeds its expected run time), Tivoli WorkloadScheduler for z/OS may need to reassess the start time of some of its operations. At thispoint, the Control option becomes important. If you selected it, Tivoli WorkloadScheduler 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.


7.M

anag

ing

Wo

rkstation

sin

the

Datab

ase

Defining Open Time IntervalsIn this window you define, on a time-interval basis, the availability of parallel servers, thecapacity of workstation resources, and the name of an alternate workstation that will allowwork to run at this workstation.

1. To add or delete an open time interval, click the Add Row or Remove Row buttons. Todelete an interval, you must first select the row, then click the button.

2. After adding a row, to define the new interval, double-click under each heading to makea choice or to write data. See Figure 9.

Figure 9. Adding an Open Time Interval

62 Version 8.1

Use the information in Table 19 to complete all the necessary fields in the window.

Table 19. Properties - Workstation in Database Open Time Intervals InformationIn this column ... Do this ...

Day menu Choose: a day of the week, Standard, or Specific Date (where acalendar pops up from which you select a date). The Standardinterval defines the values that are true at all times, with the exceptionof the additional intervals that you also specify on this page. Whenyou define a new workstation, you find a default Standard row whereyou enter the name of an alternate workstation and the quantities ofparallel servers and of workstation resources that you want to beavailable on a general basis. Select a day or Specific Date to specifythe time intervals where the quantities, name, or both are differentfrom 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 inthe quantities and with the properties defined in the current row.

ClosedTo specify that the workstation is not available during theinterval. If you select this value, the remaining cells in the roware 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 theworkstation during the time interval. Leave this field blank if you didnot specify usage of parallel servers in the General page.

R1 Capacity and R2Capacity

The available quantities, to a maximum of 99 each for every interval,of resources R1 and R2 if you specified their use for this workstationin the Resources page.

Alternate Workstation The name of another workstation of the same type that can be usedduring the interval if this workstation becomes unavailable. Thisoption is possible only for computer workstations and for WTOgeneral workstations.Note: For best results, make the configurations of the twoworkstations symmetrical, so that the two workstations can bealternates for each other.

If you need assistance in finding the alternate workstation, click theellipsis next to the field to open a Find Workstations window. See“Finding Objects” on page 48 for instructions on using the FindWorkstations window.


¶ Click OK to add the new workstation to the database and to close the window.

¶ Click Cancel to close the window without adding the workstation.


7.M

anag

ing

Wo

rkstation

sin

the

Datab

ase

Managing WorkstationsAfter you have created the workstations, create one or more workstation lists to managethem. You can use workstation lists to:

¶ View workstation characteristics

¶ View workstation status

¶ Modify workstation properties

¶ Delete workstations

You can create two types of list:

Table 20. User-defined Workstation ListsUse this type of list ... To do this ...

Database workstation lists View and update workstation definitions stored in the WorkloadScheduler for z/OS workstation description database.

Plan workstation lists View and update the status and properties of the workstationsallocated to the plan and of the jobs associated with them.

The following sections explain how to create database and plan workstation lists. They alsoexplain how to use database workstation lists to update definitions in the WorkloadScheduler for z/OS database. “Managing Workstations in the Plan” on page 161 providesinformation on how to use plan workstation lists to modify the allocation of workstations inthe plan.

Default Workstation ListsThe Job Scheduling Console provides two workstation lists. You can find them in the defaultlists groups in the tree of each Workload Scheduler for z/OS engine shown in the JobScheduling view.

Table 21. Default Workstation ListsUse this list ... To do this ...

All Workstations Display a list of all the workstations defined in the workstationdefinition 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 theirproperties and see from the empty fields that no selection criteria are specified. You canmodify their properties and make them less general by adding the filters of your choice.

64 Version 8.1

Creating a List of Workstations in the DatabaseA workstation list produces a filtered list of workstations defined in the Workload Schedulerfor z/OS workstation description database.

To create a database workstation list, in the Job Scheduling view, select an engine and clickthe List Workstations in Database button.

The Properties - Database Workstation List window is displayed.

Figure 10. The Properties - Database Workstation List Window


7.M

anag

ing

Wo

rkstation

sin

the

Datab

ase

Use the information in Table 22 to enter all the information needed to create the databaseworkstation list.

Table 22. Properties - Database Workstation List InformationIn this area ... Do this ...

Name Enter a name for the list.

Periodic Refresh Options ¶ Select Periodic Refresh to specify an automatic refreshinterval in seconds.

—OR—¶ Select Apply Defaults to use the default specified in the

Scheduler Properties window available from the JobScheduling view.

Filter Criteria In the group, specify any of the following search parameters orcombinations of two or more parameters. To generalize yoursearch, use wildcard characters, such as an asterisk (*) to representstrings of characters, or a question mark (?) to represent a singlecharacter. If you leave all fields blank, all the workstations definedin 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 reportingattributes you select with the following check boxes:¶ Automatic¶ Completion only¶ Manual start at completion¶ Non reporting

TypesLists all the workstations of the type you select with thefollowing check boxes:¶ General¶ Computer¶ Printer

Is Fault TolerantLists fault-tolerant workstations. These workstations areused to run the Workload Scheduler jobs in the WorkloadScheduler for z/OS plan.

Select :Yes To list fault-tolerant workstationsNo To list workstations that are not fault-tolerantIgnore criteria

To list workstations regardless of whether they arefault-tolerant or not



¶ Click OK to add the object for the new list to the tree under the engine you selectedwhen creating the list. To display the list, right-click it and click Open.

66 Version 8.1

Using Workstation ListsWhen you open a database workstation list object, all the workstations defined in thedatabase that respond to the filter criteria are displayed in the right-hand pane of the JobScheduling Console.

This section explains how to use database workstation lists to:

¶ Modify workstation properties

¶ Delete workstation definitions

¶ Define new workstations

To work with workstations allocated to the plan, you must use a plan workstation list. Forfurther information, see “Browsing and Modifying Workstation Properties” on page 164. Towork with workstations defined in the database, continue with “Displaying a List ofWorkstations in the Database”

Displaying a List of Workstations in the DatabaseTo display a list of workstations defined in the database, in the Job Scheduling view,right-click the list object for which you want to use to list the workstations and select Openfrom the pop-up menu.

The workstations found are displayed in the right-hand pane.

For each workstation, the following are displayed:

¶ Name and description

¶ Reporting attribute

¶ Type

¶ Whether or not it is fault-tolerant

¶ Date and operator user ID of last update of the workstation properties

Modifying Workstation Properties in the DatabaseTo modify the properties of a workstation displayed in a list:

1. In the Job Scheduling view, right-click the workstation and select Properties from thepop-up menu. The Properties - Workstation in Database window is displayed.

2. Make your changes to the workstation properties. For a description of the fields in theProperties - Workstation in Database window, see “Creating a Workstation” on page 56.

3. Click OK to save your changes.

Deleting a Workstation from the DatabaseTo delete a workstation displayed in a list:

1. In the Job Scheduling view, right-click the workstation and select Delete from thepop-up menu. A confirmation window is displayed.

2. Click Yes. The workstation is deleted from the database.


7.M

anag

ing

Wo

rkstation

sin

the

Datab

ase

Creating Workstations from Existing Ones in the DatabaseYou can select a workstation from a list and use its definition to create other workstationswith the same or similar properties. To do this:

1. In the Job Scheduling view, right-click the workstation that you want to use as a modelfor the new workstation, and select Create Another from the pop-up menu.

2. The Properties - Workstation in Database window is displayed.

3. In the Name field, change the default name to the name of your choice. If you do notchange the name, the new workstation is saved as COPY (a Workload Scheduler forz/OS workstation name cannot be more than four characters in length).

4. Change any other properties that you need to customize for the new workstation.

5. Click OK to save the new workstation and close the window. The new workstation isadded to the database.

6. To view the new workstation, either click the Refresh List Results button in the JobScheduling Console window or run another list.

68 Version 8.1

Managing Resources in the Database

In Workload Scheduler for z/OS, resources represent the physical or logical objects that areused by jobs. You can use resources to prioritize access to a data set or to limit the numberof 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

8


8.M

anag

ing

Reso

urces

inth

eD

atabase

Creating ResourcesTo create a resource in the Workload Scheduler for z/OS database, select an engine in theJob Scheduling view and click the New Resource button.

The Properties - Resource in Database window is displayed. This window contains theResource, Default Workstations, and Availability Intervals pages. On the first two pages, youenter the default information for the new resource. These values are valid at all times, exceptfor the periods that you optionally define on the Availability Intervals page.

Resource PageIn this Properties - Resource in Database Resource page, you enter information thatdescribes the resource you are creating.

Figure 11. Properties - Resource in Database Window Resource Page

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 InformationIn this area ... Do this ...

Name Specify a name identifying the resource. The name is converted touppercase.

Description Provide a description of the resource.

Default The quantity of the resource (from 1 to 999999) in Quantity. Specifythe number of the resource that is available (when you select the IsAvailable box) for the availability intervals associated with theresource. This information is used as the default unless otherwisespecified for a given interval on the Availability Intervals page.

Group ID A name of up to eight characters that identifies a group to which theresource belongs. The group ID can be used as a list filter for selectingsubsets of resources.

Hiperbatch Select to specify whether the resource is a data set eligible forHiperbatch™. Hiperbatch is a host performance enhancement thatworks with the Data Lookaside Facility (DLF) to enable batch jobs andstarted 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 resourcewhen a job that allocates this resource ends in error (and does not havean 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 criticaljobs to keep their resources even when they fail, to avoid havingto wait for resources when the job is restarted.

Free if exclusiveFree the full exclusive allocation of this resource.

Free if sharedFree the full shared allocation of this resource.

Assume System DefaultUse the default specified in the ONERROR keyword of theRESOPTS statement. Refer to the Customization and Tuningmanual.

Select Default Workstations in the left pane. The Properties - Resource in Database DefaultWorkstations page is displayed.


8.M

anag

ing

Reso

urces

inth

eD

atabase

Default Workstations PageOn this page, you list the workstations associated with and reserved for the resource.

1. To add all the workstations defined in Workload Scheduler for z/OS, click the Add AllWorkstations button in the toolbar. An asterisk (*) is added to the list of connectedworkstations.

Note: By default, all workstations are already added when the Resource Editor windowfor 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 FindWorkstation button. The Find Workstation window is displayed.

4. Several filtering items are available to search for connected workstations. Either enter aname directly in the Workstation field or select one or more boxes in the ReportingAttributes and Types groups.

5. Click Start.

6. When the search results are displayed, select a workstation and click Add to add it to theDefault Workstations list.

Select Availability Intervals in the left pane. The Properties - Resource in DatabaseAvailability Intervals page is displayed.

Figure 12. Properties - Resource in Database Default Workstations Window

72 Version 8.1

Availability Intervals PageOn this page, you define the time intervals when the resource can be used with either theQuantity, Availability, and Connected Workstations values in the Resource and DefaultWorkstations pages, or with other values that you specify for each different interval.

To add or delete an availability interval, click the Add Row or Remove Row buttons, thenselect 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 InformationIn 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 usedwith the values you entered in the other two pages. When you define anew resource, you find a default Standard row where you need not addany values except, optionally, for a time range.

Select a day or Specific Date to specify the intervals in which theresource is available with different Quantity, Availability, and ConnectedWorkstations characteristics that you specify in the row itself.

From Time and To Time Specify a time range.

Quantity Type the quantity of the resource in this time interval.

Is available menu Choose: Available, Not Available, or Default (the default specified in theResource page). To put a resource off limits for a certain period, click No.

Workstations Write the names of one or more connected workstations, each separatedby a blank. Alternatively, click the ellipsis (...), then Find Workstation.This opens a Find window that helps you search for availableworkstations. See “Finding Objects” on page 48 for an explanation ofusing the Find window.


¶ Click OK to save the new resource and close the window.

Figure 13. Properties - Resource in Database Availability Intervals Window


8.M

anag

ing

Reso

urces

inth

eD

atabase

¶ Click Cancel to close the window without saving the resource.

Managing ResourcesOnce you have created resources, create one or more resource lists to manage them. From aresource list you can:

¶ View the characteristics and status of resources

¶ Modify resource properties

¶ Delete resources

You can create two types of list:

Table 25. User-defined Resource ListsUse this type of list ... To do this ...

Database resource lists View and update resource definitions stored in the resourcedescription database.

Plan resource lists View and update the status and properties of the resource allocated tothe plan and of the jobs associated with them.

The following sections explain how to create database and plan resource lists. They alsoexplain how to use database resource lists to update definitions in the database. “ManagingResources in the Plan” on page 173 provides information on how to use plan resource liststo modify resource allocation in the plan.

Default Resource ListsThe Job Scheduling Console provides two resource lists. You can find them in the defaultlists groups in the tree of each engine displayed in the Job Scheduling view.

Table 26. Default Resource ListsUse this type of list ... To do this ...

All Resources Display a list of all the resources defined in the resource definitiondatabase. 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 theirproperties and see from the empty fields that no selection criteria are specified. You canmodify their properties and make them less general by adding the filters of your choice.

Listing Resources in the DatabaseA database resource list shows a filtered list of resources defined in the Workload Schedulerfor z/OS resource description database.

To make a database resource list, select an engine in the Job Scheduling view, then click theList Resources in Database button. The Properties - Database Resource List window isdisplayed.

74 Version 8.1

Use the information in Table 27 to enter all the information needed to create the list.

Table 27. Database Resource List InformationIn this area ... Do this ...

Name Enter a name to identify the query.

Periodic Refresh Options To refresh the list results automatically, select the Periodic Refreshcheck box and specify a refresh interval in seconds. Alternatively,click Apply Defaults to use the defaults specified in the schedulerProperties window available in the Job Scheduling view.

Filter Criteria Specify search parameters or combinations of parameters.

To generalize your search, use wildcard characters. If you leave allfields blank, then all resources are displayed when you open the list.

Specify a parameter or a combination of parameters:¶ In Resource specify a resource name.¶ Specify in Treat input as how you want the input you entered

in the Resource field to be treated. Select one of the followingoptions:Wildcard Treat special characters as wildcards.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 ID.¶ Specify whether the resources are data sets with the DLF

attribute or not, or if this is to be ignored, in Hiperbatch.



¶ Click OK to add the new list to the engine tree.

To display the list, right-click it and select Load List.

Figure 14. The Properties - Database Resource List Window


8.M

anag

ing

Reso

urces

inth

eD

atabase

Using Resource ListsWhen you open a database resource list, all the resources defined in the database thatrespond to the filter criteria are displayed in the right-hand pane of the Job SchedulingConsole.

The following sections explain how to use database resource lists to work with resourcesdefined in the resource description database. From the display produced by opening adatabase 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. Forinformation about how to work with plan resources, see “Browsing and ModifyingResources” on page 176.

Displaying a List of Resources in the DatabaseTo display a list of resources defined in the database:

1. In the Job Scheduling view, right-click the list object you want to use to list theresources and select Load List from the pop-up menu.

2. The resources are displayed in the right-hand pane.

For each resource, the display shows:

¶ Name and description

¶ Resource group name

¶ If the resource has the DLF attribute

¶ How the resource is to be acted upon when a job that allocates this resource ends inerror

¶ Date and operator of last update of the resource properties

Figure 15. List of Resources in the Database

76 Version 8.1

Modifying Resource Properties in the DatabaseTo modify the properties of a resource displayed in a list:

1. In the Job Scheduling view, right-click the resource and select Properties from thepop-up menu.

The Properties - Resource in Database window is displayed.

2. Make your changes to the resource properties. For a description of the fields in thiswindow, see “Creating Resources” on page 70.

3. Click OK to save your changes to the resource definition.

Deleting Resources from the DatabaseTo use a list to delete a resource from the resource description database:

1. In the Job Scheduling view, right-click the resource and select Delete from the pop-upmenu. A confirmation window is displayed.

2. Click OK to delete the resource from the database.

Creating Resources from Existing Ones in the DatabaseYou can select a resource in a list and use its definition to create other resources with equalor similar properties. After you have displayed a list of resources, do the following:

1. In the Job Scheduling view, right-click the resource that you want to use as a model forcreating another resource and select Create Another from the pop-up menu. TheProperties - Resource in Database window is displayed, showing the resource youselected.

2. In the Name field, change the default name to the name of your choice. If you do notchange the name, the new resource is saved as CopyOfname, where name is the modelresource name.

3. Change any other properties that you need to customize for the new resource.

4. Click OK to save the new resource. The window is closed and the new resource isadded to the database.

5. To view the new resource, either click the Refresh List Results button or run anotherlist.

Figure 16. The Properties - Resource in Database Window


8.M

anag

ing

Reso

urces

inth

eD

atabase

78 Version 8.1

Creating Job Streams

A job stream is a sequence of jobs that includes the resources and workstations that supportthe jobs, together with scheduling information. There are three types of job stream:

Job stream templateDoes not go into the plan. Contains only scheduling information for the job streams thatbelong to it. You create run cycles but no jobs.

Job stream that inherits its scheduling information from a job stream templateUses the scheduling information defined in the job stream template. You thereforecreate jobs but no run cycles.

Normal job streamYou create both jobs and run cycles.

You determine the type when you specify the job stream properties.

To create a job stream, you perform the following tasks:

Table 28. Tasks in Creating a Job StreamTo perform this task ... See ...

Specify the new job stream properties “Specifying Properties for the Job Stream” onpage 80

Create jobs “Creating a Job” on page 82

Create dependencies between jobs, wherenecessary

“Creating Dependencies between Jobs” on page 91and “Creating Dependencies between Job Streams”on page 92

Create one or more run cycles to specify whenthe job stream runs

“Scheduling Job Streams” on page 94

9


9.C

reating

Job

Stream

s

Specifying Properties for the Job StreamTo create a job stream or job stream template, select a Workload Scheduler for z/OS enginein the Job Scheduling view and click the New Job Stream button. The Job Stream Editorand the Properties - Job Stream window are displayed.

Use the information in Table 29 to enter all the information needed for this window.

Table 29. Properties - Job Stream Window InformationIn 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 streamor template. You can define up to four job streams and job streamtemplates 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 streamtemplate contains run cycles but no jobs. All job streams defined asbelonging 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 thatbelongs to a job stream template. The job stream is scheduled using thetemplate run cycle information.

Active Select this check box to schedule the job stream. If you are creating acomplex job stream that requires time to define, do not select this checkbox until you have added all jobs, specified dependencies, and created arun cycle. This avoids the risk that the incomplete job stream will beincluded in any plans. You can make the job stream active after you havecompleted it.

Valid Date Specify the time period covered by the job stream. You can specify onlythe From date. A To date of 12/31/2071 is automatically assigned byWorkload Scheduler for z/OS. To change the From value, click the smallcalendar button to select a valid From date. You can create several jobstreams with the same name but with different dates in the From field.The scheduler picks the correct version for the day it is planning.

Figure 17. Properties - Job Stream Window

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 jobsstreams. The lowest priority is 1 and the highest priority is 9. This meansthat, when job streams are competing for resources, a job stream with apriority of 3 will run before a job stream with a priority of 1. This valueis not definitive. Other factors, such as resource and workstationdependency, are considered in determining priority. This field does notapply to job stream templates.

Authority group name Enter a name to be used to generate a RACF resource name for authoritychecking. This information is optional.

Calendar Specify the name of the calendar of workdays and freedays, includingholidays, that you associate to the job stream. If you need to, click theellipsis (...) to open a Find window (see “Finding Objects” on page 48).If you leave this field blank, the scheduler uses the calendar specified inthe initialization parameter CALENDAR during startup of the TCP/IPserver.Note: The calendar that you specify here is used to display the run daysof the job stream in the Run Cycle view of the Job Stream Editor. It isnot necessarily the calendar that is used to determine the actual run daysof the job stream instances that are generated.

Owner Enter the name of the person responsible for the job stream or template.

Owner description Enter a description of the job stream or template.

Contains Monitored Job Indicates whether any jobs in this job stream will be monitored by TivoliBusiness Systems Manager when they run. The value is Yes if IsMonitored Job is selected in the properties window of one or more ofthe jobs in the job stream. This field is read-only.

Click OK to proceed. The following happens:

Table 30. What Happens When You Define a Job StreamIf you are creating a ... This happens ...

Job stream template The Job Stream Editor opens the Timeline view, where you canopen the Run Cycle view. You can add only run cycleinformation.

Job stream as belonging to atemplate

The Job Stream Editor opens the Graph view where you cancreate jobs.

Single job stream The Job Stream Editor opens the Graph view from where youcan add jobs and dependencies, and switch to the Run Cycleview to add run cycles.

Note: The Workload Scheduler for z/OS ISPF main panel, option 1.8, allows you to create ajob stream containing a single job by specifying only the name of the JCL associatedwith the operation. This option is not available in the Job Scheduling Console. Tocreate job streams with a single job, you must follow the steps in this chapter.


9.C

reating

Job

Stream

s

Creating a JobAfter you have specified the properties of a job stream, you can create the jobs thatcomprise it in the Graph view of the Job Stream Editor.

The Graph view displays an button for each possible type of job that you can define inWorkload Scheduler for z/OS. Table 31 describes these job buttons:

Table 31. Graph View Job ButtonsThis button ... Denotes this job type ...

Add JCL JobA job that consists of JCL statements. Runs on computerworkstations.

Add Started Task JobA job to start or stop a task that has alreadystarted. Runs on computer workstations.

Add Printer JobA job to print the output of a predecessor job. Runs onprinter workstations.

Add General JobA job to include activities other than printing andprocessing, such as manual activities. Runs on general workstations.

Add Setup JobA job containing a set of JCL statements for a JCL orstarted task job. Runs on general workstations.

Add Write-to-Operator JobA job containing an operator instructiondisplayed on the system console. Runs on general workstations.

Add FTW TaskAdd a task to run on a fault-tolerant workstation.

Add Dependency on External JobCreate, browse, or modify adependency on a job that is part of another job stream.

Add LinkCreate a link between jobs.

Graph ViewChange to the Graph view.

Timeline ViewChange to the Timeline view.

Run Cycle ViewChange to the Run Cycle view.

The property windows for the different job types are identical. However, when you save thejob stream, Workload Scheduler for z/OS applies different validation policies, based on thejob type, to the properties that you specified. Moreover, when you use the Find tool tosearch for a target workstation, the tool lists only workstations that are compatible with thespecific job type.

82 Version 8.1

Creating a Job Using ButtonsTo create a job in the job stream, click one of the job buttons in the Graph view of the JobStream Editor, depending on the type of job that you want to define. For example, the AddJCL 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 InformationIn this area ... Do this ...

Identifier Enter the job number. This information is required and must be uniquewithin the job stream.

Target workstation The name of the workstation on which the job is run. This informationis 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 boxesin 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 Targetworkstation 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 resourcesare available). Auto submit is selected by default.

Figure 18. Properties - JCL Job General Page


9.C

reating

Job

Stream

s

Table 32. Properties - JCL Job General Information (continued)In this area ... Do this ...

Cancel if late Select this to prevent the job from being started if it is late (accordingto the time dependencies specified in the Time Restrictions page).Note: select this option only for time-dependent jobs (time-dependentjobs must have an earliest start time and a deadline specified on theTime Restrictions page).

Deadline WTO Select this to issue an operator message if the job passes its deadline.The message is also written to the message log.

Auto release Select this to release the job when it is not submitted by WorkloadScheduler for z/OS and is in HOLD status. The job is released when alldependencies are satisfied and the requested resources are available.Auto release is selected by default.

Auto error completion Select this to mark the job ended-in-error (E) if an error occurs when itruns. Auto error completion is selected by default. If you clear it, thejob is marked complete (C) when it ends, regardless of the outcome.

Is Monitored Job Select this to specify that the running of this job is to be monitored byTivoli Business Systems Manager.

Restart and Cleanup Specify which data set and job restart actions must be performed if thejob ends in error. This option is not available for fault-tolerantworkstations.None

No cleanup and restart actions are performed. This is the default.Immediate

Data set cleanup is performed automatically when the job fails.This option is not linked to a restart, which must be initiatedseparately.

AutomaticData set cleanup is performed automatically during the rerun of thefailed job. The engine builds a set of cleanup actions that areperformed when the first step of the restarted job runs (inserted bythe scheduler). This is the preferred method of running restart andcleanup.

ManualRestart and cleanup actions are to be initiated manually from theModify Current Plan ISPF dialog.

Expanded JCLSpecifies that the JCL used for step-level restarts and, optionally,job reruns, should not be the JCL contained in the schedulerlibraries but the JCL image captured from the JESJCL sysout dataset. This is the default and recommended option.

Use Sys OutSpecifies that user sys out data sets should be used for job restarts.

84 Version 8.1


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 activeagain.

No Restarts the job, even if it overrules the installation default in theWSFAILURE or WSOFFLINE parameters of the JTOPTSinitialization statement.

DefaultUses the installation default action specified in theOPRESTARTDEFAULT keyword of the JTOPTS statement. This isselected by default.

Reroutable Specify whether to make the job eligible to be rerouted if itsworkstation becomes inactive. This option applies to the job only whenit is in ready (R) or waiting (W) status.Yes Makes the job reroutable.No Makes the job not reroutableDefault

Takes the installation default action specified in theOPRESTARTDEFAULT keyword of the JTOPTS statement. This isselected by default.

Highest acceptable returncode

Specify the highest acceptable return code from any step in the jobbefore the job is set to ended-in-error (E) status. If you leave this fieldblank, Workload Scheduler for z/OS uses the value specified inHIGHRC in the initialization parameter JTOPTS.

Feedback options The scheduler automatically monitors the actual durations of jobs. It canuse these durations to modify the estimates in the application description(AD) database. In the Feedback options group box, specify twoparameters that control how measured durations are used:¶ In the Smoothing factor field, type a number, from 0 to 999, that

determines how much a measured duration will change existingvalues in the AD database. If a measured duration is outside thelimits established by the Limit for feedback field, the smoothingfactor is not applied and the AD database is not updated.

¶ In the Limit for feedback field, type a number, from 100 to 999, toestablish the limits within which measured values are regarded asnormal and acceptable. A measured value outside the limits isignored. That is, no smoothing factor is applied and the ADdatabase is not updated.

Critical job Select this if you want to define the job as a critical job. This makes thejob eligible for Workload Manager (WLM) service class promotionwhen the job runs late. Available for OPC 2.3 only.


9.C

reating

Job

Stream

s


WLM policy If you selected the Critical job check box, click the WLM policydrop-down list to select the type of policy applied for WLM serviceclass promotion when this job is late. The policy can be:Conditional

The scheduler uses an algorithm to determine whether to applythe Deadline or the Latest start option.

DeadlineThe scheduler intervenes if the job runs beyond the deadline.

Latest startThe scheduler intervenes immediately if the job starts after thelatest start time.

Long durationThe scheduler intervenes if the job takes longer than it should ascompared to the statistics that it keeps.

This option is available for OPC 2.3 or later.

Select Task in the left pane. The Task page is displayed.

Task PageIn the Task page, enter information about the program associated with the job.

Note: If the task is a manual operation, leave this page blank.

Figure 19. Properties - JCL Job Task Page

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 InformationIn this area ... Enter this information ...

Task name The name of the JCL associated with the job, when applicable. Togetherwith the identifier you specified in the previous page, the task namelabels 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 engineto 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 jobclass from the JCL.

Select Time Restrictions in the left pane. The Time Restrictions page is displayed.

Time Restrictions PageIn the Time Restrictions page, specify the period of time that the job is allowed to run andthe amount of time the job requires.

Use the information in Table 34 on page 88 to enter all the information required to define thetime restrictions.

Figure 20. Properties - JCL Job Time Restrictions Page


9.C

reating

Job

Stream

s

Table 34. Properties - JCL Job Time Restrictions InformationIn this area ... Do this ...

Start Specify the time at which the job can start, in one of the followingways:¶ Select No restrictions to run the job as soon as all dependencies are

met. No time restrictions can result in more efficient processing forcertain jobs when extending a plan. In this way, they are run assoon as dependencies are satisfied. If this job is not time dependent,click this option.Note: This choice is not valid if you selected Cancel if late in theGeneral page.

¶ Select Follow job stream rules to specify that the earliest time thejob can start is when the job stream starts. This is the default.Note: This choice is not valid if you selected the Cancel if latebox in the General page.

¶ Select Specify earliest start time to define a specific time beforewhich the job should not start. Then:1. In the At field, enter a time, according to your local settings.

For example, enter 12:00 if you do not want the job to startbefore noon.

2. In the Delay for field, type a number of days to defer thestarttime. For example, if you type 3, the job will start three daysafter the time you originally specified in the At field.

Deadline Specify the latest time that the job can end. To do this, select Specifydeadline and use the At and Delay for fields. The default is nodeadline time.

Duration Specify how long the job is expected to run, in hours, minutes, andseconds.


88 Version 8.1

Resources PageIn the Resources page, describe the parallel servers, and the logical and workstationresources that the job uses.

In the following procedure, you perform the following actions on target resources andlogical resources, which you access from the drop-down list:

Target resourcesWhere you specify the workstation (or fixed) resources, and the parallel servers, thatthe job needs to run.

Logical resourcesWhere 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 specifythe target resoruces.

2. Double-click each cell in the Quantity column to edit the amount of resources Resource1 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 youcan 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 (...).

Figure 21. Properties - JCL Job Resources Window


9.C

reating

Job

Stream

s

6. For each logical resource, double-click under each of the next three columns to edit thefollowing attributes:Quantity

Specify the amount of the resource needed by the job.Access type

Specify whether the job needs shared or exclusive access to the resource.Keep on error

Specify whether the job keeps or frees the resource when it fails. You can alsospecify to use the default defined in the ONERROR keyword of the RESOPTSstatement.

When you have finished, click OK to save your changes and close the window. The new jobis 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 associatedand 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 inand zoom out the jobs displayed. When you move the slider downwards to zoom outof the Graph view, the job buttons change their appearance, changing color dependingon the job type.

Creating a Job Using Copy and PasteTo 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 thepop-up menu.

2. Right-click the mouse somewhere in the window and select Paste from the pop-upmenu. 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 theGraph view.

Figure 22. Job Stream Editor Graph View

90 Version 8.1

Creating Dependencies between JobsWhen you create dependencies, you link jobs in a sequence. A successor job cannot beginuntil 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 anaccount (Job A) before you calculate the account balance (Job B). Here, Job A is thepredecessor and Job B the successor.

Creating Dependencies within a Job StreamTo 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 displayedbetween the two jobs, with an arrow pointing to the successor job.

3. Repeat the previous steps to create as many dependencies as you need.

Figure 24 shows that jobs 04 and 05 can start only when job 03 has finished, and thatjob 03 can start only when job 02 has finished.

Figure 23. Job Stream Editor - Add Link

Figure 24. Job Stream Editor - Example Dependent Jobs


9.C

reating

Job

Stream

s

Creating Dependencies between Job StreamsExternal jobs represent jobs that are part of other job streams. You create a dependencybetween jobs in different jobs streams by creating a dependency on an external job. Forexample, if Job C in the Accounts job stream depends on Job B in the Reports job stream,you create an external job in the Accounts job stream to represent Job B, then you create adependency between Job C and the external job.

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” onpage 115.

To create a dependency between job streams:

1. In the Job Stream Editor Graph view, click the Add Dependency on External Jobbutton. The Properties - External Job window is displayed.

2. In the Job Stream field, enter the name of the job stream containing the external job. Ifyou 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.

Figure 25. Properties - External Job Window

Figure 26. Selecting the External Job

92 Version 8.1

5. Repeat the steps explained in “Creating Dependencies between Jobs” on page 91 todefine links with the other jobs. In the example in Figure 28, job 05 can start only afterjob 03 has finished, and also after job 1 of the TWSPRO1 job stream has completed.

Figure 27. Job Stream Editor — External Job Button

Figure 28. Job Stream Editor — Example External Job Dependency


9.C

reating

Job

Stream

s

Finding a Job StreamIf you do not know the name of the job stream that contains the external job, perform thefollowing steps to search the job streams database:

1. Click the ellipsis (...) to open the Find Job Stream window. This window allows you toenter criteria to search the database for existing job streams.

2. In the Find field, enter a search string to locate the job stream. You can use wildcards orleave the field blank to display a list of all job streams.

3. Use any of the Filter Criteria elements to find the job stream that contains the job youwant. You can write search strings with wildcard characters. Use the information inTable 35 to specify the filter criteria.

Table 35. Filter CriteriaIn this area ... Enter this information ...

Task name Name of a task contained in the job stream.

Job stream template Name of the job stream template to which the jobstream belongs.

Owner Identity of the owner of the job stream.

Is a template Select this to search for job stream templates.

Status of Job Stream Select one of the buttons to search for active,inactive, or all job streams regardless of their status.

4. Click Start. A list of job streams is displayed.

5. Double-click the name of a job stream. The Find Job Stream window closes and the jobstream is displayed in the Job Stream field in the External Dependency Propertieswindow.

Scheduling Job StreamsAfter creating the jobs and defining any existing dependencies between them, you specifythe scheduling information for the job stream using run cycles. Run cycles are generatedfrom a combination of:

¶ A calendar of workdays and freedays. The calendar is defined in Workload Scheduler forz/OS. You specify its name in the Job Stream Properties window (see “SpecifyingProperties for the Job Stream” on page 80).

¶ The validity date of the job stream, which you specify in the Job Stream Propertieswindow.

Types of Run CycleYou can create two types of run cycle:

¶ Rule-basedUses rules based on lists of ordinal numbers, types of days, and common calendarintervals or period names. For example, the last Thursday of every month. Rule-basedrun cycles are based on conventional periods, such as calendar months, weeks of theyear, and days of the week, or periods that you define, such as a semester.

¶ Offset-basedUses a combination of user-defined periods and offsets. For example, an offset of 3 in a

94 Version 8.1

period of 15 days is the third day from the beginning of the period. It is more practicalto 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 newones 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 cyclesspecify the days that the job stream must run. Exclusionary run cycles specify the days thatthe job stream must not run. You can add run cycles to generate more days, or to havemultiple instances on the same day. You can add exclusionary run cycles to exclude some ofthe days already generated.

Creating a Run CycleTo create a run cycle, in the Job Stream Editor, click the Run Cycle button. The Run Cycleview is displayed.

Table 36. Run Cycle ButtonsIf you are going to use ... Click the ...

Rules Rule-based Run Cycle button

Offsets Offset-based Run Cycle button

Depending on which choice you make, either the Properties - Rule-based Run Cycle windowor the Properties - Offset-based Run Cycle window is displayed.

General PageThe Properties - Rule-based Run Cycle General page is similar to the Properties -Offset-based Run Cycle General page.

Figure 29. Job Stream Editor - Run Cycle View


9.C

reating

Job

Stream

s

Use the information in Table 37 to specify whether the run cycle is exclusionary, the periodthat the run cycle is valid, and how to handle freedays in the schedule.

Table 37. Run Cycle General InformationIn this area ... Do this ...

Name Type a name for the run cycle.Note: Offset-based run cycles take the name of theperiod specified in the Offsets page. See “CreatingOffset-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 fromrunning.

Valid Date Use the From and To drop-down lists to specify aninterval of time for which the run cycle applies. Click thecalendar buttons next to each field to select dates usingpop-up calendars. The intersection between this valid dateand the valid date you defined in the Job StreamProperties window is the interval during which the jobstream is actually scheduled.

Figure 30. Properties - Rule-based Run Cycle General Page

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 totreat freedays when calculating the rundays of the jobstream, by selecting one of the following:Count workdays only

Excludes freedays when calculating on which daysthe job stream runs. This is the default foroffset-based run cycles.

Schedule on last workday before freedayCounts both workdays and freedays. If the rundayfalls on a freeday, it is shifted to the closest workdaybefore the freeday.

Schedule on next workday after freedayCounts both workdays and freedays. If the rundayfalls on a freeday, it is shifted to the closest workdayafter the freeday.

Count workdays and freedays alikeCounts both workdays and freedays. The job streamis scheduled on the runday, regardless whether it is afreeday or a workday. This is the default forrule-based run cycles.

If freeday, do not schedule at allCounts both workdays and freedays. If the rundayfalls on a freeday, the job stream is not scheduled torun.

JCL variable table Type a name of the variable table that the scheduler canuse on the days generated by this run cycle. Alternatively,click the ellipsis (...)to search for a variable table name.


Time Restrictions PageThe Properties - Rule-based Run Cycle Time Restrictions page is similar to the Properties -Offset-based Run Cycle Time Restrictions page.

Figure 31. Properties - Rule-based Run Cycle Time Restrictions Page


9.C

reating

Job

Stream

s

Use the information in Table 38 to complete the fields in this window.

Table 38. Run Cycle Time Restrictions InformationIn this area ... Do this ...

Start In the At field, enter the time when the job stream must start. Thedefault is 00:00 of the scheduled day.

Deadline You can use deadline time to control the correct completion of theschedule and also to make closer estimates of the duration of a jobstream.At Type a time when the job stream must stop.Type for

Enter a number of days after the start of the schedule.The default is no deadline time.

Note: If you are creating an exclusionary run cycle, be sure to match the time restrictions of the runcycle that it is intended to annul.

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 RunCycles”.

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 RunCycles” on page 102.

Creating Rule-based Run CyclesUse the information in Table 39 on page 99 to specify the elements that make up the ruleson which the run cycle is based.

Figure 32. Properties - Rule-based Run Cycle Rules Page

98 Version 8.1

Table 39. Rule-based Run Cycle Rules InformationIn this area ... Do this ...

Periods Select Week, Month, Year, or User-defined (a period that youhave defined in the scheduler). You can check more than oneperiod at a time for complex rules specifying more cycles. Forexample, you can check Week and Month, and then choose thedays that apply to both rules. You do not need to select the samedays twice, since they are fitted automatically to all cycles.

Ensure that the period you select is also highlighted so that theother options in the page are enabled. The period that you selectaffects the number of days listed in the Available daysscroll-list. Also, the In the following group changes dependingon the period you select.

Frequency OnlySelect this if the rule applies to only one day in thespecified period. The rule does not repeat within the period.For example, Only last Monday in Month schedules the jobstream to run on the last Monday of the month.

EverySelect this if the rule is used to calculate more than one daywithin the period. For example, Every last Monday inMonth schedules the job stream to run on every Monday inthe month, since this rule generates a series of Mondaysstarting from the last Monday.Note: Every first day yields the same rundays as Every day.

Shift originIf you use Every, you can shift the origin of the run cycleby the number of days you write in the Shift origin field.You shift the origin of the run cycle with respect to thedefault origin, which is Monday in the Week period, and thefirst week with at least 4 days in the Month and Yearperiods. You can also shift the origin from the end, if youspecify a combination of Every and ordinal-last days.

Available days Select the days of the period to which the rule applies. Thenumber of available days changes according to the period youselect. You can also specify ordinal-last days to count backwardsfrom the end of the period. The days you select are displayed inthe Selected Days field.

Available types of days Select the types of days to which the rule applies. The types ofdays you select are displayed in the Selected Types of Daysfield.

In the following ... Select this to specify by name the periods to which you want therule to apply. Depending on the period you select (Week, Month,Year, User-defined), this option displays lists of weeks of theyear by number, or months by name.

If you selected a user-defined period, a list of available periods isdisplayed in the In the following Periods group. Select thecheck box next to the period you want to use.


9.C

reating

Job

Stream

s

The next figure shows a rule that schedules the job stream to run on the fifth day of everyweek.

Click OK. The following happens:

¶ Workload Scheduler for z/OS calculates the days of the run cycle.

¶ The run cycle name is displayed in a list to the left of the graphic calendar in the RunCycle view. If you right-click it, you can then select a number of actions on the runcycle, such as Properties, Copy, and Delete.

¶ The rundays are displayed in blue in the graphic calendar. When you select the run cyclefrom the list, a blue stripe is displayed at the top of the corresponding generated days.

Example 1: Rule-based Run CycleThe next figure shows a rule-based run cycle that uses the rule shown in the precedingexample, starting from a Valid date of July 20, 2001, and where workdays and freedays arecounted alike.

Figure 33. Example Rule

Figure 34. Example 1: Rule-based Run Cycle

100 Version 8.1

Example 2: Exclusionary Run CycleThe next figure shows an exclusionary run cycle called WPREXCEP that prevents jobstream PAYRO21 from running on the last Friday of July 2001.

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.

Example 3: Exclusionary Run Cycle DefinedThe next figure shows the rule defined for the WPREXCEP exclusionary run cycle . Theselected days are equal to those for the WEEKLYPR run cycle. The week when the jobstream must not run is specified in the In the following weeks check box.

Figure 35. Example 2: Exclusionary Run Cycle

Figure 36. Example 3: Exclusionary Run Cycle Defined


9.C

reating

Job

Stream

s

Creating Offset-based Run Cycles

Use the information in Table 40 to specify the combination of period and offsets on whichthe run cycle is based.

Table 40. Offset-based Run Cycle Rules InformationIn this area ... Do this ...

In the following period Type the name of a user-defined period. If you do not know thename, click the ellipsis to use the Find Period window to findall 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 cyclename.

If you need to specify more than one period, create anoffset-based run cycle for each period within the job stream.

Available offsets Select the days when you want the job stream to run in theperiod. Select ordinal last days to count the days from the endof the period.

Click OK. The following happens:

¶ Workload Scheduler for z/OS calculates the days of the run cycle.

¶ The run cycle name is displayed in a list to the left of the graphic calendar in the RunCycle view. If you right-click it, you can then select a number of actions on the runcycle, such as Properties, Add, and Delete.

¶ The rundays are displayed in blue in the graphic calendar. When you select the run cyclefrom the list, a blue stripe is displayed at the top of the corresponding generated days.

Figure 37. Properties - Offset-based Run Cycle Window

102 Version 8.1

Example 1: Offset-based Run CycleThe next figure shows an offset-based run cycle named PER1. This run cycle schedules jobstream PAYRO21 to run on every second day of each cycle, beginning from a Valid date ofAugust 21, 2001.

Example 2: Offset-based Run Cycle DefinedThe next figure shows the offset for run cycle PER1. The offset is the second day of theuser defined period, also named PER1.

Figure 38. Example 1: Offset-based Run Cycle

Figure 39. Example 2: Offset-based Run Cycle Defined


9.C

reating

Job

Stream

s

Checking Time Restrictions in the Timeline ViewThe Timeline view of the Job Stream Editor shows graphically the time restrictions of thejobs and run cycles of a job stream in the database. While you create a job stream, theTimeline view helps you, at a glance, to ensure that the time dependencies you specified arecorrect and coherent. The view can point out inconsistencies between the time restrictions ofjobs and those of run cycles. It can also show if there are inconsistencies within the timerestrictions of individual jobs. You can modify the time restrictions of a job or run cyclewith a click of your mouse.

To open the Timeline view of a job stream, click the Timeline button from the toolbar ofany of the other views of the Job Stream Editor.

See the sample Timeline view in shown in the next figure.

The inside of the window has four panes. You can size the panes by dragging the horizontaland vertical lines that divide the window. The left half of the window, lists the job streamrun cycles in the top pane, and the job stream jobs in the lower pane.

Activity BarsThe right half of the window contains activity bars that represent, on a daily and hourlyscale, the time restrictions defined for every run cycle and job. You can customize thetimescale 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 FrameThe table frame is the left half of the window and contains columns that display thefollowing information:

Figure 40. Job Stream Editor - Timeline View

104 Version 8.1

¶ A warning button for inconsistencies in time restrictions. This button marks a run cyclewhen Workload Scheduler for z/OS detects that there are jobs with time restrictionsoutside the time restrictions of the run cycle.

¶ The run cycle name or job identifier .

¶ An information button showing what type of time restriction, if any, each job has. Thejobs with no restrictions have a lightning bolt, the jobs with a specified start time have aclock, and the jobs that follow job stream rules have a clock superimposed on a jobstream.

¶ The expected start and deadline times of the run cycle or job.

¶ The expected duration of the job.

Time RestrictionsIn the upper right pane, the run cycle time restrictions are displayed by a blue bar thatrepresents the time interval from the start to the deadline of the run cycle. The deadline isindicated by a vertical black line at the end of the blue bar. You can change the start and thedeadline by dragging the left and right ends of the two bars, or by dragging the wholeactivity bar. As you move the bar, an indicator displays the selected time.

Note: The run cycle time restrictions inherited from a template are displayed in read-onlymode. To modify them, you have to open the Job Stream Editor window of theparticular template.

Time restrictions for a job are shown by a thick blue bar that represents the time intervalfrom the start to the deadline of the job, and by a thinner, light blue line that represents theexpected duration. Where the duration of the job exceeds the deadline, the blue bar becomesred. You can move the interval of time between the start and the deadline times of the jobby dragging either end of the thicker bar (or the whole bar). You can only move the rightend of the thinner bar because the start position is calculated automatically based on the jobdependencies. The job deadline is indicated by a black vertical line. If a job has no specifieddeadline, the thick bar is replaced by a vertical stripe indicating the start. You can only moveit forward or backward. To specify a deadline for the job, you have to double-click the jobin the upper left pane and open a Time Restrictions page.

Other TasksIn the Timeline view you can also:

¶ Detect inconsistencies in time restrictions. Specifically, if the time restrictions of any jobare such that it is not within the time restrictions of a run cycle, a warning icon marksthe run cycle that does not include the job. If you point your mouse on the triangle, ahover 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 seethe total run time of the job stream.

¶ Click a run cycle to see how it affects the jobs that start with the job stream. Theactivity bars for jobs that start with the job stream change position when you selectdifferent run cycles.

¶ See which jobs have a specified start time, which jobs follow job stream rules, andwhich jobs have no restrictions on start time, by looking at the button at the beginningof the job activity bar.


9.C

reating

Job

Stream

s

¶ Open the Time Restrictions page of a Run Cycle Properties window or of a JobProperties window by double-clicking on a run cycle or job in the Table frame.

¶ Change the earliest start time, duration, and deadline time of a job by moving differentcomponents of the activity bar. In the same way, you can change the earliest start timeand deadline of a run cycle.

¶ See which jobs start according to the start time of the job stream, and how those jobsare affected by various rules.

Saving a Job StreamAfter you have specified job stream properties and defined jobs, job dependencies, and runcycles, you can save the job stream. Job streams are saved in the scheduler database. Tosave the new job stream, click the Save button in the Job Stream Editor toolbar.

The Job Stream Editor checks for any missing or invalid information, then saves the jobstream in the application description database.

Note: You can save a job stream from any of the three views available in the Job StreamEditor. You can define parts of a job stream, for instance the jobs that are in it, thensave it and open it again later, as explained in the next chapter, to define its runcycles. Just remember to wait to mark it active when it is ready to be scheduled.

Submit a Job StreamTo submit an existing job stream into the plan, right-click a scheduler engine and selectSubmit Job Stream from the pop-up menu. The Submit Job Stream window is displayed.

Use Table 41 to complete the information needed to submit the job stream.

Table 41. Submit Job Stream WindowIn this area ... Enter this information ...

Job Stream Name The name of the job stream. If you do not remember the name of thejob stream, click the ellipsis (...) to open a Find Job Stream window.

Figure 41. Submit Job Stream Window

106 Version 8.1

Table 41. Submit Job Stream Window (continued)In this area ... Enter this information ...

Start The Date and Time when the job can start. The defaults are the valuesin the first run cycle.

Deadline The latest Date and Time when the job stream can end. The defaultsare the values in the first run cycle.

Status of Job Stream One of the following:Simple Submit

Adds a new job stream instance in the plan.Submit & Hold

Adds a new job stream instance in the plan but it does not start.It is on hold.

Submit & EditAdds a new job stream instance in the plan and opens the Graphview so you can modify the submitted job stream instance.

Properties Opens the Submit Job Stream Header Info window where you canmodify various properties of the job stream:Priority

How the job stream ranks in importance compared to other jobsstreams. The lowest priority is 1 and the highest priority is 9. Thismeans that a job stream with a priority of 3 will run before a jobstream with a priority of 1 when job streams are competing forresources. This value is not definitive. Other factors, such asresource and workstation dependency, are considered indetermining priority. This field does not apply to job streamtemplates.

Authority GroupName used to generate a RACF resource name for authoritychecking. This information is optional.

DescriptionA brief description of the job stream.

OwnerName of the person responsible for the job stream.

Owner descriptionA brief description of the job stream owner.

JCL variable tableName of the variable table that the scheduler can use on the daysgenerated by this run cycle. Alternatively, click the ellipsis tosearch for a variable table name.

Job stream templateName of the job stream template to which the job stream belongs.


¶ Click OK to submit the job stream and close the window.

¶ Click Cancel to close the window without submitting the job stream.


9.C

reating

Job

Stream

s

108 Version 8.1

Listing and Modifying Job Streams

To view job streams, you must create and display a job stream list in the Job Schedulingview. You can create two types of job stream list:

Job stream listProduces a filtered list of job streams or job stream templates defined in the WorkloadScheduler for z/OS Application Description database.

Job stream instance listProduces a filtered list of already scheduled job stream instances together with theirtime restrictions.

This chapter explains how to list job streams from the Workload Scheduler for z/OSdatabase 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 instancelists, see “Managing Job Streams” on page 127.

Default Job Stream ListThe Job Scheduling Console provides a job stream list. You can find it in the DefaultDatabase Lists group in the tree of every engine shown in the Job Scheduling view. The listis called All Job Streams and displays all the job streams defined in the WorkloadScheduler for z/OS database.

This list works like any other user list. You can display its properties and see from theempty fields that no selection criteria are specified. You can modify properties and makethem less general by adding the filters of your choice.

Creating a Job Stream ListA job stream list allows you to view and modify job stream definitions, which are stored inthe database. You can:

¶ Open and delete a job stream, and modify job stream properties

¶ Define new job streams starting from existing definitions

¶ Create and delete jobs and external jobs, and modify job properties

¶ Add and delete dependencies between jobs

¶ Create and delete run cycles, and modify run cycle properties

¶ View and change the time restrictions of run cycles and jobs

10


10.L

isting

and

Mo

difyin

gJo

bS

treams

The changes you make from a job stream list already generated will not reflect thesechanges.

To create a job stream list, select an engine in the Job Scheduling view and click the ListJob 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 streamlist.

Table 42. Properties - Job Stream List InformationIn this area ... Do this ...

Name Type a name for the job stream list.

Periodic Refresh Options Periodic RefreshSelect this if you want the list results refreshed automatically, thenspecify a refresh interval in seconds.Note: Do not specify frequent refreshes of many detached viewsopen at the same time in order to prevent from overloading yoursystem.

—OR—Apply Defaults

Click this to use the defaults specified in the Scheduler Propertieswindow available in the Job Scheduling view.

Figure 42. The Properties - Job Stream List Window

110 Version 8.1

Table 42. Properties - Job Stream List Information (continued)In this area ... Do this ...

Filter Criteria Specify any of the following search parameters, or combinations of twoor 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 RACFauthority checking.

CalendarLists all the job streams that use this calendar.

WorkstationLists all job streams containing jobs that run on this workstation.

Is a templateLists only job streams that are templates.

Exclude templateLists only job streams that are not templates.

PriorityLists all the jobs streams that have the priority level you select inFrom and To.

DatesLists all the job streams valid within the interval you specify inFrom and To.

Status of Job StreamLists all the currently active or inactive job streams, depending onwhich button you select. The default is to ignore this criteria.

Contains Monitored JobYeslists only job streams that contain jobs selected for monitoringby Tivoli Business Systems Manager.Nolists only job streams that contain jobs that are not selected formonitoring by Tivoli Business Systems Manager.Ignore criterialists job streams, regardless of whether they contained jobsthat 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 treeunder the engine you selected at the beginning. Optionally, before saving it, you can run thelist by clicking Apply.


10.L

isting

and

Mo

difyin

gJo

bS

treams

Displaying a Job Stream ListTo display a list of job streams in the database, create a list as described in “Creating a JobStream List” on page 109 and run it by clicking on Apply. Alternatively, use an existing list.

To use an existing Job stream list:

1. Select an engine to display all the created lists in the right-hand view of the console.

2. Double-click the list object you want to use, as shown in the next figure.

The list of job streams is displayed in the right-hand pane.

The job streams are listed by:

¶ Name

¶ Description

¶ Priority level

¶ Start of validity

¶ End of validity

¶ Status (active or inactive)

¶ Authority group ID

¶ Calendar

¶ The owner ID and description

¶ When and by whom the definition was last updated

Modifying Job StreamsModifying a job stream involves changing any of the following:

¶ The job stream properties.

¶ Any of the jobs that it comprises, as well as any dependencies that might exist amongthem.

¶ Any of the run cycles that define its scheduling.

Figure 43. Displaying the Results of a Job Stream List

112 Version 8.1

To modify jobs and run cycles, open the job stream from the list. The type of job streamdetermines 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 openthe Graph view only. Open the template to see the scheduling information for the jobstream.

Modifying Job Stream PropertiesTo 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 JobStream” on page 80 for details about the Job Stream Properties window).


¶ Click OK to save the changes.

¶ Click Cancel to discard your changes and close the window.

Adding and Modifying Jobs and Dependencies in the Graph ViewTo add, modify, or delete jobs and dependencies in an existing job stream:

1. Display a job stream list.

2. When the list is displayed, double-click the job stream you want to open. The Graphview of the Job Stream Editor opens.

Table 43. Adding and Modifying Jobs and Dependencies in the Graph ViewTo do this ... See ...

Create a new job in the job stream “Creating a Job” on page 82.

Add a new external job in the job stream “Creating Dependencies between Job Streams” onpage 92.

Add a new dependency between jobs inthe job stream

“Creating Dependencies between Jobs” on page 91.

Modifying a Job1. 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 questionmark, this is an indication that the definition of the workstation associated withthe particular job cannot be found in the database. Likewise, if an button labeldisplays a (Not Found) string, it means that an external job is missing becausethe 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” onpage 82).

3. Click on Save.


10.L

isting

and

Mo

difyin

gJo

bS

treams

Adding a New Job using Copy and PasteYou can use the Copy and Paste functions to save time when creating a job that shares manyof the properties of an existing job in the job stream. For more information, see “Creating aJob Using Copy and Paste” on page 90.

Deleting a Job or External JobTo delete a job or external job from the job stream:

1. In the Graph view of the Job Stream Editor, right-click the job or external job and selectDelete from the pop-up menu.

2. Click OK in the confirmation window. The job is deleted from the job stream.

Note: If you change your mind, you can use the Undo Delete option in the same pop-upmenu 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.

Editing Another Job Stream from an External JobUse an external job to open a second Job Stream Editor window and edit the job stream towhich the job belongs. To do this:

1. In the Graph view of the Job Stream Editor, right-click the external job and select Editfrom the pop-up menu, then External Job Stream. An additional Job Stream Editorwindow is displayed.

2. As necessary, open the views to work on the job stream and its components.

Removing a Dependency between Jobs1. In the Graph view of the Job Stream Editor, right-click the line that represents the

dependency. The line becomes red and a pop-up menu is displayed

2. Select Delete from the pop-up menu. A confirmation window is displayed.

3. Click OK in the confirmation window. The dependency is removed.

4. Click Save to save the job stream.

Adding and Modifying Run CyclesSelect a job stream from a job stream list and open the Run Cycle view of the Job StreamEditor. In this way, you can work on existing run cycles or create new ones.


2. When the list is displayed, double-click the job stream you want to open.

3. Click the Run Cycle button to open the Run Cycle view of the job stream.

4. Select a run cycle in the run cycle list and right-click it to display the pop-up menu.

Table 44. Adding and Modifying Run Cycles – Pop-up Menuclick this option ... To do this ...

Properties... Edit the run cycle properties in the Run Cycle Properties window.See “Scheduling Job Streams” on page 94 for reference.

114 Version 8.1

Table 44. Adding and Modifying Run Cycles – Pop-up Menu (continued)click this option ... To do this ...

Copy Create an additional run cycle with the same properties as theselected one. A Rule-based Run Cycle Properties window or anOffset-based Run Cycle Properties window opens with the samedefinitions as the model run cycle. Modify any definitions you needto, and enter a new name before saving.

Delete Delete the run cycle from the job stream.

Viewing and Modifying Time RestrictionsThe Timeline view of the Job Stream Editor shows the time restrictions of the jobs and runcycles of a job stream. You can modify the time restrictions of a job or of a run cycle, in thesame way you created them, by using either the Job Properties window of the Graph view orthe Run Cycle Properties window of the Run Cycle view.

In addition, you can view and modify time restrictions for more than one run cycle andmore than one job in the Timeline view. For a full description of the Timeline view of a jobstream, see “Checking Time Restrictions in the Timeline View” on page 104.

Deleting Job Streams from the DatabaseTo delete a job stream from the database, you use a job stream list.

To do this:


2. When the list is opened, right-click the job stream you want to delete and select Deletefrom the pop-up menu.

3. Click OK in the confirmation window. The job stream is deleted.

Using Copy to Add an External JobYou can use the Copy function on a listed job stream to add any of the jobs that comprise itas external jobs to another job stream.

For example:


2. Right-click a job stream and select Open. The job stream opens in the Graph view of theJob Stream Editor.

3. Right-click another job stream in the list and this time select Copy from the pop-upmenu.

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 thesecond job stream are displayed.


10.L

isting

and

Mo

difyin

gJo

bS

treams

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 aredisplayed in the Graph view of the first job stream.

Figure 44. Properties - External Job Window

Figure 45. Job Stream Editor - External Job Added

116 Version 8.1

Using Existing Definitions to Create Other Job StreamsYou can select a job stream from a list and use its definition to create other job streams withequal 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 jobstream and select Create Another from the pop-up menu. The Job Stream Editor and thejob 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 thename of your choice. If you do not change the name, the new job stream is saved asCopyOfname, 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 thatyou 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 orrun another list to view the new job stream.


10.L

isting

and

Mo

difyin

gJo

bS

treams

118 Version 8.1

Listing Job Stream and Job Instances

For jobs and job streams, an instance, also known as an occurrence, is a job or job streamthat has been scheduled in the plan. The plan contains past, present, and future scheduledjob 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” onpage 127 describes how to work with instances from the lists you create.

Creating Lists of Job Stream and Job InstancesYou can maintain several lists by creating list objects with different sets of filter criteria. Forexample, you can maintain lists of job streams for different status and error conditions. Youcan also create lists to monitor the workload in progress or the outcome of scheduled jobs.

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 ListsTo do this ... Perform this task ...

List jobs that have ended in error in thelast 24 hours

Create a list of jobs with a status of Error and a timeinterval between yesterday’s and today’s dates.

Discover all the scheduled jobs thatdepend on a job that you know will endin error

List the job in error and look at all its successors.

Search for all job streams that include aspecific job 3

Create a job instance list and specify the identifier in thefilter criteria. The resulting list displays all instances of job3 and the job stream instance to which it belongs.

See all job stream instances scheduledfor the month of December 2001

Create a job stream instance list and specify the dates in thefilter criteria.

Default Instance ListsThe Job Scheduling Console provides instance lists. You can find them in the Default PlanLists group in the tree of every Workload Scheduler for z/OS engine shown in the JobScheduling view. The instance lists are:

All Scheduled Job StreamsDisplays a list of all the existing job stream instances.

All Scheduled JobsDisplays a list of all the existing job instances.

11


11.L

isting

Job

Stream

and

Job

Instan

ces

The default instance lists work in the same way as user lists. You can display theirproperties and see from the empty fields that no selection criteria are specified. You canmodify their properties and make them less general by adding filters of your choice.

Listing Job Stream Instances

To list job stream instances, in the Job Scheduling view, select an engine and click the ListJob Stream Instances button in the toolbar. The Properties - Job Stream Instance Listwindow is displayed.

Use the information in Table 46 to specify the selection criteria for the list.

Table 46. Properties - Job Stream Instance List InformationIn this area ... Do this ...

Name Type a name for the job stream instance list.

Periodic Refresh Options Periodic refreshSelect this to specify a refresh interval in seconds, if youwant the list results refreshed automatically.

Apply defaultsClick this to use the default specified in the Settings page ofthe Scheduler Properties window.

Filter Criteria

Specify any of the following search parameters, or combinations of two or more parameters. Usewildcards to help your search.

Figure 46. Properties - Job Stream Instance List Window

120 Version 8.1

Table 46. Properties - Job Stream Instance List Information (continued)In this area ... Do this ...

Job stream Lists all the job stream instances with this name or namestring.

Job stream template Lists all the job stream instances that are part of this template.

Occurrence Token Lists the job stream that is identified by this occurrence token inthe plan. The token is a unique 16-character hexadecimal stringassigned to the job stream by the scheduler.

Owner Lists all the job stream instances that belong to this owner.

Authority group Lists all the job stream instances that use this authority group forRACF authority checking.

Dates Lists all job stream instances scheduled to run in an intervalperiod starting on the day and time specified in the From Dateand Time fields and ending in the day and time specified in theTo Date and Time fields. Pop-up calendars are provided to helpyou select the days.

Priority Lists all the job stream instances that have the priority level youselect in From and To.

Manually Added Lists all those job stream instances that were added manually tothe plan (and not automatically through a plan extension), if youselect the Yes radio button. Select No to exclude manually addedjob streams from the list. Select Ignore criteria to omit this filter.

Rerun requested Lists all those job stream instances for which a rerun wasrequested, if you select the Yes radio button. Select No to excludethese job stream instances from the list. Select Ignore criteria toomit this filter.

Contains Monitored Job Yeslists only job streams that contain jobs selected for monitoringby Tivoli Business Systems Manager.Nolists only job streams that contain jobs that are not selected formonitoring by Tivoli Business Systems Manager.Ignore criterialists job streams, regardless of whether they contained jobsthat are monitored by Tivoli Business Systems Manager.

Most Critical Job The start time of the most critical job. If the job stream has nocritical job, the field is blank.

Status Lists all the job stream instances with any of the following JobScheduling Console status codes that you specify in thedrop-down list:¶ Waiting¶ Running¶ Successful¶ Error¶ Canceled


11.L

isting

Job

Stream

and

Job

Instan

ces

Table 46. Properties - Job Stream Instance List Information (continued)In this area ... Do this ...

Internal Status Lists all the job stream instances with any of the following statuscodes that you specify in the drop-down list:¶ Complete¶ Deleted¶ Error¶ Pending predecessor¶ Started¶ Undecided¶ Waiting

Note: Status and internal status exclude each other as filter criteria. However, they are bothdisplayed among the properties of job stream instances. Internal status refers to thestatus code assigned by the specific job scheduling engine. It generally provides moredetail 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 selectedwhen creating it. To display the list, right-click it and select Open. List results are displayedin the right hand pane. Optionally, before saving the list, you can click Apply to display thelist results immediately.

122 Version 8.1

Listing Job InstancesTo list job instances, in the Job Scheduling view, select an engine and click the List JobInstances button. The Properties - Job Instance List window is displayed.


Table 47. Properties - Job Instance List InformationIn this area ... Do this ...

Name Type a name for the list.

Periodic Refresh Options Periodic refreshSelect this to specify a refresh interval in seconds, if you wantthe list results refreshed automatically.

Apply defaultsClick this to use the default specified in the Settings page ofthe Scheduler Properties window.

Filter Criteria


Job stream Lists all the job instances that are in the job stream with this nameor namestring.

Job identifier Lists all the job instances that have this identifier. You cannot usewildcard 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.

Figure 47. The Properties - Job Instance List window


11.L

isting

Job

Stream

and

Job

Instan

ces

Table 47. Properties - Job Instance List Information (continued)In this area ... Do this ...

Authority group Lists all the job instances that use this authority group for RACFauthority checking.

Priority Lists all the job instances that have the priority level you select inFrom and To.

Dates Lists all job instances that are part of job stream instances scheduledto run in an interval period starting on the day and time specified inthe From Date and Time fields and ending in the day and timespecified in the To Date and Time fields. Pop-up calendars areprovided to help you select the days.

Is Monitored Job Select this to specify whether to list jobs monitored by TivoliBusiness Systems Manager.

Yeslists only jobs that are selected for monitoring by TivoliBusiness Systems Manager.Nolists only jobs that are not selected for monitoring by TivoliBusiness Systems Manager.Ignore criterialists jobs, regardless of whether they are monitored by TivoliBusiness Systems Manager.

Restart Option Lists jobs according to their restart and dataset cleanupspecifications.You can use the following filters:CleanUp Type

Select from the drop down list job instances that have one ofthe following cleanup and restart specifications:

NoneImmediateAutomaticManual

CleanUp StatusSelect from the drop down list job instances with either aCompleted or Error cleanup state.

Status Lists all the job instances with any of the following Job SchedulingConsole status codes that you specify in the drop-down list:¶ Waiting¶ Ready¶ Running¶ Successful¶ Error¶ Canceled¶ Interrupted¶ Undecided

124 Version 8.1

Table 47. Properties - Job Instance List Information (continued)In this area ... Do this ...

Internal Status Lists all the job instances with any of the following status codesthat you specify in the drop-down list:¶ Arriving¶ Ready¶ Started¶ Complete¶ Deleted¶ Interrupted¶ Ready-non reporting workstation¶ Error¶ Waiting¶ Undecided

Critical job Lists all the job instances defined as critical jobs. Available for OPC2.3 or later.

WLM policy Lists all the job instances defined as critical jobs and for which theWLM policy you indicate here was defined. click the arrow andselect 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 bothdisplayed among the properties of job instances. Internal status refers to the statuscode assigned by the specific job scheduling engine. It generally provides more detailthan 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 selectedwhen creating it. To display the list, right-click it and select Open. List results are displayedin the right-hand pane. Optionally, before saving the list, you can click Apply to display thelist results immediately.


11.L

isting

Job

Stream

and

Job

Instan

ces

126 Version 8.1

Managing Job Streams

This chapter explains how to:

¶ Browse and modify a job stream instance

¶ Delete a job stream instance

¶ Change the status of a job stream instance to complete

¶ Change the status of a job stream instance to waiting

To perform these actions, you use job stream instance lists.

Job Stream Instance ListsJob stream instance lists are displayed in two ways, the List View and the Timeline View.

List ViewThe List View shows details about each instance.

Timeline ViewThe Timeline View displays graphic information about time restrictions.

In the Timeline View, job stream instances with the same names are listed in groups. Agroup contains two or more job stream instances that have the same job stream name but

Figure 48. Job Stream Instances List View

12


12.M

anag

ing

Job

Stream

s

different run times. Groups are indicated by a small arrow on their left side. Click the arrowto display the individual instances.

The only possible action on a group of job stream instances is Delete all, which you canselect when you right-click the group. To perform the actions listed above and to displayactivity bars on the individual instances, you must first expand the group by clicking on thearrow.

Browsing and Modifying Job Stream InstancesYou can browse and modify job stream instances in the Properties - Job Stream Instancewindow, using the General page, the Time Restrictions page, or both.

Using the General PageRight-click the job stream instance and select Properties from the pop-up menu. TheProperties - Job Stream Instance window is displayed. Most of the details you see are inread-only mode. However, you can modify some editable fields.

Figure 49. Job Stream Instances Timeline View

128 Version 8.1

The General page displays:

¶ The name and description of the job stream.

¶ The occurrence token that identifies where the job stream is in the plan.

¶ If the status is running, at what time the instance started.

¶ If the status is successful, the amount of time it took the instance to complete.

¶ The current status.

¶ The earliest time at which you estimated the instance should start.

¶ The authority group name, if applicable, and the owner.

¶ The name of the calendar used for the schedule.

¶ The priority level. You can raise or lower it if the instance has not yet started.

¶ The name of the table of JCL variables, if any, used by the job stream. You can enter orchange the name of a table. Click the ellipsis button (...) to search for available tables.

¶ The name of the job stream template, if any, to which the job stream belongs.

¶ The name of the function used to schedule the job stream.

¶ Whether the instance has been run again.

¶ The number of jobs that remain to be run in the critical path, their expected duration,and the identifier of the next job scheduled to run on the critical path.

Using the Time Restrictions PageThe Time Restrictions page contains the earliest start time and deadline that you specifiedwhen you created the job stream. You can change them here in the same way as you canchange them by moving the activity bar in the Timeline View.

Figure 50. Properties - Job Stream Instance General Page


12.M

anag

ing

Job

Stream

s


¶ Click Apply to save any changes and keep the window open.

¶ Click OK to save any changes and close the window.

¶ Click Cancel to disregard any changes and close the window.

Changing Time Restrictions in the Timeline ViewThe left-hand pane of the Timeline View displays the following job stream instance details:

Table 48. Job Instance Details Timeline ViewThis column ... Specifies ...

Name The job stream name.

Status The current status.

Started The actual start time.

Runtime The actual duration.

Start at The planned start time.

Deadline The planned deadline.

Figure 51. Properties - Job Stream Instance Time Restrictions Page

130 Version 8.1

The right-hand pane has activity bars that show the actual run time if the instances havebegun, as well as the specified time restrictions for the instances.

By moving components of the activity bars, you can change the time restrictions of eachinstance and view the results of your changes, as you would by following the stepsdescribed in “Browsing and Modifying Job Stream Instances” on page 128 and goingdirectly 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 anddeadline times that were specified as time restrictions for the job stream. The deadline isindicated 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

Figure 52. Timeline View - Left Pane

Figure 53. Timeline View - Right Pane


12.M

anag

ing

Job

Stream

s

Rescheduling the InstanceTo reschedule the instance:

1. Move the activity bar by positioning the mouse pointer inside the bar and, when thepointer becomes cross-shaped, hold down the left mouse button while moving the bar ineither direction.

As you move the bar, a tooltip tells you the new deadline time at every position of theright end of the bar.

2. When you find the position you want, release the mouse button. The Properties - JobStream Instance Time Restrictions window is displayed, showing the new start anddeadline times.

Figure 54. Rescheduling a Job Stream Instance

Figure 55. Properties - Job Stream Instance Time Restrictions

132 Version 8.1

3. Click OK. The activity bar is set on the new position.

Rescheduling the Start TimeTo reschedule the start time:

1. Position the mouse pointer on the left end of the bar. When the pointer becomes adouble 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 start time at every newposition of the left end of the bar.

2. When you find the position you want, release the mouse button. The Properties - JobStream 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 newposition.

Rescheduling the Deadline TimeTo reschedule the deadline time:

1. Position the mouse pointer on the right end of the bar. When the pointer becomes adouble arrow, hold down the left mouse button while moving the end of the bar.

Figure 56. Rescheduling the Start time of a Job Stream Instance


12.M

anag

ing

Job

Stream

s

As you move your mouse, a tooltip tells you the corresponding deadline time at everynew position of the right end of the bar.

2. When you find the position you want, release the mouse button. The Properties - JobStream 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 newposition.

Deleting a Job Stream InstanceTo delete a job stream instance:

1. In a list, right-click the name of an instance or group of instances and select Delete fromthe pop-up menu. A confirmation window is displayed.

2. Click OK in the confirmation window. The instance or instances are deleted andremoved from the plan.

Setting a Job Stream Instance to CompleteTo force the completion of a job stream instance:

1. In a list, right-click the job stream instance and select Set to Complete from the pop-upmenu.

2. Click OK in the confirmation window. The status of the job stream instance is changedto Complete. The status of all the job instances that are part of the job stream is also setto Complete.

Setting a Job Stream Instance to Waiting

Note: Use this option only if no external jobs have started.

To set a job stream instance to Waiting status to force it to restart:

1. In a list, right-click the job stream instance and select Set to Waiting from the pop-upmenu. A confirmation window is displayed.

Figure 57. Rescheduling the Deadline Time

134 Version 8.1

2. Click OK in the confirmation window. The status of the job stream instance is changedto Waiting. The status of all the job instances that are part of the job stream is also set toWaiting.

Rerunning a Job Stream InstanceYou can change the status of a job and rerun a job stream instance. When you rerun theinstance, you can specify with which job is to start first.

Note: To be able to rerun a job stream instance, restart cleanup must be enabled in the jobproperties. This can only be done on the host.

To rerun a job stream instance:

1. In a list, right-click the job stream instance and select Rerun from the pop-up menu. TheJob Stream Instance Rerun Editor is displayed.

2. Right-click the job where you want to start the rerun and select StartFrom. The RerunImpact List window is displayed, showing information about the instance.

3. If you want to, select Use Restart and Cleanup, otherwise, continue with step 4. Thefollowing additional options become available from the drop-down list box:Step Restart Select this to specify at which point in the JCL the job should restart.Data Set List Select this to specify with which data set to restart.Edit JCL Select this to edit the JCL for the job.Execute Select this to run the restart and cleanup with specifying any specific

instructions.

4. Click OK to rerun the job.

Additional OptionsIn addition to the StartFrom option in the pop-up menu, you can also select:

StartCleanupStarts a cleanup operation.

DisplayCleanupDisplays the last data set to be cleaned up.

For further information, see “Restart and Cleanup” on page 160.


12.M

anag

ing

Job

Stream

s

136 Version 8.1

Managing Jobs

This chapter explains how to:

¶ Browse and modify a job instance

¶ Add, remove, or change the dependencies of a job instance on other jobs

¶ Delete a job instance from the plan

¶ Hold a job instance

¶ Release a held job instance

¶ Show predecessors and successors

¶ View the job log file

¶ Remove a job instance from the plan

¶ Restore a job instance to the plan

¶ Run a job instance immediately

¶ Change the status of a job instance

¶ Modify the variables and instructions associated with a job instance

¶ View operator instructions associated with a job instance

¶ Tailor job statements

¶ Restart a job instance and perform cleanup operations

To perform these actions, you use job instance lists.

13


13.M

anag

ing

Job

s

Job Instance ListsJob instance lists are displayed in two ways, the List View and the Timeline View.

List ViewThe List View shows details about each instance.

Timeline ViewThe Timeline View displays graphic information about time restrictions.

In the Timeline View, job instances that share the same job stream instance and runtime arelisted in groups. A group contains two or more job instances that have the same runtime butdifferent identifiers. Groups are indicated by a small arrow on their left side. Click the arrowand the individual instances are displayed.

Figure 58. Job Instances List View

Figure 59. Job Instances Groups in the Timeline View

138 Version 8.1

As shown in Figure 59 on page 138, you can perform the following actions on a group ofjob instances:

¶ Delete all the job instances

¶ Put all the job instances on hold

¶ Release all the held job instances

To perform the actions available to individual job instances and to display activity bars onthe job instances arranged in a group, you must first expand the group by clicking on thearrow.

Browsing and Modifying Job InstancesList the job instance that you want to work on then right-click it and select Properties fromthe pop-up menu.

This section describes the following pages of the the properties window:

¶ General

¶ Task

¶ Time Restrictions

¶ Details

¶ Options

¶ Resources

When you have completed your changes:¶ Click Apply to save the changes and keep the window open.¶ Click OK to save any changes you made and close the window.¶ Click Cancel to disregard the changes and close the window.


13.M

anag

ing

Job

s

General PageThe General page contains general information about the job instance. This information ismainly read-only.

Table 49 describes the contents of the window.

Table 49. Properties - JCL Job Instance General InformationThis area ... Contains this information ...

Occurrence Token Identifies where the instance is in the plan.

Identifier The job identifier.

Workstation The name of the workstation running the job.

Priority The priority level of the job stream to which the job belongs.

Started The actual date the instance started.

Runtime The time it took the instance to run if completed.

Belongs to job stream The name of the job stream to which the job belongs.

Description A description of the job. This field is editable.

Authority group The name of the authority group of the job stream.

Internal status The status of the job instance.

Status details Additional information about the status of the job instance.

Error code The code with which the instance ended in error, when applicable.

Start Time The earliest, latest, planned, and actual start times of the jobinstance.

Figure 60. Properties - JCL Job Instance Instance General Page

140 Version 8.1

Task PageThe Task page contains editable information about any task or JCL that the job instance maybe associated with:


Table 50. Properties - JCL Job Instance Task InformationThis area ... Contains this information ...

Task name The name of the task associated with the job instance.

Form number The printer form number if the job is a printer job.

Job class The job class letter.

Figure 61. Properties - JCL Job Instance Task Page


13.M

anag

ing

Job

s

Time Restrictions PageThe Time Restrictions page contains the start time, deadline, and duration that you specifiedwhen you defined the job in the database. You can change them here if the job has notstarted yet. However, Workload Scheduler for z/OS calculates the planned start time anddeadline.

Figure 62. Properties - JCL Job Instance Time Restrictions Page

142 Version 8.1

Details PageThe Details page displays additional information about the job instance.


Table 51. Properties - JCL Job Instance Details InformationThis area ... Contains this information ...

JES job number The job number assigned by JES.

Planned duration The planned duration time.

Intermediate start If there is an intermediate start.

Actual end The time of actual end, if the instance completed.

Transport time The transport time.

Dependencies This group box displays:¶ The number of jobs whose completion is necessary for this

instance to run. See the Predecessors page of the Job InstanceDependencies window for a list.

¶ The number of predecessors that have completed.¶ The number of jobs that depend on the completion of this

instance. See the Successors page of the Job InstanceDependencies window for a list.

¶ The number of logical resources reserved for the job.

CleanUp Status The status code of the data set cleanup action. This can be one of:¶ Completed¶ Error ended

If no status is displayed, either data set cleanup has been reset orit has not yet started.

Latest out passed The latest end time passed.

On critical path Whether the job instance is on the critical path.

Urgent The urgency indicator.

JCL preparation Whether JCL preparation is required.

Figure 63. Properties - JCL Job Instance Details Page


13.M

anag

ing

Job

s

Table 51. Properties - JCL Job Instance Details Information (continued)This area ... Contains this information ...

Deadline WTO Whether a write-to-operator message should be sent when the jobmisses its deadline.

WLM policy The policy applied for WLM service class promotion if this job islate. To use this option, you must also select the Critical jobcheck box. Available for OPC 2.3 or later. The policy can be:Conditional

The scheduler uses an algorithm to determine whether toapply the Deadline or the Latest start option.

DeadlineThe scheduler intervenes if the job runs beyond the deadline.

Latest startThe scheduler intervenes immediately if the job starts afterthe latest start time.

Long durationThe scheduler intervenes if the job takes longer than itshould as compared to the statistics that it keeps.

Critical job Whether or not the job has been defined as a critical job. If acritical job runs late, it is eligible for Workload Manager (WLM)service class promotion. Available for OPC 2.3 or later.

144 Version 8.1

Options PageThe Options page contains job instance properties that you can change.


Table 52. Properties - Write-to-Operator Job Instance Options InformationThis area ... Contains this information ...

Auto release Whether the instance should be automatically released. Click thecheck box to set this feature on or off.

Auto error completion Whether the instance should be automatically completed in theevent it ends in error. Select the check box to set this feature onor off.

Cancel if late Whether the instance should be cancelled automatically if late onschedule. Select the check box to set this feature on or off.

Auto submit Whether the instance should be submitted automatically. Click thecheck box to set this feature on or off.

Restartable Whether the instance should be made restartable. You can changeto Yes, No, or Default to keep the original job definition.

Reroutable Whether the instance should be made reroutable. You can changeto Yes, No, or Default to keep the original job definition.

Restart CleanUp Whether Restart CleanUp is used if the job instance ends in error.This field is read-only.

Highest acceptable return code The highest acceptable return code for the instance. You canupdate this field.

User data Editable user data.

Figure 64. Properties - JCL Job Instance Options Page


13.M

anag

ing

Job

s

Resources PageThe Resources page, shown in the next figure, contains information about the target andlogical resources used by the job instance.

Click the pull-down arrow and select the type of resources you want to see.

Target ResourcesThe Target resources list, shown in the next figure, displays the quantities of workstationresources 1 and 2, and of the parallel server. You can modify quantities by double-clickingthe field and entering a new value.

Figure 65. Properties - JCL Job Instance Resources Page

Figure 66. Target Resources for a Job Instance

146 Version 8.1

Logical ResourcesThe Logical resources list, shown in the next figure, displays information about any definedresource. Double-click any cell to enter new values or to choose values from the drop-downlists.


Table 53. Logical Resources InformationThis area ... Contains this information ...

Resource The resource name.

Quantity The resource quantity.

Access type The access type. Available options are Shared or Exclusive.

Keep on error Whether to keep the resource allocated, if it goes on error. Availableoptions are Yes, No, and Default to use the choice specified in theoriginal job definition.

To add or remove resources in the list, click the Add Row or Remove Row buttons. Whenadding a resource, click the ellipsis (...) under the Resource field to locate resources withtheFind tool. When removing a resource, select the resource before clicking on RemoveRow.

Note: You can only add or remove logical resources, not target resources.

Figure 67. Logical Resources for a Job Instance


13.M

anag

ing

Job

s

Browsing and Modifying Job DependenciesThis section describes how to browse and modify the job dependencies of a job instance.

List the job instance that you want to work on, then right-click it and select Dependenciesfrom the pop-up menu. The Dependencies - JCL Job Instance Predecessors window isdisplayed.

Predecessors WindowThe Predecessors window displays information about the job instances that must completebefore this instance can start running:


Table 54. Dependencies Predecessors InformationThis area ... Contains this information ...

Job Stream Name The name of the job stream to which the predecessor belongs, if itis external.

Identifier The identifier of the predecessor job.

Job Stream Start The start time of the job stream to which the predecessor belongs,if it is external.

Task Name The name of the task associated with the predecessor job.

Status The current status of the predecessor.

Note: If you cannot read the headings completely, widen the column heading cells withyour mouse.

Figure 68. Dependencies - JCL Job Instance Predecessors Window

148 Version 8.1

You can modify the information of this page in the following way:

Table 55. Dependencies Predecessors TasksTo do this ... Perform this task ...

Change listed predecessors Double-click each field to replace the information.

Add a predecessor Click the Add Row button in the top right of the window, thencomplete the fields of the new row.

If you need help to find an external predecessor job, or informationabout it, select the ellipsis that displays when you double-click theJob Stream Name, Identifier, or Job Stream Start fields. Thisopens a Find Job Instance window where you can start a filteredsearch of the job you are seeking. The search produces informationin terms of job stream name, job identifier, and job stream startdate. To insert these data in the row you are working on, just clickApply in the Find Job Instance window.

Delete a predecessor Select the predecessor, then click on the Delete Row button in thetop right of the window.

Select Successors in the left pane. The Successors page is displayed.


13.M

anag

ing

Job

s

Successors WindowThe Successors page displays information about other job instances that depend on thecompletion of this instance to start running.


Table 56. Dependencies Successors InformationThis area ... Contains this information ...

Job Stream Name The name of the job stream to which the successor belongs, if itis external.

Identifier The identifier of the successor job.

On critical path Whether the successor job is on the critical path

Job Stream Start The start time of the job stream to which the successor belongs, ifit is external.

Task Name The name of the task associated with the successor job.

Status The current status of the successor.

Note: If you cannot read the headings completely, widen the column heading cells withyour mouse.

Figure 69. Dependencies - JCL Job Instance Successors Page

150 Version 8.1

You can modify the information of this page in the following way:

Table 57. Dependencies Predecessors TasksTo do this ... Perform this task ...

Change listed successors Double-click each field to replace the information.

Add a successor Click the Add Row button, then complete the fields of the newrow.

If you need help to find an external successor job, or informationabout it, select the ellipsis (...) that displays when youdouble-click the Job Stream Name, Identifier, or Job StreamStart fields. This opens a Find Job Instance window where youcan start a filtered search of the job you are seeking. The searchproduces information in terms of job stream name, job identifier,and job stream start date. To insert this data in the row you areworking on, just click Apply in the Find Job Instance window.

Delete a successor Select the successor, then click the Delete Row button.

When you have finished:¶ Click Apply to save the changes and keep the window open.¶ Click OK to save any changes you made and close the window.¶ Click Cancel to disregard the changes and close thge window.


13.M

anag

ing

Job

s

Changing Time Restrictions in the Timeline ViewThe left-hand pane of the Timeline View displays the following job instance details:

Table 58. Timeline View Job Instance DetailsThis column ... Specifies ...

Name The job name

Status The current status

Started The actual start time

Runtime The actual duration

Start at The planned start time

Duration The planned duration

Deadline The planned deadline

The right-hand pane, see Figure 71, has activity bars that show the runtime of a job instancein terms of start, duration, and deadline times.

Figure 70. Timeline View of Job Instances - Left Pane

Figure 71. Timeline View of Job Instances - Right Pane

152 Version 8.1

The deadline is indicated by a black stripe at the end of the blue activity bar. The activitybar represents the time difference between the earliest planned start and the planned end thatwere specified as time restrictions for the job. A pale blue bar represents the duration of thejob. It turns red if the duration exceeds the deadline and it becomes diamond shaped if theduration is zero. A black line represents the actual runtime of the job instance.

By moving components of the activity bars, you can change the time restrictions of eachinstance and view the results of your changes, as you would by following the stepsdescribed in “Browsing and Modifying Job Instances” on page 139 and going directly to theTime Restrictions page of the job instance properties window.

You can change the time restrictions of an instance by:

¶ Rescheduling the instance

¶ Rescheduling the start time

¶ Rescheduling the deadline time

Rescheduling the InstanceTo reschedule the instance in ready status:

1. Move the activity bar by positioning the mouse pointer inside the bar. When the pointerbecomes cross-shaped, hold down the left mouse button while moving the bar in eitherdirection.

As you move the bar, a tooltip tells you the new deadline time at every position of theright end of the bar.

2. When you find the position you want, release the mouse button. The Properties - JobInstance 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 seton the new position.

Figure 72. Rescheduling a Job Instance


13.M

anag

ing

Job

s

Rescheduling the Start TimeTo reschedule the start time:

1. Position the mouse pointer on the left end of the bar. When the pointer becomes adouble-headed 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 start time for every newposition of the left end of the bar.

2. When you find the position you want, release the mouse button. The Properties - JobInstance 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 newposition.

Rescheduling the Deadline TimeTo reschedule the deadline time:

1. Position the mouse pointer on the right end of the bar. When the pointer becomes adouble arrow, hold down the left mouse button while moving the end of the bar.

Figure 73. Rescheduling the Start Time

Figure 74. Rescheduling the Deadline Time

154 Version 8.1

As you move your mouse, a tooltip tells you the corresponding deadline time for everynew position of the right end of the bar.

2. When you find the position you want, release the mouse button. The Properties - JobInstance Time Restrictions page is displayed, showing the new deadline time.

3. Click OK in the to save the new settings. The right end of the activity bar is set in thenew position.

Deleting Job InstancesTo delete a job instance:

1. Right-click the name of a job instance or group of job instances and select either Deleteor Delete all from the pop-up menu. A confirmation window is displayed.

2. Click OK in the confirmation window to delete the instance or group of instances. Theinstance or instances are deleted and removed from the plan.

Putting Job Instances on HoldTo put a job instance on hold:

1. Right-click the name of a job instance or group of job instances and select either Holdor Hold all from the pop-up menu. A confirmation window is displayed.

2. Click OK in the confirmation window. The instance or instances are placed on hold inthe plan until they are released again.

Releasing Job InstancesTo release a job instance:

1. Right-click the name of a job instance or group of job instances and select eitherRelease or Release All from the pop-up menu. A confirmation window is displayed.

2. Click OK in the confirmation window. The instance or instances are released into theplan.


13.M

anag

ing

Job

s

Showing Predecessors and SuccessorsTo show the predecessors of a job instance or its successors, right-click a job instance andselect Impact View from the pop-up menu, then either Predecessors or Successors. TheImpact View window is displayed.

You can change the way the view is displayed by using the following buttons in the toolbar.

Table 59. Impact View OptionsSelect this button ... To display this type of view ...

Radial

Left

Right

Up

Down

Displaying DependenciesTo display a dependency of a job instance, right-click the job instance and selectDependencies 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 morethan 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 thefirst level of dependent job instances is displayed.

Figure 75. Impact View Window

156 Version 8.1

Set as RootAt any time, you can reset the display using one particular job instance as the starting, orroot, job instance. To do this, right-click the job instance you want to use as as the root jobinstance and select Set As Root from the pop-up menu. The display is refreshed, showingthe selected job instance as the root instance.

To reset the display in a separate window, right-click the job instance you want to use as asthe root job instance and select Set As Root In New Frame from the pop-up menu.

Browsing the Job LogTo browse the job instance log, right-click a job instance and select Browse Job Log fromthe pop-up menu. The Job Instance Output window is displayed.

When you have finished, click Cancel to close the window.

Removing a Job Instance from the PlanYou can use the NOP option to remove a job instance that is already in the plan and isready or waiting to run. Use this option on job instances whose internal status is one of thefollowing:

¶ Arriving

¶ Ready

¶ Ready-non reporting workstation

¶ Waiting

¶ Completed (only for workstations with automatic reporting)

To use the NOP option, right-click the name of a job instance and select NOP from thepop-up menu.


13.M

anag

ing

Job

s

Restoring a Job Instance to the PlanYou can use the UN-NOP option to restore to the plan a job instance previously removedwith the NOP option.

To do this, right-click the name of a job instance and select UN-NOP from the pop-upmenu. The job instance is restored to the plan.

Running a Job Instance ImmediatelyYou can use the Execute option to immediately run a job instance that is ready to runregardless of normal scheduling rules excluding dependencies. In order to run, the resourcesthe job instance depends on must be available. Otherwise, the option is rejected.

To force the running of a job instance, right-click the name of a job instance and selectExecute from the pop-up menu. If all conditions are met, the job instance is runimmediately.

Changing the Status of a Job InstanceYou can set the status of a job instance manually. To do this:

1. Right-click the name of a job instance and select Set Status from the pop-up menu. AChange Status dialog is displayed.

2. Select the button for the status you want to use.

Note: If you are changing to an Error status, a field becomes available for entering anycode you want to show in the properties window.

Figure 76. Change Status Dialog

158 Version 8.1

Editing JCLYou can modify the variables and instructions associated with a job instance beforesubmitting a job by editing the JCL associated with the instance.

To edit the JCL:

1. In a list, right-click a job instance and select Edit JCL from the pop-up menu. The EditJCL window is displayed.

2. Make the changes you want.

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.


¶ Click OK to save the changes and close the window.

¶ Click Cancel to close the window without saving any changes.

Figure 77. Edit JCL Window


13.M

anag

ing

Job

s

Viewing Operator InstructionsYou can view any operator instructions associated with a job instance. To do this:

1. Right-click the name of a job instance and select Browse Operator Instruction from thepop-up menu. The Browse Operator Instruction window is displayed.

2. When you have finished, click OK.

Note: The Browse Operator Instruction option is only available if an operator instructionhas been defined for the job instance.

Modifying Job SetupThe Job Setup option allows you to tailor a job before it is submitted. To do this, right-clicka Job Setup job instance and select Job Setup from the pop-up menu. If there arepromptable variables that have not yet been set, the Job Setup window is displayed whereyou can change the values of the promptable variables.

Note: You can only change the variable value. A default value is displayed, if it has beenset beforehand.

When you have made your changes, click OK. A second Job Setup window is displayed foreach successor job instance. Each window shows the JCL for the instance, reflecting thechange 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.

Restart and Cleanup

Note: Before using this function, you should refer to the Restart and Cleanup description inTivoli Workload Scheduler for z/OS Planning and Scheduling.

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. TheRestart 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.

160 Version 8.1

Managing Workstations in the Plan

This chapter describes how to monitor and update workstations in the plan. You can:

¶ Monitor the status of a workstation in the plan and of the job instances scheduled to runon 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.

14


14.M

anag

ing

Wo

rkstation

sin

the

Plan

Creating a List of WorkstationsA plan workstation list produces a filtered list of workstations allocated to the plan.

To create a list of workstations in the plan, in the Job Scheduling view, select an engine andclick the List Workstations in Plan button. The Properties - Plan Workstation List windowis displayed.

Figure 78. The Properties - Plan Workstation List Window

162 Version 8.1

Use the information in Table 60 to enter all the information needed to create the planworkstation list.

Table 60. Properties - Plan Workstation List InformationIn this area ... Do this ...

Name Enter a name for the list.

Periodic Refresh Options ¶ Select Periodic Refresh to specify an automatic refreshinterval in seconds.

—OR—¶ Click Apply Defaults to use the default specified in the

Scheduler Properties window available from the JobScheduling view.

Filter Criteria In the group, specify any of the following search parameters orcombinations of two or more parameters. To generalize yoursearch, use wildcard characters, such as an asterisk (*) to representstrings of characters, or a question mark (?) to represent a singlecharacter. If you leave all fields blank, all the workstations definedin 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 reportingattributes you select with the following check boxes:¶ Automatic¶ Completion only¶ Manual start at completion¶ Non reporting

TypesLists all the workstations of the type you select with thefollowing check boxes:¶ General¶ Computer¶ Printer

Is Fault TolerantLists fault-tolerant workstations. These workstations areused to run the Workload Scheduler jobs in the WorkloadScheduler for z/OS plan. Select:Yes To list fault-tolerant workstationsNo To list workstations that are not fault-tolerantIgnore criteria

To list workstations regardless of whether they arefault-tolerant or not


14.M

anag

ing

Wo

rkstation

sin

the

Plan

Displaying WorkstationsTo display a list of workstations in the plan:

1. Double-click an engine.

2. In the tree that is displayed, right-click Status of all Workstations and select Load Listfrom the pop-up menu. A list of workstations in the plan is displayed in the right pane ofthe Job Scheduling view.

Plan workstation lists are displayed in windows composed of two horizontal panes. Inaddition to the workstation list, there is a lower pane that contains details about the jobsscheduled on the workstations. To see the lower pane, drag the horizontal dividing barlocated at the bottom of the window.

For more information, see “Displaying by Status the Job Instances Scheduled on aWorkstation” on page 171.

Browsing and Modifying Workstation PropertiesFrom a workstation list you can view workstation details. You can also:

¶ Modify some of the attributes of the workstation

¶ Specify what action to take on either jobs running or scheduled to run on theworkstation if it becomes unavailable

¶ Change the quantities of workstation resources available for defined time slots andupdate time slot definitions

¶ Check the statistics of jobs scheduled on the workstation

¶ Specify the name of a new alternate workstation

The changes you make from a workstation status list update the current workstation planinformation. 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. TheProperties - Workstation in Plan General page is displayed. Several fields are read-only.

Figure 79. Plan Workstation List Display

164 Version 8.1

General Page


Table 61. Properties - Workstation in Plan General InformationThis field ... Specifies this information ...

Name Workstation name. Read-only.

Description Workstation description. Read-only.

Workstation type Workstation type. For example, computer. Read-only.

Reporting attribute The reporting attribute. Editable. This is one of:¶ Manual start and completion¶ Automatic¶ Completion only¶ Non reporting

Control on servers Changes the control on servers selection status. If you selectControl on servers, the system will not start more job instancesat the workstation than there are available servers.

Job setup Whether the workstation is used for job setup. Read-only.

Started task, STC Whether the workstation is used for started task support.Read-only.

WTO Whether the workstation is used for WTO purposes. Read-only.

Reroute jobs Whether the workstation will reroute job instances to an alternateworkstation, before failing or going offline. Read-only.

Alternate workstation Whether an alternate workstation was defined. Read-only.

Status The current status of the workstation. Read-only.

Fault Tolerant Whether the workstation is fault-tolerant. Read-only.

Linked Whether the workstation is linked to the master. Read-only.

Select Resource in the left pane. The Properties - Workstation in Plan Resource page isdisplayed

Figure 80. Properties - Workstation in Plan General Page


14.M

anag

ing

Wo

rkstation

sin

the

Plan

Resources Page

This page displays details about the two workstation resources. For each of the tworesources 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 anunexpected event happens while job instances are running, the system considers the resourcewhen it reschedules them.

Job Summary PageSelect Job Summary in the left pane. The Job Summary page is displayed.

This page displays the number, estimated duration, and actual duration (where applicable) ofall the job instances scheduled to run on the workstation. The information is provided forinstances in the following status:

Figure 81. Properties - Workstation in Plan Resource Page

Figure 82. Properties - Workstation in Plan Job Summary Page

166 Version 8.1

¶ Completed

¶ Interrupted

¶ Started

¶ Ready

¶ Waiting

Select Open Time Intervals in the left pane. The Open Time Intervals page is displayed.

Open Time Intervals Page

This page shows a list of time slots when the workstation is available to run jobs withresource quantities different from the default. The list shows the boundaries of each time slotand, for every slot, the planned quantities of workstation resources and of parallel serversavailable, together with the name of the alternate workstation.

You cannot edit the resource quantities and the alternate workstation names in the Plannedfields. They correspond to the workstation Open Time Intervals definitions in the systemdatabase and can only be modified there (from a list of workstations in the database, forexample). You can change the time boundaries and the values in the Modified fields. Thesevalues override the Planned values for the duration of the plan.

Figure 83. Properties - Workstation in Plan Open Time Intervals Page


14.M

anag

ing

Wo

rkstation

sin

the

Plan

You can also add and delete time slots. To alter a value in a time slot, select the rowdescribing the time slot and double-click the field you want to change.

1. To change the starting day, double-click a date in the Start Date column.

2. Click the pop-up calendar button and select the new day in the calendar. The new dayis automatically entered in the field.

3. To change the initial time, double-click in the Start Time column and enter the newtime.

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 dayis 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 theModified PS column.

9. Enter a new quantity.

Figure 84. Changing the Start Date

Figure 85. Changing the Start Time

168 Version 8.1

10. To adjust the available quantity of resource R1, double-click the field in the ModifiedR1 column.


12. To adjust the available quantity of resource R2, double-click the field in the ModifiedR2 column.


14. To change or add the name of the alternate workstation, double-click the field in theModified Alternate column.

15. Enter a name for the workstation. To open a Find Workstations window, click theellipsis (...).

16. To add a new time interval, click the Add Row button and enter details as explained inthe previous steps.

17. To delete a time interval, select the row and click the Remove Row button.


Figure 86. Changing the Quantity of Resource 1


14.M

anag

ing

Wo

rkstation

sin

the

Plan

Linking Fault-Tolerant WorkstationsIf a workstation is fault-tolerant, you can link the workstation to the master workstation. Todo this, right-click on a workstation in the list and select Link from the pop-up menu.

Changing Workstation Status and Rerouting Scheduled JobInstances

You can manually change the status of a workstation and reroute scheduled job instances toan alternate workstation. This overrides, for the duration of the current plan, thecorresponding values defined in the database.

To do this:

1. Right-click a workstation in the list and select Set Status from the pop-up menu. TheChange Status - Workstation window is displayed.

2. Select one of the following:¶ Active When the workstation is functioning and available.¶ Offline When communication fails between Workload Scheduler for z/OS and the

workstation.¶ Failed When system failure makes the workstation unavailable.

Notes:

a. The options in the adjacent group box only become available if you change the statusto Offline or Failed.

b. If the workstation is fault-tolerant, only the Active and Offline options are available.

3. To specify how to handle the job instances scheduled on the workstation, if they havealready started when the status is changed, click the arrow in the drop-down list. Thechoices are:¶ Restart¶ Leave¶ Set to error

4. To reroute scheduled job instances to an alternate workstation other than the one definedin the database, select Reroute jobs.

5. Enter a valid name in the Alternate workstation field.


¶ Click OK to save your changes and close the window.

¶ ClickCancel to close the window without saving any changes.

Figure 87. Change Status - Workstation Window

170 Version 8.1

Displaying by Status the Job Instances Scheduled on a WorkstationUse a workstation status list to browse the status of the job instances scheduled on aworkstation and also to take action on a job instance of which you know the status.

To display the job instances, right-click a workstation from the list and select List Jobs, thenComplete (for example) from the pop-up menu.

All the job instances scheduled to run on the workstation and currently in Complete statusare displayed in the bottom pane of the window.

Table 62 shows the list of options that you can select from the pop-up menu.

Table 62. Workstation List Jobs OptionsSelect 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 anonreporting workstation, but are ready to run on the selectedworkstation

Ready - Non ReportingWorkstation

Have a predecessor on a non-reporting workstation, but are readyto run on the selected workstation

Started Are running on the workstation

Undecided Have an unknown status

Figure 88. List of Jobs Scheduled on the Workstation and in Complete Status


14.M

anag

ing

Wo

rkstation

sin

the

Plan

Modifying the Job Instances Scheduled on a WorkstationWorkstation status lists are useful, because they allow you to perform the same actions onjob instances as the Timeline or List Views of a job instance list.

1. Run a list of jobs scheduled on a workstation.

2. Right-click a selected job and select one of the following options from the pop-up menu:

Table 63. Modifying Job Instance OptionsSelect 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

Browse Job Log View the job log file

Impact View Show the predecessors and successors of 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

Edit JCL Modify the variables and instructions associated with a jobinstance

Browse OperatorInstruction

View operator instructions associated with a job instance

Job Setup Tailor job statements

Restart and Cleanup Restart a job instance and perform cleanup operations

For an explanation about how to use these options, see “Managing Jobs” on page 137.

172 Version 8.1

Managing Resources in the Plan

This chapter describes how to monitor and update resources allocated to the plan. You can:

¶ Browse and modify the status of a resource

¶ Modify the names of the workstations connected with a resource

¶ Modify the availability of a resource

To perform these tasks, you use a filtered list of resources in the plan.

15


15.M

anag

ing

Reso

urces

inth

eP

lan

Creating a List of ResourcesA plan resource list produces a filtered list of resources allocated to the plan.

To make a plan resource list object, select an engine in the Job Scheduling view and clickthe List Resources in Plan button.

The Properties - Plan Resource List window is displayed.

Figure 89. The Properties - Plan Resource List Window

174 Version 8.1

Use the information in Table 64 to enter all the information needed to define the availabilityinterval.

Table 64. Plan Resource List InformationIn this area ... Do this ...

Name Enter a name to identify the query.

Periodic Refresh Options Select the Periodic Refresh check box and specify a refreshinterval in seconds, if you want the list results refreshedautomatically. Alternatively, click Apply Defaults to use the defaultspecified in the Scheduler Properties window available in the JobScheduling view.

Filter Criteria Specify search parameters or combinations of parameters.

To generalize your search, use wildcard characters, such as anasterisk (*) to represent strings of characters, or a question mark (?)to represent a single character. If you leave all fields blank, then allthe resources defined in the Resource Description database aredisplayed when you open the list.

Specify a parameter or a combination of parameters:¶ In Resource specify a resource name.¶ Specify in Treat input as how you want the input you entered

in the Resource field to be treated. Select one of the followingoptions:Wildcard

Treat special characters as wildcards and charactersubstitutes.

Exact matchTreat special characters as part of the resource name.

PrefixTreat the string as a name prefix.

SuffixTreat 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 thisis to be ignored.

¶ In Waiting, specify whether or not there are job instanceswaiting to allocate the resources, or whether this is to beignored.

¶ In Available, specify whether or not the resources areavailable, or whether this is to be ignored.



¶ Click OK to add the new list to the engine tree.

To display the list, right-click it and select Load List.


15.M

anag

ing

Reso

urces

inth

eP

lan

Displaying ResourcesTo display a list of resources in the plan, first double-click an engine. In the resulting tree,right-click a plan resource list object and select Load List from the pop-up menu.

A list of resources allocated to the plan is displayed in the right pane of the Job Schedulingview. The entries displayed are read-only. To modify details of resources already allocated tothe plan, you must use the Properties - Resource in Plan window as explained in “GeneralPage” on page 177.

Plan resource lists are displayed in windows composed of two horizontal panes. In additionto the resource list, there is a lower pane that contains details about the jobs associated withthe resources. To view the lower pane, drag the horizontal dividing bar located at the bottomof the window, as shown in the next figure.

See“Displaying the Job Instances Associated with a Resource” on page 181 for details.

Browsing and Modifying ResourcesFrom a plan resource list you can view details of a resource in the plan. You can also:

¶ Change some of the resource’s attributes

¶ Change a resource’s status

¶ Specify which workstations can use the resource

¶ Specify time intervals during which the resource allocation is different from specifieddefaults

The changes you make from a plan resource list update the current resource planinformation, which is stored in the plan.

Right-click a resource from the list and select Properties from the pop-up menu.The page ofthe Properties - Resource in Plan Resource page is displayed.

Figure 90. A Plan Resource List Display

176 Version 8.1

General Page

Table 65 describes the contents of this window. Some of the information displayed isread-only. Other information you can edit.

Table 65. Properties - Resource in Plan Resource InformationThis area ... Contains this information ...

Name Name of the resource. Read-only.

Description Description of the resource. Read-only.

Default Is AvailableChanges the availability status of the resource.

QuantityAdjusts the default resource quantity that must be available whilethe plan is running by entering a new quantity in the Quantityfield.

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 arePlanningControlPlanning And ControlNeither Planning Nor Control

On Error What to do with the resource if a job instance that allocates theresource ends in error (and does not have an overriding keep-on-errorspecification in the job definition). Select one of:

FreeKeepFree if ExclusiveFree if SharedAssume System Default

Figure 91. Properties - Resource in Plan Resource Page


15.M

anag

ing

Reso

urces

inth

eP

lan

Table 65. Properties - Resource in Plan Resource Information (continued)This area ... Contains this information ...

Deviation Specifies the deviation in the resource quantity that must be availablewhile the plan is running. To change the deviation, enter a value here.The deviation is an additional quantity with respect to the defaultquantity. A value of 0 means that no change in quantity was made forthe plan.Note: If you change the deviation, then verify in the Quantity fieldthe new total quantity available as the sum of the default anddeviation quantities. If you did not specify any changes, the Deviationfield displays 0, meaning that no change in quantity was made for theplan.

Is available Specifies the type of resource availability. To change it, select one ofYes, No, or Ignore.

Note: While the updates you make to most of these details are replaced by the databasevalues at the end of the plan, the updates in Quantity and Deviation are retained alsothrough plan extensions, unless they are changed manually.

Click Default Workstations in the left pane. The Properties - Resource in Plan DefaultWorkstations page is displayed.

178 Version 8.1

Default Workstations Page

This page displays the workstations that can use the resource. Table 66 shows how to add orremove workstations in this list by using the buttons in the upper-right side of the page.

Table 66. Properties - Resource in Plan Default Workstations InformationTo 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 workstationsare connected to the resource

Add specific workstations click the Find Workstations button. A Find dialog isdisplayed.

Enter search parameters, or leave the field blank to make ageneral search, then click Start. The found workstations aredisplayed in a list. Double-click them to copy their name tothe Default Workstations page

Click Availability Intervals in the left pane. The Properties - Resource in Plan AvailabilityIntervals page is displayed.

Figure 92. Properties - Resource in Plan Default Workstations Page


15.M

anag

ing

Reso

urces

inth

eP

lan

Availability Intervals Page

This page shows a list of time intervals when the resource is available with propertiesdifferent from the defaults. You can use this list to change the resource availability values inthe defined intervals, or to add or remove availability intervals. Blank fields in anavailability interval mean that the default values, as specified in the database or in the otherpages 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 theupper-right side of the page.

Table 67. Properties - Resource in Plan Availability Intervals InformationTo perform this task ... Do this ...

Change the day in which the intervaloccurs

Double-click the Date field and select the pop-up calendarbutton. In the pop-up calendar, choose a date and click it toenter 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 ismade available or unavailable for theworkstations defined in theavailability interval

Double-click the Quantity field and enter a number.

Change the availability status of thequantity defined in the previous field

Double-click the Is available field and select one of:AvailableNot availableDefault

Default uses the value specified in the database.

Figure 93. Properties - Resource in Plan Availability Intervals Page

180 Version 8.1

Table 67. Properties - Resource in Plan Availability Intervals Information (continued)To perform this task ... Do this ...

Browse the workstations for whichthe availability specified in theprevious fields is applicable

Click the ellipsis in the Workstations field to display a dialogwith a list of workstations already defined for the timeinterval.

The dialog also contains the Find Workstations, Add allWorkstations, and Remove Row buttons featured in theDefault Workstations page that enable you to update the list

Add a new availability interval click the Add Row button and enter details as explained inthe preceding steps.

Delete an availability interval Select the row and click the Remove Row button.


Displaying the Job Instances Associated with a ResourceUse a plan resource list to browse the status of the job instances associated with a resourceand also to take action on a job instance of which you know the status.

To display the job instances, right-click a resource from the list display and select List Jobsfrom 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 displayedin the bottom pane of the window.

Modifying Job Instances Associated with a ResourcePlan resource lists are useful, because they allow you to perform the same actions on jobinstances as the Timeline or List views of a job instance list.

Obtain a list of jobs associated with a resource, then right-click a selected job and select oneof the follwing options:

Table 68. Modifying Job Instance OptionsSelect 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.


15.M

anag

ing

Reso

urces

inth

eP

lan

182 Version 8.1

III — Using the Job SchedulingConsole with Tivoli WorkloadSchedulerChapter 16. Managing Database Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Creating a Group for Database Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Creating Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Creating a List of Job Streams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Creating a List of Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Creating a List of Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Creating a List of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Creating a List of Workstation Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Creating a List of Prompts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Creating a List of Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Creating a List of NT Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Creating a List of Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Creating a List of Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Working with Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Displaying a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Detaching a List Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Modifying a Database List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Deleting a List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Finding Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Chapter 17. Managing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Creating a Job Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

UNIX Script, NT Script, or Workstation Class Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206UNIX Command, NT Command, or Workstation Class Command . . . . . . . . . . . . . . . . . . . . . . . . . 207MPE Job File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207MPE User Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Extended Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207SAP Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Displaying a List of Job Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Displaying a Job Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Displaying Job Definition Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Modifying a Job Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211Deleting Job Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Chapter 18. Managing Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Using the Job Stream Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Graph View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Timeline View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Run Cycle View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Creating a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217Specifying Job Stream Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218


Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223Prompts Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Adding External Dependencies for a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225Adding an External Job Stream Dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Adding an Internetwork Dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Adding an External Job Dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Deleting External Dependencies from a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Adding a Job to a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Specifying Job Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Copying and Pasting Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Cloning the Job Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Adding an Internetwork Dependency to a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Adding an External Job Stream to a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234Adding an External Job to a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Creating Dependencies Between Jobs in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Specifying Run Cycles for a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Inclusionary or Exclusionary Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Rule for Freedays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Colored Bars on Dates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Specifying Simple Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Specifying Weekly Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Specifying Calendar Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242Modifying Run Cycles for a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244Deleting Run Cycles from a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Specifying Time Restrictions in the Timeline View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244Specifying Time Restrictions for a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Using the Timeline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245Using a Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Specifying Time Restrictions for a Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245Using the Timeline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246Using a Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Saving a Job Stream in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247Closing the Job Stream Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247Displaying a List of Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247Displaying a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Modifying a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Modifying a Job in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249Deleting a Job in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249Modifying an Internetwork Dependency in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249Deleting an Internetwork Dependency in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250Modifying an External Job Stream in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250Deleting an External Job Stream in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250Modifying an External Job in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250Deleting an External Job in a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Deleting Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Chapter 19. Managing Workstations and Workstation Classes . . . . . . . . 251Managing Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Creating a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

184 Version 8.1

Displaying a List of Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255Displaying a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256Modifying a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256Deleting Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256Creating a Workstation by Copying Another Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Managing Workstation Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257Creating a Workstation Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258Workstations Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Displaying a List of Workstation Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Displaying a Workstation Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Modifying a Workstation Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260Deleting Workstation Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Chapter 20. Managing Domains, Users, and Calendars . . . . . . . . . . . . . . . . 261Managing Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Creating a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261Displaying a List of Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262Displaying a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262Modifying a Domain in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263Deleting Domains in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263Creating a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263Displaying a List of Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264Displaying a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Modifying a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Deleting Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266Changing User Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Managing Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266The Holidays Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266Freedays Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267Creating a Calendar in the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267Displaying a List of Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269Viewing Calendar Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269Modifying a Calendar in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269Deleting Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Chapter 21. Managing Resources, Prompts, and Parameters . . . . . . . . . . 271Managing Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

Creating a Resource. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271Displaying a List of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272Displaying a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272Modifying a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273Deleting Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273Creating a Resource by Copying Another Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Managing Prompts in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274Creating a Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274Displaying a List of Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275Displaying a Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275Modifying a Prompt in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275Deleting Prompts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276


Managing Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276Creating a Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276Displaying a List of Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277Displaying a Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277Modifying a Parameter in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278Deleting Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

Chapter 22. Plan Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279Using Plan Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Creating a Group for Plan Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279Creating a Plan List of Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279Creating a Plan List of Domain Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280Creating a Plan List of Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282Dependencies Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Creating a Plan List of Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287Dependencies Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

Creating a Plan List of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289Creating a Plan List of Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290Creating a Plan List of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291Modifying the Properties of a Plan List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292Deleting a Plan List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292Detaching a Plan List Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

Finding Objects in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293Managing Job Instances in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Displaying a List of Jobs in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294List View of Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294Timeline View of Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

Modifying the Properties of a Job Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302Prompts Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

Displaying Dependencies of a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307Predecessors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307Internetwork Predecessors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308Successors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Adding Predecessors to a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308Deleting Predecessors from a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309Displaying Successors of a Job Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309Holding a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Holding a Single Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309Holding All Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

Releasing a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310Releasing a Single Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310Releasing All Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

186 Version 8.1

Showing Predecessors and Successors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Displaying Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Set as Root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

Browsing the Job Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312Rerunning a Job Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313Canceling a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314Killing a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314Confirming a Job Instance SUCC or ABEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315Releasing a Job Instance from Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

Managing Job Stream Instances in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316Displaying a List of Job Streams in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

Timeline View of Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317List View of Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

Displaying and Changing the Properties of a Job Stream Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . 319General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322Prompts Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

Displaying Dependencies of a Job Stream Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327Adding Predecessors to a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328Deleting Predecessors from a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328Displaying Successors of a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328Holding a Job Stream Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329Releasing a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329Showing Predecessors and Successors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330Canceling a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330Changing the Job Limit of a Job Stream Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331Changing the Priority of a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331Releasing a Job Stream Instance from Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332Re-submitting a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333Submitting Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334Monitoring Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Submitting Jobs and Job Streams into the Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335Submitting a Job Stream into the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335Submitting a Job into the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

Using a Default Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336Using a Specific Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

Viewing or Modifying the Properties of the Job to Submit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343Prompts Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347Predecessors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

Submitting an Ad Hoc Job into the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355Prompts Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357


Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359Predecessors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

Managing Workstations in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361Displaying a List of Workstations in the Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361Displaying a Workstation Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362Changing the Job Limit of a Workstation in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363Changing the Job Fence of a Workstation in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364Starting a Workstation Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364Stopping a Workstation Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365Linking a Workstation Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365Unlinking a Workstation Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

Managing Domains in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365Displaying a List of Domains in the Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365Starting the Workstations in a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366Stopping the Workstations in a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366Linking the Workstations in a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366Unlinking the Workstations in a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366Switching the Domain Manager in a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Managing File Dependencies in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367Displaying File Dependencies Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Managing Prompt Dependencies in the Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368Displaying Prompt Dependencies Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368Replying to a Prompt Dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Managing Resource Dependencies in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369Displaying Resource Dependencies Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369Displaying the Properties of a Resource Dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370Changing the Number of Units of a Resource Dependency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

Setting an Alternate Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

188 Version 8.1

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 filteredtable of objects in the database. Each list you create is represented by an button in the treeview of the Job Scheduling Console.

You can create lists in the Workload Scheduler branch or you can create groups below thebranch to organize your lists. Tivoli supplies a basic set of lists in a group called DefaultDatabase Lists.

Creating a Group for Database ListsTo create a group for database lists:


2. Click the Create a Group of Lists button on the toolbar or right-click the schedulerengine 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 ofLists on the toolbar or right-click the existing group button and select Create Groupfrom the pop-up menu.


3. Enter a name for the group. You can use the same name for more than one group, if youwant. Different groups maintain their individual properties even if they have the samename.


¶ Click OK to close the window and save the new group. An button is created for the newgroup in the tree view of the Job Scheduling Console.

¶ Click Cancel to close the window without saving the new group.

After creating a group, you can create its member lists and subgroups. Right-click the groupto display a pop-up menu with the following options:


16


16.M

anag

ing

Datab

aseL

ists

Table 69. Properties List OptionsSelect 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, workstation, andother definitions in the database.

Create Plan List Create a new list of job streams, jobs, resources, workstations,and other objects in the plan.

Create Group Create a subgroup of more lists.

Creating ListsTo create a database list, right-click an engine and select one of the following options:

Table 70. Properties List OptionsTo create this type of list ... Go to page ...

Job Stream 190

Job 191

Workstation 192

Resource 193

Workstation Class 193

Prompt 194

Parameter 195

NT User 195

Domain 196

Calendar 197

Creating a List of Job StreamsTo create a list of job streams:


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 orgroup button and select Create Database List then Job Stream from the pop-up menu.

Figure 95. Create Database List Pop-up

190 Version 8.1

The Properties - Job Stream List window is displayed.

3. Enter a name for the list in the Name field.

4. If you want the list results refreshed automatically, select Periodic Refresh and enter arefresh interval in seconds in the Period (secs) field.

5. Click Apply defaults to enter the default refresh settings from the scheduler properties.

6. To filter the list results, enter a job stream name in the Job Stream Name field and aworkstation name in the Workstation Name field. You can also use wildcards or leavethe field blank to obtain an unfiltered list.



¶ Click OK to save the list and close the window. A new button is created for the list inthe tree view of the Job Scheduling Console.

¶ Click Cancel to close the window without running or saving the list.

Creating a List of JobsTo create a list of job streams:



2. Click the List Job Definitions button on the toolbar. Alternatively, right-click the engineor group button and select Create Database List then Job from the pop-up menu.

The Properties - Job List window is displayed.


Figure 96. Properties - Job Stream List Window

Figure 97. Properties - Job List Window


16.M

anag

ing

Datab

aseL

ists


5. Click Apply defaults to enter the default refresh settings from the scheduler properties.

6. To filter the list results, enter a job name in the Job Name field and a workstation namein the Workstation Name field. You can also use wildcards or leave the field blank toobtain an unfiltered list.





Creating a List of WorkstationsTo create a list of workstations:



2. Click the List Workstations in Database button on the toolbar. Alternatively, right-clickthe scheduler engine button or group button and select Create Database List thenWorkstations from the pop-up menu.

The Properties - Database Workstation List window is displayed.


4. To have the list results refreshed automatically, select Periodic Refresh and enter arefresh interval in seconds in the Period (secs) field.

5. Click Apply defaults to enter the default periodic refresh settings.

6. To filter the list results, enter a workstation name in the Workstation Name field. Youcan also use wildcards or leave the field blank to obtain an unfiltered list.




Figure 98. Properties - Database Workstation List window.

192 Version 8.1


Creating a List of ResourcesTo create a list of resources:



2. Click the List Resources in Database button on the toolbar. Alternatively, right-click thescheduler engine button or group button and select Create Database List then Resourcefrom the pop-up menu.

The Properties - Database Resource List window is displayed.




6. To filter the list results, enter a resource name in the Resource Name field and aworkstation name in the Workstation Name field. You can also use wildcards or leavethe field blank to obtain an unfiltered list.





Creating a List of Workstation ClassesTo create a list of workstation classes:



2. Right-click the scheduler engine button or group button and select Create Database Listthen Workstation Class from the pop-up menu.

The Properties - Workstation Class List window is displayed.

Figure 99. Properties - Database Resource List window.


16.M

anag

ing

Datab

aseL

ists




6. To filter the list results, enter a workstation class name in the Workstation Class Namefield. You can also use wildcards or leave the field blank to obtain an unfiltered list.





Creating a List of PromptsTo create a list of prompts:



2. Right-click the scheduler engine button or group button and select Create Database Listthen Prompt from the pop-up menu.

The Properties - Prompt List window is displayed.




Figure 100. Properties - Workstation Class List Window

Figure 101. Properties - Prompt List Window

194 Version 8.1

6. To filter the list results, enter a prompt name in the Prompt Name field. You can alsouse wildcards or leave the field blank to obtain an unfiltered list.




¶ Click Cancel buttonto close the window without running or saving the list.

Creating a List of ParametersTo create a list of parameters:



2. Right-click the scheduler engine button or group button and select Create Database Listthen Parameter from the pop-up menu.

The Properties - Parameter List window is displayed.




6. To filter the list results, enter a parameter name in the Parameter Name field. You canalso use wildcards or leave the field blank to obtain an unfiltered list.





Creating a List of NT UsersTo create a list of users:


Figure 102. Properties - Parameter List Window


16.M

anag

ing

Datab

aseL

ists


2. Right-click the scheduler engine button or group button and select Create Database Listthen NT User from the pop-up menu.

The Properties - NT User List window is displayed.




6. To filter the list results, enter a domain or user name in the NT Domain\User Namefield. You can also use wildcards or leave the field blank to obtain an unfiltered list.





Creating a List of DomainsTo create a list of domains:



2. Right-click the scheduler engine button or group button and select Create Database Listthen Domain from the pop-up menu.

The Properties - Domain List window is displayed.

Figure 103. Properties - NT User List Window

196 Version 8.1




6. To filter the list results, enter a domain name in the Domain Name field. You can alsouse wildcards or leave the field blank to obtain an unfiltered list.





Creating a List of CalendarsTo create a list of calendars:



2. Right-click the scheduler engine button or group button and select Create Database Listthen Calendar from the pop-up menu.

The Properties - Calendar List window is displayed.



Figure 104. Properties - Domain List Window

Figure 105. Properties - Calendar List Window


16.M

anag

ing

Datab

aseL

ists


6. To filter the list results, enter a calendar name in the Calendar Name field. You can alsouse wildcards or leave the field blank to obtain an unfiltered list.





Working with Lists

Displaying a ListTo display a list:


2. Right-click the list you want to run and select Load List from the pop-up menu. The listtool searches the database or plan and displays the objects it finds in the right-hand paneof the Job Scheduling view.

Note: Alternatively, you can select an engine in the tree and double-click the list youwant 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 precedingones. However, as long as a list is kept open, it is maintained and refreshed according to therefresh options specified. To view the list, click the corresponding object in the JobScheduling view.

Detaching a List DisplayDetaching 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.

To detach a database list display:

1. Open a list and wait for the results to be displayed.

Figure 106. Displaying a List

198 Version 8.1

2. Right-click the list in the tree view and select Detach View from the pop-up menu. Thelist window is displayed separately from the Job Scheduling view.

3. To place the list back in the right-hand pane, either close the detached window orright-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 listsor 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 manydetached views open at the same time.

Modifying a Database ListTo modify the properties of a list:


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.




¶ Click Cancel to close the window without running or saving the changes.

Deleting a ListTo delete a list:

1. Select a list button.

2. Click the Delete button in the toolbar or right-click on the list button and select Deletefrom the pop-up menu.

A confirmation message is displayed.

3. Click Yes to delete the list or click Cancel to cancel the delete operation.

Finding ObjectsSearch tools are provided in the Job Scheduling Console to help you find objects in thedatabase. The availability of a search tool is indicated by an ellipsis located next to the fieldwhere you enter an object name. In the following example of the Properties - Resource inDatabase window, the Workstation field provides a search tool.


16.M

anag

ing

Datab

aseL

ists

When you click the ellipsis, the Find Workstation window is displayed.

To use the Find window:

1. Type search arguments in the available fields. You can also use wildcards or leave thefield blank to obtain an unfiltered list.

2. click Start. The results of the search are listed in the lower part of the Find window.

3. Select an object in the list and do one of the following:¶ Click Apply to insert the name of the object in the text box on the parent window.

The Find window remains open to permit you to select other objects from the list.¶ Double-click the object in the list or click OK to insert the name of the object in the

text box on the parent window and close the Find window.¶ Click Cancel to close the Find window without inserting an object name.

Figure 107. Properties - Resource in Database Window

Figure 108. Find Workstation Window

200 Version 8.1

Managing Jobs

A job is a unit of work that is part of a job stream processed at a workstation. It usuallyincludes all necessary computer programs, links, files, and instructions to the operatingsystem.

Creating a Job DefinitionYou create jobs in the database using the Properties - Job Definition window. To create anew job:


2. Click the New Job Definition button on the toolbar or right-click the engine button andselect New Job Definition from the pop-up menu. This opens the Select a Task Typewindow.

3. In the Select a task type window, select a task type from the drop-down list. Once a tasktype is defined for a job it cannot be changed. Table 71 describes the task types:

Table 71. New Job Definition Task TypesThis 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.

Figure 109. Select a Task Type Window

17


17.M

anag

ing

Job

s

Table 71. New Job Definition Task Types (continued)This task type ... Specifies that ...

MPE User Job The job is streamed by an MPE user and is managed by theWorkload Scheduler.

SAP The job is an SAP job that runs on a Workload SchedulerExtended Agent for SAP. The SAP task type is only displayed ifthe Extended Agent for SAP has been installed.

4. Click OK to proceed. The Properties - Job Definition General page is displayed.Alternatively, click Cancel to cancel the operation.

General Page

Use the information in Table 72 to complete the text boxes and select options.

Table 72. Properties - Job Definition General InformationIn this area ... Enter this information ...

Name The name of the job. The name must start with a letter, and cancontain alphanumeric characters, dashes, and underscores. Fornon-expanded databases, it can contain up to eight characters. Forexpanded databases, it can contain up to 40 characters.

Workstation The name of the workstation or workstation class on which the jobruns. You can type a name directly or you can click Find and select aworkstation or workstation class from a list. If you specify aworkstation class, it must match the workstation class of any jobstream in which the job will be included. For information about usingthe Find button, refer to “Finding Objects” on page 199.

Description A description of the job. The description can contain up to 64characters.

Figure 110. Properties - Job Definition General Page

202 Version 8.1

Table 72. Properties - Job Definition General Information (continued)In this area ... Enter this information ...

Is Interactive Select this to indicate that the job runs interactively on the WindowsNT desktop. For Windows NT jobs only.

Login The user name under which the job runs. The name can contain up to47 characters. If the name contains special characters it must beenclosed in quotes (“”). Specify a user that can log on to theworkstation on which the job runs. For Windows NT jobs, the usermust also be defined in the database. For more information, see“Managing Users” on page 263.

To include a parameter in the name:¶ Place the cursor in the Login where you want to insert the

parameter and click the Add Parameter button. The FindParameters window is displayed.

¶ Enter a parameter name in the Find text box. The name cancontain wildcard characters.

¶ Click Start to display a list of parameter names.¶ Select a parameter name in the list and do one of the following:v Click Apply to insert the parameter name in the Login text box

of the Properties - Job Definition window and keep the FindParameters window open.

v Click OK or double-click the parameter in the list to insert theparameter name in the Login text box of the Properties - JobDefinition window and close the Find Parameters window.

v Click Cancel to close the Find Parameters window withoutinserting a parameter name.

A parameter can be used for all or part of the text box and multipleparameters are permitted.


17.M

anag

ing

Job

s

Table 72. Properties - Job Definition General Information (continued)In this area ... Enter this information ...

Recovery Options The recovery options for the job:Action

Specifies the action to be taken if the job ends abnormally(abends). Select one of the following. The default is Stop.Stop If the job abends, do not continue with the next job.Continue

If the job abends, continue with the next job.Rerun If the job abends, rerun the job.

PromptSpecify the text of a recovery prompt, enclosed in quotes, to bedisplayed if the job abends. The text can contain up to 64characters. The recovery prompt is a local prompt and isresponded to using the Job Scheduling Console.

Job

Specify the name of a recovery job to run if the parent jobabends. Click the Find button and select a job from a list.Recovery jobs are run only once for each abended instance of theparent job. For information about using the Find button, refer to“Finding Objects” on page 199.

WorkstationSpecify the name of the workstation on which the recovery jobruns. The name is entered automatically when you select arecovery job.

Not all jobs are eligible to have recovery jobs run on a differentworkstation. Follow these guidelines:¶ If either workstation is an extended agent, it must be hosted

by a domain manager or a fault-tolerant agent that runs inFull Status mode.

¶ The recovery job’s workstation must be in the same domain asthe parent job’s workstation.

¶ If the recovery job’s workstation is a fault-tolerant agent, itmust run in Full Status mode.

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 OptionsPrompt / Job Stop Continue Rerun

Recovery prompt: NoRecovery job: No

Intervention isrequired.

Run job2. Rerun job1. If job1 abends,issue scheduler prompt. Ifreply is yes, repeat above.If job1 is successful, runjob2.

204 Version 8.1

Table 73. Job Stream Recovery Options (continued)Prompt / Job Stop Continue Rerun

Recovery prompt: YesRecovery job: No

Issue recoveryprompt. Interventionis required.

Issue recoveryprompt. If reply isyes, run job2.

Issue recovery prompt. Ifreply is yes, rerun job1. Ifjob1 abends, repeat above.If job1 is successful, runjob2.

Recovery prompt: NoRecovery job: Yes

Run jobr. If itabends, interventionis required. If it issuccessful, run job2.

Run jobr. Run job2. Run jobr. If jobr abends,intervention is required. Ifjobr is successful, rerunjob1. If job1 abends, issuescheduler prompt. If replyis yes, repeat above. Ifjob1 is successful, runjob2.

Recovery prompt: YesRecovery job: Yes

Issue recoveryprompt. If reply isyes, run jobr. If itabends, interventionis required. If it issuccessful, run job2.

Issue recoveryprompt. If reply isyes, run jobr. Runjob2.

Issue recovery prompt. Ifreply is yes, run jobr. Ifjobr abends, intervention isrequired. If jobr issuccessful, rerun job1. Ifjob1 abends, repeat above.If job1 is successful, runjob2.

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 schedulecontaining the abended job to be marked as successful. This will prevent the schedulefrom being carried forward to the next day.

3. If you select the Rerun option without supplying a recovery prompt, Workload Schedulergenerates its own prompt.

4. To reference a recovery job in Conman, you must use the name of the original job (job1in 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 theTask page.


17.M

anag

ing

Job

s

Task Page

The Task page is different for each task type. To complete the fields and select options onthis page:

Table 74. Task TypesFor 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

UNIX Script, NT Script, or Workstation Class ScriptComplete the Script field as follows:

Specify the name of the file the job runs. Enter the file name and any options andarguments. For non-expanded databases, the field can contain up to 255 characters. Forexpanded 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 inits name and use the second file’s name in this field.

To include a parameter in the Script field, do the following:

Figure 111. Properties - Job Definition: Task Window.

206 Version 8.1

¶ Place the cursor in the Script field where you want to insert the parameter and click theAdd Parameter button.

¶ This displays the Find Parameters window.¶ Enter a parameter name in the Find field. The name can contain wildcard characters.¶ Click Start to display a list of parameter names.¶ Select a parameter name in the list and do one of the following:v Click Apply to insert the parameter name in the Script field of the Properties - Job

Definition window and keep the Find Parameters window open.v Click OK or double-click the parameter in the list to insert the parameter name in

the Script field of the Properties - Job Definition window and close the FindParameters window.

v Click Cancel to close the Find Parameters window without inserting a parametername.

A parameter can be used for all or part of the field and multiple parameters are permitted.

UNIX Command, NT Command, or Workstation Class CommandIn the Command field, specify the name of the command the job runs. Enter the commandname and any options and arguments. For non-expanded databases, the field can contain upto 255 characters. For expanded databases, it can contain up to 4095 characters.

Commands are run directly and the jobmanrc standard configuration script is not run.

To include a parameter in the Command field, do the following:¶ Place the cursor in the Command field where you want to insert the parameter and

click Add Parameter .¶ Enter a parameter name in the Find field. The name can contain wildcard characters.¶ Click Start to display a list of parameter names.¶ Select a parameter name in the list and do one of the following:v Click OK or double-click the parameter in the list to insert the parameter name in

the Command field of the Properties - Job Definition window and close the FindParameters window.

v Click Apply to insert the parameter name in the Command field of the Properties -Job Definition window and keep the Find Parameters window open.

v Click Cancel to close the Find Parameters window without inserting a parametername.


MPE Job FileComplete the Job File field by specifying the name of the MPE file the job runs. Forexample, JFILE4.JCL.CORP.

MPE User JobComplete the User Job field by specifying the name from the JOB card of the MPE job. Ifthe scheduler job name does not match the MPE job card name or you want to use skeletonjobs, click the override userjob checkbox and enter the name or wildcard. For example,$USERJOB=UJOB1 or $USERJOB=UJ@.

Extended AgentRefer to the specific user guide for the Extended Agent you are working with for moreinformation.


17.M

anag

ing

Job

s

SAP JobRefer to the Tivoli Workload Scheduler SAP/R3 Extended Agent User Guide for informationabout defining the task.


¶ Click OK to close the Properties - Job Definition window and save the new job in thedatabase.

¶ Click Cancel to close the Properties - Job Definition window without saving the job inthe database.

Displaying a List of Job DefinitionsTo display a list of jobs in the database:

1. In the tree view of the Job Scheduling Console, expand the scheduler engine button.

2. Expand the branches until you see the button for the job list you want to run. See“Creating a List of Jobs” on page 191 for information about creating job lists.

3. Select the job list button.

4. Click the Load List button on the toolbar or right-click on the job list button and selectLoad List from the pop-up menu.

The list results are displayed in the right pane of the Job Scheduling Console.

Table 75 describes the columns in the window.

Table 75. Job Definition List WindowThis column ... Specifies ...

Name The name of the job.

Workstation The name of the workstation on which the job runs.

Figure 112. Job Definition List Window

208 Version 8.1

Table 75. Job Definition List Window (continued)This column ... Specifies ...

Task Type The task type of the job:UNIX Script

Specifies that the job is an executable file on a UNIXcomputer.

UNIX CommandSpecifies that the job is a UNIX command.

NT ScriptSpecifies that the job is an executable file on a Windows NTcomputer.

NT CommandSpecifies that the job is a Windows NT command.

Workstation Class ScriptSpecifies that the job is an executable file on a specific classof workstations.

Workstation Class CommandSpecifies that the job is a command on a specific class ofworkstations.

Extended AgentSpecifies that the job is an Extended Agent job. Refer to thespecific user guide for the Extended Agent you are using formore information.

MPE Job FileSpecifies that the job is an executable file on an MPEcomputer.

MPE User JobSpecifies that the job is streamed by an MPE user and ismanaged by Workload Scheduler.

SAP JobSpecifies that the job is an SAP job. You must install theWorkload Scheduler Extended Agent for SAP software to useSAP jobs.

Creator The name of the user who created the job in the database.

Last Runtime The duration in minutes of the last run of the job.

Displaying a Job DefinitionTo display a job in the database:

1. Run a list of jobs that contains the job you want to display. See “Displaying a List ofJob Definitions” on page 208 for more information.

2. In the list results, double-click the job you want to display or right-click on the job andselect Properties from the pop-up menu.

This displays the job in the Properties - Job Definition window. For information aboutthe Properties - Job Definition window, see “Creating a Job Definition” on page 201.

3. Click OK or on Cancel to close the Properties - Job Definition window.

Displaying Job Definition DetailsTo display job details in the database:


17.M

anag

ing

Job

s

1. Run a list of jobs that contains the job you want to display. See “Displaying a List ofJob Definitions” on page 208 for more information.

2. In the list results, right-click the job you want to display and select Job Details from thepop-up menu.

This displays the Details for Job window.

Table 76 describes the contents of this window.

Table 76. Details for Job WindowThis area ... Contains this information ...

Job Information Job’s logon information:Logon Displays the user logon for the job.Description Displays the description of the job.Script File Displays the name of the job’s script file.

Recovery Information Job’s recovery information:Option Displays the job’s recovery option. It can be

Stop, Continue, or Rerun.Job Displays the name of the job’s recovery job.Prompt Displays the job’s recovery prompt.

Job Run Summary Information about the job from the most recent production plan:Total Runs Displays the total number of times the job has

run.Aborted Runs Displays the total number of abended runs of the

job.Successful Runs

Displays the total number of successful runs ofthe job.

Total CpuTime Displays the total CPU time of the job.Total Elapsed Time

Displays the total elapsed time of the job.Normal Elapsed Time

Displays the elapsed time for previous runs of thejob.

Figure 113. Details for Job Window

210 Version 8.1

Table 76. Details for Job Window (continued)This area ... Contains this information ...

Run Time History Job’s run time history for the last run, the minimum run, and themaximum run:Run Date Displays the date and time of the run.CpuTime The the CPU time of the run.Elapsed Time Displays the elapsed time of the run.

3. Click OK to close the window.

Modifying a Job DefinitionTo modify a job:

1. Run a list of jobs that contains the job you want to modify. See “Displaying a List ofJob Definitions” on page 208 for more information.

2. In the list results, double-click the job you want to modify or right-click on the job andchoose Properties from the pop-up menu. The Properties - Job Definition window isdisplayed.

3. Make your changes. For information about the window, see “Creating a Job Definition”on page 201.


¶ Click OK to save the job in the database and close the window.

¶ Click Cancel to close the window without saving the job in the database.

Deleting Job DefinitionsTo delete jobs in the database:

Figure 114. Properties - Job Definition Window


17.M

anag

ing

Job

s

1. Run a list of jobs that contains the job you want to delete. See “Displaying a List of JobDefinitions” on page 208 for more information.

2. In the list results:¶ To delete one job, right-click the job.¶ To delete multiple jobs in a range, hold down the Shift key, click the first and last

jobs in the range, then right-click one of the selected jobs.¶ To delete multiple jobs that are not in a range, hold down the Ctrl key, click each

job, then right-click one of the selected jobs.

3. Select Delete from the pop-up menu. A confirmation message is displayed for each job.

4. Click OK to delete the job in the database or click Cancel to cancel the delete operation.

212 Version 8.1

Managing Job Streams

Job streams are created and modified using the Job Stream Editor and the Properties - JobStream window. The Job Stream Editor is used to work with the jobs and followsdependencies between the jobs, as well as the run cycles of the job stream. The Properties -Job Stream window is used to specify time restrictions, resource dependencies, filedependencies, and prompt dependencies at the job stream level.

Using the Job Stream EditorUse the Job Stream Editor to create and modify job streams in the database. Job streammanagement functions are divided between three views:

¶ Graph

¶ Timeline

¶ Run Cycle

Each view contains a set of menu and toolbar functions.

Graph ViewThe Graph view provides a graphical display of the jobs in a job stream. Jobs and externaljob dependencies are represented by buttons. Dependencies between jobs are represented asarrows pointing to the successor jobs. Use this view to add and delete jobs and specifydependencies between jobs.

Figure 115. Job Stream Editor Graph View

18


18.M

anag

ing

Job

Stream

s

Table 77 describes the toolbar in the Graph view of the Job Stream Editor.

Table 77. Job Stream Editor Graph View ToolbarThis button ... Has this name ... And does this ...

Properties Displays the Job Stream Properties window.

Save Saves the job stream in the database.

Delete Deletes the selected job.

Undo Delete Undoes the previous Delete operation.

Copy Copies the selected job to the clipboard.

Paste Adds the job on the clipboard to the job stream.

Select Changes the mouse pointer to a selection arrow.

Add Job Definition Adds a job to the job stream. An button is added torepresent the job.

Add Dependency onExternal Job

Adds an button to represent an external jobdependency.

Add Dependency onExternal Job Stream

Adds an button to represent an external job streamdependency.

Add Dependency onInternetwork

Adds an button to represent an internetworkdependency.

Add Link Adds a dependency between jobs in the job stream.

Graph Displays the Graph view.

Timeline Displays the Timeline view.

Run Cycle Displays the Run Cycle view.

Timeline ViewThe Timeline view provides a tabular and timeline display of the time restriction propertiesof 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 andits jobs are displayed in the lower pane. Use the borders and the arrows on the borders toadjust the sizes of the panes. Use the arrows at the top of the timeline pane to move theview in one hour and one day increments.

214 Version 8.1

Time intervals are shown in the right pane. A dark blue bar represents the time restrictionsfor a job or job stream. A light blue bar represents the expected duration, based on past runtimes. A black segment at the end of a timeline represents the deadline time. Where theduration of the job exceeds the deadline time, the blue bar becomes red. The left pane liststhe start, deadline, and duration times for each timeline shown in the right pane.

Dragging a line, or the end of a line, adjusts the start and deadline times of the job streamor a job. Double-clicking the job or job stream name opens time properties windows. Youcan 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 ToolbarThis button ... Has this name ... And does this ...



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.

Go to Day Moves the timeline display to a day offset fromthe schedule date of the plan (Day 0).

Go to First Moves the timeline display to the start time andday offset of the job stream or its earliest job,whichever is the first to occur.



Figure 116. Job Stream Editor Timeline View


18.M

anag

ing

Job

Stream

s

Table 78. Job Stream Editor Timeline View Toolbar (continued)This button ... Has this name ... And does this ...


Run Cycle ViewThe Run Cycle view shows the run cycles of the job stream in a calendar format. Use thisview to add and modify the run cycles of the job stream.

The window is divided into two panes. The left pane lists the types of run cycles defined forthe job stream and the associated freeday rule. The right pane displays a calendar showingincluded or excluded days as defined in the selected run cycle. Use the border and thearrows on the border to adjust the pane size.

Use the tabs above the calendar to select the Monthly or Yearly view and use the arrowsabove 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 ToolbarThis button ... Has this name ... And does this ...



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 oryearly basis.

Weekly Run-Cycle Adds a run cycle of days selected on a weeklybasis.

Calendar Run-Cycle Adds a run cycle of days based on a previouslydefined calendar.


Figure 117. Job Stream Editor Run Cycle View

216 Version 8.1

Table 79. Job Stream Editor Run Cycles View Toolbar (continued)This button ... Has this name ... And does this ...



Creating a Job StreamYou create job streams in the database using the Job Stream Editor. To create a new jobstream, follow these steps:

1. In the tree view of the Job Scheduling Console, click the scheduler engine button.

2. Click New Job Stream on the toolbar or right-click on the scheduler engine button andselect New Job Stream from the pop-up menu.

This displays the Job Stream Editor and the Job Stream Properties window.

Specifying Job Stream PropertiesJob stream properties are specified in the Job Stream Properties window of the Job StreamEditor. There are five groups of job stream properties:

Table 80. Job Stream Properties GroupsThis group ... Is described on page ...

General 218

Time Restrictions 220

Resources 222

Files 223

Prompts 224

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 StreamEditor.

To specify job stream properties, click Generalin the left pane of the Job Stream Propertieswindow. The General page is displayed.


18.M

anag

ing

Job

Stream

s

General Page


Table 81. Job Stream Properties General InformationIn this area ... Enter this information ...

Name The name of the job stream. The name must start with a letter, andcan contain alphanumeric characters and dashes. For non-expandeddatabases, it can contain up to eight characters. For expandeddatabases, it can contain up to 16 characters. The name of a jobstream cannot be changed once is has been saved. However, you canuse the create another command to save the job stream with anothername.

Workstation The name of the workstation or workstation class on which the jobstream is launched. You can type a name directly or you can clickthe Find button and select a workstation or workstation class from alist. If you specify a workstation class, it must match the workstationclass of any jobs or resources used in the job stream. For informationabout using the Find button, refer to “Finding Objects” on page 199.

Description A description of the job stream.

Figure 118. Properties - Job Stream Properties General Page

218 Version 8.1

Table 81. Job Stream Properties General Information (continued)In this area ... Enter this information ...

Priority The priority of the job stream. Select a priority value from thedrop-down list or click of the following buttons:Hold

Sets the priority to 0.High

Sets the priority to 100.Go Sets the priority to 101.Possible priority values are 0 through 101, where 101 is the highestpriority. A priority value of zero prevents the job stream fromlaunching. In the case of High and Go, all jobs in the job stream aregiven the priority. High and Go jobs are launched as soon as theirdependencies are satisfied, overriding the workstation job limit, butnot overriding the job stream job limit or the workstation job fence.

Limit The number of jobs that can be running at the same time in theschedule. Select a job limit value from the drop-down list. Possiblevalues are 0 through 1024. If you specify a job limit of 0, no jobsare launched in the job stream.

Options Check any of the following options that apply:On Request

Check this to specify that the job stream is selected for runningby request. If you select On Request and specify run cycles forthe job stream, the On request flag is ignored and the job streamwill run according to the run cycle. Normally, these job streammust be submitted into the plan by the user or specificallyrequested when schedulr is run. For more information, refer tothe Reference Guide.

Carry ForwardCheck this to specify that the job stream is eligible to be carriedforward to the next day production plan if it is not completedbefore the end of the current day production day. Job streamsthat are carried forward retain the carryforward option, andtherefore, can be carried forward again. You can control thenumber of days a job stream is carried forward by specifying adeadline time (UNTIL keyword) plus x number of days.

Is Monitored Job StreamCheck this to specify that the entire job stream, and every jobthat it contains, must be monitored by Tivoli Business SystemsManager (TBSM) when it runs.

Contains Monitored JobThis read-only item indicates whether any of the jobs in this jobstream will be monitored by Tivoli Business Systems Manager(TBSM) when they run. Value is Yes if at least one of the jobsin the job stream have the Is Monitored Job check box selectedin their Properties window.


18.M

anag

ing

Job

Stream

s

Table 81. Job Stream Properties General Information (continued)In this area ... Enter this information ...

Free Days Calendar Specify the name of the calendar that lists the non-workdays for yourcompany, such as holidays and closing days, when you may not wantthe job stream to run. The calendar of freedays is used during thedefinition of the run cycles for the job stream. It is associated withthe Free day rule, where you tell Workload Scheduler how to handlea job stream if the schedule falls on a freeday. See “ManagingCalendars” on page 266 for details on creating freeday calendars. Doone of the following:¶ Click Use Default to instruct the scheduler to use the default

freedays calendar (usually named Holidays) that is displayed inthe Calendar Name field. When you select this button, all theremaining items in this group become unavailable.

¶ Click Specify Calendar to instruct the scheduler to use adifferent freedays calendar than the default and enter a calendarin the Calendar Name field. Click the ellipsis to open the FindCalendars window if you need to search amongst existingcalendars. Select the Saturday and/or Sunday check boxes ifyou want these days to be counted as freedays in the calendaryou just specified.

When you have finished, click Time Restrictions in the left pane of the Job StreamProperties window. The Time Restrictions page is displayed.

Time Restrictions Page

Figure 119. Properties - Job Stream Time Restrictions Page.

220 Version 8.1


Table 82. Job Stream Time Restrictions InformationIn this area ... Enter this information ...

Start The earliest time the job stream will be launched. The job stream will notbe launched before this time. Make your selections as follows:Specify time

Specify this option to enable the entry of a start time.At Specify a start time in the following format:

hh:mm am|pm

For example, 11:30 am or 4:25 pm.Delay for

Specify the number of days to offset the start time from the day thejob stream is selected for inclusion in the production plan.

Deadline The latest time the job stream will be launched. The job stream will notbe launched after this time. Make your selections as follows:Specify time

Specify this option to enable the entry of a deadline time.At Specify 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 forSpecify the number of days to offset the deadline time from the daythe job stream is selected for inclusion in the production plan.

Time Zone The time zone in which the job stream runs. All time values specified arein this time zone. Select a time zone from the drop-down list. Forinformation about the time zone feature, see “Enabling Time Zones in theWorkload Scheduler” on page 385. If a time zone is not specified for thejob stream, all time values specified in the Time Restrictions propertieswindow are in the time zone of the workstation on which the job streamis launched.

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 moreinformation.

When you have finished, click Resources in the left pane of the Job Stream Propertieswindow. The Resources page is displayed.


18.M

anag

ing

Job

Stream

s

Resources Page

To add a resource dependency for the job stream:

1. Click the Add Row button . This creates a new row in the list of resource dependencies.

2. Double-click in the text box in the Resources column and click Find to locate and inserta resource name. For information about using the Find window, see “Finding Objects”on page 199.

3. Double-click in the text box in the Quantity column and enter the number of resourceunits required by the job stream. The default is one. Resources can be defined with up to1024 units, but they can only be allocated in increments of 32. For example, to allocate1024 units of a resource to a job stream or job you would need to create 32 entries forthe resource with 32 units each.

To remove a resource dependency for the job stream, select the resource row in the list andclick Delete from Table.

When you have finished, click Files in the left pane of the Job Stream Properties window.The Files page is displayed.

Figure 120. Properties - Job Stream Resources Page

222 Version 8.1

Files Page

To add a file dependency for the job stream:

1. Click the Add Row button . This creates a new row in the list of file dependencies.

2. Double-click in the text box in the Workstation column and click Find to locate andinsert the name of a workstation or workstation class. For information about using theFind window, see “Finding Objects” on page 199.

3. Double-click in the text box in the Filename column and type a file name. Alternatively,click Find to locate and insert a file name.

4. Double-click in the text box in the Qualifiers column and enter the test conditions forthe file dependency. On UNIX, the valid qualifiers are the same as UNIX testcommand conditions. For more information, refer to your UNIX system documentation.

On Windows NT, only the following qualifiers are valid:-d %p

True if the file exists and is a directory.-e %p

True if the file exists.-f %p

True if the file exists and is a regular file.-r %p

True if the file exists and is readable.-s %p

True if the file exists and it’s size is greater than zero.-w %p

True if the file exists and is writable.

Notes:

a. On both UNIX and Windows NT, the expression %p inserts the file name.

Figure 121. Properties - Job Stream Files Page


18.M

anag

ing

Job

Stream

s

b. Entering notempty is the same as entering -s %p. If no qualifier is specified, thedefault is -f %p.

To remove a file dependency for the job stream, select the file row in the list and click theDelete from Table button.

When you have finished, click Prompts in the left pane of the Job Stream Propertieswindow. The Prompts page is displayed.

Prompts Page

For an ad hoc prompt dependency, select Ad Hoc Prompt from the drop-down list. For apredefined prompt dependency, select Predefined Prompt from the drop-down list.

To add a prompt dependency for the job stream:

1. Click the Add Row button (+). This creates a new row in the list of promptdependencies.

2. For a predefined prompt, double-click in the text box in the Name column and clickFind to locate and insert the name of a prompt. For information about using the Findwindow, see “Finding Objects” on page 199.

3. For an ad hoc prompt, double-click in the text box in the Text column and type in thetext of the prompt. The default behavior of a prompt is to display a message and wait fora reply. If the string begins with a colon (:), the message is displayed but no reply isnecessary. If the string begins with an exclamation mark (!), the message is not displayedbut it requires a reply. You can include backslash n (\n) within the text for new lines.

You can include one or more scheduler parameters as part or all of the text string. To usea parameter, place its name between carets (^).

Figure 122. Properties - Job Stream Prompts Window

224 Version 8.1

To remove a prompt dependency for the job stream, select the prompt row in the list andclick Delete from Table (X).


¶ Click OK to keep the properties you have selected and close the Job Stream Propertieswindow.

¶ Click Cancel to ignore the properties you have selected and close the Job StreamProperties window.

Adding External Dependencies for a Job StreamJob streams can be dependent on the successful running of other job streams, jobs in otherjob streams, and jobs in other Workload Scheduler networks (internetwork jobs). Theseexternal dependencies are also called predecessors.

To add external dependencies for a job stream, open the job stream in the Job Stream Editorand select External Dependencies from the File menu. The Job Stream ExternalDependencies window is displayed.

By clicking on the drop-down menu, you can add:

¶ External job stream dependencies

¶ Internetwork dependencies

¶ External job dependencies

Figure 123. Job Stream External Dependencies Window

Figure 124. External Dependencies Menu


18.M

anag

ing

Job

Stream

s

Adding an External Job Stream DependencyTo add an external job stream dependency:

1. Select External Job Stream from the drop-down menu at the top of the window.

2. Click the Add Row button.

3. Double-click in the Job Stream Name column of the new row.

4. Click the Find (...) button in the Job Stream Name column and use the Find JobStream window to select a job stream. For information about using the Find window, see“Finding Objects” on page 199.


¶ Click OK to add the dependency and close the window

¶ Click Cancel to close the window without adding the dependency.

Adding an Internetwork DependencyTo add an internetwork dependency:

1. Select Internetwork from the drop-down menu at the top of the window.

2. Click the Add Row button (+).

3. Double-click in the Network Agent column of the new row.

4. Click the Find (...) button in the Network Agent column and use the Find Workstationwindow to select the name of the network agent. Internetwork dependencies require thata network agent is configured to communicate with the external scheduler network. Forinformation about configuring a network agent, refer to the Tivoli Workload Scheduler:Reference Guide.

5. Double-click in the Dependency column of the new row and enter either a freeformdependency, or the job or job stream predecessor in the formworkstation#jobstream.job.




Adding an External Job DependencyTo add an external job dependency:

1. Select External Job from the drop-down menu at the top of the window.

2. Click the Add Row button (+).

3. Double-click in the Job Name column of the new row.

4. Click the Find (...) button in the Job Name column and use the Find Job window toselect a job. For information about using the Find window, see “Finding Objects” onpage 199.




226 Version 8.1

Deleting External Dependencies from a Job StreamJob streams can be dependent on the successful running of other job streams, jobs in otherjob streams, and jobs in other Workload Scheduler networks (internetwork jobs). Theseexternal dependencies are also called predecessors.

To delete external dependencies for a job stream:

1. Open the job stream in the Job Stream Editor.

2. Select External Dependencies from the File menu. This displays the Job StreamExternal Dependencies window.

3. Select External Job Stream, Internetwork, or External Job from the drop-down menu.

4. Click the row of the dependency in the list you want to delete and click on the DeleteRow button (×).


¶ Click OK to delete the dependency and close the window

¶ Click Cancel to close the window without deleting the dependency.

Adding a Job to a Job StreamA job definition is a description of work to be performed on a workstation. Jobs arescheduled for running by adding them to job streams. You add jobs in a job stream using theGraph view of the Job Stream Editor. See “Graph View” on page 213 for more information.

To add a job to a job stream:

1. To open the Graph view, right-click a job stream and select Open from the pop-upmenu.

2. In the Graph view, click the Add Job Definition button in the toolbar.

3. Move the mouse pointer to the position you want to place the new job in the Graph viewand left-click. The Properties - Job window is displayed. When you have completed thejob properties, a new job button is added in the Graph view.

Specifying Job PropertiesThe Properties - Job window opens automatically when you add a new job to a job stream.If the window is not displayed, right-click a job in the Graph view of the Job Stream Editorand select Properties from the pop-up menu.

There are five pages of job properties in the Properties - Job window:

¶ General

¶ Time Restrictions

¶ Resources

¶ Files

¶ Prompts

By default, the Properties - Job General page is displayed first.


18.M

anag

ing

Job

Stream

s

General Page


Table 83. Properties - Job General InformationIn 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 isdeleted, the task type for the job is unknown and must be specified beforeyou can save the job again.

Priority The priority of the job. Select a priority value from the drop-down list orclick 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 highestpriority. 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 theoperator. When a job with requires confirmation enabled completes, itremains in the internal status PEND until confirmation is received. Ifconfirmation is received before the job completes, its internal status iseither SUCCP or ABENDP and other job and job stream successors arenot released.

Is Monitored Job Mark this check box to specify that the running of this job must bemonitored by Tivoli Business Systems Manager.

Select Time Restrictions in the left pane of the Properties - Job window. The Restrictions pageis displayed.

Figure 125. Properties - Job General Page

228 Version 8.1



Table 84. Properties - Job Time Restrictions InformationIn this area ... Enter this information ...

Start time The earliest time the job will be launched. The job will not be launchedbefore this time. Make your selections as follows: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


Enter the number of days to offset the start time from the day the jobis selected for inclusion in the production plan.

Deadline Specifies the latest time the job will be launched. The job will not belaunched after this time. Make your selections as follows: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 forEnter the number of days to offset the deadline time from the day thejob is selected for inclusion in the production plan.

Time Zone The time zone in which the job runs. All time values specified in the TimeRestrictions view of the Properties - Job window are in this time zone.Select a time zone from the drop-down list. For information about thetime zone feature, see “Enabling Time Zones in the Workload Scheduler”on page 385. If a time zone is not specified for the job, all time values

specified in the Properties - Job Time Restrictions page are in the timezone of the workstation on which the job is launched.

Figure 126. Properties - Job Time Restrictions Page


18.M

anag

ing

Job

Stream

s

Table 84. Properties - Job Time Restrictions Information (continued)In this area ... Enter this information ...

Repeat Range The repetition rate of the job. The job is launched multiple times at thisrate.Hours

Specify the hours that a job repeats.Minutes

Specify the minutes that the job repeats.If you cancel a repetitive job, it will not be launched again. If you rerun arepetitive job, the next iteration of the job is run immediately. If you reruna repetitive job that had been cancelled, the repetition rate is reinstalled. Ifa repetitive job abends, the repetitions continue following the optionalrecovery action.

Est. Duration The estimated duration of the job if the job has run before.Normal Elapsed Time

Displays the average time this job requires to run, based on previousruns.

Note: Time Restrictions can also be set in the Job Stream Editor Timeline view. For moreinformation, see “Timeline View” on page 214.

Select Resources in the left pane of the Properties - Job window. The Resources page isdisplayed.

Resources Page

To add a resource dependency for the job:

1. Click the Add Row button. This creates a new row in the list of resource dependencies.

2. Double-click in the text box in the Resources column and click the Find (...) button tolocate and insert a resource name. For information about using the Find window, see“Finding Objects” on page 199.

3. Double-click in the text box in the Quantity column and enter the number of resource unitsrequired by the job.

Figure 127. Properties - Job Resources Page

230 Version 8.1

To remove a resource dependency for the job, select the resource row in the list and click theDelete from Table button.

Select Files in the left pane of the Properties - Job window. The Files page is displayed.

Files Page

To add a file dependency for the job:

1. Click the Add Row button. This creates a new row in the list of file dependencies.

2. Double-click in the text box in the Workstation column and enter a workstation orworkstation class name. Alternatively, click the Find button to locate and insert the name ofa workstation or workstation class.

3. Double-click in the text box in the Filename column and enter a file name. Alternatively,click the Find button to locate and insert a file name

4. Double-click in the text box in the Qualifiers column and enter the test conditions for thefile dependency. On UNIX, the valid qualifiers are the same as UNIX test commandconditions. For more information, refer to your UNIX system documentation.

On Windows NT, only the following qualifiers are valid:

-d %p True if the file exists and is a directory.

-e %p True if the file exists.

-f %p True if the file exists and is a regular file.

-r %p True if the file exists and is readable.

-s %p True if the file exists and it’s size is greater than zero.

-w %p True if the file exists and is writable.

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.

Figure 128. Properties - Job Files Page


18.M

anag

ing

Job

Stream

s

To remove a file dependency for the job, select the file row in the list and click the Delete fromTable button.

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 apredefined prompt dependency, select Predefined Prompt from the drop-down list.

To add a prompt dependency for the job, do the following:

1. Click the Add Row (+) button. This creates a new row in the list of prompt dependencies.

2. For a predefined prompt, double-click in the text box in the Name column and click theFind (...) button to locate and insert the name of a prompt. For information about using theFind window, see “Finding Objects” on page 199.

3. For an ad hoc prompt, double-click in the text box in the Text column and enter the text ofthe prompt.

The default behavior of a prompt is to display a message and wait for a reply. If the stringbegins with a colon (:), the message is displayed but no reply is necessary. If the stringbegins with an exclamation mark (!), the message is not displayed but it requires a reply.You can include backslash n (\n) within the text for new lines.

You can include one or more scheduler parameters as part or all of the text string. To use aparameter, place its name between carets (^).

To remove a prompt dependency for the job, select the prompt row in the list and click theDelete from Table button.


¶ Click OK to keep the properties you have selected and close the window. If you are addinga new job, a job button is added in the Graph view.

¶ Click Cancel to close the window without saving the properties you have selected.

Copying and Pasting JobsWithin the Job Stream Editor you can copy and paste job and job stream buttons to createdependencies:

Figure 129. Properties - Job Prompts Page

232 Version 8.1

¶ You can copy a job stream from a job stream list and paste it into the Graph view of theJob Stream Editor. Then, using the Add Link button, you can create a dependencybetween this job stream and any jobs in the Job Stream Editor.

¶ You can open multiple job streams in separate Job Stream Editors and copy and pastejobs between the job streams.

¶ You can copy a job within the Job Stream Editor and clone its dependencies to anotherjob.

Cloning the Job DependenciesThis procedure is used to clone the dependencies of a job to a new job within the Graphview of the Job Stream Editor.

To clone the dependencies of a job:

1. Right-click the job button and select Copy from the pop-up menu. Alternatively, selectthe job button and click the Copy button in the toolbar or select Copy from the Editmenu. This copies the job to the clipboard.

2. Click the Paste button in the toolbar or select Paste from the Edit menu. This displaysthe Properties - Job window for the copied job.

3. Use the find tool to find and select a new job to add to the job stream. The job name isadded to the Properties - Job General page.

4. When you click OK in the Properties - Job window, a new button is added for the job inthe Graph view of the Job Stream Editor. This job has the same dependencies as thecopied job.

5. When you have finished in the Job Stream Editor, save the job stream and close the JobStream Editor. For more information see “Saving a Job Stream in the Database” onpage 247 and “Closing the Job Stream Editor” on page 247.

Adding an Internetwork Dependency to a Job StreamAn internetwork dependency is a dependency on a job that runs in another WorkloadScheduler network. Internetwork dependencies require a network agent workstation tocommunicate with the external scheduler network. For more information about configuring anetwork agent, refer to the Tivoli Workload Scheduler Reference Guide.

Add internetwork dependencies to a job stream to create predecessors for the jobs in the jobstream you are editing. A predecessor must complete successfully before the successor job islaunched.

You add internetwork dependencies in a job stream using the Graph view of the Job StreamEditor. See “Graph View” on page 213 for more information.


18.M

anag

ing

Job

Stream

s

To add an internetwork dependency:


2. In the Graph view, click the Add Dependency on Internetwork button in the toolbar.

3. Move the mouse pointer to the position you want to place the new internetworkdependency in the Graph view and left-click. The Internetwork Dependency window isdisplayed.

4. Click the Find (...) button and use the Find Workstation window to select the name ofthe network agent.

5. In theDependency field, specify either the freeform dependency, or the job or job streampredecessor in the format workstation#jobstream.job. The maximum length of thisfield is:¶ 120 for freeform characters¶ 16 for the workstation¶ 16 for the job stream¶ 40 for the job


¶ Click OK to close the window. If you are adding a new internetwork dependency, a newinternetwork dependency button is added in the Graph view.


For information about using an internetwork dependency as a predecessor, see “CreatingDependencies Between Jobs in a Job Stream” on page 236.

Adding an External Job Stream to a Job StreamAn external job stream is any job stream other than the one you are editing. Add externaljob streams to a job stream to create predecessors for the jobs in the job stream you areediting. A predecessor must complete successfully before the successor job is launched.

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.

To add an external job stream:


2. In the Graph view, click the Add Dependency on External Job Stream button in thetoolbar.

3. Move the mouse pointer to the position you want to place the new external job stream inthe Graph view and left-click. The External Job Stream Dependency window isdisplayed.

234 Version 8.1

4. Click the Find (...) button next to the Workstation field to locate and insert the name ofthe 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.


¶ Click OK to close the window. A job stream button is added in the Graph view.


For information about using an external job stream as a predecessor, see “CreatingDependencies Between Jobs in a Job Stream” on page 236.

Adding an External Job to a Job StreamAn external job is a job that runs in a job stream other than the one you are editing. Addexternal jobs to a job stream to create predecessors for the jobs in the job stream you areediting. 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. Formore information, see “Graph View” on page 213.

To add an external job:


2. In the Graph view, click the Add Dependency on External Job button in the toolbar.

3. Move the mouse pointer to the position you want to place the new external job in theGraph view and left-click. The External Job Dependency window is displayed.

Figure 130. External Job Stream Dependency Window


18.M

anag

ing

Job

Stream

s

4. Click the Find (...) button next to the Job Stream Name field to locate and insert thename of the job stream in which the job runs. For information about using the Findwindow, see “Finding Objects” on page 199.

5. Click Show Jobs to list the jobs in the selected job stream that run on the selectedworkstation.

6. Select a job in the list.


¶ Click OK to close the window. A job button is added in the Graph view.

¶ Click Cancel to close the window without saving the properties you selected.

For information about using an external job as a predecessor, see “Creating DependenciesBetween Jobs in a Job Stream”.

Creating Dependencies Between Jobs in a Job StreamYou can add dependencies between jobs to specify the order in which they run. A job thatdepends on the successful completion of another job is called a successor and the job or jobstream that it depends on is called a predecessor.

You add dependencies between jobs in the Graph view of the Job Stream Editor. For moreinformation, see “Graph View” on page 213. The dependencies are represented by arrows.

To add a dependency between jobs:


2. In the Graph view, click the Add Link button in the toolbar.

3. Click the predecessor job or job stream and drag it to the successor job. When yourelease the mouse button, an arrow is drawn from the predecessor to the successor.

Figure 131. External Job Dependency Window

236 Version 8.1

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 arenot saved when the Job Stream Editor is closed.

To remove a dependency between jobs, select the arrow between the predecessor and thesuccessor , 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 theDatabase” on page 247.

Specifying Run Cycles for a Job StreamRun cycles specify when a job stream in the database is to run in the plan. Combinations ofrun cycles are used to include and exclude certain dates. There are three types of run cycle:

¶ Simple Run CyclesBased on specific calendar dates.

¶ Weekly Run CyclesBased on days of the week.

¶ Calendar Run CyclesBased on predefined calendars. For details about creating calendars, see “ManagingCalendars” on page 266.

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 StreamEditor or click the Run Cycle button in the toolbar. For more information, see “Run CycleView” on page 216.

Inclusionary or Exclusionary Run CyclesWhen you define a run cycle, you must specify if it designates the days when the job streamis 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 listof run cycles applied to the job stream.

Figure 132. Job Stream Editor Window Graph View


18.M

anag

ing

Job

Stream

s

The days you mark in an exclusive run cycle are displayed as Days Excluded in the listof run cycles applied to the job stream. Excluded days always take precedence overincluded days.

For each job stream, you can define as many inclusive and exclusive run cycles as youwant.

Rule for FreedaysThis rule is based on the definition of freedays. Freedays are non-workdays, such asholidays or closing days, and can be defined in one or more specific calendars. Freedayscalendars can in other terms be considered the list of non-workdays when there is no activityin 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 jobstream. The rule determines what action Workload Scheduler must take when the schedule ofa job stream falls on a freeday. If the schedule date falls on a freeday, the scheduler can doone 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 streameven if the selected run date is a freeday.

Workload Scheduler does not reschedule the same job stream more than once on a givenproduction day if its run date was moved because of a freeday rule application.

Colored Bars on DatesAs you include and exclude dates, colored bars are displayed across the dates. The bars havethe following meanings:

Table 85. Colored Bars on DatesThis 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 moreinformation, see “The Holidays Calendar” on page 266.

238 Version 8.1

Specifying Simple Run CyclesYou specify run cycles using the Job Stream Editor. To do this:

1. Right-click a job stream and select Open from the pop-up menu. The Job Stream Editoris displayed

2. Click the Run Cycle button in the toolbar.

3. In the Run Cycle view, click the Simple Run Cycle button. The Simple Run CycleGeneral page is displayed.

4. In the Inclusive/Exclusive Run Cycle box:¶ Select Inclusive to specify that the job stream must run in the dates defined on the

Rule page.¶ Select Exclusive to specify that the job stream must not run in the dates defined on

the Rule page.

5. Click the arrow in the Rule for Freedays list box and select one of:Select nearest workday before freeday

If the scheduled date falls on a freeday, run the job stream on the precedingworkday.

Select nearest workday after freedayIf the scheduled date falls on a freeday, run the job stream on the followingworkday.

If freeday, do not selectIf the scheduled date falls on a freeday, do not run the job stream.

NoneFollow no rule. Run the job stream regardless of whether the schedule falls on afreeday or on a workday.

6. Select Rule in the left pane of the Simple Run Cycle window. The Rule page isdisplayed.

Figure 133. Simple Run Cycle General Page


18.M

anag

ing

Job

Stream

s

7. Select the Monthly or Yearly tab to display the corresponding view. Use the arrowbuttons in the upper and lower bars of the selected view to move to the desired monthand year.

8. Click the dates in the calendar to add them to the run cycle. Click on the same date asecond time to remove it from the run cycle.


¶ Click OK to close the window and add the run cycle to the job stream.

¶ Click Cancel to close the window without adding the run cycle to the job stream.

Specifying Weekly Run CyclesTo specify a weekly run cycle for a job stream:



3. In the Run Cycle view, click the Weekly Run Cycle button. The Weekly Run CycleGeneral page is displayed.

Figure 134. Simple Run Cycle Rule Page

240 Version 8.1

4. In the Inclusive/Exclusive Run Cycle box:¶ Select Inclusive to specify that the job stream must run in the dates defined n the

Rule page.¶ Select Exclusive to specify that the job stream must not run in the dates defined in

the Rule page.

5. Click the arrow in the Rule for Freedays list box and select one of:Select nearest workday before freeday

If the scheduled date falls on a freeday, run the job stream on the precedingworkday.




6. Click Rule to display the Rule page which is shown below

Figure 135. Weekly Run Cycle General Page

Figure 136. Weekly Run Cycle Rule Page


18.M

anag

ing

Job

Stream

s

7. Select the days by name to add them to the run cycle. In addition to single days, you canalso select:Weekdays

Specifies every day of the week except Saturday and Sunday.Freedays

Specifies the days defined either in the freedays calendar or in the Holidayscalendar, depending on which one you specified in the properties window of the jobstream.

WorkdaysSpecifies every day of the week except Saturday, Sunday, and the days definedeither in the freedays calendar or in the Holidays calendar, depending on which oneyou specified in the properties window of the job stream.

EverydaySpecifies every day of the week.




Specifying Calendar Run CyclesTo specify a calendar run cycle for a job stream:



3. In the Run Cycle, click the Calendar Run Cycle button. The Calendar Run CycleGeneral page is displayed.

4. In the Inclusive/Exclusive Run Cycle box¶ Select Inclusive to specify that the job stream must run in the dates defined n the

Rule page.¶ Select Exclusive to specify that the job stream must not run in the dates defined in

the Rule page.

5. Click the arrow in the Rule for Freedays list box and select one of:

Figure 137. Calendar Run Cycle General Page

242 Version 8.1

Select nearest workday before freedayIf the scheduled date falls on a freeday, run the job stream on the precedingworkday.




6. Click Rule in the left pane of the Calendar Run Cycle window. The Calendar Run CycleRule page is displayed.

7. Enter the name of the calendar in the Name field or click the Find (...) button to find acalendar. 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. Forexample, if a calendar date is 3/13/2001, an offset of +2 Days results in an effective dateof 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 eitherin the freedays calendar or in the Holidays calendar, depending on which oneyou specified in the properties window of the job stream.

WeekdaysSpecifies calendar days except Saturday and Sunday.




Figure 138. Calendar Run Cycle Rule Page


18.M

anag

ing

Job

Stream

s

Modifying Run Cycles for a Job StreamTo modify the run cycles for a job stream:


2. Click the Run Cycle view button. The Run Cycle page is displayed.

3. In the Run Cycles Name column, double click the run cycle you want to modify.¶ If this is a simple run cycle:

A window is displayed showing the days selected by that run cycle. Modify the daysselected and click OK to save your changes.

¶ If this is a weekly run cycle:A window is displayed showing the days selected by that run cycle. Modify the daysselected and click OK to save your changes.

¶ If this is a calendar run cycle:A window is displayed showing the name of the calendar you selected and specifiedoffset. Modify the selected calendar or the offset and click OK to save your changes.


¶ Click OK to close the window and save the changes to the job stream.

¶ Click Cancel to close the window without saving the changes to the job stream.

Deleting Run Cycles from a Job StreamTo delete a run cycle from a job stream:


2. Click the Run Cycle view button. The Run Cycle page is displayed.

3. In the Run Cycles Name column, select the run cycle you want to delete from the jobstream.

4. Click Delete. The run cycle is deleted from the job stream. If the run cycle was acalendar it is deleted from this job stream, but it is not deleted from the database and canstill be used by other job streams.


¶ Click OK to close the window and save the changes to the job stream.

¶ Click Cancel to close the window without saving the changes to the job stream.

Specifying Time Restrictions in the Timeline ViewYou can display and specify the time restrictions for a job stream and its jobs using theTimeline view of the Job Stream Editor. For information about the Timeline view refer to“Timeline View” on page 214.

Specifying Time Restrictions for a Job StreamTo specify time restrictions for the job stream in the Timeline view of the Job Stream Editor,select Timeline from the View menu in the Job Stream Editor or click the Timeline buttonin the toolbar.

244 Version 8.1

Using the TimelineTo adjust the time restrictions using the timeline, do any of the following:

¶ Drag the left side of the timeline to adjust the start time.

¶ Drag the right side of the timeline to adjust the deadline time.

¶ Drag the center of the timeline to change both the start and the deadline time.

Using a WindowTo adjust the time restrictions using a window, either double-click the job stream row in thetabular pane or right-click the row and select Properties from the pop-up menu. A propertieswindow is displayed.


Table 86. Properties InformationIn this area ... Enter this information ...

Start The earliest time the job stream will be launched. The job stream willnot be launched before this time.Specify time


hh:mm am|pm


Enter the number of days to offset the start time from the day thejob stream is selected for inclusion in the production plan.

Deadline The latest time the job stream will be launched. The job stream willnot be launched after this time.Specify time


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 forEnter the number of days to offset the deadline time from the daythe job stream is selected for inclusion in the production plan.


¶ Click OK to close the window and save the time restrictions.

¶ Click Cancel to close the window without saving the time restrictions.

Note: Time Restrictions can also be set in the Time Restrictions view of the Properties - Jobwindow. For more information, see “Specifying Job Stream Properties” on page 217.

Specifying Time Restrictions for a JobTo specify time restrictions for a job in the Timeline view of the Job Stream Editor, eitherselect Timeline from the View menu in the Job Stream Editor or click the Timeline buttonin the toolbar.


18.M

anag

ing

Job

Stream

s

Using the TimelineTo adjust the time restrictions using the timeline, do any of the following:

¶ Drag the left side of the timeline to adjust the start time.

¶ Drag the right side of the timeline to adjust the deadline time.

¶ Drag the center of the timeline to change both the start and the deadline time.

Using a WindowTo adjust the time restrictions using a window, double-click the job row in the tabular paneor right-click the row and select Properties from the pop-up menu. A properties window isdisplayed


Table 87. Properties InformationIn this area ... Enter this information ...

Start The earliest time the job will be launched. The job will not belaunched before this time.Specify time


hh:mm am|pm


Enter the number of days to offset the start time from the day thejob is selected for inclusion in the production plan.

Deadline The latest time the job will be launched. The job will not be launchedafter this time.Specify time


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 forEnter the number of days to offset the deadline time from the daythe job is selected for inclusion in the production plan.

Time Zone The time zone for this job. For information about the time zonefeature, see “Enabling Time Zones in the Workload Scheduler” onpage 385.

Repeat Range The repetition rate of the job. The job is launched multiple times atthis rate.Hours

Specify the hours that a job repeats.Minutes

Specify the minutes that the job repeats.


¶ Click OK to close the window and save the time restrictions.

246 Version 8.1

¶ Click Cancel to close the window without saving the time restrictions.

Note: Time restrictions can also be set in the Time Restrictions view of the Properties - Jobwindow. See “Specifying Job Properties” on page 227 for more information.

Saving a Job Stream in the DatabaseTo save a job stream in the database from the Job Stream Editor, click on the Save button inthe toolbar or select Save from the File menu.

Closing the Job Stream EditorTo close the Job Stream Editor, click the Close button in the window title bar or selectClose from the File menu.

If you have not saved your job stream changes, a warning messages is displayed. Do one ofthe 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.

¶ Click Cancel to return to the Job Stream Editor without saving the job stream in thedatabase.

Displaying a List of Job StreamsTo display a list of job streams in the database:


2. Expand the branches below the scheduler until you see the button for the job stream listyou want to run. For information about creating job stream lists, see “Creating a List ofJob Streams” on page 190.

3. Select the job stream list button.

4. Right-click the job stream list button and select Load List from the pop-up menu. Thelist results are displayed in the right pane of the Job Scheduling view.

Figure 139. Job Streams List Window


18.M

anag

ing

Job

Stream

s

Table 88 describes the column headings.

Table 88. Job Streams List ColumnsThis column ... Specifies ...

Job Stream The name of the job stream.

Workstation The name of the workstation on which the job stream runs.

Status The current JSS status of the job stream.

Internal Status The Workload Scheduler internal status for the job stream instance.

Information Information about the job stream status. Can be:In OrderCarried ForwardCarryDeadline time has passedReleased from dependenciesCanceledCancel Pend.

Priority The priority of the job stream.

Num Jobs The number of jobs in the job stream.

OK Jobs The number of jobs that ran successfully.

Limit The number of jobs in the job stream that can run concurrently.

Original Job Stream The original name of the job stream, if it has been resubmitted orcarried over.

Scheduled Start The scheduled start time of the job stream.

Actual Start The time the job stream actually started.

Est. Duration The estimated duration of the job stream, based on previous timesthe job stream ran.

Actual Duration The actual duration of the job stream.

Deadline Time The time after which the job stream cannot run.

Job stream Dep. The number of job stream dependencies on the job stream. Thedependency can be a predecessor or successor.

Job Dep. The number of job dependencies on the job stream. Thedependency can be a predecessor or successor.

Inet Dep. The number of internetwork predecessors to the job stream.

File Dep. The number of file dependencies on the job stream.

Prompt Dep. The number of prompt dependencies on the job stream.

Resource Dep. The number of resource dependencies on the job stream.

Is Monitored Job Stream Whether or not the job stream, and all the jobs it contains, is to bemonitored by Tivoli Business Systems Manager.

When you right-click a job stream instance in the list, a pop-up menu is displayed. This isdescribed in “Managing Job Stream Instances in the Plan” on page 316.

Displaying a Job StreamTo display a job stream in the database:

1. Run a list of job streams that contains the job stream you want to display. For moreinformation, see “Displaying a List of Job Streams” on page 247.

248 Version 8.1

2. In the list results, either double-click the job stream you want to display, or right-clickthe job stream and select Properties from the pop-up menu.

The job stream is displayed in the Job Stream Editor. For information about the JobStream Editor, see “Creating a Job Stream” on page 217.

3. Click OK or on Cancel to close the Job Stream Editor.

Modifying a Job StreamTo modify a job stream in the database:

1. Run a list of job streams that contains the job stream you want to modify. For moreinformation, see “Displaying a List of Job Streams” on page 247.

2. In the list results, right-click the job stream and select Properties from the pop-up menu.The Properties - Job Stream window is displayed.

3. Make your changes in the Job Stream Editor. For more information, see “Specifying JobStream Properties” on page 217.

Table 89 shows where to find information about modifying a job stream.

Table 89. Modifying Objects in a Job StreamTo modify these objects ... See ...

Jobs “Modifying a Job in a Job Stream” and “Deleting a Job ina Job Stream”.

Internetwork dependencies “Modifying an Internetwork Dependency in a Job Stream”and “Deleting an Internetwork Dependency in a JobStream” on page 250.

External job streams “Modifying an External Job Stream in a Job Stream” onpage 250 and “Deleting an External Job Stream in a JobStream” on page 250.

External jobs “Modifying an External Job in a Job Stream” on page 250and “Deleting Job Streams” on page 250.

When you are finished modifying the job stream, save the job stream in the database andclose the Job Stream Editor. For more information, see “Saving a Job Stream in theDatabase” on page 247 and “Closing the Job Stream Editor” on page 247.

Modifying a Job in a Job StreamTo modify a job in a job stream, right-click the job button in the Graph view and selectProperties from the pop-up menu. For information about job properties, see “Specifying JobProperties” on page 227.

Deleting a Job in a Job StreamTo delete a job in a job stream, right-click the job button in the Graph view and selectDelete from the pop-up menu.

Modifying an Internetwork Dependency in a Job StreamTo modify an internetwork dependency in a job stream, right-click its button in the Graphview and select Properties from the pop-up menu. For information about internetworkdependency properties, see “Adding an Internetwork Dependency to a Job Stream” onpage 233.


18.M

anag

ing

Job

Stream

s

Deleting an Internetwork Dependency in a Job StreamTo delete an internetwork dependency in a job stream, right-click its button in the Graphview and select Delete from the pop-up menu.

Modifying an External Job Stream in a Job StreamTo modify an external job stream in a job stream, right-click its button in the Graph viewand select Edit , then External Job Stream from the pop-up menu. The job stream isdisplayed in the Job Stream Editor. For information about the Job Stream Editor, see “Usingthe Job Stream Editor” on page 213 and “Creating a Job Stream” on page 217.

Deleting an External Job Stream in a Job StreamTo delete an external job stream in a job stream, right-click its button in the Graph view andselect Delete from the pop-up menu.

Modifying an External Job in a Job StreamTo modify an external job in a job stream:

1. Right-click its button in the Graph view and select Edit, then External Job Streamfrom the pop-up menu. The job stream is displayed in the Job Stream Editor. Forinformation about the Job Stream Editor, see “Using the Job Stream Editor” on page 213and “Creating a Job Stream” on page 217.

2. To edit the job, right-click the job button in the Graph view and select Properties fromthe pop-up menu. For information about job properties, see “Specifying Job Properties”on page 227.

Deleting an External Job in a Job StreamTo delete an external job in a job stream, right-click its button in the Graph view and selectDelete from the pop-up menu.

Deleting Job StreamsTo delete job streams in the database, run a list of job streams that contains the job streamyou want to delete. For more information, see “Displaying a List of Job Streams” onpage 247.

To delete ... Do this ...

One job stream Right-click the job stream and select Delete from the pop-up menu

Multiple job streams in a range Hold down the Shift key, click the first and last job streams in therange, then right-click on one of the selected job streams and selectDelete from the pop-up menu

Multiple job streams that are notin a range

Hold down the Ctrl key, click each job stream, then right-click oneof the selected job streams and select Delete from the pop-upmenu

A message is displayed for each job stream asking for confirmation.

Click OK to delete the job stream in the database or click Cancel to cancel the deleteoperation.

250 Version 8.1

Managing Workstations and WorkstationClasses

Managing WorkstationsA workstation is usually an individual computer, on which jobs and job streams are run. Aworkstation definition is required for every computer that runs jobs in the WorkloadScheduler network.

Primarily workstation definitions refer to physical workstations. However, in the case ofextended agents, the workstations are logical definitions that must be hosted by a physicalworkstation.

There are several types of workstations in a Workload Scheduler Network:

¶ Master domain manager

¶ Domain manager

¶ Backup domain manager

¶ Fault-tolerant agent

¶ Standard agent

¶ Extended agent

¶ Network agent

Creating a WorkstationYou create workstations in the database using the Properties - Workstation in Databasewindow. To create a new workstation, follow the steps below. See also “Creating aWorkstation by Copying Another Workstation” on page 257. For information about creatingextended agent workstations, see the user manual for the specific extended agent.

In the tree view of the Job Scheduling Console, right-click the scheduler engine button andselect New Workstation from the pop-up menu. The Properties - Workstation in Databasewindow is displayed.

19


19.M

anag

ing

Wo

rkstation

s


Table 90. Properties - Workstation in Database InformationIn this area ... Enter this information ...

Workstation name The name of the workstation. The name must start with a letter and cancontain alphanumeric characters, dashes, and underscores. Fornon-expanded databases, it can contain up to eight characters. Forexpanded databases, it can contain up to 16 characters.Note: Workstation names must be unique, and cannot be the same asworkstation class and domain names.

Node The host name or the IP address of the workstation. Fully-qualifieddomain names are accepted.

TCP Port The Netman TCP port number that Workload Scheduler uses forcommunications on the workstation. The default is 31111. The portnumber of Netman on a workstation is defined by the localopts file in theparameter nm port.

Operating System The operating system of the workstation. Select one of:UNIXWindows NTMPE/VMPE/IXOther

Domain The name of the Workload Scheduler domain of the workstation. Thename must start with a letter and can contain alphanumeric characters,dashes, and underscores. For non-expanded databases, it can contain up toeight characters. For expanded databases, it can contain up to 16characters.Note: Domain names must be unique, and cannot be the same asworkstation and workstation class names. The default for fault-tolerant andstandard agents is the master domain, usually named MASTERDM. Thedefault for a domain manager is the domain in which it is defined as themanager. The default for an extended agent is the domain of its host.

Figure 140. Properties - Workstation in Database Window

252 Version 8.1

Table 90. Properties - Workstation in Database Information (continued)In this area ... Enter this information ...

Time Zone The time zone of the workstation. Choose a time zone name from thedrop-down list. For a description of time zone names, refer to the TivoliWorkload Scheduler Reference Guide. To ensure the accuracy ofscheduling times, this time zone must be the same as the computer’soperating system time zone.

Description A description of the workstation. The description can contain up to 40characters.

Workstation Type The type of workstation. Select one of the following from the drop-downlist:Fault-tolerant Agent

Select this type for an agent workstation that is capable of launchingits jobs and resolving local dependencies without a domain manager.Select this type for fault-tolerant agents, domain managers, andbackup domain managers.

Extended AgentSelect this type for an agent workstation that launches jobs onlyunder the direction of its host. Extended agents can be used tointerface Workload Scheduler with non-Tivoli systems andapplications. For more information refer the user manual for thespecific extended agent.

Standard AgentSelect this type for an agent workstation that launches jobs onlyunder the direction of its domain manager.

Auto Link Whether to open the link between workstations at startup. Forfault-tolerant and standard agents, select this option to have the domainmanager open the link to the agent when the domain manager is started.For a domain manager, select this option to have its agents open links tothe domain manager when they are started.

Auto Link is useful primarily during the startup sequence at thebeginning of each day. At that time, a new production plan is created andcompiled on the master domain manager, and all workstations are stoppedand restarted. For each agent that has Auto Link selected, the domainmanager automatically sends a copy of the new production plan and startsthe agent. If Auto Link is also selected for the domain manager, theagent, in turn, opens a link back to the domain manager. If Auto Link isnot selected for an agent, it is initialized when you run a link action onthe agent’s domain manager or the master domain manager.

Full Status Whether the agent is updated with full or partial status. This is forfault-tolerant agents only. When Full Status is selected, the agent isupdated about the status of jobs and job streams running on all otherworkstations in its domain and subordinate domains.

If Full Status is not selected, the agent is informed only about the statusof jobs and job streams on other workstations that affect its own jobs andjob streams. This can improve performance by reducing network activity.

To keep an agent’s production plan at the same level of detail as itsdomain manager, select Full Status and Resolve Dependencies. Alwaysselect these options for backup domain managers.

Ignore Select this so that the scheduler will ignore this workstation. This can beused to define workstations before they are actually installed.


19.M

anag

ing

Wo

rkstation

s

Table 90. Properties - Workstation in Database Information (continued)In this area ... Enter this information ...

Resolve Dependencies Specify whether an agent will track all dependencies or only its own. Thisis for fault-tolerant agents only. When Resolve Dependencies is selected,the agent tracks dependencies for all jobs and job streams, including thoserunning on other workstations. Note that Full Status must also be selectedso that the agent is informed about activity on other workstations. IfResolve Dependencies is not selected, the agent tracks dependencies forits own jobs and job streams only. This reduces processing overhead.

To keep an agent’s production plan at the same level of detail as itsdomain manager, select Full Status and Resolve Dependencies. Alwaysselect these options for backup domain managers.

Server Specify a Mailman server on the domain manager to handlecommunications with the agent. This is for fault-tolerant and standardagents only. Do not use this option for domain managers. Using serverscan reduce the time required to initialize agents and improve thetimeliness of messages.

To specify a server, select a letter or a number (A-Z and 0-9) from thedrop-down list. The IDs are unique to each domain manager, so you canuse the same IDs in other domains without conflict. If more than 36server IDs are required in a domain, consider dividing it into two or moredomains.

If a server ID is not specified, communications with the agent are handledby the main Mailman process on the domain manager.

When a domain manager starts up, it creates a separate server for eachunique server ID. If the same ID is used for multiple agents, a singleserver is created to handle their communications. As a guide, extra serversshould be defined to prevent a single server from handling more thaneight agents.

Access Method An access method for extended agents and network agents. This must bethe name of a method file that resides in the TWShome/methods directoryon the agent’s host workstation. For a local UNIX extended agent, themethod name is unixlocl. For a remote UNIX extended agent the methodname is unixrsh. For Network agents, the method name is netmth. Formore information about extended agents, refer to the individual extendedagent user’s guides. For more information about network agents, refer tothe Tivoli Workload Scheduler Reference Guide.

Host The name of the agent’s host workstation. This is required for extendedagents. The host is the workstation with which the extended agentcommunicates and where its access method resides. The host for anextended agent must be a Master, Domain Manager, or FTA. The host foran extended agent can be specified as $MASTER. This assigns the host asthe Master Domain Manager, and is useful if you need to switch mastersin the domain. The extended agent will automatically connect to the newmanager.

Note: The host option is no longer required for Standard agents. The host workstation forstandard agents is now defaulted to the domain manager.

254 Version 8.1

When you have finished in the Properties - Workstation in Database window, do one of thefollowing:

¶ 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 WorkstationsTo display a list of workstations in the database:


2. Expand the branches below the scheduler until you see the button for the workstation listyou want to run. For information about creating workstation lists, see “Creating a List ofWorkstations” 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. Thelist results are displayed in the right pane of the Job Scheduling view.

Table 91 describes the column headings in the workstation display.

Table 91. Workstation List Window ColumnsThis column ... Specifies ...

Name The name of the workstation.

Type The type of workstation. This is one of:Fault-tolerant AgentStandard AgentExtended Agent

OS The type of operating system for the workstation. This is one of:

UNIX

Windows NT

MPE/IX

MPE/V

Other

Figure 141. Workstation List Window


19.M

anag

ing

Wo

rkstation

s

Table 91. Workstation List Window Columns (continued)This column ... Specifies ...

Domain The name of the domain in which the workstation is a member.

Time Zone The time zone of the workstation, if one is defined

Creator The name of the user who created the workstation in the database

Last Updated The date the workstation was last updated in the database.

Displaying a WorkstationTo 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 theworkstation and select Properties from the pop-up menu.

This opens the workstation in the Properties - Workstation in Database window. Forinformation about this window, see “Creating a Workstation” on page 251.

3. Click OK or on Cancel to close the window.

Modifying a WorkstationTo 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 theworkstation 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 informationabout 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 windowwithout saving the workstation in the database.

Deleting WorkstationsTo 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 firstand 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, clickeach workstation, then right-click one of the selected workstations.

3. Choose Delete from the pop-up menu. A confirmation message is displayed for eachworkstation.

256 Version 8.1

4. Click OK to delete the workstation in the database or click Cancel to cancel the deleteoperation.

Creating a Workstation by Copying Another WorkstationTo 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 Createanother from the pop-up menu.

This displays a copy of the workstation in the Properties - Workstation in Databasewindow.

3. Change the name in the Workstation name text box to the name of the newworkstation.

4. Make other changes as needed to define the new workstation. For information about theProperties - Workstation in Database window, see “Creating a Workstation” on page 251.


¶ 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.

Managing Workstation ClassesA workstation class is a group of workstations. Any number of workstations can be placed ina class. Job streams and jobs can be assigned to run on a workstation class, makingreplication across many workstations easy.

If a job stream is defined on a workstation class, each job added to the job stream must bedefined either on a single workstation or on the exact same workstation class that the jobstream was defined on.

Creating a Workstation ClassTo create workstation classes in the database, you use the Properties - Workstation Classwindow.

To create a new workstation class:


2. Right-click the scheduler engine button and select New Workstation Class from thepop-up menu. The Properties - Workstation Class General window is displayed


19.M

anag

ing

Wo

rkstation

s

General Page

1. In the Name text box, enter the name of the workstation class. The name must start witha letter and can contain alphanumeric characters, dashes, and underscores. Fornon-expanded databases, it can contain up to eight characters. For expanded databases, itcan contain up to 16 characters.

Note: Workstation class names must be unique and cannot be the same as workstationand domain names.

2. Select Workstations in the left pane of the Properties - Workstation Class window. TheWorkstations page is displayed.

Workstations Page

Table 92. Properties - Workstation Class Workstations PageTo perform this task ... Do this ...

Add individual workstations to theclass

click Find Workstations. For information about using thefind facility, refer to “Finding Objects” on page 199.

Add all of the workstations in thedatabase to the workstation class

click Add All Workstations.

Delete a workstation from theworkstation class

Select the workstation in the Workstation List and clickDelete from Table (X).


Figure 142. Properties - Workstation Class General Page

Figure 143. Properties - Workstation Class Workstations Page

258 Version 8.1

¶ click OK to close the window and save the new workstation class in the database.

¶ click Cancel to close the window without saving the workstation class in the database.

Displaying a List of Workstation ClassesTo 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 workstationclass list you want to run. See “Creating a List of Workstation Classes” on page 193 forinformation 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.

Table 93 describes the of the workstation class list.

Table 93. Workstation Class List WindowThis column ... Specifies ...

Name The name of the workstation class.

Creator The name of the user who created the workstation class in thedatabase.

Last Updated The date the workstation class was last updated in the database.

Displaying a Workstation ClassTo display a workstation class in the database:

1. Run a list of workstation classes that contains the workstation class you want to display.See “Displaying a List of Workstation Classes” for more information.

2. In the list results, double-click the workstation class you want to display or right-clickthe workstation class and select Properties from the pop-up menu.

The Properties - Workstation Class window is displayed. For information about thiswindow, see “Creating a Workstation Class” on page 257.

3. click OK or on Cancel to close the window.

Figure 144. Workstation Class List Window


19.M

anag

ing

Wo

rkstation

s

Modifying a Workstation ClassTo modify a workstation class in the database:

1. Run a list of workstation classes that contains the workstation class you want to modify.See “Displaying a List of Workstation Classes” on page 259 for more information.

2. In the list results, double-click the workstation class you want to modify or right-clickthe workstation class and select Properties from the pop-up menu.

The Properties - Workstation Class window is displayed.

3. Make your changes in the window. For information about the Properties - WorkstationClass window, see “Creating a Workstation Class” on page 257.


¶ click OK to save the workstation class in the database and close the window.

¶ click Cancel to close the window without saving the workstation class in thedatabase.

Deleting Workstation ClassesTo delete workstation classes in the database:

1. Run a list of workstation classes that contains the workstation class you want to delete.See “Displaying a List of Workstation Classes” on page 259 for more information.


¶ To delete one workstation class, right-click the workstation class.

¶ To delete multiple workstation classes in a range, hold down the Shift key, click thefirst and last workstation classes in the range, then right-click one of the selectedworkstation classes.

¶ To delete multiple workstation classes that are not in a range, hold down the Ctrlkey, click each workstation class, then right-click one of the selected workstationclasses.

3. Select Delete from the pop-up menu. A message is displayed for each workstation classasking for confirmation.

4. click OK to delete the workstation class in the database or click Cancel to cancel thedelete operation.

260 Version 8.1

Managing Domains, Users, and Calendars

Managing DomainsA domain is a named group of Workload Scheduler workstations, consisting of one or moreworkstations and a domain manager acting as the management hub. All domains have aparent domain, except for the master domain.

Creating a DomainTo create domains in the database, you use the Properties - Domain window.

To do this, in the tree view of the Job Scheduling Console, right-click the scheduler enginebutton and select New Domain from the pop-up menu. The Properties - Domain window isdisplayed.

Use the information in Table 94 to complete the text boxes.

Table 94. Properties - Domain WindowIn this area ... Enter this information ...

Domain Name The name of the domain. The name must start with a letter and cancontain alphanumeric characters, dashes, and underscores. Fornon-expanded databases, it can contain up to eight characters. Forexpanded databases, it can contain up to 16 characters.Note: Domain names must be unique and cannot be the same asworkstation and workstation class names.

Description A description of the domain.

Parent Domain The name of the parent domain to which the domain manager islinked. The default is the master domain. For information about usingthe Find button, refer to “Finding Objects” on page 199.

Figure 145. Properties - Domain Window

20


20.M

anag

ing

Do

main

s,U

sers,an

dC

alend

ars

Table 94. Properties - Domain Window (continued)In this area ... Enter this information ...

Domain Manager The name of the workstation that is the domain manager. The domainmanager must be a fault-tolerant agent with Full Status and ResolveDependencies selected.Note: When creating a new domain, you can specify a domainmanager workstation that does not yet exist. For information aboutusing the Find button, refer to “Finding Objects” on page 199.


¶ Click OK to close the window and save the new domain in the database.

¶ Click Cancel to close the window without saving the domain in the database.

Displaying a List of DomainsTo display a list of domains in the database:


2. Expand the branches below the scheduler until you see the button for the domain list youwant to run. See “Creating a List of Domains” on page 196 for information aboutcreating domain lists.

3. Select the domain list button.

4. Click Load List in the toolbar or right-click on the domain list button and select LoadList from the pop-up menu.

The list results are displayed in the right pane of the Job Scheduling Console. Thefollowing are descriptions of the column headings.

Table 95 describes the columns of the domain list.

Table 95. Domain List ColumnsThis column ... Specifies ...

Name The name of the domain.

Parent Domain The name of the domain above this domain in the hierarchy.

Domain Manager The name of the workstation that is the manager of this domain.

Creator The name of the user who created the domain in the database.

Last Updated The date the domain was last updated in the database.

Displaying a DomainTo display a domain in the databases:

1. Run a list of domains that contains the domain you want to display. See “Displaying aList of Domains” for more information.

2. In the list results, double-click the domain you want to display or right-click the domainand select Properties from the pop-up menu.

This opens the domain in the Properties - Domain window. For information about thiswindow, see “Creating a Domain” on page 261.


262 Version 8.1

Modifying a Domain in the DatabaseTo modify a domain in the database, follow these steps:

1. Run a list of domains that contains the domain you want to modify. See “Displaying aList of Domains” on page 262 for more information.

2. In the list results, double-click the domain you want to modify or right-click the domainand select Properties from the pop-up menu.

This opens the domain in the Properties - Domain window.

3. Make your changes in the window. For more information, see “Creating a Domain” onpage 261.

4. When you have finished:¶ Click OK to save the domain in the database and close the Properties - Domain

window.¶ Click Cancel to close the Properties - Domain window without saving the domain in

the database.

Deleting Domains in the DatabaseTo delete domains in the database, follow these steps:

1. Run a list of domains that contains the domain you want to delete. See “Displaying aList of Domains” on page 262 for more information.


¶ To delete one domain, right-click the domain.

¶ To delete multiple domains in a range, hold down the Shift key, click the first andlast domains in the range, then right-click on one of the selected domains.

¶ To delete multiple domains that are not in a range, hold down the Ctrl key, clickeach domain, then right-click one of the selected domains.

3. Select Delete from the pop-up menu. A confirmation message is displayed for eachdomain.

4. Click OK to delete the domain in the database or click Cancel to cancel the deleteoperation.

Managing UsersThe users for whom Workload Scheduler will launch jobs must be defined in the database.This is required for Windows NT users only.

Creating a UserTo create users in the database, you use the Properties - NT User window. To do this, in thetree view of the Job Scheduling Console, right-click the scheduler engine button and selectNew User from the pop-up menu. The Properties - NT User window is displayed


20.M

anag

ing

Do

main

s,U

sers,an

dC

alend

ars

Use the information in Table 96 to complete the fields in the window.

Table 96. Properties - NT User WindowIn this area ... Enter this information ...

User Name The Windows NT user name. The name can contain up to 47 characters.

Notes:1. Windows NT user names are case-sensitive.2. A user must be able to log on to the workstation on which Workload

Scheduler will launch jobs, and have the right to Log on as batch.3. If the name is not unique in Windows NT, it is considered to be a

local user, a domain user, or a trusted domain user, in that order.

NT Domain The Windows NT domain of this user. This field is optional. If thename is not fully qualified (that is, no Windows NT domain is entered)or is not unique in Windows NT, it is considered to be a local user, adomain user, or a trusted domain user, in that order.

NT Workstation The name of the Workload Scheduler workstation on which the user isallowed to launch jobs. For information about using the Find button,refer to “Finding Objects” on page 199. The default is all workstations.

Set Password New PasswordA new user password as defined on the Windows NT computer.ConfirmationThe user password again for confirmation.


¶ Click OK to close the window and save the new user in the database.

¶ Click Cancel to close the window without saving the user in the database.

Displaying a List of UsersTo display a list of users in the database, expand the branches below the scheduler until yousee the button for the user list you want to display. Right-click the user list button and selectLoad List from the pop-up menu. The list results are displayed in the right pane of the JobScheduling view.

Figure 146. Properties - NT User Window

264 Version 8.1

Table 97 describes the columns of the window.

Table 97. Users List WindowThis column ... Specifies ...

NT Domain\User The Windows NT domain and the name of the user.

NT Workstation The name of the workstation on which the user will launch jobs.

Displaying a UserTo display a user in the database:

1. Run a list of users that contains the user you want to display. See “Displaying a List ofUsers” 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 andselect Open from the pop-up menu.

This opens the user in the Properties - NT User window. For information about theProperties - NT User window, see “Creating a User” on page 263.


Modifying a UserTo modify a user in the database:

1. Run a list of users that contains the user you want to modify. See “Displaying a List ofUsers” 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 andselect 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.


¶ 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.

Figure 147. Users List Window


20.M

anag

ing

Do

main

s,U

sers,an

dC

alend

ars

Deleting UsersTo delete users in the database:

1. Run a list of users that contains the user you want to delete. See “Displaying a List ofUsers” on page 264 for more information.


¶ To delete one user, right-click the user.

¶ To delete multiple users in a range, hold down the Shift key, click the first and lastusers in the range, then right-click on one of the selected users.

¶ To delete multiple users that are not in a range, hold down the Ctrl key, click eachuser, then right-click one of the selected users.

3. Select Delete from the pop-up menu. A confirmation message is displayed for each user.

4. Click OK to delete the user in the database or click Cancel to cancel the deleteoperation.

Changing User PasswordsTo change a user password:

1. From the main console, click the connector in the left pane.

2. Click Selected from the menu.

3. Click Change Password.

4. Click the search button to specify a name in the User Name text box.

5. Enter the password in the New Password text box.

6. Re-enter the password in the Confirmation text box.

7. Click OK.

Managing CalendarsA calendar is a list of scheduling dates defined in the scheduler database. Assigning acalendar run cycle to a job stream causes that job stream to be run on the days specified inthe calendar. Since a calendar is defined to the scheduler database, it can be assigned tomultiple job streams.

You can create as many calendars as required to meet your scheduling needs. For example:

Table 98. Example CalendarsThis calendar ... Could contain ...

PAYDAYS A list of pay dates

MONTHEND A list of month ending dates

HOLIDAYS A list of your company’s holidays

The Holidays CalendarThe HOLIDAYS calendar is used to determine non-workdays for the purpose of definingrun cycles for your job streams. It also affects the definition of the workdays keyword in thefollowing terms:workdays=everyday except saturday, sunday and all the dates appearing in the HOLIDAYS calendar

266 Version 8.1

You should create a HOLIDAYS calendar with the dates of your holidays.

Freedays CalendarsA freeday must be intended as a non-workday, when no scheduling activity is to take place.Freedays calendars extend the role of the HOLIDAYS calendar, as they provide additionalflexibility in defining workdays. When defining a job stream, if you decide to use a freedayscalendar instead of HOLIDAYS, then the definition of workdays becomes:workdays=everyday except saturday, sunday and all the dates appearing in the specified freedays calendar

If you decide to use your own freedays calendar for a particular job stream, the redefinedmeaning of workdays, as implied by the freedays calendar, is limited to that particular jobstream. A possible scenario is to define more than one freedays calendar to use in yourscheduling activity, particularly in the case your enterprise has different internationallocations, to respond to different non-workdays requirements.

When you do not specify a freedays calendar for the job stream, then HOLIDAYS is used,if available.

Creating a Calendar in the DatabaseTo 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 andselect New Calendar from the pop-up menu. The Properties - Calendar window isdisplayed.

2. In the Name field, specify the name of the calendar. The name must start with a letterand can contain alphanumeric characters, dashes, and underscores. The name cancontain up to eight characters.

Note: You cannot use Workload Scheduler keywords (for example, freedays andschedule).

3. In the Description field, enter a description of the calendar.

4. Click Define Calendar to add dates to the calendar. The Monthly Yearly Calendarwindow is displayed, as shown in the next figure.

Figure 148. Properties - Calendar Window


20.M

anag

ing

Do

main

s,U

sers,an

dC

alend

ars

5. Select Monthly or Yearly in the left pane of the window to view a monthly or yearlycalendar. Use the arrow buttons above and below the calendar to change the month andyear.

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. TheDay of Month window is displayed.

8. To add a day of the month by number, select the day number in the Day drop-downlist. 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 theStart and End drop-down lists. The days you specified are selected for every month inthis range.

10. Click OK to close the Day of Month window and select the dates. Click Cancel toclose the window without selecting the dates.

11. Click OK to close the Monthly Yearly Calendar window and add the dates to thecalendar. 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.

Figure 149. Monthly Yearly Calendar Window

Figure 150. Day of Month Window

268 Version 8.1

Displaying a List of CalendarsTo display a list of calendars in the database:

1. In the tree view of the Job Scheduling Console, expand the scheduler tree until you seethe button for the calendar list you want to run.

2. Right-click the calendar list button and select Load List from the pop-up menu. The listresults are displayed in the right pane of the Job Scheduling Console.

Viewing Calendar PropertiesTo display a calendar in the database:

1. Run a list of calendars that contains the calendar you want to display. See “Displaying aList of Calendars” for more information.

2. Right-click the calendar and select Properties from the pop-up menu.

The Properties - Calendar window is displayed. For information about this window, see“Creating a Calendar in the Database” on page 267.


¶ Click OK to save the calendar in the database and close the window.

¶ Click Cancel to close the window without saving the calendar in the database.

Modifying a Calendar in the DatabaseTo modify a calendar in the database:

1. Run a list of calendars that contains the calendar you want to modify. See “Displaying aList of Calendars” for more information.

2. Right-click the calendar and select Properties from the pop-up menu. The Properties -Calendar window is displayed.

3. Make your changes. For information about this window, see “Creating a Calendar in theDatabase” on page 267.


¶ Click OK to save the calendar in the database and close the window.

¶ Click Cancel to close the window without saving the calendar in the database.

Deleting CalendarsTo delete calendars in the database:

1. Run a list of calendars that contains the calendar you want to delete. See “Displaying aList of Calendars” for more information.


¶ To delete one calendar, right-click the calendar.

¶ To delete multiple calendars in a range, hold down the Shift key, click the first andlast calendars in the range, then right-click on one of the selected calendars.

¶ To delete multiple calendars that are not in a range, hold down the Ctrl key, clickeach calendar, then right-click one of the selected calendars.

3. Select Delete from the pop-up menu. A confirmation message is displayed for eachcalendar.


20.M

anag

ing

Do

main

s,U

sers,an

dC

alend

ars

4. Click OK to delete the calendar in the database or click Cancel to cancel the deleteoperation.

270 Version 8.1

Managing Resources, Prompts, andParameters

Managing ResourcesResources represent any type of resources on your system such as tape drives,communication lines, databases, or printers, that are needed to run a job. Resources can bephysical or logical. After defining a resource in the Workload Scheduler database, it can beused as a dependency for jobs and job streams that run on the workstation or workstationclass for which the resource is defined.

For example, you can define a resource called TAPES with a value of 2 and define jobs thatrequire both tape drives as a dependency. Jobs with this dependency cannot run concurrently,because each time a job is run the TAPES resource is in use.

Creating a ResourceTo create resources in the database, you use the Properties - Resource in Databasewindow.

To create a new resource:


2. Click the New Resource button in the toolbar or right-click the scheduler button andselect New Resource from the pop-up menu. The Properties - Resource in Databasewindow is displayed.

Use the information in Table 99 to complete the window.

Table 99. Properties - Resource in Database Window InformationIn this area ... Enter this information ...

Name The name of the resource. The name must start with a letter and cancontain alphanumeric characters, dashes, and underscores. The namecan contain up to eight characters.

Figure 151. Properties - Resource in Database Window

21


21.M

anag

ing

Reso

urces,

Pro

mp

ts,an

dP

arameters

Table 99. Properties - Resource in Database Window Information (continued)In this area ... Enter this information ...

Description A description of the resource.

Quantity The number of available resource units. Values can be 0 through1024.

Workstation Specify the name of the workstation or workstation class on whichthe resource is used. You can type a name directly or you can clickFind and select a workstation or workstation class from a list. Forinformation about using the Find button, refer to “Finding Objects”on page 199.


¶ Click OK to close the window and save the new resource in the database.

¶ Click Cancel to close the window without saving the resource in the database.

Displaying a List of ResourcesTo display a list of resources in the database:


2. Expand the branches below the scheduler until you see the button for the resource listyou want to run. See “Creating a List of Resources” on page 193 for information aboutcreating resource lists.

3. Right-click the resource list button and select Load List from the pop-up menu. The listresults are displayed in the right pane of the Job Scheduling Console.

4. In the Workstation field, enter the name of the workstation or workstation class onwhich 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 ResourceTo display a resource in the database:

Figure 152. Resource List Window

272 Version 8.1

1. Run a list of resources that contains the resource you want to display. See “Displaying aList of Resources” on page 272 for more information.

2. In the list results, double-click the resource you want to display or right-click theresource and select Properties from the pop-up menu.

This opens the resource in the Properties - Resource In Database window. Forinformation about this window, see “Creating a Resource” on page 271.


Modifying a ResourceTo modify a resource in the database:

1. Run a list of resources that contains the resource you want to modify. See “Displaying aList of Resources” on page 272 for more information.

2. In the list results, double-click the resource you want to modify or right-click theresource and select Open from the pop-up menu.

This opens the resource in the Properties - Resource In Database window.

3. Make your changes. For information about this window, see “Creating a Resource” onpage 271.

4. When you have finished:¶ Click OK to save the resource in the database and close the window.¶ Click Cancel to close the window without saving the resource in the database.

Deleting ResourcesTo delete resources in the database:

1. Run a list of resources that contains the resource you want to delete. See “Displaying aList of Resources” on page 272 for more information.


¶ To delete one resource, right-click the resource.

¶ To delete multiple resources in a range, hold down the Shift key, click the first andlast resources in the range, then right-click on one of the selected resources.

¶ To delete multiple resources that are not in a range, hold down the Ctrl key, clickeach resource, then right-click one of the selected resources.

3. Select the Delete command from the pop-up menu. A confirmation message is displayedfor each resource.

4. Click OK to delete the resource in the database or click Cancel to cancel the deleteoperation.

Creating a Resource by Copying Another ResourceTo create a new resource in the database using a copy of another resource:

1. Run a list of resources that contains the resource you want to copy. See “Displaying aList of Resources” on page 272 for more information.

2. In the list results, right-click the resource you want to copy and select Create anotherfrom the pop-up menu.

This displays a copy of the resource in the Properties - Resource In Database window.

3. In the Name text box, change the name to the name of the new resource.


21.M

anag

ing

Reso

urces,

Pro

mp

ts,an

dP

arameters

4. Change the other text boxes as needed to define the new resource. For information aboutthis window, see “Creating a Resource” on page 271.

5. When you have finished:¶ Click OK to save the resource in the database and close the window.¶ Click Cancel to close the Properties - Resource In Database window without saving

the resource in the database.

Managing Prompts in the DatabasePrompts can be used as dependencies for jobs and job streams. A prompt must be answeredaffirmatively for the dependent job or job stream to launch. For example, you can issue aprompt to make sure that a printer is online before a job that prints a report runs.

There are two types of prompt:

Ad hoc promptThis is defined within the properties of a job or job stream and is unique to that jobor job stream.

Predefined promptThis is defined in the Workload Scheduler database and can be used by any job orjob stream.

Creating a PromptTo create prompts in the database, you use the Properties - Prompt window.

To create a new prompt:

1. In the tree view of the Job Scheduling Console, right-click the scheduler button andselect New Prompt from the pop-up menu. The Properties - Prompt window isdisplayed.

2. In the Name field, enter the name of the prompt. The name must start with a letter andcan contain alphanumeric characters, dashes, and underscores. The name can contain upto 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 thestring begins with a colon (:), the message is displayed but no reply is necessary. If thestring begins with an exclamation mark (!), the message is not displayed but it requires areply. 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.

Figure 153. Properties - Prompt Window

274 Version 8.1

Displaying a List of PromptsTo display a list of prompts in the database:

1. In the tree view of the Job Scheduling Console, expand the scheduler tree.

2. Right-click the prompt list button and select Load List from the pop-up menu. The listresults are displayed in the right pane of the Job Scheduling Console.

The Name and Text columns specify the name and text content of the prompts.

Displaying a PromptTo display a prompt in the database:

1. Run a list of prompts that contains the prompt you want to display. See “Displaying aList of Prompts” for more information.

2. In the list results, double-click the prompt you want to display or right-click the promptand select Open from the pop-up menu.

This opens the prompt in the Properties - Prompt window. For information about thiswindow, see “Creating a Prompt” on page 274.


Modifying a Prompt in the DatabaseTo modify a prompt in the database:

1. Run a list of prompts that contains the prompt you want to modify. See “Displaying aList of Prompts” for more information.

2. In the list results, double-click the prompt you want to modify or right-click the promptand 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” onpage 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.

Figure 154. Prompts List Window


21.M

anag

ing

Reso

urces,

Pro

mp

ts,an

dP

arameters

Deleting PromptsTo delete prompts in the database:

1. Run a list of prompts that contains the prompt you want to delete. See “Displaying a Listof Prompts” on page 275 for more information.


¶ To delete one prompt, right-click the prompt.

¶ To delete multiple prompts in a range, hold down the Shift key, click the first andlast prompts in the range, then right-click on one of the selected prompts.

¶ To delete multiple prompts that are not in a range, hold down the Ctrl key, clickeach prompt, then right-click one of the selected prompts.

3. Select Delete from the pop-up menu. A confirmation message is displayed for eachprompt.

4. Click OK to delete the prompt in the database or click Cancel to cancel the deleteoperation.

Managing ParametersParameters are useful to substitute values into your jobs and job streams. Since parametersare stored in the Workload Scheduler database, all jobs and job streams that use theparticular parameter are updated automatically when the value changes. For scheduling, aparameter 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, theparameter must be defined on the workstation where it will be used. Parameters cannot beused when scripting Extended Agent jobs.

Note: Be careful when renaming a parameter because it might be part of a dependency for ajob scheduler object in the database. If this is the case, and you rename it, any actionyou perform that refers to the old name will return an error.

Creating a ParameterTo create parameters in the database , you use the Properties - Parameter window.

To create a new parameter:

1. In the Job scheduling Console, right-click the scheduler engine button and select NewParameter from the pop-up menu. The Properties - Parameter window is displayed.

2.

276 Version 8.1

3. In the Name field, enter the name of the parameter. The name must start with a letterand can contain alphanumeric characters, dashes, and underscores. The name can containup to eight characters.

4. In the Value field, enter the value assigned to the parameter. Do not include the namesof other parameters.

5.


¶ Click OK to close the window and save the new parameter in the database.

¶ Click Cancel to close the window without saving the parameter in the database.

Displaying a List of ParametersTo display a list of parameters in the database:

1. In the tree view of the Job Scheduling Console, expand the scheduler tree.

2. Right-click the parameter list button and select Load List from the pop-up menu. Thelist results are displayed in the right pane of the Job Scheduling Console.

The Name and Value columns show the names and values of the parameters.

Displaying a ParameterTo display a parameter in the database, follow these steps:

1. Run a list of parameters that contains the parameter you want to display. See “Displayinga List of Parameters” for more information.

2. In the list results, double-click the parameter you want to display or right-click theparameter and select Open from the pop-up menu.

Figure 155. Properties - Parameter Window

Figure 156. Parameter List Window


21.M

anag

ing

Reso

urces,

Pro

mp

ts,an

dP

arameters

This opens the parameter in the Properties - Parameter window. For information aboutthis window, see “Creating a Parameter” on page 276.


Modifying a Parameter in the DatabaseTo modify a parameter in the database:

1. Run a list of parameters that contains the parameter you want to modify. See “Displayinga List of Parameters” on page 277 for more information.

2. In the list results, double-click the parameter you want to modify or right-click theparameter and select Open from the pop-up menu.

This opens the parameter in the Properties - Parameter window.

3. Make your changes. For information about this window, see “Creating a Parameter” onpage 276.

4. When you have finished:¶ Click OK to save the parameter in the database and close the window.¶ Click Cancel to close the window without saving the parameter in the database.

Deleting ParametersTo delete parameters in the database:

1. Run a list of parameters that contains the parameter you want to delete. See “Displayinga List of Parameters” on page 277 for more information.


¶ To delete one parameter, right-click the parameter.

¶ To delete multiple parameters in a range, hold down the Shift key, click the first andlast parameters in the range, then right-click one of the selected parameters.

¶ To delete multiple parameters that are not in a range, hold down the Ctrl key, clickeach parameter, then right-click one of the selected parameters.

3. Choose Delete from the pop-up menu. A confirmation message is displayed for eachparameter.

4. Click OK to delete the parameter in the database or click Cancel to cancel the deleteoperation.

278 Version 8.1

Plan Tasks

Using Plan ListsPlan lists display objects in the Workload Scheduler plan. When you create a list, you give ita name and specify filtering criteria. When you run a list, it displays a filtered list of objectsin the plan. Each list you create is represented by an button in the tree view of the JobScheduling Console.

You can create groups to organize your lists. After installation there are a default set of basicplan lists in a group named Default Plan Lists.

Creating a Group for Plan ListsTo 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 buttonand select Create Group from the pop-up menu.

To create a group in an existing group, select the group and click Create a Group ofLists in the toolbar or right-click the existing group button and select Create Groupfrom the pop-up menu.


4. In the Name field, enter the name of the list group. The name can contain up to 40characters, starting with a letter.

5. Click OK to close the window and save the new group.

Creating a Plan List of WorkstationsTo create a plan list that displays workstations:




22


22.P

lanTasks

3. Click List Workstations in Plan in the toolbar or right-click the scheduler engine buttonor group button and select Create Plan List , then Workstation from the pop-up menu.The Properties - Plan Workstation List window is displayed.

4. In the Name field, enter a name for the list.

5. To have the list results refreshed automatically, select Periodic Refresh and specify arefresh interval in seconds in the Period (secs) text box.

6. To filter the list results, specify a workstation name in the Workstation Name text boxand a scheduler domain name in the Domain Name text box. The workstation anddomain names can contain wildcard characters. Leaving the text box blank results in anunfiltered list.


¶ Click OK to save the list and close the window. The list button is added to the groupyou selected.


Creating a Plan List of Domain StatusTo create a plan list to display domains:



3. Right-click the scheduler engine button or group button and select Create Plan List,then Domain Statusfrom the pop-up menu.

The Properties - Domain Status List window is displayed.

4. In the Name field, enter a name for the list

Figure 158. Properties - Plan Workstation List Window

Figure 159. Properties - Domains Status List Window

280 Version 8.1

5. If you want the list results refreshed automatically, select Periodic Refresh and specify arefresh interval in seconds in the Period (secs) text box.

6. To filter the list results, specify a domain name in the Domain Name text box. Thedomain name can contain wildcard characters. Leaving the text box blank results in anunfiltered list.




Creating a Plan List of Job Stream InstancesTo create a plan list of job stream instances:



3. Click List Job Stream Instances in the toolbar or right-click the scheduler button andselect Create Plan List, then Job Stream Instance from the pop-up menu.

The Properties - Job Stream Instance List General page is displayed.

General Page

Use the information in Table 100 to create the list and filter the results.

Table 100. Properties - Job Stream Instance List General InformationIn this area ... Enter this information ...

Name A name for the list.

Figure 160. Properties - Job Stream Instance List General Page


22.P

lanTasks

Table 100. Properties - Job Stream Instance List General Information (continued)In this area ... Enter this information ...

Period Refresh Options Select the Periodic Refresh check box if you want the list resultsrefreshed automatically and specify a refresh interval in seconds in thePeriod (secs) text box.

Filter Criteria Job StreamSpecify a job stream name.

Workstation NameSpecify a workstation name.

StatusTo use the Job Scheduling Console status to filter job streaminstances, select this option and select the status type from thedrop-down list.

Internal StatusTo use Workload Scheduler internal status to filter job streaminstances, select this option and select the status type from thedrop-down list.

PriorityUse the From and To text boxes to specify a priority range ofjob streams to display. Only job streams with priorities within therange are displayed. Possible priority values are 0 through 101,where 101 is the highest priority. Click Hold to select priority 0,High to select priority 100, or Go to select priority 101.



Figure 161. Properties - Job Stream Instance List Time Restrictions Page

282 Version 8.1

Use the information in Table 101 to complete this window.

Table 101. Properties - Job Stream Instance List Time Restrictions InformationIn this area ... Enter this information ...

Start Time A range for the start date and time of the job stream instances youwant to display.From Date

Use the Date and Time text boxes to specify the beginning ofa range of time. Only job streams that start running within thisrange are displayed.

To DateUse the Date and Time text boxes to specify the end of arange of time. Only job streams that start running within thisrange are displayed.

Finish Time Specify a range for the finish date and time of the job streaminstances you want to display.From Date

Use the Date and Time text boxes to specify the beginning ofa range of time. Only job streams that finish running withinthis range are displayed.

To DateUse the Date and Time text boxes to specify the end of arange of time. Only job streams that finish running within thisrange are displayed.

Select Dependencies in the left pane. The Dependencies page is displayed.

Dependencies Page

Figure 162. Properties - Job Stream Instance List Dependencies Page


22.P

lanTasks

Use this window to define a list of jobs from the plan based on dependency types. Only jobstream instances with the specified dependencies are displayed. Note that all the fields inthis window act as filters, so that all fields specified must be valid for a job stream to bechosen for display.

For example, to display all job streams with a file dependency, enter an asterisk (*) in theFile Dependency / File Name field.

To display all job streams with both a file and a prompt dependency, enter an asterisk (*) inthe File Dependency / File Name field and in the Prompt Dependency / Prompt Namefield.

Note: In this case, only job streams with both a file and a prompt dependency aredisplayed. Job Streams with only prompt dependencies or only file dependencies arenot displayed.

Use the information in Table 102 to define the list of jobs from the plan.

Table 102. Properties - Job Stream Instance List Dependency InformationIn 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.




Creating a Plan List of Job InstancesTo create a plan list to display job instances:



3. Click the List Job Instances button on the toolbar. Alternatively, you can right-click thescheduler engine button or group button and select Create Plan List, then Job Instancefrom the pop-up menu.

The Properties - Job Instance List General page is displayed.

284 Version 8.1

General Page

Use the information in Table 103 to create the list and filter the results.

Table 103. Properties - Job Instance List General InformationIn this area ... Enter this information ...


Period Refresh Options Select the Periodic Refresh check box if you want the list resultsrefreshed automatically and specify a refresh interval in seconds in thePeriod (secs) text box.

Figure 163. Properties - Job Instance List General Page


22.P

lanTasks

Table 103. Properties - Job Instance List General Information (continued)In this area ... Enter this information ...

Filter Criteria Job NameSpecify a job name.

Job StreamSpecify a job stream.

Workstation (Job Stream)Specify a workstation name.

LoginSpecify a login name.

StatusTo use Job Scheduling Console status to filter job instances,select this option and select the status type from the drop-downlist.

Internal StatusTo use Workload Scheduler internal status to filter job instances,select this option and select the status type from the drop-downlist.

Recovery OptionsSelect a job recovery option using the option buttons. Validoptions are Stop, Continue, Rerun, and None.

PriorityUse the From and To text boxes to specify a priority range ofjob instances to display. Only jobs with priorities within therange are displayed. Possible priority values are 0 through 101,where 101 is the highest priority. Click Hold to select priority 0,High to select priority 100, or Go to select priority 101.

Select Time Restrictions in the left pane. The Restrictions page is displayed.

286 Version 8.1



Table 104. Properties - Job Instance List Time Restrictions InformationIn this area ... Enter this information ...

Start Time A range for the start date and time of the job instances you want todisplay.From Date

Use the Date and Time text boxes to specify the beginning of arange of time. Only jobs that start running within this range aredisplayed.

To DateUse the Date and Time text boxes to specify the end of a rangeof time. Only jobs that start running within this range aredisplayed.

Finish Time Specify a range for the finish date and time of the job instances youwant to display.From Date

Use the Date and Time text boxes to specify the beginning ofa range of time. Only jobs that finish running within this rangeare displayed.

To DateUse the Date and Time text boxes to specify the end of arange of time. Only job streams that finish running within thisrange are displayed.

Select Dependencies in the left pane. The Dependencies page is displayed.

Figure 164. Properties - Job Instance List Time Restrictions Page


22.P

lanTasks

Dependencies Page

Use this window to define a list of jobs from the plan based on dependency types. Only jobinstances with the specified dependencies are displayed. Note that all the fields in thiswindow act as filters, so that all fields specified must be valid for a job stream to be chosenfor display.

For example, to display all jobs with a file dependency, enter an asterisk (*) in the FileDependency / File Name field.

To display all jobs with both a file and a prompt dependency, enter an asterisk (*) in theFile 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. Jobinstances 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 InformationIn 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.

Figure 165. Properties - Job Instance List Dependencies Window

288 Version 8.1

Table 105. Properties - Job Instance List Dependency Information (continued)In this area ... Enter this information ...

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.




Creating a Plan List of ResourcesTo create a plan list to display resources:



3. Click List Resources in Plan on the toolbar. Alternatively, you can right-click thescheduler engine button or group button and select Create Plan List, then Resourcefrom the pop-up menu. The Properties - Plan Resource List window is displayed.


Table 106. Properties - Plan Resource List InformationIn this area ... Enter this information ...


Periodic Refresh Options Select Periodic Refresh if you want the list results refreshedautomatically and specify a refresh interval in seconds in the Period(secs) field.

Filter Criteria In the Resource Name field, specify a resource name.In the Workstation Name field, specify a workstation name.

The resource name and workstation name can contain wildcardcharacters. Leaving the text box blank results in an unfiltered list.

Figure 166. Properties - Plan Resource List Window


22.P

lanTasks




Creating a Plan List of PromptsTo create a plan list to display prompts:



3. Right-click the scheduler engine button or group button and select Create Plan List,then Prompt Status from the pop-up menu. The Properties - Prompt Status List windowis displayed.


Table 107. Properties - Prompt Status List InformationIn this area ... Enter this information ...


Periodic Refresh Options Select Periodic Refresh if you want the list results refreshedautomatically and specify a refresh interval in seconds in the Period(secs) field.

Figure 167. Properties - Prompt Status List Window

290 Version 8.1

Table 107. Properties - Prompt Status List Information (continued)In this area ... Enter this information ...

Filter Criteria Prompt NameTo filter the list results, specify a prompt name in the PromptName field. The prompt name can contain wildcard characters.Leaving the text box blank results in an unfiltered list

StatusTo filter the list using prompt status, use the Status check boxes toselect the status values. The status values are:Asked

The prompt has been asked, but not answered.Not Asked

The prompt has not been asked.Answered Yes

The prompt has been answered with a “yes” response.Answered No

The prompt has been answered with a “no” response.If no status values are selected, prompts with all status values aredisplayed.




Creating a Plan List of FilesTo create a plan list to display files:



3. Right-click the scheduler engine button or group button and select Create Plan List,then File Status from the pop-up menu. The Properties - File Status List window isdisplayed.

4. Type a name for the list in the Name field.


Figure 168. Properties - File Status List window.


22.P

lanTasks

6. To filter the list results, enter a file name in the Filename field and a workstation namein the Workstation Name field. The file name and workstation name can containwildcards. Leaving the field blank results in an unfiltered list.




Modifying the Properties of a Plan ListTo modify the properties of a plan list:


2. Select the list button you want to modify.

3. Right-click the list button and select Properties from the pop-up menu. This displays theproperties window for the list.

4. Make your modification in the properties window.




Deleting a Plan ListTo delete a plan list:


2. Select the list button you want to delete.

3. Right-click the list button and select Delete from the pop-up menu. In the confirmationwindow, click Yes to delete the list or Cancel to cancel the delete operation.

Detaching a Plan List DisplayDetaching a list frees the right-window of the Job Scheduling Console to display otherobjects. You can detach multiple lists to display several objects simultaneously. In WorkloadScheduler you can have up to seven detached windows at a time.

To detach a plan list display:


2. Select the list button you want to view in a detached window.

3. Right-click the list button and select Detach View from the pop-up menu. This displaysthe separate window for the list display.

292 Version 8.1

Finding Objects in the PlanFind tools are provided in the Job Scheduling Console to help you find objects in the plan.The availability of the Find tool is shown by an ellipsis (...) located next to the text boxwhere you type an object name. In the following example of the Submit Job into Planwindow, the Job Name field provides a Find button (...).

Clicking on the ellipsis opens a Find window.

To use the Find window:

1. Type a search character string in the available fields. The search character string cancontain wildcard characters. Leaving the text box blank results in an unfiltered list.

2. Select other filter criteria using option buttons and check boxes.

3. Click Start. The results of the search are listed in the lower part of the Find window.The Stop button is displayed while the list is being generated. Selecting Stop stops thesearch. Any objects that have been found by the system until the Stop is clicked aredisplayed.

4. Select an object in the list and do one of the following:¶ Click Apply button to insert the name of the object in the text box on the parent

window. The Find window remains open to let you to select other objects from thelist.

¶ Double-click the object in the list or click OK to insert the name of the object in thefield in the parent window and close the Find window.

Figure 169. Example of a Find Button

Figure 170. Example Find Window


22.P

lanTasks

Managing Job Instances in the PlanA job is a unit of work that is part of a job stream processed at a workstation. A job usuallyrefers to a command or script file. Job definitions in Workload Scheduler include allnecessary workstation and path locations, command names, file names, login IDs, userpermissions, priority levels, and recovery options necessary to successfully run a commandor script file with no manual intervention.

Table 108 shows the commands that you can issue against a job instance in the plan.

Table 108. Job Instance CommandsUse 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 restrictionson 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 theJob Schedule Console status to HELD.

Release Counteracts the Hold command. The Release command reverts a jobinstance 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.

Displaying a List of Jobs in the PlanTo display a list of jobs in the plan:

1. In the Job Scheduling view, expand the scheduler button.

2. Expand the branches below the scheduler until you see the button for the job instancelist you want to run.

3. Right-click the job instance list button and select Load List from the pop-up menu. Thelist results are displayed in the right pane of the Job Scheduling Console.

The toolbar in the job instance view contains two special buttons.

This button ... Is called ... And does this ...

Go toMoves the timeline display to the date you select on thepopup calendar.

Go to FirstMoves the timeline display to the start time and dayoffset of the earliest job instance.

List View of Job InstancesThe List view provides a tabular display of job instances.

294 Version 8.1

Table 109 describes the column headings in the table part of the List view.

Table 109. Job Instance List View ColumnsThis 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 anincremental number from the value found in the file nxtjobno inTWShome.

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 moreinformation on job or job stream status refer to “Status Description andMapping” on page 387.

Internal Status The Workload Scheduler internal status of the job instance. For moreinformation on job or job stream status refer to “Status Description andMapping” 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. Apriority 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 tostart 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 beginrunning.

Job Stream Dep. The number of job stream dependencies for each job instance.

Job Dep. The number of job dependencies for each job instance.

Figure 171. Job Instance List View Window


22.P

lanTasks

Table 109. Job Instance List View Columns (continued)This column ... Specifies ...

Inet Dep. The number of internetwork predecessors to this job.

File Dep. The number of file dependencies for each job instance.

Prompt Dep. The number of prompt dependencies for each job instance.

Resource Dep. The number of resource dependencies for each job instance.

Timeline View of Job InstancesThe Timeline view provides a table and a timeline display of job instances. Use the bordersand the arrows on the borders to adjust the sizes of the windows. Use the arrows at the topof the timeline window to move the view in one hour and one day increments.

In the timeline window, the dark blue line represents the window of time a job instance canstart. 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 withinthe dark blue line represents the actual duration of the job instance. The start time, deadlinetime, 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 ColumnsThis column ... Specifies ...

Name The name of the job instance.

Status The status of the job instance. For more information on job or jobstream 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.

Figure 172. Job Instance List: Timeline View window.

296 Version 8.1

Modifying the Properties of a Job InstanceTo display the properties of a job instance in the plan:

1. Right-click the job instance list button and select Load List from the pop-up menu. Thelist results are displayed in the right pane of the Job Scheduling Console.

2. In the list results, right-click a job instance and select Properties from the pop-up menu.In this particular example, the job is a Windows NT script. The window that is displayedis therefore the Properties - Job NT Script window, showing the General page.

General Page


Table 111. Properties - NT Script Instance General InformationThis area ... Specifies ...

Job Name The name of the job instance.

Job Number The number of times this job instance has been run in the productionplan.

Workstation (Job) The name of the workstation on which the job instance is launched.

Job Stream The name of the job stream this job instance belongs to.

Workstation (Job Stream) The name of the workstation on which the job stream instance islaunched.

Login The user ID of the person running the job instance.

Priority The priority of the job instance. To change the priority, select a valuefrom the drop-down list or click Hold to select priority 0, High toselect priority 100, or Go to select priority 101. Possible priority valuesare 0 through 101, where 101 is the highest priority. A priority value ofzero prevents the job instance from launching.

Figure 173. Properties - NT Script Instance General Page


22.P

lanTasks

Table 111. Properties - NT Script Instance General Information (continued)This area ... Specifies ...

Status The Job Scheduling Console status of the job instance. For moreinformation on job or job stream status refer to “Status Description andMapping” on page 387.

Internal Status The Workload Scheduler internal status of the job instance. For moreinformation on job or job stream status refer to “Status Description andMapping” on page 387.

Information Additional information about the job instance.

Rerun Status Whether this job instance has been rerun.

Is Interactive Whether this job instance is an interactive job. This information appearsonly for Windows NT jobs.

Requires Confirmation This job instance will not be run in the plan until user intervention isused to submit it.

Actuals The actual start time and duration of the job instance, if it hascompleted running.Start Time

The actual start time of the job instance.Duration

The actual duration of the job instance.

Recovery Options These fields display any automatic recovery action to be taken if the jobinstance ends with a status of ABEND.Stop, Continue, or Rerun

Specifies what action to take if this job instance ends with a statusof ABEND (the job instance ends with an error).

Job NameSpecifies the name of an error recovery job that will run if thecurrent job instance ends with a status of ABEND.

WorkstationSpecifies the name of the workstation that owns the recovery job.

MessageSpecifies the message text that displays if the job instance endswith a status of ABEND.

Select Task in the left pane of the Properties - NT Script Instance window. The Task page isdisplayed.

298 Version 8.1

Task Page


Note: The fields in this window change according to the type of job instance displayed.

Table 112. Properties - NT Script Instance Task InformationThis 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.

Figure 174. Properties - NT Script Instance Task Page


22.P

lanTasks

Table 112. Properties - NT Script Instance Task Information (continued)This area ... Specifies ...

Workstation Class Script Displays information about the Workstation Class script file:Script Displays the path and filename of the Workstation

Class script.

Workstation ClassCommand

Displays information about the Workstation Class command:Script Displays the path and filename of the Workstation

Class command.

SAP Job Displays information about the SAP task:R/3 Job Identity

Use these fields to identify the R/3 job.Job Name The R/3 job name.Job ID This field is filled in when you submit the job to the

R/3 system.Disable BDC Wait

Indicates if BDC Wait option for the job is disabledDebug Options Indicates if additional debut information is included in

the job’s stdlist file.Trace Indicates if a trace file dev_rfc is created in the

Workload Scheduler home directory.

Select Time Restrictions in the left pane of the Properties - Job Instance window. The TimeRestrictions page is displayed.


Figure 175. Properties - NT Script Instance Time Restrictions Page

300 Version 8.1


Table 113. Properties - NT Script Instance Time Restrictions InformationThis area ... Specifies ...

Start The earliest time the job instance will be launched. The job instancewill not be launched before this time. To change the time, make yourselections as follows:Specify date and time

Select this option so you can specify a start date and a starttime.

Date Enter the start date or click the calendar button and select adate from the drop-down calendar.

Time Enter a start time in the following format:

hh:mm am|pm

For example, 11:30 am or 4:25 pm.

Deadline Specifies the latest time the job instance will be launched. The jobinstance will not be launched after this time. To change the time,make your selections as follows:Specify date and time

Select this option so you can specify a deadline date andtime.

Date Specify the deadline date or click the calendar button andselect a date from the drop-down calendar.

Time Specify a deadline time in the following format:

hh:mm am|pm


Time Zone Select a time zone from the drop-down list. The start time anddeadline time are in this time zone. If a time zone is not specified forthe job instance, all time values are in the time zone of theworkstation on which the job instance is launched. Note that the timezone option must be activated in the global options file for this fieldto be active.

Repeat Range Specifies the repeat rate of a job instance. Using the Repeat Rangefield with the Start and Deadline times allows you to run a jobinstance, for example, every 15 minutes from 1:00 pm to 5:00 pm.Hours Enter the rate in hours that this job instance will

repeat.Minutes Enter the rate in minutes that this job instance will

repeat.

Select Files in the left pane of the Properties - Job Instance window. The Files page isdisplayed.


22.P

lanTasks

Files Page


Table 114. Properties - NT Script Instance Files InformationThis column ... Specifies ...

Filename The path and name of the file.

Workstation The workstation on which the file resides.

Release Status The status of the file dependency. The possible values are:Not Released

The job instance is not released from the file dependency.Released

The job instance is released from the file dependency.To release the job instance from the file dependency, click in theStatus column and select Released from the drop-down menu.

Qualifiers The test conditions for the file dependency.

Internal Status The internal status of the file dependency. The possible values are:Not Checked

The file dependency has not been checked.Checking

The file dependency is being checked.Exists

The file dependency is satisfied.Does Not Exist

The file dependency is not satisfied.

To add a file dependency for the job instance:

1. Click the Add Row (+) button. This creates a new row in the list of file dependencies.

Figure 176. Properties - NT Script Instance Files Page

302 Version 8.1

2. Double-click the text box in the Filename column and type in a file name.

3. Double-click the text box in the Workstation column and click the ellipsis (...) to locateand insert the name of the workstation on which the file exists or will be created.

4. Double-click the text box in the Qualifiers column and specify the test conditions forthe file dependency. On UNIX, the valid qualifiers are the same as UNIX test commandconditions. For more information, refer to your UNIX system documentation.






-s %p True if the file exists and its size is greater than zero.


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 defaultis -f %p.

To remove a file dependency for the job instance, select the file row in the list and click theDelete from Table (X) button.

Select Prompts in the left pane of the Properties - NT Script Instance window. The Promptspage is displayed.


22.P

lanTasks

Prompts Page

To display ad hoc prompt dependencies, select Ad Hoc Prompt from the drop-down list inthe toolbar.

To display predefined prompt dependencies, select Predefined Prompt from the drop-downlist in the toolbar.


Table 115. Properties - NT Script Instance Prompts InformationThis column ... Specifies ...

Name The name of the prompt. Used for predefined prompts only.

Message Text The text of the prompt message.

Workstation The workstation that displays the prompt message text. For ad hocprompts only.

Number The number of the prompt dependency.

Release Status The release status of the prompt dependency. The possible values are:Not Released

The job instance is not released from the prompt dependency.Released

The job instance is released from the prompt dependency.To release the job instance from the prompt dependency, click in theStatus column and select Released from the drop-down menu.

Figure 177. Properties - NT Script Instance Prompts Page

304 Version 8.1

Table 115. Properties - NT Script Instance Prompts Information (continued)This column ... Specifies ...

Internal Status The internal status of the prompt dependency. The possible values are:Not Asked

The prompt has not been asked.Asked

The prompt has been asked, but no response has been received.Answered Yes

The prompt has been answered affirmatively and the job instancedependency is released.

Answered NoThe prompt has been answered negatively and the job instancedependency is not released.

Reply The reply to the prompt dependency. To reply to the prompt, click inthis column and select Yes or No from the drop-down menu.

To add a prompt dependency for the job instance:

1. Click the Add Row (+) button. This creates a new row in the list of promptdependencies.

2. For a predefined prompt, double-click the text box in the Name column and click theellipsis (...) to locate and insert the name of a prompt.

3. For an ad hoc prompt, double-click in the text box in the Message Text column and typein the text of the prompt.

The default behavior of a prompt is to display a message and wait for a reply. If thestring begins with a colon (:), the message is displayed but no reply is necessary. If thestring begins with an exclamation mark (!), the message is not displayed but it requires areply.

You can include backslash n (\n) within the text for new lines. You can also include oneor more Workload Scheduler parameters as part or all of the text string. To use aparameter, place its name between carets (^).

To remove a prompt dependency for the job instance, select the prompt row in the list andclick the Delete from Table (X) button.

Select Resources in the left pane of the Properties - NT Script Instance window. TheResources page is displayed.


22.P

lanTasks

Resources Page


Table 116. Properties - NT Script Instance Resources InformationThis column ... Specifies ...

Resource The name of the resource.

Workstation The workstation on which the resource resides.

Quantity The number of units of a resource are needed by the job instance tosatisfy the dependency.

Available The number of units of the resource that are currently available.

Release Status The status of the resource dependency. The possible values are:Not Released

The job instance is not released from the resource dependency.Released

The job instance is released from the resource dependency.To release the job instance from the resource dependency, click in theStatus column and select Released from the drop-down menu.

To add a resource dependency for the job instance:

1. Click the Add Row (+) button. This creates a new row in the list of resourcedependencies.

2. In the Workstation column, click the ellipsis (...) to locate and insert the name of aworkstation.

3. Double-click in the text box in the Resource column and click Find to locate and inserta resource name.

Figure 178. Properties - NT Script Instance Resources Page

306 Version 8.1

4. Double-click in the text box in the Quantity column and specify the number of resourceunits required by the job instance. The default is one.

To delete a resource dependency for the job instance, select the resource row in the list andclick the Delete from Table button.


¶ Click Apply to save the changes you made to the properties and leave the window open.

¶ Click OK to save the changes you made to the properties and close the window.

¶ Click Cancel to ignore any changes you made to the properties and close the window.

Displaying Dependencies of a Job InstanceTo display the dependencies of a job instance, in a list, right-click the job instance you wantto display and select Dependencies from the pop-up menu. The Dependencies - Job Instancewindow is displayed.

You can display three types of dependency:¶ Predecessors¶ Internetwork predecessors¶ Successors

Predecessors PageTable 117 describes the columns in the Predecessors page.

Table 117. Predecessors PageThis column ... Specifies ...

Job Stream The name of a predecessor job stream instance or the job stream thatowns the predecessor job.

Job The name of a predecessor job instance.

Workstation The workstation of the predecessor job or job stream.

Figure 179. Dependencies - NT Script Instance Successors Page


22.P

lanTasks

Table 117. Predecessors Page (continued)This column ... Specifies ...

Release Status The status of the predecessor dependency. The possible values are:Released

The job instance is released from the predecessor dependency.Not Released

The job instance is not released from the predecessor dependency.To release the job instance from the predecessor dependency, click inthe Status column and select Released from the drop-down menu.

Internal Status The Workload Scheduler internal status of the predecessor job or jobstream instance. For more information about job or job stream status,see “Status Description and Mapping” on page 387.

Internetwork Predecessors PageTable 118 describes the columns in the Internetwork Predecessors page.

Table 118. Internetwork Predecessors PageThis column ... Specifies ...

Network Agent The network agent workstation to which the predecessor belongs.

Dependency A freeform dependency or the job / job stream predecessor in theformat workstation#jobstream.job. The maximum length of thisfield is 120 for freeform characters or 16 for workstation, 16 for thejob stream, and 40 for the job.

Release Status The release status of the internetwork predecessors. The possible statesare Released or Not Released.

Internal Status The Workload Scheduler internal status of the predecessor job or jobstream.

Successors PageTable 119 describes the columns in the Successors page.

Table 119. Successors PageThis 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 statesare Released or Not Released.

Internal Status The Workload Scheduler internal status of the successor job.


¶ Click Apply to save your changes in the plan and leave the window open.

¶ Click OK to save your changes in the plan and close the window.

Adding Predecessors to a Job InstanceTo add a predecessor job or job stream to a job instance:

1.

308 Version 8.1

Display the predecessors of the job instance.

2. Click the Add Row button. This creates a new row in the list of predecessors.

3.a. To specify a predecessor job instance, double-click in the text box in the Job column

and open a Find window to find the name of a predecessor job instance.b. To specify a predecessor job stream instance, double-click in the text box in the Job

Stream column and open a Find window to find the name of a predecessor jobstream instance.




Deleting Predecessors from a Job InstanceTo delete a predecessor job or job stream from a job instance:

1. Display the predecessors of the job instance. For information, see “DisplayingDependencies of a Job Instance” on page 307.

2. Select the predecessor row in the list and click Delete from Table (X).




Displaying Successors of a Job InstanceTo display the successors of a job instance in the plan:

1. Run a list of job instances that contains the job you want to display. See “Displaying aList of Jobs in the Plan” on page 294 for more information.

2. In the list results, right-click the job instance you want to display and selectDependencies from the pop-up menu.

The Dependencies - Job Instance window is displayed.

3. To display successor jobs and job streams, click Successors in the left pane.

For descriptions of the column headings in the Successors view, refer to “DeletingPredecessors from a Job Instance”.




Holding a Job InstanceChanging a job instance to Hold sets the priority of the job instance to 0. Use the Releasecommand to change the priority back to its original level at the start of day.

Holding a Single Job InstanceTo change a single job instance to Hold:

1. Run a list of job instances that contains the job instance you want to modify. See“Displaying a List of Jobs in the Plan” on page 294 for more information.


22.P

lanTasks

2. Select All Scheduled Jobs List View.

3. Right-click the job instance you want to hold. To select more than one job instance, doone of the following:¶ To select a range of job instances in the list, hold down the shift key and left-click

the first and last job instances in the range. Right-click on one of the selected jobs toopen the popup menu.

¶ To select multiple job instances, hold down the control key and left-click on each jobinstance. Right-click one of the selected job instances to open the popup menu.

4. Select Hold from the pop-up menu and click Yes in the confirmation window.

Holding All Job InstancesTo hold all jobs in a group of job instances:

1. Run the list of job instances.

2. Select All Scheduled Jobs Timeline View.

3. Right-click the arrow next to the job instance group.

4. Click Hold All.

Releasing a Job InstanceThe Release command reverses the Hold command. The Release command sets the priorityof a job back to the original setting at the start of the processing day. Do not confuse thiscommand with Release All Dependencies. It has no effect on job dependencies.

Releasing a Single Job InstanceTo change a single job instance to Release:


2. Select All Scheduled Jobs List View.

3. Right-click the job instance you want release. To select more than one job instance, doone of the following:¶ To select a range of job instances in the list, hold down the shift key and left-click

the first and last job instances in the range. Right-click on one of the selected jobinstances to open the pop-up menu.

¶ To select multiple job instances, hold down the control key and left-click on each jobinstance. Right-click one of the selected job instances to open the pop-up menu.

4. Select Release from the pop-up menu and click Yes in the confirmation window.

Releasing All Job InstancesTo release all jobs in a group of job instances:

1. Run the list of job instances.

2. Select All Scheduled Jobs Timeline View.

3. Right-click the arrow next to the job instance group.

4. Click Release All.

310 Version 8.1

Showing Predecessors and SuccessorsTo show the predecessors of a job instance or its successors, right-click a job instance andselect Impact View from the pop-up menu, then either Predecessors or Successors. TheImpact View window is displayed.



Radial

Left

Right

Up

Down

Displaying DependenciesTo display a dependency of a job instance, right-click the job instance and selectDependencies 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 thanone level of dependency, you must right-click each dependent job instance in turn, selectingDependencies from the pop-up menu each time.

Note: If you display dependencies for more than one job, then refresh the display, only thefirst level of dependent job instances is displayed.



22.P

lanTasks

Set as RootAt any time, you can reset the display using one particular job instance as the starting, orroot, job instance. To do this, right-click the job instance you want to use as the root jobinstance and select Set As Root from the pop-up menu. The display is refreshed, showingthe selected job instance as the root instance.

To reset the display in a separate window, right-click the job instance you want to use as theroot job instance and select Set As Root In New Frame from the pop-up menu.

Browsing the Job LogA job instance log file is created for each job instance launched by Workload Scheduler. Logfiles contain header and trailer banners, echoed commands, and errors and warnings. Thesefiles can be used to troubleshoot problems when jobs run.

To view the job instance log:

1. Run a list of job instances that contains the job instance you want to rerun. See“Displaying a List of Jobs in the Plan” on page 294 for more information.

2. In the list results, right-click the job instance you want to rerun.

3. Select Browse Job Log from the pop-up menu. The job instance log file window isdisplayed.

4. When you have finished, click Cancel to close the window.

Figure 181. Job instance Log File Window

312 Version 8.1

Rerunning a Job Instance

Note: You cannot rerun multiple job instances simultaneously.

To rerun a job instance:

1. Run a list of job instances that contains the job instance you want to rerun. See“Displaying a List of Jobs in the Plan” on page 294 for more information.

2. In the list results, right-click the job instance you want to rerun.

3. Select Rerun from the pop-up menu. The Rerun Job window is displayed.

4. To rerun the job directly, click OK. Otherwise, add any additional options.


Table 121. Rerun Job Window InformationIn this area ... Enter this information ...

Step The step from which you would like to rerun this job. The new jobinstance will assume the name specified here.

From The job from which you want the job to run.

Workstation Name The workstation to run the job.

The following fields are only valid when using the From option:

Start Time The start date and time for the job.Specify Date and Time

Select this checkbox to specify a start date and time for the job.Date

Specify a start date for the job.Time

Specify a start time for the job.

Time Zone A time zone for the job. The time zone option must be enabled for thisfield to be active.

Figure 182. Rerun Job Window


22.P

lanTasks

Table 121. Rerun Job Window Information (continued)In this area ... Enter this information ...

Priority The priority of the submitted job. To change the priority, enter a valuein the field or select one of:Hold Sets the priority to 0. This job will not run until the priority is

raised.High Sets the priority to 100.Go Sets the priority to 101.Default

Sets the priority to the default priority of the selected job.Possible priority values are 0 through 101, where 101 is the highestpriority. A priority value of zero prevents the ad hoc job from launching.




Canceling a Job InstanceCanceling a job instance in the plan prevents the job from running. A canceled job instancecan be submitted anytime during the production cycle using an alias name. For moreinformation, see “Submitting a Job into the Plan” on page 336.

To cancel a job instance:


2. In the list results, right-click the job instance you want cancel. To select more than onejob instance, do one of the following:¶ To select a range of job instances in the list, hold down the shift key and left-click

the first and last job instances in the range. Right-click on one of the selected jobs toopen the popup menu.


3. Select Cancel Job from the pop-up menu and click Yes in the confirmation window.

Killing a Job InstanceKilling a job instance can only be done for UNIX command and UNIX script jobs. Youcannot kill Windows NT job instances.

To kill a UNIX job instance:

1. Run a list of job instances that contains the job instance you want to kill. See“Displaying a List of Jobs in the Plan” on page 294 for more information.

2. In the list results, right-click the job instance you want kill. To select more than one jobinstance, do one of the following:¶ To select a range of job instances in the list, hold down the shift key and left-click

the first and last job instances in the range. Right-click on one of the selected job toopen the pop-up menu.


314 Version 8.1

3. Select Kill from the pop-up menu and select Yes in the confirmation box. This kills acurrently running UNIX job.

Confirming a Job Instance SUCC or ABENDConfirming a job instance status as SUCC or ABEND allows you to force the job instanceinto a state where either its successors can continue processing or job recovery options arestarted.

To confirm a job instance status to SUCC or ABEND:

1. Run a list of job instances that contains the job instance you want to confirm. See“Displaying a List of Jobs in the Plan” on page 294 for more information.

2. In the list results, right-click the job instance you want to confirm. To select more thanone job instance, do one of the following:¶ To select a range of job instances in the list, hold down the shift key and left-click

the first and last job instances in the range. Right-click on the selected job instanceto open the pop-up menu.


3. Select Confirm, then SUCC or Confirm, then ABEND from the pop-up menu.

4. Select Yes in the confirmation box. This forces the status of the selected job instances toSUCC or ABEND.

Releasing a Job Instance from DependenciesReleasing a job instance from its dependencies removes dependencies on the following:

¶ Scheduled start time

¶ Predecessor jobs and job streams

¶ File dependencies

¶ Prompt dependencies

¶ Resource dependencies

To release a job instance from its dependencies:

1. Run a list of job instances that contains the job instance you want to release. See“Displaying a List of Jobs in the Plan” on page 294 for more information.

2. In the list results, right-click the job instance you want release. To select more than onejob instance, do one of the following:¶ To select a range of job instances in the list, hold down the shift key and left-click

the first and last job instances in the range. Right-click on the selected job instanceto open the popup menu.


3. Select Release All Dependencies from the pop-up menu and click Yes in theconfirmation window. This allows the job instance to run unless there are other higherpriority jobs waiting to run, or if the job instance priority is below the fence for theworkstation.


22.P

lanTasks

Managing Job Stream Instances in the PlanA job stream is a sequence of jobs, including the resources, prompts, parameters, andworkstations that support them, and scheduling information. The dependency of one job onthe completion of another determines the sequence of the jobs. The scheduling information,such as the use of run cycles, calendars, and time restrictions, determines when and howoften the job stream instance is run.

Table 122describes the commands that you can use on a job stream instance in the plan.

Table 122. Job Stream Instance CommandsUse 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 includesviewing, adding, modifying, or deleting the dependencies and timerestrictions 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, andthe Job Schedule Console status to held.

Release Counteracts the Hold command. The Release command reverts a jobstream 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 thenumber 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 selectedjob stream instance. See “Submitting Jobs and Job Streams into thePlan” on page 335.

Select for Monitoring Specify that the running of this job is to monitored by Tivoli BusinessSystems Manager.

Deselect for Monitoring Specify that the running of this job is no longer to be monitored byTivoli Business Systems Manager.

Displaying a List of Job Streams in the PlanTo display a list of job stream instances in the plan:

1. In the Job Scheduling view, expand the scheduler button.

2. Expand the branches below the scheduler button until you see the button for the jobstream instance list you want to run.

3. Right-click the job stream instance list button and select Load List from the pop-upmenu. The list results are displayed in the right pane of the Job Scheduling Console.

316 Version 8.1

Timeline View of Job Stream InstancesThe Timeline view provides a table and timeline display of job stream instances in the plan.Use the borders and the arrows on the borders to adjust the sizes of the windows. Use thearrows at the top of the timeline window to move the view in one hour and one dayincrements.

In the timeline window, the dark blue line represents the window of time a job streaminstance 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 blackdot. A light blue bar within the dark blue line represents the actual duration of the jobstream. 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:

This button ... Is called ... And does this ...

Go to Moves the timeline display to the date you select on thepopup calendar.

Go to First Moves the timeline display to the start time and day offsetof the earliest job stream instance.


Table 123. Job Stream Instances Timeline View WindowThis column ... Specifies ...

Name The name of the job stream instance.

Status The status of the job stream instance. For more information on job orjob stream instance status refer to “Status Description and Mapping” onpage 387.

Started The actual start date and time of the job stream instance.

Runtime Displays the actual duration of the job stream instance.

Start at The date and time of the planned start time for the job stream instance.

Duration The estimated duration time of the job stream instance.

Deadline The date and time of the deadline for the job stream instance.

Figure 183. Job Stream Instances Timeline View Window


22.P

lanTasks

List View of Job Stream InstancesThe List view provides a table display of job stream instances.


Table 124. Job Stream Instances List View WindowThis column ... Specifies ...

Job Stream The name of the job stream instance.

Workstation The name of the workstation on which the job stream instance runs.

Status The Job Scheduling Console status of the job stream instance. Formore information on job or job stream instance status refer to “StatusDescription and Mapping” on page 387.

Internal Status The Workload Scheduler internal status of the job stream instance. Formore information on job or job stream status refer to “StatusDescription and Mapping” on page 387.

Information Additional information about the job stream instance.

Priority The priority of the job stream instance.

Num Jobs The total number of jobs in the job stream instance.

OK Jobs The number of jobs that have completed successfully in the job streaminstance

Limit The job limit of the job stream instance.

Original Job Stream The original name of the job stream instance, for job stream instancesthat were submitted with an alias name.

Scheduled Start The date and time the job stream instance is scheduled to start running.

Actual Start The date and time the job stream instance started running.

Est. Duration The expected duration time of the job stream instance.

Actual Duration The actual duration time of the job stream instance.

Deadline Time The date and time of the job stream instance deadline.

Job Stream Dep. The number of predecessor job streams for the job stream instance. Anbutton indicates the lowest status of the predecessors.

Job Dep. The number of predecessor jobs of the job stream instance. An buttonindicates the lowest status of the predecessors.

Figure 184. Job Stream Instances List View Window

318 Version 8.1

Table 124. Job Stream Instances List View Window (continued)This column ... Specifies ...

Inet Dep. The number of internetwork predecessors to this job stream.

File Dep. The number of file dependencies of the job stream instance. An buttonindicates the lowest status of the dependencies.

Prompt Dep. The number of prompt dependencies of the job stream instance. Anbutton indicates the lowest status of the dependencies.

Resource Dep. The number of resource dependencies of the job stream instance. Anbutton indicates the lowest status of the dependencies.

Displaying and Changing the Properties of a Job Stream InstanceTo display the properties of a job stream instance in the plan:

1. Run a list of job stream instances that contains the job stream you want to display.

2. In the list results, double-click the job stream instance you want to display or right-clickthe job stream instance and select Properties from the pop-up menu. The Properties -Job Stream Instance General page is displayed.

General Page


Table 125. Properties - Job Stream Instance General InformationThis area ... Contains this information ...

Name The name of the job stream instance.

Original Name The original name of a job stream instance that was submitted with analias name.

Figure 185. Properties - Job Stream Instance General Page


22.P

lanTasks

Table 125. Properties - Job Stream Instance General Information (continued)This area ... Contains this information ...

Workstation Name The name of the workstation on which the job stream instance islaunched.

Workstation Class Name The name of the workstation class on which the job stream instance islaunched.

Priority The priority of the job stream instance. To change the priority, select avalue from the drop-down list or click Hold to select priority 0, Highto select priority 100, or Go to select priority 101. Possible priorityvalues are 0 through 101, where 101 is the highest priority. A priorityvalue of zero prevents the job stream instance from launching.

Limit The number of jobs that can be running at the same time in theschedule. To change the job limit, select a value from the drop-downlist. Possible values are 0 through 1024. If you specify a job limit of 0,no jobs within the job stream instance are launched.

Status The status of the job stream instance. For more information on job orjob stream status refer to “Status Description and Mapping” onpage 387.

Internal Status The Workload Scheduler internal status of the job stream instance. Formore information on job or job stream status refer to “StatusDescription and Mapping” on page 387.

Information Additional information about the job stream instance.

Production Date The current date of the production cycle.

Carry Forward Indicates this job stream instance is carried forward to the nextprocessing day if it does not complete before the end of the currentproduction day.

Job Information Information about the job instances in the job stream instance.Number Of Jobs

The total number of job instances.Number of Jobs Not Run

The number of job instances that have not run.Number Of Jobs Abended

The number of job instances that have abended.Number of Successful Jobs

The number of job instances that have run successfully.Number Of Executing Jobs

The number of job instances that are running.Number of Failed Jobs

The number of job instances that have failed to run.

Time Information Information about the timing of the job stream instance.Start Time

The time and day the job stream instance started running.Runtime

The duration of the job stream instance.Est. Duration

Specifies the estimated duration of the job stream instance.


320 Version 8.1



Table 126. Properties - Job Stream Instance Time Restrictions InformationThis area ... Contains this information ...

Start The earliest time the job stream instance will be launched. The jobstream instance will not be launched before this time. To change thetime, make your selections as follows:Specify date and time

Select this option to enable the entry of a start time.Date Specify the start date or click the calendar button and select a

date from the drop-down calendar.Time Specify a start time in the following format:

hh:mm am|pm


Deadline The latest time the job stream instance will be launched. The jobstream instance will not be launched after this time. To change thetime, make your selections as follows:Specify date and time

Select this option to enable the entry of a deadline time.Date Specify the deadline date or click the calendar button and select

a date from the drop-down calendar.Time Specify a deadline time in the following format:

hh:mm am|pm


Figure 186. Properties - Job Stream Instance Time Restrictions Page


22.P

lanTasks

Table 126. Properties - Job Stream Instance Time RestrictionsInformation (continued)This area ... Contains this information ...

Time Zone Select a time zone from the drop-down list. The start time and deadlinetime are in this time zone. If a time zone is not specified for the jobstream instance, all time values are in the time zone of the workstationon which the job instance is launched.Note: The time zone option must be activated in the global optionsfile for this field to be active

Select Files in the left pane. The Files page is displayed.

Files Page


Table 127. Properties - Job Stream Instance Files InformationThis column ... Specifies ...

Filename The name of the file.


Release Status The status of the file dependency. The possible values are:Not Released

The job stream instance is not released from the file dependency.Released

The job stream instance is released from the file dependency.To release the job instance from the file dependency, click in theStatus column and select Released from the drop-down menu.


Figure 187. Properties - Job Stream Instance Files Page

322 Version 8.1

Table 127. Properties - Job Stream Instance Files Information (continued)This column ... Specifies ...






Adding a File DependencyTo add a file dependency for the job stream instance:


2. Double-click in the text box in the Filename column and type in a file name.

3. Double-click in the text box in the Workstation column and open a Find window tolocate and insert the name of the workstation on which the file exists or will be created.

4. Double-click in the text box in the Qualifiers column and specify the test conditions forthe file dependency. On UNIX, the valid qualifiers are the same as UNIX test commandconditions. For more information, refer to your UNIX system documentation.








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 defaultis -f %p.

Removing a File DependencyTo remove a file dependency for the job stream instance, select the file row in the list andclick the Delete from Table button.

Select Prompts in the left pane. The Prompts page is displayed.


22.P

lanTasks

Prompts Page

Select the type of prompt you want to display, ad hoc or predefined.

To display ad hoc prompt dependencies, select Ad Hoc Prompt from the drop-down listin the toolbar.

To display predefined prompt dependencies, select Predefined Prompt from thedrop-down list in the toolbar.


Table 128. Properties - Job Stream Instance Prompts InformationThis column ... Specifies ...

Name The name of the prompt. This column is for predefined prompts only.


Workstation The workstation that will display the prompt message. This is for adhoc prompts only.

Number The number of the prompt dependency.

Status The status of the prompt dependency. The possible values are:Not Released

The job stream instance is not released from the promptdependency.

ReleasedThe job stream instance is released from the prompt dependency.

To release the job instance from the prompt dependency, click in theStatus column and select Released from the drop-down menu.

Figure 188. Properties - Job Stream Instance Prompts Page

324 Version 8.1

Table 128. Properties - Job Stream Instance Prompts Information (continued)This column ... Specifies ...



The has been asked, but no response has been received.Answered Yes

The prompt has been answered affirmatively and the job streaminstance dependency is released.

Answered NoThe prompt has been answered negatively and the job streaminstance dependency is not released.


Adding a Prompt DependencyTo add a prompt dependency for the job stream instance:

1. Click the Add Row button. This creates a new row in the list of prompt dependencies.

2. For a predefined prompt, double-click in the text box in the Name column and use theFind tool to locate and insert the name of a prompt.

3. For an ad hoc prompt, double-click in the text box in the Message Text column and typein the text of the prompt. The default behavior of a prompt is to display a message andwait 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 itrequires a reply. You can include backslash n (\n) within the text for new lines. You canalso include one or more Workload Scheduler parameters as part or all of the text string.To use a parameter, place its name between carets (^).

Removing a Prompt DependencyTo remove a prompt dependency for the job stream instance, select the prompt row in thelist and click the Delete from Table button.



22.P

lanTasks

Resources Page


Table 129. Properties - Job Stream Instance Resources WindowThis column ... Specifies ...



Quantity The number of units of the resource that are needed by the job streaminstance to satisfy the dependency.


Release Status The status of the resource dependency. The possible values are:Not Released

The job stream instance is not released from the resourcedependency.

ReleasedThe job stream instance is released from the resource dependency.

To release the job instance from the resource dependency, click in theStatus column and select Released from the drop-down menu.

Adding a Resource DependencyTo add a resource dependency for the job stream instance:


2. In the Workstation column, open a Find window to add the name of a workstation.

3. Double-click in the text box in the Resource column and open a Find window to add aresource name.

4. Double-click in the text box in the Quantity column and specify the number of resourceunits required by the job stream instance. The default is one.

Figure 189. Properties - Job Stream Instance Resources Page

326 Version 8.1

Deleting a Resource DependencyTo delete a resource dependency for the job stream instance, select the resource row in thelist and click the Delete from Table button.


¶ Click Apply to save the changes you made to the properties and leave the window open.

¶ Click OK to save the changes you made to the properties and close the window.

Displaying Dependencies of a Job Stream InstanceTo display the dependencies of a job stream instance, in a list, right-click the job streaminstance you want to display and select Dependencies from the pop-up menu. TheDependencies - Job Stream Instance window is displayed.

You can display three types of dependency:¶ Predecessors¶ Internetwork predecessors¶ Successors

The following figure shows the Predecessors page.


Table 130. Dependencies - Job Stream Instance Predecessor WindowThis column ... Specifies ...

Job Stream The name of a predecessor job stream instance.

Job Specifies the name of a predecessor job instance.

Workstation Specifies the workstation of the predecessor job or job stream instance.

Release Status Specifies the status of the predecessor dependency. The possible valuesare:Released

The job stream instance is released from the predecessordependency.

Not ReleasedThe job stream instance is not released from the predecessordependency.

To release the job stream instance from the predecessor dependency,click in the Release Status column and select Released from thedrop-down menu.

Figure 190. Dependencies Predecessors Page


22.P

lanTasks

Table 130. Dependencies - Job Stream Instance Predecessor Window (continued)This column ... Specifies ...

Internal Status Specifies the Workload Scheduler internal status of the predecessor jobor job stream instance. For more information on job or job streamstatus refer to “Status Description and Mapping” on page 387.




Adding Predecessors to a Job Stream InstanceTo add a predecessor job or job stream to a job stream instance:

1. Display the predecessors of the job stream instance. For information, see “DisplayingDependencies of a Job Stream Instance” on page 327.

2. Click Add Row (+). This creates a new row in the list of predecessors.

3. To specify a predecessor job stream instance, double-click in the text box in the JobStream column and click Find to locate and insert the name of the predecessor jobstream instance.

4. To specify a predecessor job instance, double-click in the text box in the Job columnand click Find to locate and insert the name of a predecessor job instance.




Deleting Predecessors from a Job Stream InstanceTo delete a predecessor job or job stream from a job stream instance:

1. Display the predecessors of the job stream instance. For information, see “DisplayingDependencies of a Job Stream Instance” on page 327.

2. Select the predecessor row in the list and click the Delete from Table (X) button.




Displaying Successors of a Job Stream InstanceTo display the successors of a job stream instance in the plan:

1. Run a list of job stream instances that contains the job stream you want to modify.

2. In the list results, right-click the job stream instance you want to display and selectDependencies... from the pop-up menu.

The Dependencies - Job Stream Instance window is displayed.

3. To display successor jobs and job streams, click Successors in the left window.

For descriptions of the column headings in the Successors view, refer to “DisplayingDependencies of a Job Stream Instance” on page 327.

328 Version 8.1




Holding a Job Stream InstanceChanging a job stream instance to Hold sets the priority of the job instance to zero. Use theRelease command to change the priority back to its original level at the start of theprocessing day.

To change a job stream instance to Hold:

1. Run a list of job stream instances that contains the job stream instance you want tomodify. See “Displaying a List of Job Streams in the Plan” on page 316 for moreinformation.

2. Select the All Scheduled Job Streams List view.

3. Right-click the job stream instance you want to hold. To select more than one job streaminstance, do one of the following:¶ To select a range of job stream instances in the list, hold down the shift key and

left-click the first and last job stream instances in the range. Right-click one of theselected job stream instances to open the popup menu.

¶ To select multiple job stream instances, hold down the control key and left-clickeach job stream instance. Right-click one of the selected job stream instances to openthe popup menu.

4. Select Hold from the pop-up menu and click Yes in the confirmation window.

Releasing a Job Stream InstanceThe Release command is used to cancel the Hold command. The Release command sets thepriority back to the original setting at the start of the processing day. Do not confuse thiscommand with the Release All Dependencies command. This command has no effect on jobstream instance dependencies.

To change a job stream instance to Release:


2. Select the All Scheduled Job Streams List view.

3. In the list results, right-click the job stream instance you want to release. To select morethan one job stream instance, do one of the following:¶ To select a range of job stream instances in the list, hold down the shift key and

left-click the first and last job stream instances in the range. Right-click one of theselected job stream instance to open the popup menu.


4. Select Release from the pop-up menu and click Yes in the confirmation window.


22.P

lanTasks

Showing Predecessors and SuccessorsTo show the predecessors of a job instance or its successors, right-click a job streaminstance and select Impact View from the pop-up menu, then either Predecessors orSuccessors. The Impact View window is displayed.



Radial

Left

Right

Up

Down

Canceling a Job Stream InstanceCanceling a job stream instance in the plan prevents the job stream instance from running. Acanceled job stream instance can be re-submitted using an alias name. For more information,see “Re-submitting a Job Stream Instance” on page 333.

To cancel a job stream instance:


2. In the list results, right-click the job stream instance you want cancel. To select morethan one job stream instance, do one of the following:


330 Version 8.1

¶ To select a range of job stream instances in the list, hold down the shift key andleft-click the first and last job stream instances in the range. Right-click one of theselected job stream instance to open the popup menu.


3. Select Cancel from the pop-up menu and click Yes in the confirmation window.

Changing the Job Limit of a Job Stream InstanceTo change the job limit of a job stream instance in the plan:

1. Run a list of job stream instances that contains the job stream instance you want tomodify.

2. In the list results, right-click the job stream instance you want modify. To select morethan one job stream instance, do one of the following:¶ To select a range of job stream instances in the list, hold down the shift key and

left-click the first and last job stream instances in the range. Right-click one of theselected job stream to open the popup menu.


3. Select Limit from the pop-up menu.

The Change Limit - Job Stream Instance window is displayed.

4. Specify a new job limit in the New Limit field.


¶ Click OK button to save the new job limit in the plan and close the window.

¶ Click Cancel button to close the window without saving the new job limit.

Changing the Priority of a Job Stream InstanceTo change the priority of a job stream instance in the plan:


2. In the list results, right-click the job stream instance you want modify or, to select morethan one job stream instance, do one of the following:¶ To select a range of job stream instances in the list, hold down the shift key and

left-click the first and last job stream instances in the range. Right-click one of theselected job stream instance to open the popup menu.

Figure 192. Change Limit - Job Stream Instance Window


22.P

lanTasks


3. Select Priority from the pop-up menu.

The Change Priority - Job Stream Instance window is displayed.

4. Select a new priority value from the drop-down list or click of the following buttons:

Table 132. Job Stream Instance PrioritiesThis 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 originalvalue of the job stream instance at the start of the processing day. If multiple jobstream instances are selected, the priority of each job stream instance is set backto what it was at start of the processing day.


¶ Click OK to save the new priority in the plan and close the window.

¶ Click Cancel to close the window without saving the new priority.

Releasing a Job Stream Instance from DependenciesReleasing a job stream instance from its dependencies removes dependencies on thefollowing objects:

¶ Scheduled start time

¶ Predecessor jobs and job streams

¶ Resources

¶ Files

¶ Prompts

To release a job stream instance from its dependencies:

1. In a list, right-click the job stream instance you want release. To select more than onejob stream instance, do one of the following:

Figure 193. Change Priority - Job Stream Instance Window

332 Version 8.1

¶ To select a range of job stream instances in the list, hold down the shift key andleft-click the first and last job stream instances in the range. Right-click one of theselected job stream to open the popup menu.


2. Select Release All Dependencies from the pop-up menu and click Yes in theconfirmation window.

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 InstanceWhen 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.

To re-submit a job stream instance in the plan:

1. Run a list of job stream instances that contains the job stream instance you want tore-submit. See “Displaying a List of Job Streams in the Plan” on page 316 for moreinformation.

2. In the list results, right-click the job stream instance you want re-submit.

3. Select Re-Submit from the pop-up menu. The Re-Submit Job Stream Instance window isdisplayed.

4. Specify an alias name for the re-submitted job stream instance in the Alias field. If youdo not specify an alias, a name is generated by Workload Scheduler. For unexpandedmode, Workload Scheduler starts with the first two characters of the original job streaminstance name followed by six random numbers. For expanded mode, the scheduler startswith the first six characters of the original job stream instance name followed by tenrandom 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.... Forinformation about job stream instance properties, see “Displaying and Changing theProperties of a Job Stream Instance” on page 319.

Figure 194. Re-Submit Job Stream Instance Window


22.P

lanTasks

7. To change the predecessors for the re-submitted job stream, see “Adding Predecessors toa Job Stream Instance” on page 328 and “Deleting Predecessors from a Job StreamInstance” on page 328.

Submitting JobsFor information about submitting jobs, see “Submitting Jobs and Job Streams into the Plan”on page 335.

Monitoring JobsTo select a job a job stream instance to be monitored by Tivoli Business Systems Manager,right-click a job stream instance and select Select for Monitoring.

To deselect a job a job stream instance from monitoring by Tivoli Business SystemsManager, right-click the job stream instance and select Deselect for Monitoring.

334 Version 8.1

Submitting Jobs and Job Streams into the PlanThis section provides information for submitting jobs and job streams into the plan forimpromptu processing. You can submit jobs and job streams that have been previouslydefined to the database into the plan for impromptu processing. If the job or job stream isalready in the plan and you would like to schedule it again, you can submit it with an alias.

You can also submit ad hoc jobs to the plan. These are jobs that have not been defined inthe database. These jobs are created and submitted into the plan, but are never saved in thedatabase.

Submitting a Job Stream into the PlanTo submit a job stream that already exists in the database into the plan:


2. Right-click the scheduler engine button and select Submit then Job Stream from thepop-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 WindowIn this field ... Do this ...

Job Stream click the ellipsis to open a Find Job Stream window. This field iscompleted automatically when you select a job stream using theFind Job Stream window.

Workstation name This field is completed automatically when you select a job streamusing the Find Job Stream window.

Alias Specify an alias name for the submitted job stream instance. Analias name is needed only if the plan contains a job stream instanceof the same name. If an alias name is necessary, and you do notspecify an alias, a name is generated by Workload Scheduler thatstarts with the first two characters of the original job stream namefollowed by six random characters.

4. To modify the properties of the submitted job stream, click Properties. For informationabout job stream properties, see “Displaying and Changing the Properties of a JobStream Instance” on page 319.


¶ Click OK to submit the job stream and close the window.

¶ Click Cancel to close the window without submitting the job stream.

Figure 195. Submit Job Stream into Plan Window


22.P

lanTasks

Submitting a Job into the PlanTo submit a job that is defined in the database into a job stream instance, you can use thejob stream instance popup menu or the Workload Scheduler engine popup menu.

If you submit the job from the scheduler engine pop-up menu, the job is submitted through adefault 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 issubmitted through that specific job stream instance (see “Using a Specific Job Stream” onpage 337).

Using a Default Job StreamTo submit a job through a default job stream instance provided by Workload Scheduler:

1. In the Job Scheduling view, right-click the scheduler engine button to display the Submitcommands.

2. Select Submit then Job from the pop-up menu.

The Submit Job into Plan window is displayed.

3. Use the information in Table 134 to complete this window.

Table 134. Submit Job into Plan WindowIn this area ... Enter this information ...

Job Specifies the job to submit.Name The name of the job that you want to submit to the

plan. If you need to, click the ellipsis (...) to displaya Find Job window where you can search for andselect a job to submit into the plan.

Workstation The name of the workstation on which the jobinstance runs. This field is completed automaticallywhen you select a job using the Find Job window.

Figure 196. Submit Job into Plan Window - Default Job Stream

336 Version 8.1

Table 134. Submit Job into Plan Window (continued)In this area ... Enter this information ...

Into Specifies the job stream through which the job is submitted.Job Stream Displays the name of the default job stream, JOBS,

provided by Workload Scheduler. You cannotmodify this.

Workstation Displays the name of the workstation on which thejob stream instance runs. You can specify adifferent workstation. Click the ellipsis (...) todisplay a Find Workstation Instance window if youwant to find a list of available workstations.

Alias An alias name for the submitted job. An alias is needed only if JOBScontains another job of the same name. An error message isdisplayed if JOBS already has a job instance of the same name.

4. When you have finished:¶ If you want to view or modify the properties of the job, click on Properties. See

“Viewing or Modifying the Properties of the Job to Submit” on page 338 for details.¶ If you want to submit the job and close the window, click OK.

Using a Specific Job StreamTo submit a job through a job stream instance that you select, in a list, right-click a jobstream instance and select Submit, then Job from the pop-up men. The Submit Job intoPlan window is displayed.


Table 135. Submit Job into Plan Window - Specific Job streamIn this area ... Enter this information ...

Job Specifies the job to submit.Name Write the name of the job that you want to submit to

the plan. If you need to, click the ellipsis (...) todisplay a Find Job window where you can search forand select a job to submit into the plan.

Workstation Write the name of the workstation on which the jobinstance runs. This field is completed automaticallywhen you select a job using the Find Job window.

Figure 197. Submit Job into Plan Window


22.P

lanTasks

Table 135. Submit Job into Plan Window - Specific Job stream (continued)In this area ... Enter this information ...

Into Displays read-only information about the job stream instance throughwhich you are submitting the job:Job Stream The name of your selected job stream instance.Workstation The name of the workstation that owns your selected

job stream instance.

Alias An alias name for the submitted job. An alias is needed only if the jobstream through which the job is submitted contains another job of thesame name. An error message is displayed if you submit a job to a jobstream instance that already has a job instance of the same name.


¶ If you want to view or modify the properties of the job, click on Properties. See“Viewing or Modifying the Properties of the Job to Submit” for details.

¶ If you want to submit the job and close the window, click OK.

Viewing or Modifying the Properties of the Job to SubmitTo view or modify the properties of a job, before submitting it into the plan, clickProperties in the Submit Job into Plan window. The Properties - Job Instance General pageis displayed.

General Page

Figure 198. Properties - Job Instance General Page

338 Version 8.1


Table 136. Properties - Job Instance General WindowThis area ... Specifies ...

Job Displays information about the submitted job.Name The name of the submitted job.Workstation The name of the workstation of the job.

Into Displays information about the job stream into which the job issubmitted.Job Stream The name of the job stream into which the job is

submitted.Workstation The name of the workstation of the job stream.

Task Type The task type of the submitted job.

Alias The alias of the submitted job, if defined.



Sets the priority to the default priority of the selected job.Possible priority values are 0 through 101, where 101 is the highestpriority. A priority value of zero prevents the ad hoc job fromlaunching.


22.P

lanTasks

Table 136. Properties - Job Instance General Window (continued)This area ... Specifies ...

Recovery Options Displays information about the recovery options of the submitted job.Action The recovery action for the submitted job. It can be

Stop, Continue, or Rerun.Message The text of a recovery prompt. The text can contain

up to 64 characters. The default behavior of a promptis to display a message and wait for a reply. If thestring begins with a colon (:), the message isdisplayed but no reply is necessary. If the stringbegins with an exclamation mark (!), the message isnot displayed but it requires a reply.

Job

The name of a recovery job to run if the parent jobABENDs. To change the name, click Find and selecta job from a list. Recovery jobs are run only once foreach ABENDed instance of the parent job.

Workstation The name of the workstation on which the recoveryjob runs. The name is entered automatically whenyou select a recovery job.

Not all jobs are eligible to have recovery jobs run ona different workstation. Follow these guidelines:¶ If either workstation is an extended agent, it must

be hosted by a domain manager or a fault-tolerantagent that runs in Full Status mode.

¶ The recovery job’s workstation must be in thesame domain as the parent job’s workstation.

¶ If the recovery job’s workstation is afault-tolerant agent, it must run in Full Statusmode.

Requires Confirmation Select this option to indicate that job completion must be confirmed bythe operator.

Select Task in the left pane of the window. The Task page is displayed.

340 Version 8.1

Task Page

The Task page is different for each type of job and operating system. These fields displaythe task type, path, and the command or script file referenced by the job. These fields areread only.

Select Time Restrictions in the left pane of the window. The Time Restrictions page.


Figure 199. Properties - Job Instance Task Page

Figure 200. Properties - Job Instance Time Restrictions Page


22.P

lanTasks

Table 137

Table 137. Properties - Job Instance Time Restrictions WindowThis area ... Specifies ...

Start The earliest time the job will be launched. The job will not belaunched before this time. To change the time:Specify date and time

Select this option to enable the entry of a start time.Date

Specify a start date or click the calendar button and select a datefrom the drop-down calendar.

TimeSpecify a start time in the following format:

hh:mm am|pm


Deadline The latest time the job will be launched. The job will not be launchedafter this time. To change the time:Specify date and time

Select this option to enable the entry of a deadline time.Date

Specify the deadline date or click the calendar button and select adate from the drop-down calendar.

TimeSpecify a deadline time in the following format:

hh:mm am|pm


Time Zone If the Time Zone option is enabled, specify the time zone in which thejob runs. The start time and deadline time are in this time zone. Formore information about the time zone feature, see “Enabling TimeZones in the Workload Scheduler” on page 385.

Repeat Range The repetition rate of the job. The job is launched multiple times atthis rate. Make your selections as follows:Hours

The value can be 00 to 23.Minutes

The value can be 00 to 59.

Select Files in the left pane of the window. The Files page is displayed

342 Version 8.1

Files Page


Table 138. Properties - Job Instance Files WindowThis column ... Specifies ...




Release Status The status of the file dependency. This field is read-only for submittedjobs. The possible values are:Not Released

The job stream instance is not released from the filedependency.

ReleasedThe job stream instance is released from the file dependency.






Figure 201. Properties - Job Instance Files Page


22.P

lanTasks

Adding a File DependencyTo add a file dependency for the job:



3. Double-click in the text box in the Workstation column and open a Find window to findthe name of the workstation on which the file exists or will be created.









Notes:a. On both UNIX and Windows NT, the expression %p inserts the file name.b. Entering notempty is the same as entering -s %p.c. If no qualifier is specified, the default is -f %p.

Removing a File DependencyTo remove a file dependency for the job, select the file row in the list and click the Deletefrom Table button.

Select Prompts in the left pane of the window. The Prompts page is displayed.

344 Version 8.1

Prompts Page

Displaying Ad Hoc Prompt DependenciesTo display ad hoc prompt dependencies, select Ad Hoc Prompt from the drop-down list inthe toolbar.


Table 139. Ad Hoc Prompt DependenciesThis column ... Specifies ...


Workstation The workstation that displays the prompt message text.

Number The internal Workload Scheduler ID number of the prompt dependency.

Release Status The status of the prompt dependency. This field is read-only forsubmitted jobs. The possible values are:Not Released


The job instance is released from the prompt dependency.



The prompt has been asked, but no response has been received.Yes The prompt has been answered affirmatively and the job

dependency is released.No The prompt has been answered negatively and the job dependency

is not released.

Reply The reply to the prompt dependency.

Figure 202. Properties - Job Instance Prompts Page


22.P

lanTasks

Displaying Predefined Prompt DependenciesTo display predefined prompt dependencies, select Predefined Prompt from the drop-downlist in the toolbar.


Table 140. Predefined Prompt DependenciesThis column ... Specifies ...

Name The name of the prompt.



Release Status The status of the prompt dependency. This field is read-only forsubmitted jobs. The possible values are:Not Released


The job instance is released from the prompt dependency.



The has been asked, but no response has been received.Yes The prompt has been answered affirmatively and the job


is not released.


Adding a Prompt DependencyTo add a prompt dependency for the job instance:


2. For a predefined prompt, double-click in the text box in the Name column and clickFind to locate and insert the name of a prompt.

3. For an ad hoc prompt, double-click in the text box in the Message Text column and typein the text of the prompt. The default behavior of a prompt is to display a message andwait 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 itrequires a reply. You can include backslash n (\n) within the text for new lines. You caninclude one or more Workload Scheduler parameters as part or all of the text string. Touse a parameter, place its name between carets (^).

Removing a Prompt DependencyTo remove a prompt dependency for the job, select the prompt row in the list and click theDelete from Table button.

Select Resources in the left pane of the window. The Resources page is displayed.

346 Version 8.1

Resources Page


Table 141. Properties - Job Instance Resources WindowThis column ... Specifies ...



Quantity The number of units of the resource that are needed by the job tosatisfy the dependency.


Release Status The status of the resource dependency. This field is read-only forsubmitted jobs. The possible values are:Not Released


The job instance is released from the resource dependency.

Adding a Resource DependencyTo add a resource dependency for the job instance:


2. Double-click in the text box in the Workstation column and click Find to locate andinsert the name of a workstation.

3. Double-click in the text box in the Name column and click Find to locate and insert aresource name.

4. Double-click in the text box in the Quantity column and specify the number of resourceunits required by the job instance. The default is one.

Figure 203. Properties - Job Instance Resources Page


22.P

lanTasks

Deleting a Resource DependencyTo delete a resource dependency for the job instance, select the resource row in the list andclick the Delete from Table button.

Select Predecessors in the left pane of the window. The Predecessors page is displayed.

Predecessors Page


Table 142. Properties - Job Instance Predecessors WindowThis column ... Specifies ...

Job Stream The name of the predecessor job stream.

Job The name of job in the predecessor job stream.

Workstation The name of the predecessor job stream’s workstation.

Release Status The status of the predecessor job or job stream.

Internal Status The Workload Scheduler internal status of the predecessor job or jobstream. For more information on job or job stream status refer to“Status Description and Mapping” on page 387.

Adding a PredecessorTo add a predecessor for the job instance:


2. To specify a predecessor job stream, double-click in the text box in the Job Streamcolumn 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 clickFind to locate and insert a resource name.

Figure 204. Properties - Job Instance Predecessors Page

348 Version 8.1

Deleting a PredecessorTo delete a predecessor for the job instance, select the predecessor row in the list and clickthe Delete from Table button.


¶ Click OK to submit the job and close the window.

¶ Click Cancel to close the window without submitting the job.

Submitting an Ad Hoc Job into the PlanTo submit an ad hoc job (a job that is not defined in the database) into a job streaminstance, you use the scheduler engine pop-up menu.

To submit a job that is defined in the database into a job stream instance, you use the jobstream instance popup menu or the scheduler engine popup menu.

To submit an ad hoc job into a job stream instance:

1. In a list, right-click a job stream instance and select Submit, then Ad Hoc from thepop-up menu. The Submit Ad Hoc Job into Plan window is displayed.

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.

Figure 205. Submit Ad Hoc Job into Plan Window


22.P

lanTasks

General Page


Table 143. Properties - Job Instance General WindowIn this area ... Enter this information ...

Job Displays information about the ad hoc job.Alias

Specify an alias name for the ad hoc job, if necessary.Workstation

Specify the name of the workstation of the ad hoc job.

Into Displays information about the job stream into which the ad hoc job issubmitted.Job Stream

Specify the name of the job stream for the ad hoc job. Theworkstation for this job stream instance is only displayed whenthe Submit > Ad Hoc command was invoked from the JobStream Instance list. For the JOBS job stream, the Properties -Job Instance window job instance will be submitted into theJOBS job stream on the workstation for the job specified in thefield above.

Task Type The task type of the submitted ad hoc job.

Login The UNIX or Windows NT user ID that launches the ad hoc job.

Figure 206. Properties - Job Instance General Page

350 Version 8.1

Table 143. Properties - Job Instance General Window (continued)In this area ... Enter this information ...



Sets the priority to the default priority of the selected job.Possible priority values are 0 through 101, where 101 is the highestpriority. A priority value of zero prevents the ad hoc job fromlaunching.

Is Interactive Specify whether this is an interactive job or not. Interactive jobs are forWindows NT only.

Recovery Options Displays information about the recovery options of the submitted adhoc job.Action

Displays the recovery action for the submitted ad hoc job. It canbe Stop, Continue, or Rerun.

MessageSpecify the text of a recovery prompt. The text can contain up to64 characters. The default behavior of a prompt is to display amessage and wait for a reply. If the string begins with a colon (:),the message is displayed but no reply is necessary. If the stringbegins with an exclamation mark (!), the message is not displayedbut it requires a reply.

JobDisplays the name of a recovery job to run if the parent jobabends. To change the name, click the Find button and select a jobfrom a list. Recovery jobs are run only once for each abendedinstance of the parent ad hoc job.

WorkstationDisplays the name of the workstation on which the recovery jobruns. The name is entered automatically when you select arecovery job.

Not all jobs are eligible to have recovery jobs run on a differentworkstation. Follow these guidelines:¶ If either workstation is an extended agent, it must be hosted

by a domain manager or a fault-tolerant agent that runs inFull Status mode.

¶ The recovery job’s workstation must be in the same domain asthe parent job’s workstation.

¶ If the recovery job’s workstation is a fault-tolerant agent, itmust run in Full Status mode.

Requires Confirmation Select this option to indicate that ad hoc job completion must beconfirmed by the operator.

Select Task in the left pane of the window. The Task page is displayed.


22.P

lanTasks

Task Page

The Task view is different for each task type. To complete the fields and select options onthis page:

Table 144. Task TypesFor 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

UNIX Script and NT ScriptComplete the Script field as follows:

Specify the name of the file the ad hoc job runs. Enter the file name and any options andarguments. For non-expanded databases, the field can contain up to 255 characters. Forexpanded 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 (\), theentire string must be enclosed in quotes (″).

If the file name contains spaces, specify the name in another file that does not have spacesin its name and use the second file’s name in this field.

Figure 207. Properties - Job Instance Task Page

352 Version 8.1

To include a parameter in the Script field:

¶ Place the cursor in the Script field where you want to insert the parameter and clickAdd Parameter.

¶ The Find Parameters window is displayed.

¶ Specify a parameter name in the Find field. The name can contain wildcard characters.

¶ Click Start to display a list of parameter names.

¶ Select a parameter name in the list click OK.


UNIX Command and NT CommandIn the Command field, specify the name of the command the ad hoc job runs. Specify thecommand name and any options and arguments. For non-expanded databases, the field cancontain up to 255 characters. For expanded databases, it can contain up to 4095 characters.Commands are run directly and the jobmanrc standard configuration script is not run.

To include a parameter in the Command field:

¶ Place the cursor in the Command field where you want to insert the parameter andclick Add Parameter.

¶ The Find Parameters window is displayed.

¶ Specify a parameter name in the Find field. The name can contain wildcard characters.

¶ Click Start to display a list of parameter names.

¶ Select a parameter name in the list click OK.


MPE Job FileComplete the Job File field by specifying the name of the MPE file the ad hoc job runs.For example, JFILE4.JCL.CORP.

MPE User JobComplete the User Job field by specifying the name from the JOB card of the MPE job.For example, $userjob=UJOB5.

Extended AgentIn the Task field, enter the XAgent script path or file name or the XAgent command for thisjob.

Click Add Parameter to add a predefined parameter to the task specification

SAP JobFor task type SAP Job, refer to the Tivoli Workload Scheduler Extended Agent for SAP/R3User’s Guide for information about defining the task.

Select Time Restrictions in the left pane of the window. The Time Restrictions page isdisplayed.


22.P

lanTasks



Table 145. Properties - Job Instance Time Restrictions WindowIn this area ... Enter this information ...

Start The earliest time the ad hoc job will be launched. The ad hoc job willnot be launched before this time. To change the time:Specify date and time

Select this option to enable the entry of a start time.Date

Specify the start date or click the calendar button and select a datefrom the drop-down calendar.

TimeSpecify a start time in the following format:

hh:mm am|pm


Deadline The latest time the ad hoc job will be launched. The ad hoc job will notbe launched after this time. To change the time:Specify date and time

Select this option to enable the entry of a deadline time.Date

Specify the deadline date or click the calendar button and select adate from the drop-down calendar.

TimeSpecify a deadline time in the following format:

hh:mm am|pm


Figure 208. Properties - Job Instance Time Restrictions Page

354 Version 8.1

Table 145. Properties - Job Instance Time Restrictions Window (continued)In this area ... Enter this information ...

Time Zone If the Time Zone option is enabled, specify the time zone in which thead hoc job runs. The start time and deadline time are in this time zone.For more information about the time zone feature, refer to “EnablingTime Zones in the Workload Scheduler” on page 385.

Repeat Range The repetition rate of the ad hoc job. The ad hoc job is launchedmultiple times at this rate. To make your selections:Hours

Specify the hours. The value can be 00 to 23.Minutes

Specify the minutes. The value can be 00 to 59.

Select Files in the left pane of the window. The Files page is displayed.

Files Page


Table 146. Properties - Job Instance Files WindowThis column ... Specifies ...




Figure 209. Properties - Job Instance Files Page


22.P

lanTasks

Table 146. Properties - Job Instance Files Window (continued)This column ... Specifies ...

Release Status The status of the file dependency. This field is read-only for submittedjob instances. The possible values are:Not Released

The ad hoc job is not released from the file dependency.Released

The ad hoc job is released from the file dependency.






Adding a File DependencyTo add a file dependency for the ad hoc job:



3. Double-click in the text box in the Workstation column and click Find to add the nameof the workstation on which the file exists or will be created.









Notes:

a. On both UNIX and Windows NT, the expression %p, inserts the file name.

b. Entering notempty is the same as entering -s %p.

c. If no qualifier is specified, the default is -f %p.

Removing a File DependencyTo remove a file dependency for the ad hoc job, select the file row in the list and click theDelete from Table button.

Select Prompts in the left pane of the window. The Prompts page is displayed.

356 Version 8.1

Prompts Page

Displaying Ad Hoc Prompt DependenciesAd hoc prompt dependencies are displayed by default when the Prompts page is displayed.


Table 147. Ad Hoc Prompt DependenciesThis column ... Specifies ...


Workstation The workstation that displays the prompt message text.


Release Status The status of the prompt dependency. This field is read only forsubmitted job instances. The possible values are:Not Released

The ad hoc job instance is not released from the promptdependency.

ReleasedThe ad hoc job instance is released from the prompt dependency.



The has been asked, but no response has been received.Yes The prompt has been answered affirmatively and the ad hoc job

dependency is released.No The prompt has been answered negatively and the ad hoc job

dependency is not released.

Reply The reply to the prompt dependency. This field is read-only forsubmitted job instances.

Figure 210. Properties - Job Instance Prompts Page


22.P

lanTasks

Displaying Predefined Prompt DependenciesTo display predefined prompt dependencies, select Predefined Prompt from the drop-downlist in the toolbar.


Table 148. Predefined Prompt DependenciesThis column ... Specifies ...

Name The name of the prompt.



Release Status The status of the prompt dependency. This field is read only forsubmitted job instances. The possible values are:Not Released

The ad hoc job instance is not released from the promptdependency.

ReleasedThe ad hoc job instance is released from the prompt dependency.



The has been asked, but no response has been received.Yes The prompt has been answered affirmatively and the job


is not released.

Reply The reply to the prompt dependency. This field is read only forsubmitted job instances.

Adding a Prompt DependencyTo add a prompt dependency for the ad hoc job instance:


2. For a predefined prompt, double-click in the text box in the Name column and clickFind to locate and insert the name of a prompt.

3. For an ad hoc prompt, double-click in the text box in the Message Text column and typein the text of the prompt. The default behavior of a prompt is to display a message andwait for a reply. If the string begins with a colon (:), the message is displayed but noreply is necessary. If the string begins with an exclamation mark (!), the message is notdisplayed but it requires a reply.

You can include backslash n (\n) within the text for new lines. You can also include oneor more Workload Scheduler parameters as part or all of the text string. To use aparameter, place its name between carets (^).

Removing a Prompt DependencyTo remove a prompt dependency for the ad hoc job, select the prompt row in the list andclick the Delete from Table button.

Select Resources in the left pane of the window. The Resources page is displayed

358 Version 8.1

Resources Page


Table 149. Properties - Job Instance Resources WindowThis column ... Specifies ...



Quantity The number of units of the resource that are needed by the ad hoc jobto satisfy the dependency.


Release Status The status of the resource dependency. This field is read-only forsubmitted job instances. The possible values are:Not Released


The job instance is released from the resource dependency.

Adding a Resource DependencyTo add a resource dependency for the ad hoc job instance:


2. Double-click in the text box in the Workstation column and click Find to add the nameof a workstation.

3. Double-click in the text box in the Name column and click Find to add a resourcename.

4. Double-click in the text box in the Quantity column and specify the number of resourceunits required by the ad hoc job instance. The default is one.

Figure 211. Properties - Job Instance Resources Page


22.P

lanTasks

Deleting a Resource DependencyTo delete a resource dependency for the ad hoc job instance, select the resource row in thelist and click the Delete from Table button.

Select Predecessors in the left pane of the window. The Predecessors page is displayed.

Predecessors Page


Table 150. Properties - Job Instance Predecessors InformationThis column ... Specifies ...

Job Stream The name of the predecessor job stream.

Job The name of job in the predecessor job stream.

Workstation The name of the predecessor job stream’s workstation.

Release Status The status of the predecessor job or job stream.

Internal Status The Workload Scheduler internal status of the predecessor job or jobstream. For more information on job or job stream status refer to“Status Description and Mapping” on page 387.

Adding a PredecessorTo add a predecessor for the ad hoc job instance:


2. To specify a predecessor job stream, double-click in the text box in the Job Streamcolumn 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 clickFind to locate and insert a resource name.

Figure 212. Properties - Job Instance Predecessors Page

360 Version 8.1

Deleting a PredecessorTo delete a predecessor for the ad hoc job instance, select the predecessor row in the list andclick the Delete from Table button.


¶ Click OK to submit the ad hoc job and close the window.

¶ Click Cancel to close the window without submitting the ad hoc job.

Managing Workstations in the PlanThe plan contains a list of all workstations that are going to be used in that days processing.You can perform the following actions on a workstation in the plan:

¶ Display a list of workstations in the plan. This list contains a number of fields withinformation about the workstation status.

¶ Change the job limit of a workstation instance

¶ Change the job fence of a workstation instance

¶ Start, stop, link, and unlink a workstation

Displaying a List of Workstations in the PlanTo display a list of workstations in the plan:


2. Expand the Default Plan lists group.

3. Right-click on the Status of All Workstations button and select Load List from thepop-up menu.



Table 151. Workstation Status List WindowThis column ... Shows ...

Name The workstation instance name.

Figure 213. Workstation Status List Window


22.P

lanTasks

Table 151. Workstation Status List Window (continued)This column ... Shows ...

Jobman Running Whether or not the jobbing process on the workstation is running.

Link Status The current link status of the workstation. A workstation can either beLINKED or UNLINKED.

Limit The total number of jobs that can be run concurrently on thisworkstation.

Fence The job fence for this workstation. The job fence is the priority a jobmust exceed to run on this workstation. Setting the fence to 40, forexample, prevents jobs with priorities of 40 or less from beinglaunched. Valid values are from 0 to 101.

Node The type of workstation and the type operating system of theworkstation in the following format:

os_wkstat

where os is one of the following:WNT Windows NT.UNX UNIX.MPV MPE/V.MPX MPE/IX.Other Other workstation OS.and where wkstat is one of the following:FTA Fault-tolerant agentMaster MasterManager Domain managerS-Agent Standard agentX-Agent Extended agent

Time Zone The time zone of the workstation.

Node Port The port address of the workstation.

CPU Type The scheduler workstation type. Valid values are MASTER, FTA,SAGENT or XAGENT.

Host The scheduler physical workstation that is hosting this workstationdefinition. This is only valid for Extended Agents and Network agents.

Run The run number of the production plan of the workstation. This is usedsynchronize the workstations in a scheduler network.

Start Time The date and time the batchman process was started on theworkstation.

Jobman Init Whether or not the jobman process on the workstation has completedits startup initialization. The value can be either YES or NO.

Method The method name, if this workstation is an extended agent or networkagent workstation.

Domain The name of the Workload Scheduler domain of the workstation.

Version The version of Workload Scheduler installed on this workstation.

Node Information Operating system information about the workstation.

Node Name The node name of the workstation

Displaying a Workstation InstanceTo display a workstation instance in the plan:

362 Version 8.1

1. Run a list of workstations that contains the workstation you want to display. See“Displaying a List of Workstations in the Plan” on page 361 for more information.

2. In the list results, right-click a workstation and select Properties from the pop-up menu.The Properties - Workstation in Plan window is displayed.

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. Formore 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.



¶ Click Cancel to close the window without saving your changes.

Changing the Job Limit of a Workstation in the PlanTo change the job limit of a workstation instance in the plan:

1. Run a list of workstations in the plan that contains the workstation you want to modify.

2. In the list results, right-click the workstation you want to modify or, to select more thanone workstation, do one of the following:¶ To select a range of workstations in the list, hold down the shift key and left-click

the first and last workstations in the range. Right-click on one of the selectedworkstations to open the popup menu.

¶ To select multiple workstations, hold down the control key and left-click on eachworkstation. Right-click one of the selected workstations to open the popup menu.

3. Select Limit from the pop-up menu.

Figure 214. Properties - Workstation in Plan Window


22.P

lanTasks

The Change Limit - Workstation window is displayed.

4. Specify a new job limit in the New Limit field.


¶ Click OK to save the new job limit in the plan and close the window.

¶ Click Cancel to close the window without saving the new job limit.

Changing the Job Fence of a Workstation in the PlanTo change the job fence of a workstation instance in the plan:

1. Run a list of workstation instances that contains the workstation you want to modify.

2. In the list results, right-click the workstation you want to modify, or, to select more thanone workstation, do one of the following:¶ To select a range of workstations in the list, hold down the shift key and left-click

the first and last workstations in the range. Right-click on one of the selectedworkstations to open the popup menu.

¶ To select multiple workstations, hold down the control key and left-click on eachworkstation. Right-click each of the selected workstations to open the popup menu.

3. Select Fence from the pop-up menu. The Change Fence - Workstation window isdisplayed.

4. Specify a new job fence or click of the following buttons:Hold None Sets the fence to 0.Hold All Sets the fence to 101.

When you have finished.

¶ Click OK to save the new job fence in the plan and close the window.

¶ Click Cancel to close the window without saving the new job fence.

Starting a Workstation InstanceTo start Workload Scheduler running on a workstation instance, in a list of workstations,right-click the workstation you want to start and select Start from the pop-up menu.

Note: To start all the workstations in a domain, refer to “Starting the Workstations in aDomain” on page 366.

Figure 215. Change Limit - Workstation Window

Figure 216. Change Fence - Workstation Window

364 Version 8.1

Missing or Incorrect ComponentsOccasionally, when you start a workstation, an error message might be displayedbecause of a missing or incorrect components file entry. This is because either thelocation for the components file is not the default and the variable$UNISON_COMPONENT_FILE is not set, or the entry in the/usr/unison/component file is incorrect (location incorrect).

To fix the problem, create a copy of the components file in the/usr/unison/components directory. If one already exists, modify the contents tomatch what is installed. Make sure you specify the path name of the home directory ofthe installed user. If your home directory is linked to another file system, make sureboth references are listed in the file.

Stopping a Workstation InstanceTo stop Workload Scheduler running on a workstation instance, in a list of workstations,right-click the workstation you want to stop and select Stop from the pop-up menu.

Note: To stop all of the workstations in a domain, refer to “Stopping the Workstations in aDomain” on page 366.

Linking a Workstation InstanceTo link a workstation instance, right-click the workstation you want to stop and select Linkfrom the pop-up menu.

Unlinking a Workstation InstanceTo unlink a workstation instance, right-click the workstation you want to stop and selectUnlink from the pop-up menu.

Note: To unlink all of the workstations in a domain, refer to “Unlinking the Workstations ina Domain” on page 366.

Managing Domains in the PlanYou can perform the following actions on domains in the plan:

¶ Display a list of domains. This list contains a number of fields with information aboutthe domain status.

¶ Start, stop, and link a workstation in a domain.

¶ Change the domain manager workstation in a domain.

Displaying a List of Domains in the PlanTo display a list of domains in the plan, follow these steps:


2. Expand the Default Plan Lists group.

3. Select a Status of All Domains list button.

4. Click Load List on the toolbar or right-click the domain list button and select Load Listfrom the pop-up menu.


22.P

lanTasks

The list results are displayed in the right pane of the Job Scheduling Console. Table 152describes the column headings in the domain display.

Table 152. List of Domains in the PlanThis column ... Specifies ...

Name The name of the domain.

Domain Manager The name of the domain manager workstation.

Domain Parent The name of the parent domain.

Starting the Workstations in a DomainTo start Workload Scheduler running on all of the workstations in a domain:

1. Run a list of domains that contains the domain you want to start. See “Displaying a Listof Domains in the Plan” on page 365 for more information.

2. In the list results, right-click the domain you want to start.

3. Select Start Workstations from the pop-up menu.

Note: To start individual workstations, see “Starting a Workstation Instance” on page 364.

Stopping the Workstations in a DomainTo 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 Listof 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 DomainTo 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 Listof 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 DomainTo unlink all of the workstations in a domain:

1. Run a list of domains that contains the domain you want to unlink. See “Displaying aList 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.

Note: To unlink individual workstations, see “Unlinking a Workstation Instance” onpage 365.

366 Version 8.1

Switching the Domain Manager in a DomainWhen switching domain managers to a backup domain manager, ensure the new domainmanager is a fault-tolerant agent with Full Status and Resolve Dependencies selected.

To switch the domain manager to a different workstation in a domain:

1. Run a list of domains that contains the domain you want to switch. See “Displaying aList of Domains in the Plan” on page 365 for more information.

2. In the list results, right-click the domain and select Switch Manager... from the pop-upmenu. This displays the Select Domain Manager window.

3. Click Find and use the Find window to select the name of the new domain managerworkstation. The new domain manager must be a member of the domain and it must bea fault-tolerant agent with Full Status and Resolve Dependencies selected.


¶ Click OK to switch to the new domain manager and close the window.

¶ Click Cancel to close the window without switching the domain manager.

Managing File Dependencies in the PlanA file dependency is when a job or job stream needs to verify the existence of one or morefiles before it can run.

Displaying File Dependencies StatusTo display a list of file dependencies in the plan:



3. Select the Status of All Files list button.

4. Expand the branches below the scheduler until you see the button for the file list youwant to run. See “Creating a Plan List of Files” on page 291 for information aboutcreating file lists.

Select the file list button.

5. Click Load List on the toolbar or right-click on the file list button and select Load Listfrom the pop-up menu.


Figure 217. Switch Manager - Domain Window


22.P

lanTasks

Table 153 describes the column headings in the file display.

Table 153. Status of All Files List WindowThis column ... Specifies ...

Full Path Name The path and name of the file.

Workstation The name of the workstation that owns the file.

Qualifiers Any qualifiers used with this file dependency.

Status The status of the file as one of the following:Not Checked

Not yet checked or the file was available and used tosatisfy a job or job stream dependency.

CheckingFile availability is being checked.

ExistsThe file exists and is available.

Does Not ExistThe file does not exist or is not available.

Managing Prompt Dependencies in the PlanA prompt dependency is when a job or job stream needs to wait for an affirmative responseto a prompt before it can run.

Displaying Prompt Dependencies StatusTo display a list of prompt dependencies in the plan:



3. Select the Status of All Prompts list button.

4. Click Load List on the toolbar or right-click on the prompt list button and select LoadList from the pop-up menu.


Figure 218. Status of All Files List Window

368 Version 8.1

Table 154 describes the contents of the columns in the prompt display.

Table 154. Prompt Dependencies StatusThis column ... Specifies ...

Name The name of a predefined prompt or the number of an ad hoc prompt.

Workstation The name of the workstation.

Dependency The jobs or job stream names that are dependent on this prompt.

Release Status The status of the prompt. This is one of:ASKED The prompt has been issued, but no response has

been received.NOT ASKED The prompt has not been issued.YES The prompt has been issued and a YES response has

been received.NO The prompt has been issued and a NO response has

been received.

Number The internal ID of the prompt.

Type The prompt type. This is one of:Ad Hoc The prompt is locally defined in a job or job stream.Predefined The prompt has a name and is defined in the

database.Recovery The prompt is locally defined in a job as a recovery

option.

Message Text The text of the prompt.

Replying to a Prompt DependencyTo reply to a prompt dependency:

1. Run a list of prompt dependencies that contains the prompt you want to modify. See“Displaying Prompt Dependencies Status” on page 368 for more information.

2. In the list results, right-click the prompt dependency you want to reply to or, to selectmore than one prompt dependency, do one of the following:¶ To select multiple prompt dependencies from the list, hold down the shift key and

left-click the first and last prompt dependencies in the range. Right-click one of theselected prompt dependencies to open the popup menu.

¶ To select multiple prompt dependencies, hold down the control key and left-clickeach prompt dependency. Right-click one of the selected prompt dependencies toopen the popup menu.

3. Select Reply then Yes, or Reply then No from the pop-up menu.

Managing Resource Dependencies in the PlanResources represent any type of resources on your system such as tape drives,communication lines, databases, or printers, that are needed to run a job. Resources can bephysical or logical. After defining a resource in the Workload Scheduler database, it can beused as a dependency for jobs and job streams that run on the workstation or workstationclass for which the resource is defined.

Displaying Resource Dependencies StatusTo display a list of resource dependencies in the plan:



22.P

lanTasks

2. Expand the branches below the scheduler until you see the button for the resource listyou want to run. See “Creating a Plan List of Resources” on page 289 for informationabout creating resource lists.

3. Select the resource list button.

4. Click Load List on the toolbar or right-click on the resource list button and select LoadList from the pop-up menu.


Table 155 describes the contents of the columns in the resource display.

Table 155. Resource Dependencies StatusThis 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 theresource and the number of units required.

Displaying the Properties of a Resource DependencyTo display a resource dependency in the plan:

1. In a list of resource dependencies, right-click the resource and choose Properties fromthe pop-up menu. The Properties - Resource in Plan window is displayed.

2. In this window, you can change the total number of defined units of the resource. To dothis, specify a new value in the Quantity Defined field.



¶ Click Cancel to close the window without saving your changes.

Changing the Number of Units of a Resource DependencyTo change the total number of defined units of a resource dependency:

1. Run a list of resource dependencies that contains the resource you want to modify. See“Displaying Resource Dependencies Status” on page 369 for more information.

2. In the list results, right-click the resource you want to modify.

3. Select Change Units from the pop-up menu. The Change Units - Resource in Planwindow is displayed.

4. Specify a new value in the Quantity Defined text box.


370 Version 8.1

¶ Click OK to save the new units in the plan and close the window.

¶ Click Cancel to close the window without saving the new units.

Setting an Alternate PlanYou can use the Set alternate plan function to set an old plan so that all the lists at planlevel refer to the selected plan. You can browse all objects in the alternate plan, such as jobsand job streams, but you cannot modify them.

To select a different plan to use:

¶ In the Job Scheduling view, right-click the scheduler button and select Set alternateplan from the pop-up menu. The Set Alternate Plan Files window is displayed.

Table 156 describes the columns in this window.

Table 156. Set Alternate Plan Files WindowThis column ... Specifies this ...

Schedule Date The date the file was scheduled to run.

Actual Date The date the file began running.

Log Date The date the file was logged.

Start Time The time file began running.

Run Number The run number assigned to the file by Workload Scheduler. This isused for internal network synchronization.

Log Number The log number indicating the chronological order of the log files.

Size The size of the log file, in records.

Filename The name of the file assigned by the scheduler.

Figure 219. Set Alternate Plan Files Window


22.P

lanTasks

¶ Select the plan you want to use.

¶ Click OK. You return to the Job Scheduling view.

372 Version 8.1

IV — Appendixes


374 Version 8.1

Using Common Lists

If your Job Scheduling view includes multiple scheduling engines, you can list job streaminstances and job instances for more than one engine at a time. This also applies if you havea mixed environment of Workload Scheduler for z/OS and Workload Scheduler engines.

In the Job Scheduling view, the Common Default Plan Lists group appears at the bottom ofthe job scheduling tree. The group provides two predefined lists, one for job instances andone for job stream instances. Unlike similar lists for specific engines, these lists display allthe job and job stream instances that exist in all the engines to which the Job SchedulingConsole is connected. The group always appears in the Job Scheduling tree, regardless of thenumber 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 particularstatus or a subset of all the engines. However, common plan lists are limited to job and jobstream instances. Common plan lists provide fewer details about the job and job streaminstances than engine-specific plan lists. If you are connected to a single engine, or if youwant to see more information about the instances of a specific engine, you should use theplan lists for that engine.

This chapter describes how to:

¶ Create a common list of job instances

¶ Create a common list of job stream instances

¶ Modify a common list

¶ Display a common list created previously

¶ Delete a common list

A


A.

Usin

gC

om

mo

nL

ists

Creating a Common List of Job Instances

Listing All Job InstancesTo list all the job instances existing in all the scheduling engines:

1. In the Job Scheduling view, double-click Common Default Plan Lists.

2. Double-click All Scheduled Jobs. The All Scheduled Jobs list is displayed in the rightpane of the Job Scheduling view.

Using Filter CriteriaTo create a list of job instances with different filter criteria, in the Job Scheduling view,select Common Default Plan Lists and click the List Job Instances button. The Properties- Job Instance Common List window is displayed.

Figure 220. Properties - Job Instance Common List Window

376 Version 8.1


Table 157. Properties - Job Instance List InformationIn this area ... Enter this information ...

Name Name for the list.


Apply defaultsTo use the default specified in the Settings page of theScheduler Properties window.

Filter Criteria


Job stream name Lists all the job instances that are in the job stream with this nameor namestring.

Job identifier Lists all the job instances that have this identifier. You cannot usewildcard characters with this filter.

Priority Lists all the job instances that have the priority level you select inFrom and To. The Workload Scheduler for z/OS priority is 1–10and the Workload Scheduler priority is 0–101.


Status Lists all the job instances with any of the following Job SchedulingConsole status codes that you specify in the drop-down list:¶ Waiting¶ Ready¶ Running¶ Successful¶ Error¶ Canceled¶ Interrupted¶ Undecided

Engine Lists all the connected engines. Select the engines for which youwant to display the job instances.


—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 DefaultPlan Lists group in the Job Scheduling view. Right-click the list in the Job Schedulingview 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.


A.

Usin

gC

om

mo

nL

ists

Creating a Common List of Job Stream Instances

Listing All Job Stream InstancesTo list all the job stream instances existing in all the scheduling engines:

1. In the Job Scheduling view, double-click Common Default Plan Lists.

2. Double-click All Scheduled Job Streams. The All Scheduled Job Streams list isdisplayed in the right pane of the Job Scheduling view.

Using Filter CriteriaTo create a list of job stream instances with different filter criteria, in the Job Schedulingview, select Common Default Plan Lists and click the List Job Stream Instances button.The Properties - Job Stream Instance Common List window is displayed.

Figure 221. Properties - Job Stream Instance Common List Window

378 Version 8.1


Table 158. Properties - Job Stream Instance List InformationIn this area ... Enter this information ...

Name Name for the list.


Apply defaultsTo use the default specified in the Settings page of theScheduler Properties window.

Filter Criteria


Job stream name Lists all the job stream instances that are in the job stream with thisname or namestring.

Job identifier Lists all the job stream instances that have this identifier. Youcannot use wildcard characters with this filter.

Priority Lists all the job stream instances that have the priority level youselect in From and To. The Workload Scheduler for z/OS priority is1–10 and the Workload Scheduler priority is 0–101.


Status Lists all the job stream instances with any of the following JobScheduling Console status codes that you specify in the drop-downlist:¶ Waiting¶ Ready¶ Running¶ Successful¶ Error¶ Canceled¶ Interrupted¶ Undecided

Engine Lists all the connected engines. Select the engines for which youwant to display the job stream instances.


—EITHER—


—OR—


Note: To display the list at a later date, double-click it in the scheduling tree.


A.

Usin

gC

om

mo

nL

ists

Displaying a Common ListTo display a common list that you have already created:

1. In the Job Scheduling view, double-click Common Default Plan Lists. The commonlists are displayed under this group.

2. Double-click the list you want to display. The results are displayed in the right handpane of the Job Scheduling view.

Modifying a Common ListTo modify a common list:


2. Right-click the list you want to modify and select Properties from the pop-up menu.The properties window of the list is displayed.

3. Make the changes you want.


—EITHER—


—OR—


Deleting a Common ListTo delete a common list from the Common Default Plan Lists group:


2. Right-click the list you want to delete and select Delete from the pop-up menu.

The list is deleted from the Common Default Plan Lists group.

380 Version 8.1

Setting Traces for the Job SchedulingConsole

This appendix explains how to set tracing facilities for the Job Scheduling Console.

You can set the tracing facility by customizing the TRACELEVEL and TRACEDATAvariables. These variables are located in the following files:

Table 159. Trace Variable Location by Operating SystemFor 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 valueranging from 0 to 3. Values enable you to tune the tracing facilities to report the type anddetail of data that best fits your needs.

TRACELEVEL enables you to choose what type of program information flow the tracingfacility must record, so that you can check for program correctness in terms of sequences ofinstructions. The following table displays what each value does:

TRACELEVEL Value Action

0 Only errors and warnings are recorded.

1 Errors, warnings, and info/debug lines are recorded.

2 Errors, warnings, and method entry/exit are recorded.

3 Errors, warnings, info/debug lines, and method entry/exit are recorded(maximum trace level).

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 datastructures exchanged between the Job Scheduling Console and the Workload Scheduler forz/OS Connector. The following table displays what each values does:

TRACEDATA Value Action

0 No data is traced.

B


B.

Settin

gTraces

for

the

Job

Sch

edu

ling

Co

nso

le

TRACEDATA Value Action

1 Data structures from/to the scheduler Connector are recorded.

2 The internal values of the Job Scheduling Console beans are recorded.

3 Both data structures and bean internal values are recorded (maximumtrace level).

The various combinations of values for TRACELEVEL and TRACEDATA give you themaximum flexibility in terms of information provided by the log file. However, it isimportant to point out that the combination of values of 2 or greater for TRACELEVEL andof 1 or greater for TRACEDATA can be quite heavy for system performance: they can slowprogram operation and generate very big log files.

Tracking of error conditions is active by default (TRACELEVEL is already set to 0). Youcan 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 thedirectory hosting the Job Scheduling Console files.

By default, the maximum size of JSCONSOLE.LOG can be 3 MB. When this limit isreached, the tracing facility creates an additional log file. The tracing facility can create upto ten log files for a total of 30 MB. You can, however, change this by using the advancedcustomization options described in the next section.

Using the Log File Advanced Customization OptionsThese options enable you to customize the log file produced by the tracing facilities. Theyare listed under a section named [trace] inside of the JSS.INI file in the \dat\.tmeconsolesubdirectory of the directory hosting the Job Scheduling Console files. The options, and theirdefault values, are listed in JSS.INI as shown below:[trace]traceFileMaxLen=3000000traceFileMaxNum=10printTimeDate=trueprintMillisecond=falseprintThreadID=falseprintComponent=falseprintType=true

where:

traceFileMaxLenDefines the maximum size, in bytes, that the log file can be. When the file reaches thissize, it is renamed and a new log file is created. The value is an integer of your choice.

traceFileMaxNumDefines the maximum number of log files that can be present on disk during eachinstance of the Job Scheduling Console. When this number is exceeded, the older filesare replaced first. This includes only the files created during the current session of theJob Scheduling Console. You have to manually delete the files stored during previoussessions. The value is an integer of your choice.

printTimeDateSpecifies if the trace calls write date and time information in the log file. The value canbe True or False.

382 Version 8.1

printMilllisecondSpecifies if the trace calls write timestamp information, in milliseconds, in the log file.The value can be True or False.

printThreadIDSpecifies if the trace calls write an identifier for the current thread in the log file. Thevalue can be True or False.

printComponentSpecifies if the trace calls write the name of the source component in the log file. Thevalue can be True or False.

printTypeSpecifies if the trace calls write the message type (error, warning or information) in thelog file. The value can be True or False.

traceFileMaxLen and traceFileMaxNumUse to decide how much disk space you want to allocate to the tracing facility. Theyenable you to achieve a correct trade-off between disk space occupancy and debug dataavailability.

Use the other options to determine what type of information you want included in the tracefile.


B.

Settin

gTraces

for

the

Job

Sch

edu

ling

Co

nso

le

384 Version 8.1

Enabling Time Zones in the WorkloadScheduler

Enabling time zones in Tivoli Workload Scheduler enables you to manage your workload ona global level. Time zone implementation also allows for easy scheduling across multipletime zone and for jobs that need to run in the ″dead zone.″ The dead zone is the gapbetween the Workload Scheduler start of day time on the master and the time on thefault-tolerant agent in another time zone. For example, if an eastern master with a WorkloadScheduler start of day of 6 AM initializes a western agent with a 3-hour time zonedifference, the dead zone for this fault-tolerant agent is between the hours of 3 AM and 6AM. Previously, special handling was required to run jobs in this time period. Now whenspecifying a time zone with the start time on a job or job stream, Workload Scheduler runsthem as expected. For example, consider the following two job streams for a PSTfault-tolerant agent with an EST master:

Schedule PST_SCHEDULE1 Schedule PST_SCHEDULE2On SU, weekdays except FR on weekdaysCARRYFORWARD AT 0330 TZ PSTAT 0330 :: jobajob1 jobbjob2 ENDEND

Job stream PST_SCHEDULE1 is not time zone enabled. To get this job stream to run everyweekday morning, you must schedule it to run Sunday through Thursday, and you mustspecify ″carryforward″. Without carryforward, the jobs would never run, since thefault-tolerant agent would be initialized at 0300 every morning (assuming an EST masterwith a Workload Scheduler start of day of 0600). Job stream PST_SCHEDULE2 is timezone enabled. When the EST master initializes the PST fault-tolerant agent at 0300, it startsthe job stream the same day at 0330.

Time zone enabling also has an effect on eastern fault-tolerant agents when scheduling fromwestern masters. For example, consider the following two job streams for an ESTfault-tolerant agent and a PST master with an 0600 start of day.

C


C.

En

ablin

gTim

eZ

on

esin

the

Wo

rkload

Sch

edu

ler

Schedule EST_SCHEDULE1 Schedule EST_SCHEDULE2On SU, weekdays except FR On SU, weekdays except FRAT 0800 + 1 DAY AT 0800 TZ ESTCARRYFORWARD :: jobajob1 jobbjob2 ENDEND

Job stream EST_SCHEDULE1 is not time zone enabled. For this job stream to run everyweekday morning, you must schedule it to run Sunday through Thursday. Specifycarryforward and +1DAY for the AT time. Carryforward is needed for the +1DAYspecification. Without the +1DAY specification, the job stream would launch immediatelyafter initialization from the western master at 0900. Job stream EST_SCHEDULE2 is timezone enabled. When the eastern fault-tolerant agent is initialized at 0900, it runs the jobstream at 0800 the next day.

Once enabled, time zones can be specified in the Job Scheduling Console or composer forstart and deadline times within jobs and job streams. For conman, the following commandsnow 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

Enabling the Time Zone FeatureThe time zone feature is enabled by an entry in the globalopts file and by specifying a timezone in the master workstation definition, as follows:timezone enable = yes|no

Time zones are disabled by default on installation or update of the product. If the timezoneenable entry is missing from the globalopts file, time zones are disabled.

386 Version 8.1

Status Description and Mapping

This Appendix provides information about job and job stream status for the Job SchedulingConsole and Workload Scheduler.

For information about job and job stream status for Workload Scheduler for z/OS, refer toTivoli Workload Scheduler for z/OS Controlling and Monitoring the Workload.

Status OverviewThere are two types of status:

Job Scheduling Console statusThis is a subset of internal status and is common for both Workload Scheduler andWorkload Scheduler for z/OS.

Internal StatusThis refers to the Workload Scheduler internal or engine status for the job or jobstream. The internal status messages are unique to the scheduler.

Job StatusThis section describes the job status for both Job Scheduling Console and WorkloadScheduler internal status.

Job Scheduling Console Job StatusBelow are listed possible job states and descriptions:

Table 160. Job Scheduling Console Job StatesThis 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 andthe 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.

D


D.

Statu

sD

escriptio

nan

dM

app

ing

Workload Scheduler Internal Job StatusBelow are listed possible job states and descriptions:

Table 161. Workload Scheduler Internal Job StatesThis job status ... Means that ...

ABEND The job terminated with a non-zero exit code.

ABENP An ABEND confirmation was received, but the job is not completed.

ADD The job is being submitted.

DONE The job completed in an unknown state.

ERROR For internetwork dependencies only, an error occurred while checkingfor the remote status.

EXEC The job is running.

EXTRN For internetwork dependencies only, the status is unknown. An erroroccurred, a rerun action was just performed on the job in the externaljob stream, or the remote job or job stream does not exist.

FAIL Unable to launch the job.

FENCE The job’s priority is below the fence.

HOLD The job is awaiting dependency resolution.

INTRO The job is introduced for launching by the system.

PEND The job completed, and is awaiting confirmation.

READY The job is ready to launch, and all dependencies are resolved.

SCHED The job’s at time has not arrived.

SUCC The job completed with an exit code of zero.

SUCCP A SUCC confirmation was received, but the job is not completed.

SUSP The job was suspended by a breakjob command. (MPE only)

WAIT The job is in the wait state. (Extended agent and MPE only)

WAITD The job is in the wait state, and is deferred. (MPE only)

Job Stream StatusThis section describes the job stream status for both Job Scheduling Console and WorkloadScheduler internal status.

Job Scheduling Console Job Stream StatusBelow are listed possible job stream states and descriptions:

Table 162. Job Scheduling Console Job Stream StatesThis 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 andthe 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.

388 Version 8.1

Table 162. Job Scheduling Console Job Stream States (continued)This job status ... Means that ...

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.

Workload Scheduler Internal Job Stream StatusBelow are listed possible job stream states and descriptions:

Table 163. Workload Scheduler Internal Job Stream StatesThis job status ... Means that ...

READY The dependencies for the job stream have been met but the timerestrictions for the job stream have not.

HOLD The job stream instance is awaiting dependency resolution.

CANCEL PEND The job stream instance is pending cancelation. Cancelation is deferreduntil all of the dependencies, including an at time, are resolved.

EXEC The job stream instance is running.

STUCK Job stream instance ion was interrupted. No jobs are launched withoutoperator intervention.

ABEND The job stream instance terminated with a non-zero exit code.

SUCC The job stream instance completed successfully.

CANCEL The job stream instance was canceled.

ADD The job stream instance was added with operator intervention.

EXTRN The job stream instance is in a remote Workload Scheduler networkand its status is unknown. An error occurred, a Rerun action wasperformed on the EXTERNAL job stream, or the INET job or jobstream does not exist.

ERROR This is for Internetwork job streams and specifies that an erroroccurred while checking for the remote status.

Status MappingThis section provides a table of how Job Scheduling Console status maps to WorkloadScheduler internal status for jobs and job streams.

Job Status MappingTable 164 describes how Job Scheduling Console status correlates to Workload Schedulerinternal status for jobs.

Table 164. Job Status MappingThis 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


D.

Statu

sD

escriptio

nan

dM

app

ing

Table 164. Job Status Mapping (continued)This console status ... Maps to this Workload Scheduler internal status ...

CANCELED Status of the job when it was canceled. Canceled flag is set.

HELD Priority = 0, WAITING, READY

UNDECIDED ERROR, EXTRN

BLOCKED SUSP

Job Stream Status MappingTable 165 describes how Job Scheduling Console status correlates to Workload Schedulerinternal status for job streams.

Table 165. Job Stream Status MappingThis console status ... Maps to this Workload Scheduler internal status ...

WAITING ADD, PEND, WAIT, WAITD, INTRO, HOLD

READY READY

RUNNING EXEC

SUCCESSFUL SUCC

ERROR ABEND, FAIL

CANCELED CANCEL, HOLD, CANCEL P

HELD HOLD

UNDECIDED EXTRN, ERROR

BLOCKED STUCK

390 Version 8.1

Job Scheduling Console Messages

Job Scheduling console message numbers have a GJS prefix and are followed by a letterindicating the type of message:

E Error

I Information

W Warning

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

GJS0008E Cannot open the Job Stream Editor

GJS0009E Cannot open the Job Stream Instance Editor

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

E


E.

Job

Sch

edu

ling

Co

nso

leM

essages

GJS0032E Cannot process OK request

GJS0033E Cannot change the job

GJS0034E Cannot add the new job

GJS0035E Cannot modify the instance

GJS0036E Cannot delete the instance

GJS0037E Cannot hold the instance

GJS0038E Cannot release the instance

GJS0039E Cannot delete the object

GJS0040E Cannot undelete the object

GJS0041E Cannot modify the status in the database

GJS0042E Cannot remove the job

GJS0043E Cannot remove the job dependency

GJS0044E Cannot remove the dependency

GJS0045E Cannot remove the external dependency

GJS0046E Cannot perform the action on the selected objects

GJS0047E Cannot perform the job stream operation

GJS0048E Cannot perform the action on the selected object

GJS0049E Cannot perform the action on the selected objects

GJS0050E Cannot update the instance from services

GJS0051E Cannot perform the action specified on the selected object

GJS0052E Cannot perform the action specified on the selected objects




GJS0060E Cannot delete the selected workstations

GJS0061E Cannot add schedule specifications

GJS0062E Cannot create another run cycle

GJS0063E Cannot perform this action

GJS0064E Cannot interrupt the operation

GJS0065E Cannot delete the resource

GJS0066E Cannot delete the selected resources

GJS0067E Cannot get the resource header

GJS0068E Cannot open the resource

GJS0069E Cannot save resource dependency changes

GJS0070E Cannot add scheduling specifications

392 Version 8.1

GJS0071E Cannot add scheduling specifications

GJS0072E Cannot process the OK request

GJS0073E You are renaming a resource

GJS0074W You are renaming a workstation

GJS0075E Cannot open the resource

GJS0076E Cannot open the workstation

GJS0077E This object is currently locked because it is being updated by another user. Itwill be displayed in read-only mode until the user releases it. Try again later.

GJS0078E Error logging in to the TMR host

GJS0079E Cannot link to the connector

GJS0080E Cannot detach the view

GJS0081E Cannot save the job stream

GJS0082E Cannot paste the external dependency

GJS0083E Cannot find the objects you are searching



GJS0086E You are renaming a job stream

GJS0087E Selected engine not available

GJS0088E Cannot attach the view

GJS0089E Cannot load workstation plan view

GJS0090E Cannot load the Job output

GJS0091E Cannot load the Job output

Messages Originated by Workload Scheduler for z/OSAll Job Scheduling Console messages that contain the GJSQ prefix refer to WorkloadScheduler for z/OS error conditions. The explanation of each message displays a specificWorkload 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/OSMessages and Codes book.


E.

Job

Sch

edu

ling

Co

nso

leM

essages

394 Version 8.1

Glossary

A

Actual start timeThe time, as logged, at which the job or job stream instance started.In the timeline, the actual start time isrepresented by a black bar running down the center of the navy blue activity bar. See also earliest start time andplanned start time.

C

CalendarA definition of workdays, free days, and holidays. The scheduler uses the calendar combined with run cycles todetermine 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

DatabaseA collection of data that is fundamental to a system. The database for each engine contains calendars, JCLvariable tables, job streams, operator instructions, periods, resources, and workstations. In the Job SchedulingConsole, you can define and modify job streams, resources, and workstations. This information is stored in thedatabase of the engine and is used to generate instances for the plan.

DeadlineThe time by which the job or job stream must be completed. The deadline is your estimate, based on yourexperience in running the job or job stream. In the timeline, the deadline is represented by the black border at theright end of the navy blue activity bar.

DependencyA relationship between two jobs in which the first job must be completed before the second can begin. When youcreate a job stream in the database, you define the dependencies between jobs

DLFData Lookaside Facility. The z/OS component that manages Hiperbatch objects.

DurationThe time you expect the job to take to complete. In the Timeline view of jobs in the database, the duration isrepresented by a light blue bar at the center of the activity bar or by a light blue diamond.

E

Earliest start timeThe time before which the job or job stream cannot start. The earliest start time is your estimate, based on yourexperience in running the job or job stream. The job or job stream can, however, start after the time you specifyas long as all other dependencies are satisfied. In the timeline, the start time is represented by the beginning (leftedge) of the navy blue activity bar. For job instances, the start time that the scheduler calculates is represented bya light blue bar. See also actual start time and planned start time.

Exclusionary run cycleA run cycle that specifies when a job stream must not run.

External jobA job from one job stream that is a predecessor for a job in another job stream. An external job is represented bya place holder button in the Graph view of the job stream. When you delete an external job either from thedatabase or the plan, the job stream that includes it as a predecessor skips it as if it did not exist, and thescheduler logs the error.


Glo

ssary

F

Fault-tolerant workstationThe CPU that runs a job stream that is scheduled in the plan.

Free day ruleDetermines how to calculate free days when scheduling the job stream. The following are free day rules: Countworkdays only. Count workdays and free days alike. Schedule on the last workday before free day. Schedule onthe next workday after free day. Do not schedule if free days.

H

HiperbatchThe z/OS facility that stores VSAM and QSAM data in Hiperspace for access by multiple jobs. The facility cansignificantly reduce the run time of certain batch streams that access VSAM and QSAM.

J

JobA unit of work in a job stream that is processed at a workstation. It usually includes all necessary computerprograms, linkages, files, and instructions to the operating system. When you create a job in the database, youalso define its dependencies on predecessor jobs and its time restrictions, such as the estimated start time anddeadline. The type of job determines the type of target workstation on which it can run: JCL jobs consist of JCLstatements and run on computer workstations. Started task jobs start or stop started tasks and run on computerworkstations. Printer jobs print the output of a predecessor job and run on printer workstations. General jobsinclude 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 generalworkstations. Write-to-operator (WTO) jobs consist of an operator instruction displayed on the system consoleand run on general workstations. Fault tolerant workstation jobs are used to run jobs from Tivoli WorkloadScheduler. They require fault tolerant workstations. Fault tolerant workstation jobs can have neither a general jobas a predecessor nor a printer job as a successor. See also job instance.

Job instanceA job scheduled for a specific run date in the plan. See also job.

Job scheduling objectA generic term that includes jobs, job streams, resources, and workstations.

Job statusSee status

Job streamA sequence of jobs, including the resources and workstations that support them, and scheduling information. Thedependency of one job on the completion of another determines the sequence of the jobs. The schedulinginformation, such as run cycles and a calendar, determines when and how often the job stream is run. See alsojob stream instance.

Job stream instanceA job stream that is scheduled for a specific run date in the plan. See also job stream.

Job stream templateAn entity that contains scheduling information, such as a calendar, a free day rule, and run cycles, that can beinherited by all the job streams that have been created using the template. Unlike typical templates, job streamscreated from a job stream template continue to be part of the template and any changes to the schedulinginformation for the template are inherited by the job streams. Therefore, you do not define run cycles for jobstreams created from a template.

396 Version 8.1

L

ListA list displays job scheduling objects. You must create separate lists for each job scheduling object. For each jobscheduling object, there are two types of lists: one of definitions in the database and another of instances in theplan.

Logical resourceSee resource.

P

PlanA detailed plan of system activity that covers a period of at least one minute and not more than 21 days. Ittypically covers one or two days. The plan encompasses all job and job stream instances and the resources andworkstations involved in running them. All job streams for which you have created run cycles are automaticallyscheduled and included in the plan. Contrast with database.

Planned start timeThe estimated start time, based on the duration of predecessors, that the scheduler makes for when the jobinstance should start. See also actual start time and earliest start time

PredecessorA job that must be completed before jobs that are dependent on it can begin. Contrast with successor.

R

ResourceAny type of limited resource, such as tape drives, communication lines, databases, or printers, that is needed torun a job. You designate when a resource is available, in what quantities, and by which logical workstations theresource can be used. This information helps determine when job stream instances are scheduled to run. In theJob Scheduling Console, resources are also called logical resources.

Resource availabilityFixed times when the job can use a resource. You define conditions, similar to run cycles, that generate thecalendar days when a resource is available. You can also define conditions for when a resource is not available.

Run cycleA 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 runcycle.

S

StatusThe 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 nonreportingworkstation, 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.


Glo

ssary

SuccessorA job that cannot start until all of the jobs on which it has a dependency are completed. Contrast withpredecessor.

V

Valid from, to datesThe interval for which a job stream is available for scheduling and can be run. The first and last date that a runcycle is in effect.

W

WorkstationThe logical machine on which a job runs. When you create a job, you identify at least one workstation on whichit will run. There are three types of workstations: Computer, Printer, General.

WTOWrite-to-operator. See also job.

398 Version 8.1

Index

Aadd link between jobs 236adding a job to a job stream 227adding dependencies between jobs 236adding file dependencies

job 231job instance 302job stream instance 322

adding predecessorsjob instance 308job stream instance 328

adding prompt dependenciesjob 232job instance 304job stream instance 324

adding resource dependenciesjob 230job instance 306job stream instance 326

adding run cycles 237adding time restrictions

job 229job instance 300job stream instance 321

adhoc job 349allocation options 175Authority group 81, 111

Bbackup domain manager, requirements 367books

feedback xxixonline xxixordering xxix

Ccalendar 63, 73, 81, 111

creating 267database list 269deleting 269modify 269view properties 269

calendar run cycle 242cancelling a job instance 314cancelling a job stream instance 330changing number of resource units 370changing the job fence, workstation 364

changing the job limitjob stream instance 331workstation 363

changing the priorityjob instance 297job stream instance 331

closing the job stream editor 247complete 57, 63confirming a job instance 315connected workstations 73connector

prerequisites 13, 17, 25control on servers 58creating a calendar 267creating a domain 261creating a group of lists 279creating a parameter 276creating a prompt 274creating a resource 271creating a user 263creating run cycles 237Customer Support xxxii

Ddata lookaside facility 71date 63, 73, 76deadline 88deleting a calendar 269deleting a domain 263deleting a parameter 278deleting a prompt 276deleting a resource 273deleting a run cycle 244deleting a user 266deleting predecessors

job instance 309job stream instance 328

dependency filter windowjob stream instance 284, 288

directory names, notation xxxiiidisplaying predecessors


displaying successorsjob instance 309job stream instance 328

DLF attribute 75, 76, 175domain

creating 261database list 262deleting 263


Ind

ex

domain (continued)modify 263starting the workstations 366view properties 262view status 365

dumpsec 31duration 57, 59

Ee-mail contact xxxiearliest start time 88enabling the time zone feature 386environment variables, notation xxxiiiexclusive 71, 175external dependencies

deleting 227external job 92

adding to a job stream 226, 235external job stream

adding to a job stream 226, 234

Ffeedback about publications xxxifile dependency

adding to a job 231status 367

find calendar window 81find workstations 63finding objects in the plan 293follows dependency 236freedays 81from time 63, 73

Gglobalopts file

time zone feature 386graph view 113

Hhiperbatch 71, 75, 175holding a job instance 309holding a job stream instance 329holidays calendar 266

Iinternetwork dependency

adding to a job 233adding to a job stream 226

interrupted 58Is available 63, 71, 73ISPF 57

JJCL 58, 111job definition

adding to a job stream 227properties 227

job fence, changing 364job instance

adding predecessors 308cancelling 314confirm 315deleting predecessors 309displaying successors 309holding 309killing 314modifying 297predecessors 307release all dependencies 315releasing 310rerun 313submitting into the plan 336

job instance propertiesfiles 302prompts 304resources 306time restrictions 300

job instances 55, 119, 123, 137, 175job limit, changing for a workstation 363job properties

files 231prompts 232resource 230time restrictions 229

Job Scheduling view 75, 110, 175job stream

adding run cycles 237saving 247submit into plan 335

job stream editor 113job stream instance

cancelling 330commands 316hold 316holding 329job limit 331list view 318modifying 319plan list 316priority 331release 316release all dependencies 316, 332

400 Version 8.1

job stream instance (continued)releasing 329resubmit 316resubmitting 333timeline view 317

job stream instance propertiesfiles 322general 319predecessors 327prompt 324resource 326time restrictions 321

job stream instances 119, 127

Kkilling a job instance 314

Llinking a workstation 365linking workstations, domain 366list view 138


listing domains in the plan 280listing file dependencies in the plan 291listing job instances in the plan 284, 294listing job streams in the plan 281listing parameters in the database 277listing prompts in the database 275listing prompts in the plan 290listing resources in the database 272listing resources in the plan 289listing workstations in the plan 279, 361

Mmanuals

feedback xxixonline xxixordering xxix

modifying a domain 263modifying a job instance 297modifying a parameter 278modifying a prompt 275modifying a resource 273modifying a run cycle 244modifying a user 265modifying file dependencies


modifying prompt dependenciesjob instance 304job stream instance 324

modifying resource dependenciesjob instance 306job stream instance 326

modifying time restrictionsjob instance 300job stream instance 321

Nnotation

environment variables xxxiiipath names xxxiiitypeface xxxiii

Ooccurrence 119online publications xxxoperations 57, 58ordering publications xxxi

Pparallel server 58parameter

creating 276database list 277deleting 278modifying 278properties 277

path names, notation xxxiiiplan 59, 119plan list

deleting 292detaching 292modifying 292

plan lists 279planning on servers 58predecessor job 59priority 81prompt

creating 274deleting 276listing 275modifying 275properties 275replying 369status 368

publicationsfeedback xxixonline xxixordering xxix


Ind

ex

Qquantity 63, 71, 73

Rready 57, 58release all dependencies


releasing a job instance 310releasing a job stream instance 329replying to a prompt 369reporting attributes 66, 83, 163rerunning a job instance 313resource

adding to a job 230changing units 370creating 271database list 272deleting 273modifying 273properties 272status 369viewing plan properties 370

Resource Description database 175resubmit a job stream instance 333run cycle

adding to a job stream 237calendar 242deleting 244modifying 244simple 239weekly 240

Ssaving a job stream 247scheduling 55, 58, 75, 175search tool 73security 31setting priority


shared 71, 175simple run cycle 239special resources 69specifying job properties 227start time 88, 144started 57, 58, 59, 71starting a workstation 364starting workstations, domain 366status

workstation 362status of job stream 111stopping a workstation 365stopping workstations, domain 366

submitting a job into the plan 336submitting a job stream into the plan 335submitting an adhoc job into the plan 349switch manager command 367switching domain managers 367

Ttarget workstation 83task name 111TCP/IP 59tempsec 31time restrictions 88

job 245job stream 244

timeline viewjob instance 296job stream instance 317

Timeline view 104, 138Tivoli Customer Support xxxiito time 63, 73transport time 59treat input as 75, 175

Uunlinking a workstation 365unlinking workstations, domain 366user

creating 263deleting 266listing 264modifying 265

using plan lists 279

Vvariables, notation for xxxiiiviewing calendars in the database 269viewing domain status 365viewing domains in the database 262viewing parameter properties 277viewing prompt properties 275viewing prompt status 368viewing resource properties 272viewing resource properties in the plan 370viewing resource status 369viewing the properties of a domain 262viewing the status of a workstation 362viewing users in the database 264

402 Version 8.1

Wwaiting 175weekly run cycle 240wildcard characters 175wmaeutil 32workdays 81workstation

linking 365properties 362starting 364stopping 365unlinking 365

workstation resources 55, 63workstation type 58wuninst 16


Ind

ex

404 Version 8.1

Program Number: 5697-WSZ

Printed in Denmark by IBM Danmark A/S

SH19-4552-00

tivoli guide

Documents