Configuring z/OS Change Tracker
z/OS Change Tracker comes preinstalled with z/OS®. It is a priced feature of z/OS that must be enabled before it can be configured and used. Configuration and deployment is done using a z/OS Management Facility (z/OSMF) workflow.
Before you begin
- Ensure that the z/OSMF server is properly
configured and that you have the necessary authorization to
use it.Tip: For a new installation of z/OSMF, begin by creating a base configuration.
Complete the SMP/E installation outlined in
z/OS V3R1 Program Directory.
- Ensure that the z/OS Change Tracker administrator has update access to CYG.** data sets.
- If you use WLM, note the following recommendations.
- Assign the z/OS Change Tracker started task (STC) to a WLM service class that has low or medium importance.
- Do not assign the started task to a WLM service class that is associated with a discretionary goal.
- If z/OS Change Tracker will run in a sysplex environment, refer to Figure 1. Decide which system to configure z/OS Change Tracker on. Decide which other systems in the sysplex also need to run the z/OS Change Tracker started task.
About this task
In a sysplex environment, the z/OS Change Tracker repository, which contains the VSAM data files and control files, is on DASD shared by all systems in the sysplex. Each started task is configured to access the shared repository files.
Procedure
Results
The workflow creates a CYGPARMS data set member that contains configuration parameters which control the operation of z/OS Change Tracker. This member is referred to by all z/OS Change Tracker processes, tasks, and jobs.
When the workflow has successfully completed, z/OS Change Tracker is configured and ready to use.