IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/os

Transcription

1 Version 6 Release 3 IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/os Common Parameter Reference SC

2

3 Version 6 Release 3 IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/os Common Parameter Reference SC

4 Note Before using this information and the product it supports, read the information in Notices on page 419. This edition applies to version 5, release 1, modification 1 of the IBM Tivoli OMEGAMON XE products and to version 6, release 3, Fix Pack 1 of IBM Tivoli Management Services on z/os (product number 5698-A79) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2010, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Chapter 1. Overview Where configured parameters are stored How parameter values are set PARMGEN method Configuration Tool method s Parameter names Determining what products are configured in each runtime environment Parameters covered in this guide New in this release New in the previous release Chapter 2. Common agent (KPP) parameters KPP_AGT_AUDIT_ITM_DOMAIN KPP_AGT_AUDIT_MAX_HIST KPP_AGT_AUDIT_TRACE KPP_AGT_CONFIGURATION_MODE KPP_AGT_COMM_PROTOCOLn KPP_AGT_FLUSH_LSR_BUFR_INT_HR KPP_AGT_FLUSH_LSR_BUFR_INT_MIN KPP_AGT_ICU_LANGUAGE_LOCALE KPP_AGT_KGL_WTO KPP_AGT_KLX_TCP_TOLERATERECYCLE KPP_AGT_NSNEWn_VALUE KPP_AGT_NONSTDn_DSN KPP_AGT_NONSTDn_MBR KPP_AGT_NONSTDn_PARM KPP_AGT_NSOLDn_VALUE KPP_AGT_PARTITION_NAME KPP_AGT_PPI_RECEIVER KPP_AGT_PPI_SENDER KPP_AGT_STC KPP_AGT_STORAGE_DETAIL_INT_HR KPP_AGT_STORAGE_DETAIL_INT_MIN KPP_AGT_STORAGE_MINIMUM_EXTEND KPP_AGT_TCP_HOST KPP_AGT_TCP_KDEB_INTERFACELIST KPP_AGT_TCP_STC KPP_AGT_TEMA_SDA KPP_AGT_TEMS_NAME_NODEID KPP_AGT_VIRTUAL_IP_ADDRESS KPP_AGT_VTAM_APPL_AA KPP_AGT_VTAM_APPL_KPPINVPO KPP_AGT_VTAM_APPL_NCS KPP_AGT_VTAM_APPL_OPERATOR KPP_AGT_VTAM_APPL_PREFIX KPP_AGT_VTAM_NODE KPP_AGT_WTO_MSG KPP_PD KPP_PD_CYL KPP_PD_GRP KPP_PD_HISTCOLL_DATA_IN_AGT_STC KPP_PD_HISTCOLL_DATA_IN_TEMS_STC KPP_PD_ROW KPP_SECURITY_ACTION_CLASS KPP_TEMS_BKUP1_NAME_NODEID KPP_TEMS_BKUP1_TCP_HOST KPP_TEMS_BKUP1_VTAM_APPL_LLB_BKR KPP_TEMS_BKUP1_VTAM_LU62_DLOGMOD.. 68 KPP_TEMS_BKUP1_VTAM_NETID KPP_TEMS_HUB_TCP_HOST KPP_TEMS_LOCAL_CONNECT_FLAG KPP_TEMS_NAME_NODEID KPP_TEMS_TCP_HOST KPP_TEMS_TCP_PIPE_PORT_NUM KPP_TEMS_TCP_PIPES_PORT_NUM KPP_TEMS_TCP_PIPE6_PORT_NUM KPP_TEMS_TCP_PIPE6S_PORT_NUM KPP_TEMS_TCP_UDP_PORT_NUM KPP_TEMS_TCP_UDP6_PORT_NUM KPP_TEMS_VTAM_APPL_LLB_BROKER KPP_TEMS_VTAM_LU62_DLOGMOD KPP_TEMS_VTAM_LU62_MODETAB KPP_TEMS_VTAM_NETID KPP_X_AGT_CONFIRM_SHUTDOWN KPP_X_AGT_DEBUG_TRACE KPP_X_AGT_KDC_DEBUG KPP_X_AGT_LGSA_VERIFY KPP_X_AGT_LSRPOOL_BUFFER_NUM KPP_X_AGT_LSRPOOL_BUFSIZE KPP_X_AGT_SDUMP_SVC_SYS1_DUMP KPP_X_AGT_STORAGE_LIMIT_EXTEND KPP_X_AGT_STORAGE_LIMIT_PRIMARY KPP_X_AGT_STORAGE_RESERVE_EXT KPP_X_AGT_STORAGE_RESERVE_PRI KPP_X_AGT_STORAGE_STGDEBUG KPP_X_AGT_TASKS_ATTACHED_NUM KPP_X_HUB_BKUP1_TCP_HOST KPP_X_HUB_BKUP1_TEMS_VTAM_NETID KPP_X_HUB_BKUP1_VTAM_APPL_GLBBKR KPP_X_HUB_TCP_HOST KPP_X_HUB_TEMS_VTAM_NETID KPP_X_HUB_VTAM_APPL_GLBBKR KPP_X_PD_HISTCOLL_DATA_AGT_STC KPP_X_PD_HISTCOLL_DATA_TEMS_STC Chapter 3. Global (GBL) parameters 109 GBL_DSN_ACF2_MACLIB GBL_DSN_CBC_SCCNOBJ GBL_DSN_CBC_SCLBSID GBL_DSN_CEE_SCEEBIND GBL_DSN_CEE_SCEEBND GBL_DSN_CEE_SCEECPP GBL_DSN_CEE_SCEELIB GBL_DSN_CEE_SCEELKED GBL_DSN_CEE_SCEELKEX GBL_DSN_CEE_SCEEMSGP GBL_DSN_CEE_SCEERUN Copyright IBM Corp. 2010, 2013 iii

