Contents

Figures
Tables
About this publication
What is new in this release
What is new in this publication
Who should read this publication
Publications
Using LookAt to look up message explanations
Accessibility
Tivoli technical training
Support information
Conventions used in this publication
Planning
Overview
Hardware and software requirements
Hardware requirements
Software requirements and optional software
Controlling system
Controlled z/OS systems
Optional software
Related software
Software compatibility
Parts and their relationships
Tracker
Controller
Server
| |
Graphical user interfaces
Data Store
Configurations
Controlling system
Controlled systems
Integration with Tivoli Workload Scheduler
Subtasks
Relationship between the Scheduler and z/OS
Using the Tivoli Workload Scheduler for z/OS Program Directory
Sample library
The installation process
Planning your configuration
Planning considerations
Trackers
Initialization statements
Communication
How to connect Tivoli Workload Scheduler for z/OS systems
Shared DASD
z/OS cross-system coupling facility
VTAM (network communication function)
TCP/IP
Workstation destination
Workload restart
JES considerations
Basic server configuration example
Basic configuration examples
DASD connected
VTAM connected
TCP/IP connected
XCF connected
Tracker and controller in a single address space
Basic data store configuration examples
SNA only connection
XCF only connection
TCP/IP only connection
Mixed SNA and XCF connection
Planning your installation
Installation considerations
Configuring for availability
Hot standby
Starting an event writer with an event reader function
Using a Hierarchical File System cluster
Checklist for installing Tivoli Workload Scheduler for z/OS
Tivoli Workload Scheduler for z/OS
Installing
Step 1. Loading tracker software
Step 2. Loading controller software
Step 3. Loading national language support software
Step 4. Using the EQQJOBS installation aid
Setting up the EQQJOBS installation aid
Creating the sample job JCL
Generating batch-job skeletons
Generating Data Store samples
Step 5. Adding SMF and JES exits for event tracking
SMF only
JES2 only
JES3 only
Step 6. Updating SYS1.PARMLIB
Defining subsystems
Calculating MAXECSA values
Authorizing the load-module library
Updating SMF parameters
Updating z/OS dump options
Updating the z/OS link-library definition
Updating XCF initialization options
Modifying TSO parameters
Performance considerations
Defining the DLF exit for Hiperbatch support
Starting the product automatically
Updating APPC options
Implementing support for data set triggering
Step 7. Setting up the RACF environment
Controlling the user ID of the address space
Controlling the user ID of submitted jobs
Normal production jobs
Stand-alone cleanup jobs
Dialog jobs
Protecting data sets
Controlling access to resources
Permitting access to the controller through the API
Controlling access to Tivoli Workload Scheduler for z/OS resources when using the Dynamic Workload Console
Permitting access to the controller through the Dynamic Workload Console
Authorizing Tivoli Workload Scheduler for z/OS as a job submitter
Authorizing Tivoli Workload Scheduler for z/OS to issue JES commands
Authorizing Tivoli Workload Scheduler for z/OS E2E server task to create USS processes
Authorizing Tivoli Workload Scheduler for z/OS E2E and Dynamic Workload Console server tasks for security resource EZB.BINDDVIPARANGE
Authorizing Tivoli Workload Scheduler for z/OS Data Store to issue JES commands
| |
Step 8. Securing communications
| |
Security for TCP/IP connections
| |
Security for HTTP connections
Step 9. Allocating data sets
Allocating the VSAM data sets
Application description data set (EQQADDS)
Current plan data sets (EQQCPnDS)
| |
Data sets for extended data (EQQXDnDS)
Current plan backup copy data set (EQQSCPDS)
JCL repository data sets (EQQJSnDS)
Operator Instruction data set (EQQOIDS)
Allocating Restart and Cleanup VSAM data sets
Restart and cleanup data sets (EQQPKIxx, EQQSKIxx, and EQQSDFxx)
Allocating non-VSAM data sets
Internal reader data set (EQQBRDS)
Checkpoint data set (EQQCKPT)
Diagnostic data sets (EQQDMSG, EQQDUMP, and SYSMDUMP)
Event data sets (EQQEVDS, EQQEVDnn, and EQQHTTP0)
Event-driven workload automation configuration file data set (EQQEVLIB)
Job library data set (EQQJBLIB)
Job-completion-checker data sets
Job-tracking data sets (EQQJTARC, EQQJTnn, EQQDLnn)
Message log data set (EQQMLOG)
Loop analysis log data set (EQQLOOP)
Parameter library (EQQPARM)
PIF parameter data set (EQQYPARM)
Automatic-recovery-procedure library (EQQPRLIB)
Script library for end-to-end scheduling with fault tolerance capabilities (EQQSCLIB)
Started-task-submit data set (EQQSTC)
Submit/release data set (EQQSUDS)
Centralized script data set for end-to-end scheduling with fault tolerance capabilities (EQQTWSCS)
Input and output events data sets for end-to-end scheduling with fault tolerance capabilities (EQQTWSIN and EQQTWSOU)
Allocating Data Store data sets
Allocating data sets for the Dynamic Workload Console reporting feature
Allocating the files and directories
Configuring for end-to-end scheduling with fault tolerance capabilities in a SYSPLEX environment
Step 10. Creating JCL procedures for address spaces
Implementing support for started-task operations
Required data sets
Optional data sets
Step 11. Defining the initialization statements
Step 12. Creating the DB2 database
Sample to migrate the history database
Step 13. Setting up the ISPF environment
Setting up the CLIST library
Setting up the ISPF tables
Setting up the default dialog-controller connection table
Setting up list tables and graphical attribute tables
Allocating dialog data sets to your TSO session
Invoking the Tivoli Workload Scheduler for z/OS dialog
Using the EQQOPCAC sample CLIST
Modifying an existing ISPF selection menu
Selecting the main menu directly from TSO
Using the ISPF select service
| |
Switching to the advanced style for ISPF panels
Step 14. Using XCF for communication
XCF groups
XCF runtime options
Initialization statements used for XCF
Step 15. Activating the network communication function
Adding NCF to the VTAM network definitions
Adding NCF session parameters
COS table
Activating network resources
Diagnostic data set
Step 16. Using TCP/IP for communication
Initialization statements used for TCP/IP
Step 17. Activating support for the API
Defining VTAM resources
Defining a local LU
Defining logon modes
Defining cross-domain resources
Updating APPC options
Activating support for APPC
Step 18. Activating support for the product dialog and programming interface using the server
Defining VTAM resources for the product dialog and program interface using the server
Defining VTAM resources for the server
Defining a local LU for the server
Defining logon modes for the server
Updating APPC options for the server
Defining VTAM resources in a parallel sysplex
Starting the server
Step 19. Activating support for the end-to-end scheduling with fault tolerance capabilities
Activating server support for the end-to-end scheduling with fault tolerance capabilities
Step 20. Activating support for the end-to-end scheduling with z-centric capabilities
Step 21. Activating support for Dynamic Workload Console
Prerequisites
Considerations
Activating server support for the Dynamic Workload Console
Step 22. Activating support for the Java utilities
Verifying your installation
Overview of verification
Verifying installation of a tracker
Ensuring that all installation tasks are complete
Checking the message log (EQQMLOG)
Verifying tracking events
The event writer
The event data set
Performing problem determination for tracking events
Verifying installation of a controller and dialogs
Ensuring that all installation tasks are complete
Checking the message log (EQQMLOG)
Checking the server message log
Checking dialog functions
Performing problem determination
Dialog problems
Authority problems
Verifying installation of a standby controller
Ensuring that all installation tasks are complete
Checking the message log (EQQMLOG)
Verifying installation of the Restart and Cleanup function
Checking the message log (EQQMLOG)
Verifying configuration
Creating entries in the databases
Running batch jobs
Checking the message logs (EQQMLOG)
Controller message log
Tracker message log
Verifying workload submission
Controlling system
Controlled systems
Verifying job submission
Verifying takeover by a standby controller
Migrating
Planning for migration
Migration considerations
Customization considerations
Migration strategies
JES and SMF exits
Migrating to existing subsystem definitions
Migrating to new subsystem definitions
Getting the right software parts
Migration overview
Migration steps overview
Establishing the required environment
Program requirements
Installation and verification
Parallel testing
Migrating an end-to-end network
Migrating DB2
Changing a shared DASD tracker-to-controller connection to an NCF, XCF, or TCP/IP connection
Running on upgraded operating systems
Migrating actions
Migrating data sets
EQQICTOP VSAM data set conversion program
Data sets that you need to convert
Data sets that can be used
Empty data sets
Tracker and Data Store considerations
Switching into production mode
Closing down your production system
Converting VSAM files to the new system format
Starting the new system
Validating the new system
Migration steps for a system in a heavy workload environment
Performing fallback
Tivoli Workload Scheduler for z/OS Connector
Installing, Upgrading, and Uninstalling on the embedded WebSphere Application Server
Preparing
Authorization roles required for installing, upgrading, or uninstalling
Instances of Tivoli Workload Automation
Installing
| |
Installation and uninstallation log files
Installing using the wizard in interactive mode
Installing using the wizard in silent mode
| |
Installing using response file templates
Installing with an automatically generated response file
Installing from the launchpad
Upgrading
Upgrading with the wizard in interactive mode
Upgrading from version 8.3
Upgrading from version 8.5 or 8.5.1
Upgrading in silent mode
Upgrading from the launchpad
Uninstalling
Uninstalling using the wizard
Uninstalling in silent mode
| |
Installing and uninstalling on WebSphere Application Server for z/OS
| |
Business Scenario
| |
Authorization roles required for installing and uninstalling
| |
Installing on WebSphere Application Server for z/OS
| |
Installing using the Integrated Solutions Console
| |
Installing using the zConnInstall.sh script
| |
Installation and uninstallation log files
| |
Enabling communications with Dynamic Workload Console
| |
Applying maintenance
| |
Uninstalling
| |
Uninstalling using the Integrated Solutions Console
| |
Uninstalling using the zConnUninstall.sh script
| |
Troubleshooting and maintaining the installation
| |
Troubleshooting the installation
| |
z/OS connector installation step hangs while installing on a TWA instance with an existing embedded WebSphere Application Server
| |
On Windows the z/OS connector installation step fails because the user account does not belong to the Administrators group
| |
Dynamic Workload Console creates wrong connection upon installation
| |
Installation fails because Windows Workstation Service is not started
| |
Failed installation of a dynamic domain manager in the same instance as the z/OS connector
| |
Maintaining the installation of the z/OS connector
| |
Updating the SOAP properties after changing the WebSphere Application Server user or its password
| |
Updating the SOAP properties usage
| |
updateWas.sh (.bat)
Dynamic Workload Console
Preparing
Overview of the Dynamic Workload Console
Installation overview
Installation considerations
Selecting your installation method
Instances of Tivoli Workload Automation
Installation media
Installation log files
Interactive wizard installation and uninstallation log files
Installation log files for the embedded WebSphere Application Server
Installing
Installing the Dynamic Workload Console
Using the launchpad
Using the installation wizard
Installing a new instance of the Tivoli Integrated Portal
Installing on an existing instance of the embedded WebSphere Application Server
Installing on your existing instance of Tivoli Integrated Portal
Performing a silent installation
| |
Installing the Tivoli Integrated Portal on an external WebSphere Application Server from the images
Post-installation steps to connect to Tivoli Workload Scheduler Version 8.3 Fix Pack 3
Post-installation steps to configure the use of Lightweight Third-Party Authentication (LDAP)
Accessing the Dynamic Workload Console
Quick steps to define a Tivoli Workload Scheduler engine connection
Quick steps to define a Dynamic Workload Broker connection
Starting and stopping the Dynamic Workload Console
Configuring
Getting started
Tivoli Workload Scheduler portfolio
Dynamic workload broker portfolio
First actions
Upgrading
| |
Updating authentication
Upgrading the console installed on an embedded WebSphere Application Server
Directory structure
Program directory
Directory for SSL files
Performing the upgrade
Uninstalling
Uninstalling using the wizard
Uninstalling in silent mode
Troubleshooting the installation, upgrade, and uninstallation
Installation and uninstallation log and trace files
Recovering a failed InstallShield wizard installation
Recovering a failed upgrade
Uninstalling the Dynamic Workload Console and the Tivoli Integrated Portal manually
Troubleshooting scenarios
Problems with the launchpad
Warning messages displayed when using the launchpad on Linux
Undefined error when using launchpad on Windows operating system
Problems with the interactive wizard
The Dynamic Workload Console installation hangs
Installation hangs during stopWas command
Tivoli Integrated Portal installation fails even if into the logs you find successfully installed
Installation from a remote shared folder fails on Windows operating system
Installation fails on a Linux 390 system with a hostname which is not a Fully Qualified Domain Name
Java Virtual Machine (JVM) failure when installing the Dynamic Workload Console on a Red Hat Enterprise Linux (RHEL) Version 5 or a Suse Linux system Version 11
The Dynamic Workload Console graphical installation and uninstallation fail to start on Red Hat Enterprise Linux (RHEL) Version 5 on x86-64
On Windows, the Dynamic Workload Console installation fails if you try to reinstall on a different profile of an external WebSphere Application Server
Problems with the silent installation
The silent uninstallation does not work and an error code is returned
| |
Problems with the upgrade
| |
Upgrade fails with message AWSUI0085E
Problems with the uninstallation
Uninstall fails on Windows if the installation directory contains the @ character
The Dynamic Workload Console interactive uninstallation wizard fails to start on Red Hat Enterprise Linux (RHEL) Version 5 on x86-64
Installation fails when reinstalling the Dynamic Workload Console after having uninstalled it
Tivoli Workload Scheduler for z/OS Agent
| |
Installing the Tivoli Workload Scheduler for z/OS Agent
| |
User authorization requirements
| |
Authorization roles for running the wizard and a silent installation
| |
Authorization roles for running the twsinst script
| |
Authorization roles for Software Distribution
| |
Starting the launchpad
| |
Installing with the installation wizard
| |
Performing a silent installation
| |
Silent installation using response file templates
| |
Silent installation using an automatically generated response file
| |
Installing using twsinst
| |
twsinst
| |
Installing using Software Distribution
| |
Software packages and parameters
| |
Installation procedure
| |
Prerequisite: Installing the Common Inventory Technology (CIT)
| |
Installing the Tivoli Workload Scheduler for z/OS Agent
| |
Enabling dynamic capabilities
| |
Adding the Java runtime to run job types with advanced options
| |
Adding Java runtime environment after installation or upgrade
| |
Enabling dynamic capabilities after installation or upgrade
| |
Upgrading the Tivoli Workload Scheduler for z/OS Agent
| |
Coexistence with previous versions
| |
User authorization requirements
| |
Upgrading notes
| |
Upgrading using the installation wizard
| |
Upgrading using a silent installation
| |
Upgrading using twsinst
| |
Upgrading process
| |
Examples
| |
Upgrading using Software Distribution
| |
Creating and installing the software package block
| |
Upgrading procedure overview
| |
Prerequisite: Install the Common Inventory Technology
| |
Upgrading the agent
| |
Upgrading the Java runtime to run job types with advanced options
| |
Adding Java runtime or enabling dynamic capabilities after upgrade
| |
Uninstalling the Tivoli Workload Scheduler for z/OS Agent
| |
User authorization requirements
| |
Uninstalling using the wizard
| |
Performing a silent uninstallation
| |
Uninstalling the Tivoli Workload Scheduler for z/OS Agent using the twsinst script
| |
Uninstalling using the Software Distribution CLI
Appendixes
Appendix A. Sample library (SEQQSAMP)
Using the Visual Age compiler
SMP/E samples
Environment setup
RECEIVE processing
APPLY processing
ACCEPT processing
SMF exits
Exit installation
Job step termination exit
Initialization exit
Record write exits
JES exits
Exit installation
JES2 QMOD phase change exit
JES2 JCT I/O exit
JES3 OSE modification exit
JES3 input service final-user exit
RACF samples
Class descriptor table
Router table
Sample library (SEQQSAMP)
Appendix B. Configuration examples
The controlling system
Automatic restart actions
Initialization statements
Multi-access spool systems connected through shared DASD
Individual systems connected via shared DASD
A z/OS Sysplex
A PLEX configuration
Controlling a z/OS system through a VTAM link
Controlling a z/OS system through a TCP/IP link
Controlling a JES2 MAS system through a VTAM link
Appendix C. Invoking the EQQEXIT macro
Invoking EQQEXIT in SMF exits
Invoking EQQEXIT in JES exits
Macro invocation syntax for EQQEXIT
Return codes
Appendix D. Invoking the EQQLSENT macro
Invoking EQQLSENT to create EQQDSLST
Macro invocation syntax for EQQLSENT
Return codes
Appendix E. Using response files
Appendix F. z/OS connector response file properties
Appendix G. The Dynamic Workload Console response file properties
Notices
Trademarks
Index