Tivoli® Workload Scheduler Job Scheduling Console

User’s Guide
V ersion 8.1
SH19-4552-00

Tivoli® Workload Scheduler Job Scheduling Console
User’s Guide
V ersion 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 License Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporation copyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. The document is not intended for production and is furnished “as is” without warranty of any kind. All warranties on this document are hereby disclaimed, including the warranties of merchantability and fitness for a particular purpose. U.S. Government Users Restricted Rights—Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Trademarks IBM, Tivoli, the Tivoli logo, AIX, BookManager, Hiperbatch, OS/390, RACF, and z/OS are trademarks or registered trademarks of International Business Machines Corporation or Tivoli Systems Inc. in the United States, other countries, or both. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marks of others. Notices References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or other legally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.

ISO 9001 Certification This product was developed using an ISO 9001 certified quality system. Certification has been awarded by Bureau Veritas 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
Who Should Read This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii What This Guide Contains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix Tivoli Workload Scheduler for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix Tivoli Workload Scheduler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx Accessing Publications Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx Workload Scheduler for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi Ordering Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi Providing Feedback about Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi LookAt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxii Conventions Used in This Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxii Typeface Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxii Operating System-dependent Variables and Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxiii Other Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxiii

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

1

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Tivoli 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 . . . . . . . . . . . . . . . . . . . . 13
Before Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Setting the Tivoli Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Installing from the Tivoli Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Installing from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Tivoli Job Scheduling Console User’s Guide iii

Uninstalling Job Scheduling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Installing Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 3. Installing the Tivoli Workload Scheduler for z/OS Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Before Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 Installing Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Useful Framework Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 4. Installing the Tivoli Workload Scheduler Connector . . . . . . . . . 25
Before Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 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 Installing Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

iv

Version 8.1

Updating Workload Scheduler Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Useful Framework Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 5. Installing the Tivoli Job Scheduling Console. . . . . . . . . . . . . . . . . 33
Before Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 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 . . . . . . . . . . . . . . . . . . . 41
The 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 Workload Scheduler for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

51

Chapter 7. Managing Workstations in the Database . . . . . . . . . . . . . . . . . . . . . 55
Creating a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 General Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Defining Open Time Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Managing Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Tivoli Job Scheduling Console User’s Guide v

Default Workstation Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Creating a List of Workstations in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Using Workstation Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 8. Managing Resources in the Database . . . . . . . . . . . . . . . . . . . . . . . . 69
Creating 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Specifying 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 . . . . . . . . . . . . . . . . . . . . . . . . 109
Default Job Stream List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Creating a Job Stream List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Displaying a Job Stream List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

vi

Version 8.1

. . 139 General Page . . . . . . . 137 Job Instance Lists . . . . . . . . . . . . . . . . . . . 128 Using the Time Restrictions Page. . . . . . . . . . . . 135 Chapter 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Deleting a Job Stream Instance . . 128 Using the General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Rescheduling the Start Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 List View . . . . . . . . . . . . . . . . . . . . . . 134 Setting a Job Stream Instance to Complete. . . . . . . . . . . . . . . . . . . . . 114 Viewing and Modifying Time Restrictions . 119 Listing Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Timeline View . . . . . . . . 112 Modifying Job Stream Properties . . . . . . . . . . . . . . . . . . . . . . 133 Rescheduling the Deadline Time . . 134 Rerunning a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Job Streams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Using Existing Definitions to Create Other Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Changing Time Restrictions in the Timeline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Browsing and Modifying Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 List View . . . . . . . . . . 127 Timeline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Tivoli Job Scheduling Console User’s Guide vii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Additional Options . . . . 113 Adding and Modifying Jobs and Dependencies in the Graph View . . . . . . . . . . . . . Listing Job Stream and Job Instances . . . . . . . . . . . . . 115 Using Copy to Add an External Job . . . . . . . . . . . . . . . . . 130 Rescheduling the Instance . . . . . . . . . . . . . . . . 123 Chapter 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Job Stream Instance Lists . . . . . . . . . . . . . 119 Creating Lists of Job Stream and Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Listing Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Deleting Job Streams from the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Setting a Job Stream Instance to Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Browsing and Modifying Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Chapter 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Default Instance Lists . . . . . . . . . . . . . . . . . . . . . . . 113 Adding and Modifying Run Cycles . . . .Modifying Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Restart and Cleanup. . 142 Details Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Displaying Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Changing Time Restrictions in the Timeline View . . . 158 Running a Job Instance Immediately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Browsing the Job Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Chapter 14. . . . . . . . 172 Chapter 15. . . . . . . . . . . . . . . . . . . . 176 viii Version 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Job Summary Page . . . . . . 159 Viewing Operator Instructions . . . . . . . . . . . 156 Set as Root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Browsing and Modifying Workstation Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Modifying the Job Instances Scheduled on a Workstation . . . . . 166 Open Time Intervals Page . . . . . . . . . . 170 Displaying by Status the Job Instances Scheduled on a Workstation . . . . . . . . . . . . . . . . . . . . 155 Showing Predecessors and Successors . . . . . . . .Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Displaying Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Resources in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Removing a Job Instance from the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Browsing and Modifying Job Dependencies . . . . 173 Creating a List of Resources . . . . . . . . . . . . . . . . . .1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Changing Workstation Status and Rerouting Scheduled Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Changing the Status of a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Editing JCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Resources Page . . . . 162 Displaying Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Linking Fault-Tolerant Workstations. . . . . . . . . . . . . . 155 Releasing Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Modifying Job Setup . . . . . . . . . . . . . 152 Deleting Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Workstations in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Putting Job Instances on Hold . . . . . . . . . . . . . . . . . 161 Creating a List of Workstations . . . . . . . . . . 157 Restoring a Job Instance to the Plan. . . . . . . . . . . . . . . . . . . . . . . . 143 Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . .

Browsing and Modifying Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Chapter 16. . . . . . . . . . . . . . . . . 209 Displaying Job Definition Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Part III. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Working with Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Displaying a Job Definition . . . . . . 199 Deleting a List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Creating a List of Calendars . . . . . . 201 General Page . . . . . 190 Creating a List of Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Displaying a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Creating a List of Resources . . . . . . . . . . . . . . 181 Modifying Job Instances Associated with a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Creating a List of NT Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Tivoli Job Scheduling Console User’s Guide ix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Creating Lists . . . . . . . . . . . 199 Finding Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Creating a List of Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Creating a List of Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Creating a List of Prompts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Creating a List of Workstations . . . . . . . . . . . . 190 Creating a List of Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Deleting Job Definitions . 199 Chapter 17. . . . . . . . . . . . . . . . . . . . . . 201 Creating a Job Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Job Scheduling Console with Tivoli Workload Scheduler. . . . . . . . 198 Detaching a List Display . . 193 Creating a List of Workstation Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Displaying the Job Instances Associated with a Resource . . . . . . . 202 Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Default Workstations Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Creating a Group for Database Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Displaying a List of Job Definitions. 209 Modifying a Job Definition . . . . . . . . . . . . . . . . . . . Managing Database Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Modifying a Database List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Availability Intervals Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . 249 Deleting an Internetwork Dependency in a Job Stream . . . 234 Adding an External Job to a Job Stream . .Chapter 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Modifying an External Job Stream in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Cloning the Job Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Creating Dependencies Between Jobs in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Adding an External Job Stream to a Job Stream. . . . . . . . . . . . . . . . . . . . . . . 249 Modifying a Job in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Specifying Time Restrictions in the Timeline View. . . . . . . . . . 236 Specifying Run Cycles for a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Specifying Job Stream Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Specifying Simple Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Copying and Pasting Jobs . . . . . . . . . . . . . . . . . . . . 250 x Version 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Saving a Job Stream in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 Closing the Job Stream Editor . . . . . . . 242 Modifying Run Cycles for a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Adding External Dependencies for a Job Stream .1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Creating a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Deleting a Job in a Job Stream . . . . . . . . . . . . . . . . . . 233 Adding an Internetwork Dependency to a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 Displaying a List of Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Run Cycle View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Job Streams. . . . . . . . . . . . . . . . . . . . . . . . 244 Specifying Time Restrictions for a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Adding a Job to a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . 244 Deleting Run Cycles from a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 Displaying a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Modifying an Internetwork Dependency in a Job Stream . . . . . . . . . . . . . . . 237 Rule for Freedays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Graph View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Specifying Weekly Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Colored Bars on Dates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Modifying a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . 225 Deleting External Dependencies from a Job Stream . . . . 213 Timeline View . . . . . . . . . . . . . . . . 244 Specifying Time Restrictions for a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Inclusionary or Exclusionary Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Specifying Calendar Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Using the Job Stream Editor . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Creating a Workstation Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Modifying a Workstation Class . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Deleting Workstations . . . 265 Deleting Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 Modifying a Domain in the Database . . . . . . 250 Chapter 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Displaying a List of Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 Creating a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Freedays Calendars . . . . . . . . . . . . . . . . . . . . . . 251 Displaying a List of Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Modifying a Workstation . . . . . . . . . . . . . . . . . . . . . . . . 264 Displaying a User . . . . . . . 257 Displaying a List of Workstation Classes . . . . . . . . . . . . . . . . . 263 Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 Displaying a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 Managing Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Creating a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Deleting Workstation Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Deleting Domains in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Displaying a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Chapter 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Creating a Calendar in the Database. . . and Calendars . . . . . . . . . . . . . . . . . . . . . . . . 250 Deleting Job Streams . . . . . . . . . . . . . . . . . 267 Displaying a List of Calendars . 250 Deleting an External Job in a Job Stream. . . . . . 261 Managing Domains . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Modifying a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 Displaying a List of Domains . . . . . . . . . . . . . . . . 269 Tivoli Job Scheduling Console User’s Guide xi . . . . . . . . . Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Managing Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Displaying a Workstation Class . . . . . 250 Modifying an External Job in a Job Stream . . . . . . . . . . . . . 257 Managing Workstation Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Workstations and Workstation Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Creating a Workstation by Copying Another Workstation . . . . . . . . . .Deleting an External Job Stream in a Job Stream . . . 266 Changing User Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Viewing Calendar Properties . . . . . . . . . . . 251 Creating a Workstation . . . . . 266 The Holidays Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Creating a Plan List of Workstations . . . . . . . . . . . . . . . . . 273 Deleting Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Creating a Plan List of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Deleting Prompts. . . Plan Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Using Plan Lists . . . . . . . . . . . . . . . . . . . . . . . 292 Finding Objects in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Creating a Resource. . . . . . . . 280 Creating a Plan List of Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Creating a Resource by Copying Another Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 Deleting Parameters. . . 269 Deleting Calendars . . . . . 277 Displaying a Parameter . . . . . . . . . . . . . . . . . . . . . . . . 272 Modifying a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 . . . . . . . . . . . . . . . . 276 Displaying a List of Parameters . . . . 289 Creating a Plan List of Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Displaying a List of Resources . 279 Creating a Group for Plan Lists . . . . . . . . . . . . . . . Prompts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Detaching a Plan List Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 xii Version 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Creating a Prompt . . . . . . . . . . . . . . . . . .Modifying a Calendar in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Modifying a Parameter in the Database . . . . . . . . . 281 Creating a Plan List of Job Instances . . . . . . . . . . . . . . . . . . . . and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Deleting a Plan List. . . . . 273 Managing Prompts in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 Modifying the Properties of a Plan List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Managing Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Displaying a Resource . . . . . . . . . . . . . . . 269 Chapter 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Creating a Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Managing Job Instances in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Modifying a Prompt in the Database . . . . . . . . . . . . . . . . . . 275 Displaying a Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 Chapter 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 Creating a Plan List of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Creating a Plan List of Domain Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Managing Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Displaying a List of Jobs in the Plan . . . . . . . . . . . . . . . . . . . . 274 Displaying a List of Prompts . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Displaying Dependencies of a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . 331 Releasing a Job Stream Instance from Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 Killing a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 Canceling a Job Instance . . . . . . . . . 314 Confirming a Job Instance SUCC or ABEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 Showing Predecessors and Successors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Submitting a Job Stream into the Plan . . . . . . . . . . . . . . . . . . . . . . . 336 Viewing or Modifying the Properties of the Job to Submit . . . . . . . 330 Changing the Job Limit of a Job Stream Instance. . . . . . . . . . . . . 309 Releasing a Job Instance . . . . . . . . . . . . . . . . . . . . . . . 361 Displaying a List of Workstations in the Plan. . . . . . 311 Browsing the Job Log . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Displaying a List of Job Streams in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Changing the Priority of a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 Adding Predecessors to a Job Instance . . . . . . . . 329 Releasing a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . 315 Releasing a Job Instance from Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Displaying Successors of a Job Stream Instance . . . . 315 Managing Job Stream Instances in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Displaying and Changing the Properties of a Job Stream Instance. . . . . . . . . . . . 349 Managing Workstations in the Plan . . . . . . . . . . . . . . 328 Deleting Predecessors from a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Adding Predecessors to a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Submitting a Job into the Plan . . . 338 Submitting an Ad Hoc Job into the Plan . . . 328 Holding a Job Stream Instance. . . . . . . . . . . . . . . . . . . . . 362 Tivoli Job Scheduling Console User’s Guide xiii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 Submitting Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Displaying Successors of a Job Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Holding a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Monitoring Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 Displaying Dependencies of a Job Stream Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 Canceling a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 Showing Predecessors and Successors . . . . . . . . . . . . . . . . . . . . .Modifying the Properties of a Job Instance. . . . . . 312 Rerunning a Job Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Submitting Jobs and Job Streams into the Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Re-submitting a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Deleting Predecessors from a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 Displaying a Workstation Instance . . . . . . . . . .

. 364 Stopping a Workstation Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 Switching the Domain Manager in a Domain . . . . . . . . . . 365 Unlinking a Workstation Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 Changing the Job Fence of a Workstation in the Plan . . . . . . . . . . . . . . . . 367 Managing File Dependencies in the Plan . . . . . . . . . . . . Using Common Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Displaying a List of Domains in the Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 Replying to a Prompt Dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 Listing All Job Instances . . . . . . . . . . . . . . . . . . . . . . Enabling Time Zones in the Workload Scheduler . . . . . . . . 378 Using Filter Criteria. 366 Stopping the Workstations in a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 xiv Version 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 Listing All Job Stream Instances . . . . . . . . . . . . Appendixes . . . 370 Changing the Number of Units of a Resource Dependency. . . . . . . . . . . . . . 380 Appendix B. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Setting an Alternate Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 Displaying Resource Dependencies Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Starting the Workstations in a Domain . . . . . . . . . . . . . . . . . . . . 378 Displaying a Common List . . . . . . . . . . . . . . . . . . . . . . . . 369 Managing Resource Dependencies in the Plan . . . . . . . . . 369 Displaying the Properties of a Resource Dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Linking a Workstation Instance . . . . . . . . . . . . . . 375 Creating a Common List of Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Traces for the Job Scheduling Console . . . . . . . . . . . 373 Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 . . . . . .Changing the Job Limit of a Workstation in the Plan . . . . . . . . . . . . . . . . . . . . . . 376 Creating a Common List of Job Stream Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 Displaying Prompt Dependencies Status. . 367 Displaying File Dependencies Status . . . . . . . . . . . . . . 371 Part IV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Managing Domains in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Starting a Workstation Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 Deleting a Common List . . . . . . . . . . . . . . . . . . . . . . . . . 367 Managing Prompt Dependencies in the Plan. . . . . . . . . . . 376 Using Filter Criteria. . . . . . . . . . . . . . . . . . 366 Unlinking the Workstations in a Domain . . . . . . 366 Linking the Workstations in a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 Modifying a Common List. . . . .

. . . . . .Appendix D. . . . . . . . 387 Appendix E. . . . . . . . . . . . . . . . . . . 399 Tivoli Job Scheduling Console User’s Guide xv . . . . . . . . . . . . . . . . . . . . . . . 395 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Glossary . . . . . . . . . Job Scheduling Console Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status Description and Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 .xvi Version 8.

. . . . . . . . Job Stream Editor — External Job Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 47. . . . . . . . . . . . . . . . . . Example 1: Rule-based Run Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 39. . . . .Rule-based Run Cycle Time Restrictions Page . . . . . Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Properties . . . . . . . . Properties . . . . . . . . . . . . . Properties . . . . . . . . . 106 42. The Properties . . . . . . . . . . . . . . . . . . . .Resource in Database Default Workstations Window . . . 76 16. . Properties . . 93 29. . . . . . . . . . . . . . . 127 49. Job Stream Instances Timeline View . . . . . . . . . Selecting the External Job . . . . . . . . . . Example 2: Offset-based Run Cycle Defined . . . . . . . . . . . . Job Stream Editor Graph View . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 2. . . . . . . . . . . . Job Stream Editor . . . . . . . . . . . . . . Job Stream Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Properties . . . . . . . . . . . Properties . . . . . . . . . . . . . .Rule-based Run Cycle Rules Page . . 100 34. . . . . . . . . . .Figures 1. . . . . . . . . . . . . . . . . . . . Job Stream Editor — Example External Job Dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . .Workstation in Database Resources Page . . . . . . . . . . . . . . . . 101 37. . . . . . . . . . . . . . . . . 90 23. . . . . . . . . . . . . . . . Properties . . . . . . . . . . . .JCL Job Resources Window. . . . . . . . . .External Job Window. . . . . . . . . Find Workstations Window. . . . . . . 96 31. . . . . Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Resource in Database Window . . . . . . . . .Example Dependent Jobs. . . . . . . . . . . . . . . . . 92 26. . . . . . . . . . . The Properties . . 93 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Tivoli Job Scheduling Console User’s Guide xvii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Run Cycle View . . . . . . . Properties . . . . . . . . . . . . . . . . . . . . . . . . .External Job Added . . .Resource in Database Availability Intervals Window. . . . . .Job Stream Window. . . . . . . . . . . . . . . . . . . . . . 91 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 33. 75 15. . . . . . . . . . . . . Properties . . . . . . . 116 45. . . . . . . 100 35. . Properties . . . . . . . . . . . . . . . . . . . . 77 17. . Properties . . .Database Workstation List Window . . . . . 72 13. . . . . . . . . . . . . . . . . . . . . .Job Stream List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 3. . . . . . 123 48. . . . . . . . . . . . . . . . . . . . . . . . . . . . .External Job Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 14. . . . . . . . . . . . Job Stream Editor . . . . . . . . . . . . . . . . . Job Stream Instances List View . . . . . . . . . . . . . . . . . . . . . . . . . . .Job Instance List window . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Results of a Job Stream List . . . . . . . . . . . . . . . . . . . . . . . . . Job Stream Editor . . . . . . . . . . . . .JCL Job Time Restrictions Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Database Resource List Window . . . . . . Properties . . . . . . . 65 11. . . . . . . . . 87 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 41. . .JCL Job Task Page . . . . . . . . . . . . . . . . . . . . . . . . 89 22. . . . . . Example 1: Offset-based Run Cycle . 110 43. . . List of Resources in the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 40. . . . . . . 97 32.Job Stream Instance List Window . . . . . . . . . . . . . . . . . . . . . . . . 92 27. . . . . . . . . . . . . . . . . . . . . . . .Offset-based Run Cycle Window .Database Resource List Window . . . Properties . . 62 10. . . . . . . . . . . . Job Stream Editor . . . . . . . . . . . . . . . 116 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 38. . . . . . . . . . . . . . . . . . . . . . . 60 9. . . . . . . . .Timeline View . . . . . . . . . . . . . . . . . . . . . . . . . . 112 44. . Job Scheduling View . . . . . . . . Example 3: Exclusionary Run Cycle Defined . . Adding an Open Time Interval . . . . . . . . . . . . . . . . .Rule-based Run Cycle General Page . . . . . . . . 91 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 5. Properties . . . . . . . . . . . . . . . . 70 12. . . . . . . . . . . . . . . . . Properties . . . . . . . . . . . . . . . . . . . .Group of Lists Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example 2: Exclusionary Run Cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 30. . . Properties . . . . . . . . . . . . . . . 49 7. . . . . . . . . . . . . . . . Submit Job Stream Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 36. . . . . . . . . . . . . The Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Properties . . . . . . . . . . . . . . . Properties . . . Displaying a List . . . . . . . . . . Example Rule . . .Workstation in Database Window. . . . . . . . . . . . . . . . . .Workstation in Database General Window General Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Add Link . . . . . . . . . . . . . . . . . . . . 86 20. . . . . . . . . . . 83 19. . . . . . . . . . . . . . . . . . . . . . . 80 18. . . . . . . . . . . . . . . . . . .Resource in Database Window Resource Page . . . . . . . . . . . . . . . . Properties . . . . .JCL Job General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

50. Properties - Job Stream Instance General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51. Properties - Job Stream Instance Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52. Timeline View - Left Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53. Timeline View - Right Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54. Rescheduling a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55. Properties - Job Stream Instance Time Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56. Rescheduling the Start time of a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57. Rescheduling the Deadline Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58. Job Instances List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59. Job Instances Groups in the Timeline View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60. Properties - JCL Job Instance Instance General Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61. Properties - JCL Job Instance Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62. Properties - JCL Job Instance Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63. Properties - JCL Job Instance Details Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64. Properties - JCL Job Instance Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65. Properties - JCL Job Instance Resources Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66. Target Resources for a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67. Logical Resources for a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68. Dependencies - JCL Job Instance Predecessors Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69. Dependencies - JCL Job Instance Successors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70. Timeline View of Job Instances - Left Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71. Timeline View of Job Instances - Right Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72. Rescheduling a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73. Rescheduling the Start Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74. Rescheduling the Deadline Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75. Impact View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76. Change Status Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77. Edit JCL Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78. The Properties - Plan Workstation List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79. Plan Workstation List Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80. Properties - Workstation in Plan General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81. Properties - Workstation in Plan Resource Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82. Properties - Workstation in Plan Job Summary Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83. Properties - Workstation in Plan Open Time Intervals Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84. Changing the Start Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85. Changing the Start Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86. Changing the Quantity of Resource 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87. Change Status - Workstation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88. List of Jobs Scheduled on the Workstation and in Complete Status . . . . . . . . . . . . . . . . . . . . . . . . . 89. The Properties - Plan Resource List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90. A Plan Resource List Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91. Properties - Resource in Plan Resource Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92. Properties - Resource in Plan Default Workstations Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93. Properties - Resource in Plan Availability Intervals Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94. Properties - Group of Lists Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95. Create Database List Pop-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96. Properties - Job Stream List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97. Properties - Job List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98. Properties - Database Workstation List window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99. Properties - Database Resource List window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100. Properties - Workstation Class List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101. Properties - Prompt List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xviii

129 130 131 131 132 132 133 134 138 138 140 141 142 143 145 146 146 147 148 150 152 152 153 154 154 156 158 159 162 164 165 166 166 167 168 168 169 170 171 174 176 177 179 180 189 190 191 191 192 193 194 194

Version 8.1

102. Properties - Parameter List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103. Properties - NT User List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104. Properties - Domain List Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105. Properties - Calendar List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106. Displaying a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107. Properties - Resource in Database Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108. Find Workstation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109. Select a Task Type Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110. Properties - Job Definition General Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111. Properties - Job Definition: Task Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112. Job Definition List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113. Details for Job Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114. Properties - Job Definition Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115. Job Stream Editor Graph View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116. Job Stream Editor Timeline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117. Job Stream Editor Run Cycle View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118. Properties - Job Stream Properties General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119. Properties - Job Stream Time Restrictions Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120. Properties - Job Stream Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121. Properties - Job Stream Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122. Properties - Job Stream Prompts Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123. Job Stream External Dependencies Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124. External Dependencies Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125. Properties - Job General Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126. Properties - Job Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127. Properties - Job Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128. Properties - Job Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129. Properties - Job Prompts Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130. External Job Stream Dependency Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131. External Job Dependency Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132. Job Stream Editor Window Graph View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133. Simple Run Cycle General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134. Simple Run Cycle Rule Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135. Weekly Run Cycle General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136. Weekly Run Cycle Rule Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137. Calendar Run Cycle General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138. Calendar Run Cycle Rule Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139. Job Streams List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140. Properties - Workstation in Database Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141. Workstation List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142. Properties - Workstation Class General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143. Properties - Workstation Class Workstations Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144. Workstation Class List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145. Properties - Domain Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146. Properties - NT User Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147. Users List Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148. Properties - Calendar Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149. Monthly Yearly Calendar Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150. Day of Month Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151. Properties - Resource in Database Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152. Resource List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153. Properties - Prompt Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tivoli Job Scheduling Console User’s Guide

195 196 197 197 198 200 200 201 202 206 208 210 211 213 215 216 218 220 222 223 224 225 225 228 229 230 231 232 235 236 237 239 240 241 241 242 243 247 252 255 258 258 259 261 264 265 267 268 268 271 272 274
xix

154. Prompts List Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155. Properties - Parameter Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156. Parameter List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157. Properties - Group of Lists Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158. Properties - Plan Workstation List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159. Properties - Domains Status List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160. Properties - Job Stream Instance List General Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161. Properties - Job Stream Instance List Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162. Properties - Job Stream Instance List Dependencies Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163. Properties - Job Instance List General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164. Properties - Job Instance List Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165. Properties - Job Instance List Dependencies Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166. Properties - Plan Resource List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167. Properties - Prompt Status List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168. Properties - File Status List window.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169. Example of a Find Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170. Example Find Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171. Job Instance List View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172. Job Instance List: Timeline View window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173. Properties - NT Script Instance General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174. Properties - NT Script Instance Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175. Properties - NT Script Instance Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176. Properties - NT Script Instance Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177. Properties - NT Script Instance Prompts Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178. Properties - NT Script Instance Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179. Dependencies - NT Script Instance Successors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180. Impact View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181. Job instance Log File Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182. Rerun Job Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183. Job Stream Instances Timeline View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184. Job Stream Instances List View Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185. Properties - Job Stream Instance General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186. Properties - Job Stream Instance Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187. Properties - Job Stream Instance Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188. Properties - Job Stream Instance Prompts Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189. Properties - Job Stream Instance Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190. Dependencies Predecessors Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191. Impact View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192. Change Limit - Job Stream Instance Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193. Change Priority - Job Stream Instance Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194. Re-Submit Job Stream Instance Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195. Submit Job Stream into Plan Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196. Submit Job into Plan Window - Default Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197. Submit Job into Plan Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198. Properties - Job Instance General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199. Properties - Job Instance Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200. Properties - Job Instance Time Restrictions Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201. Properties - Job Instance Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202. Properties - Job Instance Prompts Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203. Properties - Job Instance Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204. Properties - Job Instance Predecessors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205. Submit Ad Hoc Job into Plan Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xx

275 277 277 279 280 280 281 282 283 285 287 288 289 290 291 293 293 295 296 297 299 300 302 304 306 307 311 312 313 317 318 319 321 322 324 326 327 330 331 332 333 335 336 337 338 341 341 343 345 347 348 349

Version 8.1

206. Properties - Job Instance General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207. Properties - Job Instance Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208. Properties - Job Instance Time Restrictions Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209. Properties - Job Instance Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210. Properties - Job Instance Prompts Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211. Properties - Job Instance Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212. Properties - Job Instance Predecessors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213. Workstation Status List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214. Properties - Workstation in Plan Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215. Change Limit - Workstation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216. Change Fence - Workstation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217. Switch Manager - Domain Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218. Status of All Files List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219. Set Alternate Plan Files Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220. Properties - Job Instance Common List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221. Properties - Job Stream Instance Common List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

350 352 354 355 357 359 360 361 363 364 364 367 368 371 376 378

Tivoli Job Scheduling Console User’s Guide

xxi

xxii

Version 8.1

Tables
1. List of Publications for Tivoli Workload Scheduler for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix 2. List of Publications for Tivoli Workload Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx 3. Job Scheduling Console Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4. Setting the Tivoli Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5. Setting the Tivoli Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6. Authorization Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 7. Useful Framework Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 8. Setting the Tivoli Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 9. Authorization Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 10. Useful Framework Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 11. Job Scheduling Console Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 12. Starting the Job Scheduling Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 13. Job Scheduling View Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 14. Object List Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 15. Default Database Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 16. Default Plan Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 17. Properties List Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 18. Properties - Workstation in Database General Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 19. Properties - Workstation in Database Open Time Intervals Information . . . . . . . . . . . . . . . . . . . . . . . 63 20. User-defined Workstation Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 21. Default Workstation Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 22. Properties - Database Workstation List Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 23. Create a Resource Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 24. Define an Availability Interval Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 25. User-defined Resource Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 26. Default Resource Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 27. Database Resource List Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 28. Tasks in Creating a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 29. Properties - Job Stream Window Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 30. What Happens When You Define a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 31. Graph View Job Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 32. Properties - JCL Job General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 33. Properties - JCL Job Task Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 34. Properties - JCL Job Time Restrictions Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 35. Filter Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 36. Run Cycle Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 37. Run Cycle General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 38. Run Cycle Time Restrictions Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 39. Rule-based Run Cycle Rules Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 40. Offset-based Run Cycle Rules Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 41. Submit Job Stream Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 42. Properties - Job Stream List Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 43. Adding and Modifying Jobs and Dependencies in the Graph View . . . . . . . . . . . . . . . . . . . . . . . . . 113 44. Adding and Modifying Run Cycles – Pop-up Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 45. Examples of How to Use Job and Job Stream Instance Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 46. Properties - Job Stream Instance List Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 47. Properties - Job Instance List Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 48. Job Instance Details Timeline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 49. Properties - JCL Job Instance General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Tivoli Job Scheduling Console User’s Guide xxiii

50. Properties - JCL Job Instance Task Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51. Properties - JCL Job Instance Details Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52. Properties - Write-to-Operator Job Instance Options Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 53. Logical Resources Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54. Dependencies Predecessors Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55. Dependencies Predecessors Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56. Dependencies Successors Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57. Dependencies Predecessors Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58. Timeline View Job Instance Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59. Impact View Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60. Properties - Plan Workstation List Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61. Properties - Workstation in Plan General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62. Workstation List Jobs Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63. Modifying Job Instance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64. Plan Resource List Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65. Properties - Resource in Plan Resource Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66. Properties - Resource in Plan Default Workstations Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 67. Properties - Resource in Plan Availability Intervals Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . 68. Modifying Job Instance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69. Properties List Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70. Properties List Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71. New Job Definition Task Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72. Properties - Job Definition General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73. Job Stream Recovery Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74. Task Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75. Job Definition List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76. Details for Job Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77. Job Stream Editor Graph View Toolbar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78. Job Stream Editor Timeline View Toolbar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79. Job Stream Editor Run Cycles View Toolbar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80. Job Stream Properties Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81. Job Stream Properties General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82. Job Stream Time Restrictions Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83. Properties - Job General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84. Properties - Job Time Restrictions Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85. Colored Bars on Dates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86. Properties Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87. Properties Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88. Job Streams List Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89. Modifying Objects in a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90. Properties - Workstation in Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91. Workstation List Window Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92. Properties - Workstation Class Workstations Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93. Workstation Class List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94. Properties - Domain Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95. Domain List Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96. Properties - NT User Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97. Users List Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98. Example Calendars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99. Properties - Resource in Database Window Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100. Properties - Job Stream Instance List General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101. Properties - Job Stream Instance List Time Restrictions Information . . . . . . . . . . . . . . . . . . . . . . . .
xxiv

141 143 145 147 148 149 150 151 152 156 163 165 171 172 175 177 179 180 181 189 190 201 202 204 206 208 210 214 215 216 217 218 221 228 229 238 245 246 248 249 252 255 258 259 261 262 264 265 266 271 281 283

Version 8.1

102. Properties - Job Stream Instance List Dependency Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103. Properties - Job Instance List General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104. Properties - Job Instance List Time Restrictions Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105. Properties - Job Instance List Dependency Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106. Properties - Plan Resource List Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107. Properties - Prompt Status List Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108. Job Instance Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109. Job Instance List View Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110. Job Instance Timeline View Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111. Properties - NT Script Instance General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112. Properties - NT Script Instance Task Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113. Properties - NT Script Instance Time Restrictions Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114. Properties - NT Script Instance Files Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115. Properties - NT Script Instance Prompts Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116. Properties - NT Script Instance Resources Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117. Predecessors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118. Internetwork Predecessors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119. Successors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120. Impact View Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121. Rerun Job Window Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122. Job Stream Instance Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123. Job Stream Instances Timeline View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124. Job Stream Instances List View Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125. Properties - Job Stream Instance General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126. Properties - Job Stream Instance Time Restrictions Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . 127. Properties - Job Stream Instance Files Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128. Properties - Job Stream Instance Prompts Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129. Properties - Job Stream Instance Resources Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130. Dependencies - Job Stream Instance Predecessor Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131. Impact View Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132. Job Stream Instance Priorities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133. Submit Job Stream into Plan Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134. Submit Job into Plan Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135. Submit Job into Plan Window - Specific Job stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136. Properties - Job Instance General Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137. Properties - Job Instance Time Restrictions Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138. Properties - Job Instance Files Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139. Ad Hoc Prompt Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140. Predefined Prompt Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141. Properties - Job Instance Resources Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142. Properties - Job Instance Predecessors Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143. Properties - Job Instance General Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144. Task Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145. Properties - Job Instance Time Restrictions Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146. Properties - Job Instance Files Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147. Ad Hoc Prompt Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148. Predefined Prompt Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149. Properties - Job Instance Resources Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150. Properties - Job Instance Predecessors Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151. Workstation Status List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152. List of Domains in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153. Status of All Files List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tivoli Job Scheduling Console User’s Guide

284 285 287 288 289 290 294 295 296 297 299 301 302 304 306 307 308 308 311 313 316 317 318 319 321 322 324 326 327 330 332 335 336 337 339 342 343 345 346 347 348 350 352 354 355 357 358 359 360 361 366 368
xxv

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156. . . . . Prompt Dependencies Status. . . .Job Instance List Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159. 157. . . . . . . . . . . . . . . . . Job Scheduling Console Job States . . . . . . . . . . . . . Properties . 161. . . . . . . . . . . . Job Stream Status Mapping . . . . . Set Alternate Plan Files Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158. . . .154. . . . . . . . . . . . . . . . . . . . . 160. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165. . . . . . . . . . . 155. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Job Stream Instance List Information . . . . . . . . . . . . . . . . . . . . . . . . . . 163. . . . . . . . . . . . . . . . . . . . . . Resource Dependencies Status . . . . . . . . . . . Workload Scheduler Internal Job States . . . . . . . . . . . . . . . . 369 370 371 377 379 381 387 388 388 389 389 390 xxvi Version 8. . . . . . . . . . . . . . . Workload Scheduler Internal Job Stream States. . . . . . . . . . . . . . . . . . . . Job Status Mapping . .1 . Job Scheduling Console Job Stream States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Properties . . . . . . . Trace Variable Location by Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Job Scheduling Console supplements. and logical resources in the scheduling database. and the Tivoli Job Scheduling Console. workstations. Who Should Read This Guide This guide is intended for use by: ¶ System administrators who have the task of installing the Tivoli Job Scheduling Console. “Introduction” on page 5 provides an introduction to the Job Scheduling Console ¶ Chapter 2.2. It allows you to work with scheduling objects in the following ways: ¶ Define job streams. jobs. Getting started Part I contains the following chapters: ¶ Chapter 1. “Installing the Tivoli Workload Scheduler for z/OS Connector” on page 17 describes how to install the Tivoli Workload Scheduler for z/OS Connector. They should be familiar with performing these specific tasks and with working in the IBM® z/OS and Microsoft Windows NT® environments: ¶ Operators who have the responsibility of controlling and monitoring the scheduler plan. and resource instances in the plan. ¶ Monitor and modify job stream instances. “Installing Tivoli Job Scheduling Services” on page 13 describes how to install Job Scheduling Services. The Tivoli Job Scheduling Console User’s Guide provides an introduction to and an explanation of the Tivoli Job Scheduling Console Feature Level 1. but does not totally replace. It explains how to install the console and provides instructions for performing scheduling tasks using Tivoli Workload Scheduler for z/OS and Tivoli Workload Scheduler. The Tivoli Job Scheduling Console provides users with a Java™-based user interface to Tivoli Workload Scheduler for z/OS and Tivoli Workload Scheduler.Preface This guide describes Tivoli Workload Scheduler for z/OS™. They should be familiar with performing the tasks related to monitoring and modifying objects in the plan and with working in the IBM z/OS and Windows NT environment. which make up the Tivoli Workload Scheduler suite of applications. ¶ Chapter 3. job instances. What This Guide Contains This book contains the following sections: Part I. Tivoli Job Scheduling Console User’s Guide xxvii . Tivoli Workload Scheduler. the traditional z/OS ISPF panes on the host. workstation instances. They should be familiar with one or more of the following operating systems: Microsoft® Windows® AIX® HP-UX Sun Solaris Linux ¶ Schedulers who have the responsibility of creating and updating definitions of objects in the scheduler database and of creating lists of objects in the scheduler database and plan.

¶ Chapter 12. display. “Managing Workstations in the Plan” on page 161 describes how to display and modify workstations. and modify domains. “Managing Resources in the Database” on page 69 describes how to create and list resources.1 .¶ Chapter 4. “Creating Job Streams” on page 79 describes how to create job streams. “Managing Workstations in the Database” on page 55 describes how to create workstations and workstation lists. display. “Listing and Modifying Job Streams” on page 109 describes how to create job stream lists and how to modify them. Part III. ¶ Chapter 14. display. “Managing Jobs” on page 201 describes how to create and manage job definitions. specify dependencies. ¶ Chapter 9. ¶ Chapter 11. ¶ Chapter 20. users. Part II. and modify workstations and workstation classes. and modify job streams. “Installing the Tivoli Job Scheduling Console” on page 33 describes how to install the Tivoli Job Scheduling Console. Using the Job Scheduling Console with Tivoli Workload Scheduler Part III contains the following chapters: ¶ Chapter 16. “Listing Job Stream and Job Instances” on page 119 describes how to create lists of jobs and job instances. ¶ Chapter 6. ¶ Chapter 10. ¶ Chapter 8. Users. “Managing Domains. “Managing Jobs” on page 137 describes how to display and modify job instances. ¶ Chapter 15. “Managing Job Streams” on page 127 describes how to display and modify job stream instances. and Calendars” on page 261 describes how to create. schedule and submit job streams. ¶ Chapter 19. Using the Job Scheduling Console with Tivoli Workload Scheduler for z/OS Part II contains the following chapters: ¶ Chapter 7. “Working with the Job Scheduling Console” on page 41 describes the main features of the Job Scheduling Console. ¶ Chapter 5. ¶ Chapter 18. and calendars. “Managing Database Lists” on page 189 describes how to create all types of Workload Scheduler lists. ¶ Chapter 13. “Managing Resources in the Plan” on page 173 describes how to display and modify resources in the plan. xxviii Version 8. “Managing Job Streams” on page 213 describes how to use the Job Stream Editor to create. “Installing the Tivoli Workload Scheduler Connector” on page 25 describes how to install the Tivoli Workload Scheduler Connector. “Managing Workstations and Workstation Classes” on page 251 describes how to create. ¶ Chapter 17.

display. Prompts. Publications This section lists publications in the Tivoli Workload Scheduler suite. ¶ Appendix E. “Managing Resources. ¶ Chapter 22. It also describes how to access Tivoli publications online. ¶ Appendix C. Part IV. ¶ Appendix B. “Plan Tasks” on page 279 describes how to create and manage resources in the plan. and how to make comments on Tivoli publications. and Parameters” on page 271 describes how to create. “Status Description and Mapping” on page 387 provides information about job and job stream status. 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 Publications The following table lists the publications in the Tivoli Workload Scheduler for z/OS library. and parameters. Table 1. and modify resources. “Job Scheduling Console Messages” on page 391 lists the messages produced by the Job Scheduling Console. “Setting Traces for the Job Scheduling Console” on page 381 describes how to use the Job Scheduling Console tracing facility. prompts. Appendixes Part IV contains the following Appendixes: ¶ Appendix A. “Enabling Time Zones in the Workload Scheduler” on page 385 describes how to enable the time zone facility. “Using Common Lists” on page 375 describes how to create and modify common lists. List of Publications for Tivoli Workload Scheduler for z/OS Task Planning Tivoli Workload Scheduler for z/OS Understanding the Tivoli Workload Scheduling Suite Learning concepts and terminology Using the Java GUI Publication Tivoli Workload Scheduler for z/OS Licensed Program Specifications Tivoli Workload Scheduler for z/OS General Information Tivoli Workload Scheduler for z/OS Getting Started Tivoli Workload Scheduler for z/OS Tivoli Job Scheduling Console User’s Guide Release Notes Tivoli Workload Scheduler for z/OS Messages and Codes Order number GH19-4540 GH19-4539 SH19-4542 GI10-5781 Interpreting messages and codes SH19-4548 Tivoli Job Scheduling Console User’s Guide xxix . how to order Tivoli publications.¶ Chapter 21. ¶ Appendix D.

Translated documents are also available for some products.tivoli. and utility Guide commands Installing and configuring limited fault-tolerant agents on AS/400 Setting up and using the Plus module Interpreting messages Tivoli Workload Scheduler Limited SH19-4558 Fault-Tolerant Agent for AS/400 User’s Guide Tivoli Workload Scheduler Plus Module SH19-4562 User’s Guide Tivoli Workload Scheduler Error Messages SH19-4557 Accessing Publications Online You can access many Tivoli publications online at the Tivoli Customer Support Web site: http://www. Table 2. xxx Version 8.Table 1.com/support/documents/ These publications are available in PDF or HTML format. Tivoli Workload Scheduler Reference scheduling language.1 . List of Publications for Tivoli Workload Scheduler Task Installing a Tivoli Workload Scheduler network Publication Tivoli Workload Scheduler Planning and Installation Order number SH19-4555 SH19-4556 Using the command line interface. List of Publications for Tivoli Workload Scheduler for z/OS (continued) Task Installing Tivoli Workload Scheduler for z/OS Customizing and tuning Tivoli Workload Scheduler for z/OS Planning and scheduling the workload Controlling and monitoring the current plan Writing application programs Quick reference Diagnosing failures Publication Tivoli Workload Scheduler for z/OS Installation Guide Tivoli Workload Scheduler for z/OS Customization and Tuning Order number SH19-4543 SH19-4544 Tivoli Workload Scheduler for z/OS SH19-4546 Planning and Scheduling the Workload Tivoli Workload Scheduler for z/OS Controlling and Monitoring the Workload Tivoli Workload Scheduler for z/OS Programming Interfaces Tivoli Workload Scheduler for z/OS Quick Reference Tivoli Workload Scheduler for z/OS Diagnosis Guide and Reference SH19-4547 SH19-4545 GH19-4541 LY19-6410 Tivoli Workload Scheduler Publications The following table lists the publications in the Tivoli Workload Scheduler library. or both.

tivoli. for a list of telephone numbers.S.html Tivoli Job Scheduling Console User’s Guide xxxi .html Providing Feedback about Publications We are very interested in hearing about your experience with Tivoli products and documentation. except the licensed publications.com/support/survey/ ¶ Complete the Readers Comment Form provided at the back of the book. LookAt can be accessed from the internet or from a Time Sharing Option (TSO) command line.com/support/Prodman/html/pub_order. LookAt LookAt is an online facility that allows you to look up explanations for z/OS messages and system abends.Workload Scheduler for z/OS All the books in the Tivoli Workload Scheduler for z/OS library.com.com/inside/store/lit_order.html You can also order by telephone by calling one of these numbers: ¶ In the U. Updates to books between releases are provided in softcopy only. ¶ Complete our customer feedback survey at the following Web site: http://www. are available in displayable softcopy form on CD-ROM in the following Softcopy Collection Kit: ¶ OS/390®. If you have comments or suggestions about our products and documentation.ibm. You can use LookAt on the Internet at: http://www. see the following Web site: http://www. For additional hardware and software information. and we welcome your suggestions for improvements. contact us in one of the following ways: ¶ Send an e-mail to pubs@tivoli. refer to the documentation for the specific BookManager product you are using.tivoli.com/servers/eserver/zseries/zos/bkserv/lookat/lookat. 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 disk drive (capable of reading disks formatted in the ISO 9660 standard) and a matching adapter and cable. Using LookAt to find information is faster than a conventional search because LookAt goes directly to the explanation.tivoli.: 800-879-2755 ¶ In Canada: 800-426-4968 ¶ In other countries. Ordering Publications You can order many Tivoli publications online at: http://www.

See the Tivoli Customer Support Handbook at the following Web site: http://www. command options. type the message ID. in bold type. as well as the following information: ¶ Registration and eligibility ¶ Telephone numbers and e-mail addresses. in bold type. GC28-1778. Names of files and directories.com/support/handbook/ The handbook provides information about how to contact Customer Support. For such messages. and message text appear like this. Commands. as in the following example: lookat iec192i This results in direct access to the message explanation for message IEC192I. values you must provide. For example. To find a message explanation from the LookAt Web site. xxxii Version 8. code examples. command options. and flags that appear within text appear like this. Contacting Customer Support If you have a problem with any Tivoli product. operating system-dependent commands and paths.1 . LookAt must be installed on your host system. you can contact Tivoli Customer Support. in monospace type. type the message ID. Graphical user interface elements. You can select the release if needed. and margin graphics. text strings you must type. You can obtain the LookAt code for TSO from the LookAt Web site by clicking on News and Help. in monospace type. when they appear within text. LookAt prompts you to choose which book to open. or from the SK3T-4269. and words and phrases that are emphasized appear like this. and flags that appear on a separate line. Some messages have information in more than one book. Typeface Conventions The following typeface conventions are used in this book: Bold Lowercase and mixed-case commands. except for titles of windows and dialogs and names of keys also appear like this. in italic type. Italic Monospace Variables. IEC192I has routing and descriptor codes listed in OS/390 MVS Routing and Descriptor Codes. output. depending on the country you are in ¶ What information you should gather before contacting support Conventions Used in This Book This book uses several conventions for special terms and actions. and HTML and XML tags also appear like this. depending on the severity of your problem.tivoli. new terms. To find a message explanation from a TSO command line. names of Java methods and classes.To use LookAt as a TSO command.

Used to represent a single character. When using the Microsoft Windows command line.Operating System-dependent Variables and Paths This book uses the UNIX® convention for specifying environment variables and for directory notation. Note: If you are using the bash shell on a Windows system. you can use the UNIX conventions. Tivoli Job Scheduling Console User’s Guide xxxiii . replace $variable with %variable% for environment variables and replace each forward slash (/) with a backslash (\) in directory paths. are defined as: * (asterisk) ? (question mark) Used to represent a character string. Other Conventions Wildcards. as used in this book.

xxxiv Version 8.1 .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Working with Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . 9 Working with Resources in the Current Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Tivoli Environment . . . . . . . System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling Job Scheduling Services . . . . . . . . . . . . . 7 Working with Job Instances . . . . . . . . . . . . . . . . 6 Working with Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I — Getting Started Chapter 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Operator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Working with Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Planning Tasks . . . . . . . . . . . . . . . . 8 Working with Resource Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Working with Job Stream Instances . . . . . . . . . . . . Tivoli Job Scheduling Console User’s Guide 17 17 17 17 18 18 18 18 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Working with Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Tivoli Job Scheduling Services . . . . . . . . . . . . . . . . . . . . . . Setting the Tivoli Environment . . . . . . . . . . . 9 Working with Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Patches . . . . . . . . 13 Before Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Working with Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Tivoli Workload Scheduler for z/OS Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Job Scheduling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing from the Tivoli Desktop . . . . . 13 13 13 13 13 14 15 16 16 Chapter 3. . . . . . . . . . . . . . . . . . . . . 6 Planning Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Connector. . 9 Operator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Working with Jobs . . . . . 10 Terminology Used in the Job Scheduling Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Working with Job Streams. . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Working with Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Working with Workstations . . . . . . . . . . . . . . Installing the Tivoli Workload Scheduler for z/OS Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Tivoli Workload Scheduler Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Working with Job Instances . . . . . . . . . . . . . . . . . . . . 10 Scheduling Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Working with Job Streams. 9 Working with Workstations in the Current Plan . . . . . . . . . System Requirements . . . . . . . . 10 Chapter 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Before Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Authorization Roles Required for Instances . . . . . . . . . . . . . . . . . . Customizing the Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solaris. . . . . . . . . . . . . . . Installing from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling on Microsoft Windows . . . . . . . . . . . . . . . . 25 Before Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 33 33 34 34 35 36 36 38 39 40 40 40 Chapter 6. . . . . . . . . . . . . . . . . . 41 Using the Buttons of the Job Scheduling View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing on AIX and HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling the Job Scheduling Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with the Job Scheduling Console . . . . . . . . Installing the Connector. . . . Installing Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 The Job Scheduling View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling the Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 25 25 25 26 26 26 26 27 27 27 27 28 29 29 29 30 31 31 31 32 Chapter 5. . . . . . . Installing on Solaris and Linux . . Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware . . . . . . . . . . . . . . . . . .Installing from the Tivoli Desktop . . . . . . . . . . . . . . . . . Uninstalling on AIX. . . . . . . . . . . . . Managing Connector Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Tivoli Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Useful Framework Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 2 Version 8. Starting the Job Scheduling Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . and Linux . . . .1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Connector Instances. . . . . . . . . . . . . . . . . . . . . . . . . . 19 19 20 20 20 21 22 22 22 Chapter 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Before Installing . . . . . . . . . . . . . HP-UX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customizing the Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Workload Scheduler Security . . . . . . . . . . . . . . . . . . . .sh . . . . . . Installing on Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating AIXconsole. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . For Use With Tivoli Workload Scheduler for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . For Use With Tivoli Workload Scheduler . . . . . . . . . . . . . . . . . . . . . . Managing Connector Instances. . . . . . Installing the Tivoli Job Scheduling Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software . . . Installing Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Job Scheduling Services . . . . . . . . . . . . . . . . Installing from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Connector Instances. . . . Fault-tolerant Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing from the Tivoli Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Authorization Roles Required for Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Tivoli Workload Scheduler Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling the Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Useful Framework Commands . . . . Workload Scheduler Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Defaults for Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example: Finding a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 43 44 44 44 45 46 47 47 48 48 48 49 Tivoli Job Scheduling Console User’s Guide 3 . . . . . . . . . . . . . . . . . . . . . Displaying a List . . . . . Finding Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Group of Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a List . . . . . . . . . . . . . . . . Default Plan Lists . . . . . . . . . . . . . . . . . . . . . . . . Detaching a List Display . . . . . Modifying a List . . . . . . . . . . . . . . . . . . .Working with Lists . . . . . . . . . . . . . . . Default Database Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4 Version 8.1 .

you must install the Workload Scheduler Connector. Note: To use the Job Scheduling Console with Tivoli Workload Scheduler for z/OS. You can work with these products simultaneously from the same graphical console. modifying. It also allows you to monitor and control objects scheduled in the current plan. the list displays all the existing objects of a kind. For each of these functions. you can use a list creation mechanism that enables you to list database or plan objects that you select according to filtering criteria. The Job Scheduling Console provides two main functions: Scheduling Enables you to define and list job streams. You can use both predefined lists that are packaged with the Job Scheduling Console. Connectors are installed separately on a Tivoli management server and on managed nodes that have access to the scheduler. Monitoring and control Enables you to monitor and control scheduled jobs and job streams in the scheduler plan. To use the Job Scheduling Console with Workload Scheduler. jobs.1. Tivoli Job Scheduling Console User’s Guide 5 . Filtering criteria narrow a list down to selected objects that you want to work with. and deleting objects in the product database. you must install both types of Connector. and resource availability in the scheduler database. Connectors manage the traffic between the Job Scheduling Console and the job schedulers. The Job Scheduling Console allows you to work with Tivoli Workload Scheduler for z/OS and Tivoli Workload Scheduler. You can list objects without using filtering criteria. In this case. To use the Job Scheduling Console with both schedulers. one for each type of scheduler. In the Job Scheduling Console. you must install the Workload Scheduler for z/OS Connector. and lists that you create. built into the Job Scheduling Console. a scheduled job stream is called a job stream instance whereas a scheduled job is called a job instance. Introduction 1 Introduction The Tivoli Job Scheduling Console for Tivoli Workload Scheduler is an interactive interface for creating. Extensions. extend its base scheduling functions to specific scheduling functions of Tivoli Workload Scheduler for z/OS and of Tivoli Workload Scheduler.

or the days on which the job stream must run and when it must start Modifying a job stream involves adding. Job stream definitions are stored in the job scheduler databases. you can define and manage the following objects in the scheduler database: ¶ Job streams ¶ Jobs ¶ Resources ¶ Workstations Working with Job Streams Job streams are a collection of jobs. and the resources they require to run. Creating a job stream involves: ¶ Defining job stream properties ¶ Creating jobs. 6 Version 8. 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. The jobs that comprise a job stream usually follow a sequence where the running of a job depends on the successful completion of another job. which includes defining what resources each job requires to run and the start time ¶ Defining the necessary dependencies. scheduling information. among the jobs of the job stream and with jobs that belong to other job streams ¶ Defining one or more run cycles. The base Job Scheduling Console provides a common set of functions on which the specific functions of the supported job scheduler extensions are implemented. The rest of this chapter provides a functional overview of the Job Scheduling Console for Tivoli Workload Scheduler for z/OS and for Tivoli Workload Scheduler. you must make and run a list of job streams in the database. You cannot create jobs outside of a job stream. along with the dependencies and run cycles.This chapter describes the features of the base Job Scheduling Console. or modifying any of the jobs that comprise it. if applicable ¶ Specifying the resources that the job requires to run Jobs are stored in the job scheduler database as parts of job streams. update. Tivoli Workload Scheduler for z/OS Tasks Planning Tasks From the Job Scheduling Console. You can also delete an entire job stream. To browse. You must first create a job stream and define its properties before you can start to create the jobs that comprise it. To browse or update job streams you have created. or sequencing. you must list the parent job stream in the database.1 . or delete a job definition. deleting. Working with Jobs Jobs are the units of work in a job stream.

update. provided you display them in a job stream instance list. Tivoli Job Scheduling Console User’s Guide 7 . Introduction Working with Run Cycles A run cycle provides the scheduling information of a job stream. Defining a resource involves: ¶ Defining the resource general properties ¶ Specifying availability intervals. Workstations are usually created to represent specific elements in your system configuration. Working with Workstations A workstation describes how and when jobs have to be run. Operator Tasks From the Job Scheduling Console. modify. To browse. you must list the parent job stream in the database. you must first display them in a list in the Job Scheduling Console. Resource definitions are stored in the job scheduler database. you must make and run a list of resources in the database. Modifying a job stream instance includes changing some of its general properties. A workstation is not necessarily hardware—it is a stage in the processing that is controlled by the scheduler. the job instances it contains.1. You can browse. the start and deadline times. update. you can create run cycles only after you have defined the job streams to which they apply. To browse. Defining a workstation involves: ¶ Defining workstation properties ¶ Defining resources and their capacity ¶ Defining the availability of servers Working with Resources Resources represent physical or logical devices that jobs use in order to run. you can monitor and control the following objects in the scheduler plan: ¶ Job stream instances ¶ Job instances ¶ Resource instances ¶ Workstations To monitor and control these objects. Working with Job Stream Instances Job streams that are scheduled in the plan are job stream instances. A job stream can have more than one run cycle. periods during which the resource state and quantity available for running jobs differ from the values specified as general properties. or delete a run cycle definition. and their dependencies. or delete a resource definition. and delete job stream instances. Like jobs. 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.

Planning Tasks All the tasks that involve working with object definitions in the scheduling database are referred to as scheduler tasks in this guide. and time restrictions ¶ Deleting predecessor and successor jobs in the job instance dependency chain Working with Resource Instances A resource instance is a resource allocated to the plan. Modifying a job instance involves: ¶ Changing its state. Working with Workstations You can create.Working with Job Instances Jobs belonging to a job stream that is scheduled in the plan are job instances. update.1 . The status and quantities of the resource are specified in the general properties and availability intervals definitions in the database. These are described in the following sections of this chapter. Once you have saved an object in the database. and browse or modify their properties. you must first list it in the Job Scheduling Console if you want to browse. You can also delete workstations from the database. and browse or modify their properties. You can browse. You can also delete workstations from the database. and delete workstation definitions in the scheduler database. it supports specific functions and resources. You define 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. update. resource dependencies. Working with Workstations You can create. modify the resource availability intervals and quantity after the resource has been allocated to the plan. Tivoli Workload Scheduler Tasks The Tivoli Workload Scheduler extension supports all the tasks of the base Job Scheduling Console. 8 Version 8. change. modify. You define 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. such as scheduling resources and workstations. and delete workstation definitions in the scheduler database. or delete it. selected according to filtering criteria. selected according to filtering criteria. You can. The resource is reserved for the duration of the plan for use by the jobs that depend on it. and delete job instances after displaying them in a job instance list. In addition. however.

You define the following resource characteristics: ¶ General properties ¶ 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. Introduction Working with Job Streams You can use the Job Scheduling Console to work with job streams and job stream templates. you can change the status of a job stream instance to Waiting and Complete. You must first list the objects in the plan in order to work with any of them. Error. Ready. hold. Working with Job Instances You can: ¶ Change the status of job instances to: Running. or Successful ¶ Run. You can: ¶ Create. When you define a job stream as belonging to a template. update. Job stream templates contain only scheduling information. or release the job instance ¶ Remove or restore (NOP or UN-NOP) the job instance in the plan Working with Workstations in the Current Plan You can create and update workstation instance definitions in the plan. you imply that it must share the template calendar and run cycles. You can also delete resources from the database. and delete resource definitions in the scheduler database. This includes editing: ¶ Control properties ¶ Availability status to run jobs during specific intervals of time Tivoli Job Scheduling Console User’s Guide 9 . Operator Tasks All the tasks that involve working with objects in the plan. 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 Jobs When you create or modify a job. selected according to filtering criteria. and browse or modify their properties. update. are referred to as operator tasks in this book.1. Interrupted. Working with Job Stream Instances In addition to monitoring job stream instances. the Tivoli Workload Scheduler extension adds the following features to a basic job definition: ¶ Assigning the necessary special (logical) and workstation resources for the running of the job ¶ Defining the automatic and feedback options Working with Resources You can create.

their Job Scheduling Console equivalents. and run cycles. dependencies. Terminology Used in the Job Scheduling Console The terminology used in the Job Scheduling Console varies from that used in Tivoli Workload Scheduler for z/OS. you have to go to the scheduler to schedule the job stream into the current plan. and a brief explanation. and each job stream instance contains job instances. For more information. but typically one or two days. A job from one job stream that is a predecessor for a job in another job stream. Job Scheduling Console Terminology Tivoli Workload Scheduler for z/OS Application description Tivoli Workload Scheduler Job stream Explanation A sequence of jobs. including the resources and workstations that support them. see the “Glossary” on page 395. and you mark it active in the Job Stream Properties window. Table 3 lists Tivoli Workload Scheduler for z/OS terms. a free-day rule. and run cycles that can be inherited by all the job streams that have been created using the template. such as a calendar.1 . This includes editing the following: ¶ 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 Streams When you create a job stream. Working with Resources in the Current Plan You can create and update resource instance definitions in the plan. A detailed plan of system activity that covers a period of at least one minute and not more than 21 days. Each occurrence of a job stream is called a job stream instance. the job stream run cycles are used to generate the dates and times at which the job stream will run. A grouping of job streams that provides scheduling information. Table 3. The plan encompasses all job and job stream instances and the resources and workstations involved in running them.¶ 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 time during the plan. and scheduling information. You cannot add a job stream to the plan from the Job Scheduling Console. Application group Job stream template Current plan Plan External dependency External job 10 Version 8. After you complete the definition of a job stream in terms of jobs.

such as the 3rd day in a 90-day period. A job stream that is scheduled for a specific run date in the plan. A job scheduled for a specific run date in the plan. Includes a user-defined period and an offset. or printers. that is needed to run a job. The last date that a run cycle is valid. Operation Operation number Operations in the current plan Job Job identifier Job instances Out-of-effect date for run Valid to cycles Run cycle with offsets Run cycle with rules Special resources Offset-based run cycle Rule-based run cycle Logical resources Status: Complete Status: Delete Status: Started Task Successful Canceled Running Job Tivoli Job Scheduling Console User’s Guide 11 . Any type of limited resource. The number that identifies a job. Includes a rule. such as the first Friday of March or the second workday of the week. databases.1. A unit of work that is part of a job stream and that is processed at a workstation. communication lines. The job or job stream has been completed. such as tape drives. Job Scheduling Console Terminology (continued) Tivoli Workload Scheduler for z/OS In-effect date for run cycles Input arrival time Negative run cycle Occurrence Controller Tivoli Workload Scheduler Valid from (Earliest) start time Exclusionary run cycle Job stream instance Engine Explanation The first date that a run cycle is valid. The time before when a job or job stream is planned to be ready for processing. A job performed at a computer workstation. The job has started (jobs only). and that contains the tasks that manage the plans and databases. The job or job stream has been deleted from the plan. The component that runs on the controlling system. Specifies when a job stream must not run. Introduction Table 3.

1 .12 Version 8.

Setting the Tivoli Environment For this operating system . . Setting the Tivoli Environment To install Job Scheduling Services./etc/Tivoli/setup_env. Note: You must install Job Scheduling Services on the Tivoli server and on each managed node where the Connector is to be installed. then enter one of the following commands: Table 4.c:/windir/system32/drivers/etc/Tivoli/setup_env. To do this. Installing Tivoli Job Scheduling Services This chapter describes how to install Tivoli Job Scheduling Services.. Before Installing Read this information before you install Job Scheduling Services. AIX. Linux Microsoft Windows. Solaris.. DOS shell Enter this command . and Sun Solaris Version 3. UNIX shell Microsoft Windows. log in as root or administrator. System Requirements The Connector has the following system requirements: Software ¶ Tivoli Management Framework: Version 3. You can install Job Scheduling Services either from the Tivoli desktop or from the command line.. ¶ Approximately 4 MB of free disk space. you must first set the Tivoli environment.7B for Linux Hardware ¶ CD-ROM drive for installation. HP-UX.7.sh c:\windir\system32\drivers\etc\Tivoli\setup_env.. AIX.1 for Microsoft Windows.2 Installing Tivoli Job Scheduling Services 2.sh . Tivoli Job Scheduling Console User’s Guide 13 . HP-UX.cmd where windir is the name of the Microsoft Windows installation directory. You must install Job Scheduling Services before you install either the Workload Scheduler for z/OS Connector or the Workload Scheduler Connector.

From the Desktop menu select Install. 4. Click Select Media to select the installation directory. select the managed nodes to install on and move them to the Clients to Install On list. select Tivoli Job Scheduling Services. You can install the Connector only on managed nodes where Job Scheduling Services is installed. 3. The installation program copies the files and configures the Tivoli database with the new classes. 7. Click Close. Click Continue Install to continue the installation or click Cancel to cancel the installation. 5. Open the Tivoli Desktop. This path includes the directory containing the CONTENTS. Click Set Media & Close. Note: You must install Job Scheduling Services on at least the Tivoli management server. The Install Product window is displayed. 6. Type or select the installation path. 2. 14 Version 8. ensure you have set the Tivoli environment (see “Setting the Tivoli Environment” on page 13). In the Available Clients list.1 . When the installation is complete. which shows you the progress of the installation.Installing from the Tivoli Desktop To install the Connector from the Tivoli Desktop. the message Finished product installation appears. 10. then Install Product. The File Browser window is displayed. 8. 9. You return to the Install Product window. In the Select Product to Install list.LST file. The Product Install window is displayed. Click Install. then: 1.

then enter one of the following commands: ¶ To install on all managed nodes: winstall -c install_dir -i TMF_JSS ¶ To install on only one managed node: winstall -c install_dir -i TMF_JSS node where: install_dir is the path containing the Job Scheduling Services installation program. node is the name of the destination managed node. Installing Tivoli Job Scheduling Services Tivoli Job Scheduling Console User’s Guide 15 .Installing from the Command Line To install the Connector from the command line. You can only install the Connector on managed nodes where Job Scheduling Services is installed. ensure you have set the Tivoli environment (see “Setting the Tivoli Environment” on page 13). 2. You must install Job Scheduling Services on at least the Tivoli management server.

1 . 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.Uninstalling Job Scheduling Services Before you uninstall Job Scheduling Services. then Install Patch. Follow the instructions presented online. To uninstall Job Scheduling Services. then: 1. ensure you have uninstalled the Workload Scheduler for z/OS Connector. From the Desktop menu select Install. Installing Patches To install patches. 16 Version 8. or both. and Linux. Open the Tivoli Desktop. HP-UX. ensure you have set the Tivoli environment (see “Setting the Tivoli Environment” on page 13). This removes the Job Scheduling Services classes and installation files. first enter: bash then enter: wuninst TMF_JSS node -rmfiles where: node is the name of the system from which you want to remove Job Scheduling Services. 3. enter: wuninst TMF_JSS node -rmfiles ¶ On Microsoft Windows. the Workload Scheduler Connector. The Install Patch window is displayed. 2.

7. Tivoli Job Scheduling Console User’s Guide 17 . a protocol converter that translates the instructions entered through the console into scheduler commands.1 for Microsoft Windows. The Job Scheduling Console communicates with the Workload Scheduler for z/OS system through the Connector. For information about how to install a Tivoli server or managed node. AIX.2 ¶ TCP/IP network communications.7B for Linux ¶ Tivoli Workload Scheduler for z/OS 8. refer to the Tivoli Framework Planning and Installation Guide and the Tivoli Framework Release Notes. Hardware ¶ CD-ROM drive for installation. You must install the Connector on a Tivoli server or managed node. or Tivoli OPC 2. and Sun Solaris Version 3. Installing Scheduler for z/OS Connector Before Installing Read this information before you install the Connector. Although the Connector must be running to use the console. This chapter explains how to install the Workload Scheduler for z/OS Connector. “Installing the Tivoli Job Scheduling Console” on page 33 explains how to install the Job Scheduling Console. HP-UX. while the Job Scheduling Console can be installed on any workstation that has a TCP/IP connection with the machine running the Connector. 3. you can install them in the order you prefer.1 or later ¶ Tivoli Job Scheduling Services 1. You can create the account beforehand. ¶ A Workload Scheduler for z/OS user account is required for proper installation.1. or have the Setup program create it for you. System Requirements The Connector has the following system requirements: Software ¶ Tivoli Management Framework: Version 3.3 Installing the Tivoli Workload Scheduler for z/OS Connector This chapter describes how to install the Tivoli Workload Scheduler for z/OS Connector. “Installing the Tivoli Workload Scheduler Connector” on page 25 explains how to install the Workload Scheduler Connector.

If you want to re-install the Connector. Note: Ensure that you have already installed Job Scheduling Services. DOS shell Enter this command . 2. Creating Connector instances. Installing the Connector on the Tivoli server. UNIX shell Microsoft Windows./etc/Tivoli/setup_env.8 ¶ Linux Red Hat 7.. Standard agents require less. HP-UX. 5.¶ Approximately 100 MB of free disk space for domain managers. ¶ 128 MB RAM and 128 MB swap space for domain managers and fault-tolerant agents. Setting the Tivoli Environment To install the Connector. see “Installing Tivoli Job Scheduling Services” on page 13.1 ¶ HP-UX PA-RISC 11. the Workload Scheduler for z/OS produces log files and temporary files.c:/windir/system32/drivers/etc/Tivoli/setup_env. 11i ¶ Sun Solaris 2. See “Uninstalling the Connector” on page 22.1 Job Scheduling Services Job Scheduling Services 1.0. and fault-tolerant agents. 4.cmd 18 Version 8.3. You can install the Connector either from the Tivoli desktop or from the command line. The Connector instance name must be unique within the scheduler network. Linux Microsoft Windows.sh .0 with Service Pack 5 or Service Pack 6a Professional. then enter one of the following commands: Table 5. You must create one instance for each engine that you want to access from the Job Scheduling Console. and Advanced Server 2000 with Service Pack 1 and Service Pack 2 ¶ IBM AIX 4. If you have not yet done so.. you must uninstall the existing one before you do. AIX. Approximately 40 MB for standard agents. Installing the Connector Installation comprises the following: 1. .3s. Solaris. you must first set the Tivoli environment..1 . To do this.3.3. 2. In addition. log in as root or administrator. and the amount of time you choose to retain log files.2 must be installed in your Tivoli environment before you install the Connector. which are placed on the local hard drive. The amount of space required depends on the number of jobs managed by Workload Scheduler for z/OS.sh c:\windir\system32\drivers\etc\Tivoli\setup_env. Server. Setting the Tivoli Environment For this operating system . Supported Platforms The Tivoli Workload Scheduler for z/OS Connector is supported on the following platforms: ¶ Microsoft Windows: NT 4..7.

In the Available Clients list. Tivoli Job Scheduling Console User’s Guide 19 . You must install the Connector on at least the Tivoli management server. Type or select the installation path. the message Finished product installation appears. 9. You can create instances only on managed nodes where the Connector is installed. Click Set Media & Close. ensure you have set the Tivoli environment (see “Setting the Tivoli Environment” on page 18). then: 1.LST file. From the Desktop menu. then enter one of the following commands: ¶ To install on all managed nodes: winstall -c install_dir -i opc ¶ To install on only one managed node: winstall -c install_dir -i opc node where: install_dir is the path containing the Connector installation program. 8. The installation program copies the files and configures the Tivoli database with the new classes. 6. which shows you the progress of the installation. 10. 3. The Install Product window is displayed. ensure you have set the Tivoli environment (see “Setting the Tivoli Environment” on page 18). You return to the Install Product window. 2. Click Select Media to select the installation directory. The Product Install window is displayed. Select Tivoli OPC Connector. You can create instances only on managed nodes where the Connector is installed. The File Browser window is displayed. Installing from the Command Line To install the Connector from the command line. Click Continue Install to continue the installation or click Cancel to cancel the installation. Click Close. Installing Scheduler for z/OS Connector Note: You must install the Connector on at least the Tivoli management server. Installing from the Tivoli Desktop To install the Connector from the Tivoli Desktop. Open the Tivoli Desktop. 5. When the installation is complete. 7. select Install. then Install Product. select the managed nodes to install on and move them to the Clients to Install On list. 4.where windir is the name of the Microsoft Windows installation directory. The path includes the directory containing the CONTENTS. node is the name of the destination managed node. 3. Click Install.

To do this: 1. Select choice number 1 in the first menu. Authorization Roles Required for Instances To manage Connector instances from a Tivoli server or managed node. you must be a Tivoli administrator with one or more of the following roles: Table 6. Enter the following command on the Tivoli server or managed node where you installed the Connector that you need to access through the Job Scheduling Console: wopcconn -create [-h node] -e engine_name -a address -p port where: node is the name or the ID of the managed node on which you are creating the instance. To create an instance. enter wopcconn with no arguments. For more information refer to “Authorization Roles Required for Instances”. The name of the Tivoli server is the default. Note: You must be a Tivoli administrator with admin. You can also run the wopcconn utility in interactive mode..1 . user admin. address is the IP address of the z/OS system where the scheduler subsystem that you want to connect to is installed. port is the port number of the TCP/IP server to which the Connector will connect. On the command line. the TCP/IP server associates each Tivoli administrator to a Remote Access Control Facility (RACF®) user. a 20 Version 8. Use the instances View instance settings Perform all actions available to the user role Create and remove instances Change instance settings Start and stop instances Note: To control access to the scheduler. For this reason. provide the information that enables the Connector to connect to the TCP/IP server..Customizing the Connector This section describes how to customize the Connector. refer to the Tivoli Workload Scheduler for z/OS Installation Guide. Creating Connector Instances Create one Connector instance for each engine that you want to access with the Tivoli Job Scheduling Console. or super authorization roles. For information about activating server support for TCP/IP. super Can perform these tasks . 2. senior. Authorization Roles These roles .. engine_name is the name of the new instance. senior..

and manage Connector instances. trace_length is the maximum length of the trace file. address is the IP address of the z/OS system where the Workload Scheduler for z/OS subsystem that you want to connect to is installed. object_id is the object ID of the instance.... Create an instance Stop an instance Start an instance Restart an instance Remove an instance View the settings of an instance.. port is the port number of the Workload Scheduler for z/OS TCP/IP server to which the Connector must connect. See “Setting the Tivoli Environment” on page 18. The following table describes how to use wopcconn on the command line to manage Connector instances: To do this . you must set the Tivoli environment. Also view other information. The name of the Tivoli server is the default. new_name is the new name for the instance. engine_name is the name of the new or existing instance.Tivoli administrator should be defined for every RACF user. wopcconn -create -h node -e engine_name -a address -p port wopcconn -stop -e engine_name | -o object_id wopcconn -start -e engine_name | -o object_id wopcconn -restart -e engine_name | -o object_id wopcconn -remove -e engine_name | -o object_id wopcconn -view -e engine_name | -o object_id 3. such as product version and the object ID of the instance. trace_level is the trace detail level. refer to the Tivoli Workload Scheduler for z/OS Customization and Tuning book. Managing Connector Instances Use the wopcconn utility to create. Note: Before you use wopcconn. Change the settings of an instance Use this command . Installing Scheduler for z/OS Connector wopcconn -view -e engine_name | -o object_id -n new_name -a address -p port -t trace_level -l trace_length where: node is the name or the object ID (OID) of the managed node on which you are creating the instance. This program is downloaded when you install the Connector. from 0 to 5. Tivoli Job Scheduling Console User’s Guide 21 . For additional information. remove.

ensure you have set the Tivoli environment (see “Setting the Tivoli Environment” on page 18). Lists the patches installed on the Tivoli server. wlookup -ar ProductInfo wlookup -ar PatchInfo Performs this function . From the Desktop menu select Install. first enter: $bash then enter: wuninst OPCConnector node -rmfiles where: node is the name of the system from which you want to remove the Connector. Follow the instructions presented online. Lists the products installed on the Tivoli server. without arguments. then: 1. Uninstalling the Connector To uninstall the Connector. simply enter the command..1 . then enter one of the following commands: ¶ On AIX. To uninstall the Connector from all the managed nodes on which it is installed. then Install Patch. Refer to the Tivoli Framework Reference Guide for more details. This command removes: ¶ The Connector files ¶ All the defined Connector instances ¶ All the related class definitions Installing Patches To install patches. The Install Patch window is displayed. Open the Tivoli Desktop.. in the command line. ensure you have set the Tivoli environment (see “Setting the Tivoli Environment” on page 18).You can also use wopcconn in interactive mode. Useful Framework Commands This command . Table 7. 3. replace node with the name of the Tivoli server. Solaris.. enter: wuninst OPCConnector node -rmfiles ¶ On Microsoft Windows. Useful Framework Commands These commands can be used to check your Framework environment. 22 Version 8. and Linux.. HP-UX. To do this. 2.

wuninst -list Lists all the products that can be uninstalled..Table 7. wuninst {ProductName} -list Lists the managed nodes where a product is installed. Lists the instances of this class type (same for the other classes). In a multi-Tivoli environment.2.. For example:: barb 1318267480.. 3.19#Maestro::Engine# The number before the first period (. Installing Scheduler for z/OS Connector Tivoli Job Scheduling Console User’s Guide 23 . wlookup -ar MaestroEngine Performs this function . you can determine where a particular instance is installed by looking at this number because all Tivoli regions have a unique ID.) is the region number and the second number is the managed node ID (1 is the Tivoli server).. Useful Framework Commands (continued) This command .

24 Version 8.1 .

Approximately 40 MB for standard agents. refer to the Tivoli Framework Planning and Installation Guide and the Tivoli Framework Release Notes.4.1 ¶ Tivoli Job Scheduling Services 1. which are placed on the local hard drive. while the Job Scheduling Console can be installed on any workstation that has a TCP/IP connection with the machine running the Connector.1 for Microsoft Windows. HP-UX.7. and fault-tolerant agents. System Requirements The Connector has the following system requirements: Software ¶ Tivoli Management Framework: Version 3.2 ¶ TCP/IP network communications. a protocol converter that translates the instructions entered through the console into scheduler commands. You can create the account beforehand. you can install them in the order you prefer. Hardware ¶ CD-ROM drive for installation ¶ Approximately 100 MB of free disk space for domain managers. The amount of space required depends on the number of jobs managed by Workload Scheduler. Installing Scheduler Connector 4 Installing the Tivoli Workload Scheduler Connector This chapter describes how to install the Tivoli Workload Scheduler Connector. You must install the Connector on a Tivoli server or managed node. Tivoli Job Scheduling Console User’s Guide 25 . ¶ A Workload Scheduler user account is required for proper installation. The Job Scheduling Console communicates with the Tivoli Workload Scheduler system through the Connector.7B for Linux ¶ Tivoli Workload Scheduler 8. or have the Setup program create it for you. the Workload Scheduler produces log files and temporary files. In addition. For information about how to install a Tivoli server or managed node. and the amount of time you choose to retain log files. Although the Connector must be running to use the console. AIX. and Sun Solaris Version 3. Before Installing Read this information before you install the Connector.

If you have more than one node where you want to install the Connector (for example. You can do this during installation by using the Create Instance checkbox and completing the required fields.3. 11i ¶ Sun Solaris 2. 4. You must also create a Connector instance for the Tivoli server.1 . ¶ When the Workload Scheduler master is on a Tivoli server. Ensure that you do not select the Create Instance checkbox.1 Job Scheduling Services Job Scheduling Services 1. you must install Job Scheduling Services on the Tivoli Server and on the managed node where the master is located. After you have installed the connector on the workstations in your network. Workload Scheduler Master The Connector installation and customization varies depending on whether your Workload Scheduler master is on a Tivoli Server or on a managed node. However. in this case you should deselect the Create Instance checkbox. ¶ When the Workload Scheduler master is on a managed node. because each instance must have a unique name in the Workload Scheduler network. you can proceed with the creation of Connector instances on the machines you need to access the scheduler through the Job Scheduling Console. so you must create each instance separately.1 ¶ HP-UX PA-RISC 11. In addition.3s. and Advanced Server 2000 with Service Pack 1 and Service Pack 2 ¶ IBM AIX 4.¶ 128 MB RAM and 128 MB swap space for domain managers and fault-tolerant agents. must have Job Scheduling Services and a Connector installed. if you want to access the local data of a fault-tolerant agent through the Job Scheduling Console).8 ¶ Linux Red Hat 7. Note: Each Connector instance name must be unique within the Workload Scheduler network. you must install both the Job Scheduling Services and the Connector on the Tivoli server of your environment. there must be a unique Connector instance for each installation you need to access through the Job Scheduling Console. you can install the connector on multiple machines. use the name of the scheduler agent as the instance name. 5. Preferably. 2.0 with Service Pack 5 or Service Pack 6a Professional. Standard agents require less. 26 Version 8.0. Server.3. Fault-tolerant Agents Workload Scheduler fault-tolerant agents that are accessed through the Job Scheduling Console to check local data.2 must be installed in your Tivoli environment before you install the Connector. Supported Platforms The Tivoli Workload Scheduler Connector is supported on the following platforms: ¶ Microsoft Windows: NT 4. You must then install the Connector on the Tivoli server and on the same nodes where you installed Job Scheduling Services.7.3.

sh c:\windir\system32\drivers\etc\Tivoli\setup_env. 2. if you want to access local data on the fault-tolerant agent from the Job Scheduling Console.. HP-UX.cmd where windir is the name of the Microsoft Windows installation directory. DOS shell Enter this command . Installing Scheduler Connector Note: Each Connector instance name must be unique within your scheduler network. Skip this step if you have already done this. 3. If you want to re-install the Connector. Creating the Connector instance. UNIX shell Microsoft Windows. Note: Ensure that you have already installed Job Scheduling Services. Click Select Media to select the installation directory. and must be installed on the Tivoli server. you must first set the Tivoli environment. Note: Job Scheduling Services must be installed before the Connector. 2. Tivoli Job Scheduling Console User’s Guide 27 . If you have not yet done so. log in as root or administrator. Installing the Connector Installation comprises the following: 1. AIX. Setting the Tivoli Environment For this operating system . Open the Tivoli Desktop. The Connector instance name must be unique within the scheduler network. The File Browser window is displayed. then enter one of the following commands: Table 8. The Install Product window is displayed. To do this. Installing the Connector on the Tivoli server. You can also install the connector on a fault-tolerant agent.sh . Linux Microsoft Windows.4. then Install Product. Installing Job Scheduling Services (see “Installing Tivoli Job Scheduling Services” on page 13). There must be one instance for every Workload Scheduler engine you want to access through the Job Scheduling Console. You can install the Connector either from the Tivoli desktop or from the command line. ensure you have set the Tivoli environment (see “Setting the Tivoli Environment”). From the Desktop menu choose Install. then: 1.c:/windir/system32/drivers/etc/Tivoli/setup_env. Installing from the Tivoli Desktop To install the Connector from the Tivoli Desktop.. Setting the Tivoli Environment To install the Connector. . 3. see “Installing Tivoli Job Scheduling Services” on page 13. Solaris.. See “Uninstalling the Connector” on page 31. Where to Install Install the Connector on the Tivoli server and on the managed node where the scheduler master is installed. you must uninstall the existing one before you do../etc/Tivoli/setup_env.

click Install. because you can perform the installation simultaneously on all the nodes while creating the instance locally using wtwsconn. 9. In the TWS directory field. You can install the Connector only on managed nodes on which Job Scheduling Services is installed. 6. Click Set Media & Close.1 . You return to the Install Product window. Creating the Connector instance later is recommended when installing the Connector on multiple nodes.LST file. These fields are used only during the creation of the Connector Instance. In the Available Clients list. Click Continue Install to continue the installation or click Cancel to cancel the installation. Type or select the installation path. The Install Options window is displayed. because the instance name must be unique within the Workload Scheduler Network. you can create it later by using the wtwsconn utility from the command line (see “Creating Connector Instances” on page 29). Installing from the Command Line To install the Connector from the command line. specify a name for the Workload Scheduler instance on the managed node. select Tivoli TWS Connector. specify the directory where Workload Scheduler is installed. When the installation is complete.4. 11. Select the Create Instance checkbox. In the Install Product window. This window enables you to: ¶ Install the Connector only. The Product Install window is displayed. To install the Connector without creating a Connector instance. then enter one of the following commands: ¶ To install on all managed nodes: 28 Version 8. ensure you have set the Tivoli environment (see “Setting the Tivoli Environment” on page 27). which shows you the progress of the installation. Note: If you decide not to create the instance at this time. The installation program copies the files and configures the Tivoli database with the new classes. leave the Create Instance checkbox clear and leave the General Installation Options fields blank. 12. This name must be unique in the network. To install the Connector and create a Connector Instance: a. 14. You must install the Connector on at least the Tivoli management server. 10. In the TWS instance name field. This path includes the directory containing the CONTENTS. you must select only one node from the list. c. 8. Note: If you choose to create a Connector instance during the installation. b. ¶ Install the Connector and create a Connector instance. Click Close. 5. the message Finished product installation appears. 13. Click Set to close the Install Options window and return to the Install Product window. 7. select the nodes to install on and move them to the Clients to Install On list. In the Select Product to Install list.

You can create instances only on managed nodes where the Connector is installed. The name must be unique within the scheduler network. This is the Workload Scheduler installation directory on the specified node. Customizing the Connector This section describes how to customize the Connector. you must be a Tivoli administrator with one or more of the following roles: Tivoli Job Scheduling Console User’s Guide 29 . senior. For more information refer to “Authorization Roles Required for Instances”. or super authorization roles. Creating Connector Instances Create one Connector instance for each engine that you want to access with the Job Scheduling Console. you must be a Tivoli administrator with admin. Installing Scheduler Connector winstall -c install_dir -i TWS_CONN twsdir=/users/maestro iname= instance_name owner=maestro ¶ To install on only one managed node: winstall -c install_dir -i twsdir=/users/maestro iname=instance_name owner=maestro createinst=1 node where: install_dir is the path containing the Job Scheduling Services installation program. it defaults to the node where the script file is run. instance_name is the name of the new instance. instance_name is the name of the instance that appears in the Job Scheduling view.4. This name identifies the engine node in the Job Scheduling tree of the Job Scheduling Console. You must install the Connector on at least the Tivoli management server. maestro is the owner name. To create an instance. Enter the following command on the Tivoli server or managed node where you installed the Connector that you need to access through the Job Scheduling Console: wtwsconn -create -h node -n instance_name -t TWS_directory where: node specifies the node where the instance is created. Authorization Roles Required for Instances To manage Connector instances from a Tivoli server or managed node. node is the name of the destination managed node. TWS_directory specifies the value for the TWSdir attribute. If not specified.

sh -view -n instance wtwsconn. For additional information..sh -create [-h node] -n instance -t twsdir wtwsconn.Table 9. the TCP/IP server associates each Tivoli administrator to a Remote Access Control Facility (RACF) user. Use the instances View instance settings Perform all actions available to the user role Create and remove instances Change instance settings Start and stop instances Note: To control access to the scheduler. When -t twsdir is specified.sh -stop -n instance | -t twsdir Two stop actions are supported: When -n instance is specified. a Tivoli administrator should be defined for every RACF user. This program is downloaded when you install the Connector.1 . Change the settings of an instance wtwsconn. you must set the Tivoli environment. all the instances on this node (the node where the script is run) whose TWSdir attribute matches twsdir are stopped. To do this .. If not specified. For this reason. refer to the Tivoli Workload Scheduler for z/OS: Customization and Tuning book. See “Setting the Tivoli Environment” on page 27. The following table describes how to use wtwsconn in the command line to manage Connector instances. it defaults to the node where the script is run from. 30 Version 8.sh -remove -n instance wtwsconn. remove. Managing Connector Instances Use the wtwsconn utility to create... Remove an instance View the settings of an instance...sh -set -n instance -t twsdir where: node specifies the node where instance is created. super Can perform these tasks . the instance with that name is stopped. This name identifies the engine node in the Job Scheduling tree of the Job Scheduling Console. and manage connector instances. instance is the name of the new instance. senior. user admin. Authorization Roles These roles . The name must be unique within the scheduler network.. Note: Before you use wtwsconn.. wtwsconn. Create an instance Stop an instance Use this command .

then enter one of the following commands: ¶ On AIX. Updating Workload Scheduler Security Before you update Workload Scheduler security. first enter: $bash then enter: wuninst TWSConnector node -rmfiles where: node is the name of the system from which you want to remove the Connector. then Install Patch. This is the Workload Scheduler installation directory in node.4. you must add the scheduler user as a Tivoli administrator on the Tivoli desktop. Open the Tivoli Desktop. HP-UX. ¶ Create a Tivoli administrator that has the login of the user. Solaris. Enter: dumpsec >tempsec 4. The Install Patch window is displayed. Uninstalling the Connector To uninstall the Connector. Open the Tivoli desktop. Installing Scheduler Connector twsdir specifies the value for the scheduler dir attribute. TWSuser or maestro). then: 1. Change directory to TWS home. To update the scheduler security file: 1. ensure you have set the Tivoli environment (see “Setting the Tivoli Environment” on page 27). Tivoli Job Scheduling Console User’s Guide 31 . ensure you have set the Tivoli environment (see “Setting the Tivoli Environment” on page 27). Installing Patches To install patches. and Linux: wuninst TWSConnector node -rmfiles ¶ On Microsoft Windows. then removes Connector classes and installation files. 3. 2. 2. Edit the tempsec file so it contains the Admin name. Follow the instructions presented online. Do one of the following: ¶ Add the user login to the Edit Logins window for Tivoli Administrators. From the Desktop menu select Install. Login as the user (usually. 2. 3. To do this: 1. This stops all Connector processes.

Refer to the Tivoli Framework Reference Guide for more details. 6.2..) is the region number and the second number is the managed node ID (1 is the Tivoli server). Lists the products installed on the Tivoli server. you can determine where a particular instance is installed by looking at this number because all Tivoli regions have a unique ID. wuninst -list Lists all the products that can be uninstalled. 5.. Usually the name looks like Root_dallas-region. wmaeutil Maestro -Version * Lists the versions of the installed engine. 32 Version 8. In a multi-Tivoli environment. Lists the installation directory of the Connector. Useful Framework Commands This command . Enter: wmaeutil ALL -stop This stops the Connector. Enter: makesec tempsec Useful Framework Commands These commands can be used to check your Framework environment. wlookup -ar ProductInfo wlookup -ar PatchInfo wlookup -ar MaestroEngine Performs this function . and plan. open the Tivoli desktop and double-click Administrators. database. The Admin name is the Administrators group to which your login belongs... Lists the patches installed on the Tivoli server. wmaeutil Maestro -dbinfo * wmaeutil Maestro -gethome Lists information about the database and the plan. Table 10. wuninst {ProductName} -list Lists the managed nodes where a product is installed. Lists the instances of this class type (same for the other classes).19#Maestro::Engine# The number before the first period (. If the Admin name contains a blank. enclose it in double quotes. For example:: barb 1318267480.Note: To get the Admin name.1 .

HP-UX Sun Solaris. or 34 MB for customized (English base) installation plus approximately 4 MB for each additional language Tivoli Job Scheduling Console User’s Guide 33 .. Installing the Tivoli Job Scheduling Console Before Installing Read this information before you install the Job Scheduling Console. Microsoft Windows (see “Supported Platforms” on page 34) AIX.2 ¶ Tivoli Workload Scheduler for z/OS Version 8. Job Scheduling Console Supported Platforms To install on this operating system .3 Hardware ¶ CD-ROM drive for installation ¶ 70 MB disk space for full installation.5 Installing the Tivoli Job Scheduling Console This chapter describes how to install the Tivoli Job Scheduling Console on each of the following operating systems: Table 11.1 or later ¶ Tivoli Job Scheduling Services 1. System Requirements The 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. Linux Go to page .2 ¶ TCP/IP network communication ¶ Java Runtime Environment Version 1.1 or OPC 2.... 35 36 38 5.

0 or 8.1 .8 ¶ Linux Red Hat 7.0 with Service Pack 5 or Service Pack 6a Professional.3 Hardware ¶ CD-ROM drive for installation ¶ 70 MB disk space for full installation. 2.3s.3. and Advanced Server 2000 with Service Pack 1 and Service Pack 2 98 Millennium Edition ¶ IBM AIX 4.0. Server.1 ¶ Tivoli Job Scheduling Services 1.3. or 34 MB for customized (English base) installation plus approximately 4 MB for each additional language Supported Platforms The Job Scheduling Console is supported on the following platforms: ¶ Microsoft Windows: NT 4. 11i ¶ Sun Solaris 2.1 ¶ HP-UX PA-RISC 11.7. 4.2 ¶ TCP/IP network communication ¶ Java Runtime Environment Version 1.1 34 Version 8. 5.For Use With Tivoli Workload Scheduler Software ¶ Tivoli Workload Scheduler Connector ¶ Tivoli Workload Scheduler Version 7.3.

If you need to. 6. English is the default. b. This window leads you through the installation process. to move through these windows. Next. You can use the Previous. A progress information window is displayed. click Customize. 10. The Job Scheduling Console displays in your selected language only if the language matches the regional settings of your computer. 11. 12. the Install Complete window is displayed. This displays a drop-down list containing all the available languages in which you can perform installation. 7. A progress information window is displayed. 2.Installing on Microsoft Windows To install the Job Scheduling Console on Microsoft Windows: 1. enter: drv:\Install where: drv: is the name of the CD-ROM drive. The Choose Shortcut Location window is displayed. Click Next. besides English. Insert the Tivoli Job Scheduling Console CD-ROM into the CD-ROM drive. 5. Click Install. Enter the path where you want to install the Job Scheduling Console. 5. Click Next. you want to install the Job Scheduling Console. The Choose Install Set window is displayed. Click one of the available radio buttons to specify where the Job Scheduling Console buttons are to be placed. or Exit buttons. Click Start and select Run. when enabled. When installation is finished. Select in which languages. or select Choose to open the Select a folder window where you can specify another location. Click Next. If it does not. 3. Click Done to close the window. If you want to select the languages installed with the Job Scheduling Console (Customized Install). language and time zone settings of your system. The Job Scheduling Console splash window is displayed. The Introduction window is displayed. If you want to install the Job Scheduling Console in all available languages (Full Package). 9. In the Open field. click Install. Click the down arrow in the language field. edit the default location provided in the field. 8. Notes: a. 13. Installing the Tivoli Job Scheduling Console Tivoli Job Scheduling Console User’s Guide 35 . 14. 4. displaying a series of option windows that enable you to provide the necessary information. The Choose Install Folder window is displayed. Select your language and click OK. Go to Step 13. The Job Scheduling Console is now installed. The Customize Install window is displayed. Continue with Step 12. The Job Scheduling Console automatically adjusts to the country.

A progress information window is displayed. Click the down arrow in the language field. Select your language and click OK. Mount the CD-ROM drive. Ensure that the Java Runtime Environment is installed. A progress information window is displayed. the Install Complete window is displayed.Installing on AIX and HP-UX To install the Job Scheduling Console on AIX: 1. 12. 2. If you want to install the Job scheduling Console in all available languages (Full Package).bin The Job Scheduling Console splash window is displayed. Add to your system path the . You can use the Previous. displaying a series of option windows that enable you to provide the necessary information. edit the default location provided in the field. Enter: sh install. 5. besides English. Enter the path where you want to install the Job Scheduling Console./jre/bin subdirectory of the directory where you installed the Job Scheduling Console. If in doubt. The window leads you through the installation process. click Customize. Select in which languages. Continue with Step 11. click Install.. 3. The Choose Install Set window is displayed. 9. refer to your system administrator. Click Next. If you need to. If it does not. Click Done. Notes: a. to move through these windows. The Choose Install Folder window is displayed. Next. The Job Scheduling Console is installed.1 . you must update the AIXconsole.sh file with the path where you installed the Java Runtime Environment. 7. Click Next. This displays a drop-down list containing all the available languages in which you can perform installation. you want to install the Job Scheduling Console. Go to Step 12. language and time zone settings of your system. 8. Updating AIXconsole. The Introduction window is displayed. Click Install. 4. English is the default. or select Choose to open the Select a folder window where you can specify another location. 11. or Exit buttons. When installation is finished. 10. b. If you want to select the languages installed with the Job Scheduling Console (Customized Install). 36 Version 8. when enabled. 13. The Job Scheduling Console automatically adjusts to the country.sh To complete installation. The Customize Install window is displayed. The Job Scheduling Console displays in your selected language only if the language matches the regional settings of your computer. 6.

Find the following statement: JAVAPATH=%ENTRY% 4.sh in editing mode. Save your changes and exit the editor. You can now start the Job Scheduling Console. Installing the Tivoli Job Scheduling Console Tivoli Job Scheduling Console User’s Guide 37 . 2. Open AIXconsole. 5. Go to the /bin/java subdirectory of the directory where you installed the Job Scheduling Console. 5.To do this: 1. 3. Change %ENTRY% with the path to the Java Runtime Environment.

Click the down arrow in the language field. language and time zone settings of your system. Click Done. 6. The Job Scheduling Console is installed. The Job Scheduling Console automatically adjusts to the country. 9. You can use the Previous. Select in which languages. Click Install. 2. A progress information window is displayed. 11. Go to Step 12. when enabled. 10. edit the default location provided in the field. The Introduction window is displayed. 3.bin The Job Scheduling Console splash window is displayed. If you want to select the languages installed with the Job Scheduling Console (Customized Install). The Customize Install window is displayed. 13. Enter the path where you want to install the Job Scheduling Console. displaying a series of option windows that enable you to provide the necessary information. When installation is finished. 7. 38 Version 8. Click Next. 4. you want to install the Job Scheduling Console. Click Next.zip file before running the installer. 8. Notes: a. This displays a drop-down list containing all the available languages in which you can perform installation. Change to the directory where you downloaded the install. 12. If you want to install the Job Scheduling Console in all available languages (Full Package). The Choose Shortcut Location window is displayed. If you need to.1 . The Choose Install Set window is displayed. If it does not. Enter: sh install. This window leads you through the installation process. besides English. The Choose Install Folder window is displayed. Select your language and click OK. 5. or Exit buttons. or select Choose to open the Select a folder window where you can specify another location. Click Next.Installing on Solaris and Linux To install the Job Scheduling Console on Solaris: 1. click Install. A progress information window is displayed. to move through these windows. the Install Complete window is displayed. Select one of the available radio buttons to specify where the Job Scheduling Console buttons are to be placed. The Job Scheduling Console displays in your selected language only if the language matches the regional settings of your computer. English is the default. click Customize. b. Next. Continue with Step 11.

Microsoft Windows NT.sh Enter . start the Job Scheduling Console in one of the following ways: Table 12. 5.sh The Tivoli Job Scheduling Console startup window is displayed. 8./HPconsole. Enter NTconsole Enter console 5. Click Cancel to close the window and work with the Job Scheduling Console without online assistance. 2000 Microsoft Windows 98. ¶ Click Cancel to use default user preferences./SUNconsole. enter the user ID of the Tivoli administrator of the host machine running the scheduler engine. If you are logging onto the managed node of Host Machine for the first time.. In the Password field. telling you how to specify a user preference file for initialization. 3. 2. Do one of the following: ¶ Specify a URL where user preferences are defined. AIX SUN Solaris HP-UX Linux Enter . Click OK to continue. 9. Do one of the following: Select a radio button. an information pop-up is displayed. Depending on your platform.sh Enter . Click OK. ME In the . Installing the Tivoli Job Scheduling Console Note: You can also start the Job Scheduling Console by double-clicking the Job Scheduling Console button on the Windows Desktop or by selecting the corresponding item from the Start menu. if it exists.. The Welcome window is displayed.. Starting the Job Scheduling Console On this platform .sh Enter ./AIXconsole. In the Login As field.Starting the Job Scheduling Console 1. then click OK to start working with the Job Scheduling Console.\bin\java subdirectory of the installation path . enter the password to the host machine running the scheduler Connector 4.. In the Host Machine field. enter the name of the Tivoli managed node that runs the scheduler Connector. 6. 7./LINUXconsole. The Open Location window is displayed. Tivoli Job Scheduling Console User’s Guide 39 .. ¶ Click Get from file to open a window from where you can select a file that contains initialization data. Enter the URL and click on Load from URL.

Uninstalling the Job Scheduling Console Uninstalling on Microsoft Windows To uninstall the Job Scheduling Console on Microsoft Windows: 1. and click Uninstall Tivoli Job Scheduling Console. Solaris. Click Uninstall. 2. The InstallAnywhere Uninstaller window is displayed.1 . Uninstalling on AIX. Use the Start menu to go to the shortcut location that you specified during installation. it lists any files that the program was not able to uninstall. and Linux To uninstall the Job Scheduling Console on UNIX platforms. go to the /UninstallerData subdirectory of the installation path and enter: . 3. HP-UX. Click Exit to close the window and end the uninstall process. When the process completes. A progress indicator is displayed./Uninstall_JSconsole 40 Version 8. You will need to delete those files manually.

6. Job Scheduling View The view consists of two panes. This can be either a number of list objects or the contents of a list in the shape of a table or a Gantt chart. 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. or other). you can right-click your intended engine to open a pop-up menu displaying the same options for creating lists. Workload Scheduler for z/OS. The upper part of the Job Scheduling view contains the menu bar and a number of buttons. Working with the Job Scheduling Console Figure 1. The left pane is a tree view that displays your scheduler engines (Workload Scheduler.6 Working with the Job Scheduling Console The Job Scheduling View The Job Scheduling view is the main window of the Job Scheduling Console. groups of lists. Tivoli Job Scheduling Console User’s Guide 41 . and objects in the database. If you expand any of the objects that represent the scheduler engines. The right-hand pane displays a detailed view of the object selected in the tree. you see the lists and groups of lists available for that particular engine.

where you create a filtered list of selected job streams scheduled in the plan.Scheduler window. where you create a filtered list of selected resources.1 . job dependencies. Displays the Properties . Displays the Properties . where you define job stream properties and create jobs. and run cycles. If you have selected a list. Displays the properties of the object selected in the tree view. it opens the Properties window of that list.Job Definition window.. List resources defined in the database. Displays the Properties . 42 Version 8. and availability intervals. it displays the Properties window of the job stream. Delete the object selected in the tree view. Displays the Properties . Create a job in the database. Job Scheduling View Buttons Use this button .Using the Buttons of the Job Scheduling View Use the following buttons. Opens the Properties .Job Stream Instance List window. where you create a filtered list of selected workstations. If you have opened the Job Stream Editor. Create a workstation in the database. If you have selected a scheduler. Refresh the results of a list. Create a resource in the database.. associated workstations. where you define workstation properties. where you create a filtered list of selected jobs. Displays the Properties Workstation in Database window. Browse or modify the properties of the selected object.. and availability intervals. Click the button to reload the results of the list on display in the right-hand pane of the Job Scheduling view.. Displays the Job Stream Editor window.Resource window. instead if the list displaying in the right hand pane of the Job Scheduling view.Database Resource List window. or to create a list of objects defined in the database or in the plan: Table 13. resources. to create an object in the scheduler database.Job List window. List job stream instances in the plan. Create a job stream in the database. it opens the Properties . This button becomes available only after you have opened a list. Open a resource list in a separate window (detached view). List job streams defined in the database. located in the toolbar of the Job Scheduling view. Displays the Properties Database Workstation List window. Lists jobs defined in the database. This button is active while the results of a list are being uploaded. Stop loading a list. where you define a resource properties. List workstations defined in the database. To do this .

In the right-hand pane.Plan Resource List window. Note: Remember to select your intended engine in the tree before you use an button to create or to list an object. you must create and display a list of the objects. To display the initial layout..Table 13. update. Properties Delete Open Detach View To do this . In the tree view. The group is added to the tree of your selected scheduler and you can thereafter create lists as part of it.. you can only double-click a list to display its results. where you enter a name for the new group. many of the buttons described above disappear from the Job Scheduling view. Default Lists The console provides default lists for every scheduler engine in your installation. where you create a filtered list of selected resources allocated to the plan. Default lists are general. the Job Scheduling Console selects the first engine in the list. where you create a filtered list of selected workstations allocated to the plan.Group of Lists window. Open the list properties window. List job instances in the plan.. There is a default list for each type of scheduler object.. Job Scheduling View Buttons (continued) Use this button . List workstations in the plan. To do this . Take the results of a list from the Job Scheduling view and places them in a separate window. List resources in the plan. Right-click one of the lists to open a pop-up menu that displays the following options: Table 14. where you create a filtered list of selected jobs scheduled in the plan. Lists and list groups are displayed both in the tree view and in the right-hand pane of the Job Scheduling view. Displays the Properties . By default. refresh options. collapse the tree view to engine level. Choose this option to change the list name. 6. that is. Working with the Job Scheduling Console Working with Lists To browse. no selection Tivoli Job Scheduling Console User’s Guide 43 . or delete objects already defined in the database and plan. Object List Properties Select this option . Button availability in the Job Scheduling view follows the tasks you perform dynamically. Delete the list from the tree. Displays the Properties . The right-hand pane displays all lists and list groups available for the selected engine. Displays the Properties . For instance.. Create a group of lists. double-click an engine to display the lists available for the engine..Plan Workstation List window.. Run the list and display the results in the right-hand pane of the Job Scheduling view. Displays the Properties .Job Instance List window. or filter criteria.. if you open a list.

2. Default Database Lists This list . All job stream instances. All job instances. You can edit the properties of each default list to add more restrictive selection criteria or to change its name or refresh options... All workstation definitions. including jobs. Table 16.. All job stream definitions.. The status of every resource instance.. Default Plan Lists Table 16 describes the default plan lists. Default lists are grouped in lists that show objects defined in the database and lists that show objects defined in the current plan. Click one of the buttons displayed in the Job Scheduling view... Creating a List To create a list: 1. All Job Streams All Resources All Workstations Shows . All Scheduled Job Streams All Scheduled Jobs Status of all Resources Status of all Workstations Shows . Default Plan Lists This list . You can edit the properties of each default list to add more restrictive selection criteria or to change its name or refresh options. 44 Version 8. Shows the status of every workstation instance. All resource definitions. They therefore list all the existing objects.criteria are specified. The Properties .1 . and run cycles. Table 15.. Default Database Lists Table 15 describes the default database lists.Database Resource List window is displayed. Select an engine in the tree. dependencies.

real letters. The Properties . To do this: 1. select a scheduler engine and click the Properties button in the toolbar.Scheduler window to set or change the following defaults for lists. The more filters you use.Database Resource List Window 3. For lists of resources only. In the Name field. Enter or select filtering criteria from those displayed in the window. The new list is added in the tree under the engine you selected when creating the list. In the Job Scheduling view. use wildcard characters. 6. you can specify if you want the special characters in the search items to be treated as wildcards. This is optional. Open the Settings page and make your adjustments. Periodic refresh Select the check box and type the number of seconds after which a list display will periodically refresh. prefixes. If a default periodic refresh period is already specified in the Properties . 4. Different lists maintain their individual properties even if they have the same name. 2. You can change or deselect the default.Scheduler window is displayed.Figure 2. 5. When you have finished: ¶ Click Apply to display the list results immediately. Specify refresh options for the list. Properties .Scheduler window. Working with the Job Scheduling Console Specifying Defaults for Lists You can use the Properties . You can use combinations of more parameters. See “Specifying Defaults for Lists”. this value is automatically displayed for each new list. or suffixes. This information is Tivoli Job Scheduling Console User’s Guide 45 . all objects are displayed when you open the list. After you do this. If you leave all fields blank. ¶ Click OK to save the list. You can use the same name for more than one list. enter a name for the list. the more restricted is the search. To generalize your search. this information is used every time you click Apply defaults in the properties window of a list.

Delete the group and all its contents. Properties List Options Select this option . For example.Group of Lists Window 3. For example. Select an engine in the tree. or workstation definitions in the database. To create a group of lists: 1. The Properties . Right-click the group to display a pop-up menu with the following options: Table 17. Properties . After creating a group. Creating a Group of Lists The Job Scheduling Console allows you to organize your lists into groups. ¶ Click Cancel to close the window without saving the new group. The default is 50. Properties Delete Create Database List To do this . The value determines at which rate the results of a list are sent onto your screen. select the group and click Create a Group of Lists on the toolbar or right-click the existing group button and select Create Group from the pop-up menu. When you have finished: ¶ Click OK to close the window and save the new group. you can create a group gathering lists that enable you to work with all the objects associated with a particular plan. Change the group name.. Buffer size for lists Select a value from the drop-down list.. you can create its member lists and subgroups. 2. You can organize your groups of lists by any criterion that will help you to quickly display the objects that you want to work with. 46 Version 8.also automatically displayed in editable form in the Periodic Refresh Options group of the properties window of each new list you create.Group of Lists window is displayed. Different groups maintain their individual properties even if they have the same name. Click the Create a Group of Lists button or right-click on the engine button and select Create Group from the pop-up menu. You can use the same name for more than one group. To create a group in an existing group.1 . resource. An button is created for the new group in the tree view of the Job Scheduling Console.. but less time to display the entire list when it is scrolled. it takes more time to display the list initially.. the results of a list are sent in blocks of 100 lines. If you select a higher number. Figure 3. First you must create a group. Create a new list of job stream. if you select 100. then you can create the lists that comprise it. Enter a name for the group.

Create Plan List Create Group To do this . The right-hand pane of the console is not disabled. Create a new list of job streams. double-click the list you want to run. either close the detached window or right-click the list in the tree view and select Attach View from the pop-up menu. Tivoli Job Scheduling Console User’s Guide 47 . double-click an engine.Table 17. 2. resources. The newest list is displayed above the preceding ones. 2.. The list window is displayed separately from the Job Scheduling view. 3. Open a list and wait for the results to be displayed. or workstations in the plan. in the right-hand pane. it is maintained and refreshed according to the refresh options specified. In the tree of the Job Scheduling view.. You can detach multiple lists to view several objects simultaneously. Create a subgroup of more lists.. Right-click the list you want to run and select Load List from the pop-up menu. jobs. Right-click the list in the tree view and select Detach View from the pop-up menu. Notes: 1. You can display several lists in sequence. you can select an engine in the tree and. Displaying a List To display a list: 1. To view the list. Displaying a List Note: Alternatively. Detaching a List Display Detaching a list frees the right-pane of the Job Scheduling Console to display other objects. The list tool searches the database or plan and displays the objects it finds in the right-hand pane of the Job Scheduling view. Working with the Job Scheduling Console Figure 4.. This is so that you can run other lists or perform other tasks. as long as a list is kept open. To detach a list display: 1. However. 6. To place the list back in the right-hand pane. Properties List Options (continued) Select this option . click the corresponding object in the Job Scheduling view.

Finding Objects A contextual find tool in the Job Scheduling Console helps you to find the name of a resource. The list results are displayed in the right pane of the Job Scheduling Console. double-click an engine. To prevent your system from overloading.. 3. The properties window of the list is displayed. 4. Right-click the list you want to delete and select Delete from the pop-up menu. Click OK. An example is shown in the Properties . You can have a maximum number of seven detached views open at the same time. The find tool is available when you can see an ellipsis (.1 .) next to the field where you are asked to enter the name. 3. do not have frequent refreshes of many detached views open at the same time.Workstation in Database window. 2. When you have finished: ¶ Click Apply to run the list without closing the window. Right-click the list you want to modify and select Properties from the pop-up menu. in which the Find tool ellipsis is identified by the cursor arrow. or job stream when you need to provide one. 2. 48 Version 8.. double-click an engine. ¶ Click OK to save the changes and to close the window. ¶ Click Cancel to close the window without running or saving the changes.2. Make your changes. Modifying a List 1. In the tree of the Job Scheduling view. shown in the next figure. 3. Deleting a List 1. job. The list is deleted from the tree. In the tree of the Job Scheduling view. A confirmation message is displayed. workstation.

You can do one or more of the following: ¶ Enter a name in the Find field. Working with the Job Scheduling Console Figure 5. Click the ellipsis. ¶ Select one or more check boxes when available. Find Workstations Window 2. To use the Find tool: 1. Enter your search criteria. Properties .Workstation in Database Window Example: Finding a Workstation The following example shows how you can use the Find tool to enter the name of an alternate workstation when you are defining workstation open time intervals. The Find Workstations window is displayed. Tivoli Job Scheduling Console User’s Guide 49 .6. Figure 6. You can generalize your search by using wildcards or leave the field blank to use no filters.

1 . Click OK to close the Properties . 5. and the objects found are listed at the bottom of the window.Workstation in Database window. Select an object and click Apply. 3. Click Start. 4. The Find window closes and the name of the object is automatically entered in the required field. 50 Version 8. This results in an unfiltered search that produces a list of all the objects (workstations in this example) defined in Workload Scheduler for z/OS.¶ Add no input. The window expands.

. . . . . . . . . . . . . . . . . . . . . . Creating Dependencies between Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 70 72 73 74 74 74 76 76 77 77 77 Chapter 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default Workstation Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 56 60 62 64 64 65 67 67 67 67 68 Chapter 8. . . . . . . Modifying Workstation Properties in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Job Streams . . . Creating Workstations from Existing Ones in the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a List of Workstations in the Database . . . . . . . . . . . . Modifying Resource Properties in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Resources in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Creating Resources . . . . . Managing Workstations in the Database . . . . . . . . . . . . . . . . . . . . . . . . Creating Resources from Existing Ones in the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resource Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Run Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Resource Lists. . . . . . . . . . . Creating a Job . . . . . . . Managing Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Listing Resources in the Database . . . . . . . . . Creating Dependencies within a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Specifying Properties for the Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Open Time Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a List of Resources in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default Workstations Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Creating a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . Availability Intervals Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Workstation from the Database . . . . . . . . . . . . . Deleting Resources from the Database . . . . . . . . . . . . . . . . . . . . Creating a Job Using Copy and Paste . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 82 83 83 86 87 89 90 91 91 92 94 94 94 95 Tivoli Job Scheduling Console User’s Guide 51 . . . . . . . . . . . . . . . . . . Finding a Job Stream. . . . . . . . . . . . . . . . . . . . . . . Using Workstation Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Job Using Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .II — Using the Job Scheduling Console with Tivoli Workload Scheduler for z/OS Chapter 7. . . . . . . . Default Resource Lists. . . . . Displaying a List of Workstations in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Dependencies between Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task Page . . . . . . . . Types of Run Cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Page.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default Instance Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying Job Stream Properties . . . 119 119 120 123 Chapter 12. . . . . . . . Listing and Modifying Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Job or External Job . . . . . . . . . . . . . . . . . . . . . . . . . 109 109 112 112 113 113 113 114 114 114 114 114 115 115 115 117 Chapter 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding and Modifying Jobs and Dependencies in the Graph View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Table Frame . . . . . . . 97 Creating Rule-based Run Cycles . Rescheduling the Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Example 2: Exclusionary Run Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Time Restrictions Page . . 104 Activity Bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Time Restrictions Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Example 1: Rule-based Run Cycle . . . . . . . . . Creating a Job Stream List. 127 Job Stream Instance Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List View . . . . . 103 Checking Time Restrictions in the Timeline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Listing Job Stream and Job Instances . . . . . . . . . . Viewing and Modifying Time Restrictions . . . . . . . . . . . . . . . . . . . Modifying Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Listing Job Instances . Using Existing Definitions to Create Other Job Streams . . . . . . . . . . 103 Example 2: Offset-based Run Cycle Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Example 1: Offset-based Run Cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . Changing Time Restrictions in the Timeline View . . . . . . . . . . Using Copy to Add an External Job . . . . . . . . . . . . . . . . . Managing Job Streams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 . . . . . . . . . . . . . . . . . . . . . . .General Page. . . . . . . . . . . . . . . . . . . . . . . . . Adding and Modifying Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Saving a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timeline View . . . . . Listing Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Job Streams from the Database . 109 Default Job Stream List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Other Tasks . . . . . . . . . . . . . . . . . . 104 Time Restrictions. . . . . . . . . . . . 127 127 127 128 128 129 130 132 133 52 Version 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Example 3: Exclusionary Run Cycle Defined . . . . . . . . . . . . . . . . . . . . 106 Submit a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing Another Job Stream from an External Job . . . . . . . . . . . . . . . . . . . . 101 Creating Offset-based Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing a Dependency between Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rescheduling the Start Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Chapter 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Browsing and Modifying Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a New Job using Copy and Paste . . . . . . . . . . . . . . . . . . . . . 119 Creating Lists of Job Stream and Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a Job . . . . . . . . Displaying a Job Stream List . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Predecessors Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing JCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Browsing and Modifying Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timeline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Putting Job Instances on Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Rescheduling the Deadline Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Browsing and Modifying Job Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set as Root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Details Page . . . . . . . . . . . . . . . . . 162 164 164 165 166 166 167 Tivoli Job Scheduling Console User’s Guide 53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying Job Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rescheduling the Start Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting a Job Stream Instance to Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Page . . . . . . . . . . . . . . . Showing Predecessors and Successors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time Restrictions Page . . . . . . . . . . . . . . . . . . . . Managing Workstations in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Job Instances . . . . . . . . . Displaying Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Jobs . . . . . . . . . . Setting a Job Stream Instance to Complete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resources Page . . . . . . . . . . . . . Removing a Job Instance from the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task Page . . . . . . . . . . 133 134 134 134 135 135 Chapter 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing Time Restrictions in the Timeline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rescheduling the Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Browsing and Modifying Workstation Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Status of a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resources Page . . . . . . . . . . . . . . . . . . . . . . . Job Summary Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Successors Window . . . . . . . . . . . . . . . . . . . . . . Browsing the Job Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Job Instance Lists . . . . . Options Page . . . . . . . . . . . . . . . . . . . . . . . . . General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rescheduling the Deadline Time . . . . . Restoring a Job Instance to the Plan. . . . . . Running a Job Instance Immediately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restart and Cleanup. . . . . . . . . . . Target Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Open Time Intervals Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Operator Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rerunning a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 138 138 139 140 141 142 143 145 146 146 147 148 148 150 152 153 154 154 155 155 155 156 156 157 157 157 158 158 158 159 160 160 160 Chapter 14. . . . . . . . . . . . . . Releasing Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Job Stream Instance . . . . . . . . . . . . 161 Creating a List of Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Linking Fault-Tolerant Workstations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Creating a List of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 176 176 177 179 180 181 181 54 Version 8. . . . . . . . . . . . . . . . 170 170 171 172 Chapter 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Job Instances Associated with a Resource . . . . . . . . . . . . . . . . Displaying by Status the Job Instances Scheduled on a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Browsing and Modifying Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default Workstations Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Resources. . . Modifying Job Instances Associated with a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . Availability Intervals Page . . . . . . Changing Workstation Status and Rerouting Scheduled Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Resources in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the Job Instances Scheduled on a Workstation . . .

It is a stage in the processing that is controlled by the scheduler. the workstation on which the job instance is defined must be available. These are the times when workstation resources and parallel servers are available to process work. Workstations are usually created to represent specific elements in your system configuration. Parallel servers and resources are usually necessary to run work at the workstation. Managing Workstations in the Database 7 Managing Workstations in the Database The Tivoli Workload Scheduler for z/OS environment is defined in terms of resources and workstations. For instance. the accuracy of any planning predictions that the scheduler produces for you depends on how accurately you have described the installation to the scheduler. So.7. A workstation describes how jobs have to be run. Also. Before the scheduler can start a job instance. refer to the Tivoli Workload Scheduler for z/OS Planning and Scheduling the Workload book. The availability of these workstations should reflect the availability of those elements in the real world. a computer workstation might be created for each z/OS system in a scheduler complex. you control the running of job instances that are defined on the workstation. The scheduler establishes the availability of a workstation by using the open intervals in the list of available workstations in the database. This prevents the scheduler from submitting work to a z/OS system that is not physically available. the availability of the computer workstation should reflect the availability of the z/OS system it represents. This chapter describes how to use the Job Scheduling Console to define and administer the availability of workstations. A workstation is not necessarily hardware. So. Tivoli Job Scheduling Console User’s Guide 55 . you must define a workstation beforehand. by controlling workstation availability. For a full description of workstations. To schedule a job instance.

This is where you enter general information for the workstation.Creating a Workstation This section describes how to create a workstation in the Workload Scheduler for z/OS database. The new workstation will be defined in the database of that engine. select the engine in whose database you want to work. then click the New Workstation button in the toolbar.Workstation in Database General Window General Page 56 Version 8. the Properties . In the Job Scheduling view.1 . Figure 7. Properties . General Page When you click the New Workstation button.Workstation in Database General page is displayed.

Managing Workstations in the Database Use the information in Table 18 to enter all the information required to create the workstation. Manual start and completion if the status change of jobs is reported either from the Ready List ISPF panes on the host or from the results of a workstation status list (see “Using Workstation Lists” on page 67 for details).7. Properties . you should use this reporting attribute for dummy jobs created to simplify the sequencing of other jobs. Select one of the following mechanisms for reporting status updates on the jobs defined on the workstation: Automatic if the status change of jobs is reported automatically. Enter the ddname of the daily printout data set where reports for this workstation are to be written. Required. Name Description Workstation type Enter this information .. or for other general workstations if the duration of the task needs to be tracked.. Typically.Workstation in Database General Information In this area . Table 18.. Computer for running of jobs and started tasks. Completion only if the status change of jobs is reported either from the Ready List ISPF panes on the host or from the results of a workstation status list (see “Using Workstation Lists” on page 67 for details). Typically. you should use this reporting attribute for general workstations that are not used for job preparation. Select one of the following: General for preparation of jobs and for control of operations that are normally not controlled automatically. you should use this reporting attribute for computer and print workstations. Non reporting if jobs on this workstation are set to complete as soon as they become eligible to be started. Printer for printing.. Enter a description of the workstation. Typically. you should use this reporting attribute for general workstations that are used for job preparation. Specify a name for the new workstation. Reporting attribute Printout routing Tivoli Job Scheduling Console User’s Guide 57 . in response to event records created by Tivoli Workload Scheduler for z/OS. or for workstations that specify a user-defined destination. Typically.

You set this value when you create the workstation. or the Control on servers box only. We recommend that you select both the Control on servers and the Planning on servers check boxes. The workstation that the job is using must have that number of parallel servers available before the job can run. the number of parallel servers will be used only for planning purposes. so that Tivoli Workload Scheduler for z/OS submits jobs only up to the limit of the number of servers specified. but operations on computer workstations cannot be split. If you select the Planning on servers check box only. Note: At a non–STC computer workstation. Control on servers and Planning on servers. You must allocate at least one parallel server when you define a job.. If the preparation of the JCL is interrupted by the preparer issuing the TSAVE command. Preparation of the JCL can continue at a later time. Job setup if this is a general workstation on which to prepare job JCLs or started task JCLs manually before running. In addition.. but you can change it later. WTO if this is a general workstation on which the Tivoli Workload Scheduler for z/OS scheduling facilities can issue a write-to-operator message at the operator console designated in Destination. then Tivoli Workload Scheduler for z/OS will not evaluate the number of parallel servers when deciding when to start an operation.Workstation in Database General Information (continued) In this area . Printer workstations can also be split. If you select both check boxes. Select one of these three check boxes according to which workstation type you chose: Started task. Started task. to specify how the workstation uses parallel servers.1 .. Splittable Select this box to specify that jobs on the workstation can be interrupted and then continued at a later time. Use this attribute for a job setup general workstation where you prepare JCL for submission. or no check box at all. Use the two check boxes. When you create a Tivoli Workload Scheduler for z/OS job. the operation is given status I. the number of parallel servers required by the job must also be available on the workstation before the job can be started. because Tivoli Workload Scheduler for z/OS will submit as many jobs as are ready. STC if this is a computer workstation that will run started tasks rather than jobs. a parallel server can represent a Job Entry Subsystem initiator. and the plans that Tivoli Workload Scheduler for z/OS produces cannot accurately predict the behavior of real work in your system. interrupted.Table 18. you specify how many parallel servers it requires. Properties . STC Job setup WTO 58 Version 8. regardless of its count of the number of servers in use.. You do not need this attribute if Tivoli Workload Scheduler for z/OS can resolve all the JCL variables automatically. Control on servers Planning on servers Enter this information .

Workstation in Database General Information (continued) In this area . The default destination is the system where the Tivoli Workload Scheduler for z/OS engine is started. Destination Defaults Select Resources in the left pane... Properties . in hours:minutes (HH:MM) format. You can override this value by specifying a duration when you create a new job. for all jobs on that workstation. Note: This option applies only to workstations running on OPC 2.. When you select this box. Select this to define the workstation as fault-tolerant. to work out a timetable for all jobs. The Resources page is displayed. Tivoli Job Scheduling Console User’s Guide 59 . Use fault-tolerant workstations to run Tivoli Workload Scheduler jobs in a Tivoli Workload Scheduler for z/OS plan. however you should attempt to estimate as close as possible. Port number Enter the optional TCP/IP port number of the tracker agent that is hosting the access method. Node address Write the optional TCP/IP address or hostname of the tracker agent that is hosting the access method. when creating the plan. Enter a destination that corresponds to the destination specified on a ROUTOPTS initialization statement. Fault-tolerant workstations are automatically defined as computer workstation types with an automatic reporting attribute. that the system should allow between the end of a predecessor job and the beginning of the present job. Name Enter the name of the access method that handles the external product. all the properties for this workstation are disabled and set to their default value. Managing Workstations in the Database Table 18. Tivoli Workload Scheduler for z/OS uses the estimated processing time. The transport time of the workstation is the default transport time for all the jobs defined on the workstation and is used for planning purposes only. You do not need to give an exact figure. Duration Enter the default estimated processing time. because Tivoli Workload Scheduler for z/OS can adjust this figure dynamically from its experience of the actual durations.2 or later. Fault Tolerant Enter this information . Access Methods Enter details of any optional access methods that enable the workstation to submit and track jobs that are run by an external product. Transport time Enter the time. in HH:MM:SS format. For computer workstations and WTO general workstations this is the name of the Tivoli Workload Scheduler for z/OS tracker..7.

Unless the specified quantity of resources is available. ¶ They cannot be shared by other workstations. you can specify how many of the workstation resources (R1.Workstation in Database Resources Page You can define a maximum of two workstations. ¶ Their name is limited to two characters.Resources Page Figure 8. called Resource 1 (R1) and Resource 2 (R2). the job will not start. they are subject to the following limitations. When you create a new job. Properties . that in some instances could make it more practical to use logical resources in their place: ¶ You can have a quantity of no more than 99 of each resource.1 . However. to schedule or run jobs on this workstation. R1 and R2 can represent any physical resource in your system that is significant for scheduling purposes. When defined. R2. 60 Version 8. or both) the job will use. or fixed resources. the two resources are associated to the workstation and are recognized automatically when you schedule and run jobs on the workstation.

Tivoli Workload Scheduler for z/OS may need to reassess the start time of some of its operations. Select the Used for control check box. If something unexpected happens (for example. Select Open Time Intervals in the left pane. Tivoli Workload Scheduler for z/OS considers the workstation resource when rescheduling its operations. 2. The plan contains the best estimation of when operations will start. At this point. Tivoli Job Scheduling Console User’s Guide 61 . Enter a 2-character name in Name if you want to change its name from the R1 or R2 default. Select the Used for planning check box. 3. the workstation resource is ignored. If you selected it. The Open Time Intervals page is displayed. a job exceeds its expected run time). if you want this resource to be used when a job runs on this workstation.7. Otherwise. the Control option becomes important. Managing Workstations in the Database To define the use of each resource: 1. if you want this resource to be considered when a plan involving this workstation is built.

to define the new interval. After adding a row. you must first select the row. and the name of an alternate workstation that will allow work to run at this workstation. 1. on a time-interval basis. See Figure 9. Figure 9. Adding an Open Time Interval 62 Version 8.1 . then click the button. To delete an interval. double-click under each heading to make a choice or to write data. To add or delete an open time interval. the capacity of workstation resources. 2.Defining Open Time Intervals In this window you define. the availability of parallel servers. click the Add Row or Remove Row buttons.

you find a default Standard row where you enter the name of an alternate workstation and the quantities of parallel servers and of workstation resources that you want to be available on a general basis.7. Specify the availability status of the workstation in the given interval. Note: For best results. click the ellipsis next to the field to open a Find Workstations window. The name of another workstation of the same type that can be used during the interval if this workstation becomes unavailable. Status menu From Time and To Time Parallel Servers R1 Capacity and R2 Capacity Alternate Workstation When you have finished: ¶ Click OK to add the new workstation to the database and to close the window.Workstation in Database Open Time Intervals Information In this column .. This option is possible only for computer workstations and for WTO general workstations. ¶ Click Cancel to close the window without adding the workstation. Managing Workstations in the Database Use the information in Table 19 to complete all the necessary fields in the window. The quantity. Choose: a day of the week.. to a maximum of 99 each for every interval. A time range. to a maximum of 99. with times in the 12-hour format. name. The available quantities. Properties . make the configurations of the two workstations symmetrical. of resources R1 and R2 if you specified their use for this workstation in the Resources page. so that the two workstations can be alternates for each other. Standard. Table 19. or Specific Date (where a calendar pops up from which you select a date). If you select this value. The Standard interval defines the values that are true at all times. Day menu Do this .. Select one of the following: Defined To specify that during the interval the workstation is available in the quantities and with the properties defined in the current row. If you need assistance in finding the alternate workstation.. or both are different from Standard. When you define a new workstation. with the exception of the additional intervals that you also specify on this page. Closed To specify that the workstation is not available during the interval. See “Finding Objects” on page 48 for instructions on using the Find Workstations window. the remaining cells in the row are disabled. Tivoli Job Scheduling Console User’s Guide 63 . Leave this field blank if you did not specify usage of parallel servers in the General page. Select a day or Specific Date to specify the time intervals where the quantities. of parallel servers available to the workstation during the time interval.

Display a list of all the workstations currently allocated to the plan. You can display their properties and see from the empty fields that no selection criteria are specified. 64 Version 8. You can modify their properties and make them less general by adding the filters of your choice.1 . User-defined Workstation Lists Use this type of list . “Managing Workstations in the Plan” on page 161 provides information on how to use plan workstation lists to modify the allocation of workstations in the plan. Database workstation lists Plan workstation lists To do this . Default Workstation Lists The Job Scheduling Console provides two workstation lists. Display a list of all the workstations defined in the workstation definition database.. View and update workstation definitions stored in the Workload Scheduler for z/OS workstation description database. You can find them in the default lists groups in the tree of each Workload Scheduler for z/OS engine shown in the Job Scheduling view.. They also explain how to use database workstation lists to update definitions in the Workload Scheduler for z/OS database.. Default Workstation Lists Use this list . Resides in the Default Database Lists group.. View and update the status and properties of the workstations allocated to the plan and of the jobs associated with them. The following sections explain how to create database and plan workstation lists. 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. Table 21.Managing Workstations After you have created the workstations. create one or more workstation lists to manage them.. All Workstations Status of All Workstations To do this . The default workstation lists have the same behavior as the user lists.... Resides in the Default Plan Lists group.

in the Job Scheduling view.7. To create a database workstation list. select an engine and click the List Workstations in Database button. Managing Workstations in the Database Creating a List of Workstations in the Database A workstation list produces a filtered list of workstations defined in the Workload Scheduler for z/OS workstation description database. Figure 10. The Properties .Database Workstation List window is displayed.Database Workstation List Window Tivoli Job Scheduling Console User’s Guide 65 . The Properties .

If you leave all fields blank.. 66 Version 8. To display the list. ¶ Click OK to add the object for the new list to the tree under the engine you selected when creating the list. These workstations are used to run the Workload Scheduler jobs in the Workload Scheduler for z/OS plan. specify any of the following search parameters or combinations of two or more parameters.Use the information in Table 22 to enter all the information needed to create the database workstation list. Workstation Lists all the workstations with this name or namestring... In the group. such as an asterisk (*) to represent strings of characters.1 . use wildcard characters. right-click it and click Open. To generalize your search. Properties .Database Workstation List Information In this area . Table 22. Enter a name for the list. Name Periodic Refresh Options Do this . Reporting Attributes Lists all the workstations characterized by the reporting attributes you select with the following check boxes: ¶ Automatic ¶ Completion only ¶ Manual start at completion ¶ Non reporting Types Lists all the workstations of the type you select with the following check boxes: ¶ General ¶ Computer ¶ Printer Is Fault Tolerant Lists fault-tolerant workstations. Select Periodic Refresh to specify an automatic refresh interval in seconds. Select : Yes To list fault-tolerant workstations No To list workstations that are not fault-tolerant Ignore criteria To list workstations regardless of whether they are fault-tolerant or not ¶ Filter Criteria When you have finished: ¶ Click Apply to display the list results immediately.. —OR— ¶ Select Apply Defaults to use the default specified in the Scheduler Properties window available from the Job Scheduling view. or a question mark (?) to represent a single character. all the workstations defined in the database are displayed when you open the list.

see “Browsing and Modifying Workstation Properties” on page 164. Click OK to save your changes. For each workstation. For a description of the fields in the Properties . see “Creating a Workstation” on page 56. For further information. right-click the workstation and select Delete from the pop-up menu. The workstations found are displayed in the right-hand pane. 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. all the workstations defined in the database that respond to the filter criteria are displayed in the right-hand pane of the Job Scheduling Console. Managing Workstations in the Database Using Workstation Lists When you open a database workstation list object. 2. Make your changes to the workstation properties.Workstation in Database window. you must use a plan workstation list. A confirmation window is displayed. right-click the list object for which you want to use to list the workstations and select Open from the pop-up menu. in the Job Scheduling view. continue with “Displaying a List of Workstations in the Database” Displaying a List of Workstations in the Database To display a list of workstations defined in the database. 2.Workstation in Database window is displayed. Tivoli Job Scheduling Console User’s Guide 67 . right-click the workstation and select Properties from the pop-up menu. Click Yes.7. Deleting a Workstation from the Database To delete a workstation displayed in a list: 1. The Properties . To work with workstations defined in the database. The workstation is deleted from the database. In the Job Scheduling view. In the Job Scheduling view. 3. 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 Database To modify the properties of a workstation displayed in a list: 1.

Workstation in Database window is displayed. The new workstation is added to the database.1 . In the Name field. The Properties . change the default name to the name of your choice. 68 Version 8. Click OK to save the new workstation and close the window. 3. If you do not change the name. 6. either click the Refresh List Results button in the Job Scheduling Console window or run another list. In the Job Scheduling view. 5. To do this: 1. and select Create Another from the pop-up menu. 2. right-click the workstation that you want to use as a model for the new workstation.Creating Workstations from Existing Ones in the Database You can select a workstation from a list and use its definition to create other workstations with the same or similar properties. the new workstation is saved as COPY (a Workload Scheduler for z/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. To view the new workstation.

Managing Resources in the Database Tivoli Job Scheduling Console User’s Guide 69 . resources represent the physical or logical objects that are used by jobs. You specify how a job uses resources when you create the job. You can use resources to prioritize access to a data set or to limit the number of simultaneous file transfers on a particular network link.8 Managing Resources in the Database In Workload Scheduler for z/OS. But first you must: ¶ Create the resource and its attributes ¶ Specify the associated workstations ¶ Specify the number of resources available in each interval 8.

Resource in Database Window Resource Page 70 Version 8. Figure 11. On the first two pages.1 . This window contains the Resource. Properties . These values are valid at all times. and Availability Intervals pages. Resource Page In this Properties . you enter information that describes the resource you are creating. Default Workstations. select an engine in the Job Scheduling view and click the New Resource button.Resource in Database window is displayed.Creating Resources To create a resource in the Workload Scheduler for z/OS database. The Properties . you enter the default information for the new resource.Resource in Database Resource page. except for the periods that you optionally define on the Availability Intervals page.

A name of up to eight characters that identifies a group to which the resource belongs. Free if exclusive Free the full exclusive allocation of this resource.. The Properties . Refer to the Customization and Tuning manual. Select to specify whether the resource is a data set eligible for Hiperbatch™. Name Description Default Do this . Managing Resources in the Database Group ID Hiperbatch Used for On error Select Default Workstations in the left pane. You may want critical jobs to keep their resources even when they fail. The group ID can be used as a list filter for selecting subsets of resources. Select from the drop-down list how the resource is to be used. both exclusive and shared. Hiperbatch is a host performance enhancement that works with the Data Lookaside Facility (DLF) to enable batch jobs and started tasks to share access to data sets.Use the information in Table 23 to enter all the information needed to create the resource.. The quantity of the resource (from 1 to 999999) in Quantity. Specify a name identifying the resource. Tivoli Job Scheduling Console User’s Guide 71 .Resource in Database Default Workstations page is displayed. Free if shared Free the full shared allocation of this resource. Keep Keep the full allocation of this resource. The name is converted to uppercase. for: ¶ Planning ¶ Control ¶ Planning and control ¶ Neither planning nor control Select from the drop-down list box what action to take on the resource when a job that allocates this resource ends in error (and does not have an overriding keep-on-error specification in the job definition): Free Free the full allocation of this resource. Assume System Default Use the default specified in the ONERROR keyword of the RESOPTS statement.. Table 23. 8. to avoid having to wait for resources when the job is restarted.. Create a Resource Information In this area . This information is used as the default unless otherwise specified for a given interval on the Availability Intervals page. Provide a description of the resource. Specify the number of the resource that is available (when you select the Is Available box) for the availability intervals associated with the resource.

To remove a workstation from the list. 6.1 . 3. Note: By default. click the Add All Workstations button in the toolbar. An asterisk (*) is added to the list of connected workstations. The Find Workstation window is displayed. 72 Version 8. Select Availability Intervals in the left pane. The Find tool allows you to pick from a list of available workstations. then click the Remove Row button. Click the Find Workstation button. Properties . Either enter a name directly in the Workstation field or select one or more boxes in the Reporting Attributes and Types groups. 4.Resource in Database Availability Intervals page is displayed. The Properties .Default Workstations Page On this page. To add all the workstations defined in Workload Scheduler for z/OS. 2. select it.Resource in Database Default Workstations Window 1. Several filtering items are available to search for connected workstations. Click Start. 5. you list the workstations associated with and reserved for the resource. all workstations are already added when the Resource Editor window for a new resource opens. When the search results are displayed. Figure 12. select a workstation and click Add to add it to the Default Workstations list.

See “Finding Objects” on page 48 for an explanation of using the Find window... Choose: Available. or Specific Date. 8. Not Available. When you define a new resource. When you have finished: ¶ Click OK to save the new resource and close the window. click the Add Row or Remove Row buttons. Table 24. The Standard interval represents the norm where the resource is used with the values you entered in the other two pages. Standard. or with other values that you specify for each different interval. To put a resource off limits for a certain period. and Connected Workstations values in the Resource and Default Workstations pages. Define an Availability Interval Information In this column .. and Connected Workstations characteristics that you specify in the row itself. Use the information in Table 24 to enter the information to define the availability interval. optionally. This opens a Find window that helps you search for available workstations. Availability.. Quantity Is available menu Workstations Type the quantity of the resource in this time interval. click the ellipsis (. Availability. or Default (the default specified in the Resource page).Resource in Database Availability Intervals Window To add or delete an availability interval. for a time range. Write the names of one or more connected workstations. click No. Alternatively. Tivoli Job Scheduling Console User’s Guide 73 . you can define the new interval. you define the time intervals when the resource can be used with either the Quantity. each separated by a blank. Properties . then Find Workstation. you find a default Standard row where you need not add any values except. Managing Resources in the Database Figure 13. Day menu Do this . then select the specific interval.Availability Intervals Page On this page.. After you have added a row. Choose: a day of the week.. From Time and To Time Specify a time range. Select a day or Specific Date to specify the intervals in which the resource is available with different Quantity.).

. You can display their properties and see from the empty fields that no selection criteria are specified.¶ Click Cancel to close the window without saving the resource. create one or more resource lists to manage them. Default Resource Lists Use this type of list . The following sections explain how to create database and plan resource lists. You can find them in the default lists groups in the tree of each engine displayed in the Job Scheduling view. Resides in the Default Database Lists group.. 74 Version 8...Database Resource List window is displayed. They also explain how to use database resource lists to update definitions in the database. The Properties . Display a list of all the resources currently allocated to the plan.. Default Resource Lists The Job Scheduling Console provides two resource lists. User-defined Resource Lists Use this type of list . View and update the status and properties of the resource allocated to the plan and of the jobs associated with them.. Database resource lists Plan resource lists To do this . Managing Resources Once you have created resources.. You can modify their properties and make them less general by adding the filters of your choice. To make a database resource list. From a resource list you can: ¶ View the characteristics and status of resources ¶ Modify resource properties ¶ Delete resources You can create two types of list: Table 25. Table 26. Display a list of all the resources defined in the resource definition database. then click the List Resources in Database button.. All Resources Status of all Resources To do this . Default resource lists have the same behavior as user-defined lists. View and update resource definitions stored in the resource description database.1 . Listing Resources in the Database A database resource list shows a filtered list of resources defined in the Workload Scheduler for z/OS resource description database. Resides in the Plan Lists group. “Managing Resources in the Plan” on page 173 provides information on how to use plan resource lists to modify resource allocation in the plan. select an engine in the Job Scheduling view.

Database Resource List Window Use the information in Table 27 to enter all the information needed to create the list.8. Database Resource List Information In this area . ¶ Specify whether the resources are data sets with the DLF attribute or not. Specify a parameter or a combination of parameters: ¶ In Resource specify a resource name. To generalize your search. ¶ Click OK to add the new list to the engine tree. To display the list. Select one of the following options: Wildcard Treat special characters as wildcards. The Properties . ¶ Specify a resource group name in Group ID. Managing Resources in the Database Figure 14. then all resources are displayed when you open the list. ¶ Specify in Treat input as how you want the input you entered in the Resource field to be treated. use wildcard characters. Enter a name to identify the query. Tivoli Job Scheduling Console User’s Guide 75 .. Filter Criteria When you have finished: ¶ Click Apply to display the list results immediately. Alternatively.. click Apply Defaults to use the defaults specified in the scheduler Properties window available in the Job Scheduling view. Exact match Treat special characters as part of the resource name. in Hiperbatch. If you leave all fields blank. Prefix Treat the string as a name prefix.. To refresh the list results automatically. select the Periodic Refresh check box and specify a refresh interval in seconds. Table 27. or if this is to be ignored. Specify search parameters or combinations of parameters. right-click it and select Load List. Name Periodic Refresh Options Do this . Suffix Treat the string as a name suffix..

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 in error ¶ Date and operator of last update of the resource properties 76 Version 8. Displaying a List of Resources in the Database To display a list of resources defined in the database: 1. right-click the list object you want to use to list the resources and select Load List from the pop-up menu. The resources are displayed in the right-hand pane. The following sections explain how to use database resource lists to work with resources defined in the resource description database. all the resources defined in the database that respond to the filter criteria are displayed in the right-hand pane of the Job Scheduling Console.1 . For information about how to work with plan resources. 2. you must use a plan resource list.Using Resource Lists When you open a database resource list. List of Resources in the Database For each resource. Figure 15. 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. From the display produced by opening a database resource list. see “Browsing and Modifying Resources” on page 176. In the Job Scheduling view.

the new resource is saved as CopyOfname. For a description of the fields in this window. either click the Refresh List Results button or run another list. In the Job Scheduling view. change the default name to the name of your choice. right-click the resource that you want to use as a model for creating another resource and select Create Another from the pop-up menu. If you do not change the name. 5. A confirmation window is displayed. 3. 4. 2. see “Creating Resources” on page 70. Creating Resources from Existing Ones in the Database You can select a resource in a list and use its definition to create other resources with equal or similar properties. After you have displayed a list of resources. Click OK to delete the resource from the database. Deleting Resources from the Database To use a list to delete a resource from the resource description database: 1. do the following: 1. Tivoli Job Scheduling Console User’s Guide 77 . In the Job Scheduling view.Modifying Resource Properties in the Database To modify the properties of a resource displayed in a list: 1.Resource in Database window is displayed. Click OK to save the new resource. To view the new resource. showing the resource you selected. right-click the resource and select Delete from the pop-up menu. The Properties . Managing Resources in the Database Figure 16. 3. where name is the model resource name. In the Name field.Resource in Database Window 2. Make your changes to the resource properties. 8. The Properties . The Properties . The window is closed and the new resource is added to the database. Click OK to save your changes to the resource definition. right-click the resource and select Properties from the pop-up menu.Resource in Database window is displayed. 2. In the Job Scheduling view. Change any other properties that you need to customize for the new resource.

1 .78 Version 8.

. Creating Job Streams Normal job stream You create both jobs and run cycles. where necessary See . You create run cycles but no jobs. You therefore create jobs but no run cycles. together with scheduling information. you perform the following tasks: Table 28.. “Specifying Properties for the Job Stream” on page 80 “Creating a Job” on page 82 “Creating Dependencies between Jobs” on page 91 and “Creating Dependencies between Job Streams” on page 92 Create one or more run cycles to specify when “Scheduling Job Streams” on page 94 the job stream runs Tivoli Job Scheduling Console User’s Guide 79 . To create a job stream. You determine the type when you specify the job stream properties. There are three types of job stream: Job stream template Does not go into the plan..9 Creating Job Streams A job stream is a sequence of jobs that includes the resources and workstations that support the jobs. Specify the new job stream properties Create jobs Create dependencies between jobs. 9.. Contains only scheduling information for the job streams that belong to it. Tasks in Creating a Job Stream To perform this task . Job stream that inherits its scheduling information from a job stream template Uses the scheduling information defined in the job stream template.

All job streams defined as belonging to a template inherit the run cycles defined for the template. Description Is a template Inherits from template Active Valid Date 80 Version 8. Specify the time period covered by the job stream. To change the From value. Properties . A To date of 12/31/2071 is automatically assigned by Workload Scheduler for z/OS. Enter the name of the template if you are defining a job stream that belongs to a job stream template.. valid date. and status uniquely identify each job stream or template. The scheduler picks the correct version for the day it is planning. You can specify only the From date. and created a run cycle. Properties . do not select this check box until you have added all jobs. Select this check box to define a new job stream template. If you are creating a complex job stream that requires time to define. Enter a description for the job stream or template. The Job Stream Editor and the Properties . Enter a name for the job stream or template.. You can define up to four job streams and job stream templates that share the same name but have different valid dates. This avoids the risk that the incomplete job stream will be included in any plans. Select this check box to schedule the job stream..Job Stream Window Information In this area . select a Workload Scheduler for z/OS engine in the Job Scheduling view and click the New Job Stream button. specified dependencies. Name Do this . You can make the job stream active after you have completed it. click the small calendar button to select a valid From date. Table 29. Note: The name.Job Stream Window Use the information in Table 29 to enter all the information needed for this window. A job stream template contains run cycles but no jobs.. Figure 17.Job Stream window are displayed.Specifying Properties for the Job Stream To create a job stream or job stream template.1 . The job stream is scheduled using the template run cycle information. You can create several job streams with the same name but with different dates in the From field.

You can add only run cycle information. Job stream as belonging to a template Single job stream Note: The Workload Scheduler for z/OS ISPF main panel.Job Stream Window Information (continued) In this area .. The value is Yes if Is Monitored Job is selected in the properties window of one or more of the jobs in the job stream.. This field is read-only. the scheduler uses the calendar specified in the initialization parameter CALENDAR during startup of the TCP/IP server. option 1.. Job stream template This happens . are considered in determining priority. Specify how the job stream ranks in importance compared to other jobs streams. Specify the name of the calendar of workdays and freedays. allows you to create a job stream containing a single job by specifying only the name of the JCL associated with the operation. that you associate to the job stream.) to open a Find window (see “Finding Objects” on page 48). Other factors. when job streams are competing for resources.8. To create job streams with a single job. Properties .. Enter the name of the person responsible for the job stream or template.. Note: The calendar that you specify here is used to display the run days of the job stream in the Run Cycle view of the Job Stream Editor. This option is not available in the Job Scheduling Console.. Priority Do this .. Enter a name to be used to generate a RACF resource name for authority checking. The following happens: Table 30. If you need to. The Job Stream Editor opens the Graph view from where you can add jobs and dependencies. The Job Stream Editor opens the Graph view where you can create jobs.. and switch to the Run Cycle view to add run cycles. a job stream with a priority of 3 will run before a job stream with a priority of 1. you must follow the steps in this chapter. Authority group name Calendar 9. including holidays. If you leave this field blank. Enter a description of the job stream or template. The Job Stream Editor opens the Timeline view.. where you can open the Run Cycle view. Creating Job Streams Owner Owner description Contains Monitored Job Click OK to proceed. click the ellipsis (. This field does not apply to job stream templates. This information is optional.Table 29. Tivoli Job Scheduling Console User’s Guide 81 . It is not necessarily the calendar that is used to determine the actual run days of the job stream instances that are generated. The lowest priority is 1 and the highest priority is 9. What Happens When You Define a Job Stream If you are creating a . such as resource and workstation dependency.. This means that. This value is not definitive. Indicates whether any jobs in this job stream will be monitored by Tivoli Business Systems Manager when they run.

Runs on general workstations. Runs on computer workstations. based on the job type. Moreover. to the properties that you specified. Add Setup JobA job containing a set of JCL statements for a JCL or started task job.. Runs on general workstations. Add General JobA job to include activities other than printing and processing. Add Write-to-Operator JobA job containing an operator instruction displayed on the system console. Graph ViewChange to the Graph view. Add Dependency on External JobCreate. Workload Scheduler for z/OS applies different validation policies. the tool lists only workstations that are compatible with the specific job type. Add Printer JobA job to print the output of a predecessor job. Add Started Task JobA job to start or stop a task that has already started. you can create the jobs that comprise it in the Graph view of the Job Stream Editor. Timeline ViewChange to the Timeline view. or modify a dependency on a job that is part of another job stream. Add JCL JobA job that consists of JCL statements. such as manual activities.. Add LinkCreate a link between jobs. Runs on printer workstations. Table 31 describes these job buttons: Table 31. Runs on general workstations. browse.. However.1 . when you use the Find tool to search for a target workstation. Run Cycle ViewChange to the Run Cycle view. Graph View Job Buttons This button . The property windows for the different job types are identical.Creating a Job After you have specified the properties of a job stream. Denotes this job type . The Graph view displays an button for each possible type of job that you can define in Workload Scheduler for z/OS. Add FTW TaskAdd a task to run on a fault-tolerant workstation. when you save the job stream. Runs on computer workstations. 82 Version 8..

Creating a Job Using Buttons To create a job in the job stream. depending on the type of job that you want to define. You can also run your search by selecting boxes in the Reporting attributes group box..) button. Double-click the name of a workstation. or click it once then click on OK. Properties . Click the ellipsis (. 2. For example. If you do not know the name: 1. The Find Workstation window is displayed. click one of the job buttons in the Graph view of the Job Stream Editor.. 3.JCL Job General page.. Identifier Target workstation Do this . The Properties .. General Page 9. Enter the job number. Description Auto submit Tivoli Job Scheduling Console User’s Guide 83 . the Add JCL Job button. Creating Job Streams Figure 18.. Click Start. The name of the workstation is displayed in the Target workstation field in the Properties . This information is required and must be unique within the job stream. Properties . Table 32. A list of workstations is displayed. Select this to start the job automatically or to issue a WTO message (when all dependencies have been satisfied and all required resources are available).JCL Job window is displayed. A brief description of the job. Auto submit is selected by default. The name of the workstation on which the job is run. This information is required.JCL Job General Information In this area .. In the Find field. 4.JCL Job General Page Use the information in Table 32 to enter all the information needed to define the job details. enter the name of the workstation or you can use wildcard characters.

1 . Select this to release the job when it is not submitted by Workload Scheduler for z/OS and is in HOLD status.. Manual Restart and cleanup actions are to be initiated manually from the Modify Current Plan ISPF dialog.Table 32. Select this to mark the job ended-in-error (E) if an error occurs when it runs. Note: select this option only for time-dependent jobs (time-dependent jobs must have an earliest start time and a deadline specified on the Time Restrictions page). None No cleanup and restart actions are performed. Properties . The engine builds a set of cleanup actions that are performed when the first step of the restarted job runs (inserted by the scheduler). This is the default and recommended option. Select this to issue an operator message if the job passes its deadline. Auto release is selected by default. Auto error completion is selected by default.. Select this to specify that the running of this job is to be monitored by Tivoli Business Systems Manager. job reruns. which must be initiated separately. Cancel if late Do this . Automatic Data set cleanup is performed automatically during the rerun of the failed job. should not be the JCL contained in the scheduler libraries but the JCL image captured from the JESJCL sysout data set. Use Sys Out Specifies that user sys out data sets should be used for job restarts. Select this to prevent the job from being started if it is late (according to the time dependencies specified in the Time Restrictions page).. Specify which data set and job restart actions must be performed if the job ends in error. The job is released when all dependencies are satisfied and the requested resources are available. Expanded JCL Specifies that the JCL used for step-level restarts and. Deadline WTO Auto release Auto error completion Is Monitored Job Restart and Cleanup 84 Version 8. This is the default. This option is not available for fault-tolerant workstations. Immediate Data set cleanup is performed automatically when the job fails. If you clear it.JCL Job General Information (continued) In this area .. This option is not linked to a restart. The message is also written to the message log. This is the preferred method of running restart and cleanup. optionally. regardless of the outcome. the job is marked complete (C) when it ends.

. ¶ In the Limit for feedback field. even if it overrules the installation default in the WSFAILURE or WSOFFLINE parameters of the JTOPTS initialization statement. This option applies to the job only when it is in ready (R) or waiting (W) status. This is selected by default. It can use these durations to modify the estimates in the application description (AD) database. Specify whether to make the job eligible to be rerouted if its workstation becomes inactive. If you leave this field blank. to establish the limits within which measured values are regarded as normal and acceptable. the smoothing factor is not applied and the AD database is not updated. or on this workstation when it becomes active again. No Makes the job not reroutable Default Takes the installation default action specified in the OPRESTARTDEFAULT keyword of the JTOPTS statement. Restartable Do this . This is selected by default. that determines how much a measured duration will change existing values in the AD database.3 only. In the Feedback options group box. from 0 to 999. specify two parameters that control how measured durations are used: ¶ In the Smoothing factor field. Properties . Select this if you want to define the job as a critical job.Table 32. The scheduler automatically monitors the actual durations of jobs.. Specify the highest acceptable return code from any step in the job before the job is set to ended-in-error (E) status. Creating Job Streams Highest acceptable return code Feedback options Critical job Tivoli Job Scheduling Console User’s Guide 85 .JCL Job General Information (continued) In this area . type a number. That is. Yes Makes the job reroutable. Default Uses the installation default action specified in the OPRESTARTDEFAULT keyword of the JTOPTS statement. If a measured duration is outside the limits established by the Limit for feedback field. type a number. 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). This makes the job eligible for Workload Manager (WLM) service class promotion when the job runs late. A measured value outside the limits is ignored. from 100 to 999. No Restarts the job. Reroutable 9. no smoothing factor is applied and the AD database is not updated... Workload Scheduler for z/OS uses the value specified in HIGHRC in the initialization parameter JTOPTS. Available for OPC 2.

Note: If the task is a manual operation. leave this page blank. If you selected the Critical job check box. The policy can be: Conditional The scheduler uses an algorithm to determine whether to apply the Deadline or the Latest start option. The Task page is displayed. Task Page In the Task page... Deadline The scheduler intervenes if the job runs beyond the deadline. WLM policy Do this . Properties . Figure 19. Latest start The scheduler intervenes immediately if the job starts after the latest start time.JCL Job General Information (continued) In this area . click the WLM policy drop-down list to select the type of policy applied for WLM service class promotion when this job is late.JCL Job Task Page 86 Version 8. This option is available for OPC 2. Select Task in the left pane. enter information about the program associated with the job.1 ..Table 32.. Properties .3 or later. Long duration The scheduler intervenes if the job takes longer than it should as compared to the statistics that it keeps.

The name of the JCL associated with the job. Task name Enter this information . it enables the engine to identify the different print operations that belong to a specific job. For printer workstations with automatic reporting. Form number Job class Select Time Restrictions in the left pane.Use the information in Table 33 to enter all the information needed to define the task.. specify the period of time that the job is allowed to run and the amount of time the job requires. when applicable.JCL Job Time Restrictions Page Use the information in Table 34 on page 88 to enter all the information required to define the time restrictions. 9. The Time Restrictions page is displayed. Time Restrictions Page In the Time Restrictions page.. Properties . click the drop-down list and select a letter that matches the host job class from the JCL. Tivoli Job Scheduling Console User’s Guide 87 ..JCL Job Task Information In this area . Properties . The printer form number that appears on the daily plan and ready lists. Table 33.. Together with the identifier you specified in the previous page. Creating Job Streams Figure 20. the task name labels the job in the Graph view of the Job Stream Editor.

¶ Select Follow job stream rules to specify that the earliest time the job can start is when the job stream starts. 2. To do this. enter a time. For example. In the At field.JCL Job Time Restrictions Information In this area . In the Delay for field. If this job is not time dependent. select Specify deadline and use the At and Delay for fields. according to your local settings. enter 12:00 if you do not want the job to start before noon. Properties .. Specify the latest time that the job can end. the job will start three days after the time you originally specified in the At field. This is the default. Note: This choice is not valid if you selected Cancel if late in the General page. Start Do this . if you type 3. The default is no deadline time. they are run as soon as dependencies are satisfied. Note: This choice is not valid if you selected the Cancel if late box in the General page.1 . For example. Deadline Duration Select Resources in the left pane. In this way. No time restrictions can result in more efficient processing for certain jobs when extending a plan. minutes. ¶ Select Specify earliest start time to define a specific time before which the job should not start. in hours. 88 Version 8.. Specify the time at which the job can start. type a number of days to defer thestart time.Table 34.. Then: 1. The Resources page is displayed. in one of the following ways: ¶ Select No restrictions to run the job as soon as all dependencies are met.. Specify how long the job is expected to run. and seconds. click this option.

Properties . Click the arrow again and select Logical resources. and the parallel servers. Do the same for parallel servers. 5. you perform the following actions on target resources and logical resources. Click the Add row button for each resource you need to assign to the job. If you do not know it.). 9. Click the arrow next to Target resources. describe the parallel servers.. which you access from the drop-down list: Target resources Where you specify the workstation (or fixed) resources. Creating Job Streams Figure 21. and the logical and workstation resources that the job uses. Double-click each cell in the Quantity column to edit the amount of resources Resource 1 and Resource 2 are required by the job. that the job needs to run. 3. Logical resources Where you specify the logical and physical resources that the job needs to run 1. 2. Type the name of the resource. Columns are displayed where you can specify the logical resoruces.JCL Job Resources Window In the following procedure.. Columns are displayed where you can specify the target resoruces. use the Find tool (.Resources Page In the Resources page. Tivoli Job Scheduling Console User’s Guide 89 . 4.

4. When you move the slider downwards to zoom out of the Graph view. When you have finished. Figure 22. You can drag and drop the button to position it.1 . 3. 90 Version 8. In the Job Stream Editor. changing color depending on the job type. Keep on error Specify whether the job keeps or frees the resource when it fails. The new job is displayed as an button in the Graph view of the Job Stream Editor.6. positioned on the left margin of the Graph view. Creating a Job Using Copy and Paste To create a job using the copy and paste functions on an existing job: 1. Repeat the steps in this section to create as many jobs as you need. double-click under each of the next three columns to edit the following attributes: Quantity Specify the amount of the resource needed by the job. The Properties . the job buttons change their appearance. right-click the job you want to copy and select Copy from the pop-up menu. to zoom in and zoom out the jobs displayed. For each logical resource. Job Stream Editor Graph View The name of the button is made up of the name of the task with which the job is associated and by the job identifier. 2. Right-click the mouse somewhere in the window and select Paste from the pop-up menu. click OK to save your changes and close the window.JCL Job window for the copied job is displayed. Access type Specify whether the job needs shared or exclusive access to the resource. Click OK to save your changes and close the window. You can also specify to use the default defined in the ONERROR keyword of the RESOPTS statement. The new job is added in the Graph view. Note: You can use the slider. Change the identifier and edit the properties as required.

In the Graph view of the Job Stream Editor.Add Link 3. Tivoli Job Scheduling Console User’s Guide 91 . Creating Job Streams Figure 23. to print bank account statements. 9. even if the successor job has time restrictions. Job Stream Editor . 2. you link jobs in a sequence. and that job 03 can start only when job 02 has finished. A successor job cannot begin until the predecessor job is complete. Job Stream Editor .Example Dependent Jobs Figure 24 shows that jobs 04 and 05 can start only when job 03 has finished.Creating Dependencies between Jobs When you create dependencies. Repeat the previous steps to create as many dependencies as you need. For example. Here. you must first subtract withdrawals from an account (Job A) before you calculate the account balance (Job B). Job A is the predecessor and Job B the successor. Dependencies determine when the successor job runs. Figure 24. with an arrow pointing to the successor job. A line is displayed between the two jobs. Creating Dependencies within a Job Stream To create a dependency between jobs within the same job stream: 1. click the Add Link button. Click the predecessor job and drag the link to the successor job.

enter the name of the job stream containing the external job.1 . 3. This section describes one way to add an external job to a job stream. if Job C in the Accounts job stream depends on Job B in the Reports job stream. Figure 25. You create a dependency between jobs in different jobs streams by creating a dependency on an external job. Select a job and click OK. then you create a dependency between Job C and the external job. 92 Version 8. based on the use of job stream lists. The jobs in the job stream are displayed. In the Job Stream field.External Job Window 2. click the Add Dependency on External Job button. you create an external job in the Accounts job stream to represent Job B. In the Job Stream Editor Graph view. To create a dependency between job streams: 1. The Properties . If you do not know the name of the job stream.External Job window is displayed. is described in “Using Copy to Add an External Job” on page 115. Figure 26. For example.Creating Dependencies between Job Streams External jobs represent jobs that are part of other job streams. Another method. Properties . see “Finding a Job Stream” on page 94. An button for the external job is displayed in the Graph view. Selecting the External Job 4. Click Show Jobs.

Figure 27. job 05 can start only after job 03 has finished. Job Stream Editor — External Job Button 5. Repeat the steps explained in “Creating Dependencies between Jobs” on page 91 to define links with the other jobs. In the example in Figure 28. 9. Job Stream Editor — Example External Job Dependency Tivoli Job Scheduling Console User’s Guide 93 . Creating Job Streams Figure 28. and also after job 1 of the TWSPRO1 job stream has completed.

perform the following steps to search the job streams database: 1.. You can write search strings with wildcard characters. 5.. The calendar is defined in Workload Scheduler for z/OS. enter a search string to locate the job stream. an offset of 3 in a 94 Version 8. such as a semester. Use the information in Table 35 to specify the filter criteria.) to open the Find Job Stream window.Finding a Job Stream If you do not know the name of the job stream that contains the external job. Select this to search for job stream templates. 3. ¶ Offset-based Uses a combination of user-defined periods and offsets. 4. ¶ The validity date of the job stream. For example. or periods that you define. Identity of the owner of the job stream. This window allows you to enter criteria to search the database for existing job streams. Table 35. Scheduling Job Streams After creating the jobs and defining any existing dependencies between them. Task name Job stream template Owner Is a template Status of Job Stream Enter this information . which you specify in the Job Stream Properties window. Run cycles are generated from a combination of: ¶ A calendar of workdays and freedays. such as calendar months.. types of days. weeks of the year. Click the ellipsis (. Name of a task contained in the job stream. Use any of the Filter Criteria elements to find the job stream that contains the job you want. inactive. Filter Criteria In this area .. and days of the week. Types of Run Cycle You can create two types of run cycle: ¶ Rule-based Uses rules based on lists of ordinal numbers. A list of job streams is displayed. you specify the scheduling information for the job stream using run cycles. In the Find field. Select one of the buttons to search for active. Double-click the name of a job stream. and common calendar intervals or period names.. You can use wildcards or leave the field blank to display a list of all job streams. Rule-based run cycles are based on conventional periods.1 . or all job streams regardless of their status.. For example. Click Start. Name of the job stream template to which the job stream belongs. 2. The Find Job Stream window closes and the job stream is displayed in the Job Stream field in the External Dependency Properties window. the last Thursday of every month. You specify its name in the Job Stream Properties window (see “Specifying Properties for the Job Stream” on page 80).

Offset-based Run Cycle window is displayed. Job Stream Editor . Inclusionary run cycles specify the days that the job stream must run. Rule-based Run Cycle button Offsets Offset-based Run Cycle button Depending on which choice you make. either the Properties . You can also mix rule-based and offset-based run cycles. Exclusionary run cycles specify the days that the job stream must not run. Tivoli Job Scheduling Console User’s Guide 95 .. The Run Cycle view is displayed. 9. General Page The Properties . Creating a Run Cycle To create a run cycle. and you can add new ones afterwards.Rule-based Run Cycle General page is similar to the Properties Offset-based Run Cycle General page. It is more practical to use offset-based run cycles when the cycle is based on cyclic periods... Creating Job Streams Figure 29. You can add run cycles to generate more days. Both types of run cycles can be either inclusionary or exclusionary. or to have multiple instances on the same day.period of 15 days is the third day from the beginning of the period. You can specify multiple run cycles when you create a job stream.Run Cycle View Table 36.. click the Run Cycle button. Run Cycle Buttons If you are going to use .Rule-based Run Cycle window or the Properties . Rules Click the . You can add exclusionary run cycles to exclude some of the days already generated. in the Job Stream Editor.

Properties . Type a description of the run cycle.Figure 30. The intersection between this valid date and the valid date you defined in the Job Stream Properties window is the interval during which the job stream is actually scheduled.. and how to handle freedays in the schedule. Click the calendar buttons next to each field to select dates using pop-up calendars. Select this if the run cycle keeps the job stream from running. See “Creating Offset-based Run Cycles” on page 102.Rule-based Run Cycle General Page Use the information in Table 37 to specify whether the run cycle is exclusionary. Table 37.1 .. Use the From and To drop-down lists to specify an interval of time for which the run cycle applies. Type a name for the run cycle.. Name Do this . Run Cycle General Information In this area . Description Exclusionary run cycle Valid Date 96 Version 8.. the period that the run cycle is valid. Note: Offset-based run cycles take the name of the period specified in the Offsets page.

the job stream is not scheduled to run. Creating Job Streams JCL variable table Select Time Restrictions in the left pane. The job stream is scheduled on the runday. Type a name of the variable table that the scheduler can use on the days generated by this run cycle. If the runday falls on a freeday.Table 37. click the ellipsis (. This is the default for rule-based run cycles. If the runday falls on a freeday.. it is shifted to the closest workday before the freeday.. regardless whether it is a freeday or a workday. If the runday falls on a freeday. Specify how you want Workload Scheduler for z/OS to treat freedays when calculating the rundays of the job stream.. it is shifted to the closest workday after the freeday.Rule-based Run Cycle Time Restrictions Page Tivoli Job Scheduling Console User’s Guide 97 . Schedule on last workday before freeday Counts both workdays and freedays. The Time Restrictions page is displayed.. 9. Schedule on next workday after freeday Counts both workdays and freedays. Count workdays and freedays alike Counts both workdays and freedays. Time Restrictions Page The Properties . Figure 31. Properties . Alternatively. Run Cycle General Information (continued) In this area ... If freeday. Rule for freedays Do this .Rule-based Run Cycle Time Restrictions page is similar to the Properties Offset-based Run Cycle Time Restrictions page. by selecting one of the following: Count workdays only Excludes freedays when calculating on which days the job stream runs. This is the default for offset-based run cycles.)to search for a variable table name. do not schedule at all Counts both workdays and freedays.

Type for Enter a number of days after the start of the schedule. At Type a time when the job stream must stop. If you are creating an offset-based run cycle.1 . If you are creating a rule-based run cycle.Rule-based Run Cycle Rules Page 98 Version 8. The default is 00:00 of the scheduled day. Figure 32.Use the information in Table 38 to complete the fields in this window.. enter the time when the job stream must start.. Note: If you are creating an exclusionary run cycle. Properties .. Continue with “Creating Rule-based Run Cycles”. You can use deadline time to control the correct completion of the schedule and also to make closer estimates of the duration of a job stream. Table 38. Properties Offset-based Run Cycle Rules page is displayed. select Rules in the left pane. The Properties Rule-based Run Cycle Rules page is displayed. Creating Rule-based Run Cycles Use the information in Table 39 on page 99 to specify the elements that make up the rules on which the run cycle is based. Continue with “Creating Offset-based Run Cycles” on page 102. In the At field. select Offsets in the left pane. Run Cycle Time Restrictions Information In this area . Start Deadline Do this . be sure to match the time restrictions of the run cycle that it is intended to annul. The default is no deadline time..

Ensure that the period you select is also highlighted so that the other options in the page are enabled. or User-defined (a period that you have defined in the scheduler). Select Week. if you specify a combination of Every and ordinal-last days. You can check more than one period at a time for complex rules specifying more cycles. You can also specify ordinal-last days to count backwards from the end of the period. or months by name. and then choose the days that apply to both rules.. Every last Monday in Month schedules the job stream to run on every Monday in the month. For example. Only last Monday in Month schedules the job stream to run on the last Monday of the month. You can also shift the origin from the end. The rule does not repeat within the period. User-defined).. Year. You shift the origin of the run cycle with respect to the default origin. Tivoli Job Scheduling Console User’s Guide 99 . If you selected a user-defined period. you can shift the origin of the run cycle by the number of days you write in the Shift origin field. and the first week with at least 4 days in the Month and Year periods. since this rule generates a series of Mondays starting from the last Monday.. a list of available periods is displayed in the In the following Periods group. Month. Select the check box next to the period you want to use. The types of days you select are displayed in the Selected Types of Days field. Every Select this if the rule is used to calculate more than one day within the period. 9. For example.. For example. Note: Every first day yields the same rundays as Every day. Shift origin If you use Every. Select this to specify by name the periods to which you want the rule to apply. The days you select are displayed in the Selected Days field. this option displays lists of weeks of the year by number. Month... You do not need to select the same days twice. The number of available days changes according to the period you select. the In the following group changes depending on the period you select. The period that you select affects the number of days listed in the Available days scroll-list. Rule-based Run Cycle Rules Information In this area . which is Monday in the Week period. Frequency Only Select this if the rule applies to only one day in the specified period. Select the days of the period to which the rule applies.Table 39. Year. Also. since they are fitted automatically to all cycles. Select the types of days to which the rule applies. you can check Week and Month. Depending on the period you select (Week. Creating Job Streams Available days Available types of days In the following . Periods Do this .

¶ The run cycle name is displayed in a list to the left of the graphic calendar in the Run Cycle view. Example 1: Rule-based Run Cycle 100 Version 8. and where workdays and freedays are counted alike. 2001. and Delete. Figure 34.1 .The next figure shows a rule that schedules the job stream to run on the fifth day of every week. such as Properties. The following happens: ¶ Workload Scheduler for z/OS calculates the days of the run cycle. Example 1: Rule-based Run Cycle The next figure shows a rule-based run cycle that uses the rule shown in the preceding example. Example Rule Click OK. Figure 33. If you right-click it. Copy. a blue stripe is displayed at the top of the corresponding generated days. starting from a Valid date of July 20. When you select the run cycle from the list. ¶ The rundays are displayed in blue in the graphic calendar. you can then select a number of actions on the run cycle.

The week when the job stream must not run is specified in the In the following weeks check box. The selected days are equal to those for the WEEKLYPR run cycle. Example 2: Exclusionary Run Cycle WPREXCEP annuls the WEEKLYPR run cycle in the week marked in red. 9. Creating Job Streams Figure 35. Example 3: Exclusionary Run Cycle Defined The next figure shows the rule defined for the WPREXCEP exclusionary run cycle . Example 3: Exclusionary Run Cycle Defined Tivoli Job Scheduling Console User’s Guide 101 .Example 2: Exclusionary Run Cycle The next figure shows an exclusionary run cycle called WPREXCEP that prevents job stream 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. Figure 36.

For further information. click the ellipsis to use the Find Period window to find all the available user-defined periods. If you need to specify more than one period. a blue stripe is displayed at the top of the corresponding generated days. Properties .1 . Note: The name of the period is also used as the run cycle name. create an offset-based run cycle for each period within the job stream. 102 Version 8.Offset-based Run Cycle Window Use the information in Table 40 to specify the combination of period and offsets on which the run cycle is based. When you select the run cycle from the list. Type the name of a user-defined period. The following happens: ¶ Workload Scheduler for z/OS calculates the days of the run cycle. and Delete. Add. you can then select a number of actions on the run cycle. Table 40. If you right-click it. such as Properties. Available offsets Select the days when you want the job stream to run in the period..Creating Offset-based Run Cycles Figure 37. ¶ The run cycle name is displayed in a list to the left of the graphic calendar in the Run Cycle view. Select ordinal last days to count the days from the end of the period. In the following period Do this . Click OK. ¶ The rundays are displayed in blue in the graphic calendar... see “Finding Objects” on page 48.. Offset-based Run Cycle Rules Information In this area . If you do not know the name.

This run cycle schedules job stream PAYRO21 to run on every second day of each cycle. Example 1: Offset-based Run Cycle Example 2: Offset-based Run Cycle Defined The next figure shows the offset for run cycle PER1. Creating Job Streams Figure 38. 9. Figure 39. Example 2: Offset-based Run Cycle Defined Tivoli Job Scheduling Console User’s Guide 103 . beginning from a Valid date of August 21. The offset is the second day of the user defined period.Example 1: Offset-based Run Cycle The next figure shows an offset-based run cycle named PER1. 2001. also named PER1.

To open the Timeline view of a job stream. Job Stream Editor . Figure 40.Checking Time Restrictions in the Timeline View The Timeline view of the Job Stream Editor shows graphically the time restrictions of the jobs and run cycles of a job stream in the database. on a daily and hourly scale. Right-click anywhere along the lower scale.Timeline View The inside of the window has four panes. at a glance.1 . to ensure that the time dependencies you specified are correct and coherent. Activity Bars The right half of the window contains activity bars that represent. The left half of the window. You can customize the timescale in the following way: 1. A pop-up menu is displayed. Table Frame The table frame is the left half of the window and contains columns that display the following information: 104 Version 8. Select the radio button that matches your preference. See the sample Timeline view in shown in the next figure. It can also show if there are inconsistencies within the time restrictions of individual jobs. You can size the panes by dragging the horizontal and vertical lines that divide the window. the time restrictions defined for every run cycle and job. While you create a job stream. and the job stream jobs in the lower pane. 2. 3. click the Timeline button from the toolbar of any of the other views of the Job Stream Editor. the Timeline view helps you. The view can point out inconsistencies between the time restrictions of jobs and those of run cycles. Move your pointer to Timescale to display available choices. You can modify the time restrictions of a job or run cycle with a click of your mouse. lists the job stream run cycles in the top pane.

or by dragging the whole activity bar. ¶ The expected duration of the job. Note: The run cycle time restrictions inherited from a template are displayed in read-only mode. ¶ An information button showing what type of time restriction. the blue bar becomes red.¶ A warning button for inconsistencies in time restrictions. To modify them. a warning icon marks the run cycle that does not include the job. you have to open the Job Stream Editor window of the particular template. each job has. Time restrictions for a job are shown by a thick blue bar that represents the time interval from the start to the deadline of the job. you have to double-click the job in the upper left pane and open a Time Restrictions page. The activity bars for jobs that start with the job stream change position when you select different run cycles. ¶ View the earliest start time of the first job and latest deadline time for the last job to see the total run time of the job stream. an indicator displays the selected time. This button marks a run cycle when Workload Scheduler for z/OS detects that there are jobs with time restrictions outside the time restrictions of the run cycle. if any. The job deadline is indicated by a black vertical line. Creating Job Streams Other Tasks In the Timeline view you can also: ¶ Detect inconsistencies in time restrictions. To specify a deadline for the job. ¶ See which jobs have a specified start time. which jobs follow job stream rules. by looking at the button at the beginning of the job activity bar. if the time restrictions of any job are such that it is not within the time restrictions of a run cycle. You can only move the right end of the thinner bar because the start position is calculated automatically based on the job dependencies. You can change the start and the deadline by dragging the left and right ends of the two bars. Where the duration of the job exceeds the deadline. the jobs with a specified start time have a clock. Time Restrictions In the upper right pane. As you move the bar. If a job has no specified deadline. the thick bar is replaced by a vertical stripe indicating the start. and which jobs have no restrictions on start time. You can only move it forward or backward. ¶ The run cycle name or job identifier . 9. and the jobs that follow job stream rules have a clock superimposed on a job stream. You can move the interval of time between the start and the deadline times of the job by dragging either end of the thicker bar (or the whole bar). If you point your mouse on the triangle. ¶ Click a run cycle to see how it affects the jobs that start with the job stream. light blue line that represents the expected duration. a hover help on the triangle lists the jobs that are not included. The deadline is indicated by a vertical black line at the end of the blue bar. and by a thinner. ¶ The expected start and deadline times of the run cycle or job. the run cycle time restrictions are displayed by a blue bar that represents the time interval from the start to the deadline of the run cycle. Tivoli Job Scheduling Console User’s Guide 105 . The jobs with no restrictions have a lightning bolt. Specifically.

106 Version 8.) to open a Find Job Stream window. Job streams are saved in the scheduler database. as explained in the next chapter.. Table 41.. you can save the job stream. for instance the jobs that are in it. To save the new job stream. Figure 41. click the Save button in the Job Stream Editor toolbar. Job Stream Name Enter this information . Submit a Job Stream To submit an existing job stream into the plan. then save it and open it again later. job dependencies. Just remember to wait to mark it active when it is ready to be scheduled. Submit Job Stream Window In this area . duration. Submit Job Stream Window Use Table 41 to complete the information needed to submit the job stream. right-click a scheduler engine and select Submit Job Stream from the pop-up menu. you can change the earliest start time and deadline of a run cycle. The Submit Job Stream window is displayed.. The Job Stream Editor checks for any missing or invalid information. ¶ See which jobs start according to the start time of the job stream. If you do not remember the name of the job stream. then saves the job stream in the application description database. Saving a Job Stream After you have specified job stream properties and defined jobs. click the ellipsis (. to define its run cycles.1 . and how those jobs are affected by various rules. The name of the job stream. ¶ Change the earliest start time.¶ Open the Time Restrictions page of a Run Cycle Properties window or of a Job Properties window by double-clicking on a run cycle or job in the Table frame.. In the same way.. Note: You can save a job stream from any of the three views available in the Job Stream Editor. and deadline time of a job by moving different components of the activity bar.. You can define parts of a job stream. and run cycles.

click the ellipsis to search for a variable table name. plan and opens the Graph job stream instance... Alternatively. JCL variable table Name of the variable table that the scheduler can use on the days generated by this run cycle. such as resource and workstation dependency.. The defaults are the values in the first run cycle. ¶ Click Cancel to close the window without submitting the job stream. Job stream template Name of the job stream template to which the job stream belongs. Authority Group Name used to generate a RACF resource name for authority checking. Properties Opens the Submit Job Stream Header Info window where you can modify various properties of the job stream: Priority How the job stream ranks in importance compared to other jobs streams. This field does not apply to job stream templates. Description A brief description of the job stream. The lowest priority is 1 and the highest priority is 9. The defaults are the values in the first run cycle. Owner Name of the person responsible for the job stream. are considered in determining priority. Tivoli Job Scheduling Console User’s Guide 107 . This information is optional. plan but it does not start. Other factors. This value is not definitive. Submit Job Stream Window (continued) In this area . Owner description A brief description of the job stream owner. The latest Date and Time when the job stream can end. 9. One of the following: Simple Submit Adds a new job stream instance in the Submit & Hold Adds a new job stream instance in the It is on hold.Table 41. Start Deadline Status of Job Stream Enter this information .. Submit & Edit Adds a new job stream instance in the view so you can modify the submitted plan. This means that a job stream with a priority of 3 will run before a job stream with a priority of 1 when job streams are competing for resources. Creating Job Streams When you have finished: ¶ Click OK to submit the job stream and close the window. The Date and Time when the job can start.

108 Version 8.1 .

Listing and Modifying Job Streams 10 Listing and Modifying Job Streams To view job streams. The list is called All Job Streams and displays all the job streams defined in the Workload Scheduler for z/OS database. You can modify properties and make them less general by adding the filters of your choice. To learn how to list job stream instances. see “Listing Job Stream and Job Instances” on page 119. see “Managing Job Streams” on page 127. Default Job Stream List The Job Scheduling Console provides a job stream list. and modify job stream properties ¶ Define new job streams starting from existing definitions ¶ Create and delete jobs and external jobs. Creating a Job Stream List A job stream list allows you to view and modify job stream definitions. and modify job properties ¶ Add and delete dependencies between jobs ¶ Create and delete run cycles. You can: ¶ Open and delete a job stream.10. You can find it in the Default Database Lists group in the tree of every engine shown in the Job Scheduling view. and modify run cycle properties ¶ View and change the time restrictions of run cycles and jobs Tivoli Job Scheduling Console User’s Guide 109 . Job stream instance list Produces a filtered list of already scheduled job stream instances together with their time restrictions. This list works like any other user list. You can display its properties and see from the empty fields that no selection criteria are specified. To learn how to use job stream instance lists. you must create and display a job stream list in the Job Scheduling view. which are stored in the database. You can create two types of job stream list: Job stream list Produces a filtered list of job streams or job stream templates defined in the Workload Scheduler for z/OS Application Description database. This chapter explains how to list job streams from the Workload Scheduler for z/OS database and how to use job stream lists.

then specify a refresh interval in seconds..The changes you make from a job stream list already generated will not reflect these changes. The Properties . Table 42... —OR— Apply Defaults Click this to use the defaults specified in the Scheduler Properties window available in the Job Scheduling view.Job Stream List window is displayed. select an engine in the Job Scheduling view and click the List Job Streams button. To create a job stream list.Job Stream List Information In this area . The Properties .Job Stream List Window Use the information in Table 42 to enter the requested information to create the job stream list. Periodic Refresh Select this if you want the list results refreshed automatically. Note: Do not specify frequent refreshes of many detached views open at the same time in order to prevent from overloading your system.. Type a name for the job stream list.1 . Figure 42. Properties . Name Periodic Refresh Options Do this . 110 Version 8.

A list object with the name you specified is added to the tree under the engine you selected at the beginning. Dates Lists all the job streams valid within the interval you specify in From and To. Filter Criteria Do this .10. before saving it. Use wildcards to help your search.. or combinations of two or more parameters. Owner Lists all the job streams that belong to this owner. The default is to ignore this criteria... Job stream Lists all the job streams with this name or namestring. Tivoli Job Scheduling Console User’s Guide 111 .Job Stream List Information (continued) In this area . No lists only job streams that contain jobs that are not selected for monitoring by Tivoli Business Systems Manager. Status of Job Stream Lists all the currently active or inactive job streams. depending on which button you select. Optionally. Contains Monitored Job Yes lists only job streams that contain jobs selected for monitoring by Tivoli Business Systems Manager. Is a template Lists only job streams that are templates. Authority group Lists all the job streams that use this authority group for RACF authority checking. Click OK to save the list. Task name Lists all the job streams where this task or JCL is used. Ignore criteria lists job streams. Exclude template Lists only job streams that are not templates. Job stream template Lists all the job streams that are part of this template. Priority Lists all the jobs streams that have the priority level you select in From and To. Calendar Lists all the job streams that use this calendar. Listing and Modifying Job Streams Table 42.. regardless of whether they contained jobs that are monitored by Tivoli Business Systems Manager. Properties . Specify any of the following search parameters. Workstation Lists all job streams containing jobs that run on this workstation. you can run the list by clicking Apply.

Alternatively. 2. The list of job streams is displayed in the right-hand pane. ¶ Any of the jobs that it comprises. Figure 43. To use an existing Job stream list: 1. create a list as described in “Creating a Job Stream List” on page 109 and run it by clicking on Apply.Displaying a Job Stream List To display a list of job streams in the database.1 . Select an engine to display all the created lists in the right-hand view of the console. ¶ Any of the run cycles that define its scheduling. 112 Version 8. use an existing list. Displaying the Results of a Job Stream List 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 Streams Modifying a job stream involves changing any of the following: ¶ The job stream properties. as shown in the next figure. as well as any dependencies that might exist among them. Double-click the list object you want to use.

. The Graph view of the Job Stream Editor opens. or delete jobs and dependencies in an existing job stream: 1. double-click the job stream you want to open. ¶ For job streams that inherit their scheduling information from a template.10. Click on Save. Open the template to see the scheduling information for the job stream. 2. In the Graph view of the Job Stream Editor. right-click the job and select Properties from the pop-up menu. Make the changes you want in the window (see “Specifying Properties for the Job Stream” on page 80 for details about the Job Stream Properties window). 3. modify. Note: If any of the job buttons in the Graph view display a superimposed question mark. “Creating Dependencies between Job Streams” on page 92. Adding and Modifying Jobs and Dependencies in the Graph View To add. it means that an external job is missing because the job or the job stream to which it belongs were deleted in the meantime. see “Creating a Job” on page 82). this is an indication that the definition of the workstation associated with the particular job cannot be found in the database. ¶ Click Cancel to discard your changes and close the window. 2. 3. Display a job stream list. Modifying Job Stream Properties To modify the properties of a job stream in the database: 1. Table 43. ¶ For normal job streams you can open the Graph. When you have finished: ¶ Click OK to save the changes.. “Creating a Job” on page 82. Adding and Modifying Jobs and Dependencies in the Graph View To do this . Apply your changes (for information about how to do this. if an button label displays a (Not Found) string. and Run Cycle views. Run a job stream list. Right-click the job stream and select Properties from the pop-up menu. Tivoli Job Scheduling Console User’s Guide 113 . Listing and Modifying Job Streams To modify jobs and run cycles. Likewise. Timeline. Modifying a Job 1. The type of job stream determines which views you can access in the Job Stream Editor: ¶ For job stream templates. Create a new job in the job stream Add a new external job in the job stream Add a new dependency between jobs in the job stream See . 2... “Creating Dependencies between Jobs” on page 91. When the list is displayed. open the job stream from the list. you can open the Timeline and Run Cycle views. you can open the Graph view only.

right-click the job or external job and select Delete from the pop-up menu.. To do this: 1. 3. 4. To do this . Click OK in the confirmation window. Select Delete from the pop-up menu. 3. then External Job Stream. This option is valid until you save the job stream. 3. Select a run cycle in the run cycle list and right-click it to display the pop-up menu. Click OK in the confirmation window. For more information. When the list is displayed. 1. In the Graph view of the Job Stream Editor. Click the Run Cycle button to open the Run Cycle view of the job stream. you can use the Undo Delete option in the same pop-up menu or in the toolbar of the Graph view to put the job back in the job stream. right-click the external job and select Edit from the pop-up menu. An additional Job Stream Editor window is displayed. In the Graph view of the Job Stream Editor. see “Creating a Job Using Copy and Paste” on page 90. In this way. Adding and Modifying Run Cycles – Pop-up Menu click this option . The job is deleted from the job stream. Table 44. 4.. Removing a Dependency between Jobs 1. Click Save to save the job stream. Adding and Modifying Run Cycles Select a job stream from a job stream list and open the Run Cycle view of the Job Stream Editor. Editing Another Job Stream from an External Job Use an external job to open a second Job Stream Editor window and edit the job stream to which the job belongs. double-click the job stream you want to open. Run a job stream list. Properties.. Click Save to save the job stream. Edit the run cycle properties in the Run Cycle Properties window. you can work on existing run cycles or create new ones. A confirmation window is displayed. 2. The dependency is removed. The line becomes red and a pop-up menu is displayed 2.Adding a New Job using Copy and Paste You can use the Copy and Paste functions to save time when creating a job that shares many of the properties of an existing job in the job stream. 2.. 2.. As necessary. 114 Version 8. See “Scheduling Job Streams” on page 94 for reference. In the Graph view of the Job Stream Editor..1 . Note: If you change your mind. Deleting a Job or External Job To delete a job or external job from the job stream: 1. right-click the line that represents the dependency. open the views to work on the job stream and its components.

you can view and modify time restrictions for more than one run cycle and more than one job in the Timeline view.. Right-click anywhere in the window and select Paste from the pop-up menu. 2. 6. A Rule-based Run Cycle Properties window or an Offset-based Run Cycle Properties window opens with the same definitions as the model run cycle. When the list is opened. 3. In the Properties .10... Tivoli Job Scheduling Console User’s Guide 115 . and enter a new name before saving. 4.External Job window. Copy To do this . Run a job stream list. 5. For a full description of the Timeline view of a job stream. by using either the Job Properties window of the Graph view or the Run Cycle Properties window of the Run Cycle view. Right-click a job stream and select Open. Delete the run cycle from the job stream. In addition. Run a job stream list. You can modify the time restrictions of a job or of a run cycle. Adding and Modifying Run Cycles – Pop-up Menu (continued) click this option . Deleting Job Streams from the Database To delete a job stream from the database. Go to the Job Stream Editor where the first job stream is open. in the same way you created them. The job stream opens in the Graph view of the Job Stream Editor.. 3. For example: 1. see “Checking Time Restrictions in the Timeline View” on page 104. Click OK in the confirmation window. 2. Using Copy to Add an External Job You can use the Copy function on a listed job stream to add any of the jobs that comprise it as external jobs to another job stream. All the jobs that comprise the second job stream are displayed. right-click the job stream you want to delete and select Delete from the pop-up menu. To do this: 1. you use a job stream list.. Listing and Modifying Job Streams Table 44. Delete Viewing and Modifying Time Restrictions The Timeline view of the Job Stream Editor shows the time restrictions of the jobs and run cycles of a job stream. select Show jobs. Right-click another job stream in the list and this time select Copy from the pop-up menu. The job stream is deleted. Create an additional run cycle with the same properties as the selected one. Modify any definitions you need to.

Job Stream Editor .External Job Added 116 Version 8. Select the job or jobs that you want to add as external jobs of the first job stream. Properties . Figure 45.Figure 44.External Job window. 8. Icons for the added jobs are displayed in the Graph view of the first job stream.External Job Window 7. Click OK to close the Properties .1 .

6. change the default name to the name of your choice.10. 4. Listing and Modifying Job Streams Using Existing Definitions to Create Other Job Streams You can select a job stream from a list and use its definition to create other job streams with equal or similar properties. The Job Stream Editor and the job stream properties windows for the job stream that you selected are displayed. Tivoli Job Scheduling Console User’s Guide 117 . To do this: 1. 2. the new job stream is saved as CopyOfname. Save the new job stream and close the Job Stream Editor window. In the Name field of the job stream properties window. If you do not change the name. Right-click the job stream that you want to use as a model for creating another job stream and select Create Another from the pop-up menu. 3. where name is the name of the model job stream. In the Job Scheduling Console window. 5. In the job stream properties and Job Stream Editor windows make any other changes that you need to customize the new job stream for your requirements. Display a list of job streams. either click the Refresh List Results button or run another list to view the new job stream.

118 Version 8.1 .

To monitor and modify job and job stream instances.11 Listing Job Stream and Job Instances For jobs and job streams. also known as an occurrence. present. Listing Job Stream and Job Instances Creating Lists of Job Stream and Job Instances You can maintain several lists by creating list objects with different sets of filter criteria. “Managing Job Streams” on page 127 describes how to work with instances from the lists you create.. All Scheduled Jobs Displays a list of all the existing job instances. you can maintain lists of job streams for different status and error conditions. List jobs that have ended in error in the Create a list of jobs with a status of Error and a time last 24 hours interval between yesterday’s and today’s dates. For example. and future scheduled job streams.. You can also create lists to monitor the workload in progress or the outcome of scheduled jobs. you create and display lists for each. Perform this task . depend on a job that you know will end in error Search for all job streams that include a Create a job instance list and specify the identifier in the specific job 3 filter criteria. This chapter describes how to list job stream and job instances. an instance. The plan contains past. Table 45 shows some examples of how to use job and job stream instance lists: Table 45. Discover all the scheduled jobs that List the job in error and look at all its successors. See all job stream instances scheduled for the month of December 2001 Create a job stream instance list and specify the dates in the filter criteria. is a job or job stream that has been scheduled in the plan. The instance lists are: All Scheduled Job Streams Displays a list of all the existing job stream instances. Examples of How to Use Job and Job Stream Instance Lists To do this . It also contains the workstations and resources that support this workload. Default Instance Lists The Job Scheduling Console provides instance lists. 11. The resulting list displays all instances of job 3 and the job stream instance to which it belongs.. Tivoli Job Scheduling Console User’s Guide 119 .. You can find them in the Default Plan Lists group in the tree of every Workload Scheduler for z/OS engine shown in the Job Scheduling view.

if you want the list results refreshed automatically. Name Periodic Refresh Options Do this . You can display their properties and see from the empty fields that no selection criteria are specified.. Periodic refresh Select this to specify a refresh interval in seconds. Filter Criteria Specify any of the following search parameters. Type a name for the job stream instance list. Figure 46.Job Stream Instance List Information In this area ..The default instance lists work in the same way as user lists. Listing Job Stream Instances To list job stream instances. in the Job Scheduling view. select an engine and click the List Job Stream Instances button in the toolbar. Use wildcards to help your search.1 .Job Stream Instance List Window Use the information in Table 46 to specify the selection criteria for the list. 120 Version 8. The Properties . Properties . Apply defaults Click this to use the default specified in the Settings page of the Scheduler Properties window.. Properties . Table 46. You can modify their properties and make them less general by adding filters of your choice. or combinations of two or more parameters..Job Stream Instance List window is displayed.

If the job stream has no critical job. Pop-up calendars are provided to help you select the days.. Select No to exclude manually added job streams from the list. regardless of whether they contained jobs that are monitored by Tivoli Business Systems Manager.. if you select the Yes radio button..Job Stream Instance List Information (continued) In this area . Properties . The token is a unique 16-character hexadecimal string assigned to the job stream by the scheduler. Status Lists all the job stream instances with any of the following Job Scheduling Console status codes that you specify in the drop-down list: ¶ Waiting ¶ Running ¶ Successful ¶ Error ¶ Canceled Tivoli Job Scheduling Console User’s Guide 121 .. Select No to exclude these job stream instances from the list. Job stream template Lists all the job stream instances that are part of this template. Do this . Manually Added Lists all those job stream instances that were added manually to the plan (and not automatically through a plan extension). Occurrence Token Lists the job stream that is identified by this occurrence token in the plan. Job stream Lists all the job stream instances with this name or namestring. if you select the Yes radio button. Listing Job Stream and Job Instances Most Critical Job The start time of the most critical job. Owner Lists all the job stream instances that belong to this owner. Ignore criteria lists job streams. Dates Lists all job stream instances scheduled to run in an interval period starting on the day and time specified in the From Date and Time fields and ending in the day and time specified in the To Date and Time fields. Priority Lists all the job stream instances that have the priority level you select in From and To. 11.Table 46. Select Ignore criteria to omit this filter. Authority group Lists all the job stream instances that use this authority group for RACF authority checking. Select Ignore criteria to omit this filter. the field is blank. No lists only job streams that contain jobs that are not selected for monitoring by Tivoli Business Systems Manager. Contains Monitored Job Yes lists only job streams that contain jobs selected for monitoring by Tivoli Business Systems Manager. Rerun requested Lists all those job stream instances for which a rerun was requested.

1 . before saving the list. Internal Status Lists all the job stream instances with any of the following status codes 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. It generally provides more detail than the broader status code assigned by the Job Scheduling Console.. they are both displayed among the properties of job stream instances. Optionally. right-click it and select Open. List results are displayed in the right hand pane.Job Stream Instance List Information (continued) In this area .. An button of the new list is displayed in the tree under the engine you selected when creating it. However. you can click Apply to display the list results immediately. Click OK. Do this .Table 46. 122 Version 8. To display the list... Internal status refers to the status code assigned by the specific job scheduling engine. Properties .

. Job stream Lists all the job instances that are in the job stream with this name or namestring. Workstation Lists all the job instances run on this workstation.Listing Job Instances To list job instances. 11.Job Instance List window is displayed. You cannot use wildcard characters with this filter.Job Instance List window Use the information in Table 47 to specify the selection criteria for the list. Owner Lists all the job instances that belong to this owner. Tivoli Job Scheduling Console User’s Guide 123 . Task name Lists all the job instances that are associated with this task or JCL. Name Periodic Refresh Options Do this . Type a name for the list. select an engine and click the List Job Instances button.Job Instance List Information In this area . Listing Job Stream and Job Instances Figure 47. The Properties . Properties . Apply defaults Click this to use the default specified in the Settings page of the Scheduler Properties window. Use wildcards to help your search.. Table 47. Periodic refresh Select this to specify a refresh interval in seconds. The Properties . if you want the list results refreshed automatically. in the Job Scheduling view.. Filter Criteria Specify any of the following search parameters. or combinations of two or more parameters. Job identifier Lists all the job instances that have this identifier..

. Do this ..1 . Pop-up calendars are provided to help you select the days..You can use the following filters: CleanUp Type Select from the drop down list job instances that have one of the following cleanup and restart specifications: None Immediate Automatic Manual CleanUp Status Select from the drop down list job instances with either a Completed or Error cleanup state. Is Monitored Job Select this to specify whether to list jobs monitored by Tivoli Business Systems Manager. Authority group Lists all the job instances that use this authority group for RACF authority checking. No lists only jobs that are not selected for monitoring by Tivoli Business Systems Manager. Dates Lists all job instances that are part of job stream instances scheduled to run in an interval period starting on the day and time specified in the From Date and Time fields and ending in the day and time specified in the To Date and Time fields.Job Instance List Information (continued) In this area . Status Lists all the job instances with any of the following Job Scheduling Console status codes that you specify in the drop-down list: ¶ Waiting ¶ Ready ¶ Running ¶ Successful ¶ Error ¶ Canceled ¶ Interrupted ¶ Undecided 124 Version 8.. Restart Option Lists jobs according to their restart and dataset cleanup specifications. Ignore criteria lists jobs. Priority Lists all the job instances that have the priority level you select in From and To. Properties . Yes lists only jobs that are selected for monitoring by Tivoli Business Systems Manager.Table 47. regardless of whether they are monitored by Tivoli Business Systems Manager.

.3 or later. To display the list.. click the arrow and select one of the available policies. Properties . List results are displayed in the right-hand pane. An button of the new list is displayed in the tree under the engine you selected when creating it.. Internal Status Lists all the job instances with any of the following status codes that 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. 11. Internal status refers to the status code assigned by the specific job scheduling engine. Do this . Available for OPC 2.Table 47. Click OK.Job Instance List Information (continued) In this area . you can click Apply to display the list results immediately. before saving the list. Listing Job Stream and Job Instances Note: Status and internal status exclude each other as filter criteria.. they are both displayed among the properties of job instances. Available for OPC 2. However. right-click it and select Open. Tivoli Job Scheduling Console User’s Guide 125 .3 or later. Optionally. It generally provides more detail than the broader status code assigned by the Job Scheduling Console. WLM policy Lists all the job instances defined as critical jobs and for which the WLM policy you indicate here was defined.

126 Version 8.1 .

the List View and the Timeline View. List View The List View shows details about each instance. A group contains two or more job stream instances that have the same job stream name but Tivoli Job Scheduling Console User’s Guide 127 . Managing Job Streams Job Stream Instance Lists Job stream instance lists are displayed in two ways. In the Timeline View. job stream instances with the same names are listed in groups. Figure 48. 12. Job Stream Instances List View Timeline View The Timeline View displays graphic information about time restrictions.12 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.

The Properties . However. Click the arrow to display the individual instances.Job Stream Instance window. Job Stream Instances Timeline View The only possible action on a group of job stream instances is Delete all. you can modify some editable fields. you must first expand the group by clicking on the arrow. Browsing and Modifying Job Stream Instances You can browse and modify job stream instances in the Properties . the Time Restrictions page. or both. To perform the actions listed above and to display activity bars on the individual instances.1 . Using the General Page Right-click the job stream instance and select Properties from the pop-up menu. using the General page.different run times.Job Stream Instance window is displayed. Groups are indicated by a small arrow on their left side. Figure 49. Most of the details you see are in read-only mode. which you can select when you right-click the group. 128 Version 8.

and the identifier of the next job scheduled to run on the critical path. You can raise or lower it if the instance has not yet started. ¶ The earliest time at which you estimated the instance should start.. ¶ If the status is successful.Job Stream Instance General Page The General page displays: ¶ The name and description of the job stream. Click the ellipsis button (. Tivoli Job Scheduling Console User’s Guide 129 . if applicable.. ¶ The current status. to which the job stream belongs. ¶ The name of the table of JCL variables. ¶ The name of the calendar used for the schedule. ¶ The name of the function used to schedule the job stream. ¶ The priority level. ¶ The occurrence token that identifies where the job stream is in the plan. Managing Job Streams Figure 50. ¶ If the status is running. if any. their expected duration. if any.) to search for available tables. ¶ Whether the instance has been run again. at what time the instance started. used by the job stream. ¶ The name of the job stream template. and the owner.12. You can change them here in the same way as you can change them by moving the activity bar in the Timeline View. the amount of time it took the instance to complete. Properties . You can enter or change the name of a table. Using the Time Restrictions Page The Time Restrictions page contains the earliest start time and deadline that you specified when you created the job stream. ¶ The number of jobs that remain to be run in the critical path. ¶ The authority group name.

. The planned start time. Name Status Started Runtime Start at Deadline Specifies . Changing Time Restrictions in the Timeline View The left-hand pane of the Timeline View displays the following job stream instance details: Table 48.Job Stream Instance Time Restrictions Page When you have finished: ¶ Click Apply to save any changes and keep the window open. The planned deadline. 130 Version 8.. Job Instance Details Timeline View This column . The current status.Figure 51. Properties . The actual start time. ¶ Click OK to save any changes and close the window. ¶ Click Cancel to disregard any changes and close the window.1 . The job stream name... The actual duration.

12. a horizontal black line unfolds inside the activity bar to show the actual runtime. you can change the time restrictions of each instance and view the results of your changes. The activity bar shows the runtime of a job stream instance in terms of the start and deadline times that were specified as time restrictions for the job stream. 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 Tivoli Job Scheduling Console User’s Guide 131 .Job Stream Instance window.Right Pane By moving components of the activity bars. as you would by following the steps described in “Browsing and Modifying Job Stream Instances” on page 128 and going directly to the Time Restrictions page of the Properties . Timeline View . The deadline is indicated by a vertical black stripe at the end of the blue activity bar. Managing Job Streams Figure 53. as well as the specified time restrictions for the instances. Timeline View . As the instance starts.Left Pane The right-hand pane has activity bars that show the actual run time if the instances have begun.Figure 52.

hold down the left mouse button while moving the bar in either direction. Properties . Figure 55.1 . When you find the position you want. release the mouse button.Job Stream Instance Time Restrictions 132 Version 8. The Properties . 2. Rescheduling a Job Stream Instance As you move the bar. when the pointer becomes cross-shaped. a tooltip tells you the new deadline time at every position of the right end of the bar. showing the new start and deadline times.Job Stream Instance Time Restrictions window is displayed. Move the activity bar by positioning the mouse pointer inside the bar and. Figure 54.Rescheduling the Instance To reschedule the instance: 1.

Job Stream Instance Time Restrictions window is displayed. Managing Job Streams Figure 56. Position the mouse pointer on the right end of the bar. 12. The left end of the activity bar is set on the new position. 2. When the pointer becomes a double arrow. When you find the position you want. Position the mouse pointer on the left end of the bar. When the pointer becomes a double arrow. Rescheduling the Start time of a Job Stream Instance As you move your mouse. hold down the left mouse button while moving the end of the bar. release the mouse button. Tivoli Job Scheduling Console User’s Guide 133 . The Properties . a tooltip tells you the corresponding start time at every new position of the left end of the bar. 3. showing the new start time. hold down the left mouse button while moving the end of the bar. Rescheduling the Deadline Time To reschedule the deadline time: 1. ClickOK to save the new settings. Click OK.3. The activity bar is set on the new position. Rescheduling the Start Time To reschedule the start time: 1.

In a list. To set a job stream instance to Waiting status to force it to restart: 1. Click OK to save the new settings.Figure 57. Setting a Job Stream Instance to Complete To force the completion of a job stream instance: 1. Setting a Job Stream Instance to Waiting Note: Use this option only if no external jobs have started. The right end of the activity bar is set on the new position. In a list. 2. right-click the name of an instance or group of instances and select Delete from the pop-up menu. Rescheduling the Deadline Time As you move your mouse. 3. right-click the job stream instance and select Set to Complete from the pop-up menu. a tooltip tells you the corresponding deadline time at every new position of the right end of the bar. The Properties . A confirmation window is displayed.Job Stream Instance Time Restrictions window is displayed. 2. The instance or instances are deleted and removed from the plan. 2. In a list. Click OK in the confirmation window. The status of the job stream instance is changed to Complete. release the mouse button. right-click the job stream instance and select Set to Waiting from the pop-up menu. showing the new deadline time. Click OK in the confirmation window. A confirmation window is displayed. Deleting a Job Stream Instance To delete a job stream instance: 1. The status of all the job instances that are part of the job stream is also set to Complete. 134 Version 8.1 . When you find the position you want.

Tivoli Job Scheduling Console User’s Guide 135 . When you rerun the instance. The following 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. 2. continue with step 4. The Job Stream Instance Rerun Editor is displayed. Note: To be able to rerun a job stream instance. If you want to.2. In a list. The status of all the job instances that are part of the job stream is also set to Waiting. you can specify with which job is to start first. restart cleanup must be enabled in the job properties. you can also select: StartCleanup Starts a cleanup operation. For further information. Rerunning a Job Stream Instance You can change the status of a job and rerun a job stream instance. DisplayCleanup Displays the last data set to be cleaned up. This can only be done on the host. showing information about the instance. see “Restart and Cleanup” on page 160. Click OK to rerun the job. Edit JCL Select this to edit the JCL for the job. The Rerun Impact List window is displayed. The status of the job stream instance is changed to Waiting. Data Set List Select this to specify with which data set to restart. otherwise. Click OK in the confirmation window. Execute Select this to run the restart and cleanup with specifying any specific instructions. To rerun a job stream instance: 1. Right-click the job where you want to start the rerun and select StartFrom. 12. select Use Restart and Cleanup. 4. right-click the job stream instance and select Rerun from the pop-up menu. Managing Job Streams Additional Options In addition to the StartFrom option in the pop-up menu. 3.

1 .136 Version 8.

you use job instance lists. Managing Jobs 13 Managing Jobs This chapter explains how to: ¶ Browse and modify a job instance ¶ Add. 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. Tivoli Job Scheduling Console User’s Guide 137 .13. remove.

the List View and the Timeline View. Figure 58. List View The List View shows details about each instance. Job Instances List View Timeline View The Timeline View displays graphic information about time restrictions. In the Timeline View. Click the arrow and the individual instances are displayed. Figure 59.1 . A group contains two or more job instances that have the same runtime but different identifiers. job instances that share the same job stream instance and runtime are listed in groups. Job Instances Groups in the Timeline View 138 Version 8. Groups are indicated by a small arrow on their left side.Job Instance Lists Job instance lists are displayed in two ways.

¶ Click Cancel to disregard the changes and close the window.13. Tivoli Job Scheduling Console User’s Guide 139 . you must first expand the group by clicking on the arrow. ¶ Click OK to save any changes you made and close the window. 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. you can perform the following actions on a group of job 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 on the job instances arranged in a group. Managing Jobs As shown in Figure 59 on page 138. Browsing and Modifying Job Instances List the job instance that you want to work on then right-click it and select Properties from the pop-up menu.

This field is editable. and actual start times of the job instance. Figure 60.. The name of the authority group of the job stream. 140 Version 8. Properties . The name of the job stream to which the job belongs.. Properties .JCL Job Instance Instance General Page Table 49 describes the contents of the window. The name of the workstation running the job.JCL Job Instance General Information This area .General Page The General page contains general information about the job instance. This information is mainly read-only. The time it took the instance to run if completed. The code with which the instance ended in error.. The job identifier. The priority level of the job stream to which the job belongs. The earliest. The status of the job instance. when applicable. latest. Occurrence Token Identifier Workstation Priority Started Runtime Belongs to job stream Description Authority group Internal status Status details Error code Start Time Contains this information . A description of the job. Table 49. Additional information about the status of the job instance. planned..1 . The actual date the instance started. Identifies where the instance is in the plan.

.13. Properties .JCL Job Instance Task Page Table 50 describes the contents of the window.JCL Job Instance Task Information This area . Tivoli Job Scheduling Console User’s Guide 141 . Managing Jobs Task Page The Task page contains editable information about any task or JCL that the job instance may be associated with: Figure 61. Table 50.. The job class letter. The printer form number if the job is a printer job.. Properties . The name of the task associated with the job instance.. Task name Form number Job class Contains this information .

1 . and duration that you specified when you defined the job in the database.JCL Job Instance Time Restrictions Page 142 Version 8. Workload Scheduler for z/OS calculates the planned start time and deadline. You can change them here if the job has not started yet. Figure 62. However.Time Restrictions Page The Time Restrictions page contains the start time. deadline. Properties .

13.. If there is an intermediate start.. The planned duration time. ¶ The number of logical resources reserved for the job.. ¶ The number of predecessors that have completed. Latest out passed On critical path Urgent JCL preparation The latest end time passed. The time of actual end. This group box displays: ¶ The number of jobs whose completion is necessary for this instance to run. The job number assigned by JES. if the instance completed. This can be one of: ¶ Completed ¶ Error ended If no status is displayed.JCL Job Instance Details Information This area . JES job number Planned duration Intermediate start Actual end Transport time Dependencies Contains this information . Figure 63. See the Successors page of the Job Instance Dependencies window for a list. CleanUp Status Tivoli Job Scheduling Console User’s Guide 143 . Properties . either data set cleanup has been reset or it has not yet started.. Table 51.JCL Job Instance Details Page Table 51 describes the contents of the window. Whether the job instance is on the critical path. ¶ The number of jobs that depend on the completion of this instance. The transport time. The status code of the data set cleanup action. Whether JCL preparation is required. Managing Jobs Details Page The Details page displays additional information about the job instance. See the Predecessors page of the Job Instance Dependencies window for a list. Properties . The urgency indicator.

Available for OPC 2.. Properties . Deadline The scheduler intervenes if the job runs beyond the deadline.1 . If a critical job runs late. Latest start The scheduler intervenes immediately if the job starts after the latest start time. Available for OPC 2. To use this option. Long duration The scheduler intervenes if the job takes longer than it should as compared to the statistics that it keeps.. it is eligible for Workload Manager (WLM) service class promotion. Whether a write-to-operator message should be sent when the job misses its deadline.3 or later.. Deadline WTO WLM policy Contains this information .3 or later.. The policy can be: Conditional The scheduler uses an algorithm to determine whether to apply the Deadline or the Latest start option.Table 51. Whether or not the job has been defined as a critical job.JCL Job Instance Details Information (continued) This area . you must also select the Critical job check box. The policy applied for WLM service class promotion if this job is late. Critical job 144 Version 8.

Click the check box to set this feature on or off. Cancel if late Auto submit Restartable Reroutable Restart CleanUp Highest acceptable return code User data Tivoli Job Scheduling Console User’s Guide 145 . Click the check box to set this feature on or off.. Managing Jobs Options Page The Options page contains job instance properties that you can change. Auto release Auto error completion Contains this information .. Whether the instance should be submitted automatically. Whether the instance should be made reroutable. This field is read-only. The highest acceptable return code for the instance. Editable user data. Whether the instance should be cancelled automatically if late on schedule.Write-to-Operator Job Instance Options Information This area . No. You can update this field. No. or Default to keep the original job definition. Whether the instance should be made restartable. Select the check box to set this feature on or off.. Properties . Select the check box to set this feature on or off. Table 52. Whether the instance should be automatically completed in the event it ends in error. Figure 64.. Whether Restart CleanUp is used if the job instance ends in error. You can change to Yes. Whether the instance should be automatically released. or Default to keep the original job definition. Properties .JCL Job Instance Options Page Table 52 describes the contents of the window. You can change to Yes.13.

You can modify quantities by double-clicking the field and entering a new value. shown in the next figure.Resources Page The Resources page.JCL Job Instance Resources Page Click the pull-down arrow and select the type of resources you want to see. Properties . shown in the next figure. and of the parallel server. Target Resources for a Job Instance 146 Version 8. Target Resources The Target resources list. contains information about the target and logical resources used by the job instance. Figure 66. Figure 65.1 . displays the quantities of workstation resources 1 and 2.

Whether to keep the resource allocated. displays information about any defined resource. Double-click any cell to enter new values or to choose values from the drop-down lists. Note: You can only add or remove logical resources.. Available options are Yes. When removing a resource.. Managing Jobs Logical Resources The Logical resources list. When adding a resource. Logical Resources Information This area . Table 53. Figure 67. click the ellipsis (. The resource quantity... To add or remove resources in the list. Logical Resources for a Job Instance Table 53 describes the contents of the window. click the Add Row or Remove Row buttons.. select the resource before clicking on Remove Row.. The access type. Resource Quantity Access type Keep on error Contains this information . Available options are Shared or Exclusive. Tivoli Job Scheduling Console User’s Guide 147 . not target resources.13. shown in the next figure. if it goes on error. No. The resource name. and Default to use the choice specified in the original job definition.) under the Resource field to locate resources with theFind tool.

The Dependencies . Dependencies . then right-click it and select Dependencies from the pop-up menu.Browsing and Modifying Job Dependencies This section describes how to browse and modify the job dependencies of a job instance.. widen the column heading cells with your mouse. Table 54.1 . if it is external. List the job instance that you want to work on. The identifier of the predecessor job. The name of the job stream to which the predecessor belongs. Predecessors Window The Predecessors window displays information about the job instances that must complete before this instance can start running: Figure 68.JCL Job Instance Predecessors window is displayed. The current status of the predecessor. Dependencies Predecessors Information This area . The name of the task associated with the predecessor job.. Job Stream Name Identifier Job Stream Start Task Name Status Contains this information .JCL Job Instance Predecessors Window Table 54 describes the contents of the window. 148 Version 8. if it is external.. The start time of the job stream to which the predecessor belongs.. Note: If you cannot read the headings completely.

13. To insert these data in the row you are working on. then complete the fields of the new row. then click on the Delete Row button in the top right of the window. Tivoli Job Scheduling Console User’s Guide 149 . This opens a Find Job Instance window where you can start a filtered search of the job you are seeking.. Select Successors in the left pane. Change listed predecessors Add a predecessor Perform this task . and job stream start date. Identifier. Dependencies Predecessors Tasks To do this .. or information about it. just click Apply in the Find Job Instance window. Click the Add Row button in the top right of the window. Managing Jobs You can modify the information of this page in the following way: Table 55. Delete a predecessor Select the predecessor. select the ellipsis that displays when you double-click the Job Stream Name. The Successors page is displayed. job identifier. or Job Stream Start fields. Double-click each field to replace the information. The search produces information in terms of job stream name... If you need help to find an external predecessor job.

Dependencies Successors Information This area .. 150 Version 8. Table 56. The name of the job stream to which the successor belongs. widen the column heading cells with your mouse. Note: If you cannot read the headings completely. Figure 69..Successors Window The Successors page displays information about other job instances that depend on the completion of this instance to start running.. if it is external. Dependencies . The current status of the successor. if it is external.. The name of the task associated with the successor job. Whether the successor job is on the critical path The start time of the job stream to which the successor belongs. Job Stream Name Identifier On critical path Job Stream Start Task Name Status Contains this information .JCL Job Instance Successors Page Table 56 describes the contents of the window.1 . The identifier of the successor job.

.. If you need help to find an external successor job.13. The search produces information in terms of job stream name.. Delete a successor Select the successor.. When you have finished: ¶ Click Apply to save the changes and keep the window open. Dependencies Predecessors Tasks To do this . job identifier. This opens a Find Job Instance window where you can start a filtered search of the job you are seeking. Change listed successors Add a successor Perform this task . ¶ Click Cancel to disregard the changes and close thge window. select the ellipsis (.) that displays when you double-click the Job Stream Name. Double-click each field to replace the information.. Click the Add Row button. ¶ Click OK to save any changes you made and close the window. Tivoli Job Scheduling Console User’s Guide 151 . or information about it. then click the Delete Row button.. To insert this data in the row you are working on. Identifier. and job stream start date. Managing Jobs You can modify the information of this page in the following way: Table 57. or Job Stream Start fields. then complete the fields of the new row. just click Apply in the Find Job Instance window.

Timeline View of Job Instances ..Changing Time Restrictions in the Timeline View The left-hand pane of the Timeline View displays the following job instance details: Table 58.1 . Timeline View of Job Instances .Right Pane 152 Version 8. see Figure 71. has activity bars that show the runtime of a job instance in terms of start. Figure 71. Name Status Started Runtime Start at Duration Deadline Specifies . and deadline times. duration.. The job name The current status The actual start time The actual duration The planned start time The planned duration The planned deadline Figure 70.Left Pane The right-hand pane.. Timeline View Job Instance Details This column ..

By moving components of the activity bars. You can change the time restrictions of an instance by: ¶ Rescheduling the instance ¶ Rescheduling the start time ¶ Rescheduling the deadline time Rescheduling the Instance To reschedule the instance in ready status: 1. Move the activity bar by positioning the mouse pointer inside the bar. Figure 72. It turns red if the duration exceeds the deadline and it becomes diamond shaped if the duration is zero. A pale blue bar represents the duration of the job. release the mouse button. Tivoli Job Scheduling Console User’s Guide 153 . Managing Jobs The deadline is indicated by a black stripe at the end of the blue activity bar. you can change the time restrictions of each instance and view the results of your changes. 2.13. 3. Rescheduling a Job Instance As you move the bar. The activity bar is set on the new position. A black line represents the actual runtime of the job instance. as you would by following the steps described in “Browsing and Modifying Job Instances” on page 139 and going directly to the Time Restrictions page of the job instance properties window. a tooltip tells you the new deadline time at every position of the right end of the bar. When the pointer becomes cross-shaped. The Properties . showing the new times. Click OK in the Time Restrictions page to save the new settings. When you find the position you want.Job Instance Properties Time Restrictions page is displayed. The activity bar represents the time difference between the earliest planned start and the planned end that were specified as time restrictions for the job. hold down the left mouse button while moving the bar in either direction.

Position the mouse pointer on the left end of the bar. Figure 73. Click OK to save the new settings. 3. release the mouse button. Rescheduling the Deadline Time 154 Version 8. The left end of the activity bar is set in the new position. Rescheduling the Deadline Time To reschedule the deadline time: 1. Rescheduling the Start Time As you move your mouse. When the pointer becomes a double-headed arrow. When you find the position you want. 2. Figure 74. The Properties . showing the new start time. hold down the left mouse button while moving the end of the bar.Rescheduling the Start Time To reschedule the start time: 1.1 . a tooltip tells you the corresponding start time for every new position of the left end of the bar. When the pointer becomes a double arrow. hold down the left mouse button while moving the end of the bar.Job Instance Properties Time Restrictions page is displayed. Position the mouse pointer on the right end of the bar.

Putting Job Instances on Hold To put a job instance on hold: 1. The Properties . 2. Deleting Job Instances To delete a job instance: 1. Click OK in the to save the new settings. A confirmation window is displayed. A confirmation window is displayed. release the mouse button.Job Instance Time Restrictions page is displayed. The right end of the activity bar is set in the new position. Click OK in the confirmation window. 2. Right-click the name of a job instance or group of job instances and select either Delete or Delete all from the pop-up menu. When you find the position you want. The instance or instances are released into the plan. 2. Releasing Job Instances To release a job instance: 1. Tivoli Job Scheduling Console User’s Guide 155 . Click OK in the confirmation window to delete the instance or group of instances. The instance or instances are placed on hold in the plan until they are released again. 2. showing the new deadline time.13. The instance or instances are deleted and removed from the plan. Right-click the name of a job instance or group of job instances and select either Release or Release All from the pop-up menu. Managing Jobs As you move your mouse. a tooltip tells you the corresponding deadline time for every new position of the right end of the bar. A confirmation window is displayed. Click OK in the confirmation window. 3. Right-click the name of a job instance or group of job instances and select either Hold or Hold all from the pop-up menu.

only the first level of dependent job instances is displayed. If you want to display more than one level of dependency. Impact View Window You can change the way the view is displayed by using the following buttons in the toolbar.. Note: If you display dependencies for more than one job. To display this type of view . Only the first level of dependenct job instances is displayed.. Radial Left Right Up Down Displaying Dependencies To display a dependency of a job instance. right-click a job instance and select Impact View from the pop-up menu. then either Predecessors or Successors.Showing Predecessors and Successors To show the predecessors of a job instance or its successors.. then refresh the display.. Any dependent job instances are displayed. The Impact View window is displayed. Figure 75. Impact View Options Select this button .1 . selecting Dependencies from the pop-up menu each time. you must right-click each dependent job instance in turn. 156 Version 8. right-click the job instance and select Dependencies from the pop-up menu. Table 59.

right-click the name of a job instance and select NOP from the pop-up menu. you can reset the display using one particular job instance as the starting. Managing Jobs Set as Root At any time. The display is refreshed. To reset the display in a separate window. Use this option on job instances whose internal status is one of the following: ¶ Arriving ¶ Ready ¶ Ready-non reporting workstation ¶ Waiting ¶ Completed (only for workstations with automatic reporting) To use the NOP option. or root. right-click the job instance you want to use as as the root job instance and select Set As Root from the pop-up menu. right-click the job instance you want to use as as the root job instance and select Set As Root In New Frame from the pop-up menu. Tivoli Job Scheduling Console User’s Guide 157 . Removing a Job Instance from the Plan You can use the NOP option to remove a job instance that is already in the plan and is ready or waiting to run. job instance. showing the selected job instance as the root instance. click Cancel to close the window. The Job Instance Output window is displayed. To do this. When you have finished.13. Browsing the Job Log To browse the job instance log. right-click a job instance and select Browse Job Log from the pop-up menu.

To do this: 1. A Change Status dialog is displayed. The job instance is restored to the plan. To do this. Otherwise. Figure 76. To force the running of a job instance. a field becomes available for entering any code you want to show in the properties window. the resources the job instance depends on must be available. Select the button for the status you want to use.1 . Right-click the name of a job instance and select Set Status from the pop-up menu. right-click the name of a job instance and select Execute from the pop-up menu. Running a Job Instance Immediately You can use the Execute option to immediately run a job instance that is ready to run regardless of normal scheduling rules excluding dependencies. the job instance is run immediately. right-click the name of a job instance and select UN-NOP from the pop-up menu.Restoring a Job Instance to the Plan You can use the UN-NOP option to restore to the plan a job instance previously removed with the NOP option. In order to run. the option is rejected. 158 Version 8. If all conditions are met. Changing the Status of a Job Instance You can set the status of a job instance manually. Note: If you are changing to an Error status. Change Status Dialog 2.

In a list. Tivoli Job Scheduling Console User’s Guide 159 . 4. ¶ Click Cancel to close the window without saving any changes. 3. Figure 77.13. The Edit JCL window is displayed. When you have finished: ¶ Click OK to save the changes and close the window. Click the Export button to save any JCL from the job you are editing. Click the Import button to open a JCL file and copy JCL into the edit window. Managing Jobs Editing JCL You can modify the variables and instructions associated with a job instance before submitting a job by editing the JCL associated with the instance. Make the changes you want. Edit JCL Window 2. right-click a job instance and select Edit JCL from the pop-up menu. To edit the JCL: 1.

Note: The Browse Operator Instruction option is only available if an operator instruction has been defined for the job instance. You can restart a job instance and perform cleanup operations. When you have finished. A default value is displayed. ¶ Click Cancel to close the window without saving any changes. View the results of the clean up. Right-click a job instance and select Restart and Cleanup from the pop-up menu. Modifying Job Setup The Job Setup option allows you to tailor a job before it is submitted. Completely restart the job. Each window shows the JCL for the instance. click OK. right-click a Job Setup job instance and select Job Setup from the pop-up menu. Restart and Cleanup Note: Before using this function. To do this: 1. Select one of the following: Step Restart Job Restart Start Clean Up Display Clean Up Result Use Expanded JCL Choose at what step of the JCL the job is to restart. 2. the Job Setup window is displayed where you can change the values of the promptable variables. Only clean up the environment. click OK. The Browse Operator Instruction window is displayed. To do this. If there are promptable variables that have not yet been set. Right-click the name of a job instance and select Browse Operator Instruction from the pop-up menu. 160 Version 8. you should refer to the Restart and Cleanup description in Tivoli Workload Scheduler for z/OS Planning and Scheduling. To do this: 1. Note: You can only change the variable value. if it has been set beforehand. When you have finished. When you have made your changes. Select this to use expanded JCL.1 . for each Job Setup JCL window: ¶ Click OK to save the changes and close the window. reflecting the change made to the promptable variables.Viewing Operator Instructions You can view any operator instructions associated with a job instance. The Restart and Cleanup window is displayed. A second Job Setup window is displayed for each successor job instance. 2.

14 Managing Workstations in the Plan This chapter describes how to monitor and update workstations in the plan. 14. Managing Workstations in the Plan Tivoli Job Scheduling Console User’s Guide 161 . You can: ¶ Monitor the status of a workstation in the plan and of the job instances scheduled to run on it ¶ Modify the settings and availability of the workstation ¶ Reroute the job instances that are scheduled to run on a workstation ¶ Modify the status of the job instances running on the workstation To perform these tasks. you use a filtered list of workstations in the plan.

in the Job Scheduling view. Figure 78. The Properties .Plan Workstation List window is displayed. To create a list of workstations in the plan. The Properties .Plan Workstation List Window 162 Version 8.Creating a List of Workstations A plan workstation list produces a filtered list of workstations allocated to the plan. select an engine and click the List Workstations in Plan button.1 .

In the group. —OR— ¶ Click Apply Defaults to use the default specified in the Scheduler Properties window available from the Job Scheduling view.Use the information in Table 60 to enter all the information needed to create the plan workstation list. If you leave all fields blank. or a question mark (?) to represent a single character.. Enter a name for the list. such as an asterisk (*) to represent strings of characters. Workstation Lists all the workstations with this name or namestring. Managing Workstations in the Plan Filter Criteria Tivoli Job Scheduling Console User’s Guide 163 . These workstations are used to run the Workload Scheduler jobs in the Workload Scheduler for z/OS plan.Plan Workstation List Information In this area . Reporting Attributes Lists all the workstations characterized by the reporting attributes you select with the following check boxes: ¶ Automatic ¶ Completion only ¶ Manual start at completion ¶ Non reporting Types Lists all the workstations of the type you select with the following check boxes: ¶ General ¶ Computer ¶ Printer Is Fault Tolerant Lists fault-tolerant workstations. Properties ... Select Periodic Refresh to specify an automatic refresh interval in seconds. Name Periodic Refresh Options Do this . To generalize your search. all the workstations defined in the database are displayed when you open the list. use wildcard characters. Table 60.. Select: Yes To list fault-tolerant workstations No To list workstations that are not fault-tolerant Ignore criteria To list workstations regardless of whether they are fault-tolerant or not ¶ 14. specify any of the following search parameters or combinations of two or more parameters.

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 the workstation if it becomes unavailable ¶ Change the quantities of workstation resources available for defined time slots and update 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 plan information. In addition to the workstation list. A list of workstations in the plan is displayed in the right pane of the Job Scheduling view. To see the lower pane.Displaying Workstations To display a list of workstations in the plan: 1. there is a lower pane that contains details about the jobs scheduled on the workstations. 164 Version 8. right-click Status of all Workstations and select Load List from the pop-up menu. Browsing and Modifying Workstation Properties From a workstation list you can view workstation details. Plan workstation lists are displayed in windows composed of two horizontal panes.Workstation in Plan General page is displayed. The Properties . Double-click an engine. 2.1 . Plan Workstation List Display For more information. Figure 79. Several fields are read-only. 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. see “Displaying by Status the Job Instances Scheduled on a Workstation” on page 171. In the tree that is displayed. drag the horizontal dividing bar located at the bottom of the window.

Whether an alternate workstation was defined. For example. Whether the workstation is used for WTO purposes. the system will not start more job instances at the workstation than there are available servers. Properties .. Whether the workstation is linked to the master.. Read-only. Read-only. Properties . Read-only. If you select Control on servers. Whether the workstation is used for started task support. Workstation name. Read-only. Whether the workstation is used for job setup. Read-only. Table 61. Read-only. Whether the workstation will reroute job instances to an alternate workstation. Read-only. Control on servers Job setup Started task. Read-only. before failing or going offline..Workstation in Plan General Page Table 61 describes the contents of the window.Workstation in Plan Resource page is displayed Tivoli Job Scheduling Console User’s Guide 165 . computer. Workstation description. Workstation type. This is one of: ¶ Manual start and completion ¶ Automatic ¶ Completion only ¶ Non reporting Changes the control on servers selection status. Name Description Workstation type Reporting attribute Specifies this information . The current status of the workstation. Managing Workstations in the Plan Figure 80.. The Properties .General Page 14. Editable. Whether the workstation is fault-tolerant. STC WTO Reroute jobs Alternate workstation Status Fault Tolerant Linked Select Resource in the left pane. Read-only.Workstation in Plan General Information This field . The reporting attribute. Read-only. Read-only.

1 .Resources Page Figure 81. For each of the two resources the window displays the name. Figure 82. select Used for control. To change the type of use of each resource. Job Summary Page Select Job Summary in the left pane. This means that. if an unexpected event happens while job instances are running. estimated duration. The Job Summary page is displayed. Properties .Workstation in Plan Job Summary Page This page displays the number. The information is provided for instances in the following status: 166 Version 8. the amount in use. the system considers the resource when it reschedules them. and actual duration (where applicable) of all the job instances scheduled to run on the workstation. and the type of use.Workstation in Plan Resource Page This page displays details about the two workstation resources. Properties .

¶ Completed ¶ Interrupted ¶ Started ¶ Ready ¶ Waiting Select Open Time Intervals in the left pane. the planned quantities of workstation resources and of parallel servers available. You can change the time boundaries and the values in the Modified fields. The Open Time Intervals page is displayed. 14. Properties .Workstation in Plan Open Time Intervals Page This page shows a list of time slots when the workstation is available to run jobs with resource quantities different from the default. The list shows the boundaries of each time slot and. for every slot. together with the name of the alternate workstation. Tivoli Job Scheduling Console User’s Guide 167 . Managing Workstations in the Plan Open Time Intervals Page Figure 83. for example). They correspond to the workstation Open Time Intervals definitions in the system database and can only be modified there (from a list of workstations in the database. You cannot edit the resource quantities and the alternate workstation names in the Planned fields. These values override the Planned values for the duration of the plan.

double-click the time field in the End Time column header. select the row describing the time slot and double-click the field you want to change. The new day is automatically entered in the field. Figure 84. To change the last day. To change the final time. Changing the Start Time 4. The new day is automatically entered in the field. double-click a date in the Start Date column. Enter a new quantity. Changing the Start Date 3. Enter the new time. 9. Click the pop-up calendar button and select the new day in the calendar. double-click in the Start Time column and enter the new time. Figure 85. 5.1 . To adjust the quantity of available parallel servers. 1. Click the pop-up calendar button and select the new day in the calendar. To change the initial time. To alter a value in a time slot. double-click the date field in the End Date column. 168 Version 8. 6.You can also add and delete time slots. double-click the field in the Modified PS column. 2. To change the starting day. 7. 8.

10. To adjust the available quantity of resource R1, double-click the field in the Modified R1 column.

14. Managing Workstations in the Plan

Figure 86. Changing the Quantity of Resource 1

11. Enter a new quantity. 12. To adjust the available quantity of resource R2, double-click the field in the Modified R2 column. 13. Enter a new quantity. 14. To change or add the name of the alternate workstation, double-click the field in the Modified Alternate column. 15. Enter a name for the workstation. To open a Find Workstations window, click the ellipsis (...). 16. To add a new time interval, click the Add Row button and enter details as explained in the previous steps. 17. To delete a time interval, select the row and click the Remove 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.

Tivoli Job Scheduling Console User’s Guide

169

Linking Fault-Tolerant Workstations
If a workstation is fault-tolerant, you can link the workstation to the master workstation. To do this, right-click on a workstation in the list and select Link from the pop-up menu.

Changing Workstation Status and Rerouting Scheduled Job Instances
You can manually change the status of a workstation and reroute scheduled job instances to an alternate workstation. This overrides, for the duration of the current plan, the corresponding 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. The Change Status - Workstation window is displayed.

Figure 87. Change Status - Workstation Window

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 status to 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 have already started when the status is changed, click the arrow in the drop-down list. The choices are: ¶ Restart ¶ Leave ¶ Set to error 4. To reroute scheduled job instances to an alternate workstation other than the one defined in the database, select Reroute jobs. 5. Enter a valid name in the Alternate workstation field. When you have finished: ¶ Click OK to save your changes and close the window. ¶ ClickCancel to close the window without saving any changes.

170

Version 8.1

Displaying by Status the Job Instances Scheduled on a Workstation
Use a workstation status list to browse the status of the job instances scheduled on a workstation 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, then Complete (for example) from the pop-up menu. All the job instances scheduled to run on the workstation and currently in Complete status are displayed in the bottom pane of the window. 14. Managing Workstations in the Plan

Figure 88. List of Jobs Scheduled on the Workstation and in Complete Status

Table 62 shows the list of options that you can select from the pop-up menu. Table 62. Workstation List Jobs Options
Select this option ... Arriving Complete Deleted Error Interrupted Ready Ready List To display jobs that ... Are scheduled to run on the workstation Have completed without errors Have been canceled on the workstation Have ended in error on the selected workstation Have been interrupted on the workstation Are ready to run on the workstation Are ready to run, including jobs that have a predecessor on a nonreporting workstation, but are ready to run on the selected workstation Have a predecessor on a non-reporting workstation, but are ready to run on the selected workstation Are running on the workstation Have an unknown status

Ready - Non Reporting Workstation Started Undecided

Tivoli Job Scheduling Console User’s Guide

171

Modifying the Job Instances Scheduled on a Workstation
Workstation status lists are useful, because they allow you to perform the same actions on job 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 Options
Select this option ... Properties Dependencies Delete Hold Release Browse Job Log Impact View NOP / UN-NOP Execute Set status Edit JCL Browse Operator Instruction Job Setup Restart and Cleanup To do this ... Browse and modify the properties of the job instance Browse and modify the dependencies of the job instance Delete the job instance from the plan Hold the job instance Release the job instance View the job log file Show the predecessors and successors of the job instance NOP or UN-NOP the job instance Run the job instance immediately Change the status of the 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

For an explanation about how to use these options, see “Managing Jobs” on page 137.

172

Version 8.1

15
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. Managing Resources in the Plan

Tivoli Job Scheduling Console User’s Guide

173

Creating a List of Resources
A 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 click the 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 availability interval. Table 64. Plan Resource List Information
In this area ... Name Periodic Refresh Options Do this ... Enter a name to identify the query. Select the Periodic Refresh check box and specify a refresh interval in seconds, if you want the list results refreshed automatically. Alternatively, click Apply Defaults to use the default specified in the Scheduler Properties window available in the Job Scheduling view. Specify search parameters or combinations of parameters. To generalize your search, use wildcard characters, such as an asterisk (*) to represent strings of characters, or a question mark (?) to represent a single character. If you leave all fields blank, then all the resources defined in the Resource Description database 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 following options: Wildcard Treat special characters as wildcards and character substitutes. Exact match Treat special characters as part of the resource name. Prefix Treat the string as a name prefix. Suffix Treat the string as a name suffix. ¶ Specify a resource group name in Group. ¶ ¶ Specify whether the resources are data sets with the DLF attribute or not, or if this is to be ignored, in Hiperbatch. ¶ In Allocation Options, specify whether or not the resources have been allocated for shared or exclusive use, or whether this is to be ignored. ¶ In Waiting, specify whether or not there are job instances waiting to allocate the resources, or whether this is to be ignored. ¶ In Available, specify whether or not the resources are available, or whether this is to be ignored.

Filter Criteria

15. Managing Resources in the Plan

When you have finished: ¶ Click Apply to display the list results immediately. ¶ Click OK to add the new list to the engine tree. To display the list, right-click it and select Load List.

Tivoli Job Scheduling Console User’s Guide

175

Displaying Resources
To 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 Scheduling view. The entries displayed are read-only. To modify details of resources already allocated to the plan, you must use the Properties - Resource in Plan window as explained in “General Page” on page 177. Plan resource lists are displayed in windows composed of two horizontal panes. In addition to the resource list, there is a lower pane that contains details about the jobs associated with the resources. To view the lower pane, drag the horizontal dividing bar located at the bottom of the window, as shown in the next figure.

Figure 90. A Plan Resource List Display

See“Displaying the Job Instances Associated with a Resource” on page 181 for details.

Browsing and Modifying Resources
From 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 specified defaults The changes you make from a plan resource list update the current resource plan information, which is stored in the plan. Right-click a resource from the list and select Properties from the pop-up menu.The page of the Properties - Resource in Plan Resource page is displayed.

176

Version 8.1

Table 65. Description of the resource. Read-only. Properties . Select one of: Free Keep Free if Exclusive Free if Shared Assume System Default Group ID Hiperbatch Used for On Error Tivoli Job Scheduling Console User’s Guide 177 . Read-only. Choices are Planning Control Planning And Control Neither Planning Nor Control What to do with the resource if a job instance that allocates the resource ends in error (and does not have an overriding keep-on-error specification in the job definition). Name Description Default Contains this information . It can be Yes or No. Modifies the type of use of the resource. Some of the information displayed is read-only. Properties .Resource in Plan Resource Page Table 65 describes the contents of this window. Name of the resource. Resource group ID. Read-only.. Whether the resource is enabled to Hiperbatch. Is Available Changes the availability status of the resource.General Page 15. Quantity Adjusts the default resource quantity that must be available while the plan is running by entering a new quantity in the Quantity field. Read-only..Resource in Plan Resource Information This area ... Managing Resources in the Plan Figure 91. Other information you can edit.

Table 65. Properties - Resource in Plan Resource Information (continued)
This area ... Deviation Contains this information ... Specifies the deviation in the resource quantity that must be available while the plan is running. To change the deviation, enter a value here. The deviation is an additional quantity with respect to the default quantity. A value of 0 means that no change in quantity was made for the plan. Note: If you change the deviation, then verify in the Quantity field the new total quantity available as the sum of the default and deviation quantities. If you did not specify any changes, the Deviation field displays 0, meaning that no change in quantity was made for the plan. Specifies the type of resource availability. To change it, select one of Yes, No, or Ignore.

Is available

Note: While the updates you make to most of these details are replaced by the database values at the end of the plan, the updates in Quantity and Deviation are retained also through plan extensions, unless they are changed manually. Click Default Workstations in the left pane. The Properties - Resource in Plan Default Workstations page is displayed.

178

Version 8.1

Default Workstations Page

15. Managing Resources in the Plan

Figure 92. Properties - Resource in Plan Default Workstations Page

This page displays the workstations that can use the resource. Table 66 shows how to add or remove workstations in this list by using the buttons in the upper-right side of the page. Table 66. Properties - Resource in Plan Default Workstations Information
To perform this task ... Remove a workstation Add all available workstations Do this ... Select the workstation and click on the Remove Row button. click the Add All Workstations button. A new row is added. It contains an asterisk, meaning that all available workstations are connected to the resource click the Find Workstations button. A Find dialog is displayed. Enter search parameters, or leave the field blank to make a general search, then click Start. The found workstations are displayed in a list. Double-click them to copy their name to the Default Workstations page

Add specific workstations

Click Availability Intervals in the left pane. The Properties - Resource in Plan Availability Intervals page is displayed.

Tivoli Job Scheduling Console User’s Guide

179

Availability Intervals Page

Figure 93. Properties - Resource in Plan Availability Intervals Page

This page shows a list of time intervals when the resource is available with properties different from the defaults. You can use this list to change the resource availability values in the defined intervals, or to add or remove availability intervals. Blank fields in an availability interval mean that the default values, as specified in the database or in the other pages of this window, are the valid ones during the interval. Table 67 shows how to add or remove workstations in this list by using the buttons in the upper-right side of the page. Table 67. Properties - Resource in Plan Availability Intervals Information
To perform this task ... Change the day in which the interval occurs Change the starting time Change the finishing time Change the resource quantity that is made available or unavailable for the workstations defined in the availability interval Change the availability status of the quantity defined in the previous field Do this ... Double-click the Date field and select the pop-up calendar button. In the pop-up calendar, choose a date and click it to enter it in the field. Double-click the From Time field and enter the new time. Double-click the To Time field and enter the new time. Double-click the Quantity field and enter a number.

Double-click the Is available field and select one of: Available Not available Default Default uses the value specified in the database.

180

Version 8.1

Table 67. Properties - Resource in Plan Availability Intervals Information (continued)
To perform this task ... Browse the workstations for which the availability specified in the previous fields is applicable Do this ... Click the ellipsis in the Workstations field to display a dialog with a list of workstations already defined for the time interval. The dialog also contains the Find Workstations, Add all Workstations, and Remove Row buttons featured in the Default Workstations page that enable you to update the list Add a new availability interval Delete an availability interval click the Add Row button and enter details as explained in the preceding steps. Select the row and click the Remove 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.

Displaying the Job Instances Associated with a Resource
Use a plan resource list to browse the status of the job instances associated with a resource and 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 Jobs from the pop-up menu, then select either Waiting for Resource or Using Resource. All the job instances scheduled to use the resource and currently in this status are displayed in the bottom pane of the window.

15. Managing Resources in the Plan

Modifying Job Instances Associated with a Resource
Plan resource lists are useful, because they allow you to perform the same actions on job instances 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 one of the follwing options: Table 68. Modifying Job Instance Options
Select this option ... Properties Dependencies Delete Hold Release NOP / UN-NOP Execute Set status To do this ... Browse and modify the properties of the job instance. Browse and modify the dependencies of the job instance. Delete the job instance from the plan. Hold the job instance. Release the job instance. NOP or UN-NOP the job instance. Run the job instance immediately. Change the status of the job instance.

For an explanation on how to use these options, see “Managing Jobs” on page 137.
Tivoli Job Scheduling Console User’s Guide 181

182

Version 8.1

III — Using the Job Scheduling Console with Tivoli Workload Scheduler
Chapter 16. Managing Database Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Creating a Group for Database Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a List of Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a List of Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a List of Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a List of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a List of Workstation Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a List of Prompts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a List of Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a List of NT Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a List of Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a List of Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Detaching a List Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a Database List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 190 190 191 192 193 193 194 195 195 196 197 198 198 198 199 199 199

Chapter 17. Managing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Creating a Job Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UNIX Script, NT Script, or Workstation Class Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UNIX Command, NT Command, or Workstation Class Command . . . . . . . . . . . . . . . . . . . . . . . . . MPE Job File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MPE User Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a List of Job Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a Job Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Job Definition Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a Job Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Job Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 202 206 206 207 207 207 207 208 208 209 209 211 211

Chapter 18. Managing Job Streams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Using the Job Stream Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Graph View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timeline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Run Cycle View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Job Stream Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 213 214 216 217 217 218

Tivoli Job Scheduling Console User’s Guide

183

Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prompts Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding External Dependencies for a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding an External Job Stream Dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding an Internetwork Dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding an External Job Dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting External Dependencies from a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a Job to a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Job Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying and Pasting Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cloning the Job Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding an Internetwork Dependency to a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding an External Job Stream to a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding an External Job to a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Dependencies Between Jobs in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Run Cycles for a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inclusionary or Exclusionary Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rule for Freedays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Colored Bars on Dates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Simple Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Weekly Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Calendar Run Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying Run Cycles for a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Run Cycles from a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Time Restrictions in the Timeline View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Time Restrictions for a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Timeline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using a Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Time Restrictions for a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Timeline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using a Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saving a Job Stream in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Closing the Job Stream Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a List of Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a Job in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Job in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying an Internetwork Dependency in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting an Internetwork Dependency in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying an External Job Stream in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting an External Job Stream in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying an External Job in a Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting an External Job in a Job Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

220 222 223 224 225 226 226 226 227 227 227 232 233 233 234 235 236 237 237 238 238 239 240 242 244 244 244 244 245 245 245 246 246 247 247 247 248 249 249 249 249 250 250 250 250 250 250

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

184

Version 8.1

Displaying a List of Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Workstation by Copying Another Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Workstation Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Workstation Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workstations Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a List of Workstation Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a Workstation Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a Workstation Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Workstation Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

255 256 256 256 257 257 257 258 258 259 259 260 260

Chapter 20. Managing Domains, Users, and Calendars . . . . . . . . . . . . . . . . 261
Managing Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a List of Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a Domain in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Domains in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a List of Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing User Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Holidays Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Freedays Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Calendar in the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a List of Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Calendar Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a Calendar in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 261 262 262 263 263 263 263 264 265 265 266 266 266 266 267 267 269 269 269 269

Chapter 21. Managing Resources, Prompts, and Parameters . . . . . . . . . . 271
Managing Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Resource. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a List of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Resource by Copying Another Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Prompts in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a List of Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a Prompt in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Prompts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 271 272 272 273 273 273 274 274 275 275 275 276

Tivoli Job Scheduling Console User’s Guide

185

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Plan List of Files . . . . . . . . . . . . . . Creating a Plan List of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Job Instances in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task Page . . . . . . . . . Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Using Plan Lists . . . . . . . . . . . . . . . Displaying Successors of a Job Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a List of Parameters . . . . . . . . . . . . . . . Displaying Dependencies of a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dependencies Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding Objects in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Managing Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Plan Tasks . . . . . . . . . . . . . . General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List View of Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internetwork Predecessors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a Parameter in the Database . . . . . . . Displaying a Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Plan List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Plan List of Domain Status . . . . . . . Releasing All Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Predecessors from a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Releasing a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Holding a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Plan List of Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a List of Jobs in the Plan . Prompts Page . . . . . . . . . . . . . . . . . . . . Creating a Plan List of Workstations . . . Creating a Group for Plan Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Plan List of Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 279 279 280 281 281 282 283 284 285 287 288 289 290 291 292 292 292 293 294 294 294 296 297 297 299 300 302 304 306 307 307 308 308 308 309 309 309 309 310 310 310 310 186 Version 8. . . . . . . . . . . . . . . . . . . . . . . . . . . Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timeline View of Job Instances . . . . . . Holding a Single Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Holding All Job Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Plan List of Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dependencies Page . . . . . . . . . . . . . . . . . . . . . . . 276 276 277 277 278 278 Chapter 22. . .1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Page . . . Releasing a Single Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . Successors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Predecessors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the Properties of a Plan List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the Properties of a Job Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Detaching a Plan List Display . . . . . . . . . . . . . . . . . Adding Predecessors to a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Files Page . . . Submitting a Job into the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Predecessors from a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Releasing a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set as Root . . . . . . . . Canceling a Job Instance . . Submitting Jobs and Job Streams into the Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a List of Job Streams in the Plan . . . Timeline View of Job Stream Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Page . . . . . . . . . . . . . . . . . . . . . Prompts Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Successors of a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Releasing a Job Stream Instance from Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time Restrictions Page . . . . . . . . . . . . . . . . . Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prompts Page . . . . . . . . . . . . . . . . . . . . . . Showing Predecessors and Successors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Files Page . . . . . . . . . . . . . . . . . . .Showing Predecessors and Successors . . . . . . . . . . . . . . . . . . . . Changing the Job Limit of a Job Stream Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Priority of a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Submitting an Ad Hoc Job into the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing or Modifying the Properties of the Job to Submit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Page . . . . . . . . . . . . . . . . . . Using a Default Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tivoli Job Scheduling Console User’s Guide 311 311 312 312 313 314 314 315 315 316 316 317 318 319 319 321 322 324 326 327 328 328 328 329 329 330 330 331 331 332 333 334 334 335 335 336 336 337 338 338 341 341 343 345 347 348 349 350 352 354 355 357 187 . . . . . . . . . . . . . . . . . . Confirming a Job Instance SUCC or ABEND . . . . . . . . . . . . . . . . . . . . . Adding Predecessors to a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Re-submitting a Job Stream Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Killing a Job Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prompts Page . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time Restrictions Page . . . . . . . . . . . . . . . . . . . . . . Holding a Job Stream Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Jobs . . . . . . . . . . . . . . . . . . . . . . Task Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Job Stream Instances in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resources Page . . . . . . . . . . . . . . . . . . . . . Releasing a Job Instance from Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Page . . . Using a Specific Job Stream . Displaying and Changing the Properties of a Job Stream Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Dependencies of a Job Stream Instance. . . . . . . . . . . . . . . . . . . . . . . . . Time Restrictions Page . . . . . . . . List View of Job Stream Instances . . . . . . . . . . . . Rerunning a Job Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Submitting a Job Stream into the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Predecessors Page . . . . Submitting Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Browsing the Job Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Canceling a Job Stream Instance . . . . . . . .

. . . Changing the Job Limit of a Workstation in the Plan . . . . . . . . . . . . . . . Switching the Domain Manager in a Domain . . . . . . . . . . . . . . . . . . . . . . . . . Starting a Workstation Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unlinking a Workstation Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting an Alternate Plan . . . . . . . . Displaying a List of Domains in the Plan. . Managing Prompt Dependencies in the Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Number of Units of a Resource Dependency. . . . . . . . . . . . . . . Displaying a Workstation Instance . . Managing File Dependencies in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Workstations in a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping the Workstations in a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Predecessors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping a Workstation Instance . . . . . . . . . . .1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 360 361 361 362 363 364 364 365 365 365 365 365 366 366 366 366 367 367 367 368 368 369 369 369 370 370 371 188 Version 8. . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Job Fence of a Workstation in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a List of Workstations in the Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Resource Dependencies Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Linking the Workstations in a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Properties of a Resource Dependency . Linking a Workstation Instance . . . . . Unlinking the Workstations in a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Domains in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . Managing Workstations in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replying to a Prompt Dependency . . . . Displaying File Dependencies Status . . . . . . . . . . . . . . . . . . . . Displaying Prompt Dependencies Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Resource Dependencies in the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 94. Tivoli supplies a basic set of lists in a group called Default Database Lists. Different groups maintain their individual properties even if they have the same name. You can create lists in the Workload Scheduler branch or you can create groups below the branch to organize your lists. When you create a list. After creating a group. Creating a Group for Database Lists To create a group for database lists: 1. You can use the same name for more than one group. ¶ Click Cancel to close the window without saving the new group. Right-click the group to display a pop-up menu with the following options: Tivoli Job Scheduling Console User’s Guide 189 . An button is created for the new group in the tree view of the Job Scheduling Console.Group of Lists window is displayed. you can create its member lists and subgroups. Managing Database Lists 16 Managing Database Lists Database lists are used to display objects in the scheduler database. Enter a name for the group. The Properties . When you have finished: ¶ Click OK to close the window and save the new group.16. it displays a filtered table of objects in the database. To create a group in an existing group. Click the Create a Group of Lists button on the toolbar or right-click the scheduler engine button and select Create Group from the pop-up menu. if you want. you give it a name and specify filtering criteria. Properties .Group of Lists Window 3. When you run a list. Select an engine in the tree. Each list you create is represented by an button in the tree view of the Job Scheduling Console. select the group and click Create a Group of Lists on the toolbar or right-click the existing group button and select Create Group from the pop-up menu. 2.

Table 69. resources. Properties Delete Create Database List Create Plan List Create Group To do this . right-click the engine or group button and select Create Database List then Job Stream from the pop-up menu. jobs. and other objects in the plan. Click the List Job Streams button on the toolbar. 2. Creating Lists To create a database list. Create a new list of job streams.. Alternatively. Properties List Options Select this option . Create a subgroup of more lists. 190 191 192 193 193 194 195 195 196 197 Creating a List of Job Streams To create a list of job streams: 1. Create a new list of job stream. workstations.. 190 Version 8. resource.. Job Stream Job Workstation Resource Workstation Class Prompt Parameter NT User Domain Calendar Go to page . Properties List Options To create this type of list . workstation. Change the group name..1 . To create the list in the scheduler branch.. right-click an engine and select one of the following options: Figure 95... and other definitions in the database.. Create Database List Pop-up Table 70. Select an engine in the tree. Delete the group and all its contents. expand the branch and select a group button.

select Periodic Refresh and enter a refresh interval in seconds in the Period (secs) field. enter a job stream name in the Job Stream Name field and a workstation name in the Workstation Name field. To filter the list results. 6. 5. Properties . A new button is created for the list in the tree view of the Job Scheduling Console. ¶ Click Cancel to close the window without running or saving the list. 4.Job List window is displayed. 2.Job List Window 3. Figure 96. Select an engine in the tree.Job Stream List window is displayed. Properties . right-click the engine or group button and select Create Database List then Job from the pop-up menu. If you want the list results refreshed automatically. The Properties . Alternatively.Job Stream List Window 3. Enter a name for the list in the Name field. When you have finished: ¶ Click Apply to run the list without closing the window. To create the list in the scheduler branch. Enter a name for the list in the Name field. Click the List Job Definitions button on the toolbar. ¶ Click OK to save the list and close the window. Click Apply defaults to enter the default refresh settings from the scheduler properties. Figure 97. Creating a List of Jobs To create a list of job streams: 1.16. The list results are displayed in the right pane of the Job Scheduling Console. Managing Database Lists The Properties . Tivoli Job Scheduling Console User’s Guide 191 . You can also use wildcards or leave the field blank to obtain an unfiltered list. expand the branch and select a group button.

To create the list in the scheduler branch. 4. To filter the list results. Click the List Workstations in Database button on the toolbar. Select an engine in the tree. right-click the scheduler engine button or group button and select Create Database List then Workstations from the pop-up menu. 3.Database Workstation List window. select Periodic Refresh and enter a refresh interval in seconds in the Period (secs) field.Database Workstation List window is displayed. Properties . The list results are displayed in the right pane of the Job Scheduling Console. ¶ Click OK to save the list and close the window. A new button is created for the list in the tree view of the Job Scheduling Console. 2. Enter a name for the list in the Name field. 5. You can also use wildcards or leave the field blank to obtain an unfiltered list. To have the list results refreshed automatically. Alternatively. select Periodic Refresh and enter a refresh interval in seconds in the Period (secs) field. If you want the list results refreshed automatically. 5. Creating a List of Workstations To create a list of workstations: 1. To filter the list results. enter a job name in the Job Name field and a workstation name in the Workstation Name field. The list results are displayed in the right pane of the Job Scheduling Console. A new button is created for the list in the tree view of the Job Scheduling Console.4. When you have finished: ¶ Click Apply to run the list without closing the window. You can also use wildcards or leave the field blank to obtain an unfiltered list. ¶ Click OK to save the list and close the window. Click Apply defaults to enter the default refresh settings from the scheduler properties. enter a workstation name in the Workstation Name field. 6. ¶ Click Cancel to close the window without running or saving the list. expand the branch and select a group button. 6. When you have finished: ¶ Click Apply to run the list without closing the window.1 . Click Apply defaults to enter the default periodic refresh settings. The Properties . 192 Version 8. Figure 98.

Click Apply defaults to enter the default periodic refresh settings.Workstation Class List window is displayed. select Periodic Refresh and enter a refresh interval in seconds in the Period (secs) field. To create the list in the scheduler branch.Database Resource List window is displayed. enter a resource name in the Resource Name field and a workstation name in the Workstation Name field. Managing Database Lists ¶ Click Cancel to close the window without running or saving the list. 4. right-click the scheduler engine button or group button and select Create Database List then Resource from the pop-up menu. Select an engine in the tree. Alternatively. You can also use wildcards or leave the field blank to obtain an unfiltered list. 5. 6. expand the branch and select a group button. ¶ Click OK to save the list and close the window. Figure 99. The Properties . A new button is created for the list in the tree view of the Job Scheduling Console. To have the list results refreshed automatically. Select an engine in the tree. 2. Creating a List of Workstation Classes To create a list of workstation classes: 1. Enter a name for the list in the Name field. To create the list in the scheduler branch. Click the List Resources in Database button on the toolbar. expand the branch and select a group button. Properties .16. To filter the list results. Right-click the scheduler engine button or group button and select Create Database List then Workstation Class from the pop-up menu. The list results are displayed in the right pane of the Job Scheduling Console.Database Resource List window. When you have finished: ¶ Click Apply to run the list without closing the window. Tivoli Job Scheduling Console User’s Guide 193 . 2. Creating a List of Resources To create a list of resources: 1. The Properties . ¶ Click Cancel to close the window without running or saving the list. 3.

¶ Click Cancel to close the window without running or saving the list. Figure 101. enter a workstation class name in the Workstation Class Name field. The list results are displayed in the right pane of the Job Scheduling Console. Select an engine in the tree. select Periodic Refresh and enter a refresh interval in seconds in the Period (secs) field. Properties .1 . 5. ¶ Click OK to save the list and close the window. To have the list results refreshed automatically. Enter a name for the list in the Name field. 194 Version 8. The Properties .Prompt List window is displayed. Right-click the scheduler engine button or group button and select Create Database List then Prompt from the pop-up menu. To filter the list results. To have the list results refreshed automatically. 5. 4. Click Apply defaults to enter the default periodic refresh settings. You can also use wildcards or leave the field blank to obtain an unfiltered list. Properties . 6.Figure 100. Enter a name for the list in the Name field. select Periodic Refresh and enter a refresh interval in seconds in the Period (secs) field. To create the list in the scheduler branch. A new button is created for the list in the tree view of the Job Scheduling Console. 2.Prompt List Window 3.Workstation Class List Window 3. expand the branch and select a group button. Creating a List of Prompts To create a list of prompts: 1. Click Apply defaults to enter the default periodic refresh settings. 4. When you have finished: ¶ Click Apply to run the list without closing the window.

Creating a List of NT Users To create a list of users: 1. 6. When you have finished: ¶ Click Apply to run the list without closing the window. 2. Creating a List of Parameters To create a list of parameters: 1.Parameter List window is displayed. select Periodic Refresh and enter a refresh interval in seconds in the Period (secs) field. When you have finished: ¶ Click Apply to run the list without closing the window. Managing Database Lists 6. Figure 102. To create the list in the scheduler branch. 5. The list results are displayed in the right pane of the Job Scheduling Console. Tivoli Job Scheduling Console User’s Guide 195 . To filter the list results. A new button is created for the list in the tree view of the Job Scheduling Console. enter a parameter name in the Parameter Name field. ¶ Click OK to save the list and close the window. ¶ Click OK to save the list and close the window. The Properties . Click Apply defaults to enter the default periodic refresh settings. enter a prompt name in the Prompt Name field. A new button is created for the list in the tree view of the Job Scheduling Console.Parameter List Window 3. expand the branch and select a group button. The list results are displayed in the right pane of the Job Scheduling Console. ¶ Click Cancel buttonto close the window without running or saving the list. Enter a name for the list in the Name field.16. Properties . You can also use wildcards or leave the field blank to obtain an unfiltered list. To filter the list results. To have the list results refreshed automatically. Select an engine in the tree. You can also use wildcards or leave the field blank to obtain an unfiltered list. 4. Right-click the scheduler engine button or group button and select Create Database List then Parameter from the pop-up menu. ¶ Click Cancel to close the window without running or saving the list. Select an engine in the tree.

Creating a List of Domains To create a list of domains: 1. expand the branch and select a group button. select Periodic Refresh and enter a refresh interval in seconds in the Period (secs) field. Select an engine in the tree. 196 Version 8. The list results are displayed in the right pane of the Job Scheduling Console. expand the branch and select a group button. To filter the list results. 4. enter a domain or user name in the NT Domain\User Name field. The Properties . Enter a name for the list in the Name field.NT User List window is displayed. ¶ Click OK to save the list and close the window. 6. Properties . The Properties .NT User List Window 3.To create the list in the scheduler branch. You can also use wildcards or leave the field blank to obtain an unfiltered list. Right-click the scheduler engine button or group button and select Create Database List then Domain from the pop-up menu.Domain List window is displayed. To create the list in the scheduler branch. 2. 5. Right-click the scheduler engine button or group button and select Create Database List then NT User from the pop-up menu.1 . A new button is created for the list in the tree view of the Job Scheduling Console. Figure 103. When you have finished: ¶ Click Apply to run the list without closing the window. 2. To have the list results refreshed automatically. Click Apply defaults to enter the default periodic refresh settings. ¶ Click Cancel to close the window without running or saving the list.

6. To have the list results refreshed automatically. Figure 105. 2. Right-click the scheduler engine button or group button and select Create Database List then Calendar from the pop-up menu. The Properties .Domain List Window 3. Enter a name for the list in the Name field. Click Apply defaults to enter the default periodic refresh settings. 4. A new button is created for the list in the tree view of the Job Scheduling Console. Managing Database Lists Figure 104. select Periodic Refresh and enter a refresh interval in seconds in the Period (secs) field. expand the branch and select a group button. Tivoli Job Scheduling Console User’s Guide 197 .Calendar List Window 3. enter a domain name in the Domain Name field. To have the list results refreshed automatically.Calendar List window is displayed. To filter the list results.16. You can also use wildcards or leave the field blank to obtain an unfiltered list. Select an engine in the tree. Properties . Creating a List of Calendars To create a list of calendars: 1. Properties . select Periodic Refresh and enter a refresh interval in seconds in the Period (secs) field. The list results are displayed in the right pane of the Job Scheduling Console. ¶ Click Cancel to close the window without running or saving the list. To create the list in the scheduler branch. 4. Enter a name for the list in the Name field. 5. ¶ Click OK to save the list and close the window. When you have finished: ¶ Click Apply to run the list without closing the window.

You can detach multiple lists to view several objects simultaneously. Figure 106. ¶ Click Cancel to close the window without running or saving the list. it is maintained and refreshed according to the refresh options specified. click the corresponding object in the Job Scheduling view. Right-click the list you want to run and select Load List from the pop-up menu. 2. Detaching a List Display Detaching a list frees the right-pane of the Job Scheduling Console to display other objects. double-click an engine. you can select an engine in the tree and double-click the list you want to run in the right-hand pane of the Job Scheduling view. When you have finished: ¶ Click Apply to run the list without closing the window. To detach a database list display: 1. You can also use wildcards or leave the field blank to obtain an unfiltered list. To filter the list results. To view the list. However. The newest list is displayed above the preceding ones. as long as a list is kept open.5.1 . In the tree of the Job Scheduling view. A new button is created for the list in the tree view of the Job Scheduling Console. Open a list and wait for the results to be displayed. 6. The list tool searches the database or plan and displays the objects it finds in the right-hand pane of the Job Scheduling view. 198 Version 8. The list results are displayed in the right pane of the Job Scheduling Console. Working with Lists Displaying a List To display a list: 1. You can display several lists in sequence. enter a calendar name in the Calendar Name field. Displaying a List Note: Alternatively. ¶ Click OK to save the list and close the window. Click Apply defaults to enter the default periodic refresh settings.

4. 3.16. The availability of a search tool is indicated by an ellipsis located next to the field where you enter an object name. 2. This is so that you can run other lists or perform other tasks. Managing Database Lists 2. ¶ Click OK to save the changes and to close the window. You can have a maximum number of seven detached views open at the same time. To prevent your system from overloading. The list window is displayed separately from the Job Scheduling view. double-click an engine. ¶ Click Cancel to close the window without running or saving the changes. Deleting a List To delete a list: 1. Click the Delete button in the toolbar or right-click on the list button and select Delete from the pop-up menu. The right-hand pane of the console is not disabled. When you have finished: ¶ Click Apply to run the list without closing the window. The list results are displayed in the right pane of the Job Scheduling Console. Click Yes to delete the list or click Cancel to cancel the delete operation. Make your changes. 2. the Workstation field provides a search tool. In the tree of the Job Scheduling view. 2. Tivoli Job Scheduling Console User’s Guide 199 . 3. Notes: 1. To place the list back in the right-hand pane. either close the detached window or right-click the list in the tree view and select Attach View from the pop-up menu. do not have frequent refreshes of many detached views open at the same time.Resource in Database window. Select a list button. 3. In the following example of the Properties . The properties window of the list is displayed. Modifying a Database List To modify the properties of a list: 1. Right-click the list in the tree view and select Detach View from the pop-up menu. 3. A confirmation message is displayed. Right-click the list you want to modify and select Properties from the pop-up menu. Finding Objects Search tools are provided in the Job Scheduling Console to help you find objects in the database.

2. ¶ Click Cancel to close the Find window without inserting an object name. Find Workstation Window To use the Find window: 1. 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 Start. the Find Workstation window is displayed. Type search arguments in the available fields.Figure 107. The results of the search are listed in the lower part of the Find window. 3. Figure 108.Resource in Database Window When you click the ellipsis. 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. Properties . You can also use wildcards or leave the field blank to obtain an unfiltered list.1 . 200 Version 8.

This opens the Select a Task Type window.. Select an engine in the tree. Select a Task Type Window 3. To create a new job: 1. The job is an executable file on a UNIX computer. The job is an executable file on a Windows NT computer. New Job Definition Task Types This task type . The job is associated with an Extended Agent workstation.. Table 71 describes the task types: Table 71. It usually includes all necessary computer programs..17 Managing Jobs 17. Figure 109.Job Definition window. Creating a Job Definition You create jobs in the database using the Properties . UNIX Script UNIX Command NT Script NT Command Workstation Class Script Workstation Class Command Extended Agent MPE Job File Specifies that .. The job is a UNIX command. The job is an executable file on an MPE computer. Managing Jobs A job is a unit of work that is part of a job stream processed at a workstation. and instructions to the operating system. Click the New Job Definition button on the toolbar or right-click the engine button and select New Job Definition from the pop-up menu. Once a task type is defined for a job it cannot be changed. The job is a command that runs on a workstation class. In the Select a task type window. 2. files. Tivoli Job Scheduling Console User’s Guide 201 . The job is an executable file that runs on a workstation class. select a task type from the drop-down list. The job is a Windows NT command. links.

The name must start with a letter.Table 71.Job Definition General page is displayed.Job Definition General Page Use the information in Table 72 to complete the text boxes and select options. The name of the workstation or workstation class on which the job runs. click Cancel to cancel the operation. and can contain alphanumeric characters. it can contain up to eight characters. Alternatively. For expanded databases. For non-expanded databases. You can type a name directly or you can click Find and select a workstation or workstation class from a list. dashes. For information about using the Find button.1 .. The job is streamed by an MPE user and is managed by the Workload Scheduler.. 4. The SAP task type is only displayed if the Extended Agent for SAP has been installed... New Job Definition Task Types (continued) This task type . Properties . Workstation Description 202 Version 8. The job is an SAP job that runs on a Workload Scheduler Extended Agent for SAP. and underscores.. The Properties . Name Enter this information . it can contain up to 40 characters.. Properties . MPE User Job SAP Specifies that . The name of the job. Click OK to proceed.. it must match the workstation class of any job stream in which the job will be included. Table 72. refer to “Finding Objects” on page 199.Job Definition General Information In this area . General Page Figure 110. If you specify a workstation class.. The description can contain up to 64 characters. A description of the job.

For Windows NT jobs only. Specify a user that can log on to the workstation on which the job runs. 17. For more information. 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. v Click OK or double-click the parameter in the list to insert the parameter name in the Login text box of the Properties . the user must also be defined in the database.. If the name contains special characters it must be enclosed in quotes (“”).Job Definition window and keep the Find Parameters window open. A parameter can be used for all or part of the text box and multiple parameters are permitted.Table 72.. The name can contain up to 47 characters. Select this to indicate that the job runs interactively on the Windows NT desktop. For Windows NT jobs. The name can contain wildcard characters. ¶ 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 . ¶ Enter a parameter name in the Find text box.Job Definition General Information (continued) In this area . see “Managing Users” on page 263. The Find Parameters window is displayed. Is Interactive Login Enter this information . Properties . Managing Jobs Tivoli Job Scheduling Console User’s Guide 203 ... The user name under which the job runs. v Click Cancel to close the Find Parameters window without inserting a parameter name.Job Definition window and close the Find Parameters window. ¶ Click Start to display a list of parameter names.

rerun the job. enclosed in quotes.Table 72. ¶ The recovery job’s workstation must be in the same domain as the parent job’s workstation. If job1 is successful.. ¶ job2 is dependent on job1 and will not start until job1 is complete. ¶ If selected for job1.. run job2. repeat above. Job Stream Recovery Options Prompt / Job Recovery prompt: No Recovery job: No Stop Intervention is required. The recovery options for the job: Action Specifies the action to be taken if the job ends abnormally (abends). Recovery jobs are run only once for each abended instance of the parent job. The text can contain up to 64 characters. Workstation Specify the name of the workstation on which the recovery job runs. Properties . The name is entered automatically when you select a recovery job. Job Specify the name of a recovery job to run if the parent job abends. Continue Run job2. Continue If the job abends.1 . Rerun Rerun job1. The default is Stop. Not all jobs are eligible to have recovery jobs run on a different workstation.Job Definition General Information (continued) In this area . issue scheduler prompt. the recovery job is jobr. to be displayed if the job abends. Table 73. Follow these guidelines: ¶ If either workstation is an extended agent. Recovery Options Enter this information . The recovery prompt is a local prompt and is responded to using the Job Scheduling Console. Prompt Specify the text of a recovery prompt. it must run in Full Status mode. Stop If the job abends. continue with the next job. 204 Version 8. refer to “Finding Objects” on page 199. If reply is yes. it must be hosted by a domain manager or a fault-tolerant agent that runs in Full Status mode. ¶ If the recovery job’s workstation is a fault-tolerant agent.. do not continue with the next job. Click the Find button and select a job from a list.. For information about using the Find button. The table is based on the following criteria from a job stream called sked1: ¶ Job stream sked1 has two jobs. job1 and job2. Select one of the following. Table 73 on page 204 summarizes all possible combinations of recovery options and actions. If job1 abends. Rerun If the job abends.

intervention is required. If you select the Rerun option without supplying a recovery prompt. repeat above. If jobr abends. run job2. run job2.Table 73. run job2. If reply is yes. If jobr is successful. The continue recovery option overrides the abend state. Managing Jobs Recovery prompt: Yes Recovery job: Yes Issue recovery prompt. Notes: 1. Tivoli Job Scheduling Console User’s Guide 205 . issue scheduler prompt. If reply is yes. To reference a recovery job in Conman. Rerun Issue recovery prompt. If reply is yes. run job2. Issue recovery prompt. Workload Scheduler generates its own prompt. you must use the name of the original job (job1 in the scenario above. Select Task in the left pane of the Properties . 17. 2. ″Intervention is required″ means that job2 is not released from its dependency on job1. If reply is yes. Run job2. intervention is required. Intervention is required. If job1 is successful. Job Stream Recovery Options (continued) Prompt / Job Recovery prompt: Yes Recovery job: No Stop Issue recovery prompt. run job2. Recovery jobs are run only one per abend. run jobr. If it is successful. If jobr abends. run jobr. rerun job1. Issue recovery prompt. intervention is required.Job Definition window. Continue Issue recovery prompt. If jobr is successful. Run jobr. Recovery prompt: No Recovery job: Yes Run jobr. 3. This displays the Task page. Run job2. This will prevent the schedule from being carried forward to the next day. rerun job1. If it abends. intervention is required. run jobr. If job1 abends. repeat above. Run jobr. and therefore must be released by the operator. If reply is yes. If it is successful. repeat above. If job1 is successful. If job1 abends. rerun job1. If job1 abends. If it abends. which may cause the schedule containing the abended job to be marked as successful. not jobr). 4. run job2. If reply is yes. If job1 is successful.

or Workstation Class Script Complete the Script field as follows: Specify the name of the file the job runs. For Windows NT jobs. NT Script. Universal Naming Convention (UNC) names are permitted. For non-expanded databases.. Do not specify files on mapped drives. UNIX Script. For expanded databases. enter the name in another file that does not have spaces in its name and use the second file’s name in this field. NT Script.Job Definition: Task Window. the field can contain up to 255 characters. Enter the file name and any options and arguments. To complete the fields and select options on this page: Table 74. 206 207 207 207 208 UNIX Command. do the following: 206 Version 8..Task Page Figure 111. it can contain up to 4095 characters. Properties . To include a parameter in the Script field. The Task page is different for each task type. or Workstation Class Command 207 UNIX Script. Task Types For this task type . or Workstation Class Script MPE Job File MPE User Job Extended Agent SAP Job Go to page . If the file name contains spaces. include the file extensions... NT Command.1 .

¶ This displays the Find Parameters window.JCL. it can contain up to 4095 characters. For non-expanded databases. ¶ Click Start to display a list of parameter names. v Click Cancel to close the Find Parameters window without inserting a parameter name. The name can contain wildcard characters. or Workstation Class Command In the Command field. MPE Job File Complete the Job File field by specifying the name of the MPE file the job runs. ¶ Enter a parameter name in the Find field. For example. specify the name of the command the job runs. click the override userjob checkbox and enter the name or wildcard. JFILE4. ¶ 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 . $USERJOB=UJOB1 or $USERJOB=UJ@. 17. A parameter can be used for all or part of the field and multiple parameters are permitted.¶ Place the cursor in the Script field where you want to insert the parameter and click the Add Parameter button. To include a parameter in the Command field. the field can contain up to 255 characters. ¶ Click Start to display a list of parameter names.Job Definition window and close the Find Parameters window. v Click OK or double-click the parameter in the list to insert the parameter name in the Script field of the Properties . A parameter can be used for all or part of the field and multiple parameters are permitted. v Click Cancel to close the Find Parameters window without inserting a parameter name.Job Definition window and close the Find Parameters window. Enter the command name and any options and arguments. MPE User Job Complete the User Job field by specifying the name from the JOB card of the MPE job. Managing Jobs UNIX Command.Job Definition window and keep the Find Parameters window open. 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. NT Command. If the scheduler job name does not match the MPE job card name or you want to use skeleton jobs. do the following: ¶ Place the cursor in the Command field where you want to insert the parameter and click Add Parameter . The name can contain wildcard characters.CORP. Extended Agent Refer to the specific user guide for the Extended Agent you are working with for more information. For example. For expanded databases. Tivoli Job Scheduling Console User’s Guide 207 . ¶ Enter a parameter name in the Find field. Commands are run directly and the jobmanrc standard configuration script is not run. ¶ 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 .

. 4. The name of the job.Job Definition window and save the new job in the database. expand the scheduler engine button.SAP Job Refer to the Tivoli Workload Scheduler SAP/R3 Extended Agent User Guide for information about defining the task. The list results are displayed in the right pane of the Job Scheduling Console.. 2. When you have finished: ¶ Click OK to close the Properties . Job Definition List Window Table 75 describes the columns in the window. Select the job list button. Displaying a List of Job Definitions To display a list of jobs in the database: 1. Name Workstation Specifies . 3. Table 75. Expand the branches until you see the button for the job list you want to run. The name of the workstation on which the job runs.. In the tree view of the Job Scheduling Console. 208 Version 8.Job Definition window without saving the job in the database. Click the Load List button on the toolbar or right-click on the job list button and select Load List from the pop-up menu.. Job Definition List Window This column . ¶ Click Cancel to close the Properties . Figure 112.1 . See “Creating a List of Jobs” on page 191 for information about creating job lists.

The duration in minutes of the last run of the job.Job Definition window. 2. 17. Workstation Class Script Specifies that the job is an executable file on a specific class of workstations. SAP Job Specifies that the job is an SAP job. Run a list of jobs that contains the job you want to display. Workstation Class Command Specifies that the job is a command on a specific class of workstations. The name of the user who created the job in the database.. NT Command Specifies that the job is a Windows NT command. See “Displaying a List of Job Definitions” on page 208 for more information. double-click the job you want to display or right-click on the job and select Properties from the pop-up menu.. UNIX Command Specifies that the job is a UNIX command. For information about the Properties . You must install the Workload Scheduler Extended Agent for SAP software to use SAP jobs.Job Definition window. MPE User Job Specifies that the job is streamed by an MPE user and is managed by Workload Scheduler.Table 75. In the list results. Managing Jobs Creator Last Runtime Displaying a Job Definition To display a job in the database: 1.. see “Creating a Job Definition” on page 201. MPE Job File Specifies that the job is an executable file on an MPE computer.. Refer to the specific user guide for the Extended Agent you are using for more information. This displays the job in the Properties . 3.Job Definition window. Displaying Job Definition Details To display job details in the database: Tivoli Job Scheduling Console User’s Guide 209 . Extended Agent Specifies that the job is an Extended Agent job. Job Definition List Window (continued) This column . The task type of the job: UNIX Script Specifies that the job is an executable file on a UNIX computer. NT Script Specifies that the job is an executable file on a Windows NT computer. Click OK or on Cancel to close the Properties . Task Type Specifies .

. Total CpuTime Displays the total CPU time of the job. Continue. or Rerun. Figure 113. Job Information Contains this information . Description Displays the description of the job. 2. Recovery Information Job Run Summary 210 Version 8.1. Successful Runs Displays the total number of successful runs of the job. Aborted Runs Displays the total number of abended runs of the job. Job Displays the name of the job’s recovery job. Job’s logon information: Logon Displays the user logon for the job. Details for Job Window This area .. Total Elapsed Time Displays the total elapsed time of the job. Script File Displays the name of the job’s script file. Prompt Displays the job’s recovery prompt. Normal Elapsed Time Displays the elapsed time for previous runs of the job. right-click the job you want to display and select Job Details from the pop-up menu.. Details for Job Window Table 76 describes the contents of this window. In the list results. See “Displaying a List of Job Definitions” on page 208 for more information. It can be Stop. This displays the Details for Job window. Table 76.1 .. Run a list of jobs that contains the job you want to display. Information about the job from the most recent production plan: Total Runs Displays the total number of times the job has run. Job’s recovery information: Option Displays the job’s recovery option.

The Properties . double-click the job you want to modify or right-click on the job and choose Properties from the pop-up menu. Job’s run time history for the last run. Click OK to close the window. 3.Job Definition window is displayed. see “Creating a Job Definition” on page 201. 2. In the list results. For information about the window.. See “Displaying a List of Job Definitions” on page 208 for more information. Managing Jobs Modifying a Job Definition To modify a job: 1. When you have finished: ¶ Click OK to save the job in the database and close the window. CpuTime The the CPU time of the run. Run Time History Contains this information .. the minimum run..Job Definition Window 3.. Figure 114. Elapsed Time Displays the elapsed time of the run.Table 76. ¶ Click Cancel to close the window without saving the job in the database. Properties . Details for Job Window (continued) This area . Deleting Job Definitions To delete jobs in the database: Tivoli Job Scheduling Console User’s Guide 211 . and the maximum run: Run Date Displays the date and time of the run. Run a list of jobs that contains the job you want to modify. 17. Make your changes.

right-click the job. ¶ To delete multiple jobs in a range. 3. click each job. Select Delete from the pop-up menu. then right-click one of the selected jobs. 4. Run a list of jobs that contains the job you want to delete. See “Displaying a List of Job Definitions” on page 208 for more information. 2.1. ¶ To delete multiple jobs that are not in a range. A confirmation message is displayed for each job. Click OK to delete the job in the database or click Cancel to cancel the delete operation. click the first and last jobs in the range.1 . then right-click one of the selected jobs. 212 Version 8. hold down the Shift key. hold down the Ctrl key. In the list results: ¶ To delete one job.

resource dependencies. Job stream management functions are divided between three views: ¶ Graph ¶ Timeline ¶ Run Cycle Each view contains a set of menu and toolbar functions. as well as the run cycles of the job stream. Figure 115. 18. Dependencies between jobs are represented as arrows pointing to the successor jobs. Jobs and external job dependencies are represented by buttons.Job Stream window. Using the Job Stream Editor Use the Job Stream Editor to create and modify job streams in the database. file dependencies. The Job Stream Editor is used to work with the jobs and follows dependencies between the jobs.18 Managing Job Streams Job streams are created and modified using the Job Stream Editor and the Properties . Managing Job Streams Graph View The Graph view provides a graphical display of the jobs in a job stream. The Properties Job Stream window is used to specify time restrictions. and prompt dependencies at the job stream level. Job Stream Editor Graph View Tivoli Job Scheduling Console User’s Guide 213 . Use this view to add and delete jobs and specify dependencies between jobs.

Job Stream Editor Graph View Toolbar This button . Displays the Run Cycle view. Undoes the previous Delete operation... 214 Version 8. Saves the job stream in the database. Properties Save Delete Undo Delete Copy Paste Select Add Job Definition Add Dependency on External Job Add Dependency on External Job Stream Add Dependency on Internetwork Add Link Graph Timeline Run Cycle And does this . Adds a job to the job stream. Copies the selected job to the clipboard.Table 77 describes the toolbar in the Graph view of the Job Stream Editor... Deletes the selected job.. Use the borders and the arrows on the borders to adjust the sizes of the panes. The window is divided into four panes. Adds the job on the clipboard to the job stream. Table 77. Timeline View The Timeline view provides a tabular and timeline display of the time restriction properties of the job stream and its jobs. The job stream is displayed in the upper pane and its jobs are displayed in the lower pane. Adds an button to represent an external job dependency. Adds an button to represent an external job stream dependency. Displays the Graph view. Has this name .. Displays the Timeline view.1 . Adds an button to represent an internetwork dependency. Changes the mouse pointer to a selection arrow. Use this view to display and adjust time restriction properties. Displays the Job Stream Properties window. An button is added to represent the job. Use the arrows at the top of the timeline pane to move the view in one hour and one day increments. Adds a dependency between jobs in the job stream.

18. Moves the timeline display to a day offset from the schedule date of the plan (Day 0). Job Stream Editor Timeline View Toolbar This button . A dark blue bar represents the time restrictions for a job or job stream. Moves the timeline display to the start time and day offset of the job stream or its earliest job. A black segment at the end of a timeline represents the deadline time. Managing Job Streams Figure 116. Displays the Graph view. deadline. Has this name ... Displays the Job Stream Properties window. and duration times for each timeline shown in the right pane. the blue bar becomes red. Properties Save Move Job Up Move Job down Go to Day Go to First And does this . Table 78.. Graph Timeline Tivoli Job Scheduling Console User’s Guide 215 . Job Stream Editor Timeline View Table 78 describes the toolbar in the Timeline view of the Job Stream Editor. Displays the Timeline view. Saves the job stream in the database.Time intervals are shown in the right pane. or the end of a line. Double-clicking the job or job stream name opens time properties windows. The left pane lists the start. Move the job up one step in the job stream... whichever is the first to occur. based on past run times. adjusts the start and deadline times of the job stream or a job. Where the duration of the job exceeds the deadline time. Move the job down one step in the job stream. You can edit the time properties of the job or job stream from these windows. Dragging a line. A light blue bar represents the expected duration..

Job Stream Editor Run Cycle View Table 79 describes the toolbar in the Run Cycle view of the Job Stream Editor... Adds a run cycle of days marked on a monthly or yearly basis. Use the border and the arrows on the border to adjust the pane size. Job Stream Editor Timeline View Toolbar (continued) This button . Table 79. Run Cycle View The Run Cycle view shows the run cycles of the job stream in a calendar format. Has this name . Deletes the selected run cycle. The window is divided into two panes.. Use this view to add and modify the run cycles of the job stream.. Job Stream Editor Run Cycles View Toolbar This button . Saves the job stream in the database.Table 78. Run Cycle And does this ... The left pane lists the types of run cycles defined for the job stream and the associated freeday rule. Adds a run cycle of days based on a previously defined calendar.. Displays the Job Stream Properties window. Changes the mouse pointer to a selection arrow. Properties Save Select a Run Cycle Delete Simple Run-Cycle Weekly Run-Cycle Calendar Run-Cycle Graph And does this .. 216 Version 8.1 . Adds a run cycle of days selected on a weekly basis. Figure 117. The right pane displays a calendar showing included or excluded days as defined in the selected run cycle. Displays the Run Cycle view. Use the tabs above the calendar to select the Monthly or Yearly view and use the arrows above and below the calendar to change the month or year of the calendar.... Displays the Graph view.. Has this name .

This displays the Job Stream Editor and the Job Stream Properties window. Has this name . Click New Job Stream on the toolbar or right-click on the scheduler engine button and select New Job Stream from the pop-up menu. Job Stream Properties Groups This group . Tivoli Job Scheduling Console User’s Guide 217 . 2. Creating a Job Stream You create job streams in the database using the Job Stream Editor. General Time Restrictions Resources Files Prompts Is described on page .... To create a new job stream.. follow these steps: 1...Table 79. There are five groups of job stream properties: 18. Specifying Job Stream Properties Job stream properties are specified in the Job Stream Properties window of the Job Stream Editor. click the scheduler engine button. click Generalin the left pane of the Job Stream Properties window. Job Stream Editor Run Cycles View Toolbar (continued) This button . The General page is displayed. If the window is not displayed... Timeline Run Cycle And does this ... select Properties from the File menu of the Job Stream Editor. To specify job stream properties. Managing Job Streams Table 80. Displays the Run Cycle view. 218 220 222 223 224 The Job Stream Properties window opens automatically when you create a new job stream. Displays the Timeline view. In the tree view of the Job Scheduling Console.

. However. Properties . For expanded databases. The name of the job stream.1 .. If you specify a workstation class. it can contain up to 16 characters. it must match the workstation class of any jobs or resources used in the job stream.Job Stream Properties General Page Use the information in Table 81 to complete the text boxes and select options. You can type a name directly or you can click the Find button and select a workstation or workstation class from a list. A description of the job stream.. it can contain up to eight characters. The name must start with a letter. refer to “Finding Objects” on page 199. Name Enter this information . you can use the create another command to save the job stream with another name. Table 81.. For information about using the Find button. Job Stream Properties General Information In this area . The name of a job stream cannot be changed once is has been saved. and can contain alphanumeric characters and dashes. Workstation Description 218 Version 8. For non-expanded databases. The name of the workstation or workstation class on which the job stream is launched.General Page Figure 118.

overriding the workstation job limit.Table 81. but not overriding the job stream job limit or the workstation job fence. Managing Job Streams Tivoli Job Scheduling Console User’s Guide 219 . Contains Monitored Job This read-only item indicates whether any of the jobs in this job stream will be monitored by Tivoli Business Systems Manager (TBSM) when they run.. You can control the number of days a job stream is carried forward by specifying a deadline time (UNTIL keyword) plus x number of days. The number of jobs that can be running at the same time in the schedule. Possible values are 0 through 1024. The priority of the job stream. no jobs are launched in the job stream. Value is Yes if at least one of the jobs in the job stream have the Is Monitored Job check box selected in their Properties window. For more information. the On request flag is ignored and the job stream will run according to the run cycle. Job Stream Properties General Information (continued) In this area . Priority Enter this information . these job stream must be submitted into the plan by the user or specifically requested when schedulr is run. can be carried forward again. If you select On Request and specify run cycles for the job stream.. Normally. and therefore. A priority value of zero prevents the job stream from launching. Job streams that are carried forward retain the carryforward option. where 101 is the highest priority. refer to the Reference Guide. High Sets the priority to 100. must be monitored by Tivoli Business Systems Manager (TBSM) when it runs. Go Sets the priority to 101.. Select a job limit value from the drop-down list. If you specify a job limit of 0. and every job that it contains. Select a priority value from the drop-down list or click of the following buttons: Hold Sets the priority to 0. In the case of High and Go. Check any of the following options that apply: On Request Check this to specify that the job stream is selected for running by request. Is Monitored Job Stream Check this to specify that the entire job stream. High and Go jobs are launched as soon as their dependencies are satisfied. Carry Forward Check this to specify that the job stream is eligible to be carried forward to the next day production plan if it is not completed before the end of the current day production day. Possible priority values are 0 through 101. Limit Options 18.. all jobs in the job stream are given the priority.

. When you have finished. such as holidays and closing days. 220 Version 8. Specify the name of the calendar that lists the non-workdays for your company. When you select this button. Properties . Job Stream Properties General Information (continued) In this area . Click the ellipsis to open the Find Calendars window if you need to search amongst existing calendars. all the remaining items in this group become unavailable. where you tell Workload Scheduler how to handle a job stream if the schedule falls on a freeday. See “Managing Calendars” on page 266 for details on creating freeday calendars. ¶ Click Specify Calendar to instruct the scheduler to use a different freedays calendar than the default and enter a calendar in the Calendar Name field... Do one of the following: ¶ Click Use Default to instruct the scheduler to use the default freedays calendar (usually named Holidays) that is displayed in the Calendar Name field. It is associated with the Free day rule. The Time Restrictions page is displayed. Time Restrictions Page Figure 119. Select the Saturday and/or Sunday check boxes if you want these days to be counted as freedays in the calendar you just specified.. The calendar of freedays is used during the definition of the run cycles for the job stream.1 .Table 81. Free Days Calendar Enter this information . click Time Restrictions in the left pane of the Job Stream Properties window.Job Stream Time Restrictions Page. when you may not want the job stream to run.

11:30 am or 4:25 pm. At Specify a start time in the following format: hh:mm am|pm For example. For information about the time zone feature. Job Stream Time Restrictions Information In this area . Make your selections as follows: Specify time Specify this option to enable the entry of a start time. all time values specified in the Time Restrictions properties window are in the time zone of the workstation on which the job stream is launched. Make your selections as follows: Specify time Specify this option to enable the entry of a deadline time. Time Zone The time zone in which the job stream runs. Select a time zone from the drop-down list. Delay for Specify the number of days to offset the deadline time from the day the job stream is selected for inclusion in the production plan. Note: The Deadline time must be later than the Start Time.. Managing Job Streams hh:mm am|pm For example. Note: Time Restrictions can also be set in the Timeline view of the Job Stream Editor. Deadline The latest time the job stream will be launched. At Specify a deadline time in the following format: 18. All time values specified are in this time zone. Delay for Specify the number of days to offset the start time from the day the job stream is selected for inclusion in the production plan. click Resources in the left pane of the Job Stream Properties window. If a time zone is not specified for the job stream.. Start Enter this information .. Tivoli Job Scheduling Console User’s Guide 221 . The job stream will not be launched before this time. 11:30 am or 4:25 pm. When you have finished.Use the information in Table 82 to complete the text boxes and select options. The job stream will not be launched after this time. The Resources page is displayed. Table 82.. see “Enabling Time Zones in the Workload Scheduler” on page 385. See “Specifying Time Restrictions in the Timeline View” on page 244 for more information. The earliest time the job stream will be launched.

to allocate 1024 units of a resource to a job stream or job you would need to create 32 entries for the resource with 32 units each.1 . Double-click in the text box in the Resources column and click Find to locate and insert a resource name. When you have finished. The default is one. To remove a resource dependency for the job stream. For example. This creates a new row in the list of resource dependencies. Properties . 222 Version 8. Resources can be defined with up to 1024 units. see “Finding Objects” on page 199.Resources Page Figure 120. select the resource row in the list and click Delete from Table. 3. Click the Add Row button . click Files in the left pane of the Job Stream Properties window. but they can only be allocated in increments of 32. For information about using the Find window. The Files page is displayed. Double-click in the text box in the Quantity column and enter the number of resource units required by the job stream.Job Stream Resources Page To add a resource dependency for the job stream: 1. 2.

-w %p True if the file exists and is writable. On both UNIX and Windows NT. Alternatively. 2. Properties . This creates a new row in the list of file dependencies. On Windows NT. only the following qualifiers are valid: -d %p True if the file exists and is a directory. see “Finding Objects” on page 199. Tivoli Job Scheduling Console User’s Guide 223 . -f %p True if the file exists and is a regular file. Managing Job Streams Figure 121. Notes: a. Double-click in the text box in the Filename column and type a file name. click Find to locate and insert a file name. Double-click in the text box in the Qualifiers column and enter the test conditions for the file dependency. the expression %p inserts the file name.Files Page 18. On UNIX. Double-click in the text box in the Workstation column and click Find to locate and insert the name of a workstation or workstation class. 4. -s %p True if the file exists and it’s size is greater than zero. the valid qualifiers are the same as UNIX test command conditions.Job Stream Files Page To add a file dependency for the job stream: 1. For more information. -e %p True if the file exists. refer to your UNIX system documentation. For information about using the Find window. 3. Click the Add Row button . -r %p True if the file exists and is readable.

To add a prompt dependency for the job stream: 1. Click the Add Row button (+). select Predefined Prompt from the drop-down list. If the string begins with a colon (:). Entering notempty is the same as entering -s %p. For information about using the Find window. place its name between carets (^). For a predefined prompt dependency. If no qualifier is specified. The default behavior of a prompt is to display a message and wait for a reply. the message is not displayed but it requires a reply. 2. see “Finding Objects” on page 199.b. the message is displayed but no reply is necessary. select the file row in the list and click the Delete from Table button. click Prompts in the left pane of the Job Stream Properties window. 3. For a predefined prompt. the default is -f %p. Prompts Page Figure 122. Properties . You can include backslash n (\n) within the text for new lines.Job Stream Prompts Window For an ad hoc prompt dependency. When you have finished. 224 Version 8. This creates a new row in the list of prompt dependencies. You can include one or more scheduler parameters as part or all of the text string. To use a parameter. double-click in the text box in the Text column and type in the text of the prompt. To remove a file dependency for the job stream. select Ad Hoc Prompt from the drop-down list. The Prompts page is displayed.1 . double-click in the text box in the Name column and click Find to locate and insert the name of a prompt. If the string begins with an exclamation mark (!). For an ad hoc prompt.

¶ Click Cancel to ignore the properties you have selected and close the Job Stream Properties window. These external dependencies are also called predecessors. External Dependencies Menu Tivoli Job Scheduling Console User’s Guide 225 . and jobs in other Workload Scheduler networks (internetwork jobs). open the job stream in the Job Stream Editor and select External Dependencies from the File menu. 18. When you have finished: ¶ Click OK to keep the properties you have selected and close the Job Stream Properties window. To add external dependencies for a job stream. you can add: ¶ External job stream dependencies ¶ Internetwork dependencies ¶ External job dependencies Figure 124. select the prompt row in the list and click Delete from Table (X).To remove a prompt dependency for the job stream. jobs in other job streams. The Job Stream External Dependencies window is displayed. Adding External Dependencies for a Job Stream Job streams can be dependent on the successful running of other job streams. Job Stream External Dependencies Window By clicking on the drop-down menu. Managing Job Streams Figure 123.

3. Adding an Internetwork Dependency To add an internetwork dependency: 1. Click the Add Row button (+)..job. Double-click in the Job Stream Name column of the new row. Click the Add Row button. Double-click in the Dependency column of the new row and enter either a freeform dependency. Internetwork dependencies require that a network agent is configured to communicate with the external scheduler network. Click the Find (. or the job or job stream predecessor in the form workstation#jobstream. 5. Select External Job from the drop-down menu at the top of the window.) button in the Job Stream Name column and use the Find Job Stream window to select a job stream. For information about using the Find window. 3. see “Finding Objects” on page 199.) button in the Job Name column and use the Find Job window to select a job.1 ... Adding an External Job Dependency To add an external job dependency: 1. When you have finished: ¶ Click OK to add the dependency and close the window ¶ Click Cancel to close the window without adding the dependency. Select Internetwork from the drop-down menu at the top of the window. Select External Job Stream from the drop-down menu at the top of the window. refer to the Tivoli Workload Scheduler: Reference Guide. 4. 226 Version 8. When you have finished: ¶ Click OK to add the dependency and close the window ¶ Click Cancel to close the window without adding the dependency. see “Finding Objects” on page 199. 2. When you have finished: ¶ Click OK to add the dependency and close the window ¶ Click Cancel to close the window without adding the dependency.Adding an External Job Stream Dependency To add an external job stream dependency: 1. Click the Find (. 2..) button in the Network Agent column and use the Find Workstation window to select the name of the network agent. 4. Double-click in the Network Agent column of the new row. Click the Add Row button (+). For information about configuring a network agent. Double-click in the Job Name column of the new row. For information about using the Find window.. Click the Find (.. 3. 4. 2.

Job window is displayed. or External Job from the drop-down menu. Managing Job Streams Specifying Job Properties The Properties . When you have completed the job properties. There are five pages of job properties in the Properties . To open the Graph view. Select External Job Stream. To add a job to a job stream: 1. and jobs in other Workload Scheduler networks (internetwork jobs). 3. Move the mouse pointer to the position you want to place the new job in the Graph view and left-click. 4. This displays the Job Stream External Dependencies window. You add jobs in a job stream using the Graph view of the Job Stream Editor. right-click a job in the Graph view of the Job Stream Editor and select Properties from the pop-up menu. right-click a job stream and select Open from the pop-up menu. These external dependencies are also called predecessors. Jobs are scheduled for running by adding them to job streams.Deleting External Dependencies from a Job Stream Job streams can be dependent on the successful running of other job streams. jobs in other job streams. click the Add Job Definition button in the toolbar.Job window opens automatically when you add a new job to a job stream. the Properties . 3. When you have finished: ¶ Click OK to delete the dependency and close the window ¶ Click Cancel to close the window without deleting the dependency. 2. To delete external dependencies for a job stream: 1.Job General page is displayed first. The Properties . Open the job stream in the Job Stream Editor. a new job button is added in the Graph view. Select External Dependencies from the File menu. Tivoli Job Scheduling Console User’s Guide 227 . See “Graph View” on page 213 for more information. If the window is not displayed. 2. Adding a Job to a Job Stream A job definition is a description of work to be performed on a workstation. Internetwork. In the Graph view. 18. Click the row of the dependency in the list you want to delete and click on the Delete Row button (×).Job window: ¶ General ¶ Time Restrictions ¶ Resources ¶ Files ¶ Prompts By default.

. The Restrictions page is displayed. When a job with requires confirmation enabled completes. the task type for the job is unknown and must be specified before you can save the job again.1 . Priority Description Requires Confirmation Is Monitored Job Select Time Restrictions in the left pane of the Properties . If this workstation is deleted. Mark this check box to specify that the running of this job must be monitored by Tivoli Business Systems Manager. where 101 is the highest priority.Job window. Properties . The workstation this job is defined to run on. Name Workstation Name Enter this information . Properties . Go Sets the priority to 101. A description of the job. Select this box to indicate that job completion must be confirmed by the operator. Possible priority values are 0 through 101.... it remains in the internal status PEND until confirmation is received. 228 Version 8. High Sets the priority to 100. The priority of the job.General Page Figure 125. If confirmation is received before the job completes. Table 83.Job General Page Use the information in Table 83 to complete the text boxes and select options. its internal status is either SUCCP or ABENDP and other job and job stream successors are not released. See “Finding Objects” on page 199 for more information. A priority value of zero prevents the job from launching. Click the Find button to choose the job.Job General Information In this area . Select a priority value from the drop-down list or click of the following buttons: Hold Sets the priority to zero. The name of the job.

all time values specified in the Properties .Job Time Restrictions Page Use the information in Table 84 to complete the text boxes and select options. For information about the time zone feature. Delay for Enter the number of days to offset the deadline time from the day the job is selected for inclusion in the production plan. see “Enabling Time Zones in the Workload Scheduler” on page 385.Job window are in this time zone.Job Time Restrictions page are in the time zone of the workstation on which the job is launched. All time values specified in the Time Restrictions view of the Properties . At Enter a start time in the following format: hh:mm am|pm For example. Deadline Specifies the latest time the job will be launched.Time Restrictions Page Figure 126.. Make your selections as follows: Specify time Select this option to enable the entry of a deadline time. The job will not be launched before this time. Properties .Job Time Restrictions Information 18. Select a time zone from the drop-down list. Start time Enter this information . Make your selections as follows: Specify time Select this option to enable the entry of a start time. Managing Job Streams In this area . The earliest time the job will be launched.. Tivoli Job Scheduling Console User’s Guide 229 . 11:30 am or 4:25 pm... Properties . 11:30 am or 4:25 pm. The job will not be launched after this time. Note: The Deadline time must be later than the Start Time. Delay for Enter the number of days to offset the start time from the day the job is selected for inclusion in the production plan. Time Zone The time zone in which the job runs. If a time zone is not specified for the job. Table 84. At Enter a deadline time in the following format: hh:mm am|pm For example.

Job window. Duration Note: Time Restrictions can also be set in the Job Stream Editor Timeline view. For more information. The estimated duration of the job if the job has run before..Job Time Restrictions Information (continued) In this area .. Repeat Range Enter this information . the repetition rate is reinstalled. Normal Elapsed Time Displays the average time this job requires to run.. the repetitions continue following the optional recovery action. If a repetitive job abends. Double-click in the text box in the Resources column and click the Find (. The job is launched multiple times at this rate. Minutes Specify the minutes that the job repeats. Select Resources in the left pane of the Properties . The repetition rate of the job. based on previous runs.1 . If you cancel a repetitive job. Resources Page Figure 127. This creates a new row in the list of resource dependencies. Properties .. 2. Est. it will not be launched again.Job Resources Page To add a resource dependency for the job: 1. Double-click in the text box in the Quantity column and enter the number of resource units required by the job. see “Finding Objects” on page 199. Properties .Table 84. If you rerun a repetitive job. Hours Specify the hours that a job repeats. If you rerun a repetitive job that had been cancelled... 230 Version 8.) button to locate and insert a resource name. see “Timeline View” on page 214. 3. The Resources page is displayed. For information about using the Find window. Click the Add Row button. the next iteration of the job is run immediately.

Alternatively. Entering notempty is the same as entering -s %p. True if the file exists and is readable. True if the file exists and is a regular file.Job Files Page To add a file dependency for the job: 1. only the following qualifiers are valid: -d %p -e %p -f %p -r %p -s %p -w %p True if the file exists and is a directory. Click the Add Row button. Properties . Tivoli Job Scheduling Console User’s Guide 231 . Managing Job Streams Figure 128. If no qualifier is specified. select the resource row in the list and click the Delete from Table button. 3. refer to your UNIX system documentation. Alternatively. Select Files in the left pane of the Properties . This creates a new row in the list of file dependencies. 2. On UNIX. the valid qualifiers are the same as UNIX test command conditions. Double-click in the text box in the Workstation column and enter a workstation or workstation class name. On Windows NT. On both UNIX and Windows NT. For more information.To remove a resource dependency for the job. the default is -f %p. Double-click in the text box in the Filename column and enter a file name. True if the file exists and is writable. True if the file exists and it’s size is greater than zero. The Files page is displayed. click the Find button to locate and insert a file name 4. True if the file exists. Double-click in the text box in the Qualifiers column and enter the test conditions for the file dependency. click the Find button to locate and insert the name of a workstation or workstation class.Job window. the expression %p inserts the file name. Files Page 18.

the message is not displayed but it requires a reply. select Predefined Prompt from the drop-down list. Prompts Page Figure 129. 2. If the string begins with a colon (:). For information about using the Find window. Click the Add Row (+) button. Select Prompts in the left pane of the Properties . For a predefined prompt dependency.) button to locate and insert the name of a prompt. For a predefined prompt. If you are adding a new job. To use a parameter. ¶ Click Cancel to close the window without saving the properties you have selected. double-click in the text box in the Name column and click the Find (. The default behavior of a prompt is to display a message and wait for a reply. To add a prompt dependency for the job. select the file row in the list and click the Delete from Table button.1 . When you have finished: ¶ Click OK to keep the properties you have selected and close the window. select Ad Hoc Prompt from the drop-down list. Copying and Pasting Jobs Within the Job Stream Editor you can copy and paste job and job stream buttons to create dependencies: 232 Version 8. For an ad hoc prompt.Job Prompts Page For an ad hoc prompt dependency. If the string begins with an exclamation mark (!). double-click in the text box in the Text column and enter the text of the prompt. Properties . This creates a new row in the list of prompt dependencies.. To remove a prompt dependency for the job. do the following: 1. select the prompt row in the list and click the Delete from Table button. You can include one or more scheduler parameters as part or all of the text string. The Prompts page is displayed. see “Finding Objects” on page 199..Job window.To remove a file dependency for the job. You can include backslash n (\n) within the text for new lines. place its name between carets (^). a job button is added in the Graph view. the message is displayed but no reply is necessary. 3.

Right-click the job button and select Copy from the pop-up menu. You add internetwork dependencies in a job stream using the Graph view of the Job Stream Editor. ¶ You can copy a job within the Job Stream Editor and clone its dependencies to another job. 18. The job name is added to the Properties . ¶ You can open multiple job streams in separate Job Stream Editors and copy and paste jobs between the job streams. For more information about configuring a network agent. Use the find tool to find and select a new job to add to the job stream.Job General page. you can create a dependency between this job stream and any jobs in the Job Stream Editor. Internetwork dependencies require a network agent workstation to communicate with the external scheduler network. 4. using the Add Link button.¶ You can copy a job stream from a job stream list and paste it into the Graph view of the Job Stream Editor. When you have finished in the Job Stream Editor. See “Graph View” on page 213 for more information. a new button is added for the job in the Graph view of the Job Stream Editor. This displays the Properties . This copies the job to the clipboard. Add internetwork dependencies to a job stream to create predecessors for the jobs in the job stream you are editing.Job window. Adding an Internetwork Dependency to a Job Stream An internetwork dependency is a dependency on a job that runs in another Workload Scheduler network. For more information see “Saving a Job Stream in the Database” on page 247 and “Closing the Job Stream Editor” on page 247. Then. 5. A predecessor must complete successfully before the successor job is launched. Tivoli Job Scheduling Console User’s Guide 233 . refer to the Tivoli Workload Scheduler Reference Guide. Click the Paste button in the toolbar or select Paste from the Edit menu. This job has the same dependencies as the copied job. When you click OK in the Properties . save the job stream and close the Job Stream Editor. Managing Job Streams 3. To clone the dependencies of a job: 1. Alternatively.Job window for the copied job. Cloning the Job Dependencies This procedure is used to clone the dependencies of a job to a new job within the Graph view of the Job Stream Editor. 2. select the job button and click the Copy button in the toolbar or select Copy from the Edit menu.

job.. click the Add Dependency on Internetwork button in the toolbar. A predecessor must complete successfully before the successor job is launched. To open the Graph view.. 3. You add external job streams in a job stream using the Graph view of the Job Stream Editor. The Internetwork Dependency window is displayed. see “Creating Dependencies Between Jobs in a Job Stream” on page 236. Add external job streams to a job stream to create predecessors for the jobs in the job stream you are editing. In the Graph view. Adding an External Job Stream to a Job Stream An external job stream is any job stream other than the one you are editing. In theDependency field. ¶ Click Cancel to close the window without saving the properties you have selected. click the Add Dependency on External Job Stream button in the toolbar. 2. 5. 234 Version 8. right-click a job stream and select Open from the pop-up menu. see “Graph View” on page 213. or the job or job stream predecessor in the format workstation#jobstream. right-click a job stream and select Open from the pop-up menu. For information about using an internetwork dependency as a predecessor. To open the Graph view. The maximum length of this field is: ¶ 120 for freeform characters ¶ 16 for the workstation ¶ 16 for the job stream ¶ 40 for the job When you have finished: ¶ Click OK to close the window. Move the mouse pointer to the position you want to place the new internetwork dependency in the Graph view and left-click. 2. If you are adding a new internetwork dependency.1 . a new internetwork dependency button is added in the Graph view.To add an internetwork dependency: 1. To add an external job stream: 1. Move the mouse pointer to the position you want to place the new external job stream in the Graph view and left-click. specify either the freeform dependency. In the Graph view.) button and use the Find Workstation window to select the name of the network agent. 4. The External Job Stream Dependency window is displayed. For more information. Click the Find (. 3.

right-click a job stream and select Open from the pop-up menu. Add external jobs to a job stream to create predecessors for the jobs in the job stream you are editing. click the Add Dependency on External Job button in the toolbar. 3. Click the Find (. For more information. A job stream button is added in the Graph view. Click Show Job Streams to list the job streams that run on the workstation. The External Job Dependency window is displayed. To add an external job: 1. You add external jobs in a job stream using the Graph view of the Job Stream Editor. 5. External Job Stream Dependency Window 4. Tivoli Job Scheduling Console User’s Guide 235 . Select a job stream in the list.. A predecessor must complete successfully before the successor job is launched. For information about using an external job stream as a predecessor.) button next to the Workstation field to locate and insert the name of the workstation on which the job stream runs. Managing Job Streams When you have finished: ¶ Click OK to close the window. 2.. 18. Move the mouse pointer to the position you want to place the new external job in the Graph view and left-click. see “Graph View” on page 213. ¶ Click Cancel to close the window without saving the properties you have selected. In the Graph view. see “Creating Dependencies Between Jobs in a Job Stream” on page 236. To open the Graph view. Adding an External Job to a Job Stream An external job is a job that runs in a job stream other than the one you are editing. 6.Figure 130.

see “Graph View” on page 213. see “Creating Dependencies Between Jobs in a Job Stream”. When you have finished: ¶ Click OK to close the window. External Job Dependency Window 4. click the Add Link button in the toolbar. Select a job in the list. Click the Find (. 2. For information about using the Find window. 3. ¶ Click Cancel to close the window without saving the properties you selected. For more information.) button next to the Job Stream Name field to locate and insert the name of the job stream in which the job runs. You add dependencies between jobs in the Graph view of the Job Stream Editor. 236 Version 8. When you release the mouse button. The dependencies are represented by arrows. Creating Dependencies Between Jobs in a Job Stream You can add dependencies between jobs to specify the order in which they run.1 .. A job button is added in the Graph view.Figure 131. Click Show Jobs to list the jobs in the selected job stream that run on the selected workstation. In the Graph view. For information about using an external job as a predecessor. right-click a job stream and select Open from the pop-up menu. To open the Graph view. Click the predecessor job or job stream and drag it to the successor job. an arrow is drawn from the predecessor to the successor. 6. To add a dependency between jobs: 1.. 5. see “Finding Objects” on page 199. A job that depends on the successful completion of another job is called a successor and the job or job stream that it depends on is called a predecessor.

Managing Job Streams Specifying Run Cycles for a Job Stream Run cycles specify when a job stream in the database is to run in the plan. ¶ Calendar Run Cycles Based on predefined calendars. ¶ Weekly Run Cycles Based on days of the week. When you are finished in the Job Stream Editor. select the arrow between the predecessor and the successor . You specify run cycles for a job stream using the Run Cycle view of the Job Stream Editor.Figure 132. external jobs. Internetwork dependencies. 2. Internetwork dependencies. and external job streams cannot be successors. To remove a dependency between jobs. For details about creating calendars. The days you mark in an inclusive run cycle are displayed as Days Included in the list of run cycles applied to the job stream. To display the Run Cycle view. you must specify if it designates the days when the job stream is to run (inclusionary) or when the job stream is not to run (exclusionary). external jobs. see “Run Cycle View” on page 216. There are three types of run cycle: ¶ Simple Run Cycles Based on specific calendar dates. refer to “Saving a Job Stream in the Database” on page 247. then right-click the arrow and select Delete from the pop-up menu. 18. Tivoli Job Scheduling Console User’s Guide 237 . Combinations of run cycles are used to include and exclude certain dates. select Run Cycle from the View menu in the Job Stream Editor or click the Run Cycle button in the toolbar. Job Stream Editor Window Graph View Notes: 1. and external job streams that are not linked are not saved when the Job Stream Editor is closed. For more information. Inclusionary or Exclusionary Run Cycles When you define a run cycle. see “Managing Calendars” on page 266.

Excluded days always take precedence over included days. For details. An excluded non-workday. you can specify a rule when you define the run cycle of a job stream. If the schedule date falls on a freeday. Note: Dates defined in the Holidays calendar are shown as non-workdays.. such as holidays or closing days.. The rule determines what action Workload Scheduler must take when the schedule of a job stream falls on a freeday. Based on a freedays calendar. For more information. A non-workday.. 238 Version 8. see “Freedays Calendars” on page 267. the scheduler proceeds by default and runs the job stream even if the selected run date is a freeday. For each job stream. Freedays calendars can in other terms be considered the list of non-workdays when there is no activity in your enterprise. An included date. Freedays are non-workdays. An excluded date.1 . the scheduler can do one of the following: ¶ Run the job stream ¶ Not run the job stream ¶ Run the job stream on the closest workday before the freeday ¶ Run the job stream on the closest workday after the freeday If no freeday rule is specified. Rule for Freedays This rule is based on the definition of freedays. Workload Scheduler does not reschedule the same job stream more than once on a given production day if its run date was moved because of a freeday rule application. An included non-workday.. The bars have the following meanings: Table 85. Blue Red White White/Blue White/Red Specifies . and can be defined in one or more specific calendars. see “The Holidays Calendar” on page 266. Colored Bars on Dates As you include and exclude dates. you can define as many inclusive and exclusive run cycles as you want. Colored Bars on Dates This bar .The days you mark in an exclusive run cycle are displayed as Days Excluded in the list of run cycles applied to the job stream. colored bars are displayed across the dates.

3. 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. Click the Run Cycle button in the toolbar. 18. Select nearest workday after freeday If the scheduled date falls on a freeday. If freeday. To do this: 1. Tivoli Job Scheduling Console User’s Guide 239 . Simple Run Cycle General Page 4.Specifying Simple Run Cycles You specify run cycles using the Job Stream Editor. 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. The Job Stream Editor is displayed 2. None Follow no rule. click the Simple Run Cycle button. Managing Job Streams Figure 133. run the job stream on the following workday. ¶ Select Exclusive to specify that the job stream must not run in the dates defined on the Rule page. do not run the job stream. run the job stream on the preceding workday. Select Rule in the left pane of the Simple Run Cycle window. The Rule page is displayed. The Simple Run Cycle General page is displayed. 6. Run the job stream regardless of whether the schedule falls on a freeday or on a workday. In the Run Cycle view. Right-click a job stream and select Open from the pop-up menu. do not select If the scheduled date falls on a freeday.

Click the dates in the calendar to add them to the run cycle. Simple Run Cycle Rule Page 7. Right-click a job stream and select Open from the pop-up menu. When you have finished: ¶ Click OK to close the window and add the run cycle to the job stream. Use the arrow buttons in the upper and lower bars of the selected view to move to the desired month and year. The Weekly Run Cycle General page is displayed. 8.1 . 3. Click on the same date a second time to remove it from the run cycle. ¶ Click Cancel to close the window without adding the run cycle to the job stream. click the Weekly Run Cycle button. Select the Monthly or Yearly tab to display the corresponding view. In the Run Cycle view.Figure 134. The Job Stream Editor is displayed 2. 240 Version 8. Click the Run Cycle button in the toolbar. Specifying Weekly Run Cycles To specify a weekly run cycle for a job stream: 1.

If freeday. ¶ Select Exclusive to specify that the job stream must not run in the dates defined in the Rule page. 6. 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. Run the job stream regardless of whether the schedule falls on a freeday or on a workday. Select nearest workday after freeday If the scheduled date falls on a freeday. 5. Click Rule to display the Rule page which is shown below 18. do not select If the scheduled date falls on a freeday. Weekly Run Cycle General Page 4. run the job stream on the following workday. run the job stream on the preceding workday. 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.Figure 135. None Follow no rule. Weekly Run Cycle Rule Page Tivoli Job Scheduling Console User’s Guide 241 . Managing Job Streams Figure 136. do not run the job stream.

1 . In the Run Cycle. Calendar Run Cycle General Page 4. ¶ Click Cancel to close the window without adding the run cycle to the job stream. you can also select: Weekdays Specifies every day of the week except Saturday and Sunday. Specifying Calendar Run Cycles To specify a calendar run cycle for a job stream: 1. In addition to single days. click the Calendar Run Cycle button. 5. The Calendar Run Cycle General page is displayed. Right-click a job stream and select Open from the pop-up menu. Select the days by name to add them to the run cycle. The Job Stream Editor is displayed 2. and the days defined either in the freedays calendar or in the Holidays calendar. Click the Run Cycle button in the toolbar. 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. Sunday.7. depending on which one you specified in the properties window of the job stream. Figure 137. 3. Click the arrow in the Rule for Freedays list box and select one of: 242 Version 8. Everyday Specifies every day of the week. When you have finished: ¶ Click OK to close the window and add the run cycle to the job stream. Workdays Specifies every day of the week except Saturday. ¶ Select Exclusive to specify that the job stream must not run in the dates defined in the Rule page. Freedays Specifies the days defined either in the freedays calendar or in the Holidays calendar. depending on which one you specified in the properties window of the job stream.

Click Rule in the left pane of the Calendar Run Cycle window. 8. For example. From the drop-down menu.for a negative offset from the drop-down menu. Workdays Specifies calendar days except Saturday.Select nearest workday before freeday If the scheduled date falls on a freeday. For more information. do not select If the scheduled date falls on a freeday. Managing Job Streams Figure 138. When you have finished: ¶ Click OK to close the window and add the run cycle to the job stream.. do not run the job stream. see “Finding Objects” on page 199. If freeday. enter the number of days (between 0 and 9999). In the Offset group. Enter the name of the calendar in the Name field or click the Find (. select one of: Days Specifies calendar days with no exceptions. c. ¶ Click Cancel to close the window without adding the run cycle to the job stream. and the days defined either in the freedays calendar or in the Holidays calendar. Select + for a positive offset or .) button to find a calendar. Select nearest workday after freeday If the scheduled date falls on a freeday. Calendar Run Cycle Rule Page 7. you can specify an offset from the dates defined in the calendar. run the job stream on the following workday. None Follow no rule. an offset of +2 Days results in an effective date of 3/15/2001.. 18. Sunday. To specify an offset: a. Weekdays Specifies calendar days except Saturday and Sunday. 6. The Calendar Run Cycle Rule page is displayed. run the job stream on the preceding workday. Run the job stream regardless of whether the schedule falls on a freeday or on a workday. In the Offset field. b. depending on which one you specified in the properties window of the job stream. Tivoli Job Scheduling Console User’s Guide 243 . if a calendar date is 3/13/2001.

¶ Click Cancel to close the window without saving the changes to the job stream. but it is not deleted from the database and can still be used by other job streams. In the Run Cycles Name column. Click the Run Cycle view button. select Timeline from the View menu in the Job Stream Editor or click the Timeline button in the toolbar. Open the job stream in the Job Stream Editor. When you have finished: ¶ Click OK to close the window and save the changes to the job stream. Modify the days selected and click OK to save your changes.Modifying Run Cycles for a Job Stream To modify the run cycles for a job stream: 1. For information about the Timeline view refer to “Timeline View” on page 214. select the run cycle you want to delete from the job stream. Specifying Time Restrictions for a Job Stream To specify time restrictions for the job stream in the Timeline view of the Job Stream Editor. Open the job stream in the Job Stream Editor. double click the run cycle you want to modify. 3. 4. Click the Run Cycle view button. 2.1 . The run cycle is deleted from the job stream. 244 Version 8. ¶ If this is a simple run cycle: A window is displayed showing the days selected by that run cycle. Specifying Time Restrictions in the Timeline View You can display and specify the time restrictions for a job stream and its jobs using the Timeline view of the Job Stream Editor. ¶ If this is a weekly run cycle: A window is displayed showing the days selected by that run cycle. The Run Cycle page is displayed. ¶ Click Cancel to close the window without saving the changes to the job stream. Modify the selected calendar or the offset and click OK to save your changes. 2. ¶ If this is a calendar run cycle: A window is displayed showing the name of the calendar you selected and specified offset. In the Run Cycles Name column. Deleting Run Cycles from a Job Stream To delete a run cycle from a job stream: 1. Click Delete. 3. The Run Cycle page is displayed. When you have finished: ¶ Click OK to close the window and save the changes to the job stream. If the run cycle was a calendar it is deleted from this job stream. Modify the days selected and click OK to save your changes.

. Table 86.Job window. For more information.. Start Enter this information . Specifying Time Restrictions for a Job To specify time restrictions for a job in the Timeline view of the Job Stream Editor. The earliest time the job stream will be launched. ¶ Drag the right side of the timeline to adjust the deadline time. Managing Job Streams When you have finished: ¶ Click OK to close the window and save the time restrictions. 11:30 am or 4:25 pm. The job stream will not be launched after this time. do any of the following: ¶ Drag the left side of the timeline to adjust the start time.Using the Timeline To adjust the time restrictions using the timeline.. Properties Information In this area . Deadline The latest time the job stream will be launched. ¶ Drag the center of the timeline to change both the start and the deadline time. At Enter a deadline time in the following format: hh:mm am|pm For example. Specify time Select this option to enable the entry of a deadline time. either select Timeline from the View menu in the Job Stream Editor or click the Timeline button in the toolbar. Using a Window To adjust the time restrictions using a window. Specify time Select this option to enable the entry of a start time. Tivoli Job Scheduling Console User’s Guide 245 . 11:30 am or 4:25 pm. The job stream will not be launched before this time. At Enter a start time in the following format: hh:mm am|pm For example.. Delay for Enter the number of days to offset the deadline time from the day the job stream is selected for inclusion in the production plan. either double-click the job stream row in the tabular pane or right-click the row and select Properties from the pop-up menu. Delay for Enter the number of days to offset the start time from the day the job stream is selected for inclusion in the production plan. ¶ Click Cancel to close the window without saving the time restrictions. see “Specifying Job Stream Properties” on page 217. Note: Time Restrictions can also be set in the Time Restrictions view of the Properties . 18. Note: The deadline time must be later than the Start Time. A properties window is displayed. Use the information in Table 86 to complete the text boxes and select options.

The repetition rate of the job. do any of the following: ¶ Drag the left side of the timeline to adjust the start time. Hours Specify the hours that a job repeats. For information about the time zone feature. double-click the job row in the tabular pane or right-click the row and select Properties from the pop-up menu. A properties window is displayed Use the information in Table 87 to complete the text boxes and select options. The job will not be launched before this time. ¶ Drag the center of the timeline to change both the start and the deadline time. ¶ Drag the right side of the timeline to adjust the deadline time. 11:30 am or 4:25 pm.. At Enter a deadline time in the following format: hh:mm am|pm For example. Using a Window To adjust the time restrictions using a window.. 246 Version 8.Using the Timeline To adjust the time restrictions using the timeline. Delay for Enter the number of days to offset the deadline time from the day the job is selected for inclusion in the production plan. Deadline The latest time the job will be launched. Delay for Enter the number of days to offset the start time from the day the job is selected for inclusion in the production plan. The earliest time the job will be launched. 11:30 am or 4:25 pm.. Table 87. Time Zone The time zone for this job. Note: The deadline time must be later than the Start Time. The job is launched multiple times at this rate. Start Enter this information . Minutes Specify the minutes that the job repeats. At Enter a start time in the following format: hh:mm am|pm For example. see “Enabling Time Zones in the Workload Scheduler” on page 385. Repeat Range When you have finished: ¶ Click OK to close the window and save the time restrictions.. Properties Information In this area . The job will not be launched after this time. Specify time Select this option to enable the entry of a deadline time.1 . Specify time Select this option to enable the entry of a start time.

Closing the Job Stream Editor To close the Job Stream Editor. 2. 3. See “Specifying Job Properties” on page 227 for more information. see “Creating a List of Job Streams” on page 190. 4. In the tree view of the Job Scheduling Console. ¶ Click No to close the Job Stream Editor without saving the job stream in the database. Displaying a List of Job Streams To display a list of job streams in the database: 1. For information about creating job stream lists. Expand the branches below the scheduler until you see the button for the job stream list you want to run. click the Close button in the window title bar or select Close from the File menu. Figure 139. Do one of the following: ¶ Click Yes to save the job stream in the database before closing the Job Stream Editor. Note: Time restrictions can also be set in the Time Restrictions view of the Properties . Saving a Job Stream in the Database To save a job stream in the database from the Job Stream Editor. expand the scheduler engine button. a warning messages is displayed. Right-click the job stream list button and select Load List from the pop-up menu. 18. The list results are displayed in the right pane of the Job Scheduling view. If you have not saved your job stream changes. Managing Job Streams ¶ Click Cancel to return to the Job Stream Editor without saving the job stream in the database. Job Streams List Window Tivoli Job Scheduling Console User’s Guide 247 . Select the job stream list button. click on the Save button in the toolbar or select Save from the File menu.Job window.¶ Click Cancel to close the window without saving the time restrictions.

The number of prompt dependencies on the job stream. The name of the job stream.Table 88 describes the column headings. a pop-up menu is displayed. The name of the workstation on which the job stream runs. The current JSS status of the job stream. Resource Dep. The priority of the job stream. Whether or not the job stream. The number of file dependencies on the job stream. Can be: In Order Carried Forward Carry Deadline time has passed Released from dependencies Canceled Cancel Pend. Is Monitored Job Stream When you right-click a job stream instance in the list. is to be monitored by Tivoli Business Systems Manager. For more information. The scheduled start time of the job stream. The time the job stream actually started.1 .. The number of internetwork predecessors to the job stream. 248 Version 8. see “Displaying a List of Job Streams” on page 247. Table 88. if it has been resubmitted or carried over... Job Dep.. and all the jobs it contains. The Workload Scheduler internal status for the job stream instance. The original name of the job stream. Displaying a Job Stream To display a job stream in the database: 1. The number of job dependencies on the job stream. The number of resource dependencies on the job stream. This is described in “Managing Job Stream Instances in the Plan” on page 316. Information about the job stream status. Priority Num Jobs OK Jobs Limit Original Job Stream Scheduled Start Actual Start Est. Prompt Dep. based on previous times the job stream ran. The number of jobs in the job stream that can run concurrently. The dependency can be a predecessor or successor. File Dep. The dependency can be a predecessor or successor. The estimated duration of the job stream. Inet Dep. Job Stream Workstation Status Internal Status Information Specifies . The number of jobs in the job stream. The time after which the job stream cannot run. The actual duration of the job stream. Run a list of job streams that contains the job stream you want to display. The number of jobs that ran successfully. Duration Actual Duration Deadline Time Job stream Dep. The number of job stream dependencies on the job stream. Job Streams List Columns This column .

Modifying a Job in a Job Stream To modify a job in a job stream. see “Saving a Job Stream in the Database” on page 247 and “Closing the Job Stream Editor” on page 247. right-click the job stream and select Properties from the pop-up menu. Managing Job Streams External job streams External jobs When you are finished modifying the job stream. Modifying an Internetwork Dependency in a Job Stream To modify an internetwork dependency in a job stream. The Properties . 2. “Modifying an External Job in a Job Stream” on page 250 and “Deleting Job Streams” on page 250. The job stream is displayed in the Job Stream Editor. Make your changes in the Job Stream Editor. In the list results. either double-click the job stream you want to display. “Modifying a Job in a Job Stream” and “Deleting a Job in a Job Stream”. 3. For information about the Job Stream Editor. “Modifying an Internetwork Dependency in a Job Stream” and “Deleting an Internetwork Dependency in a Job Stream” on page 250. “Modifying an External Job Stream in a Job Stream” on page 250 and “Deleting an External Job Stream in a Job Stream” on page 250. Modifying a Job Stream To modify a job stream in the database: 1. see “Specifying Job Stream Properties” on page 217. right-click its button in the Graph view and select Properties from the pop-up menu. In the list results. 18.Job Stream window is displayed. Tivoli Job Scheduling Console User’s Guide 249 . right-click the job button in the Graph view and select Properties from the pop-up menu. right-click the job button in the Graph view and select Delete from the pop-up menu. see “Specifying Job Properties” on page 227.. For more information. Table 89 shows where to find information about modifying a job stream. Modifying Objects in a Job Stream To modify these objects ... For more information. Click OK or on Cancel to close the Job Stream Editor. see “Adding an Internetwork Dependency to a Job Stream” on page 233.. For information about job properties. save the job stream in the database and close the Job Stream Editor. see “Creating a Job Stream” on page 217. Jobs Internetwork dependencies See . see “Displaying a List of Job Streams” on page 247.2. Deleting a Job in a Job Stream To delete a job in a job stream. Run a list of job streams that contains the job stream you want to modify. or right-click the job stream and select Properties from the pop-up menu. For more information. 3. Table 89. For information about internetwork dependency properties.

see “Displaying a List of Job Streams” on page 247.. For information about the Job Stream Editor.Deleting an Internetwork Dependency in a Job Stream To delete an internetwork dependency in a job stream. To edit the job. right-click its button in the Graph view and select Delete from the pop-up menu. click each job stream. click the first and last job streams in the range. run a list of job streams that contains the job stream you want to delete..1 . see “Specifying Job Properties” on page 227.. For information about job properties. 250 Version 8.. Click OK to delete the job stream in the database or click Cancel to cancel the delete operation. For information about the Job Stream Editor. Deleting Job Streams To delete job streams in the database. The job stream is displayed in the Job Stream Editor. Right-click the job stream and select Delete from the pop-up menu Hold down the Shift key. see “Using the Job Stream Editor” on page 213 and “Creating a Job Stream” on page 217. Modifying an External Job Stream in a Job Stream To modify an external job stream in a job stream. Deleting an External Job in a Job Stream To delete an external job in a job stream. Deleting an External Job Stream in a Job Stream To delete an external job stream in a job stream. For more information. 2. To delete . right-click its button in the Graph view and select Delete from the pop-up menu. The job stream is displayed in the Job Stream Editor. then right-click on one of the selected job streams and select Delete from the pop-up menu Multiple job streams that are not Hold down the Ctrl key. Modifying an External Job in a Job Stream To modify an external job in a job stream: 1. right-click its button in the Graph view and select Delete from the pop-up menu. One job stream Multiple job streams in a range Do this . then External Job Stream from the pop-up menu. then External Job Stream from the pop-up menu. right-click its button in the Graph view and select Edit . then right-click one in a range of the selected job streams and select Delete from the pop-up menu A message is displayed for each job stream asking for confirmation. Right-click its button in the Graph view and select Edit. see “Using the Job Stream Editor” on page 213 and “Creating a Job Stream” on page 217. right-click the job button in the Graph view and select Properties from the pop-up menu.

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 Workstation You create workstations in the database using the Properties .Workstation in Database window. In the tree view of the Job Scheduling Console. right-click the scheduler engine button and select New Workstation from the pop-up menu.19. Primarily workstation definitions refer to physical workstations. in the case of extended agents. Tivoli Job Scheduling Console User’s Guide 251 . The Properties .Workstation in Database window is displayed. To create a new workstation. see the user manual for the specific extended agent. However. For information about creating extended agent workstations. A workstation definition is required for every computer that runs jobs in the Workload Scheduler network. follow the steps below. See also “Creating a Workstation by Copying Another Workstation” on page 257. the workstations are logical definitions that must be hosted by a physical workstation. Managing Workstations 19 Managing Workstations and Workstation Classes Managing Workstations A workstation is usually an individual computer. on which jobs and job streams are run.

Workstation name Enter this information . Node TCP Port Operating System Domain 252 Version 8.. Properties . The Netman TCP port number that Workload Scheduler uses for communications on the workstation. Note: Workstation names must be unique. it can contain up to eight characters. The name must start with a letter and can contain alphanumeric characters. The default for a domain manager is the domain in which it is defined as the manager. For non-expanded databases. Fully-qualified domain names are accepted.Workstation in Database Information In this area . The default is 31111.. and cannot be the same as workstation and workstation class names. The operating system of the workstation.Workstation in Database Window Use the information in Table 90 to complete the text boxes and select options. it can contain up to 16 characters. it can contain up to 16 characters. dashes. and underscores..1 . For expanded databases. Select one of: UNIX Windows NT MPE/V MPE/IX Other The name of the Workload Scheduler domain of the workstation. usually named MASTERDM.Figure 140. Properties . The name of the workstation. For expanded databases.. The default for an extended agent is the domain of its host. The name must start with a letter and can contain alphanumeric characters. and cannot be the same as workstation class and domain names. For non-expanded databases. The port number of Netman on a workstation is defined by the localopts file in the parameter nm port. dashes. The host name or the IP address of the workstation. Table 90. and underscores. The default for fault-tolerant and standard agents is the master domain. Note: Domain names must be unique. it can contain up to eight characters.

The description can contain up to 40 characters. To ensure the accuracy of scheduling times. A description of the workstation. the agent. and all workstations are stopped and restarted. This can improve performance by reducing network activity. the domain manager automatically sends a copy of the new production plan and starts the agent. Ignore Select this so that the scheduler will ignore this workstation. refer to the Tivoli Workload Scheduler Reference Guide. Standard Agent Select this type for an agent workstation that launches jobs only under the direction of its domain manager. For a description of time zone names. This can be used to define workstations before they are actually installed. For each agent that has Auto Link selected. To keep an agent’s production plan at the same level of detail as its domain manager. in turn. When Full Status is selected. select this option to have the domain manager open the link to the agent when the domain manager is started. Whether to open the link between workstations at startup. Extended Agent Select this type for an agent workstation that launches jobs only under the direction of its host. select Full Status and Resolve Dependencies. At that time. Select one of the following from the drop-down list: Fault-tolerant Agent Select this type for an agent workstation that is capable of launching its jobs and resolving local dependencies without a domain manager. If Full Status is not selected. it is initialized when you run a link action on the agent’s domain manager or the master domain manager. This is for fault-tolerant agents only..19. this time zone must be the same as the computer’s operating system time zone. select this option to have its agents open links to the domain manager when they are started. the agent is informed only about the status of jobs and job streams on other workstations that affect its own jobs and job streams. and backup domain managers. Always select these options for backup domain managers. For fault-tolerant and standard agents. If Auto Link is also selected for the domain manager. The time zone of the workstation.. If Auto Link is not selected for an agent. For more information refer the user manual for the specific extended agent. domain managers.. Full Status Whether the agent is updated with full or partial status. Choose a time zone name from the drop-down list. For a domain manager. The type of workstation. Time Zone Enter this information .. Description Workstation Type Auto Link Tivoli Job Scheduling Console User’s Guide 253 . Managing Workstations Table 90. Auto Link is useful primarily during the startup sequence at the beginning of each day.Workstation in Database Information (continued) In this area . Extended agents can be used to interface Workload Scheduler with non-Tivoli systems and applications. opens a link back to the domain manager. a new production plan is created and compiled on the master domain manager. Select this type for fault-tolerant agents. the agent is updated about the status of jobs and job streams running on all other workstations in its domain and subordinate domains. Properties .

For Network agents. Always select these options for backup domain managers. To keep an agent’s production plan at the same level of detail as its domain manager. refer to the individual extended agent user’s guides. The extended agent will automatically connect to the new manager. and is useful if you need to switch masters in the domain. For a remote UNIX extended agent the method name is unixrsh. For more information about network agents. refer to the Tivoli Workload Scheduler Reference Guide. If more than 36 server IDs are required in a domain. When Resolve Dependencies is selected. consider dividing it into two or more domains. To specify a server. or FTA. If Resolve Dependencies is not selected. Server Specify a Mailman server on the domain manager to handle communications with the agent. Using servers can reduce the time required to initialize agents and improve the timeliness of messages.. Access Method An access method for extended agents and network agents. The host is the workstation with which the extended agent communicates and where its access method resides.. The IDs are unique to each domain manager. This reduces processing overhead.Table 90. Specify whether an agent will track all dependencies or only its own.1 . a single server is created to handle their communications. The name of the agent’s host workstation.. This is for fault-tolerant and standard agents only. Properties . select a letter or a number (A-Z and 0-9) from the drop-down list. For more information about extended agents. This is required for extended agents. Do not use this option for domain managers. select Full Status and Resolve Dependencies. the agent tracks dependencies for its own jobs and job streams only. Domain Manager. Resolve Dependencies Enter this information .Workstation in Database Information (continued) In this area . so you can use the same IDs in other domains without conflict. it creates a separate server for each unique server ID. the method name is unixlocl. As a guide. Host Note: The host option is no longer required for Standard agents. This is for fault-tolerant agents only. This assigns the host as the Master Domain Manager. communications with the agent are handled by the main Mailman process on the domain manager. extra servers should be defined to prevent a single server from handling more than eight agents. including those running on other workstations. the method name is netmth. If a server ID is not specified. For a local UNIX extended agent. the agent tracks dependencies for all jobs and job streams. This must be the name of a method file that resides in the TWShome/methods directory on the agent’s host workstation. The host for an extended agent can be specified as $MASTER. When a domain manager starts up. The host workstation for standard agents is now defaulted to the domain manager. Note that Full Status must also be selected so that the agent is informed about activity on other workstations. The host for an extended agent must be a Master.. 254 Version 8. If the same ID is used for multiple agents.

. The name of the workstation. Workstation List Window Columns This column . ¶ Click the Cancel button to close window without saving the workstation in the database. Right-click the workstation list button and select Load List from the pop-up menu. For information about creating workstation lists. In the tree view of the Job Scheduling Console. 3. 4. do one of the following: ¶ Click the OK button to save the workstation in the database and close the window... The list results are displayed in the right pane of the Job Scheduling view. Expand the branches below the scheduler until you see the button for the workstation list you want to run. Managing Workstations Displaying a List of Workstations To display a list of workstations in the database: 1. Workstation List Window Table 91 describes the column headings in the workstation display. Select the workstation list button. Table 91. This is one of: Fault-tolerant Agent Standard Agent Extended Agent The type of operating system for the workstation.. 19. Figure 141. Name Type Specifies . This is one of: UNIX Windows NT MPE/IX MPE/V Other OS Tivoli Job Scheduling Console User’s Guide 255 .Workstation in Database window.When you have finished in the Properties . The type of workstation. expand the scheduler engine button. see “Creating a List of Workstations” on page 192. 2.

2. ¶ To delete multiple workstations that are not in a range. click each workstation. For information about this window.. Run a list of workstations that contains the workstation you want to display. see “Creating a Workstation” on page 251.. 3. Domain Time Zone Creator Last Updated Specifies . see “Creating a Workstation” on page 251. double-click the workstation you want to modify or right-click the workstation and select Properties from the pop-up menu. The time zone of the workstation. When you have finished: ¶ Click OK to save the workstation in the database and close the window. Run a list of workstations that contains the workstation you want to display. do one of the following: ¶ To delete one workstation. 2.. See “Displaying a List of Workstations” on page 255 for more information. if one is defined The name of the user who created the workstation in the database The date the workstation was last updated in the database.Table 91. then right-click one of the selected workstations. See “Displaying a List of Workstations” on page 255 for more information. Modifying a Workstation To modify a workstation in the database: 1. hold down the Shift key. Choose Delete from the pop-up menu. then right-click one of the selected workstations. For information about this window. Run a list of workstations that contains the workstation you want to delete. click the first and last workstations in the range. right-click the workstation. Deleting Workstations To delete workstations in the database: 1. A confirmation message is displayed for each workstation. The name of the domain in which the workstation is a member. double-click the workstation you want to display or right-click the workstation and select Properties from the pop-up menu. ¶ Click Cancel button to close the Properties . In the list results. This opens the workstation in the Properties .1 . The Properties . 4..Workstation in Database window without saving the workstation in the database. See “Creating a Workstation” on page 251 for more information. 256 Version 8. 3. Click OK or on Cancel to close the window. Workstation List Window Columns (continued) This column . In the list results. ¶ To delete multiple workstations in a range. Make your changes in the Properties . Displaying a Workstation To display a workstation in the database: 1.Workstation in Database window. 2.Workstation in Database window.Workstation in Database window is displayed. 3. hold down the Ctrl key. In the list results.

¶ Click Cancel to close the window without saving the workstation in the database.Workstation Class window. In the tree view of the Job Scheduling Console.Workstation Class General window is displayed Tivoli Job Scheduling Console User’s Guide 257 . Right-click the scheduler engine button and select New Workstation Class from the pop-up menu. 2. Change the name in the Workstation name text box to the name of the new workstation. Job streams and jobs can be assigned to run on a workstation class.Workstation in Database window. Managing Workstation Classes A workstation class is a group of workstations. 2. For information about the Properties .4. 3. Click OK to delete the workstation in the database or click Cancel to cancel the delete operation. Creating a Workstation Class To create workstation classes in the database. The Properties . Make other changes as needed to define the new workstation. Any number of workstations can be placed in a class. 4. 5. making replication across many workstations easy. 19. each job added to the job stream must be defined either on a single workstation or on the exact same workstation class that the job stream was defined on. right-click the workstation you want to copy and select Create another from the pop-up menu. Run a list of workstations that contains the workstation you want to copy. Managing Workstations Creating a Workstation by Copying Another Workstation To create a new workstation in the database using a copy of another workstation: 1. See “Displaying a List of Workstations” on page 255 for more information. expand the scheduler engine button. When you have finished: ¶ Click OK to save the workstation in the database and close the window.Workstation in Database window. This displays a copy of the workstation in the Properties . If a job stream is defined on a workstation class. see “Creating a Workstation” on page 251. you use the Properties . In the list results. To create a new workstation class: 1.

dashes.1 . enter the name of the workstation class. Workstations Page Figure 143. it can contain up to eight characters. Select Workstations in the left pane of the Properties .. Properties .Workstation Class Workstations Page Table 92. refer to “Finding Objects” on page 199.Workstation Class window.. Properties . 2. For non-expanded databases. Add individual workstations to the class Add all of the workstations in the database to the workstation class Delete a workstation from the workstation class Do this . When you have finished: 258 Version 8.Workstation Class Workstations Page To perform this task . it can contain up to 16 characters.Workstation Class General Page 1. Select the workstation in the Workstation List and click Delete from Table (X). Note: Workstation class names must be unique and cannot be the same as workstation and domain names.. click Find Workstations. Properties . and underscores.General Page Figure 142. In the Name text box.. For expanded databases. click Add All Workstations. The name must start with a letter and can contain alphanumeric characters. For information about using the find facility. The Workstations page is displayed.

. 3. click OK or on Cancel to close the window.¶ click OK to close the window and save the new workstation class in the database. The name of the user who created the workstation class in the database. 4. 2. See “Creating a List of Workstation Classes” on page 193 for information about creating workstation class lists. The date the workstation class was last updated in the database. expand the scheduler button. Select the workstation class list button. 2. The name of the workstation class.. Workstation Class List Window This column . For information about this window. In the list results. Managing Workstations Displaying a List of Workstation Classes To display a list of workstation classes in the database: 1. see “Creating a Workstation Class” on page 257. In the tree view of the Job Scheduling Console. Run a list of workstation classes that contains the workstation class you want to display. The Properties . Right-click the workstation class list button and select Load List from the pop-up menu. 3. Expand the branches below the scheduler until you see the button for the workstation class list you want to run.Workstation Class window is displayed.. Figure 144. double-click the workstation class you want to display or right-click the workstation class and select Properties from the pop-up menu.. Table 93. See “Displaying a List of Workstation Classes” for more information. The list results are displayed in the right pane of the Job Scheduling Console. ¶ click Cancel to close the window without saving the workstation class in the database. Workstation Class List Window Table 93 describes the of the workstation class list. Name Creator Last Updated Specifies . Tivoli Job Scheduling Console User’s Guide 259 . Displaying a Workstation Class To display a workstation class in the database: 1. 19.

A message is displayed for each workstation class asking for confirmation. Run a list of workstation classes that contains the workstation class you want to modify. see “Creating a Workstation Class” on page 257. then right-click one of the selected workstation classes. Make your changes in the window. double-click the workstation class you want to modify or right-click the workstation class and select Properties from the pop-up menu. 260 Version 8. click the first and last workstation classes in the range.1 . In the list results. Deleting Workstation Classes To delete workstation classes in the database: 1. Select Delete from the pop-up menu. hold down the Shift key. do one of the following: ¶ To delete one workstation class. click each workstation class. right-click the workstation class. ¶ To delete multiple workstation classes in a range. hold down the Ctrl key. Run a list of workstation classes that contains the workstation class you want to delete. 4. When you have finished: ¶ click OK to save the workstation class in the database and close the window.Workstation Class window is displayed. See “Displaying a List of Workstation Classes” on page 259 for more information. then right-click one of the selected workstation classes. 2. click OK to delete the workstation class in the database or click Cancel to cancel the delete operation. See “Displaying a List of Workstation Classes” on page 259 for more information. In the list results. The Properties . 3. ¶ To delete multiple workstation classes that are not in a range. 2. ¶ click Cancel to close the window without saving the workstation class in the database. 3. 4. For information about the Properties .Workstation Class window.Modifying a Workstation Class To modify a workstation class in the database: 1.

Figure 145. refer to “Finding Objects” on page 199. The name of the domain. Managing Domains. consisting of one or more workstations and a domain manager acting as the management hub. Creating a Domain To create domains in the database. right-click the scheduler engine button and select New Domain from the pop-up menu. To do this. except for the master domain. Description Parent Domain Tivoli Job Scheduling Console User’s Guide 261 .. and Calendars Managing Domains A domain is a named group of Workload Scheduler workstations. For information about using the Find button.. Users. Note: Domain names must be unique and cannot be the same as workstation and workstation class names. in the tree view of the Job Scheduling Console. The default is the master domain. Properties . Properties . dashes. Users. Domain Name Enter this information . The Properties .Domain window is displayed. For non-expanded databases.Domain Window In this area . The name must start with a letter and can contain alphanumeric characters..Domain Window Use the information in Table 94 to complete the text boxes.. Table 94. A description of the domain. For expanded databases. it can contain up to eight characters. and Calendars 20. you use the Properties . it can contain up to 16 characters. The name of the parent domain to which the domain manager is linked. and underscores. All domains have a parent domain.20 Managing Domains.Domain window.

Table 95 describes the columns of the domain list. refer to “Finding Objects” on page 199. See “Creating a List of Domains” on page 196 for information about creating domain lists. Click Load List in the toolbar or right-click on the domain list button and select Load List from the pop-up menu. expand the scheduler engine button. Click OK or on Cancel to close the window.. When you have finished: ¶ Click OK to close the window and save the new domain in the database. The domain manager must be a fault-tolerant agent with Full Status and Resolve Dependencies selected. Name Parent Domain Domain Manager Creator Last Updated Specifies . The name of the user who created the domain in the database. 3. The name of the domain above this domain in the hierarchy. The name of the workstation that is the domain manager. In the list results. The date the domain was last updated in the database. The name of the workstation that is the manager of this domain. See “Displaying a List of Domains” for more information.. Expand the branches below the scheduler until you see the button for the domain list you want to run. For information about this window. 2. you can specify a domain manager workstation that does not yet exist. ¶ Click Cancel to close the window without saving the domain in the database. 262 Version 8.Domain Window (continued) In this area . 4. Domain List Columns This column .1 . see “Creating a Domain” on page 261. Run a list of domains that contains the domain you want to display. Displaying a Domain To display a domain in the databases: 1. Select the domain list button... Table 95....Domain window. The list results are displayed in the right pane of the Job Scheduling Console..Table 94. For information about using the Find button. Properties . Note: When creating a new domain. 3. 2. In the tree view of the Job Scheduling Console. Displaying a List of Domains To display a list of domains in the database: 1. double-click the domain you want to display or right-click the domain and select Properties from the pop-up menu. The name of the domain. Domain Manager Enter this information . This opens the domain in the Properties . The following are descriptions of the column headings.

This is required for Windows NT users only. 2. See “Displaying a List of Domains” on page 262 for more information. hold down the Shift key. When you have finished: ¶ Click OK to save the domain in the database and close the Properties . ¶ Click Cancel to close the Properties . 4. Run a list of domains that contains the domain you want to modify. 2.NT User window. 20.NT User window is displayed Tivoli Job Scheduling Console User’s Guide 263 . Click OK to delete the domain in the database or click Cancel to cancel the delete operation. Select Delete from the pop-up menu.Modifying a Domain in the Database To modify a domain in the database. do one of the following: ¶ To delete one domain. 3. in the tree view of the Job Scheduling Console. In the list results.Domain window. To do this. Managing Domains. you use the Properties . 3. Run a list of domains that contains the domain you want to delete. Creating a User To create users in the database. click the first and last domains in the range. ¶ To delete multiple domains in a range. and Calendars Deleting Domains in the Database To delete domains in the database. 4. Users. double-click the domain you want to modify or right-click the domain and select Properties from the pop-up menu. then right-click one of the selected domains. follow these steps: 1. right-click the domain. hold down the Ctrl key. A confirmation message is displayed for each domain. The Properties . right-click the scheduler engine button and select New User from the pop-up menu. see “Creating a Domain” on page 261. For more information.Domain window without saving the domain in the database. In the list results. ¶ To delete multiple domains that are not in a range. then right-click on one of the selected domains. follow these steps: 1. click each domain. Make your changes in the window. Managing Users The users for whom Workload Scheduler will launch jobs must be defined in the database. See “Displaying a List of Domains” on page 262 for more information.Domain window. This opens the domain in the Properties .

Confirmation The user password again for confirmation.. The default is all workstations. New Password A new user password as defined on the Windows NT computer.. This field is optional. If the name is not fully qualified (that is. 264 Version 8. 2. Table 96. 3. a domain user. Windows NT user names are case-sensitive. Properties . refer to “Finding Objects” on page 199. User Name Enter this information .NT User Window Use the information in Table 96 to complete the fields in the window.. in that order. it is considered to be a local user. no Windows NT domain is entered) or is not unique in Windows NT. A user must be able to log on to the workstation on which Workload Scheduler will launch jobs. NT Domain The Windows NT domain of this user. Displaying a List of Users To display a list of users in the database. a domain user.Figure 146. or a trusted domain user. ¶ Click Cancel to close the window without saving the user in the database. The name of the Workload Scheduler workstation on which the user is allowed to launch jobs.. expand the branches below the scheduler until you see the button for the user list you want to display. NT Workstation Set Password When you have finished: ¶ Click OK to close the window and save the new user in the database. The Windows NT user name.NT User Window In this area . Right-click the user list button and select Load List from the pop-up menu. or a trusted domain user. The list results are displayed in the right pane of the Job Scheduling view. Properties . it is considered to be a local user.1 . in that order. Notes: 1. The name can contain up to 47 characters. If the name is not unique in Windows NT. For information about using the Find button. and have the right to Log on as batch.

Table 97. Tivoli Job Scheduling Console User’s Guide 265 . This opens the user in the Properties .NT User window.NT User window. Managing Domains. This opens the user in the Properties . and Calendars Figure 147. Users List Window Table 97 describes the columns of the window. The Windows NT domain and the name of the user.20. In the list results. 3. Displaying a User To display a user in the database: 1. Make your changes. Modifying a User To modify a user in the database: 1.NT User window. See “Displaying a List of Users” on page 264 for more information. 2.NT User window. 3. see “Creating a User” on page 263.. double-click the user you want to display or right-click on the user and select Open from the pop-up menu. see “Creating a User” on page 263. See “Displaying a List of Users” on page 264 for more information. Users List Window This column . For information about the Properties . In the list results. 2. Click OK or on Cancel to close the window. Users. double-click the user you want to modify or right-click on the user and select Open from the pop-up menu. ¶ Click Cancel to close the window without saving the user in the database.. 4... The name of the workstation on which the user will launch jobs. NT Domain\User NT Workstation Specifies . When you have finished: ¶ Click OK to save the user in the database and close the window. Run a list of users that contains the user you want to display. For information about the Properties . Run a list of users that contains the user you want to modify.

Deleting Users To delete users in the database: 1.1 . Select Delete from the pop-up menu. Click Change Password. click the connector in the left pane. then right-click on one of the selected users. hold down the Ctrl key. You can create as many calendars as required to meet your scheduling needs. then right-click one of the selected users. ¶ To delete multiple users that are not in a range. A list of pay dates A list of month ending dates A list of your company’s holidays The Holidays Calendar The HOLIDAYS calendar is used to determine non-workdays for the purpose of defining run cycles for your job streams. It also affects the definition of the workdays keyword in the following terms: workdays=everyday except saturday. 3. sunday and all the dates appearing in the HOLIDAYS calendar 266 Version 8. right-click the user. do one of the following: ¶ To delete one user. 7. 3. A confirmation message is displayed for each user. Since a calendar is defined to the scheduler database. Click Selected from the menu. it can be assigned to multiple job streams. Assigning a calendar run cycle to a job stream causes that job stream to be run on the days specified in the calendar. Click OK to delete the user in the database or click Cancel to cancel the delete operation. Managing Calendars A calendar is a list of scheduling dates defined in the scheduler database. Run a list of users that contains the user you want to delete. See “Displaying a List of Users” on page 264 for more information. click the first and last users in the range. 4. Enter the password in the New Password text box. Changing User Passwords To change a user password: 1. 2. In the list results.. Click the search button to specify a name in the User Name text box. 2. PAYDAYS MONTHEND HOLIDAYS Could contain . Example Calendars This calendar . 6. ¶ To delete multiple users in a range. click each user. hold down the Shift key. 5.. Re-enter the password in the Confirmation text box.. From the main console.. For example: Table 98. 4. Click OK.

right-click the scheduler button and select New Calendar from the pop-up menu. Note: You cannot use Workload Scheduler keywords (for example. as implied by the freedays calendar. Freedays calendars extend the role of the HOLIDAYS calendar. to respond to different non-workdays requirements. enter a description of the calendar. In the tree view of the Job Scheduling Console. Click Define Calendar to add dates to the calendar. 3. A possible scenario is to define more than one freedays calendar to use in your scheduling activity. Tivoli Job Scheduling Console User’s Guide 267 . you use the Properties . When defining a job stream. as shown in the next figure. when no scheduling activity is to take place. if you decide to use a freedays calendar instead of HOLIDAYS.You should create a HOLIDAYS calendar with the dates of your holidays. dashes. particularly in the case your enterprise has different international locations. specify the name of the calendar. When you do not specify a freedays calendar for the job stream. Properties . is limited to that particular job stream. then HOLIDAYS is used.Calendar Window 2. 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. freedays and schedule). Managing Domains. The Properties . The name can contain up to eight characters.Calendar window. if available. 4. 20. the redefined meaning of workdays. To do this. In the Description field. Users. In the Name field. The Monthly Yearly Calendar window is displayed. Freedays Calendars A freeday must be intended as a non-workday. : 1. Figure 148. as they provide additional flexibility in defining workdays. The name must start with a letter and can contain alphanumeric characters. and underscores.Calendar window is displayed. and Calendars Creating a Calendar in the Database To create calendars in the database. then the definition of workdays becomes: workdays=everyday except saturday.

To add a day of the month by number. Click OK to close the Day of Month window and select the dates. Click Cancel to close the window without adding the dates to the calendar. 7. 11.Figure 149. 9. select Day of Month from the Select menu.Calendar window and save the new calendar in the database. Figure 150. When you have finished: ¶ Click OK to close the Properties . To add a specific day of the month. The days you specified are selected for every month in this range. Click OK to close the Monthly Yearly Calendar window and add the dates to the calendar. 12. The Day of Month window is displayed. 10. select the day number in the Day drop-down list. select the Last Day of Month option.1 . Monthly Yearly Calendar Window 5. Click Cancel to close the window without selecting the dates. ¶ Click Cancel to close the window without saving the calendar in the database. 6. To add a specific date to the calendar. Use the arrow buttons above and below the calendar to change the month and year. To add the last day of the month. click the date in the calendar view. 268 Version 8. Day of Month Window 8. Select Monthly or Yearly in the left pane of the window to view a monthly or yearly calendar. Select start and end dates for the calendar by selecting the month and year from the Start and End drop-down lists.

2. click each calendar. Run a list of calendars that contains the calendar you want to display. 3. Users. Right-click the calendar list button and select Load List from the pop-up menu. See “Displaying a List of Calendars” for more information. Modifying a Calendar in the Database To modify a calendar in the database: 1. The Properties . Tivoli Job Scheduling Console User’s Guide 269 . Managing Domains. hold down the Shift key. click the first and last calendars in the range. Make your changes. 2. For information about this window. Right-click the calendar and select Properties from the pop-up menu. When you have finished: ¶ Click OK to save the calendar in the database and close the window. The Properties Calendar window is displayed. see “Creating a Calendar in the Database” on page 267. See “Displaying a List of Calendars” for more information. then right-click one of the selected calendars. Run a list of calendars that contains the calendar you want to delete. ¶ Click Cancel to close the window without saving the calendar in the database. ¶ To delete multiple calendars that are not in a range. hold down the Ctrl key. In the list results. expand the scheduler tree until you see the button for the calendar list you want to run. Viewing Calendar Properties 20. and Calendars To display a calendar in the database: 1. ¶ To delete multiple calendars in a range. do one of the following: ¶ To delete one calendar. Deleting Calendars To delete calendars in the database: 1. 2. See “Displaying a List of Calendars” for more information. Right-click the calendar and select Properties from the pop-up menu. In the tree view of the Job Scheduling Console. Select Delete from the pop-up menu.Displaying a List of Calendars To display a list of calendars in the database: 1. Run a list of calendars that contains the calendar you want to modify. A confirmation message is displayed for each calendar. ¶ Click Cancel to close the window without saving the calendar in the database. The list results are displayed in the right pane of the Job Scheduling Console. 2. right-click the calendar. For information about this window. then right-click on one of the selected calendars.Calendar window is displayed. When you have finished: ¶ Click OK to save the calendar in the database and close the window. 3. see “Creating a Calendar in the Database” on page 267.

270 Version 8. Click OK to delete the calendar in the database or click Cancel to cancel the delete operation.1 .4.

The name must start with a letter and can contain alphanumeric characters. 2. Prompts.. To create a new resource: 1. Name Enter this information .. and Parameters For example.Resource in Database window.21 Managing Resources.Resource in Database window is displayed. communication lines. Figure 151. and Parameters Managing Resources Resources represent any type of resources on your system such as tape drives. you can define a resource called TAPES with a value of 2 and define jobs that require both tape drives as a dependency. Table 99. databases. because each time a job is run the TAPES resource is in use. and underscores. Tivoli Job Scheduling Console User’s Guide 271 . The Properties . Properties .. dashes. Prompts. it can be used as a dependency for jobs and job streams that run on the workstation or workstation class for which the resource is defined. that are needed to run a job..Resource in Database Window Information In this area . After defining a resource in the Workload Scheduler database. The name can contain up to eight characters. Resources can be physical or logical.Resource in Database Window Use the information in Table 99 to complete the window. Properties . The name of the resource. Click the New Resource button in the toolbar or right-click the scheduler button and select New Resource from the pop-up menu. Creating a Resource To create resources in the database. expand the scheduler engine button. Jobs with this dependency cannot run concurrently. you use the Properties . In the tree view of the Job Scheduling Console. or printers. 21. Managing Resources.

Table 99. In the tree view of the Job Scheduling Console. Description Quantity Workstation Enter this information . In the Quantity field. For information about using the Find button. The number of available resource units. Figure 152. expand the scheduler engine button. When you have finished: ¶ Click OK to close the window and save the new resource in the database. enter the number of available resource units. Values can be 0 through 1024. enter the name of the workstation or workstation class on which the resource is used. Resource List Window 4. ¶ Click Cancel to close the window without saving the resource in the database. Right-click the resource list button and select Load List from the pop-up menu. Expand the branches below the scheduler until you see the button for the resource list you want to run.. The list results are displayed in the right pane of the Job Scheduling Console.Resource in Database Window Information (continued) In this area . In the Resource field. Displaying a List of Resources To display a list of resources in the database: 1. 6. Properties . See “Creating a List of Resources” on page 193 for information about creating resource lists. 3. enter the name of the resource. A description of the resource. You can type a name directly or you can click Find and select a workstation or workstation class from a list.. In the Workstation field. Specify the name of the workstation or workstation class on which the resource is used.1 . 2. refer to “Finding Objects” on page 199... 5. Displaying a Resource To display a resource in the database: 272 Version 8.

See “Displaying a List of Resources” on page 272 for more information. In the list results. double-click the resource you want to display or right-click the resource and select Properties from the pop-up menu. A confirmation message is displayed for each resource. Run a list of resources that contains the resource you want to modify. Creating a Resource by Copying Another Resource To create a new resource in the database using a copy of another resource: 1. See “Displaying a List of Resources” on page 272 for more information. In the Name text box.Resource In Database window. right-click the resource you want to copy and select Create another from the pop-up menu. When you have finished: ¶ Click OK to save the resource in the database and close the window. This displays a copy of the resource in the Properties . 3. Make your changes. In the list results. change the name to the name of the new resource. ¶ Click Cancel to close the window without saving the resource in the database. For information about this window. This opens the resource in the Properties . Modifying a Resource To modify a resource in the database: 1. In the list results. 21. For information about this window. Click OK to delete the resource in the database or click Cancel to cancel the delete operation.Resource In Database window. hold down the Ctrl key.Resource In Database window. See “Displaying a List of Resources” on page 272 for more information. Tivoli Job Scheduling Console User’s Guide 273 . 2. Run a list of resources that contains the resource you want to delete. Click OK or on Cancel to close the window. see “Creating a Resource” on page 271. then right-click on one of the selected resources. click each resource. Deleting Resources To delete resources in the database: 1. This opens the resource in the Properties . ¶ To delete multiple resources that are not in a range. Run a list of resources that contains the resource you want to copy. In the list results. Managing Resources. 2.1. right-click the resource. See “Displaying a List of Resources” on page 272 for more information. 2. click the first and last resources in the range. Run a list of resources that contains the resource you want to display. then right-click one of the selected resources. see “Creating a Resource” on page 271. 3. and Parameters 4. 3. double-click the resource you want to modify or right-click the resource and select Open from the pop-up menu. ¶ To delete multiple resources in a range. Select the Delete command from the pop-up menu. 3. 4. Prompts. 2. hold down the Shift key. do one of the following: ¶ To delete one resource.

Predefined prompt This is defined in the Workload Scheduler database and can be used by any job or job stream. right-click the scheduler button and select New Prompt from the pop-up menu. For example. Creating a Prompt To create prompts in the database. For information about this window. Properties . To create a new prompt: 1. 274 Version 8. The default behavior of a prompt is to display a message and wait for a reply. Change the other text boxes as needed to define the new resource. 3.Resource In Database window without saving the resource in the database. see “Creating a Resource” on page 271.Prompt Window 2.1 . In the Text field. and underscores. enter the name of the prompt. The name must start with a letter and can contain alphanumeric characters. you use the Properties . If the string begins with an exclamation mark (!).Prompt window. When you have finished: ¶ Click OK to save the resource in the database and close the window. the message is displayed but no reply is necessary. If the string begins with a colon (:). you can issue a prompt to make sure that a printer is online before a job that prints a report runs. enter the text of a prompt. ¶ Click Cancel to close the Properties .Prompt window is displayed. In the tree view of the Job Scheduling Console. dashes. Figure 153. There are two types of prompt: Ad hoc prompt This is defined within the properties of a job or job stream and is unique to that job or job stream. the message is not displayed but it requires a reply. In the Name field. A prompt must be answered affirmatively for the dependent job or job stream to launch. 4. 5.4. The name can contain up to eight characters. The Properties . You can include backslash n (\n) within the text to create a new line. Managing Prompts in the Database Prompts can be used as dependencies for jobs and job streams. 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.

This opens the prompt in the Properties . For information about this window. double-click the prompt you want to display or right-click the prompt and select Open from the pop-up menu. The list results are displayed in the right pane of the Job Scheduling Console. For information about this window. Tivoli Job Scheduling Console User’s Guide 275 . 4. 2.Prompt window. In the tree view of the Job Scheduling Console. and Parameters Figure 154. Make your changes. see “Creating a Prompt” on page 274. Run a list of prompts that contains the prompt you want to modify. 3. double-click the prompt you want to modify or right-click the prompt and select Open from the pop-up menu. ¶ Click Cancel to close the window without saving the prompt in the database. Managing Resources. In the list results. Prompts. 21. Run a list of prompts that contains the prompt you want to display.Prompt window. This opens the prompt in the Properties . Modifying a Prompt in the Database To modify a prompt in the database: 1. Displaying a Prompt To display a prompt in the database: 1. expand the scheduler tree. When you have finished: ¶ Click OK to save the prompt in the database and close the window. Prompts List Window The Name and Text columns specify the name and text content of the prompts. 2. 2. See “Displaying a List of Prompts” for more information. See “Displaying a List of Prompts” for more information.Displaying a List of Prompts To display a list of prompts in the database: 1. 3. see “Creating a Prompt” on page 274. Right-click the prompt list button and select Load List from the pop-up menu. Click OK or on Cancel to close the window. In the list results.

Managing Parameters Parameters are useful to substitute values into your jobs and job streams. the parameter must be defined on the workstation where it will be used. and you rename it.Parameter window. If this is the case. any action you perform that refers to the old name will return an error. A confirmation message is displayed for each prompt.Deleting Prompts To delete prompts in the database: 1. 2. a parameter can be used as a substitute for all or part of: ¶ File dependency path names ¶ Text for prompts ¶ Logon. hold down the Ctrl key. See “Displaying a List of Prompts” on page 275 for more information. To create a new parameter: 1. and script file names When using a parameter in a job script. In this case. 4.1 . click each prompt. For scheduling. then right-click one of the selected prompts. Click OK to delete the prompt in the database or click Cancel to cancel the delete operation. command.Parameter window is displayed. right-click the prompt. then right-click on one of the selected prompts. In the list results. you use the Properties . ¶ To delete multiple prompts in a range. click the first and last prompts in the range. Parameters cannot be used when scripting Extended Agent jobs. hold down the Shift key. 2. Note: Be careful when renaming a parameter because it might be part of a dependency for a job scheduler object in the database. In the Job scheduling Console. The Properties . Since parameters are stored in the Workload Scheduler database. do one of the following: ¶ To delete one prompt. Creating a Parameter To create parameters in the database . all jobs and job streams that use the particular parameter are updated automatically when the value changes. 3. 276 Version 8. right-click the scheduler engine button and select New Parameter from the pop-up menu. the value is substituted at run time. Run a list of prompts that contains the prompt you want to delete. ¶ To delete multiple prompts that are not in a range. Select Delete from the pop-up menu.

Parameter Window 3. Tivoli Job Scheduling Console User’s Guide 277 . Run a list of parameters that contains the parameter you want to display. expand the scheduler tree. Prompts. 5. Managing Resources. Properties . When you have finished: ¶ Click OK to close the window and save the new parameter in the database. The name must start with a letter and can contain alphanumeric characters. enter the value assigned to the parameter. follow these steps: 1. The name can contain up to eight characters. Right-click the parameter list button and select Load List from the pop-up menu. Figure 156. and Parameters Displaying a List of Parameters To display a list of parameters in the database: 1. enter the name of the parameter. and underscores. The list results are displayed in the right pane of the Job Scheduling Console. 2. See “Displaying a List of Parameters” for more information. In the Name field. Displaying a Parameter To display a parameter in the database. In the tree view of the Job Scheduling Console. Do not include the names of other parameters. 21.Figure 155. 2. double-click the parameter you want to display or right-click the parameter and select Open from the pop-up menu. ¶ Click Cancel to close the window without saving the parameter in the database. 4. dashes. Parameter List Window The Name and Value columns show the names and values of the parameters. In the list results. In the Value field.

Click OK or on Cancel to close the window. A confirmation message is displayed for each parameter. 4. Choose Delete from the pop-up menu. then right-click one of the selected parameters. hold down the Shift key. 3. ¶ Click Cancel to close the window without saving the parameter in the database. 3. 3. Make your changes. Run a list of parameters that contains the parameter you want to modify. 4. click the first and last parameters in the range. This opens the parameter in the Properties . See “Displaying a List of Parameters” on page 277 for more information.1 . Deleting Parameters To delete parameters in the database: 1.This opens the parameter in the Properties . When you have finished: ¶ Click OK to save the parameter in the database and close the window. 2.Parameter window. For information about this window. hold down the Ctrl key. right-click the parameter. 2. Modifying a Parameter in the Database To modify a parameter in the database: 1. then right-click one of the selected parameters. Click OK to delete the parameter in the database or click Cancel to cancel the delete operation. double-click the parameter you want to modify or right-click the parameter and select Open from the pop-up menu. See “Displaying a List of Parameters” on page 277 for more information.Parameter window. click each parameter. 278 Version 8. ¶ To delete multiple parameters in a range. see “Creating a Parameter” on page 276. Run a list of parameters that contains the parameter you want to delete. In the list results. In the list results. For information about this window. do one of the following: ¶ To delete one parameter. ¶ To delete multiple parameters that are not in a range. see “Creating a Parameter” on page 276.

it displays a filtered list of objects in the plan.Group of Lists Window 4. Figure 157. In the Name field. Creating a Plan List of Workstations To create a plan list that displays workstations: 1. Click OK to close the window and save the new group. highlight the group you want to contain this list. starting with a letter. You can create groups to organize your lists. Creating a Group for Plan Lists To create a group for plan lists: 1. 2. highlight the group you want to contain this list. select the group and click Create a Group of Lists in the toolbar or right-click the existing group button and select Create Group from the pop-up menu.22.Group of Lists window is displayed. Properties . you give it a name and specify filtering criteria. From the scheduler branch. After installation there are a default set of basic plan lists in a group named Default Plan Lists. From the scheduler branch. The Properties . Each list you create is represented by an button in the tree view of the Job Scheduling Console. To create a group in an existing group. In the Job Scheduling view. enter the name of the list group. When you create a list. When you run a list. The name can contain up to 40 characters. 5. In the Job Scheduling view. expand the scheduler engine button. expand the scheduler engine button. Plan Tasks 22 Plan Tasks Using Plan Lists Plan lists display objects in the Workload Scheduler plan. Tivoli Job Scheduling Console User’s Guide 279 . Click Create a Group of Lists in the toolbar or right-click the scheduler engine button and select Create Group from the pop-up menu. 3. 2.

Domains Status List Window 4. 5. then Workstation from the pop-up menu. To filter the list results. The list results are displayed in the right pane of the Job Scheduling Console. ¶ Click Apply to run the list without closing the window. 6. Properties . The workstation and domain names can contain wildcard characters. Figure 159. Figure 158. enter a name for the list 280 Version 8. To have the list results refreshed automatically. The Properties . When you have finished: ¶ Click OK to save the list and close the window. 2. then Domain Statusfrom the pop-up menu. The Properties .Plan Workstation List window is displayed. 3. select Periodic Refresh and specify a refresh interval in seconds in the Period (secs) text box. Creating a Plan List of Domain Status To create a plan list to display domains: 1. enter a name for the list.1 . Right-click the scheduler engine button or group button and select Create Plan List. The list button is added to the group you selected.Plan Workstation List Window 4. Click List Workstations in Plan in the toolbar or right-click the scheduler engine button or group button and select Create Plan List . specify a workstation name in the Workstation Name text box and a scheduler domain name in the Domain Name text box. In the Name field.Domain Status List window is displayed. Properties . In the Job Scheduling view. From the scheduler branch. Leaving the text box blank results in an unfiltered list.3. highlight the group you want to contain this list. expand the scheduler engine button. In the Name field.

. When you have finished: ¶ Click OK to save the list and close the window. select Periodic Refresh and specify a refresh interval in seconds in the Period (secs) text box. highlight the group you want to contain this list. Name Enter this information ... 6. Properties . Leaving the text box blank results in an unfiltered list. 3. Properties .Job Stream Instance List General page is displayed.Job Stream Instance List General Page Use the information in Table 100 to create the list and filter the results. Click List Job Stream Instances in the toolbar or right-click the scheduler button and select Create Plan List. The Properties .22. Tivoli Job Scheduling Console User’s Guide 281 . In the Job Scheduling view. Plan Tasks 5. From the scheduler branch. Table 100. A name for the list.Job Stream Instance List General Information In this area . To filter the list results. General Page Figure 160. The list button is added to the group you selected. The domain name can contain wildcard characters. 2. expand the scheduler engine button. If you want the list results refreshed automatically. then Job Stream Instance from the pop-up menu. specify a domain name in the Domain Name text box. Creating a Plan List of Job Stream Instances To create a plan list of job stream instances: 1. ¶ Click Apply to run the list without closing the window.. The list results are displayed in the right pane of the Job Scheduling Console.

Period Refresh Options Enter this information .Job Stream Instance List General Information (continued) In this area .. Internal Status To use Workload Scheduler internal status to filter job stream instances.Table 100. Workstation Name Specify a workstation name. Only job streams with priorities within the range are displayed. High to select priority 100. where 101 is the highest priority. select this option and select the status type from the drop-down list. Properties .. Filter Criteria Select Time Restrictions in the left pane. or Go to select priority 101. Select the Periodic Refresh check box if you want the list results refreshed automatically and specify a refresh interval in seconds in the Period (secs) text box.1 .. Click Hold to select priority 0. The Time Restrictions page is displayed. Priority Use the From and To text boxes to specify a priority range of job streams to display. Possible priority values are 0 through 101.Job Stream Instance List Time Restrictions Page 282 Version 8. Status To use the Job Scheduling Console status to filter job stream instances. Job Stream Specify a job stream name. Time Restrictions Page Figure 161.. Properties . select this option and select the status type from the drop-down list.

The Dependencies page is displayed. Only job streams that start running within this range are displayed. To Date Use the Date and Time text boxes to specify the end of a range of time. A range for the start date and time of the job stream instances you want to display. Only job streams that finish running within this range are displayed. Dependencies Page Figure 162. Table 101. From Date Use the Date and Time text boxes to specify the beginning of a range of time.Job Stream Instance List Time Restrictions Information In this area . Specify a range for the finish date and time of the job stream instances you want to display.Job Stream Instance List Dependencies Page Tivoli Job Scheduling Console User’s Guide 283 . Properties .22. Only job streams that start running within this range are displayed.. From Date Use the Date and Time text boxes to specify the beginning of a range of time.. Plan Tasks Use the information in Table 101 to complete this window.. Only job streams that finish running within this range are displayed. Finish Time Select Dependencies in the left pane. Properties .. Start Time Enter this information . To Date Use the Date and Time text boxes to specify the end of a range of time.

¶ Click Apply to run the list without closing the window. enter an asterisk (*) in the File Dependency / File Name field and in the Prompt Dependency / Prompt Name field. Note: In this case. 3. specify the name of a workstation. The Properties . In the Prompt Number field. specify the name of a file. specify the number of a prompt. Note that all the fields in this window act as filters. Use the information in Table 102 to define the list of jobs from the plan. The name of a file dependency. specify the name of a resource. expand the scheduler engine button. then Job Instance from the pop-up menu. In the Workstation field. In the File Name field. For example.Use this window to define a list of jobs from the plan based on dependency types. The name of a prompt dependency. Properties . so that all fields specified must be valid for a job stream to be chosen for display. only job streams with both a file and a prompt dependency are displayed. The name of a job or job stream dependency. highlight the group you want to contain this list. Table 102..1 . In the Job Scheduling view. Alternatively. specify the name of a workstation. The name of a resource dependency. 2. In the Job field. to display all job streams with a file dependency. In the Workstation field. Resource Dependency File Dependency Prompt Dependency When you have finished: ¶ Click OK to save the list and close the window. From the scheduler branch.. Only job stream instances with the specified dependencies are displayed. you can right-click the scheduler engine button or group button and select Create Plan List. specify the name of a prompt. specify the name of a job stream. Creating a Plan List of Job Instances To create a plan list to display job instances: 1. Click the List Job Instances button on the toolbar. specify the name of a job. To display all job streams with both a file and a prompt dependency. The list button is added to the group you selected.. In the Workstation field.Job Stream Instance List Dependency Information In this area .. enter an asterisk (*) in the File Dependency / File Name field.Job Instance List General page is displayed. In the Resource field. specify the name of a workstation. In the Name field. In the Job Stream field. Job Streams with only prompt dependencies or only file dependencies are not displayed. Job/Job Stream Dependency Enter this information . The list results are displayed in the right pane of the Job Scheduling Console. 284 Version 8.

.Job Instance List General Page Use the information in Table 103 to create the list and filter the results. Properties . Plan Tasks General Page Figure 163.22. Properties .. Table 103. Name Period Refresh Options Enter this information . Tivoli Job Scheduling Console User’s Guide 285 . Select the Periodic Refresh check box if you want the list results refreshed automatically and specify a refresh interval in seconds in the Period (secs) text box... A name for the list.Job Instance List General Information In this area .

Recovery Options Select a job recovery option using the option buttons. where 101 is the highest priority. select this option and select the status type from the drop-down list. Priority Use the From and To text boxes to specify a priority range of job instances to display. Job Stream Specify a job stream. Job Name Specify a job name. High to select priority 100. Login Specify a login name. Valid options are Stop. Properties .1 . and None... Internal Status To use Workload Scheduler internal status to filter job instances. select this option and select the status type from the drop-down list. 286 Version 8. Workstation (Job Stream) Specify a workstation name. Select Time Restrictions in the left pane.Table 103. or Go to select priority 101.Job Instance List General Information (continued) In this area .. Only jobs with priorities within the range are displayed. The Restrictions page is displayed. Continue. Filter Criteria Enter this information . Possible priority values are 0 through 101. Click Hold to select priority 0.. Rerun. Status To use Job Scheduling Console status to filter job instances.

Tivoli Job Scheduling Console User’s Guide 287 .Job Instance List Time Restrictions Information In this area . Only job streams that finish running within this range are displayed. Properties ... Table 104. From Date Use the Date and Time text boxes to specify the beginning of a range of time. A range for the start date and time of the job instances you want to display. Finish Time Select Dependencies in the left pane. Only jobs that start running within this range are displayed.Job Instance List Time Restrictions Page Use the information in Table 104 to complete this window. Plan Tasks Time Restrictions Page Figure 164. To Date Use the Date and Time text boxes to specify the end of a range of time. Only jobs that finish running within this range are displayed. Only jobs that start running within this range are displayed. The Dependencies page is displayed. Specify a range for the finish date and time of the job instances you want to display.. Start Time Enter this information .22. To Date Use the Date and Time text boxes to specify the end of a range of time.. Properties . From Date Use the Date and Time text boxes to specify the beginning of a range of time.

only jobs with both a file and a prompt dependency are displayed. In the Job field. For example. The name of a resource dependency. Note: In this case. specify the name of a job stream. to display all jobs with a file dependency. specify the name of a workstation.. specify the name of a resource. In the Workstation field. In the Resource field. specify the name of a workstation.. Resource Dependency 288 Version 8. enter an asterisk (*) in the File Dependency / File Name field.Job Instance List Dependencies Window Use this window to define a list of jobs from the plan based on dependency types. Properties .Job Instance List Dependency Information In this area .. Job instances with only prompt dependencies or only file dependencies are not displayed. The name of a job or job stream dependency. Note that all the fields in this window act as filters. so that all fields specified must be valid for a job stream to be chosen for display. To display all jobs with both a file and a prompt dependency. In the Workstation field.. Properties .Dependencies Page Figure 165.1 . Table 105. Only job instances with the specified dependencies are displayed. Job/Job Stream Dependency Enter this information . enter an asterisk (*) in the File Dependency / File Name field and in the Prompt Dependency / Prompt Name field. specify the name of a job. Use the information in Table 105 to define the list of jobs from the plan. In the Job Stream field.

Leaving the text box blank results in an unfiltered list. The name of a prompt dependency. In the Resource Name field. In the Prompt Number field. The Properties . In the Workstation field. The list results are displayed in the right pane of the Job Scheduling Console. Plan Tasks Table 105.. The list button is added to the group you selected. you can right-click the scheduler engine button or group button and select Create Plan List.. 2.. Select Periodic Refresh if you want the list results refreshed automatically and specify a refresh interval in seconds in the Period (secs) field. From the scheduler branch. specify the name of a file. File Dependency Enter this information . Table 106.... Prompt Dependency When you have finished: ¶ Click Apply to run the list without closing the window. specify a workstation name. Name Periodic Refresh Options Enter this information . In the Name field. then Resource from the pop-up menu. Filter Criteria Tivoli Job Scheduling Console User’s Guide 289 . specify a resource name. In the File Name field.Plan Resource List window is displayed. Properties . The name of a file dependency. Alternatively. Figure 166. specify the name of a workstation.. In the Job Scheduling view. 3. ¶ Click OK to save the list and close the window.Plan Resource List Information In this area . highlight the group you want to contain this list. Creating a Plan List of Resources To create a plan list to display resources: 1.. expand the scheduler engine button. Click List Resources in Plan on the toolbar.Plan Resource List Window Use the information in Table 106 to complete this window.22. A name for the list. The resource name and workstation name can contain wildcard characters. In the Workstation Name field. Properties . specify the name of a prompt. specify the number of a prompt. Properties .Job Instance List Dependency Information (continued) In this area .

. Creating a Plan List of Prompts To create a plan list to display prompts: 1.Prompt Status List window is displayed. 2. Table 107. The list button is added to the group you selected. Select Periodic Refresh if you want the list results refreshed automatically and specify a refresh interval in seconds in the Period (secs) field. The Properties . Properties . From the scheduler branch. Figure 167.. Properties .1 .. Name Periodic Refresh Options Enter this information . 290 Version 8. then Prompt Status from the pop-up menu.When you have finished: ¶ Click Apply to run the list without closing the window. The list results are displayed in the right pane of the Job Scheduling Console. expand the scheduler engine button.Prompt Status List Window Use the information in Table 107 to complete this window. 3. In the Job Scheduling view. Right-click the scheduler engine button or group button and select Create Plan List. A name for the list.. ¶ Click OK to save the list and close the window. highlight the group you want to contain this list.Prompt Status List Information In this area .

In the Job Scheduling view. then File Status from the pop-up menu. The status values are: Asked The prompt has been asked. The Properties . highlight the group you want to contain this list. The prompt name can contain wildcard characters. 3. 2.. prompts with all status values are displayed. 5.File Status List window is displayed. Prompt Name To filter the list results. Plan Tasks Table 107.. The list results are displayed in the right pane of the Job Scheduling Console. Filter Criteria Enter this information . Type a name for the list in the Name field. ¶ Click OK to save the list and close the window.. expand the scheduler engine button. Right-click the scheduler engine button or group button and select Create Plan List. Leaving the text box blank results in an unfiltered list Status To filter the list using prompt status. specify a prompt name in the Prompt Name field.File Status List window. When you have finished: ¶ Click Apply to run the list without closing the window. Creating a Plan List of Files To create a plan list to display files: 1. Properties . If you want the list results refreshed automatically. Figure 168.. If no status values are selected. select Periodic Refresh and enter a refresh interval in seconds in the Period (secs) field. Answered No The prompt has been answered with a “no” response. Answered Yes The prompt has been answered with a “yes” response. but not answered.22. Properties . The list button is added to the group you selected. Not Asked The prompt has not been asked. Tivoli Job Scheduling Console User’s Guide 291 .Prompt Status List Information (continued) In this area . 4. use the Status check boxes to select the status values. From the scheduler branch.

Deleting a Plan List To delete a plan list: 1. Right-click the list button and select Delete from the pop-up menu. 3. 4.1 . Select the list button you want to modify. The list button is added to the group you selected. The list results are displayed in the right pane of the Job Scheduling Console. This displays the properties window for the list. 2. In the Job Scheduling view. 2. Make your modification in the properties window. 292 Version 8. ¶ Click OK to save the changes and to close the window. Select the list button you want to view in a detached window. Detaching a Plan List Display Detaching a list frees the right-window of the Job Scheduling Console to display other objects. click Yes to delete the list or Cancel to cancel the delete operation. Leaving the field blank results in an unfiltered list. In the Job Scheduling view. 2. Select the list button you want to delete. When you have finished: ¶ Click Apply to run the list without closing the window. enter a file name in the Filename field and a workstation name in the Workstation Name field. The list results are displayed in the right pane of the Job Scheduling Console. 3. In the Job Scheduling view. Right-click the list button and select Properties from the pop-up menu. Modifying the Properties of a Plan List To modify the properties of a plan list: 1. This displays the separate window for the list display. You can detach multiple lists to display several objects simultaneously. 3. expand the scheduler engine button. To detach a plan list display: 1. When you have finished: ¶ Click Apply to run the list without closing the window.6. In the confirmation window. In Workload Scheduler you can have up to seven detached windows at a time. ¶ Click OK to save the list and close the window. expand the scheduler engine button. expand the scheduler engine button. To filter the list results. Right-click the list button and select Detach View from the pop-up menu. The file name and workstation name can contain wildcards.

Tivoli Job Scheduling Console User’s Guide 293 . Plan Tasks Finding Objects in the Plan Find tools are provided in the Job Scheduling Console to help you find objects in the plan. The Find window remains open to let you to select other objects from the list.) located next to the text box where you type an object name. Selecting Stop stops the search. Any objects that have been found by the system until the Stop is clicked are displayed.). Click Start.. 4.. 3. In the following example of the Submit Job into Plan window. 2. The results of the search are listed in the lower part of the Find window. 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 search character string can contain wildcard characters.. Figure 170. Leaving the text box blank results in an unfiltered list. Select other filter criteria using option buttons and check boxes. The availability of the Find tool is shown by an ellipsis (.. Figure 169. the Job Name field provides a Find button (. ¶ Double-click the object in the list or click OK to insert the name of the object in the field in the parent window and close the Find window.22. Type a search character string in the available fields. The Stop button is displayed while the list is being generated. Example Find Window To use the Find window: 1. Example of a Find Button Clicking on the ellipsis opens a Find window.

Managing Job Instances in the Plan A job is a unit of work that is part of a job stream processed at a workstation. Set a job instance priority to 0. 2.. 294 Version 8.. priority levels. This button . Table 108 shows the commands that you can issue against a job instance in the plan.. user permissions. the internal status to HOLD. Job Instance Commands Use this command . View or modify the properties of a job instance. Forces the status of a job instance to SUCC or ABEND.. or deleting the dependencies and time restrictions on the job instance.. Right-click the job instance list button and select Load List from the pop-up menu.. command names. Stops a job instance. modifying. Is called . Rerun a job instance. Job definitions in Workload Scheduler include all necessary workstation and path locations. and recovery options necessary to successfully run a command or script file with no manual intervention. modify.. A job usually refers to a command or script file. login IDs. The Release command reverts a job instance priority to what it was before the Hold command ran. Releases all dependencies to this job instance.1 . Dependencies Hold Release Browse Job Log Rerun Cancel Job Kill Confirm Release All Dependencies Get Job Output Displaying a List of Jobs in the Plan To display a list of jobs in the plan: 1. expand the scheduler button. Moves the timeline display to the start time and day offset of the earliest job instance. This includes viewing. or delete the predecessors of a job instance. The toolbar in the job instance view contains two special buttons.. Table 108. In the Job Scheduling view. List View of Job Instances The List view provides a tabular display of job instances. Counteracts the Hold command. Go to Go to First And does this . add. Expand the branches below the scheduler until you see the button for the job instance list you want to run... View the STDLIST of a job instance that has completed running. Opens a read-only view of the job instance log. 3. file names. View. Properties To do this . The list results are displayed in the right pane of the Job Scheduling Console. Cancels the planned running of a job instance. and the Job Schedule Console status to HELD. adding. Moves the timeline display to the date you select on the popup calendar.

For more information on job or job stream status refer to “Status Description and Mapping” on page 387. The repeat rate for this job instance. For more information on job or job stream status refer to “Status Description and Mapping” on page 387.. The date. The priority of the job instance. The estimated run time of the job instance.. in hours and minutes. the job number is an incremental number from the value found in the file nxtjobno in TWShome.22. For Windows NT. A priority of 0 stops the job instance from running. The number of job dependencies for each job instance. Tivoli Job Scheduling Console User’s Guide 295 . time and time zone after which the job instance cannot begin running. For UNIX and MPE. The number of job stream dependencies for each job instance. The date. Internal Status Information Run Options Priority Every Frequency Start Time Est.. The run options of the job instance. Additional information about the job instance. this displays the process identification number (PAID) of the job instance. Duration Actual Time Elapse Time Deadline Time Job Stream Dep. Job Dep. The name of the job stream instance that owns this job instance. Job Instance List View Columns This column . time and time zone when this job instance is scheduled to start running. The actual start time of the job instance. Job Name Job Number Specifies . Table 109. The Job Scheduling Console status of the job instance. The name of the job instance. Workstation (Job) Job Stream Status Workstation (Job Stream) The name of the workstation on which the job stream instance runs.. Job Instance List View Window Table 109 describes the column headings in the table part of the List view. The priority can be from 0 to 101. The actual duration of the job instance. The Workload Scheduler internal status of the job instance. Plan Tasks Figure 171. The name of the workstation on which the job instance runs.

.. The date and time of the planned start time for the job instance. The number of prompt dependencies for each job instance. The actual duration of the job instance. The number of internetwork predecessors to this job. Name Status Started Runtime Start at Duration Deadline Specifies . The name of the job instance... the dark blue line represents the window of time a job instance can start. The number of file dependencies for each job instance.. A light blue bar within the dark blue line represents the actual duration of the job instance. The start time.. Table 110 describes the column headings in the table part of the Timeline view.Table 109. The actual start date and time of the job instance. The actual start time of the job instance is displayed by a black dot. The date and time of the deadline for the job instance. deadline time. The estimated duration time of the job instance. File Dep. Job Instance Timeline View Columns This column . and duration time are also listed in the tabular window. The number of resource dependencies for each job instance. Inet Dep...1 . 296 Version 8. Figure 172. Use the arrows at the top of the timeline window to move the view in one hour and one day increments. Specifies . Use the borders and the arrows on the borders to adjust the sizes of the windows. The status of the job instance. Prompt Dep. Table 110. Job Instance List: Timeline View window. In the timeline window. Job Instance List View Columns (continued) This column . For more information on job or job stream status refer to “Status Description and Mapping” on page 387. Timeline View of Job Instances The Timeline view provides a table and a timeline display of job instances. Resource Dep. A black bar at the end of the blue line represents the deadline time (UNTIL keyword).

. Properties . A priority value of zero prevents the job instance from launching. the job is a Windows NT script. High to select priority 100. The name of the workstation on which the job instance is launched.Job NT Script window. The number of times this job instance has been run in the production plan. Table 111. The name of the job stream this job instance belongs to. Login Priority The user ID of the person running the job instance. General Page Figure 173.. right-click a job instance and select Properties from the pop-up menu. The window that is displayed is therefore the Properties . The name of the job instance. select a value from the drop-down list or click Hold to select priority 0. The list results are displayed in the right pane of the Job Scheduling Console. Tivoli Job Scheduling Console User’s Guide 297 ..NT Script Instance General Page Table 111 describes the contents of this window. In this particular example. or Go to select priority 101. Possible priority values are 0 through 101. showing the General page.NT Script Instance General Information This area . Job Name Job Number Workstation (Job) Job Stream Specifies . 2. In the list results. Workstation (Job Stream) The name of the workstation on which the job stream instance is launched.. The priority of the job instance. Plan Tasks Modifying the Properties of a Job Instance To display the properties of a job instance in the plan: 1.22. where 101 is the highest priority. Right-click the job instance list button and select Load List from the pop-up menu. Properties . To change the priority.

298 Version 8. Whether this job instance has been rerun. The Workload Scheduler internal status of the job instance. This information appears only for Windows NT jobs.. The actual start time and duration of the job instance. For more information on job or job stream status refer to “Status Description and Mapping” on page 387. Additional information about the job instance.. Whether this job instance is an interactive job.Table 111. Continue. The Task page is displayed. Workstation Specifies the name of the workstation that owns the recovery job. Properties . or Rerun Specifies what action to take if this job instance ends with a status of ABEND (the job instance ends with an error). Start Time The actual start time of the job instance. if it has completed running. These fields display any automatic recovery action to be taken if the job instance ends with a status of ABEND. The Job Scheduling Console status of the job instance.1 .NT Script Instance window. Status Specifies .NT Script Instance General Information (continued) This area . This job instance will not be run in the plan until user intervention is used to submit it. Stop. For more information on job or job stream status refer to “Status Description and Mapping” on page 387... Internal Status Information Rerun Status Is Interactive Requires Confirmation Actuals Recovery Options Select Task in the left pane of the Properties . Message Specifies the message text that displays if the job instance ends with a status of ABEND. Job Name Specifies the name of an error recovery job that will run if the current job instance ends with a status of ABEND. Duration The actual duration of the job instance.

Plan Tasks Task Page Figure 174. and account for this MPE User Job. Properties . and account for this MPE job file.. Information about the Windows NT command: Command Displays the path and filename of the Windows NT command. Displays information about the MPE User Job: User Job Displays the filename. Properties .. group.22. Note: The fields in this window change according to the type of job instance displayed. Task Type UNIX Script UNIX Command Specifies .NT Script Instance Task Page Table 112 describes the contents of this window.NT Script Instance Task Information This area .. Information about the Windows NT script file: Script Displays the path and filename of the Windows NT script. Table 112. Displays information about the MPE Job File: Job File Displays the filename. group. Displays information about the extended agent task: Task Displays the filename or command for this extended agent task. Information about the UNIX command: Command Displays the path and filename of the UNIX command. NT Script NT Command MPE Job File MPE User Job Extended Agent Task Tivoli Job Scheduling Console User’s Guide 299 . The task type of the job instance. Information about the UNIX script file: Script Displays the path and filename of the UNIX script..

Job Name The R/3 job name. Workstation Class Command SAP Job Select Time Restrictions in the left pane of the Properties .. Displays information about the Workstation Class script file: Script Displays the path and filename of the Workstation Class script.. Job ID This field is filled in when you submit the job to the R/3 system. Displays information about the Workstation Class command: Script Displays the path and filename of the Workstation Class command..NT Script Instance Task Information (continued) This area . Workstation Class Script Specifies . Trace Indicates if a trace file dev_rfc is created in the Workload Scheduler home directory. Disable BDC Wait Indicates if BDC Wait option for the job is disabled Debug Options Indicates if additional debut information is included in the job’s stdlist file. Properties .Table 112. Time Restrictions Page Figure 175. The Time Restrictions page is displayed..Job Instance window.1 . Properties .NT Script Instance Time Restrictions Page 300 Version 8. Displays information about the SAP task: R/3 Job Identity Use these fields to identify the R/3 job.

. Date Specify the deadline date or click the calendar button and select a date from the drop-down calendar. Start Specifies . Time Zone Select a time zone from the drop-down list. Properties . Time Enter a start time in the following format: hh:mm am|pm For example. every 15 minutes from 1:00 pm to 5:00 pm.. Time Specify a deadline time in the following format: hh:mm am|pm For example. Using the Repeat Range field with the Start and Deadline times allows you to run a job instance.NT Script Instance Time Restrictions Information This area . Hours Enter the rate in hours that this job instance will repeat. Minutes Enter the rate in minutes that this job instance will repeat. The Files page is displayed. If a time zone is not specified for the job instance. Tivoli Job Scheduling Console User’s Guide 301 .. Table 113. The job instance will not be launched before this time. Date Enter the start date or click the calendar button and select a date from the drop-down calendar. Deadline Specifies the latest time the job instance will be launched. Repeat Range Select Files in the left pane of the Properties .22. 11:30 am or 4:25 pm.Job Instance window. all time values are in the time zone of the workstation on which the job instance is launched. Note that the time zone option must be activated in the global options file for this field to be active. make your selections as follows: Specify date and time Select this option so you can specify a deadline date and time. Specifies the repeat rate of a job instance. The start time and deadline time are in this time zone. for example. Plan Tasks Table 113 describes the contents of this window. The earliest time the job instance will be launched.. The job instance will not be launched after this time. make your selections as follows: Specify date and time Select this option so you can specify a start date and a start time. 11:30 am or 4:25 pm. To change the time. To change the time.

. Properties .NT Script Instance Files Information This column .NT Script Instance Files Page Table 114 describes the contents of this window... This creates a new row in the list of file dependencies. Exists The file dependency is satisfied. Filename Workstation Release Status Specifies . Released The job instance is released from the file dependency.1 . The workstation on which the file resides. The possible values are: Not Checked The file dependency has not been checked. To release the job instance from the file dependency. The path and name of the file. The status of the file dependency. 302 Version 8. The possible values are: Not Released The job instance is not released from the file dependency. The internal status of the file dependency. Does Not Exist The file dependency is not satisfied. Checking The file dependency is being checked. Qualifiers Internal Status To add a file dependency for the job instance: 1. Table 114. Click the Add Row (+) button.Files Page Figure 176. Properties . click in the Status column and select Released from the drop-down menu.. The test conditions for the file dependency.

True if the file exists and its size is greater than zero. For more information. Double-click the text box in the Qualifiers column and specify the test conditions for the file dependency. 3. Double-click the text box in the Filename column and type in a file name. Tivoli Job Scheduling Console User’s Guide 303 . On UNIX. Entering notempty is the same as entering -s %p. the valid qualifiers are the same as UNIX test command conditions. The Prompts page is displayed. True if the file exists and is readable. refer to your UNIX system documentation... the default is -f %p.NT Script Instance window. On both UNIX and Windows NT. True if the file exists and is writable. select the file row in the list and click the Delete from Table (X) button. On Windows NT. Plan Tasks 2. the expression %p inserts the file name. To remove a file dependency for the job instance. Select Prompts in the left pane of the Properties .) to locate and insert the name of the workstation on which the file exists or will be created. 4. True if the file exists and is a regular file. True if the file exists. only the following qualifiers are valid: -d %p -e %p -f %p -r %p -s %p -w %p True if the file exists and is a directory. Double-click the text box in the Workstation column and click the ellipsis (. If no qualifier is specified.22.

The release status of the prompt dependency. To display predefined prompt dependencies. The possible values are: Not Released The job instance is not released from the prompt dependency. 304 Version 8. select Predefined Prompt from the drop-down list in the toolbar.Prompts Page Figure 177. The workstation that displays the prompt message text. click in the Status column and select Released from the drop-down menu.NT Script Instance Prompts Page To display ad hoc prompt dependencies. For ad hoc prompts only. Properties . select Ad Hoc Prompt from the drop-down list in the toolbar.NT Script Instance Prompts Information This column . The number of the prompt dependency. Table 115 describes the contents of this window... The text of the prompt message.1 .. Table 115.. Properties . Name Message Text Workstation Number Release Status Specifies . The name of the prompt. Used for predefined prompts only. To release the job instance from the prompt dependency. Released The job instance is released from the prompt dependency.

the message is displayed but no reply is necessary.NT Script Instance window.NT Script Instance Prompts Information (continued) This column . double-click in the text box in the Message Text column and type in the text of the prompt. The possible values are: Not Asked The prompt has not been asked. If the string begins with a colon (:). place its name between carets (^). Internal Status Specifies . To use a parameter. Answered Yes The prompt has been answered affirmatively and the job instance dependency is released. Select Resources in the left pane of the Properties . select the prompt row in the list and click the Delete from Table (X) button. Asked The prompt has been asked. If the string begins with an exclamation mark (!). 3. Plan Tasks Table 115. the message is not displayed but it requires a reply.) to locate and insert the name of a prompt. The default behavior of a prompt is to display a message and wait for a reply.. To reply to the prompt. double-click the text box in the Name column and click the ellipsis (.. To remove a prompt dependency for the job instance.22. 2. You can include backslash n (\n) within the text for new lines. This creates a new row in the list of prompt dependencies. Click the Add Row (+) button. click in this column and select Yes or No from the drop-down menu. For a predefined prompt.. Tivoli Job Scheduling Console User’s Guide 305 . The internal status of the prompt dependency. The reply to the prompt dependency. but no response has been received.. Reply To add a prompt dependency for the job instance: 1. Properties . The Resources page is displayed. You can also include one or more Workload Scheduler parameters as part or all of the text string... For an ad hoc prompt. Answered No The prompt has been answered negatively and the job instance dependency is not released.

Click the Add Row (+) button. The number of units of a resource are needed by the job instance to satisfy the dependency. This creates a new row in the list of resource dependencies.NT Script Instance Resources Information This column . The workstation on which the resource resides.. Properties . To release the job instance from the resource dependency. The status of the resource dependency. The name of the resource. 3.. The possible values are: Not Released The job instance is not released from the resource dependency. click the ellipsis (. To add a resource dependency for the job instance: 1.NT Script Instance Resources Page Table 116 describes the contents of this window. Table 116. click in the Status column and select Released from the drop-down menu. Released The job instance is released from the resource dependency. The number of units of the resource that are currently available.. Resource Workstation Quantity Available Release Status Specifies ...Resources Page Figure 178. 306 Version 8.1 . Double-click in the text box in the Resource column and click Find to locate and insert a resource name. 2..) to locate and insert the name of a workstation. In the Workstation column. Properties .

The name of a predecessor job instance..22. Displaying Dependencies of a Job Instance To display the dependencies of a job instance. right-click the job instance you want to display and select Dependencies from the pop-up menu. Job Stream Job Workstation Specifies . Dependencies . Plan Tasks 4. select the resource row in the list and click the Delete from Table button. The default is one.NT Script Instance Successors Page Predecessors Page Table 117 describes the columns in the Predecessors page. in a list.. The Dependencies . When you have finished: ¶ Click Apply to save the changes you made to the properties and leave the window open. Predecessors Page This column .. Double-click in the text box in the Quantity column and specify the number of resource units required by the job instance. Table 117. Tivoli Job Scheduling Console User’s Guide 307 . You can display three types of dependency: ¶ Predecessors ¶ Internetwork predecessors ¶ Successors Figure 179. The name of a predecessor job stream instance or the job stream that owns the predecessor job. The workstation of the predecessor job or job stream.. ¶ Click OK to save the changes you made to the properties and close the window.Job Instance window is displayed. To delete a resource dependency for the job instance. ¶ Click Cancel to ignore any changes you made to the properties and close the window.

Release Status Internal Status Successors Page Table 119 describes the columns in the Successors page. Internal Status Internetwork Predecessors Page Table 118 describes the columns in the Internetwork Predecessors page. Internetwork Predecessors Page This column . The Workload Scheduler internal status of the predecessor job or job stream instance. The possible states are Released or Not Released. Table 119. The network agent workstation to which the predecessor belongs. ¶ Click OK to save your changes in the plan and close the window. For more information about job or job stream status. Network Agent Dependency Specifies . Not Released The job instance is not released from the predecessor dependency.. The release status of the Internetwork predecessors.. see “Status Description and Mapping” on page 387.Table 117.... and 40 for the job. The release status of the internetwork predecessors. When you have finished: ¶ Click Apply to save your changes in the plan and leave the window open. 308 Version 8. click in the Status column and select Released from the drop-down menu. The status of the predecessor dependency. The Workload Scheduler internal status of the predecessor job or job stream.1 . Release Status Specifies . The workstation to which the successor belongs. The possible states are Released or Not Released. 16 for the job stream.. The possible values are: Released The job instance is released from the predecessor dependency. The Workload Scheduler internal status of the successor job.... Table 118.. A freeform dependency or the job / job stream predecessor in the format workstation#jobstream. Adding Predecessors to a Job Instance To add a predecessor job or job stream to a job instance: 1. Successors Page This column ... The job stream to which the successor belongs. Workstation Job Stream Job Release Status Internal Status Specifies . The name of the successor job. The maximum length of this field is 120 for freeform characters or 16 for workstation.job. To release the job instance from the predecessor dependency. Predecessors Page (continued) This column .

Select the predecessor row in the list and click Delete from Table (X). 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. ¶ Click OK to save your changes in the plan and close the window. To specify a predecessor job stream instance. Run a list of job instances that contains the job you want to display. Holding a Single Job Instance To change a single job instance to Hold: 1. When you have finished: ¶ Click Apply to save your changes in the plan and leave the window open. refer to “Deleting Predecessors from a Job Instance”.Job Instance window is displayed. To specify a predecessor job instance. Displaying Successors of a Job Instance To display the successors of a job instance in the plan: 1. 2. When you have finished: ¶ Click Apply to save your changes in the plan and leave the window open. To display successor jobs and job streams. When you have finished: ¶ Click Apply to save your changes in the plan and leave the window open. In the list results. ¶ Click OK to save your changes in the plan and close the window. See “Displaying a List of Jobs in the Plan” on page 294 for more information. For descriptions of the column headings in the Successors view. This creates a new row in the list of predecessors. Use the Release command to change the priority back to its original level at the start of day. Deleting Predecessors from a Job Instance To delete a predecessor job or job stream from a job instance: 1. 2. right-click the job instance you want to display and select Dependencies from the pop-up menu. For information. ¶ Click OK to save your changes in the plan and close the window. Run a list of job instances that contains the job instance you want to modify. double-click in the text box in the Job Stream column and open a Find window to find the name of a predecessor job stream instance. Plan Tasks Display the predecessors of the job instance. 3. a. Holding a Job Instance Changing a job instance to Hold sets the priority of the job instance to 0. Click the Add Row button. Tivoli Job Scheduling Console User’s Guide 309 . click Successors in the left pane. See “Displaying a List of Jobs in the Plan” on page 294 for more information. see “Displaying Dependencies of a Job Instance” on page 307. 2.22. 3. Display the predecessors of the job instance. The Dependencies .

¶ To select multiple job instances. Run a list of job instances that contains the job instance you want to modify. Right-click one of the selected job instances to open the pop-up menu. Right-click the arrow next to the job instance group. Right-click the arrow next to the job instance group. Releasing a Job Instance The Release command reverses the Hold command. See “Displaying a List of Jobs in the Plan” on page 294 for more information. 3. Holding All Job Instances To hold all jobs in a group of job instances: 1. The Release command sets the priority of a job back to the original setting at the start of the processing day. hold down the control key and left-click on each job instance. 3. 310 Version 8. Select Release from the pop-up menu and click Yes in the confirmation window. 4. 4. Right-click on one of the selected job instances to open the pop-up menu. Right-click on one of the selected jobs to open the popup menu. To select more than one job instance. Run the list of job instances. hold down the control key and left-click on each job instance. 2. Right-click the job instance you want release. It has no effect on job dependencies. Right-click the job instance you want to hold. Click Hold All. hold down the shift key and left-click the first and last job instances in the range. Releasing All Job Instances To release all jobs in a group of job instances: 1. do one of the following: ¶ To select a range of job instances in the list. 4. 2. 3. Select Hold from the pop-up menu and click Yes in the confirmation window. Select All Scheduled Jobs Timeline View. Run the list of job instances. do one of the following: ¶ To select a range of job instances in the list.2. Do not confuse this command with Release All Dependencies.1 . Releasing a Single Job Instance To change a single job instance to Release: 1. Select All Scheduled Jobs Timeline View. 2. Click Release All. Select All Scheduled Jobs List View. hold down the shift key and left-click the first and last job instances in the range. Select All Scheduled Jobs List View. 3. Right-click one of the selected job instances to open the popup menu. ¶ To select multiple job instances. 4. To select more than one job instance.

Tivoli Job Scheduling Console User’s Guide 311 . To display this type of view . If you want to display more than one level of dependency. The Impact View window is displayed. Plan Tasks Showing Predecessors and Successors To show the predecessors of a job instance or its successors. then either Predecessors or Successors. then refresh the display.. Any dependent job instances are displayed... right-click a job instance and select Impact View from the pop-up menu. Impact View Window You can change the way the view is displayed by using the following buttons in the toolbar. you must right-click each dependent job instance in turn. right-click the job instance and select Dependencies from the pop-up menu.. selecting Dependencies from the pop-up menu each time. Radial Left Right Up Down Displaying Dependencies To display a dependency of a job instance.22. Only the first level of dependent job instances is displayed. Table 120. Impact View Options Select this button . Figure 180. only the first level of dependent job instances is displayed. Note: If you display dependencies for more than one job.

Select Browse Job Log from the pop-up menu. 2. The display is refreshed. right-click the job instance you want to rerun. Browsing the Job Log A job instance log file is created for each job instance launched by Workload Scheduler. To do this. showing the selected job instance as the root instance.Set as Root At any time. Job instance Log File Window 4. and errors and warnings. click Cancel to close the window. right-click the job instance you want to use as the root job instance and select Set As Root In New Frame from the pop-up menu. See “Displaying a List of Jobs in the Plan” on page 294 for more information. Run a list of job instances that contains the job instance you want to rerun. job instance. In the list results. you can reset the display using one particular job instance as the starting. To view the job instance log: 1. right-click the job instance you want to use as the root job instance and select Set As Root from the pop-up menu. echoed commands. 3. The job instance log file window is displayed.1 . Log files contain header and trailer banners. These files can be used to troubleshoot problems when jobs run. Figure 181. To reset the display in a separate window. When you have finished. 312 Version 8. or root.

Date Specify a start date for the job. The Rerun Job window is displayed. right-click the job instance you want to rerun.. click OK. The time zone option must be enabled for this field to be active. The workstation to run the job.. Run a list of job instances that contains the job instance you want to rerun. Time Specify a start time for the job.. A time zone for the job. To rerun a job instance: 1. 2. Specify Date and Time Select this checkbox to specify a start date and time for the job. Figure 182. Rerun Job Window Information In this area .. Use the information in Table 121 to complete this window. Otherwise. Select Rerun from the pop-up menu. Step From Workstation Name Start Time Enter this information . Plan Tasks Rerunning a Job Instance Note: You cannot rerun multiple job instances simultaneously. The step from which you would like to rerun this job. See “Displaying a List of Jobs in the Plan” on page 294 for more information.22. To rerun the job directly. Table 121. The new job instance will assume the name specified here. The start date and time for the job. In the list results. The job from which you want the job to run. add any additional options. 3. The following fields are only valid when using the From option: Time Zone Tivoli Job Scheduling Console User’s Guide 313 . Rerun Job Window 4.

where 101 is the highest priority. Priority Enter this information . ¶ To select multiple job instances. To cancel a job instance: 1. To select more than one job instance. High Sets the priority to 100. right-click the job instance you want kill. ¶ Click OK to save your changes in the plan and close the window. do one of the following: ¶ To select a range of job instances in the list. To kill a UNIX job instance: 1. Possible priority values are 0 through 101. hold down the shift key and left-click the first and last job instances in the range. 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. You cannot kill Windows NT job instances. The priority of the submitted job. Right-click one of the selected job instances to open the pop-up menu. Killing a Job Instance Killing a job instance can only be done for UNIX command and UNIX script jobs. 314 Version 8. 3. Right-click on one of the selected jobs to open the popup menu. 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. To change the priority. Run a list of job instances that contains the job instance you want to kill. hold down the control key and left-click on each job instance. Default Sets the priority to the default priority of the selected job. Right-click one of the selected job instances to open the popup menu. enter a value in the field or select one of: Hold Sets the priority to 0. To select more than one job instance.. Go Sets the priority to 101. Canceling a Job Instance Canceling a job instance in the plan prevents the job from running. right-click the job instance you want cancel. hold down the control key and left-click on each job instance. A canceled job instance can be submitted anytime during the production cycle using an alias name. Right-click on one of the selected job to open the pop-up menu. See “Displaying a List of Jobs in the Plan” on page 294 for more information. In the list results. ¶ To select multiple job instances. When you have finished: ¶ Click Apply to save your changes in the plan and leave the window open. In the list results.Table 121.1 . For more information. This job will not run until the priority is raised. 2. 2.. Select Cancel Job from the pop-up menu and click Yes in the confirmation window. A priority value of zero prevents the ad hoc job from launching.. see “Submitting a Job into the Plan” on page 336. Rerun Job Window Information (continued) In this area .

¶ To select multiple job instances. Select Release All Dependencies from the pop-up menu and click Yes in the confirmation window. then ABEND from the pop-up menu. ¶ To select multiple job instances. or if the job instance priority is below the fence for the workstation. Tivoli Job Scheduling Console User’s Guide 315 . Run a list of job instances that contains the job instance you want to release. right-click the job instance you want to confirm. Confirming a Job Instance SUCC or ABEND Confirming a job instance status as SUCC or ABEND allows you to force the job instance into a state where either its successors can continue processing or job recovery options are started. Select Confirm. 3. To select more than one job instance. Right-click on the selected job instance to open the pop-up menu. This allows the job instance to run unless there are other higher priority jobs waiting to run. Run a list of job instances that contains the job instance you want to confirm. Select Kill from the pop-up menu and select Yes in the confirmation box. hold down the shift key and left-click the first and last job instances in the range. To select more than one job instance. hold down the control key and left-click on each job instance. Plan Tasks 3. Releasing a Job Instance from Dependencies Releasing 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. do one of the following: ¶ To select a range of job instances in the list.22. This forces the status of the selected job instances to SUCC or ABEND. Right-click one of the selected job instances to open the pop-up menu. 4. See “Displaying a List of Jobs in the Plan” on page 294 for more information. Right-click one of the selected job instances to open the popup menu. In the list results. 2. 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. See “Displaying a List of Jobs in the Plan” on page 294 for more information. then SUCC or Confirm. 2. Right-click on the selected job instance to open the popup menu. This kills a currently running UNIX job. Select Yes in the confirmation box. hold down the control key and left-click on each job instance. right-click the job instance you want release. To confirm a job instance status to SUCC or ABEND: 1. 3. In the list results.

calendars. Right-click the job stream instance list button and select Load List from the pop-up menu. adding. the internal status to hold.. View or modify the job limit of a job stream instance. such as the use of run cycles. modifying.1 . or delete the predecessors of a job stream instance.. and time restrictions. In the Job Scheduling view. The dependency of one job on the completion of another determines the sequence of the jobs. Sets a job stream instance priority to 0. Counteracts the Hold command. The Release command reverts a job stream instance priority to what it was before the Hold command ran. and scheduling information. including the resources. Job Stream Instance Commands Use this command . View or modify the properties of a job stream instance. Submits a predefined or ad hoc job into the plan as part of the selected job stream instance. Dependencies Hold Release Impact View Cancel Limit Priority Release All Dependencies Re-submit Submit Select for Monitoring Deselect for Monitoring Displaying a List of Job Streams in the Plan To display a list of job stream instances in the plan: 1. See “Submitting Jobs and Job Streams into the Plan” on page 335. expand the scheduler button. and the Job Schedule Console status to held. Opens the job stream instance in the Job Stream Instance Editor. This includes viewing. and workstations that support them. The list results are displayed in the right pane of the Job Scheduling Console.Managing Job Stream Instances in the Plan A job stream is a sequence of jobs. Cancels the planned running of a job stream instance. 316 Version 8. determines when and how often the job stream instance is run. View or modify the priority of a job stream instance. Table 122. parameters. This is the number of jobs that can run concurrently in the job stream instance. Releases all dependencies to this job stream instance. The scheduling information.. Expand the branches below the scheduler button until you see the button for the job stream instance list you want to run. View the predecessors and successors of job stream instance. or deleting the dependencies and time restrictions on the job stream instance. Table 122describes the commands that you can use on a job stream instance in the plan. View. add.. Open Properties To do this . 2. 3. Specify that the running of this job is no longer to be monitored by Tivoli Business Systems Manager. Re-submits the job stream instance under an alias name. Specify that the running of this job is to monitored by Tivoli Business Systems Manager. modify. prompts.

The actual start date and time of the job stream instance. The date and time of the planned start time for the job stream instance. Plan Tasks Timeline View of Job Stream Instances The Timeline view provides a table and timeline display of job stream instances in the plan. Is called .. The actual start time of the job stream instance is displayed by a black dot. The estimated duration time of the job stream instance.22.. For more information on job or job stream instance status refer to “Status Description and Mapping” on page 387. The name of the job stream instance.. A black bar at the end of the blue line represents the deadline time (UNTIL keyword). Displays the actual duration of the job stream instance.. Table 123. Go to Go to First And does this . and duration time are also listed in the tabular window. Name Status Specifies . The status of the job stream instance. deadline time.. Table 123 describes the contents of this window. The date and time of the deadline for the job stream instance.. In the timeline window. the dark blue line represents the window of time a job stream instance can start. Use the arrows at the top of the timeline window to move the view in one hour and one day increments.... Job Stream Instances Timeline View Window This column . Moves the timeline display to the start time and day offset of the earliest job stream instance.. Use the borders and the arrows on the borders to adjust the sizes of the windows. Figure 183. The start time. Job Stream Instances Timeline View Window The toolbar in the job stream instance Timeline view contains two special buttons: This button . Started Runtime Start at Duration Deadline Tivoli Job Scheduling Console User’s Guide 317 . Moves the timeline display to the date you select on the popup calendar. A light blue bar within the dark blue line represents the actual duration of the job stream.

An button indicates the lowest status of the predecessors. The expected duration time of the job stream instance. Job Dep. The original name of the job stream instance. The Workload Scheduler internal status of the job stream instance. An button indicates the lowest status of the predecessors. The date and time of the job stream instance deadline. Additional information about the job stream instance.List View of Job Stream Instances The List view provides a table display of job stream instances. The name of the job stream instance. The number of predecessor jobs of the job stream instance.. Figure 184. For more information on job or job stream instance status refer to “Status Description and Mapping” on page 387. The total number of jobs in the job stream instance. Job Stream Instances List View Window This column . Duration Actual Duration Deadline Time Job Stream Dep. Internal Status Information Priority Num Jobs OK Jobs Limit Original Job Stream Scheduled Start Actual Start Est. The number of predecessor job streams for the job stream instance.. The name of the workstation on which the job stream instance runs. For more information on job or job stream status refer to “Status Description and Mapping” on page 387.. The priority of the job stream instance. Job Stream Instances List View Window Table 124 describes the contents of this window. The number of jobs that have completed successfully in the job stream instance The job limit of the job stream instance. Table 124. for job stream instances that were submitted with an alias name.1 . The actual duration time of the job stream instance. 318 Version 8.. The Job Scheduling Console status of the job stream instance. Job Stream Workstation Status Specifies . The date and time the job stream instance is scheduled to start running. The date and time the job stream instance started running.

Displaying and Changing the Properties of a Job Stream Instance To display the properties of a job stream instance in the plan: 1. The number of file dependencies of the job stream instance. The number of internetwork predecessors to this job stream. Prompt Dep.22. Properties . Inet Dep.. File Dep. Specifies . Tivoli Job Scheduling Console User’s Guide 319 . An button indicates the lowest status of the dependencies. The name of the job stream instance. General Page Figure 185.... In the list results... The original name of a job stream instance that was submitted with an alias name. Resource Dep. 2.Job Stream Instance General Information This area . Table 125. Plan Tasks Table 124. Run a list of job stream instances that contains the job stream you want to display. Job Stream Instances List View Window (continued) This column . An button indicates the lowest status of the dependencies. The Properties Job Stream Instance General page is displayed.Job Stream Instance General Page Table 125 describes the contents of this window. double-click the job stream instance you want to display or right-click the job stream instance and select Properties from the pop-up menu. Properties .. The number of prompt dependencies of the job stream instance. An button indicates the lowest status of the dependencies. Name Original Name Contains this information . The number of resource dependencies of the job stream instance..

320 Version 8. Properties .Table 125. The number of jobs that can be running at the same time in the schedule. Start Time The time and day the job stream instance started running. Possible priority values are 0 through 101.. Number Of Jobs Abended The number of job instances that have abended. Information about the timing of the job stream instance. For more information on job or job stream status refer to “Status Description and Mapping” on page 387.1 . Est. Information about the job instances in the job stream instance.Job Stream Instance General Information (continued) This area . Additional information about the job stream instance. Number of Failed Jobs The number of job instances that have failed to run. where 101 is the highest priority. Number of Jobs Not Run The number of job instances that have not run.. To change the job limit. The priority of the job stream instance. The Time Restrictions page is displayed. If you specify a job limit of 0. Number of Successful Jobs The number of job instances that have run successfully. no jobs within the job stream instance are launched. Number Of Jobs The total number of job instances. Duration Specifies the estimated duration of the job stream instance. The name of the workstation class on which the job stream instance is launched. High to select priority 100. The Workload Scheduler internal status of the job stream instance. Indicates this job stream instance is carried forward to the next processing day if it does not complete before the end of the current production day. select a value from the drop-down list or click Hold to select priority 0. To change the priority.. Number Of Executing Jobs The number of job instances that are running. Limit Status Internal Status Information Production Date Carry Forward Job Information Time Information Select Time Restrictions in the left pane. or Go to select priority 101. Runtime The duration of the job stream instance. A priority value of zero prevents the job stream instance from launching. The status of the job stream instance. Possible values are 0 through 1024. The name of the workstation on which the job stream instance is launched. The current date of the production cycle. For more information on job or job stream status refer to “Status Description and Mapping” on page 387.. select a value from the drop-down list. Workstation Name Workstation Class Name Priority Contains this information .

Job Stream Instance Time Restrictions Page Table 126 describes the contents of this window. To change the time. The job stream instance will not be launched before this time. Time Specify a start time in the following format: hh:mm am|pm For example.. To change the time. make your selections as follows: Specify date and time Select this option to enable the entry of a deadline time.. 11:30 am or 4:25 pm. The job stream instance will not be launched after this time.. Date Specify the deadline date or click the calendar button and select a date from the drop-down calendar. Plan Tasks Time Restrictions Page Figure 186. Properties . Properties . The earliest time the job stream instance will be launched. 11:30 am or 4:25 pm. Tivoli Job Scheduling Console User’s Guide 321 . Time Specify a deadline time in the following format: hh:mm am|pm For example.Job Stream Instance Time Restrictions Information This area . make your selections as follows: Specify date and time Select this option to enable the entry of a start time.22. Start Contains this information . Table 126. Date Specify the start date or click the calendar button and select a date from the drop-down calendar. Deadline The latest time the job stream instance will be launched..

.Job Stream Instance Files Page Table 127 describes the contents of this window. Select a time zone from the drop-down list. The status of the file dependency.. all time values are in the time zone of the workstation on which the job instance is launched.1 .Job Stream Instance Files Information This column . The possible values are: Not Released The job stream instance is not released from the file dependency. Note: The time zone option must be activated in the global options file for this field to be active Select Files in the left pane. Filename Workstation Release Status Specifies . Time Zone Contains this information . Properties . The test conditions for the file dependency. If a time zone is not specified for the job stream instance.. Qualifiers 322 Version 8.Table 126. click in the Status column and select Released from the drop-down menu. Released The job stream instance is released from the file dependency. The name of the file... The Files page is displayed. The workstation on which the file resides. Properties . The start time and deadline time are in this time zone.. To release the job instance from the file dependency.. Table 127..Job Stream Instance Time Restrictions Information (continued) This area . Properties . Files Page Figure 187.

Entering notempty is the same as entering -s %p. 3. On both UNIX and Windows NT. the default is -f %p.. the expression %p. Double-click in the text box in the Workstation column and open a Find window to locate and insert the name of the workstation on which the file exists or will be created.. select the file row in the list and click the Delete from Table button. True if the file exists and is readable. True if the file exists and is writable. Exists The file dependency is satisfied. True if the file exists. The Prompts page is displayed. only the following qualifiers are valid: -d %p -e %p -f %p -r %p -s %p -w %p True if the file exists and is a directory. The possible values are: Not Checked The file dependency has not been checked. 2. True if the file exists and is a regular file. Plan Tasks Table 127. Click the Add Row button. The internal status of the file dependency. Properties . For more information.. Tivoli Job Scheduling Console User’s Guide 323 . refer to your UNIX system documentation. On UNIX. This creates a new row in the list of file dependencies. Select Prompts in the left pane. 4. inserts the file name. Double-click in the text box in the Filename column and type in a file name.. Checking The file dependency is being checked. Does Not Exist The file dependency is not satisfied. Adding a File Dependency To add a file dependency for the job stream instance: 1. Removing a File Dependency To remove a file dependency for the job stream instance. True if the file exists and it’s size is greater than zero. the valid qualifiers are the same as UNIX test command conditions. On Windows NT. If no qualifier is specified.22. Internal Status Specifies .Job Stream Instance Files Information (continued) This column . Double-click in the text box in the Qualifiers column and specify the test conditions for the file dependency.

Table 128. The possible values are: Not Released The job stream instance is not released from the prompt dependency... The number of the prompt dependency.. The status of the prompt dependency.1 . The text of the prompt message. Table 128 describes the contents of this window. This is for ad hoc prompts only.Job Stream Instance Prompts Page Select the type of prompt you want to display. To release the job instance from the prompt dependency. click in the Status column and select Released from the drop-down menu. To display predefined prompt dependencies. Name Message Text Workstation Number Status Specifies . Properties . The name of the prompt. ad hoc or predefined.. The workstation that will display the prompt message. Properties . 324 Version 8. select Predefined Prompt from the drop-down list in the toolbar.Job Stream Instance Prompts Information This column . Released The job stream instance is released from the prompt dependency.Prompts Page Figure 188. To display ad hoc prompt dependencies. select Ad Hoc Prompt from the drop-down list in the toolbar. This column is for predefined prompts only.

2. Click the Add Row button. The Resources page is displayed. This creates a new row in the list of prompt dependencies. the message is displayed but no reply is necessary.. Properties . click in this column and select Yes or No from the drop-down menu. The possible values are: Not Asked The prompt has not been asked. For an ad hoc prompt. double-click in the text box in the Name column and use the Find tool to locate and insert the name of a prompt. The default behavior of a prompt is to display a message and wait for a reply. double-click in the text box in the Message Text column and type in the text of the prompt. To use a parameter. If the string begins with a colon (:). 3. Answered Yes The prompt has been answered affirmatively and the job stream instance dependency is released. If the string begins with an exclamation mark (!). You can also include one or more Workload Scheduler parameters as part or all of the text string. place its name between carets (^).Job Stream Instance Prompts Information (continued) This column . select the prompt row in the list and click the Delete from Table button. the message is not displayed but it requires a reply. Asked The has been asked. The reply to the prompt dependency. For a predefined prompt.22. Reply Adding a Prompt Dependency To add a prompt dependency for the job stream instance: 1.. Plan Tasks Table 128. Internal Status Specifies . Tivoli Job Scheduling Console User’s Guide 325 . but no response has been received. The internal status of the prompt dependency. Removing a Prompt Dependency To remove a prompt dependency for the job stream instance. Answered No The prompt has been answered negatively and the job stream instance dependency is not released. You can include backslash n (\n) within the text for new lines.. Select Resources in the left pane. To reply to the prompt..

1 . The number of units of the resource that are needed by the job stream instance to satisfy the dependency. 3. Adding a Resource Dependency To add a resource dependency for the job stream instance: 1... The name of the resource. This creates a new row in the list of resource dependencies. To release the job instance from the resource dependency. The default is one. Properties . 4.. The workstation on which the resource resides. Double-click in the text box in the Resource column and open a Find window to add a resource name. In the Workstation column. Resource Workstation Quantity Available Release Status Specifies . The status of the resource dependency. Properties . Table 129.. The possible values are: Not Released The job stream instance is not released from the resource dependency.Resources Page Figure 189. 326 Version 8. open a Find window to add the name of a workstation.Job Stream Instance Resources Window This column .Job Stream Instance Resources Page Table 129 describes the contents of this window. Click the Add Row button. Double-click in the text box in the Quantity column and specify the number of resource units required by the job stream instance. click in the Status column and select Released from the drop-down menu. Released The job stream instance is released from the resource dependency. 2. The number of units of the resource that are currently available.

22. Plan Tasks

Deleting a Resource Dependency
To delete a resource dependency for the job stream instance, select the resource row in the list and click the Delete from Table button. When you have finished: ¶ 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 Instance
To display the dependencies of a job stream instance, in a list, right-click the job stream instance you want to display and select Dependencies from the pop-up menu. The Dependencies - Job Stream Instance window is displayed. You can display three types of dependency: ¶ Predecessors ¶ Internetwork predecessors ¶ Successors The following figure shows the Predecessors page.

Figure 190. Dependencies Predecessors Page

Table 130 describes the contents of this window. Table 130. Dependencies - Job Stream Instance Predecessor Window
This column ... Job Stream Job Workstation Release Status Specifies ... The name of a predecessor job stream instance. Specifies the name of a predecessor job instance. Specifies the workstation of the predecessor job or job stream instance. Specifies the status of the predecessor dependency. The possible values are: Released The job stream instance is released from the predecessor dependency. Not Released The job stream instance is not released from the predecessor dependency. To release the job stream instance from the predecessor dependency, click in the Release Status column and select Released from the drop-down menu.

Tivoli Job Scheduling Console User’s Guide

327

Table 130. Dependencies - Job Stream Instance Predecessor Window (continued)
This column ... Internal Status Specifies ... Specifies the Workload Scheduler internal status of the predecessor job or job stream instance. For more information on job or job stream status refer to “Status Description and Mapping” on page 387.

When you have finished: ¶ 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 Stream Instance
To add a predecessor job or job stream to a job stream instance: 1. Display the predecessors of the job stream instance. For information, see “Displaying Dependencies 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 Job Stream column and click Find to locate and insert the name of the predecessor job stream instance. 4. To specify a predecessor job instance, double-click in the text box in the Job column and click Find to locate and insert the name of a predecessor job instance. When you have finished: ¶ 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.

Deleting Predecessors from a Job Stream Instance
To delete a predecessor job or job stream from a job stream instance: 1. Display the predecessors of the job stream instance. For information, see “Displaying Dependencies of a Job Stream Instance” on page 327. 2. Select the predecessor row in the list and click the Delete from Table (X) button. When you have finished: ¶ 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.

Displaying Successors of a Job Stream Instance
To 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 select Dependencies... 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 “Displaying Dependencies of a Job Stream Instance” on page 327.
328 Version 8.1

22. Plan Tasks

When you have finished: ¶ 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.

Holding a Job Stream Instance
Changing a job stream instance to Hold sets the priority of the job instance to zero. Use the Release command to change the priority back to its original level at the start of the processing 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 to modify. See “Displaying a List of Job Streams in the Plan” on page 316 for more information. 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 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 the selected job stream instances to open the popup menu. ¶ To select multiple job stream instances, hold down the control key and left-click each job stream instance. Right-click one of the selected job stream instances to open the popup menu. 4. Select Hold from the pop-up menu and click Yes in the confirmation window.

Releasing a Job Stream Instance
The Release command is used to cancel the Hold command. The Release command sets the priority back to the original setting at the start of the processing day. Do not confuse this command with the Release All Dependencies command. This command has no effect on job stream instance dependencies. To change a job stream instance to Release: 1. Run a list of job stream instances that contains the job stream instance you want to modify. See “Displaying a List of Job Streams in the Plan” on page 316 for more information. 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 more than 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 the selected job stream instance to open the popup menu. ¶ To select multiple job stream instances, hold down the control key and left-click each job stream instance. Right-click one of the selected job stream instances to open the popup menu. 4. Select Release from the pop-up menu and click Yes in the confirmation window.

Tivoli Job Scheduling Console User’s Guide

329

Showing Predecessors and Successors
To show the predecessors of a job instance or its successors, right-click a job stream instance and select Impact View from the pop-up menu, then either Predecessors or Successors. The Impact View window is displayed.

Figure 191. Impact View Window

You can change the way the view is displayed by using the following buttons in the toolbar. Table 131. Impact View Options
Select this button ... To display this type of view ... Radial Left Right Up Down

Canceling a Job Stream Instance
Canceling a job stream instance in the plan prevents the job stream instance from running. A canceled 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: 1. Run a list of job stream instances that contains the job stream instance you want to modify. See “Displaying a List of Job Streams in the Plan” on page 316 for more information. 2. In the list results, right-click the job stream instance you want cancel. To select more than 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 and left-click the first and last job stream instances in the range. Right-click one of the selected job stream instance to open the popup menu. ¶ To select multiple job stream instances, hold down the control key and left-click each job stream instance. Right-click one of the selected job stream instances to open the popup menu. 3. Select Cancel from the pop-up menu and click Yes in the confirmation window.

22. Plan Tasks

Changing the Job Limit of a Job Stream Instance
To 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 to modify. 2. In the list results, right-click the job stream instance you want modify. To select more than 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 the selected job stream to open the popup menu. ¶ To select multiple job stream instances, hold down the control key and left-click each job stream instance. Right-click one of the selected job stream instances to open the popup menu. 3. Select Limit from the pop-up menu. The Change Limit - Job Stream Instance window is displayed.

Figure 192. Change Limit - Job Stream Instance Window

4. Specify a new job limit in the New Limit field. When you have finished: ¶ 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 Instance
To change the priority of a job stream instance in the plan: 1. Run a list of job stream instances that contains the job stream instance you want to modify. See “Displaying a List of Job Streams in the Plan” on page 316 for more information. 2. In the list results, right-click the job stream instance you want modify or, to select more than 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 the selected job stream instance to open the popup menu.

Tivoli Job Scheduling Console User’s Guide

331

¶ To select multiple job stream instances, hold down the control key and left-click each job stream instance. Right-click one of the selected job stream instances to open the popup menu. 3. Select Priority from the pop-up menu. The Change Priority - Job Stream Instance window is displayed.

Figure 193. Change Priority - Job Stream Instance Window

4. Select a new priority value from the drop-down list or click of the following buttons: Table 132. Job Stream Instance Priorities
This button ... Hold High Go Default Sets the priority to ... 0 100 101 Original value (see note)

Note: If a single job stream instance is selected, Default sets the priority to the original value of the job stream instance at the start of the processing day. If multiple job stream instances are selected, the priority of each job stream instance is set back to what it was at start of the processing day. When you have finished: ¶ 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 Dependencies
Releasing a job stream instance from its dependencies removes dependencies on the following 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 one job stream instance, do one of the following:

332

Version 8.1

¶ 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 the selected job stream to open the popup menu. ¶ To select multiple job stream instances, hold down the control key and left-click each job stream instance. Right-click one of the selected job stream instances to open the popup menu. 2. Select Release All Dependencies from the pop-up menu and click Yes in the confirmation 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.

22. Plan Tasks

Re-submitting a Job Stream Instance
When you re-submit a job stream instance, a new job stream instance is created in the plan. The new job stream instance is given an alias name. 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 to re-submit. See “Displaying a List of Job Streams in the Plan” on page 316 for more information. 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 is displayed.

Figure 194. Re-Submit Job Stream Instance Window

4. Specify an alias name for the re-submitted job stream instance in the Alias field. If you do not specify an alias, a name is generated by Workload Scheduler. For unexpanded mode, Workload Scheduler starts with the first two characters of the original job stream instance name followed by six random numbers. For expanded mode, the scheduler starts with the first six characters of the original job stream instance name followed by ten random numbers. 5. When you are finished: ¶ Click OK to re-submit the job stream instance and close the window. ¶ Click Cancel to close the window without re-submitting the job stream instance. 6. To change the properties of the re-submitted job stream, click Properties.... For information about job stream instance properties, see “Displaying and Changing the Properties of a Job Stream Instance” on page 319.

Tivoli Job Scheduling Console User’s Guide

333

7. To change the predecessors for the re-submitted job stream, see “Adding Predecessors to a Job Stream Instance” on page 328 and “Deleting Predecessors from a Job Stream Instance” on page 328.

Submitting Jobs
For information about submitting jobs, see “Submitting Jobs and Job Streams into the Plan” on page 335.

Monitoring Jobs
To 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 Systems Manager, right-click the job stream instance and select Deselect for Monitoring.

334

Version 8.1

. You can submit jobs and job streams that have been previously defined to the database into the plan for impromptu processing. but are never saved in the database. Submit Job Stream into Plan Window 3. If an alias name is necessary. Job Stream Do this . This field is completed automatically when you select a job stream using the Find Job Stream window. This field is completed automatically when you select a job stream using the Find Job Stream window. To modify the properties of the submitted job stream. Use the information in Table 133 to complete the fields in this window. Right-click the scheduler engine button and select Submit then Job Stream from the pop-up menu. Workstation name Alias 4. expand the scheduler engine button. If the job or job stream is already in the plan and you would like to schedule it again. a name is generated by Workload Scheduler that starts with the first two characters of the original job stream name followed by six random characters. you can submit it with an alias. When you have finished: ¶ Click OK to submit the job stream and close the window. Tivoli Job Scheduling Console User’s Guide 335 . ¶ Click Cancel to close the window without submitting the job stream. The Submit Job Stream into Plan window is displayed. Figure 195. Submitting a Job Stream into the Plan To submit a job stream that already exists in the database into the plan: 1.. Specify an alias name for the submitted job stream instance. click the ellipsis to open a Find Job Stream window. An alias name is needed only if the plan contains a job stream instance of the same name. and you do not specify an alias.22. In the Job Scheduling view. see “Displaying and Changing the Properties of a Job Stream Instance” on page 319. 2.. You can also submit ad hoc jobs to the plan.. For information about job stream properties. These are jobs that have not been defined in the database. Plan Tasks Submitting Jobs and Job Streams into the Plan This section provides information for submitting jobs and job streams into the plan for impromptu processing. click Properties. These jobs are created and submitted into the plan. Submit Job Stream into Plan Window In this field . Table 133.

Use the information in Table 134 to complete this window. click the ellipsis (. Job Enter this information . 2.. Figure 196. Select Submit then Job from the pop-up menu.1 . In the Job Scheduling view.. right-click the scheduler engine button to display the Submit commands.) to display a Find Job window where you can search for and select a job to submit into the plan. Submit Job into Plan Window . Using a Default Job Stream To submit a job through a default job stream instance provided by Workload Scheduler: 1. Workstation The name of the workstation on which the job instance runs. Name The name of the job that you want to submit to the plan. the job is submitted through a default job stream instance named JOBS (see “Using a Default Job Stream”).. Table 134.. 336 Version 8.Submitting a Job into the Plan To submit a job that is defined in the database into a job stream instance. If you need to. the job is submitted through that specific job stream instance (see “Using a Specific Job Stream” on page 337).Default Job Stream 3. The Submit Job into Plan window is displayed.. Submit Job into Plan Window In this area .. If you submit the job from the pop-up menu of a specific job stream instance. Specifies the job to submit. you can use the job stream instance popup menu or the Workload Scheduler engine popup menu. This field is completed automatically when you select a job using the Find Job window. If you submit the job from the scheduler engine pop-up menu.

. Click the ellipsis (. Into Enter this information . You can specify a different workstation. click OK. The Submit Job into Plan window is displayed. An alias is needed only if JOBS contains another job of the same name. Job Stream Displays the name of the default job stream. Tivoli Job Scheduling Console User’s Guide 337 .. click on Properties.) to display a Find Job window where you can search for and select a job to submit into the plan. right-click a job stream instance and select Submit. Specifies the job stream through which the job is submitted. Using a Specific Job Stream To submit a job through a job stream instance that you select. in a list.. Workstation Write the name of the workstation on which the job instance runs.. then Job from the pop-up men.) to display a Find Workstation Instance window if you want to find a list of available workstations. ¶ If you want to submit the job and close the window. Workstation Displays the name of the workstation on which the job stream instance runs.. Alias 4. click the ellipsis (. An error message is displayed if JOBS already has a job instance of the same name. Submit Job into Plan Window Use the information in Table 135 to complete this window. If you need to. JOBS. Name Write the name of the job that you want to submit to the plan.22. An alias name for the submitted job..Specific Job stream In this area . Table 135. provided by Workload Scheduler... When you have finished: ¶ If you want to view or modify the properties of the job. Job Enter this information .. Submit Job into Plan Window (continued) In this area .. Specifies the job to submit. Submit Job into Plan Window . You cannot modify this. This field is completed automatically when you select a job using the Find Job window. Figure 197... See “Viewing or Modifying the Properties of the Job to Submit” on page 338 for details. Plan Tasks Table 134.

The Properties . before submitting it into the plan. click on Properties. click Properties in the Submit Job into Plan window. Displays read-only information about the job stream instance through which you are submitting the job: Job Stream The name of your selected job stream instance..1 .. An error message is displayed if you submit a job to a job stream instance that already has a job instance of the same name. See “Viewing or Modifying the Properties of the Job to Submit” for details.Table 135. click OK. General Page Figure 198. ¶ If you want to submit the job and close the window. Properties . An alias name for the submitted job.Specific Job stream (continued) In this area . Into Enter this information . An alias is needed only if the job stream through which the job is submitted contains another job of the same name. Submit Job into Plan Window .Job Instance General Page 338 Version 8. Viewing or Modifying the Properties of the Job to Submit To view or modify the properties of a job..Job Instance General page is displayed.. Alias When you have finished: ¶ If you want to view or modify the properties of the job. Workstation The name of the workstation that owns your selected job stream instance.

22. Into Task Type Alias Priority Tivoli Job Scheduling Console User’s Guide 339 . Name The name of the submitted job. High Sets the priority to 100. A priority value of zero prevents the ad hoc job from launching. 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. This job will not run until the priority is raised... The alias of the submitted job. To change the priority..Job Instance General Window This area . The task type of the submitted job. Table 136. Workstation The name of the workstation of the job stream. if defined. The priority of the submitted job. Workstation The name of the workstation of the job. Displays information about the job stream into which the job is submitted. Job Stream The name of the job stream into which the job is submitted. where 101 is the highest priority. Properties . enter a value in the field or select one of: Hold Sets the priority to 0. Displays information about the submitted job.. Plan Tasks Table 136 describes the contents of this window. Job Specifies .

The text can contain up to 64 characters. If the string begins with an exclamation mark (!).1 . Properties . the message is not displayed but it requires a reply. Job The name of a recovery job to run if the parent job ABENDs.. Requires Confirmation Select this option to indicate that job completion must be confirmed by the operator. Follow these guidelines: ¶ If either workstation is an extended agent.. ¶ The recovery job’s workstation must be in the same domain as the parent job’s workstation. If the string begins with a colon (:). Displays information about the recovery options of the submitted job.. It can be Stop. 340 Version 8. Recovery Options Specifies .. The name of the workstation on which the recovery job runs. The Task page is displayed. it must be hosted by a domain manager or a fault-tolerant agent that runs in Full Status mode. Not all jobs are eligible to have recovery jobs run on a different workstation. Message The text of a recovery prompt. Action The recovery action for the submitted job. ¶ If the recovery job’s workstation is a fault-tolerant agent. The default behavior of a prompt is to display a message and wait for a reply. Recovery jobs are run only once for each ABENDed instance of the parent job. the message is displayed but no reply is necessary.Table 136. Workstation Select Task in the left pane of the window.Job Instance General Window (continued) This area . it must run in Full Status mode. The name is entered automatically when you select a recovery job. or Rerun. Continue. To change the name. click Find and select a job from a list.

These fields are read only. These fields display the task type. The Time Restrictions page. Properties . Properties . and the command or script file referenced by the job. Select Time Restrictions in the left pane of the window.22. path. Time Restrictions Page Figure 200. Plan Tasks Task Page Figure 199.Job Instance Task Page The Task page is different for each type of job and operating system.Job Instance Time Restrictions Page Tivoli Job Scheduling Console User’s Guide 341 .

Table 137 Table 137. see “Enabling Time Zones in the Workload Scheduler” on page 385. To change the time: Specify date and time Select this option to enable the entry of a start time. Repeat Range Select Files in the left pane of the window. Deadline The latest time the job will be launched. specify the time zone in which the job runs. Start Specifies .Job Instance Time Restrictions Window This area ... The repetition rate of the job. For more information about the time zone feature. Minutes The value can be 00 to 59. To change the time: Specify date and time Select this option to enable the entry of a deadline time. Time Specify a start time in the following format: hh:mm am|pm For example. The earliest time the job will be launched. The job will not be launched after this time.. The job will not be launched before this time. 11:30 am or 4:25 pm. Date Specify a start 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 For example.. The Files page is displayed 342 Version 8. Properties . Time Zone If the Time Zone option is enabled. Date Specify the deadline date or click the calendar button and select a date from the drop-down calendar.1 . Make your selections as follows: Hours The value can be 00 to 23. 11:30 am or 4:25 pm. The start time and deadline time are in this time zone. The job is launched multiple times at this rate.

. The test conditions for the file dependency. This field is read-only for submitted jobs. The possible values are: Not Checked The file dependency has not been checked. Properties . Plan Tasks Files Page Figure 201.. Properties .Job Instance Files Page Table 138 describes the contents of this window. Internal Status Tivoli Job Scheduling Console User’s Guide 343 . Does Not Exist The file dependency is not satisfied.. Filename Workstation Qualifiers Release Status Specifies . The path and name of the file. Released The job stream instance is released from the file dependency. The possible values are: Not Released The job stream instance is not released from the file dependency. Table 138. The status of the file dependency. Exists The file dependency is satisfied.22. The internal status of the file dependency. Checking The file dependency is being checked. The workstation on which the file resides.Job Instance Files Window This column ..

3. This creates a new row in the list of file dependencies. b. c. only the following qualifiers are valid: -d %p -e %p -f %p -r %p -s %p -w %p True if the file exists and is a directory. True if the file exists and it’s size is greater than zero. Double-click in the text box in the Filename column and type in a file name. the valid qualifiers are the same as UNIX test command conditions. the default is -f %p. the expression %p inserts the file name. True if the file exists and is writable. If no qualifier is specified. Select Prompts in the left pane of the window. Notes: a. For more information. 344 Version 8. On UNIX.Adding a File Dependency To add a file dependency for the job: 1. Entering notempty is the same as entering -s %p. The Prompts page is displayed. Click the Add Row button. refer to your UNIX system documentation. On Windows NT. Removing a File Dependency To remove a file dependency for the job. True if the file exists and is readable. On both UNIX and Windows NT. Double-click in the text box in the Qualifiers column and specify the test conditions for the file dependency. 2. True if the file exists and is a regular file. select the file row in the list and click the Delete from Table button.1 . 4. True if the file exists. Double-click in the text box in the Workstation column and open a Find window to find the name of the workstation on which the file exists or will be created.

Properties .. Released The job instance is released from the prompt dependency. Yes The prompt has been answered affirmatively and the job dependency is released. Message Text Workstation Number Release Status Specifies . The reply to the prompt dependency. Internal Status Reply Tivoli Job Scheduling Console User’s Guide 345 .. Plan Tasks Prompts Page Figure 202. The possible values are: Not Asked The prompt has not been asked. No The prompt has been answered negatively and the job dependency is not released. Table 139. The text of the prompt message. Ad Hoc Prompt Dependencies This column . The internal status of the prompt dependency. The status of the prompt dependency. The workstation that displays the prompt message text.. but no response has been received. Asked The prompt has been asked.. The possible values are: Not Released The job instance is not released from the prompt dependency. This field is read-only for submitted jobs. select Ad Hoc Prompt from the drop-down list in the toolbar.Job Instance Prompts Page Displaying Ad Hoc Prompt Dependencies To display ad hoc prompt dependencies. Table 139 describes the contents of the window. The internal Workload Scheduler ID number of the prompt dependency.22.

.. place its name between carets (^). The possible values are: Not Released The job instance is not released from the prompt dependency. The default behavior of a prompt is to display a message and wait for a reply. The name of the prompt. The text of the prompt message. 2. This field is read-only for submitted jobs. Internal Status Reply Adding a Prompt Dependency To add a prompt dependency for the job instance: 1. the message is not displayed but it requires a reply. select Predefined Prompt from the drop-down list in the toolbar. Released The job instance is released from the prompt dependency. For an ad hoc prompt. Click the Add Row button. Table 140. Removing a Prompt Dependency To remove a prompt dependency for the job. For a predefined prompt. The internal status of the prompt dependency. Asked The has been asked. To use a parameter. select the prompt row in the list and click the Delete from Table button. but no response has been received. Predefined Prompt Dependencies This column . Name Message Text Number Release Status Specifies . If the string begins with a colon (:). You can include backslash n (\n) within the text for new lines. The reply to the prompt dependency.Displaying Predefined Prompt Dependencies To display predefined prompt dependencies. 346 Version 8. To reply to the prompt. This creates a new row in the list of prompt dependencies. 3. If the string begins with an exclamation mark (!)... click in this column and select Yes or No from the drop-down menu. The internal Workload Scheduler ID number of the prompt dependency. The possible values are: Not Asked The prompt has not been asked. The Resources page is displayed. No The prompt has been answered negatively and the job dependency is not released. Yes The prompt has been answered affirmatively and the job dependency is released. You can include one or more Workload Scheduler parameters as part or all of the text string. double-click in the text box in the Name column and click Find to locate and insert the name of a prompt.1 . Table 140 describes the contents of the window. the message is displayed but no reply is necessary. Select Resources in the left pane of the window. The status of the prompt dependency. double-click in the text box in the Message Text column and type in the text of the prompt.

Properties .Job Instance Resources Window This column .22.. The possible values are: Not Released The job instance is not released from the resource dependency.. The status of the resource dependency. The name of the resource. Table 141. 4.Job Instance Resources Page Table 141 describes the contents of this window. Plan Tasks Resources Page Figure 203. Double-click in the text box in the Workstation column and click Find to locate and insert the name of a workstation. Double-click in the text box in the Name column and click Find to locate and insert a resource name. 2. The default is one. Adding a Resource Dependency To add a resource dependency for the job instance: 1. Resource Workstation Quantity Available Release Status Specifies . This creates a new row in the list of resource dependencies.. This field is read-only for submitted jobs. Properties . Tivoli Job Scheduling Console User’s Guide 347 . The workstation on which the resource resides. Double-click in the text box in the Quantity column and specify the number of resource units required by the job instance. 3. The number of units of the resource that are currently available. Released The job instance is released from the resource dependency.. Click the Add Row button. The number of units of the resource that are needed by the job to satisfy the dependency.

.. Table 142. This creates a new row in the list of predecessors.1 . 2. For more information on job or job stream status refer to “Status Description and Mapping” on page 387.. The name of the predecessor job stream. The Predecessors page is displayed. 348 Version 8. double-click in the text box in the Job column and click Find to locate and insert a resource name. Properties . double-click in the text box in the Job Stream column and click Find to locate and insert the name of a job stream. Predecessors Page Figure 204. select the resource row in the list and click the Delete from Table button. The status of the predecessor job or job stream. 3. The name of the predecessor job stream’s workstation. To specify a predecessor job stream..Job Instance Predecessors Page Table 142 describes the contents of this window. The name of job in the predecessor job stream. The Workload Scheduler internal status of the predecessor job or job stream.Deleting a Resource Dependency To delete a resource dependency for the job instance. Properties . Click the Add Row button. Job Stream Job Workstation Release Status Internal Status Specifies . Select Predecessors in the left pane of the window. To specify a predecessor job.Job Instance Predecessors Window This column . Adding a Predecessor To add a predecessor for the job instance: 1.

To submit a job that is defined in the database into a job stream instance. ¶ Click Cancel to close the window without submitting the job. 3. you use the job stream instance popup menu or the scheduler engine popup menu. then Ad Hoc from the pop-up menu. When you have finished: ¶ Click OK to submit the job and close the window. Submit Ad Hoc Job into Plan Window 2. In the Task Type field. Plan Tasks Deleting a Predecessor To delete a predecessor for the job instance. The Submit Ad Hoc Job into Plan window is displayed.22. Submitting an Ad Hoc Job into the Plan To submit an ad hoc job (a job that is not defined in the database) into a job stream instance. Click OK to specify the properties of this submitted ad hoc job. Tivoli Job Scheduling Console User’s Guide 349 . right-click a job stream instance and select Submit. you use the scheduler engine pop-up menu. To submit an ad hoc job into a job stream instance: 1. Figure 205.Job Instance General page is displayed. In a list. select the predecessor row in the list and click the Delete from Table button. select the task type of the ad hoc job. The Properties .

General Page Figure 206. Workstation Specify the name of the workstation of the ad hoc job. For the JOBS job stream.. The task type of the submitted ad hoc job. The UNIX or Windows NT user ID that launches the ad hoc job. Into Task Type Login 350 Version 8..Job Instance General Page Use the information in Table 143 to complete this window. if necessary. Alias Specify an alias name for the ad hoc job. Properties . Displays information about the ad hoc job.Job Instance General Window In this area .. Displays information about the job stream into which the ad hoc job is submitted. Job Stream Specify the name of the job stream for the ad hoc job.1 . Job Enter this information .. the Properties Job Instance window job instance will be submitted into the JOBS job stream on the workstation for the job specified in the field above. Properties . The workstation for this job stream instance is only displayed when the Submit > Ad Hoc command was invoked from the Job Stream Instance list. Table 143.

Workstation Displays the name of the workstation on which the recovery job runs. where 101 is the highest priority. Requires Confirmation Select this option to indicate that ad hoc job completion must be confirmed by the operator. The name is entered automatically when you select a recovery job. Continue. Recovery jobs are run only once for each abended instance of the parent ad hoc job. High Sets the priority to 100. ¶ The recovery job’s workstation must be in the same domain as the parent job’s workstation. If the string begins with a colon (:). This job will not run until the priority is raised. ¶ If the recovery job’s workstation is a fault-tolerant agent.. Interactive jobs are for Windows NT only. Specify whether this is an interactive job or not. the message is displayed but no reply is necessary. Priority Enter this information . The default behavior of a prompt is to display a message and wait for a reply.22. or Rerun. the message is not displayed but it requires a reply. it must run in Full Status mode. Properties . click the Find button and select a job from a list. Displays information about the recovery options of the submitted ad hoc job. The priority of the submitted job. enter a value in the field or select one of: Hold Sets the priority to 0. Message Specify the text of a recovery prompt. The text can contain up to 64 characters. It can be Stop. Follow these guidelines: ¶ If either workstation is an extended agent.. A priority value of zero prevents the ad hoc job from launching. it must be hosted by a domain manager or a fault-tolerant agent that runs in Full Status mode. Job Displays the name of a recovery job to run if the parent job abends.. Not all jobs are eligible to have recovery jobs run on a different workstation. Plan Tasks Table 143. Is Interactive Recovery Options Select Task in the left pane of the window.. Action Displays the recovery action for the submitted ad hoc job. The Task page is displayed. To change the priority.Job Instance General Window (continued) In this area . If the string begins with an exclamation mark (!). Default Sets the priority to the default priority of the selected job. Possible priority values are 0 through 101. Go Sets the priority to 101. To change the name. Tivoli Job Scheduling Console User’s Guide 351 .

For non-expanded databases. the field can contain up to 255 characters. Properties . it can contain up to 4095 characters. 352 353 353 353 353 353 UNIX Script and NT Script Complete the Script field as follows: Specify the name of the file the ad hoc job runs. UNIX Script and NT Script UNIX Command and NT Command MPE Job File MPE User Job Extended Agent SAP Job Go to page .. Do not specify files on mapped drives. If the file name contains spaces. Enter the file name and any options and arguments.Job Instance Task Page The Task view is different for each task type. other than slashes (/) and backslashes (\). Task Types For this task type .. For Windows NT ad hoc jobs. For expanded databases.1 . include the file extensions. the entire string must be enclosed in quotes (″). Universal Naming Convention (UNC) names are permitted. If spaces or special characters are included.. 352 Version 8.Task Page Figure 207.. To complete the fields and select options on this page: Table 144. specify the name in another file that does not have spaces in its name and use the second file’s name in this field.

specify the name of the command the ad hoc job runs. For example. The name can contain wildcard characters. For example. ¶ Click Start to display a list of parameter names. The Time Restrictions page is displayed. Extended Agent In the Task field. MPE User Job Complete the User Job field by specifying the name from the JOB card of the MPE job. The name can contain wildcard characters. it can contain up to 4095 characters. JFILE4.JCL. Tivoli Job Scheduling Console User’s Guide 353 . ¶ Select a parameter name in the list click OK. Select Time Restrictions in the left pane of the window. A parameter can be used for all or part of the field and multiple parameters are permitted. To include a parameter in the Command field: ¶ Place the cursor in the Command field where you want to insert the parameter and click Add Parameter. $userjob=UJOB5. Commands are run directly and the jobmanrc standard configuration script is not run. the field can contain up to 255 characters. ¶ Specify a parameter name in the Find field. ¶ Specify a parameter name in the Find field. ¶ Click Start to display a list of parameter names. UNIX Command and NT Command In the Command field. enter the XAgent script path or file name or the XAgent command for this job. A parameter can be used for all or part of the field and multiple parameters are permitted.22. ¶ Select a parameter name in the list click OK. ¶ The Find Parameters window is displayed. Specify the command name and any options and arguments.CORP. For non-expanded databases. MPE Job File Complete the Job File field by specifying the name of the MPE file the ad hoc job runs. Plan Tasks To include a parameter in the Script field: ¶ Place the cursor in the Script field where you want to insert the parameter and click Add Parameter. refer to the Tivoli Workload Scheduler Extended Agent for SAP/R3 User’s Guide for information about defining the task. ¶ The Find Parameters window is displayed. Click Add Parameter to add a predefined parameter to the task specification SAP Job For task type SAP Job. For expanded databases.

354 Version 8. Properties .Time Restrictions Page Figure 208. The earliest time the ad hoc job will be launched. 11:30 am or 4:25 pm.1 . The ad hoc job will not be launched after this time. Time Specify a start time in the following format: hh:mm am|pm For example.. Properties . 11:30 am or 4:25 pm.. Table 145. Start Enter this information . To change the time: Specify date and time Select this option to enable the entry of a start time.Job Instance Time Restrictions Page Use the information in Table 145 to complete this window. Date Specify the deadline date or click the calendar button and select a date from the drop-down calendar.Job Instance Time Restrictions Window In this area .. Deadline The latest time the ad hoc job will be launched. Date Specify the start date or click the calendar button and select a date from the drop-down calendar.. To change the time: Specify date and time Select this option to enable the entry of a deadline time. The ad hoc job will not be launched before this time. Time Specify a deadline time in the following format: hh:mm am|pm For example.

Repeat Range Select Files in the left pane of the window. refer to “Enabling Time Zones in the Workload Scheduler” on page 385. The workstation on which the file resides..22. Properties . Plan Tasks Table 145. Properties . specify the time zone in which the ad hoc job runs. The test conditions for the file dependency. The Files page is displayed. Properties . The path and name of the file. The value can be 00 to 23. The repetition rate of the ad hoc job. If the Time Zone option is enabled. For more information about the time zone feature.. The start time and deadline time are in this time zone. Filename Workstation Qualifiers Specifies . To make your selections: Hours Specify the hours. Tivoli Job Scheduling Console User’s Guide 355 .Job Instance Files Window This column . Files Page Figure 209. Time Zone Enter this information . Table 146..Job Instance Time Restrictions Window (continued) In this area .. Minutes Specify the minutes.. The value can be 00 to 59.. The ad hoc job is launched multiple times at this rate...Job Instance Files Page Table 146 describes the contents of this window.

b. Properties . the default is -f %p. 4. True if the file exists and is readable.1 . inserts the file name. Exists The file dependency is satisfied. Select Prompts in the left pane of the window. This field is read-only for submitted job instances. On both UNIX and Windows NT.Table 146. Does Not Exist The file dependency is not satisfied.. Checking The file dependency is being checked. Released The ad hoc job is released from the file dependency. only the following qualifiers are valid: -d %p -e %p -f %p -r %p -s %p -w %p Notes: a. True if the file exists and is a regular file.. On Windows NT.Job Instance Files Window (continued) This column . For more information. The Prompts page is displayed. refer to your UNIX system documentation. True if the file exists and is writable. the expression %p. On UNIX. Double-click in the text box in the Qualifiers column and specify the test conditions for the file dependency. Double-click in the text box in the Filename column and type in a file name. Internal Status Adding a File Dependency To add a file dependency for the ad hoc job: 1. Click the Add Row button. select the file row in the list and click the Delete from Table button. Removing a File Dependency To remove a file dependency for the ad hoc job. This creates a new row in the list of file dependencies. The status of the file dependency. If no qualifier is specified.. 356 Version 8. True if the file exists. Release Status Specifies . Double-click in the text box in the Workstation column and click Find to add the name of the workstation on which the file exists or will be created. 3. The possible values are: Not Checked The file dependency has not been checked. the valid qualifiers are the same as UNIX test command conditions.. The internal status of the file dependency. True if the file exists and is a directory. 2. True if the file exists and it’s size is greater than zero. The possible values are: Not Released The ad hoc job is not released from the file dependency. c. Entering notempty is the same as entering -s %p.

This field is read-only for submitted job instances. Table 147...22. but no response has been received.Job Instance Prompts Page Displaying Ad Hoc Prompt Dependencies Ad hoc prompt dependencies are displayed by default when the Prompts page is displayed. The text of the prompt message. The workstation that displays the prompt message text.. The status of the prompt dependency. Message Text Workstation Number Release Status Specifies . Internal Status Reply Tivoli Job Scheduling Console User’s Guide 357 . Ad Hoc Prompt Dependencies This column . Table 147 describes the contents of this window. The reply to the prompt dependency.. Yes The prompt has been answered affirmatively and the ad hoc job dependency is released. Asked The has been asked. This field is read only for submitted job instances. The possible values are: Not Asked The prompt has not been asked. The possible values are: Not Released The ad hoc job instance is not released from the prompt dependency. The internal status of the prompt dependency. The internal Workload Scheduler ID number of the prompt dependency. No The prompt has been answered negatively and the ad hoc job dependency is not released. Plan Tasks Prompts Page Figure 210. Properties . Released The ad hoc job instance is released from the prompt dependency.

This field is read only for submitted job instances. The status of the prompt dependency. This creates a new row in the list of prompt dependencies.Displaying Predefined Prompt Dependencies To display predefined prompt dependencies... For an ad hoc prompt. 2. The name of the prompt. You can also include one or more Workload Scheduler parameters as part or all of the text string. The reply to the prompt dependency. place its name between carets (^). select Predefined Prompt from the drop-down list in the toolbar. but no response has been received. select the prompt row in the list and click the Delete from Table button. The Resources page is displayed 358 Version 8. Removing a Prompt Dependency To remove a prompt dependency for the ad hoc job. The text of the prompt message. Select Resources in the left pane of the window. Released The ad hoc job instance is released from the prompt dependency. The possible values are: Not Asked The prompt has not been asked. Table 148 describes the contents of this window. Table 148. This field is read only for submitted job instances. The possible values are: Not Released The ad hoc job instance is not released from the prompt dependency. If the string begins with an exclamation mark (!).1 . For a predefined prompt.. the message is not displayed but it requires a reply. Internal Status Reply Adding a Prompt Dependency To add a prompt dependency for the ad hoc job instance: 1. No The prompt has been answered negatively and the job dependency is not released. double-click in the text box in the Message Text column and type in the text of the prompt. If the string begins with a colon (:). The default behavior of a prompt is to display a message and wait for a reply. The internal status of the prompt dependency. To use a parameter. Asked The has been asked. You can include backslash n (\n) within the text for new lines. 3. Predefined Prompt Dependencies This column . Click the Add Row button. Yes The prompt has been answered affirmatively and the job dependency is released.. The internal Workload Scheduler ID number of the prompt dependency. double-click in the text box in the Name column and click Find to locate and insert the name of a prompt. the message is displayed but no reply is necessary. Name Message Text Number Release Status Specifies .

The name of the resource..22. Tivoli Job Scheduling Console User’s Guide 359 . Resource Workstation Quantity Available Release Status Specifies ... Released The job instance is released from the resource dependency. Double-click in the text box in the Quantity column and specify the number of resource units required by the ad hoc job instance.Job Instance Resources Page Table 149 describes the contents of this window. Double-click in the text box in the Workstation column and click Find to add the name of a workstation. This field is read-only for submitted job instances.. 4. Click the Add Row button. The number of units of the resource that are currently available. Adding a Resource Dependency To add a resource dependency for the ad hoc job instance: 1. Plan Tasks Resources Page Figure 211. The status of the resource dependency. The possible values are: Not Released The job instance is not released from the resource dependency. The default is one. 2. Properties . The number of units of the resource that are needed by the ad hoc job to satisfy the dependency. This creates a new row in the list of resource dependencies. Properties . Table 149. Double-click in the text box in the Name column and click Find to add a resource name.Job Instance Resources Window This column . 3. The workstation on which the resource resides.

double-click in the text box in the Job Stream column and click Find to locate and insert the name of a job stream. select the resource row in the list and click the Delete from Table button. Predecessors Page Figure 212. Properties . The Workload Scheduler internal status of the predecessor job or job stream.Job Instance Predecessors Information This column . The Predecessors page is displayed. The name of the predecessor job stream’s workstation.Job Instance Predecessors Page Table 150 describes the contents of this window. 360 Version 8. Properties . 2. The name of the predecessor job stream. double-click in the text box in the Job column and click Find to locate and insert a resource name.Deleting a Resource Dependency To delete a resource dependency for the ad hoc job instance.1 .. Click the Add Row button. Select Predecessors in the left pane of the window... The status of the predecessor job or job stream. Adding a Predecessor To add a predecessor for the ad hoc job instance: 1. This creates a new row in the list of predecessors.. Job Stream Job Workstation Release Status Internal Status Specifies . Table 150. For more information on job or job stream status refer to “Status Description and Mapping” on page 387. To specify a predecessor job. 3. The name of job in the predecessor job stream. To specify a predecessor job stream.

Figure 213. ¶ Click Cancel to close the window without submitting the ad hoc job. When you have finished: ¶ Click OK to submit the ad hoc job and close the window. and unlink a workstation Displaying a List of Workstations in the Plan To display a list of workstations in the plan: 1. Table 151.22. stop. ¶ Change the job limit of a workstation instance ¶ Change the job fence of a workstation instance ¶ Start. link.. The workstation instance name. Name Shows . Expand the Default Plan lists group. In the Job Scheduling view. Plan Tasks Deleting a Predecessor To delete a predecessor for the ad hoc job instance. Right-click on the Status of All Workstations button and select Load List from the pop-up menu. This list contains a number of fields with information about the workstation status. Managing Workstations in the Plan The plan contains a list of all workstations that are going to be used in that days processing. select the predecessor row in the list and click the Delete from Table button. You can perform the following actions on a workstation in the plan: ¶ Display a list of workstations in the plan. expand the scheduler engine button... Workstation Status List Window Table 151 describes the contents of this window. Tivoli Job Scheduling Console User’s Guide 361 . Workstation Status List Window This column . The list results are displayed in the right pane of the Job Scheduling Console. 3.. 2.

Valid values are from 0 to 101. Whether or not the jobbing process on the workstation is running. Other Other workstation OS. The job fence for this workstation. MPV MPE/V. The node name of the workstation Node Displaying a Workstation Instance To display a workstation instance in the plan: 362 Version 8.. A workstation can either be LINKED or UNLINKED. MPX MPE/IX. The type of workstation and the type operating system of the workstation in the following format: os_wkstat where os is one of the following: WNT Windows NT. and where wkstat is one of the following: FTA Fault-tolerant agent Master Master Manager Domain manager S-Agent Standard agent X-Agent Extended agent Time Zone Node Port CPU Type Host Run Start Time Jobman Init Method Domain Version Node Information Node Name The time zone of the workstation. UNX UNIX. This is only valid for Extended Agents and Network agents. Workstation Status List Window (continued) This column . The method name. Whether or not the jobman process on the workstation has completed its startup initialization..Table 151. Operating system information about the workstation. SAGENT or XAGENT. The current link status of the workstation. The date and time the batchman process was started on the workstation. The scheduler physical workstation that is hosting this workstation definition. if this workstation is an extended agent or network agent workstation.. This is used synchronize the workstations in a scheduler network. Jobman Running Link Status Limit Fence Shows . The port address of the workstation. The scheduler workstation type.. The value can be either YES or NO. FTA. Valid values are MASTER. prevents jobs with priorities of 40 or less from being launched. The total number of jobs that can be run concurrently on this workstation. The version of Workload Scheduler installed on this workstation.1 . The job fence is the priority a job must exceed to run on this workstation. Setting the fence to 40. for example. The name of the Workload Scheduler domain of the workstation. The run number of the production plan of the workstation.

Right-click one of the selected workstations to open the popup menu.Workstation in Plan window is displayed. 3. Plan Tasks 1. See “Displaying a List of Workstations in the Plan” on page 361 for more information. The Properties .22. hold down the shift key and left-click the first and last workstations in the range. Run a list of workstations in the plan that contains the workstation you want to modify. 2. to select more than one workstation. 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. see “Displaying a List of Workstations in the Plan” on page 361. Run a list of workstations that contains the workstation you want to display. In the list results. When you have finished: ¶ Click OK to save your changes and close the window. 2. Figure 214. For more information. hold down the control key and left-click on each workstation. right-click a workstation and select Properties from the pop-up menu. Tivoli Job Scheduling Console User’s Guide 363 . do one of the following: ¶ To select a range of workstations in the list. Changing the Job Limit of a Workstation in the Plan To change the job limit of a workstation instance in the plan: 1. ¶ Click Cancel to close the window without saving your changes.Workstation in Plan Window For descriptions of the field values. ¶ To select multiple workstations. right-click the workstation you want to modify or. Properties . In the list results. Select Limit from the pop-up menu. You can change the Limit and Fence values by entering new values in the fields. 3. Right-click on one of the selected workstations to open the popup menu.

hold down the control key and left-click on each workstation. Starting a Workstation Instance To start Workload Scheduler running on a workstation instance. or. Figure 215. When you have finished. ¶ To select multiple workstations. 2. right-click the workstation you want to modify. Select Fence from the pop-up menu. Change Fence .Workstation window is displayed. Changing the Job Fence of a Workstation in the Plan To change the job fence of a workstation instance in the plan: 1. ¶ Click OK to save the new job fence in the plan and close the window. Right-click on one of the selected workstations to open the popup menu. Note: To start all the workstations in a domain. refer to “Starting the Workstations in a Domain” on page 366.Workstation Window 4. Change Limit . 3. Right-click each of the selected workstations to open the popup menu. do one of the following: ¶ To select a range of workstations in the list.1 . The Change Fence . ¶ Click Cancel to close the window without saving the new job fence. hold down the shift key and left-click the first and last workstations in the range. Specify a new job limit in the New Limit field. ¶ Click Cancel to close the window without saving the new job limit.Workstation window is displayed.The Change Limit . In the list results. When you have finished: ¶ Click OK to save the new job limit in the plan and close the window. Run a list of workstation instances that contains the workstation you want to modify. right-click the workstation you want to start and select Start from the pop-up menu. in a list of workstations. Specify a new job fence or click of the following buttons: Hold None Sets the fence to 0. Figure 216. to select more than one workstation. 364 Version 8.Workstation Window 4. Hold All Sets the fence to 101.

Make sure you specify the path name of the home directory of the installed user. right-click the workstation you want to stop and select Link from the pop-up menu. when you start a workstation. follow these steps: 1. If your home directory is linked to another file system. Plan Tasks Missing or Incorrect Components Occasionally. Managing Domains in the Plan You can perform the following actions on domains in the plan: ¶ Display a list of domains.22. expand the scheduler engine button. Expand the Default Plan Lists group. Note: To unlink all of the workstations in a domain. 3. Tivoli Job Scheduling Console User’s Guide 365 . create a copy of the components file in the /usr/unison/components directory. modify the contents to match what is installed. Unlinking a Workstation Instance To unlink a workstation instance. or the entry in the /usr/unison/component file is incorrect (location incorrect). Note: To stop all of the workstations in a domain. 2. make sure both references are listed in the file. ¶ Start. and link a workstation in a domain. Displaying a List of Domains in the Plan To display a list of domains in the plan. 4. in a list of workstations. ¶ Change the domain manager workstation in a domain. Stopping a Workstation Instance To stop Workload Scheduler running on a workstation instance. Click Load List on the toolbar or right-click the domain list button and select Load List from the pop-up menu. refer to “Stopping the Workstations in a Domain” on page 366. To fix the problem. right-click the workstation you want to stop and select Stop from the pop-up menu. In the Job Scheduling view. This is because either the location for the components file is not the default and the variable $UNISON_COMPONENT_FILE is not set. an error message might be displayed because of a missing or incorrect components file entry. If one already exists. Linking a Workstation Instance To link a workstation instance. refer to “Unlinking the Workstations in a Domain” on page 366. Select a Status of All Domains list button. right-click the workstation you want to stop and select Unlink from the pop-up menu. stop. This list contains a number of fields with information about the domain status.

Select Stop Workstations from the pop-up menu. In the list results. Table 152 describes the column headings in the domain display. Run a list of domains that contains the domain you want to unlink. In the list results. right-click the domain you want to link. 3. See “Displaying a List of Domains in the Plan” on page 365 for more information. The name of the parent domain. see “Unlinking a Workstation Instance” on page 365. Linking the Workstations in a Domain To link all of the workstations in a domain: 1. Starting the Workstations in a Domain To start Workload Scheduler running on all of the workstations in a domain: 1. see “Stopping a Workstation Instance” on page 365. 3. Select Start Workstations from the pop-up menu. 3.. 2. Note: To start individual workstations. 2. Name Domain Manager Domain Parent Specifies . In the list results. 366 Version 8. right-click the domain you want to unlink. Select Unlink Workstations from the pop-up menu. Note: To unlink individual workstations.The list results are displayed in the right pane of the Job Scheduling Console. 2.. 2.. See “Displaying a List of Domains in the Plan” on page 365 for more information. see “Starting a Workstation Instance” on page 364. 3. The name of the domain manager workstation.. Table 152. The name of the domain. see “Linking a Workstation Instance” on page 365. List of Domains in the Plan This column .1 . See “Displaying a List of Domains in the Plan” on page 365 for more information. right-click the domain you want to stop. Stopping the Workstations in a Domain To stop Workload Scheduler running on all of the workstations in a domain: 1. Run a list of domains that contains the domain you want to start. right-click the domain you want to start. Note: To stop individual workstations. Note: To link individual workstations. Select Link Workstations from the pop-up menu. Unlinking the Workstations in a Domain To unlink all of the workstations in a domain: 1. Run a list of domains that contains the domain you want to stop. Run a list of domains that contains the domain you want to link. In the list results. See “Displaying a List of Domains in the Plan” on page 365 for more information.

expand the scheduler engine button. right-click the domain and select Switch Manager. See “Creating a Plan List of Files” on page 291 for information about creating file lists. ensure the new domain manager is a fault-tolerant agent with Full Status and Resolve Dependencies selected.Domain Window 3. In the list results. See “Displaying a List of Domains in the Plan” on page 365 for more information. Plan Tasks Switching the Domain Manager in a Domain When switching domain managers to a backup domain manager. Expand the branches below the scheduler until you see the button for the file list you want to run. Run a list of domains that contains the domain you want to switch. Select the Status of All Files list button. Displaying File Dependencies Status To display a list of file dependencies in the plan: 1. 4. Figure 217. 2. Expand the Default Plan Lists group. In the Job Scheduling view. When you have finished: ¶ Click OK to switch to the new domain manager and close the window. The list results are displayed in the right pane of the Job Scheduling Console. 3.. from the pop-up menu. 5.. Switch Manager . 2. Select the file list button. Tivoli Job Scheduling Console User’s Guide 367 .22. Click Find and use the Find window to select the name of the new domain manager workstation. ¶ Click Cancel to close the window without switching the domain manager. Click Load List on the toolbar or right-click on the file list button and select Load List from the pop-up menu. This displays the Select Domain Manager window. Managing File Dependencies in the Plan A file dependency is when a job or job stream needs to verify the existence of one or more files before it can run. The new domain manager must be a member of the domain and it must be a fault-tolerant agent with Full Status and Resolve Dependencies selected. To switch the domain manager to a different workstation in a domain: 1.

4. Expand the Default Plan Lists group. Any qualifiers used with this file dependency. 2. Does Not Exist The file does not exist or is not available. Click Load List on the toolbar or right-click on the prompt list button and select Load List from the pop-up menu. Status of All Files List Window This column . The list results are displayed in the right pane of the Job Scheduling Console.. Full Path Name Workstation Qualifiers Status Specifies .. The status of the file as one of the following: Not Checked Not yet checked or the file was available and used to satisfy a job or job stream dependency.. Table 153. In the Job Scheduling view. Exists The file exists and is available. Status of All Files List Window Table 153 describes the column headings in the file display. Managing Prompt Dependencies in the Plan A prompt dependency is when a job or job stream needs to wait for an affirmative response to a prompt before it can run. Select the Status of All Prompts list button. expand the scheduler engine button.Figure 218. 3. The path and name of the file..1 . Displaying Prompt Dependencies Status To display a list of prompt dependencies in the plan: 1. Checking File availability is being checked. The name of the workstation that owns the file. 368 Version 8.

Resources can be physical or logical. hold down the shift key and left-click the first and last prompt dependencies in the range. databases. it can be used as a dependency for jobs and job streams that run on the workstation or workstation class for which the resource is defined.. See “Displaying Prompt Dependencies Status” on page 368 for more information. The internal ID of the prompt. After defining a resource in the Workload Scheduler database.. Name Workstation Dependency Release Status Specifies . right-click the prompt dependency you want to reply to or. In the list results. Tivoli Job Scheduling Console User’s Guide 369 . Recovery The prompt option.22. YES The prompt has been issued and a YES response has been received. Prompt Dependencies Status This column . NO The prompt has been issued and a NO response has been received. but no response has been received. ¶ To select multiple prompt dependencies. The jobs or job stream names that are dependent on this prompt. or Reply then No from the pop-up menu. In the Job Scheduling view. do one of the following: ¶ To select multiple prompt dependencies from the list. that are needed to run a job. 3. Plan Tasks Table 154 describes the contents of the columns in the prompt display. Right-click one of the selected prompt dependencies to open the popup menu. The text of the prompt. to select more than one prompt dependency.. communication lines. or printers. This is one Ad Hoc The prompt Predefined The prompt database. 2. expand the scheduler engine button. The prompt type. This is one of: ASKED The prompt has been issued. Table 154. has a name and is defined in the is locally defined in a job as a recovery Number Type Message Text Replying to a Prompt Dependency To reply to a prompt dependency: 1. hold down the control key and left-click each prompt dependency. The name of a predefined prompt or the number of an ad hoc prompt. Run a list of prompt dependencies that contains the prompt you want to modify. Managing Resource Dependencies in the Plan Resources represent any type of resources on your system such as tape drives. Select Reply then Yes.. NOT ASKED The prompt has not been issued. of: is locally defined in a job or job stream. Right-click one of the selected prompt dependencies to open the popup menu. The status of the prompt. Displaying Resource Dependencies Status To display a list of resource dependencies in the plan: 1. The name of the workstation.

. See “Displaying Resource Dependencies Status” on page 369 for more information. Specify a new value in the Quantity Defined text box.. See “Creating a Plan List of Resources” on page 289 for information about creating resource lists. 2. Table 155. 4. ¶ Click Cancel to close the window without saving your changes. 4. In the list results. When you have finished: ¶ Click OK to save your changes and close the window.Resource in Plan window is displayed. The resource has no units available. Expand the branches below the scheduler until you see the button for the resource list you want to run. The names of job and job stream instances that require units of the resource and the number of units required. The status of the Available Not Available Unknown resource.Resource in Plan window is displayed. 2. you can change the total number of defined units of the resource. Quantity Defined Quantity Available In Use Holders The total number of units defined for the resource. The number of resource units that are currently in use. Displaying the Properties of a Resource Dependency To display a resource dependency in the plan: 1. Name Workstation Status Specifies . The number resource units that are not in use. In this window.2. In a list of resource dependencies. To do this. This is one of: The resource has units available.1 . When you have finished: 370 Version 8. The name of the resource. The list results are displayed in the right pane of the Job Scheduling Console.. The Change Units . specify a new value in the Quantity Defined field. Select the resource list button. Run a list of resource dependencies that contains the resource you want to modify. right-click the resource you want to modify. Click Load List on the toolbar or right-click on the resource list button and select Load List from the pop-up menu. 3. The Properties . The status of the resource is unknown. Changing the Number of Units of a Resource Dependency To change the total number of defined units of a resource dependency: 1. Select Change Units from the pop-up menu. Resource Dependencies Status This column . 3.. The name of the workstation. right-click the resource and choose Properties from the pop-up menu. Table 155 describes the contents of the columns in the resource display.

The log number indicating the chronological order of the log files. The time file began running.. The name of the file assigned by the scheduler. Tivoli Job Scheduling Console User’s Guide 371 . The run number assigned to the file by Workload Scheduler. Set Alternate Plan Files Window This column . The date the file was scheduled to run. Figure 219. The size of the log file.. You can browse all objects in the alternate plan. This is used for internal network synchronization.. The Set Alternate Plan Files window is displayed. 22. The date the file began running. ¶ Click Cancel to close the window without saving the new units. but you cannot modify them. Plan Tasks Setting an Alternate Plan You can use the Set alternate plan function to set an old plan so that all the lists at plan level refer to the selected plan. Table 156. such as jobs and job streams.¶ Click OK to save the new units in the plan and close the window. Set Alternate Plan Files Window Table 156 describes the columns in this window. in records.. right-click the scheduler button and select Set alternate plan from the pop-up menu. Schedule Date Actual Date Log Date Start Time Run Number Log Number Size Filename Specifies this . To select a different plan to use: ¶ In the Job Scheduling view. The date the file was logged.

¶ Select the plan you want to use. ¶ Click OK. You return to the Job Scheduling view. 372 Version 8.1 .

IV — Appendixes Tivoli Job Scheduling Console User’s Guide 373 .

1 .374 Version 8.

you should use the plan lists for that engine. If you want to. However. the two common plan lists are defined with no filters. Like all default lists. you can create additional common plan lists that use particular filters.A Using Common Lists If your Job Scheduling view includes multiple scheduling engines. Unlike similar lists for specific engines. Common plan lists provide fewer details about the job and job stream instances than engine-specific plan lists. these lists display all the job and job stream instances that exist in all the engines to which the Job Scheduling Console is connected. common plan lists are limited to job and job stream instances. Using Common Lists Tivoli Job Scheduling Console User’s Guide 375 . or if you want to see more information about the instances of a specific engine. you can list job stream instances and job instances for more than one engine at a time. In the Job Scheduling view. the Common Default Plan Lists group appears at the bottom of the job scheduling tree. The group provides two predefined lists. This also applies if you have a mixed environment of Workload Scheduler for z/OS and Workload Scheduler engines. regardless of the number of connections that you might have. one for job instances and one for job stream instances. 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. such as a particular status or a subset of all the engines. If you are connected to a single engine. The group always appears in the Job Scheduling tree.

in the Job Scheduling view.Job Instance Common List Window 376 Version 8. double-click Common Default Plan Lists. Double-click All Scheduled Jobs. Figure 220. The Properties . select Common Default Plan Lists and click the List Job Instances button. In the Job Scheduling view. 2.Creating a Common List of Job Instances Listing All Job Instances To list all the job instances existing in all the scheduling engines: 1.Job Instance Common List window is displayed.1 . Properties . Using Filter Criteria To create a list of job instances with different filter criteria. The All Scheduled Jobs list is displayed in the right pane of the Job Scheduling view.

. Use wildcards to help your search. Properties . Note: To display the list at a later date. Status Lists all the job instances with any of the following Job Scheduling Console status codes that you specify in the drop-down list: ¶ Waiting ¶ Ready ¶ Running ¶ Successful ¶ Error ¶ Canceled ¶ Interrupted ¶ Undecided Engine Lists all the connected engines.. Periodic refresh Select this to specify a refresh interval in seconds. if you want the list results refreshed automatically. The new list definition is added to the Common Default Plan Lists group in the Job Scheduling view. Job stream name Lists all the job instances that are in the job stream with this name or namestring.Use the information in Table 157 to specify the selection criteria for the list. Job identifier Lists all the job instances that have this identifier. The list results are displayed in the right hand pane. Using Common Lists When you have finished: —EITHER— Click Apply to display the list results immediately. then click OK to close the window. Apply defaults To use the default specified in the Settings page of the Scheduler Properties window. or combinations of two or more parameters. —OR— Click OK to close the window. double-click it in the scheduling tree. Right-click the list in the Job Scheduling view and select Open. Filter Criteria Specify any of the following search parameters. Name Periodic Refresh Options Enter this information . Pop-up calendars are provided to help you select the days. Dates Lists all job instances that are part of job stream instances scheduled to run in an interval period starting on the day and time specified in the From Date and Time fields and ending in the day and time specified in the To Date and Time fields. Select the engines for which you want to display the job instances. You cannot use wildcard characters with this filter. Priority Lists all the job instances that have the priority level you select in From and To. A. Table 157... Tivoli Job Scheduling Console User’s Guide 377 . Name for the list. The Workload Scheduler for z/OS priority is 1–10 and the Workload Scheduler priority is 0–101.Job Instance List Information In this area .

Using Filter Criteria To create a list of job stream instances with different filter criteria. 2. The Properties . Figure 221.Creating a Common List of Job Stream Instances Listing All Job Stream Instances To list all the job stream instances existing in all the scheduling engines: 1. select Common Default Plan Lists and click the List Job Stream Instances button. Double-click All Scheduled Job Streams.Job Stream Instance Common List window is displayed. The All Scheduled Job Streams list is displayed in the right pane of the Job Scheduling view. In the Job Scheduling view.Job Stream Instance Common List Window 378 Version 8. double-click Common Default Plan Lists. Properties . in the Job Scheduling view.1 .

Name Periodic Refresh Options Enter this information . Priority Lists all the job stream instances that have the priority level you select in From and To. Status Lists all the job stream instances with any of the following Job Scheduling Console status codes that you specify in the drop-down list: ¶ Waiting ¶ Ready ¶ Running ¶ Successful ¶ Error ¶ Canceled ¶ Interrupted ¶ Undecided Engine Lists all the connected engines. Note: To display the list at a later date. The list results are displayed in the right hand pane. Periodic refresh Select this to specify a refresh interval in seconds. You cannot use wildcard characters with this filter. double-click it in the scheduling tree.. —OR— Click OK to close the window. Properties . Right-click the list in the Job Scheduling view and select Open. Job stream name Lists all the job stream instances that are in the job stream with this name or namestring.. Name for the list. then click OK to close the window. Tivoli Job Scheduling Console User’s Guide 379 .. The Workload Scheduler for z/OS priority is 1–10 and the Workload Scheduler priority is 0–101. Dates Lists all job instances that are part of job stream instances scheduled to run in an interval period starting on the day and time specified in the From Date and Time fields and ending in the day and time specified in the To Date and Time fields.Use the information in Table 158 to specify the selection criteria for the list.Job Stream Instance List Information In this area . Table 158. Using Common Lists When you have finished: —EITHER— Click Apply to display the list results immediately.. Pop-up calendars are provided to help you select the days. The new list definition is added to the Common Default Plan Lists group in the Job Scheduling view. Select the engines for which you want to display the job stream instances. Filter Criteria Specify any of the following search parameters. Apply defaults To use the default specified in the Settings page of the Scheduler Properties window. A. if you want the list results refreshed automatically. or combinations of two or more parameters. Use wildcards to help your search. Job identifier Lists all the job stream instances that have this identifier.

The common lists are displayed under this group.Displaying a Common List To display a common list that you have already created: 1. In the Job Scheduling view. double-click Common Default Plan Lists. Make the changes you want.1 . 2. The list is deleted from the Common Default Plan Lists group. In the Job Scheduling view. Modifying a Common List To modify a common list: 1. then click OK to close the window. double-click Common Default Plan Lists. 3. —OR— Click OK to close the window. The results are displayed in the right hand pane of the Job Scheduling view. 2. 2. The common lists are displayed under this group. The properties window of the list is displayed. In the Job Scheduling view. Right-click the list in the Job Scheduling view and select Open. The common lists are displayed under this group. 380 Version 8. Right-click the list you want to modify and select Properties from the pop-up menu. The list results are displayed in the right hand pane. Double-click the list you want to display. Deleting a Common List To delete a common list from the Common Default Plan Lists group: 1. The new list definition is added to the Common Default Plan Lists group in the Job Scheduling view. Right-click the list you want to delete and select Delete from the pop-up menu. When you have finished: —EITHER— Click Apply to display the list results immediately. double-click Common Default Plan Lists.

so that you can check for program correctness in terms of sequences of instructions. 2000 Microsoft Windows 98.. Tivoli Job Scheduling Console User’s Guide 381 . These variables are located in the following files: Table 159.sh .sh .\bin\java\console. You can set it to record the contents of the Job Scheduling Console beans or the data structures exchanged between the Job Scheduling Console and the Workload Scheduler for z/OS Connector. . Errors. info/debug lines./bin/java/AIXconsole./bin/java/LINUXconsole... The following table displays what each value does: TRACELEVEL Value 0 1 2 3 Action Only errors and warnings are recorded.. open the file in editing mode and set the variable to a value ranging from 0 to 3./bin/java/SUNconsole. and info/debug lines are recorded.. Microsoft Windows NT..\bin\java\NTconsole. warnings. B. TRACELEVEL enables you to choose what type of program information flow the tracing facility must record..sh . Setting Traces for the Job Scheduling Console TRACEDATA enables you to choose what type of data flow the tracing facility must record. ME AIX HP-UX SUN Solaris Linux The file is . Values enable you to tune the tracing facilities to report the type and detail of data that best fits your needs. and method entry/exit are recorded. Trace Variable Location by Operating System For this operating system .bat ..sh To customize either variable.. and method entry/exit are recorded (maximum trace level). The following table displays what each values does: TRACEDATA Value 0 Action No data is traced.B Setting Traces for the Job Scheduling Console This appendix explains how to set tracing facilities for the Job Scheduling Console. Errors../bin/java/HPconsole. You can set the tracing facility by customizing the TRACELEVEL and TRACEDATA variables. Errors. warnings.bat . warnings.

When this number is exceeded. When the file reaches this size. The internal values of the Job Scheduling Console beans are recorded.INI as shown below: [trace] traceFileMaxLen=3000000 traceFileMaxNum=10 printTimeDate=true printMillisecond=false printThreadID=false printComponent=false printType=true where: traceFileMaxLen Defines the maximum size.LOG can be 3 MB. Using the Log File Advanced Customization Options These options enable you to customize the log file produced by the tracing facilities. it is renamed and a new log file is created. The value is an integer of your choice. The various combinations of values for TRACELEVEL and TRACEDATA give you the maximum flexibility in terms of information provided by the log file. The log file is named JSCONSOLE.TRACEDATA Value 1 2 3 Action Data structures from/to the scheduler Connector are recorded. You have to manually delete the files stored during previous sessions. By default. are listed in JSS. Both data structures and bean internal values are recorded (maximum trace level). in bytes. traceFileMaxNum Defines the maximum number of log files that can be present on disk during each instance of the Job Scheduling Console. the tracing facility creates an additional log file. 382 Version 8.LOG and is placed in the DAT subdirectory of the directory hosting the Job Scheduling Console files. This includes only the files created during the current session of the Job Scheduling Console. it is important to point out that the combination of values of 2 or greater for TRACELEVEL and of 1 or greater for TRACEDATA can be quite heavy for system performance: they can slow program operation and generate very big log files. Tracking of error conditions is active by default (TRACELEVEL is already set to 0).INI file in the \dat\. You can. printTimeDate Specifies if the trace calls write date and time information in the log file. that the log file can be. The options. the maximum size of JSCONSOLE. However. change this by using the advanced customization options described in the next section. The value is an integer of your choice. You can also set TRACELEVEL to -1 to force the tracing facility not to create a log file at all. They are listed under a section named [trace] inside of the JSS.tmeconsole subdirectory of the directory hosting the Job Scheduling Console files. When this limit is reached.1 . The tracing facility can create up to ten log files for a total of 30 MB. the older files are replaced first. however. and their default values. The value can be True or False.

printThreadID Specifies if the trace calls write an identifier for the current thread in the log file. They enable you to achieve a correct trade-off between disk space occupancy and debug data availability. printComponent Specifies if the trace calls write the name of the source component in the log file. The value can be True or False. Use the other options to determine what type of information you want included in the trace file. Setting Traces for the Job Scheduling Console Tivoli Job Scheduling Console User’s Guide 383 . The value can be True or False. The value can be True or False. in the log file.printMilllisecond Specifies if the trace calls write timestamp information. warning or information) in the log file. printType Specifies if the trace calls write the message type (error. The value can be True or False. traceFileMaxLen and traceFileMaxNum Use to decide how much disk space you want to allocate to the tracing facility. B. in milliseconds.

384 Version 8.1 .

you must schedule it to run Sunday through Thursday. Previously. Job stream PST_SCHEDULE2 is time zone enabled. When the EST master initializes the PST fault-tolerant agent at 0300. and you must specify ″carryforward″. To get this job stream to run every weekday morning. the jobs would never run. Time zone implementation also allows for easy scheduling across multiple time zone and for jobs that need to run in the ″dead zone. For example. the dead zone for this fault-tolerant agent is between the hours of 3 AM and 6 AM. it starts the job stream the same day at 0330. consider the following two job streams for a PST fault-tolerant agent with an EST master: Schedule PST_SCHEDULE1 On SU. Enabling Time Zones in the Workload Scheduler Job stream PST_SCHEDULE1 is not time zone enabled. Now when specifying a time zone with the start time on a job or job stream. consider the following two job streams for an EST fault-tolerant agent and a PST master with an 0600 start of day. Workload Scheduler runs them as expected. special handling was required to run jobs in this time period.C Enabling Time Zones in the Workload Scheduler Enabling time zones in Tivoli Workload Scheduler enables you to manage your workload on a global level. if an eastern master with a Workload Scheduler start of day of 6 AM initializes a western agent with a 3-hour time zone difference. weekdays except FR CARRYFORWARD AT 0330 : job1 job2 END Schedule PST_SCHEDULE2 on weekdays AT 0330 TZ PST : joba jobb END C.″ The dead zone is the gap between the Workload Scheduler start of day time on the master and the time on the fault-tolerant agent in another time zone. since the fault-tolerant agent would be initialized at 0300 every morning (assuming an EST master with a Workload Scheduler start of day of 0600). Time zone enabling also has an effect on eastern fault-tolerant agents when scheduling from western masters. For example. Without carryforward. Tivoli Job Scheduling Console User’s Guide 385 . For example.

time zones are disabled. it runs the job stream at 0800 the next day. If the timezone enable entry is missing from the globalopts file. For this job stream to run every weekday morning. from″ option Enabling the Time Zone Feature The time zone feature is enabled by an entry in the globalopts file and by specifying a time zone in the master workstation definition. the following commands now accept time zone parameters where AT or UNTIL times are used: ¶ submit job ¶ submit docommand ¶ submit file ¶ submit schedule ¶ addep schedule ¶ addep job ¶ addep schedule ¶ addep job ¶ ″rurun job. weekdays except FR AT 0800 + 1 DAY CARRYFORWARD : job1 job2 END Schedule EST_SCHEDULE2 On SU. Once enabled. Without the +1DAY specification.1 . time zones can be specified in the Job Scheduling Console or composer for start and deadline times within jobs and job streams. Job stream EST_SCHEDULE2 is time zone enabled. 386 Version 8. as follows: timezone enable = yes|no Time zones are disabled by default on installation or update of the product. weekdays except FR AT 0800 TZ EST : joba jobb END Job stream EST_SCHEDULE1 is not time zone enabled. the job stream would launch immediately after initialization from the western master at 0900. Specify carryforward and +1DAY for the AT time.Schedule EST_SCHEDULE1 On SU. When the eastern fault-tolerant agent is initialized at 0900. Carryforward is needed for the +1DAY specification. For conman. you must schedule it to run Sunday through Thursday.

WAITING READY RUNNING SUCCESSFUL ERROR CANCELED HELD UNDECIDED BLOCKED Means that . The job stream instance was canceled... The dependencies of the job stream instance have been resolved and the job stream instance is ready to run. For information about job and job stream status for Workload Scheduler for z/OS. The job stream instance is running. The job stream instance has stopped running with an error. Status Overview There are two types of status: Job Scheduling Console status This is a subset of internal status and is common for both Workload Scheduler and Workload Scheduler for z/OS. Status Description and Mapping Job Scheduling Console Job Status Below are listed possible job states and descriptions: Table 160. refer to Tivoli Workload Scheduler for z/OS Controlling and Monitoring the Workload. The job stream status is currently being checked.. The job stream instance completed successfully. The job stream instance was interrupted. Job Status This section describes the job status for both Job Scheduling Console and Workload Scheduler internal status. D. Tivoli Job Scheduling Console User’s Guide 387 . Internal Status This refers to the Workload Scheduler internal or engine status for the job or job stream. Job Scheduling Console Job States This job status . The internal status messages are unique to the scheduler. The job stream instance was blocked due to unfulfilled dependencies. The job stream instance is waiting for its dependencies to be resolved.D Status Description and Mapping This Appendix provides information about job and job stream status for the Job Scheduling Console and Workload Scheduler..

ABEND ABENP ADD DONE ERROR EXEC EXTRN Means that .. Job Scheduling Console Job Stream Status Below are listed possible job stream states and descriptions: Table 162. The dependencies of the job stream instance have been resolved and the job stream instance is ready to run. The job completed. WAITING READY RUNNING SUCCESSFUL ERROR CANCELED Means that . For internetwork dependencies only. The job’s priority is below the fence. An ABEND confirmation was received. The job stream instance is waiting for its dependencies to be resolved.1 . but the job is not completed.. The job terminated with a non-zero exit code. A SUCC confirmation was received. The job was suspended by a breakjob command. 388 Version 8. The job is running... The job is ready to launch.. The job stream instance completed successfully. and all dependencies are resolved. Workload Scheduler Internal Job States This job status . The job’s at time has not arrived. The job is being submitted. Job Scheduling Console Job Stream States This job status . An error occurred.... and is awaiting confirmation. Unable to launch the job. but the job is not completed. The job completed with an exit code of zero. (Extended agent and MPE only) The job is in the wait state. (MPE only) The job is in the wait state. and is deferred. The job is awaiting dependency resolution. the status is unknown. or the remote job or job stream does not exist. The job is introduced for launching by the system. an error occurred while checking for the remote status. The job completed in an unknown state. a rerun action was just performed on the job in the external job stream. The job stream instance is running. For internetwork dependencies only.Workload Scheduler Internal Job Status Below are listed possible job states and descriptions: Table 161. The job stream instance has stopped running with an error. (MPE only) FAIL FENCE HOLD INTRO PEND READY SCHED SUCC SUCCP SUSP WAIT WAITD Job Stream Status This section describes the job stream status for both Job Scheduling Console and Workload Scheduler internal status. The job stream instance was canceled.

SUCCP. WAITING READY RUNNING SUCCESSFUL ERROR Maps to this Workload Scheduler internal status . This is for Internetwork job streams and specifies that an error occurred while checking for the remote status. Job Status Mapping Table 164 describes how Job Scheduling Console status correlates to Workload Scheduler internal status for jobs. The dependencies for the job stream have been met but the time restrictions for the job stream have not. WAITD.Table 162. HELD UNDECIDED BLOCKED Means that . Workload Scheduler Internal Job Stream States This job status . Cancelation is deferred until all of the dependencies. The job stream instance was added with operator intervention. The job stream instance is pending cancelation... ERROR D. Job stream instance ion was interrupted.. WAIT. are resolved. No jobs are launched without operator intervention. An error occurred. ADD. The job stream instance terminated with a non-zero exit code. Workload Scheduler Internal Job Stream Status Below are listed possible job stream states and descriptions: Table 163. The job stream instance was canceled. The job stream instance was blocked due to unfulfilled dependencies. INTRO. or the INET job or job stream does not exist. The job stream instance is awaiting dependency resolution. Status Description and Mapping Status Mapping This section provides a table of how Job Scheduling Console status maps to Workload Scheduler internal status for jobs and job streams.. READY HOLD CANCEL PEND EXEC STUCK ABEND SUCC CANCEL ADD EXTRN Means that . Job Scheduling Console Job Stream States (continued) This job status . The job stream instance is in a remote Workload Scheduler network and its status is unknown.. The job stream instance was interrupted. a Rerun action was performed on the EXTERNAL job stream. ABENP SUCC ABEND. The job stream instance completed successfully.. including an at time... Job Status Mapping This console status . The job stream status is currently being checked. HOLD READY EXEC. FAIL Tivoli Job Scheduling Console User’s Guide 389 .. Table 164... PEND. The job stream instance is running..

.. Job Status Mapping (continued) This console status ....1 . Priority = 0.. WAITING READY RUNNING SUCCESSFUL ERROR CANCELED HELD UNDECIDED BLOCKED Maps to this Workload Scheduler internal status . CANCEL P HOLD EXTRN.. CANCELED HELD UNDECIDED BLOCKED Maps to this Workload Scheduler internal status .Table 164. FAIL CANCEL. Status of the job when it was canceled. HOLD. READY ERROR. HOLD READY EXEC SUCC ABEND. Job Stream Status Mapping This console status . Table 165. ADD. WAIT. Canceled flag is set. INTRO. WAITD. PEND.. EXTRN SUSP Job Stream Status Mapping Table 165 describes how Job Scheduling Console status correlates to Workload Scheduler internal status for job streams. WAITING. ERROR STUCK 390 Version 8.

E Job Scheduling Console Messages Job Scheduling console message numbers have a GJS prefix and are followed by a letter indicating the type of message: E I W Error Information Warning The list below includes all the messages displayed by the base Job Scheduling console. Job Scheduling Console Messages Tivoli Job Scheduling Console User’s Guide 391 . GJS0000E GJS0001E GJS0002E GJS0003E GJS0004E GJS0005E GJS0006E GJS0007E GJS0008E GJS0009E GJS0010E GJS0012E GJS0013E GJS0014E GJS0015E GJS0016E GJS0017E GJS0027E GJS0028E GJS0029E GJS0030E GJS0031E There was an unidentified problem when connecting Cannot load job stream list Cannot load plan view Cannot load resource list Cannot load resource plan view Cannot load workstation list Cannot open job stream instance Cannot update job stream Cannot open the Job Stream Editor Cannot open the Job Stream Instance Editor Cannot open the Resource Editor Cannot load the job stream Cannot load the definition of resource availability Cannot load the job stream instance Cannot save the job stream Cannot save the resource Cannot add this dependency Cannot save the workstation Class Cast Exception There is a problem with your job scheduling engine Cannot close the window Cannot add Job Dependency E.

1 .GJS0032E GJS0033E GJS0034E GJS0035E GJS0036E GJS0037E GJS0038E GJS0039E GJS0040E GJS0041E GJS0042E GJS0043E GJS0044E GJS0045E GJS0046E GJS0047E GJS0048E GJS0049E GJS0050E GJS0051E GJS0052E GJS0053E GJS0054E GJS0058E GJS0060E GJS0061E GJS0062E GJS0063E GJS0064E GJS0065E GJS0066E GJS0067E GJS0068E GJS0069E GJS0070E Cannot process OK request Cannot change the job Cannot add the new job Cannot modify the instance Cannot delete the instance Cannot hold the instance Cannot release the instance Cannot delete the object Cannot undelete the object Cannot modify the status in the database Cannot remove the job Cannot remove the job dependency Cannot remove the dependency Cannot remove the external dependency Cannot perform the action on the selected objects Cannot perform the job stream operation Cannot perform the action on the selected object Cannot perform the action on the selected objects Cannot update the instance from services Cannot perform the action specified on the selected object Cannot perform the action specified on the selected objects Cannot perform the action specified on the selected objects Cannot perform the action specified on the selected objects Cannot perform the action specified on the selected objects Cannot delete the selected workstations Cannot add schedule specifications Cannot create another run cycle Cannot perform this action Cannot interrupt the operation Cannot delete the resource Cannot delete the selected resources Cannot get the resource header Cannot open the resource Cannot save resource dependency changes Cannot add scheduling specifications 392 Version 8.

Try again later. For information about these messages. refer to the Tivoli Workload Scheduler for z/OS Messages and Codes book. Error logging in to the TMR host Cannot link to the connector Cannot detach the view Cannot save the job stream Cannot paste the external dependency Cannot find the objects you are searching Cannot find the objects you are searching Cannot find the objects you are searching You are renaming a job stream Selected engine not available Cannot attach the view Cannot load workstation plan view Cannot load the Job output Cannot load the Job output E. It will be displayed in read-only mode until the user releases it.GJS0071E GJS0072E GJS0073E GJS0074W GJS0075E GJS0076E GJS0077E GJS0078E GJS0079E GJS0080E GJS0081E GJS0082E GJS0083E GJS0084E GJS0085E GJS0086E GJS0087E GJS0088E GJS0089E GJS0090E GJS0091E Cannot add scheduling specifications Cannot process the OK request You are renaming a resource You are renaming a workstation Cannot open the resource Cannot open the workstation This object is currently locked because it is being updated by another user. The explanation of each message displays a specific Workload Scheduler for z/OS message. Job Scheduling Console Messages Messages Originated by Workload Scheduler for z/OS All Job Scheduling Console messages that contain the GJSQ prefix refer to Workload Scheduler for z/OS error conditions. Tivoli Job Scheduling Console User’s Guide 393 . These messages are identified by the EQQ prefix.

394 Version 8.1 .

Dependency A relationship between two jobs in which the first job must be completed before the second can begin. Exclusionary run cycle A run cycle that specifies when a job stream must not run. the actual start time is represented by a black bar running down the center of the navy blue activity bar. free days. you can assign a calendar to a job stream. the job stream that includes it as a predecessor skips it as if it did not exist. you must use the ISPF panes to create or modify calendars in the database. For job instances. The job or job stream can. D Database A collection of data that is fundamental to a system. In the Timeline view of jobs in the database. In the GUI. This information is stored in the database of the engine and is used to generate instances for the plan. at which the job or job stream instance started. based on your experience in running the job or job stream. Duration The time you expect the job to take to complete. Tivoli Job Scheduling Console User’s Guide 395 . An external job is represented by a place holder button in the Graph view of the job stream. and workstations. based on your experience in running the job or job stream. resources. the deadline is represented by the black border at the right end of the navy blue activity bar. The earliest start time is your estimate. The deadline is your estimate. See also actual start time and planned start time. When you delete an external job either from the database or the plan. and workstations. the start time that the scheduler calculates is represented by a light blue bar. start after the time you specify as long as all other dependencies are satisfied. resources. In the timeline. When you create a job stream in the database. as logged. the start time is represented by the beginning (left edge) of the navy blue activity bar. you can define and modify job streams.In the timeline. however. Glossary E Earliest start time The time before which the job or job stream cannot start. The scheduler uses the calendar combined with run cycles to determine on which days to run the job stream. and holidays. you define the dependencies between jobs DLF Data Lookaside Facility. In the Job Scheduling Console. C Calendar A definition of workdays. Deadline The time by which the job or job stream must be completed. In the timeline. periods. and the scheduler logs the error. The z/OS component that manages Hiperbatch objects. See also earliest start time and planned start time. External job A job from one job stream that is a predecessor for a job in another job stream. The database for each engine contains calendars. job streams. the duration is represented by a light blue bar at the center of the activity bar or by a light blue diamond. JCL variable tables. operator instructions.Glossary A Actual start time The time. however.

Schedule on the last workday before free day. including the resources and workstations that support them. you do not define run cycles for job streams created from a template.1 . See also job stream. The dependency of one job on the completion of another determines the sequence of the jobs.F Fault-tolerant workstation The CPU that runs a job stream that is scheduled in the plan. you also define its dependencies on predecessor jobs and its time restrictions. such as the estimated start time and deadline. Count workdays and free days alike. that can be inherited by all the job streams that have been created using the template. such as manual activities and run on general workstations. and workstations. Therefore. Fault tolerant workstation jobs are used to run jobs from Tivoli Workload Scheduler. Write-to-operator (WTO) jobs consist of an operator instruction displayed on the system console and run on general workstations. The type of job determines the type of target workstation on which it can run: JCL jobs consist of JCL statements and run on computer workstations. Do not schedule if free days. and run cycles. Job stream instance A job stream that is scheduled for a specific run date in the plan. See also job. Free day rule Determines how to calculate free days when scheduling the job stream. Job stream template An entity that contains scheduling information. job streams. 396 Version 8. The scheduling information. It usually includes all necessary computer programs. such as run cycles and a calendar. Job scheduling object A generic term that includes jobs. Printer jobs print the output of a predecessor job and run on printer workstations. General jobs include activities other than printing and processing. job streams created from a job stream template continue to be part of the template and any changes to the scheduling information for the template are inherited by the job streams. J Job A unit of work in a job stream that is processed at a workstation. Job status See status Job stream A sequence of jobs. Unlike typical templates. Started task jobs start or stop started tasks and run on computer workstations. They require fault tolerant workstations. determines when and how often the job stream is run. and instructions to the operating system. The facility can significantly reduce the run time of certain batch streams that access VSAM and QSAM. such as a calendar. Schedule on the next workday after free day. See also job instance. H Hiperbatch The z/OS facility that stores VSAM and QSAM data in Hiperspace for access by multiple jobs. a free day rule. The following are free day rules: Count workdays only. and scheduling information. Job instance A job scheduled for a specific run date in the plan. See also job stream instance. Setup jobs require preparation of a set of JCL statements for a JCL or started task job and run on general workstations. Fault tolerant workstation jobs can have neither a general job as a predecessor nor a printer job as a successor. resources. linkages. When you create a job in the database. files.

L List A list displays job scheduling objects. except a predecessor at a nonreporting workstation. Canceled The instance has been deleted from the plan. P Plan A detailed plan of system activity that covers a period of at least one minute and not more than 21 days. See also exclusionary run cycle. such as. Undecided The status of the instance is not known. You must create separate lists for each job scheduling object. resources are also called logical resources. This information helps determine when job stream instances are scheduled to run. that generate the calendar days when a resource is available. All job streams for which you have created run cycles are automatically scheduled and included in the plan. Resource availability Fixed times when the job can use a resource. It typically covers one or two days. or printers. similar to run cycles. Ready The instance is ready to start. You define conditions. communication lines. the first Friday of March or the second workday of the week Offset-based: Includes a user-defined period and an offset. The plan encompasses all job and job stream instances and the resources and workstations involved in running them. Successful The instance has been completed successfully. Waiting The instance is waiting for a predecessor job to end. Error The instance has ended in error. Running The job has started. Interrupted The instance has been interrupted (jobs only). in what quantities. All predecessors are complete (jobs only). Run cycle A specification of the days that a job stream is scheduled to run. Glossary S Status The state of a job or job stream instance. All predecessors. that the scheduler makes for when the job instance should start. based on the duration of predecessors. there are two types of lists: one of definitions in the database and another of instances in the plan. It can be either rule-based or offset-based: Rule-based: Includes a rule. the 3rd day in a 90-day period. In the Job Scheduling Console. For each job scheduling object. Logical resource See resource. You designate when a resource is available. You can also define conditions for when a resource is not available. Ready-nonreporting workstation The job instance is ready to start. R Resource Any type of limited resource. See also actual start time and earliest start time Predecessor A job that must be completed before jobs that are dependent on it can begin. such as tape drives. Contrast with successor. databases. such as. and by which logical workstations the resource can be used. It can be one of the following: Arriving The instance is waiting for input to arrive (jobs only). Tivoli Job Scheduling Console User’s Guide 397 . are complete (jobs only). Pending predecessor The job stream instance is waiting for a predecessor to be completed (job streams only). Planned start time The estimated start time. Contrast with database. that is needed to run a job.

Printer.1 . 398 Version 8. W Workstation The logical machine on which a job runs. There are three types of workstations: Computer. WTO Write-to-operator. you identify at least one workstation on which it will run. The first and last date that a run cycle is in effect. V Valid from. Contrast with predecessor. When you create a job.Successor A job that cannot start until all of the jobs on which it has a dependency are completed. See also job. General. to dates The interval for which a job stream is available for scheduling and can be run.

175 domain creating 261 database list 262 deleting 263 B backup domain manager. 73. 76. 288 directory names. 63 confirming a job instance 315 connected workstations 73 connector prerequisites 13. notation xxxiii displaying predecessors job instance 307 job stream instance 327 displaying successors job instance 309 job stream instance 328 DLF attribute 75. 76 deadline 88 deleting a calendar 269 deleting a domain 263 deleting a parameter 278 deleting a prompt 276 deleting a resource 273 deleting a run cycle 244 deleting a user 266 deleting predecessors job instance 309 job stream instance 328 dependency filter window job stream instance 284. requirements books feedback xxix online xxix ordering xxix 367 Index C calendar 63. 17. 111 creating 267 database list 269 deleting 269 modify 269 view properties 269 calendar run cycle 242 cancelling a job instance 314 cancelling a job stream instance 330 changing number of resource units 370 changing the job fence. workstation 364 Tivoli Job Scheduling Console User’s Guide 399 .Index A add link between jobs 236 adding a job to a job stream 227 adding dependencies between jobs adding file dependencies job 231 job instance 302 job stream instance 322 adding predecessors job instance 308 job stream instance 328 adding prompt dependencies job 232 job instance 304 job stream instance 324 adding resource dependencies job 230 job instance 306 job stream instance 326 adding run cycles 237 adding time restrictions job 229 job instance 300 job stream instance 321 adhoc job 349 allocation options 175 Authority group 81. 81. 73. 111 236 changing the job limit job stream instance 331 workstation 363 changing the priority job instance 297 job stream instance 331 closing the job stream editor 247 complete 57. 25 control on servers 58 creating a calendar 267 creating a domain 261 creating a group of lists 279 creating a parameter 276 creating a prompt 274 creating a resource 271 creating a user 263 creating run cycles 237 Customer Support xxxii D data lookaside facility 71 date 63.

71. 332 F feedback about publications xxxi file dependency adding to a job 231 status 367 find calendar window 81 find workstations 63 finding objects in the plan 293 follows dependency 236 freedays 81 from time 63. 175 job limit. 234 J JCL 58.domain (continued) modify 263 starting the workstations view properties 262 view status 365 dumpsec 31 duration 57. 123. 75. changing for a workstation 363 job properties files 231 prompts 232 resource 230 time restrictions 229 Job Scheduling view 75. changing 364 job instance adding predecessors 308 cancelling 314 confirm 315 deleting predecessors 309 displaying successors 309 holding 309 killing 314 modifying 297 predecessors 307 release all dependencies 315 releasing 310 rerun 313 submitting into the plan 336 job instance properties files 302 prompts 304 resources 306 time restrictions 300 job instances 55.1 . 59 I 366 internetwork dependency adding to a job 233 adding to a job stream interrupted 58 Is available 63. 175 holding a job instance 309 holding a job stream instance holidays calendar 266 329 400 Version 8. 175 external dependencies deleting 227 external job 92 adding to a job stream 226. 73 ISPF 57 226 E e-mail contact xxxi earliest start time 88 enabling the time zone feature 386 environment variables. 235 external job stream adding to a job stream 226. 111 job definition adding to a job stream 227 properties 227 job fence. 137. 73 G globalopts file time zone feature graph view 113 386 H hiperbatch 71. notation xxxiii exclusive 71. 119. 110. 175 job stream adding run cycles 237 saving 247 submit into plan 335 job stream editor 113 job stream instance cancelling 330 commands 316 hold 316 holding 329 job limit 331 list view 318 modifying 319 plan list 316 priority 331 release 316 release all dependencies 316.

361 occurrence 119 online publications xxx operations 57. 119 plan list deleting 292 detaching 292 modifying 292 plan lists 279 planning on servers 58 predecessor job 59 priority 81 prompt creating 274 deleting 276 listing 275 modifying 275 properties 275 replying 369 status 368 publications feedback xxix online xxix ordering xxix Index M manuals feedback xxix online xxix ordering xxix modifying a domain 263 modifying a job instance 297 modifying a parameter 278 modifying a prompt 275 modifying a resource 273 modifying a run cycle 244 modifying a user 265 modifying file dependencies job instance 302 job stream instance 322 modifying prompt dependencies job instance 304 job stream instance 324 Tivoli Job Scheduling Console User’s Guide 401 . domain 366 list view 138 job instance 294 job stream instance 318 listing domains in the plan 280 listing file dependencies in the plan 291 listing job instances in the plan 284.job stream instance (continued) releasing 329 resubmit 316 resubmitting 333 timeline view 317 job stream instance properties files 322 general 319 predecessors 327 prompt 324 resource 326 time restrictions 321 job stream instances 119. 294 listing job streams in the plan 281 listing parameters in the database 277 listing prompts in the database 275 listing prompts in the plan 290 listing resources in the database 272 listing resources in the plan 289 listing workstations in the plan 279. 58 ordering publications xxxi P parallel server 58 parameter creating 276 database list 277 deleting 278 modifying 278 properties 277 path names. notation xxxiii plan 59. 127 modifying resource dependencies job instance 306 job stream instance 326 modifying time restrictions job instance 300 job stream instance 321 N notation environment variables path names xxxiii typeface xxxiii xxxiii K killing a job instance 314 O L linking a workstation 365 linking workstations.

163 rerunning a job instance 313 resource adding to a job 230 changing units 370 creating 271 database list 272 deleting 273 modifying 273 properties 272 status 369 viewing plan properties 370 Resource Description database 175 resubmit a job stream instance 333 run cycle adding to a job stream 237 calendar 242 deleting 244 modifying 244 simple 239 weekly 240 T target workstation 83 task name 111 TCP/IP 59 tempsec 31 time restrictions 88 job 245 job stream 244 timeline view job instance 296 job stream instance 317 Timeline view 104. 71 starting a workstation 364 starting workstations. 58. 58. 144 started 57. notation for xxxiii viewing calendars in the database 269 viewing domain status 365 viewing domains in the database 262 viewing parameter properties 277 viewing prompt properties 275 viewing prompt status 368 viewing resource properties 272 viewing resource properties in the plan 370 viewing resource status 369 viewing the properties of a domain 262 viewing the status of a workstation 362 viewing users in the database 264 402 Version 8. 83.1 . 175 simple run cycle 239 special resources 69 specifying job properties 227 start time 88. domain 366 V variables. 73 transport time 59 treat input as 75. 75. domain 366 status workstation 362 status of job stream 111 stopping a workstation 365 stopping workstations. 59. domain user creating 263 deleting 266 listing 264 modifying 265 using plan lists 279 366 S saving a job stream 247 scheduling 55. 58 release all dependencies job instance 315 job stream instance 332 releasing a job instance 310 releasing a job stream instance 329 replying to a prompt 369 reporting attributes 66. 175 U unlinking a workstation 365 unlinking workstations. 138 Tivoli Customer Support xxxii to time 63. 71. 175 search tool 73 security 31 setting priority job instance 297 job stream instance 316 shared 71. 73 submitting a job into the plan 336 submitting a job stream into the plan 335 submitting an adhoc job into the plan 349 switch manager command 367 switching domain managers 367 R ready 57.Q quantity 63.

W waiting 175 weekly run cycle 240 wildcard characters 175 wmaeutil 32 workdays 81 workstation linking 365 properties 362 starting 364 stopping 365 unlinking 365 workstation resources 55. 63 workstation type 58 wuninst 16 Index Tivoli Job Scheduling Console User’s Guide 403 .

404 Version 8.1 .

.

Program Number: 5697-WSZ Printed in Denmark by IBM Danmark A/S SH19-4552-00 .

Master your semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master your semester with Scribd & The New York Times

Cancel anytime.