Perform these actions on each system in your Tivoli Workload Scheduler for z/OS configuration:

• Run SMP/E to receive tracker software.
• Apply tracker maintenance.

Perform these actions on each system where you are installing a controller, standby controller, or dialogs:

• Run SMP/E to receive controller software.
• Apply controller maintenance.

Perform these actions on each system where you are installing a controller standby controller, or dialogs:

• Run SMP/E to receive NLS software.
• Apply NLS maintenance.

You can run EQQJOBS as soon as the tracker software is loaded. It helps you install Tivoli Workload Scheduler for z/OS:

• Set up EQQJOBS.
• Create the sample job JCL. Do this to generate tailored samples from the EQQJOBS dialog.
• Generate batch job skeletons. Use EQQJOBS to generate skeletons for the ISPF dialogs.
• Optionally generate the Data Store samples if you want to install the Data Store.

Perform this task on every z/OS system in your Tivoli Workload Scheduler for z/OS configuration.

On each system where you are installing the product, perform the actions that are applicable to your installation:

• Define Tivoli Workload Scheduler for z/OS subsystems (IEFSSNnn). This is required for each system where the product is installed.
• Authorize the Tivoli Workload Scheduler for z/OS load module library (IEAAPFnn). Do this if you install the product in a separate load module library.
• Update SMF parameters (SMFPRMnn). Do this when installing a tracker.
• Update dump-content definitions. Consider this on each system where you are installing the product.
• Update the z/OS link-library definition (LNKLSTnn) on each system where you are installing the product.
• Update XCF initialization options (COUPLEnn). Review this section if you use XCF connections.
• Modify TSO parameters (IKJTSOnn). Do this when installing a controller, a standby controller, or the ISPF dialogs.
• Update PPT for performance (SCHEDnn) on each system where you are installing the product.
• Define the DLF exit for Hiperbatch support (COFDLFnn). Do this if you use Hiperbatch support.
• Choose whether to Tivoli Workload Scheduler for z/OS automatically (COMMNDnn). Consider this on each system where you are installing the product.
• Update APPC options (APPCPMnn). Consider this action if you intend to use the Tivoli Workload Scheduler for z/OS API or server. Define VTAM® resources before you update SYS1.PARMLIB. Coordinate this action with task 18 or 19.

Perform these actions on each system in your Tivoli Workload Scheduler for z/OS configuration:

• Update RACF for Tivoli Workload Scheduler for z/OS started tasks (ICHRIN03) on all Tivoli Workload Scheduler for z/OS started tasks on each system.
• Update RACF for a controller or standby controller.
• Use functions of RACF 1.9 or later. Consider this action if you use RACF 1.9 or later.

Perform these actions to activate a secure communication in a TCP/IP network:

• Create the SSL work directory.
• Create as many private keys, certificates, and trusted certification authority (CA) chains as you plan to use in your network.
• Configure the scheduler, by specifying the TCPOPTS statement for each component of your network.

Perform these actions if you are installing a tracker or a controller:

• Review the section on allocating Tivoli Workload Scheduler for z/OS data sets. Do this before you allocate data sets.
• Allocate VSAM data sets for a controller. Perform this action to create new data sets for a controller.
• Allocate non-VSAM data sets. Perform this action for each Tivoli Workload Scheduler for z/OS address space.
• Optionally allocate the VSAM Data Store data sets if you want to use the Data Store.
• Optionally allocate the files and directory to use the end-to-end scheduling with fault tolerance capabilities.

Perform these actions for each Tivoli Workload Scheduler for z/OS address space.

• Create a JCL procedure for each address space on all z/OS systems where you are installing Tivoli Workload Scheduler for z/OS.
• If you use Tivoli Workload Scheduler for z/OS to schedule started-task operations, ensure that the started-task-submit data set (EQQSTC) is in the JES PROCLIB concatenation and in the master scheduler start procedure.
• If you use Restart and Cleanup, copy the EQQCLEAN sample procedure to a data set that is referenced in the JES PROCLIB concatenation.

Perform this task for each Tivoli Workload Scheduler for z/OS address space:

• Define initialization statements. Create members in the parameter library (EQQPARM) for each address space.

Perform this task if you need history support:

