EQQI1mst

IBM Tivoli Workload Scheduler for z/OS

Installation GuideVersion 8.2

SC32-1264-00

NoteBefore using this information and the product it supports, read the information in Notices on page 211.

First Edition (June 2003)

This edition applies to version 8, release 2, modification 0 of IBM Tivoli Workload Scheduler for z/OS (programnumber 5697-WSZ) and to all subsequent releases and modifications until otherwise indicated in new editions.

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.

ContentsFigures . . . . . . . . . . . . . . vii

Tables . . . . . . . . . . . . . . . ix

Preface . . . . . . . . . . . . . . . xiWho Should Read This Manual . . . . . . . . xiWhat This Manual Contains . . . . . . . . . xiiPublications . . . . . . . . . . . . . . xiii

Publications for IBM Tivoli Workload Schedulerfor z/OS . . . . . . . . . . . . . . xiiiPublications for IBM Tivoli Workload Scheduler xivUsing LookAt to Look up Message Explanations xivAccessing Publications Online . . . . . . . xvSoftcopy Collection Kit . . . . . . . . . xvOrdering Publications . . . . . . . . . . xv

Accessibility . . . . . . . . . . . . . . xviContacting IBM Software Support . . . . . . xviConventions Used in This Manual . . . . . . xviWhat Is New in This Version . . . . . . . . xvi

z/OS Functions . . . . . . . . . . . . xviEnd-to-End Functions . . . . . . . . . xviiServer Connectivity . . . . . . . . . . xviii

How to Read Syntax Diagrams . . . . . . . xviii

Part 1. Planning . . . . . . . . . . 1

Chapter 1. Overview . . . . . . . . . 3Parts and Their Relationships . . . . . . . . . 3

Tracker . . . . . . . . . . . . . . . 3Controller . . . . . . . . . . . . . . 4Server . . . . . . . . . . . . . . . 4Data Store . . . . . . . . . . . . . . 5Configurations. . . . . . . . . . . . . 5

Controlling System . . . . . . . . . . 5Controlled Systems . . . . . . . . . . 5Integration with IBM Tivoli WorkloadScheduler . . . . . . . . . . . . . 6

Subtasks . . . . . . . . . . . . . . . . 6Relationship between the Scheduler and z/OS . . . 8Using the IBM Tivoli Workload Scheduler for z/OSProgram Directory . . . . . . . . . . . . 9Sample Library . . . . . . . . . . . . . 9The Installation Process . . . . . . . . . . . 9

Chapter 2. Planning Your Configuration 11Planning Considerations . . . . . . . . . . 11

Trackers . . . . . . . . . . . . . . 11Initialization Statements . . . . . . . . . 11Communication . . . . . . . . . . . . 12

Ways to Connect IBM Tivoli Workload Scheduler forz/OS Systems . . . . . . . . . . . . . 12

Shared DASD . . . . . . . . . . . . 12z/OS Cross-System Coupling Facility. . . . . 13VTAM (Network Communication Function) . . 13

TCP/IP. . . . . . . . . . . . . . . 13Workstation Destination . . . . . . . . . . 13Workload Restart . . . . . . . . . . . . 14JES Considerations . . . . . . . . . . . . 14Basic Server Configuration Example . . . . . . 15Basic Configuration Examples . . . . . . . . 16

DASD Connected . . . . . . . . . . . 17VTAM Connected . . . . . . . . . . . 18XCF Connected . . . . . . . . . . . . 19Tracker and Controller in a Single Address Space 21

Basic Data Store Configuration Examples . . . . 22SNA Only Connection . . . . . . . . . . 22XCF Only Connection . . . . . . . . . . 24Mixed SNA and XCF Connection . . . . . . 26

Part 2. Installing Tivoli WorkloadScheduler for z/OS . . . . . . . . 31

Chapter 3. Planning Your Installation 33Installation Considerations . . . . . . . . . 33

Configuring for Availability . . . . . . . . 33Hot Standby . . . . . . . . . . . . . 33Starting an Event Writer with an Event ReaderFunction . . . . . . . . . . . . . . 34Using a Hierarchical File System (HFS) Cluster 34

Checklist for Installing IBM Tivoli WorkloadScheduler for z/OS . . . . . . . . . . . . 34

Chapter 4. Installing . . . . . . . . . 41Step 1. Loading Tracker Software . . . . . . . 42Step 2. Loading Controller Software . . . . . . 43Step 3. Loading National Language SupportSoftware . . . . . . . . . . . . . . . 44Step 4. Using the EQQJOBS Installation Aid . . . 44

Setting Up the EQQJOBS Installation Aid . . . 44Creating the Sample Job JCL. . . . . . . . 45Generating Batch-Job Skeletons . . . . . . . 50Generating Data Store Samples . . . . . . . 55

Step 5. Adding SMF and JES Exits for EventTracking . . . . . . . . . . . . . . . 58

SMF Only . . . . . . . . . . . . . . 59JES2 Only . . . . . . . . . . . . . . 60JES3 Only . . . . . . . . . . . . . . 60

Step 6. Updating SYS1.PARMLIB . . . . . . . 60Defining Subsystems . . . . . . . . . . 60

Calculating MAXECSA Values . . . . . . 61Authorizing the Load-Module Library . . . . 62Updating SMF Parameters . . . . . . . . 63Updating z/OS Dump Options . . . . . . . 64Updating the z/OS Link-Library Definition. . . 65Updating XCF Initialization Options . . . . . 65Modifying TSO Parameters . . . . . . . . 66Performance Considerations . . . . . . . . 67Defining the DLF Exit for Hiperbatch Support. . 67

Copyright IBM Corp. 1991, 2003 iii

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

|||

||

||

||||||||

||

Starting the Product Automatically . . . . . 68Updating APPC Options . . . . . . . . . 68Implementing Support for Data Set Triggering. . 68

Step 7. Setting Up the RACF Environment . . . . 69Controlling the User ID of the Address Space . . 69Controlling the User ID of Submitted Jobs . . . 69

Normal Batch Jobs . . . . . . . . . . 70Batch Jobs . . . . . . . . . . . . . 70

Protecting Data Sets . . . . . . . . . . 70Controlling Access to Resources . . . . . . 71

Permitting Access to the Controller throughthe API . . . . . . . . . . . . . . 72

Controlling Access to IBM Tivoli WorkloadScheduler for z/OS Resources when Using IBMTivoli Workload Scheduler Job SchedulingConsole. . . . . . . . . . . . . . . 73

Permitting Access to the Controller throughthe IBM Tivoli Workload Scheduler JobScheduling Console. . . . . . . . . . 73

Authorizing IBM Tivoli Workload Scheduler forz/OS as a Job Submitter . . . . . . . . . 73Authorizing IBM Tivoli Workload Scheduler forz/OS to Issue JES Commands . . . . . . . 74

Step 8. Allocating Data Sets . . . . . . . . . 75Allocating the VSAM Data Sets . . . . . . . 77

Application Description Data set (EQQADDS) 80Current Plan Data sets (EQQCPnDS) . . . . 80Current Plan Backup Copy Dataset to CreateSymphony (EQQSCPDS) . . . . . . . . 81JCL Repository Data sets (EQQJSnDS) . . . 81

Allocating Restart and Clean Up VSAM DataSets . . . . . . . . . . . . . . . . 81

Restart and Clean Up Data Sets (EQQPKIxx,EQQSKIxx, and EQQSDFxx) . . . . . . . 82

Allocating Non-VSAM Data Sets . . . . . . 82Internal Reader Data Set (EQQBRDS) . . . . 84Checkpoint Data Set (EQQCKPT) . . . . . 84Diagnostic Data Sets (EQQDMSG, EQQDUMP,and SYSMDUMP) . . . . . . . . . . 85Event Data Set (EQQEVDS and EQQEVDnn) 86Job Library Data Set (EQQJBLIB) . . . . . 87Job-Completion-Checker Data Sets. . . . . 87Job-Tracking Data Sets (EQQJTARC, EQQJTnn,EQQDLnn) . . . . . . . . . . . . 88Message Log Data Set (EQQMLOG) . . . . 89Parameter Library (EQQPARM) . . . . . 90PIF Parameter Data Set (EQQYPARM) . . . 90Automatic-Recovery-Procedure Library(EQQPRLIB) . . . . . . . . . . . . 90End-to-end Script Library (EQQSCLIB) . . . 90Started-Task-Submit Data Set (EQQSTC) . . . 91Submit/Release Data Set (EQQSUDS) . . . 91End-to-end Centralized Script Data Set(EQQTWSCS). . . . . . . . . . . . 91End-to-end Input and Output Events DataSets (EQQTWSIN and EQQTWSOU) . . . . 92

Allocating Data Store Data Sets . . . . . . . 93Allocating the Files and Directories . . . . . 93

Step 9. Creating JCL Procedures for Address Spaces 94Implementing Support for Started-TaskOperations . . . . . . . . . . . . . 95

Required Data Sets . . . . . . . . . . . 96Optional Data Sets . . . . . . . . . . . 97

Step 10. Defining the Initialization Statements . . 100Step 11. Creating the DB2 Database . . . . . . 100

