Scenario PGN02: Creating a sharing-with-base runtime environment that uses system variables
In this scenario, you create a new runtime environment that shares its libraries with a base environment that has system variables enabled. In configuring the new environment, you enable it to exploit system variables and configure a remote monitoring server, OMEGAMON XE monitoring agents, and the OMEGAMON enhanced 3270 user interface.
About this task
- Setting up PARMGEN work libraries
- Cloning the customized WCONFIG members from an existing runtime environment
- Updating the libraries and creating the profiles
- Customizing the configuration profiles
- Validating the parameters
- Creating the runtime members and jobs
- Submitting the batch jobs to complete the setup of the runtime environment
This scenario assumes that you have launched the PARMGEN Workflow user interface (see Starting the Workflow user interface).
Procedure
- To set up the PARMGEN
work libraries for the PLB3SYSG environment, complete the following
steps:
- 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 runtime environment
will run. Note that if you did not choose the R (RESET) option from the previous runtime environment, the values for GBL_USER_JCL, RTE_PLIB_HILEV, and RTE_NAME are carried forward from the previous session. In this case, simply change the RTE_NAME value from PLB1SP22 to PLB3SYSG. If the values have not been carried over, specify the high-level qualifiers for the JCL and work libraries shared by the new runtime environment and the base runtime environment and the name for the new runtime environment.
- Select option 1, KCIJPCFG Set up PARMGEN work
environment for an RTE, from the menu.
Because the runtime environment that you specified is a new one, you are asked if you want to reset the 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 selecting Option "R" to reset RTE, status and date fields for a new RTE. Press ENTER to perform the reset for a new RTE. Press F3 to abort. - Press Enter. You see a verification screen:
KCIP@PGP ---------------- PARMGEN MESSAGES -------------------------- COMMAND ===> This will clear the GBL_USER_JCL, RTE_PLIB_HILEV and RTE_NAME fields and all Status and Date fields. Press ENTER to proceed. Press F3 to abort. - Press Enter. You are returned to the main Workflow panel.
- Select 1 again to begin setting
up the work environment. The first Set up PARMGEN work environment for an RTE panel (KCIP@PG1 is displayed
- Leave the first field (RTE profile library and member
name) blank. If appropriate, specify the Install Job Generator output
library.
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.PLB3SYSG.WCONFIG(PLB3SYSG)) **or** - If converting an ICAT-created RTE to PARMGEN mode, specify the ICAT RTE Batch member location and RTE member (ex.: &hlq.INSTJOBS(PLB3SYSG)) 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% ,,username’,CLASS=A,____________________ ==> // MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID.,REGION=0M_________________ ==> //** RTE_NAME=%RTE_NAME%________________________________________________ ==> //** SYSJOBNAME=%SYSJOBNAME% SYSMEMBER=%SYSMEMBER%______________________ - Press Enter to proceed to the next setup panel.
- 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 and GBL_SYSDA_UNIT values completed automatically, because PARMGEN processing 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. - Press Enter to proceed to the next panel.
The third setup panel 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=PLB3SYSG. Press F1=Help for more information. More: + RTE_DESCRIPTION: "PLB3SYSG LPAR"_________________________________ 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: TSTEST.&userid______________ (&hlq portion of Non-VSAM RK* HLQ=&hlq.&rte_name) RTE_VSAM_HILEV: TSTEST.&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) RTE_X_SYSV_OVERRIDE_SYMBOLS: N (Y, N) (Override local system symbols) Security settings: RTE_SECURITY_USER_LOGON: NONE______ (RACF, ACF2, TSS, NAM, None) RTE_SECURITY_FOLD_PASSWORD_FLAG: Y (Y, N) (Fold password to upper case) RTE_SECURITY_CLASS: ____________________________________________ RTE_X_SECURITY_EXIT_LIB: TSTEST.CCAPI.PLB3SYSG.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: PLB3SYSG:CMS_______________ (e.g.,PLB3SYSG: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) Note: Type BACK to go back one panel. - Review the values on the panel and modify them as follows.
Depending on your screen resolution, you might have to scroll down
(PF8) to see all the parameters. The More: + indicates that more parameters
are present on the panel.
- Because the new runtime environment will share a base runtime
environment, set the RTE_TYPE parameter to
SHARING. - To create the Base runtime environment that this environment will share, customize the RTE_X_HILEV_SHARING parameter to the high level qualifier for the base runtime environment and the RTE_SHARE parameter to the name of the base runtime environment.
- 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.)
- If required by your site conventions, use RTE_STC_PREFIX to specify a prefix of up to 4 characters to replace the default IBM prefix for the names of the started tasks that are created by the configuration software. If you use symbolics, you can use up to 18 characters that resolve to 4 characters. For example, &SYSCLONE..
- If required by your site conventions, use RTE_VTAM_APPLID_PREFIX to specify a prefix of up to 4 characters (or a symbolic of up to 18 characters that resolve to 4) for all VTAM major nodes and applids. For example, TS&SYSCLONE..
- Set the RTE_SYSV_SYSVAR_FLAG parameter to Y to enable system variables.
- 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 might want to specify a more global security exit library that different environments can share.KCIP@PG3 ---- SET UP PARMGEN WORK ENVIRONMENT FOR AN RTE (3 OF 3) ------------- Command ===> Scroll ===> PAGE Enter parameter values appropriate for the LPAR RTE=PLB3SYSG. Press F1=Help for more information. More: + RTE_DESCRIPTION: "PLB3SYSG LPAR"_________________________________ 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: SHARING_ (FULL, SHARING) RTE_HILEV: TSTEST.&userid______________ (&hlq portion of Non-VSAM RK* HLQ=&hlq.&rte_name) RTE_VSAM_HILEV: TSTEST.&userid______________ (&hlq portion of VSAM RK* HLQ=&hlq.&rte_name) If RTE_TYPE is SHARING: RTE_X_HILEV_SHARING: TSTEST____________________ (&hlq portion of shared RTE's HLQ=&hlq.&rte_share) RTE_SHARE: BASE&SYSALVL._________________ ("SMP" value or *&rte_share) (*&rte_share portion of shared RTE's HLQ=&hlq.&rte_share) RTE_LOAD_SHARED_LIBS: Y (Y, N) (Is RTE updater of RO shared libs) If symbolics (system variables or user-defined variables) will be used: RTE_SYSV_SYSVAR_FLAG: Y (Y, N) (System variable flag) RTE_X_SYSV_OVERRIDE_SYMBOLS: N (Y, N) (Override local system symbols) Security settings: RTE_SECURITY_USER_LOGON: NONE______ (RACF, ACF2, TSS, NAM, None) RTE_SECURITY_FOLD_PASSWORD_FLAG: Y (Y, N) (Fold password to upper case) RTE_SECURITY_CLASS: ____________________________________________ RTE_X_SECURITY_EXIT_LIB: TSTEST.&userid.PLB3&SYSNAME..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: PLB3&SYSNAME.:CMS__________ (e.g.,PLB3SYSG:cms) KDS_TEMS_TYPE: REMOTE (Hub, Remote) KDS_TEMS_HA_TYPE: __ (HA=High Availability Hub TEMS type) ITM components' communication-related and started tasks settings: RTE_TCP_PORT_NUM: 1918_________________ (1-65535 port number) RTE_VTAM_APPLID_PREFIX: TS&SYSCLONE.___________ (1-4 char.VTAM APPLID prefix) RTE_STC_PREFIX: TSS3_________________ (1-4 char.started task prefix) Note: Type BACK to go back one panel. - Because the new runtime environment will share a base runtime
environment, set the RTE_TYPE parameter to
- After you make any necessary changes, press Enter to
proceed to the next panel (KCIP@PG4).
The KCIP@PG4 panel displays the list of products that are installed in the SMP/E target library and are available for configuration.
KCIP@PG4 ------------ DISPLAY PARMGEN ENVIRONMENT ANALYSIS --- Row 1 to 6 of 6 Command ===> Scroll ===> PAGE Review message traffic before proceeding. These Kpp components are installed into the TSTEST.ITM62351.TKANCUS SMP/E target library and are available for (re)configuration and/or upgrade into the RTE=PLB3SYSG 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 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 - After you review the message traffic, press Enter to
proceed to the next panel. The Include Products in this PARMGEN RTE panel is displayed. All the installed products are preselected.
- Deselect any products that you do not want to configure
in this environment. In the following example, all products are deselected except for the OMEGAMON XE monitoring agents, the Tivoli Enterprise Monitoring Server, and the OMEGAMON enhanced 3270 user interface.
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=PBL3SYSG 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 - Change Confirm from N to Y,
then press Enter. The file-tailored GBL_USER_JCL(KCIJPCFG) job is displayed.
- Review the notes and values and submit the job. Return to the main Workflow panel.
- 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 runtime environment
will run.
- (Optional) Clone the customized members
from the PLB1SP22 WCONFIG library.
- Select option 3 from the Workflow
main menu. The KCIJPCCF job is displayed.
- Review the job to determine if you have 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 RTE profile 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 that you want cloned over to the WCONFIG library for the new runtime environment.
- Submit the job and return to the Workflow main menu.
- Select option 3 from the Workflow
main menu.
- Select option 4
to update interim libraries and to create profiles.
The KCIJPUP1 job is displayed. Review the notes and values, then submit the job.
- Customize the configuration profiles for this runtime environment:
- Select option 8, PLB3SYSG Customize PARMGEN
configuration profiles, from the Workflow main menu. The Customize PARMGEN Configuration Profile Members panel is displayed:Customization of the PLB3SYSG LPAR profile (option 1) is required. If you cloned the $GLB$USR profile and if both runtime environments will share the same values, no further edits should be necessary, but you should review the profile 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-specific values. If user-defined symbols will be used as parameter values in the LPAR configuration profile, the system variables profile (option 3) must also be edited to define those values.
KCIP@PG6 ------ CUSTOMIZE PARMGEN CONFIGURATION PROFILE MEMBERS --------------- Option ===> Review/Customize the LPAR-specific and global configuration values: *1. PLB3SYSG 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) PLB3SYSG LPAR-specific and option (2) $GBL$USR global user profiles above: *3. PLB3SYSG 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 customize
the LPAR configuration profile for PLB3SYSG runtime environment.
For guidance on setting parameter values, see the following sources of information:
- Comments in the PARMGEN configuration profiles
- Online help for the configuration profile (F1))
- Common parameters
- Documentation for your monitoring agents
- Configure the runtime environment to exploit system
variables:
- Set the RTE_NAME parameter to the static symbolic PLB3&SYSNAME..
ISREDDE2 TSTEST.&userid.PLB3SYSG.WCONFIG(PLB3SYSG) Command ===> Scroll ===> CSR 000360 ** Runtime environment (RTE) settings: 000361 ** Specify the name of the RTE in the RTE_NAME parameter if this RTE 000362 ** is not enabled for System Variables (RTE_SYSV_SYSVAR_FLAG=N). 000363 RTE_NAME PLB3&SYSNAME. - Perform an EXCLUDE FIND of all
TEMS_VTAM_NETIDstrings, then change all references toUSIBMNETto the&SYSVTAMNETID.KCIPARSE-extracted symbol.Note that NETID value is autodiscovered by the PARMGEN process when you submit the KCIJPUP1 job. The ID will be different for your site. For the agents (in this example runtime environment, these are KC5_TEMS_VTAM_* and KGW_TEMS_VTAM_*), these parameters denote the VTAM® network ID of the LPAR running the primary Tivoli Enterprise Monitoring Server that they connect to.
ISREDDE2 TSTEST.&userid.PLB3SYSG.WCONFIG(PLB3SYSG) Command ===> C 'USIBMNET' '&SYSVTAMNETID.' ALL Scroll ===> CSR ****** ***************************** Top of Data ****************************** - - - - - - - - - - - - - - - - - - 499 Line(s) not Displayed 000500 RTE_VTAM_NETID &SYSVTAMNETID. - - - - - - - - - - - - - - - - - - 216 Line(s) not Displayed 000717 KDS_TEMS_VTAM_NETID &SYSVTAMNETID. - - - - - - - - - - - - - - - - - - - 81 Line(s) not Displayed 000799 KDS_PH01_TEMS_VTAM_NETID "&SYSVTAMNETID." - - - - - - - - - - - - - - - - - - - 27 Line(s) not Displayed 000827 KDS_HUB_VTAM_NETID "&SYSVTAMNETID." - - - - - - - - - - - - - - - - - - 112 Line(s) not Displayed 001168 KC5_TEMS_VTAM_NETID &SYSVTAMNETID. - - - - - - - - - - - - - - - - - - - 46 Line(s) not Displayed 001359 KGW_TEMS_VTAM_NETID &SYSVTAMNETID. - - - - - - - - - - - - - - - - - - - 39 Line(s) not Displayed ****** **************************** Bottom of Data **************************** - Perform an EXCLUDE FIND of all
TEMS_TCP_HOSTstrings and change all references to the four-character host name to the&SYSIPHOSTNAME.KCIPARSE-extracted symbol.Note that the host name is autodiscovered by the PARMGEN process when you submit the KCIJPUP1 job. For the agents (in our current runtime environment, these are KC5_TEMS_VTAM_* and KGW_TEMS_VTAM_*), these parameters denote the IP hostname of the 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 Displayed 000694 ** Note: If this is a High-Availability Hub TEMS, KDS_TEMS_TCP_HOST - - - - - - - - - - - - - - - - - - - 1 Line(s) not Displayed 000696 KDS_TEMS_TCP_HOST "&SYSIPHOSTNAME." - - - - - - - - - - - - - - - - - - - 90 Line(s) not Displayed 000787 ** Note: If this is a High-Availability Hub TEMS, KDS_PH01_TEMS_TCP_HOST - - - - - - - - - - - - - - - - - - - 9 Line(s) not Displayed 000797 KDS_PH01_TEMS_TCP_HOST "&SYSIPHOSTNAME." - - - - - - - - - - - - - - - - - - 353 Line(s) not Displayed 001151 ** Note: KC5_TEMS_TCP_HOST and KC5_AGT_TCP_HOST must be the same value - - - - - - - - - - - - - - - - - - - 1 Line(s) not Displayed 001153 KC5_TEMS_TCP_HOST "&SYSIPHOSTNAME." - - - - - - - - - - - - - - - - - - 188 Line(s) not Displayed 001342 ** Note: KGW_TEMS_TCP_HOST and KGW_AGT_TCP_HOST must be the same value - - - - - - - - - - - - - - - - - - - 1 Line(s) not Displayed 001344 KGW_TEMS_TCP_HOST "&SYSIPHOSTNAME." - - - - - - - - - - - - - - - - - - 347 Line(s) not Displayed ****** **************************** Bottom of Data **************************** - Perform the same steps for all
AGT_TCP_HOSTstrings, then change all references to the four-character host name to the&SYSIPHOSTNAME.KCIPARSE-extracted symbol.For the agents, these parameters denote the IP host name of the LPAR where the agent is running (the same IP host name as the local z/OS remote monitoring server that they will connect to).
ISREDDE2 TSTEST.&userid.PLB3SYSG.WCONFIG(PLB3SYSG) Command ===> C 'SYSG' '&SYSIPHOSTNAME.' ALL Scroll ===> CSR ****** ***************************** Top of Data ****************************** - - - - - - - - - - - - - - - - - - 1150 Line(s) not Displayed 001156 KC5_AGT_TCP_HOST "&SYSIPHOSTNAME." - - - - - - - - - - - - - - - - - - 185 Line(s) not Displayed 001347 KGW_AGT_TCP_HOST "&SYSIPHOSTNAME." - - - - - - - - - - - - - - - - - - 344 Line(s) not Displayed ****** **************************** Bottom of Data **************************** - If SDA is enabled or a product requires z/OS
UNIX System Services files, set the RTE_USS_RTEDIR parameter
to the user-defined symbolic
&RTE_USS_RTEDIR..ISREDDE2 TSTEST.&userid.PLB3SYSG.WCONFIG(PLB3SYSG) 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 000495 ** - GBL_DSN_SYS1_SBPXEXEC 000496 ** - RTE_USS_RTEDIR 000497 ** - KDS_KMS_SDA 000498 ** - KDS_TEMA_SDA 000499 ** - Kpp_AGT_TEMA_SDA (per Kpp Agent exploiting SDA) 000500 RTE_USS_RTEDIR "&RTE_USS_RTEDIR." - Perform an EXCLUDE FIND of all _PORT parameters. Then, customize
_PORT according to your site's conventions.
ISREDDE2 TSTEST.&userid.PLB3SYSG.WCONFIG(PLB3SYSG) 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 **************************** - 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 would be directed to the first runtime environment's static hub monitoring server in the PLB1SP22 runtime environment. In this case, you should convert the parameters to user-defined symbols to keep them generic so it is easier to reassign the values of these symbolics if you reconfigure the remote monitoring server to point to a different hub later on. (See Variables in PARMGEN configuration for more information on using variables.)
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 Displayed 000671 ** If this is a Remote TEMS, update the KDS_HUB_* parameters 000672 ** by uncommenting out the corresponding KDS_HUB_TCP_*_PORT_NUM - - - - - - - - - - - - - - - - - - - 51 Line(s) not Displayed 000724 KDS_TEMS_VTAM_APPL_GLB_BROKER "&KDS_HUB_VTAM_APPL_GLB_BROKER." - - - - - - - - - - - - - - - - - - - 96 Line(s) not Displayed 000821 ** If the TEMS is a Remote, uncomment the KDS_HUB_* parameters - - - - - - - - - - - - - - - - - - - 1 Line(s) not Displayed 000823 KDS_HUB_TEMS_NAME_NODEID "&KDS_HUB_TEMS_NAME_NODEID." - - - - - - - - - - - - - - - - - - - 2 Line(s) not Displayed 000826 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 Displayed 000830 KDS_HUB_TCP_HOST "&KDS_HUB_TCP_HOST." - - - - - - - - - - - - - - - - - - - 2 Line(s) not Displayed 000833 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 **************************** - Perform an EXCLUDE FIND of all
TEMS_BKUP1strings and uncomment the parameters accordingly.The agent's Kpp_TEMS_BKUP1_* parameters enable the secondary monitoring server for the agents that run in their own agent address spaces. In the event that the primary monitoring server that they connect to goes down (the local remote monitoring server, in this case), they can reconnect to the backup (secondary) monitoring server.
By default, the parameters already point to generic
&AGT_*user-defined symbols, so it is easier to reassign the values of these symbols if you reconfigure the agents to point to a different backup monitoring server later on. The values specified for the Kpp_TEMS_BKUP1_* parameters are used in the agent's CT_CMSLIST parameter in the agent-specific xKANPARU(KppENV) runtime member.EDIT TSTEST.&userid.PLB3SYSG.WCONFIG(PLB3SYSG) - 01.00 Columns 00001 00072 Command ===> Scroll ===> CSR ****** ***************************** Top of Data ****************************** - - - - - - - - - - - - - - - - - - 1269 Line(s) not Displayed 001270 ** - KC5_TEMS_BKUP1_* Agent's Backup TEMS parameter values - - - - - - - - - - - - - - - - - - 123 Line(s) not Displayed 001394 ** Note: Specify the Backup TEMS (KC5_TEMS_BKUP1_*) parameter values - - - - - - - - - - - - - - - - - - - 4 Line(s) not Displayed 001399 KC5_TEMS_BKUP1_NAME_NODEID "&AGT_TEMS_BKUP1_NAME_NODEID." - - - - - - - - - - - - - - - - - - - 2 Line(s) not Displayed 001402 KC5_TEMS_BKUP1_TCP_HOST "&AGT_TEMS_BKUP1_TCP_HOST." - - - - - - - - - - - - - - - - - - - 2 Line(s) not Displayed 001405 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 Displayed 001540 ** - KGW_TEMS_BKUP1_* Agent's Backup TEMS parameter values - - - - - - - - - - - - - - - - - - - 85 Line(s) not Displayed 001626 ** Note: Specify the Backup TEMS (KGW_TEMS_BKUP1_*) parameter values - - - - - - - - - - - - - - - - - - - 4 Line(s) not Displayed 001631 KGW_TEMS_BKUP1_NAME_NODEID "&AGT_TEMS_BKUP1_NAME_NODEID." - - - - - - - - - - - - - - - - - - - 2 Line(s) not Displayed 001634 KGW_TEMS_BKUP1_TCP_HOST "&AGT_TEMS_BKUP1_TCP_HOST." - - - - - - - - - - - - - - - - - - - 2 Line(s) not Displayed 001637 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 Displayed 002149 ** - KN3_TEMS_BKUP1_* Agent's Backup TEMS parameter values - - - - - - - - - - - - - - - - - - - 90 Line(s) not Displayed
- Set the RTE_NAME parameter to the static symbolic PLB3&SYSNAME..
- Set the RTE_X_STC_INAPF_INCLUDE_FLAG option to Y.
ISREDDE2 TSTEST.&userid.PLB3SYSG.WCONFIG(PLB3SYSG) 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 - If you are using enabling password encryption across
your monitoring environment, and you are not using the default encryption
key, customize the Tivoli Management Services password
encryption by uncommenting the RTE_SECURITY_KAES256_KEY parameter
and then specifying the KAES256 encryption key.
000615 ** ------------------------------------------------------------------- 000616 ** (Required) KAES256 encryption key: 000617 ** This is required if you are enabling the ITM Password Encryption 000618 ** (KAES256) across the ITM enterprise: The 000619 ** "RTE_SECURITY_KAES256_KEY" value is encrypted and 000620 ** xKANPARU(KAES256) member is created as part of the 000621 ** xKANSAMU(KCIJPSEC) composite security or standalone KDSDKAES job. 000622 ** The TEMS and Agents started tasks are also updated to concatenate 000623 ** the ICSF load library (GBL_DSN_CSF_SCSFMOD0 parameter value) in the 000624 ** RKANMODL DD. 000625 ** Notes: 000626 ** 1. This parameter used to be tracked in 000627 ** KDS_TEMS_SECURITY_KAES256_ENCKEY PARMGEN profile parameter. 000628 ** Any customizations to the key must now be made through the 000629 ** global RTE RTE_SECURITY_KAES256_KEY parameter as this 000630 ** key is applicable to all components, including the Agents. 000631 ** 2. Starting in ITM6.3.0, specification of the ICSF load library and 000632 ** enabling the KAES256 key is required. 000633 ** 3. For an existing RTE, ensure that you rerun the 000634 ** WKANSAMU(KCIJPSYS) job to refresh the TMS:Engine started tasks 000635 ** in the system procedure library (GBL_DSN_SYS1_PROCLIB value). 000636 ** 4. Related PARMGEN CONFIG profile parameters: 000637 ** - GBL_DSN_CSF_SCSFMOD0 (DSN value is concatenated in the 000638 ** TEMS and Agent STCs' RKANMODL DD) 000639 ** - KDS_TEMS_SECURITY_KAES256_ENCKEY (renamed to RTE_* name) 000640 ** - KDS_KMS_SECURITY_COMPATMD (applicable to ITM6.3.0+ only) 000641 ** ------------------------------------------------------------------- 000642 RTE_SECURITY_KAES256_KEY "IBMTivoliMonitoringEncryptionKey"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, for example a remote monitoring server. An ampersand (&) cannot be part of the encryption key. Note that this value must match across your site's IBM Tivoli Monitoring enterprise.
If you use a library other than the default library, you must uncomment and customize the GBL_DSN_CSF_SCSFMOD0 parameter in the $GBL$USR global configuration profile.
- Refer to the Planning and Configuration Guide for each component to make sure that you have made any required configuration changes.
- Save the profile and exit to the Customize PARMGEN Configuration Profile Members panel.
- Customize the $GBL$USR profile to use symbolic values.
- Select option 2.
- Provide symbolic values for the appropriate parameters.
For example, you can set GBL_HFS_JAVA_DIR1 to &GBL_HFS_JAVA_DIR1..
- Save the profile and exit to the Customize PARMGEN Configuration Profile Members panel.
- Customize the PLB3SYSG system variables configuration
profile to set all user-defined symbols that are referenced when you
customized the LPAR profile.
- Select option 3.
- 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, these parameters point to the hub created on LPAR SP22 in scenario 1.
- Supply the values for all the user-defined symbols.
ISREDDE2 TSTEST.SYSPLEX.PARMGEN.JCL(PLB3SYSG) - 01.16 Columns 00001 00072 Command ===> Scroll ===> CSR ****** ***************************** Top of Data ****************************** 000100 * ****************************************************************** 000110 * Member: KCI$RTEV 000120 * Master Source: TSTEST.ITM62351.TKANSAM(KCI$RTEV) 000130 * KCIJPUP1 Batch Job Output (PART 3): 000131 * TSTEST.&userid.PLB3SYSG.IKANSAMU(KCI$RTEV) - IBM Default Copy 000140 * TSTEST.SYSPLEX.PARMGEN.JCL(PLB3SYSG) - Customer Copy 000150 * Purpose: 000160 * TSTEST.SYSPLEX.PARMGEN.JCL(PLB3SYSG) 000170 * member houses user-defined symbolics for this RTE if 000180 * System Variables mode is enabled. 000190 * Note: These are symbolics in addition to the typical static 000200 * system symbols defined in SYS1.IPLPARM and system variables 000210 * derived by KCIPARSE program (for TYPE:CE (CHAR extracted) 000221 * and TYPE:IE (INTEGER extracted) KCIPARSE-extracted symbolics 000222 * for System Variables use in the SYSPRINT DDNAME's GLOBAL 000224 * 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:CMS 000292 AGT_TEMS_BKUP1_TCP_HOST SP22 000293 AGT_TEMS_BKUP1_VTAM_LU62_DLOGMOD CANCTDCS 000294 AGT_TEMS_BKUP1_VTAM_APPL_LLB_BKR CTDDSLB 000295 AGT_TEMS_BKUP1_VTAM_NETID USIBMNET 000296 * ----------- 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 symbols 009500 RTE_USS_RTEDIR /tstest 009710 KDS_HUB_TEMS_NAME_NODEID "PLB1SP22:CMS" 009711 KDS_HUB_VTAM_APPL_GLB_BROKER CTDDSLB 009720 KDS_HUB_VTAM_NETID USIBMNET 009730 KDS_HUB_TCP_HOST SP22 009780 KDS_HUB_TCP_PIPE_PORT_NUM nnnnn 009790 KDS_HUB_TCP_UDP_PORT_NUM nnnnn 009800 GBL_HFS_JAVA_DIR1 /Java/J6.0 ****** **************************** Bottom of Data ****************************
- Save the changes and return to the main Workflow panel.
- Select option 8, PLB3SYSG Customize PARMGEN
configuration profiles, from the Workflow main menu.
- On the Workflow main panel, select option 9 to validate the configuration profile values that you supplied. Submit the generated KCIJPVAL job.
- Create the runtime members and jobs:
- From the Workflow main menu, select option 10, Create
the RTE members and jobs:
The screen Submit $PARSESV Batch Jobs to Complete PARMGEN Setup is displayed.
- Select option 1 to edit and then
submit the $PARSESV composite job.
KCIP@PR1 ------ $PARSE/$PARSESV: CREATE THE RTE MEMBERS AND JOBS -------------- Option ===> Select option 1 to SUBMIT the full $PARSESV job in WCONFIG for RTE=PLB3SYSG. $PARSESV 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. 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 $PARSESV 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.
- From the Workflow main menu, select option 10, Create
the RTE members and jobs:
- Submit the batch jobs to complete the
PARMGEN setup:
- On the Workflow main panel, select option 11, Submit batch jobs to complete PARMGEN setup.
- On the Submit Batch Jobs to Complete PARMGEN Setup panel, select
option 1 to submit the KCIJVSUB composite SUBMIT job, or select the other
options to submit each job individually. If you select option 1, review the KCIJVSUB job first and
edit the job according to which conditional jobs you want to be submitted automatically.
KCIP@SUB -------- 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 (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 (Yes) 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/Tip) 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 Press F1=Help for more information. Type UTIL to access utility menu.If you select option 1, you are prompted with the following message:----------------------------- PARMGEN MESSAGES ----------------------------- Command ===> The KCIJVSUB composite job submits several PARMGEN configuration jobs via TSO SUBMIT commands. Some of those SUBMIT commands are commented out. Carefully review the comments in the JCL to determine which of those jobs you do or do not want to submit. Uncomment the SUBMIT commands of those jobs that you want to submit. Do NOT delete any SUBMIT commands as they may be needed in the future. - Press Enter. The following message is displayed:
----------------------------- PARMGEN MESSAGES ----------------------------- Command ===> In a system variable environment, job KCIJVSUB runs $PARSESV to customize then submit the KCIJPSUV job. EDIT and modify the KCIJPSUV job as appropriate. See comments in the JCL for further information. DO NOT MANUALLY SUBMIT THE KCIJPSUV JOB! - Press Enter to edit the KCIJPSUV job. Jobs that require authorization or are conditional are not submitted automatically. You must either submit them manually, or uncomment them to run automatically.
- Press F3, and the KCIJVSUB job is displayed for submission. Submit the job. Check the status of each of the jobs submitted. The allocation and load jobs must run successfully, or others jobs being submitted by the composite job will not run.