6 GBL_DSN_CEE_SCEESPC GBL_DSN_CICS_CTG_DLL GBL_DSN_CICS_SCTGSID GBL_DSN_CICS_SDFHC GBL_DSN_CICS_SDFHLOAD GBL_DSN_CSF_SCSFMOD GBL_DSN_DB2_DSNEXIT GBL_DSN_DB2_LOADLIB_Vn GBL_DSN_DB2_RUNLIB_Vn GBL_DSN_DB2_SDSNLOAD GBL_DSN_HZSPROC_LOADLIB GBL_DSN_IMS_RESLIB GBL_DSN_IMS_SCEXLINK GBL_DSN_IMS_SFUNLINK GBL_DSN_ISP_SISPLOAD GBL_DSN_NETVIEW_CNMLINK GBL_DSN_SYS1_BRODCAST GBL_DSN_SYS1_CSSLIB GBL_DSN_SYS1_HSMLOGY GBL_DSN_SYS1_LINKLIB GBL_DSN_SYS1_MACLIB GBL_DSN_SYS1_MODGEN GBL_DSN_SYS1_PARMLIB GBL_DSN_SYS1_PROCLIB GBL_DSN_SYS1_SAXREXEC GBL_DSN_SYS1_SBLSCLI GBL_DSN_SYS1_SBPXEXEC GBL_DSN_SYS1_SISTMAC GBL_DSN_SYS1_VTAMLIB GBL_DSN_SYS1_VTAMLST GBL_DSN_TCP_ETC_SERVICES GBL_DSN_TCP_SEZACMTX GBL_DSN_TCP_SEZARNT GBL_DSN_TCP_SEZATCP GBL_DSN_TCP_SYSTCPD_TCPDATA GBL_DSN_TCP_SYSTCPD_TCPDATA_MFN GBL_DSN_WMQ_SCSQANLE GBL_DSN_WMQ_SCSQAUTH GBL_DSN_WMQ_SCSQLOAD GBL_HFS_JAVA_DIRn GBL_INST_HILEV GBL_TARGET_HILEV GBL_USER_JCL Chapter 4. Runtime environment (RTE) parameters RTE_BASE_NAME RTE_CANSCN_STC RTE_CANSETE_STC RTE_DEBUG_SYSOUT RTE_DESCRIPTION RTE_HCK_STC_INTERVAL RTE_HILEV RTE_JCL_SUFFIX RTE_KCNDLSSI_IEFSSN00_FORMAT RTE_KCNSTR00_SSID RTE_KCNSTR00_WTO RTE_KCNSTR00_XCFGROUP RTE_LOAD_OPTIMIZE RTE_LOAD_SHARED_LIBS RTE_LOG_SYSOUT iv RTE_NAME RTE_PDS_BATCHINIT_FLAG RTE_PDS_BACKUP_FLAG RTE_PDS_EXPORT_FLAG RTE_PDS_EXTRACT_FLAG RTE_PDS_FILE_COUNT RTE_PDS_HILEV RTE_PDS_KPDPROC_PREFIX RTE_PDS_SMS_MGMTCLAS RTE_PDS_SMS_STORCLAS RTE_PDS_SMS_UNIT RTE_PDS_SMS_VOLUME RTE_REMOTE_LPAR_FLAG RTE_SECURITY_CLASS RTE_SECURITY_FOLD_PASSWORD_FLAG RTE_SECURITY_USER_LOGON RTE_SHARE RTE_SMS_MGMTCLAS RTE_SMS_PDSE_FLAG RTE_SMS_STORCLAS RTE_SMS_UNIT RTE_SMS_VOLUME RTE_SMS_VSAM_MGMTCLAS RTE_SMS_VSAM_STORCLAS RTE_SMS_VSAM_VOLUME RTE_STC_PREFIX RTE_SYSV_BASE_ALIAS RTE_SYSV_NAME RTE_SYSV_SYSVAR_FLAG RTE_SYSV_TEMS_NAME_NODEID RTE_SYSV_VTAM_APPLID_MODEL RTE_SYSV_VTAM_APPLID_PREFIX RTE_SYSV_VTAM_NETID RTE_TCP_HOST RTE_TCP_PORT_NUM RTE_TCP_STC RTE_TEMS_CONFIGURED_FLAG RTE_TEMS_NAME_NODEID RTE_TN3270_DXL_HOSTADDRESS RTE_TN3270_DXL_LUGROUP RTE_TN3270_DXL_TN3270PORT RTE_TYPE RTE_USERMODS_FLAG RTE_USS_MKDIR_MODE RTE_SECURITY_CLASS RTE_SECURITY_KAES256_KEY RTE_USS_RTEDIR RTE_VSAM_HILEV RTE_VTAM_APPLID_PREFIX RTE_VTAM_GBL_MAJOR_NODE RTE_VTAM_LU62_DLOGMOD RTE_VTAM_LU62_MODETAB RTE_VTAM_NETID RTE_X_HILEV_SHARING RTE_X_KCNDLSSI_INITPARM_FLAG RTE_X_KCNSTR00_PLEXCOLLECT RTE_X_KCNSTR00_REFRESH RTE_X_SECURITY_DATA_ABOVE RTE_X_SECURITY_EXIT_LIB RTE_X_SMS_MGMTCLAS_SHARE RTE_X_SMS_PDSE_FLAG_SHARE IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/os Common Parameter Reference