Sample to Migrate the History Database . . . 100Step 12. Setting Up the ISPF Environment . . . . 101

Setting Up the CLIST Library . . . . . . . 102Setting Up the ISPF Tables . . . . . . . . 102

Setting Up the Default DialogcontrollerConnection Table . . . . . . . . . . 102Setting Up List Tables and GraphicalAttribute Tables . . . . . . . . . . 103

Allocating Dialog Data Sets to Your TSO Session 103Invoking the IBM Tivoli Workload Scheduler forz/OS Dialog. . . . . . . . . . . . . 104

Using the EQQOPCAC Sample CLIST . . . 104Modifying an Existing ISPF Selection Menu 104Selecting the Main Menu Directly from TSO 105Using the ISPF Select Service . . . . . . 105

Step 13. Using XCF for Communication . . . . 105XCF Groups . . . . . . . . . . . . . 106XCF Run-Time Options . . . . . . . . . 107Initialization Statements Used for XCF . . . . 107

Step 14. Activating the Network CommunicationFunction . . . . . . . . . . . . . . . 107

Adding NCF to the VTAM Network Definitions 108Adding NCF Session Parameters . . . . . . 109

COS Table . . . . . . . . . . . . 109Activating Network Resources. . . . . . . 110Diagnostic Data Set . . . . . . . . . . 110

Step 15. Activating Support for the API. . . . . 110Defining VTAM Resources . . . . . . . . 111

Defining a Local LU . . . . . . . . . 111Defining Logon Modes . . . . . . . . 111Defining Cross-Domain Resources . . . . 112

Updating APPC Options. . . . . . . . . 112Activating Support for APPC . . . . . . . 113

Step 16. Activating Support for the Product Dialogand Programming Interface Using the Server . . . 113

Defining VTAM Resources for the ProductDialog and Program Interface Using the Server . 114Defining VTAM Resources for the Server . . . 114

Defining a Local LU for the Server . . . . 115Defining Logon Modes for the Server . . . 115

Updating APPC Options for the Server . . . . 116Defining VTAM Resources in a Parallel Sysplex 116Starting the Server. . . . . . . . . . . 117

Step 17. Activating Support for the End-to-endFeature . . . . . . . . . . . . . . . 117

Activating Server Support for the End-to-endFeature . . . . . . . . . . . . . . 117

Step 18. Activating Support for the IBM TivoliWorkload Scheduler Job Scheduling Console . . . 118

Activating Server Support for the IBM TivoliWorkload Scheduler Job Scheduling Console . . 118

Chapter 5. Verifying Your Installation 119Overview of Verification . . . . . . . . . . 119Verifying Installation of a Tracker. . . . . . . 119

Ensuring that All Installation Tasks AreComplete . . . . . . . . . . . . . . 120

iv IBM Tivoli Workload Scheduler for z/OS Installation Guide

|||

|||

||

||||||||

||

||||||

Checking the Message Log (EQQMLOG) . . . 120Verifying Tracking Events . . . . . . . . 121

The Event Writer . . . . . . . . . . 121The Event Data set . . . . . . . . . 121

Performing Problem Determination for TrackingEvents. . . . . . . . . . . . . . . 122

Verifying Installation of a Controller and Dialogs 125Ensuring that All Installation Tasks AreComplete . . . . . . . . . . . . . . 125Checking the Message Log (EQQMLOG) . . . 125Checking the Server Message Log . . . . . 126Checking Dialog Functions . . . . . . . . 126Performing Problem Determination . . . . . 127

Dialog Problems . . . . . . . . . . 127Authority Problems . . . . . . . . . 127

Verifying Installation of a Standby Controller. . . 128Ensuring that All Installation Tasks AreComplete . . . . . . . . . . . . . . 128Checking the Message Log (EQQMLOG) . . . 128

Verifying Installation of the Restart and CleanupFunction . . . . . . . . . . . . . . . 129

Checking the Message Log (EQQMLOG) . . . 130Verifying Configuration . . . . . . . . . . 131

Creating Entries in the Databases. . . . . . 131Running Batch Jobs . . . . . . . . . . 131Checking the Message Logs (EQQMLOG) . . . 131

Controller Message Log . . . . . . . . 131Tracker Message Log . . . . . . . . . 139

Verifying Workload Submission . . . . . . 142Controlling System . . . . . . . . . 142Controlled Systems . . . . . . . . . 142

Verifying Job Submission . . . . . . . . 143Verifying Takeover by a Standby Controller . . 144

Part 3. Migrating . . . . . . . . . 145

Chapter 6. Planning for Migration. . . 147Installation Considerations . . . . . . . . . 147Customization Considerations . . . . . . . . 147Migration Strategies . . . . . . . . . . . 148

JES and SMF Exits. . . . . . . . . . . 148Migrating to Existing Subsystem Definitions . . 148Migrating to New Subsystem Definitions . . . 149Getting the Right Software Parts . . . . . . 149

Load Modules . . . . . . . . . . . 149The ISPF environment . . . . . . . . 150

Migration Overview . . . . . . . . . . . 151Migration Overview . . . . . . . . . . 151Establishing the Required Environment. . . . 151Program Requirements . . . . . . . . . 151

Installation and Verification . . . . . . . . 151Parallel Testing . . . . . . . . . . . . . 152Migrating an End-to-end Network . . . . . . 153Migrating from a Tracker Agent to a DistributedAgent . . . . . . . . . . . . . . . . 153

Using the Tracker Jobs Migration Tool . . . . 154Migrating Backwards . . . . . . . . . . 155

Migrating DB2 . . . . . . . . . . . . . 156Running on Upgraded Operating Systems. . . . 156

Chapter 7. Migration Actions . . . . . 157Migrating Data Sets . . . . . . . . . . . 157

EQQICTOP VSAM Data Set ConversionProgram . . . . . . . . . . . . . . 158Data Sets that You Need to Convert . . . . . 161Data Sets that Can Be Used . . . . . . . 161Empty Data Sets . . . . . . . . . . . 161

Switching into Production Mode . . . . . . . 162Closing Down Your Production System. . . . 162Ensuring that LTP and NCP Data Sets AreCurrent . . . . . . . . . . . . . . 163Converting VSAM Files to the New SystemFormat . . . . . . . . . . . . . . 163Starting the New System . . . . . . . . 164Starting the New System in a Heavy WorkloadEnvironment . . . . . . . . . . . . 165Validating the New System. . . . . . . . 166

Performing Fallback . . . . . . . . . . . 166

Part 4. Appendixes . . . . . . . . 169

Appendix A. Accessibility . . . . . . 171Navigating the interface using the keyboard . . . 171Magnifying what is displayed on the screen . . . 171

Appendix B. Sample Library(SEQQSAMP) . . . . . . . . . . . 173Using the Visual Age Compiler . . . . . . . 177SMP/E Samples . . . . . . . . . . . . 178

Environment Setup . . . . . . . . . . 178RECEIVE Processing . . . . . . . . . . 178APPLY Processing . . . . . . . . . . . 179ACCEPT Processing . . . . . . . . . . 180

SMF Exits . . . . . . . . . . . . . . 180Exit Installation. . . . . . . . . . . . 181Job Step Termination Exit . . . . . . . . 181Initialization Exit . . . . . . . . . . . 181Record Write Exit . . . . . . . . . . . 181

JES Exits . . . . . . . . . . . . . . . 182Exit Installation. . . . . . . . . . . . 182JES2 JCT I/O Exit . . . . . . . . . . . 182JES3 OSE Modification Exit. . . . . . . . 182JES3 Input Service Final-User Exit . . . . . 182

RACF Samples . . . . . . . . . . . . . 183Class Descriptor Table . . . . . . . . . 183Router Table. . . . . . . . . . . . . 183

Sample Library (SEQQSAMP) . . . . . . . . 183

Appendix C. Configuration Examples 185The Controlling System . . . . . . . . . . 185Automatic Restart Actions . . . . . . . . . 185Initialization Statements . . . . . . . . . . 185Multi-Access Spool Systems Connected via SharedDASD . . . . . . . . . . . . . . . . 185Individual Systems Connected via Shared DASD 188A z/OS Sysplex . . . . . . . . . . . . 190A PLEX Configuration . . . . . . . . . . 193Controlling a z/OS System via a VTAM Link. . . 195Controlling a JES2 MAS System via a VTAM Link 196

Contents v

|||||

||

||

||||||

|||

||||||

||

Appendix D. Invoking the EQQEXITMacro. . . . . . . . . . . . . . . 199Invoking EQQEXIT in SMF Exits . . . . . . . 199Invoking EQQEXIT in JES Exits . . . . . . . 199

Macro Invocation Syntax for EQQEXIT . . . . 201

Appendix E. Invoking the EQQLSENTMacro. . . . . . . . . . . . . . . 203Invoking EQQLSENT to Create EQQDSLST . . . 203

Macro Invocation Syntax for EQQLSENT . . . 204

Appendix F. Hardware and SoftwareRequirements . . . . . . . . . . . 207Hardware Requirements. . . . . . . . . . 207

Software Requirements and Optional Software . . 208Controlling System . . . . . . . . . . 208Controlled OS/390 Systems . . . . . . . 208Optional Software . . . . . . . . . . . 208

