Scheduler Job Scheduling Console

Transcription

1 Tivoli IBM Tivoli Workload Scheduler Job Scheduling Console Feature Level 1.3 (Revised December 2004) User s Guide SC

2

3 Tivoli IBM Tivoli Workload Scheduler Job Scheduling Console Feature Level 1.3 (Revised December 2004) User s Guide SC

4 Note Before using this information and the product it supports, read the information in Notices on page 333. Third Edition (December 2004) This edition applies to feature level 1.3 of IBM Tivoli Workload Scheduler Job Scheduling Console (program number 5697-WSZ) and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces SC Copyright International Business Machines Corporation 1991, All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents List of figures ix List of tables xi About this guide xiii What is new in this guide xiii Who should read this guide xiv What this guide contains xv Publications xviii Tivoli Workload Scheduler library..... xviii Related publications xxi Accessing publications online xxii Ordering publications xxii Accessibility xxiii Tivoli technical training xxiii Support information xxiii Conventions used in this guide xxiii Typeface conventions xxiii Operating system-dependent variables and paths xxiv Command syntax xxiv Part 1. Introduction Chapter 1. Job Scheduling Console overview Tivoli Workload Scheduler architecture Components Topology Connection Part 2. Planning, installation and upgrade Chapter 2. Planning and installing the Job Scheduling Console Planning installation Installation methods Installing using the installation wizard Running the installation wizard Performing a silent installation Installing using Software Distribution Installing from the command line Installing the Java Virtual Machine Chapter 3. Planning and installing the z/os connector Planning connector installations Installation methods Installing from the Tivoli Desktop Installing Job Scheduling Services from the Tivoli Desktop Installing the connector from the Tivoli Desktop 18 Installing using the installation wizard Performing a silent installation Installing from the command line Installing Job Scheduling Services from the command line Installing the connector from the command line 21 Customizing the connector Authorization roles required for instances...21 Managing z/os connector instances with wopcconn Managing distributed connector instances with wtwsconn Installation scenarios Useful framework commands Chapter 4. Upgrading the z/os connector Upgrading using the installation wizard Upgrade scenarios Upgrading using the Tivoli Desktop Upgrading using the command line Chapter 5. Installing new languages on an existing installation Installing new languages using the installation wizard Chapter 6. Uninstalling the components 33 Setting the Tivoli Environment Uninstalling the Job Scheduling Console Uninstalling the Job Scheduling Console using the Software Distribution CLI Uninstalling the Job Scheduling Services Uninstalling the connectors Part 3. Console overview Chapter 7. Job Scheduling Console object descriptions Common objects Distributed engine specific objects Lists Database Plan Chapter 8. Job Scheduling Console quick start guide Task types Definition tasks Management tasks Task flows Definition task flows Copyright IBM Corp. 1991, 2004 iii

6 Management task flows Task mapping Terminology mapping Chapter 9. Starting the Job Scheduling Console Job Scheduling Console interface description...48 Job Scheduling Console main window Standard functionality Part 4. Defining objects Chapter 10. Creating workstations Creating a z/os workstation General tab Resources tab Open Time Intervals tab Creating a distributed workstation Chapter 11. Creating Windows users 65 Creating a Windows user Chapter 12. Creating parameters Creating a parameter Chapter 13. Creating prompts Creating a prompt Chapter 14. Creating calendars The Holidays calendar The freedays calendar Creating a calendar Chapter 15. Creating domains Creating a domain Chapter 16. Creating workstation classes Creating a workstation class General tab Workstations tab Chapter 17. Creating distributed job definitions Creating a job definition General tab Task tab Chapter 18. Creating job streams Creating a job stream for a z/os engine Creating a job for z/os job streams Creating dependencies between jobs Scheduling job streams Saving a job stream Creating a distributed job stream General tab Time Restrictions tab Resources tab Files tab Prompts tab Adding external dependencies to a job stream 106 Adding a job to a job stream Copying and pasting jobs Cloning job dependencies Adding an internetwork dependency to a job stream Adding an external job stream to a job stream 112 Adding an external job to a job stream Creating dependencies between jobs in a job stream Specifying run cycles for a job stream Specifying time restrictions in the Timeline View 120 Chapter 19. Creating resources Creating a z/os resource Resource tab Default Workstations tab Availability Intervals tab Creating a distributed resource Chapter 20. Creating objects using Create Another Chapter 21. Creating lists Creating database lists Creating a list of job streams Creating a list of workstations Creating a list of resources Creating a list of job definitions Creating a list of workstation classes Creating a list of prompts Creating a list of parameters Creating a list of Windows users Creating a list of domains Creating a list of calendars Creating plan lists Creating a job stream instance list for distributed engines Creating a job stream instance list for z/os engines Creating a job instance list for distributed engines Creating job instance list for z/os engines Creating a list of workstations Creating a list of resources Creating a list of files Creating a list of prompts Creating a list of domain states Creating a group of lists Creating default common plan lists Creating a common list of job stream instances 150 Creating a common list of job instances Setting list properties Part 5. Managing database objects 153 iv IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

7 Chapter 22. Working with object lists 155 Displaying a list of objects Detaching a list display Modifying a list Deleting a list Chapter 23. Managing workstations 159 Viewing and modifying workstation properties Deleting workstations Chapter 24. Managing job streams 161 Editing job streams using the job stream editor Deleting external dependencies from 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 Deleting an external job stream in a job stream 162 Modifying an external job in a job stream Deleting an external job in a job stream Modifying run cycles for a job stream Deleting run cycles from a job stream Modifying z/os job streams Adding and modifying jobs and dependencies in the graph view Adding and modifying run cycles Viewing and modifying time restrictions Using the copy function to add an external job 165 Checking time restrictions in the Timeline View 165 Activity bars Table frame Time restrictions Other tasks Deleting job streams Chapter 25. Managing resources Displaying resource properties Modifying a resource Deleting a resource Chapter 26. Managing job definitions 171 Displaying a job definition Displaying job definition details Modifying a job definition Deleting job definitions Using existing definitions to create other job definitions Chapter 27. Managing workstation classes Displaying and modifying workstation class properties Deleting workstation classes Chapter 28. Managing domains Displaying and modifying domain properties Deleting domains in the database Chapter 29. Managing Windows users 179 Displaying and modifying Windows user properties Changing Windows user passwords Deleting Windows users Chapter 30. Managing calendars Displaying and modifying calendar properties Deleting calendars Chapter 31. Managing prompts Displaying and modifying prompt properties Deleting prompts Chapter 32. Managing parameters Displaying and modifying parameter properties 185 Deleting parameters Part 6. Managing plans Chapter 33. Managing z/os plans Managing job stream instances in the plan Job stream instance lists Submit a job stream Browsing and modifying job stream instances 191 Changing time restrictions in the Timeline View 192 Managing job instances in the plan Job instance lists Browsing and modifying job instances Showing predecessors and successors Browsing the job log Removing a job instance from the plan Restoring a job instance to the plan Running a job instance immediately Changing the status of a job instance Editing JCL Viewing operator instructions Modifying job setup Restart and cleanup Recovery information Managing z/os workstations in the plan Displaying workstations Browsing and modifying workstations Linking fault-tolerant workstations Changing workstation status and rerouting scheduled job instances Displaying the job instances scheduled on a workstation by status Modifying the job instances scheduled on a workstation Managing resources in the plan Displaying resources Browsing and modifying resources Displaying the job instances associated with a resource Contents v

8 Modifying job instances associated with a resource Chapter 34. Managing distributed plans Managing job stream instances in the plan Displaying and changing the properties of a job stream instance Displaying and changing the dependencies of a job stream instance Internetwork Predecessors tab Successors tab Adding predecessors to a job stream instance 225 Deleting predecessors from a job stream instance Holding a job stream instance Releasing a job stream instance Showing predecessors and successors Canceling a job stream instance Changing the job limit of a job stream instance 227 Changing the priority of a job stream instance 227 Releasing a job stream instance from dependencies Resubmitting a job stream instance Submitting jobs Monitoring jobs Managing job instances in the plan Modifying the properties of a job instance Modifying dependencies of a job instance Holding a job instance Releasing a job instance Showing predecessors and successors Browsing the job log Rerunning a job instance Canceling a job instance Killing a job instance Confirming a job instance SUCC or ABEND Releasing a job instance from dependencies Submitting jobs and job streams into the plan Submitting a job stream into the plan Submitting a job into the plan Viewing or modifying the properties of the job to submit Submitting an ad hoc job into the plan Managing workstations in the plan Displaying the status of workstations in the plan Displaying a workstation instance Changing the job limit of a workstation in the plan Changing the job fence of a workstation in the plan Starting a workstation instance Stopping a workstation instance Linking a workstation instance Unlinking a workstation instance Managing domains in the plan Starting the workstations in a domain Stopping the workstations in a domain Linking the workstations in a domain Unlinking the workstations in a domain Switching the domain manager in a domain Managing file dependencies in the plan Displaying file dependencies status Managing prompt dependencies in the plan Displaying prompt dependencies status Replying to a prompt dependency Managing resource dependencies in the plan Displaying resource dependencies status Displaying the properties of a resource dependency Changing the number of units of a resource dependency Setting an alternate plan Part 7. Troubleshooting Chapter 35. Setting traces for the Job Scheduling Console Chapter 36. Troubleshooting Installation Job Scheduling Console installation log Connector installation log General Repairing the installation Chapter 37. Job Scheduling Console messages Appendix A. Accessibility Navigating the interface using the keyboard Magnifying what is displayed on the screen Appendix B. Setting Security Setting secure authentication and encryption Configuring the Job Scheduling Console to work across a firewall Useful framework commands Appendix C. Status description and mapping Appendix D. Support information Searching knowledge bases Search the information center on your local system or network Search the information center at the IBM support Web site Search the Internet Obtaining fixes Contacting IBM software support Determine the business impact of your problem 331 Describe your problem and gather background information Submit your problem to IBM Software Support 331 Notices Trademarks vi IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

9 Glossary Index Contents vii

10 viii IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

11 List of figures 1. Structural changes to the task chapters xiv 2. Single tier topology Multi tier topology End-to-end topology with Job Scheduling Console Job Scheduling Console connection Definition task flows Management task flows Example rule Example 1: Rule-based run cycle Example 2: Exclusionary Run Cycle Example 3: Exclusionary run cycle defined Example 1: Offset-based run cycle Example 2: Offset-based run cycle defined Example Properties panel for distributed engines Example Properties panel for z/os Engines Timeline View - Left Pane Timeline View - Right Pane Connecting across a firewall Copyright IBM Corp. 1991, 2004 ix

12 x IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

13 List of tables 1. Command syntax xxiv 2. Job Scheduling Console prerequisite components Installation parameter Operating system variables Setting the Tivoli Environment Authorization roles Installation scenarios Useful framework commands Upgrading to IBM Tivoli Workload Scheduler for z/os connector version Starting the uninstall program for the Job Scheduling Console z/os and distributed task mapping Job Scheduling Console terminology mapping Starting the Job Scheduling Console Properties - Workstation in Database General information Properties - Workstation in Database Open Time Intervals information Properties - Workstation in Database information Properties - Windows User information Example calendars Properties - Domain panel New Job Definition task types Properties - Job Definition general information Job stream recovery options Task types Properties - Job Stream panel for z/os What Happens When You Define a Job Stream Graph view job buttons Properties - JCL Job General information Properties - JCL Job Task information Properties - JCL Job Time Restrictions information Run cycle buttons Run Cycle General information Run Cycle Time Restrictions information Rule-based Run Cycle Rules information Offset-based run cycle rules information Job Stream Properties General information Job Stream Time Restrictions information Properties - Job General information Properties - Job Time Restrictions information Colored bars on dates Properties Information Create a resource information Create availability intervals information Properties - Resource in Database Panel information Database properties list options Job stream list data for distributed engines Job stream list data for z/os engines Workstation list data for distributed engines Workstation list data for z/os engines Resource list data for distributed engines Resource list data for z/os engines Properties - Job List information Workstation Class List Data Prompt list data Properties - Parameter List information Windows user list data Domain list data Properties - Calendar List information Plan list options Properties - Job Stream Instance List General information Properties - Job Stream Instance List Time Restrictions information Properties - Job Stream Instance List Dependency information Properties - Job Stream Instance List information Properties - Job Instance List General information Properties - Job Instance List Time Restrictions information Properties - Job Instance List Dependency information Properties - Job Instance List information Properties - File List information Properties - Prompt List Information Properties - Domain Status List information Adding and modifying jobs and dependencies in the graph view Adding and modifying run cycles pop-up menu Details for Job panel Submit job stream panel Job Instance Details Timeline View Properties - JCL Job Instance General information Properties - JCL Job Instance Task Information Properties - JCL Job Instance Details information Properties - JCL Job Instance Options Information Logical Resources information Dependencies Predecessors information Dependencies Predecessors Tasks Dependencies successors information Dependencies successors tasks Timeline View Job Instance Details Properties - Workstation in Plan General information Workstation list job options Modifying job instance options Properties - Resource in Plan Resource information Properties - Resource in Plan Default Workstations information Copyright IBM Corp. 1991, 2004 xi

14 90. Properties - Resource in Plan Availability Intervals information Modifying job instance options Job stream instance options Properties - Job Stream Instance General information Properties - Job Stream Instance Time Restrictions information Properties - Job Stream Instance Files information Properties - Job Stream Instance Prompts information Properties - Job Stream Instance Resources panel Properties - Job Stream Instance Predecessors information Dependencies - Job Stream Instance Predecessor information Internetwork Predecessors information Successors information Job Stream Instance Priorities Job instance options Properties - Windows Script Instance General Information Properties - Job Instance Task information Properties - Windows Script Instance Time Restrictions information Properties - Windows Script Instance Files information Properties - Windows Script Instance Prompts information Properties - Windows Script Instance Resources information Predecessors tab Internetwork Predecessors tab Successors tab Rerun Job Window information Submit Job Stream into Plan Window Submit Job into Plan Window Submit Job into Plan information Properties - Job Instance General information Properties - Job Instance Time Restrictions information Properties - Job Instance Files information Ad hoc prompt dependencies Predefined prompt dependencies Properties - Job Instance Resources Properties - Job Instance Predecessors Properties - Job Instance General Task types Properties - Job Instance Time Restrictions Properties - Job Instance Files Ad hoc prompt dependencies Predefined prompt dependencies Properties - Job Instance Resources Properties - Job Instance Predecessors Workstation Status List pane Status of All Files List Prompt Dependencies Status Resource Dependencies Status Set Alternate Plan Files Window Logging properties keys Useful framework commands Useful framework commands Job Scheduling Console job states Tivoli Workload Scheduler Internal job states Job Scheduling Console job stream states Tivoli Workload Scheduler internal job stream states Job status mapping Job stream status mapping xii IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

15 About this guide What is new in this guide The IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide describes Tivoli Workload Scheduler for z/os, IBM Tivoli Workload Scheduler, and the IBM Tivoli Workload Scheduler Job Scheduling Console, which make up the Tivoli Workload Scheduler suite of applications. The Job Scheduling Console provides users with a Java-based user interface to IBM Tivoli Workload Scheduler for z/os and IBM Tivoli Workload Scheduler. The Job Scheduling Console supplements, but does not totally replace, the traditional z/os ISPF panes on the host. It allows you to work with scheduling objects in the following ways: v Define job streams, jobs, workstations, and logical resources in the scheduling database. v Monitor and modify job stream instances, job instances, workstation instances, and resource instances in the plan. The IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide provides an introduction to and an explanation of the IBM Tivoli Workload Scheduler Job Scheduling Console Feature Level 1.3. It explains how to install the console and provides instructions for performing scheduling tasks using IBM Tivoli Workload Scheduler for z/os and IBM Tivoli Workload Scheduler for distributed engines. This chapter describes the modifications made to this guide. The book is now divided into the following parts: v Planning and Installation. See Part 2, Planning, installation and upgrade, on page 9. v Console Overview. See Part 3, Console overview, on page 37. v Defining Objects. See Part 4, Defining objects, on page 51. v Managing Database Objects. See Part 5, Managing database objects, on page 153. v Managing Plans. See Part 6, Managing plans, on page 187. v Troubleshooting. See Part 7, Troubleshooting, on page 269. The previous issue of the book was divided into the following parts: v Planning and Installation v Using the Job Scheduling Console with IBM Tivoli Workload Scheduler for z/os v Using the Job Scheduling Console with IBM Tivoli Workload Scheduler To create a guide that is more task oriented the structure of the book was changed. This change in structure impacts the task sections of the book as illustrated in Figure 1 on page xiv. Copyright IBM Corp. 1991, 2004 xiii

16 Refresh 1 Creating workstations Refresh 2 Creating job streams Creating resources Creating distributed job definitions z/os Managing workstations Managing resources Creating job streams Listing and modifying job streams Listing job stream instances and job Instances Managing job stream instances Managing job instances Managing workstations in the plan Managing resources in the plan Managing database lists Managing jobs Managing job streams Managing workstations and workstation classes Managing domains, Windows users and calendars Managing resources, prompts, and parameters Plan tasks Distributed Creating workstation classes Creating domains Creating Windows users Creating calendars Creating prompts Creating parameters Creating objects using copy Creating object lists Working with object lists Managing workstations Managing job streams Key Definition Monitoring Both Managing resources in the database Managing workstation classes Managing domains Managing Windows users Managing calendars Managing prompts Managing parameters Managing plans Figure 1. Structural changes to the task chapters Who should read this guide Figure 1 illustrates how in the previous edition tasks were divided by engine, and not by task types. A small troubleshooting section has been added to the book, which documents the Job Scheduling Console messages and the most common problems that are encountered with the Job Scheduling Console. This guide is intended for the following audience: v System administrators who have the task of installing the Job Scheduling Console. They should be familiar with one or more of the following operating systems: Microsoft Windows AIX HP-UX Sun Solaris Linux v 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 xiv IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

17 What this guide contains database and plan. They should be familiar with performing these specific tasks and with working in the IBM z/os and Microsoft Windows environments: v Operators who have the responsibility of controlling and monitoring the scheduler plan. 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 environment. This guide contains the following sections: Part 1. Introduction Part 1 provides a description of the Job Scheduling Console and how it fits into the overall topology. It contains the following chapters: Job Scheduling Console overview Describes the overall architecture of Tivoli Workload Scheduler and where the Job Scheduling Console fits into that topology. See Chapter 1, Job Scheduling Console overview, on page 3. Part 2. Planning, installation and upgrade Part 2 provides the information necessary for you to plan and install the Job Scheduling Console and its necessary components. It contains the following chapters: Planning and installing the Job Scheduling Console Describes how to plan and install the Job Scheduling Console. See Chapter 2, Planning and installing the Job Scheduling Console, on page 11. Planning and installing the z/os connector Describes how to plan and install the z/os connector. See Chapter 3, Planning and installing the z/os connector, on page 17. Upgrading the z/os connector Describes how to upgrade the z/os connector. See Chapter 4, Upgrading the z/os connector, on page 27. Installing new languages on an existing installation Describes how to install new languages. See Chapter 5, Installing new languages on an existing installation, on page 31. Uninstalling the components Describes how to uninstall the various components that comprise the Job Scheduling Console. See Chapter 6, Uninstalling the components, on page 33. Part 3. Console overview Part 3 provides an overview of the Job Scheduling Console and a quick start to working with it. It contains the following chapters: Job Scheduling Console object descriptions Describes the objects that are created and managed using the Job Scheduling Console. See Chapter 7, Job Scheduling Console object descriptions, on page 39. About this guide xv

18 Job Scheduling Console quick start guide Describes the tasks that you perform using the Job Scheduling Console, a flow of the task order, and links to those tasks. See Chapter 8, Job Scheduling Console quick start guide, on page 41. Starting the Job Scheduling console Describes starting the console, and of the console elements. See Chapter 9, Starting the Job Scheduling Console, on page 47. Part 4. Definition tasks Part 4 provides the information necessary for you to define database objects, and create the lists you use to manage them. It contains the following chapters: Creating workstations Describes how to create workstations in the z/os and distributed environments. See Chapter 10, Creating workstations, on page 53. Creating Windows users Describes how to create Windows users in the distributed environment. See Chapter 11, Creating Windows users, on page 65. Creating parameters Describes how to create parameters in the distributed environment. See Chapter 12, Creating parameters, on page 67. Creating prompts Describes how to prompts in the distributed environment. See Chapter 13, Creating prompts, on page 69. Creating calendars Describes how to create calendars for the distributed environment. See Chapter 14, Creating calendars, on page 71. Creating domains Describes how to create domains for the distributed environment. See Chapter 15, Creating domains, on page 75. Creating workstation classes Describes how to create workstation classes in the distributed environment. See Chapter 16, Creating workstation classes, on page 77. Creating distributed job definitions Describes how to create job definitions in the distributed environment. See Chapter 17, Creating distributed job definitions, on page 79. Creating job streams Describes how to create job streams in the z/os and distributed environments. See Chapter 18, Creating job streams, on page 85. Creating resources Describes how to create resources in the z/os and distributed environments. See Chapter 19, Creating resources, on page 123. Create objects using create another Describes how to clone objects in the z/os and distributed environments. See Chapter 20, Creating objects using Create Another, on page 127. Creating lists Describes how to create lists in the z/os and distributed environments. See Chapter 21, Creating lists, on page 129. xvi IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

19 Part 5. Managing database objects Part 5 provides the information necessary for you to manage objects in the database after you have created them. It contains the following chapters: Working with object lists Describes how to display tables of database and plan objects using the List function. See Chapter 22, Working with object lists, on page 155. Managing workstations Describes how to manage workstations in the database. See Chapter 23, Managing workstations, on page 159. Managing job streams Describes how to manage z/os and distributed job streams in the database. See Chapter 24, Managing job streams, on page 161. Managing resources Describes how to manage z/os and distributed resources in the database. See Chapter 25, Managing resources, on page 169. Managing job definitions Describes how to manage distributed job definitions in the database. See Chapter 26, Managing job definitions, on page 171. Managing workstation classes Describes how to manage distributed workstation classes in the database. See Chapter 27, Managing workstation classes, on page 175. Managing domains Describes how to manage distributed domains in the database. See Chapter 28, Managing domains, on page 177. Managing windows users Describes how to manage distributed Windows users in the database. See Chapter 29, Managing Windows users, on page 179. Managing calendars Describes how to manage distributed calendars in the database. See Chapter 30, Managing calendars, on page 181. Managing prompts Describes how to manage distributed prompts in the database. See Chapter 31, Managing prompts, on page 183. Managing parameters Describes how to manage distributed parameters in the database. See Chapter 32, Managing parameters, on page 185. Part 6. Managing plans Part 6 provides the information necessary for you to manage objects in z/os and distributed plans. It contains the following chapters: Managing z/os plans Describes how to manage objects in the z/os plan. See Chapter 33, Managing z/os plans, on page 189. Managing distributed plans Describes how to manage objects in the distributed plan. See Chapter 34, Managing distributed plans, on page 217. About this guide xvii

20 Part 7. Troubleshooting Part 7 provides troubleshooting information. It contains the following chapters: Setting traces for the Job Scheduling Console Describes how to set traces for the Job Scheduling Console. See Chapter 35, Setting traces for the Job Scheduling Console, on page 271. Troubleshooting Describes the most common problems and how they are resolved. See Chapter 36, Troubleshooting, on page 273. Job Scheduling Console message Describes the messages. See Chapter 37, Job Scheduling Console messages, on page 279. Part 8. Appendixes Part 8 provides general information. It contains the following appendixes: Accessibility Describes the accessibility features of the Job Scheduling Console. See Appendix A, Accessibility, on page 321. Setting security Describes setting SSL security features. See Appendix B, Setting Security, on page 323. Status description and mapping Describes job and job stream states within the Job Scheduling Console and how to map between the console and engine states. See Appendix C, Status description and mapping, on page 325. Support information Describes how to contact IBM support. See Appendix D, Support information, on page 329 Publications This section lists publications in the Tivoli Workload Scheduler library and any other related documents. It also describes how to access Tivoli publications online and how to order Tivoli publications. Tivoli Workload Scheduler library Tivoli Workload Scheduler comprises several separate products available on a variety of platforms, and the library is similarly divided: IBM Tivoli Workload Scheduling suite library This library contains all cross-platform and cross-product publications for Tivoli Workload Scheduler. IBM Tivoli Workload Scheduler distributed library This library contains all of the publications that refer to using Tivoli Workload Scheduler on platforms other than z/os. IBM Tivoli Workload Scheduler for z/os library This library contains all publications that apply only to IBM Tivoli Workload Scheduler for z/os. xviii IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

21 IBM Tivoli Workload Scheduler for Applications library This library contains all publications that apply only to IBM Tivoli Workload Scheduler for Applications. IBM Tivoli Workload Scheduler for Virtualized Data Centers library This library contains all publications that apply only to IBM Tivoli Workload Scheduler for Virtualized Data Centers. IBM Tivoli Workload Scheduling suite library The following publications are available in the IBM Tivoli Workload Scheduling suite library. This includes publications which are common to all products, platforms, and components. v IBM Tivoli Workload Scheduler: General Information, SC Provides general information about all Tivoli Workload Scheduler products. It gives an overview of how they can be used together to provide workload management solutions for your whole enterprise. v IBM Tivoli Workload Scheduler: Job Scheduling Console User s Guide, SC Describes how to work with Tivoli Workload Scheduler, regardless of platform, using a common GUI called the job scheduling console. v IBM Tivoli Workload Scheduler: Job Scheduling Console Release Notes, SC Provides late-breaking information about the job scheduling console. v IBM Tivoli Workload Scheduler: Warehouse Enablement Pack Version Implementation Guide for Tivoli Enterprise Data Warehouse, Version 1.1, Provides information about enabling Tivoli Workload Scheduler for Tivoli Data Warehouse. Note: This guide is only available on the product CD. It is not possible to access it online, as you can the other books (see Accessing publications online on page xxii). IBM Tivoli Workload Scheduler distributed library The following publications are available in the IBM Tivoli Workload Scheduler distributed library. This includes publications which refer to using the product on all platforms except z/os. v IBM Tivoli Workload Scheduler: Release Notes, SC Provides late-breaking information about Tivoli Workload Scheduler on platforms other than z/os. v IBM Tivoli Workload Scheduler: Planning and Installation Guide, SC Describes how to plan for and install IBM Tivoli Workload Scheduler on platforms other than z/os, and how to integrate Tivoli Workload Scheduler with NetView, Tivoli Data Warehouse, and IBM IBM Tivoli Business Systems Manager. v IBM Tivoli Workload Scheduler: Reference Guide, SC Describes the Tivoli Workload Scheduler command line used on platforms other than z/os, and how extended and network agents work. v IBM Tivoli Workload Scheduler: Administration and Troubleshooting, SC Provides information about how to administer Tivoli Workload Scheduler on platforms other than z/os, and what to do if things go wrong. It includes help on many messages generated by the main components of Tivoli Workload Scheduler. v IBM Tivoli Workload Scheduler: Limited Fault-tolerant Agent for OS/400, SC About this guide xix

