The configuration profiles have been tailored with the
values you provided in the previous step. They also contain default
values for all required parameters and some optional parameters. The
amount of additional customization required depends upon how much
your environment differs from the model or product-provided defaults.
At a minimum, you must supply site-specific values. You must enable
and configure any features you want to exploit (such as event forwarding
or support for self-describing agents). In this scenario, you must
also edit the variables configuration profile (%GBL_USER_JCL%.%RTE_NAME%)
to specify resolution values for any user-defined variables.
About this task
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 can assign symbolics to additional parameters,
but see Parameters ineligible to use variables for parameters that must be
excluded from use of symbolics. In addition, you must also customize
the product-specific parameters listed in Configure OMEGAMON monitoring agents and other components, as applicable. Optionally, you
can configure any monitoring server features that you want to enable
(Configure a Tivoli Enterprise Monitoring Server). In the global profile, you
can assign symbolics to any of the parameters. At a minimum, you must
assign a symbolic value to the GBL_HFS_JAVA_DIR1 parameter, for example, &GBL_HFS_JAVA_DIR1.
or change the literal default to a site-appropriate one. You must
also edit the value for load library parameters GBL_DSN_CSF_SCSFMOD0
and any of the product-specific parameters listed in Customizing the global configuration profile, as appropriate.
If you assign
symbolics in either the RTE or the global configuration profile to
parameters that are concatenated in or part of started task procedures,
you must follow the MVS rules governing the use of symbolics in started
task procedures and JCL. In the RTE profile, these are the following
parameters:
- RTE_NAME
- RTE_HILEV
- RTE_VSAM_HILEV
- RTE_X_HILEV_SHARING
- RTE_SHARE
- Kpp_*_VTAM_APPL_*
In the global profiles, these are the following parameters:
- GBL_DSN_DB2_*
- GBL_DSN_IMS_*
- GBL_DSN_CICS_CTG_DLL
- GBL_DSN_WMQ_*
- GBL_DSN_CSF_SCSFMOD0
- GBL_DSN_TCP_SYSTCPD_TCPDATA
In the variables profile (%GBL_USER_JCL%.%RTE_NAME%),
if you want to use the self-describing agent feature, set the resolution
value for KDS_KMS_SDA to
Y, and provide site-specific
values for the following symbols:
- RTE_USS_RTEDIR
- GBL_HFS_JAVA_DIR1
In addition, provide values for any user-defined variables that
you add, any variables that whose values differ from the IBM-provided
default resolution values, and any variables whose values cannot be
automatically discovered from the system IPL PARMLIB data set. See
Customizing the variables profile for more information on customizing
variables.