ibm tivoli workload scheduling suitepublib.boulder.ibm.com/tividd/td/tws/sc32-1256-00/en_us/... ·...

72
IBM Tivoli Workload Scheduling Suite General Information Version 8.2 SC32-1256-00

Upload: others

Post on 05-Jun-2020

12 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

IBM Tivoli WorkloadScheduling Suite

General InformationVersion 8.2

SC32-1256-00

���

Page 2: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version
Page 3: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

IBM Tivoli WorkloadScheduling Suite

General InformationVersion 8.2

SC32-1256-00

���

Page 4: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

NoteBefore using this information and the product it supports, read the information in ″Notices″ on page x..“Notices” onpage 49.

First Edition (June 2003)

This edition applies to version 8, release 2 of IBM Tivoli Workload Scheduling Suite (product numbers 5697-WSZ,5698-WSH, and 5698-WSE) and to all subsequent releases and modifications until otherwise indicated in neweditions.

© Copyright International Business Machines Corporation 1991, 2003. All rights reserved.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Page 5: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Contents

Figures . . . . . . . . . . . . . . . v

Preface . . . . . . . . . . . . . . viiWho Should Read This Manual . . . . . . . viiPublications . . . . . . . . . . . . . . vii

Publications for Tivoli Workload Scheduler forz/OS . . . . . . . . . . . . . . . viiPublications for Tivoli Workload Scheduler . . viiiUsing LookAt to Look Up Message Explanations ixAccessing Publications Online . . . . . . . ixSoftcopy Collection Kit. . . . . . . . . . ixOrdering Publications . . . . . . . . . . xProviding Feedback about Publications . . . . x

Accessibility . . . . . . . . . . . . . . xContacting IBM Software Support . . . . . . . xConventions Used in This Manual . . . . . . . xiSummary of Enhancements . . . . . . . . . xii

Enhancements to Tivoli Workload Scheduler forz/OS . . . . . . . . . . . . . . . xii

z/OS Functions . . . . . . . . . . . xiiMulti-Protocol Server and Sysplex. . . . . xiiTivoli Workload Scheduler End-to-end . . . xii

Enhancements to Tivoli Workload Scheduler . . xiiiWizard-guided Installation Process . . . . xiiiSecure Authentication and Encryption . . . xiiiWork Across Firewalls . . . . . . . . xivCentralized Security Mechanism . . . . . xivData Warehousing . . . . . . . . . . xivJob Return Code Mapping . . . . . . . xivExtended Autotrace Feature . . . . . . . xvEnhanced Time Zone Support . . . . . . xvNew Options for Handling Time Constraints xvEvent State Management . . . . . . . . xv

Enhancements to the Job Scheduling Console xviLate Jobs Handling . . . . . . . . . xviReturn Code Mapping . . . . . . . . xviFirewall Support . . . . . . . . . . xviExplorer Viewer . . . . . . . . . . xviHyperbolic Viewer. . . . . . . . . . xvi

Chapter 1. Overview of the WorkloadScheduler Suite . . . . . . . . . . . 1The State-of-the-art Solution . . . . . . . . . 1

Comprehensive Workload Planning. . . . . . 2Centralized Systems Management . . . . . . 2Systems Management Integration . . . . . . 2Automation. . . . . . . . . . . . . . 4Workload Monitoring . . . . . . . . . . 4Automatic Workload Recovery . . . . . . . 5Productivity . . . . . . . . . . . . . 5

Business Solutions . . . . . . . . . . . . 5User Productivity . . . . . . . . . . . . . 5Growth Enabling . . . . . . . . . . . . . 5Who Uses the Workload Scheduler Suite . . . . . 6

Role of the Scheduling Manager—The Focal Point 6

Role of the Operations Manager . . . . . . . 6A Powerful Tool for the Shift Supervisor . . . . 7Role of the Application Programmer . . . . . 7Console Operators . . . . . . . . . . . 7Workstation Operators . . . . . . . . . . 7End Users and the Help Desk . . . . . . . 7

Summary . . . . . . . . . . . . . . . 8

Chapter 2. Tivoli Workload Scheduler . . 9Overview . . . . . . . . . . . . . . . 9

What is Tivoli Workload Scheduler . . . . . . 9The Tivoli Workload Scheduler Network . . . . 9Manager and Agent Types . . . . . . . . 11Topology . . . . . . . . . . . . . . 12Networking . . . . . . . . . . . . . 12Tivoli Workload Scheduler Components . . . . 13Tivoli Workload Scheduler Scheduling Objects. . 14The Production Process . . . . . . . . . 15

Scheduling . . . . . . . . . . . . . . 16Defining Scheduling Objects . . . . . . . . 16Creating Job Streams . . . . . . . . . . 16Setting Job Recovery . . . . . . . . . . 16

Running Production . . . . . . . . . . . 17Start-of-day Processing . . . . . . . . . 17Running Job Streams . . . . . . . . . . 17Monitoring . . . . . . . . . . . . . 18Reporting . . . . . . . . . . . . . . 18Auditing . . . . . . . . . . . . . . 19

Options and Security . . . . . . . . . . . 19Setting Global and Local Options . . . . . . 19Setting Security . . . . . . . . . . . . 20

Secure Authentication and Encryption . . . 20Work Across Firewalls . . . . . . . . . 20Centralized Security Mechanism . . . . . 21

Using Time Zones . . . . . . . . . . . 21Using Extended Agents . . . . . . . . . . 21

Chapter 3. Tivoli Workload Schedulerfor z/OS . . . . . . . . . . . . . . 23How Your Production Workload Is Managed . . . 23

Structure . . . . . . . . . . . . . . 23Concepts . . . . . . . . . . . . . . 23Plans in Tivoli Workload Scheduler for z/OS . . 26

Long-term Planning . . . . . . . . . 26Detailed Planning . . . . . . . . . . 26

Automatically Controlling the ProductionWorkload . . . . . . . . . . . . . . 27

Automatic Workload Submission . . . . . 28Automatic Recovery and Restart . . . . . 28z/OS Automatic Restart Manager Support . . 30Workload Manager (WLM) Support . . . . 30Automatic Status Checking . . . . . . . 30Status Reporting from HeterogeneousEnvironments. . . . . . . . . . . . 31Status Reporting from User Programs . . . 31

© Copyright IBM Corp. 1991, 2003 iii

|||||||||||||||||||||

|||||||||||||||||||||||||||||||||||||||||||||

Page 6: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Additional Job-completion Checking . . . . 31Managing Unplanned Work . . . . . . . 31

Interfacing with Other Programs . . . . . . 31Manual Control and Intervention . . . . . . 31

Status Inquiries . . . . . . . . . . . 32Modifying the Current Plan . . . . . . . 32

Management of Critical Jobs . . . . . . . . 33Security . . . . . . . . . . . . . . 33

Audit Trail . . . . . . . . . . . . 33System Authorization Facility . . . . . . 34

Protection of Data and Resources . . . . 34Data Integrity During Submission . . . . 34

Configurations of Tivoli Workload Scheduler forz/OS . . . . . . . . . . . . . . . . 34

The Controlling System . . . . . . . . . 34Controlled z/OS Systems . . . . . . . . . 35

Remote Systems . . . . . . . . . . . 35Remote Panels and Program InterfaceApplications . . . . . . . . . . . . . 36Scheduling Jobs That Are in Tivoli WorkloadScheduler . . . . . . . . . . . . . . 36

Chapter 4. Tivoli Job SchedulingConsole . . . . . . . . . . . . . . 37Overview . . . . . . . . . . . . . . . 37Tivoli Workload Scheduler for z/OS Tasks . . . . 38

Scheduler Tasks . . . . . . . . . . . . 38Working with Job Streams . . . . . . . 38Working with Jobs . . . . . . . . . . 38Working with Workstations . . . . . . . 39Working with Resources . . . . . . . . 39

Operator Tasks . . . . . . . . . . . . 39Working with Job Stream Instances . . . . 39Working with Job Instances . . . . . . . 39Working with Workstations in the Plan . . . 40

Working with Resources in the Plan . . . . 40Tivoli Workload Scheduler Tasks . . . . . . . 40

Scheduler Tasks . . . . . . . . . . . . 40Working with Job Streams . . . . . . . 41Working with Jobs . . . . . . . . . . 41Working with Calendars . . . . . . . . 41Working with Prompts . . . . . . . . 41Working with Parameters. . . . . . . . 41Working with Domains . . . . . . . . 42Working with Workstations . . . . . . . 42Working with Workstation Classes. . . . . 42Working with Resources . . . . . . . . 42Working with Users . . . . . . . . . 42

Operator Tasks . . . . . . . . . . . . 43Working with Job Stream Instances . . . . 43Working with Job Instances . . . . . . . 43Working with Workstations . . . . . . . 43Working with Domains . . . . . . . . 44Working with File Dependencies . . . . . 44Working with Prompt Dependencies . . . . 44Working with Resource Dependencies . . . 44

Common Tasks . . . . . . . . . . . . . 44

Chapter 5. End-to-end Scheduling . . . 45How End-to-end Scheduling Works . . . . . . 45Distributed Agents . . . . . . . . . . . . 46Supported End-to-end Configurations . . . . . 47Benefits of End-to-end scheduling . . . . . . . 47

Notices . . . . . . . . . . . . . . 49Trademarks . . . . . . . . . . . . . . 50

Index . . . . . . . . . . . . . . . 51

iv General Information

||

Page 7: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Figures

1. This Tivoli Workload Scheduler network ismade up by two domains. . . . . . . . 10

2. How Extended Agents Work. . . . . . . 223. Automatic Recovery and Restart . . . . . 294. Production Workload Restart and Hot Standby 30

5. Security . . . . . . . . . . . . . . 336. Tivoli Workload Scheduler for z/OS

Configurations . . . . . . . . . . . 357. End-to-end configuration . . . . . . . . 46

© Copyright IBM Corp. 1991, 2003 v

|||||

Page 8: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

vi General Information

Page 9: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Preface

This book describes the suite of Tivoli®®

Workload Scheduler 8.2 and its enterpriseworkload management functions. This book provides introductory informationabout Tivoli Workload Scheduler, Tivoli Workload Scheduler for z/OS™, and theTivoli Job Scheduling Console for all users. It does not provide detailed technicalexplanations about how it works. This book describes:v The structure of the productv Where it fits in single-host and multiple-host systemsv Major functionsv How it works with other products

Who Should Read This ManualThis book is intended for:v Data processing (DP) operations managers and their technical advisors who are

evaluating the product or planning their scheduling servicev Individuals who require general information for evaluating, installing, or using

the product

PublicationsThis section lists publications in the Tivoli Workload Scheduler for z/OS library andany other related documents. It also describes how to access Tivoli publicationsonline, how to order Tivoli publications, and how to make comments on Tivolipublications.

Publications for Tivoli Workload Scheduler for z/OSThe following documents are available in the Tivoli Workload Scheduler for z/OSlibrary:v Customization and Tuning, SC32-1265

Describes how to customize Tivoli Workload Scheduler for z/OS.v Installation Guide, SC32-1264

Describes how to install Tivoli Workload Scheduler for z/OS.v Diagnosis Guide and Reference, SC32-1261

Provides information to help diagnose and correct possible problems when usingthe product.

v General Information, SC32-1256Describes the benefits of the entire Tivoli Workload Scheduler suite.

v Getting Started, SC32-1262Describes concepts and terminology of Tivoli Workload Scheduler for z/OS andprovides instructions to get you working with the product as soon as possible.

v Tivoli Job Scheduling Console Release Notes, SC32-1258Provides information about working with Tivoli Workload Scheduler, regardlessof platform, from a common GUI.

v Tivoli Job Scheduling Console User’s Guide, SC32-1257

© Copyright IBM Corp. 1991, 2003 vii

|

||||

|

||

|

|

|

|

|

||

|

|

|

||

|

||

|

Page 10: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Provides information about working with Tivoli Workload Scheduler, regardlessof platform, from a common GUI.

v License Program Specifications, GI11-4208Provides planning information to plan about Tivoli Workload Scheduler forz/OS.

v Managing the Workload, SC32-1263Explains how to plan and schedule the workload and how to control andmonitor the current plan.

v Memo to Users, GI11-4209Provides a summary of changes for the current release of the product.

v Messages and Codes, SC32-1267Explains messages and codes.

v Program Directory, GI11-4203Provided with the Tivoli Workload Scheduler for z/OS installation tape,describes all of the installation materials and gives installation instructionsspecific to the product release level or feature number.

v Programming Interfaces, SC32-1266Provides information to write application programs.

v Quick Reference, SC32-1268Provides a quick and easy consultation reference to operate the product.

Publications for Tivoli Workload SchedulerThe following manuals are available in the Tivoli Workload Scheduler library:v Tivoli Workload Scheduler Planning and Installation Guide, SC32-1273

Describes planning and installing Tivoli Workload Scheduler.v Tivoli Workload Scheduler Reference Guide, SC32-1274

Explains the Tivoli Workload Scheduler command line, understanding howextended and network agents work, and integrating Tivoli Workload Schedulerwith NetView® and with Tivoli Business Systems Manager.

v Tivoli Workload Scheduler Troubleshooting and Error Messages, SC32-1275Interprets Tivoli Workload Scheduler error messages, and provides sources ofinformation that will help you in solving problems with Tivoli WorkloadScheduler.

v Tivoli Workload Scheduler for Applications User’s Guide, SC32-1278Describes installing, using, and troubleshooting for the Tivoli WorkloadScheduler extended agents.

v Tivoli Workload Scheduler for Applications Release Notes, SC32-1279Provides last-minute information about the Tivoli Workload Scheduler extendedagents.

v Tivoli Workload Scheduler AS/400® Limited FTA User’s Guide, SC32-1280Describes installing, configuring, and using Tivoli Workload Schedulerfault-tolerant agents on AS/400.

v Tivoli Workload Scheduler Plus Module User’s Guide, SC32-1276Explains setting up and using the Tivoli Workload Scheduler Plus module.

v Tivoli Workload Scheduler Release Notes, SC32-1277Explains late-breaking information about Tivoli Workload Scheduler.

viii General Information

||

|

||

|

||

|

|

|

|

|

|||

|

|

|

|

|

|

|

|

|

|||

|

|||

|

||

|

||

|

||

|

|

|

|

Page 11: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Using LookAt to Look Up Message ExplanationsLookAt is an online facility that lets you look up explanations for most messagesyou encounter, as well as for some system abends and codes. Using LookAt to findinformation is faster than a conventional search because in most cases LookAt goesdirectly to the message explanation.

You can access LookAt from the Internet at:http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/ or from anywhere inz/OS or z/OS.e where you can access a TSO/E command line (for example,TSO/E prompt, ISPF, z/OS UNIX System Services running OMVS).

The LookAt Web site also features a mobile edition of LookAt for devices such asPocket PCs, Palm OS, or Linux-based handhelds. So, if you have a handhelddevice with wireless access and an Internet browser, you can now access LookAtmessage information from almost anywhere.

To use LookAt as a TSO/E command, you must have LookAt installed on yourhost system. You can obtain the LookAt code for TSO/E from a disk on your(SK3T-4270) or from the LookAt Web site’s Download link.

Accessing Publications OnlineThe product CD contains the publications that are in the product library. Theformat of the publications is PDF, HTML, or both. To access the publications usinga Web browser, open the infocenter.html file. The file is in the appropriatepublications directory on the product CD.

IBM posts publications for this and all other Tivoli products, as they becomeavailable and whenever they are updated, to the Tivoli Software InformationCenter Web site. The Tivoli Software Information Center is located at the followingWeb address:

http://publib.boulder.ibm.com/tividd/td/tdprodlist.html

Click the Tivoli Workload Scheduler for z/OS link to access the product library.

Note: If you print PDF documents on other than letter-sized paper, select the Fit topage check box in the Adobe Acrobat Print dialog. This option is availablewhen you click File → Print. Fit to page ensures that the full dimensions of aletter-sized page print on the paper that you are using.

Softcopy Collection KitAll the books in the library, except the licensed publications, are available indisplayable softcopy form on CD-ROM in the OS/390®, SK2T-6951 SoftcopyCollection Kit.

You can read the softcopy books on CD-ROMs using these IBM® licensedprograms:v BookManager® READ/2v BookManager READ/DOSv BookManager READ/6000

