Checklist for installing IBM Z Workload Scheduler

This section contains a checklist to guide you through the installation tasks for a tracker, a controller, a standby controller, or the ISPF dialogs.

Note: Always install the tracker first on the controlling system or on a system where a standby controller will be installed.

In the checklist, the task numbers are arranged in a recommended order but are not meant to imply a required order. You perform the tasks suited to your own configuration.

The Applies to column indicates for which IBM Z Workload Scheduler address space you should perform that particular task. You might not need to perform every task outlined in the list. Skip those tasks or actions that do not apply to your installation.

A check mark (✓) in the IPL column means that an IPL of the z/OS system is needed for the change to take effect. It does not indicate how many IPLs are needed. You can install IBM Z Workload Scheduler with only one IPL of the z/OS system by performing all the required steps before a scheduled IPL.

Table 1. Checklist for installing IBM Z Workload Scheduler
Step Description Applies to IPL
Step 1. Loading tracker software Load tracker software.
Perform the following actions on each system in your IBM Z Workload Scheduler configuration:
  • Run SMP/E to receive tracker software.
  • Apply tracker maintenance.
  • Tracker
Step 2. Loading controller software Load controller software.
Perform the following actions on each system where you are installing a controller, standby controller, or dialogs:
  • Run SMP/E to receive controller software.
  • Apply controller maintenance.
  • Z controller
  • Standby controller
  • Dialogs
Step 3. Loading national language support software Load national language support (NLS) software for the controller.
Perform the following actions on each system where you are installing a controller standby controller, or dialogs:
  • Run SMP/E to receive NLS software.
  • Apply NLS maintenance.
  • Z controller
  • Standby controller
  • Dialogs
Step 4. Using the EQQJOBS installation aid Run the EQQJOBS installation aid.
You can run EQQJOBS as soon as the tracker software is loaded. It helps you install IBM Z Workload Scheduler:
  • 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.
  • Tracker
  • Z controller
  • Standby controller
  • Dialogs
Step 5. Adding SMF and JES exits for event tracking Add SMF and JES event tracking exits.

Perform this task on every z/OS system in your IBM Z Workload Scheduler configuration.

Note: If you place exits in a link-pack-area (LPA) library, you must perform an IPL of the z/OS system with the CLPA option.
  • Tracker
 ✓
Step 6. Updating SYS1.PARMLIB Update SYS1.PARMLIB.
On each system where you are installing the product, perform the actions that are applicable to your installation:
  • Define IBM Z Workload Scheduler subsystems (IEFSSNnn). This is required for each system where the product is installed.
  • Authorize the IBM Z Workload Scheduler 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 start IBM Z Workload Scheduler 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 IBM Z Workload Scheduler API or server. Define VTAM® resources before you update SYS1.PARMLIB. Coordinate this action with task 18 or 19.
  • Tracker
  • Z controller
  • Standby controller
  • Dialogs
 ✓
Step 7. Setting up the RACF environment Set up the RACF® environment.
Perform these actions on each system in your IBM Z Workload Scheduler configuration:
  • Update RACF® for IBM Z Workload Scheduler started tasks (ICHRIN03) on all IBM Z Workload Scheduler started tasks on each system.
  • Update RACF® for a controller or standby controller.
  • Tracker
  • Z controller
  • Standby controller
  • Dialogs
 ✓
At this point, if you placed exit modules in LPA, you can IPL with CLPA. No other options for IBM Z Workload Scheduler require an IPL.
Step 8. Securing communications Set up the SSL environment

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.
  • Tracker
  • Z controller
  • Standby controller
  • Data Store server
  • User address space
Step 9. Allocating data sets Allocate data sets.
Perform these actions if you are installing a tracker or a controller:
  • Review the section on allocating IBM Z Workload Scheduler 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 IBM Z Workload Scheduler 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.
  • Tracker
  • Z controller
  • Data Store server
Implementing support for started-task operations Update SYS1.PROCLIB.
Perform these actions for each IBM Z Workload Scheduler address space.
  • Create a JCL procedure for each address space on all z/OS systems where you are installing IBM Z Workload Scheduler.
  • If you use IBM Z Workload Scheduler 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.
  • Tracker
  • Z controller
  • Standby controller