22 Describes how to install, configure, and use Tivoli Workload Scheduler limited fault-tolerant agents on AS/400. v IBM Tivoli Workload Scheduler: Plus Module User s Guide, SC Describes how to set up and use the Tivoli Workload Scheduler Plus module. See for an introduction to the product. IBM Tivoli Workload Scheduler for z/os library The following documents are available in the Tivoli Workload Scheduler for z/os library: v IBM Tivoli Workload Scheduler for z/os: Getting Started, SC Discusses how to define your installation data for Tivoli Workload Scheduler for z/os and how to create and modify plans. v IBM Tivoli Workload Scheduler for z/os: Installation Guide Describes how to install Tivoli Workload Scheduler for z/os. v IBM Tivoli Workload Scheduler for z/os: Customization and Tuning, SC Describes how to customize Tivoli Workload Scheduler for z/os. v IBM Tivoli Workload Scheduler for z/os: Managing the Workload, SC Explains how to plan and schedule the workload and how to control and monitor the current plan. v IBM Tivoli Workload Scheduler for z/os: Quick Reference, SC Provides a quick and easy consultation reference to operate Tivoli Workload Scheduler for z/os. v IBM Tivoli Workload Scheduler for z/os: Diagnosis Guide and Reference, SC Provides information to help diagnose and correct possible problems when using Tivoli Workload Scheduler for z/os. v IBM Tivoli Workload Scheduler for z/os: Messages and Codes, SC Explains messages and codes in Tivoli Workload Scheduler for z/os. v IBM Tivoli Workload Scheduler for z/os: Programming Interfaces, SC Provides information to write application programs for Tivoli Workload Scheduler for z/os. v IBM Tivoli Workload Scheduler for z/os: Licensed Program Specifications, GI Provides planning information about Tivoli Workload Scheduler for z/os. v IBM Tivoli Workload Scheduler for z/os: Memo for program 5697-WSZ, GI Provides a summary of changes for the current release of the product. v IBM Tivoli Workload Scheduler for z/os: Program Directory for program 5697-WSZ, GI Provided with the installation tape for Tivoli Workload Scheduler for z/os (program 5697-WSZ), describes all of the installation materials and gives installation instructions specific to the product release level or feature number. v IBM Tivoli Workload Scheduler for z/os: Program Directory for program 5698-WSZ, GI Provided with the installation tape for Tivoli Workload Scheduler for z/os (program 5698-WSC), describes all of the installation materials and gives installation instructions specific to the product release level or feature number. See for an introduction to the product. xx IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

23 Related IBM Tivoli Workload Scheduler for Applications library The following manuals are available in the IBM Tivoli Workload Scheduler for Applications library: v IBM Tivoli Workload Scheduler for Applications: Release Notes, SC Provides late-breaking information about the Tivoli Workload Scheduler extended agents. v IBM Tivoli Workload Scheduler for Applications: User s Guide, SC Describes how to install, use, and troubleshoot the Tivoli Workload Scheduler extended agents. See for an introduction to the product. IBM Tivoli Workload Scheduler for Virtualized Data Centers library The following manuals are available in the IBM Tivoli Workload Scheduler for Virtualized Data Centers library: v IBM Tivoli Workload Scheduler for Virtualized Data Centers: Release Notes, SC Provides late-breaking information about Tivoli Workload Scheduler for Virtualized Data Centers. v IBM Tivoli Workload Scheduler for Virtualized Data Centers: User s Guide, SC Describes how to extend the scheduling capabilities of Tivoli Workload Scheduler to workload optimization and grid computing by enabling the control of IBM LoadLeveler and IBM Grid Toolbox jobs. See products/y614224t20392s50.html for an introduction to the product. publications The following publications provide additional information: v IBM Redbooks : High Availability Scenarios with IBM Tivoli Workload Scheduler and IBM Tivoli Framework This IBM Redbook, shows you how to design and create highly available IBM Tivoli Workload Scheduler and IBM Tivoli Management Framework (TMR server, Managed Nodes and Endpoints) environments. It presents High Availability Cluster Multiprocessing (HACMP ) for AIX and Microsoft Windows Cluster Service (MSCS) case studies. This Redbook can be found on the Redbooks Web site at v IBM Redbooks: Customizing IBM Tivoli Workload Scheduler for z/os V8.2 to Improve Performance This IBM Redbook covers the techniques that can be used to improve the performance of Tivoli Workload Scheduler for z/os (including end-to-end scheduling). This Redbook can be found on the Redbooks Web site at v IBM Redbooks: End-to-End Scheduling with IBM Tivoli Workload Scheduler Version 8.2 This IBM Redbook considers how best to provide end-to-end scheduling using Tivoli Workload Scheduler Version 8.2, both distributed (previously known as Maestro ) and mainframe (previously known as OPC) components. This Redbook can be found on the Redbooks Web site at About this guide xxi

24 The Tivoli Software Glossary includes definitions for many of the technical terms related to Tivoli software. The Tivoli Software Glossary is available, in English only, at the following Web site: Accessing publications online The product CD contains the publications that are in the product library. The format of the publications is PDF, HTML, or both. To access the publications using a Web browser, open the infocenter.html file. The file is in the appropriate publications directory on the product CD. Ordering IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli software information center Web site. Access the Tivoli software information center by first going to the Tivoli software library at the following Web address: Scroll down and click the Product manuals link. In the Tivoli Technical Product Documents Alphabetical Listing window, click the appropriate Tivoli Workload Scheduler product link to access the product s libraries at the Tivoli software information center. All publications in the Tivoli Workload Scheduler suite library, distributed library and z/os library can be found under the entry Tivoli Workload Scheduler. Note: If you print PDF documents on other than letter-sized paper, set the option in the File Print window that allows Adobe Reader to print letter-sized pages on your local paper. Tivoli Workload Scheduler online books All the books in the Tivoli Workload Scheduler for z/os library, are available in displayable softcopy form on CD-ROM in the IBM Online Library: z/os Software Products Collection Kit, SK3T You can read the softcopy books on CD-ROMs using these IBM licensed programs: v BookManager READ/2 (program number ) v BookManager READ/DOS (program number ) v BookManager READ/6000 (program number ) All the BookManager programs need a personal computer equipped with a CD-ROM disk drive (capable of reading disks formatted in the ISO 9660 standard) and a matching adapter and cable. For additional hardware and software information, refer to the documentation for the specific BookManager product you are using. Updates to books between releases are provided in softcopy only. publications You can order many Tivoli publications online at the following Web site: publications/cgibin/pbi.cgi You can also order by telephone by calling one of these numbers: v In the United States: xxii IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

25 v In Canada: In other countries, see the following Web site for a list of telephone numbers: Accessibility Tivoli technical training Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to use software products With this product, you can use assistive technologies to hear and navigate the interface. You can also use the keyboard instead of the mouse to operate all features of the graphical user interface. For additional information, see Appendix A, Accessibility, on page 321. For Tivoli technical training information, refer to the following IBM Tivoli Education Web site: Support information If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need: v Searching knowledge bases: You can search across a large collection of known problems and workarounds, Technotes, and other information. v Obtaining fixes: You can locate the latest fixes that are already available for your product. v Contacting IBM Software Support: If you still cannot solve your problem, and you need to work with someone from IBM, you can use a variety of ways to contact IBM Software Support. For more information about these three ways of resolving problems, see Appendix D, Support information, on page 329. Conventions used in this guide Typeface This guide uses several conventions for special terms and actions, operating system-dependent commands and paths, comman syntax, and margin graphics. conventions This guide uses the following typeface conventions: Bold v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text v Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) v Keywords and parameters in text About this guide xxiii

26 Italic v Words defined in text v Emphasis of words (words as words) v New terms in text (except in a definition list) v Variables and values you must provide Monospace v Examples and code examples v File names, programming keywords, and other elements that are difficult to distinguish from surrounding text v Message text and prompts addressed to the user v Text that the user must type v Values for arguments or command options Operating system-dependent variables and paths Command This guide uses the UNIX convention for specifying environment variables and for directory notation. When using the Windows command line, replace $variable with % variable% for environment variables and replace each forward slash (/) with a backslash (\) in directory paths. The names of environment variables are not always the same in Windows and UNIX. For example, %TEMP% in Windows is equivalent to $tmp in UNIX. Note: If you are using the bash shell on a Windows system, you can use the UNIX conventions. syntax This guide uses the following syntax wherever it describes commands: Table 1. Command syntax Syntax convention Description Brackets ([ ]) The information enclosed in brackets ([ ]) is optional. Anything not enclosed in brackets must be specified. Braces ({ }) Braces ({ }) identify a set of mutually exclusive options, when one option is required. Underscore ( _ ) An underscore (_) connects multiple words in a variable. Vertical bar ( ) Mutually exclusive options are separated by a vertical bar( ). You can enter one of the options separated by the vertical bar, but you cannot enter multiple options in a single use of the command. A vertical bar can be used to separate optional or required options. Bold Bold text designates literal information that must be entered on the command line exactly as shown. This applies to command names and non-variable options. Italic Italic text is variable and must be replaced by whatever it represents. xxiv IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

27 Part 1. Introduction Chapter 1. Job Scheduling Console overview.. 3 Tivoli Workload Scheduler architecture Components Topology Connection Copyright IBM Corp. 1991,

28 2 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

29 Chapter 1. Job Scheduling Console overview The job scheduling console is an interactive interface for creating, modifying, and deleting objects in the product database of Tivoli Workload Scheduler. It also allows you to monitor and control objects scheduled in the current plan. The job scheduling console is part of the distributed architecture, but allows you to work with Tivoli Workload Scheduler on both z/os and distributed engines simultaneously. This chapter describes the overall architecture of Tivoli Workload Scheduler and where the Job Scheduling Console fits into that topology. Tivoli Workload Scheduler architecture This section describes the components, topology and connection of a Tivoli Workload Scheduler. Components A Tivoli Workload Scheduler network is made up of the following types of workstation: Master Domain Manager (MDM) The master domain manager is the topmost domain of a Tivoli Workload Scheduler network. It contains the centralized database files used to document scheduling objects. It creates the Production plan, distributes it to all the agents in the network at the start of each day, and performs all logging and reporting for the network. Fault-tolerant Agent (FTA) A workstation capable of resolving local dependencies and launching its jobs in the absence of a domain manager. Standard Agent A workstation that launches jobs only under the direction of its domain manager. The workstation types can assume the following roles: Parent Domain The domain directly above the current domain. All domains, except the master domain, have a parent domain. All communication to and from a domain is rooted through the parent domain manager. Backup Master A fault-tolerant agent capable of assuming the responsibilities of the master domain manager. Domain Manager The management hub in a domain. All communications to and from the agents in a domain are routed through the domain manager. Backup Domain Manager A fault-tolerant agent capable of assuming the responsibilities of its domain manager. Copyright IBM Corp. 1991,

30 Architecture Host The scheduling function required by extended agents. It can be performed by any Tivoli Workload Scheduler workstation, except another extended agent. Extended Agent A logical workstation definition that enables you to launch and control jobs on other systems and applications. Network Agent A logical workstation definition for creating dependencies between jobs and job streams in separate Tivoli Workload Scheduler networks. Topology Your Tivoli Workload Scheduler topology can be complex or simple according to your job scheduling requirements. Figure 2 shows a single tier hierarchy, where the agents are directly connected to the master domain manager. JSC Master Domain Manager FTAs AIX Linux Windows Solaris Figure 2. Single tier topology Figure 3 on page 5 shows a multi tier hierarchy where the agents are connected to a domain manager at the various tiers of the topology. 4 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

31 Architecture Master Domain JSC Master Domain Manager Backup Master FTA DomainA DomainB Domain Manager Domain Manager Backup Domain Manager FTA SA FTA FTA DomainC DomainD DomainE DM DM DM FTA FTA FTA FTA FTA FTA Figure 3. Multi tier topology The domain manager of domain A acts as the master domain manager for domain C, and the domain manager of domain B acts as the master domain manager for domains D and E. Normally you would connect the Job Scheduling Console to the master domain manager to control your job scheduling activities, but there is no reason why you should not connect to a domain manager or a fault-tolerant agent. Figure 4 on page 6 shows an end-to-end topology with the Job Scheduling Console connected to the z/os master domain. Chapter 1. Job Scheduling Console overview 5

32 Architecture OPCMASTER JSC z/os Master Domain Manager DomainZ Domain Manager AIX DomainA DomainB AIX Domain Manager Domain Manager HPUX SA FTA FTA FTA Figure 4. End-to-end topology with Job Scheduling Console Connection The Job Scheduling Console connects to the engines through the Job Scheduling Services and the relevant connector. The connectors must be installed together with the Job Scheduling Services on a Tivoli Management Framework server. The Job Scheduling Console communicates with the system through the connector, a protocol converter that translates the instructions entered through the Job Scheduling Console into scheduler commands. 6 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

33 Architecture JSC Tivoli Framework Job Scheduling Services z/os Connector Distributed Connector Figure 5. Job Scheduling Console connection You can manage plan and database objects not only from the master or agent workstations, but also from any system on which the job scheduling console is installed with a TCP/IP connection to the master or the fault-tolerant agent running the connector. You can manage IBM Tivoli Workload Scheduler for z/os and distributed engine database and plan objects from the same Job Scheduling Console provided you install the relevant connectors. Chapter 1. Job Scheduling Console overview 7

34 Architecture 8 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

35 Part 2. Planning, installation and upgrade Chapter 2. Planning and installing the Job Scheduling Console Planning installation Installation methods ISMP installation wizard Software Distribution Installing using the installation wizard Running the installation wizard Performing a silent installation Installing using Software Distribution Installing from the command line Installing the Java Virtual Machine Chapter 3. Planning and installing the z/os connector Planning connector installations Installation methods Installing from the Tivoli Desktop Installing Job Scheduling Services from the Tivoli Desktop Installing the connector from the Tivoli Desktop 18 Installing using the installation wizard Performing a silent installation Installing from the command line Installing Job Scheduling Services from the command line Installing the connector from the command line 21 Customizing the connector Authorization roles required for instances...21 Managing z/os connector instances with wopcconn Managing distributed connector instances with wtwsconn Installation scenarios Useful framework commands Chapter 4. Upgrading the z/os connector Upgrading using the installation wizard Upgrade scenarios Upgrading using the Tivoli Desktop Upgrading using the command line Chapter 5. Installing new languages on an existing installation Installing new languages using the installation wizard Chapter 6. Uninstalling the components Setting the Tivoli Environment Uninstalling the Job Scheduling Console Uninstalling the Job Scheduling Console using the Software Distribution CLI Uninstalling the Job Scheduling Services Uninstalling the connectors Copyright IBM Corp. 1991,

36 10 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

37 Chapter 2. Planning and installing the Job Scheduling Console This chapter describes installation of the Job Scheduling Console. It describes: v Planning Installations v Installing Using ISMP v Installing Using Software Distribution Planning installation This section provides you with the information that is necessary for you to plan your Job Scheduling Console installations. It outlines the necessary components for running the Job Scheduling Console and the installation methods you can use to install. The Job Scheduling Console can be installed on any workstation that has a TCP/IP connection. For the most current information about supported platforms and system requirements, refer to IBM Tivoli Workload Scheduler Job Scheduling Console Release Notes. You can install only one instance of the Job Scheduling Console on each machine. To use the Job Scheduling Console, you first need to have the components described below installed on your network. Install the components in the order in which they are listed. You can install the IBM Tivoli Workload Scheduler for z/os connector, or IBM Tivoli Workload Scheduler connector, or both, depending on your working environment. Although the connector must be running to use the console, you can install them in the order you prefer. Table 2. Job Scheduling Console prerequisite components Component Installation location Tivoli Management Framework Tivoli Management Region server (Tivoli server) and managed nodes. Job Scheduling Services Tivoli server and each managed node where any of the connectors are to be installed. IBM Tivoli Workload Scheduler for z/os connector IBM Tivoli Workload Scheduler connector Tivoli server or managed node. Tivoli server and managed node where the scheduler master is installed. If you install the connector on one or more managed nodes, you must also install it on the Tivoli server. Note: If you use the installation wizard, Job Scheduling Services is installed automatically and no user intervention is required. The connectors for the distributed environment are installed with the engine. For information about installing them, see IBM Tivoli Workload Scheduler Planning and Installation Guide. For information about installing the z/os connectors, see Chapter 3, Planning and installing the z/os connector, on page 17. Copyright IBM Corp. 1991,

38 Planning installation Installation methods You can use the following methods to install the Job Scheduling Console: v ISMP Installation Wizard v Software Distribution ISMP installation wizard When you are installing the Job Scheduling Console on a single workstation, you can use the installation wizard in interactive or silent mode. In interactive mode, the wizard guides you through the installation steps. In silent mode a response file provides the relevant information to the install process, which is run in background without user intervention. For information about installing using the wizard, see Installing using the installation wizard. Software Distribution When you are installing the Job Scheduling Console on more than one workstation simultaneously, you can use a software package block (SPB) of Tivoli Configuration Manager in interactive or silent mode. In interactive mode, the Tivoli Desktop guides you through the installation steps. In silent mode, you can use a connected Tivoli Configuration Manager command line interface. For information about installing using Software Distribution, see Installing using Software Distribution on page 13 and IBM Tivoli Configuration Manager, User s Guide for Software Distribution. Installing using the installation wizard Using the wizard you can install directly from the CDs. On UNIX systems, you can copy the CD to a file system and mount that file system. On Windows systems, you can copy the CD to a network drive and map that network drive. The installation wizard can perform the operations listed below. Proceed to one of the following sections: v Running the installation wizard v Installing new languages using the installation wizard on page 31 v Repairing the installation on page 276 Running the installation wizard If no previously installed version of the Job Scheduling Console is detected, the product is installed. A new installation, has a full, typical, or custom option. To perform a first-time product installation, complete the following steps: 1. Navigate to the JSC directory. 2. Run the installation executable according to the operating system where you are installing: v Windows: setup.exe v UNIX: setup.bin 3. Select the language of the installation wizard. Click OK. 4. Read the welcome information. Click Next. 5. Read and accept the license agreement. Click Next. 6. Accept the default installation directory, or click Browse or type the path name to select a different directory. Click Next. 12 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

39 Using the installation wizard Note: The Job Scheduling Console installation directory inherits the access rights of the directory where the installation is performed. Because the Job Scheduling Console requires user settings to be saved, it is important to select a directory in which users are granted access rights. The maximum number of characters for the installation directory is Select the type of installation you want to perform: v Typical. English and the language of the locale are installed. Click Next. v Custom. Select the languages you want to install. Click Next. v Full. All languages are automatically selected for installation. Click Next 8. Select the locations for the Job Scheduling Console icons. Click Next. 9. Review the installation settings. Click Next. The installation is started. 10. When the installation completes, a panel displays a successful installation or contains a list of which items failed to install and the location of the log file containing the details of the errors. See Job Scheduling Console installation log on page Click Finish. Performing a silent installation Silent installation allows you to install in background. A template for a response file is provided on the IBM Tivoli Workload Scheduler Job Scheduling Console CD 1 in the Response_File folder. You can copy the response file to your system and edit it as required. Instructions for editing the response file are provided in the response file itself. The following options are available in the response file: v Installation location v Icon location v Installation type: Typical, Custom, Full v Language pack installation To start the installation in silent mode on Windows systems, enter the following command: SETUP.exe -silent -options filename To start the installation in silent mode on UNIX systems, enter the following command: setup.bin -silent -options filename specifying the fully qualified path to the response file. Note: The parameters of the silent install are described in detail as comments in the response file. Installing using Software Distribution The Job Scheduling Console can be installed by distributing a software package block (SPB) using the software distribution component of IBM Tivoli Configuration Manager, Version 4.2. You can distribute the SPB locally or remotely, using either the command line interface or the Tivoli desktop. Chapter 2. Planning and installing the Job Scheduling Console 13

40 Using Software Distribution On the IBM Tivoli Workload Scheduler Job Scheduling Console CD 1, locate the directory of the platform where you want to install the Job Scheduling Console. The following two software package blocks exist for each supported platform: TWSConsole.spb Installs the Job Scheduling Console. TWSConsoleLanguages.spb Installs one or more language packs. Table 3 describes the Job Scheduling Console parameter used by the software package block to define the installation directory. This parameter is defined as a default variable in the software package. Table 3. Installation parameter Default Variable Default Value Value and Description Required INSTALL_DIR $(INSTALL_DIR_$ (os_name)) The fully qualified path to the location of the Job Scheduling Console installation. This path is created if it does not already exist. No The INSTALL_DIR variable is resolved to the appropriate value depending on the operating system where you are installing. Default values for each operating system are listed in the table below. The INSTALL_DIR variable overrides the operating system variables, if specified. Table 4. Operating system variables Default variable Default value INSTALL_DIR_Linux INSTALL_DIR_Windows_NT INSTALL_DIR_AIX INSTALL_DIR_HP-UX INSTALL_DIR_SunOS /opt/jsc_1_3 $(program_files)\jsc_1_3 /opt/jsc_1_3 /opt/jsc_1_3 /opt/jsc_1_3 To perform the installation, complete the following steps: 1. Import the software package block. 2. Install the software package block. For complete instructions on performing these tasks, refer to the IBM Tivoli Configuration Manager, User s Guide for Software Distribution. Installing from the command line When you have an open connection to Tivoli Configuration Manager you can use the command line to install the Job Scheduling Console software packages. Enter the following command: winstsp f [ D INSTALL_DIR =Installation Path] TWSConsole.spb where: D INSTALL_DIR Specifies the path to the directory where the product is to be installed. If no path is specified, the default value is assumed. 14 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

41 Using Software Distribution TWSConsole.spb Specifies the path to the directory where the TWSConsole.spb software package is located. To install the Job Scheduling Console language packs, ensure you have set the Tivoli environment (see Table 5 on page 17), then type the following command: winstsp f [ D INSTALL_DIR =Installation Path] TWSConsoleLanguages.spb where: D INSTALL_DIR Specifies the path to the directory where the product is to be installed. If no path is specified, the default value is assumed. If you specify a path, use the same path defined when installing the Job Scheduling Console. TWSConsoleLanguages.spb Specifies the path to the directory where the TWSConsoleLanguages.spb software package is located. By default, all languages are selected for installation. The following is an example of the syntax for installing the Italian language pack: winstsp f [ D INSTALL_DIR =Installation Path] D zh_cn=false D it=true D ko=false D es=false D zh_tw=false D ja=false D pt_br=false D de=false D fr=false TWSConsoleLanguages.spb Installing the Java Virtual Machine If you install the Job Scheduling Console using Software Distribution, the Java Virtual Machine is not installed. You have to install it separately after installing the Job Scheduling Console using the software package blocks provided in the Tivoli Workload Scheduler Job Scheduling Console CD 2 in the JVM_CM folder. A software package block is provided for each supported operating system. The Java Virtual Machine software packages are automatically installed in the Job Scheduling Console installation directory. To perform the installation, complete the following steps: 1. Import the software package block. 2. Install the software package block. For complete instructions on performing these tasks, refer to the IBM Tivoli Configuration Manager, User s Guide for Software Distribution. To install the Java Virtual Machine using software packages, enter the following command: winstsp f JRE131_operatingsystem.spb where: JRE131_operatingsystem.spb Specifies the path to the directory where the Java Virtual Machine software package for each supported operating system is located. Chapter 2. Planning and installing the Job Scheduling Console 15

42 Using Software Distribution 16 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

43 Chapter 3. Planning and installing the z/os connector This chapter describes the installation of the z/os connectors needed by the Job Scheduling Console to connect to z/os engines. Note: Before installing the connectors, back up your Tivoli database. For information about installing the connectors for distributed engines, refer to IBM Tivoli Workload Scheduler Planning and Installation Guide. Planning connector installations Tivoli Management Framework versions or 4.1 and job scheduling services version 1.2 are a prerequisite for installing or upgrading to connector version 1.3. You must install the connector on a Tivoli server or managed node. For the connector to function the job scheduling services must also be installed on the Tivoli server and each managed node where the connector is installed. For information about how to install a Tivoli server or managed node, refer to the Tivoli Enterprise Installation Guide and the Tivoli Management Framework Release Notes. For the most current information about supported platforms and system requirements, refer to the IBM Tivoli Workload Scheduler Release Notes. To perform the installation, you must first set the Tivoli environment. To do this, log in as root or administrator, then enter one of the following commands: Table 5. Setting the Tivoli Environment For this operating system... Enter this command... AIX, Solaris, HP-UX, Linux. /etc/tivoli/setup_env.sh Microsoft Windows, UNIX shell. c:/windir/system32/drivers/etc/tivoli/setup_env.sh Microsoft Windows, DOS shell c:\windir\system32\drivers\etc\tivoli\setup_env.cmd where windir is the name of the Microsoft Windows installation directory. Note: If it is the first time that you are running the setup_env.sh, you must make it an executable. Installation methods You can install and upgrade the components of the connector using any of the following installation mechanisms: v Using the Tivoli desktop, where you select which product and patches to install on which machine. v Using an installation wizard that creates a new Tivoli server and automatically installs or upgrades the IBM Tivoli Workload Scheduler connector and job scheduling services. For more information, refer to IBM Tivoli Workload Scheduler: Planning and Installation Guide. v Using winstall command provided by Tivoli Management Framework, where you specify which products and patches to install on which machine. Copyright IBM Corp. 1991,