All the BookManager programs need a personal computer equipped with aCD-ROM disk drive (capable of reading disks formatted in the ISO 9660 standard)

Preface ix

|

||||

||||

||||

|||

|

||||

||||

|

|

||||

|

|||

|||||

||

Page 12: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

and a matching adapter and cable. For additional hardware and softwareinformation, refer to the documentation for the specific BookManager product youare using.

Updates to books between releases are provided in softcopy only.

Ordering PublicationsYou can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

You can also order by telephone by calling one of these numbers:v In the United States: 800-879-2755v In Canada: 800-426-4968

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

http://www.ibm.com/software/tivoli/order-lit/

Providing Feedback about PublicationsIf you have comments or suggestions about Tivoli products and documentation,complete the customer feedback survey at the following Web site:

http://www.ibm.com/software/sysmgmt/products/support

AccessibilityAccessibility features help users with a physical disability, such as restrictedmobility or limited vision, to use software products successfully. With this product,you can use assistive technologies to hear and navigate the interface.You can alsouse the keyboard instead of the mouse to operate all features of the graphical userinterface.

Contacting IBM Software SupportIf you have a problem with any Tivoli product, you can contact IBM SoftwareSupport. See the IBM Software Support Guide at the following Web site:

http://techsupport.services.ibm.com/guides/handbook.html

The guide provides information about how to contact IBM Software Support,depending on the severity of your problem, and the following information:v Registration and eligibilityv Telephone numbers and e-mail addresses, depending on the country in which

you are locatedv Information you must have before contacting IBM Software Support

x General Information

|||

|

|

|

|||

|

|

|

|

|

|

||

|

|

|||||

|

||

|

||

|

||

|

Page 13: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Conventions Used in This ManualThe manual uses several typeface conventions for special terms and actions. Theseconventions have the following meanings:

Information type Style convention Example

Commands All capital letters CREATE

References in the text tofields on panels

All capital letters QUANTITY

Input you should type inpanel fields

Monospace MYAPPLICATION

First time new termintroduced

Italics Application

Preface xi

Page 14: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Summary of EnhancementsThis section describes the enhancements to the following:v Tivoli Workload Scheduler for z/OSv Tivoli Workload Schedulerv Tivoli Job Scheduling Console

Enhancements to Tivoli Workload Scheduler for z/OSThe following sections describe the enhancements to Version 8.2 of Tivoli WorkloadScheduler for z/OS.

z/OS FunctionsThe following list summarizes the changes in this version of z/OS functions:v You can have the local time on a z/OS system change automatically, for

example, for daylight savings time, without having to stop and restart TivoliWorkload Scheduler for z/OS.

v You can turn the JESLOG SPIN option on or off using the SPIN keyword in theOPCOPTS statement. By default Tivoli Worksload Scheduler for z/OS adds theJESLOG=NOSPIN parameter to the JOB card when the following conditionsboth occur:– You submit a JCL on a CPU running z/OS Version 1.2 or higher.– In the OPCOPTS initialization statement, you specify data store or job

completion checker activities.v To facilitate migration from other scheduling products, Tivoli Workload

Scheduler for z/OS operations now accept a new symbolic name that can be upto 54 characters long. This operation extended name enables you to represent thejob with something other than the operation number. You can specify theoperation extended name when you define an operation in the database or whenyou copy it into the current plan. You can also use it to filter queries onoperations in the database and current plan.

v You can use a mixed connection (SNA and XCF) between the controller andallocated data stores.

v A new exit routine, EQQUXPIF, validates changes in an application description(AD) made using the programming interface (PIF), batch loader (BL), and theJob Scheduling Console (JSC).

v To increase the virtual storage from 16MB to 2GB, the Tivoli Workload Schedulerfor z/OS components have been changed to use 31-bit addressing mode insteadof 24-bit.

Multi-Protocol Server and Sysplexv The server can use APPC and TCP/IP in simultaneous connections with the Job

Scheduling Console, PIF, ISPF panels, and distributed agents.v When an application is moved to another system in a sysplex environment, for

example, for maintenance of the current system or for a failure, the applicationcan be reached under the same virtual IP address. Using a dynamic virtual IPaddress makes the end-to-end configuration more flexible, because yourapplication is independent of the TCP/IP stack within the sysplex.

Tivoli Workload Scheduler End-to-endThe following list summarizes the changes in this version of end-to-endscheduling:v For fault-tolerant workstations, you can continue to use centralized scripts,

which are stored in the JOBLIB dataset. With centralized scripts, you can

xii General Information

|

|

|

|

|

|

||

||

|||

|||||||

|||||||

||

|||

|||

|||

|||||

|||

||

Page 15: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

perform variable substitution, automatic recovery, JCL editing, and job setup (asfor the jobs in the JOBLIB). However, this implies a loss of fault tolerance andrequires downloading the script to the agent every time the job is submitted.You need to weigh the benefits and disadvantages of using centralized scripts.

v You can use a new syntax to recover non-centralized jobs on distributed agentsautomatically when the jobs abend. This recovery is similar to the recovery inthe distributed environment.

v You can use variable substitution for jobs that run on fault-tolerant workstationsand that do not use centralized scripts. Tivoli Workload Scheduler for z/OSsupplied-variable and user- defined variable tables are supported.

v You can enable firewall support and SSL authentication in end-to-endscheduling.

v You can specify a success condition for each job that determines whether a job isconsidered successful or abended.

v You can specify or modify the deadline time for a job or a job stream.v There are new log files for netman, batchman, mailman, the writer, and the

translator.v Multiple domain managers can be connected to the controller. This allows

greater flexibility, scalability, and improved performance.v You can make an application or an operation dependent on the existence of one

or more files before it can begin execution.v You can activate and deactivate the submission of jobs scheduled in an

end-to-end environment.v You can enable or disable the auditing trail of a plan.v You can change the status of distributed agents and switch their domain

manager.v You can refresh the content of the work directory.v You can use the ISPF panels to produce an APAR tape that collects end-to-end

data.v You can use the Job Migration Tool to migrate from tracker agents to distributed

agents.

Enhancements to Tivoli Workload SchedulerThe following sections describe the enhancements to Version 8.2 of Tivoli WorkloadScheduler.

Wizard-guided Installation ProcessAn InstallShield wizard for Tier–1 platforms is provided to guide you inperforming the following installation procedures:v Install a new instance of Tivoli Workload Schedulerv Upgrade Tivoli Workload Scheduler from the previous versionv Add a new feature to the existing Tivoli Workload Scheduler installationv Promote an existing installationv Install a patchv Remove or uninstall Tivoli Workload Scheduler or only specified features

Secure Authentication and EncryptionSecurity is enhanced for connections between protected and non-protected domainsby applying the authentication and encryption mechanism based on the SecureSockets Layer (SSL) protocol. SSL uses digital certificates to authenticate theidentity of a workstation.

Preface xiii

||||

|||

|||

||

||

|

||

||

||

||

|

||

|

||

||

|

||

|||

|

|

|

|

|

|

|||||

Page 16: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

The Tivoli Workload Scheduler administrator must plan how authentication will beused within the network:v Use one certificate for the entire Tivoli Workload Scheduler network.v Use a separate certificate for each domain.v Use a separate certificate for each workstation.

SSL support is automatically installed with Tivoli Workload Scheduler, version 8.2.

Work Across FirewallsFor previous versions of Tivoli Workload Scheduler, running the commands to startor stop a workstation or to get the standard list requires opening a direct TCP/IPconnection between the originator and the destination nodes. In a firewallenvironment, this forces users to break the firewall to open a direct communicationpath between the master and each fault-tolerant agent in the network.

Version 8.2 features a new configurable attribute-behindfirewall- in the workstation’sdefinition in the database. You can set this attribute to ON to indicate that afirewall exists between that particular workstation and its domain manager, andthat the link between the domain manager and the workstation (which can beanother domain manager itself) is the only allowed link between the respectivedomains.

Also, for all the workstations having this attribute set to ON, the commands tostart or stop the workstation or to get the standard list will be transmitted throughthe domain hierarchy instead of opening a direct connection between the master(or domain manager) and the workstation.

Centralized Security MechanismA new global option makes it possible to change the security model in the TivoliWorkload Scheduler network. If you use this option, then the security files for thefault-tolerant agents in the network can be created or modified only on the master.The Tivoli Workload Scheduler administrator takes charge of creating, updating,and distributing the security files for all the agents where a user access is required.Setting this global option triggers a security mechanism to identify and trust theTivoli Workload Scheduler network corresponding to that master.

If you prefer the traditional security model, you can still do so by not activatingthe global variable.

Data WarehousingBecause your environment contains many products and services that manage andmonitor your IT enterprise, storing this data, generating reports, and analyzing thedata becomes a complex task. Collecting this data in one place, a central datawarehouse, enables you to construct an end-to-end view of your enterprise andview its components independent of specific applications.

Locate and read the documentation for the warehouse enablement pack. Thedocumentation is located on CD_2 in a PDF file in the subdirectorytedw_apps_etl/aws/pkg/v820/doc.

Job Return Code MappingFormerly, Tivoli Workload Scheduler considered a job to have executed successfullyif it terminated with a return code of zero, and to have failed, if it terminated witha return code different than zero. You can now define a logical expression torepresent which return codes are to be considered successful. The ability to define

xiv General Information

||

|

|

|

|

||||||

||||||

||||

||||||||

||

||||||

|||

|||||

Page 17: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

the job as successful or failed allows more flexibility in controlling the jobexecution flow depending on the result of the job execution.

Extended Autotrace FeatureThis is a built-in flight-recorder-style trace mechanism that logs all activitiesperformed by the IBM Tivoli Workload Scheduler processes. In case of productfailure or unexpected behavior, this feature can be extremely effective in findingthe cause of the problem.

In case of problems, you are asked to create a trace snap file by issuing somesimple commands. The trace snap file is then inspected by the Tivoli support team,which uses the logged information as an efficient problem determination base.

The autotrace feature, already available with version 8.1, has now been extended torun on additional platforms. Refer to Tivoli Workload Scheduler Troubleshooting andError Messages for more information about this feature.

Enhanced Time Zone SupportThis version increases the granularity of the supported time zones. In fact, itconsiders the fact that locations that belong to the same time zone, maynevertheless follow different daylight savings timetables.

New Options for Handling Time ConstraintsJobs and job streams are constrained by the start times and deadlines specified forthem, and also by any dependencies they have on the completion of other jobs orjob streams. To aid you in determining the status of jobs and job streams, thefollowing enhancements have been implemented:v Messages related to job and job stream errors and delays are displayed by the

Job Scheduling GUI and logged to the message log .v A message is issued for jobs and job streams that have reached the start time

specified for them, but cannot start because of pending dependencies on otherjobs or job streams.

v A message is issued when the deadline time is reached for a job or job streamthat has not yet started.

v A query facility enables you to query jobs and job streams using the JobScheduling GUI or command line interface for the following information:– Jobs or job streams whose start times have been reached, but have not yet

started running– Jobs or job streams whose deadlines have been reached, but have not yet

started running– Jobs or job streams whose deadlines have been reached, but have not yet

completed runningv New options enable you to start jobs or job streams whose deadlines have been

reached but have not yet started. In such cases, notifications are sent by issuinga message to Batchman and the console log; and an event is sent to the TivoliEnterprise Console and the Tivoli Business Systems Manager.

Event State ManagementIn this release, new Tivoli Enterprise Console events and rules have beenimplemented related to the new job and job stream time constraint options. Youcan define which jobs are considered key jobs and have events sent to the TivoliEnterprise Console reporting not just the final state, but also intermediate job statesof all key jobs. You can also customize Tivoli Enterprise Console rules toautomatically submit jobs when specific events are received. Refer to the Tivoli

Preface xv

||

|||||

|||

|||

||||

|||||

||

|||

||

||

||

||

||

||||

|||||||

Page 18: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Workload Scheduler Plus Module User’s Guide for information about creating andcustomizing new Tivoli Enterprise Console rules.

Enhancements to the Job Scheduling ConsoleThe Job Scheduling Console Feature Level 1.3 is delivered with the workloadscheduler suite or either of its components. The following sections describe theenhancements to Version 1.3 of Job Scheduling Console.

Late Jobs HandlingJobs and job streams are constrained by the start times and deadlines specified forthem, and also by any dependencies they have on the completion of other jobs orjob streams. To aid you in determining the status of jobs and job streams, thefollowing enhancements have been implemented:v Messages related to job and job stream errors and delays are displayed and

logged to the Tivoli Workload Scheduler message log.v A query facility enables you to query jobs and job streams for the following

information:– Jobs or job streams whose start times have been reached, but have not yet

started– Jobs or job streams whose deadlines have been reached, but have not yet

started– Jobs or job streams whose deadlines have been reached, but have not yet

completed runningv Start jobs or job streams whose deadlines have been reached but have not yet

started.

Return Code MappingYou can now define a logical expression to represent which return codes are to beconsidered successful in the job execution.

Firewall SupportThe Job Scheduling Console provides a secure method for connecting to an IBMTivoli Workload Scheduler engine positioned behind a firewall, using always thespecified TCP/IP ports.

Explorer ViewerThe Explorer Viewer provides an integrated view of job stream instances with theirrelated jobs and dependencies, if any, in a tree view.

Hyperbolic ViewerThe Hyperbolic Viewer displays an integrated view of job stream instances withtheir related jobs and dependencies, if any, in a graphic format. This view is veryuseful for displaying complicated queries which involve many job streaminstances.

xvi General Information

||

|

|||

|||||

||

||

||

||

||

||

|||

||||

|||

|||||

Page 19: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Chapter 1. Overview of the Workload Scheduler Suite

The workload scheduler suite is the state-of-the-art production workload manager,designed to help you meet your present and future data processing challenges. Itsscope encompasses your entire enterprise information system, includingheterogeneous environments.

Pressures on today’s data processing (DP) environment are making it increasinglydifficult to maintain the same level of services to customers. Many installationsfind that their batch window is shrinking. More critical jobs must be finishedbefore the morning online work begins. Conversely, requirements for the integratedavailability of online services during the traditional batch window put pressure onthe resources available for processing the production workload. More and more 7days a week, 24 hours a day is not only a DP objective but a requirement.

Users and owners of DP services are also making more use of batch services thanever before. The batch workload tends to increase each year at a rate slightly belowthe increase in the online workload. Combine this with the increase in data usageby batch jobs, and the end result is a significant increase in the volume of work.

Furthermore, there is a shortage of people with the required skills to operate andmanage increasingly complex DP environments. The complex interrelationshipsbetween production activities—between manual and machine tasks—have becomeunmanageable without a workload management tool.

The workload scheduler suite simplifies systems management acrossheterogeneous environments by integrating systems management functions. Thereare three main components to the suite:v Tivoli Workload Scheduler for z/OS

The scheduler in OS/390 and z/OS environmentsv Tivoli Workload Scheduler

The scheduler in distributed environmentsv Tivoli Job Scheduling Console

The common user interface for both Tivoli Workload Scheduler for z/OS andTivoli Workload Scheduler

The State-of-the-art SolutionThe suite provides leading-edge solutions to problems in production workloadmanagement. It can automate, plan, and control the processing of your enterprise’sentire production workload, not just the batch subset. The suite functions as an“automatic driver” for your production workload to maximize the throughput ofwork, and optimize your resources, but also allows you to intervene manually asrequired.

When the suite interfaces with other system management products, it forms part ofan integrated automation and systems management platform for your DPoperation.

© Copyright IBM Corp. 1991, 2003 1

Page 20: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Comprehensive Workload PlanningThe suite forms operating plans based on user descriptions of the operationsdepartment and its production workload. These plans provide the basis for yourservice level agreements and give you a picture of the production workload at anypoint in time.

Good planning is the cornerstone of any successful management technique.Effective planning also helps you maximize return on your investments ininformation technology.

Centralized Systems ManagementThe suite automates, monitors, and controls the flow of work through yourenterprise’s entire DP operation—on both local and remote systems. From a singlepoint of control, the suite analyzes the status of the production work and drivesthe processing of the workload according to installation business policies. Itsupports a multiple-end-user environment, enabling distributed processing andcontrol across sites and departments within your enterprise.