Step 11. Defining the initialization statements Define initialization statements.
Perform this task for each IBM Z Workload Scheduler address space:
  • Define initialization statements. Create members in the parameter library (EQQPARM) for each address space.
  • Tracker
  • Z controller
  • Standby controller
If you are not using NCF, XCF, or TCP/IP connections you can now start a tracker and continue with the verification task.
The ISPF environment Set up the ISPF environment.
Perform these actions on the system where you are installing the ISPF dialogs.
  • Set up the IBM Z Workload Scheduler CLIST library.
  • Set up the ISPF tables.
  • Allocate ISPF and IBM Z Workload Scheduler data sets to your TSO session.
  • Invoke the IBM Z Workload Scheduler dialog.
  • Dialogs
If you are not using NCF, XCF, or TCP/IP connections, the API or server, you can now start a controller and continue with the verification task.
Step 13. Using XCF for communication Using XCF for local communications.
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 IBM Z Workload Scheduler configuration.
  • Add initialization statement options for XCF. Specify XCF runtime options in the parameter library for all started tasks.
  • Tracker
  • Z controller
  • Standby controller
Step 14. Activating the network communication function Activate NCF for VTAM® connections.
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 IBM Z Workload Scheduler 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.
  • Tracker
  • Z controller
  • Standby controller
Step 15. Using TCP/IP for communication Activate TCP/IP connections
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 IBM Z Workload Scheduler 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.
  • Tracker
  • Z controller
  • Standby controller
Step 16. Activating support for the API Activate support for the IBM Z Workload Scheduler API.
To use the API, perform these actions for each IBM Z Workload Scheduler address space that you want to send requests to:
  • Define VTAM® resources. Define a local LU for IBM Z Workload Scheduler, logon modes, and cross-domain resources, as required.
  • Update APPC options. Update the APPCPMnn member of SYS1.PARMLIB.
  • Activate IBM Z Workload Scheduler support for APPC. In the parameter library, include APPCTASK(YES) on the OPCOPTS statement.
  • Tracker
  • Z controller
  • Standby controller
Step 17. Activating support for the product dialog and programming interface using the server Activate support for the IBM Z Workload Scheduler Server to use APPC or TCP/IP communications.
Note: Include this task when activating an IBM Z Workload Scheduler server.
To activate the server, perform these actions in the order shown:
  1. Define VTAM® resources. Define a local LU for IBM Z Workload Scheduler, logon modes, and cross-domain resources, as required.
  2. Update APPC options. Update the APPCPMnn member of SYS1.PARMLIB.
  3. Activate IBM Z Workload Scheduler support for APPC. In the parameter library, include SERVERS on the OPCOPTS statement.
  • Server
  • Z controller
  • Standby controller
Step 18. Activating support for the end-to-end scheduling with fault tolerance capabilities Activate support for end-to-end scheduling with fault tolerance capabilities
Note: Include this task when you intend to use IBM® Z Workload Scheduler to schedule jobs on distributed fault-tolerant agents.
  • 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® Z Workload Scheduler parameter library.
  • To activate the controller, include TPLGYSRV on the OPCOPTS statement in the IBM® Z Workload Scheduler parameter library.
  • To activate the Daily Planning batch jobs, include TPLGYPRM in the BATCHOPTS statement in the IBM® Z Workload Scheduler parameter library.
  • Z controller
  • Standby controller
  • Server
Step 19. Activating support for end-to-end scheduling with z-centric capabilities Activate support for end-to-end scheduling with z-centric capabilities
Note: Include this task when you intend to use IBM® Z Workload Scheduler to schedule jobs on distributed z-centric agents.
  • Define the ROUTOPTS initialization parameters for the controller.
  • Define the HTTPOPTS initialization parameters for the tracker.
  • Tracker
  • Z controller
  • Standby controller
Step 20. Activating support for Dynamic Workload Console Activate Support for the Dynamic Workload Console
Note: Include this task when activating a server and intending to use the Dynamic Workload Console.
To activate the server, perform these actions:
  • Install the Connector
  • In the parameter library, include SERVERS on the OPCOPTS statement.
  • Server
  • Z controller
  • Standby controller
Step 21. Activating support for the Java utilities Activate Support for the Java™ utilities
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.
  • Z controller