Related Software . . . . . . . . . . . . 209Software Compatibility . . . . . . . . . . 209

Notices . . . . . . . . . . . . . . 211Trademarks . . . . . . . . . . . . . . 212

Glossary . . . . . . . . . . . . . 213

Index . . . . . . . . . . . . . . . 227

vi IBM Tivoli Workload Scheduler for z/OS Installation Guide

Figures1. A Basic Server Configuration Example . . . 152. A z/OS System Connected via Shared DASD 173. A z/OS System with a VTAM Connection 194. A z/OS System with an XCF Connection 205. A Tracker and Controller Configured in a

Single Address Space . . . . . . . . . 226. Controller and Tracker in Same Address Space

with Tracker Connected via SNA. . . . . . 237. Controller, Tracker, and Data Store Connected

via XCF . . . . . . . . . . . . . . 258. A Mixed SNA and XCF Connection . . . . 279. EQQJOBS0EQQJOBS Application Menu 45

10. EQQJOBS3Create Sample Job JCL . . . . 4511. EQQJOBS4Create Sample Job JCL . . . . 4612. EQQJOBS8Create Sample Job JCL . . . . 4813. EQQJOBS1Generate IBM Tivoli Workload

Scheduler for z/OS Batch-Job Skeletons . . . 5114. EQQJOBS2Generate IBM Tivoli Workload

Scheduler for z/OS Batch-Job Skeletons . . . 52

15. EQQJOBSAGenerate IBM Tivoli WorkloadScheduler for z/OS Batch-Job Skeletons . . . 53

16. EQQJOBS5Create Data Store Samples 5517. EQQJOBS6Create Data Store Samples 5618. EQQJOBS7Create Data Store Samples 5719. Sample Message Log for a Standby controller 12920. Sample Message Log for a Controller 13521. Sample Message Log for a Tracker . . . . 14122. Two z/OS JES2 MAS Complexes Connected

via Shared DASD . . . . . . . . . . 18623. Individual Systems Connected via Shared

DASD . . . . . . . . . . . . . . 18924. A z/OS Sysplex . . . . . . . . . . . 19125. An IBM Tivoli Workload Scheduler for z/OS

PLEX Environment . . . . . . . . . 19426. Controlling an z/OS System via a VTAM

Link . . . . . . . . . . . . . . 19527. Controlling a JES2 MAS System via a VTAM

Link . . . . . . . . . . . . . . 197

Copyright IBM Corp. 1991, 2003 vii

||

||||||||||

||

|||||||||||

viii IBM Tivoli Workload Scheduler for z/OS Installation Guide

Tables1. IBM Tivoli Workload Scheduler for z/OS

Subtasks . . . . . . . . . . . . . . 62. These Stages Summarize the IBM Tivoli

Workload Scheduler for z/OS InstallationProcess . . . . . . . . . . . . . . 10

3. Example EQQSERP Members for Figure 1 164. Example EQQPARM Members for Figure 2 185. Example EQQPARM Members for Figure 3 on

page 19 . . . . . . . . . . . . . . 196. Example EQQPARM Members for Figure 4 on

page 20 . . . . . . . . . . . . . . 217. Example EQQPARM Members for Figure 5 on

page 22 . . . . . . . . . . . . . . 228. Example Members for Figure 6 on page 23 249. Example Members for Figure 7 on page 25 26

10. Example Members for Figure 8 on page 27 2911. Checklist for Installing IBM Tivoli Workload

Scheduler for z/OS . . . . . . . . . . 3412. IBM Tivoli Workload Scheduler for z/OS

Installation Tasks. . . . . . . . . . . 4113. Tracker Libraries Loaded by SMP/E . . . . 4214. controller Libraries Loaded by SMP/E . . . 4315. NLS Libraries Loaded by SMP/E . . . . . 4416. Sample JCL Generated by the EQQJOBS

Dialog . . . . . . . . . . . . . . 4917. controller Skeleton JCL Generated by the

EQQJOBS Dialog. . . . . . . . . . . 5418. Data Store Samples Generated by the

EQQJOBS Dialog. . . . . . . . . . . 5819. Sample Exits for IBM Tivoli Workload

Scheduler for z/OS . . . . . . . . . . 5920. Examples of MAXECSA Storage Values 6221. Sample Library Members for Updating RACF

Tables . . . . . . . . . . . . . . 72

22. IBM Tivoli Workload Scheduler for z/OSVSAM Data sets . . . . . . . . . . . 77

23. Calculations of VSAM Data Set Size . . . . 7924. Restart and Clean Up VSAM data sets . . . 8125. IBM Tivoli Workload Scheduler for z/OS

Non-VSAM Data sets . . . . . . . . . 8226. Data Store VSAM data sets . . . . . . . 9327. Started task JCL samples for IBM Tivoli

Workload Scheduler for z/OS address spaces. . 9528. IBM Tivoli Workload Scheduler for z/OS

Required data sets . . . . . . . . . . 9629. IBM Tivoli Workload Scheduler for z/OS

Optional data sets . . . . . . . . . . 9830. ISPF and IBM Tivoli Workload Scheduler for

z/OS Dialog Data Sets . . . . . . . . 10331. Problem Determination for Missing Tracking

Events . . . . . . . . . . . . . . 12232. Recommended PTFs for Previous Versions of

IBM Tivoli Workload Scheduler for z/OS forJES2 EXIT7 . . . . . . . . . . . . 148

33. Data Sets that You Need to Convert . . . . 16134. Data Sets that IBM Tivoli Workload Scheduler

for z/OS Can Use . . . . . . . . . . 16135. SEQQSAMP Library Members . . . . . . 17336. Example EQQPARM Members for the

Previous Figure . . . . . . . . . . . 18737. Example EQQPARM Members for the

Previous Figure . . . . . . . . . . . 18938. Example EQQPARM Members for Figure 24

on page 191 . . . . . . . . . . . . 19239. Example EQQPARM Members for the

Previous Figure . . . . . . . . . . . 19440. Example EQQPARM Members for Figure 17 19641. Example EQQPARM Members for Figure 18 198

Copyright IBM Corp. 1991, 2003 ix

|||

||

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

|||

||||||||

|||

|||||||||||

x IBM Tivoli Workload Scheduler for z/OS Installation Guide

PrefaceInstallation Guide describes the configuration planning and installation tasks ofIBM Tivoli Workload Scheduler for z/OS. Installation is the task of making aprogram ready to do useful work. This task includes adding the materials on theIBM distribution tape to your system, initializing the program, and applying PTFsto the program. When you install a product, you are carrying out decisions youmade in the planning step. Customization, an optional step, gives you theopportunity to tailor the program to the desired behavior or special needs of yoursite.

Your workload can run on various platforms, but you control it from a centralz/OS system that runs the Tivoli Workload Scheduler for z/OS controller.

The term the scheduler, when used in this book, refers to Tivoli Workload Schedulerfor z/OS. The term DB2, when used in this book, also applies to DATABASE2and DB2 Universal Database.

The term z/OS is used in this manual to mean z/OS and OS/390 operatingsystems. Where the term OS/390 appears, the related information applies only toOS/390 operating systems.

This manual complements the IBM Tivoli Workload Scheduler for z/OS ProgramDirectory which covers adding the materials on the IBM distribution tape to yoursystem.

The Program Directory comes with the IBM Tivoli Workload Scheduler for z/OSinstallation tape. It describes all of the installation materials and gives installationinstructions specific to the product release level or feature number. If anydifferences exist between this manual and the Program Directory use theinformation in the Program Directory.

Who Should Read This ManualThis book is intended for system programmers who are responsible for software onan z/OS system and plan on installing IBM Tivoli Workload Scheduler for z/OS.

To use this book effectively, you must be familiar with the following topics:v Job control language (JCL)v IBM System Modification Program Extended (SMP/E)v z/OSv JES concepts and facilitiesv Writing small code fragments in the Assembler H languagev Interactive System Productivity Facility (ISPF)v Interactive System Productivity Facility/Program Development Facility

(ISPF/PDF)v Time-Sharing Option (TSO)v Virtual Storage Access Method (VSAM) (desirable but not essential)

Copyright IBM Corp. 1991, 2003 xi

|

|

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

The IBM Tivoli Workload Scheduler for z/OS Application Programming Interface(API) uses advanced program-to-program communication (APPC) services.Defining and configuring the conversation partners requires some knowledge ofAPPC services.

What This Manual ContainsThis manual contains the following sections:

Part 1, Planning

This part contains the following chapters:v Chapter 1, Overview, on page 3

Describes the IBM Tivoli Workload Scheduler for z/OS parts, subtasks, andintroduces the IBM Tivoli Workload Scheduler for z/OS configuration options.

v Chapter 2, Planning Your Configuration, on page 11Describes connections between IBM Tivoli Workload Scheduler for z/OS systemsand provides possible configurations to consider when planning yourinstallation.

Part 2, Installing Tivoli Workload Scheduler for z/OS

This part contains the following chapters:v Chapter 3, Planning Your Installation, on page 33

Offers considerations for the installation process and provides a checklist thatyou can use to perform the installation.

