IBM Tivoli OMEGAMON XE and Tivoli Management Services …...The last two of the options on the menu are utilities. v Option U displays the PARMGEN work libraries (WK*), the GBL_USER_JCL

IBM Tivoli OMEGAMON XE and Tivoli Management Serviceson z/OSVersion 6 Release 3

PARMGEN Reference

SC22-5483-00

��

IBM Tivoli OMEGAMON XE and Tivoli Management Serviceson z/OSVersion 6 Release 3

PARMGEN Reference

SC22-5483-00

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 149.

This edition applies to version 5, release 1 of the IBM Tivoli OMEGAMON XE products and to version 6, release 3of IBM Tivoli Management Services on z/OS (product number 5698-A79) and to all subsequent releases andmodifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2012, 2013.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . v

Tables . . . . . . . . . . . . . . . vii

Chapter 1. Overview of the ParameterGenerator configuration method . . . . 1PARMGEN Workflow configuration tool . . . . . 3Configuration profiles . . . . . . . . . . . 4Imbed members . . . . . . . . . . . . . 5New in this release . . . . . . . . . . . . 5

Chapter 2. Implementation scenarios . . 7Scenario PGN01: Create a full runtime environmentwith a hub monitoring server and OMEGAMONagents . . . . . . . . . . . . . . . . 8Scenario PGN02: Create a sharing-with-base runtimeenvironment that uses system variables . . . . . 23Scenario PGN03: Configure a high-availability hubmonitoring server . . . . . . . . . . . . 39Scenario PGN04: Clone an existing environment andconvert its hub monitoring server to a remote . . . 52Scenario PGN05: Convert an existing ConfigurationTool environment to PARMGEN and upgrade it tothe current release . . . . . . . . . . . . 66

Extract the Configuration Tool parameters . . . 66Create and configure the converted PARMGENruntime environment . . . . . . . . . . 67

Chapter 3. SMP/E maintenancescenarios . . . . . . . . . . . . . 83Post-SMP/E maintenance steps . . . . . . . . 83Scenario SMPE01: Apply maintenance to an existingruntime environment without changing theconfiguration . . . . . . . . . . . . . . 83Scenario SMPE02: Apply SMP/E maintenance to anexisting RTE with configuration changes usingIBM-supplied configuration defaults for newfeatures. . . . . . . . . . . . . . . . 85Scenario SMPE03: Apply SMP/E maintenance to anexisting RTE with new configuration changes andoverride the IBM-supplied configuration defaults. . 87Scenario SMPE04: Upgrade an existing runtimeenvironment with no configuration changes . . . 88Scenario SMPE05: Upgrade an existing runtimeenvironment with configuration changes usingIBM-supplied configuration defaults . . . . . . 90Scenario SMPE06: Upgrade an existing runtimeenvironment and override defaults . . . . . . 92Scenario SMPE07: Stage an upgrade using a clonedenvironment . . . . . . . . . . . . . . 94

Chapter 4. Runtime environmentmaintenance scenarios. . . . . . . . 99Scenario RTE01: Add a new product into an existingPARMGEN runtime environment . . . . . . . 99Scenario RTE02: Upgrade a single OMEGAMONproduct in an existing runtime environment . . . 103Scenario RTE03: Change PARMGEN parameters 105Scenario RTE04: Convert a hub monitoring serverto a remote . . . . . . . . . . . . . . 108Scenario RTE05: Delete a product or componentfrom a runtime environment . . . . . . . . 113Scenario RTE06: Delete a runtime environment . . 117

Chapter 5. PARMGEN how-tos . . . . 119How to: Convert an existing static hub monitoringenvironment to a high-availability hubenvironment . . . . . . . . . . . . . . 119How to: Use KOBSUPDT security exits withPARMGEN . . . . . . . . . . . . . . 120How to: Override the currently configured defaultstorage limit within the RKANPARU(KppSYSIN)startup member . . . . . . . . . . . . 124How to: Avoid refreshing shared read-only baselibraries multiple times . . . . . . . . . . 127How to: Customize the RTE_BASE_MIDLEV . . . 129

Appendix A. Product codes . . . . . 133

Appendix B. PARMGEN utilities . . . 135Start the Workflow user interface . . . . . . . 135XF edit macro . . . . . . . . . . . . . 136KCIRPLBS online help macro . . . . . . . . 137

Appendix C. System variables . . . . 139

Documentation library . . . . . . . 143Shared OMEGAMON XE publications . . . . . 143IBM Tivoli Monitoring library . . . . . . . . 144

Documentation for the base agents . . . . . 145Other sources of documentation . . . . . . . 145

Support information . . . . . . . . 147

Notices . . . . . . . . . . . . . . 149Trademarks . . . . . . . . . . . . . . 150

Index . . . . . . . . . . . . . . . 151

© Copyright IBM Corp. 2012, 2013 iii

iv IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: PARMGEN Reference

Figures

1. PARMGEN libraries and the PARMGEN jobsthat create and populate them. . . . . . . 2

2. The PARMGEN Workflow main panel . . . . 33. The PARMGEN Workflow main panel 136

© Copyright IBM Corp. 2012, 2013 v

vi IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: PARMGEN Reference

Tables

1. Summary of scenario features . . . . . . . 82. Names of OMEGAMON security command

table exits . . . . . . . . . . . . . 1203. Source of the KppSUPDI KOBSUPDT

OMEGAMON security exits . . . . . . 120

4. Names of security command table exit byproduct and configuration method . . . . 121

5. Source of the OMEGAMON external securityexits and modules referenced in theKOBSUPDT KppSUPDI exit . . . . . . . 121

© Copyright IBM Corp. 2012, 2013 vii

viii IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: PARMGEN Reference

Chapter 1. Overview of the Parameter Generator configurationmethod

The Parameter Generator (PARMGEN) method is a runtime environment-centric approach toconfiguration. With the PARMGEN configuration method, you edit a comprehensive list of parameters forall the installed products and components that you want to configure on an LPAR. Then you submit aseries of jobs to create a complete runtime environment with the parameter values you specified. Theseparameters are stored in configuration profiles.

Figure 1 on page 2 shows the PARMGEN-created jobs and the libraries that they create and populate,grouped by functional area.

© Copyright IBM Corp. 2012, 2013 1

The PARMGEN method can be used for creating and maintaining new runtime environments and forupgrading existing ones that were created from product versions for which the PARMLIB configurationmethod was enabled. To upgrade from a product version earlier than the first PARMLIB-enabled version,you must use the Configuration Tool. To determine the earliest PARMLIB-enabled version of each of yourproducts, see the PARMLIB Technote at http://www.ibm.com/support/docview.wss?uid=swg21417935.

The PARMGEN Workflow configuration tool steps you through generating and submitting the jobs thatset up the work environment and create the required libraries and runtime members.

Figure 1. PARMGEN libraries and the PARMGEN jobs that create and populate them

2 IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: PARMGEN Reference

http://www.ibm.com/support/docview.wss?uid=swg21417935

PARMGEN provides a conversion tool (the KCIJPCNV job) you can use to create new runtimeenvironments based on the parameters of existing runtime environments configured using theConfiguration Tool.

This guide presents various scenarios for using the PARMGEN Workflow tool to deploy, configure, andmaintain OMEGAMON Monitoring Agents and the Tivoli Management Services on z/OS componentsthat they share.

For more information about OMEGAMON monitoring agents, Tivoli Management Services on z/OS, andbasic PARMGEN configuration instructions, see the IBM Tivoli OMEGAMON XE and Tivoli ManagementServices on z/OS: Common Planning and Configuration.

PARMGEN Workflow configuration toolYou can manually create and submit the jobs necessary to set up and configure runtime environments.However, you can also use the Parameter Generator (PARMGEN) Workflow tool. The PARMGENWorkflow interface guides you through the steps required to edit configuration profiles, and to create,edit, and submit the jobs that set up and tailor the runtime environment. It also provides access toPARMGEN libraries and utilities.

The PARMGEN Workflow user interface puts a wrapper around the entire PARMGEN configurationprocess. From the Parameter Generator (PARMGEN) Workflow main menu you can execute the stepsrequired to configure, and maintain your runtime environments and the products in them.

On the Workflow main panel, you specify the parameters to identify the environment you want to createor modify. Then you select from a list of options to create, clone, maintain, and upgrade runtimeenvironments.

--------------- PARAMETER GENERATOR (PARMGEN) WORKFLOW - WELCOME --------------Option ===> Scroll ===> PAGEEnter PARMGEN parameter values appropriate for your environment:GBL_USER_JCL: ____________________________________________

PARMGEN common/global library for RTEs (CONFIG DD lib. in STCs)RTE_PLIB_HILEV: ________________________

High-Level Qualifier (HLQ) of work libraries (IK*,WCONFIG,WK*)RTE_NAME: ________ (Type ? for a list of configured RTEs)

Runtime environment (RTE) name for this LPAR

Enter n (1-11) to perform tasks. Status DateEnter ns (1s-11s) to display detailed status. --------- ----------

1. KCIJPCFG Set up PARMGEN work environment for an RTE.2. $JOBINDX Review PARMGEN job index.3. KCIJPCCF Clone customized WCONFIG members. (COND)4. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup profile (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGEF7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE

Figure 2. The PARMGEN Workflow main panel

Chapter 1. Overview of the Parameter Generator configuration method 3

The last two of the options on the menu are utilities.v Option U displays the PARMGEN work libraries (WK*), the GBL_USER_JCL library, and the

RTE_X_SECURITY_EXIT_LIB common security exit library, in ISPF EDIT mode.v Option R clears the parameter values identifying the previous runtime environment, and the status and

dates for the various steps invoked.

Configuration profilesThe parameter values for each runtime environment are stored in configuration profiles. An LPAR-specificprofile contains the configuration values for each runtime environment and for the components andproducts configured in it. A global profile contains values for global system libraries. A third profilecontains user system variable definitions.

%RTE_NAME%LPAR-specific configuration file. This file contains parameters that define the configuration for theruntime environment itself and for all the shared components of the infrastructure and for eachproduct configured in the runtime environment. This profile is named for the runtimeenvironment and is stored in the WCONFIG data set.

$GBL$USRConfiguration file for global system libraries. This profile is stored in the WCONFIG data set.This file can be copied to other runtime environments if these global system libraries are typicallythe same across LPARS. Customization of this profile is required if this is not a ConfigurationTool-to-PARMGEN conversion, or if this is a product upgrade.

Review and possibly customization of this profile is required if the runtime environment is beingupgraded and there may be new GBL_* parameters introduced in the new version of the productthat were not in the original Configuration Tool batch member supplied. The batch member maystill be at the previous version of that product that is now being converted into PARMGEN, andupgraded at the same time. Review is also required to customize product-specific GBL_* commonor global parameters that may apply to more than one product or apply to several componentswithin a product family (for example, GBL_DB2_KD2_CLASSIC_STC parameter applies to allOMEGAMON XE for DB2 PE/PM components).

%RTE_NAME%System variables configuration file. This file is stored in the data set specified by theGBL_USER_JCL parameter.

Customization of the system variables configuration file is required if the runtime environment isenabled for system variables (RTE_SYSV_SYSVAR_FLAG=Y) and user-defined symbols are beingused. If variable overrides are enabled in the runtime environment configuration profile(RTE_X_SYSV_OVERRIDE_SYMBOLS=Y), the values for all types of symbolics must be definedin this member, regardless if they are system, KCIPARSE-extracted, or a user-defined.

PARMGEN maintains default LPAR ($CFG$IBM) and global profiles ($GBL$IBM), which are used as thetemplates for user-customized profiles. These default profiles are refreshed with any new or changedconfiguration parameters when the KCIJPUP1 job is run during upgrades or maintenance.

Default values are provided for all required parameters and for some optional ones. If you do not wantto customize these parameters, and you do not want to enable optional features, you can complete theconfiguration by accepting these defaults. Otherwise, you can specify custom values for these parameters.You can also specify custom values for optional parameters that have no defaults.

Tip: The PARMGEN configuration profiles can have a large number of parameters to review. It may beuseful, therefore, to EXCLUDE certain PARMGEN parameters while you focus on a particular configurationtask. For example, EXCLUDE all PARMGEN parameters that are for started tasks. Then FIND all occurrencesof these parameters so you can quickly do a CHANGE ALL command. PARMGEN provides anEXCLUDE-FIND (XF) macro for this task (see “XF edit macro” on page 136.).


For help with the parameter values, consult the following resources:v Comments in the profilesv Online help for parameters (see “KCIRPLBS online help macro” on page 137 for more information)v PARMGEN technote http://www.ibm.com/support/docview.wss?uid=swg21417935v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Parameter Reference

v Parameter Reference for each product

Imbed membersPARMGEN configuration creates a set of files that get imbedded in a number of the most-commonlyupdated runtime members in the user libraries--such xKANCMDU(KppAGST), xKANPARU(KppENV),xKANPARU(KppSYSIN), xKANSAMU(&stc). These imbed files can be used to add new user-definedparameters that might otherwise be overwritten when maintenance or upgrades are performed, or tooverride existing values.

The imbed files include the following:Kpp$C*,Kpp$P* and Kpp@P*Kpp$S*KCI$XW2R

where * represents either ENV, SYSIN, or &stc_name. The override members are copied from the IK*interim staging libraries to the corresponding WCONFIG PARMLIB control library by the KCIJPUP1 job.They are then imbedded into the appropriate members (such as started tasks and profiles) by the $PARSEor $PARSESV job. These files are not overlaid during maintenance or upgrades unless they are renamed.Edit these files before you run the PARSE/PARSESV job.

You can edit these files from the PARMGEN Workflow user interface. Select option U from the PARMGENWorkflow main to view and edit the files. After you have customized the files, you can copy the tailoredversions from one runtime environment to another. The KCIJPCCF job can be used to copy them.

Individual products may include their own imbed members. See the product documentation for moreinformation.

New in this releaseThe configuration scenarios in this guide have been reorganized and updated to reflect changes to thePARMGEN configuration method.

The changes in this guide reflect changes introduced in the following APARs for FMID HKCI310:v OA40035 (PTF UA67172 4Q12)v OA40649 (PTF UA67787 1Q13A)

For more information, see “New in this release” in the IBM Tivoli OMEGAMON XE and Tivoli ManagementServices on z/OS: Common Planning and Configuration Guide.

Chapter 1. Overview of the Parameter Generator configuration method 5



Chapter 2. Implementation scenarios

The scenarios in this section are aimed at both novice and experienced PARMGEN users. Users new toboth PARMGEN and Tivoli Management Services will find scenarios PGN01 through PGN04 particularlyhelpful both in building their initial runtime environment and in understanding the structure of the TivoliManagement Services and OMEGAMON environments. Scenario PGN05 is intended more forexperienced users aiming to upgrade their existing Tivoli Management Services and OMEGAMONenvironments.

Note: These scenarios build upon one another. For example, the runtime environment in scenario 2imports values specified for the runtime environment created in scenario 1.

Scenarios involving maintenance-type tasks that you can perform using PARMGEN are presented inChapter 3, “SMP/E maintenance scenarios,” on page 83 and Chapter 4, “Runtime environmentmaintenance scenarios,” on page 99.

“Scenario PGN01: Create a full runtime environment with a hub monitoring server and OMEGAMONagents” on page 8

In this scenario, you create a full runtime environment comprising a z/OS-based hub TivoliEnterprise Monitoring Server, OMEGAMON monitoring agents, and the OMEGAMON enhanced3270 user interface.

“Scenario PGN02: Create a sharing-with-base runtime environment that uses system variables” onpage 23

In this scenario, you create a new runtime environment that shares libraries with a baseenvironment named BASE2 which has system variables enabled. This environment comprises az/OS-based remote Tivoli Enterprise Monitoring Server , OMEGAMON monitoring agents, andthe OMEGAMON Enhanced 3270 user interface.

“Scenario PGN03: Configure a high-availability hub monitoring server” on page 39In this scenario, you create a new, full PARMGEN-based runtime environment comprising ahigh-availability hub Tivoli Enterprise Monitoring Server.

“Scenario PGN04: Clone an existing environment and convert its hub monitoring server to a remote”on page 52

In this scenario you clone an existing runtime environment. The new runtime environmentinherits the values and product set configured in the first environment, but you change its type tosharing-with-SMP/E and convert the static z/OS-based hub monitoring server into a remote. Youthen configure the remote to report to the high-availability hub monitoring server built as part of“Scenario PGN03: Configure a high-availability hub monitoring server” on page 39.

“Scenario PGN05: Convert an existing Configuration Tool environment to PARMGEN and upgrade itto the current release” on page 66

In this scenario, you upgrade the z/OS-based Tivoli Enterprise Monitoring Server andOMEGAMON monitoring agents through a Configuration Tool-to-PARMGEN conversion of theruntime environment. The new environment is similar to the runtime already set up in scenarioPGN02. It shares files with a base environment named BASE2 for which system variables areenabled.

Tips:

v These scenarios assume that you are using the PARMGEN Workflow interface to perform theconfiguration steps. For instructions on launching the interface, see “Start the Workflow user interface”on page 135.

v For information on getting help for parameters, see “KCIRPLBS online help macro” on page 137.v For locating and changing values for related parameters, see “XF edit macro” on page 136.


Table 1. Summary of scenario features

Scenario RTE name RTE type TEMS typeConverted/Cloned/Upgraded System variables

PGN01 PLB1SP22 Full Hub No No

PGN02 PLB3SYSG Sharing-with-base Remote No Yes

PGN03 PLBHAHUB Full HA hub No No

PGN04 PLB2SP23 Sharing-with-SMP/E Remote Cloned No

PGN05 PLB3SP13 Sharing-with-base Remote Converted/upgrade

Yes

Scenario PGN01: Create a full runtime environment with a hubmonitoring server and OMEGAMON agentsThis scenario creates a full runtime environment comprising a z/OS-based hub monitoring server,OMEGAMON monitoring agents, and the OMEGAMON enhanced 3270 user interface.

About this task

This scenario involves 6 steps:1. Set up PARMGEN work environment for the runtime environment.2. Update interim libraries and create the PARMGEN configuration profiles.3. Customize the configuration profiles.4. Validate the profile parameter values.5. Create the runtime members and jobs.6. Submit batch jobs to complete PARMGEN setup.

After you have completed these steps, you can complete any configuration steps required outside theconfiguration software and start the products.

Follow this step-by-step procedure to create the sample runtime environment.

Procedure1. Set up the PARMGEN work environment.

a. On the Parameter Generator (PARMGEN) Workflow main panel, specify values for theGBL_USER_JCL, RTE_PLIB_HILEV, and RTE_NAME fields for this runtime environment, asshown in the following example.


KCIP@PG0 ------ PARAMETER GENERATOR (PARMGEN) WORKFLOW - WELCOME ------ NEW RTEOption ===> 1 Scroll ===> CSREnter PARMGEN parameter values appropriate for your environment:GBL_USER_JCL: TSTEST.SYSPLEX.PARMGEN.JCL___________________

PARMGEN common/global library for RTEs (CONFIG DD lib. in STCs)RTE_PLIB_HILEV: TSTEST.&userid____________

High-Level Qualifier (HLQ) of work libraries (IK*,WCONFIG,WK*)RTE_NAME: PLB1SP22 (Type ? for a list of configured RTEs)




These parameters specify initial setup and global parameter values.

GBL_USER_JCLSpecifies the name of the data set of the PARMGEN global user JCL library. If the runtimeenvironment is enabled for system variables, this data set is concatenated in the CONFIGDDNAME of product started tasks. If the data set does not exist, you are prompted tocorrect the name or allocate the data set.

The PARMGEN global user JCL library is also where the PARMGEN process creates thesystem variables configuration profile. Customization of this member is required if aruntime environment is enabled for system variables and you are using user-definedsymbols or overriding the default values for system symbols. If the data set does not exist,you are prompted to correct the name or allocate the data set.

Important: The GBL_USER_JCL library keeps track of the different runtime environmentdefinitions such as KCIJPCFG values and PARMGEN job status and date in the KCIDJP02member. If you switch GBL_USER_JCL libraries, ensure that you copy the members to thenew GBL_USER_JCL. Otherwise, PARMGEN will not be able to carry forward informationabout existing runtime environment definitions tracked in the current GBL_USER_JCLlibrary. However, if you copy the members over to the new GBL_USER_JCL, then the$GBL$IBM and $GBL$USR global configuration profiles for each runtime environmentstored in the runtime environment-specific WCONFIG libraries must be adjusted to pointto the new name.

In addition, the GBL_USER_JCL library must not be the same library as the runtimeenvironment's WCONFIG runtime environment profile library. The PARMGEN WCONFIGcontrol library is where configuration profiles and other members are stored by theKCIJPUP1 job.

RTE_PLIB_HILEVSpecifies the non-VSAM high-level qualifier that you want to use for the followingPARMGEN work libraries:v WCONFIG control library where configuration profiles and other members are stored

by the KCIJPUP1 job.

Chapter 2. Implementation scenarios 9

v Interim staging (IK*) libraries where PARMGEN product runtime members (templateversions) are stored by the KCIJPUP1 job.

v Work output (WK*) libraries where PARMGEN file-tailored runtime members and jobsare created by the $PARSE or $PARSESV job.

RTE_NAMESpecifies a unique name for the runtime environment that you are configuring. The namethat you specify is appended to the RTE_PLIB_HILEV values to make each set ofPARMGEN and runtime libraries unique: %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(%RTE%).

b. Select option 1 from the main menu to set up the PARMGEN work libraries for the PLB1SP22environment. The first Set up PARMGEN work environment for an RTE panel is displayed.

KCIP@PG1 ---- SET UP PARMGEN WORK ENVIRONMENT FOR AN RTE (1 OF 3) -------------Command ===>

Specify the RTE profile library and member name that fits your scenario:==> ___________________________________________________ (ex:&dset(&rte))- If creating a brand new RTE, leave this field blank. **or**- If creating another new RTE and you want to clone a PARMGEN-created

RTE’s configured product set, specify the WCONFIG profile library andRTE member name to clone (ex.: &hlq.&rte.WCONFIG(&clone_from)). **or**

- If reconfiguring or upgrading this existing PLB3SYSG RTE, specify itsvalues (TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22)) **or**

- If converting an ICAT-created RTE to PARMGEN mode, specify the ICATRTE Batch member location and RTE member (ex.: &hlq.INSTJOBS(PLB1SP22))

Specify the Install Job Generator (JOBGEN) output library if you wantPARMGEN to reuse CALLLIBS parameters from the JOBGEN repository:==> ____________________________________________

(Type ? for last referenced JOBGEN library discovered, if any.)Enter Jobcard data:==> //&userid.J JOB (ACCT),'%SYSMEMBER% ,,username',CLASS=A,____________________==> // MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID.,REGION=0M_________________==> //** RTE_NAME=%RTE_NAME%________________________________________________==> //** SYSJOBNAME=%SYSJOBNAME% SYSMEMBER=%SYSMEMBER%______________________

c. You are configuring a new runtime environment, so leave the first field blank. If appropriate,specify the Install Job Generator output library and jobcard data.

d. Press Enter to proceed to the next panel. If the GBL_USER_JCL data set does not exist, you arepresented with the following verification screen:

KCIPPLBP ------------ USER JCL LIB PROCESSING ----------------------COMMAND ===>

The specified User JCL library does not exist.- Press ENTER to ALLOCATE NEW like TKANCUS.- Correct dsname and press ENTER to use an existing dataset.- Press F3 to abort processing.

GBL_USER_JCL:TSTEST.SYSPLEX.PARMGEN.JCL____________________________

Enter=Next F3=End/Cancel

e. Perform one of the following steps:v Press Enter to allocate a new data set.v Specify the desired data set name then press Enter.

The Set Up PARMGEN Work Environment for an RTE (2 OF 3) panel (KCIP@PG2) is displayed.f. Specify the values as shown in the following example panel, then press Enter.

Note that this is necessary only for the first runtime environment. These values are stored forharvesting for the next environment. If you specified the JOBGEN repository in the previousKCIP@PG1 panel, the GBL_TARGET_HILEV and GBL_SYSDA_UNIT fields are filled outautomatically, as PARMGEN reuses the data from the repository.


KCIP@PG2 ----- SET UP PARMGEN WORK ENVIRONMENT FOR AN RTE (2 OF 3) ------------COMMAND ===>

GBL_USER_JCL: TSTEST.SYSPLEX.PARMGEN.JCLRTE_PLIB_HILEV: TSTEST.&useridRTE_NAME: PLB1SP22

Enter parameter values appropriate for your environment:

GBL_INST_HILEV: ___________________________________HLQ of ICAT INSTLIB/INSTJOBS installation datasets

GBL_TARGET_HILEV: TSTEST.ITM62351____________________HLQ of SMP/E target (TK*) datasets

GBL_SYSDA_UNIT: SYSDA___Non-VSAM disk UNIT (global work datasets)

Enter=Next F1=Help F3=End/Cancel

The Set up PARMGEN Work Environment for an RTE (3 OF 3) panel (KCIP@PG3) is displayed.g. Specify the appropriate values, then press Enter. Depending on your screen resolution, you may

have to scroll down (PF8) to see all the parameters. (Note the More: + indicating that there isadditional content on the panel.) The values you specify on this panel are inherited by all theproducts and components in the runtime environment.

KCIP@PG3 ---- SET UP PARMGEN WORK ENVIRONMENT FOR AN RTE (3 OF 3) -------------Command ===> Scroll ===> PAGE

Enter parameter values appropriate for your RTE=PLB1SP22.Note: See F1=Help for SMS-related and RTE HLQ-related considerationswhen VOLUME, UNIT, STORCLAS, and MGMTCLAS parameters are required forthe global RTE_* parameters and the Kpp_* product-specific parameters.

More: +RTE_SMS_PDSE_FLAG: Y (PDSE flag (Y, N))

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_HILEV: TSTEST.&userid____________ (Non-VSAM prod. RK* HLQ)RTE_VSAM_HILEV: TSTEST.&userid____________ (VSAM production RK* HLQ)

RTE_TYPE: FULL_ (FULL, SHARING)RTE_SHARE: ________________________ (SMP or shared RTE name)RTE_X_HILEV_SHARING: ________________________ (HLQ of shared RTE)RTE_TEMS_CONFIGURED_FLAG: Y (Y, N)RTE_TEMS_NAME_NODEID: PLB1SP22:CMS_______________ (e.g., RTE1:cms)RTE_STC_PREFIX: CANS______________________ (Started task prefix)RTE_VTAM_APPLID_PREFIX CTD_______________________ (VTAM APPLID prefix)RTE_SYSV_SYSVAR_FLAG: N_________________________ (System variable flag)RTE_X_SYSV_OVERRIDE_SYMBOLS: N (Y, N) (SysVar override flag)RTE_SECURITY_USER_LOGON: NONE____ (RACF, ACF2, TSS, NAM, SAF, None)RTE_SECURITY_FOLD_PASSWORD_FLAG: Y (Fold to upper case (Y, N))RTE_SECURITY_CLASS: ________RTE_X_SECURITY_EXIT_LIB: TSTEST.&userid.PLB1SP22.RKANSAMU_______________GBL_DSN_ACF2_MACLIB: ____________________________________________ (If ACF2)KDS_TEMS_TYPE: HUB____ (Hub, Remote)KDS_TEMS_HA_TYPE: _______ (Hub TEMS type (HA))

Note: Type BACK to go back one panel.


For example:v If you do not want to configure a Tivoli Enterprise Monitoring Server in this environment, set

the RTE_TEMS_CONFIGURED_FLAG to N.v If you need to the change default prefix appended to all started tasks created by the

configuration software, or the prefix appended to the VTAM applids used by the productcomponents, to conform to site conventions, set the RTE_STC_PREFIX andRTE_VTAM_APPLID_PREFIX parameters.

The next panel, Display PARMGEN Environment Analysis (KCIP@PG4), displays the list ofproducts installed and available for configuration.

KCIP@PG4 ------------ DISPLAY PARMGEN ENVIRONMENT ANALYSIS - Row 1 to 14 of 14Command ===> Scroll ===> PAGE

Review message traffic before proceeding. These Kpp components are installedinto the TSTEST.ITM62351.TKANCUS SMP/E target library andare available for (re)configuration and/or upgrade into the RTE=PLB1SP22.Refer to the next panel ("EXCLUDE PRODUCTS FROM PARMGEN CUSTOMIZATION")for a legend of the Kpp components’ product names.

34 Components installed in TSTEST.ITM62351.TKANCUS:KAH KC2 KC5 KDF KDO KDS KD2 KD4 KD5 KGWKHL KI2 KI5 KMC KMQ KMV KM2 KM5 KNA KN3KOB KON KQI KRG KRH KRJ KRK KRN KRV KRWKS3 KT1 KWO KYN

End of data

h. Press Enter to display the Exclude Products From PARMGEN Customization panel (KCIP@PG5).i. Place an X before products that will not be configured in this runtime environment In the following

example, no products are excluded from configuration: all 34 products are configured.

KCIP@PG5 -------- EXCLUDE PRODUCTS FROM PARMGEN CUSTOMIZATION ---- Row 1 of 25Command ===> Scroll ===> CSR

Select (X) products to EXCLUDE from PARMGEN customization in RTE=PLB1SP22.

When finished, change "N" to "Y" to confirm selections. Confirm ==> Y (Y, N)

Kpp Product Name/Version---- ----------------------------------------------------------------------

_ KAH IBM Tivoli System Automation for z/OS V330_ KC5 IBM Tivoli OMEGAMON XE for CICS on z/OS V510_ KDO IBM Tivoli Decision Support for z/OS V181_ KDS Tivoli Enterprise Monitoring Server V630_ KD4 IBM Tivoli Composite Application Manager for SOA V711_ KD5 IBM Tivoli OMEGAMON XE for DB2 PE/PM V511_ KGW IBM Tivoli OMEGAMON XE for CICS TG on z/OS V510_ KHL IBM OMEGAMON z/OS Management Console V410_ KI5 IBM Tivoli OMEGAMON XE for IMS on z/OS V510_ KMC IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Configuration V710_ KMQ IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Monitoring V710_ KM5 IBM Tivoli OMEGAMON XE on z/OS V510_ KNA IBM Tivoli NetView for z/OS Agent V610_ KN3 IBM Tivoli OMEGAMON XE for Mainframe Networks V510_ KOB Tivoli OMEGAMON Enhanced 3270 User Interface V700_ KQI IBM Tivoli OMEGAMON XE for Messaging - WebSphere Message Broker V710_ KRG IBM Tivoli Advanced Audit for DFSMShsm V240_ KRH IBM Tivoli Advanced Reporting and Management for DFSMShsm V240_ KRJ IBM Tivoli Advanced Allocation Management for z/OS V320_ KRK IBM Tivoli Automated Tape Allocation Manager for z/OS V320_ KRN IBM Tivoli Advanced Catalog Management for z/OS V240_ KRV IBM Tivoli Advanced Backup and Recovery for z/OS V230_ KRW IBM Tivoli Tape Optimizer for z/OS V220_ KS3 IBM Tivoli OMEGAMON XE for Storage on z/OS V510_ KWO IBM Tivoli OMEGAMON DE on z/OS - OMEGAVIEW and OMEGAVIEW II V510_ KYN ITCAM for Application Diagnostics on z/OS V710


j. Specify Y in the Confirm ==> field and press Enter. The file-tailored %GBL_USER_JCL%(KCIJPCFG) job is presented.

k. Review the notes in the KCIJPCFG job and submit it. After you return to the Workflow mainpanel, you will see a jobstep indicator on the 1> line. This indicates that this is the last step youperformed. Also, notice the updated Status and Date for the KCIJPCFG job.

l. (Optional) Select option 2 ($JOBINDX Review PARMGEN job index) to review the job index forplanning purposes.

KCIP@PG0 ------ PARAMETER GENERATOR (PARMGEN) WORKFLOW - WELCOME ------Option ===> 2 Scroll ===> CSREnter PARMGEN parameter values appropriate for your environment:GBL_USER_JCL: TSTEST.SYSPLEX.PARMGEN.JCL__________________

PARMGEN common/global library for RTEs (CONFIG DD lib. in STCs)RTE_PLIB_HILEV: TSTEST.&userid__________




1> KCIJPCFG Set up PARMGEN work environment for an RTE. Submitted 2012/08/092. $JOBINDX Review PARMGEN job index.3. KCIJPCCF Clone customized WCONFIG members. (COND)4. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup PLB1SP22 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB1SP22 Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

2. Update the interim libraries and create the configuration profiles:a. Select option 4 from the Workflow main menu.

KCIP@PG0 ------ PARAMETER GENERATOR (PARMGEN) WORKFLOW - WELCOME ------ NEW RTEOption ===> 4 Scroll ===> CSREnter PARMGEN parameter values appropriate for your environment:GBL_USER_JCL: TSTEST.SYSPLEX.PARMGEN.JCL__________________





1. KCIJPCFG Set up PARMGEN work environment for an RTE. Submitted 2012/08/092> $JOBINDX Review PARMGEN job index. Viewed 2012/08/093. KCIJPCCF Clone customized WCONFIG members. (COND)4. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup PLB1SP22 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB1SP22 Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The KCIJPUP1 job is displayed.b. Review the notes section, then submit the KCIJPUP1 job.


3. Customize the PARMGEN profiles:a. On the main panel, select 8.






1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/092. $JOBINDX Review PARMGEN job index. Viewed 2012/08/093. KCIJPCCF Clone customized WCONFIG members. (COND)4> KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/095. KCIJPMC1 Merge profile from backup PLB1SP22 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB1SP22 Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSE Create the RTE members and jobs. RC= 00004 2011/10/1411. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The Customize PARMGEN Configuration Profile Members panel is displayed.

KCIP@PG6 ------ CUSTOMIZE PARMGEN CONFIGURATION PROFILE MEMBERS ---------------Option ===>(Required)* Select option 1 to customize the PLB1SP22 RTE LPAR profile:

1. PLB1SP22 RTE LPAR CONFIG profile in WCONFIG

(Conditional)* Select option 2 and/or 3 if applicable to this RTE:2. $GBL$USR Global parameters CONFIG profile in WCONFIG

(Required if this is not an ICAT-to-PARMGEN conversionor if this is a product upgrade - see F1=Help)

3. PLB1SP22 System Variables CONFIG profile in GBL_USER_JCL(TSTEST.SYSPLEX.PARMGEN.JCL)(Required if using user-defined symbols or overridingsystem symbols’ resolved values - see F1=Help)

*Note: The PARMGEN configuration profiles above are preserved(initially created by KCIJPUP1 or KCIJPUP2 job).

(Reference) IBM-supplied default profiles (refreshed by KCIJPUP1 job):4. $CFG$IBM IBM default RTE LPAR CONFIG profile in WCONFIG5. $GBL$IBM IBM default Global parameters CONFIG profile in WCONFIG6. $SYSIN $PARSE/$PARSESV SYSIN controls

(Optional) Select option 7 for member list of the WCONFIG library:7. WCONFIG TSTEST.&userid.PLB1SP22.WCONFIG

The applicable profiles for configuration are the LPAR profile (option 1) and the global parametersprofile (option 2).

b. Select option 1 to display the PLB1SP22 profile and complete the following steps to customize theprofile:1) Do a FIND on 'USER PROLOG' to begin logging overrides to the profile.


ISREDDE2 TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22)Command ===> Scroll ===> CSR****** ***************************** Top of Data ******************************000001 * *******************************************************************000002 * Member: KCICFG##000003 * Master Source: TSTEST.ITM62351.TKANSAM(KCIPRMLB)000004 * KCIJPUP1 Batch Job Output:000005 * TSTEST.&userid.PLB1SP22.WCONFIG($CFG$IBM) - IBM Default Copy000006 * TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22) - Customer Copy000007 *000008 * PURPOSE:000009 * $CFG$IBM/PLB1SP22 members are the default composite PARMGEN000010 * configuration profiles which contain parameter values for all the000011 * product parameters in a runtime environment (RTE). $CFG$IBM is000012 * the maintenance copy of the PLB1SP22 default copy and000013 * is available for reference only. $CFG$IBM is always refreshed000014 * during maintenance of any new or changed product configuration000015 * parameters...000180 * SECTION: USER PROLOG (OPTIONAL)000181 * *********************************************************************000182 *+---+-------------------------------------------------+--------+----+*000183 *|NO.| CHANGE DESCRIPTION | DATE | ID |*000184 *+---+---------------------------------------+---------+--------+----+*000185 *|@nn| |mm/dd/yy| xx |*000186 * *********************************************************************

2) If you intend to enable self-describing agent processing, which requires UNIX System Servicesdirectories, customize the RTE_USS_RTEDIR.

SP22 TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22)Command ===> Scroll ===> CSR000488 ** (Optional) If any products to be configured in this RTE require000489 ** Unix System Services (USS) directories created, specify the main RTE000490 ** HFS/zFS USS directory (#rtedir):000491 ** Note: This is also required if you are enabling the Self-describing000492 ** Agent (SDA) functionality in the z/OS TEMS and Agents:000493 ** Related PARMGEN CONFIG profile parameters (for SDA):000494 ** - GBL_HFS_JAVA_DIRn (typically in WCONFIG($GBL$USR))000495 ** - GBL_DSN_SYS1_SBPXEXEC (typically in WCONFIG($GBL$USR))000496 ** - RTE_USS_RTEDIR000497 ** - KDS_KMS_SDA000498 ** - KDS_TEMA_SDA000499 ** - Kpp_AGT_TEMA_SDA (per Kpp Agent exploiting SDA)000491 RTE_USS_RTEDIR "/tstest"

The GBL_ parameters are found in the WCONFIG($GBL$USR) member for furthercustomization.

3) (Optional) Customize RTE_VTAM_GBL_MAJOR_NODE.

SP22 TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22) - 01.00 Columns 00001 00072Command ===> C KCANDLE1 TSSND122 ALL Scroll ===> CSR000480 RTE_VTAM_GBL_MAJOR_NODE KCANDLE1

4) Change port numbers according to your site's convention by doing an EXCLUDE FIND of all_PORT parameters and then specifying alternative values for the defaults.


SP22 TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22) - 01.00 Columns 00001 00072Command ===> XF _PORT Scroll ===> CSR****** ***************************** Top of Data ******************************- - - - - - - - - - - - - - - - - - 485 Line(s) not Displayed000486 RTE_TCP_PORT_NUM 1918- - - - - - - - - - - - - - - - - - - 13 Line(s) not Displayed000654 KDS_TEMS_TCP_PIPE_PORT_NUM 1918 * IP.PIPE000655 KDS_TEMS_TCP_UDP_PORT_NUM 1918 * IP.UDP000656 KDS_TEMS_TCP_PIPE6_PORT_NUM "" * IP.PIPE for IPV6000657 KDS_TEMS_TCP_UDP6_PORT_NUM "" * IP.UDP for IPV6000658 KDS_TEMS_TCP_PIPES_PORT_NUM "" * Secure IP.PIPE000659 KDS_TEMS_TCP_PIPE6S_PORT_NUM "" * Secure IP.PIPE for IPV6- - - - - - - - - - - - - - - - - - - 72 Line(s) not Displayed000758 KDS_PH01_TEMS_TCP_PORT_NUM 1918- - - - - - - - - - - - - - - - - - - 38 Line(s) not Displayed001094 KC5_TEMS_TCP_PIPE_PORT_NUM 1918 * IP.PIPE001095 KC5_TEMS_TCP_UDP_PORT_NUM 1918 * IP.UDP001096 KC5_TEMS_TCP_PIPE6_PORT_NUM "" * IP.PIPE for IPV6001097 KC5_TEMS_TCP_UDP6_PORT_NUM "" * IP.UDP for IPV6001098 KC5_TEMS_TCP_PIPES_PORT_NUM "" * Secure IP.PIPE001099 KC5_TEMS_TCP_PIPE6S_PORT_NUM "" * Secure IP.PIPE for IPV6****** **************************** Bottom of Data ****************************

SP22 TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22) - 01.00 Columns 00001 00072Command ===> C ’ 1918 ’ ’ nnnnn ’ ALL Scroll ===> CSR- - - - - - - - - - - - - - - - - - 485 Line(s) not Displayed000486 RTE_TCP_PORT_NUM nnnnn- - - - - - - - - - - - - - - - - - - 13 Line(s) not Displayed000654 KDS_TEMS_TCP_PIPE_PORT_NUM nnnnn * IP.PIPE000655 KDS_TEMS_TCP_UDP_PORT_NUM nnnnn * IP.UDP000656 KDS_TEMS_TCP_PIPE6_PORT_NUM "" * IP.PIPE for IPV6000657 KDS_TEMS_TCP_UDP6_PORT_NUM "" * IP.UDP for IPV6000658 KDS_TEMS_TCP_PIPES_PORT_NUM "" * Secure IP.PIPE000659 KDS_TEMS_TCP_PIPE6S_PORT_NUM "" * Secure IP.PIPE for IPV6- - - - - - - - - - - - - - - - - - - 72 Line(s) not Displayed000758 KDS_PH01_TEMS_TCP_PORT_NUM nnnnn- - - - - - - - - - - - - - - - - - - 38 Line(s) not Displayed001094 KC5_TEMS_TCP_PIPE_PORT_NUM nnnnn * IP.PIPE001095 KC5_TEMS_TCP_UDP_PORT_NUM nnnnn * IP.UDP001096 KC5_TEMS_TCP_PIPE6_PORT_NUM "" * IP.PIPE for IPV6001097 KC5_TEMS_TCP_UDP6_PORT_NUM "" * IP.UDP for IPV6001098 KC5_TEMS_TCP_PIPES_PORT_NUM "" * Secure IP.PIPE001099 KC5_TEMS_TCP_PIPE6S_PORT_NUM "" * Secure IP.PIPE for IPV6- - - - - - - - - - - - - - - - - - 345 Line(s) not Displayed****** **************************** Bottom of Data ****************************

5) Imbed the APF-authorization commands for the libraries concatenated in the STEPLIB andRKANMODL DDNAMES all the started tasks by setting theRTE_X_STC_INAPF_INCLUDE_FLAG option to Y.

SP22 TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22) - 01.00 Columns 00001 00072Command ===> Scroll ===> CSR000528 ** (Optional) INAPF INCLUDE statement in product started tasks (STCs):000529 ** Specify "Y" if you want to generate this statement as uncommented000530 ** out in all product STCs: "INAPF INCLUDE MEMBER=%RTE_STC_PREFIX%APF"000531 ** This sample composite member contains APF-authorization commands for000532 ** libraries concatenated in the STC STEPLIB and RKANMODL DDNAMEs.000533 ** This member also contains the VARY activate command pointing to the000534 ** %RTE_VTAM_GBL_MAJOR_NODE% VTAM major node (TSSND122 by default).000535 ** Review %RTE_STC_PREFIX%APF and %RTE_STC_PREFIX%STRT WKANSAMU000536 ** members for more information.000537 RTE_X_STC_INAPF_INCLUDE_FLAG Y

6) Enable self-describing agent processing by uncommenting the KDS_KMS_SDA parameter:


SP22 TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22)Command ===> Scroll ===> CSR000839 ** Enable TEMS Self-Description Agent (SDA) processing:000840 ** This is required if you are enabling the Self-describing000841 ** Agent (SDA) functionality in the z/OS TEMS and Agents:000842 ** Note: By default, the KMS_SDA KDSENV parameter is:000843 ** - initially disabled @ the Hub TEMS (KMS_SDA=N)000844 ** - initially enabled @ the Remote TEMS (KMS_SDA=Y)000845 ** Customize the parameter accordingly by uncommenting out the000846 ** parameter and specifying the applicable value.000847 ** Related PARMGEN CONFIG profile parameters:000848 ** - GBL_HFS_JAVA_DIRn (typically in WCONFIG($GBL$USR))000849 ** - GBL_DSN_SYS1_SBPXEXEC (typically in WCONFIG($GBL$USR))000850 ** - RTE_USS_RTEDIR000851 ** - KDS_KMS_SDA000852 ** - KDS_TEMA_SDA000853 ** - Kpp_AGT_TEMA_SDA (per Kpp Agent exploiting SDA)000810 KDS_KMS_SDA "Y" * Y, N

Important: If you intend to enable granular control of the SDA, the HTTP or HTTPS port mustbe enabled at the hub monitoring server to allow the tacmd command-line utility to connectthrough the SOAP server interface. To enable the SOAP server, ensure that theKDS_TEMS_SOAP_SERVER_FLAG parameter is set to Y.

7) (Optional) If your site is using an encryption key other than the IBM-supplied defaultencryption key, activate Tivoli Management Services password encryption by uncommentingthe KDS_TEMS_SECURITY_KAES256_ENCKEY parameter and specifying the KAES256encryption key. This value must be the same across your monitoring environment. Thenuncomment and customize the GBL_DSN_CSF_SCSFMOD0 parameter.Specify a unique, 32-byte password encryption key. The value is case-sensitive. Be sure torecord the value you use for the key. You must use the same key during the installation of anycomponents that communicate with this monitoring server, such as the a remote monitoringserver. The ampersand (&) character cannot be part of the encryption key.

SP22 TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22)Command ===> Scroll ===> CSR000709 ** TEMS’ security settings:000710 KDS_TEMS_SECURITY_KDS_VALIDATE N000711000712 ** TEMS’ security settings: KAES256 encryption key000713 ** Note: This is required if you are enabling the ITM Password000714 ** Encryption (KAES256) across the ITM enterprise:000715 ** The "KDS_TEMS_SECURITY_KAES256_ENCKEY" value is encrypted000716 ** and xKANPARU(KAES256) member is created as part of the000717 ** xKANSAMU(KCIJPSEC) composite security job.000718 ** Related PARMGEN CONFIG profile parameter:000719 ** - GBL_DSN_CSF_SCSFMOD0 (DSN value is concatenated in the000720 ** TEMS STC’s STEPLIB DD)000721 KDS_TEMS_SECURITY_KAES256_ENCKEY "IBMTivoliMonitoringEncryptionKey"

8) If another monitoring server is using the same IP port number for connectivity in this LPAR,do an EXCLUDE FIND of all KDEB_INTERFACELIST parameters. Then uncomment eachparameter to enable it for the monitoring server and the agents.

SP22 TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22)Command ===> Scroll ===> CSR

- - - - - - - - - - - - - - - - - - 699 Line(s) not Displayed000702 KDS_TEMS_TCP_KDEB_INTERFACELIST "!*"- - - - - - - - - - - - - - - - - - 456 Line(s) not Displayed001159 KC5_AGT_TCP_KDEB_INTERFACELIST "!*"- - - - - - - - - - - - - - - - - - 190 Line(s) not Displayed001350 KGW_AGT_TCP_KDEB_INTERFACELIST "!*"- - - - - - - - - - - - - - - - - - 340 Line(s) not Displayed


The KDEB_INTERFACELIST parameters prevent IP bind problems.v If the agent requires network interface list support: If your site runs more than one

TCP/IP interface or network adapter on the same z/OS image, you can specify networkinterfaces to be used by monitoring servers and monitoring agents on a z/OS system. Youspecify the network interfaces in the IP communication protocol parameters for eachcomponent.

Note: Specify "!*" as the value if this agent runs on the same candidate z/OS image that isrunning a high-availability hub monitoring server.Related PARMGEN configuration profile parameters:– KDS_TEMS_TYPE– KDS_TEMS_HA_TYPE– KDS_TEMS_HA_INCLUDE_Kpp– KDS_TEMS_TCP_KDEB_INTERFACELIST

See the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: CommonParameter Reference for full information about these parameters.

v If the monitoring server requires network interface list support: If your site runs morethan one TCP/IP interface or network adapter on the same z/OS image, you can specifynetwork interfaces to be used by monitoring servers and monitoring agents on a z/OSsystem. You specify the network interfaces in the IP communication protocol parameters foreach component.Notes:

a) If this is a high-availability hub monitoring server, uncomment theKDS_TEMS_TCP_KDEB_INTERFACELIST, and set its value to !dvipa_address.

b) Specify "!*" as the value if this is a remote Tivoli Enterprise Monitoring Server that runson the same candidate z/OS image running a high-availability hub.

Related PARMGEN configuration profile parameters:– KDS_TEMS_TYPE– KDS_TEMS_HA_TYPE– KDS_TEMS_HA_INCLUDE_Kpp– Kpp_AGT_TCP_KDEB_INTERFACELIST

See the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: CommonParameter Reference for full information about these parameters.

9) Configure monitoring agents using the information in the product's Planning and ConfigurationGuide.

c. Save and close the profile.d. To customize the $GBL$USR global parameters profile, select option 2 on the Customize

PARMGEN Configuration Profile Members panel (KCIP@PG6).The profile is displayed:


SP22 TSTEST.&userid.PLB1SP22.WCONFIG($GBL$USR)Command ===> Scroll ===> CSR****** ***************************** Top of Data ******************************000001 * $GBL$USR BEGIN *-------------- PARMGEN CONFIGURATION ---------------*000002 * *******************************************************************000003 * MEMBER: KCI$GBLU000004 * MASTER SOURCE: TSTEST.ITM62351.TKANSAM(KCIPRMLB)000005 * PURPOSE: Input to the composite WCONFIG($GBL$USR) customer-overridable000006 * CONFIG profile member for global system libraries.000007 * IMPORTANT NOTES:000008 * 1. Customizing this member for applicable GBL_* parameters is000009 * a required step if this is not an ICAT-->PARMGEN RTE conversion.000010 * For a brand new RTE being set-up via PARMGEN, there are 2 required000011 * PARMGEN CONFIG profiles required for user customization:000012 * - WCONFIG($GBL$USR) global CONFIG profile000013 * - WCONFIG(PLB1SP22) LPAR-specific RTE CONFIG profile000014 * 2. $GBL$USR settings take precedence over $GBL$IBM. Customize000015 * WCONFIG:$GBL$IBM accordingly. It is ideal for copying to other000016 * WCONFIG RTEs if these global system libraries are typically the000017 * same across LPARs.000018 * 3. These values are being made available for configuration use000019 * to harvest the same information that may have already been000020 * customized from the Install Job Generator work performed.000021 * 4. $PARSE job creates WKANSAMU(KCIJPSYS) system set-up job.000022 * For KCIJPSYS planning purposes, note that KCIJPSYS job000023 * creates runtime members in the following system libraries.000024 * ========================== ==============================000025 * PARMGEN CONFIG Parameter Default PARMGEN CONFIG Value000026 * ========================== ==============================000027 * GBL_DSN_HZSPROC_LOADLIB "USER.LOADLIB"000028 * GBL_DSN_SYS1_PARMLIB "SYS1.PARMLIB"000029 * GBL_DSN_SYS1_PROCLIB "SYS1.PROCLIB"000030 * GBL_DSN_SYS1_SAXREXEC "SYS1.SAXREXEC"000031 * GBL_DSN_SYS1_VTAMLIB "SYS1.VTAMLIB"000032 * GBL_DSN_SYS1_VTAMLST "SYS1.VTAMLST"000033 * For more information about KCIJPSYS job, please refer to000034 * WCONFIG($JOBINDX) job index member.000035 * 5. For applicable GBL_* parameters that indicate "Related000036 * PARMGEN CONFIG profile parameters", these respective000037 * parameters typically indicate that if a function is to be000038 * enabled, refer to the related parameters as they also would000039 * require customization. The parameters are either customized000040 * in the WCONFIG(PLB1SP22) PARMGEN CONFIG LPAR profile or in000041 * the WCONFIG(%GBL$USR) PARMGEN CONFIG global profile.000042 * If this is an ICAT-->PARMGEN RTE conversion, then after the000043 * WCONFIG(KCIJPCNV) conversion job is run, the parameters (GBL_*000044 * and LPAR-specific parameters) are usually available for000045 * further customization in the WCONFIG(PLB1SP22) RTE LPAR profile.000046 * -----------------------------------------------------------------000047 ** ============================ ================================000048 ** PARMGEN CONFIG Parameter PARMGEN CONFIG Value000049 ** ============================ ================================000050 * -----------------------------------------------------------------000051 * SECTION: GLOBAL_SMP_RTE_ENVIRONMENT: SMP/E and CALLLIBS values:000052 * -----------------------------------------------------------------000053 **** SMP/E Target High-Level Qualifier (HLQ):000054 GBL_TARGET_HILEV "TSTEST.ITM62351"000055000056 **** PARMGEN User JCL:000057 GBL_USER_JCL TSTEST.SYSPLEX.PARMGEN.JCL..

e. Customize the following parameters, as appropriate:v GBL_DSN_HZSPROC_LOADLIBv GBL_DSN_SYS1_PARMLIBv GBL_DSN_SYS1_PROCLIBv GBL_DSN_SYS1_SAXREXECv GBL_DSN_SYS1_VTAMLST


v GBL_DSN_CSF_SCSFMOD0v GBL_HFS_JAVA_DIR1v GBL_DSN_SYS1_SBPXEXEC

SP22 TSTEST.&userid.PLB1SP22.WCONFIG($GBL$USR)Command ===> Scroll ===> CSR000068 **** Common system libraries (if applicable):000069 **** Health Check configuration values for HZSPRMCI and000070 **** HCK1%RTE_JCL_SUFFIX% xKANPARU members:000089 GBL_DSN_HZSPROC_LOADLIB "TSTEST.SYS1.LOAD"000090000073 **** (Required) GBL_DSN_SYS1_* system libraries:000092 GBL_DSN_SYS1_PARMLIB "TSTEST.SYS1.PARMLIB"000093 GBL_DSN_SYS1_PROCLIB "TSTEST.SYS1.PROCLIB"000094 GBL_DSN_SYS1_SAXREXEC "TSTEST.SYS1.SAXREXEC"000095 GBL_DSN_SYS1_VTAMLIB "TSTEST.SYS1.VTAMLIB"000096 GBL_DSN_SYS1_VTAMLST "TSTEST.SYS1.VTAMLST"..000115 **** GBL_DSN_CSF_* ICSF system libraries:000116 **** Note: This is required if you are enabling the ITM Password000117 **** Encryption (KAES256) across the ITM enterprise:000118 **** This library is concatenated in the TEMS STC’s STEPLIB DD:000119 **** Related PARMGEN CONFIG profile parameters:000120 **** - KDS_TEMS_SECURITY_KAES256_ENCKEY000121 GBL_DSN_CSF_SCSFMOD0 "CSF.SCSFMOD0"000122000123 **** Java home directory name:000124 **** Note: This is required if you are enabling the Self-describing000125 **** Agent (SDA) functionality in the z/OS TEMS and Agents:000126 **** "GBL_HFS_JAVA_DIRn" value becomes part of the000127 **** TEMS_JAVA_BINPATH parameter in the RKANDATV(KDSDPROF) member000128 **** that is created by the WKANSAMU(KCIJPUSP) USS preparation000129 **** job. "/bin" is added to the "GBL_HFS_JAVA_DIRn" Java home000130 **** directory value programmatically.000131 **** Related PARMGEN CONFIG profile parameters:000132 **** - GBL_DSN_SYS1_SBPXEXEC000133 **** - RTE_USS_RTEDIR000134 **** - KDS_KMS_SDA000135 **** - KDS_TEMA_SDA000136 **** - Kpp_AGT_TEMA_SDA000137 GBL_HFS_JAVA_DIR1 /Java/J6.0000138 **GBL_HFS_JAVA_DIR2 ""000139 **GBL_HFS_JAVA_DIR3 ""000140 **GBL_HFS_JAVA_DIR4 ""000141 **GBL_HFS_JAVA_DIR5 ""000142000143 **** z/OS UNIX System Services (USS) CLIST/EXEC library name:000144 GBL_DSN_SYS1_SBPXEXEC "SYS1.SBPXEXEC"000145..000164 * $GBL$USR END *-------------- PARMGEN CONFIGURATION ---------------******* **************************** Bottom of Data ****************************

f. Save your changes and close the profile.4. Validate the configuration profile values that you supplied:

a. On the Workflow main panel, select option 9.







1. KCIJPCFG Set up PARMGEN work environment for an RTE. Submitted 2012/08/102. $JOBINDX Review PARMGEN job index. Viewed 2012/08/103. KCIJPCCF Clone customized WCONFIG members. (COND)4. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/105. KCIJPMC1 Merge profile from backup PLB1SP22 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8> PLB1SP22 Customize PARMGEN configuration profiles. Edited 2012/08/139. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The KCIJPVAL job is displayed.b. Review the notes and submit the job. The parameter validation report is written to

%RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG($VALRPT) Enter 9s to view the report.c. If the job gets a condition code greater than 4, review the $VALRPT. Return to the previous step

and correct the parameter values, then resubmit the validation job.5. Create the WK* runtime members and WKANSAMU jobs:

a. On the Workflow main panel, select option 10 (Create the RTE members and jobs).






1. KCIJPCFG Set up PARMGEN work environment for an RTE. Submitted 2012/08/102. $JOBINDX Review PARMGEN job index. Viewed 2012/08/103. KCIJPCCF Clone customized WCONFIG members. (COND)4. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/105. KCIJPMC1 Merge profile from backup PLB1SP22 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB1SP22 Customize PARMGEN configuration profiles. Edited 2012/08/139> KCIJPVAL Validate PARMGEN profile parameter values. RC= 00000 2012/08/1310. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The $PARSE/$PARSESV: Create the RTE Members and Jobs (KCIP@PRS) panel is displayed.b. Select option 1 to submit the generated $PARSE composite job.


KCIP@PRS ---- $PARSE/$PARSESV: CREATE THE RTE MEMBERS AND JOBS --------------Option ===> 1

Select option 1 to SUBMIT the full $PARSE job in WCONFIG for RTE=PLB1SP22.Alternatively, select other options to SUBMIT $PARSE jobs individually.Press F1=Help for additional considerations when selecting options 2-5.

Note: Enter ns (1s-5s) for detailed task status. Status Date--------- ----------

1. $PARSE Composite $PARSE job** or **

2. $PARSECM IKANCMDU/WKANCMDU $PARSE job (Optional)3. $PARSEPR IKANPARU/WKANPARU $PARSE job (Optional)4. $PARSESM IKANSAMU/WKANSAMU $PARSE job (Optional)

5. $PARSEDV Generate listing of symbolics (Optional)

Note: If this is a reconfiguration of an existing PARMGEN-maintainedRTE, then after rerunning the $PARSESV, $PARSEPR or $PARSESMjob, you must rerun the WKANSAMU(KCIJVUPV) System VariableIEBUPDTE job next, to refresh the variable-named members.Please see the help panel for more information.

6. Submit the batch jobs to complete the PARMGEN setup:a. On the Workflow main panel, select option 11 (Submit batch jobs to complete PARMGEN setup).






1. KCIJPCFG Set up PARMGEN work environment for an RTE.2. $JOBINDX Review PARMGEN job index.3. KCIJPCCF Clone customized WCONFIG members. (COND)4. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup PLB1SP22 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB1SP22 Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10> $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The SUBMIT Submit batch jobs to complete PARMGEN setup (KCIP@SUB ) is displayed.


KCIP@SUB -------- SUBMIT BATCH JOBS TO COMPLETE PARMGEN SETUP -----------------Option ===> Scroll ===> PAGE

Select option 1 to SUBMIT the composite jobs in WKANSAMU for RTE=PLB1SP22.Alternatively, select other options to SUBMIT each job individually.Press F1=Help for additional considerations when selecting options 4-14.

Note: Enter ns (1s-14s) for detailed job/task status. Status Date--------- ----------

1. KCIJPSUB Composite SUBMIT job (See JCL comments)** or **

2. KCIJPALO Allocate runtime libraries RC= 00000 2012/02/293. KCIJPLOD Load TK*->RK* runtime libraries RC= 00000 2012/04/064. KCIJPSEC Product security (Conditional) RC= 00000 2012/02/295. N/A System Variables IEBUPDTE (Conditional) RC= 00000 2012/04/136. KCIJPUSP USS preparation (Conditional) RC= 00000 2012/02/277. KCIJPUSS USS system set-up (Authorization required) RC= 00000 2012/04/138. KCIJPSYS System set-up (Authorization required) RC= 00000 2012/02/299. KCIJPLNK ASM/Link RKANMODU modules (Conditional) RC= 00000 2012/02/2910. KCIJPIVP Configuration verification RC= 00000 2012/04/0611. KCIJPCPW Backup WK* work libraries (Conditional) RC= 00000 2012/12/1512. KCIJPCPR Backup RK* production user libs (Conditional) RC= 00000 2012/12/1513. KCIJPW2R WK*->RK* deployment (Conditional) RC= 00000 2012/04/1314. KCIJPMNT Composite maintenance job (Conditional) RC= 00000 2012/09/12

b. Select option 1 to submit the KCIJPSUB master submit job, or select the other options to submiteach job separately.

c. If you select option 1, first review the KCIJPSUB job, and edit the job according to which of theconditional jobs need to be submitted automatically.

d. Submit the master SUBMIT job, and check for good condition codes.

Note: The WSUPERC step will encounter an informational condition code of 4 if OMEGAMONXE for DB2 on z/OS is not configured in this runtime environment as there are no xKD2* librariesto compare.

e. Review the resulting output:v $IVPRPT report, which is stored in the WCONFIG libraryv WSUPERC SYSTSPRT report, which is stored in the WSUPERC sequential library

f. Correct any errors, and rerun any jobs that did not complete successfully.

Results

You have created runtime environment PLB1SP22.

What to do next

Perform the applicable steps to complete the configuration outside the configuration software, asdocumented in your planning and configuration guides, and start the products.

Scenario PGN02: Create a sharing-with-base runtime environment thatuses system variablesIn this scenario, you create a new runtime environment which shares its libraries with a baseenvironment that has system variables enabled. In configuring the new environment, you enable it toexploit system variables and configure a remote monitoring server, OMEGAMON monitoring agents, andthe Tivoli OMEGAMON enhanced 3270 user interface.


About this task

This scenario involves 7 steps:1. Set up PARMGEN work libraries.2. Clone the customized WCONFIG members from an existing runtime environment.3. Update the libraries and create the profiles.4. Customize the configuration profiles.5. Validate the parameters6. Create the runtime members and jobs.7. Submit the batch jobs to complete the set up of the runtime environment.

Step 2 is optional. This step clones user-customized members (such as override imbeds, $JOBCARD, and$GBL$USR) from an existing WCONFIG library to a new one. If you do clone the WCONFIG librariesand you want to use different values for some parameters, you will need to edit the $GBL$USR profileby uncommenting parameters and supplying the appropriate values.

This scenario assumes that you have launched the PARMGEN Workflow user interface (see “Start theWorkflow user interface” on page 135).

Procedure1. To set up the PARMGEN work libraries for the PLB3SYSG environment, complete the following steps:

a. On the Workflow main panel, for RTE_NAME, specify the name of the new runtime environment(PLB3SYSG in this example). This name must contain the name of the LPAR on which the runtimeenvironment will run. Note that if you did not choose the R (RESET) option from the previousruntime environment, the values for GBL_USER_JCL, RTE_PLIB_HILEV, and RTE_NAME arecarried forward from the previous session. In this case, simply change the RTE_NAME value fromPLB1SP22 to PLB3SYSG. If the values have not been carried over, specify the high-level qualifiersfor the JCL and work libraries shared by the new runtime environment and the base runtimeenvironment, as well as the name for the new runtime environment.

b. Select option 1 from the menu.

KCIP@PG0 ------ PARAMETER GENERATOR (PARMGEN) WORKFLOW - WELCOME ------ NEW RTEOption ===> 1 Scroll ===> CSREnter PARMGEN parameter values appropriate for your environment:GBL_USER_JCL: TSTEST.SYSPLEX.PARMGEN.JCL___________________


High-Level Qualifier (HLQ) of work libraries (IK*,WCONFIG,WK*)RTE_NAME: PLB3SYSG (Type ? for a list of configured RTEs)





Because the runtime environment you specified is a new one, you are asked if you want to resetthe definition values before you proceed:

KCIP@MSG ---------------- PARMGEN MESSAGES --------------------------COMMAND ===>

You have asked to configure a new RTE profile.This action is recommended to be preceeded by selectingOption "R" to reset RTE, status and date fieldsfor a new RTE.

Press ENTER to perform the reset for a new RTE.Press F3 to abort.

c. Press Enter. You are presented with a verification screen:

KCIP@PGP ---------------- PARMGEN MESSAGES --------------------------COMMAND ===>

This will clear the GBL_USER_JCL, RTE_PLIB_HILEV andRTE_NAME fields and all Status and Date fields.

Press ENTER to proceed. Press F3 to abort.

d. Press Enter. You are returned to the main Workflow panel.e. Select 1 again to begin setting up the work environment. The first Set up PARMGEN work

environment for an RTE panel (KCIP@PG1 is displayedf. Leave the first field (RTE profile library and member name) blank. If appropriate, specify the

Install Job Generator output library.




- If reconfiguring or upgrading this existing PLB3SYSG RTE, specify itsvalues (TSTEST.&userid.PLB3SYSG.WCONFIG(PLB3SYSG)) **or**

- If converting an ICAT-created RTE to PARMGEN mode, specify the ICATRTE Batch member location and RTE member (ex.: &hlq.INSTJOBS(PLB3SYSG))



g. Press Enter to proceed to the next setup panel.h. Review the values on the KCIP@PG2 panel and override where necessary. If you specified the

JOBGEN repository from the previous KCIP@PG1 panel, the GBL_TARGET_HILEV andGBL_SYSDA_UNIT values will already be filled out automatically, as PARMGEN reuses the datafrom the repository.


KCIP@PG2 ----- SET UP PARMGEN WORK ENVIRONMENT FOR AN RTE (2 OF 3) -------------COMMAND ===>

GBL_USER_JCL: TSTEST.SYSPLEX.PARMGEN.JCLRTE_PLIB_HILEV: TSTEST.&useridRTE_NAME: PLB3SYSG






i. Press Enter to proceed to the next panel. The third setup panel is displayed.


Enter parameter values appropriate for your RTE=PLB3SYS.Note: See F1=Help for SMS-related and RTE HLQ-related considerationswhen VOLUME, UNIT, STORCLAS, and MGMTCLAS parameters are required forthe global RTE_* parameters and the Kpp_* product-specific parameters.




RTE_TYPE: FULL_ (FULL, SHARING)RTE_SHARE: ________________________ (SMP or shared RTE name)RTE_X_HILEV_SHARING: ________________________ (HLQ of shared RTE)RTE_TEMS_CONFIGURED_FLAG: Y (Y, N)RTE_TEMS_NAME_NODEID: PLB3SYSG:CMS_______________ (e.g., RTE1:cms)RTE_STC_PREFIX: CANS______________________ (Started task prefix)RTE_VTAM_APPLID_PREFIX CTD_______________________ (VTAM APPLID prefix)RTE_SYSV_SYSVAR_FLAG: N_________________________ (System variable flag)RTE_X_SYSV_OVERRIDE_SYMBOLS: N (Y, N) (SysVar override flag)RTE_SECURITY_USER_LOGON: NONE____ (RACF, ACF2, TSS, NAM, SAF, None)RTE_SECURITY_FOLD_PASSWORD_FLAG: Y (Fold to upper case (Y, N))RTE_SECURITY_CLASS: ________RTE_X_SECURITY_EXIT_LIB: TSTEST.&userid.PLB3SYSG.RKANSAMU_______________GBL_DSN_ACF2_MACLIB: ____________________________________________ (If ACF2)KDS_TEMS_TYPE: HUB___ (Hub, Remote)KDS_TEMS_HA_TYPE: ______ (Hub TEMS type (HA))


j. Review the values on the panel and modify them as follows. Depending on your screen resolution,you may have to scroll down (PF8) to see all the parameters. (Note the More: + indicator on thepanel.)v Because the new runtime environment will share a base runtime environment, set the RTE_TYPE

parameter to SHARING.


v To create the Base runtime environment that this environment will share, customize theRTE_X_HILEV_SHARING to the high level qualifier for the base runtime environment andRTE_SHARE to the name of the runtime environment.

v Because you are going to use variables, set any occurrence of SYSG to &SYSNAME.. (For example,set RTE_TEMS_NAME_NODEID to PLB3&SYSNAME.:CMS.)

v If required by your site conventions, use RTE_STC_PREFIX to specify a prefix of up to 4characters to replace the default CANS prefix for the names of started tasks created by theconfiguration software. If you choose to use symbolics, you can use up to 18 characters thatresolve to 4 characters. For example, &SYSCLONE..

v If required by your site conventions, use RTE_VTAM_APPLID_PREFIX to specify a prefix of upto 4 characters (or a symbolic of up to 18 characters that resolve to 4) for all VTAM major nodesand applids. For example, TS&SYSCLONE..

v Set the RTE_SYSV_SYSVAR_FLAG parameter to Y to enable system variables.v Change the KDS_TEMS_TYPE parameter to REMOTE.

Tip: The RTE_X_SECURITY_EXIT_LIB library is used in the WKANSAMU(KCIJcSEC) security job.If security exits are typically shared across different runtime environments, you may even specify amore global security exit library that different environments can share.


Enter parameter values appropriate for your RTE=PLB3SYSG.Note: See F1=Help for SMS-related and RTE HLQ-related considerationswhen VOLUME, UNIT, STORCLAS, and MGMTCLAS parameters are required forthe global RTE_* parameters and the Kpp_* product-specific parameters.




RTE_TYPE: SHARING (FULL, SHARING)RTE_SHARE: BASE&SYSALVL.___________ (SMP or shared RTE name)RTE_X_HILEV_SHARING: TSTEST___________________ (HLQ of shared RTE)RTE_TEMS_CONFIGURED_FLAG: Y (Y, N)RTE_TEMS_NAME_NODEID: PLB3&SYSNAME.:CMS______________ (e.g., RTE1:cms)RTE_STC_PREFIX: TSS3_____________________ (Started task prefix)RTE_VTAM_APPLID_PREFIX TS&SYSCLONE._____________ (VTAM APPLID prefix)RTE_SYSV_SYSVAR_FLAG: Y_________________________ (System variable flag)RTE_X_SYSV_OVERRIDE_SYMBOLS: N (Y, N) (SysVar override flag)RTE_SECURITY_USER_LOGON: NONE____ (RACF, ACF2, TSS, NAM, SAF, None)RTE_SECURITY_FOLD_PASSWORD_FLAG: Y (Fold to upper case (Y, N))RTE_SECURITY_CLASS: ________RTE_X_SECURITY_EXIT_LIB: TSTEST.&userid.PLB3&SYSNAME..RKANSAMU_______GBL_DSN_ACF2_MACLIB: ____________________________________________ (If ACF2)KDS_TEMS_TYPE: REMOTE (Hub, Remote)KDS_TEMS_HA_TYPE: ______ (Hub TEMS type (HA))


k. After you have made any necessary changes, press Enter to proceed to the next panel(KCIP@PG4).KCIP@PG4 displays the list of products installed in the SMP/E target library and available forconfiguration.


KCIP@PG4 ------------ DISPLAY PARMGEN ENVIRONMENT ANALYSIS --- Row 1 to 6 of 6Command ===> Scroll ===> PAGE

Review message traffic before proceeding. These Kpp components are installedinto the TSTEST.ITM62351.TKANCUS SMP/E target library andare available for (re)configuration and/or upgrade into the RTE=PLB3SYSGRefer to the next panel ("EXCLUDE PRODUCTS FROM PARMGEN CUSTOMIZATION")for a legend of the Kpp components’ product names.

34 Components installed in TSTEST.ITM62351.TKANCUS:KAH KC2 KC5 KDF KDO KDS KD2 KD4 KD5 KGWKHL KI2 KI5 KMC KMQ KMV KM2 KM5 KNA KN3KOB KON KQI KRG KRH KRJ KRK KRN KRV KRWKS3 KT1 KWO KYNEnd of data

l. After you have reviewed the message traffic, press Enter to proceed to the next panel. The ExcludeProducts from PARMGEN Customization panel is displayed.

m. Place an X before any products that you do not want to configure in this environment. In thefollowing example, we exclude all products except for the OMEGAMON monitoring agents, theTivoli Enterprise Monitoring Server, and the OMEGAMON enhanced 3270 user interface.

KCIP@PG5 -------- EXCLUDE PRODUCTS FROM PARMGEN CUSTOMIZATION Row 1 to 24 of 24Command ===> Scroll ===> CSR

Select (X) products to EXCLUDE from PARMGEN customization in RTE=PLB3SYSG


Kpp Product Name/Version (Kpp* components configured in RTE profile)---- ----------------------------------------------------------------------

_ KC5 IBM Tivoli OMEGAMON XE for CICS on z/OS V510X KDO IBM Tivoli Decision Support for z/OS V181_ KDS Tivoli Enterprise Monitoring Server V630X KD4 IBM Tivoli Composite Application Manager for SOA V711_ KD5 IBM Tivoli OMEGAMON XE for DB2 PE/PM V511_ KGW IBM Tivoli OMEGAMON XE for CICS TG on z/OS V510X KHL IBM OMEGAMON z/OS Management Console V410_ KI5 IBM Tivoli OMEGAMON XE for IMS on z/OS V510_ KMC IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Configuration V710_ KMQ IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Monitoring V710_ KM5 IBM Tivoli OMEGAMON XE on z/OS V510_ KN3 IBM Tivoli OMEGAMON XE for Mainframe Networks V510_ KOB Tivoli OMEGAMON Enhanced 3270 User Interface V700_ KQI IBM Tivoli OMEGAMON XE for Messaging - WebSphere Message Broker V710X KRG IBM Tivoli Advanced Audit for DFSMShsm V240X KRH IBM Tivoli Advanced Reporting and Management for DFSMShsm V240X KRJ IBM Tivoli Advanced Allocation Management for z/OS V320X KRK IBM Tivoli Automated Tape Allocation Manager for z/OS V320X KRN IBM Tivoli Advanced Catalog Management for z/OS V240X KRV IBM Tivoli Advanced Backup and Recovery for z/OS V230X KRW IBM Tivoli Tape Optimizer for z/OS V220_ KS3 IBM Tivoli OMEGAMON XE for Storage on z/OS V510_ KWO IBM Tivoli OMEGAMON DE on z/OS - OMEGAVIEW and OMEGAVIEW II V510X KYN ITCAM for Application Diagnostics on z/OS V710

n. Change Confirm from N to Y, then press Enter. The file-tailored GBL_USER_JCL(KCIJPCFG) job ispresented.

o. Review the notes and values and submit the job. Return to the main Workflow panel.2. (Optional) Clone the customized members from the PLB1SP22 WCONFIG library.

a. Select option 3 from the Workflow main menu. The KCIJPCCF job is presented.b. Review the job to determine if you need to further modify the library concatenated in the

OLDWCNFG DDNAME.By default, this DDNAME already points to the WCONFIG library that you specified in the RTEprofile library field of the first work environment setup panel. If necessary, modify the job to point


to an existing WCONFIG library that contains the customized members you want cloned over tothe WCONFIG library for the new runtime environment.

c. Submit the job and return to the Workflow main menu.3. Select option 4 to update interim libraries and create profiles.






1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/142. $JOBINDX Review PARMGEN job index. Viewed 2012/08/143.> KCIJPCCF Clone customized WCONFIG members. (COND)4. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup PLB3SYSG (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB3SYSG Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSESV Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The KCIJPUP1 job is presented. Review the notes and values, then submit the job.4. Customize the configuration profiles for this runtime environment:

a. Select option 8 from the Workflow main menu.






1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/142. $JOBINDX Review PARMGEN job index. Viewed 2012/08/143. KCIJPCCF Clone customized WCONFIG members. (COND) RC= 00000 2012/08/144> KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/145. KCIJPMC1 Merge profile from backup PLB3SYSG (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB3SYSG Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSESV Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The Customize PARMGEN Configuration Profile Members panel is displayed:


KCIP@PG6 ------ CUSTOMIZE PARMGEN CONFIGURATION PROFILE MEMBERS ---------------Option ===>(Required)* Select option 1 to customize the PLB3SYSG RTE LPAR profile:

1. PLB3SYSG RTE LPAR CONFIG profile in WCONFIG



3. PLB3SYSG System Variables CONFIG profile in GBL_USER_JCL(TSTEST.SYSPLEX.PARMGEN.JCL)(Required if using user-defined symbols or overridingsystem symbols’ resolved values - see F1=Help)



(Optional) Select option 7 for member list of the WCONFIG library:7. WCONFIG TSTEST.&userid.PLB3SYSG.WCONFIG

Customization of the PLB3SYSG LPAR profile (option 1) is required. If you cloned the $GLB$USRprofile and if both runtime environments will share the same values, no further edits should benecessary, but you should review it to see if other changes might be required for this environment.If you did not clone the $GBL$USR profile, edit the member to provide any environment-specificvalues. If user-defined symbols will be used as parameter values in the LPAR configurationprofile, the system variables profile (option 3) must also be edited to define those values.

b. Select option 1 to customize the LPAR configuration profile for PLB3SYSG.

Note: For guidance on setting parameter values, see the following sources of information:v Comments in the PARMGEN configuration profilesv Online help for the configuration profile (see “KCIRPLBS online help macro” on page 137)v IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Parameter

Reference

v Documentation for your monitoring agentsc. Configure the runtime environment to exploit system variables:

1) Set the RTE_NAME parameter to static symbolic PLB3&SYSNAME..

ISREDDE2 TSTEST.&userid.PLB3SYSG.WCONFIG(PLB3SYSG)Command ===> Scroll ===> CSR000360 ** Runtime environment (RTE) settings:000361 ** Specify the name of the RTE in the RTE_NAME parameter if this RTE000362 ** is not enabled for System Variables (RTE_SYSV_SYSVAR_FLAG=N).000363 RTE_NAME PLB3&SYSNAME.

2) Do an EXCLUDE FIND of all TEMS_VTAM_NETID strings, then change all references to USIBMNETto the &SYSVTAMNETID. KCIPARSE-extracted symbol.Note that NETID value is autodiscovered by the PARMGEN process when you submit theKCIJPUP1 job. ID will be different for your site. For the agents (in this example runtimeenvironment, these are KC5_TEMS_VTAM_* and KGW_TEMS_VTAM_*), these parametersdenote the VTAM® network ID of the LPAR running the primary Tivoli Enterprise MonitoringServer that they connect to.


ISREDDE2 TSTEST.&userid.PLB3SYSG.WCONFIG(PLB3SYSG)Command ===> C ’USIBMNET’ ’&SYSVTAMNETID.’ ALL Scroll ===> CSR****** ***************************** Top of Data ******************************- - - - - - - - - - - - - - - - - - 499 Line(s) not Displayed000500 RTE_VTAM_NETID &SYSVTAMNETID.- - - - - - - - - - - - - - - - - - 216 Line(s) not Displayed000717 KDS_TEMS_VTAM_NETID &SYSVTAMNETID.- - - - - - - - - - - - - - - - - - - 81 Line(s) not Displayed000799 KDS_PH01_TEMS_VTAM_NETID "&SYSVTAMNETID."- - - - - - - - - - - - - - - - - - - 27 Line(s) not Displayed000827 KDS_HUB_VTAM_NETID "&SYSVTAMNETID."- - - - - - - - - - - - - - - - - - 112 Line(s) not Displayed001168 KC5_TEMS_VTAM_NETID &SYSVTAMNETID.- - - - - - - - - - - - - - - - - - - 46 Line(s) not Displayed001359 KGW_TEMS_VTAM_NETID &SYSVTAMNETID.- - - - - - - - - - - - - - - - - - - 39 Line(s) not Displayed****** **************************** Bottom of Data ****************************

3) Do an EXCLUDE FIND of all TEMS_TCP_HOST strings and change all references to thefour-character host name to the &SYSIPHOSTNAME. KCIPARSE-extracted symbol.Note that the host name is autodiscovered by the PARMGEN process when you submit theKCIJPUP1 job. For the agents (in our current runtime environment, these areKC5_TEMS_VTAM_* and KGW_TEMS_VTAM_*), these parameters denote the IP hostname ofthe LPAR running the primary Tivoli Enterprise Monitoring Server that they connect to.

ISREDDE2 TSTEST.&userid.PLB3SYSG.WCONFIG(PLB3SYSG)Command ===> C ’SYSG’ '&SYSIPHOSTNAME.' ALL Scroll ===> CSR****** ***************************** Top of Data ******************************- - - - - - - - - - - - - - - - - - 693 Line(s) not Displayed000694 ** Note: If this is a High-Availability Hub TEMS, KDS_TEMS_TCP_HOST- - - - - - - - - - - - - - - - - - - 1 Line(s) not Displayed000696 KDS_TEMS_TCP_HOST "&SYSIPHOSTNAME."- - - - - - - - - - - - - - - - - - - 90 Line(s) not Displayed000787 ** Note: If this is a High-Availability Hub TEMS, KDS_PH01_TEMS_TCP_HOST- - - - - - - - - - - - - - - - - - - 9 Line(s) not Displayed000797 KDS_PH01_TEMS_TCP_HOST "&SYSIPHOSTNAME."- - - - - - - - - - - - - - - - - - 353 Line(s) not Displayed001151 ** Note: KC5_TEMS_TCP_HOST and KC5_AGT_TCP_HOST must be the same value- - - - - - - - - - - - - - - - - - - 1 Line(s) not Displayed001153 KC5_TEMS_TCP_HOST "&SYSIPHOSTNAME."- - - - - - - - - - - - - - - - - - 188 Line(s) not Displayed001342 ** Note: KGW_TEMS_TCP_HOST and KGW_AGT_TCP_HOST must be the same value- - - - - - - - - - - - - - - - - - - 1 Line(s) not Displayed001344 KGW_TEMS_TCP_HOST "&SYSIPHOSTNAME."- - - - - - - - - - - - - - - - - - 347 Line(s) not Displayed****** **************************** Bottom of Data ****************************

4) Perform the same steps for all AGT_TCP_HOST strings, then change all references to thefour-character host name to the &SYSIPHOSTNAME. KCIPARSE-extracted symbol.For the agents, these parameters denote the IP hostname of the LPAR where the agent isrunning (the same IP hostname as the local z/OS® remote monitoring server that they willconnect to).

ISREDDE2 TSTEST.&userid.PLB3SYSG.WCONFIG(PLB3SYSG)Command ===> C ’SYSG’ ’&SYSIPHOSTNAME.’ ALL Scroll ===> CSR****** ***************************** Top of Data ******************************- - - - - - - - - - - - - - - - - - 1150 Line(s) not Displayed001156 KC5_AGT_TCP_HOST "&SYSIPHOSTNAME."- - - - - - - - - - - - - - - - - - 185 Line(s) not Displayed001347 KGW_AGT_TCP_HOST "&SYSIPHOSTNAME."- - - - - - - - - - - - - - - - - - 344 Line(s) not Displayed****** **************************** Bottom of Data ****************************

5) If SDA is enabled or a product requires UNIX System Services files, set RTE_USS_RTEDIR touser-defined symbolic &RTE_USS_RTEDIR..


ISREDDE2 TSTEST.&userid.PLB3SYSG.WCONFIG(PLB3SYSG)Command ===> Scroll ===> CSR000488 ** (Optional) If any products to be configured in this RTE require000489 ** Unix System Services (USS) directories created, specify the main RTE000490 ** HFS/zFS USS directory (#rtedir):000491 ** Note: This is also required if you are enabling the Self-describing000492 ** Agent (SDA) functionality in the z/OS TEMS and Agents:000493 ** Related PARMGEN CONFIG profile parameters (for SDA):000494 ** - GBL_HFS_JAVA_DIRn000495 ** - GBL_DSN_SYS1_SBPXEXEC000496 ** - RTE_USS_RTEDIR000497 ** - KDS_KMS_SDA000498 ** - KDS_TEMA_SDA000499 ** - Kpp_AGT_TEMA_SDA (per Kpp Agent exploiting SDA)000500 RTE_USS_RTEDIR "&RTE_USS_RTEDIR."

6) Do an EXCLUDE FIND of all _PORT parameters. Then customize _PORT according to yoursite's conventions.

ISREDDE2 TSTEST.&userid.PLB3SYSG.WCONFIG(PLB3SYSG)Command ===> C ’ 1918 ’ ’ nnnnn ’ ALL Scroll ===> CSR- - - - - - - - - - - - - - - - - - 485 Line(s) not Displayed000486 RTE_TCP_PORT_NUM nnnnn- - - - - - - - - - - - - - - - - - - 13 Line(s) not Displayed000654 KDS_TEMS_TCP_PIPE_PORT_NUM nnnnn * IP.PIPE000655 KDS_TEMS_TCP_UDP_PORT_NUM nnnnn * IP.UDP000656 KDS_TEMS_TCP_PIPE6_PORT_NUM "" * IP.PIPE for IPV6000657 KDS_TEMS_TCP_UDP6_PORT_NUM "" * IP.UDP for IPV6000658 KDS_TEMS_TCP_PIPES_PORT_NUM "" * Secure IP.PIPE000659 KDS_TEMS_TCP_PIPE6S_PORT_NUM "" * Secure IP.PIPE for IPV6- - - - - - - - - - - - - - - - - - - 72 Line(s) not Displayed000758 KDS_PH01_TEMS_TCP_PORT_NUM nnnnn- - - - - - - - - - - - - - - - - - - 38 Line(s) not Displayed001094 KC5_TEMS_TCP_PIPE_PORT_NUM nnnnn * IP.PIPE001095 KC5_TEMS_TCP_UDP_PORT_NUM nnnnn * IP.UDP001096 KC5_TEMS_TCP_PIPE6_PORT_NUM "" * IP.PIPE for IPV6001097 KC5_TEMS_TCP_UDP6_PORT_NUM "" * IP.UDP for IPV6001098 KC5_TEMS_TCP_PIPES_PORT_NUM "" * Secure IP.PIPE001099 KC5_TEMS_TCP_PIPE6S_PORT_NUM "" * Secure IP.PIPE for IPV6- - - - - - - - - - - - - - - - - - 345 Line(s) not Displayed****** **************************** Bottom of Data ****************************

7) Do an EXCLUDE FIND of all KDS_HUB strings, then customize each parameter accordingly.The KDS_HUB_* parameters denote the remote monitoring server's hub settings, which wouldbe directed to the first runtime environment's static hub monitoring server on environmentPLB1SP22. In this case, you should convert the parameters to user-defined symbols to keepthem generic so it is easier to reassign the values of these symbolics if you reconfigure theremote monitoring server to point to a different hub later on. (See Appendix C, “Systemvariables,” on page 139 for more information.)The values specified for the KDS_HUB_* parameters are used in the xKANPARU(KDCSSITE)and xKANPARU(KDSENV) runtime members.


ISREDDE2 TSTEST.&userid.PLB3SYSG.WCONFIG(PLB3SYSG)Command ===> Scroll ===> CSR****** ***************************** Top of Data ******************************- - - - - - - - - - - - - - - - - - 670 Line(s) not Displayed000671 ** If this is a Remote TEMS, update the KDS_HUB_* parameters000672 ** by uncommenting out the corresponding KDS_HUB_TCP_*_PORT_NUM- - - - - - - - - - - - - - - - - - - 51 Line(s) not Displayed000724 KDS_TEMS_VTAM_APPL_GLB_BROKER "&KDS_HUB_VTAM_APPL_GLB_BROKER."- - - - - - - - - - - - - - - - - - - 96 Line(s) not Displayed000821 ** If the TEMS is a Remote, uncomment the KDS_HUB_* parameters- - - - - - - - - - - - - - - - - - - 1 Line(s) not Displayed000823 KDS_HUB_TEMS_NAME_NODEID "&KDS_HUB_TEMS_NAME_NODEID."- - - - - - - - - - - - - - - - - - - 2 Line(s) not Displayed000826 KDS_HUB_VTAM_APPL_GLB_BROKER "&KDS_HUB_VTAM_APPL_GLB_BROKER."000827 KDS_HUB_VTAM_NETID "&KDS_HUB_VTAM_NETID."- - - - - - - - - - - - - - - - - - - 2 Line(s) not Displayed000830 KDS_HUB_TCP_HOST "&KDS_HUB_TCP_HOST."- - - - - - - - - - - - - - - - - - - 2 Line(s) not Displayed000833 KDS_HUB_TCP_PIPE_PORT_NUM "&KDS_HUB_TCP_PIPE_PORT_NUM."000834 KDS_HUB_TCP_UDP_PORT_NUM "&KDS_HUB_TCP_UDP_PORT_NUM."..- - - - - - - - - - - - - - - - - - 853 Line(s) not Displayed****** **************************** Bottom of Data ****************************

8) Do an EXCLUDE FIND of all TEMS_BKUP1 strings and uncomment the parameters accordingly.The agent's Kpp_TEMS_BKUP1_* parameters enable the secondary monitoring server for theagents that run in their own agent address spaces. In the event that the primary monitoringserver that they connect to goes down (the local remote monitoring server, in this case), theycan reconnect to the backup (secondary) monitoring server. By default, the parameters alreadypoint to generic &AGT_* user-defined symbols so it is easier to reassign the values of thesesymbolics if you reconfigure the agents to point to a different backup monitoring server lateron. The values specified for the Kpp_TEMS_BKUP1_* parameters are used in the agent'sCT_CMSLIST parameter in the agent-specific xKANPARU(KppENV) runtime member.

File Edit Edit_Settings Menu Utilities Compilers Test HelpsssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssEDIT TSTEST.CCAPI.PLB3SYSG.WCONFIG(PLB3SYSG) - 01.00 Columns 00001 00072Command ===> Scroll ===> CSR****** ***************************** Top of Data ******************************- - - - - - - - - - - - - - - - - - 1269 Line(s) not Displayed001270 ** - KC5_TEMS_BKUP1_* Agent’s Backup TEMS parameter values- - - - - - - - - - - - - - - - - - 123 Line(s) not Displayed001394 ** Note: Specify the Backup TEMS (KC5_TEMS_BKUP1_*) parameter values- - - - - - - - - - - - - - - - - - - 4 Line(s) not Displayed001399 KC5_TEMS_BKUP1_NAME_NODEID "&AGT_TEMS_BKUP1_NAME_NODEID."- - - - - - - - - - - - - - - - - - - 2 Line(s) not Displayed001402 KC5_TEMS_BKUP1_TCP_HOST "&AGT_TEMS_BKUP1_TCP_HOST."- - - - - - - - - - - - - - - - - - - 2 Line(s) not Displayed001405 KC5_TEMS_BKUP1_VTAM_LU62_DLOGMOD &AGT_TEMS_BKUP1_VTAM_LU62_DLOGMOD.001406 KC5_TEMS_BKUP1_VTAM_APPL_LLB_BKR &AGT_TEMS_BKUP1_VTAM_APPL_LLB_BKR.001407 KC5_TEMS_BKUP1_VTAM_NETID &AGT_TEMS_BKUP1_VTAM_NETID.- - - - - - - - - - - - - - - - - - 132 Line(s) not Displayed001540 ** - KGW_TEMS_BKUP1_* Agent’s Backup TEMS parameter values- - - - - - - - - - - - - - - - - - - 85 Line(s) not Displayed001626 ** Note: Specify the Backup TEMS (KGW_TEMS_BKUP1_*) parameter values- - - - - - - - - - - - - - - - - - - 4 Line(s) not Displayed001631 KGW_TEMS_BKUP1_NAME_NODEID "&AGT_TEMS_BKUP1_NAME_NODEID."- - - - - - - - - - - - - - - - - - - 2 Line(s) not Displayed001634 KGW_TEMS_BKUP1_TCP_HOST "&AGT_TEMS_BKUP1_TCP_HOST."- - - - - - - - - - - - - - - - - - - 2 Line(s) not Displayed001637 KGW_TEMS_BKUP1_VTAM_LU62_DLOGMOD &AGT_TEMS_BKUP1_VTAM_LU62_DLOGMOD.001638 KGW_TEMS_BKUP1_VTAM_APPL_LLB_BKR &AGT_TEMS_BKUP1_VTAM_APPL_LLB_BKR.001639 KGW_TEMS_BKUP1_VTAM_NETID &AGT_TEMS_BKUP1_VTAM_NETID.- - - - - - - - - - - - - - - - - - 509 Line(s) not Displayed002149 ** - KN3_TEMS_BKUP1_* Agent’s Backup TEMS parameter values- - - - - - - - - - - - - - - - - - - 90 Line(s) not Displayed


d. Set the RTE_X_STC_INAPF_INCLUDE_FLAG option to Y.

ISREDDE2 TSTEST.&userid.PLB3SYSG.WCONFIG(PLB3SYSG)Command ===> Scroll ===> CSR000528 ** (Optional) INAPF INCLUDE statement in product started tasks (STCs):000529 ** Specify "Y" if you want to generate this statement as uncommented000530 ** out in all product STCs: "INAPF INCLUDE MEMBER=%RTE_STC_PREFIX%APF"000531 ** This sample composite member contains APF-authorization commands for000532 ** libraries concatenated in the STC STEPLIB and RKANMODL DDNAMEs.000533 ** This member also contains the VARY activate command pointing to the000534 ** %RTE_VTAM_GBL_MAJOR_NODE% VTAM major node (TSSND122 by default).000535 ** Review %RTE_STC_PREFIX%APF and %RTE_STC_PREFIX%STRT WKANSAMU000536 ** members for more information.000537 RTE_X_STC_INAPF_INCLUDE_FLAG Y

e. If you are using enabling password encryption across your monitoring environment, and you arenot using the default encryption key, customize the Tivoli Management Services passwordencryption by uncommenting the KDS_TEMS_SECURITY_KAES256_ENCKEY parameter and thenspecifying the KAES256 encryption key.

ISREDDE2 TSTEST.&userid.PLB3SYSG.WCONFIG(PLB3SYSG)Command ===> Scroll ===> CSR000709 ** TEMS’ security settings:000710 KDS_TEMS_SECURITY_KDS_VALIDATE N000711000712 ** TEMS’ security settings: KAES256 encryption key000713 ** Note: This is required if you are enabling the ITM Password000714 ** Encryption (KAES256) across the ITM enterprise:000715 ** The "KDS_TEMS_SECURITY_KAES256_ENCKEY" value is encrypted000716 ** and xKANPARU(KAES256) member is created as part of the000717 ** xKANSAMU(KCIJPSEC) composite security job.000718 ** Related PARMGEN CONFIG profile parameter:000719 ** - GBL_DSN_CSF_SCSFMOD0 (DSN value is concatenated in the000720 ** TEMS STC’s STEPLIB DD)000721 KDS_TEMS_SECURITY_KAES256_ENCKEY "IBMTivoliMonitoringEncryptionKey"

Specify a unique, 32-byte password encryption key. The value is case-sensitive. Be sure to recordthe value you use for the key. You must use the same key during the installation of anycomponents that communicate with this monitoring server, such as the a remote monitoringserver. The ampersand (&) character cannot be part of the encryption key. Note that this valuemust match across your site's IBM Tivoli Monitoring enterprise.If you use a library other than the default, you will need to uncomment and customize theGBL_DSN_CSF_SCSFMOD0 parameter in the $GBL$USR global configuration profile.

f. Refer to the planning and configuration guide for each component to make sure you have madeany required configuration changes.

g. Save the profile and exit to the Customize PARMGEN Configuration Profile Members panel.h. Customize the $GBL$USR profile to use symbolic values.

1) Select option 2.2) Provide symbolic values for the appropriate parameters.

For example, you can set GBL_HFS_JAVA_DIR1 to &GBL_HFS_JAVA_DIR1..3) Save the profile and exit to the Customize PARMGEN Configuration Profile Members panel.

i. Customize the PLB3SYSG system variables configuration profile to set all user-defined symbolsreferenced when you customized the LPAR profile.v Select option 3.v Customize AGT_TEMS_BKUP1* values to point to a backup monitoring server that the agents

can automatically connect to if the local monitoring server goes down. In the following example,this points to the hub created on LPAR SP22 in scenario 1.

v Supply the values for all the user-defined symbols.


ISREDDE2 TSTEST.SYSPLEX.PARMGEN.JCL(PLB3SYSG) - 01.16 Columns 00001 00072Command ===> Scroll ===> CSR****** ***************************** Top of Data ******************************000100 * ******************************************************************000110 * Member: KCI$RTEV000120 * Master Source: TSTEST.ITM62351.TKANSAM(KCI$RTEV)000130 * KCIJPUP1 Batch Job Output (PART 3):000131 * TSTEST.&userid.PLB3SYSG.IKANSAMU(KCI$RTEV) - IBM Default Copy000140 * TSTEST.SYSPLEX.PARMGEN.JCL(PLB3SYSG) - Customer Copy000150 * Purpose:000160 * TSTEST.SYSPLEX.PARMGEN.JCL(PLB3SYSG)000170 * member houses user-defined symbolics for this RTE if000180 * System Variables mode is enabled.000190 * Note: These are symbolics in addition to the typical static000200 * system symbols defined in SYS1.IPLPARM and system variables000210 * derived by KCIPARSE program (for TYPE:CE (CHAR extracted)000221 * and TYPE:IE (INTEGER extracted) KCIPARSE-extracted symbolics000222 * for System Variables use in the SYSPRINT DDNAME’s GLOBAL000224 * VARIABLE TABLE SUMMARY of a KCIPARSE run).000227 * Instructions:000228 * Add your user-defined symbolics below, if any...000284 * *********************************************************************000285 * SECTION: PRE-DEFINED / USER-DEFINED SYMBOLICS *000286 * *********************************************************************000287 * ----------- BEGIN - USER SECTION: PRE-DEFINED SYMBOLICS ----------- *000288 * ====================== ===============000289 * User-defined symbolic: Resolved value:000290 * ====================== ===============000291 AGT_TEMS_BKUP1_NAME_NODEID PLB1SP22:CMS000292 AGT_TEMS_BKUP1_TCP_HOST SP22000293 AGT_TEMS_BKUP1_VTAM_LU62_DLOGMOD CANCTDCS000294 AGT_TEMS_BKUP1_VTAM_APPL_LLB_BKR CTDDSLB000295 AGT_TEMS_BKUP1_VTAM_NETID USIBMNET000296 * ----------- END - USER SECTION: PRE-DEFINED SYMBOLICS ----------- *000297 * ----------- BEGIN - USER SECTION: USER-DEFINED SYMBOLICS ---------- *000298 * ====================== ===============000299 * User-defined symbolic: Resolved value:000300 * ====================== ===============000400 * ----------- END - USER SECTION: USER-DEFINED SYMBOLICS ---------- *008300 * ----------- BEGIN - USER SECTION: USER-DEFINED SYMBOLICS ---------- *

009400 * Type 3: User defined symbols009500 RTE_USS_RTEDIR /tstest009710 KDS_HUB_TEMS_NAME_NODEID "PLB1SP22:CMS"009711 KDS_HUB_VTAM_APPL_GLB_BROKER CTDDSLB009720 KDS_HUB_VTAM_NETID USIBMNET009730 KDS_HUB_TCP_HOST SP22009780 KDS_HUB_TCP_PIPE_PORT_NUM nnnnn009790 KDS_HUB_TCP_UDP_PORT_NUM nnnnn009800 GBL_HFS_JAVA_DIR1 /Java/J6.0****** **************************** Bottom of Data ****************************

j. Save the changes and return to the main Workflow panel.5. On the Workflow main panel, select option 9 to validate the configuration profile values that you

supplied. Submit the generated KCIJPVAL job.







1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/142. $JOBINDX Review PARMGEN job index. Viewed 2012/08/143. KCIJPCCF Clone customized WCONFIG members. (COND)4. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/145. KCIJPMC1 Merge profile from backup PLB3SYSG (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8> PLB3SYSG Customize PARMGEN configuration profiles. Edited 2012/08/149. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSESV Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

If there are any errors in the job, enter 9s to display the detailed report. Browse the report for anyerrors and correct them in the profile, then rerun the validation job.

6. Create the runtime members and jobs:a. From the Workflow main menu, select option 10:






1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/142. $JOBINDX Review PARMGEN job index. Viewed 2012/08/143. KCIJPCCF Clone customized WCONFIG members. (COND)4. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/145. KCIJPMC1 Merge profile from backup PLB3SYSG (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB3SYSG Customize PARMGEN configuration profiles. Edited 2012/08/149> KCIJPVAL Validate PARMGEN profile parameter values. RC= 00000 2012/08/1410. $PARSESV Create the RTE members and jobs. RC= 00000 2012/08/1311. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The Submit $PARSESV Batch Jobs to Complete PARMGEN Setup is presented.b. Select option 1 to edit and then submit the $PARSESV composite job.


KCIP@PRS ---- $PARSE/$PARSESV: CREATE THE RTE MEMBERS AND JOBS ------------Option ===> 1

Select option 1 to SUBMIT the full $PARSESV job in WCONFIG for RTE=PLB3SYSG.Alternatively, select other options to SUBMIT $PARSE jobs individually.Press F1=Help for additional considerations when selecting options 2-5.


1> $PARSESV Composite $PARSESV job** or **




7. Submit the batch jobs to complete the PARMGEN setup:a. On the Workflow main panel, select option 11.






1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/142. $JOBINDX Review PARMGEN job index. Viewed 2012/08/143. KCIJPCCF Clone customized WCONFIG members. (COND)4. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/145. KCIJPMC1 Merge profile from backup PLB3SYSG (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB3SYSG Customize PARMGEN configuration profiles. Edited 2012/08/149. KCIJPVAL Validate PARMGEN profile parameter values. RC= 00000 2012/08/1410> $PARSESV Create the RTE members and jobs. Submitted 2012/08/1411. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

b. On the Submit Batch Jobs to Complete PARMGEN Setup, select option 1 if you want to submit theKCIJVSUB master SUBMIT job, or select the other options to submit each job individually. If youselect option 1, review the KCIJVSUB job first and edit the job according to which conditional jobsneed be submitted automatically.


----------------- SUBMIT BATCH JOBS TO COMPLETE PARMGEN SETUP -----------------Option ===> Scroll ===> PAGE

Select option 1 to SUBMIT the composite jobs in WKANSAMU for RTE=PLB3SYSG.Alternatively, select other options to SUBMIT each job individually.Press F1=Help for additional considerations when selecting options 4-14.


1. KCIJVSUB Composite SUBMIT job (See JCL comments)** or **

2. KCIJVALO Allocate runtime libraries3. KCIJVLOD Load TK*->RK* runtime libraries4. KCIJVSEC Product security (Conditional)5. KCIJVUPV System Variables IEBUPDTE (Conditional)6. KCIJVUSP USS preparation (Conditional)7. KCIJVUSS USS system set-up (Authorization required)8. KCIJVSYS System set-up (Authorization required)9. KCIJVLNK ASM/Link RKANMODU modules (Conditional)10. KCIJVIVP Configuration verification11. KCIJVCPW Backup WK* work libraries (Conditional)12. KCIJVCPR Backup RK* production user libs (Conditional)13. KCIJVW2R WK*->RK* deployment (Conditional)14. KCIJVMNT Composite maintenance job (Conditional)

If you select option 1, you are prompted with the following message:

c. Press Enter. The following message is displayed:

----------------------------- PARMGEN MESSAGES -----------------------------Command ===>

In a system variable environment, job KCIJVSUB runs $PARSESVto customize then submit the KCIJPSUV job. EDIT and modifythe KCIJPSUV job as appropriate. See comments in the JCL forfurther information.DO NOT MANUALLY SUBMIT THE KCIJPSUV JOB!

d. Press Enter to edit the KCIJPSUV job. Jobs that require authorization or are conditional are notsubmitted automatically. You must either submit them manually, or uncomment them to runautomatically.

e. Press F3, and you are presented with the KCIJVSUB job for submission. Submit the job. Check thestatus of each of the jobs submitted. The allocation and load jobs must run successfully, or othersjobs being submitted by the composite job will not run.


The KCIJVSUB composite job submits several PARMGENconfiguration jobs via TSO SUBMIT commands. Some ofthose SUBMIT commands are commented out. Carefullyreview the comments in the JCL to determine whichof those jobs you do or do not want to submit.Uncomment the SUBMIT commands of those jobs thatyou want to submit.

Do NOT delete any SUBMIT commands as they may beneeded in the future.


Results

You have created runtime environment PLB3SYSG. Perform the applicable steps required outside theconfiguration software documented in your planning and configuration guides and start the products.

Scenario PGN03: Configure a high-availability hub monitoring serverIn this scenario, you create a full runtime environment that contains a z/OS-based high-availability hubTivoli Enterprise Monitoring Server to which remote monitoring servers will report.

About this task

The only Tivoli Management Services on z/OS component that you can configure in a runtimeenvironment containing a high-availability (HA) hub Tivoli Enterprise Monitoring Server is a hubmonitoring server (component code KDS). In addition, a high-availability hub on z/OS has the followingrequirements:v It must be configured in a sysplex.v It must have a dynamic virtual IP address (DVIPA), so it can respond to the same IP address on any

LPAR in the sysplex.v It must be configured stand-alone (in its own runtime environment without monitoring agents).v Its runtime libraries must be stored on shared DASD, so that the hub can start on any LPAR in the

sysplex without requiring replication of the libraries.v Its runtime environment cannot use system variables. The hub is not defined to run on any specific

system, and it retains the same parameter values on any system in the sysplex.

This scenario involves 6 steps:1. Create the work libraries.2. Update the interim libraries and create the profiles.3. Customize the profiles.4. Validate the profile values.5. Create the runtime members and jobs6. Submit jobs to complete PARMGEN set up.

Complete the following procedure to create a sample runtime environment named PLBHAHUB.

Procedure1. Create the PARMGEN work libraries:

a. On the Workflow main panel, specify the GBL_USER_JCL, RTE_PLIB_HILEV, and RTE_NAMEfields, as shown in the following example, then select option 1. Note that if you did not invoke theR (RESET) option when building a previous environment, the values for GBL_USER_JCL,RTE_PLIB_HILEV, and RTE_NAME are carried forward from that session; in this case, change theRTE_NAME to PLBHAHUB.




High-Level Qualifier (HLQ) of work libraries (IK*,WCONFIG,WK*)RTE_NAME: PLBHAHUB (Type ? for a list of configured RTEs)



1. KCIJPCFG Set up PARMGEN work environment for an RTE.2. $JOBINDX Review PARMGEN job index.3. KCIJPCCF Clone customized WCONFIG members. (Optional)4. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup PLBHAHUB (Optional)6. KCIJPMC2 Merge profile from model RTE. (Optional)7. KCIJPCNV Convert an ICAT RTE Batch member. (Optional)8. Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

GBL_USER_JCLSpecify the data set name of the PARMGEN global user JCL library. If the data set doesnot exist, you are prompted to correct the name or allocate the data set.

Important: The GBL_USER_JCL library keeps track of the different runtime environmentdefinitions such as KCIJPCFG values and PARMGEN job status and date in the KCIDJP02member. If you switch GBL_USER_JCL libraries, ensure that you copy the members to thenew GBL_USER_JCL. Otherwise, PARMGEN will not be able to carry forward informationabout existing runtime environment definitions tracked in the current GBL_USER_JCLlibrary. However, if you copy the members over to the new GBL_USER_JCL, then the$GBL$IBM and $GBL$USR global configuration profiles for each runtime environmentstored in the runtime environment-specific WCONFIG libraries must be adjusted to pointto the new name.

In addition, the GBL_USER_JCL library must not be the same library as the runtimeenvironment's WCONFIG runtime environment profile library. The PARMGEN WCONFIGcontrol library is where configuration profiles and other members are stored by theKCIJPUP1 job.

RTE_PLIB_HILEVSpecify the non-VSAM high-level qualifier that you want to use for the followingPARMGEN work libraries:v WCONFIG control library where configuration profiles and other members are stored

by the KCIJPUP1 job.v Interim staging (IK*) libraries where PARMGEN product runtime members (template

versions) are stored by the KCIJPUP1 job.v Work output (WK*) libraries where PARMGEN file-tailored runtime members and jobs

are created by the $PARSE or $PARSESV job.

RTE_NAMESpecify a unique name for the runtime environment that you are configuring (in thisexample, PLBHAHUB). The name that you specify is appended to the RTE_PLIB_HILEVvalues to make each set of PARMGEN and runtime libraries unique. For example:%RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(%RTE%).


b. Press Enter. Because the runtime environment you specified is a new runtime environment, youare asked if you want to reset the definition values before you proceed:








d. Press Enter to reset the parameter values. You are returned to the main Workflow panel.e. Select option 1 from the main menu. The first Set up PARMGEN Work Environment for an RTE

panel is displayed.f. Because you are creating a new environment, leave the first field blank (the first condition). If

appropriate, specify the Install Job Generator output library.




- If reconfiguring or upgrading this existing PLBHAHUB RTE, specify itsvalues (TSTEST.&userid.PLBHAHUB.WCONFIG(PLBHAHUB)) **or**

- If converting an ICAT-created RTE to PARMGEN mode, specify the ICATRTE Batch member location and RTE member (ex.: &hlq.INSTJOBS(PLBHAHUB))



g. Press Enter to proceed to the next set up panel. The second setup panel is displayed:


KCIP@PG2 ---- SET UP PARMGEN WORK ENVIRONMENT FOR AN RTE (2 OF 3) -------------COMMAND ===>

GBL_USER_JCL: TSTEST.SYSPLEX.PARMGEN.JCLRTE_PLIB_HILEV: TSTEST.&useridRTE_NAME: PLBHAHUB






h. Review the values and override as necessary. These values are initially inherited from the firstruntime environment. If you specified the JOBGEN repository from the previous KCIP@PG1 panel,the GBL_TARGET_HILEV and GBL_SYSDA_UNIT parameters are filled out automatically, asPARMGEN reuses the data from the repository.

i. Press enter to proceed to the third set up panel:


Enter parameter values appropriate for your RTE=PLBHAHUB.Note: See F1=Help for SMS-related and RTE HLQ-related considerationswhen VOLUME, UNIT, STORCLAS, and MGMTCLAS parameters are required forthe global RTE_* parameters and the Kpp_* product-specific parameters.




RTE_TYPE: FULL____ (FULL, SHARING)RTE_SHARE: ________________________ (SMP or shared RTE name)RTE_X_HILEV_SHARING: ________________________ (HLQ of shared RTE)RTE_TEMS_CONFIGURED_FLAG: Y (Y, N)RTE_TEMS_NAME_NODEID: PLBHAHUB:CMS_________________ (e.g., RTE1:cms)RTE_STC_PREFIX: CANS______________________ (Started task prefix)RTE_VTAM_APPLID_PREFIX CTD_______________________ (VTAM APPLID prefix)RTE_SYSV_SYSVAR_FLAG: N_________________________ (System variable flag)RTE_X_SYSV_OVERRIDE_SYMBOLS: N (Y, N) (SysVar override flag)RTE_SECURITY_USER_LOGON: NONE____ (RACF, ACF2, TSS, NAM, SAF, None)RTE_SECURITY_FOLD_PASSWORD_FLAG: Y (Fold to upper case (Y, N))RTE_SECURITY_CLASS: ________ (ACF2 max is 3 characters)RTE_X_SECURITY_EXIT_LIB: TSTEST.&userid.PLBHAHUB.RKANSAMU_______________GBL_DSN_ACF2_MACLIB: ____________________________________________ (If ACF2)KDS_TEMS_TYPE: HUB___ (Hub, Remote)KDS_TEMS_HA_TYPE: HA____ (Hub TEMS type (HA))



j. Change the KDS_TEMS_HA_TYPE to HA. If you are using a runtime environment high levelqualifier that is not SMS managed, you will also need to specify the SMS parameters. You mightalso need to change the started task prefix and VTAM applid prefix to conform to siterequirements. Otherwise you can accept the defaults.

k. Press Enter to proceed to the Display PARMGEN Environment Analysis panel (KCIP@PG4). Thispanel lists the products installed and available for configuration.


Review message traffic before proceeding. These Kpp components are installedinto the TDTST.ITM62351.TKANCUS SMP/E target library andare available for (re)configuration and/or upgrade into the RTE=PLBHAHUB.Refer to the next panel ("EXCLUDE PRODUCTS FROM PARMGEN CUSTOMIZATION")for a legend of the Kpp components’ product names.

34 Components installed in TDTST.ITM62351.TKANCUS:KAH KC2 KC5 KDF KDO KDS KD2 KD4 KD5 KGWKHL KI2 KI5 KMC KMQ KMV KM2 KM5 KNA KN3KOB KON KQI KRG KRH KRJ KRK KRN KRV KRWKS3 KT1 KWO KYN

1 Components installed and configured in RTE profile PLBHAHUB:KDS

33 Components installed but not configured in RTE profile PLBHAHUB:KAH KC2 KC5 KDF KDO KD2 KD4 KD5 KGW KHLKI2 KI5 KMC KMQ KMV KM2 KM5 KNA KN3 KOBKON KQI KRG KRH KRJ KRK KRN KRV KRW KS3KT1 KWO KYNEnd of data

l. Review the messages, then press Enter to display the Exclude Products from PARMGENCustomization Panel. A warning popup reminds you that only a monitoring server can beconfigured in a high-availability hub runtime environment.

KCIP@MSG -------------------- PARMGEN MESSAGES -----------Command ===>

You have asked to configure a High Availability (HA) Hub.Only the TEMS can be configured in an HA Hub RTE.

RTE_NAME: PLBHAHUBTEMS: Tivoli Enterprise Monitoring Server V630

Press ENTER to continue.

-----------------------------------------------------------

m. Press Enter to proceed. The KCIJPCFG job is displayed.n. If desired, review the notes to understand what the job is doing, then submit it. You are returned

to the main Workflow panel.2. Select option 4 (KCIJPUP1 Update interim libraries and create profiles), then submit the

WCONFIG(KCIJPUP1) job.







1> KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/152. $JOBINDX Review PARMGEN job index.3. KCIJPCCF Clone customized WCONFIG members. (Optional)4. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup PLBHAHUB (Optional)6. KCIJPMC2 Merge profile from model RTE. (Optional)7. KCIJPCNV Convert an ICAT RTE Batch member. (Optional)8. PLBHAHUB Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

3. After you return to the main panel, select option 8 (PLBHAHUB Customize PARMGEN configurationprofiles). The Customize PARMGEN Configuration Profile Members is displayed. You will need tocustomize both the LPAR configuration profile PLBHAHUB and the global configuration profile,$GLB$USR.a. Select 1 to customize the PLBHAHUB LPAR profile.

KCIP@PG6 ------ CUSTOMIZE PARMGEN CONFIGURATION PROFILE MEMBERS ---------------Option ===> 1(Required)* Select option 1 to customize the PLBHAHUB RTE LPAR profile:

1. PLBHAHUB RTE LPAR CONFIG profile in WCONFIG



3. PLBHAHUB System Variables CONFIG profile in GBL_USER_JCL(TSTEST.SYSPLEX.PARMGEN.JCL)(Required if using user-defined symbols or overridingsystem symbols’ resolved values - see F1=Help)



(Optional) Select option 7 for member list of the WCONFIG library:7. WCONFIG TSTEST.&userid.PLBHAHUB.WCONFIG

The PLBHAHUB profile is displayed.b. Customize the parameters as follows to create a high-availability hub monitoring server.

1) Do an EXCLUDE FIND of all "_TCP_HOST" strings. Then customize all occurrences of theLPAR name to the reserved Dynamic VIPA name. In this example, this is hostnameOMEGHAHUB.


ISREDDE2 TSTEST.&userid.PLBHAHUB.WCONFIG(PLBHAHUB)Command ===> C &hostname OMEGHAHUB ALL Scroll ===> CSR****** ***************************** Top of Data ******************************- - - - - - - - - - - - - - - - - - 307 Line(s) not Displayed000308 ** 000029 RTE_TCP_HOST "OMEGHAHUB"- - - - - - - - - - - - - - - - - - 197 Line(s) not Displayed000506 RTE_TCP_HOST "OMEGHAHUB"- - - - - - - - - - - - - - - - - - 186 Line(s) not Displayed000693 ** Note: If this is a High-Availability Hub TEMS, KDS_TEMS_TCP_HOST- - - - - - - - - - - - - - - - - - - 1 Line(s) not Displayed000695 KDS_TEMS_TCP_HOST "OMEGHAHUB"- - - - - - - - - - - - - - - - - - - 90 Line(s) not Displayed000786 ** Note: If this is a High-Availability Hub TEMS, KDS_PH01_TEMS_TCP_HOST- - - - - - - - - - - - - - - - - - - 9 Line(s) not Displayed000796 KDS_PH01_TEMS_TCP_HOST "OMEGHAHUB"- - - - - - - - - - - - - - - - - - - 32 Line(s) not Displayed****** **************************** Bottom of Data ****************************

2) If you want to use a port other than the default 1918, do an EXCLUDE FIND of all _PORTparameters, then customize as appropriate.

ISREDDE2 TSTEST.&userid.PLBHAHUB.WCONFIG(PLBHAHUB)Command ===> C ’ 1918 ’ ’ nnnnn ’ ALL Scroll ===> CSR****** ***************************** Top of Data ******************************- - - - - - - - - - - - - - - - - - 507 Line(s) not Displayed==CHG> RTE_TCP_PORT_NUM nnnnn- - - - - - - - - - - - - - - - - - 176 Line(s) not Displayed==CHG> KDS_TEMS_TCP_PIPE_PORT_NUM nnnnn * IP.PIPE==CHG> KDS_TEMS_TCP_UDP_PORT_NUM nnnnn * IP.UDP- - - - - - - - - - - - - - - - - - 110 Line(s) not Displayed==CHG> KDS_PH01_TEMS_TCP_PORT_NUM nnnnn- - - - - - - - - - - - - - - - - - 151 Line(s) not Displayed****** **************************** Bottom of Data ****************************

3) If you intend to enable self-describing agents, or configure any products that require a UNIXSystem Services directory, set RTE_USS_RTEDIR to the directory created for that purpose.

ISREDDE2 TSTEST.&userid.PLBHAHUB.WCONFIG(PLBHAHUB)Command ===> Scroll ===> CSR000488 ** (Optional) If any products to be configured in this RTE require000489 ** Unix System Services (USS) directories created, specify the main RTE000490 ** HFS/zFS USS directory (#rtedir):000491 ** Note: This is also required if you are enabling the Self-describing000492 ** Agent (SDA) functionality in the z/OS TEMS and Agents:000493 ** Related PARMGEN CONFIG profile parameters (for SDA):000494 ** - GBL_HFS_JAVA_DIRn000495 ** - GBL_DSN_SYS1_SBPXEXEC000496 ** - RTE_USS_RTEDIR000497 ** - KDS_KMS_SDA000498 ** - KDS_TEMA_SDA000499 ** - Kpp_AGT_TEMA_SDA (per Kpp Agent exploiting SDA)000500 RTE_USS_RTEDIR "/tstest"

4) (Optional) Set the RTE_X_STC_INAPF_INCLUDE_FLAG option to Y.

ISREDDE2 TSTEST.&userid.PLBHAHUB.WCONFIG(PLBHAHUB)Command ===> Scroll ===> CSR000528 ** (Optional) INAPF INCLUDE statement in product started tasks (STCs):000529 ** Specify "Y" if you want to generate this statement as uncommented000530 ** out in all product STCs: "INAPF INCLUDE MEMBER=%RTE_STC_PREFIX%APF"000531 ** This sample composite member contains APF-authorization commands for000532 ** libraries concatenated in the STC STEPLIB and RKANMODL DDNAMEs.000533 ** This member also contains the VARY activate command pointing to the000534 ** %RTE_VTAM_GBL_MAJOR_NODE% VTAM major node (TSSND122 by default).000535 ** Review %RTE_STC_PREFIX%APF and %RTE_STC_PREFIX%STRT WKANSAMU000536 ** members for more information.000537 RTE_X_STC_INAPF_INCLUDE_FLAG Y


5) Customize the TEMS protocols to support only IP: At least one of the values must be IPPIPE,IP6PIPE, IPSPIPE, or IP6SPIPE. Nullify the KDS_TEMS_COMM_PROTOCOL3 parameter bysetting it to "" (instead of the SNA value set initially).

ISREDDE2 TSTEST.&userid.PLBHAHUB.WCONFIG(PLBHAHUB)Command ===> Scroll ===> CSR000658 ** TEMS communication protocols:000659 ** Specify the communication protocols to be used by the local TEMS.000660 ** Valid values are IPPIPE, IP, SNA, IP6PIPE, IP6, IPSPIPE, and000661 ** IP6SPIPE. When communication with another ITM component (TEPS, Hub000662 ** TEMS or Remote TEMS, Agents) is initiated, the TEMS tries Protocol 1000663 ** first and goes to Protocol 2 and so on, in case of failure.000664 ** Note: Update the corresponding KDS_TEMS_TCP_*_PORT_NUM port number000665 ** parameter for each KDS_TEMS_COMM_PROTOCOLx parameter enabled.000666 ** For example, if KDS_TEMS_COMM_PROTOCOL1="IPPIPE", set the000667 ** corresponding KDS_TEMS_TCP_PIPE_PORT_NUM parameter.000668 ** If KDS_TEMS_COMM_PROTOCOL2="IP" (for IP.UDP), set the000669 ** corresponding KDS_TEMS_TCP_UDP_PORT_NUM parameter.000670 ** If this is a Remote TEMS, update the KDS_HUB_* parameters000671 ** by uncommenting out the corresponding KDS_HUB_TCP_*_PORT_NUM000672 ** parameters and specify the Remote’s Hub TEMS port numbers.000673 KDS_TEMS_COMM_PROTOCOL1 IPPIPE000674 KDS_TEMS_COMM_PROTOCOL2 IP000675 KDS_TEMS_COMM_PROTOCOL3 ""

6) Uncomment the KDS_TEMS_TCP_KDEB_INTERFACELIST parameter, then change its valuefrom the default (!*) to !dvipa_hostname, where dvipa_hostname is the private DVIPA name setfor the KDS_TEMS_TCP_HOST parameter (in this example, !OMEGAHUB). This settingensures that the high-availability hub is restricted to its private DVIPA address and cannotinterfere with the remote monitoring server configured on the same LPAR.

ISREDDE2 TSTEST.&userid.PLBHAHUB.WCONFIG(PLBHAHUB)Command ===> Scroll ===> CSR000698 ** If the TEMS requires network interface list support:000699 ** Note: If this is a High-Availability Hub TEMS, uncomment the000700 ** KDS_TEMS_TCP_KDEB_INTERFACELIST and set its value to000701 ** "!<dvipa_address>"000702 KDS_TEMS_TCP_KDEB_INTERFACELIST "!OMEGHAHUB"

7) (Conditional) Customize IBM Tivoli Monitoring password encryption by uncommenting theKDS_TEMS_SECURITY_KAES256_ENCKEY parameter; then specify the KAES256 encryptionkey if using other than the IBM-supplied PARMGEN default key. Specify a unique, 32-bytepassword encryption key. The value is case-sensitive. The ampersand (&) character cannot bepart of the encryption key. Be sure to record the value you use for the key. You must use thesame key during the installation of any components that communicate with this monitoringserver, such as the a remote monitoring server.

ISREDDE2 TSTEST.&userid.PLBHAHUB.WCONFIG(PLBHAHUB)Command ===> Scroll ===> CSR000709 ** TEMS’ security settings:000710 KDS_TEMS_SECURITY_KDS_VALIDATE N000711000712 ** TEMS’ security settings: KAES256 encryption key000713 ** Note: This is required if you are enabling the ITM Password000714 ** Encryption (KAES256) across the ITM enterprise:000715 ** The "KDS_TEMS_SECURITY_KAES256_ENCKEY" value is encrypted000716 ** and xKANPARU(KAES256) member is created as part of the000717 ** xKANSAMU(KCIJPSEC) composite security job.000718 ** Related PARMGEN CONFIG profile parameter:000719 ** - GBL_DSN_CSF_SCSFMOD0 (DSN value is concatenated in the000720 ** TEMS STC’s STEPLIB DD)000721 KDS_TEMS_SECURITY_KAES256_ENCKEY "IBMTivoliMonitoringEncryptionKey"

8) To use self-describing agent feature, uncomment the KDS_KMS_SDA parameter. If necessary,customize the related parameters described in the comments.


SP22 TSTEST.&userid.PLBHAHUB.WCONFIG(PLBHAHUB)Command ===> Scroll ===> CSR000839 ** Enable TEMS Self-Description Agent (SDA) processing:000840 ** This is required if you are enabling the Self-describing000841 ** Agent (SDA) functionality in the z/OS TEMS and Agents:000842 ** Note: By default, the KMS_SDA KDSENV parameter is:000843 ** - initially disabled @ the Hub TEMS (KMS_SDA=N)000844 ** - initially enabled @ the Remote TEMS (KMS_SDA=Y)000845 ** Customize the parameter accordingly by uncommenting out the000846 ** parameter and specifying the applicable value.000847 ** Related PARMGEN CONFIG profile parameters:000848 ** - GBL_HFS_JAVA_DIRn000849 ** - GBL_DSN_SYS1_SBPXEXEC000850 ** - RTE_USS_RTEDIR000851 ** - KDS_KMS_SDA000852 ** - KDS_TEMA_SDA000853 ** - Kpp_AGT_TEMA_SDA (per Kpp Agent exploiting SDA)000810 KDS_KMS_SDA "Y" * Y, N

Important: If you intend to enable granular control of the SDA, the HTTP or HTTPS portmust be enabled at the monitoring server to allow the tacmd command-line utility to connectthrough the SOAP server interface. To enable the SOAP server, ensure that theKDS_TEMS_SOAP_SERVER_FLAG parameter is set to Y.

9) To enable the auditing feature, locate and uncomment the audit parameters in theconfiguration profile:** Audit parameters:** Note:** Specify M=Minimum, B=Basic, D=Detail or X=Disabled to enable or** disable z/OS SMF output (z/Secure).**KDS_AUDIT_TRACE "B" * M, B, D, or X** Specify the maximum entries in the in-memory cache reported by** queries.**KDS_AUDIT_MAX_HIST "100" * 10-1000** Specify an identifier that may be used to associate audit** records.**KDS_AUDIT_ITM_DOMAIN ""

v Set the KDS_AUDIT_TRACE parameter to M, B, D, or X, where

Minimum (M)Records major changes to the product state such as authorization failure, newconnections to the monitoring server or the portal server, or failed user loginattempts.

Basic (B)Records any actions that modify objects or cause an access failure, such as attemptsto modify monitoring server entities like situations and Take Action commands.

This is the default tracing level.

Detail (D)Records all authorization requests, whether successful or failed, such as allsuccessful logins and all modifications to entities such as Take Action commands.

Disabled (X)Disables the auditing function.

.v Set KDS_AUDIT_MAX_HIST to any value from 10 to 1000, depending on the number of

audit records you want kept in the in-memory cache before writing them out.v To group audit records by related agents and monitoring servers, set

KDS_AUDIT_ITM_DOMAIN to the name you assigned to that group.


10) Press F3 to save the changes and return to the Customize PARMGEN Configuration Profilespanel.

c. Complete the following steps to customize the $GLB$USR profile.1) Select option 2 ($GBL$USR). The WCONFIG($GBL$USR) profile is displayed.2) Review the following parameters which identify system libraries to which the KCIJPSYS job

copies various members to determine if you need to override the IBM supplied defaults. Tooverride the default, uncomment out the parameter and overtype the value.v GBL_DSN_HZSPROC_LOADLIBv GBL_DSN_SYS1_PARMLIBv GBL_DSN_SYS1_PROCLIBv GBL_DSN_SYS1_SAXREXECv GBL_DSN_SYS1_VTAMLIBv GBL_DSN_SYS1_VTAMLST

3) If you enabled the self-describing agent feature, you may need to customize the followingparameters:v GBL_HFS_JAVA_DIRn

v GBL_DSN_SYS1_SBPXEXEC

000130 **** Java home directory name:000131 **** Note: This is required if you are enabling the Self-describing000132 **** Agent (SDA) functionality in the z/OS TEMS and Agents:000133 **** "GBL_HFS_JAVA_DIRn" value becomes part of the000134 **** TEMS_JAVA_BINPATH parameter in the RKANDATV(KDSDPROF) member000135 **** that is created by the WKANSAMU(KCIJPUSP) USS preparation000136 **** job. "/bin" is added to the "GBL_HFS_JAVA_DIRn" Java home000137 **** directory value programmatically.000138 **** Related PARMGEN CONFIG profile parameters:000139 **** - GBL_DSN_SYS1_SBPXEXEC000140 **** - RTE_USS_RTEDIR000141 **** - KDS_KMS_SDA000142 **** - KDS_TEMA_SDA000143 **** - Kpp_AGT_TEMA_SDA000144 **GBL_HFS_JAVA_DIR1 /usr/lpp/java/IBM/J6.0000145 **GBL_HFS_JAVA_DIR2 ""000146 **GBL_HFS_JAVA_DIR3 ""000147 **GBL_HFS_JAVA_DIR4 ""000148 **GBL_HFS_JAVA_DIR5 ""000149000150 **** z/OS UNIX System Services (USS) CLIST/EXEC library name:000151 **GBL_DSN_SYS1_SBPXEXEC "SYS1.SBPXEXEC"

4) If you enabled password encryption for the Tivoli Enterprise Monitoring Server and you areusing a library other than CSF.SCSFMOD0 (the default), you must uncomment and customizethe GBL_DSN_CSF_SCSFMOD0 parameter.

5) If no GLOBALTCPIPDATA statement is configured for your TCP/IP environment, customizethe following two parameters to enable the SYSTCPD DDNAME automatically for all startedtasks in this runtime environment:v GBL_DSN_TCP_SYSTCPD_TCPDATAv KDS_X_STC_SYSTCPD_INCLUDE_FLAG (in the LPAR configuration profile)

For example:

EDIT TSTEST.&userid.PLBHAHUB.WCONFIG($GBL$USR)Command ===>000120 GBL_DSN_TCP_SYSTCPD_TCPDATA "EZA.SEZAINST" <-- default is TCPIP.SEZAINST


EDIT IBM.ITM62351.LPAR1.WCONFIG(LPAR1)Command ===>000541 KDS_X_STC_SYSTCPD_INCLUDE_FLAG Y <-- default is N

6) Press F3 to save the parameters and return to the Customize PARMGEN configuration profilespanel, then press F3 again to return to the main Workflow panel.

4. Validate the configuration profile values you supplied:a. On the Workflow main panel, select option 9.






1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/152. $JOBINDX Review PARMGEN job index.3. KCIJPCCF Clone customized WCONFIG members. (Optional)4. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/155. KCIJPMC1 Merge profile from backup PLBHAHUB (Optional)6. KCIJPMC2 Merge profile from model RTE. (Optional)7. KCIJPCNV Convert an ICAT RTE Batch member. (Optional)8> PLBHAHUB Customize PARMGEN configuration profiles. Edited 2012/08/169. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)


%RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG($VALRPT).c. If the job gets a condition code greater than 4, review the $VALRPT. Enter 9s to view the report,

return to the previous step and correct the flagged values, then resubmit the validation job.5. From the Workflow menu, select option 10 to create the WK* runtime members and WKANSAMU

jobs.







1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/152. $JOBINDX Review PARMGEN job index. T3. KCIJPCCF Clone customized WCONFIG members. (Optional)4. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/155. KCIJPMC1 Merge profile from backup PLBHAHUB (Optional)6. KCIJPMC2 Merge profile from model RTE. (Optional)7. KCIJPCNV Convert an ICAT RTE Batch member. (Optional)8. PLBHAHUB Customize PARMGEN configuration profiles. Edited 2012/08/169> KCIJPVAL Validate PARMGEN profile parameter values. RC= 00000 2012/08/1610. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The Submit $PARSE Batch Jobs to Complete PARMGEN Setup panel is displayed:

===============================================================================KCIP@PRS ------ $PARSE/$PARSESV: CREATE THE RTE MEMBERS AND JOBS --------------Option ===>

Select option 1 to SUBMIT the full $PARSE job in WCONFIG for RTE=PLBHAHUB.Alternatively, select other options to SUBMIT $PARSE jobs individually.Press F1=Help for additional considerations when selecting options 2-5.






===============================================================================

Select option 1 to submit the generated $PARSE composite job.6. Submit the jobs that complete the setup of the runtime environment.

a. From the Workflow menu, select option 11.







1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/152. $JOBINDX Review PARMGEN job index. Viewed 2012/08/153. KCIJPCCF Clone customized WCONFIG members. (Optional) RC= 00000 2012/08/154. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/155. KCIJPMC1 Merge profile from backup PLBHAHUB (Optional)6. KCIJPMC2 Merge profile from model RTE. (Optional)7. KCIJPCNV Convert an ICAT RTE Batch member. (Optional)8. PLBHAHUB Customize PARMGEN configuration profiles. Edited 2012/08/169. KCIJPVAL Validate PARMGEN profile parameter values. RC= 00000 2012/08/1610> $PARSE Create the RTE members and jobs. RC= 00000 2012/08/1611. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The Submit Batch Jobs to Complete PARMGEN Setup panel is displayed.


Select option 1 to SUBMIT the composite jobs in WKANSAMU for RTE=PLBHAHUB.Alternatively, select other options to SUBMIT each job individually.Press F1=Help for additional considerations when selecting options 4-14.



2. KCIJPALO Allocate runtime libraries3. KCIJPLOD Load TK*->RK* runtime libraries4. KCIJPSEC Product security (Conditional)5. N/A System Variables IEBUPDTE (Conditional)6. KCIJPUSP USS preparation (Conditional)7. KCIJPUSS USS system set-up (Authorization required)8. KCIJPSYS System set-up (Authorization required)9. KCIJPLNK ASM/Link RKANMODU modules (Conditional)10. KCIJPIVP Configuration verification11. KCIJPCPW Backup WK* work libraries (Conditional)12. KCIJPCPR Backup RK* production user libs (Conditional)13. KCIJPW2R WK*->RK* deployment (Conditional)14. KCIJPMNT Composite maintenance job (Conditional)

b. Select option 1 to submit the KCIJPSUB master submit job, or, to submit each job individually,select the other options. If you select option 1, first review the KCIJPSUB job, and edit the jobaccording to which of the conditional jobs need to be submitted automatically, and which need tobe submitted manually (for example, jobs that require authorization).

Results

You have created runtime environment PLBHAHUB.


What to do next

Perform the applicable “Complete the configuration” steps in IBM Tivoli OMEGAMON XE and TivoliManagement Services on z/OS: Configuring the Tivoli Enterprise Monitoring Server on z/OS and start thehigh-availability hub.

Scenario PGN04: Clone an existing environment and convert its hubmonitoring server to a remoteIn this scenario, you clone an existing runtime environment to create a new environment that has thesame parameter values and product set. The new runtime environment inherits the parameter values andproduct set of the model runtime environment, but you convert the new environment from a full to asharing-with-SMP/E type and convert the static hub monitoring server inherited from the modelenvironment into a remote.

Before you begin

Launch the PARMGEN Workflow interface as described in “Start the Workflow user interface” on page135.

About this task

In this scenario, you clone the sample runtime environment PLB1SP22 created in scenario PGN01 tocreate a runtime environment named PLB2SP23, which runs on a different LPAR. This scenario assumesthat both environments share DASD, so no jobs or members need to be copied (transported) to the newLPAR.

PLB1SP22 is a full runtime environment that comprises a hub monitoring server and several monitoringagents. As you configure PLB2SP23, you convert it from a full to a sharing-with-SMPE environment. Youalso convert the hub monitoring server to a remote and configure it to connect to the high-availabilityhub Tivoli Enterprise Monitoring Server set up for runtime environment PLBHAHUB (see the PGN03scenario). The agents in the new environment automatically point to the local remote monitoring server.

This task involves 8 steps:1. Set up the PARMGEN work environment.2. Clone the WCONFIG members from the model runtime environment.3. Update the interim libraries and create the configuration profiles for the new environment.4. Merge the values from the model LPAR configuration profile.5. Customize the profile parameter values.6. Validate the configuration parameters.7. Create the runtime members and jobs.8. Submit the jobs to create the runtime environment.

Procedure1. Set up the PARMGEN work environment as follows:

a. On the PARMGEN Workflow main panel, specify the GBL_USER_JCL, RTE_PLIB_HILEV, andRTE_NAME values for the new runtime environment.If you do not do an R (RESET), the values for GBL_USER_JCL, RTE_PLIB_HILEV, and RTE_NAMEare carried forward from any previous session. In this case, simply change the RTE_NAME fromto PLB2SP23.







1. KCIJPCFG Set up PARMGEN work environment for an RTE.2. $JOBINDX Review PARMGEN job index.3. KCIJPCCF Clone customized WCONFIG members. (COND)4. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup PLB4SYSG (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

b. Select option 1

Because the runtime environment you specified is a new one, you are asked if you want to resetthe definition and status values before you proceed:








d. Press Enter to perform the reset. You are returned to the main Workflow panel.e. Select 1 again to begin setting up the work environment. The first Set up PARMGEN work

environment for an RTE panel (KCIP@PG1) is displayedf. In the first field, specify the dataset and member name of the LPAR configuration profile whose

values and product set you want to clone. In this example, you are cloning PLB1SP22. Ifappropriate, specify the Install Job Generator output library.



Specify the RTE profile library and member name that fits your scenario:==> TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22)___________________ (ex:&dset(&rte))- If creating a brand new RTE, leave this field blank. **or**- If creating another new RTE and you want to clone a PARMGEN-created


- If reconfiguring or upgrading this existing PLB2SP23 RTE, specify itsvalues (TSTEST.&userid.PLB2SP23.WCONFIG(PLB2SP23)) **or**




g. Press Enter to proceed to the next panel. If the GBL_USER_JCL data set does not exist, you arepresented with the following verification screen:





h. Perform one of the following steps:v Press Enter to allocate a new data set.v Specify the correct data set name, then press Enter.

The Set Up PARMGEN Work Environment for an RTE (2 OF 3) panel (KCIP@PG2) is displayed.i. Review the values on the example KCIP@PG2 panel and override as necessary. These values are

read from the LPAR profile you specified on the first panel.



GBL_USER_JCL: TSTEST.SYSPLEX.PARMGEN.JCLRTE_PLIB_HILEV: TSTEST.&useridRTE_NAME: &rte_name


GBL_INST_HILEV: _____________________HLQ of ICAT INSTLIB/INSTJOBS installation datasets




j. Press Enter to proceed to the next panel.The third setup panel is displayed. Depending on your screen resolution, you may have to scrolldown (PF8) to see all the parameters. (Note the More: + indicator.)




RTE_SMS_UNIT: ________ (Non-VSAM disk UNIT type)RTE_SMS_VOLUME: ________ (Non-VSAM disk VOLSER)RTE_SMS_MGMTCLAS: MCSTD___ (Non-VSAM disk MGMTCLAS)RTE_SMS_STORCLAS: SCTSTEST (Non-VSAM disk STORCLAS)RTE_SMS_VSAM_VOLUME: ______ (VSAM disk VOLSER)RTE_SMS_VSAM_MGMTCLAS: MCSTD___ (VSAM disk MGMTCLAS)RTE_SMS_VSAM_STORCLAS: SCTSTEST (VSAM disk STORCLAS)


RTE_TYPE: FULL _ (FULL, SHARING)RTE_SHARE: _______________ (SMP or shared RTE name)RTE_X_HILEV_SHARING: ________________________ (HLQ of shared RTE)RTE_TEMS_CONFIGURED_FLAG: Y (Y, N)RTE_TEMS_NAME_NODEID: PLB1SP22:CMS_______________ (e.g., RTE1:cms)RTE_STC_PREFIX: TSS1______________________ (Started task prefix)RTE_VTAM_APPLID_PREFIX TS1_______________________ (VTAM APPLID prefix)RTE_SYSV_SYSVAR_FLAG: N_________________________ (System variable flag)RTE_X_SYSV_OVERRIDE_SYMBOLS: N (Y, N) (SysVar override flag)RTE_SECURITY_USER_LOGON: NONE____ (RACF, ACF2, TSS, NAM, SAF, None)RTE_SECURITY_FOLD_PASSWORD_FLAG: Y (Fold to upper case (Y, N))RTE_SECURITY_CLASS: ________ (ACF2 max is 3 characters)RTE_X_SECURITY_EXIT_LIB: TSTEST.&userid.PLB1SP22.RKANSAMU____________GBL_DSN_ACF2_MACLIB: ____________________________________________ (If ACF2)KDS_TEMS_TYPE: HUB (Hub, Remote)KDS_TEMS_HA_TYPE: _______ (Hub TEMS type (HA))



Typically, you would make the following changes on this panel. However, this scenario merges thecustomized values from the model runtime environment. Those values will take precedence overany values specified here, so you will change these values in the LPAR configuration profile for thenew runtime environment.1) Change the type of runtime environment to Sharing-with-SMPE by setting RTE_TYPE to

SHARING and RTE_SHARE to SMP.2) Change RTE_TEMS_NAME_NODEID to PLB2SP23:CMS. (Note that the NODEID points to

PLB1SP22 because that was specified as the model runtime environment.)3) (Optionally) Change RTE_X_SECURITY_EXIT_LIB to TSTEST.userid.PLB2SP23.RKANSAMU. If

you are sharing the same security settings and permission as the model runtime environment,you can use the same library.

4) Convert the hub to a remote by setting KDS_TEMS_TYPE to REMOTE.k. Press Enter to proceed to the next panel.

The Display PARMGEN Environment Analysis panel is displayed:


Review message traffic before proceeding. These Kpp components are installedinto the TSTEST.ITM62351.TKANCUS SMP/E target library andare available for (re)configuration and/or upgrade into the RTE=PLB2SP23.Refer to the next panel ("EXCLUDE PRODUCTS FROM PARMGEN CUSTOMIZATION")for a legend of the Kpp components’ product names.34 Components installed in TSTEST.ITM62351.TKANCUS:KAH KC2 KC5 KDF KDO KDS KD2 KD4 KD5 KGWKHL KI2 KI5 KMC KMQ KMV KM2 KM5 KNA KN3KOB KON KQI KRG KRH KRJ KRK KRN KRV KRWKS3 KT1 KWO KYN

34 Components installed and configured in RTE profile PLB2SP23:KAH KC2 KC5 KDF KDO KDS KD2 KD4 KD5 KGWKHL KI2 KI5 KMC KMQ KMV KM2 KM5 KNA KN3KOB KON KQI KRG KRH KRJ KRK KRN KRV KRWKS3 KT1 KWO KYN

1 Components installed but not configured in RTE profile PLB2SP23:KT1End of data

This panel displays the list of products installed and available for configuration. The “Componentsinstalled and configured in the RTE profile PLB2SP23” field lists products that will be configured.

l. After you review the information on panel KCIP@PG4, press Enter to display panel [email protected] an X on the _ALL entry to configure only the same product sets as the model environment(PLB1SP22) contains. Then specify Y in the Confirm ==> Y (Y, N) field and press Enter. Notice the* (asterisk) next to the products that will be configured into this PLB2SP23 cloned runtimeenvironment.


KCIP@PG5 -------- EXCLUDE PRODUCTS FROM PARMGEN CUSTOMIZATION ---- Row 1 of 23Command ===> Scroll ===> CSR

Select (X) products to EXCLUDE from PARMGEN customization in RTE=PLB2SP23.



X ALL Exclude all not configured in RTE profile_ KC5* IBM Tivoli OMEGAMON XE for CICS on z/OS V510_ KDO* IBM Tivoli Decision Support for z/OS V181_ KDS* Tivoli Enterprise Monitoring Server V630_ KD4* IBM Tivoli Composite Application Manager for SOA V711_ KD5* IBM Tivoli OMEGAMON XE for DB2 PE/PM V511_ KGW* IBM Tivoli OMEGAMON XE for CICS TG on z/OS V510_ KI5* IBM Tivoli OMEGAMON XE for IMS on z/OS V510_ KMC* IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Configuration V710_ KMQ* IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Monitoring V710_ KM5* IBM Tivoli OMEGAMON XE on z/OS V510_ KN3* IBM Tivoli OMEGAMON XE for Mainframe Networks V510_ KOB* Tivoli OMEGAMON Enhanced 3270 User Interface V700_ KQI* IBM Tivoli OMEGAMON XE for Messaging - WebSphere Message Broker V710_ KRG* IBM Tivoli Advanced Audit for DFSMShsm V240_ KRH* IBM Tivoli Advanced Reporting and Management for DFSMShsm V240_ KRJ* IBM Tivoli Advanced Allocation Management for z/OS V320_ KRK* IBM Tivoli Automated Tape Allocation Manager for z/OS V320_ KRN* IBM Tivoli Advanced Catalog Management for z/OS V240_ KRV* IBM Tivoli Advanced Backup and Recovery for z/OS V230_ KRW* IBM Tivoli Tape Optimizer for z/OS V220_ KS3* IBM Tivoli OMEGAMON XE for Storage on z/OS V510_ KWO* IBM Tivoli OMEGAMON DE on z/OS - OMEGAVIEW and OMEGAVIEW II V510_ KYN* ITCAM for Application Diagnostics on z/OS V710

The GBL_USER_JCL(KCIJPCFG) file-tailored job is presented.m. Review the notes and values in the job and submit it. Return to the main Workflow panel.

2. Clone the WCONFIG members for the new runtime environment from the model runtimeenvironment's WCONFIG library:This step allows you to reuse any customizations to an existing PARMGEN environment for the newenvironment. The WCONFIG(KCIJPCCF) job clones user-customized members (such as Kpp$C*,Kpp$P*/Kpp@P*, Kpp$S*, KCI$X*, $JOBCARD, and $GBL$USR) from an existing WCONFIG library toa new one.a. From the Workflow main menu, select option 3.







1> KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/172. $JOBINDX Review PARMGEN job index.3. KCIJPCCF Clone customized WCONFIG members. (COND)4. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup PLB2SP23 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB2SP23 Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (COND)R New RTE Reset RTE, Status and Date fields. (COND)

The KCIJPCCF job is presented.b. Review the job to determine if you need to further modify the library concatenated in the

OLDWCNFG DDNAME.

000082 //* *******************************************************************000083 //CLONWCFG EXEC PGM=KCIPARSE,000084 // PARM=’MV=32000,MAXL=32000,MI=255,LIST=YES’000085 //STEPLIB DD DISP=SHR,000086 // DSN=TDITNT.DEV.ITM62351.TKANMOD000087 //OLDWCNFG DD DISP=OLD,000088 // DSN=TSTEST.&userid.PLB1SP22.WCONFIG000089 //NEWWCNFG DD DISP=SHR,000090 // DSN=TSTEST.&userid.PLB2SP23.WCONFIG000091 //SYSPRINT DD SYSOUT=*000092 //SYSVROUT DD SYSOUT=*000093 //SYSINLST DD SYSOUT=*000094 //SYSIN DD *

By default, this DDNAME already points to the WCONFIG library that you specified in the RTEprofile library field of the first work environment setup panel. If necessary, modify the job to pointto an existing WCONFIG library that contains the customized members you want cloned over tothe WCONFIG library for the new runtime environment.

c. Submit the job and return to the main Workflow panel. Notice the jobstep indicator on 3> todenote that this is the last step you performed. Also notice the updated Status and Date on theKCIJPCCF job (option 1).

3. Update the interim libraries and create profiles:a. Select option 4.







1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/172. $JOBINDX Review PARMGEN job index.3> KCIJPCCF Clone customized WCONFIG members. (COND) RC= 00000 2012/08/174. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup PLB4SYSG (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB2SP23 Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (COND)R New RTE Reset RTE, Status and Date fields. (COND)

The WCONFIG(KCIJPUP1) job is displayed.b. Review then submit the job.

The work libraries are updated with the configuration values you specified and the configurationprofiles for the PLB2SP23 runtime environment are created.

4. Merge the values from the LPAR configuration profile of the model runtime environment into theprofile for the new runtime environment.a. From the Workflow main menu, select option 6 (KCIJPMC2 Merge profile from model RTE).






1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/172. $JOBINDX Review PARMGEN job index. Viewed 2012/08/173. KCIJPCCF Clone customized WCONFIG members. (COND) RC= 00000 2012/08/174> KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/175. KCIJPMC1 Merge profile from backup PLB2SP23 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB2SP23 Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (COND)R New RTE Reset RTE, Status and Date fields. (COND)

The TSTEST.&userid.PLB2SP23.WCONFIG(KCIJPMC2) member is presented.


b. Review the job and make any required changes. By default, the OLDMEM(&value) parameter isalready set to the runtime environment you specified in the first setup panel (in this example,TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22).

===============================================================================EDIT TSTEST.&userid.PLB2SP23.WCONFIG(KCIJPMC2)Command ===> Scroll ===> CSR000068 //* MERGECHG Step:000069 //* Merge the changes in %OLDMEM% into %NEWMEM% member.000070 //* *******************************************************************000071 //MERGECHG EXEC PGM=IKJEFT01,DYNAMNBR=99,REGION=4M000072 //SYSEXEC DD DISP=SHR,000073 // DSN=TSTEST.ITM62351.TKANCUS000074 //SYSTSPRT DD SYSOUT=*000075 //SYSPRINT DD SYSOUT=*000076 //SYSTSIN DD *000077 KCIRPLBX +000078 BATCH +000079 SKIPVAR(TSTEST.ITM62351.TKANCUS(KCIDPGNX)) +000080 OLDMEM(TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22)) +000081 NEWMEM(TSTEST.&userid.PLB2SP23.WCONFIG(PLB2SP23))000082 /*===============================================================================

c. Submit the job to merge the profile values.5. Customize the PARMGEN configuration profiles.

a. From the Workflow main menu, select option 8.






1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/172. $JOBINDX Review PARMGEN job index.3. KCIJPCCF Clone customized WCONFIG members. (COND) RC= 00000 2012/08/174. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/175. KCIJPMC1 Merge profile from backup PLB2SP23 (COND)6> KCIJPMC2 Merge profile from model RTE. (COND) RC= 00000 2012/08/177. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB2SP23 Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (COND)R New RTE Reset RTE, Status and Date fields. (COND)

The Customize PARMGEN Configuration Profile Members panel is presented.


KCIP@PG6 ------ CUSTOMIZE PARMGEN CONFIGURATION PROFILE MEMBERS ---------------Option ===> 1(Required)* Select option 1 to customize the PLB2SP23 RTE LPAR profile:








Customization of the (WCONFIG(PLB2SP23) LPAR profile is required. Customization of the(WCONFIG($GBL$USR) global profile is optional, but you might want to review the profile todetermine if there are changes you want to make.

b. Select option 1 and customize the PLB2SP23 LPAR profile as follows.1) Change the type of runtime environment to Sharing-with-SMPE by setting RTE_TYPE to

SHARING and RTE_SHARE to SMP.2) Convert the hub to a remote by setting KDS_TEMS_TYPE to REMOTE.3) Change all references to PLB1SP22 (inherited from the model profile) to PLB2SP23.


ISREDDE2 TSTEST.&userid.PLB2SP23.WCONFIG(PLB2SP23)Command ===> C PLB1SP22 PLB2SP23 ALL Scroll ===> CSR****** ***************************** Top of Data ******************************- - - - - - - - - - - - - - - - - - 354 Line(s) not Displayed==CHG> RTE_NAMESV PLB2SP23- - - - - - - - - - - - - - - - - - - 6 Line(s) not Displayed==CHG> RTE_NAME PLB2SP23- - - - - - - - - - - - - - - - - - - 1 Line(s) not Displayed==CHG> RTE_DESCRIPTION "PLB2SP23 LPAR"- - - - - - - - - - - - - - - - - - 110 Line(s) not Displayed==CHG> RTE_TEMS_NAME_NODEID "PLB2SP23:CMS"- - - - - - - - - - - - - - - - - - - 20 Line(s) not Displayed==CHG> RTE_X_SECURITY_EXIT_LIB TSTEST.&userid.PLB2SP23.RKANSAM- - - - - - - - - - - - - - - - - - 296 Line(s) not Displayed==CHG> KDS_PH01_TEMS_NAME_NODEID "PLB2SP23:CMS"==CHG> KDS_PH01_TEMS_RTE PLB2SP23- - - - - - - - - - - - - - - - - - - 6 Line(s) not Displayed==CHG> KDS_PH01_TEMS_ALIAS_NAME "PLB2SP23:CMS"- - - - - - - - - - - - - - - - - - - 12 Line(s) not Displayed==CHG> **KDS_PU01_TEMS_NAME_NODEID "PLB2SP23:CMS"- - - - - - - - - - - - - - - - - - 332 Line(s) not Displayed==CHG> KC5_TEMS_NAME_NODEID "PLB2SP23:CMS"- - - - - - - - - - - - - - - - - - 190 Line(s) not Displayed==CHG> KGW_TEMS_NAME_NODEID "PLB2SP23:CMS"- - - - - - - - - - - - - - - - - - 198 Line(s) not Displayed==CHG> KM2_HIST_DSTOR_RKM2EDS_DSN1 TSTEST.&userid.PLB2SP23.RKM2EDS1- - - - - - - - - - - - - - - - - - - 3 Line(s) not Displayed==CHG> KM2_HIST_DSTOR_RKM2EDS_DSN2 TSTEST.&userid.PLB2SP23.RKM2EDS2- - - - - - - - - - - - - - - - - - - 3 Line(s) not Displayed==CHG> KM2_HIST_DSTOR_RKM2EDS_DSN3 TSTEST.&userid.PLB2SP23.RKM2EDS3- - - - - - - - - - - - - - - - - - - 24 Line(s) not Displayed==CHG> **KM2_HIST_WORKLOAD_PROFILE_DSN TSTEST.&userid.PLB2SP23.RKM2PROF- - - - - - - - - - - - - - - - - - - 45 Line(s) not Displayed==CHG> KM5_AGT_TEMS_NAME_NODEID "PLB2SP23:CMS"- - - - - - - - - - - - - - - - - - - 74 Line(s) not Displayed****** **************************** Bottom of Data ****************************

4) To reconfigure the agents to point to the local remote monitoring server, do an EXCLUDEFIND on TCP_HOST and change all to SP23 (the IP host name).

5) Change the started task name for the monitoring server (KDS_TEMS_STC).6) (Optional) Change all references of TS1 according to your site VTAM naming convention for

VTAM prefixes.

Note: This change is not typically required if the new runtime environment is a completeclone of the previous environment, differing only in the library names. For this scenario,PLB2SP23 is being set up for a conversion to a remote monitoring server, so the currentPLB1SP22 configuration is being preserved for the PGN01 scenario.

7) To configure the monitoring server to connect to the high-availability hub (created in PGN03),do an EXCLUDE FIND on all reference to KDS_HUB. Then specify the high-availability hubmonitoring server values that this remote monitoring server will connect to. In this example,these values represent the high-availability hub configured for the PLBHAHUB runtimeenvironment.


SP22 TSTEST.&userid.PLB2SP23.WCONFIG(PLB2SP23)Command ===> XF KDS_HUB Scroll ===> CSR000829000830 ** Note: The KDS_HUB_* values populate the xKANPARU(KDCSSITE) member000831 ** that Remote TEMS reads to know how to connect to its Hub.000832 KDS_HUB_TEMS_NAME_NODEID "PLBHAHUB"000833000834 ** If the TEMS is a Remote and requires VTAM SNA support:000835 KDS_HUB_VTAM_APPL_GLB_BROKER "" * Hub KDS_TEMS_VTAM_APPL_GLB_BROKER000836 KDS_HUB_VTAM_NETID "" * Hub KDS_TEMS_VTAM_NETID000837000838 ** If the TEMS is a Remote and requires TCP/IP support:000839 KDS_HUB_TCP_HOST "OMEGHAHUB"000840000841 ** If the TEMS is a Remote, specify port numbers of its Hub:000842 KDS_HUB_TCP_PIPE_PORT_NUM nnnnn * Hub KDS_TEMS_TCP_PIPE_PORT_NUM000843 KDS_HUB_TCP_UDP_PORT_NUM nnnnn * Hub KDS_TEMS_TCP_UDP_PORT_NUM000844 KDS_HUB_TCP_PIPE6_PORT_NUM "" * Hub KDS_TEMS_TCP_PIPE6_PORT_NUM000845 KDS_HUB_TCP_UDP6_PORT_NUM "" * Hub KDS_TEMS_TCP_UDP6_PORT_NUM000846 KDS_HUB_TCP_PIPES_PORT_NUM "" * Hub KDS_TEMS_TCP_PIPES_PORT_NUM000847 KDS_HUB_TCP_PIPE6S_PORT_NUM "" * Hub KDS_TEMS_TCP_PIPE6S_PORT_NUM- - - - - - - - - - - - - - - - - - 853 Line(s) not Displayed****** **************************** Bottom of Data ****************************

8) After you finish customizing the profile, press F3 to save the changes and return to theCustomize PARMGEN Configuration Profile Members panel. Press F3 again to return to themain Workflow panel.

6. Validate the configuration profile values that you supplied:a. On the Workflow main panel, select option 9.






1. KCIJPCFG Set up PARMGEN work environment for an RTE. Submitted 2012/08/102. $JOBINDX Review PARMGEN job index. Viewed 2012/08/103. KCIJPCCF Clone customized WCONFIG members. (COND) RC= 00000 2012/08/174. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/105. KCIJPMC1 Merge profile from backup PLB1SP22 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND) RC= 00000 2012/08/177. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8> PLB2SP23 Customize PARMGEN configuration profiles. Edited 2012/08/139. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)


%RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG($VALRPT). Enter 9s to view the report.c. If the job gets a condition code greater than 4, review the $VALRPT. Return to the previous step

and correct the parameter values, then resubmit the validation job.7. Create the WK* runtime members and the WKANSAMU jobs:

a. Select option 10 from the Workflow main menu.







1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/172. $JOBINDX Review PARMGEN job index. Viewed 2012/08/163. KCIJPCCF Clone customized WCONFIG members. (COND) RC= 00000 2012/08/174. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/175. KCIJPMC1 Merge profile from backup PLB4SYSG (COND)6. KCIJPMC2 Merge profile from model RTE. (COND) RC= 00000 2012/08/177. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB2SP23 Customize PARMGEN configuration profiles. Edited 2012/08/179> KCIJPVAL Validate PARMGEN profile parameter values. Submitted 2012/08/1710. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The $PARSE/$PARSESV: Create the RTE Members and Jobs panel is displayed.b. Select option 1 to submit the generated $PARSE composite job.

===============================================================================KCIP@PRS ------ $PARSE/$PARSESV: CREATE THE RTE MEMBERS AND JOBS --------------Option ===>

Select option 1 to SUBMIT the full $PARSE job in WCONFIG for RTE=PLB2SP23Alternatively, select other options to SUBMIT $PARSE jobs individually.Press F1=Help for additional considerations when selecting options 2-5.






===============================================================================

The $PARSE member is presented.c. Review the member, then submit the job. Return to the main Workflow panel.

8. Submit the batch jobs to complete the setup of the runtime environment:a. Select option 11 from the Workflow main menu.







1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/162. $JOBINDX Review PARMGEN job index. Viewed 2012/08/163. KCIJPCCF Clone customized WCONFIG members. (COND) RC= 00000 2012/08/164. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/175. KCIJPMC1 Merge profile from backup PLB2SP23 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND) RC= 00000 2012/08/177. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB2SP23 Customize PARMGEN configuration profiles. Edited 2012/08/179. KCIJPVAL Validate PARMGEN profile parameter values. RC= 00000 2012/08/1710> $PARSE Create the RTE members and jobs. Submitted 2012/08/1711. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The Submit Batch Jobs to Complete PARMGEN Setup (KCIP@SUB) panel is displayed.b. Select option 1 if you want to submit the KCIJPSUB master SUBMIT job, or select the other

options to submit each job individually. If you select option 1, review the KCIJPSUB job first, andedit the job according to which of the conditional jobs need be submitted automatically and whichneed to be submitted manually (for example, for reasons of authorization).





2. KCIJPALO Allocate runtime libraries3. KCIJPLOD Load TK*->RK* runtime libraries4. KCIJPSEC Product security (Conditional)5. N/A System Variables IEBUPDTE (Conditional)6. KCIJPUSP USS preparation (Conditional)7. KCIJPUSS USS system set-up (Authorization required)8. KCIJPSYS System set-up (Authorization required)9. KCIJPLNK ASM/Link RKANMODU modules (Conditional)10. KCIJPIVP Configuration verification11. KCIJPCPW Backup WK* work libraries (Conditional)12. KCIJPCPR Backup RK* production user libs (Conditional)13. KCIJPW2R WK*->RK* deployment (Conditional) R14. KCIJPMNT Composite maintenance job (Conditional)

c. Submit the job.

Results

You have created a copy of the PLB1SP22 runtime environment with a remote monitoring server insteadof a hub and you have changed the runtime environment from full to sharing-with-SMP/E.


What to do next

Complete any configuration steps required outside the configuration software. See the Planning andConfiguration Guide for each product for details.

Scenario PGN05: Convert an existing Configuration Tool environmentto PARMGEN and upgrade it to the current releaseThis scenario converts an existing runtime environment created by the Configuration Tool to PARMGEN,upgrades the Tivoli Enterprise Monitoring Server and monitoring agents configured in the environment,and adds a new component, the OMEGAMON enhanced 3270 user interface. The new environmentshares files with the base environment named BASE2, created in Scenario PGN02, for which systemvariables are enabled. In addition to inheriting the parameter values from the converted ConfigurationTool runtime environment, the new environment merges values from the LPAR and global profiles of anexisting environment that already has system variables set.

About this task

Before you can begin PARMGEN configuration, you must extract the parameters used to build yourexisting Configuration Tool environment and store them in a batch parameter deck.

Extract the Configuration Tool parametersThis procedure extracts the parameter values for a selected runtime environment into a batch modeparameter file.

About this task

If you have not already created a batch parameter deck for the runtime environment, complete thefollowing steps. If you intend to upgrade the products in the environment, make sure that theConfiguration Tool is pointed at the SMP/E target libraries that have the upgraded SMP/E packageinstalled. In a sharing type environment, you must also extract the parameters for the sharedenvironment, because in a conversion scenario, the conversion job (KCIJPCNV) looks in INSTJOBS for theparameters of the shared environment to set up the parameters of the sharing environment.

Procedure1. Invoke the Configuration Tool:

EX ’&shilev.INSTLIB’

2. From the main menu, select option 3 (Configure products), and press Enter.3. From the next panel, select option 1 (Select product to configure), and press Enter.4. On the next panel, select any product, and press Enter.5. On the next panel, type a Z by the runtime environment to be processed, and press Enter.6. On the next panel, select option 1 (Create/Clone batch mode parameters), and press Enter.7. On the next panel, select option 1 (Create batch mode parameter deck), and press Enter.8. On the next panel, verify that the Parameter library field contains the name of the correct INSTJOBS

data set and that the Member name field contains the name of the selected environment. Then pressEnter. The generated member is displayed (if you selected that option) and saved in the INSTJOBSdata set.

9. If you want the new PARMGEN runtime environment to have different high-level qualifiers than theConfiguration Tool environment, but reuse most of the configuration values for the productsconfigured in this runtime environment, change them now. Changing the high-level qualifiers leavesthe Configuration Tool environment available for staged upgrades.


To change the qualifiers, edit the batch parameter member and do a change all to change the RTEhigh-level qualifiers to the new qualifiers. For example, RTE_HILEV, RTE_VSAM_HILEV andvariants.

Important: If you are converting a sharing type environment, you must also change the high-levelqualifiers for the shared environment (base or full).

10. Exit the Configuration Tool.

What to do next

Now you can begin the process that will convert the Configuration Tool parameter deck values to theirPARMGEN equivalents, create a runtime environment, and upgrade the products in the environment.

Create and configure the converted PARMGEN runtime environmentThis procedure converts the existing Configuration Tool parameters to their PARMGEN equivalents. Inaddition, it clones the customized members from the WCONFIG library of an existing runtimeenvironment, merges the values from the LPAR configuration profile of that runtime environment,upgrades the IBM Tivoli Monitoring components in the new runtime environment to the latest release,and configures the OMEGAMON enhanced 3270 user interface.

Before you begin

This scenario uses the PARMGEN Workflow user interface to set up the work environment, customizeprofiles, and create and submit the jobs that create the runtime environment. For instructions onlaunching the interface, see “Start the Workflow user interface” on page 135.

About this task

The conversion of the Configuration Tool environment preserves the customizations made in that runtimeenvironment. Cloning existing WCONFIG members (for example, $GBL$USR) means that you do nothave to configure those files if you are using the same global system procedure libraries, VTAM lists, andso forth. In addition, there may be new GBL_* parameters in $GBL$USR that were not in the originalConfiguration Tool runtime environment. Merging means you do not have to configure the symbolics inthis environment.

There are 9 steps involved in this task:1. Set up PARMGEN work libraries.2. (Optional) Clone the customized WCONFIG members from an existing runtime environment.3. Update the libraries and create the profiles.4. Convert the Configuration Tool environment values to PARMGEN.5. Merge values from the LPAR profile of an existing PARMGEN environment which already has

variables customized into the profiles for the new environment.6. Customize the configuration profiles.7. Validate the parameters in the configuration profiles8. Create the runtime members and jobs.9. Submit the batch jobs to complete the set up of the runtime environment.

Procedure1. Set up the PARMGEN work environment as follows:

a. On the PARMGEN Workflow main panel, specify the GBL_USER_JCL, RTE_PLIB_HILEV, andRTE_NAME values for the new runtime environment.


If you do not do an R (RESET), the values for GBL_USER_JCL, RTE_PLIB_HILEV, and RTE_NAMEare carried forward from any previous session. If these are appropriate for the new environment,simply change the RTE_NAME. The RTE_NAME should be the same as the name of theConfiguration Tool batch member that you are converting. In the following example, the newruntime environment is named PLB3SP13 and it uses the same JCL library and high-level qualifieras previously created environments.






1. KCIJPCFG Set up PARMGEN work environment for an RTE.2. $JOBINDX Review PARMGEN job index.3. KCIJPCCF Clone customized WCONFIG members. (COND)4. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup PLB3SP13 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB3SP13 Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

b. Select option 1

Because the runtime environment you specified is a new one, you are asked if you want to resetthe definition and status values before you proceed:








d. Press Enter to perform the reset. You are returned to the main Workflow panel.e. Select 1 again to begin setting up the work environment. The first Set up PARMGEN work

environment for an RTE panel (KCIP@PG1) is displayedf. In the first field, specify the %GBL_INST_HILEV%.INSTJOBS(%RTE_NAME%) Configuration Tool

batch parameter member that you want to convert. If appropriate, specify the Install Job Generatoroutput library.



Specify the RTE profile library and member name that fits your scenario:==> TDOMPT.ITM623.INSTJOBS(PLB3SP13)___________________ (ex:&dset(&rte))- If creating a brand new RTE, leave this field blank. **or**- If creating another new RTE and you want to clone a PARMGEN-created


- If reconfiguring or upgrading this existing PLB3SP13 RTE, specify itsvalues (TSTEST.&userid.PLB3SP13.WCONFIG(PLB3SP13)) **or**




g. Press Enter to proceed to the next panel. If the GBL_USER_JCL data set does not exist, you arepresented with the following verification screen:





h. Perform one of the following steps:v Press Enter to allocate a new data set.v Specify the correct data set name then press Enter.

The Set Up PARMGEN Work Environment for an RTE (2 OF 3) panel (KCIP@PG2) is displayed.i. Review the values on the example KCIP@PG2 panel and override them if necessary.

These values are read from the member with the same name as the environment in the runtimeenvironment's profile library: &hlq.INSTJOBS(PLB3SP13), in this case.



GBL_USER_JCL: TSTEST.SYSPLEX.PARMGEN.JCLRTE_PLIB_HILEV: TSTEST.&useridRTE_NAME: PLB3SP13

nter parameter values appropriate for your environment:

GBL_INST_HILEV: TDOMPT.ITM623______________________HLQ of ICAT INSTLIB/INSTJOBS installation datasets




j. Press Enter to proceed to the next panel. The third setup panel (KCIP@PG3) is displayed.






RTE_TYPE: SHARING_ (FULL, SHARING)RTE_SHARE: BASE ___________ (SMP or shared RTE name)RTE_X_HILEV_SHARING: ________________________ (HLQ of shared RTE)RTE_TEMS_CONFIGURED_FLAG: Y (Y, N)RTE_TEMS_NAME_NODEID: PLB3SP13:CMS_______________ (e.g., RTE1:cms)RTE_STC_PREFIX: TSS3______________________ (Started task prefix)RTE_VTAM_APPLID_PREFIX TS13___________ (VTAM APPLID prefix)RTE_SYSV_SYSVAR_FLAG: Y_________________________ (System variable flag)RTE_X_SYSV_OVERRIDE_SYMBOLS: N (Y, N) (SysVar override flag)RTE_SECURITY_USER_LOGON: NONE____ (RACF, ACF2, TSS, NAM, SAF, None)RTE_SECURITY_FOLD_PASSWORD_FLAG: Y (Fold to upper case (Y, N))RTE_SECURITY_CLASS: ________RTE_X_SECURITY_EXIT_LIB: TSTEST.&userid.PLB3SP13.RKANSAMU________GBL_DSN_ACF2_MACLIB: ____________________________________________ (If ACF2)KDS_TEMS_TYPE: REMOTE___ (Hub, Remote)KDS_TEMS_HA_TYPE: _______ (Hub TEMS type (HA))


You do not need to make any changes to this panel, because any changes you make will beoverridden when you merge the LPAR profile from the existing runtime environment.

k. Press Enter to proceed to the next panel. The Display PARMGEN Environment Analysis panel isdisplayed:


KCIP@PG4 ------------ DISPLAY PARMGEN ENVIRONMENT ANALYSIS --- Row 1 to 6 of 6Command ===> Scroll ===> PAGE

Review message traffic before proceeding. These Kpp components are installedinto the TSTEST.ITM62351.TKANCUS SMP/E target library andare available for (re)configuration and/or upgrade into the RTE=PLB3SYSGRefer to the next panel ("EXCLUDE PRODUCTS FROM PARMGEN CUSTOMIZATION")for a legend of the Kpp components’ product names.

34 Components installed in TSTEST.ITM62351.TKANCUS:KAH KC2 KC5 KDF KDO KDS KD2 KD4 KD5 KGWKHL KI2 KI5 KMC KMQ KMV KM2 KM5 KNA KN3KOB KON KQI KRG KRH KRJ KRK KRN KRV KRWKS3 KT1 KWO KYN

20 Components installed and configured in the RTE profile PLB3SP13KC2 KC5 KDF KDS KD2 KD5 KGW KHL KI2 KI5KMC KMQ KMV KM2 KM5 KN3 KON KQI KS3KWO

14 Components installed but not configured in RTE profile PLB3SP13:KAH KDO KD4 KNA KOB KRG KRH KRJ KRK KRNKRV KRW KT1 KYNEnd of data

This panel displays the list of products installed and available for configuration. The “Componentsinstalled and configured in the RTE profile PLB3SP13” field lists products that will be configured(this list is inherited from INSTJOBS(PLB3SP13).

l. Review the information on panel to determine if you want to configure additional components,then press Enter to display the next panel. The Exclude Products from PARMGEN Customizationpanel (KCIP@PG5) is displayed.

m. Place an X before all of the products that do not have an asterisk except for KOB. The asterisks (*)indicate the components configured in the Configuration Tool environment. However, the versionnumbers reflect the latest version installed in the SMP/E target libraries to which the componentswill be upgraded.



Select (X) products to EXCLUDE from PARMGEN customization in RTE=PLB3SP13



_ ALL Exclude all not configured in RTE profileX KAH IBM Tivoli System Automation for z/OS V330_ KC5* IBM Tivoli OMEGAMON XE for CICS on z/OS V510X KDO IBM Tivoli Decision Support for z/OS V181_ KDS* Tivoli Enterprise Monitoring Server V630X KD4 IBM Tivoli Composite Application Manager for SOA V711_ KD5* IBM Tivoli OMEGAMON XE for DB2 PE/PM V511_ KGW* IBM Tivoli OMEGAMON XE for CICS TG on z/OS V510_ KHL* IBM OMEGAMON z/OS Management Console V410_ KI5* IBM Tivoli OMEGAMON XE for IMS on z/OS V510_ KMC* IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Configuration V710_ KMQ* IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Monitoring V710_ KM5* IBM Tivoli OMEGAMON XE on z/OS V510X KNA IBM Tivoli NetView for z/OS Agent V610_ KN3* IBM Tivoli OMEGAMON XE for Mainframe Networks V510_ KOB Tivoli OMEGAMON Enhanced 3270 User Interface V700_ KQI* IBM Tivoli OMEGAMON XE for Messaging - WebSphere Message Broker V710X KRG IBM Tivoli Advanced Audit for DFSMShsm V240X KRH IBM Tivoli Advanced Reporting and Management for DFSMShsm V250X KRJ IBM Tivoli Advanced Allocation Management for z/OS V320X KRK IBM Tivoli Automated Tape Allocation Manager for z/OS V320X KRN IBM Tivoli Advanced Catalog Management for z/OS V240X KRV IBM Tivoli Advanced Backup and Recovery for z/OS V230X KRW IBM Tivoli Tape Optimizer for z/OS V220_ KS3* IBM Tivoli OMEGAMON XE for Storage on z/OS V510_ KWO* IBM Tivoli OMEGAMON DE on z/OS - OMEGAVIEW and OMEGAVIEW II V510X KYN ITCAM for Application Diagnostics on z/OS V710.03End of data

The GBL_USER_JCL(KCIJPCFG) file-tailored job is presented.n. After you have reviewed the notes and values in the job, submit it and return to the main

Workflow panel.

The PARMGEN work libraries are created.2. Clone WCONFIG members for the new runtime environment from another runtime environment's

WCONFIG library):The WCONFIG(KCIJPCCF) job clones user-customized members (Kpp$C*, Kpp$P*/Kpp@P*, Kpp$S*),$JOBCARD, and common PARMGEN configuration profile members such as $GBL$USR) from anexisting WCONFIG library to a new one. In this scenario, we clone the members from the runtimeenvironment created in scenario PGN02.a. From the Workflow main menu, select option 3.







1> KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/172. $JOBINDX Review PARMGEN job index.3. KCIJPCCF Clone customized WCONFIG members. (COND) RC= 00000 2012/08/174. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup PLB3SP13 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB3SP13 Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The TSTEST.&userid.PLB3SP13.WCONFIG(KCIJPCCF) job is presented.b. Modify the library concatenated in the OLDWCNFG DDNAME to point to an existing WCONFIG

library that contains the customized members you want cloned over to the WCONFIG library forthe new runtime environment (in this case, TSTEST.&userid.PLB3SYSG.WCONFIG).

c. Submit the job, then return to the main Workflow panel. Note that a jobstep indicator (>) appearson option 3 to denote that this is the last step you performed. The Status and Date fields for theKCIJPCCF job are updated.

The customized members have been copied to the WCONFIG library of the new runtime environment(TSTEST.&userid.PLB3SP13.WCONFIG).

3. Update the interim libraries and create profiles:a. Select option 4 from the Workflow main menu.






1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/172. $JOBINDX Review PARMGEN job index. Viewed 2012/08/173> KCIJPCCF Clone customized WCONFIG members. (COND) RC= 00000 2012/08/174. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup PLB3SP13 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB3SP13 Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)


The WCONFIG(KCIJPUP1) job is displayed.b. Review then submit the job and return to the main Workflow panel.

The interim libraries for the new runtime environment are updated and the configuration profiles arecreated.

4. Convert the Configuration Tool batch member in INSTJOBS(PLB3SP13) to PARMGEN format.a. Select option 7 from the Workflow main menu.






1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/172. $JOBINDX Review PARMGEN job index. Viewed 2012/08/173. KCIJPCCF Clone customized WCONFIG members. (COND) RC= 00000 2012/08/174> KCIJPUP1 Update interim libraries and create profiles. Submitted 2012/08/175. KCIJPMC1 Merge profile from backup PLB3SP13 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB3SP13 Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The KCIJPCNV job is displayed.b. Review the notes and customize parameters as appropriate. In particular, note that you can

convert several Configuration Tool batch files at once.c. Submit the job. Check for successful condition codes and return to the main Workflow panel.

5. (Optional) Merge values from the customized LPAR profile from another runtime environment intothe profile for the new runtime environment. Merging the values from the LPAR profile means thatyou do not have do change all the parameter values to symbolics.a. From the Workflow main menu, select option 6 (KCIJPMC2 Merge profile from model RTE).







1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/172. $JOBINDX Review PARMGEN job index. Viewed 2012/08/173. KCIJPCCF Clone customized WCONFIG members. (COND) RC= 00000 2012/08/174. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/175. KCIJPMC1 Merge profile from backup PLB3SP13 (COND) RC= 00000 2012/08/176. KCIJPMC2 Merge profile from model RTE. (COND)7> KCIJPCNV Convert an ICAT RTE Batch member. (COND) RC= 00000 2012/08/178. PLB3SP13 Customize PARMGEN configuration profiles. Edited 2012/08/179. KCIJPVAL Validate PARMGEN profile parameter values. RC= 00000 2012/08/1710. $PARSE Create the RTE members and jobs. RC= 00000 2012/08/1711. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The TSTEST.&userid.PLB3SP13.WCONFIG(KCIJPMC2) member is presented.b. Customize the member by changing the OLDMEM(&value) parameter to the runtime environment

whose configuration settings you want to clone (in this example, TSTEST.&sysuid.PLB3SYSG.WCONFIG(PLB3SYSG), which already has a fully customized PARMGENprofile that uses symbolics).

===============================================================================EDIT TSTEST.&sysuid.PLB3SP13.WCONFIG(KCIJPMC2)Command ===> Scroll ===> CSR000068 //* MERGECHG Step:000069 //* Merge the changes in %OLDMEM% into %NEWMEM% member.000070 //* *******************************************************************000071 //MERGECHG EXEC PGM=IKJEFT01,DYNAMNBR=99,REGION=4M000072 //SYSEXEC DD DISP=SHR,000073 // DSN=TSTEST.ITM62351.TKANCUS000074 //SYSTSPRT DD SYSOUT=*000075 //SYSPRINT DD SYSOUT=*000076 //SYSTSIN DD *000077 KCIRPLBX +000078 BATCH +000079 SKIPVAR(TSTEST.ITM62351.TKANCUS(KCIDPGNX)) +000080 OLDMEM(TSTEST.&userid.PLB3SYSG.WCONFIG(PLB3SYSG)) +000081 NEWMEM(TSTEST.&userid.PLB3SP13.WCONFIG(PLB3SP13))000082 /*===============================================================================

c. Submit the job to merge the profiles.6. Customize PARMGEN configuration profiles.

a. From the Workflow main menu, select option 8.







1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/172. $JOBINDX Review PARMGEN job index. Viewed 2012/08/163. KCIJPCCF Clone customized WCONFIG members. (COND) RC= 00000 2012/08/174. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/175> KCIJPMC1 Merge profile from backup PLB3SP13 (COND) RC= 00000 2012/08/176. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND) RC= 00000 2012/08/178. PLB3SP13 Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The Customize PARMGEN Configuration Profile Members panel is presented.b. Customize the applicable profiles.

KCIP@PG6 ------ CUSTOMIZE PARMGEN CONFIGURATION PROFILE MEMBERS ---------------Option ===>(Required)* Select option 1 to customize the PLB3SP13 RTE LPAR profile:








v Customization of the WCONFIG(PLB3SP13) LPAR profile (option 1) to edit parameters specificto PBL3SYSG (inherited from the merge) is required.

v Customization of the WCONFIG($GBL$USR) global profile (option 2) is optional, but youshould review it to determine if other changes need to be applied.

v Customization of the TSTEST.SYSPLEX.PARMGEN.JCL(PLB3SP13) system variables profile(option 3) is also required to define the user-defined symbols that will be used as the parametervalues of the LPAR profile parameters in WCONFIG(PLB3SP13).

c. Customize the PLB3SP13 LPAR profile to add new product parameters or component parametersbrought in by the upgrade (KOB* in this case).

Tip: For guidance on setting parameter values, see the following sources of information:v Comments in the PARMGEN configuration profiles


v Online help for the configuration profile.v IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Parameter

Reference

v Parameter references for your monitoring agents1) From the KCIJPMC2 merge profile job, the PLB3SP13 LPAR profile inherited all of the values

from PLB3SYSG runtime environment. Change all references of PLB3YSG to PLB3SP13.

ISREDDE2 TSTEST.&userid.PLB3SP13.WCONFIG(PLB3SP13)ommand ===> C PLB3SYSG PLB3SP13 ALL Scroll ===> CSR

2) Do an EXCLUDE FIND on all references to “PLB3SP13”. Then see if any of the parametersremaining should be converted to a more generic PLB3&SYSNAME..

Important:

v In a system variables scenario, the RTE_NAMESV, RTE_HILEVSV, andRTE_VSAM_HILEVSV parameters must have a nonsymbolic value, as these parameters areused directly in the WKANSAMU(KCIJV*) jobs. In the RTE_NAMESV parameter, the valuemust remain PLB3SP13.

v The RTE_X_SECURITY_EXIT_LIB library is used in the WKANSAMU(KCIJcSEC) securityjob. If security exits are typically shared across different runtime environments, you mayeven specify a more global security exit library that different environments can share.

ISREDDE2 TSEST.&userid.PLB3SP13.WCONFIG(PLB3SP13)Command ===> XF PLB3SP13 Scroll ===> CSR****** ***************************** Top of Data ******************************- - - - - - - - - - - - - - - - - - - 24 Line(s) not Displayed000149 RTE_NAMESV PLB3SP13- - - - - - - - - - - - - - - - - - - 13 Line(s) not Displayed****** **************************** Bottom of Data ****************************

Note: If you are creating this runtime environment on any other LPAR than SP13, you mustenable system variable overrides (RTE_X_SYSV_OVERRIDE_SYMBOLS=Y). This ensures thatvariable resolve to the correct values for the system on which the environment exists. Whereyou run the jobs, depends upon when you want to transport the files for the environment. Seethe topic “PARMGEN transport scenarios” in the IBM Tivoli OMEGAMON XE and TivoliManagement Services on z/OS: Common Planning and Configuration Guide.

If you are setting up the environment on the target system, you do not need to enable theoverrides.

3) After you finish customizing the LPAR profile, press F3 to save the changes and return to theCustomize PARMGEN Configuration Profile Members panel.

d. Customize the PLB3SP13 system variables profile to define all user-defined symbols used in theprevious steps.1) Select option 3. The PLB3SP13 system variables profile is presented.2) Because the PLB3SP13 LPAR profile inherited the symbolics from the merged PLB3SYSG LPAR

profile, replace the contents of TSTEST.SYSPLEX.PARMGEN.JCL(PLB3SP13) with the contentsof the TSTEST.SYSPLEX.PARMGEN.JCL(PLB3SYSG) system variables profile (as the modelenvironment already has the symbolics defined.)Now both monitoring servers point to the same hub monitoring server (the static hubmonitoring server on SP22 and the agents point to the local monitoring server. The PLB3SP13runtime environment also inherited the same back up monitoring server, which happens to bethe hub on SP22.

3) Save the profile and press F3 until you return to the main Workflow panel.7. Validate the PARMGEN LPAR configuration profile values:


a. On the Workflow main panel, select option 9.






1. KCIJPCFG Set up PARMGEN work environment for an RTE. Submitted 2012/08/102. $JOBINDX Review PARMGEN job index. Viewed 2012/08/103. KCIJPCCF Clone customized WCONFIG members. (COND)4. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/105. KCIJPMC1 Merge profile from backup PLB1SP22 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8> PLB3SP13 Customize PARMGEN configuration profiles. Edited 2012/08/139. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)


%RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG($VALRPT). Enter 9s option view the report.c. If the job gets a condition code greater than 4 (COND CODE 0004), review the $VALRPT. Return

to the previous step and correct the parameter values, then resubmit the validation job.8. Create the WK* runtime members and the WKANSAMU jobs:

a. Select option 10.






1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/172. $JOBINDX Review PARMGEN job index. Viewed 2012/08/163. KCIJPCCF Clone customized WCONFIG members. (COND) RC= 00000 2012/08/174. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/175. KCIJPMC1 Merge profile from backup PLB3SP13 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND) RC= 00000 2012/08/177. KCIJPCNV Convert an ICAT RTE Batch member. (COND) RC= 00000 2012/08/178. PLB3SP13 Customize PARMGEN configuration profiles. Edited 2012/08/179> KCIJPVAL Validate PARMGEN profile parameter values. Submitted 2012/08/1710. $PARSESV Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The $PARSE/$PARSESV: Create the RTE Members and Jobs (KCIP@PRS) panel is displayed.b. Select option 1 to submit the generated $PARSESV composite job.



Select option 1 to SUBMIT the full $PARSESV job in WCONFIG for RTE=PLB3SP13.Alternatively, select other options to SUBMIT $PARSE jobs individually.Press F1=Help for additional considerations when selecting options 2-5.






The $PARSESV member is presented.c. Review the member for any jobs that need to be submitted manually, then submit the job. Return

to the main Workflow panel.9. Submit the batch jobs to complete the PARMGEN setup:

a. Select option 11 from the menu.






1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/172. $JOBINDX Review PARMGEN job index. Viewed 2012/08/163. KCIJPCCF Clone customized WCONFIG members. (Optional) RC= 00000 2012/08/174. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/175. KCIJPMC1 Merge profile from backup PLB3SP13 (Optional) RC= 00000 2012/08/176. KCIJPMC2 Merge profile from model RTE. (Optional)7. KCIJPCNV Convert an ICAT RTE Batch member. (Optional) RC= 00000 2012/08/178. PLB3SP13 Customize PARMGEN configuration profiles. Edited 2012/08/179. KCIJPVAL Validate PARMGEN profile parameter values. RC= 00000 2012/08/1710> $PARSESV Create the RTE members and jobs. Submitted 2012/08/1711. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The Submit Batch Jobs to Complete PARMGEN Setup (KCIP@SUB) panel is displayed.b. Select option 1 if you want to submit the KCIJVSUB master SUBMIT job, or select the other

options to submit each job individually. If you select option 1, review the KCIJVSUB job first, andedit the job according to which the conditional jobs need be submitted automatically and whichneed to be submitted manually.








c. Press Enter. The following message is displayed:



d. Press Enter to edit the KCIJPSUV job. Jobs that require authorization or are conditional are notsubmitted automatically. You must either submit them manually, or uncomment them to runautomatically.

e. Press F3, and you are automatically be presented with the KCIJVSUB job for submission. Submitthe job. Check the status of each of the jobs submitted. The allocation and load jobs must runsuccessfully, or others jobs will not run.





Results

You have created the PLB3SP13 runtime environment. Perform the applicable Complete the Configurationsteps in your planning and configuration guides, and start the products on the appropriate LPAR.



Chapter 3. SMP/E maintenance scenarios

After you apply SMP/E maintenance, at a minimum you must run the KCIJcLOD job to copy files fromTK* to the runtime RK* libraries (where c=V if system variables are enabled, c=P if variables are notenabled. Depending upon the maintenance scenario you are enacting, you may need to performadditional steps.

“Post-SMP/E maintenance steps” provides a high level summary of the steps required for enacting themost common maintenance scenarios following the application of SMP/E maintenance. The topics thatfollow provide step-by-step instructions for executing those scenarios.

Post-SMP/E maintenance stepsDuring maintenance of a runtime environment, only a subset of the PARMGEN KCIJ* jobs need to bererun to refresh the read-only product execution runtime libraries and the product-specific RKANDATVlibrary.

The PARMGEN jobs that need to be regenerated or resubmitted in addition to the KCIJcLOD load jobvary depending on which maintenance scenario you want to complete:1. Apply SMP/E maintenance to an existing RTE with no new configuration changes.2. Apply SMP/E maintenance to an existing RTE with new configuration changes, but use or run with

IBM-supplied configuration defaults.3. Apply SMP/E maintenance to an existing RTE with new configuration changes where you want to

exploit or override the IBM-supplied configuration defaults.4. Upgrade the SMP/E environment to new FMID versions and upgrade an existing RTE with no new

configuration changes.5. Upgrade the SMP/E environment to new FMID versions and upgrade an existing RTE with new

configuration changes, but use or run with IBM-supplied configuration defaults.6. Upgrade the SMP/E environment to new FMID versions and upgrade an existing RTE with new

configuration changes where you want to exploit or override the IBM-supplied configuration defaults.

For scenarios 1 and 4, only the KCIJcLOD job is required.

For scenarios 2, 3, 5, and 6, additional jobs are required.

Scenario SMPE01: Apply maintenance to an existing runtimeenvironment without changing the configurationIn this scenario, you apply maintenance to an existing runtime environment without changing theexisting configuration.

About this task

Complete the following procedure to apply maintenance. You can run the job yourself, or use thePARMGEN Workflow tool.

Procedure

Run the KCIJcLOD job using one of the following methods (where c=V if system variables are enabled;c=P if variables are not enabled):


v Submit the KCIJcLOD job in the %RTE_PLIB_HILEV%.%RTE_NAME%.WKANSAMU library.v Submit the KCIJcLOD job from the PARMGEN Workflow interface:

1. Select option 11 from the Workflow main menu to display the Submit Batch Jobs to CompletePARMGEN Setup menu:


Select option 1 to SUBMIT the composite jobs in WKANSAMU for RTE=&rte_name.Alternatively, select other options to SUBMIT each job individually.Press F1=Help for additional considerations when selecting options 4-14.




2. Select option 3.The KCIJPLOD job (or KCIJVLOD, if system variables are enabled in the runtime environment) isdisplayed.

3. Review the notes and submit the job.

The job copies members of the products' SMP/E target libraries to the read-only RK* runtime libraries.The runtime libraries are loaded with IEBCOPY in a two-step process:1. All members are copied from the SMP/E target libraries to the runtime libraries.2. The runtime libraries are compressed.

If any members in the IEBCOPY steps are not found in the source libraries, a return code of 4 (which isacceptable) is generated.See the comments in the KCIJcLOD JCL for further information.

Results

The runtime environment is updated with the maintenance. The runtime members in the production userlibraries (RKANCMDU, RKANPARU, RKANSAMU, RKD2PAR**, RKD2PRF**, RKD2SAM**) are runningwith the original runtime members without any new parameters or members possibly introduced withthe maintenance. For example, without any new parameters in RKANPARU(KppENV), or without newmember that would typically be populated in the RK* user library. Similar processing is done for thePARMGEN WK* work libraries.


Scenario SMPE02: Apply SMP/E maintenance to an existing RTE withconfiguration changes using IBM-supplied configuration defaults fornew featuresIn this scenario, the SMP/E maintenance applied includes new product features that introduce newconfiguration parameters. Typically, these types of Interim Feature (IF) configuration changes or Fix Pack(FP) configuration changes are delivered as benign, and IBM-supplied configuration defaults aresupplied. The changes are added to the global libraries, but the LPAR specific profiles are not updated.

About this task

You have two options for maintaining runtime environments in this scenario:v You can treat the new Interim Feature (IF) or Fix Pack (FP) as normal maintenance, just as in scenario

SMPE01, and just reload the runtime environment by rerunning the KCIJcLOD load job.This means that the current runtime members in the production user libraries (RKANCMDU,RKANPARU, RKANSAMU, RKD2PAR**, RKD2PRF**, RKD2SAM**) are running with the originalruntime members without added new parameters in RKANPARU(KppENV), or without new membersthat would typically be populated in the RK* user library. Similar processing is done for thePARMGEN work libraries (the WK* equivalent of the product user libraries).

v You can stage the new product configuration parameters for each runtime environment by adding newparameters and members to the runtime libraries. To stage the new parameters, you must submit theKCIJPUP1, $PARSE/PARSESV, and the KCIJcLOD jobs. Optionally, you can submit the KCIJPW2R jobto deploy the updated runtime members from the WK* work libraries to the RK* production userlibraries. If you decide to submit the KCIJcW2R job, you should also submit the KCIJcCPR job to backup the production libraries before copying over the work libraries.You can submit the jobs individually, or you can submit the appropriate maintenance job (KCIJVMNTor KCIJPMNT).

To stage the new configuration parameters using the Workflow interface and the maintenance job,complete the following procedure.

Procedure1. Select option 11 from the Workflow main menu.

The Submit Batch Jobs to Complete PARMGEN Setup menu is displayed:

Chapter 3. SMP/E maintenance scenarios 85


Select option 1 to SUBMIT the composite jobs in WKANSAMU for RTE=DEMO.Alternatively, select other options to SUBMIT each job individually.Press F1=Help for additional considerations when selecting options 4-14.




2. Select option 14 to display the KCIJPMNT job (or KCIJVMNT, if system variables are enabled). Thisjob submits the following additional jobs.v WCONFIG(KCIJPUP1) composite TK*->IK* IEBUPDTE jobv WCONFIG($PARSE) IK*->WK* create runtime members jobv WKANSAMU(KCIJcLOD) composite TK*->RK* runtime library RTE load job (read-only RK*

libraries)v WKANSAMU(KCIJcIVP) configuration verification jobv **WKANSAMU(KCIJcCPR) backup RK* production user runtime libraries jobv **WKANSAMU(KCIJcCPW) backup WK* PARMGEN work libraries job.v **WKANSAMU(KCIJcW2R) WK*->RK* deployment jobThe KCIJVMNT job also submits WKANSAMU(KCIJVUPV) after the $PARSESV job is submitted. Seethe KCIJVMNT and KCIJPMNT jobs for more information.

3. Review the instructions in the job and uncomment the additional jobs you want to run.4. Submit the job.

Tip: Before you submit the KCIJcW2R job, instead of submitting the KCIJcIVP configurationverification job, you can modify the USER%%%U PROC symbols in the PARMGEN generated startedtasks to run from the WK* libraries. This allows a quick test prior to copying the updated WK*runtime members to the production RK* user libraries.

Results

The runtime members and WKANSAMU jobs are updated with the new parameters using theIBM-supplied defaults.


Scenario SMPE03: Apply SMP/E maintenance to an existing RTE withnew configuration changes and override the IBM-suppliedconfiguration defaultsThis scenario is similar to SMPE02 scenario, except that here you want to exploit the new configurationfeatures, all of which are in the LPAR configuration profile. This means that you must take additionalsteps.

About this task

There are 4 main steps involved in this scenario:1. Regenerate and resubmit the KCIJPCFG setup job.2. Edit your WCONFIG(%RTE_NAME%) LPAR configuration profile, and apply necessary overrides.3. Create the runtime members and jobs by running the $PARSE or $PARSESV composite job.4. Submit the batch jobs necessary to complete the set up of the environment.

Tip: Each site has different change-control procedures. Certain sites deploy these types of changes byrenaming the current production RK* libraries to a backup set like RK*.Dyymmdd, then renaming thelatest WK* set to RK*. Sample deployment and backup jobs WKANSAMU(KCIJcCPR) andWKANSAMU(KCIJcW2R) provide helpful samples.

To perform these steps using the PARMGEN Workflow user interface, complete the following procedure.

Procedure1. Regenerate and resubmit the KCIJPCFG setup job.

This step backs up (renames) the existing LPAR profile, runs the KCIJPUP2 job to update interimlibraries and recreate the configuration profiles with any new parameters, and runs KCIJPMC1 tomerge the backup profile with the newly created one.a. On the main Workflow panel, specify the name of the runtime environment to which you want to

apply maintenance.b. From the Workflow main menu, select option 1 to regenerate and resubmit the KCIJPCFG job. The

following message is displayed:

____________________________________________________________________________KCIP@MSG -------------------- PARMGEN MESSAGES -----------------------------Command ===>

While configuring an existing RTE profile, you have asked tonavigate to the KCIJPCFG option to review or make changes to theKCIJPCFG job, which was run with highest condition code RC= 00000on 2012/12/14. In most cases, if you change any KCIJPCFGparameters, you will have to rerun the KCIJPCFG job and certainsubsequent PARMGEN configuration jobs.

Press ENTER to continue with KCIJPCFG changes.

Press F1 for help. Press F3 to abort.

_______________________________________________________________________________

c. Press Enter to continue. The first setup panel (KCIP@PG1) is displayed.d. Press Enter to continue through the following screens until the Exclude Products from PARMGEN

Customization panel is displayed.e. On the panel, place an X next to ALL Exclude all not configured in RTE profile, then specify Y in

the Confirm ==> field and press Enter to continue. The following panel is displayed:


KCIP@PG5 -------- EXCLUDE PRODUCTS FROM PARMGEN CUSTOMIZATIO Row 1 to 23 of 27_____________________________________________________________________________________KCIP@BAK ------- REFRESH THE LPAR RTE USER AND IBM PROFILES ----------------Command ===>

After initial configuration of this PLB1SP22 RTE, if you changedconfiguration values on the panels in the "SET UP PARMGEN WORKENVIRONMENT FOR AN RTE (n of 3)" KCIJPCFG navigation, or you changedthe configured product mix and versions installed/configured, then youmust regenerate and resubmit the KCIJPCFG job. You must also refreshthe PARMGEN profiles (global or LPAR) by:1. Renaming the current WCONFIG(PLB1SP22) to a backup (manually).2. Resubmitting the WCONFIG(KCIJPUP1) job.3. Recustomizing and resubmitting the WCONFIG(KCIJPMC1) merge job.

You have the option to automate these refresh steps by specifying abackup member name below. This triggers PARMGEN to generate theKCIJPCFG job with a new KCIJPPRF profile refresh job. The KCIJPPRF jobcustomizes and resubmits the KCIJPUP1 and KCIJPMC1 jobs. When you submitthe KCIJPCFG job, it job tailors and submits the KCIJPPRF job.

PLB1SP22 Backup member name ===> ________ (Required for KCIJPPRF)Note: Press F1=Help for important information about when to enter a

backup member name and what other jobs might need to be rerun._______________________________________________________________________________

f. Enter a name for the profile backup member. The modified KCIJPCFG job is displayed.g. Submit the job. The KCIJPCFG job backs up the LPAR profile, updates the libraries and creates

new profiles, and merges the values from the backed up profile into the new profile.2. Edit the WCONFIG(%RTE_NAME%) LPAR configuration profile to customize it as required.

For example, customize any new parameters brought in by the IF or Fix Pack.

Tip: In a scenario where you have also added a new product to configure to this runtimeenvironment, ensure that you also customize the new product's Kpp_* PARMGEN profile parametersadded into the refreshed LPAR configuration profile.

3. Create the runtime members by running the $PARSE or $PARSESV jobs.4. Submit the batch jobs necessary to complete the set up of the environment:

v WKANSAMU(KCIJcLOD) composite TK*→RK* runtime library load job (see maintenance scenario 2for details)

v (Optional but best practice) WKANSAMU(KCIJcIVP) configuration verification job.Alternatively, you can modify the USER%%%U PROC symbols in the PARMGEN-created startedtasks to run from the WK* libraries for a quick test before copying the updated WK* runtimemembers to the production RK* user libraries.

v (Optional) WKANSAMU(KCIJcW2R) sample job to deploy the updated runtime members from theWK* libraries to the RK* production user libraries. If you run KCIJcW2R, you should run KCIJcCPRto back up the RK* production libraries.

Results

The maintenance is applied, and any customizations you made are in effect.

Scenario SMPE04: Upgrade an existing runtime environment with noconfiguration changesIn this scenario you apply maintenance that contains upgraded FMIDs but does not contain features thatrequire configuration changes.


About this task

If are upgrading it to V6.3.0 and you have a V6.2.3 z/OS hub monitoring server with SDA enabled andyou elected to retain the previous behavior (no granular controls), follow the steps in Scenario SMPE06. Ifyou are upgrading a monitoring server at a version prior to V6.2.3 to V6.3.0, you must also followScenario SMPE06. In the first case, the load job needs to be refreshed to add the REPROKFA step to theload job. In the second scenario, new VSAM libraries need to be allocated, so the KCIJcALO andKCIJcLOD jobs need to be refreshed.

Otherwise, use the following procedure.

Procedure

Run the KCIJcLOD job using one of the following methods (where c=V if system variables are enabled;c=P if variables are not enabled):v Submit the KCIJcLOD job in the %RTE_PLIB_HILEV%.%RTE_NAME%.WKANSAMU library.v Submit the KCIJcLOD job from the PARMGEN Workflow interface:

1. Select option 11 from the Workflow main menu to display the Submit Batch Jobs to CompletePARMGEN Setup menu:


Select option 1 to SUBMIT the composite jobs in WKANSAMU for RTE=&rte_name.Alternatively, select other options to SUBMIT each job individually.Press F1=Help for additional considerations when selecting options 4-14.




2. Select option 3.The KCIJPLOD job (or KCIJVLOD, if system variables are enabled in the runtime environment) isdisplayed.

3. Review the notes and submit the job.

The job copies members of the products' SMP/E target libraries to the read-only RK* runtime libraries.The runtime libraries are loaded with IEBCOPY in a two-step process:1. All members are copied from the SMP/E target libraries to the runtime libraries.2. The runtime libraries are compressed.

If any members in the IEBCOPY steps are not found in the source libraries, a return code of 4 (which isacceptable) is generated.See the comments in the KCIJcLOD JCL for further information.


Scenario SMPE05: Upgrade an existing runtime environment withconfiguration changes using IBM-supplied configuration defaultsThis scenario assumes that the upgraded FMIDs applied included new product features that introduceconfiguration changes (such as new product configuration parameters in RKANPARU(KppENV), or newRK* runtime members). Typically, these types of configuration changes caused by new product versionsare delivered as benign, and IBM-supplied configuration defaults are supplied.

About this task

You have two options for upgrading runtime environments in this scenario:1. You can treat the new FMID's configuration enhancements as normal maintenance, just as in scenario

SMPE01, and just reload the runtime environment by rerunning KCIJcLOD load job.This means that the current runtime members in the production user libraries (RKANCMDU,RKANPARU, RKANSAMU, RKD2PAR**, RKD2PRF**, RKD2SAM**) are running with the originalruntime members without the added new parameters or without the new member that wouldtypically be populated in the RK* user library. Similar processing is done for the PARMGEN worklibraries (the WK* equivalent of the product user libraries).

2. You can start staging the new components or product configuration parameters for each runtimeenvironment. To stage the new parameters, you must resubmit the following jobs:v the KCIJPCFG job to refresh the work environment, update interim libraries, recreate the

configuration profiles with any new parameters, and merge the backup profile with the newlycreated one.

v the $PARSE or $PARSESV job to recreate the runtime members and jobsv the following batch jobs:

– KCIJpLOD to copy the target libraries to the RK* runtime libraries– KCIJcSEC (if upgrade introduces changes in security) to create security-related members (load

modules, encryption key, and other elements) based on the product security requirements– KCIJcUSP and KCIJcUSS (if upgrade introduces changes in UNIX System Services requirements)– KCIJcSYS (if upgrade introduces new started tasks or nodes)– KCIJcCPR to backup RK* production user runtime libraries job– KCIJcCPW) to backup WK* PARMGEN work libraries job– KCIJcW2R) to copy the WK* work libraries to the RK* production libraries

Tip: Each site has different change-control procedures. Certain sites deploy these types of changes byrenaming the current production RK* libraries to a backup set like RK*.Dyymmdd, then renaming thelatest WK* set to RK*. Sample deployment and backup jobs WKANSAMU(KCIJcCPY) andWKANSAMU(KCIJcW2R) provide helpful samples.

To stage the new configuration parameters, complete the following procedure.



apply maintenance.b. From the Workflow main menu, select option 1 to regenerate and resubmit the KCIJPCFG job.

The following message is displayed:






_______________________________________________________________________________

c. Press Enter to continue. The first setup panel (KCIP@PG1) is displayed.d. Press Enter to continue through the following screens. On the Exclude Products from PARMGEN

Customization panel, specify Y in the Confirm ==> field to continue. The following panel isdisplayed:






e. Enter a name for the profile backup member. The modified KCIJPCFG job is displayed.f. Submit the job. The KCIJPCFG job backs up the profile, updates the libraries and creates the

profiles, and merges the values from the backed up profile into the new one.2. From the Workflow main menu, select option 10 and submit the $PARSE or $PARSESV job, as

appropriate.3. Submit the WKANSAMU batch jobs.

a. From the Workflow main menu, select option 11 to display the Submit Batch Jobs to CompletePARMGEN Setup panel.

b. Select 1 to display the KCIJcSUB composite job.c. Edit the job to submit the following jobs, as appropriate:

v KCIJpLOD to copy the target libraries to the RK* runtime librariesv KCIJcSEC (if upgrade introduces changes in security) to create security-related members (load

modules, encryption key, and other elements) based on the product security requirementsv KCIJcUSP and KCIJcUSS (if upgrade introduces changes in UNIX System Services requirements)


v KCIJcSYS (if upgrade introduces new started tasks or nodes)v KCIJcCPR to backup RK* production user runtime libraries jobv KCIJcCPW) to backup WK* PARMGEN work libraries jobv KCIJcW2R) to copy the WK* work libraries to the RK* production libraries

If you decide to uncomment the KCIJPW2R job, you should also uncomment the KCIJPCPR job toback up the production libraries before copying over the work libraries. Alternatively, you canmodify the PARMGEN-created STC's new USER%%%U PROC symbols to run from the WK*libraries for a quick test prior to copying the updated WK* runtime members to the productionRK* user libraries.

Results

The new product features are implemented and the defaults are in effect.

Scenario SMPE06: Upgrade an existing runtime environment andoverride defaultsThis scenario is similar to scenario SMPE05, except that in this scenario you want to exploit the newconfiguration features and change the IBM-supplied defaults, so you edit the LPAR configuration profile.

About this task

There are 4 main steps involved in this scenario:1. Regenerate and resubmit the KCIJPCFG setup job to refresh the work environment, update interim

libraries, recreate the configuration profiles with any new parameters, and merge the backup profilewith the newly created one..

2. Edit your WCONFIG(%RTE_NAME%) LPAR configuration profile, and apply necessary overrides.3. Create the runtime members and jobs by running the $PARSE or $PARSESV composite job.4. Submit the batch jobs necessary to complete the set up of the environment.

Tip: Each site has different change-control procedures. Certain sites deploy these types of changes byrenaming the current production RK* libraries to a backup set like RK*.Dyymmdd, then renaming thelatest WK* set to RK*. Sample deployment and backup jobs WKANSAMU(KCIJcCPR) andWKANSAMU(KCIJcW2R) provide helpful samples.

To perform these steps using the PARMGEN Workflow user interface, complete the following procedure.



apply maintenance.b. From the Workflow main menu, select option 1 to regenerate and resubmit the KCIJPCFG job. The

following message is displayed:






_______________________________________________________________________________

c. Press Enter to continue. The first setup panel (KCIP@PG1) is displayed.d. Press Enter to continue through the following screens until the Exclude Products from PARMGEN

Customization panel is displayed.e. On the panel, place an X next to ALL Exclude all not configured in RTE profile, then specify Y in

the Confirm ==> field and press Enter to continue. The following panel is displayed:





backup member name and what other jobs might need to be rerun.

_______________________________________________________________________________

f. Enter a name for the profile backup member. The modified KCIJPCFG job is displayed.g. Submit the job. The KCIJPCFG job backs up the LPAR profile, updates the libraries and creates

new profiles, and merges the values from the backed up profile into the new profile.2. Edit the WCONFIG(%RTE_NAME%) LPAR configuration profile to customize it as required.

For example, customize any new parameters brought in by the upgrade.

Tip: In a scenario where you have also added a new product to configure to this runtimeenvironment, ensure that you also customize any new Kpp_* PARMGEN profile parameters for theproduct added into the refreshed LPAR configuration profile.

3. Create the runtime members by running the $PARSE or $PARSESV jobs.4. From the Workflow main menu, select option 10 and submit the $PARSE or $PARSESV job, as

appropriate.


5. Submit the WKANSAMU batch jobs.a. From the Workflow main menu, select option 11 to display the Submit Batch Jobs to Complete

PARMGEN Setup panel.b. Select 1 to display the KCIJcSUB composite job.c. Edit the job to submit the following jobs, as appropriate:

v KCIJpLOD to copy the target libraries to the RK* runtime librariesv KCIJcSEC (if upgrade introduces changes in security) to create security-related members (load

modules, encryption key, and other elements) based on the product security requirementsv KCIJcUSP and KCIJcUSS (if upgrade introduces changes in UNIX System Services requirements)v KCIJcSYS (if upgrade introduces new started tasks or nodes)v KCIJcCPR to backup RK* production user runtime libraries jobv KCIJcCPW) to backup WK* PARMGEN work libraries jobv KCIJcW2R) to copy the WK* work libraries to the RK* production libraries

If you decide to uncomment the KCIJPW2R job, you should also uncomment the KCIJPCPR job toback up the production libraries before copying over the work libraries. Alternatively, you canmodify the PARMGEN-created STC's new USER%%%U PROC symbols to run from the WK*libraries for a quick test prior to copying the updated WK* runtime members to the productionRK* user libraries.

Results

The runtime environment is upgraded and any values you customized are in effect.

Scenario SMPE07: Stage an upgrade using a cloned environmentIn this scenario, you create runtime environments that contain the same product set and configurationvalues as the old environments but which contain upgraded versions of products and components. Youinstall new product versions in a new set of SMP/E target libraries, point the runtime environment at thenew libraries, clone the work and production libraries from an old environment, and then merge itsconfiguration values into a new runtime environment with the same name that points to the newinstallation libraries. In the process, you upgrade any products and components installed in the oldenvironments.

By cloning environments and installing new versions into the cloned environments, you can continue toapply maintenance to and reconfigure runtime environments that contain previous versions of productsand components.

Note: This scenario assumes a PARMGEN to PARMGEN upgrade. For instructions for cloning aConfiguration Tool environment, converting it to PARMGEN, and upgrading it, see “Scenario PGN05:Convert an existing Configuration Tool environment to PARMGEN and upgrade it to the current release”on page 66.

About this task

This task involves the following steps:1. Install the products into a new set of SMP/E target libraries.2. Clone the GBL_USER_JCL global library.3. Set up the new PARMGEN work environment.4. Clone the WCONFIG members from the model runtime environment.5. Update the interim libraries and create the configuration profiles for the new environment.6. Merge the values from the model LPAR configuration profiles.


7. (Conditional) Customize the profile parameter values.8. Create the runtime members and jobs.9. Submit the jobs to create the runtime environment.

Procedure1. Install the products into a new set of SMP/E target libraries using the Install Job Generator

(JOBGEN).a. Launch the installation and configuration software in an existing installation:

EX ’%HILEV%.%MIDLEV%.TKANCUS’

b. On the Welcome page, select option 4 (SMP/E-install z/OS products with Install Job Generator).c. Supply the values as prompted.d. Submit the file-tailored KCIJG* SMP/E jobs to complete the installation.e. Exit JOBGEN and then exit the software configuration software.

2. Clone the GBL_USER_JCL global library for runtime environments (the library specified by theCONFIG DD statement in started tasks) to the new high-level qualifier.

3. Set up the new work environment:a. Invoke the configuration software from TKANCUS of the new environment and select the

PARMGEN Workflow interface (option 5).b. On the main PARMGEN Workflow panel, set the GBL_USER_JCL and RTE_PLIB_HILEV fields to

the new values for the cloned GBL_USER_JCL. For RTE_NAME, specify the name of the runtimeenvironment you want to clone and upgrade.For RTE_PLIB_HILEV, use a different value for the high-level qualifier, not the one in production(for example, change OMEG623.&userid to OMEG630.&userid), so the new runtime environmentuses a different set of PARMGEN IK*, WCONFIG, and WK* work libraries.

c. Select option 1 (Set up PARMGEN work environment for an RTE).v On the first set-up panel, provide the LPAR profile library and member name for the runtime

environment you are cloning (for example, OMEG623.&userid.PLBLPAR1.WCONFIG(PLBLPAR1).

v On the second set-up panel, specify the new GBL_TARGET_HILEV.v On the third set-up panel, make no changes. Any changes you make here will be overwritten

when you clone the WCONFIG members from the runtime environment whose values you arecloning. If you need to make changes, make them to the corresponding parameters in theconfiguration profiles.

v On the fifth set-up panel (Exclude Products From PARMGEN Customization), place an X besidethe ALL entry to configure only the same product sets as the model environment contains (allproducts shown with an asterisk). Then specify Y in the Confirm ==> field and press Enter. Thelatest versions of the products installed will be configured into the new runtime environment.

d. Review and submit the KCIJPCFG job, then return to the main Workflow panel.4. Clone the WCONFIG members for the new runtime environment from the model runtime

environment's WCONFIG library:a. From the Workflow main menu, select option 3.

The WCONFIG(KCIJPCCF) job is presented.b. Review the job to determine if you need to further modify the library concatenated in the

OLDWCNFG DDNAME.By default, this DDNAME already points to the WCONFIG library that you specified in the RTEprofile library field of the first work environment set-up panel. If necessary, modify the job topoint to an existing WCONFIG library that contains the customized members you want clonedover to the WCONFIG library for the new runtime environment.

c. Submit the job and return to the main Workflow panel.


5. Update the interim libraries and create profiles:a. Select option 4. The WCONFIG(KCIJPUP1) job is displayed.b. Review then submit the job.

The work libraries are updated with the configuration values you specified and the configurationprofiles for the runtime environment are created.

6. Merge the values from the LPAR configuration profile of the model runtime environment into theprofile for the new runtime environment.a. From the Workflow main menu, select option 6 (KCIJPMC2 Merge profile from model RTE). The

WCONFIG(KCIJPMC2) member is presented.b. Review the job and make any required changes. By default, the OLDMEM(&value) parameter is

already set to the runtime environment you specified in the first setup panel (in this example,OMEG623.&sysuid.PLB1SP22.WCONFIG(PLB1SP22).

c. Submit the job to merge the profile values.7. Customize the PARMGEN configuration profiles.

a. From the Workflow main menu, select option 8. The Customize PARMGEN Configuration ProfileMembers panel is presented. Customization of the LPAR profile is required. Customization of the$GBL$USR global profile is optional, but you might want to review the profile to determine ifthere are changes you want to make.

b. Select option 1 and change all instances of *HILEV* to the high-level qualifier for the newenvironment. If the new FMIDs contain new components or configuration values you want tocustomize, you can also make those changes.

c. Press F3 to close and save the LPAR configuration profile and return to the Customize PARMGENConfiguration Profile Members panel.

d. Select 2 to review the $GBL.$USR profile and make any appropriate changes.e. Press F3 to exit the $GBL.$USR profile, and F3 again to return to the main Workflow panel.

8. Create the WK* runtime members and the WKANSAMU jobs:a. Select option 10 from the Workflow main menu. The Submit $PARSE Batch Jobs to Complete

PARMGEN Setup panel is displayed.b. Select option 1 to submit the generated $PARSE composite job. The $PARSE member is presented.c. Review the member for any jobs that need to be submitted manually, then submit the job. Return

to the main Workflow panel.9. Submit the batch jobs to complete the setup of the runtime environment:

a. Select option 11 from the Workflow main menu. The Submit Batch Jobs to Complete PARMGENSetup (KCIP@SUB) panel is displayed.

b. Select option 1 if you want to submit the KCIJPSUB master SUBMIT job, or select the otheroptions to submit each job individually. If you select option 1, review the KCIJPSUB job first, andedit the job according to which of the conditional jobs need be submitted automatically and whichneed to be submitted manually (for example, for reasons of authorization).

c. Submit the job.

Results

You have cloned and upgraded the selected runtime environment.

What to do next

Complete any configuration steps required outside the software. Then repeat steps 2 - 9 for every runtimeenvironment you want to upgrade.


Important: The cloned environment inherits configuration values from the original runtime environment,including started task names. However, if the runtime environments use the same PROCLIB, there can beonly one set of STCs. The simplest way to deal with this is to create a temporary PROCLIB on the systemor systems you upgrade that contain the new procedures. Then, once every LPAR is upgraded, copy theprocedures from the temporary PROCLIB to the normal PROCLIB. You might want to schedule a changecontrol window when you can switch libraries.



Chapter 4. Runtime environment maintenance scenarios

After you have set up your runtime environments using PARMGEN, you may occasionally need tomodify them. For example, you might need to add, reconfigure, or delete products. You might need tochange parameter values to tune monitoring performance.

This section contains step-by-step scenarios for maintain your runtime environments using thePARMGEN method.

See the OMEGAMON XE and Tivoli Management Services on z/OS: Upgrade Guide for upgrade scenarios.

Scenario RTE01: Add a new product into an existing PARMGENruntime environmentIn this scenario, you add a new product to an existing runtime environment. The product is SMP/Einstalled, but not yet configured in the runtime environment.

About this task

The key to adding a new product to an existing runtime environment is the specifications on the ExcludeProducts From PARMGEN Customization (KCIP@PG5) panel.



add the product.b. From the Workflow main menu, select option 1 to regenerate and resubmit the KCIJPCFG job. The

following message is displayed, notifying you that you will need to resubmit the modifiedKCIJPCFG job after you make changes:





_______________________________________________________________________________

c. Press Enter to continue. The first setup panel (KCIP@PG1) is displayed.d. Press Enter until the Exclude Products From PARMGEN Customization (KCIP@PG5) panel is

displayed.


Any products already configured into the environment are flagged with an asterisk (*). Anyproducts not flagged by an asterisk (*) will be configured into the runtime environment unless youexclude them.

e. Place an X next to any new product that you do not want to include in the runtime environment.In the following example, a monitoring server, the OMEGAMON enhanced 3270 user interface,and all of the OMEGAMON XE products except OMEGAMON XE for Storage are alreadyconfigured in the runtime environment. To add OMEGAMON XE for Storage, an X is placed nextto every product without an asterisk except for OMEGAMON XE for Storage.


Select (X) products to EXCLUDE from PARMGEN customization in RTE=LPAR1.



_ ALL Exclude all not configured in RTE profile_ KAH* IBM Tivoli System Automation for z/OS V330_ KC5* IBM Tivoli OMEGAMON XE for CICS on z/OS V510X KDO IBM Tivoli Decision Support for z/OS V181_ KDS* Tivoli Enterprise Monitoring Server V630X KD4 IBM Tivoli Composite Application Manager for SOA V711_ KD5* IBM Tivoli OMEGAMON XE for DB2 PE/PM V511_ KGW* IBM Tivoli OMEGAMON XE for CICS TG on z/OS V510X KHL IBM OMEGAMON z/OS Management Console V410_ KI5* IBM Tivoli OMEGAMON XE for IMS on z/OS V510_ KMC* IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Configuration V710_ KMQ* IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Monitoring V710_ KM5* IBM Tivoli OMEGAMON XE on z/OS V510X KNA IBM Tivoli NetView for z/OS Agent V610_ KN3* IBM Tivoli OMEGAMON XE for Mainframe Networks V510_ KOB* Tivoli OMEGAMON Enhanced 3270 User Interface V700_ KQI* IBM Tivoli OMEGAMON XE for Messaging - WebSphere Message Broker V710X KRG IBM Tivoli Advanced Audit for DFSMShsm V230X KRH IBM Tivoli Advanced Reporting and Management for DFSMShsm V240X KRJ IBM Tivoli Advanced Allocation Management for z/OS V310X KRK IBM Tivoli Automated Tape Allocation Manager for z/OS V320X KRN IBM Tivoli Advanced Catalog Management for z/OS V240X KRV IBM Tivoli Advanced Backup and Recovery for z/OS V230X KRW IBM Tivoli Tape Optimizer for z/OS V220_ KS3 IBM Tivoli OMEGAMON XE for Storage on z/OS V510_ KWO* IBM Tivoli OMEGAMON DE on z/OS - OMEGAVIEW and OMEGAVIEW II V510X KYN ITCAM for Application Diagnostics on z/OS V710Enter=Next F1=Help F3=Back F7=Up F8=Down

f. Specify Y in the Confirm ==> field then press Enter to continue. The following panel is displayed:







g. Enter a name for the profile backup member. The modified KCIJPCFG job is displayed.h. Submit the job. The KCIJPCFG job submits the KCIJPPRF job, which does the equivalent of the

KCIJPUP1 and KCIJPMC1 jobs.i. Return to the main Workflow panel.

2. If necessary, edit the configuration profiles. See the Planning and Configuration Guide and ParameterReference for the product for information on new parameters. Note that the new product will inheritany global runtime environment parameters specified in the Set up PARMGEN Work Environment foran RTE (3 OF 3) panel (KCIP@PG3), such as started task prefixes.

3. Recreate the runtime environment members and jobs.a. Select option 10.



High-Level Qualifier (HLQ) of work libraries (IK*,WCONFIG,WK*)RTE_NAME: LPAR1 (Type ? for a list of configured RTEs)



1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/172. $JOBINDX Review PARMGEN job index. Viewed 2012/08/163. KCIJPCCF Clone customized WCONFIG members. (COND) RC= 00000 2012/08/174. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/175. KCIJPMC1 Merge profile from backup PLB3SP13 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND) RC= 00000 2012/08/177. KCIJPCNV Convert an ICAT RTE Batch member. (COND) RC= 00000 2012/08/178. LPAR1 Customize PARMGEN configuration profiles. Edited 2012/08/179> KCIJPVAL Validate PARMGEN profile parameter values. Submitted 2012/08/1710. $PARSESV Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The $PARSE/$PARSESV: Create the RTE Members and Jobs (KCIP@PRS) panel is displayed.

Chapter 4. Runtime environment maintenance scenarios 101

b. Select option 1 to submit the generated $PARSE or $PARSESV composite job.


Select option 1 to SUBMIT the full $PARSESV job in WCONFIG for RTE=LPAR1.Alternatively, select other options to SUBMIT $PARSE jobs individually.Press F1=Help for additional considerations when selecting options 2-5.






The $PARSE or $PARSESV member is presented.c. Review the member for any jobs that need to be submitted manually, then submit the job. Return


a. On the Workflow main panel, select option 11 (Submit batch jobs to complete PARMGEN setup).






1. KCIJPCFG Set up PARMGEN work environment for an RTE.2. $JOBINDX Review PARMGEN job index.3. KCIJPCCF Clone customized WCONFIG members. (COND)4. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup PLB1SP22 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. LPAR1 Convert an ICAT RTE Batch member. (COND)8. PLB1SP22 Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10> $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The SUBMIT Submit batch jobs to complete PARMGEN setup (KCIP@SUB ) is displayed.b. Select option 1 to submit the KCIJcSUB master submit job, or select the other options to submit

each job separately.c. If you select option 1, first review the KCIJPSUB job, and edit the job according to which of the

conditional jobs need to be submitted automatically.a. Submit the master SUBMIT job, and check for good condition codes.



b. Review the resulting output:v $IVPRPT report, which is stored in the WCONFIG libraryv WSUPERC SYSTSPRT report, which is stored in the WSUPERC sequential library

c. Correct any errors, and rerun any jobs that did not complete successfully.

What to do next

See the Planning and Configuration Guide for the new product to complete any configuration stepsrequired outside the configuration software.

Scenario RTE02: Upgrade a single OMEGAMON product in an existingruntime environmentYou have a runtime environment that has already been upgraded to the latest versions of the monitoringserver and monitoring agents. Now there is a new release of one of the products in the environment andyou want to upgrade that product.

About this task

The site has already upgraded its current runtime environments to:v Tivoli Management Services V6.3.0, including a z/OS-based Tivoli Enterprise Monitoring Server at the

V6.3.0 levelv OMEGAMON XE on z/OS V5.1.0v OMEGAMON XE for CICS on z/OS V5.1.0v OMEGAMON enhanced 3270 user interfacev OMEGAMON XE for DB2 V5.1.0

Now the site wants to upgrade these environments to include OMEGAMON XE for DB2 V5.1.1. The keyto upgrading a product's version in an existing runtime environment is the specifications on the ExcludeProducts From PARMGEN Customization (KCIP@PG5) panel.

Procedure1. Regenerate and resubmit the KCIJPCFG job.


add the product.b. From the Workflow main menu, select option 1 to regenerate and resubmit the KCIJPCFG job. The

following message is displayed, notifying you that you will need to resubmit the modifiedKCIJPCFG job after you make changes:






_______________________________________________________________________________


displayed.Any products already configured into the environment are flagged with an asterisk (*). Anyproducts not flagged by an asterisk (*) will be configured into the runtime environment unless youexclude them.

e. Place an X next to any new product that you do not want to include in the runtime environment.In the following example, the products already configured in the environment are indicated withasterisks. Because PARMGEN is pointing to the SMP/E target libraries where the OMEGAMONXE for DB2 V5.1.1 product has been installed, the version shows up as “V511”. As indicated by theasterisk (*) next to _KD5, this product was previously configured in this runtime environment, butat the V5.1.0 (GA-1) release.





_ ALL Exclude all not configured in RTE profile

X KAH IBM Tivoli System Automation for z/OS V330_ KC5* IBM Tivoli OMEGAMON XE for CICS on z/OS V510X KDO IBM Tivoli Decision Support for z/OS V181_ KDS* Tivoli Enterprise Monitoring Server V630_ KD4* IBM Tivoli Composite Application Manager for SOA V711_ KD5* IBM Tivoli OMEGAMON XE for DB2 PE/PM V511_ KGW* IBM Tivoli OMEGAMON XE for CICS TG on z/OS V510X KHL IBM OMEGAMON z/OS Management Console V410X KI5 IBM Tivoli OMEGAMON XE for IMS on z/OS V510X KMC IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Configuration V701X KMQ IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Monitoring V701_ KM5* IBM Tivoli OMEGAMON XE on z/OS V510X KNA IBM Tivoli NetView for z/OS Agent V610X KN3 IBM Tivoli OMEGAMON XE for Mainframe Networks V510_ KOB* Tivoli OMEGAMON Enhanced 3270 User Interface V700X KQI IBM Tivoli OMEGAMON XE for Messaging - WebSphere Message Broker V701X KRG IBM Tivoli Advanced Audit for DFSMShsm V230X KRH IBM Tivoli Advanced Reporting and Management for DFSMShsm V240X KRJ IBM Tivoli Advanced Allocation Management for z/OS V310X KS3 IBM Tivoli OMEGAMON XE for Storage on z/OS V510X KWO IBM Tivoli OMEGAMON DE on z/OS - OMEGAVIEW and OMEGAVIEW II V510X KYN ITCAM for Application Diagnostics on z/OS V710Enter=Next F1=Help F3=Back F7=Up F8=Down









KCIJPUP1 and KCIJPMC1 jobs.2. The next steps depend on whether or not you have configuration changes to make:

v If you want to upgrade the SMP/E environment to the new FMID but make no configurationchanges, follow the steps for maintenance task SMPE04.

v If you want to upgrade the SMP/E environment to the new FMID with new configuration changesbut use or run with IBM-supplied configuration defaults, follow the steps for maintenance taskSMPE05.

v If you want to upgrade the SMP/E environment to the new FMID versions and either exploit newconfiguration changes or override the IBM-supplied configuration defaults, follow the steps formaintenance task SMPE06.

What to do next

Complete any configuration steps required outside the configuration software.

Scenario RTE03: Change PARMGEN parametersAfter the initial configuration, you might need to change, add, or delete parameter values in the LPARconfiguration profile. If you change parameters, you must resubmit the $PARSE or $PARSESV job toregenerate the runtime members and jobs in the WK* work libraries. Then you run theWKANSAMU(KCIJPW2R) job to deploy runtime members from the work libraries to the runtimeproduction user libraries. If system variables are enabled in the runtime environment, you must also runKCIJPUPV job.

For example, you might not want to enable security for the Tivoli Enterprise Portal or the enhanced 3270user interface logon until you have verified that all components are configured and communicatingcorrectly. After you have verified that you can successfully view data in the Tivoli Enterprise Portal client,you can to go back and set KDS_TEMS_SECURITY_KDS_VALIDATE to YES to enable authentication ofTivoli Enterprise Portal user IDs and passwords. Or you can enable security for the enhanced 3270 userinterface by providing a security authorization facility (SAF) resource class using theRTE_SECURITY_CLASS parameter.


About this task

This task involves three main steps:1. Edit the configuration profile.2. Recreate the runtime environment and jobs by submitting the appropriate $PARSE/$PARSESV job.3. Copy the runtime members from the work libraries to the production libraries by using the

KCIJPW2R job.

If system variables are enabled in the runtime environment, you must also run the KCIJVUPV job topopulate variable-named members application-specific KppJPUPB composite IEBUPDTE members in theWK* work output libraries, before you run the KCIJPW2R job.

The WCONFIG($PARSE) or $PARSESV composite job processes all IK*→WK* user libraries (or the$PARSESV job if the runtime environment is enabled for system variable. If you need to regenerate onlythe parameters in a single library, you can also submit the library-specific $PARSE%% jobs (where %% =CM for CMDU, SM for SAMU, PR for PARU) in WCONFIG. Within each library, you can specify aspecific member or set of members.

For example, if you are adding a new parameter to the WCONFIG(KAG$PENV) global agent overrideimbed and the WCONFIG(KDS$PENV) monitoring server override imbed, you only need to update theWKANPARU(KppENV) members. Similarly, if you make a change to theKDS_TEMS_TCP_KDEB_INTERFACELIST and the 25 Kpp_AGT_TCP_KDEB_INTERFACELISTKDEB_INTERFACELIST parameters that need to be implemented globally across all products, so only theWKANPARU(*ENV) members need to be reprocessed by $PARSEPR.

To implement this example scenario, edit the SELECT MEMBER=(*) statement in the USER SECTION:CONFIG/SELECT MEMBER section of the $PARSEPR job to SELECT MEMBER=(*ENV):

EDIT IBM.&userid.LPAR1.WCONFIG($PARSEPR)Command ===>000110 * ----------- BEGIN - USER SECTION: CONFIG/SELECT MEMBER ---------- *000111 * *******************************************************************000112 * USER SECTION: CONFIG/SELECT MEMBER *000113 * *******************************************************************.000121 CONFIG MEMBER=(WCONFIG:$GBL$IBM)000122 * 4. $CFG$IBM IBM-supplied PARMGEN CONFIG profile (RTE-specific)000123 CONFIG MEMBER=(WCONFIG:$CFG$IBM)000124 * 5. $GBL$USR Customer-overridable PARMGEN CONFIG profile (SMP-related000125 * and other global parameters)000126 * Note: (OPTIONAL) Customize WCONFIG:$GBL$USR accordingly. It is000127 * ideal for copying to other WCONFIG RTEs if these global system000128 * libraries are typically the same across LPARs.000129 CONFIG MEMBER=(WCONFIG:$GBL$USR)000130 * 6. TESTSYSG Customer-overridable PARMGEN CONFIG profile000131 * (RTE-specific applicable to this LPAR)000132 CONFIG MEMBER=(WCONFIG:LPAR1)000133 SELECT MEMBER=(*ENV)000134 * ----------- END - USER SECTION: CONFIG/SELECT MEMBER ---------- *

This change tells the $PARSEPR job to recreate only the *ENV members.

You can also code SELECT MEMBER=(*ENV,K??SYSIN) if you want to regenerate only the KppENV members,and all members matching the K??SYSIN wildcard. These are just a few examples how flexible the SELECTMEMBER= parameter is.

Note that the library-specific $PARSE%% jobs regenerate the runtime members in the PARMGEN worklibraries (such as WKANPARU and WKANCMDU, etc.) because PARMGEN supports a stageddeployment and does not update the running production user libraries and execution libraries (such asRKANPARU and RKANCMDU). You must run the WKANSAMU(KCIJPW2R) job to deploy runtime


members from the WK* libraries to the RK* production user libraries. However, if you would like the$PARSE* jobs to update the production user libraries directly, without having to run KCIJPW2R, updatethe SYSUT2 DD to point to RK* instead of the WK* PARMGEN work libraries, as shown in the example$PARSEPR job:

EDIT IBM.&userid.LPAR1.WCONFIG($PARSEPR)Command ===>000091 //* *******************************************************************000092 //* WKANPARU Step: IKANPARU-->WKANPARU000093 //* Process the PARMGEN members from IKANPARU to WKANPARU based on $CFG*000094 //* CONFIG and/or converted PARMGEN RTE Batch deck profile settings.000095 //* *******************************************************************000096 //WKANPARU EXEC PGM=KCIPARSE,000097 // PARM=’MV=32000,MAXL=32000,ML=500,MI=255,MS=20000,LV=Y,LG=10’000098 //STEPLIB DD DISP=SHR,000099 // DSN=IBM.TARGET.TKANMOD000100 //INPUT1 DD DISP=SHR,000101 // DSN=IBM.ITM62351.LPAR1.IKANPARU000102 //INPUT2 DD DISP=SHR,000103 // DSN=IBM.ITM62351.LPAR1.WKANPARU000104 //WCONFIG DD DISP=SHR,000105 // DSN=IBM.ITM62351.LPAR1.WCONFIG000106 //SYSUT2 DD DISP=SHR,000107 // DSN=IBM.ITM62351.LPAR1.WKANPARU <<<-- change to RKANPARU

To test the parameter changes quickly before moving the members from WK* to RK* productionuser-libraries, modify the new USER%%%U PROC symbols in the PARMGEN-created started tasks to runfrom the WK* libraries.

Complete the following procedure to change configuration parameters using the PARMGEN Workflowinterface.

Procedure1. Edit the configuration profile.

a. On the main Workflow panel, specify the name of the runtime environment you want to modify.b. From the main menu, select option 8. The Customize PARMGEN Configuration Profile Members

panel is displayed.c. Select option 1 to edit the LPAR configuration profile. The profile member is displayed.d. Complete the necessary changes. For example, locate KDS_TEMS_SECURITY_KDS_VALIDATE

and change N to Y. Edit the values for all required related parameters, such asRTE_SECURITY_USER_LOGON to specify what security system is used to validate TivoliEnterprise Portal users.

e. Save the changes and return to the main Workflow panel.2. Recreate the runtime environment members and jobs.

a. From the main menu, select option 10. The $PARSE/$PARSESV: Create the RTE Members and Jobspanel is displayed.

b. Select the $PARSE (or $PARSESV) composite job or the appropriate $PARSE%% library specificjob. The JCL is presented.

c. Review the job and make any required adjustments, then submit it and return to the mainWorkflow panel.

3. Edit and submit the batch jobs to complete the setup.a. Select option 11 from the main menu. The Submit Batch Job to Complete PARMGEN Setup panel

is displayedb. If system variables are enabled, select option 5 and submit the KCIJVUPV job.c. (Optional, but best practice) Select option 12 and submit the KCIJcCPR job to backup the

production libraries.


d. Select option 13 and submit the KCIJcW2R job to copy the work libraries to the productionlibraries.

Results

The configuration profile for the runtime environment is updated.

Scenario RTE04: Convert a hub monitoring server to a remoteIn this scenario, you convert a static z/OS hub Tivoli Enterprise Monitoring Server to a z/OS remotemonitoring server and configure the remote to report to a hub.

Before you begin

Launch the PARMGEN Workflow interface as described in “Start the Workflow user interface” on page135.

About this task

Procedure1. On the main PARMGEN Workflow menu (KCIP@PG0), change the RTE_NAME to the name of the

runtime environment whose hub you want to convert. Then select option 8.



High-Level Qualifier (HLQ) of work libraries (IK*,WCONFIG,WK*)RTE_NAME: &rte_name___ (Type ? for a list of configured RTEs)



1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/162. $JOBINDX Review PARMGEN job index. Viewed 2012/08/163. KCIJPCCF Clone customized WCONFIG members. (COND) RC= 00000 2012/08/164. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/175. KCIJPMC1 Merge profile from backup PLB2SP22 (COND) RC= 00000 2012/08/176. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. LPAR1 Customize PARMGEN configuration profiles. Edited 2012/08/179. KCIJPVAL Validate PARMGEN profile parameter values. RC= 00000 2012/08/1710. $PARSE Create the RTE members and jobs. RC= 00000 2012/08/1711> SUBMIT Submit batch jobs to complete PARMGEN setup. RC= 00000 2012/08/17U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The Customize PARMGEN Configuration Profile Members panel is displayed.2. Select option 1 to edit the LPAR configuration profile.


KCIP@PG6 ------ CUSTOMIZE PARMGEN CONFIGURATION PROFILE MEMBERS ---------------Option ===> 1(Required)* Select option 1 to customize the &rte_name RTE LPAR profile:

1. &rte_name RTE LPAR CONFIG profile in WCONFIG



3. LPAR1 System Variables CONFIG profile in GBL_USER_JCL(TSTEST.SYSPLEX.PARMGEN.JCL)(Required if using user-defined symbols or overridingsystem symbols’ resolved values - see F1=Help)



(Optional) Select option 7 for member list of the WCONFIG library:7. WCONFIG TSTEST.&userid.&rte_name.WCONFIG

3. Reconfigure the monitoring server as follows. (If you are reconfiguring the remote to point to ahigh-availability hub, see Scenario PGN03.) If the environment is enabled for system variables, usesystem variables to configure these values. You will also need to customize the system variablesprofile before returning to the main Workflow panel. See Scenario PGN02.a. Change the KDS_TEMS_TYPE value from HUB to REMOTE.

ISREDDE2 TSTEST.&userid.LPAR1.WCONFIG(LPAR1)Command ===> Scroll ===> CSR****** ***************************** Top of Data ******************************000602 KDS$ BEGIN *--------- TIVOLI ENTERPRISE MONITORING SERVER --------*000603 ** ============================ ================================000604 ** PARMGEN CONFIG Parameter PARMGEN CONFIG Value000605 ** ============================ ================================000606000607 ** TEMS configuration values:000608 KDS_TEMS_TYPE REMOTE * HUB or REMOTE ******* **************************** Bottom of Data ****************************

b. Do an EXCLUDE FIND on all KDS_HUB references. (For information on the XF (“EXCLUDEFIND") macro, see “XF edit macro” on page 136.) Then specify the values for the hub to whichthis remote monitoring server will connect.

SP22 TSTEST.&userid.LPAR1.WCONFIG(LPAR1)Command ===> XF KDS_HUB Scroll ===> CSR000829000830 ** Note: The KDS_HUB_* values populate the xKANPARU(KDCSSITE) member000831 ** that Remote TEMS reads to know how to connect to its Hub.000832 KDS_HUB_TEMS_NAME_NODEID "PLBHUB"000833000834 ** If the TEMS is a Remote and requires VTAM SNA support:000835 KDS_HUB_VTAM_APPL_GLB_BROKER "" * Hub KDS_TEMS_VTAM_APPL_GLB_BROKER000836 KDS_HUB_VTAM_NETID "" * Hub KDS_TEMS_VTAM_NETID000837000838 ** If the TEMS is a Remote and requires TCP/IP support:000839 KDS_HUB_TCP_HOST "OMEGHUB"000840000841 ** If the TEMS is a Remote, specify port numbers of its Hub:000842 KDS_HUB_TCP_PIPE_PORT_NUM nnnnn * Hub KDS_TEMS_TCP_PIPE_PORT_NUM000843 KDS_HUB_TCP_UDP_PORT_NUM nnnnn * Hub KDS_TEMS_TCP_UDP_PORT_NUM000844 KDS_HUB_TCP_PIPE6_PORT_NUM "" * Hub KDS_TEMS_TCP_PIPE6_PORT_NUM000845 KDS_HUB_TCP_UDP6_PORT_NUM "" * Hub KDS_TEMS_TCP_UDP6_PORT_NUM000846 KDS_HUB_TCP_PIPES_PORT_NUM "" * Hub KDS_TEMS_TCP_PIPES_PORT_NUM000847 KDS_HUB_TCP_PIPE6S_PORT_NUM "" * Hub KDS_TEMS_TCP_PIPE6S_PORT_NUM- - - - - - - - - - - - - - - - - - 853 Line(s) not Displayed****** **************************** Bottom of Data ****************************


c. Press F3 to save the changes and return to the main Workflow panel.4. On the KCIP@PG0 main panel, select option 10 to create the WK* runtime members and the

WKANSAMU jobs.

Note: If you are reconfiguring a runtime environment in which system variables are enabled, option10 displays $PARSESV instead of $PARSE, as in the following example.






1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/162. $JOBINDX Review PARMGEN job index. Viewed 2012/08/163. KCIJPCCF Clone customized WCONFIG members. (COND) RC= 00000 2012/08/164. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/175. KCIJPMC1 Merge profile from backup PLB2SP22 (COND) RC= 00000 2012/08/176. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. LPAR1 Customize PARMGEN configuration profiles. Edited 2012/11/299> KCIJPVAL Validate PARMGEN profile parameter values. RC= 00000 2012/11/2910. $PARSE Create the RTE members and jobs. RC= 00000 2012/08/1711. SUBMIT Submit batch jobs to complete PARMGEN setup. RC= 00000 2012/08/17U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The $PARSE/$PARSESV : Create the RTE Members and Jobs panel is displayed.5. Select option 1 to submit the generated $PARSE (or $PARSESV) composite job.

--------------- $PARSE/$PARSESV: CREATE THE RTE MEMBERS AND JOBS --------------Option ===> 1

Select option 1 to SUBMIT the full $PARSE job in WCONFIG for RTE=&rte_name.Alternatively, select other options to SUBMIT $PARSE jobs individually.Press F1=Help for additional considerations when selecting options 2-5.


1. $PARSE Composite $PARSE job RC= 00004 2012/11/27** or **

2. $PARSECM IKANCMDU/WKANCMDU $PARSE job (Optional) RC= 00000 2012/08/223. $PARSEPR IKANPARU/WKANPARU $PARSE job (Optional) RC= 00000 2012/09/124. $PARSESM IKANSAMU/WKANSAMU $PARSE job (Optional) RC= 00004 2012/09/27



The JCL for the $PARSE (or $PARSESV) job is displayed.6. Review the job and submit it, then return to the main Workflow panel.

Tip: If you receive a bad return code (over 0004), enter 1s to view detailed status for the job.7. From the Workflow main menu, select option 11to set up of the runtime environment.







1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/162. $JOBINDX Review PARMGEN job index. Viewed 2012/08/163. KCIJPCCF Clone customized WCONFIG members. (Optional) RC= 00000 2012/08/164. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/175. KCIJPMC1 Merge profile from backup PLB2SP22 (Optional) RC= 00000 2012/08/176. KCIJPMC2 Merge profile from model RTE. (Optional)7. KCIJPCNV Convert an ICAT RTE Batch member. (Optional)8. LPAR1 Customize PARMGEN configuration profiles. Edited 2012/11/319. KCIJPVAL Validate PARMGEN profile parameter values. RC= 00000 2012/11/3110> $PARSE Create the RTE members and jobs. RC= 00000 2012/11/3111. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The Submit Batch Jobs to Complete PARMGEN Setup (KCIP@SUB) panel is displayed.8. Depending upon your environment, complete one of the following sets of steps:

v If your environment does not have system variables enabled:a. Select option 1 to submit the KCIJPSUB master submit job, or, to submit each job individually,

select the other options.

KCIP@SUB -------- SUBMIT BATCH JOBS TO COMPLETE PARMGEN SETUP -----------------OPTION ===> 1 SCROLL ===> CSR



1. KCIJPSUB Composite master SUBMIT job

2. KCIJPALO Allocate runtime libraries3. KCIJPLOD Load TK*->RK* runtime libraries4. KCIJPSEC Product security (Conditional)5. N/A System Variables IEBUPDTE (Conditional)6. KCIJPUSP USS preparation (Conditional)7. KCIJPUSS USS system set-up (Authorization required)8. KCIJPSYS System set-up (Authorization required)9. KCIJPLNK ASM/Link RKANMODU modules (Conditional)10. KCIJPCPY Backup IK*,WK* or RK* user lib. (Conditional)11. KCIJPW2R WK*->RK* deployment (Conditional)12. KCIJPIVP Configuration verificationEnter=Next F1=Help F3=End/Cancel

If you select option 1, first review the KCIJPSUB job, and edit the job according to which of theconditional jobs need to be submitted automatically.

v If your environment has system variables enabled:a. On the Submit Batch Jobs to Complete PARMGEN Setup, select option 1 if you want to submit

the KCIJVSUB master SUBMIT job, or select the other options to submit each job individually. Ifyou select option 1, review the KCIJVSUB job first and edit the job according to whichconditional jobs need be submitted automatically.



Select option 1 to SUBMIT the composite jobs in WKANSAMU for RTE=PLB3SYSG.Alternatively, select other options to SUBMIT each job individually.Press F1=Help for additional considerations when selecting options 4-14.





b. Press Enter.The following message is displayed:



c. Press Enter.The following message is displayed:







d. Press Enter to edit the KCIJPSUV job.Jobs that require authorization or are conditional are not submitted automatically. You musteither submit them manually, or uncomment them to run automatically.

e. Press F3, and you are automatically be presented with the KCIJVSUB job for submission. Submitthe job. Check the status of each of the jobs submitted. The allocation and load jobs must runsuccessfully, or others jobs will not run.

Results

You have reconfigured the runtime environment's hub monitoring server as a remote monitoring serverand connected it to a hub monitoring server running on a different LPAR.

What to do next

If your KCIJPSYS job is pointing to your own version of the following libraries, you must refresh theproduction version.

GBL_DSN_HZSPROC_LOADLIBGBL_DSN_SYS1_PARMLIBGBL_DSN_SYS1_SAXREXECGBL_DSN_SYS1_PROCLIBGBL_DSN_SYS1_VTAMLIBGBL_DSN_SYS1_VTAMLIB

Restart the remote monitoring server.

Scenario RTE05: Delete a product or component from a runtimeenvironmentIn this scenario, you delete a product or component from an existing runtime environment.

About this task

The procedure is similar to adding a new product as outlined in “Scenario RTE01: Add a new productinto an existing PARMGEN runtime environment” on page 99. The difference is that here you need toexclude an already configured component or product on the Exclude Products From PARMGENCustomization (KCIP@PG5) panel.


This step backs up (renames) the existing LPAR profile, runs the KCIJPUP2 job to update interimlibraries and recreate the configuration profiles with any new parameters, and runs KCIJPMC1 tomerge the backup profile with the newly created one. This job also ensures that theWCONFIG($VERSION) member points to the correct upgraded versions of the FMIDs, as these valuesare key to the $PARSE* processing.


a. On the main Workflow panel, specify the name of the runtime environment to which you want toapply maintenance.

b. From the Workflow main menu, select option 1 to regenerate and resubmit the KCIJPCFG job. Thefollowing message is displayed:





_______________________________________________________________________________


displayed.e. Place an X next to any product that you do not want to include in the runtime environment. In the

following example, z/OS Management Console is being deleted from the runtime environment asit has now been incorporated into OMEGAMON XE for z/OS V5.1.0.





_ ALL Exclude all not configured in RTE profile_ KAH* IBM Tivoli System Automation for z/OS V330_ KC5* IBM Tivoli OMEGAMON XE for CICS on z/OS V510_ KDS* Tivoli Enterprise Monitoring Server V630_ KD4* IBM Tivoli Composite Application Manager for SOA V711_ KD5* IBM Tivoli OMEGAMON XE for DB2 PE/PM V511_ KGW* IBM Tivoli OMEGAMON XE for CICS TG on z/OS V510X KHL* IBM OMEGAMON z/OS Management Console V410_ KI5* IBM Tivoli OMEGAMON XE for IMS on z/OS V510_ KMC* IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Configuration V710_ KMQ* IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Monitoring V710_ KM5* IBM Tivoli OMEGAMON XE on z/OS V510_ KNA* IBM Tivoli NetView for z/OS Agent V610_ KN3* IBM Tivoli OMEGAMON XE for Mainframe Networks V510_ KOB* Tivoli OMEGAMON Enhanced 3270 User Interface V700_ KQI* IBM Tivoli OMEGAMON XE for Messaging - WebSphere Message Broker V710_ KRG* IBM Tivoli Advanced Audit for DFSMShsm V230_ KRH* IBM Tivoli Advanced Reporting and Management for DFSMShsm V240_ KRJ* IBM Tivoli Advanced Allocation Management for z/OS V310_ KRK* IBM Tivoli Automated Tape Allocation Manager for z/OS V320_ KRN* IBM Tivoli Advanced Catalog Management for z/OS V240_ KRV* IBM Tivoli Advanced Backup and Recovery for z/OS V230_ KRW* IBM Tivoli Tape Optimizer for z/OS V220_ KS3* IBM Tivoli OMEGAMON XE for Storage on z/OS V510_ KWO* IBM Tivoli OMEGAMON DE on z/OS - OMEGAVIEW and OMEGAVIEW II V510_ KYN* ITCAM for Application Diagnostics on z/OS V710Enter=Next F1=Help F3=Back F7=Up F8=Down









KCIJPUP1 and KCIJPMC1 jobs.2. Recreate the runtime environment members and jobs.

a. Select option 10.






1. KCIJPCFG Set up PARMGEN work environment for an RTE. RC= 00000 2012/08/172. $JOBINDX Review PARMGEN job index. Viewed 2012/08/163. KCIJPCCF Clone customized WCONFIG members. (COND) RC= 00000 2012/08/174. KCIJPUP1 Update interim libraries and create profiles. RC= 00000 2012/08/175. KCIJPMC1 Merge profile from backup PLB3SP13 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND) RC= 00000 2012/08/177. KCIJPCNV Convert an ICAT RTE Batch member. (COND) RC= 00000 2012/08/178. PLB1SP22 Customize PARMGEN configuration profiles. Edited 2012/08/179> KCIJPVAL Validate PARMGEN profile parameter values. Submitted 2012/08/1710. $PARSESV Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The $PARSE/$PARSESV: Create the RTE Members and Jobs (KCIP@PRS) panel is displayed.b. Select option 1 to submit the generated $PARSE or $PARSESV composite job.



Select option 1 to SUBMIT the full $PARSESV job in WCONFIG for RTE=PLB1SP22.Alternatively, select other options to SUBMIT $PARSE jobs individually.Press F1=Help for additional considerations when selecting options 2-5.






The $PARSE ot $PARSESV member is presented.c. Review the member for any jobs that need to be submitted manually, then submit the job. Return


a. On the Workflow main panel, select option 11 (Submit batch jobs to complete PARMGEN setup).






1. KCIJPCFG Set up PARMGEN work environment for an RTE.2. $JOBINDX Review PARMGEN job index.3. KCIJPCCF Clone customized WCONFIG members. (COND)4. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup PLB1SP22 (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. PLB1SP22 Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10> $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

The SUBMIT Submit batch jobs to complete PARMGEN setup (KCIP@SUB ) is displayed.b. Select option 1 to submit the KCIJcSUB master submit job, or select the other options to submit

each job separately.c. If you select option 1, first review the KCIJPSUB job, and edit the job according to which of the

conditional jobs need to be submitted automatically.a. Submit the master SUBMIT job, and check for good condition codes.



b. Review the resulting output:v $IVPRPT report, which is stored in the WCONFIG libraryv WSUPERC SYSTSPRT report, which is stored in the WSUPERC sequential library

c. Correct any errors, and rerun any jobs that did not complete successfully.

Scenario RTE06: Delete a runtime environmentIn this scenario, you delete an entire runtime environment.

About this task

When the libraries for a particular runtime environment are deleted, the persistent datastore libraries aredeliberately not deleted to accommodate other Tivoli Enterprise Monitoring Servers in other runtimeenvironments that use the same sysplex-level persistent datastore libraries

Procedure

To delete a runtime environment, copy the KCIJPDEL job from WKANSAMU to the library defined bythe GBL_USER_JCL parameter (the first field on the main PARMGEN Workflow panel), then submit it.The KCIJPDEL job specifies the name of the runtime environment from which it was copied. It must berun from a different library, because it cannot delete itself.Note that the name of the runtime environment will still appear in the list that appears when you enter aquestion mark (?) in the RTE_NAME field on the main Workflow panel, and the PARMGEN worklibraries and the configuration profiles still exist. Only the RK* production libraries are deleted. This canbe useful if you want to recreate the environment.



Chapter 5. PARMGEN how-tos

This section contains topics that tell you “how to” perform specific tasks, especially tasks that were donedifferently using the Configuration Tool method.

How to: Convert an existing static hub monitoring environment to ahigh-availability hub environmentTo convert an existing hub environment to a high-availability (HA) hub environment, you create a newruntime environment with an HA hub and then either create a new RTE with a remote or convert theexisting hub runtime environment to a remote and configure it and any other remotes to connect to thenew HA.

About this task

When converting from a standard, static z/OS hub to an HA hub, you create a new runtime environment(either full or sharing) for the HA hub. The old static hub is either decommissioned if no longer neededor replaced by a remote monitoring server. The newly converted remote will take over all non-hubresponsibilities of the old hub, such as collecting data for OMEGAMON XE on z/OS product or hostingagents. The new HA hub handles only hub-type functions. To preserve any customization (situations,managed systems list, and the like), the Enterprise Information Base from the static hub can be given tothe new HA hub. Any application support such as the catalog and attribute files for distributed agentsthat were manually added to the old, static hub will need to be copied from the old hub to the new HAhub.

Procedure1. Create a new runtime environment and configure a high-availability hub in it (see scenario PGN03).2. Before shutting down the old hub for the last time, create a member in RKANSQLU with the

following statements:DELETE FROM O4SRV.TSITDESC WHERE SITNAME LIKE ’UADVISOR_KM5_V*’;DELETE FROM O4SRV.SITDB WHERE RULENAME LIKE ’KM5.V*’;

3. Execute the commands by using a Modify command:F <hub stc>,CTDS START SPUFIL <name of member>

These situations are seeded using the configuration software and must not be in the database of theHA hub because they can trigger data collection attempts.

4. Back up the old hub runtime environment, preferably with the hub down.5. Delete the following data sets from the new HA hub runtime environment and replace them with the

old hub data sets. :%HILEV%.%RTENAME%.RKDS*%HILEV%.%RTENAME%.RKCF* if applicable%HILEV%.%RTENAME%.RKCP* if applicable

This gives the new hub the entire EIB of the old one as well as the MQ Configuration Database (ifapplicable) and the CICSplex Service Level parameters (if applicable).

6. Take one of the following paths:v Build a new runtime environment for the LPAR where the old hub used to run. Define the

monitoring server as remote and configure it to report to the new HA hub (see, for example,scenario PGN01).


v Modify the existing runtime environment to convert the hub to a remote (scenario PGN04).7. Reconfigure any portal server or agent connecting directly to the hub, such as Warehouse Proxy

Agents. For the portal server, do not rebuild the portal server database but use the same one that wasused for the old hub (respond No to the pop-up). Reconfigure any remote monitoring servers to reportto the new HA hub (see scenario RTE04).

8. After a portal server is connected to the new HA hub, use the Managed Systems List editor to reviewall custom MSLs that include monitoring server node IDs (if any) and use the situation editor toreview all situations that are distributed to remote monitoring servers directly or to Managed SystemsLists that include monitoring server Node IDs. Also, review all Historical Data Collectionconfiguration.

How to: Use KOBSUPDT security exits with PARMGENThis scenario illustrates how to keep KOBSUPDT OMEGAMON security command table exits for thePARMGEN KCIJPSEC composite security job when converting from a Configuration Tool runtimeenvironment to a PARMGEN configuration.

About this task

Table 2 lists the names of the security command table exits. Table 3 provides the source of these exits.

Table 2. Names of OMEGAMON security command table exits

PARMGEN Configuration Tool

OMEGAMON XE for CICS KOCSUPDI KC2XSECU

OMEGAMON XE for DB2Performance ExpertOMEGAMON XE for DB2Performance Monitor

KO2SUPDI KO2SUPDI

OMEGAMON XE for IMS KOISUPDI KOISUPDI

OMEGAMON XE on z/OS KOMSUPDI KOMSUPDI

Table 3. Source of the KppSUPDI KOBSUPDT OMEGAMON security exits

Component

KOBSUPDTSecurity Jobs(PARMGEN)

KOBSUPDTSecurity Jobs(ICAT)

KOBSUPDTLocation(PARMGEN)

KOBSUPDTLocation (ICAT)

KOBSUPDTMODULE

OMEGAMON(3270) z/OS

Composite:WKANSAMU(KCIJPSEC) orstand-alone:WKANSAMU(KOMSUPD)

INSTJOBS(M2#Oxxxx) orstand-alone:RKANSAMU(KOMSUPD)

RTE'sWKANSAMU

RTE'sRKANPARU

KOMCM510OMCMD510

OMEGAMON(3270) CICS

Composite:WKANSAMU(KCIJPSEC) orstand-alone:WKANSAMU(KOCSUPD)

INSTJOBS(C2#Oxxxx) orstand-alone: nonefor C2#Oxxxx

RTE'sWKANSAMU

&shilev.INSTDATA

KOCCMX00

OMEGAMON(3270) DB2

Composite:WKANSAMU(KCIJPSEC) orstand-alone:WKANSAMU(KO2SUPD)

INSTJOBS(D2#Oxxxx) orstand-alone:RKD2SAM(KO2SUPD)

RTE'sWKANSAMU

RTE's RKD2SAM KO2OCMDB


Table 3. Source of the KppSUPDI KOBSUPDT OMEGAMON security exits (continued)

Component

KOBSUPDTSecurity Jobs(PARMGEN)

KOBSUPDTSecurity Jobs(ICAT)

KOBSUPDTLocation(PARMGEN)

KOBSUPDTLocation (ICAT)

KOBSUPDTMODULE

OMEGAMON(3270) IMS

Composite:WKANSAMU(KCIJPSEC) orstand-alone:WKANSAMU(KOISUPD)

INSTJOBS(I2#Oxxxx) orstand-alone:RKANSAMU(KOISUPD

RTE'sWKANSAMU

RTE'sRKANPARU

KOICTJQ(IMS9.1)KOICTKQ(IMS10.1)KOICTLQ(IMS11.1)KOICTMQ(IMS12.1)

Table 4 lists the names of the external security exits for each product. Table 5 provides the source for theexternal exits.

Table 4. Names of security command table exit by product and configuration method

PARMGEN Configuration Tool

OMEGAMON XE on z/OS KOMACF2X KOMRACFX

OMEGAMON XE for CICS KOCAACF2KOCARACFKOCATOPS

KOCBRACF

OMEGAMON XE for DB2 KO2ACF2X KO2RACFX

OMEGAMON XE for IMS KOIACF2X KOIRACFX

Table 5. Source of the OMEGAMON external security exits and modules referenced in the KOBSUPDT KppSUPDIexit

Component

ExternalSecurity Jobs(PARMGEN)

ExternalSecurity Jobs(ICAT)

ExternalSecurityLocation(PARMGEN)

ExternalSecurityLocation(ICAT)

ExternalSecurityMODULEReferenced inKOBSUPDTExit Name(RACF)

ExternalSecurityMODULEReferenced inKOBSUPDTExit Name(ACF2)

OMEGAMON(3270) CICS

Composite:WKANSAMU(KCIJPSEC) orstand-alone:WKANSAMU(KOCACF2A),WKANSAMU(KOCRACFA),andWKANSAMU(KOCTOPSA)

INSTJOBS(C2#3xxxx)creates thestand-alonejobs; then runthe applicablejobs:RKANSAMU(KOCJACF2),RKANSAMU(KOCJRACF),andRKANSAMU(KOCJTOPS)

User-specifiedRTE_X_SECURITY_EXIT_LIBlibrary(initiallycopied fromTKANSAMsample exit).

RTE'sRKANSAMU(C2#3xxxx jobcopied initiallyfromTKANSAMsample exit).

KOCARACFKOCBRACF(SAF)

KOCAACF2

Chapter 5. PARMGEN how-tos 121

Table 5. Source of the OMEGAMON external security exits and modules referenced in the KOBSUPDT KppSUPDIexit (continued)

Component

ExternalSecurity Jobs(PARMGEN)

ExternalSecurity Jobs(ICAT)

ExternalSecurityLocation(PARMGEN)

ExternalSecurityLocation(ICAT)

ExternalSecurityMODULEReferenced inKOBSUPDTExit Name(RACF)

ExternalSecurityMODULEReferenced inKOBSUPDTExit Name(ACF2)

OMEGAMON(3270) DB2

Composite:WKANSAMU(KCIJPSEC) orstand-alone:WKANSAMU(KO2ACF2A)andWKANSAMU(KO2RACFA)

INSTJOBS(D2#3xxxx)creates thestand-alonejobs; then runthe applicablejobs:-RKD2SAM(KO2ACF2A)and RKD2SAM(KO2RACFA)


RTE'sRKD2SAM(D2#3xxxx jobcopied initiallyfromTKANSAMsample exit).

KO2RACFX KO2ACF2X

OMEGAMON(3270) IMS

Composite:WKANSAMU(KCIJPSEC) orstand-alone:WKANSAMU(KOIACF2A)andWKANSAMU(KOIRACFA)

INSTJOBS(I2#3xxxx)creates thestand-alonejobs; then runthe applicablejobs:RKANSAMU(KOIACF2A)andRKANSAMU(KOIRACFA)


RTE'sRKANSAMU(I2#3xxxx jobcopied initiallyfromTKANSAMsample exit).

KOIURCHK KOIUACHK

OMEGAMON(3270) z/OS

Composite:WKANSAMU(KCIJPSEC) orstand-alone:WKANSAMU(KOMACF2A)andWKANSAMU(KOMRACFA)

INSTJOBS(M2#3xxxx)creates thestand-alonejobs; then runthe applicablejobs:RKANSAMU(KOMACF2A)andRKANSAMU(KOMRACFA))


RTE'sRKANSAMU(M2#3xxxx jobcopied initiallyfromTKANSAMsample exit).

KOMRACFX KOMACF2X

Procedure1. If the RTE_X_SECURITY_EXIT_LIB parameter in the LPAR configuration profile is pointing to

RKANSAM (the original default), change it to point to the appropriate library. The new default isRKANSAMU.This global security exit data set is allocated by the KCIJPALO allocation job. TheRTE_X_SECURITY_EXIT_LIB parameter defaults to the RKANSAMU library of the runtimeenvironment, because this is where the KCIJcLOD copies all the product security exits, includingKppSUPDI.In this example, IBM.ITM62351.LPAR1.SECURITY is the RTE_X_SECURITY_EXIT_LIB value, asshown in line 536 of the following example.


EDIT IBM.ITM62351.LPAR1.WCONFIG(LPAR1)Command ===>000524 ** Library where user security exits are located:000525 ** Override the SYSIN DD where the user exits may have been000526 ** customized (if other than default RKANSAM location).000527 ** The KppJPSC3 input members to the composite KCIJPSEC security job000528 ** point SYSIN DD to RKANSAM by default. If you need to make further000529 ** changes to sample exit, copy the user exit to xKANSAMU library and000530 ** make changes accordingly. Then modify the RTE_X_SECURITY_EXIT_LIB000531 ** parameter and change the value to RKANSAMU instead.000532 ** ICAT->PARMGEN conversion considerations:000533 ** If this is an ICAT RTE conversion, the security exit source000534 ** library varies for each product. Please refer to the000535 ** application-specific security jobs for more information.000536 RTE_X_SECURITY_EXIT_LIB IBM.ITM62351.LPAR1.SECURITY

2. Run the $PARSE or $PARSESV job to recreate the runtime members and update the jobs.3. Submit the following jobs from the Submit Batch Jobs to Complete PARMGEN Setup (KCIP@SUB)

panel (option 11):a. If you changed the name of the library, rerun KCIJcALO.b. Run the KCIJcLOD job.

4. Select option 4 (KCIJPcSEC). The following message is displayed:


You are about to run the security job. Before editing thesecurity job, you will first be given an opportunity to editthe security exits in lib TSTEST.CCAPI.PLB1SP22.RKANSAMU.If desired, customize the security exits.

_______________________________________________________________________________

5. Press Enter to proceed.6. Select the exits you want to edit, and customize them as appropriate. For example, if they have not

already been customized, edit the RACF-related or ACF2-related external security exits to point tothe preferred resource class if other than the IBM-supplied default. If not already customized, editthe applicable KppSUPDI KOBSUPDT security exits to point the MODULE= parameter to yourexternal security module. (See the columns labeled External Security MODULE Referenced inKOBSUPDT Exit Name in Table 5 on page 121).

7. After you finish making the changes, press F3. The modified KCIJcSEC job is presented.8. Submit the job.9. Submit the KCIJcCPR to back up the RK* production user libraries.

10. Submit the KCIJcW2R job to copy the work libraries (WK*) to the production libraries (RK*).

Results

The KOBSUPDT OMEGAMON security command table exits are available in the new PARMGENruntime environment.


How to: Override the currently configured default storage limit withinthe RKANPARU(KppSYSIN) startup memberIn general, when in PARMGEN mode, any storage-related parameters (including the ones currently notexternalized when using the Configuration Tool) are available for customization and overrides.IBM-supplied defaults are set using the same values as those hard-coded in a Configuration Tool runtimeenvironment. In this scenario, you change the storage limit parameter reflected in the KppSYSIN start upmember.

About this task

This task involves three main steps:1. Edit the applicable *_LIMIT_EXTEND parameter in the LPAR configuration profile.2. Run the $PARSE or $PARSESV job, as appropriate to recreate the runtime members and jobs.3. Resubmit the appropriate batch jobs to complete the setup.

Follow this procedure to complete this task using the PARMGEN Workflow user interface.

Procedure1. Edit the LPAR configuration profile:

a. On the main Workflow panel, set the name of the runtime environment you want to modify andselect option 8 to edit its LPAR profile.

b. On the Customize PARMGEN Configuration Profile Member panel, select option 1. The profile isdisplayed.

c. Change the appropriate parameters.v To modify the storage limit for a z/OS monitoring server, locate the

KDS_TEMS_STORAGE_LIMIT_EXTEND and provide the desired value.

Command ===> Scroll ===> CSR000916 KDS_TEMS_STORAGE_LIMIT_PRIMARY 20000917 KDS_TEMS_STORAGE_LIMIT_EXTEND 30000918 KDS_TEMS_KGL_WTO Y000919 KDS_TEMS_KDC_DEBUG N000920 KDS_TEMS_KLX_TCP_TOLERATERECYCLE Y

v To modify the storage limit for agents running in their own address space, do an EXCLUDEFIND on AGT_STORAGE and specify the desired values. (For information on EXCLUDE FIND,see “XF edit macro” on page 136.)


File Edit Edit_Settings Menu Utilities Compilers Test HelpsssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssEDIT TSTEST.CCAPI.PLB4SYSG.WCONFIG(PLB4SYSG) - 01.02 Columns 00001 00072Command ===> Scroll ===> CSR****** ***************************** Top of Data ******************************- - - - - - - - - - - - - - - - - - 1408 Line(s) not Displayed001409 KC5_AGT_STORAGE_MINIMUM_EXTEND 384000001410 KC5_AGT_STORAGE_DETAIL_INT_HR 00001411 KC5_AGT_STORAGE_DETAIL_INT_MIN 60- - - - - - - - - - - - - - - - - - 130 Line(s) not Displayed001542 KC5_X_AGT_STORAGE_LIMIT_PRIMARY 16

001543 KC5_X_AGT_STORAGE_LIMIT_EXTEND 23001544 KC5_X_AGT_STORAGE_RESERVE_PRI 2048001545 KC5_X_AGT_STORAGE_RESERVE_EXT 2048- - - - - - - - - - - - - - - - - - - 8 Line(s) not Displayed001554 KC5_X_AGT_STORAGE_STGDEBUG N- - - - - - - - - - - - - - - - - - 142 Line(s) not Displayed001697 KGW_AGT_STORAGE_MINIMUM_EXTEND 256000001698 KGW_AGT_STORAGE_DETAIL_INT_HR 00001699 KGW_AGT_STORAGE_DETAIL_INT_MIN 60- - - - - - - - - - - - - - - - - - 106 Line(s) not Displayed001806 KGW_X_AGT_STORAGE_LIMIT_PRIMARY 16001807 KGW_X_AGT_STORAGE_LIMIT_EXTEND 22001808 KGW_X_AGT_STORAGE_RESERVE_PRI 2048001809 KGW_X_AGT_STORAGE_RESERVE_EXT 2048- - - - - - - - - - - - - - - - - - - 8 Line(s) not Displayed001818 KGW_X_AGT_STORAGE_STGDEBUG N- - - - - - - - - - - - - - - - - - 624 Line(s) not Displayed002443 KD5_AGT_STORAGE_MINIMUM_EXTEND 300000002444 KD5_AGT_STORAGE_DETAIL_INT_HR 00002445 KD5_AGT_STORAGE_DETAIL_INT_MIN 60- - - - - - - - - - - - - - - - - - - 81 Line(s) not Displayed

d. To modify the CUA environment for an OMEGAMON agent, modify itsKpp_X_*_STORAGE_LIMIT_EXTEND parameter.The following screen shows a full list of available agent-specific Kpp_X_AGT_STORAGE_*PARMGEN profile parameters and their current IBM-supplied configuration default values.


****** ***************************** Top of Data *****************************- - - - - - - - - - - - - - - - - - 665 Line(s) not Displayed000666 KDS_TEMS_STORAGE_MINIMUM_EXTEND 768000000667 KDS_TEMS_STORAGE_LIMIT_PRIMARY 20000668 KDS_TEMS_STORAGE_LIMIT_EXTEND 23- - - - - - - - - - - - - - - - - - - 3 Line(s) not Displayed000672 KDS_TEMS_STORAGE_DETAIL_LOG_FLAG Y000673 KDS_TEMS_STORAGE_DETAIL_INT_HR 00000674 KDS_TEMS_STORAGE_DETAIL_INT_MIN 60- - - - - - - - - - - - - - - - - - 134 Line(s) not Displayed000809 KDS_X_TEMS_STORAGE_RESERVE_PRI 4096- - - - - - - - - - - - - - - - - - - 18 Line(s) not Displayed000828 KDS_X_TEMS_STORAGE_STGDEBUG N- - - - - - - - - - - - - - - - - - 248 Line(s) not Displayed001077 Kpp_AGT_STORAGE_MINIMUM_EXTEND 256000001078 Kpp_AGT_STORAGE_DETAIL_INT_HR 00001079 Kpp_AGT_STORAGE_DETAIL_INT_MIN 60- - - - - - - - - - - - - - - - - - - 54 Line(s) not Displayed001134 Kpp_X_AGT_STORAGE_LIMIT_EXTEND 22001135 Kpp_X_AGT_STORAGE_LIMIT_PRIMARY 16001136 Kpp_X_AGT_STORAGE_RESERVE_PRI 2048001137 Kpp_X_AGT_STORAGE_RESERVE_EXT 2048- - - - - - - - - - - - - - - - - - - 8 Line(s) not Displayed001146 Kpp_X_AGT_STORAGE_STGDEBUG N- - - - - - - - - - - - - - - - - - 138 Line(s) not Displayed001285 KC2_X_CICS_STORAGE_MIN_EXTEND 16384001286 KC2_X_CICS_STORAGE_LIMIT_EXTEND 17001287 KC2_X_CICS_STORAGE_LIMIT_PRIMARY 17- - - - - - - - - - - - - - - - - - - 2 Line(s) not Displayed001290 KC2_X_CICS_STORAGE_STGDEBUG N- - - - - - - - - - - - - - - - - - 175 Line(s) not Displayed002788 KD2_X_DB2_STORAGE_LIMIT_PRIMARY 16002789 KD2_X_DB2_STORAGE_LIMIT_EXTEND 18- - - - - - - - - - - - - - - - - - - 6 Line(s) not Displayed002796 KD2_X_DB2_STORAGE_MIN_PRIMARY 512002797 KD2_X_DB2_STORAGE_MIN_EXTEND 8192- - - - - - - - - - - - - - - - - - - 2 Line(s) not Displayed002800 KD2_X_DB2_STORAGE_STGDEBUG N- - - - - - - - - - - - - - - - - - 193 Line(s) not Displayed003468 KI2_X_IMS_STORAGE_STGDEBUG N- - - - - - - - - - - - - - - - - - - 6 Line(s) not Displayed003475 KI2_X_IMS_STORAGE_RESERVE_PRI 2048003476 KI2_X_IMS_STORAGE_RESERVE_EXT 2048003477 KI2_X_IMS_STORAGE_MIN_PRIMARY 4096003478 KI2_X_IMS_STORAGE_MIN_EXTEND 20000003479 KI2_X_IMS_STORAGE_LIMIT_EXTEND 23003480 KI2_X_IMS_STORAGE_LIMIT_PRIMARY 16- - - - - - - - - - - - - - - - - - 134 Line(s) not Displayed004483 KM2_X_MVS_STORAGE_MIN_EXTEND 76800004484 KM2_X_MVS_STORAGE_RESERVE_PRI 2048004485 KM2_X_MVS_STORAGE_LIMIT_PRIMARY 20004486 KM2_X_MVS_STORAGE_LIMIT_EXTEND 23- - - - - - - - - - - - - - - - - - - 6 Line(s) not Displayed004493 KM2_X_MVS_STORAGE_STGDEBUG N- - - - - - - - - - - - - - - - - - 161 Line(s) not Displayed004906 KON_X_VTAM_STORAGE_MIN_PRIMARY 1024004907 KON_X_VTAM_STORAGE_MIN_EXTEND 60000004908 KON_X_VTAM_STORAGE_LIMIT_PRIMARY 20004909 KON_X_VTAM_STORAGE_LIMIT_EXTEND 23004910 KON_X_VTAM_STORAGE_RESERVE_PRI 2048004911 KON_X_VTAM_STORAGE_RESERVE_EXT 4096- - - - - - - - - - - - - - - - - - - 10 Line(s) not Displayed004922 KON_X_VTAM_STORAGE_STGDEBUG N- - - - - - - - - - - - - - - - - - 158 Line(s) not Displayed006978 KDF_X_SMS_STORAGE_MIN_EXTEND 60000006979 KDF_X_SMS_STORAGE_LIMIT_EXTEND 22006980 KDF_X_SMS_STORAGE_LIMIT_PRIMARY 17006981 KDF_X_SMS_STORAGE_RESERVE_PRI 2048- - - - - - - - - - - - - - - - - - - 11 Line(s) not Displayed006993 KDF_X_SMS_STORAGE_STGDEBUG N- - - - - - - - - - - - - - - - - - 235 Line(s) not Displayed****** **************************** Bottom of Data ****************************


The Kpp codes and the products they represent are listed in Appendix A, “Product codes,” onpage 133.

e. Save the changes and return to the main Workflow panel.2. Recreate the runtime environment members and jobs.

a. From the main menu, select option 10. The $PARSE/$PARSESV: Create the RTE Members and Jobspanel is displayed.

b. Select the $PARSE (or $PARSESV) composite job or the appropriate $PARSE%% library specificjob. The JCL is presented.

c. Review the job and make any required adjustments, then submit it and return to the mainWorkflow panel.

3. Edit and submit the batch jobs to complete the setup.a. Select option 11 from the main menu. The Submit Batch Job to Complete PARMGEN Setup panel

is displayedb. If system variables are enabled, select option 5 and submit the KCIJVUPV job.c. (Optional, but best practice) Select option 12 and submit the KCIJcCPR job to backup the product

libraries.d. Select option 13 to submit KCIJcW2R to copy the work libraries to the production libraries.

Results

The LPAR configuration profile is updated, and the KppSYSIN members are updated with the newvalues.

How to: Avoid refreshing shared read-only base libraries multipletimesRunning the KCIJPLOD load job is part of most maintenance scenarios. For sharing-with-baseenvironments, this job loads both the LPAR-unique libraries and the common shared base libraries bydefault. The RTE_LOAD_SHARED_LIBS parameter in the configuration profile of each runtimeenvironment controls whether or not the base libraries are loaded. If you have multiple runtimeenvironments sharing the same base libraries, to avoid loading the base libraries multiple times designateone environment as the master by leaving its flag set to Y, and disable loading of base libraries in all theothers.

About this task

If the RTE_LOAD_SHARED_LIBS parameter is set to Y (the default) in the profiles for all the runtimeenvironments that share the same base libraries, then the KCIJPLOD job for each environment loads thebase libraries each time you run the KCIJPLOD job. Although it does not hurt the configuration to do so,running the job multiple times will perform multiple IEBCOPY steps to the RK* libraries for the sameSMP/E code. If you have multiple runtime environments sharing the read-only base libraries, it is a bestpractice designate one master environment that will load the base libraries. Leave theRTE_LOAD_SHARED_LIBS parameter for the master environment set to the default. Set the value for theother environments to N.

Procedure

To disable loading of base libraries in sharing runtime environments, locate theRTE_LOAD_SHARED_LIBS parameter in the configuration profile and set its value to N:


IBM.ITM62351.LPAR1.WCONFIG(LPAR1)Command ===> Scroll ===> CSR000358 ** Runtime environment (RTE) settings:000359 ** Specify the name of the RTE in the RTE_NAME parameter if this RTE000360 ** is not enabled for System Variables (RTE_SYSV_SYSVAR_FLAG=N).000361 RTE_NAME LPAR1000362000365 ** Type of RTE:000366 ** There are three types of RTEs:000367 ** FULL - Allocates Image-specific and Base libraries.000368 ** SHARING - Allocates Image-specific libraries and shares Base000369 ** libraries with another RTE or SMP/E target libraries.000370 RTE_TYPE SHARING * FULL, SHARING *

000381 ** If RTE high-level qualifier of the production runtime (RK*)000382 ** libraries is different from PARMGEN RTE_PLIB_HILEV qualifier,000383 ** then specify. Otherwise, default is the PARMGEN RTE_PLIB_HILEV000384 ** qualifier. For an ICAT-to-PARMGEN converted RTE, RTE_HILEV and000385 ** RTE_VSAM_HILEV are set to the same RTE HLQ previously used000386 ** prior to conversion.000387 RTE_HILEV IBM.ITM62351000388 RTE_VSAM_HILEV IBM.ITM62351000389000390 ** Required if RTE_TYPE is SHARING:000391 ** Specify the Non-VSAM HLQ in the "RTE_X_HILEV_SHARING" of the000392 ** RTE being shared to by LPAR1 RTE.000393 ** For RTE_SHARE parameter, specify "SMP" value if this RTE is sharing000394 ** with SMP/E target libraries.000395 ** Otherwise, specify the name of the shared-to RTE in the "RTE_SHARE"000396 ** parameter.000397 RTE_X_HILEV_SHARING "IBM.ITM62351"000398 RTE_SHARE "BASEA"

000400 ** (Optional) Only valid when RTE_TYPE is SHARING, and RTE_SHARE is000401 ** not SMP. Specify "Y" to include shared runtime datasets in the000402 ** RTE Load job.000403 RTE_LOAD_SHARED_LIBS "Y"

Important: In sharing runtime environments where RTE_LOAD_SHARED_LIBS has been set to N, someof the IEBCOPY steps that refresh the read-only libraries are not generated as part of the KCIJPLOD job.However, these steps are generated in the KCIJPLOD job for the designated master runtime environment(where RTE_LOAD_SHARED_LIBS has been set to Y). Examples of these types of IEBCOPY steps thatwill not be generated are as follows.


EDIT IBM.ITM62351.LPAR1.WKANSAMU(KCIJPLOD)Command ===>000356 //KANEXEC EXEC PGM=IEBCOPY,REGION=0M000357 //SYSPRINT DD SYSOUT=*000358 //TKANEXEC DD DISP=SHR,000359 // DSN=IBM.ITM62351.TKANEXEC000360 //RKANEXEC DD DISP=SHR,000361 // DSN=IBM.ITM62351.BASEA.RKANEXEC000362 //SYSUT3 DD UNIT=3390,SPACE=(TRK,(15,15))000363 //SYSUT4 DD UNIT=3390,SPACE=(TRK,(15,15))000364 //SYSIN DD *000365 COPY INDD=((TKANEXEC,R)),OUTDD=RKANEXEC000366 COPY INDD=RKANEXEC,OUTDD=RKANEXEC000367 /*000368 //KANOSRC EXEC PGM=IEBCOPY,REGION=0M000369 //SYSPRINT DD SYSOUT=*000370 //TKANOSRC DD DISP=SHR,000371 // DSN=IBM.ITM62351.TKANOSRC000372 //RKANOSRC DD DISP=SHR,000373 // DSN=IBM.ITM62351.BASEA.RKANOSRC000374 //SYSUT3 DD UNIT=3390,SPACE=(TRK,(15,15))000375 //SYSUT4 DD UNIT=3390,SPACE=(TRK,(15,15))000376 //SYSIN DD *000377 COPY INDD=((TKANOSRC,R)),OUTDD=RKANOSRC000378 COPY INDD=RKANOSRC,OUTDD=RKANOSRC000379 /*000380 //KANWENU EXEC PGM=IEBCOPY,REGION=0M000381 //SYSPRINT DD SYSOUT=*000382 //TKANWENU DD DISP=SHR,000383 // DSN=IBM.ITM62351.TKANWENU000384 //RKANWENU DD DISP=SHR,000385 // DSN=IBM.ITM62351.BASEA.RKANWENU000386 //SYSUT3 DD UNIT=3390,SPACE=(TRK,(15,15))000387 //SYSUT4 DD UNIT=3390,SPACE=(TRK,(15,15))000388 //SYSIN DD *000389 COPY INDD=((TKANWENU,R)),OUTDD=RKANWENU000390 COPY INDD=RKANWENU,OUTDD=RKANWENU000391 /*

How to: Customize the RTE_BASE_MIDLEVWith the Configuration Tool method, you customized the RTE_BASE_MIDLEV parameter to tell theConfiguration Tool what to name the base runtime environment. With PARMGEN, there is no need tocustomize the RTE_BASE_MIDLEV parameter. So long as the RTE_SHARE andRTE_X_HILEV_SHARING parameters are specified for RTE_TYPE=SHARING, PARMGEN creates boththe sharing runtime environment and the runtime environment it shares with. Allocating and loading theruntime environments it shares with are performed as part of the same setup for the sharing runtimeenvironment.

With the Configuration Tool, it is a two-phase process to create, first, the base runtime environment, thenthe runtime environment that will share the base runtime environment’s setup. With PARMGEN, sharedruntime environments go through the process of creating both the shared-to and sharing runtimeenvironment in one PARMGEN setup, This design obviates the need to customize theRTE_BASE_MIDLEV in PARMGEN. The RTE_BASE_MIDLEV parameter is used only during theConfiguration Tool to PARMGEN conversion using the KCIJPCNV conversion job.

To illustrate:v With the Configuration Tool method, the base runtime environment is called PLEXNAME. Its base

runtime environment's high-level qualifier is IBM.ITM62351, making IBM.ITM62351.PLEXNAME.RK*the base runtime environment's read-only base runtime libraries (copies of the targets like RKANMOD,RKANMODL, RKANPENU, and so on).


v The sharing LPAR runtime environment is called TESTLPAR; it shares the PLEXNAME base runtimeenvironment. Its high-level qualifier is IBM.ITM62351, making IBM.ITM62351.TESTLPAR.RK* theruntime environment-specific runtime libraries such as RKANPARU, RKANMODU, RKANDATV, andso forth.

With the Configuration Tool, this scenario translates to two batch members:v Runtime environment batch deck #1 (TESTLPAR sharing runtime environment that shares PLEXNAME

base libraries):

IBM.ICAT.INSTJOBS(TESTLPAR)===>

000004 RTE_TYP SHARING000005000006 ** If RTE_TYP is SHARING:000007 RTE_SHARE PLEXNAME000008 **000009 ** RTE global defaults:000010 RTE_HILEV IBM.ITM62351000011 RTE_VSAM_HILEV IBM.ITM62351000012000013 ** (Optional) Only valid when RTE_TYP is BASE:000014 **RTE_BASE_MIDLEV000015000016 RTE_VOL PRI102000017 RTE_VSAM_VOL PRI102000018 RTE_UNIT 3390000019 RTE_SMS_STOR_CLAS SCSTD000020 RTE_SMS_VSAM_STOR_CLAS SCSTD000021 RTE_SMS_MGMT_CLAS MCSTD000022 RTE_SMS_VSAM_MGMT_CLAS MCSTD000023 RTE_PDSE N

v Runtime environment batch deck #2 (PLEXNAME base runtime environment):

IBM.ICAT.INSTJOBS(PLEXNAME)Command ===>000004 RTE_TYP BASE000005 **000006 ** RTE global defaults:000007 RTE_HILEV IBM.ITM62351 <-- in PARMGEN, this becomes//* RTE_X_HILEV_SHARING

000008 RTE_VSAM_HILEV IBM.ITM62351

000009 RTE_BASE_MIDLEV PLEXNAME <-- in PARMGEN, this becomes RTE_SHARE

000010 RTE_VOL PRI101 <-- in PARMGEN, this becomes//* RTE_X_SMS_VOLUME_SHARE

000011 RTE_VSAM_VOL PRI101 <-- in PARMGEN, this becomes//* RTE_X_SMS_VSAM_VOLUME_SHARE

000012 RTE_UNIT 3390 <-- in PARMGEN, this becomes//* RTE_X_SMS_UNIT_SHARE

000013 RTE_SMS_STOR_CLAS SCSTD <-- in PARMGEN, this becomes//* RTE_X_SMS_STORCLAS_SHARE

000014 RTE_SMS_VSAM_STOR_CLAS SCSTD <-- in PARMGEN, this becomes//* RTE_X_SMS_VSAM_STORCLAS_SHARE

000015 RTE_SMS_MGMT_CLAS MCSTD <-- in PARMGEN, this becomes//* RTE_X_SMS_MGMTCLAS_SHARE

000016 RTE_SMS_VSAM_MGMT_CLAS MCSTD <-- in PARMGEN, this becomes//* RTE_X_SMS_VSAM_MGMTCLAS_SHARE

000017 RTE_PDSE Y


During conversion to PARMGEN, the KCIJPCNV job ensures it reads both the INSTJOBS(PLEXNAME)and INSTJOBS(TESTLPAR) members so it can build one composite TESTLPAR PARMGEN WCONFIGprofile that automatically populates the base runtime environment-specific RTE_X_HILEV_SHARING,RTE_SHARE, and RTE_X_SMS_* shared parameters.



Appendix A. Product codes

This appendix lists the Kpp products and the IBM Tivoli Monitoring or OMEGAMON product each oneidentifies

KAH IBM Tivoli System Automation for z/OS

KC5 IBM Tivoli OMEGAMON XE for CICS on z/OS

KDO IBM Tivoli Decision Support for z/OS

KDS Tivoli Enterprise Monitoring Server

KD4 IBM Tivoli Composite Application Manager for SOA

KD5 IBM Tivoli OMEGAMON XE for DB2 PE/PM

KGW IBM Tivoli OMEGAMON XE for CICS TG on z/OS

KHL IBM OMEGAMON z/OS Management Console

KI5 IBM Tivoli OMEGAMON XE for IMS on z/OS

KMC IBM Tivoli OMEGAMON XE for Messaging: WebSphere MQ Configuration

KMQ IBM Tivoli OMEGAMON XE for Messaging: WebSphere MQ Monitoring

KM5 IBM Tivoli OMEGAMON XE on z/OS

KNA IBM Tivoli NetView for z/OS Agent

KN3 IBM Tivoli OMEGAMON XE for Mainframe Networks

KQI IBM Tivoli OMEGAMON XE for Messaging - WebSphere Message Broker

KRG IBM Tivoli Advanced Audit for DFSMShsm

KRH IBM Tivoli Advanced Reporting and Management for DFSMShsm

KRJ IBM Tivoli Advanced Allocation Management for z/OS

KRK IBM Tivoli Automated Tape Allocation Manager for z/OS

KRN IBM Tivoli Advanced Catalog Management for z/OS

KRV IBM Tivoli Advanced Backup and Recovery for z/OS

KRW IBM Tivoli Tape Optimizer for z/OS

KS3 IBM Tivoli OMEGAMON XE for Storage on z/OS

KWO IBM Tivoli OMEGAMON DE on z/OS: OMEGAVIEW and OMEGAVIEW II

KYN ITCAM for Application Diagnostics on z/OS



Appendix B. PARMGEN utilities

PARMGEN provides several utilities to facilitate the configuration process.

Start the Workflow user interfaceThe Parameter Generator (PARMGEN) Workflow user interface steps you through the process ofconfiguring and maintaining runtime environments.

About this task

Use the following procedure to start the Workflow user interface:

Procedure1. Launch the interface using the following command:

EX ’gbl_target_hilev’.TKANCUS’

The Welcome screen for the z/OS Installation and Configuration Tools is displayed:

2. Select 5 (Configure z/OS products with Parameter Generator Workflow). The main ParameterGenerator (PARMGEN) Workflow (KCIP@PG0) panel is displayed:

Welcome to the z/OS Installation and Configuration Tools forIBM Tivoli Management Services (TMS) dependent products

Option ===>

Read/Print Checklists prior to installation and configuration:

1. Checklist: Planning and Acquisition2. Checklist: Prepare the system3. Checklist: Review the product components & installation steps

4. SMP/E-install z/OS products with Install Job Generator (JOBGEN)5. Configure z/OS products with Parameter Generator Workflow (PARMGEN)

6. Checklist: Complete the post-configuration steps

7. About joining the community: Service Management Connect (SMC)

P. Print checklist(s) selectively



In the top section of the panel, you specify the parameters specific to the configuration and runtimeenvironment that you are creating or modifying. The bottom part of the panel provides a menu ofoptions for performing the tasks that must be completed to create, update, and maintain a functioningruntime environment. The Workflow interface informs you about the status of each task and when thestatus was last changed.

What to do next

Identify the runtime environment you want to work with, then proceed with the appropriate steps for theconfiguration or maintenance scenario you are performing.

XF edit macroThe XF (“exclude find”) macro is useful in cases where you want to EXCLUDE certain parameters whenediting PARMGEN’s configuration profiles. For example, you can EXCLUDE all parameters for startedtasks, then FIND all occurrences of these parameters so you can quickly issue a CHANGE ALLcommand.

IBM provides an XF macro with PARMGEN for your use. The macro comprises the following commands:ISREDIT MACRO (FARG)ISREDIT EXCLUDE ALLISREDIT F &FARG ALL

Example1. Do an EXCLUDE FIND of all *_STC parameters in the WCONFIG(%RTE_NAME%) PARMGEN

runtime environment profile.

KCIP@PG0 ------ PARAMETER GENERATOR (PARMGEN) WORKFLOW - WELCOMEOption ===> Scroll ===> PAGEEnter PARMGEN parameter values appropriate for your environment:GBL_USER_JCL: ____________________________________________

PARMGEN common/global library for RTEs (CONFIG DD lib. in STCs)RTE_PLIB_HILEV: ________________________

High-Level Qualifier (HLQ) of work libraries (IK*,WCONFIG,WK*)RTE_NAME: ________ (Type ? for a list of configured RTEs)



1. KCIJPCFG Set up PARMGEN work environment for an RTE.2. $JOBINDX Review PARMGEN job index.3. KCIJPCCF Clone customized WCONFIG members. (COND)4. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup profile (COND)6. KCIJPMC2 Merge profile from model RTE. (COND)7. KCIJPCNV Convert an ICAT RTE Batch member. (COND)8. Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. Create the RTE members and jobs. RC= 00004 2012/10/1111. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)


Figure 3. The PARMGEN Workflow main panel


EDIT TSTEST.&userid.&rtename.WCONFIG(&rte)Command ===>XF _STC Scroll ===> CSR****** ***************************** Top of Data- - - - - - - - - - - - - - - - - - 443 Line(s) not displayed000444 RTE_STC_PREFIX CANS- - - - - - - - - - - - - - - - - - - 29 Line(s) not displayed000515 RTE_CANSETE_STC CANSETE- - - - - - - - - - - - - - - - - - - 2 Line(s) not displayed000518 RTE_CANSCN_STC CANSCN- - - - - - - - - - - - - - - - - - - 87 Line(s) not displayed000625 KDS_TEMS_STC CANSDSST****** **************************** Bottom of Data

2. Customize all *_STC started task parameters using the TSS1 naming convention by changing allCANS references to TSS1 as shown in the following example:

EDIT TSTEST.&userid.&rtename.WCONFIG(&rte)Command ===>C ’ CANS’ ’ TSS1’ ALL+ Scroll ===> CSR

KCIRPLBS online help macroThe KCIRPLBS online help macros provides help for parameters in the configuration profiles. After themacro is set up, help can be invoked by pressing setting the cursor on a parameter and pressing F14.

To set up the help macro, copy KCIRPLBS from %GBL_TARGET_HILEV%.TKANCUS to your SYSPROCconcatenation. To find your SYSPROC concatenation, enter TSO ISRDDN on the ISPF command line.Note that after you copy the macros to your SYSPROC concatenation, you can run them directly from thecommand line without specifying the fully qualified library name.

Tip: An alternative to copying KCIRPLBS set-up macro to your SYSPROC concatenation is to execute theREXX program directly from your %GBL_TARGET_HILEV%.TKANCUS library by executing thefollowing command: ==> TSO EXEC ’%GBL_TARGET_HILEV%.TKANCUS(KCIRPLBS)’ .

To invoke the help:1. Enter TSO KCIRPLBS at the command line to run the help macro.2. If necessary, enter PFSHOW ON at the command line to display the PF keys.3. Place the cursor anywhere on the line containing the parameter for which you want help text to be

displayed, and press F14=ParmHelp key.

Other sources of help for customizing the configuration profile include the following:v Comments in the configuration profilev IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Parameter Reference

v PARMGEN Technote at http://www.ibm.com/support/docview.wss?uid=swg21417935v Product-specific Parameter Reference Guide

Appendix B. PARMGEN utilities 137



Appendix C. System variables

PARMGEN configuration supports the same system symbolics as the Configuration Tool supports. Inaddition, it supports all static system symbols, KCIPARSE PARMGEN-extracted symbols, anduser-defined symbols. System variable support for a runtime environment is enabled by setting theRTE_SYSV_SYSVAR_FLAG in the WCONFIG(%RTE_NAME%) LPAR configuration profile to Y.

If system variable support is enabled, you can use the following types of symbols:v Typical static system symbols (those defined in SYS1.IPLPARM, such as &SYSNAME and

&SYSCLONE).You can use these symbolics as parameter values in the configuration profile so long as you specifytheir values using the following syntax:& || VARNAME || .

For example, to use a static symbol such as &SYSNAME for the PARMGEN CONFIG RTE_NAMEparameter, specify &SYSNAME., as shown in the following example:

000001 RTE$ BEGIN *------------ CONFIGURATION TOOL V310000002 ** ============================ ====================000003 ** PARMGEN CONFIG Parameter PARMGEN CONFIG Value000004 ** ============================ ====================000005 RTE_NAME "&SYSNAME."

v KCIPARSE-extracted symbols.The PARMGEN process has built-in application program interfaces (APIs) to extract system-relatedinformation such as IP network address, IP address, VTAM network ID, and so forth. On the Submit$PARSE Batch Jobs To Complete PARMGEN Setup panel, you can review and submit the $PARSEDVjob to get a list of symbolics that you can use as PARMGEN configuration values.The $PARSEDV job generates a $SYSVAR1 output member and stores it in the WCONFIG library. Thereport lists all &SYS* symbolics (TYPE:CE (CHAR extracted) and TYPE:IE (INTEGER extracted)symbolics) that were extracted by KCIPARSE for use as system variables. When executing anyKCIPARSE job, (the KCIJPCFG, KCIJPUP1, and $PARSE* jobs, for example), review the SYSVROUTDDNAME output for a full listing.For example, to use a KCIPARSE-extracted symbol such as &SYSIPHOSTNAME for the PARMGENCONFIG RTE_TCP_HOST parameter, specify &SYSIPHOSTNAME., as shown in the following example:

000012 ** ============================ ====================000013 ** PARMGEN CONFIG Parameter PARMGEN CONFIG Value000014 ** ============================ ====================000015 RTE_TCP_HOST "&SYSIPHOSTNAME."

v User-defined symbolics.You may reference any symbolics that your site defines as long so the PARMGEN configuration profileparameter value is not used as any PROC symbol in a started task.For example, to use a generic user symbol such as &HUB_HOST for the PARMGEN CONFIGKDS_HUB_TCP_HOST parameter, specify &HUB_HOST., as shown in the following example:

000021 KDS$ BEGIN *-- TIVOLI ENTERPRISE MONITORING SERVER000022 ** ============================ ====================000023 ** PARMGEN CONFIG Parameter PARMGEN CONFIG Value000024 ** ============================ ====================000025 KDS_HUB_TCP_HOST "&HUB_HOST."


GBL_USER_JCL(%RTE_NAME%) system variables resolution member

The GBL_USER_JCL(%RTE_NAME%) system variables configuration profile defines the symbols andtheir resolved values. This profile must be customized if the runtime environment is enabled for systemvariables under the following conditions:1. If you are referencing user-defined symbols.2. If you specified Y for the RTE_X_SYSV_OVERRIDE_SYMBOLS parameter in the WCONFIG(

%RTE_NAME%) LPAR profile.If you elect to enable overrides of symbols, you must define all types of symbolics in this memberand the strings the symbolics resolve to, regardless of whether this is a system, aKCIPARSE-extracted, or a user-defined symbol. Review the WCONFIG(%RTE_NAME%) usage notesfor the RTE_X_SYSV_OVERRIDE_SYMBOLS parameter.

Runtime parts in system variables mode

The following runtime elements are involved in processing when the runtime environment is in systemvariable mode.

Runtime membersWhen the $PARSESV job creates the runtime members and KCIJV* and KCIJP* jobs in theruntime environment’s WK* work libraries, the runtime members are created with a reference tothe symbolics, where applicable.

KCIJV* PARMGEN jobsAfter the $PARSESV job creates the runtime members and KCIJV* and KCIJP* jobs in the runtimeenvironment's WK* work libraries, the KCIJV* jobs are ready for submission.

For example, the KCIJPALO RTE Build/Allocation job has an equivalent KCIJVALO job, whichsimply submits KCIJPALO after a KCIPARSE step is performed between KCIJPALO submissions.This processing is required because references in the KCIJPALO job may be using symbolics thatneed to be resolved before submitting the subsequent job. Otherwise, if symbolics are used forthe RTE_HILEV or RTE_NAME parameters, the job will encounter a JCL error as these parametervalues are used directly in the KCIJP* jobs. Thus, a preprocessor job that resolves all symbolicsthe job may contain is needed. The KCIJVALO equivalent job performs the symbolic substitutionprior to submitting the processed KCIJPALO from a temporary dataset to the internal reader.

Product started tasks

The $PARSESV job generates the product started tasks in the WKANSAMU library withadditional imbeds added to a typical product started task:v The KCIPARSE step imbed performs the symbolic substitution step.v The RKANPAR/RKANCMD DDNAME imbed concatenates either the physical runtime

libraries (xKANCMDU, xKANPARU) when the runtime environment is not in system variablesmode, or the temporary libraries where the KCIPARSE step has resolved the symbolicsreferenced in the physical runtime libraries.

v The RKPDIN DDNAME imbed concatenates either the physical xKANPARU PersistentDatastore command files (KppPG, KppPCTL) when the runtime environment is not in systemvariables mode or the temporary libraries where the Persistent Datastore command files(KppPG, KppPCTL) have been processed for symbolics.

Post-KCIPARSE processing in the running started taskThe RKLVLOG DDNAME of the started task gets passed the resolved values of the symbolicspecified, whether this is a typical static symbol, a KCIPARSE-extracted symbol, or a user-definedsymbol.


Additional considerations for using system variables

The following PARMGEN profile parameters support symbolics as their parameter values. Theseparameter values are referenced in the STC PROC symbols:

RTE_NAMEUsed as the STC PROC SYS=symbol parameter.

RTE_HILEVUsed as the STC PROC RHILEV=symbol parameter.

RTE_VSAM_HILEVUsed as the STC PROC RVHILEV=symbol parameter.

RTE_X_HILEV_SHARINGUsed as part of the STC PROC BASEHLEV=symbol parameter.

RTE_SHAREUsed as part of the STC PROC BASEHLEV=symbol parameter.

Any PARMGEN profile parameters that have VTAM APPLIDs (Kpp_*_VTAM_APPL_*) are applicable to&stc_prefix.M2RC and &stc_prefix.TOM, as well as the STC PROC APPL=symbol parameter.

The following additional symbolics are available for OMEGAMON XE for IMS on z/OS sites:

KI2_I1nn_CLASSIC_IMSIDUsed in the OMEGAMON XE for IMS on z/OS Classic interface's STC PROC IMSID=symbolparameter.

KI2_I1nnn_CLASSIC_MPREFIXUsed in the OMEGAMON XE for IMS on z/OS Classic interface's STC PROC MPREFIX=symbolparameter.

Note: Use caution when specifying user-defined symbols (as opposed to static symbols) for any of theseconfiguration profile parameters. JCL rules that govern the use of system symbols state that most systemsymbols cannot be used in batch JCL. In started-task procedures, you will generate a startup JCL error ifyou issue the /START &stc command, as user symbols (&SYSCLONE., for example) referenced as part ofthe STC PROC statement are not recognized by the system. (Static symbols like &SYSNAME. or&SYSCLONE. are defined system-wide).

There are ways to get around this JCL rule by overriding the value of these symbols using the startupcommand or by using the PARMGEN sample composite STC startup member (CANSAPF, by default)and then defining your own PROC symbol overrides. For VTAM_APPL-related parameters, there are noexceptions; these must not use user-defined symbols, as both the started tasks and the VTAM major nodemembers will not work.

Additional considerations for submitting the PARMGEN batch jobs

If system variables are enabled for a runtime environment, there are planning considerations forsubmitting the batch jobs to complete the PARMGEN setup.

Submitting jobs generated by the $PARSE* job in WKANSAMU (option 11 on the Parameter Generator(PARMGEN) Workflow - Welcome menu) is a follow-on step to customizing the configuration profilesmembers (step 8 ). Whether the PARMGEN jobs are submitted in the target LPAR where the symbolicsare resolved or submitted in the local LPAR where the PARMGEN runtime environment work is beingset up will depend on how the runtime environment is configured for system variables.

Appendix C. System variables 141

If the runtime environment is enabled for system variables and you are using symbolics in data setnames (RTE_NAME, RTE_HILEV, etc.) in an environment where the PARMGEN work is all done on oneLPAR whereas the production runtime environment runs on a different LPAR:v If you are on the LPAR where the symbolics resolve, submit the jobs as usual.v If you are not on the LPAR where the symbolics resolve, you have two options:

– Option 1: Use the RTE_X_SYSV_OVERRIDE_SYMBOLS parameter.

Setting the RTE_X_SYSV_OVERRIDE_SYMBOLS to Y and defining the symbols and their resolvedvalues in the GBL_USER_JCL(&rte) system variables profiles enables you to submit the PARMGENjobs in the system where the PARMGEN runtime environment work is being done (allocating RTEproduct execution RK* runtime libraries, loading TK* to RK* runtime libraries, and so on).

– Option 2: Specify a /*JOBPARM SYSAFF=xxxx card in your WKANSAMU(KCIJV*) jobcard (where xxxx isthe LPAR system name where you want the submitted jobs to execute).

Specifying a job card allows you to submit LPAR specific jobs while on a different LPAR.JES3 users: Specify the SCHENV=-name parameter to define the name of the Workload Manager (WLM)scheduling environment to associate with the KCIJV* jobs.

Tip: Add the /*JOBPARM SYSAFF=xxxx card to your WCONFIG($JOBCARD) member prior tosubmitting the WCONFIG($PARSESV) job. In this way, the WKANSAMU(KCIJV*) jobs that$PARSESV creates will already contain the JOBPARM card.

Note: Certain sites pose JOBPARM restrictions when directing jobs to execute on production LPARs.Consult your site’s system programmers for more information.

$JOBCARD considerations for using symbolics

The following example shows the default jobcard in the %GBL_TARGET_HILEV%.TKANSAM library:

//*&userid.A JOB (ACCT),’%SYSMEMBER% - NAME’,CLASS=A,//* MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=,REGION=0M//** RTE_NAME=%RTE_NAME%//** SYSJOBNAME=%SYSJOBNAME% SYSMEMBER=%SYSMEMBER%//* Begin - Sample Jobcard: -------------------------------------------//* ****************************************************************//* Primary Source: TKANSAM(KCI$JCRD) User Copy: WCONFIG($JOBCARD)//* Execute JOBCARD macro and/or customize the sample above.//* Notes: 1. The jobcard statements above are commented out by default.//* 2. REGION=0M is recommended.//* 3. SYSJOBNAME/SYSMEMBER values are generated for reference.//* For the first job (KCIJPCFG), these symbolics are not//* resolved on purpose. See KCIJPCFG help panel for more//* information.//* 4. RTE_NAME value is generated for reference.//* ****************************************************************//* End - Sample Jobcard: ---------------------------------------------

Notice that symbols such as SYSJOBNAME and SYSMEMBER extracted by the KCIPARSE program aregenerated for reference only. For the KCIJPCFG job, these symbolics are intentionally not resolved, as theKCIJPCFG job must copy the resulting $JOBCARD member from the GBL_USER_JCL library toWCONFIG. The symbols must be preserved, so jobs run after the initial KCIJPCFG job can takeadvantage of the resolved values. For example, the KCIJPCFG job generates the KCIJPUP1 job. In thefile-tailored KCIJPUP1 job, its jobcard will generate as follows (based on the IBM-supplied jobcard):

//&userid.A JOB (ACCT),’KCIJPUP1 - NAME’,CLASS=A,// MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID.,REGION=0M//* RTE_NAME=TESTSP23//* SYSJOBNAME=&userid.A SYSMEMBER=KCIJPUP1


Documentation library

This appendix contains information about the publications related to IBM Tivoli Monitoring and to thecommonly shared components of Tivoli® Management Services.

These publications are listed in the following categories:v IBM Tivoli Monitoring libraryv Related publications

See the IBM Tivoli Monitoring Documentation Guide for information about accessing and using thepublications. You can find the Documentation Guide in the IBM Tivoli Monitoring and OMEGAMON® XEInformation Center at http://pic.dhe.ibm.com/infocenter/tivihelp/v61r1/index.jsp. To open theDocumentation Guide in the information center, select Using the publication in the Contents pane.

To find a list of new and changed publications, click What's new on the Welcome page of the IBM TivoliMonitoring and OMEGAMON XE Information Center. To find publications from the previous version ofa product, click Previous versions under the name of the product in the Contents pane.

Shared OMEGAMON XE publicationsThe publications in this library provide information common to OMEGAMON XE products that areinstalled on z/OS.v IBM Tivoli OMEGAMON XE Monitoring Agents on z/OS: Quick Start Guide, GI13-2314

Summarizes the installation and setup of an OMEGAMON XE monitoring agent on z/OS.v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning and Configuration

Guide, SC22-5484

Gives instructions for planning and configuration tasks common to the components of TivoliManagement Services on z/OS and the OMEGAMON XE monitoring agents on z/OS.

v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Upgrade Guide, SC22-5486

Gives instructions for complete and staged upgrades to V4.2.0 and V5.1.0 of the OMEGAMON XEproducts.

v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Parameter Reference,SC22-5482

Provides reference information on parameters used for setting up runtime environments andconfiguring hub and remote Tivoli Enterprise Monitoring Servers on z/OS, including detaileddescriptions of the PARMLIB parameters.

v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: PARMGEN Reference, SC22-5483

Provides detailed instructions and common configuration scenarios for creating and maintainingruntime environments using the PARMGEN configuration method.

v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Tivoli OMEGAMON Enhanced 3270User Interface Guide, SC22-5487

Describes the features of the OMEGAMONenhanced 3270 user interface and provides operatinginstructions and reference material.

v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: End-to-End Response Time FeatureReference, SC27-2303

Provides instructions and reference information for the End-to-End Response Time Feature, whichsupplies response time data to several OMEGAMON XE products.


http://pic.dhe.ibm.com/infocenter/tivihelp/v61r1/index.jsp

v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Reports for Tivoli Common Reporting,SC27-2304

Explains how to use the Tivoli Common Reporting tool to create reports from data displayed in theTivoli Enterprise Portal and stored in the Tivoli Data Warehouse database.

IBM Tivoli Monitoring libraryThe publications in this library provide information about the components of Tivoli Management Services(IBM Tivoli Monitoring) that are installed on distributed platforms.v Quick Start Guide

Introduces the components of IBM Tivoli Monitoring.v Installation and Setup Guide, SC22-5445

Provides instructions for installing and configuring IBM Tivoli Monitoring components on Windows,Linux, and UNIX systems.

v High Availability Guide for Distributed Systems, SC22-5455Gives instructions for several methods of ensuring the availability of the IBM Tivoli Monitoringcomponents.

v Administrator's Guide, SC22-5446Describes the support tasks and functions required for the Tivoli Enterprise Portal Server and clients,including Tivoli Enterprise Portal user administration.

v Command Reference, SC22-5448Provides detailed syntax and parameter information, as well as examples, for the commands you canuse in IBM Tivoli Monitoring.

v Messages, SC22-5450Lists and explains messages generated by all IBM Tivoli Monitoring components and by z/OS-basedTivoli Management Services components (such as Tivoli Enterprise Monitoring Server on z/OS, theOMEGAMON enhanced 3270 user interface, and TMS:Engine).

v Troubleshooting Guide, GC22-5449Provides information to help you troubleshoot problems with the software, including TivoliManagement Services on z/OS components.

v Tivoli Enterprise Portal online helpProvides context-sensitive reference information about all features and customization options of theTivoli Enterprise Portal. Also gives instructions for using and administering the Tivoli EnterprisePortal.

v Tivoli Enterprise Portal User's Guide, SC22-5447Complements the Tivoli Enterprise Portal online help. The guide provides hands-on lessons anddetailed instructions for all Tivoli Enterprise Portal features.

v Agent Builder User's Guide, SC32-1921Explains how to use the Agent Builder for creating monitoring agents and their installation packages,and for adding functions to existing agents.

v Tivoli Universal Agent User’s Guide, SC32-9459Introduces you to the IBM® Tivoli Universal Agent, an agent of IBM Tivoli Monitoring. The IBM TivoliUniversal Agent enables you to use the monitoring and automation capabilities of IBM TivoliMonitoring to monitor any type of data you collect.

v Performance Analyzer User’s Guide, SC27-4004Explains how to use the Performance Analyzer to understand resource consumption trends, identifyproblems, resolve problems more quickly, and predict and avoid future problems.

v IBM Tivoli Universal Agent API and Command Programming Reference Guide, SC32-9461


Explains the procedures for implementing the IBM Tivoli Universal Agent APIs and providesdescriptions, syntax, and return status codes for the API calls and command-line interface commands.

Documentation for the base agentsIf you purchased IBM Tivoli Monitoring as a product, you received a set of base monitoring agents aspart of the product. If you purchased a monitoring agent product (for example, an OMEGAMON XEproduct) that includes the commonly shared components of Tivoli Management Services, you did notreceive the base agents.

The following publications provide information about using the base agents.v Operating system agents:

– Windows OS Agent User's Guide, SC22-5451– UNIX OS Agent User's Guide, SC22-5452– Linux OS Agent User's Guide, SC22-5453– i5/OS Agent User's Guide, SC22-5454– UNIX Log Agent User's Guide, SC32-9471

v Agentless operating system monitors:– Agentless Monitoring for Windows Operating Systems User's Guide, SC23-9765– Agentless Monitoring for AIX Operating Systems User's Guide, SC23-9761– Agentless Monitoring for HP-UX Operating Systems User's Guide, SC23-9763– Agentless Monitoring for Solaris Operating Systems User's Guide, SC23-9764– Agentless Monitoring for Linux Operating Systems User's Guide, SC23-9762

v Warehouse agents:– Warehouse Summarization and Pruning Agent User's Guide, SC22-5457– Warehouse Proxy Agent User's Guide, SC22-5456

v System P agents:– AIX Premium Agent User's Guide, SA23-2237– CEC Base Agent User's Guide, SC23-5239– HMC Base Agent User's Guide, SA23-2239– VIOS Premium Agent User's Guide, SA23-2238

v Other base agents:– Tivoli Log File Agent User’s Guide, SC14-7484– Systems Director base Agent User’s Guide, SC27-2872– Monitoring Agent for IBM Tivoli Monitoring 5.x Endpoint User's Guide, SC32-9490

Other sources of documentationYou can obtain technical documentation about OMEGAMON XE and related products from a number ofadditional sources.v Service Management Connect (SMC)

For introductory information about SMC, see IBM Service Management Connect (http://www.ibm.com/developerworks/servicemanagement).Connect, learn, and share with Service Management professionals. Get access to developers andproduct support technical experts who provide their perspectives and expertise. Using SMC, you can:– Become involved with transparent development, an ongoing, open engagement between external

users and developers of Tivoli products where you can access early designs, sprint demos, productroadmaps, and pre-release code.

Documentation library 145

http://www.ibm.com/developerworks/servicemanagement

– Connect one-on-one with the experts to collaborate and network about Tivoli and Integrated ServiceManagement.

– Benefit from the expertise and experience of others using blogs.– Collaborate with the broader user community using wikis and forums.

The System z community https://www.ibm.com/developerworks/servicemanagement/z/index.htmlshould be of particular interest.

v IBM Integrated Service Management Libraryhttp://www.ibm.com/software/brandcatalog/ismlibrary/IBM Integrated Service Management Library is an online catalog that contains integrationdocumentation and other downloadable product extensions.

v Redbooks®

http://www.redbooks.ibm.com/IBM Redbooks and Redpapers include information about products from platform and solutionperspectives.

v TechnotesTechnotes provide the latest information about known product limitations and workarounds. You canfind Technotes through the IBM Software Support Web site at http://www.ibm.com/software/support/.


https://www.ibm.com/developerworks/servicemanagement/z/index.html

http://www-01.ibm.com/software/brandcatalog/ismlibrary/

http://www.redbooks.ibm.com/

http://www.ibm.com/software/support/

http://www.ibm.com/software/support/

Support information

If you have a problem with your IBM software, you want to resolve it quickly. IBM provides thefollowing ways for you to obtain the support you need:

OnlineGo to the IBM Software Support site at http://www.ibm.com/support/servicerequest and followthe instructions.

IBM Support AssistantThe IBM Support Assistant (ISA) is a free local software serviceability workbench that helps youresolve questions and problems with IBM software products. The ISA provides quick access tosupport-related information and serviceability tools for problem determination. To install the ISAsoftware, go to http://www.ibm.com/software/support/isa.

Troubleshooting GuideFor more information about resolving problems, see the product's Troubleshooting Guide.


http://www.ibm.com/support/servicerequest

http://www.ibm.com/software/support/isa


Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer theproducts, services, or features discussed in this document in other countries. Consult your local IBMrepresentative for information on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead. However, it is the user'sresponsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in thisdocument. The furnishing of this document does not give you any license to these patents. You can sendlicense inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual PropertyDepartment in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where suchprovisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY ORFITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore,this statement might not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication.IBM may make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not inany manner serve as an endorsement of those websites. The materials at those websites are not part ofthe materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.


Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some casespayment of a fee.

The licensed program described in this document and all licensed material available for it are providedby IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement orany equivalent agreement between us.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platform forwhich the sample programs are written. These examples have not been thoroughly tested under allconditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. You may copy, modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing application programs conformingto IBM‘s application programming interfaces.

If you are viewing this information in softcopy form, the photographs and color illustrations might not bedisplayed.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both. If these and other IBM trademarkedterms are marked on their first occurrence in this information with a trademark symbol (® or ™), thesesymbols indicate U.S. registered or common law trademarks owned by IBM at the time this informationwas published. Such trademarks may also be registered or common law trademarks in other countries. Acurrent list of IBM trademarks is available on the Web at “Copyright and trademark information” atwww.ibm.com/legal/copytrade.shtml.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.


http://www.ibm.com/legal/us/en/copytrade.shtml

Index

Special characters$BGL$USR profile 4$PARSExx jobs 106%GBL_USER_JCL%(%RTE_NAME%) 4

Aabout this guide 1auditing function

tracing levels for 47

Ccloned CSI 94configuration profiles 4converting static hub to remote 119

DdeveloperWorks 145DVIPA 39

Eedit macros

IBM-provided 136

Gglobal profile 4

Hhigh-availability hub

DVIPA requirements for 39

IIBM Support Assistant 147imbed files 5installing new versions into 94Integrated Service Management

Library 145ISA 147

KKppSYSIN startup memebers 124KCIJcLOD job 83KCIJPCFG job 99, 113KCIJPLOD job 83, 124, 127KCIJPSEC composite security job 120

Llibraries

OMEGAMON XE sharedpublications 143

LPAR configuration profile 4

Mmaintenance scenarios

adding a new product to an existingRTE 99

apply maintenance to existingenvironment 83

base libraries for the sharing RTE,refreshing 127

configuring a newly addedproduct 99, 129

disabling configuration of a deletedproduct 113

effects of changing PARMGENparameters 106

overriding the default storagelimit 124

performing post-SMP/E maintenancesteps 83

refreshing read-only baselibraries 127

retaining KOBSUPDT security exitsupdates 120

RTE_BASE_MIDLEV parameter 129storage limit, increasing the

default 124upgrading a product to an existing

runtime environment 103upgrading an OMEGAMON to a

production RTE 103using PARMGEN 99

Nnew in this release 5

OOMEGAMON XE for IMS on z/OS

system variables for 139override values 5

Pparameters

GBL_USER_JCL 9, 40RTE_NAME 10, 40RTE_PLIB_HILEV 9, 40

PARMGENmaintenance scenarios 83, 99

adding a new product to anexisting RTE 99

PARMGEN (continued)maintenance scenarios (continued)

base libraries for the sharing RTE,refreshing 127

configuring a newly addedproduct 99

disabling configuration of adeleted product 113

effect of changed parameters 106KOBSUPDT security exits 120naming the base runtime

environment 129overriding the default storage

limit 124refreshing read-only base

libraries 127retaining KOBSUPDT security exits

updates 120RTE_BASE_MIDLEV

parameter 129storage limit, increasing the

default 124upgrading a product to an existing

runtime environment 103upgrading an OMEGAMON to a

production RTE 103scenarios 7

PGN01 8PGN02 24PGN03 39PGN04 52PGN05 66

starting the PARMGEN Workflowuser interface 135

PARMGEN Workflow user interfacestarting 135

product codes 133publications

OMEGAMON XE 143shared 143Tivoli Management Services on

z/OS 143

RRedbooks 145RTE_BASE_MIDLEV parameter 129runtime environments

PLB1SP22 8PLB2SP22 52PLB3SYSG 24PLB4SYSG 66PLBHAHUB 39

Sscenarios

PGN01 8PGN02 24PGN03 39


scenarios (continued)PGN04 52PGN05 66PLB1SP22 8PLB2SP22 52PLB3SYSG 24PLB4SYSG 66PLBHAHUB 39

SELECT MEMBER parameter 106Service Management Connect 145shared publications 143SMC 145Software Support 147static hub 119support assistant 147system variables

referencing 139in started tasks 139in VTAM major node

members 139

TTechnotes 145

WWCONFIG(%RTE_NAME%) profile 4

XXF macro 136


��

Printed in USA

SC22-5483-00

Documents

IBM Tivoli OMEGAMON XE and Tivoli Management Services …...The last two of the options on the menu are utilities. v Option U displays the PARMGEN work libraries (WK*), the GBL_USER_JCL