After you configure one or more runtime environments, you
can clone them to other LPARs. Cloning runtime environments allows
you to replicate environments with considerably less customization.
There are seven main steps that are involved in cloning a runtime
environment:
Set up PARMGEN work environment for the runtime environment.
Clone customized WCONFIG members to the WCONFIG library of the
new runtime environment.
Update interim libraries and create configuration profiles.
Merge the configuration profile parameter values from the model
runtime environment into the new runtime environment.
Customize the configuration profiles.
Create the runtime environment members and jobs ($PARSE/$PARSESV).
Submit batch jobs to complete PARMGEN setup.
Steps 2, 3, and 4 are performed automatically by the configuration software. The location where
these steps are performed depends upon which transport scenario you are using to replicate the
environment to another LPAR.
To clone an existing RTE, you specify the fully-qualified name
of the profile for that RTE as the model profile on the first panel
when you set up the work environment (see Figure 1).Figure 1. Specifying
the fully qualified name of the RTE profile that is being cloned
KCIPQPG1 ---- SET UP PARMGEN WORK ENVIRONMENT FOR AN RTE (1 OF 3) -------------
Command ===>
Quick Configuration Mode
Specify the RTE model profile to use:
==> &hlq.&rte.WCONFIG(&clone_from) _______________________
- To create an RTE from scratch, leave this field blank.
- To create an RTE based on a predefined IBM model, type a ? in the
field and press Enter, then select the appropriate template.
- To create an RTE that is a clone of an existing PARMGEN RTE, specify
the WCONFIG profile library and RTE member name to clone;
for example: &hlq.&rte.WCONFIG(&clone_from)
- To create an RTE that is a clone of an ICAT-created RTE,
specify the ICAT RTE Batch member location and RTE member;
for example: &hlq.ICAT.INSTJOBS(DEMO)
- To reconfigure or upgrade this existing RTE, specify its values;
for example: (TDITN.IDTST.DEMO.WCONFIG(DEMO))
Specify the Install Job Generator (JOBGEN) output library if you want
PARMGEN to reuse CALLLIBS parameters from the JOBGEN repository:
==> ____________________________________________
(Type ? for last referenced JOBGEN library discovered, if any.)
Enter Jobcard data:
==> //SSABSA JOB (IDD),'%SYSMEMBER% - NAME',CLASS=A,________________________
==> // MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID.,REGION=0M___________________
==> //** RTE_NAME=%RTE_NAME%_________________________________________________
==> //** SYSJOBNAME=%SYSJOBNAME% SYSMEMBER=%SYSMEMBER%_______________________
F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGE
F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE
In the RTE configuration profile of the new RTE you might need
to change some or all of the following parameters, depending upon
the configuration of the RTE you are cloning.
If you are replicating runtime environments that share base libraries, to avoid loading the
libraries multiple times, designate one environment to load the base libraries by leaving
RTE_LOAD_SHARED_LIBS=Y for that environment only, and
disable loading of base libraries in all the other RTEs
(RTE_LOAD_SHARED_LIBS=N).
If you are changing a hub monitoring server to a remote, change KDS_TEMS_TYPE=HUB to
KDS_TEMS_TYPE=REMOTE.
If you are cloning an RTE that contains a hub monitoring server
and changing a hub to a remote, configure the remote to connect to
the hub.
This value is the TCP/IP host name (in IPV4 dotted decimal format)
of the z/OS® system where the
remote monitoring server is installed.
KDS_HUB_TCP_HOST
This value is the TCP/IP host name (in IPV4 dotted decimal format)
of the distributed system where the hub monitoring server is installed.
KDS_HUB_TCP_pipe_type_PORT_NUM
The value must be the port number of the hub for each protocol
selected.
If you are cloning an RTE that has OMEGAMON® for z/OS configured, and the model environment is already configured
as the primary sysplex proxy
(KM5_SYSPLEX_PROXY_POSITION=PRIMARY), ensure that cloned
environments are set to
KM5_SYSPLEX_PROXY_POSITION=BACKUP. Otherwise, the
KCIJPALO allocation job tries to allocate the sysplex-related persistent data store files for the
environment (or all the RKM5* PDS history data sets are left allocated but not initialized).
Tips:
The parameters that are discussed here are not the only parameters
that you might want to change. Many other KDS_* parameters
are needed for the remote monitoring server configuration. See Common parameters for information about KDS parameters.
After you set the parameters that are shown here, go through the entire
configuration profile to ensure that the parameter values are correct
for the configuration you want.
Be sure to uncomment any parameters that are needed for your configuration
but are commented out by default. For example, the configuration profile
for an RTE that contains a remote monitoring server that uses the
IP.PIPE protocol to communicate with the hub requires the KDS_HUB_TCP_PIPE_PORT_NUM parameter,
which is commented out by default. For such a configuration, you must
uncomment this parameter and insert the port number between the quotation
marks for the parameter value.
If the hub monitoring server to which the remote is reporting has
SDA enabled, uncomment and customize the following parameters in the
$GBL$USR global configuration profile:
GBL_DSN_SYS1_SBPXEXEC to the appropriate
SYS1 library (default is SYS1.SBPXEXEC)
GBL_HFS_JAVA_DIR1 (default is "/usr/lpp/java/IBM/J6.0"
Note: The Java™ directory
can be any working Java directory.
If variables are enabled, edit the variables configuration profile
to supply the values for any user-defined variables or any variables
whose values are being overridden in this environment.