44 Using Tivoli Desktop Installing from the Tivoli Desktop Before installing the connector, ensure you have installed job scheduling services. Installing Job Scheduling Services from the Tivoli Desktop To install the job scheduling services, perform the following steps: 1. Open the Tivoli Desktop. 2. From the Desktop menu select Install, then Install Product. The Install Product window is displayed. 3. Click Select Media to select the installation directory. The File Browser window is displayed. 4. Type or select the installation path that path includes the directory containing the CONTENTS.LST file: <INSTALL_DIR>\CONNECT\TWS4ZOS\CFG. 5. Click Set Media & Close. 6. In the Select Product to Install list, select Tivoli Job Scheduling Services v In the Available Clients list, select the managed nodes to install on and move them to the Clients to Install On list. 8. Click Install. The Product Install window is displayed, which shows the operations to be performed by the installation program. 9. Click Continue Install, or click Cancel to cancel the installation. 10. The installation program copies the files and configures the Tivoli database with the new classes. When the installation is complete, the message Finished product installation appears. Click Close. Installing the connector from the Tivoli Desktop To install the connector, perform the following steps: 1. Open the Tivoli Desktop. 2. From the Desktop menu, select Install, then Install Product. The Install Product window is displayed. 3. Click Select Media to select the installation directory. The File Browser window is displayed. 4. Type or select the installation path that path includes the directory containing the CONTENTS.LST file: <INSTALL_DIR>\CONNECT\TWS4ZOS\CFG 5. Click Set Media & Close. You return to the Install Product window. 6. Select IBM Tivoli Workload Scheduler Connector for z/os v In the Available Clients list, select the managed nodes to install on and move them to the Clients to Install On list. 8. Click Install. The Product Install window is displayed, which shows the operations to be performed by the installation program. 9. Click Continue Install to continue the installation or click Cancel to cancel the installation. 10. The installation program copies the files and configures the Tivoli database with the new classes. When the installation is complete, the message Finished product installation appears. Click Close. 18 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

45 Using the installation wizard Installing using the installation wizard Using the installation wizard you can only install components on the Tivoli server. To install components on the Tivoli server and on managed nodes, see Installing from the Tivoli Desktop on page 18 and Installing from the command line on page 20. Note: If Tivoli Management Framework is not installed and you are installing from a CD, it is recommended that you copy the setup or SETUP.exe file for the operating system you are installing on to a local directory and start the installation from your system. To perform the installation on the server, complete the following steps: 1. Insert the IBM Tivoli Workload Scheduler Job Scheduling Console CD 2 in the CD-ROM drive. 2. Navigate to the CONNECT directory. 3. Run the setup according to the operating system where you are installing: v Windows: SETUP.exe v UNIX: setup 4. Select the language of the installation wizard. Click OK. 5. Read the Welcome information. Click Next. The installation program verifies that the current user has the necessary rights for performing the installation. A check is performed to detect any previous installations of Tivoli Management Framework, job scheduling services and the connectors on the Tivoli server and in the Tivoli Management region. See Installation scenarios on page 23 for further information. 6. Read and accept the license agreement. Click Next. 7. When the installation wizard does not detect a previous installation, a dialog is displayed requesting information for installing Tivoli Management Framework version 4.1. a. In the Destination Directory text field, type the name of the directory where you want to install Tivoli Management Framework, or use the Browse button to locate it. This field is required. The remaining fields are optional and apply if you intend to deploy Tivoli programs or managed nodes in your Tivoli Management Framework environment. The following fields are displayed only on Windows systems. v In the Remote Access Account text field, type the Tivoli remote access account name through which Tivoli programs will access remote file systems. This field is optional. v In the Password text field, type the password for the remote access account. This field is optional. v In the Installation Password text field, type an installation password that must be used when installing managed nodes. This field is optional. Click Next. 8. Select Yes in the Create Instance section to create an instance. You can optionally create the instance later, as described in Managing z/os connector instances with wopcconn on page 22. When you select Yes, a dialog is displayed requesting information for creating the instance. a. In Engine Name, type the name of the new instance. Preferably, use the name of the controller agent as the instance name. b. In IP Address or Hostname, type the IP address of the z/os system where the scheduler subsystem that you want to connect to is installed. Chapter 3. Planning and installing the z/os connector 19

46 Using the installation wizard c. In IP port number, type the port number of the TCP/IP server to which the connector will connect. Click Next. 9. Review the installation settings and click Next. The installation is started. 10. If you chose to install Tivoli Management Framework, a dialog is displayed requesting installation information. Type the path to the TMF.IND file in the Destination directory. Click OK. Note: On Windows systems, if Tivoli Management Framework is being installed for the first time, the system has to be rebooted. After reboot, the installation wizard continues the installation and requires you to specify the path to the TMF_JSS.IND and TWS_CONN.IND files when installing the job scheduling services and the connector. 11. When the installation completes, a panel displays a successful installation or contains a list of which items failed to install and the location of the log file. 12. Click Finish. Performing a silent installation Silent installation allows you to install in background. A template for a response file is provided on the IBM Tivoli Workload Scheduler Job Scheduling Console CD 2 in the RESPONSE_FILE folder. You can copy the response file to your system and edit it as necessary. The following options are available in the response file: v Tivoli Management Framework installation location v Tivoli Management Framework language pack installation v Connector instance creation To start the installation in silent mode on Windows systems, type the following command: SETUP.exe -silent -options filename To start the installation in silent mode on UNIX systems, type the following command: setup -silent -options filename specifying the fully qualified path to the response file. Note: The parameters of the silent install are described in detail as comments in the response file. Installing from the command line Before installing the IBM Tivoli Workload Scheduler for z/os connector, ensure you have installed job scheduling services. Installing Job Scheduling Services from the command line To install job scheduling services from a connected Tivoli Configuration Manager command line, enter on the Tivoli server one of the commands described below. v To install on all managed nodes: winstall -c install_dir -i TMF_JSS v To install on only one managed node: 20 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

47 Using the command line winstall -c install_dir -i TMF_JSS node where: install_dir Is the path to the TMF_JSS.IND file. node Is the name of the destination managed node. If the managed node is located on the Tivoli server, or if you do not specify the node variable, the commands are applied to all managed nodes in the Tivoli Management Region. Installing the connector from the command line To install the connector from a connected Tivoli Configuration Manager command line, enter one of the following commands: v To install the z/os connector on all managed nodes: winstall -c install_dir -i opc v To install the z/os connector on only one managed node: winstall -c install_dir -i opc node where: Customizing the connector install_dir Is the path to the OPC.IND file. node Is the name of the destination managed node. If the managed node is located on the Tivoli server, or if you do not specify the node variable, the commands are applied to all managed nodes in the Tivoli Management Region. This section describes how to customize the connector. Authorization roles required for instances To manage connector instances from a Tivoli server or managed node, you must be a Tivoli administrator with one or more of the following roles: Table 6. Authorization roles These roles... Can perform these tasks... user Use the instances View instance settings admin, senior, super Perform all actions available to the user role Create and remove instances Change instance settings Start and stop instances Note: To control access to the scheduler, the TCP/IP server associates each Tivoli administrator to a Remote Access Control Facility (RACF ) user. For this reason, a Tivoli administrator should be defined for every RACF user, while several RACF users can be associated to the same Tivoli administrator. You can perform this operation from the Tivoli desktop, as described in the following steps: 1. Open the Tivoli desktop. 2. Perform one of the following operations: Chapter 3. Planning and installing the z/os connector 21

48 Customizing the connector v Add the user login to the Edit Logins window for Tivoli Administrators. v Create a Tivoli administrator with the same login as the RACF user. For additional information, refer to the IBM Tivoli Workload Scheduler for z/os Customization and Tuning. Managing z/os connector instances with wopcconn For the z/os environment, you can use the wopcconn utility to create, remove, and manage connector instances. This program is downloaded when you install the connector. Before you use wopcconn, you must set the Tivoli environment. See Setting the Tivoli Environment on page 33. The following table describes how to use wopcconn on the command line to manage connector instances: To do this... Use this command... Create an instance wopcconn -create -h node -e engine_name -a address -p port Stop an instance wopcconn -stop -e engine_name -o object_id Start an instance wopcconn -start -e engine_name -o object_id Restart an instance wopcconn -restart -e engine_name -o object_id Remove an instance wopcconn -remove -e engine_name -o object_id View the settings of an instance. Also view other information, such as product version and the object ID of the instance. Change the settings of an instance wopcconn -view -e engine_name -o object_id 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. The name of the Tivoli server is the default. engine_name Is the name of the new or existing instance. object_id Is the object ID of the instance. For information on how to obtain the object ID, see Table 8 on page 24. new_name Is the new name for the instance. address Is the IP address of the z/os system where the IBM Tivoli Workload Scheduler for z/os subsystem that you want to connect to is installed. port Is the port number of the IBM Tivoli Workload Scheduler for z/os TCP/IP server to which the connector must connect. trace_level Is the trace detail level, from 0 to 5. The default value is 0. trace_length Is the maximum length of the trace file. 22 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

49 Managing distributed connector instances with wtwsconn You install the distributed connectors when you install the engine components. For information about installing the distributed connector, see IBM Tivoli Workload Scheduler Planning and Installation Guide. Use the wtwsconn utility to create, remove, and manage connector instances. This utility is downloaded when you install the Connector. Before you use wtwsconn, you must set the Tivoli environment. See Table 5 on page 17. The following table describes how to use wtwsconn in the command line to manage connector instances. To do this... Use this command... Create an instance wtwsconn.sh -create [-h node] -n instance -t twsdir Stop an instance wtwsconn.sh -stop -n instance -t twsdir Two stop actions are supported: When -n instance is specified, the instance with that name is stopped. When -t twsdir is specified, all the instances on this node (the node where the script is run) whose TWSdir attribute matches twsdir are stopped. Remove an instance wtwsconn.sh -remove -n instance View the settings of an instance. Change the settings of an instance wtwsconn.sh -view -n instance wtwsconn.sh -set -n instance -t twsdir Customizing the connector where: node Specifies the node where the instance is created. If not specified, it defaults to the node from where the script is run. instance Is the name of the new instance. This name identifies the engine node of the Job Scheduling Console. The name must be unique within the scheduler network. twsdir Specifies the value for the scheduler directory attribute. This is the Tivoli Workload Scheduler installation directory node. Installation scenarios The installation program automatically installs the Tivoli Management Framework server and Job Scheduling Services if they are not detected during installation. If an installation is detected, the installation program verifies the current version and upgrades it, if necessary. The following table summarizes the installation steps required to install IBM Tivoli Workload Scheduler for z/os connector version 1.3. Chapter 3. Planning and installing the z/os connector 23

50 Installation scenarios Table 7. Installation scenarios What is currently installed... Tivoli Management Framework version 3.6 No job scheduling services No IBM Tivoli Workload Scheduler for z/os connector No Tivoli Management Framework No job scheduling services No IBM Tivoli Workload Scheduler connector Tivoli Management Framework versions or 4.1 No job scheduling services No IBM Tivoli Workload Scheduler for z/os connector Tivoli Management Framework versions or 4.1 Job scheduling services 1.2 No IBM Tivoli Workload Scheduler for z/os connector Follow these steps... Refer to Upgrade to Tivoli Management Framework version Run the installation program to install Job Scheduling Services version 1.2 and IBM Tivoli Workload Scheduler for z/os Connector version 1.3. Run the installation program to install Tivoli Management Framework version 4.1, Job Scheduling Services version 1.2, and IBM Tivoli Workload Scheduler for z/os connector version 1.3. Run the installation program to install Job Scheduling Services version 1.2 and IBM Tivoli Workload Scheduler for z/os Connector version 1.3. Run the installation program to install IBM Tivoli Workload Scheduler for z/os connector version 1.3. Tivoli Enterprise Installation Guide Installing using the installation wizard on page 19 Installing using the installation wizard on page 19 Installing using the installation wizard on page 19 Installing using the installation wizard on page 19 Useful framework commands Note: You can optionally create a Connector instance at installation time, or create it later as described in Managing z/os connector instances with wopcconn on page 22. These commands can be used to check your Framework environment. Refer to the Tivoli Management Framework Reference Guide for more details. Table 8. Useful framework commands This command... Performs this function... wlookup -ar ProductInfo Lists the products installed on the Tivoli server. wlookup -ar PatchInfo Lists the patches installed on the Tivoli server. 24 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

51 Framework commands Table 8. Useful framework commands (continued) This command... Performs this function... wlookup -ar OPC Engine wlookup -ar Maestro Engine Lists the instances of this class type (same for the other classes). Examples: barb #OPC::Engine# barb #Maestro::Engine# The number before the first period (.) is the region number and the second number is the managed node ID (1 is the Tivoli server). The whole numeric string is the object ID. In a multi-tivoli environment, you can determine where a particular instance is installed by looking at this number because all Tivoli regions have a unique ID. wuninst -list * Lists all the products that can be uninstalled. wuninst {ProductName} -list * Lists the managed nodes where a product is installed. wuninst -a * Lists all products and patches Notes: 1. Before using the commands marked with an asterisk (*), you must first enter a bash. 2. For these commands to work, you must run /etc/tivoli/setup_env.sh to source the Framework environment. Chapter 3. Planning and installing the z/os connector 25

52 Framework commands 26 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

53 Chapter 4. Upgrading the z/os connector This chapter describes the upgrade procedure for the IBM Tivoli Workload Scheduler for z/os connector and the Job Scheduling Services. You can perform the upgrade using any of the following methods: v Using the installation wizard. See Upgrading using the installation wizard. v Using the Tivoli desktop. See Upgrading using the Tivoli Desktop on page 29. v Using the Command Line. See Upgrading using the command line on page 29. For information about upgrading the IBM Tivoli Workload Scheduler distributed connector, refer to IBM Tivoli Workload Scheduler: Planning and Installation Guide. Before upgrading, you should back up the contents of your database. Before upgrading you must set the Tivoli Environment as described in Setting the Tivoli Environment on page 33. Upgrading using the installation wizard You can use the installation program to upgrade job scheduling services version 1.1 to the current 1.2 version, and IBM Tivoli Workload Scheduler for z/os connector version 1.1 and 1.2 to the current 1.3 version. The connector instances created with the current installation are maintained. To perform an upgrade, perform the following steps: 1. Insert the IBM Tivoli Workload Scheduler Job Scheduling Console CD 2 in the CD-ROM drive. 2. Navigate to the CONNECT directory. 3. Locate the directory of the platform on which you want to upgrade the IBM Tivoli Workload Scheduler for z/os connector and job scheduling services, and run the setup program for the operating system on which you are upgrading: v Windows: SETUP.exe v UNIX: setup 4. Select the language of the installation wizard. Click OK. 5. Read the Welcome information. Click Next. A check is performed to detect any previous installations of Tivoli Management Framework, job scheduling services and IBM Tivoli Workload Scheduler for z/os connector. In case a previous installation is detected, see Table 9 on page 28 for further information. 6. Read and accept the license agreement. Click Next. 7. A dialog is displayed listing any previous installations. Click Next. 8. When the wizard does not detect an installation of Tivoli Management Framework, you must provide the following: a. In Destination Directory, type the name of the directory where you want to install Tivoli Management Framework, or using Browse to locate it. This field is required. The remaining fields are optional and apply if you intend Copyright IBM Corp. 1991,

54 Using the installation wizard Upgrade to deploy Tivoli programs or managed nodes in your Tivoli Management Framework environment. The following optional fields are displayed only on Windows systems. 1) In Remote Access Account, type the Tivoli remote access account name through which Tivoli programs will access remote file systems. 2) In Password, type the password for the remote access account. 3) In Installation Password, type an installation password that must be used when installing managed nodes. Click Next. 9. Select Yes in the Create Instance section to create an instance at this time. You can optionally create the instance later, as described in Managing z/os connector instances with wopcconn on page 22. a. If you select Yes, a dialog is displayed requesting information for creating the instance. b. In Engine Name, type the name of the new instance. Preferably, use the name of the controller agent as the instance name. c. In IP Address or Hostname, type the IP address of the z/os system where the scheduler subsystem that you want to connect to is installed. d. In IP port number, type the port number of the TCP/IP server to which the connector will connect. Click Next. 10. Review the installation settings and click Next. 11. If you chose to install Tivoli Management Framework, a dialog is displayed requesting information for the installation. Type the path to the TMF.IND file in the Destination directory. Click OK. 12. When the installation completes, a panel displays a successful installation or contains a list of which items failed to install and the location of the log file. 13. Click Finish. scenarios Depending on the version of the installed products, the following operations are performed: Table 9. Upgrading to IBM Tivoli Workload Scheduler for z/os connector version 1.3 What is currently installed... Tivoli Management Framework version 3.6.x Job scheduling services version 1.1 IBM Tivoli Workload Scheduler for z/os connector version 1.1 Tivoli Management Framework version 4.1 or Job scheduling services version 1.2 IBM Tivoli Workload Scheduler for z/os sonnector version 1.2 Follow these steps... Refer to Upgrade to Tivoli Management Framework version Run the installation program to upgrade to Job Scheduling Services version 1.2 and IBM Tivoli Workload Scheduler for z/os Connector version 1.3. Run the installation program to upgrade to IBM Tivoli Workload Scheduler for z/os Connector version 1.3. Tivoli Enterprise Installation Guide Upgrading using the installation wizard on page 27. Upgrading using the installation wizard on page IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

55 Using the installation wizard Table 9. Upgrading to IBM Tivoli Workload Scheduler for z/os connector version 1.3 (continued) What is currently installed... Tivoli Management Framework version 4.1 or Job scheduling services version 1.1 IBM Tivoli Workload Scheduler for z/os connector version 1.1 Follow these steps... Refer to... Run the installation program to upgrade to Job Scheduling Services version 1.2 and IBM Tivoli Workload Scheduler for z/os Connector version 1.3. Upgrading using the installation wizard on page 27 Note: You can optionally create a connector instance at installation time, or create it later as described in Managing z/os connector instances with wopcconn on page 22. Upgrading using the Tivoli Desktop To upgrade using the Tivoli desktop, perform the following steps: 1. Open the Tivoli Desktop. 2. From the Desktop menu select Install, then Install Patch. The Install Patch panel is displayed. 3. Click Select Media to select the installation directory. The File Browser window is displayed. 4. Type or select the installation path. This path includes the directory containing the PATCHES.LST file and the index (.IND) file for the patch. 5. Click Set Media & Close. You return to the Install Patch window. 6. In the Select Patch to Install list, select the patch you want to install. 7. In the Available Clients list, select the managed nodes to install on and move them to the Clients to Install On list. 8. Click Install. The Patch Install window is displayed, which shows the operations to be performed by the installation program. 9. Click Continue Install to continue the installation or click Cancel to cancel the installation. 10. The installation program copies the files and configures the Tivoli database with the new classes. When the installation is complete, the message Finished Patch installation appears. Click Close. Upgrading using the command line To upgrade using the command line, enter one of the following commands: v To install on all managed nodes: wpatch -c install_dir -i patch v To install on only one managed node: wpatch -c install_dir -i patch node where: Chapter 4. Upgrading the z/os connector 29

56 Using the command line install_dir Is the path to the directory containing the PATCHES.LST file and the index (.IND) file for the patch. patch Is the patch index (.IND) file to install. node Is the name of the destination managed node. If the managed node is located on the Tivoli server, or if you do not specify the node variable, the commands are applied to all managed nodes in the Tivoli Management Region. 30 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

57 Chapter 5. Installing new languages on an existing installation This chapter describes how you install a new language on an existing installation. Note: After you have installed a fix pack, you cannot install a new Job Scheduling Console language without first returning the Job Scheduling Console to the GA version. Installing new languages using the installation wizard To add new languages, perform the following steps: 1. Navigate to the JSC directory. 2. Run the setup according to the operating system where you are installing: v Windows: setup.exe v UNIX: setup.bin 3. Select the language of the installation wizard. Click OK. 4. Read the welcome information. Click Next. 5. Select Add languages. Click Next. Note: See Repairing the installation on page 276 for information about repairing a build. 6. Select the languages you want to install. Click Next. 7. Review the installation settings. Click Next. The installation is started. 8. When the installation completes, a panel displays a successful installation or contains a list of which items failed to install and the location of the log file. 9. Click Finish. When you change a language, you must edit the appropriate console file (for example, NTConsole.bat, LinuxConsole.sh) and add the following lines: -Duser.language=xx -Duser.region=yy where xx is the standard two digit language code and yy is the standard two digit region code. For example: -Duser.language=en -Duser.region=US Copyright IBM Corp. 1991,

58 Using the installation wizard 32 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

59 Chapter 6. Uninstalling the components This chapter describes the uninstall procedure for the Job Scheduling Console and all prerequisite components. Setting the Tivoli Environment To uninstall the connector components, you must first set the Tivoli environment, as described in Setting the Tivoli Environment. Uninstalling the Job Scheduling Console To uninstall the Job Scheduling Console, perform the following steps: 1. Close the Job Scheduling Console, if running. 2. Depending on your platform, start the uninstall program for the Job Scheduling Console in one of the following ways: Table 10. Starting the uninstall program for the Job Scheduling Console On this platform... Perform the following action: Microsoft Windows Go to the \uninstaller subdirectory in the installation path and enter: uninstall.exe or use the shortcut icons, if created at installation time. UNIX Go to the. /uninstaller subdirectory in the installation path and enter:. /uninstall.bin or use the shortcut icons, if created at installation time. The Uninstall program window is displayed. Click Next 3. A progress indicator is displayed. When the process completes, it lists any files that the program was not able to uninstall. You will need to delete those files manually. In addition, the.tmeconsole directory, containing the user preferences, is maintained in the user home directory. In case the installation completes with errors, the log file is maintained in the product installation directory. 4. Click Finish to close the window and end the uninstall process. Uninstalling the Job Scheduling Console using the Software Distribution CLI You can uninstall Job Scheduling Console using the Software Distribution command wremovsp as follows: [subscribers...] Copyright IBM Corp. 1991,

60 Uninstalling the Job Scheduling Services Uninstalling the Job Scheduling Services To uninstall the job scheduling services, enter one of the following commands: v On UNIX: wuninst tag node -rmfiles v On Windows, first enter: bash then enter: wuninst tag node -rmfiles where: tag Is the registered product tag. Uninstalling the connectors node Is the name of the managed node from which you want to remove the job scheduling services. If the managed node is located on the Tivoli server, or if you do not specify the node variable, the commands are applied to all managed nodes in the Tivoli Management Region. To uninstall the connector components, enter one of the following commands: v On UNIX: wuninst tag node -rmfiles v On Windows, first enter: bash then enter: wuninst tag node -rmfiles where: tag Is the registered product tag. node Is the name of the managed node from which you want to remove the connector. If the managed node is located on the Tivoli server, or if you do not specify the node variable, the commands are applied to all managed nodes in the Tivoli Management Region. Note: On Linux systems, if you have installed the IBM Tivoli Workload Scheduler for z/os connector version 1.2 GA, you should uninstall the product manually, and install the IBM Tivoli Workload Scheduler for z/os connector version 1.3. To uninstall the product manually, perform the following steps: 1. To display all installed products with the related ID, enter the following command: wlookup -ar ProductInfo The ID is displayed in the following format: OPCConnector ProductID#TMF_Install::ProductInfo# 2. To remove the connector, enter the following command: idlcall ProductID remove 3. Depending on the operating system, perform one of the following operations: 34 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

61 Uninstalling the connectors v On UNIX systems, change to the $DBDIR directory v On Windows systems, change to the %DBDIR% directory and manually remove the connector installation directory. 4. To remove any installed patches, perform the following steps: a. Enter the following command: wlookup -ar PatchInfo b. Enter the following command: idlcall PatchID remove Chapter 6. Uninstalling the components 35

62 Uninstalling the connectors 36 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

63 Part 3. Console overview Chapter 7. Job Scheduling Console object descriptions Common objects Distributed engine specific objects Lists Database Plan Chapter 8. Job Scheduling Console quick start guide Task types Definition tasks Management tasks Task flows Definition task flows Management task flows Task mapping Terminology mapping Chapter 9. Starting the Job Scheduling Console 47 Job Scheduling Console interface description...48 Job Scheduling Console main window Standard functionality Standard buttons Finding objects Pop-up menus Copyright IBM Corp. 1991,

64 38 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

65 Chapter 7. Job Scheduling Console object descriptions This chapter describes the objects of the Job Scheduling Console interface that you use to schedule and maintain jobs. Common objects The following objects are common to both distributed and z/os engines: Workstations Workstations represent the physical or logical nodes where jobs are to be scheduled. Job streams Job streams are a collection of jobs together with their scheduling and dependency definitions. Resources In the Job Scheduling Console, resources are the physical or logical elements that are used by jobs. You define resources in the database prior to defining the jobs that will use them. Jobs A job is an executable process that is controlled by the Tivoli Workload Scheduler. Jobs, their scheduling data, and their dependencies are grouped together in job streams. Distributed engine specific objects The following are objects that are specific to the distributed environment: Workstation Classes A workstation class is a group of workstations. Any number of workstations can be placed in a class. Job streams and jobs can be assigned to run on a workstation class, making replication across many workstations easy. If a job stream is defined on a workstation class, each job added to the job stream must be defined either on a single workstation or on the exact same workstation class that the job stream was defined on. Domains A domain is a named group of Tivoli Workload Scheduler workstations, consisting of one or more workstations and a domain manager acting as the management hub. All domains have a parent domain, except for the master domain. Windows Users When you are running jobs in a Windows environment, you will need to create the user details in the Job Scheduling Console database. Windows users must be defined on the workstation where they log on to the Job Scheduling Console. Calendars A calendar is a list of scheduling dates defined in the scheduler database. Assigning a calendar run cycle to a job stream causes that job stream to be run on the days specified in the calendar. Since a calendar is defined to the scheduler database, it can be assigned to multiple job streams. Copyright IBM Corp. 1991,

66 Distributed specific objects Lists Database Plan Prompts Prompts are used as dependencies for jobs and job streams. A prompt must be answered affirmatively for the dependent job or job stream to launch. For example, you can issue a prompt to make sure that a printer is online before a job that prints a report runs. Parameters Parameters are used to substitute values in jobs and job streams. Since parameters are stored in the Tivoli Workload Scheduler database, all jobs and job streams that use the particular parameter are updated automatically when the value changes. For scheduling, a parameter can be used as a substitute for all or part of: v File dependency path names v Text for prompts v Logon, command, and script file names Files Files are dependencies whose existence a job or job stream must verify before they can start. Lists are filters that allow objects in the database and in the plan to be filtered. There are standard default lists available in the Job Scheduling Console, or you can create lists that are specific to your needs. The scheduler database stores scheduling object definitions. Examples of common scheduling object definitions are: v Workstations v Resources v Job Streams The plan is the master control for the current production day. Object definitions in the database become instances in the current production day plan, where they can be monitored and modified. Examples of common object instances are: v Job Streams v Jobs 40 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

