To set up the work environment for an RTE, you specify
the type of RTE that is being configured, set RTE-specific values,
and select the products to be configured in the environment. Then
you submit the KCIJPCFG job, which uses the values you provide to
allocate the work libraries, update the interim libraries, and create
the configuration profiles for the RTE. You can use the model @MDLRFV
to set up the new RTE, or configure it from scratch.
Procedure
Select Set up PARMGEN work environment for
an RTE from the 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.)
To use the IBM-provided model RTE, enter a question mark
(?) on the first line and select @MDLRFV from the list of model profiles.
To create an RTE from scratch, leave the field blank. As appropriate,
specify the Install Job Generator output library and job card data.
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. The values on this panel are read from the profile library
and runtime member you specified on the preceding panel.
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.
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. If you selected the model profile, the panel contains
the values shown in the following figure. If you are configuring the
RTE from scratch, the panel displays the IBM® defaults.
KCIP@PG3 SET UP/REFRESH 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: Full RTE w/ Remote TEMS/Agents w/ variables_____
RTE_TYPE: FULL____ (Full, Sharing)
RTE_HILEV: TDITN.IDTST_____________________________ (ex.: TDITN.IDTST
(&hlq portion of Non-VSAM RK* HLQ=&hlq.&rte_name)
RTE_VSAM_HILEV: TDITN.IDTST_____________________________ (ex.: TDITN.IDTST
(&hlq portion of VSAM RK* HLQ=&hlq.&rte_name)
If any RTE dataset HLQ-related parameter values are NONSMS-managed:
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_SMS_PDSE_FLAG: Y (Y, N) (Allocate Non-VSAM PDSE libraries)
If RTE_TYPE is SHARING:
RTE_X_HILEV_SHARING: ___________________________________ (ex.: TDITN.IDTST)
(&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: Y (Y, N) (System/User variables flag)
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: &OMEGSAF._______________________________________
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 (Y, N) (Configure TEMS in this RTE)
RTE_TEMS_NAME_NODEID: &SYSNAME.:CMS______________________ (e.g.,DEMO:cms))))
KDS_TEMS_TYPE: REMOTE__ (Hub, Remote)
KDS_TEMS_HA_TYPE: __ (HA=High Availability Hub TEMS type)
ITM components' communication-related and started tasks settings:
RTE_TCP_PORT_NUM: &RTE_PORT.____________ (1-65535 port number)
RTE_VTAM_APPLID_PREFIX: K&SYSCLONE.___________ (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. (Look for the More:
+ which indicates that there is additional content on
the panel.)
If your environment is not SMS-managed, specify the VSAM
values. If you are using the IBM-provided model, you do need to make
any other changes.
If you are configuring the RTE from scratch, set RTE_TYPE to
FULL, RTE_SYSV_SYSVAR_FLAG to Y,
and KDS_TEMS_TYPE to REMOTE.
Optionally, you can customize the following parameters to use system or user-defined variables:
RTE_TEMS_NAME_NODEID (for example,
&SYSNAME.:CMS)
RTE_TCP_PORT_NUM (for example, &RTE_PORT.)
RTE_VTAM_APPLID_PREFIX (for example,
K&SYSCLONE.)
RTE_SECURITY_CLASS (for example, &OMEGSAF.)
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 library.
KCIP@PGI - INCLUDE (CONFIGURE) INSTALLED PRODUCT(S) IN THIS LPAR R Row 1 of 26
Command ===> Scroll ===> PAGE
Select ("S" or "/") products to CONFIGURE those product(s) in DEMO RTE.
Select or deselect products to include or exclude from configuration.
Products configured in the model or current RTE (reconfiguring) are preselected
When finished, change N to Y to confirm selections. Confirm ==> N (Y, N)
Kpp Component or Product Name and Version
---- ----------------------------------------------------------------------
/ KAH System Automation Monitoring Agent V350
/ KC5 OMEGAMON for CICS V550
/ KDO Tivoli Decision Support for z/OS Agent V181
/ KDS Tivoli Enterprise Monitoring Server V630
/ KD4 ITCAM for SOA Agent V711
/ KD5 OMEGAMON for DB2 PE/PM V540
/ KGW OMEGAMON for CICS TG V550
/ KI5 OMEGAMON for IMS V550
/ KJJ OMEGAMON for JVM V540
/ KMQ OMEGAMON for Messaging - MQ V750
/ KM5 OMEGAMON for z/OS V550
/ KNA NetView for z/OS Agent V621
/ KN3 OMEGAMON for Networks V550
/ 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 for Storage V540
/ KYN ITCAM for Application Diagnostics, TEMA V710.03
End of data
Deselect any products that you do not want to include in
the RTE, then change Confirm ==> N to Y,
and press Enter.
The 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 primary option menu.
The
KCIJPCFG job submits a second job, KCIJPPRF. Wait until both jobs
complete successfully before proceeding to the next step.
Results
The configuration software allocates the runtime libraries,
creates the configuration profiles, and populates the PARMGEN templates
in IKAN* libraries with runtime members for the products selected
for configuration.