Checklist for installing HCL Workload Automation for Z

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 HCL Workload Automation for Z 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 HCL Workload Automation for Z with only one IPL of the z/OS system by performing all the required steps before a scheduled IPL.

The TopicPage column indicates the topicpage in this guide where the task is described.

Table 1. Checklist for installing HCL Workload Automation for Z
Task	Description	Applies to	IPL	Page
1	*Load tracker software*. Perform these actions on each system in your HCL Workload Automation for Z configuration: Run SMP/E to receive tracker software. Apply tracker maintenance.	tracker		Step 1. Loading tracker software
2	*Load controller software*. 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.	Controller Standby controller Dialogs		Step 2. Loading controller software
3	Load national language support (NLS) software for the controller. This step is not applicable to this version. 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.	Controller Standby controller Dialogs
4	*Run the EQQJOBS installation aid*. You can run EQQJOBS as soon as the tracker software is loaded. It helps you install HCL Workload Automation for Z: 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 controller Standby controller Dialogs		Setting up the EQQJOBS installation aid
5	*Add SMF and JES event tracking exits*. Perform this task on every z/OS system in your HCL Workload Automation for Z 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 5. Adding SMF and JES exits for event tracking
6	*Update SYS1.PARMLIB*. On each system where you are installing the product, perform the actions that are applicable to your installation: Define HCL Workload Automation for Z subsystems (IEFSSNnn). This is required for each system where the product is installed. Authorize the HCL Workload Automation for Z 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 HCL Workload Automation for Z 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 HCL Workload Automation for Z API or server. Define VTAM® resources before you update SYS1.PARMLIB. Coordinate this action with task 18 or 19.	Tracker controller Standby controller Dialogs	✓	Step 6. Updating SYS1.PARMLIB
7	*Set up the RACF® environment*. Perform these actions on each system in your HCL Workload Automation for Z configuration: Update RACF® for HCL Workload Automation for Z started tasks (ICHRIN03) on all HCL Workload Automation for Z started tasks on each system. Update RACF® for a controller or standby controller.	Tracker controller Standby controller Dialogs	✓	Step 7. Setting up the RACF environment
At this point, if you placed exit modules in LPA, you can IPL with CLPA. No other options for HCL Workload Automation for Z require an IPL.
8	*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 controller Standby controller Data Store server User address space		Step 8. Securing communications
9	*Allocate data sets*. Perform these actions if you are installing a tracker or a controller: Review the section on allocating HCL Workload Automation for Z 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 HCL Workload Automation for Z address space. Optionally, allocate the VSAM Data Store data sets if you want to use the Data Store.	Tracker controller Data Store server		Step 9. Allocating data sets
10	*Update SYS1.PROCLIB*. Perform these actions for each HCL Workload Automation for Z address space. Create a JCL procedure for each address space on all z/OS systems where you are installing HCL Workload Automation for Z. If you use HCL Workload Automation for Z 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 controller Standby controller		Implementing support for started-task operations
11	*Define initialization statements*. Perform this task for each HCL Workload Automation for Z address space: Define initialization statements. Create members in the parameter library (EQQPARM) for each address space.	Tracker controller Standby controller		Step 11. Defining the initialization statements
If you are not using NCF, XCF, or TCP/IP connections you can now start a tracker and continue with the verification task.
12	*Set up the ISPF environment*. Perform these actions on the system where you are installing the ISPF dialogs. Set up the HCL Workload Automation for Z CLIST library. Set up the ISPF tables. Allocate ISPF and HCL Workload Automation for Z data sets to your TSO session. Invoke the HCL Workload Automation for Z dialog.	Dialogs		The ISPF environment
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.
13	*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 HCL Workload Automation for Z configuration. Add initialization statement options for XCF. Specify XCF runtime options in the parameter library for all started tasks.	Tracker controller Standby controller		Step 13. Using XCF for communication
14	*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 HCL Workload Automation for Z 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 controller Standby controller		Step 14. Activating the network communication function
15	*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 HCL Workload Automation for Z 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 controller Standby controller		Step 15. Using TCP/IP for communication
16	*Activate support for the HCL Workload Automation for Z API*. To use the API, perform these actions for each HCL Workload Automation for Z address space that you want to send requests to: Define VTAM® resources. Define a local LU for HCL Workload Automation for Z, logon modes, and cross-domain resources, as required. Update APPC options. Update the APPCPMnn member of SYS1.PARMLIB. Activate HCL Workload Automation for Z support for APPC. In the parameter library, include APPCTASK(YES) on the OPCOPTS statement.	Tracker controller Standby controller		Step 16. Activating support for the API
17	*Activate support for the HCL Workload Automation for Z Server to use APPC or TCP/IP communications.* Note: Include this task when activating an HCL Workload Automation for Z server. To activate the server, perform these actions in the order shown: Define VTAM® resources. Define a local LU for HCL Workload Automation for Z, logon modes, and cross-domain resources, as required. Update APPC options. Update the APPCPMnn member of SYS1.PARMLIB. Activate HCL Workload Automation for Z support for APPC. In the parameter library, include SERVERS on the OPCOPTS statement.	Server controller Standby controller		Step 17. Activating support for the product dialog and programming interface using the server
19	*Activate support for end-to-end scheduling with z-centric capabilities* Note: Include this task when you intend to use HCL Workload Automation for Z 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 controller Standby controller		Step 19. Activating support for end-to-end scheduling with z-centric capabilities
20	*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 controller Standby controller		Step 20. Activating support for Dynamic Workload Console
21	*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.	Controller		Step 21. Activating support for the Java utilities