The work environment for a cloned runtime environment (RTE) is based upon the values inherited from the existing RTE. You can then modify those values to customize the new RTE. For example, you can add new products or convert a hub monitoring server to a remote.
About this task
To base a new RTE upon an existing RTE, you identify the RTE you want to clone, so that the configuration software can import values from that RTE.
Procedure
Select Set up PARMGEN work environment for an RTE from the Workflow - Primary Options Menu.
The first Set up PARMGEN work environment for an RTE panel is displayed.
KCIPQPG1 SET UP/REFRESH PARMGEN WORK ENVIRONMENT FOR AN RTE (1 OF 3) --------
Command ===>
Quick Configuration Mode
More: +
Specify the RTE model profile to use:
==> ______________________________________________________
- To create a new RTE based on a predefined IBM model, type a ? in
the field and press Enter, then select the appropriate template.
- To create a new 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 a new 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(SYSA))
- To create a new RTE from scratch, leave this field blank.
- To reconfigure or upgrade this existing PARMGEN RTE, specify its values;
for example: (TDITNT.IDTST.SYSA.WCONFIG(SYSA))
Customize jobcard data:
==> //TDITNT JOB (ACCT),'%SYSMEMBER% - NAME',CLASS=A,______________________
==> // MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID.,REGION=0M__________________
==> //** 0 0 RTE_NAME=%RTE_NAME% SYSMEMBER=%SYSMEMBER%_____________________
==> //** \_~_/ SYSJOBNAME=%SYSJOBNAME% JOBPARM SYSAFF=%SYSNAME%______________
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.)
In the first field, specify the fully-qualified name of the RTE configuration profile of the existing RTE that you want to clone: %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(%RTE_NAME%).
Review the following fields and make any changes required.
Jobcard data
If
a customized job card is already available, it is retrieved from the
ISPF user profile pool. If it is not available and if you did not
specify a JOBGEN output library, the job card is harvested from gbl_target_hilev.TKANSAM SMP/E
target library where the initial PARMGEN sample job card default is
supplied. If you specified a JOBGEN output library, the job card information
is harvested from that location. You can modify the retrieved data
as needed. The customized job card is saved in the ISPF user profile
pool and persists across ISPF sessions. On this panel, specify the
parameter values appropriate for your environment. In most cases,
the PARMGEN configuration parameters on this panel are required.
Press Enter to proceed to the next panel.
The Set up PARMGEN Work Environment for an RTE (2 of 3) panel (KCIP@PG2) is displayed.
KCIP@PG2 SET UP/REFRESH PARMGEN WORK ENVIRONMENT FOR AN RTE (2 OF 3) ---------
Command ===>
Quick Configuration Mode
GBL_USER_JCL: TDITN.IDTST.PARMGEN.JCL
RTE_PLIB_HILEV: TDITM.IDTST
RTE_NAME: SYSA
Enter parameter values appropriate for your environment:
UNIT / STORCLAS /
VOLSER MGMTCLAS
GBL_TARGET_HILEV: IBM.TARGET.ITM63055________________ ________ / ________ /
HLQ of SMP/E target (TK*) datasets ______ ________
GBL_SYSDA_UNIT: SYSDA___
Work datasets UNIT name
GBL_REGION: 0M______
JCL REGION (specify K/M suffix)
Note: Type BACK to go back one panel. Type UTIL to access utility menu.
Review the values on the panel and override them as necessary. Make sure that the GBL_TARGET_HILEV points to the libraries from which you executed TKANCUS for the new RTE.
GBL_TARGET_HILEV
Specifies the SMP/E
high-level qualifier of the SMP/E target (TK*) libraries.
GBL_SYSDA_UNIT
Specifies the non-VSAM
disk UNIT for global work data sets.
GBL_REGION
Specifies the JCL REGION
value override if other than the REGION=0M value. This is the required storage value in Kilobytes or
in Megabytes for PARMGEN batch jobs and product started tasks. The jobs contain the REGION=
parameter on the EXEC statement. The syntax of the JCL REGION parameter is either &valueK or
&valueM. Change this value as required by your installation. Specify K/M suffix (ex.: 4096K,
0M). The default is 0M.
Press Enter to proceed to the next panel.
The Set Up PARMGEN Work Environment for an RTE (3 OF 3) panel (KCIP@PG3) is displayed. The values on this panel are taken from the RTE that you are cloning, including any symbolics, if variables were enabled on that RTE.
KCIP@PG3 ---- SET UP PARMGEN WORK ENVIRONMENT FOR AN RTE (3 OF 3) -------------
Command ===> Scroll ===> PAGE
Enter parameter values appropriate for the LPAR RTE=DEMO.
Press F1=Help for more information.
More: -
RTE_DESCRIPTION: _____________________________
RTE_SMS_PDSE_FLAG: Y (Y, N) (Allocate Non-VSAM PDSE libs)
RTE_SMS_UNIT: __________ (Non-VSAM disk UNIT type)
RTE_SMS_VOLUME: __________ (Non-VSAM disk VOLSER)
RTE_SMS_MGMTCLAS: __________ (Non-VSAM disk MGMTCLAS)
RTE_SMS_STORCLAS: __________ (Non-VSAM disk STORCLAS)
RTE_SMS_VSAM_VOLUME: __________ (VSAM disk VOLSER)
RTE_SMS_VSAM_MGMTCLAS: __________ (VSAM disk MGMTCLAS)
RTE_SMS_VSAM_STORCLAS: __________ (VSAM disk STORCLAS)
RTE_TYPE: FULL____ (FULL, SHARING)
RTE_HILEV: TDITN.IDTST_______________
(&hlq portion of Non-VSAM RK* HLQ=&hlq.&rte_name)
RTE_VSAM_HILEV: TDITN.IDTST_______________
(&hlq portion of VSAM RK* HLQ=&hlq.&rte_name)
If RTE_TYPE is SHARING:
RTE_X_HILEV_SHARING: __________________________
(&hlq portion of shared RTE's HLQ=&hlq.&rte_share)
RTE_SHARE: ___________________________ ("SMP" value or *&rte_share)
(*&rte_share portion of shared RTE's HLQ=&hlq.&rte_share)
RTE_LOAD_SHARED_LIBS: Y (Y, N) (Is RTE updater of RO shared libs)
If symbolics (system variables or user-defined variables) will be used:
RTE_SYSV_SYSVAR_FLAG: N (Y, N) (System variable flag)
RTE_X_SYSV_OVERRIDE_SYMBOLS: N (Y, N) (Override local system symbols)
Security settings:
RTE_SECURITY_USER_LOGON: NONE______ (RACF, ACF2, TSS, NAM, None)
RTE_SECURITY_FOLD_PASSWORD_FLAG: Y (Y, N) (Fold password to upper case)
RTE_SECURITY_CLASS: ____________________________________________
RTE_X_SECURITY_EXIT_LIB: TDITN.IDTST.DEMO.RKANSAMU________________
GBL_DSN_ACF2_MACLIB: ____________________________________________
GBL_DSN_ACF2_MACLIB1: ____________________________________________
Local Tivoli Enterprise Monitoring Server (TEMS) settings in this LPAR RTE:
RTE_TEMS_CONFIGURED_FLAG: _ (Y, N) (Configure TEMS in this RTE)
RTE_TEMS_NAME_NODEID: DEMO:CMS______________________ (e.g.,IDTEST:cms)
KDS_TEMS_TYPE: HUB___ (Hub, Remote)
KDS_TEMS_HA_TYPE: __ (HA=High Availability Hub TEMS type)
ITM components' communication-related and started tasks settings:
RTE_TCP_PORT_NUM: 1918__________________ (1-65535 port number)
RTE_VTAM_APPLID_PREFIX: CTD___________________ (1-4 char.VTAM APPLID prefix)
RTE_STC_PREFIX: IBM___________________ (1-4 char.started task prefix)
Depending upon your screen resolution, you might have to scroll down (PF8) to see all the parameters. (Note the More: + which indicates that there is additional content on the panel.)
Review the parameter values and provide any LPAR-specific values for the new RTE. For example, you might want to change the description of the RTE, or change the monitoring server type from a hub to a remote.
If support for variables is enabled, you do not need to made any changes to this panel. If variables are not enabled, you must make the following changes:
Change the value of RTE_TEMS_NAME_NODEID to the host name of the new RTE (old_rte:CMS changed to new_rte:CMS).
If this is a shared DASD environment, you must modify the following parameters to keep them unique:
RTE_VTAM_APPLID_PREFIX
RTE_STC_PREFIX
If you make changes to any of the following RTE parameters on this panel, you must make the same changes to the corresponding product-specific parameters in the RTE profile (for example, *_STC_PREFIX), as the values of those parameters will be inherited from the cloned RTE.
RTE_SMS_UNIT
RTE_SMS_VOLUME
RTE_SMS_MGMTCLAS
RTE_SMS_STORCLAS
RTE_SMS_VSAM_VOLUME
RTE_SMS_VSAM_MGMTCLAS
RTE_SMS_VSAM_STORCLAS
RTE_HILEV
RTE_VSAM_HILEV
RTE_SECURITY_USER_LOGON
RTE_TEMS_NAME_NODEID
RTE_TCP_PORT_NUM
RTE_VTAM_APPLID_PREFIX
RTE_STC_PREFIX
Press Enter to proceed to the next panel.
The Include Products in this PARMGEN RTE panel (KCIP@PGI) is displayed. This panel lists all the products installed in the product target library. The products configured in the RTE you are cloning are indicated by a slash (/).
KCIP@PGI ------------ INCLUDE PRODUCTS IN THIS PARMGEN RTE - Row 1 to 19 of 26
Command ===> Scroll ===> PAGE
Select (/) product(s) to CONFIGURE those product(s) in RTE=$DOCRTE
All installed products have been preselected (/).
Select or deselect products to include or exclude from configuration.
When finished, change "N" to "Y" to confirm selections. Confirm ==> N (Y, N)
Kpp Product Name/Version
---- ----------------------------------------------------------------------
_ KAH System Automation Monitoring Agent V350
/ KC5 OMEGAMON AI for CICS V610
_ KDO Tivoli Decision Support for z/OS Agent V181
/ KDS Tivoli Enterprise Monitoring Server V630
_ KD4 ITCAM for SOA Agent V711
/ KD5 OMEGAMON AI for DB2 V610
/ KGW OMEGAMON AI for CICS TG V610
/ KI5 OMEGAMON for IMS V550
/ KJJ OMEGAMON AI for JVM V610
/ KMC OMEGAMON for Messaging - WebSphere MQ Configuration V730
/ KMQ OMEGAMON for Messaging - MQ V750
/ KM5 OMEGAMON AI for z/OS V610
_ KNA NetView for z/OS Agent V621
/ KN3 OMEGAMON AI for Networks V610
/ KOB OMEGAMON Enhanced 3270 User Interface V750
/ KQI OMEGAMON for Messaging - Integration Bus V750
_ KRG Advanced Audit for DFSMShsm Agent V260
_ KRH Advanced Reporting and Management for DFSMShsm Agent V260
_ KRJ Advanced Allocation Management Agent V330
_ KRK Automated Tape Allocation Manager for z/OS Agent V330
_ KRN Advanced Catalog Management Agent V260
_ KRV Advanced Backup and Recovery for z/OS Agent V240
_ KRW Tape Optimizer for z/OS Agent V220
/ KS3 OMEGAMON AI for Storage V610
_ KYN ITCAM for Application Diagnostics, TEMA V710.03
End of data
Deselect (by removing the slash) any products that you do not want to include in the new RTE. (For example, you might not want to configure another instance of the OMEGAMON enhanced 3270 user interface in this RTE.) Select any products that you want to add to the new RTE.
Change Confirm ==> N to Confirm ==> Y to confirm your choices, then press Enter.
The modified JCL for the KCIJPCFG job is displayed.
Review the JCL to understand what the job is doing, then submit the job and return to the Workflow - Primary Options Menu.
The KCIJPCFG job submits the KCIJPPRF job, which updates the work libraries and merges the values from the existing RTE. You will see a status of SUBMITTED until both jobs have completed. Do not proceed to the next step until you see a successful return code.
Results
The configuration software allocates
the work libraries, creates the configuration profiles with values
taken from the model RTE or specified on the KCIP@PG3 panel, and populates
the PARMGEN templates in IKAN* libraries with runtime members for
the products that are selected for configuration.
What to do next
Now you can review or customize the
configuration profiles for the RTE.