Systems Management IntegrationSolutions to today’s systems management problems require an integration ofapplication programs and processes. The suite offers you integration with thefollowing:v Agents for controlling the workload on non-z/OS platformsv Other systems management applications and architecture environments.

The suite interfaces directly with some of the z/OS products as well as with anumber of other IBM products to provide a comprehensive, automated processingfacility and an integrated approach for the control of complex productionworkloads.

NetView. The NetView program is the IBM platform for network management andautomation. You can use the interface for Tivoli Workload Scheduler for z/OS withthe NetView program to pass information about the work that is being processed.The suite lets you communicate with the NetView program in conjunction with theproduction workload processing. Tivoli Workload Scheduler for z/OS can also passinformation to the NetView program for alert handling in response to situationsthat occur while processing the production workload. The NetView program canautomatically trigger Tivoli Workload Scheduler for z/OS to perform actions inresponse to these situations using a variety of methods. Tivoli WorkloadScheduler/NetView is a NetView application that gives network managers theability to monitor and diagnose Tivoli Workload Scheduler networks from aNetView management node. It includes a set of submaps and symbols to viewTivoli Workload Scheduler networks topographically and determine the status ofjob scheduling activity and critical Tivoli Workload Scheduler processes on eachworkstation.

Workload Manager (WLM). WLM controls the amount of system resourcesavailable to each work unit in host environments. Tivoli Workload Scheduler forz/OS works in concert with WLM to detect critical jobs and move them to ahigher-performance service class. In addition with WLM, critical jobs receive moresystem resources and complete more quickly.

Resource Object Data Manager (RODM). RODM provides a central location forstoring, retrieving, and managing the operational resource information needed for

2 General Information

Page 21: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

network and systems management. You can map a special resource to a RODMobject. This lets you schedule the production workload considering actual resourceavailability, dynamically updated.

Tivoli Performance Reporter for OS/390 (Performance Reporter). PerformanceReporter helps you effectively manage the performance of your system bycollecting performance data in a DATABASE 2™ (DB2®) database and presentingthe data in a variety of formats for use in systems management. PerformanceReporter uses data from Tivoli Workload Scheduler for z/OS to produce summaryand management reports about the production workload, both planned and actualresults.

Report Management and Distribution System (RMDS). RMDS helps customersincrease productivity and reduce the costs of printing by providing a means forstoring and handling reports in a z/OS environment. When a dialog user requeststo view a job log or to automatically rebuild the JCL for a step-level restart, TivoliWorkload Scheduler for z/OS interfaces with RMDS. This interface removes therequirement to duplicate job log information, saving both CPU cycles and directaccess storage device (DASD) space.

Tivoli Service Desk for OS/390 (TSD/390). TSD/390 supports the administrationof the systems management process of an enterprise’s hardware, software, andrelated resources. An interface with TSD/390 is provided for reporting problemsdetected while processing the production workload.

Resource Access Control Facility (RACF®). RACF is the IBM product for datasecurity. You can use RACF as the primary tool to protect your Tivoli WorkloadScheduler for z/OS services and data at the level required by your enterprise. WithRACF 2.1, you can use a Tivoli Workload Scheduler for z/OS reserved resourceclass to protect your resources.

System Automation for OS/390 (SA/390). SA/390 initiates automation proceduresthat perform operator functions to manage OS/390 components, data sets, andsubsystems. SA/390 includes an automation feature for Tivoli Workload Schedulerfor z/OS.

Data Facility Hierarchical Storage Manager (DFHSM). Tivoli Workload Schedulerfor z/OS catalog management functions invoke DFHSM to recall migrated datasets during data set cleanup for a failed or rerun job.

CICS® and IMS™ (Computer Information Control System and InformationManagement System). Tivoli Workload Scheduler for z/OS lets you schedule thestarting and stopping of started tasks. Because Tivoli Workload Scheduler for z/OStracks the status of started tasks, you can serialize work, such as backups of yourtransaction databases, according to the status of your CICS or IMS subsystems.

Tivoli Business Systems Manager. Tivoli Business Systems Manager providesmonitoring and event management of resources, applications, and subsystems withthe objective of providing continuous availability for the enterprise. Using TivoliBusiness Systems Manager with the suite provides the ability to manage strategicapplications from a unique business systems perspective. Tivoli Business SystemsManager monitors batch-related applications and operations represented by thesuite and seamlessly integrates these objects with all other business objectsmonitored by Tivoli Business Systems Manager.

Chapter 1. Overview 3

Page 22: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Tivoli Enterprise Console®. The Tivoli Enterprise Console is a powerful,rules-based event management application that integrates network, systems,database, and application management. It offers a centralized, global view of yourcomputing enterprise while ensuring the high availability of your application andcomputing resources. Tivoli Enterprise Console acts as a central collection point foralarms and events from a variety of sources, including those from Tivoliapplications. Tivoli Workload Scheduler runs a Tivoli Enterprise Console adapterthat reads events from the Tivoli Workload Scheduler log file.

Besides these IBM products, there are many products from other software vendorsthat work with or process data from the suite.

AutomationBy automating management of your production workload with the suite, you canminimize human errors in production workload processing and free your staff formore productive work. The suite lets you to plan, drive, and control the processingof your production workload—important steps toward automation and unattendedoperations. Whether you are running one or more systems at a single site—or atseveral distributed sites—the suite helps you automate your production workloadby:v Coordinating all shifts and production work across installations of all sizes, from

a single point of controlv Automating complex and repetitive operator tasksv Dynamically modifying your production workload schedule in response to

changes in the production environment (such as urgent jobs, changed priorities,or hardware failures) and then managing the workload accordingly

v Resolving workload dependenciesv Managing utilization of shared resourcesv Tracking each unit of workv Detecting unsuccessful processingv Displaying status information and instructions to guide operations personnel in

their workv Interfacing with other key IBM products to provide an integrated automation

platform

The suite lets you centralize and integrate control of your production workloadand reduces the number of tasks that your staff need to perform.

Workload MonitoringBesides providing a single point of control for the production workload acrossyour systems, the suite:v Monitors the production workload in real time, providing operations staff with

the latest information on the status of the workload so that they can reactquickly when problems occur.

v Provides security interfaces that ensure the protection of your services and data.v Enables manual intervention in the processing of work.v Reports the current status of your production workload processing.v Provides reports that can serve as the basis for documenting your service level

agreements with users. Your customers can see when and how their work is tobe processed.

4 General Information

Page 23: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Automatic Workload RecoveryThe suite enables processing production workload to continue even when systemor connection failures occur. If one system fails, the suite can restart the processingon another system. When the controlling system is running in a z/OS systemcomplex (sysplex), a hot standby function can automatically transfer control of theproduction workload to another system in the sysplex. Because the suite continuesto manage the production workload during failures, you can maintain the integrityof your processing schedules and continue to service your customers.

In Tivoli Workload Scheduler, a switchmanager function provides the possibility toreplace a failing master domain manager or domain manager workstation with anappropriately configured backup fault-tolerant agent or domain manager .

ProductivityThe suite represents real productivity gains by ensuring fast and accurateperformance through automation. Many of today’s automation solutions quoteunrealistic productivity benefits. Some of the tasks automated should never beperformed, or certainly not as often as they are by automation. Because of this, it isdifficult to correlate real productivity benefits to your enterprise.

The tasks the suite performs not only have to be performed, but have to beperformed correctly, every time, and as quickly as possible. Many of these tasks,traditionally performed by DP professionals, are tedious and as a result prone toerror. With the suite, your DP staff can use their time more efficiently.

Business SolutionsThe suite provides business solutions by:v Driving production according to your business objectivesv Automating the production workload to enhance company productivityv Providing you with information about current and future workloadsv Managing a high number of activities efficiently.

User ProductivityYour DP staff and end users can realize significant productivity gains through thesuite’s:v Fast-path implementation.v Immediate response to dialog requests for workload status inquiries. Users are

provided with detailed real-time information about production workloadprocessing so that they can detect and promptly correct errors.

v Automation of operator tasks such as error recovery and data set cleanup.v Job Scheduling Console with its easy-to-use graphical user interface and

sophisticated online help facilities.

Growth EnablingAs you implement automation and control you can manage greater productionworkload volumes. The suite enables growth within your DP operation byproviding:v Ways of absorbing the increasing batch workload without increasing operations

personnel

Chapter 1. Overview 5

Page 24: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

v An open interface for submitting and tracking the workload on a variety ofoperating systems

v Interfaces with other systems management application programsv An open interface for, and communicating with, programs on other platformsv Management of current and future production workload volumesv Simulation facilities to forecast future workloads

Who Uses the Workload Scheduler SuiteIn a typical enterprise, many people contribute to the implementation andoperation of the suite:v Scheduling managerv Operations managerv Shift supervisorv Application programmerv Console operatorsv Workstation operators, such as print operators, job setup staff, and login

receptionistsv End usersv Help desk

This section describes how the suite can directly benefit your DP staff.

Role of the Scheduling Manager—The Focal PointThe scheduler makes it possible for the scheduling manager to maintain currentand future production processing across your enterprise. The suite benefits thescheduling manager in the following ways:v Automatically scheduling all production workload activities.v Automatically resolving the complexity of production workload dependencies

and driving the work in the most efficient way.v Supporting the simulation of future workloads on the system. The scheduling

manager can evaluate, in advance, the effect of changes in production workloadvolumes or processing resources.

v Giving a real-time view of the status of work as it flows through the system sothat the scheduling manager can quickly:– Respond to customer queries about the status of their work– Identify problems in the workload processing.

v Providing facilities for manual intervention.v Managing many workload problems automatically. The production-workload-

restart facilities, hot standby, automatic recovery of jobs and started tasks, anddata set cleanup provide the scheduling manager with comprehensiveerror-management and disaster-management facilities.

v Providing a log of changes to the production workload data through theaudit-trail facility. This assists the scheduling manager in resolving problemscaused by user errors.

v Managing unplannable work.

Role of the Operations ManagerThe reporting, planning, and control functions can help the operations manager todo the following:

6 General Information

Page 25: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

v Improve the efficiency of the operationv Improve control of service levels and qualityv Set service level agreements for end-user applications and for services providedv Improve relationships with end-user departmentsv Increase the return on your IT investmentv Develop staff potential.

A Powerful Tool for the Shift SupervisorThe suite is important for the shift supervisor, especially in multisystem complexes,where local and remote systems are controlled from a central site. The suite canhelp the shift supervisor to do the following:v Monitor and control the production workload through multisystem complexesv Control the use of mountable devicesv Separate information about work status from system and other informationv Provide end users with status information directlyv Manage the workload if a system failure occursv Make changes to the current plan in response to unplanned events, such as

equipment failures, personnel absences, and rush jobs.

Role of the Application ProgrammerThe user-authority checking enables application development groups to use all theplanning and control functions in parallel with—but in isolation from—productionsystems and services.

The suite can be a valuable tool for application development staff when they aredoing the following:v Packaging new applications for regular runningv Testing new JCL in final packaged formv Testing new applications and changes to existing onesv Restarting or rerunning unsuccessful jobs.

Console OperatorsThe suite can free console operators from the these time-consuming tasks:v Starting and stopping started tasksv Preparing JCL before job submissionv Submitting jobsv Verifying the sequence of workv Reporting job statusv Performing data set cleanup in recovery and rerun situationsv Responding to workload failurev Preparing the JCL for step-level restarts.

Workstation OperatorsThe suite helps workstation operators do their work by providing the following:v Complete and timely status informationv Up-to-date ready lists that prioritize the work flowv Online assistance in operator instructions.

End Users and the Help DeskYour end users often need to be informed about the status of workload processing.They can use the Job Scheduling Console to check the status of the processing oftheir job streams themselves from a personal workstation. End users can make

Chapter 1. Overview 7

Page 26: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

queries using the Job Scheduling Console without having to be familiar with thesuite, ISPF, or TSO, and without having to be logged on to a local system.

The help desk can use the Job Scheduling Console in the same way to answerqueries from end users about the progress of their workload processing.

SummaryThe suite communicates with other key IBM products to provide a comprehensive,automated processing facility and an integrated solution for the control of allproduction workloads. Here are the benefits that the suite offers you:v Increased automation, which increases efficiency and uses DP resources more

effectively, resulting in improved service levels for your customersv Improved systems management integration, providing a unified solution to

your systems management problemsv More effective control of DP operations, which lets you implement change and

manage growth more efficientlyv Increased availability, through automatic workload recoveryv Opportunities for growth, through your ability to manage greater workload

volumesv Investment protection, by building on your current investment in z/OS and

allowing existing customers to build on their existing investment in workloadmanagement

v Improved customer satisfaction, resulting from higher levels of service andavailability, fewer errors, and faster response to problems

v Greater productivity, because repetitive, error-prone tasks are automated andoperations personnel can use their time more efficiently

v Integration of multiple operating environments, which provides a singlecontrolling point for the cooperating systems that comprise your DP operation

The suite is more than just a batch scheduling tool—it is a production managementsystem with the capability to schedule all the work running on any system.

8 General Information

Page 27: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Chapter 2. Tivoli Workload Scheduler

Tivoli Workload Scheduler’s scheduling features help you plan every phase ofproduction. During the processing day, the Tivoli Workload Scheduler productioncontrol programs manage the production environment and automate most operatoractivities. Tivoli Workload Scheduler prepares jobs for execution, resolvesinterdependencies, and launches and tracks each job. Because jobs start running assoon as their dependencies are satisfied, idle time is minimized, and throughputimproves significantly. Jobs never run out of sequence, and, if a job fails, TivoliWorkload Scheduler handles the recovery process with little or no operatorintervention.

OverviewThe next pages provide an outline of Tivoli Workload Scheduler.

What is Tivoli Workload SchedulerTivoli Workload Scheduler is composed of three parts:

Tivoli Workload Scheduler engineThe scheduling engine. It runs on every computer of a Tivoli WorkloadScheduler network. Upon installation, the engine is configured for the rolethat the workstation will play within the scheduling network, such asmaster domain manager, domain manager, or agent.

Tivoli Workload Scheduler ConnectorMaps Job Scheduling Console commands to the Tivoli Workload Schedulerengine. The Tivoli Workload Scheduler connector runs on the master andon any of the fault-tolerant agents (FTA) that you will use as backupmachines for the master workstation. The connector pre-requires the TivoliManagement Framework configured for a Tivoli server or Tivoli managednode.

Job Scheduling (JS) ConsoleA Java™ based graphical user interface (GUI) for the Tivoli WorkloadScheduling suite. The Job Scheduling Console runs on any machine fromwhich you want to manage Tivoli Workload Scheduler plan and databaseobjects. It provides, through the Tivoli Workload Scheduler connector,Conman and Composer functionality. The Job Scheduling Console does notrequire to be installed in the same machine with the Tivoli WorkloadScheduler engine or connector. You can use the Job Scheduling Consolefrom any machine as long as it has a TCP/IP link with the machinerunning the Tivoli Workload Scheduler connector.

From the same Job Scheduling Console you can also manage TivoliWorkload Scheduler for z/OS plan and database objects, provided that youcan log into a machine running the Tivoli Workload Scheduler for z/OSconnector.

The Tivoli Workload Scheduler NetworkA Tivoli Workload Scheduler network is made up of the workstations, or CPUs, onwhich jobs and job streams are run.

© Copyright IBM Corp. 1991, 2003 9

Page 28: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

A Workload Scheduler network contains at least one Workload Scheduler domain,the master domain, in which the master domain manager is the management hub.Additional domains can be used to divide a widely distributed network intosmaller, locally managed groups.

Using multiple domains reduces the amount of network traffic by reducing thecommunications between the master domain manager and other computers.

In a single domain configuration, the master domain manager maintainscommunications with all of the workstations in the Workload Scheduler network.

In a multi-domain configuration, the master domain manager communicates withthe workstations in its domain and with the subordinate domain managers. Thesubordinate domain managers, in turn, communicate with the workstations in theirdomains and subordinate domain managers. Multiple domains also providefault-tolerance by limiting the problems caused by losing a domain manager to asingle domain. To limit the effects further, you can designate backup domainmanagers to take over if their domain managers fail.

