Integrating IBM Tivoli Workload Scheduler with Tivoli products

This IBM Redbooks publication explains the benefits and technical merits of integrating IBM Tivoli Workload Scheduler Distributed and IBM Tivoli Workload Scheduler for z/OS with other IBM products. Scheduling is a mission critical process for any company. However, when you talk about scheduling, you...

Descripción completa

Detalles Bibliográficos
Autor Corporativo: International Business Machines Corporation. International Technical Support Organization (-)
Otros Autores: Gucer, Vasfi (Editor)
Formato: Libro electrónico
Idioma:Inglés
Publicado: Austin, TX : IBM, International Technical Support Organization c2005.
Edición:1st ed
Colección:IBM redbooks.
Materias:
Ver en Biblioteca Universitat Ramon Llull:https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009626920106719
Tabla de Contenidos:
  • Front cover
  • Contents
  • Notices
  • Trademarks
  • Preface
  • The team that wrote this redbook
  • Become a published author
  • Comments welcome
  • Part 1 Introduction
  • Chapter 1. Architecture of integration
  • 1.1 IBM TWS for z/OS solution scenario
  • 1.1.1 Integrating with Tivoli Information Management for z/OS
  • 1.1.2 Integrating with Tivoli NetView for z/OS
  • 1.1.3 Integrating with Workload Manager for z/OS
  • 1.1.4 Integrating with Tivoli Decision Support for OS/390
  • 1.1.5 Integrating with Tivoli Business Systems Manager (for z/OS)
  • 1.1.6 Integrating with Tivoli System Automation for z/OS
  • 1.1.7 Integrating with DFSMSrmm™
  • 1.1.8 Integrating with JOB/SCAN
  • 1.2 IBM TWS solution scenario
  • 1.2.1 Integrating with Tivoli Service Level Advisor
  • 1.2.2 Integrating with Tivoli Intelligent Orchestrator
  • 1.2.3 Integrating with Tivoli Data Warehouse
  • 1.2.4 Integrating with Tivoli Business Systems Manager
  • 1.2.5 Integrating with Tivoli Storage Manager
  • 1.2.6 Integrating with Tivoli NetView
  • 1.2.7 Integrating with Tivoli Enterprise Console
  • 1.2.8 Integrating with Tivoli Monitoring
  • 1.2.9 Integrating with Tivoli Configuration Manager
  • 1.2.10 Integrating with IBM DB2 Content Manager OnDemand
  • Part 2 TWS for z/OS integrations
  • Chapter 2. Integrating Tivoli Infoman
  • 2.1 The TWS for z/OS and Infoman configuration
  • 2.2 Creating problem records in Infoman
  • 2.3 TWS for z/OS set up
  • 2.3.1 Creating TWS for z/OS exit 7
  • 2.3.2 Setting up the skeleton JCL
  • 2.3.3 Activating EQQUX007
  • 2.3.4 Adding the required DD statements
  • 2.4 Infoman set up
  • 2.4.1 Creating a privilege class
  • 2.4.2 Creating a stored response chain
  • 2.5 Solving issues with the interface
  • Chapter 3. Integrating Tivoli NetView for z/OS
  • 3.1 Description of the environment and scenarios
  • 3.1.1 Scenarios shown in this solution.
  • 3.2 Exposing TWS for z/OS messages to Tivoli NetView for z/OS automation
  • 3.2.1 Reporting job and TWS for z/OS failures
  • 3.2.2 Reporting workstation failures
  • 3.3 Customizing NetView to enable SMTP notification
  • 3.4 Adding REXX routines to DSICLD user library
  • 3.4.1 TWSWSDN
  • 3.4.2 TWSWSUP
  • 3.4.3 TWSJBERR
  • 3.4.4 TWSJBLAT
  • 3.4.5 Verifying that NetView can send SMTP mail
  • 3.5 Testing your NetView notification automation
  • 3.5.1 Trying the job failure scenario
  • 3.5.2 Trying the workstation scenario
  • Chapter 4. Integrating with OPC Automation extension of System Automation
  • 4.1 The TWS for z/OS and System Automation for z/OS configuration
  • 4.1.1 How TWS for z/OS communicates with System Automation
  • 4.1.2 Configuring TWS for z/OS
  • 4.1.3 Configuring System Automation
  • 4.1.4 Defining work that uses the Tivoli Workload Scheduler for z/OS NV64 workstation
  • 4.2 Issues encountered during the interface activation
  • 4.3 Successful implementation of the Tivoli Workload Scheduler for z/OS and System Automation interface
  • Chapter 5. Integrating Tivoli Business Systems Manager
  • 5.1 Description of the environment and systems
  • 5.2 Forwarding events from Tivoli Workload Scheduler for z/OS to Tivoli Business Systems Manager
  • 5.2.1 Configuring communications
  • 5.2.2 Turning on external monitoring for jobs
  • 5.2.3 Event-driven view on Tivoli Business Systems Manager
  • 5.3 Creating lines of business using Daily Plan data
  • 5.3.1 Creating the .sqi file to define lines of business
  • 5.3.2 Compiling the .sqi file
  • 5.3.3 Running the .sql file to create lines of business
  • 5.3.4 Changing TWS for z/OS definitions
  • 5.4 Loading the TWS for z/OS Daily Plan
  • 5.4.1 Copying the daily plan report to the database server for processing
  • 5.4.2 Creating the opc_autoload.ksh file.
  • 5.4.3 Creating the check_opc_plan_1.cfg configuration file
  • 5.4.4 Scheduling an OPC Check for the new Daily Plan job
  • 5.5 Viewing TWS for z/OS objects in Tivoli Business Systems Manager
  • 5.5.1 Viewing the physical tree on the All Resources view
  • 5.5.2 The Batch Management Summary view
  • 5.5.3 The Event Management view
  • 5.5.4 Viewing lines of business
  • 5.5.5 The Executive Dashboard
  • Chapter 6. Integrating Tivoli Decision Support for OS/390
  • 6.1 Installing the TWS for z/OS - OPC Component
  • 6.2 Identifying the data to be collected
  • 6.2.1 BATCHOPT member considerations
  • 6.2.2 Handling the tracklog data
  • 6.3 Creating the collect application
  • 6.3.1 Standardization considerations
  • 6.3.2 Creating the tracklog data collection application
  • 6.4 Collecting TWS for z/OS data
  • 6.5 Running the OPC reports
  • 6.5.1 Creating the report batch JCL
  • 6.5.2 Running the batch job
  • 6.5.3 Using TWS for z/OS to run the report job
  • 6.5.4 Creating a REXX executable for the report
  • 6.5.5 Creating a JCL procedure
  • 6.5.6 Setting the report batch settings
  • 6.5.7 Running the batch job with the procedure and REXX
  • 6.5.8 Other report information
  • 6.5.9 A daily TWS for z/OS view of the Tivoli Decision Support for OS/390 applications
  • 6.5.10 Overcoming the reporting restrictions
  • 6.6 The Extra OPC Component
  • 6.6.1 Defining the extra component
  • 6.6.2 Adding the extra component to the Components list
  • 6.6.3 Installing the extra component
  • 6.6.4 REXX executable changes
  • 6.6.5 JCL procedure changes
  • 6.6.6 TWS for z/OS environment
  • 6.6.7 Retaining report data
  • 6.7 Hosting reports on a Web site
  • 6.7.1 Converting tabular reports to HFS format
  • 6.7.2 Converting graphical reports to HFS format
  • 6.7.3 Using NetView FTP to transfer data sets to Web hosting system
  • 6.8 Dealing with multiple TWS for z/OS controllers.
  • Chapter 7. Integrating JOB/SCAN
  • 7.1 Customizing for JOB/SCAN installations
  • 7.1.1 Product library allocation
  • 7.1.2 Changing the TWS for z/OS command table
  • 7.1.3 Modifying the Optional functions panel
  • 7.1.4 Setting the JCL edit tool
  • 7.1.5 Configuring JOB/SCAN to match your environment
  • 7.2 Preparing the JCL for scheduling
  • 7.2.1 Preparing and validating JCL within the ISPF editor
  • 7.2.2 Viewing and editing JCL from within an application definition
  • 7.2.3 Automating the conversion from test to production JCL
  • 7.3 Validating the dependencies between operations
  • 7.4 Assessing the impact of changing variables
  • 7.5 Avoiding production problems
  • 7.5.1 Daily validation of jobs in the current plan
  • 7.5.2 Daily planning process
  • 7.5.3 Validating JCL beyond the current plan
  • 7.5.4 Ad-hoc changes
  • 7.6 Tuning JOB/SCAN for special situations
  • 7.6.1 Extending this example
  • Part 3 TWS Distributed integrations
  • Chapter 8. Integrating Tivoli Enterprise Console
  • 8.1 Benefits of integration
  • 8.2 Tivoli Enterprise Console terminology
  • 8.3 Solution components
  • 8.4 Tivoli Enterprise Console configuration
  • 8.5 TWS configuration
  • 8.6 Server architecture
  • 8.7 Design of the integration
  • 8.8 Implementation of the integration
  • 8.8.1 Installation
  • 8.8.2 Configuration
  • 8.8.3 Configuring install options on FTAs with endpoints
  • 8.8.4 Distributing the TEC logfile adapter to MDM
  • 8.8.5 Configuring the Tivoli Enterprise Console server
  • 8.8.6 Configuring the TEC logfile adapter
  • 8.9 Using the integration
  • 8.10 Possible enhancements
  • Chapter 9. Integrating Tivoli Monitoring
  • 9.1 Benefits of integration
  • 9.2 Tivoli Monitoring terminology
  • 9.3 Solution components
  • 9.4 Tivoli Monitoring configuration
  • 9.5 TWS configuration
  • 9.6 Server architecture
  • 9.7 Design.
  • 9.7.1 About host status availability
  • 9.7.2 Host availability using NetView
  • 9.7.3 Host availability using a resource model
  • 9.7.4 Application status (batchman)
  • 9.7.5 Application status (netman)
  • 9.7.6 Application status (mailman)
  • 9.7.7 Application status (jobman)
  • 9.7.8 TWS SpaceFree
  • 9.7.9 TWS SpaceUsed (stdlist)
  • 9.7.10 TWS SpaceUsed (schedlog)
  • 9.8 Implementation
  • 9.8.1 Installing the integration
  • 9.8.2 About the configuration
  • 9.8.3 Creating a profile manager
  • 9.8.4 Adding subscribers
  • 9.8.5 Adding profiles
  • 9.8.6 Creating HostAvail custom resource model
  • 9.8.7 Adding HostAvail custom resource model
  • 9.8.8 Creating a SpaceUsed custom resource model
  • 9.8.9 Adding a SpaceUsed custom resource model
  • 9.8.10 Configuring the Host Status Availability resource model
  • 9.8.11 Configuring Application Status (batchman) resource model
  • 9.8.12 Configuring Application Status (netman) Resource Model
  • 9.8.13 Configuring Application Status (mailman) resource model
  • 9.8.14 Configuring Application Status (jobman) resource model
  • 9.8.15 Configuring Space Free resource model
  • 9.8.16 Configuring Space Used (stdlist) resource model
  • 9.8.17 Configuring Space Used (schedlog) resource model
  • 9.8.18 About configuring an action
  • 9.8.19 Distributing profiles to subscribers
  • 9.9 Using the integration
  • 9.10 Possible enhancements
  • Chapter 10. Integrating Tivoli Business Systems Manager
  • 10.1 Prerequisites
  • 10.2 Installing Intelligent Monitor for TWS
  • 10.3 Process overview
  • 10.3.1 Adapter internals
  • 10.4 Configuration of the log adapter
  • 10.4.1 AdapterEnv.conf
  • 10.4.2 DriverPlugIns.conf
  • 10.4.3 DB_Server.conf
  • 10.4.4 localadapter.config
  • 10.4.5 Log.conf
  • 10.4.6 TWSConf.conf
  • 10.5 Starting the adapter
  • 10.5.1 Starting the adapter at boot time
  • 10.6 Operation.
  • 10.6.1 TbsmObjectCache.properties.