7 RTE_X_SMS_STORCLAS_SHARE RTE_X_SMS_UNIT_SHARE RTE_X_SMS_VOLUME_SHARE RTE_X_SMS_VSAM_MGMTCLAS_SHARE RTE_X_SMS_VSAM_STORCLAS_SHARE RTE_X_SMS_VSAM_VOLUME_SHARE RTE_X_STC_INAPF_INCLUDE_FLAG RTE_X_SYSV_OVERRIDE_SYMBOLS Chapter 5. Tivoli Enterprise Monitoring Server (KDS) parameters. 253 KDS_AUDIT_ITM_DOMAIN KDS_AUDIT_MAX_HIST KDS_AUDIT_TRACE KDS_HUB_TCP_HOST KDS_HUB_TCP_PIPE_PORT_NUM KDS_HUB_TCP_PIPE6_PORT_NUM KDS_HUB_TCP_PIPE6S_PORT_NUM KDS_HUB_TCP_PIPES_PORT_NUM KDS_HUB_TCP_UDP_PORT_NUM KDS_HUB_TCP_UDP6_PORT_NUM KDS_HUB_TEMS_HA_TYPE KDS_HUB_TEMS_NAME_NODEID KDS_HUB_VTAM_APPL_GLB_BROKER KDS_HUB_VTAM_NETID KDS_KMS_SDA KDS_KMS_SDA_NO_GRANULAR KDS_KMS_SECURITY_COMPATMD KDS_MIG_TAPE_HILEV KDS_MIG_TAPE_UNIT KDS_MIG_TAPE_VOL KDS_MIG_VER KDS_MIG_VSAM_HILEV KDS_NONSTDnn_DSN KDS_NONSTDnn_MBR KDS_NONSTDnn_PARM KDS_NSNEWnn_VALUE KDS_NSOLDnn_VALUE KDS_PA KDS_PA_PARTITION_ADDRESS KDS_PA_PARTITION_NAME KDS_PA_ROW KDS_PD KDS_PD_CYL KDS_PD_GRP KDS_PD_ROW KDS_PH KDS_PH_ROW KDS_PH_TEMS_ALIAS_NAME KDS_PH_TEMS_COMM_PROTOCOL KDS_PH_TEMS_KSH_SECURE KDS_PH_TEMS_NAME_NODEID KDS_PH_TEMS_RTE KDS_PH_TEMS_SYSV_FLAG KDS_PH_TEMS_TCP_HOST KDS_PH_TEMS_TCP_HOST_LEN KDS_PH_TEMS_TCP_PORT_NUM KDS_PH_TEMS_USER_QUERY KDS_PH_TEMS_USER_UPDATE KDS_PH_TEMS_VTAM_APPL_GLB_BROKER KDS_PH_TEMS_VTAM_LU62_DLOGMOD KDS_PH_TEMS_VTAM_NETID KDS_PPI_RECEIVER KDS_PPI_SENDER KDS_PU KDS_PU_ROW KDS_PU_TEMS_NAME_NODEID KDS_PU_TEMS_RTE KDS_PU_TEMS_USER_ID KDS_PU_TEMS_USER_QUERY KDS_PU_TEMS_USER_UPDATE KDS_TEMA_SDA KDS_TEMS_COMM_ADDRESS_XLAT KDS_TEMS_COMM_PROTOCOLn KDS_TEMS_DRA_FLAG KDS_TEMS_EIF_BUFFER_EVENT_MAXSZE KDS_TEMS_EIF_DISABLE_TEC_EMITTER KDS_TEMS_EIF_EVENT_LISTENER KDS_TEMS_EIF_FLAG KDS_TEMS_EIF_HOST KDS_TEMS_EIF_PORT_NUM KDS_TEMS_FLUSH_LSR_BUFR_INT_HR KDS_TEMS_FLUSH_LSR_BUFR_INT_MIN KDS_TEMS_HA_EXCL_LIST KDS_TEMS_HA_TYPE KDS_TEMS_HTTP_PORT_NUM KDS_TEMS_ICU_LANGUAGE_LOCALE KDS_TEMS_KDC_DEBUG KDS_TEMS_KGL_WTO KDS_TEMS_KLX_TCP_TOLERATERECYCLE KDS_TEMS_PARTITION_NAME KDS_TEMS_SECURITY_KAES256_ENCKEY (deprecated) KDS_TEMS_SECURITY_KDS_VALIDATE KDS_TEMS_SOAP_SERVER_FLAG KDS_TEMS_STC KDS_TEMS_STORAGE_DETAIL_INT_HR KDS_TEMS_STORAGE_DETAIL_INT_MIN KDS_TEMS_STORAGE_DETAIL_LOG_FLAG KDS_TEMS_STORAGE_LIMIT_EXTEND KDS_TEMS_STORAGE_LIMIT_PRIMARY KDS_TEMS_STORAGE_MINIMUM_EXTEND KDS_TEMS_TCP_HOST KDS_TEMS_TCP_KDEB_INTERFACELIST KDS_TEMS_TCP_PIPE_PORT_NUM KDS_TEMS_TCP_PIPE6_PORT_NUM KDS_TEMS_TCP_PIPE6S_PORT_NUM KDS_TEMS_TCP_PIPES_PORT_NUM KDS_TEMS_TCP_STC KDS_TEMS_TCP_UDP_PORT_NUM KDS_TEMS_TCP_UDP6_PORT_NUM KDS_TEMS_TYPE KDS_TEMS_VIRTUAL_IP_ADDRESS KDS_TEMS_VTAM_APPL_CUA_OPER KDS_TEMS_VTAM_APPL_GLB_BROKER KDS_TEMS_VTAM_APPL_KDS_VTAMID KDS_TEMS_VTAM_APPL_KDSINVPO KDS_TEMS_VTAM_APPL_LLB_BROKER KDS_TEMS_VTAM_APPL_OPERATOR KDS_TEMS_VTAM_APPL_PREFIX KDS_TEMS_VTAM_LU62_DLOGMOD KDS_TEMS_VTAM_LU62_MODETAB Contents v

8 KDS_TEMS_VTAM_NETID KDS_TEMS_VTAM_NODE KDS_X_HUB_BKUP1_TCP_HOST KDS_X_HUB_BKUP1_TEMS_VTAM_NETID KDS_X_HUB_BKUP1_VTAM_APPL_GLBBKR KDS_X_KDCFC_RXLIMIT KDS_X_KDE_TRANSPORT_HTTP_OPTIONS KDS_X_KDE_TRANSPORT_OPTIONS KDS_X_KDE_TRANSPORT_POOL_OPTIONS KDS_X_STC_SYSTCPD_INCLUDE_FLAG KDS_X_TEMS_CONFIRM_SHUTDOWN KDS_X_TEMS_DEBUG_TRACE KDS_X_TEMS_EIF_BFR_EVT KDS_X_TEMS_EIF_BFR_EVT_PATH KDS_X_TEMS_EIF_FLT_ATTR KDS_X_TEMS_EIF_FLT_CLASS KDS_X_TEMS_EIF_FLT_MODE KDS_X_TEMS_FRAME_STACK_SIZE KDS_X_TEMS_KDSSTRT1_DELAY_INT KDS_X_TEMS_LGSA_VERIFY KDS_X_TEMS_LOGBLOCK_RKLVLOG_SIZE KDS_X_TEMS_LOGBUFS_RKLVLOG_BUFSZ KDS_X_TEMS_LSRPOOL_BUFFER_NUMn KDS_X_TEMS_LSRPOOL_BUFSIZEn KDS_X_TEMS_LSRSTRNO_CONCURRENT KDS_X_TEMS_SDUMP_SVC_SYS1_DUMP KDS_X_TEMS_STORAGE_RESERVE_PRI KDS_X_TEMS_STORAGE_STGDEBUG KDS_X_TEMS_TASKS_ATTACHED_NUM KDS_X_TEMS_WTO Parameters for the high-availability hub monitoring server KDS_TEMS_HA_TYPE Chapter 6. Enhanced 3270 user interface (KOB) parameters KOB_SAF_ACTION_CLASS_NAME KOB_SAF_LOGON_CLASS_NAME KOB_SAF_LOGON_RESOURCE_PREFIX KOB_SAF_QUERY_CLASS_NAME KOB_TOM_STC KOB_TOM_VTAM_APPL_LOGON KOB_TOM_VTAM_NODE Documentation library Shared OMEGAMON XE publications IBM Tivoli Monitoring library Documentation for the base agents Other sources of documentation Support information Notices Trademarks Privacy policy considerations Index vi IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/os Common Parameter Reference

9 Chapter 1. Overview This guide provides reference information about the parameters that are used for setting and storing configuration values for the common components of IBM Tivoli Management Services on z/os and for the runtime environments in which the IBM Tivoli OMEGAMON XE monitoring agents are configured. For agent parameter information, see the documentation for each product. Where configured parameters are stored Most configuration parameters and their configured values are stored in the KppENV or KppSYSIN members of the rhilev.rte.rkanparu data set for each runtime environment. Where: pp rhilev rte is the 2-character product or component code is the high-level qualifier for the runtime environment data sets is the runtime environment name, which is used as the mid-level qualifier for the runtime environment data sets (For information about runtime environments, see Planning your deployment in IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide.) The parameters stored in the KppENV member are environment variables, which determine the operating characteristics of the runtime environment in which products and components are configured. The parameters stored in the KppSYSIN member are startup parameters, which determine the default startup values for each product or component. How parameter values are set Most parameters are provided with default values that you can accept or change. Some parameters are included in the runtime libraries by default, and others are excluded by default. You can set parameter values by either of two basic methods: v PARMGEN method v Configuration Tool method on page 2 For instructions on using both configuration methods, see IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide. If you decide to use the PARMGEN tool to create or update your site s runtime environments, you might want to take advantage of the detailed scenarios in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: PARMGEN Reference. PARMGEN method With the PARMGEN configuration method, you edit a comprehensive list of parameters for configuring all installed products and components. You then submit a series of jobs to create a complete runtime environment with the parameter values you specified. The PARMGEN method can be used for creating new runtime environments and for upgrading existing ones that were created from product versions for which the PARMGEN configuration method was Copyright IBM Corp. 2010,

