Customizing the configuration profiles

The configuration profiles have been tailored with the values you provided as you set up the work environment. They also contain default values for all required parameters and some optional parameters. The amount of additional customization that is required depends upon how much your environment differs from the model or product-provided defaults. At a minimum, you must supply certain site-specific values. You must also enable and configure any features you want to exploit (such as support for self-describing agents).

About this task

In the RTE configuration profile, at a minimum you must set the KDS_HUB_* parameters to the appropriate values for the hub monitoring server to which this remote reports.
  • KDS_HUB_TEMS_NAME_NODEID
  • KDS_HUB_VTAM_APPL_GLB_BROKER (if the hub is enabled for SNA)
  • KDS_HUB_VTAM_NETID (if the hub is enabled for SNA)
  • KDS_HUB_TCP_HOST
  • KDS_HUB_TCP_PIPE_PORT_NUM
If the hub is an HA hub, you must set the monitoring server and agent KDEB_INTERFACELIST parameters (KDS_TEMS_TCP_KDEB_INTERFACELIST and Kpp_AGT_TCP_KDEB_INTERFACELIST) to "!*.
In addition, you might need to configure one or more of the following parameters:
  • If any of the products that you are configuring require any z/OS® UNIX System Services directories running on either the Hierarchical File System (HFS) or on the zSeries File System (zFS), or if you are planning to enable the self-describing agent (SDA) feature, specify the directory to be used (RTE_USS_RTEDIR).
  • To enable the SDA feature, set KDS_KMS_SDA to Y.
  • To automate APF-authorization of all generated started tasks by generating the required commands for all libraries concatenated within the STEPLIB and RKANMODL DD names of the started tasks, set RTE_X_STC_INAPF_INCLUDE_FLAG to Y.
  • To collect historical data for display in either the Tivoli® Enterprise Portal or the OMEGAMON® Enhanced 3270 user interface, data sets must be allocated to store the data. The persistent datastore (PDS) that manages the collected data must be configured (see Allocate data sets and configure maintenance for historical data). It is enabled by default to collect at the agent.
You may want to configure some or all of the following features on the monitoring server: support for self-describing agents, auditing, a SOAP server. For instructions on enabling these features, see Configure a Tivoli Enterprise Monitoring Server.

The parameters discussed here are not the only parameters for which you must either accept or override the default values in the configuration profile for the runtime environment. After you set the parameters shown here, be sure to go through the configuration profiles to make sure the parameter values are correct for the configuration you want. Customizing the runtime environment configuration profile discusses the values and features that are typically customized in the RTE configuration profile.

In the global configuration profile, if you set the RTE_USS_RTEDIR, you must provide a site-appropriate value for GBL_HFS_JAVA_DIR1 parameter. You must also edit the value for load library parameter GBL_DSN_CSF_SCSFMOD0 and any of the product-specific parameters listed in Customizing the global configuration profile, as appropriate.

Procedure

  1. From the Workflow - Primary Option Menu, select 2 (Customize PARMGEN configuration profiles).

    The Customize PARMGEN Configuration Profile Members panel (KCIP@PG6) is displayed.

  2. Type DLAJOB in the Command line and press Enter to review the composite KCIJPDLA job that auto-discovers the values to some parameters in the configuration profiles. Submit the job after you review the job settings.
    For more information about the KCIJPDLn jobs, see Preparing the configuration profiles by running the KCIJPDLn jobs, and PARMGEN z/OS DLA utility jobs and commands.
  3. Select 1 to edit the RTE profile.
  4. Select 2 to edit the $GBL$USR global profile.

What to do next

If you need to further customize the configuration using the override embed members, customize the embed files before you run the $PARSE job to create the RTE members and jobs. To edit the embed files, select option 4 on the Customize PARMGEN Configuration Profile Members panel. You can also edit the files by entering UTIL on the command line of any Workflow panel to access the Access PARMGEN Utilities panel, then selecting option 7. For more information on customizing embed files, see Customizing the override embed members.