v Chapter 4, Installing, on page 41Guides you, step-by-step, through the installation process, from loading softwareto verifying that the product has been installed correctly.

v Chapter 5, Verifying Your Installation, on page 119Contains the installation verification process.

Part 3, Migrating

This part contains the following chapters:v Chapter 6, Planning for Migration, on page 147

Describes planning for migration.v Chapter 7, Migration Actions, on page 157

Guides you, step-by-step, through the conversion process to Version 8.2 fromearlier versions and releases of the product.

Part 4. Appendixes

This part contains the following appendixes:v Appendix A, Accessibility, on page 171

Describes the features that make the product and the documentation accessibleto users with physical disabilities, such as restricted mobility or limited vision.

v Appendix B, Sample Library (SEQQSAMP), on page 173Describes the members of the sample library.

v Appendix C, Configuration Examples, on page 185

xii IBM Tivoli Workload Scheduler for z/OS Installation Guide

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

Contains complex configuration examples for multiple systems and multipledata centers.

v Appendix D, Invoking the EQQEXIT Macro, on page 199Describes how you generate event-tracking code using the event-tracking-exitsmacro.

v Appendix E, Invoking the EQQLSENT Macro, on page 203Describes how to create a table of data set names that you want to monitor fordata set close.

v Appendix F, Hardware and Software Requirements, on page 207Lists the hardware and software prerequisites.

PublicationsThis section lists publications in the Tivoli Workload Scheduler for z/OS libraryand any other related documents. It also describes how to access Tivolipublications online, how to order Tivoli publications, and how to make commentson Tivoli publications.

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

Describes how to customize IBM 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 IBM Tivoli Workload Scheduler suite.

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

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

v IBM Tivoli Workload Scheduler Job Scheduling Console Users Guide, SC32-1257Provides information about working with IBM Tivoli Workload Scheduler,regardless of platform, from a common GUI.

v Licensed Program Specifications, GI11-4208Provides planning information to plan about IBM 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-4203

Preface xiii

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

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

Provided with the IBM 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 IBM Tivoli Workload SchedulerThe following manuals are available in the IBM Tivoli Workload Scheduler library:v IBM Tivoli Workload Scheduler Planning and Installation Guide, SC32-1273

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

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

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

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

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

v IBM Tivoli Workload Scheduler Limited Fault-tolerant Agent for AS/400 Users Guide,SC32-1280Describes installing, configuring, and using IBM Tivoli Workload Schedulerfault-tolerant agents on AS/400.

v IBM Tivoli Workload Scheduler Plus Module Users Guide, SC32-1276Explains setting up and using the IBM Tivoli Workload Scheduler Plus module.

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

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.

xiv IBM Tivoli Workload Scheduler for z/OS Installation Guide

|||||||

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

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

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 yourSK3T-4270 Collection Kit or from the LookAt Web sites 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 insoftcopy in the following collection kits:v IBM Online Library Omnibus Edition OS/390 Collection Kit, SK2T-6700.v IBM Online Library z/OS Software Products Collection Kit, SK2T-4270.

You can read the softcopy books on CD-ROMs using these IBM licensed programs:v Softcopy Readerv 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)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 PDF and HTML on the Web.

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

Preface xv

|||

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

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

||||||||

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

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

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.

For additional information, see Appendix A, Accessibility, on page 171.

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

Conventions Used in This ManualThe manual uses several typeface conventions for special terms and actions.Technical changes to the text are indicated by a vertical line to the left of thechange. These conventions 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, book titles

Italics Application

What Is New in This VersionThe following sections summarize the changes in this version of IBM TivoliWorkload Scheduler.

z/OS Functionsv 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 IBMTivoli Workload Scheduler.

xvi IBM Tivoli Workload Scheduler for z/OS Installation Guide

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

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

||||

v You can turn the JESLOG SPIN option on or off using the SPIN keyword in theOPCOPTS statement. By default IBM Tivoli Workload Scheduler 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, IBM Tivoli Workload

Scheduler operations now accept a new symbolic name that can be up to 54characters long. This operation extended name enables you to represent the jobwith something other than the operation number. You can specify the operationextended name when you define an operation in the database or when you copyit into the current plan. You can also use it to filter queries on operations in thedatabase 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 16 MB to 2 GB, the IBM Tivoli WorkloadScheduler components have been changed to use 31-bit addressing mode insteadof 24-bit.

End-to-End Functionsv For fault-tolerant workstations, you can continue to use centralized scripts,

which are stored in the JOBLIB data set. With centralized scripts, you canperform 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. IBM Tivoli Workload Schedulersupplied-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.

Preface xvii

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

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

v You can change the status of distributed agents and switch their domainmanager.

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.

Server Connectivityv 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.

How to Read Syntax DiagramsThroughout this book, syntax is described in diagrams like the one shown here,which describes the SRSTAT TSO command:

SRSTAT ' resource name 'OPCA

SUBSYS( subsystem name )MSTR

KEEP

AVAIL( RESET )NOYES

KEEPDEVIATION( amount )

RESET

KEEP

QUANTITY( amount )RESET

YESCREATE( NO )

0

TRACE( trace level )

The symbols have these meanings:

The statement begins here.

The statement is continued on the next line.

The statement is continued from a previous line.

The statement ends here.

xviii IBM Tivoli Workload Scheduler for z/OS Installation Guide

|||||||

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

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

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

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

||||||||||

Read the syntax diagrams from left to right and from top to bottom, following thepath of the line.

These are the conventions used in the diagrams:v Required items appear on the horizontal line (main path):

STATEMENT required item

v Optional items appear below the main path:

STATEMENToptional item

v An arrow returning to the left above the item indicates an item that you canrepeat. If a separator is required between items, it is shown on the repeat arrow.

STATEMENT '

,

repeatable item

v If you can choose from two or more items, they appear vertically in a stack. If you must choose one of the items, one item of the stack appears on the

main path:

STATEMENT required choice 1required choice 2

If choosing one of the items is optional, the entire stack appears below themain path:

STATEMENToptional choice 1optional choice 2

A repeat arrow above a stack indicates that you can make more than onechoice from the stacked items:

STATEMENT '

,

optional choice 1optional choice 2optional choice 3

STATEMENT '

,

required choice 1required choice 2required choice 3

v Parameters that are above the main line are default parameters:

Preface xix

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

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

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

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

||

|

STATEMENTdefault

alternative

v Keywords appear in uppercase (for example, STATEMENT).v Parentheses and commas must be entered as part of the command syntax, as

shown.v For complex commands, the item attributes might not fit on one horizontal line.

If that line cannot be split, the attributes appear at the bottom of the syntaxdiagram:

STATEMENT required choice 1option 1 option 2

required choice 2required choice 3

option 1

defaultoptional choice 1( alternative )

option 2

defaultoptional choice 2( alternative )

xx IBM Tivoli Workload Scheduler for z/OS Installation Guide

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

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

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

Part 1. PlanningChapter 1. Overview . . . . . . . . . . . 3Parts and Their Relationships . . . . . . . . . 3

Tracker . . . . . . . . . . . . . . . 3Controller . . . . . . . . . . . . . . 4Server . . . . . . . . . . . . . . . 4Data Store . . . . . . . . . . . . . . 5Configurations. . . . . . . . . . . . . 5

Controlling System . . . . . . . . . . 5Controlled Systems . . . . . . . . . . 5Integration with IBM Tivoli WorkloadScheduler . . . . . . . . . . . . . 6

Subtasks . . . . . . . . . . . . . . . . 6Relationship between the Scheduler and z/OS . . . 8Using the IBM Tivoli Workload Scheduler for z/OSProgram Directory . . . . . . . . . . . . 9Sample Library . . . . . . . . . . . . . 9The Installation Process . . . . . . . . . . . 9

Chapter 2. Planning Your Configuration . . . . 11Planning Considerations . . . . . . . . . . 11

Trackers . . . . . . . . . . . . . . 11Initialization Statements . . . . . . . . . 11Communication . . . . . . . . . . . . 12

Ways to Connect IBM Tivoli Workload Scheduler forz/OS Systems . . . . . . . . . . . . . 12

Shared DASD . . . . . . . . . . . . 12z/OS Cross-System Coupling Facility. . . . . 13VTAM (Network Communication Function) . . 13TCP/IP. . . . . . . . . . . . . . . 13

Workstation Destination . . . . . . . . . . 13Workload Restart . . . . . . . . . . . . 14JES Considerations . . . . . . . . . . . . 14Basic Server Configuration Example . . . . . . 15Basic Configuration Examples . . . . . . . . 16

DASD Connected . . . . . . . . . . . 17VTAM Connected . . . . . . . . . . . 18XCF Connected . . . . . . . . . . . . 19Tracker and Controller in a Single Address Space 21

Basic Data Store Configuration Examples . . . . 22SNA Only Connection . . . . . . . . . . 22XCF Only Connection . . . . . . . . . . 24Mixed SNA and XCF Connection . . . . . . 26

Copyright IBM Corp. 1991, 2003 1

|

|||

||

||

||||||||

2 IBM Tivoli Workload Scheduler for z/OS Installation Guide