10 enabled. To upgrade from a product version earlier than the first PARMGEN-enabled version, you must use the Configuration Tool. To determine the earliest PARMGEN-enabled version of each of your products, see the PARMGEN Technote at If you have runtime environments that are already configured by the Configuration Tool method, a conversion tool (the KCIJPCNV job) is provided for using the existing parameter values in those runtime environments to set up initial values for new runtime environments to be configured by the PARMGEN method. After you use the PARMGEN method to configure new runtime environments, you cannot use the Configuration Tool to edit or maintain them. Configuration Tool method The Configuration Tool (also called the Installation and Configuration Assistance Tool, or ICAT) is software provided for configuring the Tivoli Enterprise Monitoring Server and monitoring agents on z/os systems. The Configuration Tool operates in two modes: v Interactive mode, where an ISPF panel-driven facility assists you in specifying parameters and tailoring jobs for configuring new products and new versions of products. v Batch mode, where you create a single batch job that you can use to build, configure, and load a runtime environment for the Tivoli Enterprise Monitoring Server, monitoring agents, or both. The batch job performs the same processing as the interactive Configuration Tool. Batch mode is a quick way to configure your runtime environments and is particularly useful for replicating a configured runtime environment to other z/os systems. For details, see the "Batch mode" chapter of IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide. In most cases, you use interactive mode to set parameter values for a runtime environment and for the products and components in the runtime environment, and then you use batch mode to propagate the parameter values to other LPARs. (See Part 4, Replicating configured environments, and Part 5, Configuration and deployment scenarios, in IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide.) s Some parameters have only one default value, and some have more than one. For example, TMS:Engine sets this global default value for the KDS_TEMS_STORAGE_LIMIT_EXTEND on page 344 parameter: LIMIT(16,X) However, the Configuration Tool panels and PARMGEN files override the TMS:Engine default and show a different default value for the Tivoli Enterprise Monitoring Server: LIMIT(23,X) When you edit a default value on a Configuration Tool panel or in a PARMGEN file, your edited value overrides the Configuration Tool or PARMGEN default value, which has already overridden the TMS:Engine default value (if a TMS:Engine default value exists). The default values provided by an individual monitoring agent product often differ from the TMS:Engine default values, the Tivoli Enterprise Monitoring Server default values, and the default values of other monitoring agents. s for monitoring agents are shown in the Configuration Tool panels, batch mode data dictionaries, parameter maps (described in IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide), and PARMGEN configuration profiles (also described in IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide). These values are also included in the documentation for each monitoring agent product. 2 IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/os Common Parameter Reference

11 This guide includes information about the default values for runtime environment and Tivoli Enterprise Monitoring Server parameters. Parameter names Most parameters have several different names in the Configuration Tool, in Batch mode, and in PARMGEN. Stored parameter name Name of the parameter as stored in a runtime library. Example: LIMIT Configuration Tool field name Name of the field that identifies the parameter on an interactive panel. Example: Maximum storage request size (extended) Name of the parameter in the batch parameter member. Example: KDS_CMS_EXT_LIM Name of the parameter in the PARMGEN parameter list. Example: KDS_TEMS_STORAGE_LIMIT_EXTEND In this guide, the parameters in each chapter are documented in alphabetical order by, and all other applicable names for each parameter are shown. You can use the Index to look up a parameter by one of the names other than the. Parameters with n or nn in their names Some parameters include n or nn in their names. These are not the actual names of these commands as you will see them in the configuration profile. The n or nn means that you can have multiple instances of this parameter in your configuration profile. For example, you will most likely have multiple instances of the set of monitoring agent component override commands (for example, KN3_TCPXnn_OVRD_CONN or KN3_TCPXnn_OVRD_FTP) because you have one set of values for every instance in which you override the global (all stacks) collection values for a specific stack. Likewise, you would have multiple instances of the KN3_AGT_NONSTDn_DSN, KN3_AGT_NONSTDn_MBR, KN3_AGT_NONSTDn_PARM values if you defined several nonstandard parameters. If you cannot find a parameter by searching on its full name, try searching on a part of the name, omitting the numbers that define instance. Parameters designated N/A Some parameters have "N/A" (not applicable) designated in the field description. This designation means that these parameter cannot be set using the mode being described. Certain groups of parameters cannot be set using the Configuration Tool and cannot be updated in your environment using Batch. Examples include the KN3_X and KON_X parameters, most of which are stored in either the KN3SYSIN or KONSYSIN member in the rhilev.midlev.rtename.rkanparu library. You can set these values using PARMGEN because they are part of the configuration profile. If you configure your monitoring agent using the Configuration Tool and the default values provided for this product do no meet your needs, you must modify these values using the Non-Standard Parameter panels in the Configuration Tool. Refer to the common configuration guide for information about nonstandard parameters. If you do not use this method to modify these values, then the values will revert to the default values when the Configuration Tool is updated. There is a difference in how PARMGEN designates multiple instances of sets of parameters for stack-specific configuration (as opposed to global values) in the configuration profile file and how Batch mode handles these same parameters. As noted previously, override commands in PARMGEN have a two-digit number (represented as nn) appended to the middle of the parameter name (for example, KN3_TCPXnn) indicating a stack-specific override of a global value (for example, KN3_TCPX01_OVRD_CONN Chapter 1. Overview 3

12 or KN3_TCPX02_OVRD_CONN to override the global value KN3_TCP_CON). Batch mode does not append the two-digit number to indicate a stack-specific override. Instead, Batch overrides are indicated with a KN3_TCPX BEGIN or KON_TCPX BEGIN statement and concluded with a KN3_TCPX END or KON_TCPX END statement, as shows in the following sample Batch mode file: ** TCP/IP Information: KN3_TCP_DATA SYS1.TCPPARMS(TCPDATA) KN3_TCP_SAMP_INTERVAL 1 KN3_TCP_STACK Y KN3_TCP_CON Y <-- global default.. ** Define TCP monitoring systems member: KN3_TCPX BEGIN * Table begin KN3_TCPX_ROW KN3_TCPX_SYS_NAME $$$$ KN3_TCPX_ADDR_SPACE $$$$$$$$ KN3_TCPX_PROF_DATASET TCPIP.PROFILE.TCPIP KN3_TCPX_OGBL N KN3_TCPX_OSTACK Y KN3_TCPX_OTCPC Y <-- stack specific-default (this is also global).. **KN3_TCPX_PROF_MEMBER KN3_TCPX_ROW KN3_TCPX_SYS_NAME $$$$ KN3_TCPX_ADDR_SPACE SAMPLESTACK KN3_TCPX_PROF_DATASET USER.PARMLIB KN3_TCPX_OGBL Y KN3_TCPX_OSTACK Y KN3_TCPX_OTCPC Y <-- stack specific for SAMPLESTACK.. KN3_TCPX_PROF_MEMBER SAMPLESTACK <-- End of SAMPLESTACK parameters.. KN3_TCPX END <--End of all overrides for all stacks Therefore, parameters such as KN3_TCPX or KON_TCPX can be set using the Non-Standard Parameters panels in the Configuration Tool, but do not have Batch names (they are designated "N/A" in this guide). The Configuration Tool sets these parameters internally unless you set them using the Non-Standard Parameter panels. You can override the system-defined defaults by editing the stack-specific instance of the KPPSYSIN file or by using the Non-Standard Parameter Panels, which persist after Configuration Tool maintenance has been applied. Determining what products are configured in each runtime environment One of the first sections in the configuration profile is the set of flags that define the set of monitoring agents running in this runtime environment. These configuration flag statements are in the following format: * Tivoli Enterprise Monitoring Server: KDS flag CONFIGURE_TEMS_KDS "Y" Where the first line, which is commented out, identifies the product or component to be configured and the second statement is the PARMGEN command to configure the specified product. Specify Y if the product-specific configuration flag if the product is to be configured in this runtime environment. Specify N if you do not plan to configure the specified product in this runtime environment. The full set of configuration flags are found in the table that follows. 4 IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/os Common Parameter Reference