Before the start of each new day, the master domain manager creates a productioncontrol file, named Symphony. Tivoli Workload Scheduler is then restarted in thenetwork, and the master domain manager sends a copy of the new productioncontrol file to each of its automatically linked agents and subordinate domainmanagers. The domain managers, in turn, send copies to their automatically linkedagents and subordinate domain managers.

Once the network is started, scheduling messages like job starts and completionsare passed from the agents to their domain managers, through the parent domainmanagers to the master domain manager. The master domain manager thenbroadcasts the messages throughout the hierarchical tree to update the productioncontrol files of domain managers and fault tolerant agents running in Full Statusmode.

Figure 1. This Tivoli Workload Scheduler network is made up by two domains.

10 General Information

Page 29: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Manager and Agent TypesPrimarily, workstation definitions refer to physical workstations. However, in thecase of extended and network agents, the workstations are logical definitions thatmust be hosted by a physical Tivoli Workload Scheduler workstation.

Tivoli Workload Scheduler workstations can be of the following types:

Master domain manager (MDM)The domain manager in the topmost domain of a Tivoli WorkloadScheduler network. It contains the centralized database files used todocument scheduling objects. It creates the production plan at the start ofeach day, and performs all logging and reporting for the network.

Backup masterA fault-tolerant agent or domain manager capable of assuming theresponsibilities of the master domain manager for automatic workloadrecovery.

Domain managerThe management hub in a domain. All communications to and from theagents in a domain are routed through the domain manager.

Backup domain managerA fault-tolerant agent capable of assuming the responsibilities of itsdomain manager.

Fault-tolerant agent (FTA)A workstation capable of resolving local dependencies and launching itsjobs in the absence of a domain manager.

Standard agentA workstation that launches jobs only under the direction of its domainmanager.

Extended agentA logical workstation definition that enables you to launch and control jobson other systems and applications, such as Peoplesoft, Oracle Applications,SAP, and z/OS™.

Network AgentA logical workstation definition for creating dependencies between jobsand job streams in separate Tivoli Workload Scheduler networks.

Job Scheduling Console ClientAny workstation running the graphical user interface from whichschedulers and operators can manage Tivoli Workload Scheduler plan anddatabase objects.

The following table summarizes which Tivoli Workload Scheduler component goesinto what type of workstation:

Workstation type Engine Connector Job Scheduling Console

Master Domain Manager Yes Yes Optional

Backup Master Yes Yes Optional

Domain Manager Yes Optional Optional

Backup Domain Manager Yes Optional Optional

Fault-tolerant Agent Yes Optional Optional

Standard Agent Yes No Optional

Chapter 2. Tivoli Workload Scheduler 11

Page 30: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Workstation type Engine Connector Job Scheduling Console

Extended Agent Not Applicable Not Applicable Not Applicable

Network Agent Not Applicable Not Applicable Not Applicable

Job Scheduling ConsoleClient

No No Yes

TopologyA key to choosing how to set up Tivoli Workload Scheduler domains for anenterprise is the concept of localized processing. The idea is to separate or localizethe enterprises’s scheduling needs based on a common set of characteristics.

Common characteristics are things such as geographical locations, businessfunctions, and application groupings. Grouping related processing can limit theamount of interdependency information that needs to be communicated betweendomains. The benefits of localizing processing in domains are:v Decreased network traffic. Keeping processing localized to domains eliminates

the need for frequent interdomain communications.v Provides a convenient way to tighten security and simplify administration.

Security and administration can be defined at, and limited to, the domain level.Instead of network-wide or workstation-specific administration, you can havedomain administration.

v Network and workstation fault tolerance can be optimized. In a multiple domainTivoli Workload Scheduler network, you can define backups for each domainmanager, so that problems in one domain do not disrupt operations in otherdomains.

NetworkingThe following questions will help in making decisions about how to set up yourenterprise’s Tivoli Workload Scheduler network. Some questions involve aspects ofyour network, and others involve the applications controlled by Tivoli WorkloadScheduler. You may need to consult with other people in your organization toresolve some issues.v How large is your Tivoli Workload Scheduler network? How many computers

does it hold? How many applications and jobs does it run?The size of your network will help you decide whether to use a single domainor the multiple domain architecture. If you have a small number of computers,or a small number of applications to control with Tivoli Workload Scheduler,there may not be a need for multiple domains.

v How many geographic locations will be covered in your Tivoli WorkloadScheduler network? How reliable and efficient is the communication betweenlocations?This is one of the primary reasons for choosing a multiple domain architecture.One domain for each geographical location is a common configuration. If youchoose single domain architecture, you will be more reliant on the network tomaintain continuous processing.

v Do you need centralized or decentralized management of Tivoli WorkloadScheduler?A Tivoli Workload Scheduler network, with either a single domain or multipledomains, gives you the ability to manage Tivoli Workload Scheduler from asingle node, the master domain manager. If you want to manage multiplelocations separately, you can consider the installation of a separate Tivoli

12 General Information

Page 31: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Workload Scheduler network at each location. Note that some degree ofdecentralized management is possible in a stand-alone Tivoli WorkloadScheduler network by mounting or sharing file systems.

v Do you have multiple physical or logical entities at a single site? Are theredifferent buildings, and several floors in each building? Are there differentdepartments or business functions? Are there different applications?These may be reasons for choosing a multi-domain configuration. For example, adomain for each building, department, business function, or each application(manufacturing, financial, engineering, etc.).

v Do you run applications, like SAP R/3, that will operate with Tivoli WorkloadScheduler?If they are discrete and separate from other applications, you may choose to putthem in a separate Tivoli Workload Scheduler domain.

v Would you like your Tivoli Workload Scheduler domains to mirror yourWindows NT domains?This is not required, but may be useful.

v Do you want to isolate or differentiate a set of systems based on performance orother criteria?This may provide another reason to define multiple Tivoli Workload Schedulerdomains to localize systems based on performance or platform type.

v How much network traffic do you have now?If your network traffic is manageable, the need for multiple domains is lessimportant.

v Do your job dependencies cross system boundaries, geographical boundaries, orapplication boundaries? For example, does the start of Job1 on CPU3 depend onthe completion of Job2 running on CPU4?The degree of interdependence between jobs is an important consideration whenlaying out your Tivoli Workload Scheduler network. If you use multipledomains, you should try to keep interdependent objects in the same domain.This will decrease network traffic and take better advantage of the domainarchitecture.

v What level of fault-tolerance do you require?An obvious disadvantage of the single domain configuration is the reliance on asingle domain manager. In a multi-domain network, the loss of a single domainmanager affects only the agents in its domain.

Tivoli Workload Scheduler ComponentsTivoli Workload Scheduler uses several manager processes to efficiently segregateand manage networking, dependency resolution, and job launching. Theseprocesses communicate among themselves through the use of message queues.Message queues are also used by the Console Manager to integrate operatorcommands into the batch process.

On any computer running Tivoli Workload Scheduler there are a series of activemanagement processes. They are started as a system service, or by the StartUpcommand, or manually from the Job Scheduling Console. The following are themain processes:

NetmanThe network management process that establishes network connectionsbetween remote Mailman processes and local Writer processes.

Chapter 2. Tivoli Workload Scheduler 13

Page 32: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

MailmanThe mail management process that sends and receives inter-CPU messages.

BatchmanThe production control process. Working from Symphony, the productioncontrol file, it runs jobs streams, resolves dependencies, and directs Jobmanto launch jobs.

Writer The network writer process that passes incoming messages to the localMailman process.

JobmanThe job management process that launches and tracks jobs under thedirection of Batchman.

ConmanThe console manager. It is the user’s interface to daily production activitiesby means of the command line interface or of the Job Scheduling Console.Conman writes information that is received by either the local Netman orMailman processes.

Tivoli Workload Scheduler Scheduling ObjectsScheduling with Tivoli Workload Scheduler includes the capability to do thefollowing:v Schedule jobs across a network.v Group jobs into job streams according, for example, to function or application.v Set limits on the number of jobs that can run concurrently.v Create job streams based on day of the week, on specified dates and times, or by

customized calendars.v Ensure correct processing order by identifying dependencies such as successful

completion of previous jobs, availability of resources, or existence of requiredfiles.

v Set automatic recovery procedures for unsuccessful jobs.v Forward incomplete jobs to the next production day.

Tivoli Workload Scheduler administrators and operators work with these objectsfor their scheduling activity:Workstation

Also referred to as CPU. Usually an individual computer on which jobsand job streams are run. Workstations are defined in the Tivoli WorkloadScheduler database as a unique object. A workstation definition is requiredfor every computer that executes jobs or job streams in the WorkloadScheduler network.

Workstation classA group of workstations. Any number of workstations can be placed in aclass. Job streams and jobs can be assigned to execute on a workstationclass. This makes replication of a job or job stream across manyworkstations easy.

Job A script or command, run on the user’s behalf, run and controlled byTivoli Workload Scheduler.

Job streamAlso referred to as schedule. A mechanism for grouping jobs by function orapplication on a particular day and time. A job stream definition includes alaunch time, priorities, dependencies, and job names.

CalendarAn object defined in the Tivoli Workload Scheduler database that contains

14 General Information

Page 33: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

a list of scheduling dates. Each calendar can be assigned to multiple jobstreams. Assigning a calendar to a job stream causes that job stream to runon the days specified in the calendar. A calendar can be used as aninclusionary or exclusionary run cycle.

Run cycleA cycle that specifies the days that a job stream is scheduled to run. Runcycles are defined as part of job streams and may include calendars thatwere previously defined. There are three types of run cycles: a Simple runcycle, a Weekly run cycle, or a Calendar run cycle (commonly called acalendar). Each type of run cycle can be inclusionary or exclusionary. Thatis, each run cycle can define the days when a job stream is included in theproduction cycle, or when the job stream is excluded from the productioncycle.

PromptAn object that can be used as a dependency for jobs and job streams. APrompt must be answered affirmatively for the dependent job or jobstream to launch. There are two types of prompts: predefined and ad hoc.An ad hoc prompt is defined within the properties of a job or job streamand is unique to that job or job stream. A predefined prompt is defined inthe Tivoli Workload Scheduler database and can be used by any job or jobstream.

ResourceAn object representing either physical or logical resources on your system.Once defined in the Tivoli Workload Scheduler database, resources can beused as dependencies for jobs and job streams. For example, you candefine a resource named tapes with a unit value of two. Then, define jobsthat require two available tape drives as a dependency. Jobs with thisdependency cannot run concurrently because each time a job is run the“tapes” resource is in use.

ParameterA parameter used to substitute values into your jobs and job streams.When using a parameter in a job script, the value is substituted at runtime. In this case, the parameter must be defined on the workstation whereit will be used. Parameters cannot be used when scripting extended agentjobs.

DependencyA condition that must be met in order to launch a job or job stream.

User For Windows NT only, the user name specified in a job definition’s“Logon” field must have a matching user definition. The definitionsfurnish the user passwords required by Tivoli Workload Scheduler tolaunch jobs.

The Production ProcessTivoli Workload Scheduler runs in daily run cycles called a production day. Theproduction day is a 24-hour period, but it does not have to conform to the actualcalendar day. It may be offset. For example, the production day by default runsfrom 6:00 a.m. to 5:59 a.m. the next day. At the start of each production day, TivoliWorkload Scheduler executes a program that selects the job streams that are to runon that day from the databases found on the master domain manager. Thenanother program includes the uncompleted schedules from the previousproduction day into the current day’s production and logs all the previous day’sstatistics into an archive.

All of the required information for that production day is placed into a productioncontrol database named Symphony. During the production day, the production

Chapter 2. Tivoli Workload Scheduler 15

Page 34: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

control database is continually being updated to reflect the work that needs to bedone, the work in progress, and the work that has been completed. A copy of theSymphony file is sent to all subordinate domain managers and to all thefault-tolerant agents in the same domain. The subordinate domain managersdistribute their copy to all the fault-tolerant agents in their domain and to all thedomain managers that are subordinate to them, and so on down the line. Thisenables fault-tolerant agents throughout the network to continue processing even ifthe network connection to their domain manager is down. From the JobScheduling Console or the command line interface, the operator can view andmake changes in the day’s production by making changes in the Symphony file.

Tivoli Workload Scheduler processes monitor the production control database andmake calls to the operating system to launch jobs as required. The operatingsystem runs the job, and in return informs Tivoli Workload Scheduler whether thejob completed successfully or not. This information is entered into the productioncontrol database to indicate the status of the job.

SchedulingScheduling can be accomplished either through the Tivoli Workload Schedulercommand line interface or the Tivoli Job Scheduling Console.

Scheduling includes the following tasks:v Defining and maintaining workstations.v Defining scheduling objects.v Defining job streams.v Starting and stopping production processing.v Viewing and modifying jobs and job streams.

Defining Scheduling ObjectsScheduling objects are workstations, workstation classes, domains, jobs, jobstreams, resources, prompts, calendars, and parameters. Scheduling objects aremanaged with the Composer program and are stored in Workload Scheduler’sdatabase. To create or modify an object, you can use either the Tivoli WorkloadScheduler command line interface or the Job Scheduling Console.

Creating Job StreamsTivoli Workload Scheduler’s primary processing task is running job streams. A jobstream is an outline of batch processing consisting of a list of jobs. Although jobstreams can be defined from the product’s command line interface, using the Jobstream editor of the Job Scheduling Console is the recommended way to create andmodify job streams. The Job Stream Editor is for working with the jobs and followsdependencies between the jobs, as well as the run cycles of the job stream. The jobstream properties window is for specifying time restrictions, resourcedependencies, file dependencies, and prompt dependencies at the job stream level.

Setting Job RecoveryWhen defining a job, the possibility must be taken into account that in someinstance the job may not complete successfully. The administrator can define arecovery option and recovery actions when defining the job. One of the followingrecovery options is possible:v Not continuing with the next job. This stops the execution of the job stream and

puts it in the stuck state. This is the default action.

16 General Information

Page 35: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

v Continuing with the next job.v Running the job again.

Optionally, a recovery prompt can be associated with the job. A recovery prompt isa local prompt to display when the job completes unsuccessfully. Processing doesnot continue until the prompt is answered affirmatively.

Another option is to define a recovery job that can be run in the place of theoriginal job if it completes unsuccessfully. The recovery job must have beendefined previously. Processing will stop if also the recovery job completesunsuccessfully.

Running ProductionProduction consists in taking the definitions of the scheduling objects from thedatabase, their time constraints, and their dependencies, and building and runningthe production control file.

Start-of-day ProcessingThe processing day of Tivoli Workload Scheduler begins at the time defined by theGlobal Option start, which is set by default to 6:00 a.m. To turnover a new day,pre-production set up is performed for the upcoming day, and post-productionlogging and reporting is performed for the day just ended.

Pre and post-production processing can be fully automated by adding theTivoli-supplied final job stream, or a user-supplied equivalent, to the TivoliWorkload Scheduler database along with other job streams.

The final job stream is placed in production everyday, and results in running a jobnamed Jnextday prior to the start of a new day. The job performs the followingtasks:1. Selects job streams for the new day’s production plan.2. Compiles the production plan.3. Prints pre-production reports.4. Stops Tivoli Workload Scheduler.5. Carries forward uncompleted job streams, logs the old production plan, and

installs the new plan.6. Start Tivoli Workload Scheduler for the new day.7. Prints post-production reports for the previous day.8. Logs job statistics for the previous day.

These steps are run on the master workstation.

Running Job StreamsDepending on their run cycle definition, job streams are taken from the TivoliWorkload Scheduler database and automatically inserted in the daily productionplan of the day.

While the job stream is in the plan, and as long as it has not completed, it can stillbe modified in any of its components. That is, you can modify the job streamproperties, the properties of its jobs, their sequence, the workstation or resourcesthey use, and so on, in order to be able to face last minute contingencies. The best

Chapter 2. Tivoli Workload Scheduler 17

Page 36: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

way to do this is by means of the job stream instance editor of the Job SchedulingConsole, where the term instance implies a scheduling object that has beenincluded in the current plan.

You can also hold, release, or cancel a job stream, as well as change the maximumnumber of jobs within the job stream that can run concurrently. You can change thepriority previously assigned to the job stream and release the job stream from allits dependencies.