Chapter 1. OverviewIBM Tivoli Workload Scheduler for z/OS can plan, control, and automate the entireproduction workload in your enterprise, not just the z/OS batch subset. Itautomatically plans, controls, and monitors your production workload to maximizethe throughput and optimize resource use, but lets you intervene manually whenrequired. If you are currently using previously supported versions, follow theinstructions in Part 3, Migrating, on page 145.

This chapter introduces IBM Tivoli Workload Scheduler for z/OS and itsimplementation. Later chapters describe the installation and migration tasks ingreater detail.

If you are not familiar with IBM Tivoli Workload Scheduler for z/OS terminologyor functions, read the General Information.

Parts and Their RelationshipsIBM Tivoli Workload Scheduler for z/OS consists of a base product, the agent, anda number of features. You need the base product to track the workload. Hereafter,you might see the agent referred to as the tracker and the engine referred to as thecontroller. One z/OS system in your complex is designated the controlling systemand runs the controller feature. Only one controller feature is required, even whenyou want to start standby controllers on other z/OS systems in a sysplex.

You can control work that runs on non-z/OS operating environments from acentral controller.

You need the appropriate fault-tolerant workstation and the end-to-end enablerfeature on the controlling system of the scheduler. Refer to IBM Tivoli WorkloadScheduler Planning and Installation Guide for a list of supported operatingenvironments.

The workload on other operating environments can also be controlled using theend-to-end scheduling functionality provided by IBM Tivoli Workload Schedulerfor z/OS and by IBM Tivoli Workload Scheduler.

Additionally, national language features let you see the IBM Tivoli WorkloadScheduler for z/OS ISPF dialogs in the language of your choice. These languagesare available:

EnglishGermanJapaneseSpanish

This section describes the tracker and controller, their relationship, and the ways inwhich you can configure them.

TrackerA tracker is required for every z/OS system in a IBM Tivoli Workload Schedulerfor z/OS configuration. The tracker handles the submission of jobs and tasks onthe system, and keeps track of the status of the workload. In conjunction with


||||||

||||

|||||||

standard interfaces to JES and SMF, IBM Tivoli Workload Scheduler for z/OSrecords the relevant information about the workload by generating event records.The event records are captured and stored by the tracker. The tracker thencommunicates event information to the controller for further processing. The logwhere events are written by the tracker is called the event data set.

IBM Tivoli Workload Scheduler for z/OS address spaces are defined as z/OSsubsystems. IBM Tivoli Workload Scheduler for z/OS routines that execute duringsubsystem initialization establish services that enable event information to begenerated and stored in common storage (ECSA) even when an address space isnot active.

You can optionally install a data store for each JES spool in a system. In a simpleJES configuration this would mean one data store for each tracker. In systems withshared spools (for example, JES2 MAS), there is a data store for each spool, andthere are fewer data stores than trackers.

ControllerThe controller is the focal point of your IBM Tivoli Workload Scheduler for z/OSconfiguration. It contains the controlling functions, the ISPF dialogs, the databases,and the plans. The system that the controller is started on is called the IBM TivoliWorkload Scheduler for z/OS controlling system. IBM Tivoli Workload Schedulerfor z/OS systems that communicate with the controlling system are calledcontrolled, or tracker systems. You need to install at least one controller for yourproduction systems. It can control the entire IBM Tivoli Workload Scheduler forz/OS configuration, the OPCplex, both local and remote.

You can use the controller to provide a single, consistent, control point forsubmitting and tracking the workload on any operating environment. IBM TivoliWorkload Scheduler for z/OS provides distributed agents and open interfaces thatenable you to integrate the planning, scheduling, and control of work units such asonline transactions, file transfers, or batch processing in any operating environmentthat can communicate with z/OS.

ServerIBM Tivoli Workload Scheduler for z/OS provides a server that enables you toaccess the controller remotely from ISPF dialogs, PIFs, and from the IBM TivoliWorkload Scheduler Job Scheduling Console interface. Connections with the serverrun through advanced program-to-program communications APPC sessions, or justfor the IBM Tivoli Workload Scheduler Job Scheduling Console using TCP/IPconnections. The server runs in its own address space; however, it is optional ifyou do not access the controller remotely.

The server is also used to communicate with the distributed agents for theend-to-end feature.

A Started Task JCL enables you to start and stop one or more servers eitherindividually, using the Start and Stop operator commands, or automatically withthe controller, using a keyword in the OPCOPTS statement. A server must start onthe same z/OS image as its controller. Only one server can be started with theend-to-end feature active.

The PIF dialog connection to the controller, whether via server or subsysteminterface, is only allowed when the code is at the same level on both sides of theinterface.


||||||

|||||||

Data StoreData store is a separate address space. Its function is to collect structured (stepsand data sets) and, optionally, unstructured (SYSOUT) information for allsubmitted jobs.

Data store is required in order to use the restart and cleanup functions:v Restart at the job or step levelv Data set clean upv JOBLOG retrieval

The controller can be connected to data store via XCF or SNA.

ConfigurationsYou can configure IBM Tivoli Workload Scheduler for z/OS to control virtually anycombination of operating environments. IBM Tivoli Workload Scheduler for z/OScan automatically schedule, submit, and track batch jobs, started tasks, andwrite-to-operator (WTO) messages. You can also use IBM Tivoli WorkloadScheduler for z/OS to coordinate manual activities in your production workload.

Your IBM Tivoli Workload Scheduler for z/OS configuration can include:v A controlling systemv Controlled systems:

Local and remote controlled z/OS systems, including a parallel sysplex Standby controller systems Previous OPC Releases. Controlled systems that run on distributed agents. Other operating environments that do not support the distributed agents.

Chapter 2, Planning Your Configuration, on page 11 explains connectionsbetween IBM Tivoli Workload Scheduler for z/OS systems and shows examples ofconfigurations.

Controlling SystemA controlling IBM Tivoli Workload Scheduler for z/OS system requires both atracker and a controller. If you install only one IBM Tivoli Workload Scheduler forz/OS system, this is the controlling system. The controlling IBM Tivoli WorkloadScheduler for z/OS system can communicate with controlled z/OS systems usingshared DASD, the cross-system coupling facility (XCF), and the networkcommunication function (NCF).

Controlled SystemsA controlled z/OS system requires a tracker. Communication with the controllingsystem is through shared DASD, XCF, or NCF. The tracker writes event records toan event data set, and transfers the records to the controlling system if connectedvia XCF or NCF. NCF uses ACF/VTAM to link IBM Tivoli Workload Scheduler forz/OS systems.

If you use XCF for communication, you can include a standby controller on one ormore controlled systems. A standby controller is started in its own address space.It can take over the functions of the controller if z/OS fails or if the controller itselffails. It cannot perform the functions of a tracker while in standby mode.

Chapter 1. Overview 5

||||||||

||

||||||

You can use IBM Tivoli Workload Scheduler for z/OS to control workloads onoperating environments that have the end-to-end feature. Controlled systemsconnect to the controlling system using advanced program-to-programcommunication (APPC) services.

The controller can also control the workload in other operating environments, suchas VM/ESA. The Customization and Tuning publication describes in detailcontrolling other operating environments.

Integration with IBM Tivoli Workload SchedulerThe end-to-end feature is based on the Common Agent Technology and it enablesIBM Tivoli Workload Scheduler for z/OS to be the master of a IBM TivoliWorkload Scheduler distributed network. This configuration is implemented byconnecting a IBM Tivoli Workload Scheduler domain manager directly to IBMTivoli Workload Scheduler for z/OS.

IBM Tivoli Workload Scheduler for z/OS receives events from the IBM TivoliWorkload Scheduler distributed network and updates the current plan (CP)according to these events. Conversely, every time the current plan is updated, anevent is sent to the distributed network to update local plans on the distributedagents.

Being fault-tolerant, the distributed agents can independently carry on withscheduling when communications with IBM Tivoli Workload Scheduler for z/OSare interrupted due to network problems. At the same time, the distributed agentsare prevented from acting on IBM Tivoli Workload Scheduler for z/OS jobs sincethese are viewed as running on the Master that is the only node that has theauthorization to operate on those jobs.

A new type of CPU, named fault-tolerant workstation, is added to IBM TivoliWorkload Scheduler for z/OS to logically define in the database and in the planthe distributed agents that will be running jobs for IBM Tivoli Workload Schedulerfor z/OS.

SubtasksA IBM Tivoli Workload Scheduler for z/OS address space consists of many z/OSsubtasks. Some of these subtasks are always attached when the IBM TivoliWorkload Scheduler for z/OS address space is started, others are conditionallyattached according to initialization parameters specified for the scheduler options(OPCOPTS) statement in the IBM Tivoli Workload Scheduler for z/OS parameterlibrary. The following table describes the subtasks.

Table 1. IBM Tivoli Workload Scheduler for z/OS Subtasks

SubtaskID

Componentcode Description

Component ofFMID

Activated byOPCOPTSparameter Function

APPC PP APPCfunctions

JWSZ202 APPCTASK(YES) Starts APPC support

AR AR Automaticrecovery

JWSZ202 RECOVERY(YES) Manages failing operations

DRT DX Data router HWSZ200 Always activated Routes data to other subtasks orIBM Tivoli Workload Schedulerfor z/OS subsystems