67 Chapter 8. Job Scheduling Console quick start guide This chapter describes the flow of the tasks that you perform using the job scheduling console, and provides a map between those tasks that are common to both z/os and distributed environments, and those tasks that are unique to each environment. It describes: v Task Types v Task Flows v Task Mapping Task types Definition Management This section describes the task types that you can utilize in the Job Scheduling Console. tasks You use the definition tasks of the Job Scheduling Console to create job streams and jobs, defining their various resources and parameters depending on the type of engine to which they relate: z/os or distributed. The types of resources and parameters vary according to the engine type, and for a clearer view of these differences refer to Task flows. tasks You use management tasks to monitor the status of job streams and make adjustments both in the database and the plan. Task flows Task flows in the Job Scheduling Console can be grouped into definition tasks and management tasks. Definition task flows Figure 6 on page 42 illustrates that the flow of definition tasks depends on the type of environment for which you are creating the jobs. In a z/os environment, you create your job definitions while you are creating or modifying a job stream, but in a distributed environment you should create Windows users (when relevant), parameters, and job definitions before you create your job stream. You can perform the other activities for a distributed definition in the order you prefer, but you should be aware that for your job streams to function correctly you should complete most of the definition tasks. Copyright IBM Corp. 1991,

68 Task flows Defining Creating Workstations Creating Windows Users Creating Parameters Creating Prompts Creating Calendars Creating Domains Creating Workstation Classes Creating Job Streams Creating Job Definitions Creating Resources Creating Object Lists Common tasks Distributed tasks Figure 6. Definition task flows Creating Object Lists in the definition task flow is important, as most of your monitoring activity will be performed using lists. Create object lists before beginning any management tasks. Management task flows Figure 7 on page 43 illustrates that the flow of management tasks depends on the day-to-day work that you will be performing. Figure 6 on page 42 starts with Using Object Lists because you perform most of your management activities using object lists to filter for the objects with which you want to work. Working with plans are listed next because they represent the most frequently used management activities. 42 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

69 Task flows Managing Using Object Lists Database Objects Managing Workstations z/os Plans Job Stream Instances Distributed Plans Job Stream Instances Managing Job Streams Job Instances Job Instances Managing Resources Managing Job Definitions Workstations Resources Submitting Jobs and Job Streams Workstations Managing Workstation Classes Domains Managing Domains File Dependencies Managing Windows Users Prompt Dependencies Managing Calendars Managing Prompts Managing Parameters Resource Dependencies Setting Alternate Plan Common tasks z/os tasks Distributed tasks Figure 7. Management task flows Chapter 8. Job Scheduling Console quick start guide 43

70 Task mapping Task mapping The Job Scheduling Console has different task groups: administrative tasks, and operator tasks. The tasks that you can use are further divided by the type of engine: z/os or distributed. Table 11. z/os and distributed task mapping Task z/os Distributed Link Definition Tasks Creating workstations Yes Yes Chapter 10, Creating workstations, on page 53 Creating job streams Yes Yes Chapter 18, Creating job streams, on page 85 Creating resources Yes Yes Chapter 19, Creating resources, on page 123 Creating job definitions No Yes Chapter 17, Creating distributed job definitions, on page 79 Creating workstation classes No Yes Chapter 16, Creating workstation classes, on page 77 Creating domains No Yes Chapter 15, Creating domains, on page 75 Creating Windows users No Yes Chapter 11, Creating Windows users, on page 65 Creating calendars No Yes Chapter 14, Creating calendars, on page 71 Creating prompts No Yes Chapter 13, Creating prompts, on page 69 Creating parameters No Yes Chapter 12, Creating parameters, on page 67 Creating using Create Another Yes Yes Chapter 20, Creating objects using Create Another, on page 127 Creating lists Yes Yes Chapter 21, Creating lists, on page 129 Management Tasks Working with lists Yes Yes Chapter 22, Working with object lists, on page 155 Managing workstations Yes Yes Chapter 23, Managing workstations, on page 159 Managing job streams Yes Yes Chapter 24, Managing job streams, on page 161 Managing resources Yes Yes Chapter 25, Managing resources, on page 169 Managing job definitions No Yes Chapter 26, Managing job definitions, on page 171 Managing workstation classes No Yes Chapter 27, Managing workstation classes, on page IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

71 Task mapping Table 11. z/os and distributed task mapping (continued) Task z/os Distributed Link Managing domains No Yes Chapter 28, Managing domains, on page 177 Managing Windows users No Yes Chapter 29, Managing Windows users, on page 179 Managing calendars No Yes Chapter 30, Managing calendars, on page 181 Managing prompts No Yes Chapter 31, Managing prompts, on page 183 Managing parameters No Yes Chapter 32, Managing parameters, on page 185 Managing z/os plans Yes No Chapter 33, Managing z/os plans, on page 189 Managing distributed plans No Yes Chapter 34, Managing distributed plans, on page 217 Terminology mapping The terminology used in the Job Scheduling Console varies from that used in Tivoli Workload Scheduler. Table 12 lists Tivoli Workload Scheduler distributed and z/os terms and their Job Scheduling Console equivalents. For more information, see the Glossary on page 337. Table 12. Job Scheduling Console terminology mapping IBM Tivoli Workload Scheduler IBM Tivoli Workload Scheduler for z/os Job Scheduling Console Explanation Schedule Application Job stream A sequence of jobs, including the resources and workstations that support them, and scheduling information. Not applicable Application group Job stream template A grouping of job streams that provides scheduling information, such as a calendar, a free-day rule, and run cycles that can be inherited by all the job streams that have been created using the template. Symphony Current plan Plan A detailed plan of system activity. The plan encompasses all job and job stream instances and the resources and workstations involved in running them. External dependency External dependency Not applicable In-effect date for run cycles External job A job from one job stream that is a predecessor for a job in another job stream. Valid from The first date that a run cycle is valid. Chapter 8. Job Scheduling Console quick start guide 45

72 Terminology mapping Table 12. Job Scheduling Console terminology mapping (continued) IBM Tivoli Workload Scheduler IBM Tivoli Workload Scheduler for z/os Job Scheduling Console Start Time Input arrival time (Earliest) start time Exclusionary run cycle Negative run cycle Exclusionary run cycle Schedule Occurrence Job stream instance Explanation The time before when a job or job stream is planned to be ready for processing. Specifies when a job stream must not run. A job stream that is scheduled for a specific run date in the plan. Engine Controller Engine The component that runs on the controlling system, and that contains the tasks that manage the plans and databases. Job Operation Job A unit of work that is part of a job stream and that is processed at a workstation. Job identifier Operation number Job (in the plan) Operations in the current plan Not applicable Out-of-effect date for run cycles Not applicable Run cycle with offsets Not applicable Run cycle with rules Job identifier The number that identifies a job. Job instances A job scheduled for a specific run date in the plan. Valid to The last date that a run cycle is valid. Offset-based run cycle Rule-based run cycle Resources Special resources Logical resources Includes a user-defined period and an offset, such as the 3rd day in a 90-day period. Includes a rule, such as the first Friday of March or the second workday of the week. Any type of limited resource, such as tape drives, communication lines, databases, or printers, that is needed to run a job. Not applicable Task Job A job performed at a computer workstation. 46 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

73 Chapter 9. Starting the Job Scheduling Console This chapter describes how to start the Job Scheduling Console. 1. Depending on your platform, start the Job Scheduling Console in one of the following ways: Table 13. Starting the Job Scheduling Console On this platform... In the..\bin\java subdirectory of the installation path... Microsoft Windows NT, 2000, XP Enter NTconsole, or double-click the Job Scheduling Console icon on the Windows Desktop, or from the Start menu, if created at installation time. AIX Enter. /AIXconsole.sh or use the shortcut icons, if created at installation time. SUN Solaris Enter. /SUNconsole.sh or use the shortcut icons, if created at installation time. HP-UX Enter. /HPconsole.sh or use the shortcut icons, if created at installation time. Linux Enter. /LINUXconsole.sh or use the shortcut icons, if created at installation time. The Job Scheduling Console startup window is displayed. 2. In the User Name field, enter the login of the Tivoli administrator of the host machine running the scheduler engine. 3. In the Password field, enter the password to the host machine running the scheduler connector. 4. In Server Name, type or select the name of the Tivoli managed node that runs the scheduler connector. The last five successful log in servers are listed in the dropdown. If you do not use the default port number, enter the correct port number in this field in the following format: server_name: port_number 5. Click OK to continue. The Job Scheduling Console startup program automatically opens TCP port 9992 to listen for possible user commands directed to the logging program Copyright IBM Corp. 1991,

74 associated with the console. If you are concerned that this default may expose Job Scheduling Console performance to network malfunctions, you can disable the mechanism by adding the following line to one of the startup commands listed in Table 13 on page 47: Djava jlog.nologcmd=true Also, the port on which the logging program listens can be changed by setting the system property jlog.logcmdport to the desired port number. Job Scheduling Console interface description This chapter describes the elements of the Job Scheduling Console interface. Job Scheduling Console main window The main window of the Job Scheduling Console consists of the following elements: v Menu bar v Toolbar v Actions list pane v Work with engines pane v Object list view pane v Status bar You use the Actions List pane to perform the following operations to perform the definition and management tasks described in Part 4, Defining objects, on page 51, Part 5, Managing database objects, on page 153 and Part 6, Managing plans, on page 187. The Work with engines pane is a tree view that displays your scheduler engines (distributed, z/os, or both). If you expand any of the objects that represent the 48 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

75 Interface description Standard scheduler engines, you see the lists and groups of lists available for that particular engine. You can right-click any list item to display a pop-up menu that allows you to manage the list properties. The right-hand pane displays a list view of the object selected in the tree. This can be: v A number of list objects or the contents of a list in the Table View, for Default Database Lists and Common Default Plan Lists v A Table View, Explorer View, or Hyperbolic View for Default Plan Lists functionality This section lists the functionality that is standard throughout the Job Scheduling Console. Standard buttons When you have finished a procedure, perform the following operations: v Click OK to close the window and save. v Click Cancel to close the window without saving. v Click Apply to save without closing the window. v Click Reset to return all fields to the values of the last save. Finding objects The Job Scheduling Console uses a standard search functionality for finding objects in the database or plan. Whenever you see three ellipses (...), or an icon representing a torch, you can search for objects using a find pane. When searching you can use wildcard characters, such as an asterisk (*) to represent a string of characters, or a question mark (?) to represent a single character. Pop-up menus You can right-click objects in the panes to display a pop-up menu of tasks related to the object. Chapter 9. Starting the Job Scheduling Console 49

76 Interface description 50 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

77 Part 4. Defining objects Chapter 10. Creating workstations Creating a z/os workstation General tab Resources tab Open Time Intervals tab Creating a distributed workstation Chapter 11. Creating Windows users Creating a Windows user Chapter 12. Creating parameters Creating a parameter Chapter 13. Creating prompts Creating a prompt Chapter 14. Creating calendars The Holidays calendar The freedays calendar Creating a calendar Chapter 15. Creating domains Creating a domain Chapter 16. Creating workstation classes Creating a workstation class General tab Workstations tab Chapter 17. Creating distributed job definitions 79 Creating a job definition General tab Task tab UNIX script, Windows script, or workstation class script UNIX command, Windows command, or workstation class command Adding parameters to jobs Extended agent SAP job Chapter 18. Creating job streams Creating a job stream for a z/os engine Creating a job for z/os job streams Creating a job in z/os Creating dependencies between jobs Creating dependencies within a job stream..93 Creating dependencies between job streams 93 Scheduling job streams Types of run cycle Creating a run cycle Creating rule-based run cycles Creating offset-based run cycles Saving a job stream Creating a distributed job stream General tab Time Restrictions tab Resources tab Files tab Prompts tab Adding external dependencies to a job stream 106 Adding an external job stream dependency 106 Adding an internetwork dependency Adding an external job dependency Adding a job to a job stream Specifying job properties Copying and pasting jobs Using the copy function to add an external job Cloning job dependencies Adding an internetwork dependency to a job stream Adding an external job stream to a job stream 112 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 Specifying time restrictions in the Timeline View 120 Specifying time restrictions for a job stream 120 Specifying time restrictions for a job Chapter 19. Creating resources Creating a z/os resource Resource tab Default Workstations tab Availability Intervals tab Creating a distributed resource Chapter 20. Creating objects using Create Another Chapter 21. Creating lists Creating database lists Creating a list of job streams Creating a list of workstations Creating a list of resources Creating a list of job definitions Creating a list of workstation classes Creating a list of prompts Creating a list of parameters Creating a list of Windows users Creating a list of domains Creating a list of calendars Creating plan lists Copyright IBM Corp. 1991,

78 Creating a job stream instance list for distributed engines General tab Time Restrictions tab Dependencies tab Column definition Creating a job stream instance list for z/os engines Creating a job instance list for distributed engines General tab Time Restrictions tab Dependencies tab Creating job instance list for z/os engines Creating a list of workstations Creating a list of resources Creating a list of files Creating a list of prompts Creating a list of domain states Creating a group of lists Creating default common plan lists Creating a common list of job stream instances 150 Creating a common list of job instances Setting list properties IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

79 Chapter 10. Creating workstations This chapter describes how to create workstations in the Tivoli Workload Scheduler environment. To create a workstation, perform the following steps: 1. In the Actions list pane, open New Workstation. 2. Select the engine. Creating a z/os workstation The Workstation in Database panel depends on the type of engine: z/os or distributed. The Workstation in Database panel is displayed. The panel consists of the following tabs: Copyright IBM Corp. 1991,

80 Creating a z/os workstation v v General General Resources v Open Time Intervals tab Use the General tab to enter general information for the workstation. Table 14 defines the information necessary to create a workstation. In the Properties section, use Control on servers and Planning on servers to specify how the workstation uses parallel servers. When you create a job, you specify how many parallel servers it requires. The workstation that the job is using must have that number of parallel servers available before the job can run. You set this value when you create the workstation, but you can change it later. Select both Control on servers and Planning on servers so that Tivoli Workload Scheduler submits jobs only up to the limit of the number of servers specified. If you select Planning on servers only, or nothing, then Tivoli Workload Scheduler does not evaluate the number of parallel servers when deciding when to start an operation. In addition, the number of parallel servers is used only for planning purposes, and plans cannot accurately predict the behavior of work in your system, because Tivoli Workload Scheduler submits as many jobs as are ready, regardless of the count of the number of servers in use. Note: At a non STC computer workstation, a parallel server can represent a job entry subsystem initiator. You must allocate at least one parallel server when you define a job. If you select both Control on servers and Planning on servers, or Control on servers only, the number of parallel servers required by the job must also be available on the workstation before the job can be started. Table 14. Properties - Workstation in Database General information In this area... Specify... Information Name A name for the new workstation. This field is required. Description A description of the workstation. Maximum supported length for this field is 38 characters. Workstation type One of the following: General For preparation of jobs and for control of operations that are normally not controlled automatically. Printer For printing. Computer For running jobs and started tasks. 54 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

81 Creating a z/os workstation Table 14. Properties - Workstation in Database General information (continued) In this area... Specify... Reporting attribute The mechanism for reporting status updates on the jobs defined on 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. Typically, you should use this reporting attribute for general workstations that are used for job preparation, or for other general workstations if the duration of the task needs to be tracked. Non reporting If jobs on this workstation are set to complete as soon as they become eligible to be started. Typically, you should use this reporting attribute for dummy jobs created to simplify the sequencing of other jobs. Automatic If the status change of jobs is reported automatically, in response to event records created by IBM Tivoli Workload Scheduler for z/os. Typically, you should use this reporting attribute for computer and print workstations, or for workstations that specify a user-defined destination. 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. Typically, you should use this reporting attribute for general workstations that are not used for job preparation. Printout routing The data definition name (ddname) of the daily printout data set where reports for this workstation are to be written. Destination A destination that corresponds to the destination specified on a ROUTOPTS initialization statement. For computer workstations and WTO general workstations, this is the name of the IBM Tivoli Workload Scheduler for z/os tracker. The default destination is the system where the engine is started. Properties Control on servers That the number of parallel servers that the jobs use be available on the workstation in order for the jobs to be started. Planning on servers That the number of parallel servers is only for planning purposes and to submit as many jobs as are ready, regardless of the number of servers in use. Chapter 10. Creating workstations 55

82 Creating a z/os workstation Table 14. Properties - Workstation in Database General information (continued) In this area... Specify... Splittable That jobs on the workstation can be interrupted. Use this attribute for a job setup general workstation where you prepare JCL for submission. If the preparation of the JCL is interrupted by the preparer issuing the TSAVE command, the operation is assigned status I. Preparation of the JCL job can continue at a later time. Printer workstations can also be split, but operations on computer workstations cannot be split. Job Setup When using a general workstation to prepare job JCLs or started task JCLs manually before running. This attribute is not necessary if IBM Tivoli Workload Scheduler for z/os can resolve all the JCL variables automatically. Started task, STC When using a computer workstation that will run started tasks rather than jobs. WTO When using a general workstation on which the scheduling facilities can issue a write-to-operator message at the operator console designated in Destination. Fault Tolerant The workstation as fault-tolerant. Use fault-tolerant workstations to run distributed jobs in a z/os plan. Fault-tolerant workstations are automatically defined as computer workstation types with an automatic reporting attribute. All the properties for this workstation are disabled and set to their default value. Defaults Transport time The time in HH:MM that the system allows between the end of a predecessor job and the beginning of the present job. The transport time of the workstation is the default transport time for all the jobs defined on the workstation and is used for planning purposes only. Duration The default estimated processing time in HH:MM:SS for all jobs on that workstation. Tivoli Workload Scheduler uses the estimated processing time when creating the plan, to work out a timetable for all jobs. You do not need to give an exact figure, because Tivoli Workload Scheduler can adjust it dynamically using actual durations. However, your estimation should be as accurate as possible. You can override this value by specifying a duration when you create a new job. Access Methods Name The name of the access method that handles the third-party product. Node address The optional TCP/IP address or host name of the fault tolerant agent that is hosting the access method. Port number The optional TCP/IP port number of the tracker agent that is hosting the access method. Resources tab You can define a maximum of two workstations, or fixed resources called Resource 1 (R1) and Resource 2 (R2), to schedule or run jobs on a workstation. 56 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

83 Creating a z/os workstation When defined, the two resources are associated to the workstation and are recognized automatically when you schedule and run jobs on the workstation. However, they are subject to the following limitations, that in some instances could make it more practical to use logical resources: v The maximum quantity for each resource is 99 v They cannot be shared by other workstations v Their name is limited to two characters R1 and R2 can represent any physical resource in your system, which is significant for scheduling purposes. When you create a new job, you can specify how many workstation resources (R1, R2, or both) the job will use. If the specified quantity of resources is not available, the job will not start. To define the use of each resource: 1. Type a 2-character name in Name if you want to change the resource name. The names R1 and R2 are provided by default. 2. Select Used for planning, if you want the resource to be considered when a plan involving this workstation is built. 3. Select Used for control, if you want the resource to be used when a job runs on this workstation. The plan contains the best estimation of the time operations will start. If an unexpected problem occurs, for example, a job exceeds its expected run time Tivoli Workload Scheduler may need to reassess the start time of some of the operations. If you selected Control on servers, Tivoli Workload Scheduler considers the workstation resource when rescheduling its operations. Otherwise, the workstation resource is ignored. Open Time Intervals tab Use this tab to define the availability of parallel servers on a time-interval basis, the capacity of workstation resources, and the name of an alternate workstation that enables jobs to run on the workstation. 1. To add an open time interval, click Add Row. To delete an open time interval, select it and click Remove Row. 2. After you add a row, you can modify the values by double-clicking under the column header. Table 15 defines the information necessary to create time intervals. Table 15. Properties - Workstation in Database Open Time Intervals information In this column... Specify... Day A day of the week, Standard, or Specific Date (where a calendar pops up from which you select a date). The Standard interval defines the values that are true at all times, with the exception of the additional intervals that you also specify on this page. When you define a new workstation, you find a default Standard row where you enter the name of an alternate workstation and the quantities of parallel servers and of workstation resources that you want to be available on a general basis. Select a day or Specific Date to specify the time intervals when quantities, name, or both are different from Standard. Chapter 10. Creating workstations 57

84 Creating a z/os workstation Table 15. Properties - Workstation in Database Open Time Intervals information (continued) In this column... Specify... Status The availability status of the workstation in the given interval. Select one of the following: Defined To specify that during the interval the workstation is available in the quantities and with the properties defined in the current row. Closed To specify that the workstation is not available during the interval. If you select this value, the remaining cells in the row are disabled. From Time and To Time A time interval in the 12-hour clock format. Parallel Servers The quantity of parallel servers available to the workstation during the time interval. Leave this field blank if you did not specify parallel servers in the General tab. The maximum value is 99. R1 Capacity and R2 Capacity The available quantities for every interval of resources R1 and R2 if you specified that they be used for this workstation in the Resources tab. The maximum value for each resource is 99. Alternate Workstation The name of a workstation of the same type that can be used during the interval if this workstation becomes unavailable. This option is available only for computer workstations and for WTO general workstations. Note: For the best results the configurations of the two workstations should be symmetrical. 58 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

85 Creating a distributed workstation Creating a distributed workstation The Workstation in Database panel is displayed. Table 16 defines the information necessary to create a distributed workstation. Table 16. Properties - Workstation in Database information In this area... Specify... Information Chapter 10. Creating workstations 59

86 Creating a distributed workstation Table 16. Properties - Workstation in Database information (continued) In this area... Specify... Name The name of the workstation. The name must start with a letter and can contain alphanumeric characters, dashes, and underscores. For non-expanded databases, it can contain up to eight characters. For expanded databases, it can contain up to 16 characters. Note: Workstation names must be unique, and cannot be the same as workstation class and domain names. Node The host name or the IP address of the workstation. Fully-qualified domain names are accepted. TCP Port The netman TCP port number that Tivoli Workload Scheduler uses for communications on the workstation. The default is The port number of netman on a workstation is defined by the localopts file in the parameter nm port. Operating System The operating system of the workstation. Available options are: UNIX Windows Other Domain The name of the domain of the workstation. The name can start with a letter or with a number and can contain alphanumeric characters, dashes, and underscores. For non-expanded databases, it can contain up to eight characters. For expanded databases, it can contain up to 16 characters. The default for fault-tolerant and standard agents is the master domain, usually named MASTERDM. The default for a domain manager is the domain in which it is defined as the manager. The default for an extended agent is the domain of its host. Note: Domain names must be unique, and cannot be the same as workstation and workstation class names. Time Zone The time zone of the workstation. Choose a time zone name from the drop-down list. For a description of time zone names, refer to the IBM Tivoli Workload Scheduler Reference Guide. To ensure the accuracy of scheduling times, this time zone must be the same as the computer operating system time zone. The Time Zone field is editable only if the time zone feature is enabled. Description A description of the workstation. The description can contain up to 40 characters. Security 60 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

87 Creating a distributed workstation Table 16. Properties - Workstation in Database information (continued) In this area... Specify... SSL Communication Which type of Secure Socket Layer (SSL) communication is enabled. Supported values are: Enabled The workstation uses SSL authentication only if a peer workstation requires it. On The workstation uses SSL authentication when it connects with its domain manager. The domain manager uses SSL authentication when it connects to a parent domain manager, and the master domain manager has SSL authentication enabled. However, it refuses any incoming connection from its parent domain manager if it is not an SSL connection. Force The workstation uses SSL authentication for all of its connections. It will refuse any incoming connection if it is not an SSL connection. You can also disable the SSL protocol, by selecting the blank space in the drop-down list. Behind Firewall That a firewall exists between the workstation and its domain manager, and that the link between the domain manager and the workstation is the only allowed link between the respective domains. Secure Port The number of the secure port to be used for SSL communication. The default value is Workstation Type The type of workstation. Select one of the following options 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. Select this type for fault-tolerant agents, domain managers, and backup domain managers. Extended Agent Select this type for an agent workstation that launches jobs only under the direction of its host. Extended agents can be used to interface Tivoli Workload Scheduler with non-tivoli systems and applications. For more information refer to the user manual for the specific extended agent. Standard Agent Select this type for an agent workstation that launches jobs only under the direction of its domain manager. Chapter 10. Creating workstations 61

88 Creating a distributed workstation Table 16. Properties - Workstation in Database information (continued) In this area... Specify... Auto Link Whether to open the link between workstations at startup. For fault-tolerant and standard agents, select this option to have the domain manager open the link to the agent when the domain manager is started. For a domain manager, select this option to have its agents open links to the domain manager when they are started. Auto Link is useful primarily during the startup sequence at the beginning of each day. At that time, a new production plan is created and compiled on the master domain manager, and all workstations are stopped and restarted. For each agent that has Auto Link selected, the domain manager automatically sends a copy of the new production plan and starts the agent. If Auto Link is also selected for the domain manager, the agent, in turn, opens a link back to the domain manager. If Auto Link is not selected for an agent, it is initialized when you run a link action on the agent domain manager or the master domain manager. Full Status Whether the agent is updated with full or partial status. This is for fault-tolerant agents only. When Full Status is selected, the agent is updated with the status of jobs and job streams running on all other workstations in its domain and subordinate domains. If Full Status is not selected, the agent is informed only about the status of jobs and job streams on other workstations that affect its own jobs and job streams. This can improve performance by reducing network activity. Ignore That the scheduler ignores this workstation. This can be used to define workstations before they are actually installed. Resolve Dependencies Whether an agent tracks all dependencies, or only its own. This is for fault-tolerant agents only. When Resolve Dependencies is selected, the agent tracks dependencies for all jobs and job streams, including those running on other workstations. Full Status must also be selected so that the agent is informed about activity on other workstations. If Resolve Dependencies is not selected, the agent tracks dependencies for its own jobs and job streams only. This reduces processing overhead. Server A mailman server on the domain manager to handle communications with the agent. This is for fault-tolerant and standard agents only. Using servers can reduce the time required to initialize agents and improve message efficiency. To specify a server, select a letter or a number (A-Z and 0-9) from the drop-down list. The IDs are unique to each domain manager, so you can use the same IDs in other domains without conflict. If more than 36 server IDs are required in a domain, consider dividing it into two or more domains. If a server ID is not specified, communication with the agent is handled by the main mailman process on the domain manager. When a domain manager starts it creates a separate server for each unique server ID. If the same ID is used for multiple agents, a single server is created to handle their communications. You should define a single server for groups of 8 agents. 62 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

