Front cover -- Contents -- Figures -- Tables -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Notice -- Comments welcome -- Chapter 1. Introduction -- 1.1 Job scheduling -- 1.2 Introduction to Tivoli Workload Scheduler for z/OS -- 1.2.1 Overview of Tivoli Workload Scheduler for z/OS -- 1.2.2 Tivoli Workload Scheduler for z/OS architecture -- 1.3 Introduction to Tivoli Workload Scheduler -- 1.3.1 Overview of Tivoli Workload Scheduler -- 1.3.2 Tivoli Workload Scheduler architecture -- 1.4 Benefits of integrating TWS for z/OS and TWS -- 1.5 Summary of enhancements in Tivoli Workload Scheduler 8.1 -- 1.5.1 Enhancements to Tivoli Workload Scheduler for z/OS -- 1.5.2 Enhancements to Tivoli Workload Scheduler -- 1.5.3 Enhancements to the Job Scheduling Console -- 1.6 The terminology used in this book -- 1.7 Material covered in this book -- Chapter 2. End-to-end TWS architecture and components -- 2.1 Tivoli Workload Scheduler architecture -- 2.1.1 The Tivoli Workload Scheduler network -- 2.1.2 Tivoli Workload Scheduler workstation types -- 2.1.3 Tivoli Workload Scheduler topology -- 2.1.4 Tivoli Workload Scheduler components -- 2.1.5 Tivoli Workload Scheduler database objects -- 2.1.6 Tivoli Workload Scheduler plan -- 2.1.7 Other Tivoli Workload Scheduler features -- 2.1.8 Making the Tivoli Workload Scheduler network fail-safe -- 2.2 Tivoli Workload Scheduler for z/OS architecture -- 2.2.1 Tivoli Workload Scheduler for z/OS configuration -- 2.2.2 Tivoli Workload Scheduler for z/OS database objects -- 2.2.3 Tivoli Workload Scheduler for z/OS plans -- 2.2.4 Other Tivoli Workload Scheduler for z/OS features -- 2.3 End-to-end scheduling architecture -- 2.3.1 How end-to-end scheduling works -- 2.3.2 Tivoli Workload Scheduler for z/OS end-to-end components -- 2.3.3 Tivoli Workload Scheduler for z/OS end-to-end configuration.

2.3.4 Tivoli Workload Scheduler for z/OS end-to-end database objects -- 2.3.5 Tivoli Workload Scheduler for z/OS end-to-end plans -- 2.3.6 How to make the TWS for z/OS end-to-end fail-safe -- 2.3.7 Tivoli Workload Scheduler for z/OS end-to-end benefits -- 2.4 Job Scheduling Console and related components -- 2.4.1 A brief introduction to the Tivoli Management Framework -- 2.4.2 Job Scheduling Services (JSS) -- 2.4.3 Connectors -- Chapter 3. Planning, installation, and configuration of the TWS 8.1 -- 3.1 Planning end-to-end scheduling for TWS for z/OS -- 3.1.1 Preventive Service Planning (PSP) -- 3.1.2 Software ordering -- 3.1.3 Tracker agents -- 3.1.4 Workload Monitor -- 3.1.5 System documentation -- 3.1.6 EQQPDF -- 3.1.7 Sharing hierarchical file system (HFS) cluster -- 3.1.8 TCP/IP considerations -- 3.1.9 Script repository -- 3.1.10 Submitting user ID -- 3.2 Installing Tivoli Workload Scheduler for z/OS -- 3.2.1 Executing EQQJOBS installation aid -- 3.2.2 Defining Tivoli Workload Scheduler for z/OS subsystems -- 3.2.3 Allocate end-to-end datasets -- 3.2.4 Create and customize the work directory -- 3.2.5 Create the started task procedures for TWS for z/OS -- 3.2.6 Define end-to-end initialization statements -- 3.2.7 Initialization parameter used to describe the topology -- 3.2.8 Reflecting a distributed environment in TWS for z/OS -- 3.2.9 Verify the installation -- 3.3 Installing the TWS for z/OS TCP/IP server for JSC usage -- 3.3.1 Controlling access to OPC using Tivoli Job Scheduling Console -- 3.4 Planning end-to-end scheduling for TWS -- 3.4.1 Network planning and considerations -- 3.4.2 Backup domain manager -- 3.4.3 Performance considerations -- 3.4.4 FTA naming conventions -- 3.5 Installing TWS in an end-to-end environment -- 3.5.1 Installing multiple instances of TWS on one machine -- 3.6 Installing and configuring Tivoli Framework.

