To set up the work environment for an RTE, you specify
what type of RTE 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 select a model RTE to use to set up
the new RTE, or configure it from scratch.
Procedure
Select Set up PARMGEN work environment for an
RTEfrom 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.)
To use the IBM-provided model RTE configuration profile,
enter a question mark (?) in the first field, then select $MDLHA from
the presented list of models. The configuration software then populates
the field with the fully-qualified name for the RTE. 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 jobcard 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 jobcard is harvested from gbl_target_hilev.TKANSAM SMP/E
target library where the initial PARMGEN sample jobcard default is
supplied. If you specified a JOBGEN output library, the jobcard information
is harvested from that location. You can modify the retrieved data
as needed. The customized jobcard 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/Refresh 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 name 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.
KCIP@PG3 SET UP/REFRESH PARMGEN WORK ENVIRONMENT FOR Top of data
Command ===> Scroll ===> PAGE
Enter parameter values appropriate for the LPAR RTE=DEMO.
Press F1=Help for more information.
More: +
RTE_DESCRIPTION: Full RTE w/ High Availability Hub TEMS__________
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: N (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: ________________________________________________
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: DEMO:CMS__________________________ (e.g.,DEMO:cms))))
KDS_TEMS_TYPE: HUB_____ (Hub, Remote)
KDS_TEMS_HA_TYPE: HA (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)
Note: Type BACK to go back one panel. Type UTIL to access utility menu.
Depending upon your screen resolution, you might have to scroll
down (PF8) to see all the parameters. (Look for the More:
+ that indicates that there is additional content on the
panel.)
If you are using high-level index for an environment that
is not SMS-managed, specify values for the RTE_SMS* parameters.
If you select the IBM-provided model, you do not need to
make any other changes to this panel. If you are setting the RTE from
scratch, set KDS_TEMS_HA_TYPE to HA. Optionally,
you can customize the values for the following parameters as required
by your site requirements:
RTE_TEMS_NAME_NODEID
RTE_TCP_PORT_NUM
RTE_VTAM_APPLID_PREFIX
RTE_STC_PREFIX
Press Enter to proceed to the next panel.
The
following message is displayed:
KCIP@MSG ---------------- PARMGEN MESSAGES --------------------------
Command ===>
There are two conditions as to why this panel is presented:
1. You have asked to configure a High Availability (HA) Hub.
Only the TEMS (KDS) can be configured in an HA Hub RTE.
2. The only product installed in this SMP/E environment
is the TEMS (KDS).
RTE_NAME: SYSA
TEMS: Tivoli Enterprise Monitoring Server V630
GBL_TARGET_HILEV: TDITNT.DEMO
Press ENTER to continue.
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 Workflow main menu.
The
KCIJPCFG job submits a second job, KCIJPPRF. Do not proceed to the
next step until you see a return code indicating that both jobs have
finished successfully.
Results
The PARMGEN work libraries are allocated, and the configuration
profiles are created.