Configuration profiles

Edit online

The configuration values for each runtime environment (RTE) are stored in configuration profiles. The RTE configuration profile contains the values for each runtime environment and for the components and products configured in it. The global configuration profile contains values for global system libraries. The variables configuration profile contains definitions of user-defined variables and RTE-specific system variables.

%RTE_NAME%
The RTE-specific configuration file. This file contains parameters that define the configuration for the RTE itself, for infrastructure components and features, and for the product configured in the runtime environment. This profile is named for the runtime environment and is stored in the WCONFIG data set.
The RTE configuration profile contains two types of parameters:
  • RTE$/RTE_* parameters, which specify values for the RTE.
  • Kpp$* or Kpp_* parameters (where Kpp is the three-letter code for a component or product), which specify product-specific values.

This profile is customized by the KCIJPUP1 job with values provided during the setup of the work environment. Default values are provided for all required parameters and some optional ones.

Customization of this profile is required provide to override defaults and specify custom or site-specific values and to enable optional features.

$GBL$USR
The configuration file for global or common system libraries and other common values that can be shared across different products. This file can be copied to other runtime environments if these global system libraries are typically the same across RTEs. This profile is stored in the WCONFIG data set. The parameters in this profile all begin with GBL_*.

Review of the $GBL$USR profiles is required to customize product-specific GBL_* common or global parameters that may apply to more than one product or apply to several components within a product family.

%GBL_USR_JCL%(%RTE_NAME%)
Variables configuration file. The variables used in PARMGEN configuration and their resolved values are defined in a resolution member named GBL_USER_JCL(%RTE_NAME%). This member is referred to as the variables configuration profile. If support for variables has been enabled for a runtime environment, any user-defined variables and their resolution values must be defined in the variables configuration profile. Any system variables whose resolution values cannot be determined from the IPL PARMLIB must also be defined.

A small subset of parameters cannot use variables. See Parameters ineligible to use variables in the Reference section for more information.

PARMGEN maintains default RTE ($CFG$IBM) and global profiles ($GBL$IBM), which are used as the templates for user-customized profiles. These default profiles are refreshed with any new or changed configuration parameters when the KCIJPUP1 job is run during upgrades or maintenance.

Default values are provided for all required parameters and for some optional parameters. If you do not want to customize these parameters, and you do not want to enable optional features, you can complete the configuration by accepting these defaults. Otherwise, you can specify custom values for these parameters. You can also specify custom values for optional parameters that have no defaults.

Tip: The PARMGEN configuration profiles can have a large number of parameters to review. It might be useful, therefore, to exclude certain PARMGEN parameters while you focus on a particular configuration task. For example, exclude all PARMGEN parameters that are for started tasks. Then, find all occurrences of these parameters so you can quickly use a CHANGE ALL command. PARMGEN configuration provides an EXCLUDE-FIND (XF) macro for this task (see XF edit macro.).

For help with the parameter values, consult the following resources:

  • Comments in the profiles
  • Online help for parameters (F1)
  • Common parameters
  • The Parameter Reference for each product