89 Creating a distributed workstation Table 16. Properties - Workstation in Database information (continued) In this area... Specify... Access Method An access method for extended agents and network agents. This must be the name of a method file that resides in the TWShome/methods directory on the agent host workstation. For a local UNIX extended agent, the method name is unixlocl. For a remote UNIX extended agent the method name is unixrsh. For network agents, the method name is netmth. For more information about extended agents, refer to the individual extended agent user guides. For more information about network agents, refer to the IBM Tivoli Workload Scheduler Reference Guide. Host The name of the agent host workstation. This is required for extended agents. The host is the workstation with which the extended agent communicates and where its access method resides. The host for an extended agent must be a master, domain manager, or fault tolerant agent. The host for an extended agent can be specified as $MASTER. This assigns the host as the master domain manager, and is useful if you need to switch masters in the domain. The extended agent automatically connects to the new manager. Notes: 1. The host option is not required for standard agents. The host workstation for standard agents is defaulted to the domain manager. 2. To keep an agent production plan at the same level of detail as its domain manager, select Full Status and Resolve Dependencies. Always select these options for backup domain managers. Chapter 10. Creating workstations 63

90 Creating a distributed workstation 64 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

91 Chapter 11. Creating Windows users Creating a Windows user This chapter describes how you create Windows users in a distributed environment. The users for whom Tivoli Workload Scheduler launches jobs must be defined in the database. This configuration step is required for Windows users only. To create Windows users in the database, perform the following steps: 1. In the Actions list pane, click New Windows User. 2. Select the engine. The Properties - Windows User panel is displayed. Table 17 defines the information necessary to create a Windows user. Table 17. Properties - Windows User information In this area... Specify... Information Name The Windows user name. The name can contain up to 31 characters. Notes: 1. Windows user names are case-sensitive. 2. A Windows user must be able to log on to the workstation on which Tivoli Workload Scheduler will launch jobs, and have the right to Log on as batch. 3. If the name is not unique in Windows, it is considered to be a local user, a domain user, or a trusted domain user, in that order. Copyright IBM Corp. 1991,

92 Creating a windows user Table 17. Properties - Windows User information (continued) In this area... Specify... Windows Domain The Windows domain of this user. This field is optional. If the name is not fully qualified (that is, no Windows domain is entered) or is not unique in Windows, it is considered to be a local user, a domain user, or a trusted domain user, in that order. Windows Workstation The name of the Tivoli Workload Scheduler workstation on which the user is allowed to launch jobs. Set Password New Password A new user password as defined on the Windows computer. Confirmation The user password again for confirmation. 66 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

93 Chapter 12. Creating parameters Creating a parameter This chapter describes how you create parameters for the distributed environment. When using a parameter in a job script, the value is substituted at run time. In this case, the parameter must be defined on the workstation where it will be used. Parameters cannot be used when scripting Extended Agent jobs. Note: Be careful when renaming a parameter because it might be part of a dependency for a job scheduler object in the database. If this is the case, and you rename it, any action you perform that refers to the old name will return an error. To create a new parameter, perform the following steps: 1. In the Actions list pane, click New Parameter. 2. Select the engine. The Properties - Parameter pane is displayed. 3. In Name, type the name of the parameter. The name must start with a letter and can contain alphanumeric characters, dashes, and underscores. The name can contain up to eight characters. 4. In Value, type the value assigned to the parameter. Do not include the names of other parameters. Copyright IBM Corp. 1991,

94 Creating a parameter 68 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

95 Chapter 13. Creating prompts Creating a prompt This chapter describes how you create prompts for the distributed environment. 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. Predefined prompt This is defined in the Tivoli Workload Scheduler database and can be used by any job or job stream. To create a new prompt, perform the following steps: 1. In the Actions list pane, click New Prompt. 2. Select the engine. The Properties - Prompt panel is displayed. 3. In Name, type the name of the prompt. The name must start with a letter and can contain alphanumeric characters, dashes, and underscores. The name can contain up to eight characters. 4. In Text, type the text of a prompt. The default behavior of a prompt is to display a message and wait for a reply. If the string begins with a colon (:), the message is displayed but no reply is necessary. If the string begins with an exclamation mark (!), the message is not displayed but it requires a reply. You can include backslash n (\n) within the text to create a new line. Copyright IBM Corp. 1991,

96 Creating a prompt 70 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

97 Chapter 14. Creating calendars This chapter describes how you create calendars for distributed engines. You can create as many calendars as required to meet your scheduling needs. For example: Table 18. Example calendars This calendar... Could contain... PAYDAYS A list of pay dates MONTHEND A list of month ending dates HOLIDAYS A list of your company s holidays The Holidays calendar The freedays calendar Note: The maximum size of the calendars you create and manage depends on the size of your system RAM. For example, the maximum calendar size for a computer with 256 MB RAM is 1000 consecutive days (3 years). If you select a calendar for a job stream that is larger than your RAM can manage, the job stream definition process hangs, and must be stopped. 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 as follows: workdays=everyday except saturday, sunday and all the dates appearing in the HOLIDAYS calendar Create a HOLIDAYS calendar with the dates of your holidays. Freedays calendars are intended as non-work days, when no scheduling activity is to take place. Freedays calendars extend the role of the HOLIDAYS calendar, as they provide additional flexibility in defining workdays. When defining a job stream, if you decide to use a freedays calendar instead of HOLIDAYS, then the definition of workdays becomes: workdays=everyday except saturday, sunday and all the dates appearing in the specified freedays calendar If you decide to use your own freedays calendar for a job stream, the redefined meaning of workdays is limited to that job stream. A possible scenario is to define more than one freedays calendar to use in your scheduling activity, particularly in the case your enterprise has different international locations, to respond to different non-work day requirements. When you do not specify a freedays calendar for the job stream, then HOLIDAYS is used, if available. Copyright IBM Corp. 1991,

98 Creating calendars Creating a calendar To create calendars in the database, perform the following steps: 1. In the Actions list pane, click New Calendar. 2. Select the engine. The Properties - Calendar panel is displayed. 3. In Name, type the name of the calendar. The name must start with a letter and can contain alphanumeric characters, dashes, and underscores. The name can contain up to eight characters. Note: You cannot use Tivoli Workload Scheduler keywords (for example, freedays and schedule). 4. In Description, type a description of the calendar. 72 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

99 Creating calendars 5. Click Define Calendar to add dates to the calendar. The Monthly Yearly Calendar window is displayed. 6. Select Monthly or Yearly to view a monthly or yearly calendar. Use the arrow buttons above and below the calendar to change the month and year. 7. To add a specific date to the calendar, click the date in the calendar view. 8. To add a specific day of the month, select Day of Month from the Select menu. The Day of Month pane is displayed. 9. To add a day of the month by number, select the day number in the Day drop-down list. To add the last day of the month, select the Last Day of Month option. 10. Select start and end dates for the calendar by selecting the month and year from the Start and End drop-down lists. The days you specify are selected for every month in this range. 11. Click OK to close the Day of Month pane and select the dates. Click Cancel to close the pane without selecting the dates. 12. Click OK to close the Monthly Yearly Calendar pane and add the dates to the calendar. Click Cancel to close the pane without adding the dates to the calendar. Chapter 14. Creating calendars 73

100 Creating calendars 74 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

101 Chapter 15. Creating domains Creating a domain This chapter describes how you create domains in a distributed environment. To create a domain in the database, you use the Properties - Domain window, as explained in the following steps: 1. In the Actions list pane, click New Domain. 2. Select the engine. The Properties - Domain panel is displayed. Table 19 defines the information necessary to create a new domain. Table 19. Properties - Domain panel In this area... Specify... Information Domain Name The name of the domain. The name can start with a letter or with a number and can contain alphanumeric characters, dashes, and underscores. For non-expanded databases, it can contain up to eight characters. For expanded databases, it can contain up to 16 characters. Note: Domain names must be unique and cannot be the same as workstation and workstation class names. Description A description of the domain. Parent Domain The name of the parent domain to which the domain manager is linked. The default is the master domain. Domain Manager The name of the workstation that is the domain manager. The domain manager must be a fault-tolerant agent with Full Status and Resolve Dependencies selected. Note: When creating a new domain, you can specify a domain manager workstation that does not yet exist. Copyright IBM Corp. 1991,

102 Creating a domain 76 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

103 Chapter 16. Creating workstation classes Creating a workstation class This chapter describes how you create workstation classes for the distributed environment. To create workstation classes in the database, you use the Properties - Workstation Class pane. To create a new workstation class, perform the following steps: 1. In the Actions list pane, click New Workstation Class. 2. Select the engine. The Properties - Workstation Class panel is displayed. General tab Workstations 1. In Name, type the name of the workstation class. The name must start with a letter and can contain alphanumeric characters, dashes, and underscores. For non-expanded databases, it can contain up to eight characters. For expanded databases, it can contain up to 16 characters. Note: Workstation class names must be unique and cannot be the same as workstation and domain names. tab To associate the workstations to the workstation class, perform the following steps: 1. Click Find Workstation to find a workstation to associate to the workstation class. 2. Click Add All Workstations to add all the workstations in the database to the workstation class. Copyright IBM Corp. 1991,

104 Creating a workstation class 3. Select a row and click Delete from Table to remove a workstation from the workstation class. 78 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

105 Chapter 17. Creating distributed job definitions Creating a job definition This chapter describes how to create a job definition for a distributed engine. A job is a unit of work that is part of a job stream processed at a workstation. It usually includes all necessary computer programs, links, files, and instructions to the operating system. You create jobs in the database using the Properties - Job Definition window. To create a new job, perform the following steps: 1. In the Actions list pane, click New Job Definition. 2. Select the engine. 3. Select a task type in the list displayed. You cannot change a task type after it is defined for a job. Table 20 describes the task types: Table 20. New Job Definition task types This task type... Specifies that... UNIX Script The job is an executable file on a UNIX computer. UNIX Command The job is a UNIX command. Windows Script The job is an executable file on a Windows computer. Windows Command The job is a Windows command. Workstation Class Script The job is an executable file that runs on a workstation class. Workstation Class Command The job is a command that runs on a workstation class. Extended Agent Task The job is associated with an Extended Agent workstation. SAP The job is a SAP job that runs on an IBM Tivoli Workload Scheduler Extended Agent for SAP. The SAP task type is only displayed if the Extended Agent for SAP has been installed. For more information on SAP jobs, refer to IBM Tivoli Workload Scheduler for Applications User s Guide. Copyright IBM Corp. 1991,

106 Creating a job definition General tab The Properties - Job Definition panel is displayed. Table 21 defines the information necessary to create a job definition. Table 21. Properties - Job Definition general information In this area... Specify... Information Task Type This information field indicates the task type you selected. Name The name of the job. The name must start with a letter, and can contain alphanumeric characters, dashes, and underscores. For non-expanded databases, it can contain up to eight characters. For expanded databases, it can contain up to 40 characters. Workstation The name of the workstation or workstation class on which the job runs. Workstation classes must match the workstation class of a job stream where the job is included. Description A description of the job. The description can contain up to 64 characters. Is Interactive That the job runs interactively on the Windows desktop. Login Login The user name where the job runs. The maximum length is 31 characters. Specify a user that can log on to the workstation where the job runs. For Windows jobs, the user must also be defined in the database. For more information, see Chapter 11, Creating Windows users, on page 65. To include a parameter in the name, perform the steps described in Adding parameters to jobs on page 83. Recovery Options 80 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

107 Creating a job definition Table 21. Properties - Job Definition general information (continued) In this area... Specify... Stop If the job ends in error, do not continue with the next job. Stop is the default. Continue If the job ends in error, continue with the next job. Rerun If the job ends in error, rerun the job. Message The text of a recovery prompt to be displayed if the job ends in error. The text can contain up to 64 characters. The recovery prompt is a local prompt and is responded to using the Job Scheduling Console. The status of All Prompts shows the recovery prompts whether they have been asked or not. If a job ended in error, the prompt status is Asked and the message is displayed. If a job successfully ended, the status is Not Asked, and no message appears. Job The name of a recovery job to run if the parent job ends in error. Recovery jobs are run only once for each instance of the parent job ended in error. Workstation The name of the workstation on which the recovery job runs. The name is entered automatically when you select a recovery job. Not all jobs are eligible to have recovery jobs run on a different workstation. Follow these guidelines: v If either workstation is an extended agent, it must be hosted by a domain manager or a fault-tolerant agent that runs in Full Status mode. v The recovery job workstation must be in the same domain as the parent job workstation. v If the recovery job workstation is a fault-tolerant agent, it must run in Full Status mode. Table 22 on page 81 summarizes all possible combinations of recovery options and actions. The table is based on the following criteria from a job stream called sked1: v Job stream sked1 has two jobs, job1 and job2. v If selected for job1, the recovery job is jobr. v job2 is dependent on job1 and will not start until job1 is complete. Table 22. Job stream recovery options Prompt / Job Stop Continue Rerun Recovery prompt: No Recovery job: No Recovery prompt: Yes Recovery job: No Intervention is required. Issue recovery prompt. Intervention is required. Run job2. Rerun job1. If job1 ends in error, issue scheduler prompt. If reply is yes, repeat above. If job1 is successful, run job2. Issue recovery prompt. If reply is yes, run job2. Issue recovery prompt. If reply is yes, rerun job1. If job1 ends in error, repeat above. If job1 is successful, run job2. Chapter 17. Creating distributed job definitions 81

108 Creating a job definition Table 22. Job stream recovery options (continued) Prompt / Job Stop Continue Rerun Recovery prompt: No Recovery job: Yes Recovery prompt: Yes Recovery job: Yes Run jobr. If it ends in error, intervention is required. If it is successful, run job2. Issue recovery prompt. If reply is yes, run jobr. If it ends in error, intervention is required. If it is successful, run job2. Run jobr. Run job2. Issue recovery prompt. If reply is yes, run jobr. Run job2. Run jobr. If jobr ends in error, intervention is required. If jobr is successful, rerun job1. If job1 ends in error, issue scheduler prompt. If reply is yes, repeat above. If job1 is successful, run job2. Issue recovery prompt. If reply is yes, run jobr. If jobr ends in error, intervention is required. If jobr is successful, rerun job1. If job1 ends in error, repeat above. If job1 is successful, run job2. Notes: 1. Intervention is required means that job2 is not released from its dependency on job1, and therefore must be released by the operator. 2. The continue recovery option overrides the abend state, which may cause the schedule containing the job ended in error to be marked as successful. This will prevent the schedule from being carried forward to the next day. 3. If you select the Rerun option without supplying a recovery prompt, Tivoli Workload Scheduler generates its own prompt. 4. To reference a recovery job in conman, you must use the name of the original job (job1 in the scenario above, not jobr). Recovery jobs are run only one per abend. 82 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

109 Task tab Depending on the task type you selected, different properties are available in the task tab. For more information, see Table 23. Table 23. Task types For this task type... Go to... UNIX Script, Windows Script, or Workstation Class Script UNIX script, Windows script, or workstation class script UNIX Command, Windows Command, or Workstation Class Command Creating a job definition UNIX command, Windows command, or workstation class command Extended Agent Extended agent on page 84 SAP Job SAP job on page 84 UNIX script, Windows script, or workstation class script Complete Script as follows: Type the file name and any options and arguments. For non-expanded databases, the field can contain up to 255 characters. For expanded databases, it can contain up to 4095 characters. For Windows jobs, include the file extensions. Universal Naming Convention (UNC) names are permitted. Do not specify files on mapped drives. If the file name contains spaces, enter the name in another file that does not have spaces in its name and use the second file name in this field. For information about adding parameters, see Adding parameters to jobs. UNIX command, Windows command, or workstation class command In the Command field, specify the name of the command the job runs. Enter the command name and any options and arguments. For non-expanded databases, the field can contain up to 255 characters. For expanded databases, it can contain up to 4095 characters. Commands are run directly and the jobmanrc standard configuration script is not run. To include a parameter in the Command field, perform the steps described in Adding parameters to jobs. The Return Code Mapping section allows the user to define which return codes cause the job to be successful. In the Expression field, enter a logical expression that defines the success condition. Allowed operators are comparison operators (=,!= or <>, >, >=, <, <=) and logical operators (AND, OR, NOT). Adding parameters to jobs To include a parameter in Script, perform the following steps: 1. Place the cursor in field where you want to insert the parameter and click Add Parameter. Chapter 17. Creating distributed job definitions 83

110 Creating a job definition 2. This displays the Find Parameters pane. 3. Search for a parameter name. The name can contain wildcard characters. 4. Click Start to display a list of parameter names. 5. Select a parameter name in the list and perform one of the following operations: v Click OK or double-click the parameter in the list to insert the parameter name in Script of the Properties - Job Definition pane v Click Cancel to close the Find Parameters pane without inserting a parameter name. Extended agent Refer to the specific user guide for the Extended Agent you are working with for more information. SAP job Refer to the IBM Tivoli Workload Scheduler for Applications User s Guide for information about defining the task. 84 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

111 Chapter 18. Creating job streams This chapter describes how you create job streams. After you create job streams, you need to edit them before they can be submitted to the daily plan. For information about editing job streams, see Chapter 24, Managing job streams, on page 161. To create a new job stream, perform the following steps: 1. In the Actions list pane, click New Job Stream. 2. Select the engine. The Job Stream panel depends on the type of engine: z/os or distributed. Creating a job stream for a z/os engine The Properties Job Stream panel is displayed. Copyright IBM Corp. 1991,

112 Creating z/os job streams Table 24 defines the information necessary to create a job stream. Table 24. Properties - Job Stream panel for z/os In this area... Specify... Information Name A name for the job stream or template. Note: The name, valid date, and status uniquely identify each job stream or template. You can define up to four job streams and job stream templates that share the same name but have different valid dates. Description A description of the job stream or template. Owner The name of the person responsible for the job stream or template. Owner description Information for contacting a person for assistance when the job stream does not complete according to the plan. Template A new job stream template. A job stream template contains run cycles but no jobs. All job streams defined as belonging to a template inherit the run cycles defined for the template. Is Active The job stream schedule. Do not select this until you have added all the jobs, specified dependencies, and created a run cycle. Inherits from template The name of the template if you are defining a job stream that belongs to a job stream template. The job stream is scheduled using the template run cycle information. Contains Monitored Job Whether any jobs in this job stream are monitored by Tivoli Business Systems Manager when they run. The value is Yes if Is Monitored Job is selected in the properties pane of one or more of the jobs in the job stream. This field is read-only. Authority group name A name to be used to generate a RACF resource name for authority checking. This information is optional. Calendar The name of the calendar of workdays and freedays, including holidays, that you associate to the job stream. If you leave this field blank, the scheduler uses the calendar specified in the initialization parameter CALENDAR during startup of the TCP/IP server. Note: The calendar that you specify here is used to display the run days of the job stream in the Run Cycle view of the Job Stream Editor. It is not necessarily the calendar that is used to determine the actual run days of the job stream instances that are generated. Priority The priority of job stream compared to other jobs streams. The lowest priority is 1 and the highest priority is 9. When job streams are competing for resources, a job stream with a priority of 3 will run before a job stream with a priority of 1. This value is not definitive. Other factors, such as resource and workstation dependency, are considered in determining priority. This field does not apply to job stream templates. Valid Date From The time period covered by the job stream. You can specify only the From date. Click the small calendar button to select a valid From date. You can create several job streams with the same name but with different From dates. The scheduler selects the correct version for the day being planned. To A To date of 12/31/2071 is automatically assigned. 86 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

113 Creating z/os job streams Note: The IBM Tivoli Workload Scheduler ISPF main pane, option 1.8, allows you to create a job stream containing a single job by specifying only the name of the JCL associated with the operation. This option is not available in the job scheduling console. To create job streams with a single job, you must follow the steps in this chapter. Click OK. Table 25. What Happens When You Define a Job Stream If you are creating a... This happens... Job stream template The job stream editor opens the Timeline view, where you can open the Run Cycle view. You can add only run cycle information. Job stream that belongs to a template The job stream editor opens the Graph view where you can create jobs. Single job stream The job stream editor opens the Graph view from where you can add jobs and dependencies, and switch to the Run Cycle view to add run cycles. Creating a job for z/os job streams After you have specified the properties of a z/os job stream, you create the jobs that comprise it using the Graph view of the job stream editor. To access the Graph view of the job stream editor, display a list and double-click the job stream. The Graph view displays a button for each type of job that you can define. Table 26 describes these buttons: Table 26. Graph view job buttons This button... Performs this operation... Add JCL Job: Adds a job consisting of JCL statements. Runs on computer workstations. Add Started Task Job: Adds a started task. Runs on computer workstations on which the Started task, STC check box was selected. Add Printer Job: Adds a job to print the output of a predecessor job. Runs on printer workstations. Add General Job: Adds a job to include activities other than printing and processing, such as manual activities. Runs on general workstations. Add Setup Job: Adds a job containing a set of JCL statements for a JCL or started task job. Runs on general workstations on which the Job setup check box was selected. Add Write-to-Operator Job: Adds a job containing an operator instruction displayed on the system console. Runs on general workstations on which the WTO check box was selected. Add FTW Task: Adds a job to run on a fault-tolerant workstation. Add Dependency on External Job: Creates, browses, or modifies a dependency on a job that is part of another job stream. Chapter 18. Creating job streams 87

114 Creating z/os job streams Table 26. Graph view job buttons (continued) This button... Performs this operation... Add Link: Creates a link between jobs. Graph: Changes to the Graph view. Timeline: Changes to the Timeline view. Run Cycle: Changes to the Run Cycle view. The property panes for the different job types are identical. However, when you save the job stream, Tivoli Workload Scheduler applies different validation policies to the properties that you specified, based on the job type. When you search for a target workstation, only workstations compatible with the specific job type are listed. Creating a job in z/os To create a job in the job stream, click one of the job buttons in the Graph view of the job stream editor. For example, to create a JCL Job, click Add JCL Job. The Properties - JCL Job panel is displayed. General tab: Table 27 defines the information necessary to create the general information of a job. Table 27. Properties - JCL Job General information In this area... Specify... Information Name The JCL job name. Target workstation The name of the workstation on which the job is run. This information is required. Description A brief description of the job. Auto hold release To release the job when it is not submitted by Tivoli Workload Scheduler and is in HOLD status. The job is released when all dependencies are satisfied and the requested resources are available. Auto hold release is the default. Auto error completion To mark the job ended-in-error (E) if an error occurs when it runs. Auto error completion is selected by default. If you clear it, the job is marked complete (C) when it ends, regardless of the outcome. Critical job To define the job as a critical job. This makes the job eligible for Workload Manager (WLM) service class promotion when the job runs late. Monitored Job That the running of this job is to be monitored by Tivoli Business Systems Manager. 88 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

115 Creating z/os job streams Table 27. Properties - JCL Job General information (continued) In this area... Specify... Cancel if late To prevent the job from being started if it is late (according to the time dependencies specified in the Time Restrictions page). 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). Auto job submission To start the job automatically or to issue a WTO message (when all dependencies have been satisfied and all required resources are available). Auto job submission is selected by default. Deadline WTO To issue an operator message if the job passes its deadline. The message is also written to the message log. Centralized script That the script associated to the job resides on the domain master. WLM policy The WLM policy applied for WLM service class promotion when this job is late if you selected Critical Job. Possible values are: Conditional The scheduler uses an algorithm to determine whether to apply the Deadline or the Latest start option. Deadline The scheduler intervenes if the job runs beyond the deadline. Latest start The scheduler intervenes immediately if the job starts after the latest start time. Highest acceptable return code Long duration The scheduler intervenes if the job takes longer than it should as compared to the statistics that it keeps. The highest acceptable return code from any step in the job before the job is set to ended-in-error (E) status. If you leave this field blank, IBM Tivoli Workload Scheduler for z/os uses the value specified in HIGHRC in the initialization parameter JTOPTS. Restartable Whether to restart the job if the related workstation becomes inactive. Possible values are: v Yes: Restarts the job from the beginning on the alternate workstation (if one was defined), or on this workstation when it becomes active again. v No: Restarts the job, even if it overrules the installation default in the WSFAILURE or WSOFFLINE parameters of the JTOPTS initialization statement. v Default: Uses the installation default action specified in the OPRESTARTDEFAULT keyword of the JTOPTS statement. This is selected by default. Chapter 18. Creating job streams 89

116 Creating z/os job streams Table 27. Properties - JCL Job General information (continued) In this area... Specify... Reroutable Whether to make the job eligible to be rerouted if its workstation becomes inactive. This option applies to the job only when it is in ready (R) or waiting (W) status. Possible values are: v Yes: Makes the job reroutable. v No: Makes the job not reroutable. v Default: Takes the installation default action specified in the OPREROUTDEFAULT keyword of the JTOPTS statement. This is selected by default. Restart and Cleanup Specify which data set and job restart actions must be performed if the job ends in error. This option is not available for fault-tolerant workstations. Possible values are: v None: No cleanup and restart actions are performed. This is the default. v Immediate: Data set cleanup is performed immediately if the job ends in error. This option is not linked to a restart, which must be initiated separately. The operation is treated as if it had the Automatic option selected when it is rerun. v Automatic: A data set cleanup is inserted automatically as the first step to be performed during the rerun of the failed job. This is the preferred method of running restart and cleanup. v Manual: Restart and cleanup actions are to be initiated manually from the Modify Current Plan ISPF dialog. Expanded JCL That the JCL used for step-level restarts and, optionally, job reruns, should not be the JCL contained in the scheduler libraries but the JCL image captured from the JESJCL sysout data set. This is the default and recommended option. Use Sys Out That user sys out data sets should be used for job restarts. Feedback options The scheduler automatically monitors the actual durations of jobs. It can use these durations to modify the estimates in the application description (AD) database. Possible values are: v Smoothing factor: A number, from 0 to 999, that determines how much a measured duration changes existing values in the AD database. If a measured duration is outside the limit set by Limit for feedback, the smoothing factor is not applied and the AD database is not updated. v Limit for feedback: A number, from 100 to 999, to set the limit within which measured values are regarded as acceptable. A measured value outside the limit is ignored. No smoothing factor is applied and the AD database is not updated. Task tab: In the Task tab, enter information about the program associated with the job. Note: If the task is a manual operation, leave this tab blank. 90 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

