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
- RTE configuration profile
- The RTE profile inherits the symbolics specified on the KCIP@PG3
panel. However, you must replace all instances of the actual RTE name
in the RTE profile with a symbolic (for example, &SYSNAME.), except
for the RTE_NAMESV parameter instance. You must also edit the variables
profile to set the resolution value of the symbolic assigned to the
RTE name.
You must also 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
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.
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.
- Global configuration profile
- If you set the RTE_USS_RTEDIR parameter in
the RTE profile, in the global configuration profile provide a site-appropriate
value for GBL_HFS_JAVA_DIR1 parameter.
You must also edit the value for the GBL_DSN_CSF_SCSFMOD0 load library parameter and any of the product-specific parameters listed in Customizing the global configuration profile, as appropriate.
- Variables profile
- Edit the variables profile to set the resolution value of the symbolic assigned to the
RTE_NAME parameter in the RTE profile. The resolution value must be the RTE
name.
If you enabled the self-describing agent feature (by setting KDS_KMS_SDA to Y, provide site-specific values for the following symbols:
- RTE_USS_RTEDIR
- GBL_HFS_JAVA_DIR1