• Update initialization statements.
• Create a DB2 database.

Perform these actions on the system where you are installing the ISPF dialogs.

• Set up the Tivoli Workload Scheduler for z/OS CLIST library.
• Set up the ISPF tables.
• Allocate ISPF and Tivoli Workload Scheduler for z/OS data sets to your TSO session.
• Invoke the Tivoli Workload Scheduler for z/OS dialog.

Even if you have already specified XCF initialization statements in Task 12 and updated the COUPLEnn member in Task 7, consider these actions if you use XCF:

• Update XCF initialization options. Ensure that XCF initialization options are suitable for your Tivoli Workload Scheduler for z/OS configuration.
• Add initialization statement options for XCF. Specify XCF runtime options in the parameter library for all started tasks.

Perform these actions for each address space that is connected through NCF. Ensure that a standby controller has the same tracker connections as the controller and that each tracker can connect to all standby controllers:

• Add NCF network definitions. Define VTAM applications on each system where a started task uses NCF.
• Add NCF session parameters on each z/OS system where Tivoli Workload Scheduler for z/OS is installed.
• Update the COS table. Consider this action if you do not want to use the VTAM COS default entry.
• Activate network resources. Check that all the required VTAM resources are active.
• Add NCF initialization options. Include initialization statement options in the parameter library for all started tasks that use NCF.

Perform these actions for each address space that is connected via TCP/IP. Ensure that a standby controller has the same tracker connections as the controller and that each tracker can connect to all standby controllers:

• Add TCP/IP network definitions. Define IP address for the controller and tracker.
• Add TCP/IP initialization options. Include initialization statement options in the parameter library for all started tasks that use TCP/IP.
• For TCP/IP, the Tivoli Workload Scheduler for z/OS server can manage up to 500 concurrent connection requests in a queue. In the PROFILE.TCPIP configuration file, set the SOMAXCONN statement to a value not greater than 500.

To use the API, perform these actions for each Tivoli Workload Scheduler for z/OS address space that you want to send requests to:

• Define VTAM resources. Define a local LU for Tivoli Workload Scheduler for z/OS, logon modes, and cross-domain resources, as required.
• Update APPC options. Update the APPCPMnn member of SYS1.PARMLIB.
• Activate Tivoli Workload Scheduler for z/OS support for APPC. In the parameter library, include APPCTASK(YES) on the OPCOPTS statement.

To activate the server, perform these actions in the order shown:

1. Define VTAM resources. Define a local LU for Tivoli Workload Scheduler for z/OS, logon modes, and cross-domain resources, as required.
2. Update APPC options. Update the APPCPMnn member of SYS1.PARMLIB.
3. Activate Tivoli Workload Scheduler for z/OS support for APPC. In the parameter library, include SERVERS on the OPCOPTS statement.

• Ensure that you have loaded the fault-tolerant end-to-end enabler software on the system where you have installed the controller.
• Verify that all the VSAM and non-VSAM data sets and the files used for the end-to-end scheduling with fault tolerance capabilities have been allocated (for details, see the task that describes how to allocate data sets).
• To activate the server, include TPLGYPRM on the SERVOPTS statement in the IBM Tivoli Workload Scheduler for z/OS parameter library.
• To activate the controller, include TPLGYSRV on the OPCOPTS statement in the IBM Tivoli Workload Scheduler for z/OS parameter library.
• To activate the Daily Planning batch jobs, include TPLGYPRM in the BATCHOPTS statement in the IBM Tivoli Workload Scheduler for z/OS parameter library.

• Define the ROUTOPTS initialization parameters for the controller.
• Define the HTTPOPTS initialization parameters for the tracker.

To activate the server, perform these actions:

• Install the Connector
• In the parameter library, include SERVERS on the OPCOPTS statement.

Perform this task if you want to use one of the following features:

• Dynamic Workload Console reporting.
• Event-driven workload automation for data set triggering, with centralized deploy process.

In the Tivoli Workload Scheduler for z/OS address space, verify the following installations:

• Tracker installation.
• Controller installation.
• Standby controller installation.
• End-to-end installation.
• Data Store installation.
• Server installation.

When a current plan has been created, verify your Tivoli Workload Scheduler for z/OS configuration.