Customizing the configuration profiles
is a critical part of the configuration process. The profiles contain
the values that define the runtime environment, communication protocols
and addresses, the framework features that are enabled, product-specific
values, and so forth. The configuration profiles are tailored with
the information you specify when you set up the RTE work environment.
Default values are provided for all other required parameters and
some optional ones. The amount of editing required to customize the
configuration profiles depends upon how you are creating the runtime
environment (RTE) and how much your environment differs from the model
or product-provided defaults.
About this task
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. Alternatively,
you can edit the profiles to override defaults and provide custom
values for optional parameters that have no defaults.
Review and customization of the RTE configuration profile is required
to override defaults with any required site-specific values, such
as port numbers and to enable optional features such as automatic
APF authorization, event forwarding, or support for self-describing
agents.
Review of the $GBL$USR profiles is required under either of the
following conditions:
If the RTE is being upgraded and there may be new GBL_* parameters introduced in the new version
of the product.
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 (for example,
GBL_DB2_KD2_CLASSIC_STC parameter applies to all OMEGAMON XE for Db2 PE/PM
components if configuring this product family).
Customization of the variables configuration file is required
if the runtime environment is enabled for system variables (RTE_SYSV_SYSVAR_FLAG=Y)
and user-defined symbols are being used. Any system variables whose
resolution values cannot be determined from the IPL PARMLIB must also
be defined.
Usage note: Include parameter values
in quotation marks ("") if they include mixed casing, embedded blanks,
or special characters, or if they are followed by a comment.
For
help with the parameter values, consult the following resources:
To customize the configuration profiles, from the Workflow
main panel, select option 8.
KCIP@PG0 ------ PARAMETER GENERATOR (PARMGEN) WORKFLOW - WELCOME --------------
Option ===> 8 Scroll ===> PAGE
Enter PARMGEN parameter values appropriate for your environment:
GBL_USER_JCL: TDITN.IDTST.PARMGEN.JCL_____________________
PARMGEN common/global library to store cross-RTE values for
the RTEs created using the same GBL_USER_JCL common library
RTE_PLIB_HILEV: TSTEST.&userid____________
High-Level Qualifier (&hlq) portion of the PARMGEN libraries:
- &hlq.&rte_name.IK*/WK*/WCONFIG PARMGEN work libraries
RTE_NAME: DEMO_ (Type ? for a list of PARMGEN-created RTEs)
Runtime environment ($rte_name) name for this LPAR
Note: Enter n (1-11) to perform tasks. Status Date
Enter ns (1s-11s) for detailed job/task status. --------- ----------
1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2014/09/08
2. $JOBINDX Review PARMGEN job index. Viewed 2014/09/08
3. KCIJPCCF Clone customized WCONFIG members. (COND)
4> KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2014/09/08
5. KCIJPMC1 Merge profile from backup RTEDEMOR (COND)
6. KCIJPMC2 Merge profile from model RTE. (COND)
7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)
8. DEMO Customize PARMGEN configuration profiles.
9. KCIJPVAL Validate PARMGEN profile parameter values.
10. Create the RTE members and jobs.
11. SUBMIT Submit batch jobs to complete PARMGEN setup.
U Utility Access PARMGEN utilities. (Optional)
R New RTE Reset RTE, Status and Date fields. (Optional)
The Customize PARMGEN Configuration
Profile Members (KCIP@PG6) panel is displayed.