13 Table 1. Master Flags from CONFIGURE_PRODUCTS USER SECTION Product Configuration statement (Y or N) Tivoli Enterprise Monitoring Server IBM Tivoli OMEGAMON XE for CICS on z/os IBM Tivoli OMEGAMON XE for CICS TG on z/os: IBM Tivoli OMEGAMON XE for DB2 PE/PM IBM Tivoli OMEGAMON XE for IMS on z/os IBM Tivoli OMEGAMON XE on z/os IBM Tivoli System Automation for z/os IBM OMEGAMON z/os Management Console IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Configuration IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Monitoring: IBM Tivoli OMEGAMON XE for Messaging - WebSphere Message Broker IBM Tivoli NetView for z/os Agent IBM Tivoli OMEGAMON XE for Mainframe Networks IBM Tivoli OMEGAMON XE for Storage on z/os IBM Tivoli OMEGAMON DE on z/os - OMEGAVIEW and OMEGAVIEW II IBM Tivoli Decision Support for z/os IBM Tivoli Composite Application Manager for SOA IBM Tivoli Advanced Audit for DFSMShsm IBM Tivoli Advanced Reporting for DFSMShsm IBM Tivoli Advanced Allocation Management for z/os IBM Tivoli Automated Tape Allocation Manager for z/os IBM Tivoli Advanced Catalog Management for z/os IBM Tivoli Advanced Backup and Recovery for z/os IBM Tivoli Tape Optimizer for z/os ITCAM for Application Diagnostics on z/os CONFIGURE_TEMS_KDS CONFIGURE_CICS_KC5 CONFIGURE_CICS_TG_KGW CONFIGURE_DB2_AGENT_KD5 CONFIGURE_IMS_KI5 CONFIGURE_ZOS_KM5 CONFIGURE_SA_KAH CONFIGURE_ZMC_KHL CONFIGURE_MESSAGING_KMC CONFIGURE_MESSAGING_KMQ CONFIGURE_MESSAGING_KQI CONFIGURE_NETVIEW_KNA CONFIGURE_MFN_KN3 CONFIGURE_STORAGE_KS3 CONFIGURE_OMEGAVIEW_KWO CONFIGURE_TDS_KDO CONFIGURE_SOA_KD4 CONFIGURE_AAD_KRG CONFIGURE_ARD_KRH CONFIGURE_AAM_KRJ CONFIGURE_ATAM_KRK CONFIGURE_ACM_KRN CONFIGURE_ABR_KRV CONFIGURE_TOZ_KRW CONFIGURE_ITCAMAD_KYN Parameters covered in this guide This guide documents several types of parameters. v Chapter 2, Common agent (KPP) parameters, on page 9 The parameters common to all agents had been documented in the OMEGAMON XE for Mainframe Networks parameter reference guide. The definitions of these parameters have been broadened and moved to this common location since the parameters are common to all agents configured with PARMGEN. v Chapter 3, Global (GBL) parameters, on page 109 The global parameters provide default settings for installation and common system library names. v Chapter 4, Runtime environment (RTE) parameters, on page 165 The runtime environment parameters provide configuration settings for an individual runtime environment and default settings for the components and products configured in the runtime environment. v Chapter 5, Tivoli Enterprise Monitoring Server (KDS) parameters, on page 253 Chapter 1. Overview 5

14 The Tivoli Enterprise Monitoring Server parameters provide configuration settings for hub and remote monitoring servers on z/os. In addition, the Parameters for the high-availability hub monitoring server on page 403 section of this chapter describes parameters specific to a HA hub TEMS. v Chapter 6, Enhanced 3270 user interface (KOB) parameters, on page 405 The OMEGAMON enhanced 3270 user interface has its own set of common configuration parameters, each of which begins with "KOB". New in this release The following updates apply to the Tivoli Management Services version update of this book. The following parameters have been added: v A new parameter has been added to control the behavior of self-describing agents. Beginning with IBM Tivoli Monitoring V6.3, the products and versions for which application data is installed can be explicitly specified. By default, this control is disabled on z/os monitoring servers. It can be enabled by setting KDS_KMS_SDA_NO_GRANULAR to NO. However, if granular control is enabled, no data is installed until products and versions are specified using the tacmd command line interface. For more information, see IBM Tivoli OMEGAMON XE and Tivoli Management Service on z/os: Configuring the Tivoli Enterprise Monitoring Server on z/os. v A new RTE_X_SYSV_OVERRIDE_SYMBOLS parameter lets you override variables locally so that a runtime environment can be configured on a system other than the one on which it will run. v A set of parameters have been introduced to configure sharing runtime environments. RTE_X_HILEV_SHARING RTE_X_SMS_MGMTCLAS_SHARE RTE_X_SMS_PDSE_FLAG_SHARE RTE_X_SMS_STORCLAS_SHARE RTE_X_SMS_UNIT_SHARE RTE_X_SMS_VOLUME_SHARE RTE_X_SMS_VSAM_MGMTCLAS_SHARE RTE_X_SMS_VSAM_VOLUME_SHARE RTE_X_SMS_VSAM_STORCLAS_SHARE RTE_X_SMS_VSAM_VOLUME_SHARE v The following parameters have been added to allow you to override the global SAF class for logon, queries, or Take Action commands in the OMEGAMON enhanced 3270 user interface. To use these parameters, add them to the &rhilev_&rte_rkanparu(kob$penv) MEMBER (PARMGEN) or use the Nonstandard Parameter Editor (Configuration Tool). KOB_SAF_LOGON_CLASS_NAME KOB_SAF_QUERY_CLASS_NAME KOB_SAF_ACTION_CLASS_NAME KOB_SAF_LOGON_RESOURCE_PREFIX New in the previous release The following updates apply to the Tivoli Management Services Version Fix Pack 1 update of this book. v A new $GBL* configuration profile is now available. This addition profile provides a clearer categorization of GBL-like candidate parameters and differentiates them from LPAR-candidate parameters. The content of this configuration file varies, depending on customer deployment practices. The profiles are called in this order. The LPAR-specific one ($CFG$IBM or the &rte_name) member takes precedence over the $GBL* configuration profile: 6 IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/os Common Parameter Reference

