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)
Diagnostic message and trace data set (EQQDMSG)
Diagnostic data set (EQQDUMP)
Dump data set (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
JCC-message-table library (EQQJCLIB)
JCC-incident-log data set
JCC-incident work data set (EQQINCWK)
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
Load modules
The ISPF environment
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
Example
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
Close down your production system
Convert VSAM files to the new system format
Initialize the new system
Produce a checkpoint data set containing data from the old production system
Start the new system
Validate the new system
Performing fallback