EMGR EM Event manager JWSZ202 OPCHOST(YES) Processes job-tracking events


||||

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

||

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

|||||||

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

Table 1. IBM Tivoli Workload Scheduler for z/OS Subtasks (continued)

SubtaskID

Componentcode Description

Component ofFMID

Activated byOPCOPTSparameter Function

ERDR ER Event reader HWSZ200 ERDRTASK(n) Reads events from an event dataset

EWTR EW Event writer HWSZ200 EWTRTASK(YES) Writes events to an event dataset

EXA EX External router JWSZ202 OPCHOST(YES) Calls EQQUX009 to routesubmit requests to auser-defined destination ID

FL FL Fetch joblog JWSZ202 RCLEANUP(YES) Retrieves JOBLOG information

GEN GS General service JWSZ202 OPCHOST(YES) Processes IBM Tivoli WorkloadScheduler for z/OS dialogrequests

JCC JC Job completionchecker

HWSZ200 JCCTASK(YES) Scans SYSOUT data sets

JLA JL JT log archiver JWSZ202 OPCHOST(YES) Copies JT logs to the archivedata set, EQQJTARC

NMM NM Normal modemanager

JWSZ202 OPCHOST(YES) Maintains the current plan

PSU PS Pre-SUBMITtailoring

JWSZ202 RCLEANUP(YES) Tailors the JCL beforesubmitting ti by adding theEQQCLEAN pre-step

RODM RM RODMsupport

HWSZ200 RODMTASK (YES) Starts RODM support

SUB SU Submit task HWSZ200 Always activated Initiates work (job submit, jobrelease, and WTO and STCoperations)

TA TA TCP/IP router JWSZ202 TCP keyword ofROUTOPTS

Handles communications withTCP/IP-connected trackeragents

TWS TWS End-to-endtask

JWSZ202 TPLGYSRV andkeyword ofOPCOPTS

Handles events to and fromfault-tolerant workstations(using the IBM Tivoli WorkloadScheduler for z/OS server)

VTAM CB Networkcommunicationfunction (NCF)

HWSZ200 NCFTASK(YES) Transmits/receives IBM TivoliWorkload Scheduler for z/OSdata through a VTAM link

WSA WA Workstationanalyzer

JWSZ202 OPCHOST(YES) Schedules work for processing

Note: The subtask ID is the same identifier used to control the subtask using the z/OS MODIFY command.

When a controller is started in standby mode, only the IBM Tivoli WorkloadScheduler for z/OS main task (EQQMAJOR) is started. The subtasks that comprisean active controller are attached when a takeover is performed.


|

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

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

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

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

||

Relationship between the Scheduler and z/OSIBM Tivoli Workload Scheduler for z/OS is a z/OS subsystem, initialized duringIPL. Routines executed during subsystem initialization establish basic IBM TivoliWorkload Scheduler for z/OS services, such as an event queue in ECSA. IBMTivoli Workload Scheduler for z/OS uses standard interfaces to SMF and JES togather relevant information about the workload on the z/OS system.

The functions of the controller are available when an address space has beencreated for it, and the required subtasks have been successfully initialized. Thecontroller can execute either as a started task or batch address space. Normally, theaddress space is started during the IPL process, that is by a z/OS start commandin COMMNDnn, or by console automation. Alternatively, a z/OS operator canissue a START command from the operator console. The z/OS operator can alsostop or modify the IBM Tivoli Workload Scheduler for z/OS address space, usingthe STOP and MODIFY commands.

A TSO user accesses IBM Tivoli Workload Scheduler for z/OS services using theIBM Tivoli Workload Scheduler for z/OS dialogs. An IBM Tivoli WorkloadScheduler for z/OS dialog is a sequence of ISPF panels. Many of the functionssupported by the IBM Tivoli Workload Scheduler for z/OS dialogs pass servicerequests from the TSO users address space to the controller address space forprocessing.

Before performing any function requested by an IBM Tivoli Workload Schedulerfor z/OS user, the dialog function passes the request to the system authorizationfacility (SAF) router. If RACF, or a functionally equivalent security product, isinstalled and active on the z/OS system, the SAF router passes the verificationrequest to RACF to perform this authority check.

A typical request for service from the dialog is a request for access to one or morerecords in VSAM files that are maintained and controlled by IBM Tivoli WorkloadScheduler for z/OS. Such a request is passed to IBM Tivoli Workload Scheduler forz/OS through the z/OS subsystem interface (SSI). This interface invokes an IBMTivoli Workload Scheduler for z/OS routine that resides in common storage. Thisroutine must be invoked in APF-authorized mode.

Consider that all long term plan (LTP) and CP batch planning jobs have to beexcluded from SMARTBATCH DA (Data Accelerator) processing. When theSMARTBATCH DATA ACCELERATOR is used with the scheduler LTP and CPbatch planning jobs, the normal I/O to EQQCKPT is delayed until END OF JOB(or at least END OF JOBSTEP). This interferes with the normal exchange of databetween the batch job and the controller started task so that when the batch jobsignals the controller to check the EQQCKPT to determine whether a new currentplan has been created, the required updates to the CKPT have not yet been made.This causes the controller to conclude that no NCP has been created, and noturnover processing is done. As a result, even if the plan jobs run successfully, theNCP is not taken into production by the controller unless a CURRPLAN(NEW)restart is performed.

The data store uses the MVS/JES SAPI functions to access sysout data sets,allowing concurrent access to multiple records from a single address space.

Batch optimizer utilities, such as BMC Batch Optimizer Data Optimizer andMainview Batch Optimizer, prevent correct communication between theschedulers controller and CP/LTP batch planning jobs. The schedulers logic


||||||

|||||

depends on an exchange of enqueues and real-time updates of several sequentialdata sets to pass information back and forth between the controllers STC and theCP/LTP batch planning jobs. These optimizers hold I/O from the batch jobs untilEND OF STEP or END OF JOB, then preventing the required communication fromtaking place. When such utilities are allowed to manage I/O for the schedulersCP or LTP batch planning jobs, communication between the jobs and the controlleris disrupted. This causes numerous problems that are hard to diagnose. Mostcommonly, the CURRENT PLAN EXTEND or REPLAN jobs will run to normalcompletion, and an NCP data set will be successfully created, but the controllerwill fail to automatically take the new plan into production until it is forced to doso via a CURRPLAN(NEW) restart of the CONTROLLER. Use of BATCHPIPESwith these batch planning jobs will result in the same sorts of problems.

Using the IBM Tivoli Workload Scheduler for z/OS Program DirectoryThe Program Directory provided with your IBM Tivoli Workload Scheduler forz/OS distribution tape may include technical information that is more recent thanthe information provided in this guide. In addition, the Program Directory describesthe program temporary fix (PTF) level of the IBM Tivoli Workload Scheduler forz/OS licensed program that is shipped to you. It is an important document whenyou install IBM Tivoli Workload Scheduler for z/OS.

The Program Directory contains instructions for unloading the IBM Tivoli WorkloadScheduler for z/OS software and information about additional maintenance foryour level of the distribution tape.

Before you start installing IBM Tivoli Workload Scheduler for z/OS, check thepreventive service planning (PSP) bucket for recommendations added by the serviceorganizations after your Program Directory was produced. The PSP includes aService Recommendations section that includes high impact or pervasive (HIPER)APARs. Ensure the corresponding PTFs are installed before you start a IBM TivoliWorkload Scheduler for z/OS subsystem.

Sample LibraryTake special note of one of the files included on the distribution tape. SEQQSAMPis a library containing samples of exits, application programs, and the job controllanguage (JCL). You can use the samples for specific installation tasks. Appendix B,Sample Library (SEQQSAMP), on page 173 describes the members of theSEQQSAMP library. Familiarize yourself with the contents of the SEQQSAMPlibrary before you begin installation.

The Installation ProcessTo understand the flow of the installation, migration, and customization processes,read through this guide before you begin to install IBM Tivoli Workload Schedulerfor z/OS.

Here is the installation process:


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

Table 2. These Stages Summarize the IBM Tivoli Workload Scheduler for z/OS Installation ProcessStage Description For more information ...

1 Plan your configuration. You might create adiagram of your own IBM Tivoli WorkloadScheduler for z/OS configurationto refer toduring the installation process.

Chapter 2, Planning Your Configuration givesexamples of common IBM Tivoli WorkloadScheduler for z/OS configurations.

2 Plan your software installation. Chapter 3, Planning Your Installation describesconsiderations for installing IBM Tivoli WorkloadScheduler for z/OS and provides a checklist for theinstallation tasks.

3 Install the software. Chapter 4, Installing describes the installationtasks in detail.

4 Verify your IBM Tivoli Workload Scheduler forz/OS installation.

Chapter 5, Verifying Your Installation describeshow you can verify that IBM Tivoli WorkloadScheduler for z/OS is correctly installed.

When you have installed IBM Tivoli Workload Scheduler for z/OS, you mightwant to include more functions. Customization and Tuning explains how to updateyour IBM Tivoli Workload Scheduler for z/OS systems to include extra functions.


|||

