Installation and verification

If you are migrating to existing subsystem definitions, you must perform these installation tasks:

  1. Load the tracker software (Step 1. Loading tracker software).
  2. Load the controller software (Step 2. Loading controller software).
  3. Load the NLS software (Step 3. Loading national language support software).
  4. Run the EQQJOBS CLIST (Step 4. Using the EQQJOBS installation aid).
  5. Install JES and SMF exits at Tivoli Workload Scheduler for z/OS level (Step 5. Adding SMF and JES exits for event tracking).
  6. Update PARMLIB (Step 6. Updating SYS1.PARMLIB).
  7. |Import the new default security certificates for HTTP |connections (Step 8. Securing communications).
  8. Allocate VSAM and non-VSAM data sets (Step 9. Allocating data sets).
  9. Update the JCL procedure for the Tivoli Workload Scheduler for z/OS address space (Step 10. Creating JCL procedures for address spaces).
  10. Update the initialization statements (Step 11. Defining the initialization statements).
  11. Update the ISPF environment (Step 13. Setting up the ISPF environment).

Ensure that you follow the subsystem verification procedures outlined in Verifying your installation.

You can use the conversion program for both migration and fallback. You should consider testing your installation by migrating in the production environment and then falling back.

Note:
Verify that all the Tivoli Workload Scheduler for z/OS parameters defined in the previous release are still valid in the current release.