117 Creating z/os job streams Use the information in Table 28 to enter all the information needed to define the task. Table 28. Properties - JCL Job Task information In this area... Specify... Task name The name of the JCL associated with the job. Together with the identifier you specified in the previous tab, the task name labels the job in the Graph view of the job stream editor. Form number The printer form number that appears on the daily plan and ready lists. For printer workstations with automatic reporting, it enables the engine to identify the different print operations that belong to a specific job. Job class A letter that matches the host job class from the JCL. Output class A letter that matches the host output class from the JCL. Use extended information That Extended task name is enabled. Extended task name A descriptive name for the job. Maximum supported length is 54 characters. Time Restrictions tab: In the Time Restrictions tab, specify the period of time that the job is allowed to run and the amount of time the job requires. Table 29 defines the information necessary to define the time restrictions for the job. Table 29. Properties - JCL Job Time Restrictions information In this area... Specify... Start: Specify the time at which the job can start. No restrictions To run the job as soon as all dependencies are met. No time restrictions can result in more efficient processing for certain jobs when extending a plan. In this way, they are run as soon as dependencies are satisfied. Note: This choice is not valid if you selected Cancel if late in the General tab. Follow job stream rules That the earliest time the job can start is when the job stream starts. This is the default. Note: This choice is not valid if you selected Cancel if late in the General tab. Specify earliest start time Deadline A specific time before which the job should not start. Then: 1. In At, type a time according to your locale settings. For example, type 12:00 if you do not want the job to start before noon. 2. In Delay for days, type a number of days to defer the start time. For example, if you type 3, the job starts three days after the time you originally specified in At. Specify deadline The latest time that the job can end. Use At and Delay for days. The default is no deadline time. Duration Hours, Minutes, Seconds How long the job is expected to run, in hours, minutes, and seconds. Chapter 18. Creating job streams 91

118 Creating z/os job streams Resources tab: In the Resources tab, describe the parallel servers, and the logical and workstation resources that the job uses. In the procedure, you perform the following actions on target resources and logical resources that you access from the drop-down list: Target resources Where you specify the workstation (or fixed) resources, and the parallel servers, that the job needs to run. Logical resources Where you specify the logical and physical resources that the job needs to run 1. Click the arrow next to Target resources. Columns are displayed where you can specify the target resources. 2. Double-click each cell in the Quantity column to edit the amount of resources (Resource 1 and Resource 2) that are required by the job. Do the same for parallel servers. 3. Click the arrow and select Logical resources. Columns are displayed where you can specify the logical resources. 4. Click Add row for each resource you need to assign to the job. 5. Type the name of the resource. If you do not know it, use... (find) to search for it. 6. For each logical resource, double-click under the next three columns to edit the following attributes: Quantity Specify the amount of the resource needed by the job. Access type Specify whether the job needs shared or exclusive access to the resource. Keep on error Specify whether the job keeps or frees the resource when it fails. You can also specify to use the default defined in the ONERROR keyword of the RESOPTS statement. The default value is FREESR. When you have finished, click OK to save your changes and close the window. The new job is displayed as an icon in the Graph view of the job stream editor. The name of the job is made up of the name of the task with which the job is associated and by the job identifier. You can drag and drop the icon to position it. Repeat the steps in this section to create as many jobs as you need. Note: You can use the slider, positioned on the left margin of the Graph view, to zoom in and zoom out the jobs displayed. When you move the slider downwards to zoom out of the Graph view, the job buttons change their appearance, changing color depending on the job type. Creating dependencies between jobs When you create dependencies, you link jobs in a sequence. A successor job cannot begin until the predecessor job is complete. Dependencies determine when the successor job runs, even if the successor job has time restrictions. 92 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

119 Creating z/os job streams For example, to print bank account statements, you must first subtract withdrawals from an account (Job A) before you calculate the account balance (Job B). Job A is the predecessor and Job B the successor. Creating dependencies within a job stream To create a dependency between jobs within the same job stream, perform the following steps: 1. In the Graph view of the job stream editor, click Add Link. 2. Click the predecessor job and drag the link to the successor job. A line is displayed between the two jobs, with an arrow pointing to the successor job. 3. Repeat the previous steps to create as many dependencies as you need. Creating dependencies between job streams External jobs represent jobs that are part of other job streams. You create a dependency between jobs in different job streams by creating a dependency on an external job. For example, if Job C in the Accounts job stream depends on Job B in the Reports job stream, you create an external job in the Accounts job stream to represent Job B, then you create a dependency between Job C and the external job. This section describes one way to add an external job to a job stream. Another method, based on the use of job stream lists, is described in Using the copy function to add an external job on page 165. To create a dependency between job streams, perform the following steps: 1. In the Job Stream Editor Graph view, click Add Dependency on External Job. The Properties - External Job panel is displayed. 2. In Job Stream, type the name of the job stream containing the external job. 3. Click Show Jobs. The jobs in the job stream are displayed. 4. Select a job and click OK. An icon for the external job is displayed in the Graph view. 5. Repeat the steps explained in Creating dependencies between jobs on page 92 to define links with the other jobs. Scheduling job streams After creating the jobs and defining any existing dependencies between them, you specify the scheduling information for the job stream using run cycles. Run cycles are generated from a combination of the following information: v A calendar of workdays and freedays. The calendar is defined in IBM Tivoli Workload Scheduler for z/os. You specify its name in the Job Stream Properties panel (see Creating a job stream for a z/os engine on page 85). v The validity date of the job stream, which you specify in the Job Stream Properties panel. Chapter 18. Creating job streams 93

120 Creating z/os job streams Types of run cycle You can create two types of run cycle: v v Offset-based Uses a combination of user-defined periods and offsets. For example, an offset of 3 in a period of 15 days is the third day from the beginning of the period. It is more practical to use offset-based run cycles when the cycle is based on cyclic periods. Rule-based Uses rules based on lists of ordinal numbers, types of days, and common calendar intervals or period names. For example, the last Thursday of every month. Rule-based run cycles are based on conventional periods, such as calendar months, weeks of the year, and days of the week, or periods that you define, such as a semester. You can specify multiple run cycles when you create a job stream, and you can add new ones afterwards. You can also mix rule-based and offset-based run cycles. Both types of run cycles can be either inclusionary or exclusionary. Inclusionary run cycles specify the days that the job stream must run. Exclusionary run cycles specify the days that the job stream must not run. You can add run cycles to generate more days, or to have multiple instances on the same day. You can add exclusionary run cycles to exclude some of the days already generated. Creating a run cycle To create a run cycle, in the job stream editor, click Run Cycle. The Run Cycle view is displayed. Table 30. Run cycle buttons If you are going to use... Click... Offsets Offset-based Run Cycle Rules Rule-based Run Cycle Creating rule-based run cycles The Properties - Rule-based Run Cycle panel is displayed. General tab: Table 31 defines the information necessary to define the run cycle details. Table 31. Run Cycle General information In this area... Specify... General Name A name for the run cycle. Note: Offset-based run cycles take the name of the period specified in the Offsets page. See Creating offset-based run cycles on page 99. Description A description of the run cycle. Exclusionary run cycle If the run cycle keeps the job stream from running. 94 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

121 Creating z/os job streams Table 31. Run Cycle General information (continued) In this area... Specify... Rule for freedays How you want IBM Tivoli Workload Scheduler for z/os to treat freedays when calculating the rundays of the job stream, by selecting one of the following: Count workdays only Excludes freedays when calculating on which days the job stream runs. This is the default for offset-based run cycles. Schedule on last workday before freeday Counts both workdays and freedays. If the runday falls on a freeday, it is shifted to the closest workday before the freeday. Schedule on next workday after freeday Counts both workdays and freedays. If the runday falls on a freeday, it is shifted to the closest workday after the freeday. Count workdays and freedays alike Counts both workdays and freedays. The job stream is scheduled on the runday, regardless whether it is a freeday or a workday. This is the default for rule-based run cycles. If freeday, do not schedule at all Counts both workdays and freedays. If the runday falls on a freeday, the job stream is not scheduled to run. JCL variable table A name of the variable table that the scheduler can use on the days generated by this run cycle. Alternatively, click the ellipsis (...) to search for a variable table name. Valid Date From, To An interval of time for which the run cycle applies. Click the calendar buttons next to each field to select dates using pop-up calendars. The intersection between this valid date and the valid date you defined in the Job Stream Properties pane is the interval during which the job stream is actually scheduled. Time Restrictions tab: Table 32 defines the information necessary to define the time restrictions. Table 32. Run Cycle Time Restrictions information In this area... Specify... Start At The time when the job stream must start. The default is 00:00 of the scheduled day. Deadline At The time for the job stream to stop. Delay for days A number of days after the start of the schedule. The default is no deadline time. Chapter 18. Creating job streams 95

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

123 Creating z/os job streams Figure 8 illustrates a rule that schedules the job stream to run on the fifth day of every week. Figure 8. Example rule Click OK. The following happens: v IBM Tivoli Workload Scheduler for z/os calculates the days of the run cycle. v The run cycle name is displayed in a list to the left of the graphic calendar in the Run Cycle view. If you right-click it, you can then select a number of actions on the run cycle, such as Properties, Copy, and Delete. v The rundays are displayed in blue in the graphic calendar. When you select the run cycle from the list, a blue stripe is displayed at the top of the corresponding generated days. Example 1: Rule-based run cycle: Figure 9 on page 98 illustrates a rule-based run cycle starting from a Valid Date of May, 23, 2003, and where workdays and freedays are both counted. Chapter 18. Creating job streams 97

124 Creating z/os job streams Figure 9. Example 1: Rule-based run cycle Example 2: Exclusionary run cycle: Figure 10 illustrates an exclusionary run cycle WPREXCEP that prevents job stream PAYRO21 from running on the last Friday of May The rundays of an exclusionary run cycle are marked with a red bar in the graphic calendar. Figure 10. Example 2: Exclusionary Run Cycle WPREXCEP excludes the WEEKLYPR run cycle in the week marked in red. 98 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

125 Creating z/os job streams Example 3: Exclusionary run cycle defined: Figure 11 illustrates a rule defined for the WPREXCEP exclusionary run cycle. The selected days are equal to those for the WEEKLYPR run cycle. The week when the job stream must not run is specified in In the following weeks. Figure 11. Example 3: Exclusionary run cycle defined Creating offset-based run cycles Table 34 defines the information necessary to specify the combination of period and offsets on which a run cycle is based. Table 34. Offset-based run cycle rules information In this area... Specify... In the following period The name of a user-defined period. Note: The name of the period is also used as the run cycle name. If you need to specify more than one period, create an offset-based run cycle for each period within the job stream. Available offsets The days when you want the job stream to run in the period. Select ordinal last days to count the days from the end of the period. The days you select are displayed in Selected offsets. Click OK. The following happens: v IBM Tivoli Workload Scheduler for z/os calculates the days of the run cycle. v The run cycle name is displayed in a list to the left of the graphic calendar in the Run Cycle view. If you right-click it, you can then select a number of actions on the run cycle, such as Properties, Add, and Delete. v The rundays are displayed in blue in the graphic calendar. When you select the run cycle from the list, a blue stripe is displayed at the top of the corresponding generated days. Chapter 18. Creating job streams 99

126 Creating z/os job streams Example 1: Offset-based run cycle: Figure 12 illustrates an offset-based run cycle named PER1. This run cycle schedules job stream PAYRO21 to run on every second day of each cycle, beginning from a Valid date of May 21, Figure 12. Example 1: Offset-based run cycle Example 2: Offset-based run cycle defined: Figure 13 illustrates the offset for run cycle PER1. The offset is the second day of the user defined period, also named PER1. Figure 13. Example 2: Offset-based run cycle defined 100 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

127 Saving a job stream After you have specified job stream properties and defined jobs, job dependencies, and run cycles, you can save the job stream. Job streams are saved in the scheduler database. To save the new job stream, click Save in the job stream editor toolbar. The Job Stream Editor checks for any missing or invalid information, then saves the job stream in the application description database. Note: You can save a job stream from any of the three views available in the job stream editor. You can define parts of a job stream, for instance the jobs that are in it, then save it and open it again later, as explained in the next chapter, to define its run cycles. If this is the case, do not mark it as active until it is ready to be scheduled. Creating a distributed job stream The Job Stream panel is displayed. Creating z/os job streams Chapter 18. Creating job streams 101

128 Creating distributed job streams General tab Table 35 defines the information necessary to create the general characteristics of the job stream. Table 35. Job Stream Properties General information In this area... Specify... Information Name The name of the job stream. The name must start with a letter, and can contain alphanumeric characters and dashes. Maximum supported length is 16 characters. The name of a job stream cannot be changed after it has been saved. However, you can use the create another command to save the job stream with another name. This field is mandatory. Workstation The name of the workstation or workstation class on which the job stream is launched. If you specify a workstation class, it must match the workstation class of any jobs or resources used in the job stream. This field is mandatory. Description A description of the job stream. Priority The priority of the job stream. Type a priority value or click: Hold Sets the priority to 0. High Sets the priority to 100. Go Sets the priority to 101. Possible priority values are 0 through 101, where 101 is the highest priority. A priority value of zero prevents the job stream from launching. For High and Go, all jobs in the job stream are given the priority. High and Go jobs are launched as soon as their dependencies are satisfied, overriding the workstation job limit, but not overriding the job stream job limit or the workstation job fence. Limit The number of jobs that can be running at the same time in the schedule. Possible values are 0 through If you specify a job limit of 0, no jobs are launched in the job stream. Options On Request That the job stream is selected for running on request. If you select On Request and specify run cycles for the job stream, the On Request flag is ignored and the job stream runs according to the run cycle. For more information, refer to the IBM Tivoli Workload Scheduler Reference Guide. Carry Forward 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. Job streams that are carried forward retain the carryforward option and, therefore, can be carried forward again. 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. Monitored Job Stream That the entire job stream must be monitored by Tivoli Business Systems Manager (TBSM) when it runs. 102 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

129 Creating distributed job streams Table 35. Job Stream Properties General information (continued) In this area... Specify... Contains Monitored Job This information field indicates whether any of the jobs in this job stream are monitored by Tivoli Business Systems Manager (TBSM) when they run. Value is Yes if at least one of the jobs in the job stream have Monitored Job selected in the Properties pane. Free Days Calendar The name of the calendar that lists the non-workdays for your company, such as holidays, and weekends, when you may not want the job stream to run. The calendar of freedays is used during the definition of the run cycles for the job stream. It is associated with the free day rule, where you tell Tivoli Workload Scheduler how to handle a job stream if the schedule falls on a freeday. See The freedays calendar on page 71 for details on creating freeday calendars. Use Default Default freedays calendar (usually named Holidays) that is displayed in Calendar Name. When you select Use Default, the other properties in this group become unavailable. Specify Calendar A freedays calendar and enter a calendar in Calendar Name. Select Saturday and Sunday if you want these days to be counted as freedays in the calendar. When you have finished, click OK. Time Restrictions tab Table 36 defines the information necessary to set the job stream time restrictions. Table 36. Job Stream Time Restrictions information In this area... Specify... Start Specify time That entry of a start time is enabled. The earliest time the job stream will be launched. The job stream will not be launched before this time. If no time is specified, the job stream will be launched as soon as all necessary conditions are met. At A start time in the format of your locale, for example: 11:30 a.m. or 4:25 p.m.. Delay for days The number of days to offset the start time from the day the job stream is selected for inclusion in the production plan. Latest Start Time Specify time The latest start time at which the job stream should be allowed to start. At A start time in the format of your locale, for example: 11:30 a.m. or 4:25 p.m.. Delay for days The number of days to offset the latest start time from the day the job stream is selected for inclusion in the production plan. Chapter 18. Creating job streams 103

130 Creating distributed job streams Table 36. Job Stream Time Restrictions information (continued) In this area... Specify... Action The action to be performed in case the job stream does not start and the Latest Start Time expires. Suppress To specify that the job stream does not start, even if the error condition that prevented it from starting is corrected, and dependencies are not released. Suppress is the default. Continue To specify that the job stream starts when the error condition that prevented it from starting is corrected. Cancel To specify that the job stream is canceled and dependencies are released. Termination Deadline Specify time That entry of latest time the job stream is launched is enabled. The job stream will not be launched after this time. At A deadline time in the format of your locale, for example: 11:30 a.m. or 4:25 p.m.. Note: The Deadline time must be later than the Start Time. Delay for days The number of days to offset the deadline time from the day the job stream is selected for inclusion in the production plan. Time Zone Time Zone The time zone in which the job stream runs. All time values specified are in this time zone. Select a time zone from the drop-down list. If a time zone is not specified for the job stream, all time values specified in the Time Restrictions properties pane are in the time zone of the workstation on which the job stream is launched. This list is available only if time zone support is enabled. For information about enabling the time zone, refer to IBM Tivoli Workload Scheduler Planning and Installation Guide. Resources Note: Time restrictions can also be set in the Timeline view of the job stream editor. See Specifying time restrictions in the Timeline View on page 120 for more information. tab To add a resource dependency for the job stream, perform the following steps: 1. Click Add Row. This creates a new row in the list of resource dependencies. 2. Double-click in the Resources column to locate and insert a resource name. 3. Double-click in the Quantity column and enter the number of resource units required by the job stream. The default is one. Resources can be defined with up to 1024 units, but they can only be allocated in increments of 32. For example, 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. The number of jobs and schedules using a resource at any one time cannot exceed 32. To remove a resource dependency for the job stream, select the resource row in the list and click Delete from Table. When you have finished, click Files in the left pane of the Job Stream Properties pane. The Files page is displayed. 104 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

131 Files Prompts tab To add a file dependency for the job stream, perform the following steps: 1. Click Add Row. This creates a new row in the list of file dependencies. 2. Double-click in the Workstation column and locate and insert the name of a workstation or workstation class. 3. Double-click in the Filename column and type a file name or search for a file name. You can search for a workstation only if it is the one where the Job Scheduling Console resides. 4. Double-click in the Qualifiers column and enter the test conditions for the file dependency. On UNIX, the valid qualifiers are the same as UNIX test command conditions. For more information, refer to your UNIX system documentation. On Windows, only the following qualifiers are valid: -d %p True if the file exists and is a directory. -e %p True if the file exists. -f %p True if the file exists and is a regular file. -r %p True if the file exists and is readable. -s %p True if the file exists and its size is greater than zero. -w %p True if the file exists and is available for editing. Notes: Creating distributed job streams a. On both UNIX and Windows, the expression %p inserts the file name. b. Entering notempty is the same as entering -s %p. If no qualifier is specified, the default is -f %p. To remove a file dependency for the job stream, select the file row in the list and click Delete from Table. tab To define an ad hoc prompt dependency, select Ad Hoc Prompt from the drop-down list. For a predefined prompt dependency, select Predefined Prompt from the drop-down list. To add a prompt dependency for the job stream, perform the following steps: 1. Click Add Row. A new row is displayed in the list of prompt dependencies. 2. To add a predefined prompt, double-click in the Name column and locate and insert the name of a prompt. 3. To define an ad hoc prompt, double-click in the Text column and type the text of the prompt. The default behavior of a prompt is to display a message and wait for a reply. If the string begins with a colon (:), the message is displayed but no reply is necessary. If the string begins with an exclamation mark (!), the message is not displayed but it requires a reply. You can include backslash n (\n) within the text for new lines. You can include one or more scheduler parameters as part or all of the text string. To use a parameter, place its name between carets (^). Chapter 18. Creating job streams 105

132 Creating distributed job streams To remove a prompt dependency for the job stream, select the prompt row in the list and click Delete from Table. Adding external dependencies to a job stream Job streams can be dependent on the successful running of other job streams, jobs in other job streams, and jobs in other Tivoli Workload Scheduler networks (internetwork jobs). These external dependencies are also called predecessors. To add external dependencies to a job stream, open the job stream in the job stream editor and select External Dependencies from the File menu. The Job Stream External Dependencies panel is displayed. Click External Job, and select one of the following dependencies: v External job stream dependencies v Internetwork dependencies v External job dependencies Adding an external job stream dependency To add an external job stream dependency, perform the following steps: 1. Click Add Row. 2. Double-click in the Job Stream Name column of the new row. 3. Click... (find) in the Job Stream Name column to search for and select a job stream. Adding an internetwork dependency To add an internetwork dependency, perform the following steps: 1. Click Add Row. 2. Double-click in the Network Agent column of the new row. 3. Click... (find) in the Network Agent column to search for and select the name of the network agent. Internetwork dependencies require that a network agent is configured to communicate with the external scheduler network. For information about configuring a network agent, refer to the IBM Tivoli Workload Scheduler Reference Guide. 4. Double-click in the Dependency column of the new row and enter either a freeform dependency, or the job or job stream predecessor in the form workstation#jobstream.job. 106 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

133 Creating distributed job streams Adding an external job dependency To add an external job dependency, perform the following steps: 1. Click Add Row. 2. Double-click in the Job Name column of the new row. 3. Click the... (find) in the Job Name column to search for and select a job. Adding a job to a job stream A job definition is a description of work to be performed on a workstation. Jobs are scheduled for running by adding them to job streams. You add jobs to a job stream using the Graph view of the job stream editor. See Editing job streams using the job stream editor on page 161 for more information. To add a job to a job stream, perform the following steps: 1. To open the Graph view, right-click a job stream and select Open from the pop-up menu. 2. In the Graph view, click Add Job Definition in the toolbar. Specifying job properties The Properties - Job panel opens automatically when you add a new job to a job stream. If the panel is not displayed, right-click a job in the Graph view of the job stream editor and select Properties from the pop-up menu. General tab: Table 37 on page 108 defines the information necessary to specify the general properties of the job. Chapter 18. Creating job streams 107

134 Creating distributed job streams Table 37. Properties - Job General information In this area... Specify... Information Name The name of the job. Workstation Name The workstation this job is defined to run on. If this workstation is deleted, the task type for the job is unknown and must be specified before you can save the job again. Priority The priority of the job. Type a priority value or click: Hold Sets the priority to zero. High Sets the priority to 100. Go Sets the priority to 101. Possible priority values are 0 through 101, where 101 is the highest priority. A priority value of zero prevents the job from launching. Requires Confirmation That job completion must be confirmed by the operator. When a job that requires confirmation completes, it remains in PEND until confirmation is received. If confirmation is received before the job completes, its internal status is either SUCCP or ABENDP and other job and job stream successors are not released. Description A description of the job. Monitored Job That the running of this job must be monitored by Tivoli Business Systems Manager. Time Restrictions tab: Table 38 defines the information necessary to create the time restrictions for the job. Table 38. Properties - Job Time Restrictions information In this area... Specify... Start Specify time That entry of a start time is enabled. The job is not be launched before this time. At A start time in the format of your locale, for example: 11:30 a.m. or 4:25 p.m.. Delay for days The number of days to offset the start time from the day the job is selected for inclusion in the production plan. Latest Start Time Specify time The latest time at which the job should be allowed to start. At The latest possible start time in a format specific to your locale, for example: 11:30 a.m. or 4:25 p.m.. Delay for days The number of days to offset the latest start time from the day the job is selected for inclusion in the production plan. 108 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

135 Creating distributed job streams Table 38. Properties - Job Time Restrictions information (continued) In this area... Specify... Action The action to be performed in case the job does not start and the Latest Start Time expires. Suppress To specify that the job does not start, even if the error condition that prevented it from starting is corrected, and dependencies are not released. Suppress is the default. Continue To specify that the job starts when the error condition that prevented it from starting is corrected. Cancel To specify that the job is canceled and dependencies are released. Termination Deadline Specify Time To enable the entry of a deadline time. The job will not be launched after this time. At A deadline time in the format of your locale, for example: 11:30 a.m. or 4:25 p.m.. Delay for days The number of days to offset the deadline time from the day the job is selected for inclusion in the production plan. Time Zone Time Zone The time zone in which the job stream runs. All time values specified are in this time zone. Select a time zone from the drop-down list. If a time zone is not specified for the job stream, 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. This list is available only if time zone support is enabled. For information about enabling the time zone feature, refer to IBM Tivoli Workload Scheduler Planning and Installation Guide. Repeat Range Hours, Minutes The interval of time for each execution of the job to be repeated. Using the Repeat Range information with the Start and Termination Deadline times allows you to run a job instance, for example, every 15 minutes from 1:00 p.m. to 5:00 p.m.. Est. Duration Normal Elapsed Time Displays the average time this job requires to run, based on previous runs. Note: Time restrictions can also be set in the job stream editor Timeline view. For more information, see Specifying time restrictions in the Timeline View on page 120. Resources tab: To add a resource dependency for the job, perform the following steps: 1. Click Add Row. This creates a new row in the list of resource dependencies. 2. Double-click in the Resources column and click... (find) to locate and insert a resource name. Chapter 18. Creating job streams 109