Chapter 2. Planning Your ConfigurationThis chapter describes several areas to consider when planning the configurationfor your installation. It explains connections between IBM Tivoli WorkloadScheduler for z/OS systems and provides some examples of basic IBM TivoliWorkload Scheduler for z/OS configurations. Refer to Customization and Tuning fordetails on how to configure end-to-end scheduling in distributed environment.

Planning ConsiderationsIBM Tivoli Workload Scheduler for z/OS must recognize when events occur; forexample, when a started task or job begins to execute or terminates, or when adata set has been printed. IBM Tivoli Workload Scheduler for z/OS uses JES andSMF exits to obtain this information from z/OS and to create event recordsdescribing the changes in the system. The event records are stored in a sequentialfile called the event data set identified by the EQQEVDS DD name.

IBM Tivoli Workload Scheduler for z/OS also uses the event data set to writecheckpoint information for submission requests. The first record of the data set isused for this purpose. So the EQQEVDS DD name must be specified for all IBMTivoli Workload Scheduler for z/OS address spaces. The same data set can be usedfor both submit checkpointing and the event-writer subtask.

TrackersA tracker must be installed on every z/OS system that you want IBM TivoliWorkload Scheduler for z/OS to control. The tracker on each IBM Tivoli WorkloadScheduler for z/OS system writes events to the event data set. A subtask of thetracker, called the event writer performs this function. For the IBM Tivoli WorkloadScheduler for z/OS current plan to be updated, the event information must becommunicated to, and processed by, the controller. The events are routed to thecontroller through the connection linking the tracker and the controller, either byan event reader subtask, or by requesting the event writer to queue the eventsimmediately to the data router subtask, when the connected type is not sharedDASD.

Initialization StatementsIBM Tivoli Workload Scheduler for z/OS initialization statements specified in theIBM Tivoli Workload Scheduler for z/OS parameter library describe, among otherthings, the configuration of your installation. In a shared DASD environment, anevent reader subtask started at the controller reads the events from the event dataset. The events are then used to update the current plan. A sequence number,specified on the ERSEQNO of the ERDROPTS initialization statement, identifieseach event reader subtask. This number is used to build a DD name in the JCLprocedure of the address space where the event reader is started. This DD nameidentifies the event data set that the event reader should process. The DD namehas the format EQQEVDnn, where nn is the sequence number of the event readerthat services this event data set.

When a tracker has a non-DASD connection with the controller (that is, an XCF orNCF connection) or the tracker and controller are executing in the same addressspace, the event writer can be used to forward events directly to the controller.When an event writer is started with the EWSEQNO keyword on the EWTROPTS


|||||

initialization statement, the event writer logs event information on the event dataset and adds the event concurrently to the data router queue. The event is not readback from the event data set each time as it is by an event reader subtask. In thisconfiguration, events are only read back from DASD if they need to be resent tothe controller during restart processing, for example when the communication linkto the controller becomes active after an outage.

Refer to Customization and Tuning for more information on the ERDROPTS andEWTROPTS initialization statements. Also see ,Event Data Set (EQQEVDS andEQQEVDnn) on page 86 which provides important information about allocatingevent data sets.

CommunicationThe data router subtask is responsible for communicating the event to thecontroller event manager subtask, either by XCF, NCF, or by adding directly to thequeue when the tracker and controller are started in the same address space. Thiseliminates the need for a separate event-reader function, saves time, and saves I/Ooperations. The EWSEQNO value is not used to build a DD name, as happenswith the event reader subtask. The event writer uses the EQQEVDS DD name toidentify the event data set.

If a connection is lost between a tracker and the controller, the event writercontinues to record events. When the connection is restored, the event data set isprocessed from the last event received by the controller before the outage.

Note that controllers scheduling work (for a given MVS image) must have uniquesubsystem names.

Ways to Connect IBM Tivoli Workload Scheduler for z/OS SystemsIBM Tivoli Workload Scheduler for z/OS systems can be connected through any ofthese methods:v Shared DASDv XCF communication linksv VTAM link

The IBM Tivoli Workload Scheduler for z/OS controller uses any of these methodsto transmit work to a tracker system. The tracker system uses the same connectionto transmit events back to the controller.

Distributed agents communicate with the controller using TCP/IP services.

Shared DASDWhen two IBM Tivoli Workload Scheduler for z/OS systems are connectedthrough shared DASD, they share two data sets for communication:v Event data setv Submit/release data set

The tracker writes the event information it collects to the event data set. An eventreader, started in the controller, reads the data set and adds the events to the datarouter queue.

A submit/release data set is one method that the controller uses to pass work to acontrolled system. When two IBM Tivoli Workload Scheduler for z/OS systemsshare a submit/release data set, the data set can contain these records:


|

v Release commandsv Job JCLv Started-task JCL proceduresv Data set cleanup requestsv WTO message textBoth the host and the controlled system must have access to the submit/releasedata set. The EQQSUDS DD name identifies the submit/release data set in thetracker address space. At the controller, the DD name is user-defined, but it mustbe the same name as that specified in the DASD keyword of the ROUTOPTSstatement. The controller can write to any number of submit/release data sets.

z/OS Cross-System Coupling FacilityIBM Tivoli Workload Scheduler for z/OS uses the z/OS cross-system couplingfacility (XCF), introduced in MVS/ESA SP Version 4, to connect IBM TivoliWorkload Scheduler for z/OS systems using XCF communication links.

When one or more trackers are connected to the controller via XCF communicationlinks, the IBM Tivoli Workload Scheduler for z/OS systems form an XCF group.The systems use XCF group, monitoring, and signaling services to communicate.The controller submits work and control information to the trackers using XCFsignaling services. The trackers use XCF services to transmit events back to thecontroller.

XCF connections let IBM Tivoli Workload Scheduler for z/OS support a hotstandby controller and automatic-workload-restart functions.

VTAM (Network Communication Function)IBM Tivoli Workload Scheduler for z/OS uses the network communicationfunction (NCF) to connect a tracker to the controller using a VTAM link. Thecontroller transmits work to the tracker via NCF, and the same connection is usedto pass back event information.

TCP/IPIBM Tivoli Workload Scheduler for z/OS uses TCP/IP to connect a distributedagent to the server. The controller transmits work to the tracker or to thefault-tolerant workstation via TCP/IP, and the same connection is used to passback event information. The TCP/IP connection between the server and the agentsis established by the server.

Workstation Destination

The various physical and logical locations where tasks are performed at yourinstallation are represented in IBM Tivoli Workload Scheduler for z/OS byworkstations. Each workstation groups related activities. Every operation in theapplication description database and the current plan is associated with aworkstation. You define workstations in the workstation description database.

The destination field is one attribute of a workstation description. It identifies thesystem in your IBM Tivoli Workload Scheduler for z/OS configuration thatoperations scheduled for this workstation should be submitted to. The field cancontain either the DD name of a submit/release data set, an XCF member name,the VTAM LU of a tracker, or a user-defined destination.

Chapter 2. Planning Your Configuration 13

||||||

If the destination field is not blank, the same name must also be present in theAPPC, DASD, SNA, TCP, USER, or XCF keywords of the ROUTOPTS statement,depending on the connection method.

The destination field can also remain blank. A blank destination field means thatoperations at this workstation will be submitted by the controller or by afault-tolerant agent, whose workstation type is FTA.

The operation-initiation exit, EQQUX009, handles routing of the workload touser-defined destinations.

Workload RestartYou can use workload restart (WLR) to restart and reroute work in your IBM TivoliWorkload Scheduler for z/OS configuration. WLR tracks the status ofworkstations. It can be invoked when a workstation becomes inactive; that is,when the controller cannot communicate with the tracker at the destination thatthe workstation represents. If an operation is restartable, it can be started again byIBM Tivoli Workload Scheduler for z/OS after a workstation failure. If anoperation is reroutable, it can be moved to an alternative workstation for executionwhen its workstation is no longer active.

For WLR purposes, the status of a workstation can be either active or inactive. Aninactive workstation has a status of offline, failed, or unknown. The actions thatWLR performs depend on the new status of the workstation and on the values youspecify on the WSFAILURE and WSOFFLINE keywords of the JTOPTSinitialization statement. The inactive status that a workstation can have depends onthe type of connection between the tracker and the controller. The connection typeand the new workstation status determine whether workload restart actions can beinvoked automatically. You can use the full capabilities of WLR on systems that areconnected by XCF.

Note: JES also has restart functions, which can be used when the system isrestarted after a failure. JES can restart jobs that were active when the failureoccurred. To prevent jobs from being started twice, ensure that both JES andWLR do not perform restart actions for jobs on the failing system.

JES ConsiderationsThe JES type and configuration in your installation has implications on your IBMTivoli Workload Scheduler for z/OS configuration. Consider these situations:1. On systems where JES2 is installed, a IBM Tivoli Workload Scheduler for z/OS

Tracker must be installed on each system in the JES2 Multi-Access Spool (MAS)complex.

2. If you do not install IBM Tivoli Workload Scheduler for z/OS on all systems ina JES3 complex, ensure that:v A tracker is installed on the global.v Jobs are submitted, whether by IBM Tivoli Workload Scheduler for z/OS or

outside IBM Tivoli Workload Scheduler for z/OS, to a system where atracker is installed. Use the //*MAIN SYSTEM=sysid statement in the JCL, orstart job classes used by these jobs only on those systems where a tracker isinstalled.