Last minute changes to the current production plan include the possibility tosubmit jobs and job streams that are already defined in the Tivoli WorkloadScheduler database but were not included in the plan. You can as well submit jobsthat are being defined ad hoc. These jobs are submitted to the current plan but arenot stored in the database.

MonitoringMonitoring is done by listing plan objects in the Job Scheduling Console. Usinglists, you can see the status of all or of subsets of the following objects in thecurrent plan:v Job stream instances.v Job instances.v Domains.v Workstations.v Resources.v File dependencies, where a file dependency is when a job or job stream needs to

verify the existence of one or more files before it can begin execution.v Prompt dependencies, where a prompt dependency is when a job or job stream

needs to wait for an affirmative response to a prompt before it can beginexecution.

You can use these lists also for managing some of these objects. You can forinstance reallocate resources, link or unlink workstations, kill jobs, or switching adomain manager.

Additionally, you can monitor the daily plan with Tivoli Business SystemsManager, an object-oriented systems management application that providesmonitoring and event management of resources, applications and subsystems, thatis integrated with version 8.1 of Tivoli Workload Scheduler.

Network managers can use Tivoli Workload Scheduler/NetView, a NetViewapplication, to monitor and diagnose Tivoli Workload Scheduler networks from aNetView management node. It includes a set of submaps and symbols to viewTivoli Workload Scheduler networks topographically, and determine the status ofthe job scheduling activity and critical Tivoli Workload Scheduler processes oneach workstation. Menu actions are provided to start and stop Tivoli WorkloadScheduler processing, and to run conman on any workstation in the network.

ReportingAs part of the pre-production and post-production processes, reports are generatedwhich show summary or detail information about the previous or next productionday. These reports can also be generated ad-hoc. The available reports are:v Job details listingv Prompt listing

18 General Information

Page 37: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

v Calendar listingv Parameter listingv Resource listingv Job History listingv Job histogramv Planned production schedulev Planned production summaryv Planned production detailv Actual production summaryv Actual production detailv Cross reference report

In addition, during production, a standard list file (STDLIST) is created for eachjob instance launched by Tivoli Workload Scheduler. Standard list files containheader and trailer banners, echoed commands, and errors and warnings. Thesefiles can be used to troubleshoot problems in job execution.

AuditingAn auditing option helps track changes to the database and the plan.

For the database, all user modifications, except for the delta of the modifications,are logged. If an object is opened and saved, the action will be logged even if nomodification has been done.

For the plan, all user modifications to the plan are logged. Actions are loggedwhether they are successful or not.

Audit files are logged to a flat text file on individual machines in the TivoliWorkload Scheduler network. This minimizes the risk of audit failure due tonetwork issues and allows a straightforward approach to writing the log. The logformats are the same for both plan and database in a general sense. The logsconsist of a header portion which is the same for all records, an “action ID”, and asection of data which will vary according the action type. All data is kept in cleartext and formatted to be readable and editable from a text editor such as vi ornotepad.

Options and SecurityThe Tivoli Workload Scheduler options files determine how Tivoli WorkloadScheduler runs on your system. several performance, tuning, security, logging, another configuration options are available.

Setting Global and Local OptionsGlobal options are defined on the master domain manager and apply to allworkstations in the Tivoli Workload Scheduler network. Global options are enteredin the globalopts file with a text editor. Changes can be made at any time, but theydo not take effect until Tivoli Workload Scheduler is stopped and restarted. Globaloptions are used to:v Set the name of the master domain manager.v Determine if object names can be up to sixteen characters long.v Determine whether or not uncompleted job streams will be carried forward from

the old to the new production control file.

Chapter 2. Tivoli Workload Scheduler 19

Page 38: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

v Define the start time of the Tivoli Workload Scheduler processing day.

Local options are entered with a text editor into a file named localopts, whichresides in the Tivoli Workload Scheduler user’s home directory. The local optionsare defined on each workstation and apply only to that workstation. Local optionsare used to:v Specify the name of the local workstation.v Prevent the launching of jobs execute by root in UNIX®.v Prevent unknown clients from connecting to the system.v Specify a number of performance options.v Specify a number of logging preferences.

Setting SecuritySecurity is accomplished with the use of a security file that contains one or moreuser definitions. Each user definition identifies a set of users, the objects they arepermitted to access, and the types of actions they can perform.

A template file is installed with the product. The template must be edited to createthe user definitions and compiled and installed with a utility program to create anew operational security file. After it is installed, further modifications can bemade by creating an editable copy with another utility.

Each workstation in a Tivoli Workload Scheduler network has its own security file.An individual file can be maintained on each workstation, or a single security filecan be created on the master domain manager and copied to each domainmanager, fault-tolerant agent, and standard agent.

Secure Authentication and EncryptionSecurity is enhanced for connections between protected and non-protected domainsby applying the authentication and encryption mechanism based on the SecureSockets Layer (SSL) protocol. SSL uses digital certificates to authenticate theidentity of a workstation.

The Tivoli Workload Scheduler administrator must plan how authentication will beused within the network:v Use one certificate for the entire Tivoli Workload Scheduler network.v Use a separate certificate for each domain.v Use a separate certificate for each workstation.

SSL support is automatically installed with Tivoli Workload Scheduler, version 8.2.

Work Across FirewallsFor previous versions of Tivoli Workload Scheduler, running the commands to startor stop a workstation or to get the standard list requires opening a direct TCP/IPconnection between the originator and the destination nodes. In a firewallenvironment, this forces users to break the firewall to open a direct communicationpath between the master and each fault-tolerant agent in the network.

Version 8.2 features a new configurable attribute-behindfirewall- in the workstation’sdefinition in the database. You can set this attribute to ON to indicate that afirewall exists between that particular workstation and its domain manager, andthat the link between the domain manager and the workstation (which can beanother domain manager itself) is the only allowed link between the respectivedomains.

20 General Information

|

||||||

Page 39: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Also, for all the workstations having this attribute set to ON, the commands tostart or stop the workstation or to get the standard list will be transmitted throughthe domain hierarchy instead of opening a direct connection between the master(or domain manager) and the workstation.

Centralized Security MechanismA new global option makes it possible to change the security model in the TivoliWorkload Scheduler network. If you use this option, then the security files for thefault-tolerant agents in the network can be created or modified only on the master.The Tivoli Workload Scheduler administrator takes charge of creating, updating,and distributing the security files for all the agents where a user access is required.Setting this global option triggers a security mechanism to identify and trust theTivoli Workload Scheduler network corresponding to that master.

If you prefer the traditional security model, you can still do so by not activatingthe global variable.

Using Time ZonesTivoli Workload Scheduler supports time zones. Enabling time zones provides theability to manage one’s workload on a global level. Time-zone implementation alsoallows for easy scheduling across multiple time zone and for jobs that need to runin the “dead zone.” The dead zone is the gap between the Tivoli WorkloadScheduler start of day time on the master and the time on the fault-tolerant agentin another time zone. For example, if an eastern master with a Tivoli WorkloadScheduler start of day of 6 a.m. initializes a western agent with a 3-hour time-zonedifference, the dead zone for this agent is between the hours of 3 a.m. and 6 a.m.Previously, special handling was required to run jobs in this time period. Nowwhen specifying a time zone with the start time on a job or job stream, TivoliWorkload Scheduler runs them as expected.

Once enabled, time zones can be specified in the Job Scheduling Console orcomposer for start and deadline times within jobs and job streams.

Using Extended AgentsWith IBM Tivoli Workload Scheduler for Applications, extended agents (XA) areused to extend the job scheduling functions of Tivoli Workload Scheduler to othersystems and applications. An extended agent is defined as a workstation that has ahost and an access method.

The host is a Tivoli Workload Scheduler fault-tolerant agent (FTA) or standardagent (SA).

The access method is a program that is executed by the hosting workstationwhenever Tivoli Workload Scheduler, either through its command line or the TivoliJob Scheduling Console, needs to interact with the external system. IBM TivoliWorkload Scheduler for Applications includes the following access methods:v Oracle e-Business Suite access method (MCMAGENT)v PeopleSoft access method (psagent)v R/3 access method (r3batch)v z/OS access method (mvsca7, mvsjes, and mvsopc)

Chapter 2. Tivoli Workload Scheduler 21

|||||||

Page 40: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

To launch and monitor a job on an extended agent, the host executes the accessmethod, passing it job details as command line options. The access methodcommunicates with the external system to launch the job and returns the status ofthe job.

An extended agent workstation is only a logical entity related to an access methodhosted by the physical Tivoli Workload Scheduler workstation. More than oneextended agent workstations can be hosted by the same Tivoli Workload Schedulerworkstation and rely on the same access method. The x-agent is defined in astandard Tivoli Workload Scheduler workstation definition, which gives thex-agent a name and identifies the access method.

The next figure shows how these elements fit together in the case of a typicalextended agent configuration.

To launch a job in an external environment, Tivoli Workload Scheduler executes theextended agent access method providing it with the extended agent workstationname and information about the job. The method looks at the corresponding filenamed <WORKSTATION_NAME>_ <method_name>.opts to determine which externalenvironment instance it will connect to. The access method can then launch jobs onthat instance and monitor them through completion writing job progress and statusinformation in the standard list file of the job.

Extended agents can be used to run jobs also in an end-to-environment, wheretheir scheduling and monitoring is performed from a Tivoli Workload Schedulerfor z/OS controller.

Hosting Tivoli Workload Scheduler Agent

Access methodXA CPU 1

XA CPU 2

XA CPU 3

.OPTS FILE 1

.OPTS FILE 2

.OPTS FILE 3

External environment 1

External environment 2

External environment 3

Figure 2. How Extended Agents Work.

22 General Information

Page 41: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Chapter 3. Tivoli Workload Scheduler for z/OS

Tivoli Workload Scheduler for z/OS expands the scope for automating your dataprocessing (DP) operations. It plans and automatically schedules the productionworkload. From a single point of control, it drives and controls the workloadprocessing at both local and remote sites. By using Tivoli Workload Scheduler forz/OS to increase automation, you use your DP resources more efficiently, havemore control over your DP assets, and manage your production workloadprocessing better.

How Your Production Workload Is ManagedHow does Tivoli Workload Scheduler for z/OS give you all this? This sectiondescribes functions that make your information systems (IS) operations run moreefficiently. But first, here is a brief introduction to the structure of the product andsome concepts.

StructureTivoli Workload Scheduler for z/OS consists of a base product, the agent and anumber of features. Every z/OS system in your complex requires the base product.One z/OS system in your complex is designated the controlling system and runsthe engine feature. Only one engine feature is required, even when you want tostart standby engines on other z/OS systems in a sysplex.

Tivoli Workload Scheduler for z/OS with Tivoli Workload Scheduler addressesyour production workload in the distributed environment. You can schedule,control, and monitor jobs in Tivoli Workload Scheduler from Tivoli WorkloadScheduler for z/OS. For example, in the current plan, you can specify jobs to runon workstations in Tivoli Workload Scheduler.

The workload on other operating environments can also be controlled with theopen interfaces provided with Tivoli Workload Scheduler for z/OS. Sampleprograms using TCP/IP or an NJE/RSCS (network job entry/remote spoolingcommunication subsystem) combination show you how you can control theworkload on environments that at present have no scheduling feature.

Additionally, national language features let you see the dialogs and messages, inthe language of your choice. These languages are currently available:v Englishv Germanv Japanesev Spanish

Panel and message text can also be modified to include enterprise-specificinstructions or help.

ConceptsIn managing production workloads, Tivoli Workload Scheduler for z/OS builds onseveral important concepts.

Plans. Tivoli Workload Scheduler for z/OS constructs operating plans based onuser-supplied descriptions of the DP operations department and its production

© Copyright IBM Corp. 1991, 2003 23

Page 42: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

workload. These plans provide the basis for your service level agreements and giveyou a picture of the status of the production workload at any point in time. Youcan simulate the effects of changes to your production workload, calendar, andinstallation by generating trial plans.

Job streams. A job stream is a description of a unit of production work. It caninclude the following:v A list of the jobs (related tasks) associated with that unit of work, such as:

– Data entry– Job preparation– Job submission or started-task initiation– Communication with the NetView program– File transfer to other operating environments– Printing of output– Postprocessing activities, such as quality control or dispatch– Other tasks related to the unit of work that you want to schedule, control,

and trackv A description of dependencies between jobs within a job stream and between

jobs in other job streamsv Information about resource requirements, such as exclusive use of a data setv Special operator instructions that are associated with a jobv How and where each job should be processedv Run policies for that unit of work; that is, when it should be scheduled or

alternatively the name of a group definition that records the run policy

Tivoli Workload Scheduler for z/OS schedules work based on the information youprovide in your job stream descriptions.

Workstations. When scheduling and processing work, Tivoli Workload Schedulerfor z/OS considers the processing requirements of each job. Some typicalprocessing considerations are:v What human or machine resources are required for processing the work—for

example, operators, processors, or printers?v When are these resources available?v How will these jobs be tracked?v Can this work be processed somewhere else if the resources become

unavailable?

Tivoli Workload Scheduler for z/OS supports a range of work process types, calledworkstations, that map the processing needs of any task in your productionworkload. Each workstation supports one type of activity. This gives you theflexibility to schedule, monitor, and control any type of DP activity, including thefollowing:v Job setup—both manual and automaticv Job submissionv Started-task actionsv Communication with the NetView programv Print jobsv Manual preprocessing or postprocessing activity

You can plan for maintenance windows in your hardware and softwareenvironments. Tivoli Workload Scheduler for z/OS enables you to perform acontrolled and incident-free shutdown of the environment, preventing last-minute

24 General Information

Page 43: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

cancellation of active tasks. You can choose to reroute the workload automaticallyduring any outage, planned or unplanned.

Tivoli Workload Scheduler for z/OS tracks jobs as they are processed atworkstations and dynamically updates the plan with real-time information on thestatus of jobs. You can view or modify this status information online using theworkstation ready lists in the dialog.

Dependencies. In general, every DP-related activity must occur in a specific order.Activities performed out of order will, at the very least, create invalid output; inthe worst case your corporate data will be corrupted. In any case, the result iscostly reruns, missed deadlines, and unsatisfied customers.

You can define dependencies for jobs when a specific processing order is required.When Tivoli Workload Scheduler for z/OS manages the dependent relationshipsfor you, the jobs are always started in the correct order every time they arescheduled. A dependency is called internal when it is between two jobs in the samejob stream, and external when it is between two jobs in different job streams.

You can work with job dependencies graphically from the Tivoli Job SchedulingConsole.

Tivoli Workload Scheduler for z/OS lets you serialize work based on the status ofany DP resource. A typical example is a job that uses a data set as input, but mustnot start until the data set is successfully created and loaded with valid data. Youcan use resource serialization support to send availability information about a DPresource to Tivoli Workload Scheduler for z/OS.

Special resources. Special resources are typically defined to represent physical orlogical object used by jobs. A special resource can be used to serialize access to adata set or to limit the number of file transfers on a particular network link. Theresource does not have to represent a physical object in your configuration,although it often does.

Tivoli Workload Scheduler for z/OS keeps a record of the state of each resourceand its current allocation status. You can choose to hold resources in case a joballocating the resources ends abnormally. You can also use the Tivoli WorkloadScheduler for z/OS interface with the Resource Object Data Manager (RODM) toschedule jobs according to real resource availability. You can subscribe to RODMupdates in both local and remote domains.

Tivoli Workload Scheduler for z/OS lets you subscribe to data set activity on z/OSsystems. The data set triggering function of Tivoli Workload Scheduler for z/OSautomatically updates special resource availability when a data set is closed. Youcan use this notification to coordinate planned activities or to add unplanned workto the schedule.

Calendars. Tivoli Workload Scheduler for z/OS uses information about when thejobs departments work and when they are free, so that job streams are notscheduled to run on days when processing resources are not available (forexample, Sundays and holidays). This information is stored in a calendar. TivoliWorkload Scheduler for z/OS supports multiple calendars for enterprises wheredifferent departments have different work days and free days. Different groupswithin a business operate according to different calendars).

Chapter 3. Tivoli Workload Scheduler for z/OS 25

Page 44: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

The multiple calendar function is critical if your enterprise has installations inmore than one geographical location (for example, with different local or nationalholidays).

