Scenario PGN01: Creating a full runtime environment with a hub monitoring server and OMEGAMON agents
This scenario creates a full runtime environment comprising a z/OS-based hub monitoring server, OMEGAMON XE monitoring agents, and the OMEGAMON enhanced 3270 user interface.
About this task
- Setting up PARMGEN work environment for the runtime environment
- Updating interim libraries and create the PARMGEN configuration profiles
- Customizing the configuration profiles
- Validating the profile parameter values
- Creating the runtime members and jobs
- Submitting batch jobs to complete the PARMGEN setup
Follow this procedure to create the sample runtime environment.
Procedure
- Set up the PARMGEN work environment.
- Note:On the Parameter Generator (PARMGEN) Workflow main panel, specify values for the GBL_USER_JCL, RTE_PLIB_HILEV, and RTE_NAME fields for this runtime environment. The following example may not accurately reflect the options or fields you see on the screen. It is provided as a sample only.These parameters specify initial setup and global parameter values.
KCIP@PG0 ------ PARAMETER GENERATOR (PARMGEN) WORKFLOW - WELCOME ------ NEW RTE Option ===> 1 Scroll ===> CSR Enter PARMGEN parameter values appropriate for your environment: GBL_USER_JCL: TDITN.IDTST.PARMGEN.JCL_____________________ PARMGEN common/global library to store cross-RTE values for the RTEs created using the same GBL_USER_JCL common library RTE_PLIB_HILEV: TSTEST.CCAPI____________ High-Level Qualifier (&hlq) portion of the PARMGEN libraries: - &hlq.&rte_name.IK*/WK*/WCONFIG PARMGEN work libraries RTE_NAME: PLB1SP22 (Type ? for a list of PARMGEN-created RTEs) Runtime environment (&rte_name) name for this LPAR There are 13 selectable options below: Note: Enter n (1-11) to perform tasks. Status Date Enter 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)- GBL_USER_JCL
- Specifies the name of the
data set of the PARMGEN global user JCL library. If the runtime environment is enabled
for system variables, this data set is concatenated in the CONFIG DDNAME of product started tasks.
If the data set does not exist, you are prompted to correct the name or allocate the data set.
The PARMGEN global user JCL library is also where the PARMGEN process creates the system variables configuration profile. Customization of this member is required if a runtime environment is enabled for system variables and you are using user-defined symbols 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 environment definitions such as KCIJPCFG values and the PARMGEN job status and date in the KCIDJP02 member. If you switch GBL_USER_JCL libraries, ensure that you copy the members to the new GBL_USER_JCL. Otherwise, PARMGEN configuration cannot carry forward information about existing runtime environment definitions tracked in the current GBL_USER_JCL library. However, if you copy the members to the new GBL_USER_JCL, the $GBL$IBM and $GBL$USR global configuration profiles for each runtime environment stored in the runtime environment-specific WCONFIG libraries must be adjusted to point to the new name.In addition, the GBL_USER_JCL library must not be the same library as the runtime environment's WCONFIG runtime environment profile library. The PARMGEN WCONFIG control library is where configuration profiles and other members are stored by the KCIJPUP1 job.
- RTE_PLIB_HILEV
- Specifies the non-VSAM
high-level qualifier that you want to use for the following PARMGEN work libraries:
- WCONFIG control library where configuration profiles and other members are stored by the KCIJPUP1 job.
- Interim staging (IK*) libraries where PARMGEN product runtime members (template versions) are stored by the KCIJPUP1 job.
- Work output (WK*) libraries where customized runtime members and jobs are created by the $PARSE or $PARSESV job.
- RTE_NAME
- Specifies a unique name for the runtime environment that you are configuring. The name that you specify is appended to the RTE_PLIB_HILEV values to make each set of PARMGEN and runtime libraries unique: %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(%RTE%).
- Select option 1 from the main
menu to set up the PARMGEN work libraries for the PLB1SP22 environment.
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 and RTE member name to clone (ex.: &hlq.&rte.WCONFIG(&clone_from)). **or** - If reconfiguring or upgrading this existing PLB3SYSG RTE, specify its values (TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22)) **or** - If converting an ICAT-created RTE to PARMGEN mode, specify the ICAT RTE Batch member location and RTE member (ex.: &hlq.INSTJOBS(PLB1SP22)) Specify the Install Job Generator (JOBGEN) output library if you want PARMGEN to reuse CALLLIBS parameters from the JOBGEN repository: ==> ____________________________________________ (Type ? for last referenced JOBGEN library discovered, if any.) Enter Jobcard data: ==> //&userid.J JOB (ACCT),’%SYSMEMBER% - NAME’,CLASS=A,_____________________ ==> // MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID.,REGION=0M_________________ ==> //** RTE_NAME=%RTE_NAME%________________________________________________ ==> //** SYSJOBNAME=%SYSJOBNAME% SYSMEMBER=%SYSMEMBER%______________________ - Because you are configuring a new runtime environment, leave the first field blank. If
appropriate, specify the Install Job Generator output library and job card data.
If a customized JOBCARD is already available, it is retrieved from the ISPF user profile pool. If not and if you did not specify a JOBGEN output library, the JOBCARD is harvested from &gbl_target_hilev.TKANSAM SMP/E target library where the initial PARMGEN sample JOBCARD default is supplied. If you specified a JOBGEN output library, the JOBCARD information is harvested from there. You can modify the retrieved data as needed. The customized JOBCARD is saved in the ISPF user profile pool and persists across ISPF sessions.
- Press Enter to proceed to the next panel.
If the GBL_USER_JCL data set does not exist, the following verification screen is presented:
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____________________________ - Perform one of the following steps:
- Press Enter to allocate a new data set.
- Specify the data set name and press Enter.
The "Set Up/Refresh PARMGEN Work Environment for an RTE (2 OF 3)" panel (KCIP@PG2) is displayed. - Specify the values as shown in the following example
panel, then press Enter.
Note that specifying values on this panel is necessary only for the first runtime environment. These values are stored for use in the next environment. If you specified the JOBGEN repository in the previous KCIP@PG1 panel, the GBL_TARGET_HILEV and GBL_SYSDA_UNIT fields are filled out automatically, because the PARMGEN process reuses the data from the repository.
KCIP@PG2 SET UP/REFRESH PARMGEN WORK ENVIRONMENT FOR AN RTE (2 OF 3) ------- Command ===> Quick Configuration Mode GBL_USER_JCL: TSTEST.SYSPLEX.PLEX.JCL RTE_PLIB_HILEV: TSTEST.userid .DB2 RTE_NAME: DB2 Enter parameter values appropriate for your environment: UNIT / STORCLAS / VOLSER MGMTCLAS GBL_TARGET_HILEV: TDCI.ZSMSDB2.SMPE__________________ ________ / ________ / HLQ of SMP/E target (TK*) datasets ______ ________ GBL_SYSDA_UNIT: SYSDA___ Work datasets UNIT name GBL_REGION: 0M______ JCL REGION (specify K/M suffix) Note: Type BACK to go back one panel. Type U or UTIL to access utility menu.The Set up PARMGEN Work Environment for an RTE (3 OF 3) panel (KCIP@PG3) is displayed.KCIP@PG3 ---- SET UP PARMGEN WORK ENVIRONMENT FOR AN RTE (3 OF 3) ------------- Command ===> Scroll ===> PAGE Enter parameter values appropriate for the LPAR RTE=PLB1SP22. Press F1=Help for more information. More: - RTE_DESCRIPTION: _____________________________ RTE_SMS_PDSE_FLAG: Y (Y, N) (Allocate Non-VSAM PDSE libs) RTE_SMS_UNIT: __________ (Non-VSAM disk UNIT type) RTE_SMS_VOLUME: __________ (Non-VSAM disk VOLSER) RTE_SMS_MGMTCLAS: __________ (Non-VSAM disk MGMTCLAS) RTE_SMS_STORCLAS: __________ (Non-VSAM disk STORCLAS) RTE_SMS_VSAM_VOLUME: __________ (VSAM disk VOLSER) RTE_SMS_VSAM_MGMTCLAS: __________ (VSAM disk MGMTCLAS) RTE_SMS_VSAM_STORCLAS: __________ (VSAM disk STORCLAS) RTE_TYPE: FULL____ (FULL, SHARING) RTE_HILEV: TDITN.&userid_______________ (&hlq portion of Non-VSAM RK* HLQ=&hlq.&rte_name) RTE_VSAM_HILEV: TDITN.&userid_______________ (&hlq portion of VSAM RK* HLQ=&hlq.&rte_name) If RTE_TYPE is SHARING: RTE_X_HILEV_SHARING: __________________________ (&hlq portion of shared RTE's HLQ=&hlq.&rte_share) RTE_SHARE: ___________________________ ("SMP" value or *&rte_share) (*&rte_share portion of shared RTE's HLQ=&hlq.&rte_share) RTE_LOAD_SHARED_LIBS: Y (Y, N) (Is RTE updater of RO shared libs) If symbolics (system variables or user-defined variables) will be used: RTE_SYSV_SYSVAR_FLAG: N (Y, N) (System variable flag) Security settings: RTE_SECURITY_USER_LOGON: NONE______ (RACF, ACF2, TSS, NAM, None) RTE_SECURITY_FOLD_PASSWORD_FLAG: Y (Y, N) (Fold password to upper case) RTE_SECURITY_CLASS: ____________________________________________ RTE_X_SECURITY_EXIT_LIB: TSTEST.&userid.PLB1SP22.RKANSAMU________________ GBL_DSN_ACF2_MACLIB: ____________________________________________ GBL_DSN_ACF2_MACLIB1: ____________________________________________ Local Tivoli Enterprise Monitoring Server (TEMS) settings in this LPAR RTE: RTE_TEMS_CONFIGURED_FLAG: Y (Y, N) (Configure TEMS in this RTE) RTE_TEMS_NAME_NODEID: PLB1SP22:CMS ___________________ (e.g.,IDTEST:cms) KDS_TEMS_TYPE: HUB___ (Hub, Remote) KDS_TEMS_HA_TYPE: __ (HA=High Availability Hub TEMS type) ITM components' communication-related and started tasks settings: RTE_TCP_PORT_NUM: 1918__________________ (1-65535 port number) RTE_VTAM_APPLID_PREFIX: CTD___________________ (1-4 char.VTAM APPLID prefix) RTE_STC_PREFIX: IBM___________________ (1-4 char.started task prefix) - Specify the appropriate values, then press Enter. Depending
on your screen resolution, you might have to scroll down (PF8) to
see all the parameters. The More: + on the panel indicates that there
is additional content on the panel.)
The values that you specify on this panel are inherited by all the products and components in the runtime environment.
The following are examples of parameters that you might customize:- If you did not want to configure a Tivoli Enterprise Monitoring Server in this environment, set the RTE_TEMS_CONFIGURED_FLAG to N.
- If you have to change the default prefix appended to all started tasks created by the configuration software, or the prefix appended to the VTAM applids used by the product components to conform to site conventions, set the RTE_STC_PREFIX and RTE_VTAM_APPLID_PREFIX parameters.
The next panel, Display PARMGEN Environment Analysis (KCIP@PG4), displays the list of all products installed and available for configuration.
KCIP@PG4 ------------ DISPLAY PARMGEN ENVIRONMENT ANALYSIS - Row 1 to 14 of 14 Command ===> Scroll ===> PAGE Review message traffic before proceeding. These Kpp components are installed into the TSTEST.ITM63053.TKANCUS SMP/E target library and are available for (re)configuration and/or upgrade into the RTE=PLB1SP22. Refer to the next panel ("INCLUDE PRODUCT IN THIS PARMGEN PARMGEN RTE") for a legend of the Kpp components' product names. 34 Components installed in TSTEST.ITM63053.TKANCUS: KAH KC2 KC5 KDF KDO KDS KD2 KD4 KD5 KGW KHL KI2 KI5 KMC KMQ KMV KM2 KM5 KNA KN3 KOB KON KQI KRG KRH KRJ KRK KRN KRV KRW KS3 KT1 KWO KYN End of data - Press Enter to display the Include Products in this
PARMGEN RTE panel (KCIP@PGI).
All the products that have been installed are selected.
- Deselect any products that you do not want to include
in this runtime environment. In the following example, we have excluded all non-OMEGAMON products from the configuration.
KCIP@PGI ------------ INCLUDE PRODUCTS IN THIS PARMGEN RTE - Row 1 to 19 of 26 Command ===> Scroll ===> PAGE Select (/) product(s) to CONFIGURE those product(s) in RTE=$PLB1SP22 All installed products have been preselected (/). Select or deselect products to include or exclude from configuration. When finished, change "N" to "Y" to confirm selections. Confirm ==> N (Y, N) Kpp Product Name/Version ---- ---------------------------------------------------------------------- _ KAH System Automation Monitoring Agent V350 / KC5 OMEGAMON for CICS on z/OS V530 _ KDO Tivoli Decision Support for z/OS Agent V181 / KDS Tivoli Enterprise Monitoring Server V630 _ KD4 ITCAM for SOA Agent V711 / KD5 OMEGAMON for DB2 PE/PM V540 / KGW OMEGAMON for CICS TG on z/OS V530 / KI5 OMEGAMON for IMS on z/OS V530 / KJJ OMEGAMON for JVM V540 / KMC OMEGAMON for Messaging - WebSphere MQ Configuration V730 / KMQ OMEGAMON for Messaging - MQ V730 / KM5 OMEGAMON for z/OS V530 / KNA NetView for z/OS Agent V621 / KN3 OMEGAMON for Networks V530 / KOB OMEGAMON Enhanced 3270 User Interface V730 / KQI OMEGAMON for Messaging - Integration Bus V730 _ KRG Advanced Audit for DFSMShsm Agent V260 _ KRH Advanced Reporting and Management for DFSMShsm Agent V260 _ KRJ Advanced Allocation Management Agent V330 _ KRK Automated Tape Allocation Manager for z/OS Agent V330 _ KRN Advanced Catalog Management Agent V260 _ KRV Advanced Backup and Recovery for z/OS Agent V240 _ KRW Tape Optimizer for z/OS Agent V220 / KS3 OMEGAMON for Storage on z/OS V540 / KWO OMEGAMON Dashboard Edition on z/OS - OMEGAVIEW V530 _ KYN ITCAM for Application Diagnostics, TEMA V710.03 End of data - Specify Y in the Confirm ==> field and
press Enter. The file-tailored
%GBL_USER_JCL%(KCIJPCFG)job is displayed. - Review the notes in the KCIJPCFG job and submit it.
After you return to the Workflow main panel, you see a jobstep indicator on the 1> line. This indicates that this is the last step you performed. Also, notice the updated Status and Date for the KCIJPCFG job.
- (Optional) Select option 2 ($JOBINDX Review PARMGEN job index) on the PARMGEN Workflow panel to review the job index for planning purposes.
- Update the interim libraries and create the configuration
profiles:
- Select option 4,
KCIJPUP1 Update interim libraries and create profiles, from the Workflow main menu.The KCIJPUP1 job is displayed. - Review the notes section, then submit the KCIJPUP1 job.
- Select option 4,
- Customize the PARMGEN profiles:
- On the main PARMGEN Workflow panel, select 8.
The Customize PARMGEN Configuration Profile Members panel is displayed.
The applicable profiles for configuration are the LPAR profile (option 1) and the global parameters profile (option 2).KCIP@PG6 ------ CUSTOMIZE PARMGEN CONFIGURATION PROFILE MEMBERS --------------- Option ===> Review/Customize the LPAR-specific and global configuration values: *1. PLB1SP22 RTE LPAR-specific CONFIG profile in WCONFIG (User copy) *2. $GBL$USR Global parameters CONFIG profile in WCONFIG (User copy) Review/Customize symbolic resolution values in option (3) for applicable system or user-defined variables used in option (1) PLBHAHUB LPAR-specific and option (2) $GBL$USR global user profiles above: *3. PLB1SP22 System Variables CONFIG profile in GBL_USER_JCL (TDITN.IDTST.PARMGEN.JCL) *Note: The PARMGEN configuration profiles above are preserved. (Reference) IBM-supplied default profiles (refreshed by KCIJPUP1 job): 4. $CFG$IBM RTE LPAR-specific CONFIG profile in WCONFIG (IBM copy) 5. $GBL$IBM Global parameters CONFIG profile in WCONFIG (IBM copy) 6. $SYSIN $PARSE/$PARSESV SYSIN controls (CONFIG/SELECT MEMBER) Press F1=Help for more information. Type UTIL to access utility menu. - Select option 1 to display the
PLB1SP22 profile and complete the following steps to customize the
profile:
- Perform 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 Copy 000006 * TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22) - Customer Copy 000007 * 000008 * PURPOSE: 000009 * $CFG$IBM/PLB1SP22 members are the default composite PARMGEN 000010 * configuration profiles which contain parameter values for all the 000011 * product parameters in a runtime environment (RTE). $CFG$IBM is 000012 * the maintenance copy of the PLB1SP22 default copy and 000013 * is available for reference only. $CFG$IBM is always refreshed 000014 * during maintenance of any new or changed product configuration 000015 * parameters. . . 000180 * SECTION: USER PROLOG (OPTIONAL) 000181 * ********************************************************************* 000182 *+---+-------------------------------------------------+--------+----+* 000183 *|NO.| CHANGE DESCRIPTION | DATE | ID |* 000184 *+---+---------------------------------------+---------+--------+----+* 000185 *|@nn| |mm/dd/yy| xx |* 000186 * ********************************************************************* - If you intend to enable self-describing agent processing, which requires z/OS®
UNIX System Services directories, customize the
RTE_USS_RTEDIR parameter.The GBL_ parameters are found in the WCONFIG($GBL$USR) member for additional customization.
SP22 TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22) Command ===> Scroll ===> CSR 000488 ** (Optional) If any products to be configured in this RTE require 000489 ** Unix System Services (USS) directories created, specify the main RTE 000490 ** HFS/zFS USS directory (#rtedir): 000491 ** Note: This is also required if you are enabling the Self-describing 000492 ** 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_RTEDIR 000497 ** - KDS_KMS_SDA 000498 ** - KDS_TEMA_SDA 000499 ** - Kpp_AGT_TEMA_SDA (per Kpp Agent exploiting SDA) 000491 RTE_USS_RTEDIR "/tstest" - (Optional) Customize RTE_VTAM_GBL_MAJOR_NODE.
SP22 TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22) - 01.00 Columns 00001 00072 Command ===> C KCANDLE1 TSSND122 ALL Scroll ===> CSR 000480 RTE_VTAM_GBL_MAJOR_NODE KCANDLE1 - Change port numbers according to your site's convention by performing
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 00072 Command ===> XF _PORT Scroll ===> CSR ****** ***************************** Top of Data ****************************** - - - - - - - - - - - - - - - - - - 485 Line(s) not Displayed 000486 RTE_TCP_PORT_NUM 1918 - - - - - - - - - - - - - - - - - - - 13 Line(s) not Displayed 000654 KDS_TEMS_TCP_PIPE_PORT_NUM 1918 * IP.PIPE 000655 KDS_TEMS_TCP_UDP_PORT_NUM 1918 * IP.UDP 000656 KDS_TEMS_TCP_PIPE6_PORT_NUM "" * IP.PIPE for IPV6 000657 KDS_TEMS_TCP_UDP6_PORT_NUM "" * IP.UDP for IPV6 000658 KDS_TEMS_TCP_PIPES_PORT_NUM "" * Secure IP.PIPE 000659 KDS_TEMS_TCP_PIPE6S_PORT_NUM "" * Secure IP.PIPE for IPV6 - - - - - - - - - - - - - - - - - - - 72 Line(s) not Displayed 000758 KDS_PH01_TEMS_TCP_PORT_NUM 1918 - - - - - - - - - - - - - - - - - - - 38 Line(s) not Displayed 001094 KC5_TEMS_TCP_PIPE_PORT_NUM 1918 * IP.PIPE 001095 KC5_TEMS_TCP_UDP_PORT_NUM 1918 * IP.UDP 001096 KC5_TEMS_TCP_PIPE6_PORT_NUM "" * IP.PIPE for IPV6 001097 KC5_TEMS_TCP_UDP6_PORT_NUM "" * IP.UDP for IPV6 001098 KC5_TEMS_TCP_PIPES_PORT_NUM "" * Secure IP.PIPE 001099 KC5_TEMS_TCP_PIPE6S_PORT_NUM "" * Secure IP.PIPE for IPV6 ****** **************************** Bottom of Data ****************************SP22 TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22) - 01.00 Columns 00001 00072 Command ===> C ' 1918 ' ' nnnnn ' ALL Scroll ===> CSR - - - - - - - - - - - - - - - - - - 485 Line(s) not Displayed 000486 RTE_TCP_PORT_NUM nnnnn - - - - - - - - - - - - - - - - - - - 13 Line(s) not Displayed 000654 KDS_TEMS_TCP_PIPE_PORT_NUM nnnnn * IP.PIPE 000655 KDS_TEMS_TCP_UDP_PORT_NUM nnnnn * IP.UDP 000656 KDS_TEMS_TCP_PIPE6_PORT_NUM "" * IP.PIPE for IPV6 000657 KDS_TEMS_TCP_UDP6_PORT_NUM "" * IP.UDP for IPV6 000658 KDS_TEMS_TCP_PIPES_PORT_NUM "" * Secure IP.PIPE 000659 KDS_TEMS_TCP_PIPE6S_PORT_NUM "" * Secure IP.PIPE for IPV6 - - - - - - - - - - - - - - - - - - - 72 Line(s) not Displayed 000758 KDS_PH01_TEMS_TCP_PORT_NUM nnnnn - - - - - - - - - - - - - - - - - - - 38 Line(s) not Displayed 001094 KC5_TEMS_TCP_PIPE_PORT_NUM nnnnn * IP.PIPE 001095 KC5_TEMS_TCP_UDP_PORT_NUM nnnnn * IP.UDP 001096 KC5_TEMS_TCP_PIPE6_PORT_NUM "" * IP.PIPE for IPV6 001097 KC5_TEMS_TCP_UDP6_PORT_NUM "" * IP.UDP for IPV6 001098 KC5_TEMS_TCP_PIPES_PORT_NUM "" * Secure IP.PIPE 001099 KC5_TEMS_TCP_PIPE6S_PORT_NUM "" * Secure IP.PIPE for IPV6 - - - - - - - - - - - - - - - - - - 345 Line(s) not Displayed ****** **************************** Bottom of Data **************************** - Imbed the APF-authorization commands for the libraries concatenated
in the STEPLIB and RKANMODL DDNAMES statements of all the started
tasks by setting the RTE_X_STC_INAPF_INCLUDE_FLAG option to Y.
SP22 TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22) - 01.00 Columns 00001 00072 Command ===> Scroll ===> CSR 000528 ** (Optional) INAPF INCLUDE statement in product started tasks (STCs): 000529 ** Specify "Y" if you want to generate this statement as uncommented 000530 ** out in all product STCs: "INAPF INCLUDE MEMBER=%RTE_STC_PREFIX%APF" 000531 ** This sample composite member contains APF-authorization commands for 000532 ** libraries concatenated in the STC STEPLIB and RKANMODL DDNAMEs. 000533 ** This member also contains the VARY activate command pointing to the 000534 ** %RTE_VTAM_GBL_MAJOR_NODE% VTAM major node (TSSND122 by default). 000535 ** Review %RTE_STC_PREFIX%APF and %RTE_STC_PREFIX%STRT WKANSAMU 000536 ** members for more information. 000537 RTE_X_STC_INAPF_INCLUDE_FLAG Y - Enable self-describing agent processing by uncommenting the KDS_KMS_SDA parameter:
SP22 TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22) Command ===> Scroll ===> CSR 000839 ** Enable TEMS Self-Description Agent (SDA) processing: 000840 ** This is required if you are enabling the Self-describing 000841 ** 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 the 000846 ** 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_RTEDIR 000851 ** - KDS_KMS_SDA 000852 ** - KDS_TEMA_SDA 000853 ** - Kpp_AGT_TEMA_SDA (per Kpp Agent exploiting SDA) 000810 KDS_KMS_SDA "Y" * Y, NImportant: If you intend to enable granular control of the SDA, the HTTP or HTTPS port must be enabled at the hub monitoring server to allow the Tivoli administrative commands (tacmd) Command Line Interface (CLI) utility to connect through the SOAP server interface. To enable the SOAP server, ensure that the KDS_TEMS_SOAP_SERVER_FLAG parameter is set to Y. - (Optional) If your site is using an encryption key other than
the IBM-supplied default encryption key, activate Tivoli Management Services password encryption
by uncommenting the RTE_SECURITY_KAES256_KEY parameter and specifying
the KAES256 encryption key. This value must be the same across your
monitoring environment. If you enable encryption, you also must uncomment
and customize the GBL_DSN_CSF_SCSFMOD0 parameter in the $GBL$USR configuration
profile.
Specify a unique, 32-byte password encryption key. The value is case sensitive. Be sure to record the value that you use for the key. You must use the same key during the installation of any components that communicate with this monitoring server, such as the a remote monitoring server. An ampersand (&) cannot be part of the encryption key.
** ------------------------------------------------------------------- ** (Required) KAES256 encryption key: ** This is required if you are enabling the ITM Password Encryption ** (KAES256) across the ITM enterprise: The ** "RTE_SECURITY_KAES256_KEY" value is encrypted and ** xKANPARU(KAES256) member is created as part of the ** xKANSAMU(KCIJPSEC) composite security or standalone KDSDKAES job. ** The TEMS and Agents started tasks are also updated to concatenate ** the ICSF load library (GBL_DSN_CSF_SCSFMOD0 parameter value) in the ** RKANMODL DD. ** Notes: ** 1. This parameter used to be tracked in ** KDS_TEMS_SECURITY_KAES256_ENCKEY PARMGEN profile parameter. ** Any customizations to the key must now be made through the ** global RTE RTE_SECURITY_KAES256_KEY parameter as this ** key is applicable to all components, including the Agents. ** 2. Starting in ITM6.3.0, specification of the ICSF load library and ** enabling the KAES256 key is required. ** 3. For an existing RTE, ensure that you rerun the ** WKANSAMU(KCIJPSYS) job to refresh the TMS:Engine started tasks ** in the system procedure library (GBL_DSN_SYS1_PROCLIB value). ** 4. Related PARMGEN CONFIG profile parameters: ** - GBL_DSN_CSF_SCSFMOD0 (DSN value is concatenated in the ** TEMS and Agent STCs' RKANMODL DD) ** - KDS_TEMS_SECURITY_KAES256_ENCKEY (renamed to RTE_* name) ** - KDS_KMS_SECURITY_COMPATMD (applicable to ITM6.3.0+ only) ** ------------------------------------------------------------------- RTE_SECURITY_KAES256_KEY "IBMTivoliMonitoringEncryptionKey" - If another monitoring server is
using the same IP port number for connectivity in this LPAR, perform
an EXCLUDE FIND of all KDEB_INTERFACELIST parameters. Then, uncomment
each parameter to enable it for the monitoring server and the agents.The KDEB_INTERFACELIST parameters prevent IP bind problems.
SP22 TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22) Command ===> Scroll ===> CSR - - - - - - - - - - - - - - - - - - 699 Line(s) not Displayed 000702 KDS_TEMS_TCP_KDEB_INTERFACELIST "!*" - - - - - - - - - - - - - - - - - - 456 Line(s) not Displayed 001159 KC5_AGT_TCP_KDEB_INTERFACELIST "!*" - - - - - - - - - - - - - - - - - - 190 Line(s) not Displayed 001350 KGW_AGT_TCP_KDEB_INTERFACELIST "!*" - - - - - - - - - - - - - - - - - - 340 Line(s) not Displayed- 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 network interfaces to be
used by a monitoring server and monitoring agent on a z/OS system. You specify the network
interfaces in the IP communication protocol parameters for each component.Note: Specify "!*" as the value if this agent runs on the same candidate z/OS image that is running a high-availability hub monitoring server.
- If the monitoring server 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 network interfaces to be used by a monitoring server and a monitoring agent on a z/OS system. You specify the network interfaces in the IP communication protocol parameters for each component.
- 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 network interfaces to be
used by a monitoring server and monitoring agent on a z/OS system. You specify the network
interfaces in the IP communication protocol parameters for each component.
- Configure monitoring agents using the information in the Planning and Configuration Guide.
- Perform a FIND on USER PROLOG to begin
logging overrides to the profile.
- Save and close the profile.
- 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$GBLU 000004 * MASTER SOURCE: TSTEST.ITM62351.TKANSAM(KCIPRMLB) 000005 * PURPOSE: Input to the composite WCONFIG($GBL$USR) customer-overridable 000006 * CONFIG profile member for global system libraries. 000007 * IMPORTANT NOTES: 000008 * 1. Customizing this member for applicable GBL_* parameters is 000009 * 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 required 000011 * PARMGEN CONFIG profiles required for user customization: 000012 * - WCONFIG($GBL$USR) global CONFIG profile 000013 * - WCONFIG(PLB1SP22) LPAR-specific RTE CONFIG profile 000014 * 2. $GBL$USR settings take precedence over $GBL$IBM. Customize 000015 * WCONFIG:$GBL$IBM accordingly. It is ideal for copying to other 000016 * WCONFIG RTEs if these global system libraries are typically the 000017 * same across LPARs. 000018 * 3. These values are being made available for configuration use 000019 * to harvest the same information that may have already been 000020 * 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 job 000023 * creates runtime members in the following system libraries. 000024 * ========================== ============================== 000025 * PARMGEN CONFIG Parameter Default PARMGEN CONFIG Value 000026 * ========================== ============================== 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 to 000034 * WCONFIG($JOBINDX) job index member. 000035 * 5. For applicable GBL_* parameters that indicate "Related 000036 * PARMGEN CONFIG profile parameters", these respective 000037 * parameters typically indicate that if a function is to be 000038 * enabled, refer to the related parameters as they also would 000039 * require customization. The parameters are either customized 000040 * in the WCONFIG(PLB1SP22) PARMGEN CONFIG LPAR profile or in 000041 * the WCONFIG(%GBL$USR) PARMGEN CONFIG global profile. 000042 * If this is an ICAT-->PARMGEN RTE conversion, then after the 000043 * WCONFIG(KCIJPCNV) conversion job is run, the parameters (GBL_* 000044 * and LPAR-specific parameters) are usually available for 000045 * further customization in the WCONFIG(PLB1SP22) RTE LPAR profile. 000046 * ----------------------------------------------------------------- 000047 ** ============================ ================================ 000048 ** PARMGEN CONFIG Parameter PARMGEN CONFIG Value 000049 ** ============================ ================================ 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" 000055 000056 **** PARMGEN User JCL: 000057 GBL_USER_JCL TSTEST.SYSPLEX.PARMGEN.JCL . . - Customize the following parameters,
as appropriate:
- GBL_DSN_HZSPROC_LOADLIB
- GBL_DSN_SYS1_PARMLIB
- GBL_DSN_SYS1_PROCLIB
- GBL_DSN_SYS1_SAXREXEC
- GBL_DSN_SYS1_VTAMLST
- GBL_DSN_CSF_SCSFMOD0
- GBL_HFS_JAVA_DIR1
- GBL_DSN_SYS1_SBPXEXEC
SP22 TSTEST.&userid.PLB1SP22.WCONFIG($GBL$USR) Command ===> Scroll ===> CSR 000068 **** Common system libraries (if applicable): 000069 **** Health Check configuration values for HZSPRMCI and 000070 **** HCK1%RTE_JCL_SUFFIX% xKANPARU members: 000089 GBL_DSN_HZSPROC_LOADLIB "TSTEST.SYS1.LOAD" 000090 000073 **** (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 Password 000117 **** 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_ENCKEY 000121 GBL_DSN_CSF_SCSFMOD0 "CSF.SCSFMOD0" 000122 000123 **** Java home directory name: 000124 **** Note: This is required if you are enabling the Self-describing 000125 **** Agent (SDA) functionality in the z/OS TEMS and Agents: 000126 **** "GBL_HFS_JAVA_DIRn" value becomes part of the 000127 **** TEMS_JAVA_BINPATH parameter in the RKANDATV(KDSDPROF) member 000128 **** that is created by the WKANSAMU(KCIJPUSP) USS preparation 000129 **** job. "/bin" is added to the "GBL_HFS_JAVA_DIRn" Java home 000130 **** directory value programmatically. 000131 **** Related PARMGEN CONFIG profile parameters: 000132 **** - GBL_DSN_SYS1_SBPXEXEC 000133 **** - RTE_USS_RTEDIR 000134 **** - KDS_KMS_SDA 000135 **** - KDS_TEMA_SDA 000136 **** - Kpp_AGT_TEMA_SDA 000137 GBL_HFS_JAVA_DIR1 /Java/J6.0 000138 **GBL_HFS_JAVA_DIR2 "" 000139 **GBL_HFS_JAVA_DIR3 "" 000140 **GBL_HFS_JAVA_DIR4 "" 000141 **GBL_HFS_JAVA_DIR5 "" 000142 000143 **** 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 **************************** - Save your changes and close the profile.
- On the main PARMGEN Workflow panel, select 8.
- Validate the configuration profile values
that you supplied:
- On the Workflow main panel, select option 9,
KCIJPVAL Validate PARMGEN profile parameter values.The KCIJPVAL job is displayed. - Review the notes and submit the job. The parameter validation report is written to the
%RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG($VALRPT)member. Enter 9s to view the report. - If the job gets a condition code greater than 4, review the $VALRPT report. Return to the previous step and correct the parameter values, then resubmit the validation job.
- On the Workflow main panel, select option 9,
- Create the WK* runtime members and WKANSAMU jobs:
- On the Workflow main panel, select option 10,
Create the RTE members and jobs.The
$PARSE/$PARSESV: Create the RTE Members and Jobs(KCIP@PRS) panel is displayed.--------------- $PARSE/$PARSESV: CREATE THE RTE MEMBERS AND JOBS -------------- Option ===> Select option 1 to SUBMIT the full $PARSE job in WCONFIG for RTE=PLB1SP22. $PARSE composite job creates product runtime members and jobs in all the PARMGEN WK* work libraries. Alternatively, press F5 to SUBMIT the library-specific $PARSE* jobs individually. Enter ns (1s-2s) for detailed job/task status. Description Job Name Status Date ---------------------------------------------- -------- --------- ---------- 1. Create runtime members/jobs in all WK* libs. $PARSE 2. Generate listing of symbolics (Optional) $PARSEDV Important If this is a reconfiguration of an existing PARMGEN-maintained System Variables-enabled RTE, then after rerunning the $PARSE job, you must rerun the WKANSAMU(KCIJVUPV) System Variables IEBUPDTE job next, to refresh the variable-named runtime members. Press F1=Help for more information. Press F5 for library specific $PARSE jobs. - Select option 1 to submit the generated $PARSE composite job.
- On the Workflow main panel, select option 10,
- Submit the batch jobs to complete the
PARMGEN setup:
- On the Workflow main panel, select option 11,
Submit batch jobs to complete PARMGEN setup.TheSubmit batch jobs to complete PARMGEN setup(KCIP@SUB) panel is displayed.----------------- 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 (2-12) to submit each job individually. Enter ns (1s-12s) for detailed job/task status. Description REQ Job Name Status Date --------------------------------------- ----- -------- --------- ---------- 1. Composite SUBMIT job (See JCL comments) KCIJPSUB ** or ** 2. Allocate runtime RO and RW (user) libs (Yes) KCIJPALO 3. Copy SMP/E mbrs from TK*->RK* RO libs (Yes) KCIJPLOD 4. Run product security steps (No ) KCIJPSEC 5. Update variable-named runtime mbrs (Yes) KCIJPUPV 6. Create USS runtime mbrs in RKANDATV (Yes) KCIJPUSP 7. Execute USS commands (Yes) KCIJPUSS 8. Copy runtime mbrs to system libs (AUTH/Yes) KCIJPSYS 9. Run post-SMP/E RKANMODU ASM/LINK steps (Yes) KCIJPLNK 10. Verify the configuration jobs (Tip) KCIJPIVP 11. Back-up RK* product execution user libs (Tip) KCIJPCPR 12. Copy runtime mbrs from WK*->RK* RW libs (Yes) KCIJPW2R - Select option 1 to submit the KCIJPSUB composite submit job, or select the other options to submit each job separately.
- If you select option 1, first review the KCIJPSUB job, and edit the JCL according to which of the conditional jobs must be submitted automatically.
- Submit the composite SUBMIT job, and check for good condition codes. The WSUPERC step encounters an informational condition code of 4 if OMEGAMON for Db2 on z/OS is not configured in this runtime environment as there are no xKD2* libraries to compare.
- Review the resulting output:
- The $IVPRPT report, which is stored in the WCONFIG library
- The WSUPERC SYSTSPRT report, which is stored in the WSUPERC sequential library
- Correct any errors, and rerun any jobs that did not complete successfully.
- On the Workflow main panel, select option 11,