15 rhilev.midlev.wconfig($sysin) v A number of the existing GBL_* parameters that were previously found in the $CFG* configuration file have been moved to $GBL$IBM/$GBL$USR. The latest version of this file is in rhilev.midlev.wconfig($gbl$ibm). v IBM Tivoli Monitoring v6.2.3 includes a new auditing facility that provides detailed messages for certain major state changes or events that occur within the environment (in Tivoli Enterprise Portal Server, the Tivoli Enterprise Monitoring Server, and the monitoring agents). Audit Events in the system reflect major and minor state changes, such as authorization and authentication failures, and do not reflect minor service messages stored in the RAS logs. These audit parameters can be customized for inclusion in the KDSENV member of the KDCSSITE member of the rhilev.midlev.rkanparu library for the monitoring server for monitoring agents on z/os or by editing the KDSENV values for the distributed monitoring agents. The following new parameters were added: Kpp_AGT_AUDIT_ITM_DOMAIN Kpp_AGT_AUDIT_MAX_HIST Kpp_AGT_AUDIT_TRACE Kpp_AGT_TEMA_SDA Kpp_SECURITY_ACTION_CLASS KDS_AUDIT_ITM_DOMAIN KDS_AUDIT_MAX_HIST KDS_AUDIT_TRACE KDS_KMS_SDA KDS_TEMA_SDA KDS_TEMS_DRA_FLAG GBL_HFS_JAVA_DIRn GBL_DSN_SYS1_SBPXEXEC RTE_SECURITY_CLASS RTE_USS_RTEDIR KOB_TOM_STC KOB_TOM_VTAM_APPL_LOGON KOB_TOM_VTAM_NODE v The list of parameters that describe a high-availability hub monitoring server has been enhanced considerably; the new parameters are: KDS_KCF_EXT_SECURITY KDS_KCF_MAX_ERROR KDS_KCF_SAFCLASS KDS_KMC_MQ_MAXROWS KDS_TEMS_HA_INCLUDE_Kpp KDS_TEMS_HA_TYPE KDS_TEMS_TCP_KDEB_INTERFACELIST KDS_TEMS_TYPE KMC_CFG_AUDIT_FLAG KMC_CFG_DATABASE_TYPE KMC_CFG_DB_DB2_DATABASE KMC_CFG_DB_DB2_NAME KMC_DEFAULT_RCACFG_NODENAME KMC_I_CFG_AUDIT_SETTING KMC_I_KCF_DB2_NAME KMC_NODENAME KMC_X_KCF_MAX_ERROR KMC_X_KMC_MQ_MAXROWS KMC_X_SECURITY_KCF_SAFCLASS KMC_X_SECURITY_KCF_EXT_SECURITY Kpp_AGT_TCP_KDEB_INTERFACELIST v The OMEGAMON enhanced 3270 user interface has its own set of common configuration parameters, each of which begins with "KOB". The new KOB parameters are: Chapter 1. Overview 7

16 KOB_TOM_STC KOB_TOM_VTAM_APPL_LOGON KOB_TOM_VTAM_NODE These parameters are described in a new chapter, Chapter 6, Enhanced 3270 user interface (KOB) parameters, on page IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/os Common Parameter Reference

17 Chapter 2. Common agent (KPP) parameters The KPP common agent configuration parameters are documented in this section. The definitions for the PP variable are found in the following table. Table 2. Common agent parameter prefixes Agent name IBM Tivoli System Automation for z/os IBM Tivoli OMEGAMON enhanced 3270 user interface IBM Tivoli OMEGAMON XE for CICS on z/os IBM Tivoli OMEGAMON XE for CICS TG on z/os IBM Tivoli Decision Support for z/os IBM Tivoli Composite Application Manager for SOA IBM Tivoli OMEGAMON XE for DB2 PE/PM IBM OMEGAMON z/os Management Console IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Configuration IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Monitoring IBM Tivoli OMEGAMON XE for Messaging - WebSphere Message Broker OMEGAVIEW and OMEGAVIEW II IBM Tivoli OMEGAMON XE on z/os IBM Tivoli NetView for z/os Agent IBM Tivoli OMEGAMON XE for Mainframe Networks IBM Tivoli Advanced Audit for DFSMShsm IBM Tivoli Advanced Reporting for DFSMShsm IBM Tivoli Advanced Allocation Management for z/os IBM Tivoli Automated Tape Allocation Manager for z/os IBM Tivoli Advanced Catalog Management for z/os IBM Tivoli Advanced Backup and Recovery for z/os IBM Tivoli Tape Optimizer for z/os ITCAM for Application Diagnostics on z/os Agent prefixes KAH KOB KOC, KC2, KC5 KGW KDO KD4 KO2, KD2, KD5 KHL KMC KMQ KQI KMV, KWO KOM, KM2, KM5 KNA KON, KN3 KRG KRH KRJ KRK KRN KRV KRW KYN Copyright IBM Corp. 2010,

18 KPP_AGT_AUDIT_ITM_DOMAIN This parameter is the audit domain name. Optional Location where the parameter value is stored KppENV member of the rhilev.rte.rkanparu library for the agent s runtime environment Parameter name and syntax ITM_DOMAIN=%Kpp_AGT_AUDIT_ITM_DOMAIN% Character string, maximum length 32. In the Configuration Tool (ICAT) Specify Advanced Agent Configuration Values KAG62P5 Field z/os Audit collection values: Domain Character string, maximum length 32. Kpp_AGT_AUDIT_ITM_DOMAIN Kpp_AGT_AUDIT_ITM_DOMAIN This field specifies an identifier that may be used to associate audit records. It is suited for commonly identifying agents that are associated with each other. An example use may be for sorting records by a particular customer. This field will also be used to create unique namespaces for RBAC. v KPP_AGT_AUDIT_TRACE on page 12 v KPP_AGT_AUDIT_MAX_HIST on page 11 v KDS_AUDIT_TRACE on page 256 v KDS_AUDIT_MAX_HIST on page 255 v KDS_AUDIT_ITM_DOMAIN on page IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/os Common Parameter Reference

