The amount of editing required to customize the configuration
profiles for the new runtime environment (RTE) depends upon how much
the new RTE differs from the RTE you are cloning it from. Presumably,
you are cloning the RTE because you want the new RTE to have the same
values as the RTE you are cloning it from, so the configuration should
be minimal, especially in a variable-enabled RTE. You can clone the
customized WCONFIG members, including the global configuration profile,
from the model RTE and copy its variables profile. You can also clone
any customized data such as situation definitions or enhanced 3270
user interface profiles or workspace definitions. However, there are
a few LPAR-specific values you must change in the RTE configuration
profile of the new RTE.
About this task
In the RTE configuration profile, make the following changes:
- Replace any occurrences of the RTE name with the name of the new
RTE.
- If there is a monitoring server configured in this RTE, modify
the IP host name to the IP host where the agents and monitoring server
will run.
- If you changed the RTE_STC_PREFIX and RTE_VTAM_APPLID_PREFIX on
the KCIPQPG3 panel, make the same changes to the corresponding agent
parameters:
- If you changed a hub monitoring server to a remote, configure
the remote monitoring server parameters that define where the hub
is.
- Customize any the parameter values for any agents or framework
component that are specific to this RTE.
To use the override embeds and $GBL$USR member already customized for the RTE you are cloning,
use the KCIJPCCF job to clone the customized members. Then, review the cloned $GBL$USR member and
make any required RTE-specific changes. At a minimum, you must customize the
GBL_HFS_JAVA_DIR1 parameter to a site-appropriate value. 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.
To copy other customized data from the model RTE, use the KCIJPCLN job. The job must be run after
the $PARSE job is run. See How to: Clone customized data from an existing RTE for more information on running this job.
If
variables are supported in the RTEs, replace the contents of the variables
profile of the new RTE with the contents of the variables file for
the RTE you are cloning (copy %GBL_USER_JCL%(%OLD_RTE%) to %GBL_USER_JCL%(%NEW_RTE%)).
Procedure
-
Select Customize PARMGEN configuration profiles from the Workflow main
options menu.
The Customize PARMGEN Configuration Profile Members panel is displayed.
KCIP@PG6 ------ CUSTOMIZE PARMGEN CONFIGURATION PROFILE MEMBERS ---------------
Option ===>
Quick Configuration Mode
(Required) Customize the RTE profile and the $GBL$USR user profiles:
(Tip) Review KCIJPDLA autodiscovery job in Utility menu or type DLAJOB cmd.
*1. SYSA RTE LPAR-specific CONFIG profile in WCONFIG (User copy)
*2. $GBL$USR Global parameters CONFIG profile in WCONFIG (User copy)
(Required) Customize the Variables profile if RTE_SYSV_SYSVAR_FLAG=Y:
*3. SYSA Variables (system, user) CONFIG profile in GBL_USER_JCL PARMGEN
global library (TDITN.IDTST.PARMGEN.JCL).
Add/Modify system/user-defined symbols and their
resolution values, for override variables used as parameter
values in the $DOCRTE RTE and $GBL$USR global profiles.
(Tip) Review/Customize WCONFIG Kpp$C*/Kpp$P*/Kpp$S* user imbeds:
(Cloning Tip) Review KCIJPCCF job in Utility menu prior to customization.
4. WCONFIG TDITN.IDTST.$DOCRTE.WCONFIG
(Tip) Review if you want to compare with IBM-supplied default profile values:
5. $CFG$IBM RTE LPAR-specific CONFIG profile in WCONFIG (IBM copy)
6. $GBL$IBM Global parameters CONFIG profile in WCONFIG (IBM copy)
(Optional) Override SYSIN member to supply additional (User) profiles:
7. $SYSIN $PARSE/$PARSESV SYSIN controls (CONFIG/SELECT MEMBER)
Press F1=Help for more information. Type UTIL to access utility menu.
-
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.
-
Select option 1 to edit the RTE configuration profile as follows.
- Do a CHANGE ALL to replace the name of the cloned RTE with the name of the
new RTE.
- If there is a monitoring server configured in this RTE, do an EXCLUDE FIND on
TCP_HOST
and change the host name of the cloned RTE to the IP host name for this
RTE.This change reconfigures the agents and components to report to the local monitoring
server.
- If this RTE shares DASD with the RTE it was cloned from, change all occurrences of
Kpp_VTAM_APPLID_PREFIX and Kpp STC_PREFIX to ensure that
these values are unique.
- If you changed a hub monitoring server to a remote when you cloned the RTE, perform an
EXCLUDE FIND on all references to
KDS_HUB
and change the value
of these parameters to the hub values. For example, change
KDS_HUB_TEMS_NAME_NODEID to the name of the hub monitoring server and
KDS_HUB_TCP_HOST to the hub's IP host name.
- If you intend to clone customized data using the KCIJPCLN job, set the following two parameters
to the appropriate values:
- RTE_CLONE_FROM_HLQRTE
- RTE_CLONE_FROM_VSAM_HLQRTE
- Customize any agent parameter values specific to this RTE.
At a minimum, you must configure
the following parameters.
- If OMEGAMON for Db2 on z/OS Performance Expert and Performance Monitor is configured:
- KD2_DBnn_DB2_SSID
- KD2_DBnn_DB2_PROFID
- KD2_DBnn_DB2_VER
- KD2_DBnn_PWH_LOADLIB
- KD2_DBnn_PWH_EXITLIB
- If OMEGAMON for IMS on z/OS is configured:
- For each subsystem, uncomment the following block of parameters.
KI2_I1 BEGIN * Table begin *
KI2_I101_ROW 01
KI2_I101_CLASSIC_XMIT 00
KI2_I101_CLASSIC_IMSID IMSA * Not eligible for symbolics *
KI2_I101_CLASSIC_STC IBMOI0
KI2_I101_CLASSIC_IMS_RESLIB DFS.V12R0M0.SDFSRESL
KI2_I101_CLASSIC_MPREFIX M0
KI2_I101_CLASSIC_VTAM_NODE CTDOI0N
KI2_I101_CLASSIC_VTAM_APPL_LOGON CTDOI0
KI2_I101_CLASSIC_LROWS 255
KI2_I101_CLASSIC_USER_PROFILE /C
KI2_I101_CLASSIC_CTRL_UNIT_ADDR XXXX
KI2_I1 END * Table end *
- At a minimum, customize the following two parameters:
- KI2_I101_CLASSIC_IMSID
- KI2_I101_CLASSIC_IMS_RESLIB
- If OMEGAMON for Networks is configured in the RTE, for each monitored TCP/IP stack customize the
following parameters:
- KN3_TCPXnn_TCPIP_PROFILES_DSN
- KN3_TCPXnn_TCPIP_PROFILES_MBR
- Press F3 to save the changes and return to the Customize
PARMGEN Configuration Profile Members panel.
- Clone the customized WCONFIG files from the RTE you are
cloning.
- Enter UTIL on the command line.
The Utilities panel is displayed.
- Select option 24 (Clone customized WCONFIG members).
The KCIJPCCF JCL is displayed.
- Review the JCL to ensure that the
//OLDWCNFG
DDNAME
is set to the WCONFIG of the RTE you are cloning.
- Submit the job and return to the Customize PARMGEN Configuration
Profile Members panel.
- Edit the cloned $GBL$USR profile as follows:
- From the Customize PARMGEN Configuration Profile
Members menu, select option 2.
-
Customize the GBL_HFS_JAVA_DIR1 parameter with a site-appropriate value. Customizing the global configuration profile,
- If password encryption (KAES256) is enabled, set the
value for the ICSF system library: GBL_DSN_CSF_SCSFMOD0.
- Edit the following product-specific parameters.
- If OMEGAMON for Db2 on z/OS Performance Monitor or Performance Expert is configured in the RTE:
- Uncomment and customize the following parameters as applicable to your Db2 environment:
- GBL_DSN_DB2_SDSNLOAD
- GBL_DSN_DB2_LOADLIB_V8
- GBL_DSN_DB2_LOADLIB_V9
- GBL_DSN_DB2_LOADLIB_V10
- GBL_DSN_DB2_LOADLIB_V11
- GBL_DSN_DB2_LOADLIB_V12
- GBL_DSN_DB2_RUNLIB_V8
- GBL_DSN_DB2_RUNLIB_V9
- GBL_DSN_DB2_RUNLIB_V10
- GBL_DSN_DB2_RUNLIB_V11
- GBL_DSN_DB2_RUNLIB_V12
- GBL_DSN_DB2_DSNEXIT
- If OMEGAMON for CICS TG is configured, uncomment and customize the following parameter:
- If OMEGAMON for IMS on z/OS is configured, uncomment and customize the following parameter:
- If OMEGAMON for Messaging on z/OS is configured, uncomment
and customize the following parameters:
- GBL_DSN_WMQ_SCSQANLE
- GBL_DSN_WMQ_SCSQAUTH
- GBL_DSN_WMQ_SCSQLOAD
- Press F3 to save the changes and return to the Customize
PARMGEN Configuration Profile Members panel.
- If support for variables is enabled, replace the contents
of the variables profile of the new RTE with the contents of the variables
profile for the RTE you are cloning.
- Select option 3. The variables profile for the new RTE
is opened in edit mode.
- Delete the contents of the profile using the standard
TSO command.
- Replace the contents of the profile with the contents
of the variables profile of the cloned RTE.
- Press F3 to save the changes, then press F3 to return to
the main Workflow panel.