Business processing cycles. Tivoli Workload Scheduler for z/OS uses businessprocessing cycles, or periods, to calculate when your job streams should be run—forexample, weekly, or every 10th working day. Periods are based on the businesscycles of your customers. Tivoli Workload Scheduler for z/OS supports a range ofperiods for processing the different job streams in your production workload.

When you define a job stream, you specify when it should be planned using a runcycle, which can be:v A rule with a format such as

ONLY the SECOND TUESDAY of every MONTH

EVERY FRIDAY in the user-defined period SEMESTER1

where the words in capitals are selected from lists of ordinal numbers, names ofdays, and common calendar intervals or period names, respectively.

v A combination of period and offset. For example, an offset of 10 in a monthlyperiod specifies the tenth day of each month.

Plans in Tivoli Workload Scheduler for z/OSTivoli Workload Scheduler for z/OS plans your production workload schedule. Itproduces both high-level and detailed plans. Not only do these plans drive theproduction workload, but they can also show you the status of the productionworkload on your system at any specified time. You can produce trial plans toforecast future workloads.

Long-term PlanningThe long-term plan is a high-level schedule of your anticipated productionworkload. It lists, by day, the instances of job streams to be run during the periodof the plan. Each instance of a job stream is called an occurrence. The long-termplan shows when occurrences are to run, as well as the dependencies that existbetween the job streams. You can view these dependencies graphically on yourterminal as a network, to check that work has been defined correctly. The plan canassist you in forecasting and planning for heavy processing days. Thelong-term-planning function can also produce histograms showing plannedresource use for individual workstations during the plan period.

You can use the long-term plan as the basis for documenting your service levelagreements. It lets you relate service level agreements directly to your productionworkload schedules so that your customers can see when and how their work is tobe processed.

The long-term plan provides a window to the future. How far into the future is upto you: from one day to four years. You can also produce long-term plansimulation reports for any future date. Tivoli Workload Scheduler for z/OS canautomatically extend the long-term plan at regular intervals. You can print thelong-term plan as a report, or you can view, alter, and extend it online using thedialogs.

Detailed PlanningThe current plan is the heart of Tivoli Workload Scheduler for z/OS processing: infact, it drives the production workload automatically and provides a way to checkits status. The current plan is produced by the run of batch jobs that extract from

26 General Information

Page 45: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

the long term plan the occurrences that fall within the specified period of timeconsidering also the job details. What the current plan does is to select a windowfrom the long term plan and make the jobs ready to be run: they will be reallystarted depending on the decided restrictions (for example, dependencies,resources availability, or time depending jobs).

The current plan is a rolling plan that can cover several days. A common methodis to cover 1–2 days with regular extensions each shift. Production workloadprocessing activities are listed by minute.

You can either print the current plan as report, or view, or alter and extend itonline, by using the dialogs.

Automatically Controlling the Production WorkloadTivoli Workload Scheduler for z/OS automatically drives the production workloadby monitoring the flow of work and by directing the processing of jobs so that itfollows the business priorities established in the plan.

Through its interface to the NetView program or its management-by-exceptionISPF dialog, Tivoli Workload Scheduler for z/OS can alert the production controlspecialist to problems in the production workload processing. Furthermore, theNetView program can automatically trigger Tivoli Workload Scheduler for z/OS toperform corrective actions in response to these problems.

Tivoli Workload Scheduler for z/OS automatically:v Starts and stops started tasksv Edits job statements: z/OS JCL or equivalent job statements for other operating

environments before submissionv Submits jobs in the specified sequence to the target operating

environment—every timev Tracks each scheduled job in the planv Determines the success or failure of the jobsv Displays status information and instructions to guide workstation operatorsv Provides automatic recovery of jobs when they end in error, regardless of the

operating environmentv Generates processing dates for your job stream run cycles using rules, such as:

– Every second Tuesday of the month– Only the last Saturday in June, July, and August– Every third workday in the user-defined PAYROLL period

v Starts jobs with regard to real resource availabilityv Performs data set cleanup in error and rerun situations for the z/OS workloadv Tailors the JCL for step restarts of z/OS jobs and started tasksv Dynamically schedules additional processing in response to unplannable

activitiesv Provides automatic notification when an updated data set is closed—which can

be used to trigger subsequent processingv Generates alerts when abnormal situations are detected in the workload

Tivoli Workload Scheduler for z/OS also provides manual control facilities, whichare described in “Manual Control and Intervention” on page 31.

Chapter 3. Tivoli Workload Scheduler for z/OS 27

Page 46: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Automatic Workload SubmissionTivoli Workload Scheduler for z/OS automatically drives work through the system,taking into account work that requires manual or program-recorded completion.(Program-recorded completion refers to situations where the status of ascheduler-controlled job is set to “complete” by a user-written program.) It alsopromotes the optimum use of resources, improves system availability, andautomates complex and repetitive operator tasks. Tivoli Workload Scheduler forz/OS automatically controls the submission of work according to:v Dependencies between jobsv Workload prioritiesv Specified time for the submission of particular workv Availability of resources

By saving a copy of the JCL for each separate run, or occurrence, of a particular jobin its plans, Tivoli Workload Scheduler for z/OS prevents the unintentional reuseof temporary JCL changes, such as overrides.

Job tailoring. Tivoli Workload Scheduler for z/OS provides automatic job tailoringfunctions, which enables jobs to be automatically edited. This can reduce yourdependency on time-consuming and error-prone manual editing of jobs. TivoliWorkload Scheduler for z/OS job tailoring provides:v Automatic variable substitutionv Dynamic inclusion and exclusion of inline job statementsv Dynamic inclusion of job statements from other libraries or from an exit

For jobs to be submitted on a z/OS system, these job statements will be z/OS JCL,but scheduler JCL tailoring directives can be included in jobs to be submitted onother operating systems, such as AIX®/6000.

Variables can be substituted in specific columns, and you can define verificationcriteria to ensure that invalid strings are not substituted. Special directivessupporting the variety of date formats used by job stream programs let youdynamically define the required format and change the multiple times for the samejob. Arithmetic expressions can be defined to let you calculate values such as thecurrent date plus four work days.

Automatic Recovery and RestartTivoli Workload Scheduler for z/OS provides automatic restart facilities for yourproduction work. You can specify the restart actions to be taken if work initiatedby Tivoli Workload Scheduler for z/OS ends in error (see Figure 3 on page 29.) Youcan use these functions to predefine automatic error-recovery and restart actionsfor jobs and started tasks. The scheduler’s integration with the NetView programallows it to automatically pass alerts to the NetView program in error situations.Use of z/OS’s cross-system coupling facility (XCF) enables Tivoli WorkloadScheduler for z/OS to maintain production workload to maintain productionworkload processing when system failures occur.

Recovery of jobs and started tasks. Automatic recovery actions for failed jobs arespecified in user-defined control statements. Parameters in these statementsdetermine the recovery actions to be taken when a job or started task ends in error.

28 General Information

Page 47: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Restart and cleanup. You can use restart and cleanup to catalog, uncatalog, ordelete data sets when a job ends in error, or when you need to rerun a job. Dataset cleanup takes care of JCL in the form of in-stream JCL, in-stream procedures,and cataloged procedures on both local and remote systems. This function can beinitiated automatically by Tivoli Workload Scheduler for z/OS or manually by auser through the panels. Tivoli Workload Scheduler for z/OS will reset the catalogto the status that it was before the job ran for both generation data set groups(GDGs) and for DD allocated data sets contained in JCL. In addition, restart andcleanup supports the use of Removable Media Manager in your environment.

Restart at both the step- and job-level is also provided in the Tivoli WorkloadScheduler for z/OS panels. It manages resolution of generation data group (GDG)names, JCL containing nested INCLUDEs or PROC, and IF-THEN-ELSEstatements. Tivoli Workload Scheduler for z/OS also automatically identifiesproblems that can prevent successful restart, providing a logic of the “best restartstep.”

You can browse the job log or request a step-level restart for any z/OS job orstarted task even when there are no catalog modifications. The job-log browsefunctions are also available for the workload on other operating platforms, whichis especially useful for those environments that do not support an SDSF-likefacility. If you use a SYSOUT archiver, for example RMDS, you can interface withit from Tivoli Workload Scheduler for z/OS and so prevent duplication of job loginformation.

These facilities are available to you without the need to make changes to yourcurrent JCL.

Tivoli Workload Scheduler for z/OS gives you an enterprise-wide data set cleanupcapability on remote agent systems.

User Application

RestartAn Earlier

Job?

AutomaticCatalog

Cleanup?

Restartthe Failing

Job?

Job 3Ends In

Error

1

2

Job 2

Job 3

!

Job 1

Continue? Do Nothing?

RecoveryJob?

Analyze

The Scheduler Analyzesthe Error and Determines

the Restart Action

Figure 3. Automatic Recovery and Restart

Chapter 3. Tivoli Workload Scheduler for z/OS 29

Page 48: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Production workload restart. Tivoli Workload Scheduler for z/OS provides aproduction workload restart, which can automatically maintain the processing ofyour work if a system or connection fails. Scheduler-controlled production workfor the unsuccessful system is rerouted to another system. Because Tivoli WorkloadScheduler for z/OS can restart and manage the production workload, the integrityof your processing schedule is maintained, and service continues for yourcustomers.

Tivoli Workload Scheduler for z/OS exploits the VTAM® Model ApplicationProgram Definition feature and the z/OS defined symbols to ease theconfiguration and job in a sysplex environment, giving the user a single systemview of the sysplex.

Starting, stopping, and managing your engines and agents do not require you toknow which sysplex z/OS image is actually running on.

Hot standby. Tivoli Workload Scheduler for z/OS provides a single point ofcontrol for your z/OS production workload. If this controlling system fails, TivoliWorkload Scheduler for z/OS can automatically transfer the controlling functionsto a backup system within a Parallel Sysplex®, see Figure 4. Through XCF, TivoliWorkload Scheduler for z/OS can automatically maintain production workloadprocessing during system or connection failures.

z/OS Automatic Restart Manager SupportAll the scheduler components are enabled to be restarted by the Automatic RestartManager (ARM) of the z/OS operating system, in the case of program failure.

Workload Manager (WLM) SupportWith Workload Manager (WLM), you can make the best use of resources accessedby your scheduled jobs. In addition, your jobs maintain the highest possiblethroughput with WLM and Tivoli Workload Scheduler for z/OS. When used withWLM, the scheduler is able to achieve the best possible system response times.

Automatic Status CheckingTo track the work flow, Tivoli Workload Scheduler for z/OS interfaces directlywith the operating system, collecting and analyzing status information about the

z/OS

ControllingScheduler

SharedDASD

ControlledScheduler

(Hot Standby)

ControlledScheduler

XCFXCF XCF

Parallel Sysplex

Figure 4. Production Workload Restart and Hot Standby

30 General Information

Page 49: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

production work that is currently active in the system. Tivoli Workload Schedulerfor z/OS can record status information from both local and remote processors.When status information is reported from remote sites in different time zones,Tivoli Workload Scheduler for z/OS makes allowances for the time differences.

Status Reporting from Heterogeneous EnvironmentsThe processing on other operating environments can also be tracked by TivoliWorkload Scheduler for z/OS. You can use supplied programs to communicatewith the engine from any environment that can establish communications with az/OS system.

Status Reporting from User ProgramsYou can pass status information about production workload processing to TivoliWorkload Scheduler for z/OS from your own user programs through a standardsupplied routine.

Additional Job-completion CheckingIf required, Tivoli Workload Scheduler for z/OS provides further status checkingby scanning SYSOUT and other print data sets from your processing when thesuccess or failure of the processing cannot be determined by completion codes. Forexample, Tivoli Workload Scheduler for z/OS can check the text of systemmessages or messages originating from your user programs. Using informationcontained in job completion checker (JCC) tables, Tivoli Workload Scheduler forz/OS determines what actions to take when it finds certain text strings. Theseactions can include:v Reporting errorsv Requeuing SYSOUTv Writing incident records to an incident data set

Managing Unplanned WorkTivoli Workload Scheduler for z/OS can be automatically triggered to update thecurrent plan with information about work that cannot be planned in advance. Thisallows Tivoli Workload Scheduler for z/OS to control unexpected work. BecauseTivoli Workload Scheduler for z/OS checks the processing status of this work,automatic recovery facilities are also available.

Interfacing with Other ProgramsTivoli Workload Scheduler for z/OS provides a program interface (PIF). Using thisinterface, you can automate most actions that you can perform online through thedialogs. This interface can be called from CLISTs, user programs, and via TSOcommands.

The application programming interface (API) lets your programs communicatewith Tivoli Workload Scheduler for z/OS from any compliant platform. You canuse Common Programming Interface for Communications (CPI-C), advancedprogram-to-program communication (APPC), or your own logical unit (LU) 6.2verbs to converse with Tivoli Workload Scheduler for z/OS through the API. Youcan use this interface to query and update the current plan. The programs can berunning on any platform that is connected locally, or remotely through a network,with the z/OS system where the engine runs.

Manual Control and InterventionTivoli Workload Scheduler for z/OS lets you check the status of work andintervene manually when priorities change or when you need to run unplannedwork. You can query the status of the production workload and then modify theschedule if needed.

Chapter 3. Tivoli Workload Scheduler for z/OS 31

Page 50: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Status InquiriesWith the ISPF dialogs or with the Job Scheduling Console, you can make queriesonline and receive timely information on the status of the production workload.

Time information that is displayed by the dialogs can be in the local time of thedialog user. Using the dialogs, you can request detailed or summary informationon individual job streams, jobs, and workstations, as well as summary informationconcerning workload production as a whole. You can also display dependenciesgraphically as a network at both job stream and job level. Status inquiries:v Provide you with overall status information that you can use when considering

a change in workstation capacity or when arranging an extra shift or overtimework.

v Help you supervise the work flow through the installation; for instance, bydisplaying the status of work at each workstation.

v Help you decide whether intervention is required to speed the processing ofspecific job streams. You can find out which job streams are the most critical.You can also check the status of any job stream, as well as the plans and actualtimes for each job.

v Enable you to check information before making modifications to the plan. Forexample, you can check the status of a job stream and its dependencies beforedeleting it or changing its input arrival time or deadline. See “Modifying theCurrent Plan” for more information.

v Provide you with information on the status of processing at a particularworkstation. Perhaps work that should have arrived at the workstation has notarrived. Status inquiries can help you locate the work and find out what hashappened to it.

Modifying the Current PlanTivoli Workload Scheduler for z/OS makes status updates to the planautomatically, using its tracking functions. However, it lets you change the planmanually to reflect unplanned changes to the workload or to the operationsenvironment, which often occur during a shift. For example, you may need tochange the priority of a job stream, add unplanned work, or reroute work fromone workstation to another. Or you may need to correct operational errorsmanually. Modifying the current plan may be the best way to handle thesesituations.

You can modify the current plan online. For example, you can:v Include unexpected jobs or last-minute changes to the plan. Tivoli Workload

Scheduler for z/OS then automatically creates the dependencies for this work.v Manually modify the status of jobs.v Delete occurrences of job streams.v Graphically display job dependencies before you modify them.v Modify the data in job streams, including the JCL.v Respond to error situations by:

– Rerouting jobs– Rerunning jobs or occurrences– Completing jobs or occurrences– Changing jobs or occurrences

v Change the status of workstations by:– Rerouting work from one workstation to another– Modifying workstation reporting attributes– Updating the availability of resources

32 General Information

Page 51: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

– Changing the way resources are handledv Replan or extend the current plan

In addition to using the dialogs, you can modify the current plan from your ownjob streams using the program interface or the application programming interface.You can also trigger Tivoli Workload Scheduler for z/OS to dynamically modifythe plan using TSO commands or a batch program. This enables unexpected workto be added automatically to the plan.

Management of Critical JobsTivoli Workload Scheduler for z/OS exploits the capability of the WorkloadManager component of z/OS to ensure that critical jobs are completed on time. If acritical job is late, Tivoli Workload Scheduler for z/OS favors it using existingWorkload Manager interface.