19 KPP_AGT_AUDIT_MAX_HIST This parameter specifies the maximum in-memory cache entries; it is the maximum number of records kept in short-term memory for direct queries. Optional Location where the parameter value is stored The AUDIT_MAX_HIST parameter in the RKANPARU data set, member KPPENV for the agent s runtime environment. Parameter name and syntax AUDIT_MAX_HIST=%Kpp_AGT_AUDIT_MAX_HIST% In the Configuration Tool (ICAT) Specify Advanced Agent Configuration Values KAG62P5 Field z/os Audit collection values: Maximum in-memory cache entries Kpp_AGT_AUDIT_MAX_HIST Kpp_AGT_AUDIT_MAX_HIST The maximum number of records kept in short-term memory for direct queries. v KPP_AGT_AUDIT_TRACE on page 12 v KPP_AGT_AUDIT_ITM_DOMAIN on page 10 v KDS_AUDIT_TRACE on page 256 v KDS_AUDIT_MAX_HIST on page 255 v KDS_AUDIT_ITM_DOMAIN on page 254 Chapter 2. Common agent (KPP) parameters 11

20 KPP_AGT_AUDIT_TRACE This parameter indicates the trace level to pass messages. Optional Location where the parameter value is stored KppENV member of the rhilev.rte.rkanparu library for the agent s runtime environment. Parameter name and syntax AUDIT_TRACE=%Kpp_AGT_AUDIT_TRACE% M, B, D, X In the Configuration Tool (ICAT) Specify Advanced Agent Configuration Values KAG62P5 Field z/os Audit collection values: Enable/Disable z/os audit collection M, B, D, X Kpp_AGT_AUDIT_TRACE Kpp_AGT_AUDIT_TRACE This indicates the trace level to pass messages. Message trace levels, from low to high, are: X disabled M minimum B basic D detail Higher levels imply all lower levels. v KPP_AGT_AUDIT_MAX_HIST on page 11 v KPP_AGT_AUDIT_ITM_DOMAIN on page 10 v KDS_AUDIT_TRACE on page 256 v KDS_AUDIT_MAX_HIST on page 255 v KDS_AUDIT_ITM_DOMAIN on page IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/os Common Parameter Reference

21 KPP_AGT_CONFIGURATION_MODE Use the KPP_AGT_CONFIGURATION_MODE parameter to specify how you want to run the monitoring agent you are defining, in the agent address space or the server address space. Required Location where parameter value is stored The parameter value is not stored, but is used for internal processing. Parameter name N/A STANDALONE One of the following: v STANDALONE v CMS In the Configuration Tool (ICAT) CONFIGURE monitoring_agent KppVVMCU, where VV is the agent-specific panel ID. Field Configure monitoring_agent This value is set when you select Option 3 on this panel and complete the resulting set of panels. If you choose Option 3 then the value for this parameter is set to AGTCMS, which is strongly recommended for more monitoring agents, (meaning that the agent runs in its own address space). If you choose PF5 Advanced on Panel KppvvvMCU, then the value for this parameter will be set to CMS, which means that the agent runs in the run in the Tivoli Enterprise Monitoring Server (CMS) address space. This value must be selected for the IBM Tivoli OMEGAMON XE on z/os monitoring agent and the IBM Tivoli OMEGAMON XE for Storage on z/os monitoring agent since these agents run only in the monitoring server address space. No default One of the following: v STANDALONE v CMS v AGTCMS KPP_AGT_CONFIG KPP_AGT_CONFIGURATION_MODE PARMGEN classification Values that describe the address space Agent configuration option This parameter specifies how you want to run the monitoring agent you are defining. Chapter 2. Common agent (KPP) parameters 13

22 When defining an agent, you have the option to run the agent in an agent address space or in the server address space. For performance reasons, you should run the agent in an agent address space. If you plan to run the agent in the server address space, the runtime environment must contain a server. To run the agent in an agent address space, choose Option 3 (AGTCMS) in the Configuration Tool, which is the preferred configuration or specify STANDALONE in PARMGEN. Otherwise, by choosing PF5 Advanced from the KPPVVMCU panel (the monitoring_agent s main menu panel), you specify CMS in the Configuration Tool or TEMS in PARMGEN to run the agent in the server. The procedures outlined in the product-specific planning and configuration guide assumes that you are running the recommended configuration for this agent, which is running in the agent address space. 14 IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/os Common Parameter Reference

23 KPP_AGT_COMM_PROTOCOLn Use the KPP_AGT_COMM_PROTOCOLn parameter to specify the communication protocol for the TEMS connection. Valid values are IPPIPE, IP, SNA, IP6PIPE, IP6, IPSPIPE, and IP6SPIPE. When communication with the TEMS is initiated, the agent first tries protocol 1, then goes to protocol 2, and so on, in case of failure. Note: Update the corresponding Kpp_TEMS_TCP_*_PORT_NUM parameter for each Kpp_AGT_COMM_PROTOCOLx parameter enabled. For example, if Kpp_AGT_COMM_PROTOCOL1="IPPIPE", set the corresponding Kpp_TEMS_TCP_PIPE_PORT_NUM parameter. If Kpp_TEMS_COMM_PROTOCOL2="IP" (for IP.UDP), set the corresponding Kpp_TEMS_TCP_UDP_PORT_NUM parameter. Required Location where the parameter value is stored In the KPPENV member of the rhilev.rtename.rkanparu library Parameter name N/A IP.PIPE, IP.UDP, IP6.PIPE, IP6.UDP, IP.SPIPE, IP6.SPIPE, and SNA.PIPE In the Configuration Tool (ICAT) SPECIFY AGENT ADDRESS SPACE PARAMETERS KAG62P2 Field Specify the communication protocols in priority sequence. v IP.PIPE v IP.UDP v IP6.PIPE v IP6.UDP v IP.SPIPE v IP6.SPIPE v SNA.PIPE Example: KDE_TRANSPORT=\ IP6.PIPE PORT:1918 USE:N\ IP6.UDP PORT:1918 USE:N\ IP.SPIPE PORT:3660 USE:N\ IP6.SPIPE PORT:3660 USE:N\ IP.PIPE PORT:1918\ IP.UDP PORT:1918\ SNA.PIPE PORT: KPP_AGT_COMM_PROn Chapter 2. Common agent (KPP) parameters 15

24 KPP_AGT_COMM_PROTOCOLn PARMGEN classification Specify communication protocols preference for TEMS connection Agent Communication protocol n This parameter specifies the communication protocol to be supported by the monitoring agent, where n corresponds to a number between 1 and 7 to indicate the priority sequence for the communication protocols. In the Configuration Tool (ICAT), the seven fields corresponding to the communication protocols that can be supported are shown, and you can set the priority sequence for these protocols by assigning each field a value from 1 to 7, with 1 as the highest priority and 7 as the lowest. Leave blank any fields that represent unsupported communication protocols. The protocols, both supported and unsupported, are listed along with assigned port numbers in the KPPENV member, as shown in the Example section. Unused protocols are indicated by USE:N. Supported protocols are listed in priority order. 16 IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/os Common Parameter Reference

