Scenario PGN03: Configuring a high-availability hub monitoring server
In this scenario, you create a full runtime environment
that contains a z/OS-based high-availability hub Tivoli Enterprise Monitoring
Server to which remote
monitoring servers will report.
About this task
- It must be configured in a sysplex.
- It must have a dynamic virtual IP address (DVIPA), so it can respond to the same IP address on any LPAR in the sysplex.
- It must be a stand-alone configuration (in its own runtime environment without monitoring agents).
- 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.
- 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.
- Creating the work libraries
- Updating the interim libraries and create the profiles
- Customizing the profiles
- Validating the profile values
- Creating the runtime members and jobs
- Submitting jobs to complete PARMGEN setup
Procedure
- Create the PARMGEN work libraries:
- On the Workflow main panel, specify the GBL_USER_JCL, RTE_PLIB_HILEV, and RTE_NAME
fields, as shown in the following example. Note that if you did not invoke the R (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 the RTE_NAME to PLBHAHUB.Note: The example below may not accurately reflect the options or fields you see on the screen. It is provided as a sample only.
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.- GBL_USER_JCL
- Specify the data set name of
the PARMGEN global user JCL library. 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 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 processing cannot carry forward information about existing runtime environment definitions tracked in the current GBL_USER_JCL library. However, if you copy the members over 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
- Specify 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 PARMGEN file-tailored runtime members and jobs are created by the $PARSE or $PARSESV job.
- RTE_NAME
- Specify a unique name for the
runtime environment
that you are configuring (in this example, PLBHAHUB). The name that you specify is appended to the
RTE_PLIB_HILEV values to make each set of PARMGEN and runtime libraries unique. For example:
%RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(%RTE%).
- Press Enter. Because the runtime environment that you specified is a new runtime environment, 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. A verification screen is displayed:
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 to reset the parameter values.
You are returned to the main Workflow panel.
- Select option 1 from the main menu. The first "Set up PARMGEN Work Environment for an RTE" panel is displayed.
- Because you are creating a new environment, leave the first field blank (the first condition). If appropriate, specify the Install Job Generator output library.
- Press Enter to proceed to the next setup panel.
The second setup panel is displayed:
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. - Review the values and change them as necessary.
These values are initially inherited from the first runtime environment. If you specified the JOBGEN repository from the previous KCIP@PG1 panel, the GBL_TARGET_HILEV and GBL_SYSDA_UNIT parameters are completed automatically, because PARMGEN processing reuses the data from the repository.
- Press Enter to proceed to the third setup panel:
KCIP@PG3 ---- SET UP PARMGEN WORK ENVIRONMENT FOR AN RTE (3 OF 3) ------------- Command ===> Scroll ===> PAGE Enter parameter values appropriate for the LPAR RTE=PLBHAHUB. 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: 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.&userid.PLBHAHUB.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: PLBHAHUB: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) - Change the KDS_TEMS_HA_TYPE parameter to HA. If you are using a runtime environment high level qualifier that is not SMS managed, you must also specify the SMS parameters. You might also want to change the started task prefix and VTAM applid prefix to conform to site requirements. Otherwise, you can accept the defaults.
- Press Enter to proceed to the Display PARMGEN Environment
Analysis panel (KCIP@PG4). This panel lists the products installed and available for configuration.
KCIP@PG4 ------------ DISPLAY PARMGEN ENVIRONMENT ANALYSIS - Row 1 to 15 of 15 Command ===> Scroll ===> PAGE Review message traffic before proceeding. These Kpp components are installed into the TDTST.ITM63053.TKANCUS SMP/E target library and are 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.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 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 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 - Review the messages, then press Enter to display the Exclude Products from
PARMGEN Customization panel. A message reminds you that only a monitoring server can be configured 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: PLBHAHUB TEMS: Tivoli Enterprise Monitoring Server V630 Press ENTER to continue. ----------------------------------------------------------- - Press Enter to proceed. The KCIJPCFG job is displayed.
- Submit the job. Return to the main Workflow panel.
- On the Workflow main panel, specify the GBL_USER_JCL, RTE_PLIB_HILEV, and RTE_NAME
fields, as shown in the following example.
- Select option 4, KCIJPUP1 Update interim libraries and create profiles, then submit the WCONFIG(KCIJPUP1) job.
- After you return to the main panel, select option 8, PLBHAHUB
Customize PARMGEN configuration profiles. The Customize PARMGEN Configuration Profile Members panel is displayed. You must customize both the PLBHAHUB RTE configuration profile and the $GLB$USR global configuration profile.
- Select 1 to customize the PLBHAHUB RTE profile.
KCIP@PG6 ------ CUSTOMIZE PARMGEN CONFIGURATION PROFILE MEMBERS --------------- Option ===> Quick Configuration Mode Review/Customize the LPAR-specific and global configuration values: *1. PLBHAHUB 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. PLBHAHUB 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.The PLBHAHUB profile is displayed. - Customize the parameters as follows to create a high-availability hub monitoring
server.
- Perform an EXCLUDE FIND of all "_TCP_HOST" strings. Next, customize all occurrences of the LPAR
name to the reserved Dynamic VIPA name. In this example, this is the OMEGHAHUB host name.
ISREDDE2 TSTEST.&userid.PLBHAHUB.WCONFIG(PLBHAHUB) Command ===> C &hostname OMEGHAHUB ALL Scroll ===> CSR ****** ***************************** Top of Data ****************************** - - - - - - - - - - - - - - - - - - 307 Line(s) not Displayed 000308 ** 000029 RTE_TCP_HOST "OMEGHAHUB" - - - - - - - - - - - - - - - - - - 197 Line(s) not Displayed 000506 RTE_TCP_HOST "OMEGHAHUB" - - - - - - - - - - - - - - - - - - 186 Line(s) not Displayed 000693 ** Note: If this is a High-Availability Hub TEMS, KDS_TEMS_TCP_HOST - - - - - - - - - - - - - - - - - - - 1 Line(s) not Displayed 000695 KDS_TEMS_TCP_HOST "OMEGHAHUB" - - - - - - - - - - - - - - - - - - - 90 Line(s) not Displayed 000786 ** Note: If this is a High-Availability Hub TEMS, KDS_PH01_TEMS_TCP_HOST - - - - - - - - - - - - - - - - - - - 9 Line(s) not Displayed 000796 KDS_PH01_TEMS_TCP_HOST "OMEGHAHUB" - - - - - - - - - - - - - - - - - - - 32 Line(s) not Displayed ****** **************************** Bottom of Data **************************** - If you want to use a port other than the default port of 1918, perform an EXCLUDE FIND of all
_PORT parameters, 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 **************************** - If you intend to enable self-describing agents, or configure any products that require a z/OS®
UNIX System Services directory, set RTE_USS_RTEDIR to the
directory created for that purpose.
ISREDDE2 TSTEST.&userid.PLBHAHUB.WCONFIG(PLBHAHUB) 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 "/tstest" - (Optional) Set the RTE_X_STC_INAPF_INCLUDE_FLAG option to Y to
automatically APF authorize the libraries concatenated in the STC STEPLIB and RKANMODL DDNAMEs. This
VARYs the %RTE_VTAM_GBL_MAJOR_NODE% VTAM major node active.
ISREDDE2 TSTEST.&userid.PLBHAHUB.WCONFIG(PLBHAHUB) 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 - Customize the Tivoli Enterprise Monitoring Server protocols to support only IP: At least one of
the values must be
IPPIPE,IP6PIPE,IPSPIPE, orIP6SPIPE. Nullify the KDS_TEMS_COMM_PROTOCOL3 parameter by setting it to "" (instead of the initial value of SNA).ISREDDE2 TSTEST.&userid.PLBHAHUB.WCONFIG(PLBHAHUB) Command ===> Scroll ===> CSR 000658 ** 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, and 000661 ** IP6SPIPE. When communication with another ITM component (TEPS, Hub 000662 ** TEMS or Remote TEMS, Agents) is initiated, the TEMS tries Protocol 1 000663 ** first and goes to Protocol 2 and so on, in case of failure. 000664 ** Note: Update the corresponding KDS_TEMS_TCP_*_PORT_NUM port number 000665 ** parameter for each KDS_TEMS_COMM_PROTOCOLx parameter enabled. 000666 ** For example, if KDS_TEMS_COMM_PROTOCOL1="IPPIPE", set the 000667 ** corresponding KDS_TEMS_TCP_PIPE_PORT_NUM parameter. 000668 ** If KDS_TEMS_COMM_PROTOCOL2="IP" (for IP.UDP), set the 000669 ** corresponding KDS_TEMS_TCP_UDP_PORT_NUM parameter. 000670 ** If this is a Remote TEMS, update the KDS_HUB_* parameters 000671 ** by uncommenting out the corresponding KDS_HUB_TCP_*_PORT_NUM 000672 ** parameters and specify the Remote's Hub TEMS port numbers. 000673 KDS_TEMS_COMM_PROTOCOL1 IPPIPE 000674 KDS_TEMS_COMM_PROTOCOL2 IP 000675 KDS_TEMS_COMM_PROTOCOL3 "" - Uncomment the KDS_TEMS_TCP_KDEB_INTERFACELIST parameter, then change its value from the default
(!*) to !dvipa_hostname, where dvipa_hostname is the private
DVIPA name set for the KDS_TEMS_TCP_HOST parameter (in this example, !OMEGAHUB). This setting
ensures that the high-availability hub is restricted to its private DVIPA address and cannot
interfere with the remote monitoring server configured on the same LPAR.
ISREDDE2 TSTEST.&userid.PLBHAHUB.WCONFIG(PLBHAHUB) Command ===> Scroll ===> CSR 000698 ** If the TEMS requires network interface list support: 000699 ** Note: If this is a High-Availability Hub TEMS, uncomment the 000700 ** KDS_TEMS_TCP_KDEB_INTERFACELIST and set its value to 000701 ** "!<dvipa_address>" 000702 KDS_TEMS_TCP_KDEB_INTERFACELIST "!OMEGHAHUB" - (Conditional) Customize IBM Tivoli Monitoring password encryption by
uncommenting the RTE_SECURITY_KAES256_KEYparameter; then specify the KAES256 encryption key if using
other than the IBM-supplied PARMGEN default key.
Specify a unique, 32-byte password encryption key. The value is case sensitive. An ampersand (&) cannot be part of the encryption key. 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.
ISREDDE2 TSTEST.&userid.PLBHAHUB.WCONFIG(PLBHAHUB) Command ===> Scroll ===> CSR 000709 ** TEMS' security settings: 000710 KDS_TEMS_SECURITY_KDS_VALIDATE N 000711 000712 ** TEMS' security settings: KAES256 encryption key 000713 ** Note: This is required if you are enabling the ITM Password 000714 ** Encryption (KAES256) across the ITM enterprise: 000715 ** The "KDS_TEMS_SECURITY_KAES256_ENCKEY" value is encrypted 000716 ** and xKANPARU(KAES256) member is created as part of the 000717 ** xKANSAMU(KCIJPSEC) composite security job. 000718 ** Related PARMGEN CONFIG profile parameter: 000719 ** - GBL_DSN_CSF_SCSFMOD0 (DSN value is concatenated in the 000720 ** TEMS STC's STEPLIB DD) 000721 KDS_TEMS_SECURITY_KAES256_ENCKEY "IBMTivoliMonitoringEncryptionKey" - To use the 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 ===> 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 000849 ** - GBL_DSN_SYS1_SBPXEXEC 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 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. - To enable the auditing feature, locate and uncomment the audit parameters in the configuration 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 ""- 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, new connections to the monitoring server or the portal server, or failed user login attempts.
- Basic (B)
- Records any actions that modify objects or cause an access failure, such as attempts to 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 all successful logins and all modifications to entities such as Take Action commands.
- Disabled (X)
- Disables the auditing function.
- Set the KDS_AUDIT_MAX_HIST parameter to any value from 10 - 1000, depending on the number of audit records that you want kept in the in-memory cache before writing them out.
- To group audit records by related agent and monitoring server, set the KDS_AUDIT_ITM_DOMAIN parameter to the name that you assigned to that group.
- Set the KDS_AUDIT_TRACE parameter to M, B, D, or X, where
- Press F3 to save the changes and return to the Customize PARMGEN Configuration Profiles panel.
- Perform an EXCLUDE FIND of all "_TCP_HOST" strings. Next, customize all occurrences of the LPAR
name to the reserved Dynamic VIPA name. In this example, this is the OMEGHAHUB host name.
- Complete the following steps to customize the $GLB$USR profile.
- Select option 2 ($GBL$USR). The WCONFIG($GBL$USR) profile is displayed.
- Review the following parameters that identify system libraries to which the KCIJPSYS job copies
various members to determine if you have to override the IBM supplied defaults. To override the
default, uncomment out the parameter and type the new value.
- GBL_DSN_HZSPROC_LOADLIB
- GBL_DSN_SYS1_PARMLIB
- GBL_DSN_SYS1_PROCLIB
- GBL_DSN_SYS1_SAXREXEC
- GBL_DSN_SYS1_VTAMLIB
- GBL_DSN_SYS1_VTAMLST
- If you enabled the self-describing agent feature, you might have to customize the following parameters:
- GBL_HFS_JAVA_DIRn
- GBL_DSN_SYS1_SBPXEXEC
000130 **** Java home directory name: 000131 **** Note: This is required if you are enabling the Self-describing 000132 **** Agent (SDA) functionality in the z/OS TEMS and Agents: 000133 **** "GBL_HFS_JAVA_DIRn" value becomes part of the 000134 **** TEMS_JAVA_BINPATH parameter in the RKANDATV(KDSDPROF) member 000135 **** that is created by the WKANSAMU(KCIJPUSP) USS preparation 000136 **** job. "/bin" is added to the "GBL_HFS_JAVA_DIRn" Java home 000137 **** directory value programmatically. 000138 **** Related PARMGEN CONFIG profile parameters: 000139 **** - GBL_DSN_SYS1_SBPXEXEC 000140 **** - RTE_USS_RTEDIR 000141 **** - KDS_KMS_SDA 000142 **** - KDS_TEMA_SDA 000143 **** - Kpp_AGT_TEMA_SDA 000144 **GBL_HFS_JAVA_DIR1 /usr/lpp/java/IBM/J6.0 000145 **GBL_HFS_JAVA_DIR2 "" 000146 **GBL_HFS_JAVA_DIR3 "" 000147 **GBL_HFS_JAVA_DIR4 "" 000148 **GBL_HFS_JAVA_DIR5 "" 000149 000150 **** z/OS UNIX System Services (USS) CLIST/EXEC library name: 000151 **GBL_DSN_SYS1_SBPXEXEC "SYS1.SBPXEXEC" - If you enabled password encryption for the Tivoli Enterprise Monitoring Server and you are using a library other than CSF.SCSFMOD0 (the default), you must uncomment and customize the GBL_DSN_CSF_SCSFMOD0 parameter.
- If no GLOBALTCPIPDATA statement is configured for your TCP/IP environment, customize the GBL_DSN_TCP_SYSTCPD_TCPDATA parameter to enable the SYSTCPD DDNAME automatically for all started tasks in this runtime environment:
- Press F3 to save the parameters and to return to the Customize PARMGEN Configuration Profiles panel, then press F3 again to return to the main Workflow panel.
- Select 1 to customize the PLBHAHUB RTE profile.
- 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. - If the job gets a condition code greater than 4, review the $VALRPT report. Enter 9s to view the report, return to the previous step and correct the flagged values, then resubmit the validation job.
- On the Workflow main panel, select option 9, KCIJPVAL
Validate PARMGEN profile parameter values.
- From the Workflow menu, select option 10, $PARSE Create
the RTE members and jobs, to create the
WK*runtime members and the WKANSAMU jobs.The Submit $PARSE Batch Jobs to Complete PARMGEN Setup panel is displayed:Select option 1 to submit the generatedKCIP@PR1 ------ $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 RC= 00000 2012/02/08 2. Generate listing of symbolics (Optional) $PARSEDV RC= 00000 2013/08/21 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.$PARSEcomposite job. - Submit the jobs that complete the setup of the runtime
environment.
- From the Workflow menu, select option 11, SUBMIT.
The
Submit Batch Jobs to Complete PARMGEN Setuppanel 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=PLBHAHUB Tip: Review the SUBMIT commands in the KCIJPSUB composite job. 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 (No ) 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. - Select option 1 to submit the KCIJPSUB composite submit job, or select the other options to submit each job individually. If you select option 1, first review the KCIJPSUB job, then edit the job according to which of the conditional jobs can to be submitted automatically and which jobs have to be submitted manually (for example, jobs that require authorization).
- From the Workflow menu, select option 11, SUBMIT.