SecurityToday, DP operations increasingly require a high level of data security, particularlyas the scope of DP operations expands and more people within the enterprisebecome involved. Tivoli Workload Scheduler for z/OS provides complete securityand data integrity within the range of its functions. It provides a shared centralservice to different user departments even when the users are in differentcompanies and countries. Tivoli Workload Scheduler for z/OS provides a highlevel of security to protect scheduler data and resources from unauthorized access.With Tivoli Workload Scheduler for z/OS, you can easily organize, isolate, andprotect user data to safeguard the integrity of your end-user applications (seeFigure 5 on page 33). Tivoli Workload Scheduler for z/OS can plan and control thework of many user groups, and maintain complete control of access to data andservices.

Audit TrailWith the audit trail, you can define how you want Tivoli Workload Scheduler forz/OS to log accesses (both reads and updates) to scheduler resources. Because itprovides a history of changes to the databases, the audit trail can be extremelyuseful for staff that works with debugging and problem determination.

Scheduler

Scheduler Data

AuditTrail

JCL

JCL

Finance

TSO User

Manufact.Sales

RACF

TSO User

TSO User JCL

Figure 5. Security

Chapter 3. Tivoli Workload Scheduler for z/OS 33

Page 52: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

A sample program is provided for reading audit-trail records. The program readsthe logs for a period that you specify and produces a report detailing changes thathave been made to scheduler resources.

System Authorization FacilityTivoli Workload Scheduler for z/OS uses the system authorization facility (SAF), afunction of z/OS, to pass authorization verification requests to your securitysystem, for example RACF. This means that you can protect your scheduler dataobjects with any security system that uses the SAF interface.

Protection of Data and Resources: Each user request to access a function or toaccess data is validated by SAF. This is some of the information that can beprotected:v Calendars and periodsv Job stream names or job stream owner, by namev Workstation, by namev Job stream-specific data in the planv Operator instructionsv JCL

To support distributed, multi-user handling, Tivoli Workload Scheduler for z/OSlets you control the level of security you want to implement, right down to thelevel of individual records. You can define generic or specific RACF resourcenames to extend the level of security checking.

If you have RACF Version 2 Release 1 installed, you can use the Tivoli WorkloadScheduler for z/OS reserved resource class to manage your Tivoli WorkloadScheduler for z/OS security environment. This means you do not have to defineyour own resource class by modifying RACF and restarting your system.

Data Integrity During Submission: Tivoli Workload Scheduler for z/OS canensure the correct security environment for each job it submits, regardless ofwhether the job is run on a local or a remote system. Tivoli Workload Schedulerfor z/OS lets you create tailored security profiles for individual jobs or groups ofjobs.

Configurations of Tivoli Workload Scheduler for z/OSTivoli Workload Scheduler for z/OS supports many configuration options using avariety of communication methods:v The Controlling Systemv Controlled z/OS Systemsv Remote Panels and Program Interface Applicationsv Scheduling Jobs That Are in Tivoli Workload Scheduler

The Controlling SystemThe controlling system requires both the agent and the engine. One controllingsystem can manage the production workload across all your operatingenvironments.

The engine is the focal point of control and information. It contains the controllingfunctions, the dialogs, and the scheduler’s own batch programs. Only one engine isrequired to control the entire installation, including local and remote systems (seeFigure 6 on page 35).

34 General Information

Page 53: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Controlled z/OS SystemsAn agent is required for every controlled z/OS system in an configuration. Thisincludes, for example, local controlled systems within shared DASD or sysplexconfigurations.

The agent runs as a z/OS subsystem and interfaces with the operating system(through JES2 or JES3, and SMF), using the subsystem interface and the operatingsystem exits. The agent monitors and logs the status of work, and passes the statusinformation to the engine via shared DASD, XCF, or ACF/VTAM®.

You can exploit z/OS and cross-system coupling facility (XCF) to connect yourlocal z/OS systems. Rather than being passed to the controlling system via sharedDASD, work status information is passed directly via XCF connections. XCF letsyou exploit all of production-workload-restart facilities and its hot standbyfunction. See “Automatic Recovery and Restart” on page 28.

Remote SystemsThe agent on a remote z/OS system passes status information about theproduction work in progress to the engine on the controlling system. Allcommunication between Tivoli Workload Scheduler for z/OS subsystems on thecontrolling and remote systems is done via ACF/VTAM.

Sysplex

OS/390 TrackerHot Standby Controller

OS/390 TrackerHot Standby ControllerOS/390 Tracker

Active Controller

Sysplex

OS/390 TrackerHot Standby Controller

OS/390 TrackerHot Standby ControllerOS/390 Tracker

Active Controller

DistributedAgents

Domain Managers

z/OSDistributed

TivoliManagementFramework

ConnectorConnector

z/OS Agents

Job SchedulingConsole

Figure 6. Tivoli Workload Scheduler for z/OS Configurations

Chapter 3. Tivoli Workload Scheduler for z/OS 35

|

||

Page 54: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Tivoli Workload Scheduler for z/OS lets you link remote systems usingACF/VTAM networks. Remote systems are frequently used locally “on premises”to reduce the complexity of the data processing (DP) installation.

Remote Panels and Program Interface ApplicationsISPF panels and program interface (PIF) applications can run in a different z/OSsystem from the one where the engine is running. Dialogs and PIF applicationssend requests to and receive data from a Tivoli Workload Scheduler for z/OSserver which is running on the same z/OS system where the target engine isrunning, via advanced program-to-program communications (APPC). The serverwill communicate with the engine to perform the requested actions.

The server is a separate address space, started and stopped either automatically bythe engine or by the user via the z/OS start command. There can be more thanone server for an engine.

If the dialogs or the PIF applications run on the same z/OS system where thetarget engine is running, the server may not be involved.

Scheduling Jobs That Are in Tivoli Workload SchedulerTivoli Workload Scheduler for z/OS also allows you to access job streams(schedules in Tivoli Workload Scheduler) and add them to the current plan inTivoli Workload Scheduler for z/OS. In addition, you can build dependenciesamong Tivoli Workload Scheduler for z/OS job streams and Tivoli WorkloadScheduler jobs. From Tivoli Workload Scheduler for z/OS, you can monitor andcontrol the distributed agent.

In the Tivoli Workload Scheduler for z/OS current plan, you can specify jobs torun on workstations in Tivoli Workload Scheduler. Tivoli Workload Scheduler forz/OS passes the job information to the Tivoli Workload Scheduler Symphony file,which in turn passes the jobs in the current plan to Tivoli Workload Scheduler todistribute and process. In turn, Tivoli Workload Scheduler reports the status ofrunning and completed jobs back to the current plan for monitoring in TivoliWorkload Scheduler for z/OS.

36 General Information

Page 55: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Chapter 4. Tivoli Job Scheduling Console

This chapter describes feature level 1.2 of the Tivoli Job Scheduling Console that isdistributed as part of the Tivoli Workload Scheduling suite.

OverviewThe Tivoli Job Scheduling Console for the Tivoli Workload Scheduling suite is aninteractive interface for creating, modifying, and deleting objects in the productdatabase. It also enables you to monitor and control objects scheduled in thecurrent plan.

The Job Scheduling Console enables you to work with Tivoli Workload Schedulerfor z/OS and with Tivoli Workload Scheduler. You can work with these productssimultaneously from the same graphical console.

To run the console, you only have to be able to log into a scheduling enginethrough a connector. This means that you can manage plan and database objectsfrom any system, including a laptop, on which the Job Scheduling Console isinstalled and from which you can reach via TCP/IP a server running the connectorfor Tivoli Workload Scheduler or for Tivoli Workload Scheduler for z/OS.

Connectors manage the traffic between the Job Scheduling Console and the jobschedulers. Connectors are installed separately on a Tivoli management server andon managed nodes that have access to the scheduler.

If you plan to use the Job Scheduling Console to schedule the workload with TivoliWorkload Scheduler for z/OS, you need to install the Tivoli Workload Schedulerfor z/OS connector. If you plan to use the Job Scheduling Console to schedule theworkload with Tivoli Workload Scheduler, you need to install the Tivoli WorkloadScheduler connector.

The Job Scheduling Console provides two main functions:

SchedulingEnables you to define and list job streams, jobs, and resource availability inthe scheduler database.

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

Extensions, built into the Job Scheduling Console, extend its base schedulingfunctions to specific scheduling functions of Tivoli Workload Scheduler for z/OSand of Tivoli Workload Scheduler.

For each of these functions, you can use a list creation mechanism that enables youto list database or plan objects that you select according to filtering criteria.Filtering criteria narrow a list down to selected objects that you want to work with.You can list objects without using filtering criteria. In this case, the list displays allthe existing objects of a kind. You can use both pre-defined lists that are packagedwith the Job Scheduling Console and lists that you create.

© Copyright IBM Corp. 1991, 2003 37

Page 56: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Tivoli Workload Scheduler for z/OS TasksThis section describes what Tivoli Workload Scheduler for z/OS tasks can beaccomplished with the Job Scheduling Console. The tasks are grouped according towhether they are run typically by an administrator or by an operator.

Work begins by selecting a Tivoli Workload Scheduler for z/OS engine. A popupwindow lists what actions are available for the engine. The same actions can bedone by clicking the corresponding icons at the top of the window. The iconsdisplay contextually with the engine.

Scheduler TasksFrom the Job Scheduling Console, you can define and manage the followingobjects in the scheduler database:v Job streamsv Jobsv Workstationsv Resources

Working with Job StreamsJob streams are a collection of jobs, scheduling information, and the resources theyrequire to run. The jobs that comprise a job stream usually follow a sequencewhere the execution of a job depends on the successful completion of another job.Creating a job stream involves:1. Defining job stream properties.2. Creating jobs, which includes defining what resources each job requires to run

and the timing of its execution.3. Defining the necessary dependencies, or sequencing, among the jobs of the job

stream and with jobs that belong to other job streams.4. Defining one or more run cycles, or the days on which the job stream must run

and when it must start.

Modifying a job stream involves adding, deleting, or modifying any of the jobsthat comprise it, along with the dependencies and run cycles. You can also deletean entire job stream.

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

Working with JobsJobs are the units of work in a job stream. You cannot create jobs outside of a jobstream. You must first create a job stream and define its properties before you canstart to create the jobs that comprise it. Creating a job involves:1. Defining job properties.2. Specifying when the job must run (time restrictions) within its job stream’s run

cycle.3. Defining the properties of the task associated with the job, if applicable.4. Specifying the resources that the job requires to run.

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

38 General Information

Page 57: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Working with WorkstationsWorkstations describe how jobs have to be run. A workstation is not necessarilyhardware. It is a stage in the processing that is controlled by the scheduler. Toschedule a job instance, a workstation must have been defined beforehand. Beforethe scheduler can start a job instance, the workstation on which the job instance isdefined must be available. So, by controlling workstation availability, you controlthe running of job instances that are defined on the workstation. Defining aworkstation involves:1. Defining the workstation’s general properties.2. Specifying open time intervals, periods during which the workstation‘s

resources and parallel servers are available to process work. Parallel serversand resources are usually necessary to run work at the workstation.

Working with ResourcesResources represent physical or logical devices that jobs use in order to run.Defining a resource involves:1. Defining the resource’s general properties.2. Specifying availability intervals, periods during which the resource’s state and

quantity available for running jobs differ from the values specified as generalproperties.

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

Operator TasksFrom the Job Scheduling Console, you can monitor and control the followingobjects in the current plan:v Job stream instancesv Job instancesv Workstationsv Resources

To monitor and control these objects, you must first display them in a list in theJob Scheduling Console.

Working with Job Stream InstancesJob streams that are scheduled in the plan are job stream instances. You canbrowse, modify, and delete job stream instances, provided you display them in ajob stream instance list. Modifying a job stream instance includes changing some ofits general properties and the start and deadline times.

You can also change the status of a job stream instance to Waiting or to Complete.

Working with Job InstancesJobs belonging to a job stream that is scheduled in the plan are job instances. Youcan browse, modify, and delete job instances after displaying them in a job instancelist. Modifying a job instance involves:v Changing its state, resource dependencies, and time restrictions.v Deleting predecessor and successor jobs in the job instance’s dependency chain.v Mark job instances for monitoring with Tivoli Business Systems Manager.

In addition, you can:

Chapter 4. Tivoli Job Scheduling Console 39

Page 58: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

v Hold or release job instances.v Remove or restore job instances in the current plan.v Run a job instance immediately regardless of normal scheduling rules.v Browse the job log.v View and modify operator instructions.v Tailor job statements.v Restart a job instance and perform cleanup operations.

Working with Workstations in the PlanA workstation instance is a workstation that is allocated to the plan. By usingfiltered lists of workstations in the plan, you can:v Monitor the status of a workstation in the plan and of the job instances

scheduled to run on it.v Modify the settings and availability of the workstation.v Change the status of a workstation.v Reroute the job instances that are scheduled to run on a workstation.v Display by status the job instances scheduled on a workstation and, eventually,

modify the job instances.

Working with Resources in the PlanA resource instance is a resource that is allocated to the plan. The resource isreserved for the duration of the plan for use by the jobs that depend on it. Thestatus and quantities of the resource are specified in the general properties andavailability intervals definitions in the database. You can:v Modify a resource’s availability intervals and quantity after the resource has

been allocated to the plan.v Use lists of resource instances to view and modify job instances associated with

the resources.v Specify connected workstations.

Tivoli Workload Scheduler TasksThe Job Scheduler Console provides conman and composer functionality for TivoliWorkload Scheduler engines. This section describes what Tivoli WorkloadScheduler tasks can be accomplished with the Job Scheduling Console. The tasksare grouped according to whether they are run typically by an administrator or byan operator.

Work begins by selecting a Tivoli Workload Scheduler engine. A popup windowlists what actions are available for the engine. The same actions can be done byclicking the corresponding icons at the top of the window. The icons displaycontextually with the engine.

Scheduler TasksFrom the Job Scheduling Console, you can define and manage the followingobjects in the scheduler database:v Job streamsv Jobsv Calendarsv Promptsv Parameters

40 General Information

Page 59: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

v Domainsv Workstations and workstation classesv Resourcesv Users

Working with Job StreamsYou can use the Job Scheduling Console to work with job streams and job streamtemplates. Job stream templates contain only scheduling information. When youdefine a job stream as belonging to a template, you imply that it must share thetemplate calendar and run cycles. You can:v Create, update, or delete job stream templates.v Add or remove a job stream from a job stream template.v List job stream templates in the scheduler database.v Mark job streams for monitoring with Tivoli Business Systems Manager.

Working with JobsWhen you create or modify a job, the Tivoli Workload Scheduler extension addsthe following features to a basic job definition:v Assigning the necessary special (logical) and workstation resources for the

execution of the job.v Defining the job’s automatic and feedback options.

Working with CalendarsA 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 onthe days specified in the calendar. Since a calendar is defined to the schedulerdatabase, it can be assigned to multiple job streams. You can create as manycalendars as required to meet your scheduling needs.

Working with PromptsPrompts can be used as dependencies for jobs and job streams. A prompt must beanswered 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 thatprints a report runs.

There are two types of prompt:

Ad hoc promptIs defined within the properties of a job or a job stream and is unique tothat job or job stream.

Predefined promptIs defined in the Tivoli Workload Scheduler database and can be used byany job or job stream.

You can create, modify, and delete prompts in the Tivoli Workload Schedulerdatabase.

Working with ParametersParameters are useful to substitute values into your jobs and job streams. Sinceparameters are stored in the Tivoli Workload Scheduler database, all jobs and jobstreams that use the particular parameter are updated automatically when thevalue changes. For scheduling, a parameter can be used as a substitute for all orpart of:v File dependency path names

Chapter 4. Tivoli Job Scheduling Console 41

Page 60: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

v Text for promptsv Logon, command, and script file names

You can create, modify, and delete parameters in the Tivoli Workload Schedulerdatabase.

Working with DomainsA domain is a named group of Workload Scheduler workstations, consisting of oneor more workstations and a domain manager acting as the management hub. Alldomains have a parent domain, except for the master domain.

You can create, modify, and delete domain definitions in the Tivoli WorkloadScheduler database.

Working with WorkstationsYou can create, update, and delete workstation definitions in the schedulerdatabase. You define the following workstation characteristics:v General propertiesv Availability status during specific periods of timev Available quantities during specific periods of time

You can list workstations defined in the scheduler database, selected according tofiltering criteria, and browse or modify their properties. You can also deleteworkstations from the database.