25 KPP_AGT_FLUSH_LSR_BUFR_INT_HR Use the KPP_AGT_FLUSH_LSR_BUFR_INT_HR parameter to specify the interval to force all deferred VSAM writes to DASD. Required Location where the parameter value is stored In the KPPAGST member in the rhilev.midlev.rtename.rkancmdu library Parameter name EVERY HH:MM:SS FLUSH (Flush VSAM buffers interval - hours) 0 hours, 30 minutes 0-24 In the Configuration Tool (ICAT) Specify Advanced Agent Configuration Values KAG62P5 Field Flush VSAM buffers: Hours 0 hours, 30 minutes, 0 seconds (seconds is not configurable) 0-24 KPP_AGT_FLUSH_INT_HR KPP_AGT_FLUSH_LSR_BUFR_INT_HR PARMGEN classification Advanced Agent configuration values Flush VSAM buffers interval - hours This parameter specifies the interval to force all deferred VSAM writes to DASD. The interval values are written as part of the third EVERY command in the KPPAGST member in the rhilev.midlev.rtename.rkancmdu library. The default is 0 hours (hh) and 30 minutes (mm). Chapter 2. Common agent (KPP) parameters 17

26 KPP_AGT_FLUSH_LSR_BUFR_INT_MIN Use the KPP_AGT_FLUSH_LSR_BUFR_INT_MIN parameter to specify the interval to force all deferred VSAM writes to DASD. Required Location where the parameter value is stored In the KPPAGST member in the rhilev.midlev.rtename.rkancmdu library Parameter name EVERY HH:MM:SS FLUSH (Flush VSAM buffers interval - mins) 0 hours 30 minutes 0-60 In the Configuration Tool (ICAT) Specify Advanced Agent Configuration Values KAG62P5 Field Flush VSAM buffers: Minutes 0 hours 30 minutes 0 seconds (seconds is not configurable) 0-60 KPP_AGT_FLUSH_INT_MIN KPP_AGT_FLUSH_LSR_BUFR_INT_MIN Flush VSAM buffers interval - mins This parameter specifies the interval to force all deferred VSAM writes to DASD. The interval values are written as part of the third EVERY command in: rhilev.midlev.rtename.rkancmdu(kppagst) The default is 0 hours (hh) and 30 minutes (mm). 18 IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/os Common Parameter Reference

27 KPP_AGT_ICU_LANGUAGE_LOCALE Use the KPP_AGT_ICU_LANGUAGE_LOCALE parameter to specify the language and codeset (system's locale) that you want the monitoring agent to use. Required Location where the parameter value is stored Generated in the KPPENV member in the rhilev.midlev.rtename.rkanparu library Parameter name LANG= (Language locale of z/os system) In the Configuration Tool (ICAT) Specify Advanced Agent Configuration Values KAG62P5 Field Language locale 1 (English - United States) v 1 (English - United States) v 2 (English - United Kingdom) v 3 (German - Germany) v 4 (German - Switzerland) v 5 (French - Belgium) v 6 (French - France) v 7 (French - Switzerland) v 8 (Spanish - Spain) v 9 (Italian - Italy) v 10 (Portuguese - Portugal) v 11 (Portuguese - Brazil) v 12 (Norwegian - Norway) v 13 (Swedish - Sweden) v 14 (Danish - Denmark) v 15 (Finnish - Finland) v 16 (Japanese - Japan) v 17 (French - Canada) v 18 (Traditional Chinese - Taiwan) v 19 (Simplified Chinese - China) v 20 (Albanian - Albania) v 21 (Bulgarian - Bulgaria) v 22 (Czech - Slovenia) v 23 (Dutch - Belgium) v 24 (Dutch - Netherlands) v 25 (Greek - Greece) v 26 (Hebrew - Israel) v 27 (Korean - Korea) v 28 (Lithuanian - Lithuania) v 29 (Macedonian - Macedonia) v 30 (Romanian - Romania) v 31 (Russian - Russia) v 32 (Serbian - Serbia) Chapter 2. Common agent (KPP) parameters 19

28 v 33 (Slovak - Slovakia) v 34 (Slovenian - Slovenia) v 35 (Thai - Thailand) v 36 (Turkish - Turkey) KPP_AGT_ICU_LANG KPP_AGT_ICU_LANGUAGE_LOCALE PARMGEN classification Advanced Agent configuration values Language and region for the z/os system. This parameter specifies the language and codeset (system's locale) that you want the monitoring agent to use. The language locale value is used for National Language support. This field requires the numeric value (1-36) representing the Language and Region in the table below. As an example, specify 1 for English - United States. The country and character set that this language represents (for example, country is en_us and character set is ibm-037) make up the LANG= environmental variable value generated in the KPPENV member in the rhilev.midlev.rtename.rkanparu library. For English - United States, LANG=en_US.ibm-037 is generated in KPPENV. From the Configuration Tool panel, press F1 (Help) and select Language locale for a list of the possible values. If you accept the default value of 1 (English - United States), the Configuration Tool generates this environment variable in KPPENV: LANG=en_US.ibm-037 If the z/os UNIX System Services (USS) codepage (en_us.ibm-1047) is required, you can specify either en_us.ibm-1047 or 1A in the Language locale field on the Configuration Tool panel. In batch mode, you can specify either of these values: KPP_AGT_ICU_LANG en_us.ibm-1047 KPP_AGT_ICU_LANG 1 In PARMGEN mode, you can specify either of these values for the USS codepage: KPP_AGT_ICU_LANGUAGE_LOCALE en_us.ibm-1047 The USS codepage (en_us.ibm-1047) is required for agent autonomy and for private situation XML files. 20 IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/os Common Parameter Reference

29 KPP_AGT_KGL_WTO Use the KPP_AGT_KGL_WTO parameter to activate write-to-operator messages for a particular agent. Required Location where the parameter value is stored In the KPPENV member of the rhilev.midlev.rtename.rkanparu library Parameter name KGL_WTO= (Enable agent WTO messages) YES YES or NO In the Configuration Tool (ICAT) Specify Agent Advanced Configuration Values KAG62P5 Field Enable startup console messages N Y, N KPP_AGT_KGL_WTO KPP_AGT_KGL_WTO PARMGEN classification Advanced Agent configuration values Enable agent WTO messages Specify Y to this parameter if you want a SYSLOG message on the console to indicate when the monitoring agent finishes initializing. You can use this message in an automation script. See the automation package for your site for further instructions on how to capture the monitoring agent startup automation message IDs. If you specify Y, the KGL_WTO=YES parameter is added to the rhilev.midlev.rtename.rkanparu(kppenv) member. The default is N for the Configuration Tool and YES for PARMGEN. Note: The existence of the KGL_WTO= parameter triggers the startup console messages. Therefore this parameter must not be present in the KPPENV member if you do not want this feature enabled. When it is enabled after configuration, the parameter is added to the KPPENV member. If you want to turn it off again, you must regenerate the Configuration Tool PP#3xxx job created in the monitoring agent Create runtime members step to refresh PP3ENV, where xxx is the JCL suffix. If you configured using PARMGEN, you can edit the configuration profile and recycle the monitoring agent. Chapter 2. Common agent (KPP) parameters 21