3.6.1 Installing Tivoli Management Framework 3.7B -- 3.6.2 Upgrade to Tivoli Management Framework 3.7.1 -- 3.7 Install Job Scheduling Services -- 3.7.1 Installing the connectors (for TWS and TWS for z/OS connector) -- 3.7.2 Creating connector instances -- 3.7.3 Creating TMF Administrators for Tivoli Workload Scheduler -- 3.8 Planning for Job Scheduling Console availability -- 3.9 Installing the Job Scheduling Console -- 3.9.1 Hardware and software prerequisites -- 3.9.2 Installing the JSC -- 3.10 The Tivoli Workload Scheduler security model -- 3.10.1 The security file -- 3.10.2 Sample security file -- 3.11 Maintenance -- Chapter 4. End-to-end implementation scenarios and examples -- 4.1 The rationale behind the conversion to end-to-end scheduling -- 4.2 Description of our environment and systems -- 4.3 Implementing TWS for z/OS end-to-end scheduling from scratch -- 4.3.1 The configuration and topology for the end-to-end network -- 4.3.2 Customize the TWS for z/OS plan program topology definitions -- 4.3.3 Customize the TWS for z/OS engine -- 4.3.4 Restart the TWS for z/OS engine -- 4.3.5 Define fault tolerant workstations in the engine database -- 4.3.6 Activate the fault tolerant workstation definitions -- 4.3.7 Create jobs, user definitions, and job streams for verification tests -- 4.3.8 Verification test of the end-to-end installation -- 4.3.9 Some general experiences from the test environment -- 4.4 Migrating TWS for z/OS tracker agents to TWS for z/OS end-to-end -- 4.4.1 Migration benefits -- 4.4.2 Migration planning -- 4.4.3 Migration checklist -- 4.4.4 Migration actions -- 4.4.5 Migrating backwards -- 4.4.6 TWS for z/OS JCL variables in connection with TWS parameters -- 4.5 Conversion from TWS network to TWS for z/OS managed network -- 4.5.1 Illustration of the conversion process -- 4.5.2 Considerations before doing the conversion.

4.5.3 The conversion process from TWS to TWS for z/OS -- 4.5.4 Some guidelines to automate the conversion process -- 4.6 TWS for z/OS end-to-end fail-over scenarios -- 4.6.1 Configure TWS for z/OS backup engines -- 4.6.2 Configure DVIPA for the TWS for z/OS end-to-end server -- 4.6.3 Configure backup domain manager for primary domain manager -- 4.6.4 Switch to TWS for z/OS backup engine -- 4.6.5 Switch to TWS backup domain manager -- 4.6.6 HACMP configuration guidelines for TWS workstations -- 4.6.7 Configuration guidelines for High Availability environments -- 4.7 Backup and maintenance guidelines for end-to-end FTAs -- 4.7.1 Backup of the TWS agents -- 4.7.2 Stdlist files on TWS fault tolerant agents -- 4.7.3 Auditing log files on TWS fault tolerant agents -- 4.7.4 Files in the TWS schedlog directory -- 4.7.5 Monitoring file systems on TWS agents -- 4.7.6 Central repositories for important TWS files -- Chapter 5. Using The Job Scheduling Console -- 5.1 Using the Job Scheduling Console -- 5.2 Starting the Job Scheduling Console -- 5.3 Job Scheduling Console fundamentals -- 5.4 TWS for z/OS-specific JSC enhancements -- 5.4.1 Submit job streams to TWS for z/OS current plan -- 5.4.2 JSC text editor to display and modify JCLs in current plan -- 5.4.3 JSC read-only text editors for job logs and operator instructions -- 5.4.4 New restart possibilities in JSC -- 5.5 TWS-specific JSC enhancements -- 5.5.1 Editing a job stream instance -- 5.5.2 Re-Submitting a job stream instance -- 5.5.3 New run cycle options -- 5.6 General JSC enhancements -- 5.6.1 The filter row -- 5.6.2 Sorting list results -- 5.6.3 Non-modal windows -- 5.6.4 Copying jobs from one job stream to another -- 5.7 Common Default Plan Lists in JSC -- 5.7.1 Example showing how to use common list of job instances -- 5.7.2 When to use the TWS for z/OS legacy interfaces.

Chapter 6. Troubleshooting in a TWS end-to-end environment -- 6.1 Troubleshooting for Tivoli Workload Scheduler for z/OS -- 6.1.1 Using keywords to describe a problem -- 6.1.2 Searching the software-support database -- 6.1.3 Problem-type keywords -- 6.1.4 Problem analysis procedures -- 6.1.5 Abnormal termination (ABEND or ABENDU) procedure -- 6.1.6 The diagnostic file (EQQDUMP) -- 6.1.7 Trace information -- 6.1.8 System dump dataset -- 6.1.9 LOOP procedure -- 6.1.10 Message (MSG) procedure -- 6.1.11 Performance (PERFM) procedure -- 6.1.12 WAIT procedure -- 6.1.13 Preparing a console dump -- 6.1.14 Dump the failing system -- 6.1.15 Information needed for all problems -- 6.1.16 Performing problem determination for tracking events -- 6.2 Troubleshooting TWS for z/OS end-to-end solution -- 6.2.1 End-to-end working directory -- 6.2.2 The standard list directory -- 6.2.3 The standard list messages -- 6.2.4 Diagnose and fix problems with unlinked workstations -- 6.2.5 Symphony renew option -- 6.2.6 UNIX System Services diagnostics -- 6.2.7 TCP/IP server -- 6.2.8 Tivoli Workload Scheduler for z/OS connector -- 6.2.9 Job Scheduling Console -- 6.2.10 Trace for the Job Scheduling Console -- 6.3 TWS troubleshooting checklist -- 6.3.1 FTAs not linking to the master -- 6.3.2 Batchman not up or will not stay up (batchman down) -- 6.3.3 Jobs not running -- 6.3.4 Jnextday is hung or still in EXEC state -- 6.3.5 Jnextday in ABEND state -- 6.3.6 FTA still not linked after Jnextday -- 6.4 A brief introduction to the TWS 8.1 tracing facility -- Chapter 7. Tivoli NetView integration -- 7.1 Tivoli NetView -- 7.1.1 Network management ABCs -- 7.1.2 NetView as an SNMP manager -- 7.2 What the integration provides -- 7.3 How the integration works -- 7.4 Integration architecture and our environment -- 7.5 Installing and customizing the integration software.

7.5.1 Installing mdemon on the NetView Server.