136 Creating distributed job streams 3. Double-click in the Quantity column and enter the number of resource units required by the job. The number of jobs and schedules using a resource at any one time cannot exceed 32. To remove a resource dependency for the job, select the resource row in the list and click Delete from Table. Files tab: To add a file dependency for the job, perform the following steps: 1. Click Add Row. This creates a new row in the list of file dependencies. 2. Click... (find) to locate and insert the name of a workstation or workstation class. 3. Double-click in the Filename column and enter a file name. You can use the... only if the workstation you choose is the one where the Job Scheduling Console resides. 4. Double-click in the Qualifiers column and enter the test conditions for the file dependency. On UNIX, the valid qualifiers are the same as UNIX test command conditions. For more information, refer to your UNIX system documentation. For a list of the Windows qualifiers, see 4 on page 105. On both UNIX and Windows, the expression %p inserts the file name. Entering notempty is the same as entering -s %p. If no qualifier is specified, the default is -f %p. To remove a file dependency for the job, select the file row in the list and click Delete from Table. Prompts tab: For an ad hoc prompt dependency, select Ad Hoc Prompt from the drop-down list. For a predefined prompt dependency, select Predefined Prompt from the drop-down list. To add a prompt dependency for the job, do the following: 1. Click Add Row. This creates a new row in the list of prompt dependencies. 2. For a predefined prompt, double-click in the Name column and click... (find) to locate and insert the name of a prompt. 3. For an ad hoc prompt, double-click the Text column and enter the text of the prompt. The default behavior of a prompt is to display a message and wait for a reply. If the string begins with a colon (:), the message is displayed but no reply is necessary. If the string begins with an exclamation mark (!), the message is not displayed but it requires a reply. You can include backslash n (\n) within the text for new lines. You can include one or more scheduler parameters as part or all of the text string. To use a parameter, place its name between carets (^). To remove a prompt dependency for the job, select the prompt row in the list and click Delete from Table. Copying and pasting jobs In the job stream editor you can copy and paste job and job stream icons to create dependencies: v You can open a job stream in the Graph view of the job stream editor, then copy another job stream from a job stream list and paste it into the job stream editor. 110 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

137 Creating distributed job streams Using Add Link, you can create an external dependency between the first and the second job streams. For more information, see Creating dependencies between jobs in a job stream on page 114. v You can open multiple job streams in separate job stream editors and copy and paste jobs between the job streams. v You can copy a job within the job stream editor and clone its dependencies to another job. Using the copy function 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, as described in the following example: 1. Run a job stream list. 2. Right-click a job stream and select Open. The job stream opens in the Graph view of the job stream editor. 3. Right-click another job stream in the list and this time select Copy from the pop-up menu. 4. Go to the job stream editor where the first job stream is open. 5. Right-click anywhere in the window and select Paste from the pop-up menu. 6. In the Dependencies Properties - External Job panel, select Show jobs. All the jobs that comprise the second job stream are displayed. 7. Select the job or jobs that you want to add as external jobs of the first job stream. 8. Click OK to close the Properties - External Job panel. Icons for the added jobs are displayed in the Graph view of the first job stream. Note: You can use Add Link to define dependencies between the jobs in the job stream editor. For more information, see Adding external dependencies to a job stream on page 106. Cloning 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. To clone the dependencies of a job, perform the following steps: 1. Right-click the job icon and select Copy from the pop-up menu. Alternatively, select the job icon and click Copy in the toolbar or select Copy from the Edit menu. This copies the job to the clipboard. 2. Click Paste in the toolbar or select Paste from the Edit menu. This displays the Properties - Job window for the copied job. 3. Use the Find tool to find and select a new job to add to the job stream. The job name is added to the Properties - Job General tab. 4. When you click OK in the Properties - Job panel, a new button is added for the job in the Graph view of the job stream editor. This job has the same dependencies as the copied job. 5. Save the job stream and close the job stream editor. Adding an internetwork dependency to a job stream An internetwork dependency is a dependency on a job that runs in another IBM Tivoli Workload Scheduler network. Internetwork dependencies require a network Chapter 18. Creating job streams 111

138 Creating distributed job streams agent workstation to communicate with the external scheduler network. For more information about configuring a network agent, refer to the IBM Tivoli Workload Scheduler Reference Guide. Add internetwork dependencies to a job stream to create predecessors for the jobs in the job stream you are editing. A predecessor must complete successfully before the successor job is launched. You add internetwork dependencies in a job stream using the Graph view of the job stream editor. See Editing job streams using the job stream editor on page 161 for more information. To add an internetwork dependency, perform the following steps: 1. To open the Graph view, right-click a job stream and select Open from the pop-up menu. 2. In the Graph view, click Add Dependency on Internetwork in the toolbar. The Internetwork Dependency pane is displayed. 3. Click... (find) to search for and select the name of the network agent. 4. In Dependency, specify either the freeform dependency, or the job or job stream predecessor in the format workstation#jobstream.job. The maximum length of this field is: v 120 for freeform characters v 16 for the workstation v 16 for the job stream v 40 for the job For information about using an internetwork dependency as a predecessor, see Creating dependencies between jobs in a job stream on page 114. Adding an external job stream to a job stream You add external job streams to a job stream to create predecessors for the jobs in the job stream you are editing. A predecessor must complete successfully before the successor job is launched. You add external job streams in a job stream using the Graph view of the job stream editor. For more information, see Editing job streams using the job stream editor on page 161. To add an external job stream, perform the following steps: 1. To open the Graph view, right-click a job stream and select Open from the pop-up menu. 112 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

139 Creating distributed job streams 2. Click Add Dependency on External Job Stream in the toolbar. The External Job Stream Dependency panel is displayed. 3. Click... (...) to locate and insert the name of the workstation on which the job stream runs. 4. Click Show Job Streams to list the job streams that run on the workstation. 5. Select a job stream from the list. 6. Add a link between the external job stream and its successor. For information about using an external job stream as a predecessor, see Creating dependencies between jobs in a job stream on page 114. Adding an external job to a job stream You add external jobs to a job stream to create predecessors for the jobs in the job stream you are editing. A predecessor must complete successfully before the successor job is launched. You add external jobs in a job stream using the Graph view of the job stream editor. For more information, see Editing job streams using the job stream editor on page 161. To add an external job, perform the following steps: 1. To open the Graph view, right-click a job stream and select Open from the pop-up menu. Chapter 18. Creating job streams 113

140 Creating distributed job streams 2. Click Add Dependency on External Job in the toolbar. The External Job Dependency panel is displayed. 3. Click... (find) to locate and insert the name of the job stream in which the job runs. 4. Click Show Jobs to list the jobs in the selected job stream that run on the selected workstation. 5. Select a job in the list. 6. Add a link between the external job stream and its successor. For information about using an external job as a predecessor, see Creating dependencies between jobs in a job stream. Creating dependencies between jobs in a job stream You can add dependencies between jobs to specify the order in which they run. A job that depends on the successful completion of another job is called a successor and the job or job stream that it depends on is called a predecessor. You add dependencies between jobs in the Graph view of the job stream editor. For more information, see Editing job streams using the job stream editor on page 161. The dependencies are represented by arrows. To add a dependency between jobs, perform the following steps: 1. To open the Graph view, right-click a job stream and select Open from the pop-up menu. 114 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

141 Creating distributed job streams 2. Click Add Link in the toolbar. 3. Click the predecessor job or job stream and drag it to the successor job. When you release the mouse button, an arrow is drawn from the predecessor to the successor. Notes: 1. Internetwork dependencies, external jobs, and external job streams cannot be successors. 2. Internetwork dependencies, external jobs, and external job streams that are not linked are not saved when the Job Stream Editor is closed. To remove a dependency between jobs, select the arrow between the predecessor and the successor, then right-click the arrow and select Delete from the pop-up menu. Specifying run cycles for a job stream Run cycles specify when a job stream in the database is to run in the plan. Combinations of run cycles are used to include and exclude certain dates. There are the following types of run cycle: v Simple Run Cycles Based on specific calendar dates. v Weekly Run Cycles Based on days of the week. v Calendar Run Cycles Based on predefined calendars. For details about creating calendars, see Chapter 14, Creating calendars, on page 71. You specify run cycles for a job stream using the Run Cycle view of the job stream editor. To display the Run Cycle view, select Run Cycle from the View menu in the job stream editor or click Run Cycle in the toolbar. See Figure 9 on page 98. Inclusionary or exclusionary run cycles When you define a run cycle, you must specify if it designates the days when the job stream is to run (inclusionary) or when the job stream is not to run (exclusionary). The days you mark in an inclusive run cycle are displayed as Days Included in the list of run cycles applied to the job stream. 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. Excluded days always take precedence over included days. For each job stream, you can define as many inclusive and exclusive run cycles as you want. Rule for freedays This rule is based on the definition of freedays. Freedays are non-workdays, such as holidays or weekends, and can be defined in one or more specific calendars. Freedays calendars can in other terms be considered the list of non-workdays when there is no activity in your enterprise. For details, see The freedays calendar on page 71. Based on a freedays calendar, you can specify a rule when you define the run cycle of a job stream. The rule determines what action Tivoli Workload Scheduler must Chapter 18. Creating job streams 115

142 Creating distributed job streams take when the schedule of a job stream falls on a freeday. If the schedule date falls on a freeday, the scheduler can do one of the following: v Run the job stream v Not run the job stream v Run the job stream on the closest workday before the freeday v Run the job stream on the closest workday after the freeday If no freeday rule is specified, the scheduler proceeds by default and runs the job stream even if the selected run date is a freeday. Tivoli Workload Scheduler does not reschedule the same job stream more than once on a given production day if its run date was moved because of a freeday rule application. Colored bars on dates As you include and exclude dates, colored bars are displayed across the dates. The bars have the following meanings: Table 39. Colored bars on dates This bar... Specifies... Blue An included date. Red An excluded date. White A non-workday. White/Blue An included non-workday. White/Red An excluded non-workday. Note: Dates defined in the Holidays calendar are shown as non-workdays. For more information, see The Holidays calendar on page 71. Specifying simple run cycles You specify run cycles using the job stream editor. To do this, perform the following steps: 1. Right-click a job stream and select Open from the pop-up menu. The job stream editor is displayed. 2. Click Run Cycle in the toolbar. 116 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

143 Creating distributed job streams 3. Click Simple Run Cycle. The Simple Run Cycle panel is displayed. 4. In Inclusive/Exclusive Run Cycle: v Select Inclusive to specify that the job stream must run in the dates defined on the Rule tab. v Select Exclusive to specify that the job stream must not run in the dates defined on the Rule tab. 5. Click the arrow in the Rule for Freedays list box and select one of: Select nearest workday before freeday If the scheduled date falls on a freeday, run the job stream on the preceding workday. Select nearest workday after freeday If the scheduled date falls on a freeday, run the job stream on the following workday. If freeday, do not select If the scheduled date falls on a freeday, do not run the job stream. None Follow no rule. Run the job stream regardless of whether the schedule falls on a freeday or on a workday. 6. Select Rule. The Rule tab is displayed. 7. Select the Monthly or Yearly tab to display the corresponding view. Use the arrow buttons in the upper and lower bars of the selected view to move to the desired month and year. 8. Click the dates in the calendar to add them to the run cycle. Click on the same date a second time to remove it from the run cycle. Specifying weekly run cycles To specify a weekly run cycle for a job stream, perform the following steps: Chapter 18. Creating job streams 117

144 Creating distributed job streams 1. Right-click a job stream and select Open from the pop-up menu. The job stream editor is displayed 2. Click Run Cycle in the toolbar. 3. Click Weekly Run Cycle. The Weekly Run Cycle panel is displayed. 4. In Inclusive/Exclusive Run Cycle: v Select Inclusive to specify that the job stream must run in the dates defined n the Rule tab. v Select Exclusive to specify that the job stream must not run in the dates defined in the Rule tab. 5. Click the arrow in the Rule for Freedays list box and select one of: Select nearest workday before freeday If the scheduled date falls on a freeday, run the job stream on the preceding workday. Select nearest workday after freeday If the scheduled date falls on a freeday, run the job stream on the following workday. If freeday, do not select If the scheduled date falls on a freeday, do not run the job stream. None Follow no rule. Run the job stream regardless of whether the schedule falls on a freeday or on a workday. 6. Click Rule to display the Rule tab. 7. Select the days by name to add them to the run cycle. In addition to single days, you can also select: Weekdays Specifies every day of the week except Saturday and Sunday. 118 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

145 Creating distributed job streams Freedays Specifies the days defined either in the freedays calendar or in the Holidays calendar, depending on which one you specified in the properties panel of the job stream. Workdays Specifies every day of the week except Saturday, Sunday, and the days defined either in the freedays calendar or in the Holidays calendar, depending on which one you specified in the properties panel of the job stream. Everyday Specifies every day of the week. Specifying calendar run cycles To specify a calendar run cycle for a job stream, perform the following steps: 1. Right-click a job stream and select Open from the pop-up menu. The job stream editor is displayed 2. Click Run Cycle in the toolbar. 3. Click the Calendar Run Cycle. The Calendar Run Cycle panel is displayed. 4. In Inclusive/Exclusive Run Cycle select: v Inclusive to specify that the job stream must run in the dates defined in the Rule tab. v Exclusive to specify that the job stream must not run in the dates defined in the Rule tab. 5. Click the arrow in the Rule for Freedays list box and select one of: Select nearest workday before freeday If the scheduled date falls on a freeday, run the job stream on the preceding workday. Select nearest workday after freeday If the scheduled date falls on a freeday, run the job stream on the following workday. If freeday, do not select If the scheduled date falls on a freeday, do not run the job stream. None Follow no rule. Run the job stream regardless of whether the schedule falls on a freeday or on a workday. 6. Click Rule. 7. Enter the name of the calendar in the Name field or click... (find) to find a calendar. 8. In the Offset group, you can specify an offset from the dates defined in the calendar. For example, if a calendar date is 3/13/2001, an offset of +2 Days results in an effective date of 3/15/2001. To specify an offset: a. Select the positive sign (+) for a positive offset or the negative sign (-) for a negative offset from the drop-down menu. b. In the Offset field, enter the number of days (between 0 and 9999). c. From the drop-down menu, select one of: Days Specifies calendar days with no exceptions. Workdays Specifies calendar days except Saturday, Sunday, and the days defined either in the freedays calendar or in the Holidays calendar, depending on which one you specified in the properties window of the job stream. Weekdays Specifies calendar days except Saturday and Sunday. Chapter 18. Creating job streams 119

146 Creating distributed job streams 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. Specifying time restrictions for a job stream To specify time restrictions for the job stream, select Timeline from the View menu in the job stream editor or click Timeline in the toolbar. Using the Timeline View: To adjust the time restrictions using the timeline, do any of the following: v Drag the left side of the timeline to adjust the start time. v Drag the right side of the timeline to adjust the deadline time. v Drag the center of the timeline to change both the start and the deadline time. Using a properties pane: To adjust the time restrictions using a pane, either double-click the job stream row in the tabular pane or right-click the row and select Properties from the pop-up menu. A properties panel is displayed. Table 40 defines the information necessary to create time restrictions. Table 40. Properties Information In this area... Specify... Start Specify time That entry of a start time is enabled. The earliest time the job stream will be launched. The job stream is not launched before this time. If no time is specified, the job stream is launched as soon as all necessary conditions are met. At A start time in a format specific to your locale, for example: 11:30 a.m. or 4:25 p.m.. Delay for days The number of days to offset the start time from the day the job stream is selected for inclusion in the production plan. Latest Start Time Specify time The latest start time at which the job stream should be allowed to start. At The latest possible start time in a format specific to your locale, for example: 11:30 a.m. or 4:25 p.m.. Delay for days The number of days to offset the latest start time from the day the job stream is selected for inclusion in the production plan. Action The action to be performed in case the job stream does not start and the Latest Start Time expires. Suppress The job stream does not start, even if the error condition that prevented it from starting is corrected, and dependencies are not released. Suppress is the default. Continue The job stream starts when the error condition that prevented it from starting is corrected. Cancel The job stream is canceled and dependencies are released. Termination Deadline 120 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

147 Creating distributed job streams Table 40. Properties Information (continued) In this area... Specify... Specify time That the latest time the job stream will be launched is enabled. The job stream will not be launched after this time. At A deadline time in a format specific to your locale, for example: 11:30 a.m. or 4:25 p.m.. Note: The Deadline time must be later than the Start Time. Delay for days The number of days to offset the deadline time from the day the job stream is selected for inclusion in the production plan. Time Zone Time Zone The time zone in which the job stream runs. All time values specified are in this time zone. Select a time zone from the drop-down list. If a time zone is not specified for the job stream, 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. This list is available only if time zone support is enabled. For information about enabling the time zone feature, refer to IBM Tivoli Workload Scheduler Planning and Installation Guide. Note: Time restrictions can also be set in the Time Restrictions view of the Properties - Job panel. For more information, see Specifying time restrictions in the Timeline View on page 120. Specifying time restrictions for a job To specify time restrictions for a job in the Timeline view of the job stream editor, either select Timeline or click Timeline in the toolbar. For information about using the timeline view and the Properties panel, see Specifying time restrictions for a job stream on page 120. Note: Time restrictions can also be set in the Time Restrictions view of the Properties - Job panel. See Specifying job properties on page 107 for more information. Chapter 18. Creating job streams 121

148 Creating distributed job streams 122 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

149 Chapter 19. Creating resources Creating a z/os resource Resources represent the physical or logical objects that are used by jobs. You can use resources to prioritize access to a data set or to limit the number of simultaneous file transfers on a particular network link. Before a job can use a resource, you must create it specifying the associated workstations and attributes. To create a resource, perform the following steps: 1. In the Actions list pane, click New Resource. 2. Select the engine. The Resource in Database panel depends on the type of engine: z/os or distributed. The Resource in Database panel is displayed. The panel consists of the following tabs: v Resource Resource v Default Workstations v Availability Intervals tab Use the Resource tab to enter general information about the resource you are creating. Copyright IBM Corp. 1991,

150 Creating z/os resources Table 41 defines the information necessary to create the resource. Table 41. Create a resource information In this area... Specify... Information Name A name identifying the resource. The name is converted to uppercase. Description A description of the resource. Hiperbatch Whether the resource is a data set eligible for Hiperbatch. Hiperbatch is a host performance enhancement that works with the Data Lookaside Facility (DLF) to enable batch jobs and started tasks to share access to data sets. Group ID A name of up to eight characters that identifies a group to which the resource belongs. The group ID can be used as a list filter for selecting subsets of resources. Used for How the resource is to be used. Possible values are: v Planning v Control v Planning and control v Neither planning nor control On error The action to take when a job that allocates this resource ends in error, and does not have an overriding keep-on-error specification in the job definition: Free Free the full allocation of this resource, both exclusive and shared. Keep Keep the full allocation of this resource. You may want critical jobs to keep their resources even when they fail, to avoid having to wait for resources when the job is restarted. Free if exclusive Free the full exclusive allocation of this resource. Free if shared Free the full shared allocation of this resource. Assume System Default Use the default specified in the ONERROR keyword of the RESOPTS statement. The default value is FREESR. Default Is Available Whether the resource is usually available. You can specify on the Availability Intervals tab when the resource is not available for a particular workstation. Quantity A number in the range of of this resource to be reserved when you select Is Available for the availability intervals associated with the resource. This information is used as the default unless otherwise specified for a given interval on the Availability Intervals tab. 124 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

151 Default Workstations tab Use the Default Workstations tab to list the workstations associated with, and reserved for the resource. By default, all workstations are already added when the Resource Editor pane for a new resource opens. To add one or more workstations, click on Find tool. To remove a workstation from the list, select it, then click Delete From Table. Availability Intervals tab Use the Availability Intervals tab to define the time intervals when the resource can be used. To add or delete an availability interval, click Add Row, or Delete from Table, then select the specific interval. After you have added a row, you can define the new interval. Table 42 defines the information necessary to create availability intervals. Table 42. Create availability intervals information In this column... Specify... Day menu A day of the week, Standard, or Specific Date. From Time and To Time The Standard interval represents the norm where the resource is used with the values you entered in the other two pages. When you define a new resource, you find a default Standard row where you need not add any values except, optionally, for a time range. Select a day or Specific Date to specify the intervals in which the resource is available with different Quantity, Availability, and Connected Workstations characteristics that you specify in the row itself. A time range. Quantity The quantity of the resource in this time interval. Creating z/os resources Is available menu Available, Not Available, or Default (the default specified in the Resource page). To put a resource off limits for a certain period, select Not Available.. Workstations The names of one or more connected workstations, each separated by a blank or double-click the Workstation column and click Find Workstation. When you have finished, click OK to save the new resource. Chapter 19. Creating resources 125

152 Creating distributed resources Creating a distributed resource The Properties - Resource in Database panel is displayed. Table 43 defines the information necessary to create a distributed resource. Table 43. Properties - Resource in Database Panel information In this area... Specify... Information Name The name of the resource. The name must start with a letter and can contain alphanumeric characters, dashes, and underscores. The name can contain up to eight characters. Description A description of the resource. Quantity The number of available resource units. Values can be 0 through Workstation The name of the workstation or workstation class on which the resource is used. 126 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

153 Chapter 20. Creating objects using Create Another This chapter describes how to create objects using the Create another feature. To create a new object in the database using a copy, perform the following steps: 1. Run a list that contains the object you want to copy. See Chapter 22, Working with object lists, on page 155 for more information. 2. In the list results, right-click the object you want to copy and select Create another. This displays a copy of the object in the relevant properties window. 3. In Name, change the name to the name of the new object. 4. Change the other properties as needed to define the new object. Copyright IBM Corp. 1991,

154 Using Create Another 128 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

155 Chapter 21. Creating lists This chapter describes how you create and maintain database and plan lists. When you create a list, you give it a name and specify the filtering criteria. When you run a list, it displays a filtered table of objects. Each list you create is represented by an icon in the tree view. There are two types of lists that you can create and work with: database lists and plan lists. There are also default plan and database lists provided, and common plan and database lists that relate to both the z/os and the distributed environments. This chapter is therefore divided into the following: v Creating database lists v Creating plan lists v Creating default common plan lists v Creating list groups Creating database lists v Setting list properties To create a database list right-click an engine, choose Create Database List, and select one of the following options: Table 44. Database properties list options To create this type of list... Go to page... Job Stream 131 Job Definitions 135 Workstation 133 Resource 134 Workstation Class 136 Prompt 136 Parameter 137 Windows User 137 Domain 138 Calendar 138 The Properties panels of database lists are essentially the same regardless of the list type, but they do differ for distributed and z/os engines. Figure 14 on page 130 illustrates the Properties panel for a distributed job stream list. The differences between this distributed list properties panel and the others are minimal, and described in the following subsections. Copyright IBM Corp. 1991,

156 Creating database lists Figure 14. Example Properties panel for distributed engines Figure 15 on page 131 illustrates the Properties panel for a z/os job stream list. The differences between this distributed list properties panel and the others are minimal, and described in the following subsections. 130 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

157 Creating database lists Figure 15. Example Properties panel for z/os Engines Creating a list of job streams You can create job stream lists for both the distributed and the z/os environments. The Properties - Job Stream List panel is displayed. The panel varies according to the engine you selected. Table 45 and Table 46 on page 132 define the information necessary to create the job stream list. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the job streams defined in the database are displayed when you open the list. Table 45. Job stream list data for distributed engines In this area... Specify... Information Name A name for the job stream list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Chapter 21. Creating lists 131

158 Creating database lists Table 45. Job stream list data for distributed engines (continued) In this area... Specify... Job Stream Name All the job streams with this name or name string. Workstation Name All the job streams related to the specified workstation(s). Table 46. Job stream list data for z/os engines In this area... Specify... Information Name A name for the job stream list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Job Stream All the job streams with this name or name string. Task Name All the job streams where this task or JCL is used. Extended Task Name All the job streams containing jobs that use a specific extended task name or name string. Job Stream Template All the job streams that are part of this template. Owner All the job streams that belong to this owner. Authority Group All the job streams that use this authority group for RACF authority checking. Calendar All the job streams that use this calendar. Workstation Lists all job streams containing jobs that run on this workstation. Is a template Only job streams that are templates. Exclude template Only job streams that are not templates. Priority From, To The priority level for the job streams to be listed. Dates From, To The dates for the job streams to be listed. Status of Job Stream v Active v Inactive v Ignore criteria Contains Monitored Job v Yes v No v Ignore criteria The status for the job streams to be listed. Select Ignore criteria to omit this filter. Whether to list job streams containing monitored jobs. Select Ignore criteria to omit this filter. Use the Column Definition tab to define the columns displayed in the list. 132 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

159 Creating a list of workstations You can create workstation lists for both the distributed and the z/os environments. The Properties - Database Workstation List panel is displayed. Table 47 and Table 48 define the information necessary to create the workstation list. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the workstations defined in the database are displayed when you open the list. Table 47. Workstation list data for distributed engines In this area... Specify... Information Name A name for the list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Workstation Name Lists workstations with this name or name string. Creating database lists Table 48. Workstation list data for z/os engines In this area... Specify... Information Name A name for the list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Workstation All the workstations with this name or name string. Reporting Attributes v Automatic v Completion only v Manual start and completion v Non reporting Workstation Types v v v General Computer Printer Is Fault Tolerant All the workstations characterized by the reporting attributes you select. All the workstations of the type you select. Chapter 21. Creating lists 133

160 Creating database lists Table 48. Workstation list data for z/os engines (continued) In this area... Specify... v Yes v No v Ignore Criteria Whether to List or excludes fault-tolerant workstations. Select Ignore criteria to omit this filter. Use the Column Definition tab to define the columns displayed in the list. Creating a list of resources You can create resource lists for both the distributed and the z/os environments. The Properties - Database Resource List panel is displayed. Table 49 and Table 50 define the information needed to create a resource list. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the resources defined in the database are displayed when you open the list. Table 49. Resource list data for distributed engines In this area... Specify... Information Name A name for the resource list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Resource Name All the resources with this name or name string. Workstation Name Workstations with this name or name string. Table 50. Resource list data for z/os engines In this area... Specify... Information Name A name for the list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Resource All the resources with this name or name string. 134 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

161 Creating database lists Table 50. Resource list data for z/os engines (continued) In this area... Specify... Treat Input As How the string that you specify in Resource is interpreted. 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. Group ID Resources that belong to the specified group. Hiperbatch v Yes v No v Ignore criteria Whether to List or excludes resources that can work with Hiperbatch. Select Ignore criteria to omit this filter. Use the Column Definition tab to define the columns displayed in the list. Creating a list of job definitions You can create a list of job definitions for the distributed environment only. The Properties - Job List panel is displayed. Table 51 defines the information necessary to create the job list. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the jobs defined in the database are displayed when you open the list Table 51. Properties - Job List information In this area... Specify... Information Name A name for the job list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Job Name All the jobs with this name or name string. Workstation Name All the jobs related to the specified workstation(s). Use the Column Definition tab to define the columns displayed in the list. Chapter 21. Creating lists 135