Working with Workstation ClassesA workstation class is a group of workstations. Any number of workstations can beplaced in a class. Job streams and jobs can be assigned to execute on a workstationclass, making replication across many workstations easy.

If a job stream is defined on a workstation class, each job added to the job streammust be defined either on a single workstation or on the exact same workstationclass that the job stream was defined on.

You can create, modify, and delete workstation classes.

Working with ResourcesYou can create, update, and delete resource definitions in the scheduler database.You define the following resource characteristics:v General propertiesv Availability status on a given workstation during specific periods of timev Available quantities on a given workstation during specific periods of timev Workstations connected to the resource

You can list resources defined in the scheduler database, selected according tofiltering criteria, and browse or modify their properties. You can also deleteresources from the database.

Working with UsersThe users for whom Tivoli Workload Scheduler will launch jobs must be defined inthe database. This is required for Windows NT users only.

From the Job Scheduling Console you can:v Create, modify, and delete user definitions in the database.v Change user passwords.

42 General Information

Page 61: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Operator TasksFrom the Job Scheduling Console, you can monitor and control the followingobjects in the daily plan:v Job stream instancesv Job instancesv Workstationsv Domainsv File dependenciesv Prompt dependenciesv Resource dependencies

To monitor and control these objects, you must first display them in a list.

You can also select a different plan to use, other than the current plan.

Working with Job Stream InstancesYou can use the console to do the following on job stream instances:v Modify the properties.v Mark or unmark for monitoring with Tivoli Business Systems Manager.v Display, add, and delete predecessors.v Display successors.v Hold or release.v Cancel, or re-submit.v Change the job limit or the priority.v Release from dependencies.v Submit additional job streams to the current plan.

Working with Job InstancesYou can use the console to do the following on job instances:v Modify the properties.v Mark or unmark for monitoring with Tivoli Business Systems Manager.v Display, add, and delete predecessors.v Display successors.v Hold or release.v Cancel, kill, or rerun.v Confirm as successful or abended.v Release from dependencies.v Submit additional jobs to the current plan.

In addition, you can browse job logs and get job outputs (STDLST).

Working with WorkstationsYou can use the console to do the following on workstation instances:v Display the properties and the status.v Change the job limit or the job fence.v Start or stop.v Link or unlink.

Chapter 4. Tivoli Job Scheduling Console 43

Page 62: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Working with DomainsYou can use the console to do the following on domains in the Tivoli WorkloadScheduler plan:v List the domains.v Start or stop the workstations in a domain.v Link or unlink the workstations in a domain.v Switch the domain manager in a domain.

Working with File DependenciesA file dependency is when a job or job stream needs to verify the existence of oneor more files before it can begin execution. You can display the status of filedependencies.

Working with Prompt DependenciesA prompt dependency is when a job or job stream needs to wait for an affirmativeresponse to a prompt before it can begin execution. From the Job SchedulingConsole you can:v Display the status of prompt dependencies.v Reply to a prompt dependency.

Working with Resource DependenciesResources represent any type of resources on your system such as tape drives,communication lines, databases, or printers, that are needed to run a job. Resourcescan be physical or logical. After defining a resource in the Workload Schedulerdatabase, it can be used as a dependency for jobs and job streams that run on theworkstation or workstation class for which the resource is defined.

Use the Job Scheduling Console to:v Display the properties and the status of resource dependencies.v Change the number of units of a resource dependency.

Common TasksThe Common view is an additional selection at the bottom of the tree view of thescheduling engines. It provides the ability to list job and job stream instances in asingle view and regardless of the scheduling engine, thus furthering integration forworkload scheduling on the mainframe and the distributed platforms.

You can display common plan lists in the main Job Scheduling Console window.With these you can run common lists of job and job stream instances from all theengines displayed in the Job Scheduling tree.

You can list job or job stream instances from all the engines to which the JobScheduling Console is connected. As it is for individual engines, default lists areprovided, but you can also create and save filtered lists that respond to yourneeds.

The Common view implementation considers only the common properties of joband job stream instances. This means that you can filter your queries only oncommon characteristics and the resulting lists will have only columns that displaythe common attributes.

You can select the engines to query on.You can also modify the objects by selectingthe actions that are allowed by the specific scheduler engine

44 General Information

Page 63: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Chapter 5. End-to-end Scheduling

End-to-end scheduling allows you to schedule and control jobs on mainframe,Windows®, and UNIX environments, for truly distributed scheduling. In theend-to-end configuration, Tivoli Workload Scheduler for z/OS is used as theplanner for the job scheduling environment. Tivoli Workload Scheduler DomainManagers and fault-tolerant agents are used to schedule on the distributedplatforms. The agents replace the use of tracker agents.

How End-to-end Scheduling WorksEnd-to-end scheduling directly connects Tivoli Workload Scheduler domainmanagers, and their underlying agents and domains, to Tivoli Workload Schedulerfor z/OS. Tivoli Workload Scheduler for z/OS is seen by the distributed networkas the master domain manager.

Tivoli Workload Scheduler for z/OS creates the production plan also for thedistributed network and sends it to the domain managers. The domain managerssend a copy of the plan to each of their agents and subordinate domain managersfor execution.

The Tivoli Workload Scheduler domain managers function as the broker systemsfor the distributed network by resolving all dependencies for their subordinatemanagers and agents. They send their updates (in the form of events) to TivoliWorkload Scheduler for z/OS so that it can update the plan accordingly. TivoliWorkload Scheduler for z/OS handles its own jobs and notifies the domainmanagers of all the status changes of the Tivoli Workload Scheduler for z/OS jobsthat involve the Tivoli Workload Scheduler plan. In this configuration, the domainmanagers and all the distributed agents recognize Tivoli Workload Scheduler forz/OS as the master domain manager and notify it of all the changes occurring intheir own plans. At the same time, the agents are not permitted to interfere withthe Tivoli Workload Scheduler for z/OS jobs, since they are viewed as running onthe master that is the only node that is in charge of them.

Tivoli Workload Scheduler for z/OS also allows you to access job streams(schedules in Tivoli Workload Scheduler) and add them to the current plan inTivoli Workload Scheduler for z/OS. In addition, you can build dependenciesamong Tivoli Workload Scheduler for z/OS job streams and Tivoli WorkloadScheduler jobs. From Tivoli Workload Scheduler for z/OS, you can monitor andcontrol the distributed agents.

In the Tivoli Workload Scheduler for z/OS current plan, you can specify jobs torun on workstations in the Tivoli Workload Scheduler network. Tivoli WorkloadScheduler for z/OS passes the job information to the Symphony file in the TivoliWorkload Scheduler for z/OS server, which in turn passes the Symphony file tothe Tivoli Workload Scheduler domain managers (DMZ) to distribute and process.In turn, Tivoli Workload Scheduler reports the status of running and completedjobs back to the current plan for monitoring in the Tivoli Workload Scheduler forz/OS engine.

The following figure shows a Tivoli Workload Scheduler network managed by aTivoli Workload Scheduler for z/OS and the flow of data.

© Copyright IBM Corp. 1991, 2003 45

|

||||

||||

||||||||||||

||||||

||||||||

|||

Page 64: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Distributed AgentsA distributed agent is a computer that is part of a Tivoli Workload Schedulerdomain on which you can schedule jobs from Tivoli Workload Scheduler for z/OS.Examples of distributed agents are the following: standard agents, extended agents,fault-tolerant agents, and domain managers.

The following is a description of the types of distributed agents:

Domain ManagerThe management hub in a domain. All communications to and from theagents in a domain are routed through the domain manager.

Backup Domain ManagerA fault-tolerant agent or domain manager capable of assuming theresponsibilities of its domain manager for automatic workload recovery.

Fault-tolerant Agent (FTA)A workstation capable of resolving local dependencies and launching itsjobs in the absence of a domain manager.

Standard AgentA workstation that launches jobs only under the direction of its domainmanager.

DomainZ

MASTERDM

AIX

AIX HPUX

AIX Windows 2000 Solaris

DomainB

FTA1 FTA2 FTA3 FTA4

OS/400

The TWS plan is extracted

from the TWS for z/OS plan

The TWS plan is then distributed

to the subordinate DMs and FTAs

TWS for

z/OS planTWS plan

TWS plan

MasterDomainManager

DomainManagerDMZ

DomainA

z/OS

DomainManagerDMA

DomainManagerDMB

Figure 7. End-to-end configuration

46 General Information

Page 65: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Extended AgentA logical workstation definition that enables you to launch and control jobson other systems and applications, such as Baan, Peoplesoft, OracleApplications, SAP, and MVS JES2 and JES3.

Distributed agents replace tracker agents in Tivoli Workload Scheduler for z/OS.The distributed agents enable you to schedule on non-z/OS systems with a morereliable, fault-tolerant and scalable agent.

In the Tivoli Workload Scheduler for z/OS plan, the logical representation of adistributed agent is called a fault-tolerant workstation.

Supported End-to-end ConfigurationsThe following table lists the agents that you can use in the end-to-end distributednetwork.

Platform Domain Manager Fault-tolerant Agents

IBM AIX U U

HP-UX PA-RISC U U

Solaris Operating Environment U U

Microsoft® Windows NT U U

Microsoft Windows 2000 Server,Advanced Server

U U

Microsoft Windows 2000Professional

U

Microsoft Windows XP Pro U

Compaq Tru64 U

IBM OS/400® U

SGI Irix U

IBM Sequent® Dynix U

Red Hat Linux/INTEL U U

Red Hat Linux/390 U U

Red Hat Linux/zSeries U

SuSe Linux/INTEL U U

SuSe Linux/390 and zSeries (kernel2.4, 31-bits)

U U

SuSe Linux/zSeries (kernel 2.4,64-bits)

U

SuSe Linux/iSeries and pSeries(kernel 2.4, 31-bits)

U

Benefits of End-to-end schedulingThe benefits that can be gained from using end-to-end scheduling are thefollowing:v Connecting fault-tolerant agents Tivoli Workload Scheduler to Tivoli Workload

Scheduler for z/OS.v Scheduling on additional operating systems.

Chapter 5. End-to-end Scheduling 47

||||

|||

|||

|||

|||

||||

||||

|||

|||

|||

|||

|||

|||

|||

|||

|||

||||

||||

||||

|

Page 66: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

v Synchronization of work in mainframe and distributed environments.v The ability for Tivoli Workload Scheduler for z/OS to use multi-tier architecture

with domain managers.v Extended planning capabilities, such as the use of long-term plans, trial plans

and extended plans, also to the distributed part of the network.

48 General Information

Page 67: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents.You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

© Copyright IBM Corp. 1991, 2003 49

Page 68: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation

2Z4A/101

11400 Burnet Road

Austin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

TrademarksThe following terms are trademarks of International Business MachinesCorporation in the United States, other countries, or both: AIX, BookManager,CICS, DB2, DB2 Universal Database, Hiperbatch, Hiperspace, IBM, the IBM logo,IMS, MVS, NetView, OS/390, RACF, SAA, Sysplex Timer, VTAM, and z/OS, Tivoli,the Tivoli logo are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both.

Microsoft, Windows NT, and Windows 2000 are registered trademarks of MicrosoftCorporation in the United States, other countries, or both.

Other company, product, and service names might be trademarks or service marksof others.

50 General Information

Page 69: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

Index

Aadvanced program-to-program

communication (APPC) 31alerts, passing to NetView 28API (application programming

interface) 31APPC (advanced program-to-program

communication) 31application

definition of 24application programmer 7application programming interface

(API) 31audit-trail facility 33authority checking 34automatic

job submission 28status checking 30status reporting 31

automatic job and started-taskrecovery 28, 30

automation 4availability 5

Bbackup domain manager 11backup master 11backup system 30batchman 14benefits 1, 8books

feedback viionline viiordering vii

business processing cycle 26

Ccalendar 14

definition of 25CICS 3Common Programming Interface for

Communications (CPI-C) 31configurations 34Conman 14connector 9

for Tivoli Workload Scheduler 9Tivoli Workload Scheduler for

z/OS 9console operator 7controlled systems 35controlling system

description 34recovery of 30

CPI-C (Common Programming Interfacefor Communications) 31

cross-system coupling facility (XCF) 28,30, 35

current plan 26

Customer Support xcustomers, queries from 7

DData Facility Hierarchical Storage

Manager (DFSHM) 3Data Warehouse enablement pack xivdependencies

defining 25graphic display of 25

dependency 15explorer viewer

z/OS xvihyperbolic viewer

z/OS xviDFHSM (Data Facility Hierarchical

Storage Manager) 3domain manager 11

Ee-mail contact xend users, queries from 7extended agent 11

Ffault-tolerant agent 11feedback about publications xfile dependency 18final job stream 17

Gglobal options 19graphic display of dependencies 25

Hhelpdesk 7

IIMS 3integration 2ISPF (Interactive System Productivity

Facility)dialog 27

JJnextday 17job completion checker (JCC) 31

job dependenciesSee operation dependencies

job instanceexplorer viewer

z/OS xvihyperbolic viewer

z/OS xvijob log 40job recovery

automatic 28manual 32

job stream editor 16job stream instance

explorer viewerz/OS xvi

hyperbolic viewerz/OS xvi

job stream instance editor 18job streams 36job submission

automatic 28manual 32

job tailoring 28jobman 14JSconsole client 11

Llocal options 20long-term plan 26LookAt message retrieval tool ix

Mmailman 14manual status control 33manuals

feedback viionline viiordering vii

master domain 10master domain manager 11message retrieval tool, LookAt ixmonitoring the workload 4multi-tier architecture 48

Nnational language features 23netman 13NetView

alerts 28description of 2RODM 2

network Agent 11

Ooccurrences 26

© Copyright IBM Corp. 1991, 2003 51

Page 70: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

online publicationsaccessing ix

operation dependencies 25operations manager 6operator, workstation 7ordering publications x

Pparameter 15Performance Reporter 3periods 26PIF (program interface) 31PIF applications

applications 36plan

current 26definition of 26detailed 26long-term 26modification of 32trial 24types 23

planningtrial plans 24

production control file 10production day 15production workload restart 28, 30program interface (PIF) 31prompt 15, 41prompt dependency 18publications

feedback viionline viiordering vii, x

RRACF (Resource Access Control

Facility) 3, 34recovery 28, 30recovery job 17recovery prompt 17remote dialogs

dialogs 36Report Management and Distribution

System (RMDS) 3resource 15Resource Access Control Facility

(RACF) 3, 34Resource Object Data Manager

(RODM) 2restart 28, 30restart management 28, 30RMDS (Report Management and

Distribution System) 3RODM (Resource Object Data

Manager) 2run cycle 15

SSA/390 (System Automation for

OS/390) 3SA/390 Automation Feature 3SAF (system authorization facility) 34

schedule 26scheduling manager 6security 34shift supervisor 7simulation with trial plans 24special resources

definition of 25standard agent 11standard list file 19status checking, automatic 30status control

manual 31, 32status inquiries 31status reporting

automatic 31from heterogeneous environments 31from user programs 31

step-level restart 29symphony 10, 15SYSOUT, checking of 31system authorization facility (SAF) 34System Automation OS/390 (SA/390) 3system failures 28Systems Application Architecture

Common Programming Interface forCommunications 31

Ttime restrictions 39Tivoli Business Systems Manager 18Tivoli Management Framework 9Tivoli Service Desk for OS/390

(TSD/390) 3Tivoli Workload Scheduler 23, 36Tivoli Workload Scheduler/NetView 18tracker agents 45trial plans 24TSD/390 (Tivoli Service Desk for

OS/390) 3TWS connector 9

Uunplannable work 31user 15user authority checking 34

Wwork submission, automatic 28Workload Manager (WLM) 2, 30workload monitoring 4workload restart 28, 30workstation

changing the status of 32definition of 24operator 7

workstation class 14writer 14

XXCF (cross-system coupling facility) 28,

30, 35

52 General Information

Page 71: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version
Page 72: IBM Tivoli Workload Scheduling Suitepublib.boulder.ibm.com/tividd/td/TWS/SC32-1256-00/en_US/... · 2004-05-04 · IBM Tivoli Workload Scheduling Suite General Information Version

���

Program Number: 5697-WSZ, 5698-WSH, and 5698-WSE

Printed in Denmark by IBM Danmark A/S

SC32-1256-00