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.
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.
Step | Description | Applies to | IPL |
---|---|---|---|
Step 1. Loading tracker software | Load tracker
software. Perform the following actions on each system in your HCL Workload Automation for Z
configuration:
|
|
|
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:
|
|
|
This step is not applicable to this version. | Load national language support (NLS) software for the controller. This step is not applicable to this version. | ||
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 HCL Workload Automation for Z:
|
|
|
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 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. |
|
✓ |
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:
|
|
✓ |
Step 7. Setting up the RACF environment | Set up the RACF® environment. Perform these actions on each system in your
HCL Workload Automation for Z
configuration:
|
|
✓ |
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. | |||
Step 8. Securing communications | Set up the SSL environment
Perform these actions to activate a secure communication in a TCP/IP network:
|
|
|
Step 9. Allocating data sets | Allocate data sets. Perform these
actions if you are installing a tracker or a
controller:
|
|
|
Implementing support for started-task operations | Update SYS1.PROCLIB. Perform these
actions for each HCL Workload Automation for Z address
space.
|
|
|
Step 11. Defining the initialization statements | Define initialization statements.
Perform this task for each HCL Workload Automation for Z address
space:
|
|
|
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.
|
|
|
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:
|
|
|
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:
|
|
|
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:
|
|
|
Step 16. Activating support for the API | 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:
|
|
|
Step 17. Activating support for the product dialog and programming interface using the server | 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:
|
|
|
Step 18 is not available. | N/A | N/A | |
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 HCL Workload Automation for Z to schedule
jobs on distributed z-centric agents.
|
|
|
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:
|
|
|
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:
|
|