162 Creating database lists Creating a list of workstation classes You can create a list of workstation classes for the distributed environment only. The Properties - Workstation Class List panel is displayed. Table 52 defines the information necessary to create the workstation list. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the workstations defined in the database are displayed when you open the list. Table 52. Workstation Class List Data In this area... Specify... Information Name A name for the workstation class list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Workstation Class Name Workstation classes with this name or name string. Use the Column Definition tab to define the columns displayed in the list. Creating a list of prompts You can create a list of prompts for the distributed environment only. The Properties - Prompt List panel is displayed. Table 53 defines the information necessary to create the prompt list. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the prompts defined in the database are displayed when you open the list. Table 53. Prompt list data In this area... Specify... Information Name A name for the prompt list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Prompt Name Prompts with this name or name string. 136 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

163 Creating database lists Use the Column Definition tab to define the columns displayed in the list. Creating a list of parameters You can create a list of parameters for the distributed environment only. The Properties - Parameter List panel is displayed. Table 54 defines the information necessary to create the parameter list. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the parameters defined in the database are displayed when you open the list. Table 54. Properties - Parameter List information In this area... Specify... Information Name A name for the parameter list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Parameter Name Parameters with this name or name string. Use the Column Definition tab to define the columns displayed in the list. Creating a list of Windows users You can create a list of Windows users for the distributed environment only. The Properties - Windows User List panel is displayed. Table 55 defines the information necessary to create the Windows user list. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the Windows users defined in the database are displayed when you open the list. Table 55. Windows user list data In this area... Specify... Information Name A name for the Windows user list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Chapter 21. Creating lists 137

164 Creating database lists Table 55. Windows user list data (continued) In this area... Specify... Windows Domain \ User Name Domains or users with this name or name string. Use the Column Definition tab to define the columns displayed in the list. Creating a list of domains You can create a list of domains for the distributed environment only. The Properties - Domain List panel is displayed. Table 56 defines the information necessary to create the domain list. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the domains defined in the database are displayed when you open the list. Table 56. Domain list data In this area... Specify... Information Name A name for the domain list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Domain Name Lists domains with this name or name string. Use the Column Definition tab to define the columns displayed in the list. Creating a list of calendars You can create a list of calendars for the distributed environment only. The Properties - Calendar List panel is displayed. Table 57 defines the information necessary to create the calendar list. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the calendars defined in the database are displayed when you open the list. Table 57. Properties - Calendar List information In this area... Specify... Information Name A name for the calendar list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. 138 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

165 Creating database lists Table 57. Properties - Calendar List information (continued) In this area... Specify... Period (Secs) A refresh interval in seconds. Apply Defaults That the defaults specified in the scheduler Properties panel are applied. Filter Criteria Calendar Name Calendars with this name or name string. Creating plan lists Use the Column Definition tab to define the columns displayed in the list. To create a plan list right-click an engine, choose Create Plan List in the pop-up menu, and select one of the following options: Table 58. Plan list options To create this type of list... Go to page... Job Stream Instance 139 and 141 Job Instance 143 and 146 Workstation 148 Resource 148 File 148 Prompt 149 Domain Status 149 Creating a job stream instance list for distributed engines The Properties - Job Stream Instance List panel is displayed. General tab Table 59 defines the information necessary to create the job stream instance list. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the job stream instances defined in the plan are displayed when you open the list. Table 59. Properties - Job Stream Instance List General information In this area... Specify... Information Name A name for the list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Job Stream Name Job streams with this name or name string. Chapter 21. Creating lists 139

166 Creating plan lists Table 59. Properties - Job Stream Instance List General information (continued) In this area... Specify... Workstation Name Job streams related to workstations with this name or name string. Status Status The status to filter job stream instances. Select this option and select the status type from the drop-down list. Internal Status The internal status to filter job stream instances. Select this option and select the status type from the drop-down list. Priority From, To A priority range of job streams to display. Only job streams with priorities within the range are displayed. Possible priority values are 0 through 101, where 101 is the highest priority. Click Hold to select priority 0, High to select priority 100, or Go to select priority 101. Time Restrictions tab Table 60 defines the information necessary to filter on time restrictions. Table 60. Properties - Job Stream Instance List Time Restrictions information In this area... Specify... Start Time From Date The beginning of a range of time. Only job streams that start running within this range are displayed. To Date The end of a range of time. Only job streams that start running within this range are displayed. Latest Start Time From Date The beginning of a range of time. Only job streams that start running within this range are displayed. To Date The end of a range of time. Only job streams that start running within this range are displayed. Action The action to be performed when the job stream does not start before Latest Start Time. Finish Time Suppress The job stream does not start, even if the error condition that prevented it from starting is corrected, and dependencies are not released. This radio button is selected by default. Continue The job stream starts when the error condition that prevented it from starting is corrected. Cancel The job stream is canceled and dependencies are released. From Date The beginning of a range of time. Only jobs that are set to finish running within this range are displayed. To Date The end of a range of time. Only job streams that are set to finish running within this range are displayed. 140 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

167 Dependencies tab Use this tab to define a list of jobs from the plan based on dependency types. Only job stream instances with the specified dependencies are displayed. Note that all the fields in this window act as filters, so that all fields specified must be valid for a job stream to be chosen for display. For example, to display all job streams with a file dependency, enter an asterisk (*) in the File Dependency / File Name field. To display all job streams with both a file and a prompt dependency, enter an asterisk (*) in the File Dependency / File Name field and in the Prompt Dependency / Name field. Note: In this case, only job streams with both a file and a prompt dependency are displayed. Job Streams with only prompt dependencies or only file dependencies are not displayed. Table 61 defines the information necessary to filter on job stream dependencies. Table 61. Properties - Job Stream Instance List Dependency information In this area... Specify... Job/Job Stream Dependency Workstation The name of a workstation. Job Stream The name of a job stream. Job The name of a job. Resource Dependency Workstation The name of a workstation. Resource The name of a resource. File Dependency Workstation The name of a workstation. File Name The name of a file. Prompt Dependency Name The name of a prompt. Prompt Number The number of a prompt. Creating plan lists Column definition When you are creating lists, you can use the Column Definition tab to define the columns displayed in the list. This tab consists of three sections, Job Stream Table, Job Table and Dependency. In each of those sections you can choose the columns which describe all the information that you want to display in the list about the job instance, job stream instance, or dependency, selecting or clearing the check boxes corresponding to the column names. Creating a job stream instance list for z/os engines The Properties - Job Stream Instance List panel is displayed. Table 62 on page 142 defines the information necessary to create the job stream instance list. Specify any of the available search parameters or combinations of two Chapter 21. Creating lists 141

168 Creating plan lists or more parameters. If you leave all fields blank, all the job stream instances defined in the database are displayed when you open the list. Table 62. Properties - Job Stream Instance List information In this area... Specify... Information Name A name for the job stream instance list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Job stream All the job stream instances with this name or name string. Job stream template All the job stream instances that are part of this template. Occurrence Token The job stream that is identified by this occurrence token in the plan. The token is a unique 16-character hexadecimal string assigned to the job stream by the scheduler. Owner All the job stream instances that belong to this owner. Authority group All the job stream instances that use this authority group for RACF authority checking. Extended task name All the job stream instances containing jobs that use a specific extended task name or name string. Dates From, To All job stream instances scheduled to run in an interval period starting on the day and time specified in the Date and Time fields and ending in the day and time specified in the Date and Time fields. Pop-up calendars are provided to help you select the days. Priority From, To All the job stream instances that have the priority level you select. Manually Added v Yes v No v Ignore criteria Rerun requested v Yes v No v Ignore criteria Contains Monitored Job v Yes v No v Ignore criteria Most Critical Job To lists or exclude job stream instances that were added manually to the plan (and not automatically through a plan extension). Select Ignore criteria to omit this filter. To lists or exclude job stream instances for which a rerun was requested. Select Ignore criteria to omit this filter. To lists or exclude job stream instances based on whether they contain jobs selected for monitoring by Tivoli Business Systems Manager. Select Ignore criteria to omit this filter. 142 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

169 Creating plan lists Table 62. Properties - Job Stream Instance List information (continued) In this area... Specify... Hours, Minutes The start time of the most critical job. If the job stream has no critical job, the field is blank. Status Status All the job stream instances with any of the following job scheduling console status codes that you specify in the drop-down list: v Waiting v Running v Successful v Error v Canceled Internal Status All the job stream instances with any of the following status codes that you specify in the drop-down list: v Complete v Deleted v Error v Pending predecessor v Started v Undecided v Waiting Note: Status and internal status exclude each other as filter criteria. However, they are both displayed among the properties of job stream instances. Internal status refers to the status code assigned by the specific job scheduling engine. It generally provides more detail than the broader status code assigned by the Job Scheduling Console. Use the Column Definition tab to define the columns displayed in the list. Creating a job instance list for distributed engines The Properties - Job Instance List panel is displayed. General tab Table 63 defines the information necessary to create the job instance list. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the job instances defined in the plan are displayed when you open the list. Table 63. Properties - Job Instance List General information In this area... Specify... Information Name A name for the list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Chapter 21. Creating lists 143

170 Creating plan lists Table 63. Properties - Job Instance List General information (continued) In this area... Specify... Job Name A job name. Job Stream A job stream. Workstation (Job Stream) A workstation name. Login A login name. Status Status One or more states to filter which job instances are to be listed. Only job instances that are in the specified states are displayed. Internal Status This filter can be used as the previous one. The difference between the two is: Always Show Rerun Instances Recovery Options Stop, Continue, Rerun, None Priority Status Is the state of a job instance as interpreted by the Job Scheduling Console. Internal Is the state of a job instance according to a legacy of Tivoli Workload Scheduler values. The two filters are mutually exclusive. That rerun instances are included in the list, regardless of the status you specified in Status. For example: 1. You specified that only job instances in the successful status be listed. 2. You also selected this check box. 3. A job was rerun that was previously in a status other than successful. 4. Because this option was selected, and because the job was rerun one or more times, all the instances of this job, whatever their status might be, are displayed in the list. 5. If the option had not been selected, only the latest successful instances would have been listed. Notes: 1. This option is significant only if you also specified a status for Status. 2. It makes no difference if the job status is the same as the rerun status. To display job instances that match the specified recovery option. Selecting None excludes recovery options as filtering criteria. From, To A priority range of job instances to display. Only jobs with priorities within the range are displayed. Possible priority values are 0 through 101, where 101 is the highest priority. Click Hold to select priority 0, High to select priority 100, or Go to select priority IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

171 Time Restrictions tab Table 64 defines the information necessary to filter on time restrictions. Table 64. Properties - Job Instance List Time Restrictions information In this area... Specify... Start Time From date The beginning of a range of time. Only jobs that start running within this range are displayed. To Date The end of a range of time. Only jobs that start running within this range are displayed. Latest Start Time From Date The beginning of a range of time. Only jobs that start running within this range are displayed. To Date The end of a range of time. Only jobs that start running within this range are displayed. Action The action to be performed in case the job does not start before Latest Start Time. Finish Time Creating plan lists Suppress The job does not start, even if the error condition that prevented it from starting is corrected, and dependencies are not released. Suppress is the default. Continue The job starts when the error condition that prevented it from starting is corrected. Cancel The job is canceled and dependencies are released. From Date The beginning of a range of time. Only jobs that finish running within this range are displayed. To Date The end of a range of time. Only job streams that finish running within this range are displayed. Dependencies tab Use this tab to define a list of jobs from the plan based on dependency types. Only job instances with the specified dependencies are displayed. Note that all the fields in this window act as filters, so that all fields specified must be valid for a job stream to be chosen for display. For example, to display all jobs with a file dependency, enter an asterisk (*) in the File Dependency / File Name field. To display all jobs with both a file and a prompt dependency, enter an asterisk (*) in the File Dependency / File Name field and in the Prompt Dependency / Prompt Name field. Note: In this case, only jobs with both a file and a prompt dependency are displayed. Job instances with only prompt dependencies or only file dependencies are not displayed. Chapter 21. Creating lists 145

172 Creating plan lists Table 65 defines the information necessary to filter on dependencies. Table 65. Properties - Job Instance List Dependency information In this area... Specify... Job/Job Stream Dependency Workstation The name of a workstation. Job Stream The name of a job stream. Job The name of a job. Resource Dependency Workstation The name of a workstation. Name The name of a resource. File Dependency Workstation The name of a workstation. File Name The name of a file. Prompt Dependency Name The name of a prompt. Prompt Number The number of a prompt. Use the Column Definition tab to define the columns displayed in the list. Creating job instance list for z/os engines The Properties - Job Instance List panel is displayed. Table 66 defines the information necessary to create the job instance list. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the job instances defined in the database are displayed when you open the list. Table 66. Properties - Job Instance List information In this area... Specify... Information Name A name for the list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Job stream All the job instances that are in the job stream with this name or name string. Job identifier All the job instances that have this identifier. You cannot use wildcard characters with this filter. Task name All the job instances that are associated with this task or JCL. Extended task name All the job instances that use a specific extended task name or name string. 146 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

173 Creating plan lists Table 66. Properties - Job Instance List information (continued) In this area... Specify... Workstation All the job instances run on this workstation. Owner All the job instances that belong to this owner. Authority group All the job instances that use this authority group for RACF authority checking. Dates From, To All job instances scheduled to run in an interval period starting on the day and time specified in the Date and Time fields and ending in the day and time specified in the Date and Time fields. Pop-up calendars are provided to help you select the days. Priority From, To All the job instances that have the priority level you select. Contains Monitored Job v Yes v No v Ignore criteria Restart Option To List or exclude job instances monitored by Tivoli Business Systems Manager. Select Ignore criteria to omit this filter. CleanUp Type The following cleanup and restart specifications: None Immediate Automatic Manual CleanUp Status All the job instances with either a Completed or Error cleanup state. Status Status All the job instances with any of the following job scheduling console status codes that you specify in the drop-down list: v Waiting v Ready v Running v Successful v Error v Canceled v Held v Undecided v Blocked Internal Status All the job instances with any of the following status codes that you specify in the drop-down list: v Arriving v Ready v Started v Complete v Deleted v Interrupted v Ready-non reporting workstation v Error v Waiting v Undecided WLM Policy Chapter 21. Creating lists 147

174 Creating plan lists Table 66. Properties - Job Instance List information (continued) In this area... Specify... Critical job All the job instances defined as critical jobs. WLM policy All the job instances defined as critical jobs and for which the WLM policy you indicate here was defined. Click the arrow and select one of the available policies. Note: Status and internal status exclude each other as filter criteria. However, they are both displayed among the properties of job instances. Internal status refers to the status code assigned by the specific job scheduling engine. It generally provides more detail than the broader status code assigned by the Job Scheduling Console. Use the Column Definition tab to define the columns displayed in the list. Creating a list of workstations You can create workstation lists for both the distributed and the z/os environments. The Properties - Plan Workstation List panel is displayed. Table 47 on page 133 and Table 48 on page 133 define the information necessary to create the workstation list. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the workstations defined in the database are displayed when you open the list. The workstation list for distributed engines in the plan has the following additional field: Domain Name Lists workstations belonging to domains with this name or name string. Use the Column Definition tab to define the columns displayed in the list. Creating a list of resources You can create resource lists for both the distributed and the z/os environments. The Properties - Database Resource List window is displayed. Table 49 on page 134 and Table 50 on page 134 define the information necessary to create a resource list. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the resources defined in the database are displayed when you open the list. Creating a list of files You can create files lists for distributed engines only. The Properties - Database File List panel is displayed. Table 67 on page 149 defines the information necessary to create a file list. Specify any of the available search parameters or combinations of two or more parameters.if you leave all fields blank, all the resources defined in the database are displayed when you open the list. 148 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

175 Creating plan lists Table 67. Properties - File List information In this area... Specify... Information Name A name for the file list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Filename Files with this name or name string. Creating a list of prompts You can create prompt lists for distributed engines only. The Properties - Database Prompts List panel is displayed. Table 68 defines the information necessary to create a prompt list. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the resources defined in the database are displayed when you open the list. Table 68. Properties - Prompt List Information In this area... Specify... Information Name A name for the file list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Prompt Name Files with this name or name string. Status Asked Whether the prompt has already been asked. Not Asked Whether the prompt has not yet been asked. Answered Yes Whether the prompt has been answered positively. Answered No Whether the prompt has been answered negatively. Creating a list of domain states You can create domain status lists for distributed engines only. The Properties - Database Domain Status List panel is displayed. Chapter 21. Creating lists 149

176 Creating plan lists Table 69 defines the information necessary to create a prompt list. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the resources defined in the database are displayed when you open the list. Table 69. Properties - Domain Status List information In this area... Specify... Information Name A name for the file list. Maximum supported length for this field is 80 characters. Periodic Refresh Options Periodic Refresh An automatic refresh interval in seconds. Period (Secs) A refresh interval in seconds. Apply Defaults The defaults specified in the scheduler Properties pane are applied. Filter Criteria Domain Name Domains with this name or name string. Creating a group of lists The Job Scheduling Console allows you to organize your lists into groups. You can organize your groups of lists by any criteria that help you to quickly display the objects that you want to work with. For example, you can create a group gathering lists that enable you to work with all the objects associated with a particular plan. First you must create a group, then you can create the lists that comprise it. You can create a group of lists within an engine or within the default lists available for each engine. To create a group of lists, perform the following steps: 1. In the Work with engines panel, right-click on the scheduler engine switch and select Create Group. The Properties - Group of Lists panel is displayed. 2. Enter a name for the group. You can use the same name for more than one group. Different groups maintain their individual properties even if they have the same name. The maximum supported length for this field is 80 characters. 3. Create the lists contained in the group as described inchapter 21, Creating lists, on page 129. Creating default common plan lists This section describes how you create default common plan lists. Creating a common list of job stream instances To create a common job stream instance list, perform the following steps: 1. In the Work with engines pane, right-click Common Default Plan Lists and select Job Stream Instance. 2. The Properties - Job Stream Instance Common List panel is displayed. The fields in this dialog are a subset of the fields available in Properties - Job Stream Instance List described in Creating a job stream instance list for z/os engines on page 141. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the common job stream instances are displayed when you open the list. Use the 150 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

177 Creating default plan lists Engine pull-down menu to specify which engines are used when creating the list. By default, all the engines to which the JJob Scheduling Console is connected are selected. Use the Column Definition tab to define the columns displayed in the list. Creating a common list of job instances To create a common job instance list, perform the following steps: Setting list properties 1. In the Work with engines pane, right-click Common Default Plan Lists and select Job Instance. 2. The Properties - Job Instance Common List panel is displayed. The fields in this dialog are a subset of the fields available in Properties - Job Instance List described in Creating job instance list for z/os engines on page 146. Specify any of the available search parameters or combinations of two or more parameters. If you leave all fields blank, all the common job stream instances are displayed when you open the list. Use the Engine pull-down menu to specify which engines are used when creating the list. By default, all the engines to which the Job Scheduling Console is connected are selected. Use the Column Definition tab to define the columns displayed in the list. You can use the Properties panel for each scheduler engine to set or change the defaults for lists. To do this: 1. In the Work with engines pane, right-click a scheduler engine and select Properties in the pop-up menu. The Properties panel is displayed. 2. Open the Settings tab and make your adjustments. Periodic refresh Type the number of seconds after which a list display will refresh. After you do this, this information is used every time you click Apply defaults in the properties window of a list. This information is also automatically displayed in editable form in the Periodic Refresh Options group of the properties window of each new list you create. Buffer size for lists Select a value from the drop-down list. The value determines at which rate the results of a list are sent onto your screen. For example, if you select 100, the results of a list are sent in blocks of 100 lines. The default value is 250. If you select a higher number, it takes more time to display the list initially, but less time to display the entire list when it is scrolled. The highest supported value is 400. Select Engine Time Zone Specify the time of the engine time zone displayed in the Submit Job Stream panel in the Start and Deadline sections. This check box is not selected, by default, and this means that if the engine is in a time zone different from yours, and you start a submission at a certain time, the engine will perform the submission at the time indicated in the Engine Time Zone box, no matter what is the time at your location. If the Select Engine Time Zone check box is selected, the time you will see in the Start and Deadline sections is referred to that of the engine that starts the operation, and the job stream submission will be performed at the selected time. This is valid only if no run cycle is active on the engine. Chapter 21. Creating lists 151

178 Setting list properties The value of the engine time zone can be verified in the Scheduler Information tab in the format GMT +/ n, where n is the number of offset hours from GMT. Note: To see the Engine Time Zone check box in the Settings page and the Engine Time Zone and Code Page values in the Scheduler Information tab properly, you must have the Job Scheduling Console Version 1.3 Fix Pack 2 or later installed, as well as the Tivoli Workload Scheduler for z/os Connector Version 1.3 Fix Pack 2 or later. Further, the z/os engine must have the required UQ79631 PTF applied. 152 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

179 Part 5. Managing database objects Chapter 22. Working with object lists Displaying a list of objects Detaching a list display Modifying a list Deleting a list Chapter 23. Managing workstations Viewing and modifying workstation properties Deleting workstations Chapter 24. Managing job streams Editing job streams using the job stream editor Deleting external dependencies from 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 Deleting an external job stream in a job stream 162 Modifying an external job in a job stream Deleting an external job in a job stream Modifying run cycles for a job stream Deleting run cycles from a job stream Modifying z/os job streams Adding and modifying jobs and dependencies in the graph view Modifying a job Deleting a job or external job Editing another job stream from an external job Removing a dependency between jobs Adding and modifying run cycles Viewing and modifying time restrictions Using the copy function to add an external job 165 Checking time restrictions in the Timeline View 165 Activity bars Table frame Time restrictions Other tasks Deleting job streams Using existing definitions to create other job definitions Chapter 27. Managing workstation classes Displaying and modifying workstation class properties Deleting workstation classes Chapter 28. Managing domains Displaying and modifying domain properties Deleting domains in the database Chapter 29. Managing Windows users Displaying and modifying Windows user properties Changing Windows user passwords Deleting Windows users Chapter 30. Managing calendars Displaying and modifying calendar properties Deleting calendars Chapter 31. Managing prompts Displaying and modifying prompt properties Deleting prompts Chapter 32. Managing parameters Displaying and modifying parameter properties 185 Deleting parameters Chapter 25. Managing resources Displaying resource properties Modifying a resource Deleting a resource Chapter 26. Managing job definitions Displaying a job definition Displaying job definition details Modifying a job definition Deleting job definitions Copyright IBM Corp. 1991,

180 154 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

181 Chapter 22. Working with object lists This chapter describes how you maintain lists. The methods described apply to all list types: v v Database Plan Displaying a list of objects v Default Most of your monitoring activities require a list of objects from which you can work. Creating lists is described in Chapter 21, Creating lists, on page 129. To display a list: 1. In the Work with engines pane, select the engine. 2. Click the list you want to run. The list results are displayed in the right-hand pane. You can display several lists in sequence. The newest list is displayed first. However, as long as a list is kept open, it is maintained and refreshed according to the refresh options specified. To view the list, click the corresponding object in the Job Scheduling Console, or click the button on the task bar that is displayed when a list is run. The properties of lists are described in Chapter 21, Creating lists, on page 129. Copyright IBM Corp. 1991,

182 Displaying a List When you display a list of All scheduled jobs, or All scheduled job streams for z/os or distributed engines (not common lists) a tree view pane is also present. Detaching a list display Modifying a list Detaching a list frees the right-pane of the Job Scheduling Console to display other objects. You can detach multiple lists to view several objects simultaneously. To detach a database list display: 1. Select a list and wait for the results to be displayed. 2. Select Detach Task in the upper right-corner of the panel. The list panel is displayed separately from the main window. 3. To reattach the list, either close the detached window or select Attach Task in the upper right-corner of the detached pane. Notes: 1. The right-hand pane of the console is not disabled. This is so that you can run other lists or perform other tasks. 2. To prevent your system from overloading, do not have frequent refreshes of many detached panes open at the same time. To modify the properties of a list: 1. In the Work with engines pane, select the engine. 2. Right-click the list you want to modify and select Properties. 156 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

183 Modifying a list 3. The properties panel of the list is displayed. 4. Make your changes. The properties of lists are described in Chapter 21, Creating lists, on page 129. Deleting a list To delete a list: 1. In the Work with engines pane, right-click on a list. 2. Select Delete from the pop-up menu. A confirmation message is displayed. 3. Click Yes to delete the list, or click Cancel to cancel the delete operation. Chapter 22. Working with object lists 157

184 Deleting a list 158 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

185 Chapter 23. Managing workstations After you have created the workstations, create one or more workstation lists to manage them. See Chapter 21, Creating lists, on page 129. In order to manage workstations, you must display them in the relevant list. In the database, you can use workstation lists to: v Viewing and modifying workstation properties v Deleting workstations Viewing and modifying workstation properties To display workstation properties in the database, perform the following steps: 1. Run a list of workstations that contains the workstation you want to display. See Chapter 22, Working with object lists, on page 155 for more information. 2. In the list results, double-click the workstation you want to display, or right-click the workstation and select Properties. The Properties - Workstation in Database panel is displayed. For information about this panel, see Creating a z/os workstation on page 53 and Creating a distributed workstation on page Make any changes required and click OK. Deleting workstations To delete a workstation from the database, perform the following steps: 1. Run a list of workstations that contains the workstation you want to delete. See Chapter 22, Working with object lists, on page 155 for more information. 2. In the list results, select the workstation you want to delete and right-click. 3. Select Delete from the pop-up menu. 4. Click Yes to confirm deletion of the workstation you selected. Copyright IBM Corp. 1991,

186 Deleting workstations 160 IBM Tivoli Workload Scheduler Job Scheduling Console User s Guide

187 Chapter 24. Managing job streams This chapter describes how you manage job streams for z/os and distributed engines. Editing job streams using the job stream editor You can use the job stream editor to modify 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, and jobs in other Tivoli Workload Scheduler networks (internetwork jobs). These external dependencies are also called predecessors. To delete external dependencies for a job stream, perform the following steps: 1. Run a list that contains the job stream that you want to modify. See Chapter 22, Working with object lists, on page Double-click the job stream you want to modify. The Job Stream Editor is displayed. 3. Select External Dependencies from the File menu. This displays the Job Stream External Dependencies window. 4. Select External Job Stream, Internetwork, or External Job from the drop-down menu. 5. Click the row of the dependency in the list you want to delete and clickdelete Row. Modifying a job in a job stream To modify a job in a job stream, right-click the job icon in the Graph view and select Properties from the pop-up menu. For information about job properties, see Specifying job properties on page 107. Copyright IBM Corp. 1991,