v If you track print operations, output is printed only on those systems wherea tracker is installed.


|||

|||

Basic Server Configuration ExampleThis section gives an example of a basic server configuration of IBM TivoliWorkload Scheduler for z/OS. IBM Tivoli Workload Scheduler for z/OS connectsdistributed agents to the server via TCP/IP. The controller transmits work to thefault-tolerant workstations via TCP/IP, and the same connection is used to passevent information back. The server is connected to the first level domain managersin the distributed network. TCP/IP is also used to connect the Job SchedulingConsoles to the server through the connector. The server connects to the remoteinterfaces, either Programming Interfaces or remote ISPF interface users, usingAPPC. The following example shows a simple configuration using mixed protocolsand minimal parameter customization.

Table 3 shows the initialization statements you can use to create the configurationin Figure 1.

JSC

Key:E2E End-to-endJSC Job Scheduling Console

E2EEvent

Data sets

Controller

E2EEnabler

APPC

Server

TCP/IPISPF

orProgramming

Interface

Connector

JSC JSC

Subsystem Interface

DistributedEnvironment

Figure 1. A Basic Server Configuration Example


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

||

Table 3. Example EQQSERP Members for Figure 1

EQQSERP

SERVOPTS SUBSYS(OPCA)USERMAP(USERS)PROTOCOL(E2E,JSC,APPC)

TPLGYPRM(TPLGY)

INIT CALENDAR(DEFAULT)

TPLGY

TOPOLOGY TPLGYMEM(TPLGYDOM)BINDIR(/usr/lpp/TWS8.2.0)WRKDIR(/var/TWS/OPCA)USRMEM(TPLGYUSR)CODEPAGE(IBM-280)

TPLGYUSR

USRREC USRCPU(FTW1)USRNAM(tws82)USRPSW(tws82)

TPLGYDOM

DOMREC DOMAIN(DOM0)DOMMNGR(FTW1)DOMPARENT(MASTERDM)

CPUREC CPUNAME(FTW1)CPUOS(WNT)CPUNODE(xxx.xx.xxx.x)CPUDOMAIN(DOM0)CPUTYPE(FTA)CPUTCPIP(31111)CPUFULLSTAT(ON)CPUAUTOLNK(ON)CPULIMIT(SYSTEM)FIREWALL(NO)CPUTZ(EUT)

Note: For USERS members, see the SERVOPTS USERMAP parameter, and for the TPLGYmembers, see the TOPOLOGY statement in Customization and Tuning.

Basic Configuration ExamplesThis section gives examples of IBM Tivoli Workload Scheduler for z/OSconfigurations using the various connection methods. The examples are based on asingle-image z/OS environment. Appendix C, Configuration Examples, onpage 185 contains examples of more complex configurations.

The examples in this section show:v All IBM Tivoli Workload Scheduler for z/OS address spaces as Version 2

subsystems.v Sample initialization statements that you can use to create the configuration.

Only initialization statements that specifically relate to the configuration areincluded.

v The IBM Tivoli Workload Scheduler for z/OS components that are required, theflow of automatic work submission, and event collection in various systemcombinations.


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

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

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

DASD ConnectedFigure 2 shows two IBM Tivoli Workload Scheduler for z/OS address spaces witha DASD connection on a z/OS system.

You represent this system to IBM Tivoli Workload Scheduler for z/OS by defininga computer workstation with a destination field that specifies a submit/release DDname. The controller writes JCL, release commands, WTO messages, and cleanuprequests into the submit-release data set. The tracker reads the submit-release dataset and performs the following actions:v Submits JCL for batch jobs to the JES internal readerv Writes the JCL for started tasks into the EQQSTC data set and issues START

procname z/OS commandsv Issues JES release commands for jobs in HOLD statusv Submits the cleanup job.

The event-tracking routines create event records to describe activities that occur onthe system. These records are added to the tracker event writer queue in ECSA.The tracker processes the queue and writes the events into the event data set. Anevent-reader subtask started in the controller address space reads the event dataset, and the current plan is updated.

You can also configure this system without a submit-release data set. When theworkstations destination is blank; batch jobs, started tasks, release commands, andWTO messages, are processed by the submit subtask automatically started in thecontroller address space. The event-tracking process remains unchanged.


Figure 2. A z/OS System Connected via Shared DASD


Table 4. Example EQQPARM Members for Figure 2Members for the controller Members for the tracker

OPCECNT

OPCOPTS OPCHOST(YES)ERDRTASK(1)ERDRPARM(STDERDR)

ROUTOPTS DASD(EQQSYSA)

TRKA

OPCOPTS OPCHOST(NO)ERDRTASK(0)EWTRTASK(YES)EWTRPARM(STDEWTR)

TRROPTS HOSTCON(DASD)

STDERDR

ERDROPTS ERSEQNO(01)

STDEWTR

EWTROPTS SUREL(YES)

Note: In this example, EQQSYSA is used for the user-defined DD name of thesubmit/release data set. This DD name appears in the JCL procedure of the controller andin the destination field of the workstation.

VTAM ConnectedFigure 3 on page 19 shows two IBM Tivoli Workload Scheduler for z/OS addressspaces with a VTAM connection on a z/OS system.

You represent this system to IBM Tivoli Workload Scheduler for z/OS by defininga computer workstation with a destination field that specifies the LU name of thetracker. The controller transmits JCL, release commands, WTO messages, andcleanup requests across the LU-LU link using the NCF component. The trackerreceives data across the VTAM link and and performs the following actions:v Submits JCL for batch jobs to the JES internal readerv Writes the JCL for started tasks into the EQQSTC data set and issues START

procname z/OS commandsv Issues JES release commands for jobs in HOLD statusv Submits the cleanup job.

The event-tracking routines create event records to describe activities that occur onthe system. These records are added to the tracker event writer queue in ECSA.The tracker processes the queue, transmits the records to the controller across theVTAM link, and writes the events into the event data set. The VTAM subtask inthe controller receives the event records, and the current plan is updated.

Note: You must specify EQQEVDS for a controller, even if an event writer is notstarted in the controller address space. The EQQEVDS data set is used forsubmit checkpointing. It can be the same data set that is used by anevent-writer function. Use a unique EQQEVDS for each address space of thescheduler.



Table 5. Example EQQPARM Members for Figure 3Members for the controller Members for the tracker

OPCECNT

OPCOPTS OPCHOST(YES)ERDRTASK(0)NCFTASK(YES)NCFAPPL(CNTSYS)

ROUTOPTS SNA(TRKSYS)

TRKA

OPCOPTS OPCHOST(NO)ERDRTASK(0)EWTRTASK(YES)EWTRPARM(STDEWTR)NCFTASK(YES)NCFAPPL(TRKSYS)

TRROPTS HOSTCON(SNA) SNAHOST(CNTSYS)

STDEWTR

EWTROPTS EWSEQNO(01)

Note: In this example, the LU name of the controller is CNTSYS and the tracker usesTRKSYS. The tracker LU is defined in the destination field of the workstation.

XCF ConnectedFigure 4 on page 20 shows two IBM Tivoli Workload Scheduler for z/OS addressspaces with an XCF connection in an z/OS monoplex.

Figure 3. A z/OS System with a VTAM Connection


You represent this system to IBM Tivoli Workload Scheduler for z/OS by defininga computer workstation with a destination field that specifies the XCF membername of the tracker. The controller uses XCF services to transport JCL, releasecommands, WTO messages, and cleanup requests to members in the sysplex. Thetracker receives data from XCF and and performs the following actions:v Submits JCL for batch jobs to the JES internal readerv Writes the JCL for started tasks into the EQQSTC data set and issues START

procnamez/OS commandsv Issues JES release commands for jobs in HOLD statusv Submits the cleanup job.

The event-tracking routines create event records to describe activities that occur onthe system. These records are added to the tracker event writer queue in ECSA.The tracker processes the queue, transports the records to the controller across theXCF link, and writes the events into the event data set. The data router subtask inthe controller receives the event records from XCF, and the current plan is updated.

Table 6 on page 21 shows the initialization statements you can use to create theconfiguration in Figure 4.

Figure 4. A z/OS System with an XCF Connection


Table 6. Example EQQPARM Members for Figure 4 on page 20Members for the controller Members for the tracker

OPCECNT

OPCOPTS OPCHOST(YES)ERDRTASK(0)

ROUTOPTS XCF(OPCTRK)XCFOPTS MEMBER(OPCCNT)

GROUP(PLEXSYSA)

TRKA

OPCOPTS OPCHOST(NO)ERDRTASK(0)EWTRTASK(YES)EWTRPARM(STDEWTR)

TRROPTS HOSTCON(XCF)XCFOPTS MEMBER(OPCTRK)

GROUP(PLEXSYSA)

STDEWTR

EWTROPTS EWSEQNO(01)

Note: In this example, the name of the monoplex is PLEXSYSA. The members in thatgroup are:v OPCCNTthe controllerv OPCTRKthe tracker.The tracker member name is defined in the destination field of the workstation.

Tracker and Controller in a Single Address Spa

Documents

EQQI1mst